Michael Glasson

A new setting allows the user to set Poweramp to ignore play commands coming from the Bluetooth player (in my case, my A3 car player) for up to 10 seconds. This fixed the issue for me.

While there is a setting to prevent auto resume on Bluetooth connection, it is possible that, as in my A3, the car's head unit is issuing a play command. A new setting in the latest beta allows the user to configure Poweramp to ignore play commands issued by a Bluetooth player for up to 10 seconds. This fixed what looks like a very similar issue for me.

With thanks to @andrewilley, @maxmp and @mOuStAcHe_BR for helping to implement this feature. It seems to have stopped the unwanted behaviour in our A3. Yay! This issue has been going for a while, so it is excellent to have a resolution. I was a little anxious when I saw that the user configurable delay was only 10 seconds, as it is a little close to the documented 8 second delay between Bluetooth connection and the head unit initiated play command. In practice, however, I picked the 10 second max and Poweramp does indeed ignore the play command.

Potentially good possibilities there @eng3, @andrewilley. My current workaround is to have an album consisting of one track of mp3 silence. If I remember to play that album before I get in the car, there is no sudden music just when I am trying to back out of a shopping centre car par. PS, sorry to call you Andrew Andre.

@andrewilley, it appears that it is taking Our A3 8 seconds to issue the RESUME command after the Bluetooth connection is made. Two 'turn on ignition' events are shown below with Poweramp Resume on Bluetooth switched OFF. In both cases, Bluetooth reconnects at 12 seconds past the minute and car issues KEYCODE_MEDIA_PLAY ACTION_DOWN at 20 seconds past the minute. Potential fix might be to have Poweramp ignore media keys for a user settable amount of time, say from 0 seconds to 30 seconds from Bluetooth reconnection. ================== 08:35:12.488 BTReceiver headset event connection BT=true am mode=0 Our A3 ================== 08:35:12.662 PlayerService onRoutingChanged newDevice=bt oldDevice=speaker ================== 08:35:12.662 PlayerService reloadPipeline allowPlaying=true forceResume=false state after reload=2 ================== 08:35:20.850 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=392574974 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=2 ================== 08:35:20.864 PlayerService RESUME from PSMediaButtonReceiver resumePlaying ================== 08:35:21.061 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=392575185 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=1 ================== 08:35:21.067 PlayerService RESUME from PSMediaButtonReceiver resumePlaying ================== 08:35:28.175 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=392582299 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=1 ================== 08:35:28.524 BTReceiver headset event disconnection BT=true am mode=0 Our A3 no_keep_notif_on_dscn=true ================== 08:35:28.524 BTReceiver cmd_player_pause_playing ================== 08:35:28.549 HeadsetPlugReceiver headset event disconnection BT=false am mode=0 no_keep_notif_on_dscn=true ================== 08:35:28.549 HeadsetPlugReceiver cmd_player_remove_notif ================== 08:35:29.554 PlayerService onRoutingChanged newDevice=speaker oldDevice=bt ================== ================== 08:36:12.482 BTReceiver headset event connection BT=true am mode=0 Our A3 ================== 08:36:12.654 PlayerService onRoutingChanged newDevice=bt oldDevice=speaker ================== 08:36:12.654 PlayerService reloadPipeline allowPlaying=true forceResume=false state after reload=2 ================== 08:36:20.590 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=392634714 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=2 ================== 08:36:20.600 PlayerService RESUME from PSMediaButtonReceiver resumePlaying ================== 08:36:20.817 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PLAY ACTION_UP name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=392634941 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=1 ================== 08:36:20.820 PlayerService RESUME from PSMediaButtonReceiver resumePlaying ================== 08:36:26.789 PSMediaButtonReceiver android.intent.action.MEDIA_BUTTON KEYCODE_MEDIA_PAUSE ACTION_DOWN name=Virtual source=0x0 sources=0x301 virt=true repeat=0 actionTime=392640913 sourcePak=com.android.bluetooth isAvrcp flags=0x0 playerState=1 ================== 08:36:27.152 HeadsetPlugReceiver headset event disconnection BT=false am mode=0 no_keep_notif_on_dscn=true ================== 08:36:27.152 HeadsetPlugReceiver cmd_player_pause_playing ================== 08:36:27.154 BTReceiver headset event disconnection BT=true am mode=0 Our A3 no_keep_notif_on_dscn=true ================== 08:36:27.154 BTReceiver cmd_player_pause_playing ================== 08:36:31.151 PlayerService onRoutingChanged newDevice=speaker oldDevice=bt

