This is easily the 4 3 feature that surprised me the most, and also where I benefit from the most

[G+_Andreas Ebbert-Karroum]

This is easily the 4.3 feature that surprised me the most, and also where I benefit from the most. I mostly listen to music in my car via my Bluetooth connected Galaxy Nexus, which streams music from Google Play. Of course most often I know the current artist... Still it is nice that the meta data are now also transmitted. (BTW. Apparently this worked for ages with iOS already my G+ pals told me)

 

Originally shared by Andreas Ebbert-Karroum

 

WIE GEIL IST DAS DENN? Android 4.3 & Audi MMI F.T. EFFING W! :) #twt #fb

[G+_Johan Appelgren]

I think avrcp 1.3 (that Android now supports) was added to bluetooth in 2007, but I guess the Android devs didn't think it was a priority :)

[G+_Amar R]

So AVRCP 1.3 was actually in the older bluez bluetooth stack.  Due to licensing issues (I think?) they switched to a less mature bluetooth stack called bluedroid.  They recently updated bluedroid to add this functionality back.  A lot of vendors ended up continuing to use bluez because of this and can now switch to bluedroid without losing any functionality.

[G+_Johan Appelgren]

Amar Rajvanshi Don't think AOSP ever had a version of BlueZ that supported AVRCP 1.3. It was introduced in BlueZ 4.93 and AOSP used BlueZ 4.63 or something until they switched to bluedroid.  Of course, some manufacturers added AVRCP 1.3 support one way or another in their builds. 

[G+_Amar R]

Johan Appelgren Oh I see, I thought that bluez worked as far as forwarding metadata to the head unit though, even if it wasn't AVRCP 1.3.  Maybe that was just the setup that some OEMs had in their stock roms as you said though.