0019792: Playback sometimes starts by itself - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0019792	MMA	Playback	public	2023-02-05 19:41	2023-04-28 14:29

Reporter	rusty	Assigned To
Priority	urgent	Severity	major	Reproducibility	random
Status	closed	Resolution	reopened
Product Version	2.0.0
Target Version	2.0.0	Fixed in Version	2.0.0

Summary	0019792: Playback sometimes starts by itself
Description	Upon using my phone after it had been sleeping for about 24 hours, MMA playback started spontaneously through the speaker even though the app wasn't active and there was no bluetooth audio connection. Tested with build 1066 Log ID: E41J6D8QEE Description: MediaMonkey started playing by itself Note: the following options were enabled - Always respond to remote buttons - Resume play on connection (Bluetooth) Also, fyi, my phone is connected to an Android Wear watch. Could it be that the bug is that it sometimes playback resumes due to a bluetooth connection to a _watch_ (even though it should only resume on Bluetooth connection to an audio device)?
Tags	No tags attached.

Fixed in build

martin 2023-02-06 10:24 developer ~0071095	I can see in log that key 85 KEYCODE_MEDIA_PLAY_PAUSE was fired, so this was the reason why playback started.

rusty 2023-02-06 21:39 administrator ~0071109	Re-opening because I've noticed 2 other possible issues with build 1066 and want to make sure that they aren't real issues: 2) If the following options are disabled: [ ] Always respond to remote buttons [ ] Resume play on connection (Bluetooth) --> MMA still responds to buttons if MMA was the last-used player. Is this expected (I believe it is)? Debug log: WP4F911PEL 3) If the following options are disabled: [ ] Always respond to remote buttons [ ] Resume play on connection (Bluetooth) --> Android Auto starts playback on its own Debug log: 4NDE3BWQE9 Is Android Auto requesting playback to start (in which case it isn't a bug)?

rusty 2023-02-06 21:43 administrator ~0071110	Upon reviewing this, 2) Seems to be expected 3) Occurs because Android Auto > Start Music Automatically is enabled

rusty 2023-02-10 18:42 administrator ~0071145 Last edited: 2023-02-17 07:14	Retested with 1067 and have found that playback does start by itself if BT connects while the 'Show in notifications bar' timer has not expired. e.g. 1 Turn on Car and wait for BT to connect 2 Press 'play' button on the car stereo 4 times in stereo. No response. (tracked at 0019708) 3 Initiate playback on device --> playback works 4 Pressed play pause on car stereo --> buttons respond 5 Turn off car 6 Restart car --> Bluetooth connects and playback starts by itself! Log ID: J5ES4F3HBF Description: playback starts by itself EDIT: I suspect that this may not be an MM bug since I observed similar behavior with other players.

rusty 2023-02-13 17:10 administrator ~0071151 Last edited: 2023-02-17 07:15	With build 1067, I unlocked phone after it was sitting on the table asleep for a few minutes, and then MMA playback starts by itself (no bluetooth connection was involved in this case). Note: - 'Show in notifications bar' timer had already expired (MMA hadn't been used in 20+ minutes and the timer was set to 10 minutes) - Bluetooth remote buttons option was disabled Log ID: MFSXBDS1RL EDIT: This may not be an MMA bug since Android Auto's 'Head unit server' was active (this is a developer option 'Start head unit server' used in conjunction with Android Auto Emulation), and it may have been responsible for the buggy behaviour.

martin 2023-03-08 15:24 developer ~0071323	I can confirm that Android Auto Emulation can cause autoplay sometimes. No suspicious behavior in the log.

rusty 2023-03-08 21:15 administrator ~0071328	Closing as I haven't observed this issue outside of this specific case.