View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019964 | MMA | DB | public | 2023-04-25 21:09 | 2023-05-29 14:10 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | reopened | ||
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.0 | Fixed in Version | 2.0.0 | ||
| Summary | 0019964: Performance: background tasks use CPU/Battery to generate unneeded video thumbnails | ||||
| Description | Many users only want to use MMA for audio purposes. However, by default it initially scans for both audio and video files and then uses CPU/Battery to generate video thumbnails. All of this can be prevented by prompting the user what to include in the library when it's first run. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1085 | ||||
|
|
Considering that: - the issue can be easily resolved by removing a directory via Options > Library > Choose library folders - it's not desirable to force users to go through another config screen at install/first run A simple solution would be to optimize this along the following lines: 1) Initially generate ~ 20 video thumbnails from the /Video or /Movies directories 2) After that, only generate x thumbnails each time the user navigates to 'Video' or those specific folders |
|
|
Further optimization planned in 0018866 Fixed in build 2.0.0.1085 |
|
|
With build 1086, I noticed that notifications indicated 'generating thumbnails' for some time and this only disappeared when I ran MMA. This makes it appear to the user as if thumbnail generation is going on in the background for a long time (even though I suspect that it isn't). Log ID: 3PCXDVJH16 |
|
|
According to the log, no thumbnails were created, and only a check was performed(took less than a second). Notification remained displayed for an unknown reason (handled by OS in this case). I cannot replicate this, fortunately, this has no effect on the battery, hence we can lower the priority for this issue. |
|
|
Similar issue to 0020019 Unfortunately, notifications for those two cases are processed in ForegroundService handled by OS. There isn't a simple solution on the MMA side, I think on Android 13 this no longer happens and on Android 12 it happens very rarely and a future system update could resolve this. |
