|
Post by GoneMAD on Jun 29, 2022 20:02:06 GMT -5
i may see if i can find a cheap / used A52, cuz i think some of the users with the issue have that phone. I used to buy phones that were likely stolen on ebay for pretty cheap (basically phones that couldnt actually be used to make calls, but worked fine otherwise) i ended up picking a cheap samsung a13, that can be upgraded to android 12. So hopefully i'll be able to recreate a lot of these samsung specific issues. I figure their lower end devices are likely to have more of the problems (i think they support their flagship devices fairly well)
|
|
|
Post by GoneMAD on Jul 1, 2022 11:58:45 GMT -5
well so far i cannot reproduce it. its on android 11 and oneui 3.1 will tryu to update it to 12 / 4.1
I am assuming the metadata in the notification issue is specific to android 12 with oneui 4.1? Can those with the issue send in an error report from in app via email? I am wondering if there is some weird combination of settings? I tried crossfade on and off
|
|
|
Post by jeddix on Jul 2, 2022 3:49:57 GMT -5
I didn't change any settings since the last time i sent them to you.
|
|
|
Post by bwaldron on Jul 2, 2022 6:45:50 GMT -5
I didn't change any settings since the last time i sent them to you. Same here -- and I no longer have GMMP installed on my phone. I can confirm that on my Samsung S10e, the issues appeared only after the phone was updated to Android 12 and OneUI 4.0. No issues before that.
|
|
|
Post by GoneMAD on Jul 2, 2022 12:29:13 GMT -5
good news guys. i updated the device to android 12 / oneui 4.1 and can easily reproduce the issue!
will look into the cause after the holidays and see if i can find a fix. Well worth the 80 bucks to buy this a13 (found another issue as well with the background album art in now playing not showing up correctly)
|
|
|
Post by bwaldron on Jul 3, 2022 5:42:12 GMT -5
good news guys. i updated the device to android 12 / oneui 4.1 and can easily reproduce the issue! will look into the cause after the holidays and see if i can find a fix. Well worth the 80 bucks to buy this a13 (found another issue as well with the background album art in now playing not showing up correctly) Tremendous!
|
|
|
Post by patrick on Jul 4, 2022 9:10:09 GMT -5
if you happened to fix your tags, including the albumartist after the albums were scanned in.. the multiple albums will not get merged together Does your all album list show multiple copies of the album? Edit: case changes (only case changes) after a tag edit being reflected in the database until one of the more recent 3.3.x patches The all albums list shows only one Album (but. With the wrong lower case letter). And is there a possibility to rescan the Album or sth. after I changed the tags? To remove the files, clear database, move them back and scan again seems not like a very intuitive or good way.. Maybe a rescan database option would be a good option to implement. (Clearing database is no option, as then the date added will get lost)
|
|
|
Post by MotleyGord on Jul 4, 2022 9:51:46 GMT -5
The all albums list shows only one Album (but. With the wrong lower case letter). And is there a possibility to rescan the Album or sth. after I changed the tags? To remove the files, clear database, move them back and scan again seems not like a very intuitive or good way.. Maybe a rescan database option would be a good option to implement. (Clearing database is no option, as then the date added will get lost) I’ve thought the same, something to trigger the scanner manually to look for any changed files since they were last scanned. Mostly looking for tag edits that would have been updated externally, like the example from patrick.
|
|
|
Post by GoneMAD on Jul 4, 2022 10:05:30 GMT -5
send in your database file so i can take a look at how you managed to get in a situation like that. It sounded like you had music that was not tagged correctly (multiple artists for a single album so multiple albums were added due to how the scanner works), and then fixed it in app and the cleanup didnt remove all the extra albums in the database like its supposed to
Scanner does only scan in files that have changed. it keeps track of the last date modified and will only scan the file if that date modified is different from whats in the database. Changing tags in app also updates the database
|
|
|
Post by GoneMAD on Jul 6, 2022 22:02:17 GMT -5
i figured out the notification issue. So in android 11 and newer.. the playing metadata / playstate is taken from the "MediaSession" (which is also used to send metadata over bluetooth and whatnot), however the notification buttons and the structure of the notification is handled through the Notification apis. These samsung devices will not force an update of the notification when only the mediasession metadata gets updated. GMMP updates the notification and mediasession asynchronously, on these devices the notification appears to get updated first, and then the mediasession would get updated. This is why the previous track would show up. It's a race condition so depending on the timing of the updates, sometimes their update order would be different. I added some code to force a notification update AFTER the mediasession update and it appears to be working 100% of the time.'
Fix will be in 3.3.7
|
|
|
Post by jeddix on Jul 7, 2022 11:39:14 GMT -5
That's nice to hear.
|
|
|
Post by GoneMAD on Jul 12, 2022 22:10:54 GMT -5
Rolling out to google play:
3.3.7 (2022/07/12):
Fixes: -OpenSL decoder is now used as a fallback when main decoder fails to open a file -Finally fixed android 11+ media notifications showing the previous track info on some devices -Fixed some smart playlist issues with files with multiple genres or multiple artists -Reduce number of extra db queries in some views -List items now display correctly after custom metadata is changed without having to reload the UI -Only first artist of a multi artist track will now be used for scrobbling -Fixed now playing layout 1 status bar color in landscape -Fixed now playing album art / blur background not taking up the full screen on some devices -Fixed rare fdsan crash
|
|
|
Post by bwaldron on Jul 15, 2022 8:00:11 GMT -5
Got 3.3.7 from Google Play and can confirm that the notification issue with my Samsung S10e has been fixed. I'm so happy to return to using GMMP rather than Poweramp (a fine app in its own right, but lacks some GMMP features/customizability that I have grown to depend on).
|
|
|
Post by MotleyGord on Jul 15, 2022 13:37:53 GMT -5
3.3.7 (2022/07/12): Fixes: -Fixed some smart playlist issues with files with multiple genres or multiple artists -List items now display correctly after custom metadata is changed without having to reload the UI -Fixed now playing layout 1 status bar color in landscape These three items I can confirm are all working now on my Android 8.1 device (iBasso DX160 DAP).
|
|
|
Post by jeddix on Jul 17, 2022 9:39:47 GMT -5
Just found the time to test the new version and the notification problems are indeed fixed on my A52s.
Maybe it's finally time to upgrade to 3.x when the final version hits the play store.
|
|