View Issue Details

IDProjectCategoryView StatusLast Update
0013961MMAPlaybackpublic2017-04-25 14:28
Reporterpeke Assigned To 
PriorityurgentSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Target Version1.3.0Fixed in Version1.3.0 
Summary0013961: BT: Track not updating on Car head Unit
DescriptionUsing MediaMonkey Android 1.3.0.0665 with Volvo V60 2012 headunit Song info is not correctly shown/updated. It works fine with the default audio player.

debug log: FZ5VSSXDL1
Additional Informationhttp://www.mediamonkey.com/forum/viewtopic.php?f=26&t=86994#p432127

Another similar report on Mazda: CXN-271-35935
TagsNo tags attached.
Fixed in build692

Relationships

related to 0014201 resolvedmartin MMA stays active due to MediaBrowserServiceCompat 

Activities

peke

2017-01-31 00:39

developer   ~0047119

Last edited: 2017-01-31 00:44

Based on http://www.mediamonkey.com/forum/viewtopic.php?p=432196#p432196 It seams to me that when MMA lose BT connection it doesn't reinit AVRCP to send correct data or does reconnect correctly.

Also for User questions Android 7.1.1 still support on AVRCP 1.3 https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles#Audio.2FVideo_Remote_Control_Profile_.28AVRCP.29
https://www.bluetooth.com/specifications/adopted-specifications

Or also it fails on some of commands http://mt-system.ru/sites/default/files/documents/iwrap6_a2dp_application_note.pdf

martin

2017-02-13 16:11

developer   ~0047274

It seems on device specific issue.
I can't replicate it on my devices neither with BT car radio.
User still testing it, it has random occurrences with his car radio.
From debug log I can see that BT metadata are updated from MMA side.

peke

2017-02-22 17:20

developer   ~0047320

I agree that indeed looks like mazda issue I was able to test 2 days ago. Where BT Data is left from previous track until track change while protected. I guess Head Unit assume same track is resumed playback.

rusty

2017-03-13 14:54

administrator   ~0047466

I've triaged this back to 1.3.0 since the issue doesn't seem to be specific to Mazda head units -- Rivorson provided two logs here from a Toyota unit:
http://www.mediamonkey.com/forum/viewtopic.php?p=433724#p433724

martin

2017-03-15 14:19

developer   ~0047505

Hopefully fixed in build 1.3.0.680

rusty

2017-03-17 04:56

administrator   ~0047525

No regressions observed in build 682.

rusty

2017-03-20 12:26

administrator   ~0047531

Rivorson confirmed that the fix worked for him at http://www.mediamonkey.com/forum/viewtopic.php?f=26&t=86994

rusty

2017-04-03 17:33

administrator   ~0047707

A couple of users have reported that updating to 1.3.0 has triggered this problem:
http://www.mediamonkey.com/forum/viewtopic.php?f=26&t=86994

rusty

2017-04-10 15:06

administrator   ~0047763

Strangely, enabling 'always respond to buttons' resolves the issue for one user. I say 'strangely', because that UI option doesn't indicate any relationship to display of metadata.

i.e. if MMA responds to button presses, No user would expect that enabling this option would have an effect on metadata display.

martin

2017-04-13 22:58

developer   ~0047787

Finally I can replicate it with S5 mini and Kenwood car radio.
Fixed in build 1.3.0.692