View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020014 | MMA | Playback | public | 2023-05-08 11:56 | 2023-09-19 17:03 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | sometimes |
| Status | resolved | Resolution | no change required | ||
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.0 | ||||
| Summary | 0020014: Playback starts by itself | ||||
| Description | With build 1080, MMA hadn't been used overnight. In the morning, I tapped the microphone button in Google translate and MMA started playing the current track for about 2 seconds! Log ID: EIZPNTFHY2 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Unable to replicate since this occurred. Last tested with build 1085. Resolving. |
|
|
Spontaneous playback just occurred with build 1087. MMA was opened to the 'Library & Sync' options configuration, when all of a sudden it started playing by itself! Debug log: 3A3DPEBC5T |
|
|
TOOGLE_PAUSE_ACTION started the playback service, I had to improve logs to the next build 2.0.0.1088 to identify the source. We will have more info when the issue occurs again. |
|
|
This just occurred in build 1088. I was testing selection in Music > Accoustic Rock > Boyce Avenue and playback of the Playing list (unrelated to the Boyce avenue tracks) started. Debug log: 3UVSTL6WKV Possibly related to 0020053:0072128 ? (though in the case above I didn't even initiate Queue next/Queue last or any other commands). |
|
|
Log confirms that keyCode: 85 KEYCODE_MEDIA_PLAY_PAUSE was received in MediaSession.Callback MediaSession.Callback receives media buttons, transport controls, and commands from controllers and the system. |
|
|
The strange thing is that: - this only started happening again recently starting with builds 1087/1088 - in both cases in which this occurred, MMA was the active application in the foreground (in one case in config options and in the other Genre navigation-selection) which makes me think that MMA is somehow triggering the bug. |
|
|
Logs extended to identify source App/device. In build 2.0.0.1089 |
|
|
This issue is not replicable in build 1089. Resolving. |
|
|
This just occurred again with build 1099. Here's what happened: 1 connected BT headphones and made a phone call 2 after call terminated, left headphones in ears --> after about 5 minutes, MMA started playing spontaneously! Debug log: F2HXCXF8D8 Note: MMA was not even running (i.e. it hadn't been used in ~15 hours, and wasn't in the recent apps list)!! |
|
|
onHeadsetConnected(3)TOYOTA RAV4 48:F0:7B:A9:64:86 onHeadsetConnected: ResumePlayback NOT ACTIVATED resume on Bluetooth connected is disabled MsKeyProcessor.onMediaButtonEventDown(PROCESS) keyCode: 126 KEYCODE_MEDIA_PLAY Start service with PLAY_START_ACTION --------------------------------------------------------------------------------------------------------- You got in the car, right? 1) Your device was connected to the car BT 2) PLAY action was triggered automatically (from the car side) Note: On MMA side "Resume playback when connected" is disabled. 3) You have also "Always respond to remote buttons" enabled, so MMA should respond to BT actions as much as possible. |
|
|
I actually didn't get into the car. When this occurred, I was only using by Sony Linkbuds earbuds. Note that step 1 at 0020014:0072685 was misleading: I didn't 'Plug-in' any headphones--I connected them over Bluetooth (I've edited the original text to eliminate this poor choice of words). MM really just started playing in my earbuds by itself! Also, note that there's a new report of this at https://www.mediamonkey.com/forum/viewtopic.php?p=512462#p512462 |
|
|
08-22 16:55:10.009 PlaybackService(2): onHeadsetConnected(3)LinkBuds S F8:4E:17:71:B5:F5 isA2dpConnected: false 08-22 16:55:10.245 PlaybackService(2): onHeadsetConnected(3)LinkBuds S F8:4E:17:71:B5:F5 isA2dpConnected: true 08-22 16:55:10.649 PlaybackService(2): onHeadsetConnected(3)TOYOTA RAV4 48:F0:7B:A9:64:86 isA2dpConnected: false 08-22 16:55:11.421 onMediaButtonEventDown(PROCESS) keyCode: 126 KEYCODE_MEDIA_PLAY[b() 38 MsKeyProcessor.onMediaButtonEventDown(PROCESS) keyCode: 126 KEYCODE_MEDIA_PLAY 2 08-22 16:55:11.958 PlaybackService(2): onHeadsetConnected(3)TOYOTA RAV4 48:F0:7B:A9:64:86 isA2dpConnected: true Not sure from which device MMA received KEYCODE_MEDIA_PLAY action because both devices had been connected within one second. It is strange that the TOYOTA RAV4 device appears in the logs at all, however, the valid KEYCODE_MEDIA_PLAY action has been received to which MMA must respond. Anyway, two devices can be connected simultaneously. You have enabled "Always respond to remote controls" so MMA takes audio focus when BT headset is connected. 1) Link buds have a touch sensor and a single tap causes play or pause music https://helpguide.sony.net/mdr/linkbudss/v1/en/contents/TP1000539058.html So maybe when you ended the call and put down the pods, you activated to start playing by the tap gesture and noticed it later. However I have been testing it too, and I was unable to replicate your scenario, except incidentally touching my pods. |
|
|
I suppose it's possible that the sensor on the earbuds was somehow activated (e.g. by Wind or hair), but I think that it has occurred with the speaker as well but I'm not certain. If it occurs again, I'll add more info. |
|
|
This just occurred with build 1101. I was using my phone (using the Hopper app) when all of a sudden MediaMonkey started playing from the middle of a song. MediaMonkey hadn't been used for hours. Also in this case playback started by itself through the speaker which would seem to indicate that it's not a BT issue. Log ID: K3LCQUJH1J Note: Is it possible that this is somehow related or triggered by Android going into Do Not Disturb mode? I had disabled bedtime mode for 30m (which also disables DnD for 30m), and the audio playback started just before bedtime mode was re-activated. |
|
|
MMA had not been running, but Media key: 85 KEYCODE_MEDIA_PLAY_PAUSE was received, leading to the start playback. I also see in the log that the content is browsed by the remote client com.google.android.wearable.app (like Smartwatch) Could this be related? The action for playback is again correct and coming from outside the app. |
|
|
OK. I've uninstalled the wearable app and will re-open if this occurs again. |
