Originally Posted by unistyle
A lot of misinformation here. I thought I would clear up a few things. All of the Android phones that have been listed in the last few pages completely support AVRCP 1.3 and are all capable of metadata over Bluetooth. If your phone is running a version of Android 4.2 or newer, you currently do not have working Bluetooth metadata. The reason for this is because at 4.2, Android Open Source Project dropped the BlueZ stack and replaced it with the Bluedroid stack that was provided by Broadcom. The stack must now be completely reworked for the many Bluetooth chips found in all of these phones, many of which are not even Broadcom chips.
This is the reason why anyone running 4.2 or 4.2.1 has noticeably lower quality Bluetooth audio streaming. A lot of the high-end audio frequencies have distortion, and there is a lot of the low-end bass frequencies that are straight up missing. If and when you upgrade to 4.2.2, which just came out, you will notice a considerable boost overall in audio streaming over Bluetooth. The difference is large enough that you will probably have to adjust your equalizer. A large amount of the fixes that are included in 4.2.2 are specifically targeted at Bluetooth and all the problems it is having.
Unfortunately, there is still no fix for Bluetooth metadata, even with the 4.2.2 update. As a Galaxy Nexus owner whose Bluetooth metadata used to work just fine, I am really hoping this is fixed in 4.2.3.
I have a galaxy note 2 running 4.1. I get metadata when I stream an mp3 that is stored locally on the device. What we were talking about was metadata from streaming services such as pandora, slacker, or songza. My old radio - a $99 JVC would display the metadata from these streaming services, MFT does not.
Sent from my Galaxy Note 2 using FF Mobile.