I found another issue. With OS12/Samsung OneUI4, the device lock screen was no longer showing the playing track info, just the MMA icon. Other media apps were showing the playing track info.

Turns out this is an issue with having the "Playback Notification" set to anything other than "System". I had it set to "Small" to conserve space in the notification shade.

[quote=Peke post_id=494222 time=1644010588 user_id=213]
Hi,
I hope second log was sent, I can't open imgur images due the "Cross site xss scripting threat" :([/quote]
I think the second one went through. At least, no crash on my end on sending.
[quote]
I have seen that soem users report similar thin and they had to tap on notification to show MMA player, also there is notification settings in MMA Options, so try other ones.
[/quote]
Ok, here are the screen shots via ImgBB (I hope, the preview doesn't show them):

[URL=https://ibb.co/tHfkGFv][IMG]https://ibb.co/tHfkGFv[/IMG][/URL]
[URL=https://ibb.co/YWDXdHt][IMG]https://ibb.co/YWDXdHt[/IMG][/URL]

Hi,
I hope second log was sent, I can't open imgur images due the "Cross site xss scripting threat" :(

I have seen that soem users report similar thin and they had to tap on notification to show MMA player, also there is notification settings in MMA Options, so try other ones.

My Samsung Galaxy s20+ (unlocked on Verizon (USA)) updated from OS11 to 12 yesterday. I have restarted a couple times since.

I'm now having intermittent issues with MediaMonkey not showing the lock screen or notification panel miniplayer, or failing to load the application.

Two screen shots of the first issue (on imgur.com). This one shows the lockscreen [url]https://imgur.com/dFCUpgy[/url], and this one shows the notification panel [url]https://imgur.com/oHzeVmL[/url].

I tried to capture a screen recording of the failure to launch, but because of how the layouts work, I the "start recording" button got covered by the phone's "app isn't responding" dialog, and when I went to start the recording first and then open MMA, it opened normally.

I just sent logs from MMA, log ID unknown: I also told it to save locally, but the local file is showing as zero bytes and naturally cannot be opened, moved or shared. Maybe has something to do with the fact that the app crashed when I sent the log... second attempt, reading the log ID off the dialog: K6L7WDK641, this one appears to have gone through.