Server Version#: 1.26.1.5772
Player Version#:4.2.1
I have been using Plex amp for quite a long time, mostly since Google play music was cancelled. Since I got android 12, plexAmp has been behaving oddly on a few fronts.
Background - I typically listen to music when I’m riding my motorbike. In the past I have used plug in headphones but since phones no longer come with 5.5 mm jacks, I now use a bluetooth headset, either the comm module in my helmet, or my wireless earbuds.
After I arrive home from work, I pause the music and disconnect the bluetooth device. The next morning, I reconnect the bluetooth device. Previous to Android 12, if I just hit play on my bluetooth device the music will resume. Since I got my Pixel 6, this function is sporadic. but mostly wont play. I open my phone and on my lock screen, Plexamp (widget??) shows the last song played with a play, fwd and back button. Rarely, if ever, pressing play resumes the music. The majority of the time, if I press play, the widget disappears. When this happens, I unlock the phone and when I tap on the app, the music instantly starts playing (resumes).
There are a couple other issues I am experiencing but one thing at a time.
Not something that I can help you with, other than to say that I was seeing similar behaviour on my previous handset when it was running Android 11. I still see it on my new handset running Android 12.
I have simply resigned myself to opening the Plexamp app every time I want to restart music. That seems fairly reliable, but that’s not to say that I don’t share your sentiments about the Plexamp “media controls” (that seems to be the given name for the play/pause/skip buttons that are shown when you pull down on the notification shade).
I open my phone and on my lock screen, Plexamp (widget??)
I think this is a notification, you could confirm for me by unlocking the phone, pulling down the notifications draw and trying the play button there if it’s present.
You mean, instead of tapping the play from the notification, instead open the phone and pull down from the top and pressing that play button? I will do that in the morning and let you know
Interesting. I searched this forum and nothing came up remotely close, and then you are able to preproduce it in a few tries. That’s excellent. Thank you.
It only happens if the notification controls are used after a long period of idle (in my case > 1 hour) so I can see why it wouldn’t get reported that frequently.
Understood. Question about that. If I connect my headset after that period, and use the play function on my headset, is that the same as using the notification controls?
The headset button action should already try to use code which doesn’t require the app to be open. It can take a few seconds though as the app needs to cold start before we can start playing.
