View Issue Details

IDProjectCategoryView StatusLast Update
0018866MMAGeneralpublic2023-10-17 22:31
Reportermartin Assigned To 
PriorityurgentSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
PlatformAndroidOS-OS Versionall
Product Version1.4.4 
Target Version2.0.0Fixed in Version2.0.0 
Summary0018866: Performance: Libraries are scanned frequently, and takes several minutes (or longer) each time for some
DescriptionScanning and comparing changes can take awhile (several hours for some large libraries), and occurs every half hour, and on other occasions. It also occurs every time MMA is launched, causing it to take some time before the user can initiate playback (loading.... appears on the screen for a few seconds, and the scanning process can take much longer).

The process should be optimized, and should be launched only when necessary.

If the process still takes awhile for very large libraries, we can consider making auto-scanning configurable like in MMW. e.g.
Scan automatically
[ ] Scan for changes on startup and when MediaStorage updates are detected.


Scan automatically
[ ] On startup
[ ] When MediaStorage updates are detected
[ ] Every 30 minutes
Additional Information
Ticket # 3506
TagsNo tags attached.
Fixed in build1151


related to 0016233 newmartin WiFiSync: Start of sync should stop Media Scanner 
related to 0019972 newmartin Library Scan settings are overridden by Sync settings 
related to 0019964 resolvedmartin Performance: background tasks use CPU/Battery to generate unneeded video thumbnails 
related to 0020085 newmartin Scanning UI layout/terminology tweaks 



2023-06-21 13:20

developer   ~0072249

Can take more time to identify cases to improve.

Currently, it's executed only at startup at least after 30 minutes, and only if some changes are detected, so there is no need to make an option for this.

re 1) media from library folders must be scanned, otherwise, they would not be known to exist and could be downloaded and duplicated. Also, the missing tracks would not have been downloaded if they still existed in the database.
This would also affect playlists.

I have to test it with a huge library and identify what causes an issue.
I believe that the most pain will be huge playlists and maybe folder tree scanning.


2023-10-04 11:40

developer   ~0072991

Last edited: 2023-10-05 08:24

Fixed in build


2023-10-17 22:31

developer   ~0073149

Verified 1151