@andrewilley Thanks for your reply again, Andrew. I don't use the separate Poweramp Equalizer app on my phone. I will do a couple of experiments to find out how long the autoplay takes to happen in our 2014 Audi A3 and let you know the result.

I notice that Musicolet has a 'prevent unwanted autoplay' setting that addresses this exact issue. When enabled, Musicolet ignores all 'Play commands' for a few seconds after connecting/disconnecting to a device. This seems to be a better response than saying, 'It's your car's fault and nothing to do with us.' One trick I have found to get around this issue in my otherwise-beloved music player is to find some tracks of total silence on the internet and make them into an album of silence. I put tags like '!Silence!' in the album artist, title and genre. If I can remember, I just play a track of silence, knowing that when my car tells Poweramp to play whatever it has going, at least I won't get that nerve-jangling experience of unwanted autoplay when I get in the car.

I think I agree with you, @w3wilkes. "Queue Only" mode probably would do it, although, if @andrewilley is correct, to implement that mode the developer would indeed need to touch "lots of bits of code that rely on that [something has to be the current song in the Player Screen] functionality".

Thanks for your response @andrewilley. Before I read your response, I did indeed reinstall Poweramp and saw that the first song in the All Songs list was all cued up and ready to go. I think I may have confused Poweramp's behaviour with that of PlexAmp, which I use when I am at home and in WiFi range. It seems that PlexAmp simply closes the player part of its UI either when the stop button is pressed or it reaches the end of its 'now playing' list. There are, of course, play buttons in the library and these buttons launch the player component. In some of those other products, there seems to be a slightly greater separation betweent the player and library components, a separation that allows the player to be closed on reaching the end of whatever it was asked to play. The stop button has the same effect - it stops and closes the player component. For some reason, I find that behaviour more intuitive than Poweramp's always-open player component. It seems that there is no way that Poweramp is likely to provide anything like that kind of experience. To be fair, it may only be the in-car experience, where it seems the car issues a 'play' command when Bluetooth connection is established that is really inconvenient and is not remediable by toggling the 'resume playing on Bluetooth' setting. I have been and will continue to be a keen user of Poweramp when I am on the move. Thanks again for your responses @andrewilley and @MotleyG.

Thanks for your response, MotleyG. I can see I will get no joy from further persisting with the stop button idea, although I will say that my Plex player has a very nice stop button that clears the 'now playing' item, closes the player controls, leaves me with a clean library view and allows me to choose something else to play. Perhaps I may have better luck with a more modest proposal simply to have the option of closing the player UI (and any open home screen notifications) when the end of a category is reached and returning me to the library view. Would that make sense. If I had an option to do that, it would give me a clear cue that I have reached the end of my selection and might like to pick something else to play. It would relieve me of the need to look at the track count to see that I have indeed reached track n of n and have therefore reached the end of my selection. In relation to the 'accidental' play, I have seen this mentioned in the forum by people who find that a car's music player issues a 'play' command to the player on Bluetooth connection. This is not remedied by turning off the 'resume playing on Bluetooth' toggle, as it is a car-initiated play command. The last thing I want to do when I get in my car is work out how to stop the music. I would prefer, when an album is finished, not to have the last track sitting in the player UI. That way, there would be nothing to play when the car sends the play command on Bluetooth connection. How about that?

I see there are many posts related to ways to stop Poweramp and to clear the player. Despite having used Poweramp for many years, I still find it hard to know if something is really missing, or if I have just not found out how to do something. There is no stop button, so all I can do is play/pause the current category. My car player and probably many others do not have a stop button either and I think I get why people might think of a stop button as being redundant. At the same time, with the last song still on the screen at the end of a category a press of the play button will restart that song. In the car, a stray, car-initiated 'play' event on Bluetooth connection will start the last song. I would love the player to just have a clear, 'playing nothing' screen either at the end of the category (optionally I guess), or a stop button to clear the current category. As it stands, it seems there is no way to get to a 'clean slate'. A stop button would have the same effect - clearing the player back to not playing anything and not having any active category in the UI - but you could press it at any time. So much of the time on my phone's home screen or in the player UI, I see that active category sitting on the last item, just waiting to be played again accidentally. When I am not playing anything, I would really like the player to be in a 'clear' state. Yes, I know that all I need to do to get rid of the 'now playing' list is to pick another category, but I would really like to have the ability for the player to be completely clear. It would prevent accidental plays, but it would also give me the confidence that when I press stop, the player is clear. Does this make sense?