mporcas Posted December 21, 2023 Share Posted December 21, 2023 Thanks Andre. I've installed the APK, overwriting the Play version. I'll test it out tomorrow (I have a long drive planned!) and report back. I did try enabling beta versions on Play but it wouldn't give me the new version. I guess it doesn't trigger until a new beta version arrives in the Play store?? Link to comment Share on other sites More sharing options...
andrewilley Posted December 21, 2023 Share Posted December 21, 2023 @mporcas The Play Store beta versions are sometimes a little behind the website releases. So the first people who get a beta update will always be those who manually install it, and thus they know that they've done it. Andre Link to comment Share on other sites More sharing options...
Richard Robertson Posted December 21, 2023 Share Posted December 21, 2023 I got build 980 from Play Store beta. Thank you so much for adding that filter. It'll be nice to hit next on my steering wheel at the end of a folder and not wonder if it's going to loop back to the beginning of the same folder. Link to comment Share on other sites More sharing options...
sorosch Posted December 21, 2023 Share Posted December 21, 2023 @andrewilley: Thank you very much for the very quick answer. I test it and get in touch here again in a few days. Link to comment Share on other sites More sharing options...
Richard Robertson Posted December 25, 2023 Share Posted December 25, 2023 (edited) It happened again. I have it set to ignore all shuffle/repeat Bluetooth commands but it did it anyway. I still don't understand why my car would be trying to set the repeat mode when I hit next but somehow it got around the filter setting. Edited December 25, 2023 by Richard Robertson missed the log photo Link to comment Share on other sites More sharing options...
sorosch Posted December 26, 2023 Share Posted December 26, 2023 I can confirm. The problem continues to occur for me - although "Ignore Reteat/Shuffle" is activated. I also increased "Ignore Bluetooth Commands" to 10 seconds - unfortunately it didn't work either. Link to comment Share on other sites More sharing options...
automp Posted December 29, 2023 Share Posted December 29, 2023 (edited) Same here. My cars audio system (Ford/Sync) keeps setting play mode to repeat. I updated to the beta 981 version and set all repeat/shuffle bluetooth commands to ignore. No effect at all. I'm using Android 14/OneUI 6.0 too. Edited December 29, 2023 by automp Link to comment Share on other sites More sharing options...
andrewilley Posted December 29, 2023 Share Posted December 29, 2023 @sorosch @automp Could you both confirm what you see in the Last Processed Commands log when this happens. Thanks. Andre Link to comment Share on other sites More sharing options...
automp Posted December 30, 2023 Share Posted December 30, 2023 @andrewilley Sure... these are the commands happening when the phone connects to the car. Each time i try changing the play mode (press the button) then, the last visible command keeps showing up again. The play mode stays on repeat ================== 13:40:47.995 BTReceiver headset event connection BT=true am mode=0 SYNC ================== 13:40:48.389 PlayerService onRoutingChanged newDevice=bt oldDevice=speaker ================== 13:40:48.395 PlayerService reloadPipeline allowPlaying=true forceResume=false state after reload=2 ================== 13:40:49.431 PlayerService reloadPipeline allowPlaying=true forceResume=false state after reload=2 ================== 13:40:54.177 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=396036978 sourcePak=com.android.bluetooth isAvrcp IGNORED due ignore_bt_sec lastRouteTimeDiff=4653 lastBTTimeDiff=6203 ================== 13:40:54.179 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=396036982 sourcePak=com.android.bluetooth isAvrcp IGNORED due ignore_bt_sec lastRouteTimeDiff=4656 lastBTTimeDiff=6206 ================== 13:40:54.694 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=396037498 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=2 ================== 13:40:54.738 PlayerService RESUME from PSMediaButtonReceiver resumePlaying ================== 13:40:54.740 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=396037543 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=2 ================== 13:40:54.798 PlayerService RESUME from PSMediaButtonReceiver resumePlaying ================== 13:40:57.305 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.android.bluetooth Link to comment Share on other sites More sharing options...
sorosch Posted December 30, 2023 Share Posted December 30, 2023 I tried again other Bluetooth devices (various Bluetooth headphones, soundbar, bluetooth radio) - Poweramp works correctly for everyone - only if the smartphone connects with the carradio, the problem occurs ("Zur nächsten Liste springen" --> will be set up again and again "Wiederhole Liste") ================== 13:08:09.978 HeadsetPlugReceiver headset event disconnection BT=false am mode=0 no_keep_notif_on_dscn=false ================== 13:08:09.987 BTReceiver headset event disconnection BT=true am mode=0 LE-Bose QC Earbuds II no_keep_notif_on_dscn=false ================== 13:08:11.112 PlayerService onRoutingChanged newDevice=speaker oldDevice=bt ================== 13:08:11.112 PlayerService reloadPipeline allowPlaying=false forceResume=false state after reload=2 ================== 14:01:59.090 BTReceiver headset event connection BT=true am mode=0 BMW 12313 ================== 14:01:59.091 BTReceiver RESUME resume_on_bt delay=500 ================== 14:01:59.367 PlayerService onRoutingChanged newDevice=bt oldDevice=speaker ================== 14:01:59.570 PlayerService RESUME from BTReceiver resumePlaying ================== 14:02:02.674 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.google.android.bluetooth ================== 14:04:53.917 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=1520704 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 14:04:53.992 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=1520722 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 14:04:54.009 PlayerService PAUSE from PSMediaButtonReceiver pausePlaying ================== 14:04:54.020 BTReceiver headset event disconnection BT=true am mode=0 BMW 12313 no_keep_notif_on_dscn=false ================== 14:04:54.049 HeadsetPlugReceiver headset event disconnection BT=false am mode=0 no_keep_notif_on_dscn=false ================== 14:04:55.495 PlayerService onRoutingChanged newDevice=speaker oldDevice=bt ================== 14:04:55.496 PlayerService reloadPipeline allowPlaying=false forceResume=false state after reload=2 ================== 14:47:42.770 BTReceiver headset event connection BT=true am mode=0 BMW 12313 ================== 14:47:42.770 BTReceiver RESUME resume_on_bt delay=500 ================== 14:47:43.011 PlayerService onRoutingChanged newDevice=bt oldDevice=speaker ================== 14:47:43.011 PlayerService reloadPipeline allowPlaying=true forceResume=false state after reload=2 ================== 14:47:43.295 PlayerService RESUME from BTReceiver resumePlaying ================== 14:47:45.456 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.google.android.bluetooth ================== 14:50:30.388 PSAudioFocusHelper AUDIOFOCUS_LOSS_TRANSIENT_CAN_DUCK duckPlaying ================== 14:50:32.716 PSAudioFocusHelper AUDIOFOCUS_GAIN ================== 14:50:33.070 PlayerService UNDUCK afterFocus ================== 14:51:41.137 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=1935815 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 14:51:41.139 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=1935816 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 14:51:41.148 PlayerService PAUSE from PSMediaButtonReceiver pausePlaying ================== 14:51:41.216 BTReceiver headset event disconnection BT=true am mode=0 BMW 12313 no_keep_notif_on_dscn=false ================== 14:51:41.235 HeadsetPlugReceiver headset event disconnection BT=false am mode=0 no_keep_notif_on_dscn=false ================== 14:51:42.703 PlayerService onRoutingChanged newDevice=speaker oldDevice=bt ================== 14:51:42.703 PlayerService reloadPipeline allowPlaying=false forceResume=false state after reload=2 Link to comment Share on other sites More sharing options...
maxmp Posted December 30, 2023 Share Posted December 30, 2023 @sorosch thanks for the logs - the Shuffle/Repeat ignoring logic will be improved in the next build. Link to comment Share on other sites More sharing options...
sorosch Posted December 31, 2023 Share Posted December 31, 2023 @maxmp Great to hear - Thank you very much. I wish you a all a happy new year Link to comment Share on other sites More sharing options...
mporcas Posted January 9 Share Posted January 9 I don't know if it's relevant but the repeat and shuffle buttons on the head unit in my car don't actually appear to do anything when playing from my phone. Could there have been some changes to the Google APIs or the Android Auto APIs that are causing both the issues previously mentioned in this post, and the buttons not working? Is there a mis-match between the shuffle mode codes, i.e. does 'repeatMode=2' mean something different now and it's trying to confirm between the systems and resetting it due to the differing codes? Just a thought... Link to comment Share on other sites More sharing options...
Richard Robertson Posted January 19 Share Posted January 19 Any update on the filter not working? Even with ignore shuffle/repeat on the Bluetooth menu, it's still forcing album/folder repeat mode when I want it to play the next one (repeat off). Link to comment Share on other sites More sharing options...
andrewilley Posted January 19 Share Posted January 19 Yes, Max said it would be further improved in the next beta build. Andre Link to comment Share on other sites More sharing options...
Donnie1490 Posted March 16 Share Posted March 16 Hello new here Any update on this? This has been the most annoying bug, it only happens for me when connecting to my car Bluetooth when a shuffle is already set. I have a bluetooth speaker in my house that I tested this on, connecting and disconnecting and it doesn't do this, it continue the shuffle with no problem Link to comment Share on other sites More sharing options...
andrewilley Posted March 16 Share Posted March 16 @Donnie1490 Make sure you are running the latest beta build of Poweramp (981) and enable Settings=>Headset/Bluetooth=>Ignore Repeat/Shuffle. That should make Poweramp ignore the Repeat or Shuffle commands that are being sent to it. If this does not work for you, please post your 'Last Processed Commands' log here (from the same menu). Andre Link to comment Share on other sites More sharing options...
mporcas Posted March 16 Share Posted March 16 Hi @andrewilley. Mine still does it, despite upgrading to build 981 back in Jan. My logs are currently blank, not sure why, but I can post once I have some. I'm sure someone mentioned that this would be improved in the next beta. It's been a while since 981 came out, is the next one expected soon? Link to comment Share on other sites More sharing options...
Richard Robertson Posted March 16 Share Posted March 16 Same here. It still changes repeat mode over Bluetooth on me even with ignore all enabled. That was why I asked about it again in January. Link to comment Share on other sites More sharing options...
Matt Gertz Posted March 20 Share Posted March 20 This hit me again yesterday as well (I'm not using the beta, I should mention -- not even sure how to do that, TBH) -- I was demonstrating a new playlist to a friend, and I didn't notice that "Shuffle Just Songs" got changed to "Shuffle All Available Songs" when my truck's Bluetooth (Ford Sync 3/Android Auto) connected, and the next thing I knew, I was suddenly playing a Christmas song once the current acid jazz track finished. This sort of thing has happened about 20% of the time since my phone got upgraded to Android 14 in November, and so as of last night I've temporarily shifted to a free (albeit much more limited) player until this problem gets worked-around. I'd really, really rather use Poweramp because it's awesome and a lot more fully-featured that pretty much any other player -- but, paradoxically, the fact that it has so many shuffle and replay options makes it more affected by this Android 14 behavior change than many other players. Most other players I've seen limit shuffling and replay to whatever the current album or playlist is, so it's not as big of a deal if those get toggled by this Bluetooth weirdness -- you can fix that from the controls on the steering wheel, as you are still "in" the current "category." But if a Bluetooth change happens that takes you out of the current album or playlist (for me, it's been the shuffle-shift mentioned above), the only recourse is to hope that verbal commands will work correctly to re-select the playlist or album -- beyond that, I have to hope for a very long red traffic light to do the several clicks and swipes to get me back to where I was. (There was some indication that Android was going to investigate why they were suddenly messing up player apps with this Bluetooth oddness back in November, but I have been unable to locate any info on how that was coming along... I feel bad for you Poweramp folks.) Link to comment Share on other sites More sharing options...
andrewilley Posted March 20 Share Posted March 20 @Matt Gertz You can get the latest Poweramp beta builds from the Download tab at the top of the page. Currently build 981 is the latest: This may allow you to fix your issue, but a number of users have reported that it is still happening with their Android 14 variants even with the new 'ignore' option enabled. Max is planning to add a better workaround in the next release. Andre Link to comment Share on other sites More sharing options...
mporcas Posted March 20 Share Posted March 20 On 3/16/2024 at 9:20 AM, mporcas said: Hi @andrewilley. Mine still does it, despite upgrading to build 981 back in Jan. My logs are currently blank, not sure why, but I can post once I have some. I'm sure someone mentioned that this would be improved in the next beta. It's been a while since 981 came out, is the next one expected soon? Here's my last commands BTW. ================== 16:01:41.561 BTReceiver headset event connection BT=true am mode=0 Ford Audio ================== 16:01:41.561 BTReceiver RESUME resume_on_bt delay=500 ================== 16:01:42.501 PlayerService RESUME from BTReceiver resumePlaying ================== 16:19:22.590 PSAudioFocusHelper AUDIOFOCUS_LOSS_TRANSIENT inPhone ================== 16:19:22.590 PSAudioFocusHelper PAUSE pauseInCall ================== 16:20:31.254 PSAudioFocusHelper AUDIOFOCUS_GAIN ================== 16:20:31.255 PSAudioFocusHelper RESUME after call or audio focus ================== 16:26:07.341 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=81299839 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 16:26:07.344 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=81299848 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 16:26:07.360 PlayerService PAUSE from PSMediaButtonReceiver pausePlaying ================== 16:26:08.114 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=81300617 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=2 ================== 16:26:08.190 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=81300694 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=2 ================== 16:26:11.043 HeadsetPlugReceiver headset event disconnection BT=false am mode=0 no_keep_notif_on_dscn=false ================== 16:26:11.083 BTReceiver headset event disconnection BT=true am mode=0 Ford Audio no_keep_notif_on_dscn=false ================== 16:26:12.128 PlayerService onRoutingChanged newDevice=speaker oldDevice=bt ================== 16:26:12.128 PlayerService reloadPipeline allowPlaying=false forceResume=false state after reload=2 Link to comment Share on other sites More sharing options...
andrewilley Posted March 20 Share Posted March 20 @mporcas I can't see anything in that log that should be affecting Shuffle/Repeat status. @maxmp might be able to comment further though. I think what is usually the culprit is this sort of thing: Andre Link to comment Share on other sites More sharing options...
mporcas Posted March 20 Share Posted March 20 Ha ha, just noticed it doesn't say anything about me changing the repeat. Will try again tomorrow. Sorry! Link to comment Share on other sites More sharing options...
Richard Robertson Posted March 20 Share Posted March 20 Yeah, the Bluetooth log can fill up pretty fast and the repeat line isn't always obvious. Sometimes need to scroll up or down the log to find it in my experience. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now