mporcas

As I mentioned, I'm still having this issue, so decided to do a little test this morning. When I arrived at work I decided to cycle through the repeat and shuffle buttons on my head unit just to see what happens. I should note that I'm only having issues with Repeat, Shuffle behaves properly. Not sure why that may be. Here's the log from the moment I arrived at work: ================== 07:39:11.996 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=1 com.google.android.bluetooth ================== 07:39:17.666 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.google.android.bluetooth ================== 07:39:22.015 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=1 com.google.android.bluetooth ================== 07:39:24.028 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.google.android.bluetooth ================== 07:39:26.386 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=0 com.google.android.bluetooth ================== 07:39:26.822 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.google.android.bluetooth ================== 07:39:31.534 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=1 com.google.android.bluetooth ================== 07:39:33.353 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.google.android.bluetooth ================== 07:39:35.773 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=0 com.google.android.bluetooth ================== 07:39:36.061 PSMediaSessionHelper.Callback onSetRepeatMode repeatMode=2 com.google.android.bluetooth ================== 07:39:52.923 PSMediaSessionHelper.Callback onSetShuffleMode shuffleMode=1 com.google.android.bluetooth ================== 07:39:54.386 PSMediaSessionHelper.Callback onSetShuffleMode shuffleMode=0 com.google.android.bluetooth ================== 07:39:57.101 PSMediaSessionHelper.Callback onSetShuffleMode shuffleMode=1 com.google.android.bluetooth ================== 07:39:58.909 PSMediaSessionHelper.Callback onSetShuffleMode shuffleMode=0 com.google.android.bluetooth ================== 07:40:06.167 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=476008964 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 07:40:06.406 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=476009016 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=1 ================== 07:40:06.421 PlayerService PAUSE from PSMediaButtonReceiver pausePlaying ================== 07:40:06.590 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=476009386 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=2 ================== 07:40:06.648 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=476009445 sourcePak=com.google.android.bluetooth A2dpOn isAvrcp flags=0x0 playerState=2 ================== 07:40:10.022 HeadsetPlugReceiver headset event disconnection BT=false am mode=0 no_keep_notif_on_dscn=false ================== 07:40:10.024 BTReceiver headset event disconnection BT=true am mode=0 Ford Audio no_keep_notif_on_dscn=false ================== 07:40:11.076 PlayerService onRoutingChanged newDevice=speaker oldDevice=bt ================== 07:40:11.076 PlayerService reloadPipeline allowPlaying=false forceResume=false state after reload=2 It does appear as though there's an extra command being processed by PA around half a second after the setting is changed to 'repeatMode=0', (either via the head unit or in PA). I can't believe that all these various head units (multiple makes of cars at that!) are suddenly sending these additional signals, especially when I know my head unit has not been updated since I've had it. It also only seems to be happening on Android 14, and only since the day of upgrading in my case, so it has to be something in the OS causing the issue. Could it be the case that the Google/Android Bluetooth API is sending a confirmation signal to the head unit incorrectly which is triggering a change of state at the head unit end, triggering a further Bluetooth command to come through to PA??? Looking forward to the next beta, with the improvements to ignoring the repeat/shuffle commands. Thanks, Martin

Ha ha, just noticed it doesn't say anything about me changing the repeat. Will try again tomorrow. Sorry!

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

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?

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...

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??

I use the 'Play' version yet Google's still showing v976. Is v980 going to be available on Play soon? Just a thought, this new setting ignores commands following connection, however my phone and car keep trying to sync the setting, up until it's disconnected. If I try to correct it on my phone, something (I'm assuming the API calls back and forth with the car) turns it back to 'repeat on'. My concern is that it'll be fine for the first x seconds, then change after that. Having said that, perhaps it'll allow them to be in sync somehow? Once I can install 980, i'll check what happens and report back if that's OK?

I'm having the same repeat issue since upgrading my Pixel 6 to android 14. I'm getting the same repeatmode=2 command popping up, and keeps coming up if I try to change the repeat mode to off. I don't seem to be getting the shuffle issue though. Not sure if it helps but my car is a 10 year old Ford. Also, I don't have the problem when using a Bluetooth headset. Some sort of option under the Bluetooth settings to ignore repeat and shuffle commands would be useful as I don't use either.