View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012501 | MMA | General | public | 2015-01-16 20:17 | 2015-01-28 07:14 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.1.0 | ||||
| Target Version | 1.1.0 | ||||
| Summary | 0012501: MMA takes 1-2 seconds to start up (regression 369) | ||||
| Description | As of build 369, if MMA isn't running in the background and is launched, it takes ~1-2s for it to become active. First it launches with a black screen, and then after another ~1 seconds, the UI becomes active. The startup time appears to be proportional to the size of the library (i.e. a device with only a hundred tracks started up immediately, but the observed delays occurred with 2 devices that each had 0000198:0001000 tracks). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Is it really a regression ? I do not see any difference between build 346 and 370 ? It take some time to start but it always took ~1s to start. I have library with 600 tracks |
|
|
It's unclear to me whether it's a regression as the issue doesn't seem to occur consistently. e.g. on a Nexus 5, after the first couple of times running, the issue seems to go away (maybe some app data is cached?). However, I timed it, and on a Galaxy Tab (where all content is stored on an SD card), a black screen appears for 1.6s before the MMA UI appears. So whether this is a regression or not, it's too long. Is there a way to optimize this? |
|
|
So do You mean that you saw black screen for 1.6s. Then the UI occuerred and was immediately ok (not frozen)? Could you please send me log immediately after this occurrs? Btw there are many initializations that are needed for UI too. But it take .5 - .8 seconds for me and I am trying it with old SGS2 (4.4 kitkat). I think that it might be related to storage recognition procedure (different storage type). |
|
|
I can no longer replicate this in 370. Will test further... |
|
|
This seems to have been a transient issue (perhaps related to a database update). Resolving--no change needed. |
|
|
Closing. |
