3.0.4 - issue with scanner?

[eckless]

Hi there! You mentioned there were a lot of changes in the scanner that went into 3.0.4 - I'm having trouble getting the scanner to work on 3.0.4.

* Worked on 3.0.3 (although there were slownesses with picking up album art, etc - which I know was one of the things you were trying to fix)
* When I hit scan (no other changes from 3.0.3), the notification will go up to some number - like "Scanning: 331 tracks found" - and then stay there. (I have over 10000 tracks). It stays there for several minutes - eventually I get "Scanning: 0 tracks found", or it stays on "Scanning: 331 tracks found". The 331 changes - sometimes it gets to the 1000-1500 area. But it always stops at some point.
* I have tried uninstall/reinstalling.

Anybody else having this issue on 3.0.4? I appreciate the efforts in making the scanner run more smoothly!

Thank you!
Eckless

[GoneMAD]

run a scan and then generate a logcat when it appears to stop. gonemadmusicplayer.blogspot.com/2014/07/how-to-get-logcat-system-log-to-help.html

The scanning algorithm actually stayed the same as 3.0.3 but i moved the art searches to be part of the background scan instead of launching it separately (that was causing the slowdown) and restricting it to local storage only during the scan. My guess would be something is causing an error thats killing or hanging the scan.

Just a note that the notification only shows new tracks, so if something is already in the database its not going to increment the notification counter

[GoneMAD]

also try one thing... try actually deleting the app cache/data. I have a feeling that since 3.x is targeting the newer versions of android.. that it auto backs everything up (including internal corrupted data). I've had a few times where i'd reinstall the app.. turn away for a minute and come back to it being configured exactly how it was before. I dont think the app cache/data wipe will do that. Hopefully thats the issue because one of the other users i was working with that had major scanner issues said that 3.0.4 fixed his problems. I also verified that even if an art search would throw an error.. it would be caught and the scan would continue on.. so that wouldnt be the problem

[eckless]

Thank you - solution was to clean out the temporary files in the "Files" app. (Had plenty of space on the phone, but apparently too many temporary files). Scanner works very well now - and quickly. Thank you!!!

[GoneMAD]

awesome

[wicky]

I've had the same issue, I think also starting with 3.0.4 though that was also around the time I upgraded to Android 11. One of those cleared my library and I haven't been able to get the scanner to finish a run since. I've got ~20,000 songs stored on an SD card, and it starts and gets through a few thousand of them, but inevitably stops at some point and starts scanning from the beginning. (The most it's gotten through is about 7,000)

Tried turning off battery optimization and leaving it on Stay Awake mode with only GoneMAD running, but it doesn't seem to help. (Also just tried worked for eckless, in addition to reinstalling and clearing all data storage for the app, but still have the same problem..)


Any thoughts?


Edit: Attempted to create and send a bug report, it's too large to attach here but emailed to [e-mail], subject: bugreport-BabyGroot_00WW-RKQ1.200928.002-2021-02-14-15-36-24.zip

[GoneMAD]

been dealing with this over email.. but i wanted to post to see if anyone else still had the issue?

In wicky's case his device is killing the scanner after about 40 seconds (which i find quite ridiculous.. stock android gives 8-10 minutes at least)

[MotleyGord]

Mine gets killed at exactly 10 minutes. After a few seconds, the scanner resumes from 0 and finishes the scan. My library has 24k songs total, the scanner typically gets to around 20k at the 10 minute mark. I have a LG G8 with Android 10.
I also have a DAP, iBasso DX160 at Android 8.1. With the same 24k song library the first pass gets to around 18k as the processor is a bit slower. It also times out at 10 minutes,but again resumes and finishes on the second pass.

[GoneMAD]

yea thats what typically happens with my one test device with around 25k tracks

[scott]

I saw a problem like this, maybe a few GoneMAD versions ago. Since I deleted all of GoneMAD's cache and storage with the Android settings menu, it has been able to complete scans. However it misses MP3 tags of new songs, as discussed here:
gonemadmusicplayer.proboards.com/thread/1184/scanner-find-tags

[GoneMAD]

Feb 15, 2021 22:46:57 GMT -5 scott said:

I saw a problem like this, maybe a few GoneMAD versions ago. Since I deleted all of GoneMAD's cache and storage with the Android settings menu, it has been able to complete scans. However it misses MP3 tags of new songs, as discussed here:
gonemadmusicplayer.proboards.com/thread/1184/scanner-find-tags

next patch i hope to have an approach to solve this

[nicks]

I didn't want to open a new thread since my issue is still scanner related so here it is: (First of all i must say that i have the app (latest update) on my car's player so there is no killing of the scanner i think since the screen is always on)

Lets say i have 25000 tracks on my hd. I ve been running the scanner for some time,i check the Database Stats and see it has registered 24500 tracks. I exit the player,re-open it and start the scanner again to find the rest of the tracks (500 tracks) (the Database Stats still showed 24500 before the new scan,so it remembers what it has scanned).I start the scanner and it keeps scanning but it doesn't stop on 500 tracks found as it should be because it had already found 24500 tracks.It is still finding new tracks.1000,2000,3000.. it wont stop.

So what is the scanner doing?Re-scanning the whole library?

I also have another issue that is maybe related.When i enter a folder it takes some seconds to open it/display the track list,like it was not scanned before,it also won't load the track i press to play as fast as it should.

This behavior was not present on the previous (old) version of the player.

[GoneMAD]

the counter will increase if its rescanning/updating a file. it'll do that if the modified date of the file is larger than whats stored in gmmp's database (which would indicate the file was modified since it was scanned in). Also some things like cue files will increase the counter every scan

"I also have another issue that is maybe related.When i enter a folder it takes some seconds to open it/display the track list,like it was not scanned before,it also won't load the track i press to play as fast as it should."

if a scan is running that might be slower just because the scanner is also reading from disk at the same time

edit: also a note.. i've mentioned it a few places.. you shouldnt have to run manual scans. GMMP stays in sync with the android media library and as of 3.0.9 it should always auto scan file before playing if its not already in the database. Older versions had a bug where it was basically a race condition on whether it would play or not, but i fixed that