Database Users

[Q] Bluetooth on Nexus 4 woes

Trying to connect the N4 to a car Bluetooth audio (2012 model car, relatively new, only 9 months old).
(1) I had a very hard time getting the two paired: lots of "connection failed" attempts until they finally connected.
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
(3) Without any music being streamed to the car audio, if I make a phone call via the car bluetooth, when the call ends the music player on the N4 starts automatically. This is very annoying, not sure if it's a problem with the car implementation sending a "play" command at the end of the call or the N4 doing something weird. I tend to blame the N4 as two other phones, an iPhone and the older LG mentioned above do not do this.
(4) The car has a play/pause toggle that it can send to the bluetooth player. Pause works, the player on the N4 pauses, but then play doesn't work, I have to hit play on the device.
(5) After I use bluetooth on the N4, I find that sometimes the widget toggle can no longer turn bluetooth on/off until I reboot the phone.
(6) After I use bluetooth on the N4, the phone sometimes randomly reboots. Not sure if it's really related or just a coincidence. Given (5) above I suspect something is going on.
Anyone else having such a hard time with the bluetooth part? Potential hardware issue or simply buggy software that we can hope to get addressed at some point?

I have experienced the issue with track information not being sent. Also random changes in volume during playback. Seems there's still some work that needs to be done in 4.2 regarding blue tooth.
Sent from my Nexus 4 using Tapatalk HD

sirxdroid said:
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
Click to expand...
Click to collapse
Is this an issue that can be addressed by flashing a custom ROM or perhaps using a different music player than stock or is there more to it, deep down in the bluetooth drivers and it would need a fix from Google in the form of new drivers?

Yeah I have had a few issues too. My track/artist/album names do not send where my S2 sends them. Also the headunit I have has buttons for shuffle and repeat and these do not show up at all (I assume because it detects they aren't supported). I haven't taken a call yet or tried turning BT off after streaming but I'll give it a shot and see.. My nexus 4 also randomly shuts down for no apparent reason sometimes (rarely atm). I think it's just 4.2.1 problems - I doubt a different music app will fix it (I tried one), custom ROM may work though..

My N4 is paired with an Alpine 135BT and it's worked very well so far. I initially had some trouble connecting but once they were paired I didn't have any additional connection issues. The N4 does automatically play as soon as it connects to the unit. I've got BeyondPod and Spotify installed and for whatever reason it always defaults to BeyondPod instead of Spotify even if I had BeyondPod closed and Spotify open. Not a big deal to me though.
Are you running the stock rom or a custom rom? I had my EVO LTE hooked up to the same head unit. It worked perfectly on the stock software but gave me all kinds of trouble when I started using custom roms. Otherwise, it could just be that the N4 and your particular head unit just don't play nicely together.

sirxdroid said:
Trying to connect the N4 to a car Bluetooth audio (2012 model car, relatively new, only 9 months old).
(1) I had a very hard time getting the two paired: lots of "connection failed" attempts until they finally connected.
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
(3) Without any music being streamed to the car audio, if I make a phone call via the car bluetooth, when the call ends the music player on the N4 starts automatically. This is very annoying, not sure if it's a problem with the car implementation sending a "play" command at the end of the call or the N4 doing something weird. I tend to blame the N4 as two other phones, an iPhone and the older LG mentioned above do not do this.
(4) The car has a play/pause toggle that it can send to the bluetooth player. Pause works, the player on the N4 pauses, but then play doesn't work, I have to hit play on the device.
(5) After I use bluetooth on the N4, I find that sometimes the widget toggle can no longer turn bluetooth on/off until I reboot the phone.
(6) After I use bluetooth on the N4, the phone sometimes randomly reboots. Not sure if it's really related or just a coincidence. Given (5) above I suspect something is going on.
Anyone else having such a hard time with the bluetooth part? Potential hardware issue or simply buggy software that we can hope to get addressed at some point?
Click to expand...
Click to collapse
(1) Haven't had any connection issues so far on my vehicle or my wife's.
(2) Currently stock Android uses AVCR v1.0 which only only allows you to control via Bluetooth (play, pause, etc) but not send track info. Other manufactures that customize Android (LG, Samsung, etc) will sometimes use v1.3 that supports track info. That's why your old phone did it.
You could install a custom Rom that has v1.3. I think cm10 does.
(3) Again, not happening on my two cars. The only time the music starts after a call is if it was playing before the call. I'm wondering if you have another music/podcast player that is taking over Bluetooth controls and causing problems. I use the stock player and Player Pro. If I don't disable the headset/BT controls in Player Pro I have control issues.
(4) I have the same issue. To get around this I cheat and push the track advance button on the radio to play the next track.
(5) This is an issue I've had on all of my previous android phones. I haven't noticed I my N4 because I never toggle off Bluetooth anymore.
(6) Not having this problem but maybe try solution in (3).
Sent from my Nexus 4 using xda premium

got the sony mw600 for bluetooth audio.. no id tags on display.. on every musicplayer (play music, poweramp, cm musicplayer..) the same.
dont know why, but today even the start/stop, forward and prev. buttons didnt work! the only thing i can use is volume control..
anyone an idea?

Any luck with this?
I want to buy one but couldn't find it in Sri Lanka so planning to order one via ebay & need to check if it works. Running cyanogen mod 10, heard that the bluetooth stack was updated on CM which supports most of the features since stock rom only has older stack version which can have issues!
clsmn said:
got the sony mw600 for bluetooth audio.. no id tags on display.. on every musicplayer (play music, poweramp, cm musicplayer..) the same.
dont know why, but today even the start/stop, forward and prev. buttons didnt work! the only thing i can use is volume control..
anyone an idea?
Click to expand...
Click to collapse

dark5un0 said:
... that the bluetooth stack was updated on CM which supports most of the features since stock rom only has older stack version ...
Click to expand...
Click to collapse
using the actual cm10.1 nightly with franco r53

Wow, maybe I'll wait for a few weeks & see if it works out for you..
Sent from my Nexus 4 using xda app-developers app

dark5un0 said:
Wow, maybe I'll wait for a few weeks & see if it works out for you..
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well.. Sound and controll works.. even headset-function works for telephone calls.. only thing not working now is id for tracks

Awesome! Thanks for the reply! I hope it worked out soon!
Sent from my Nexus 4 using xda app-developers app

I also have the track name issue. This is a massive let down. I like to just get in my car and flip through tracks with my phone in my pocket. My iPhone did this, my s3 did this. Why not the nexus 4? Come on Google. Sort it out

TrickyTree1984 said:
I also have the track name issue. This is a massive let down. I like to just get in my car and flip through tracks with my phone in my pocket. My iPhone did this, my s3 did this. Why not the nexus 4? Come on Google. Sort it out
Click to expand...
Click to collapse
my impression is that almost nothing involving Bluetooth functions as it should currently on the N4. I can't even get a mouse to work. what a shambles! it's not as if BT is some new technology. this all better get sorted out in 4.2.2.

If I'm not mistaken Google moved to a new Broadcom b/t stack. Yeah, good move! And I agree, b/t has been around for like what at least 10 years now? You'd think that getting track info should be a given by now. I have a crappy old LG phone running Gingerbread and it has no issues at all.

Bluetooth
When I got the N4, I connected my helmet headset to it and everything seems to work fine. My headset supports ad2p music and phone. Both connected and both worked, including play controls. Not sure about the audio quality, I didn't test it long enough After I flashed Jellybro (CM 10.1 Kang) Music connects, but phone goes on a connect/disconnect loop. Audio needs further testing, can't tell if the left side is off because of the bluetooth or not. Controls work most of the time, every now and again playback will decide to pause itself and sometimes the play command doesn't work. Haven't had a chance to flash stock CM 10.1 nightly yet either.

Play/Pause Works Inconsistently
Has anyone had this issue?
I am on stock 4.2.2, I connect with my car stereo no problems. I use to be able to just hit play/pause on my car stereo and it would just play music from Google Music. Now, sometimes when I hit the play/pause button on my stereo, it won't play. I have to manually hit play from my phone. After initially doing that, then I can hit play/pause and the control is there. I haven't had the problem since I got my phone on Nov 14th, this issue just started to happen. I notice this after installing Light Manager, but I have uninstalled it and still the issue is there. It is inconsistent, but the issue is more often than not.
Thanks in advance for your input.
Just reiterating, stock Android does not show artist/track info, it is not in the protocol, but you can skip tracks or go back to previous tracks. If it is important to you, you should root and get a custom ROM, not sure which ones for N4 has it though, been too happy with stock to root.

About time, Google:
http://www.androidpolice.com/2013/0...vrcp-1-3-coming-to-android-with-api-level-18/

Is anyone else having problems wit Bluetooth audio streaming in car? My music sounds like it's speed up a tiny bit. Kinda like chipmunks voices. Is this a ROM issue?
Sent from my Nexus 4 using xda app-developers app

Bluetooth streaming audio stuttering persists in Android 4.3

Hi fellow xda'ers
I got the 4.3 OTA today for my Nexus 4 and the problem of stuttering bluetooth audio persists for me.
This is in reference to the bug described here: http://code.google.com/p/android/issues/detail?id=39633
I also unpaired my phone and re-paired it but still facing the same problem.
So, just wanted to ask around...
1. Is anyone still facing this same bluetooth audio bug like me in Android 4.3?
2. Can anyone who had this bug in 4.2.2 confirm that it got resolved for them in Android 4.3?
Thanks..

mailrachit said:
Hi fellow xda'ers
I got the 4.3 OTA today for my Nexus 4 and the problem of stuttering bluetooth audio persists for me.
This is in reference to the bug described here: http://code.google.com/p/android/issues/detail?id=39633
I also unpaired my phone and re-paired it but still facing the same problem.
So, just wanted to ask around...
1. Is anyone still facing this same bluetooth audio bug like me in Android 4.3?
2. Can anyone who had this bug in 4.2.2 confirm that it got resolved for them in Android 4.3?
Thanks..
Click to expand...
Click to collapse
Mine is great..plus the track name is one there now....but i never had problems in 4.2 either so.
what do you have for a stereo?
I use mine in my car (sony stereo) and i also have a bluetooth radio for my patio i got at home depot that works just fine

Every thing is fine with mine too
Sent from my Nexus 4 using XDA Premium HD app

Never had suffer stutter
Sent from my Nexus 4 using Tapatalk 4 Beta

I am using my phone with a Clarion car stereo.
The issue now is much rarer than it was before.
I guess I need to test it out for a few more days.
Thanks..

Worked fine for me in 4.2.2 .... now in 4.3 LOTS of stutter and occasional drops. Very annoying and probably related to the change of Bluetooth in 4.3 ... hope someone comes up with a fix, otherwise I'll need to go back to 4.2.2 as I use Bluetooth for music lots. Anyone that can help ... ??

I was excited to see that as soon as I upgraded from 4.2.2 to 4.3 my bluetooth streaming worked flawlessly in my car for a 2 hour drive into the mountains. However, a couple days later the stuttering came back, just as you described.
This was the one thing I was looking forward to for 4.3 but it looks like we've been let down.
mailrachit said:
I am using my phone with a Clarion car stereo.
The issue now is much rarer than it was before.
I guess I need to test it out for a few more days.
Thanks..
Click to expand...
Click to collapse
Odd, I also have a Clarion stereo. I'll be curious to try it out in another car with a different brand of stereo to see if it may just be that our phones don't play well with Clarion...

I've never had issues...I have a Sony stereo and I also play in my buddies new toyota truck and plays fine. I would try on other devices..my guess would be your problem is with the stereo than the phone
Sent from my Nexus 4 using xda app-developers app

sn0warmy said:
I was excited to see that as soon as I upgraded from 4.2.2 to 4.3 my bluetooth streaming worked flawlessly in my car for a 2 hour drive into the mountains. However, a couple days later the stuttering came back, just as you described.
This was the one thing I was looking forward to for 4.3 but it looks like we've been let down.
Odd, I also have a Clarion stereo. I'll be curious to try it out in another car with a different brand of stereo to see if it may just be that our phones don't play well with Clarion...
Click to expand...
Click to collapse
I'm not really sure, what's happening.
I tried earlier on with Poweramp Player (third party app) and Google Play Music, I had stuttering in both the apps.
Then I decided to unpair the phone/stereo, change the phone name and then re-pair. Just wanted a fresh start..
After that, I had the stuttering problem whenever I used Poweramp player. The problem happens within 5-7 min. However, when I use Google Play Music, it seems to work fine. However, I haven't tested it for long. Maybe 1 hour max, so can't say if my hypothesis is correct but I'm keeping my fingers crossed. After 7 months with this phone, I really need to get Bluetooth working.

mailrachit said:
I'm not really sure, what's happening.
I tried earlier on with Poweramp Player (third party app) and Google Play Music, I had stuttering in both the apps.
Then I decided to unpair the phone/stereo, change the phone name and then re-pair. Just wanted a fresh start..
After that, I had the stuttering problem whenever I used Poweramp player. The problem happens within 5-7 min. However, when I use Google Play Music, it seems to work fine. However, I haven't tested it for long. Maybe 1 hour max, so can't say if my hypothesis is correct but I'm keeping my fingers crossed. After 7 months with this phone, I really need to get Bluetooth working.
Click to expand...
Click to collapse
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:

sn0warmy said:
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
Click to expand...
Click to collapse
At the same time have you checked the reverse? Any other phones that work fine with your stereo?
I have and I can say all other phones have worked fine with my Clarion stereo.
If N4 continues to have problems with the Clarion stereo, it could be easier for me to sell the N4 and get another phone, unfortunately a non-Nexus one

mailrachit said:
At the same time have you checked the reverse? Any other phones that work fine with your stereo?
I have and I can say all other phones have worked fine with my Clarion stereo.
If N4 continues to have problems with the Clarion stereo, it could be easier for me to sell the N4 and get another phone, unfortunately a non-Nexus one
Click to expand...
Click to collapse
sn0warmy said:
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
Click to expand...
Click to collapse
I was wrong btw. The problem came back for Play Music too :crying:
Don't know what to do...

Using all stock 4.3 and btooth working perfectly. Using it right now. I just have a $50 lg headset but have no issues.
Not sure what's up with your device man
Sent from my Nexus 4 using xda app-developers app

@sn0warmy
It seems the problem is with our Clarion car stereo indeed. A lot of Clarion stereos have bluetooth issues:
http://www.fixya.com/support/t12082313-bluetooth_audio_streaming_breaks_up
http://community.crutchfield.com/car_audio_and_video/f/27/receivers/t/22006/clarion-cx501-bluetooth
Phones like iPhone 4, Lumia 920 and Moto Razr also seem to have these problems.
My stereo CX501 doesn't have any bluetooth firmware upgrade too. Though, they have provided some firmware update for some other stereos like NX501 and so on. So you should check out on their site for a firmware upgrade.
http://www.clarion.com/us/en/support/compatibility/bluetooth/index.html

I really think you're right. I tried streaming music through my girlfriend's car stereo last night and had absolutely no issues. I've also read the threads you linked to as well as a few others and the consensus is that Clarion keeps trying to pin the blame on the phones and not their receivers. Looks like it's time to change stereos...

sn0warmy said:
I really think you're right. I tried streaming music through my girlfriend's car stereo last night and had absolutely no issues. I've also read the threads you linked to as well as a few others and the consensus is that Clarion keeps trying to pin the blame on the phones and not their receivers. Looks like it's time to change stereos...
Click to expand...
Click to collapse
You should at least check if there is a firmware upgrade available for you on Clarion's support site before spending on a new stereo.
Unfortunately, it's not available for my stereo CX501.

I have stuttering too on both my A2DP devices. Both are cheap: one is from DX, th eother is from a local 'dollar store' (where it was 10 euro or so).
The one from the dollar store seems to work fine after pairing, but not when connecting again.
The one from DX (z nice plug for the aux in of the car, with a mic and henadsfree speakers through the car audio) seems to stop stuttering after a few minutes. The audio level is a lot better with 4.3.
But no difference in stuttering beween 4.2.2 and 4.3.

Problems remain
I have found no improvement with my Nexus 7 with Android 4.3. I get stuttering every minute or so. I've done a bit of reading and found that Bluetooth is hellishly complex - and would be very difficult to debug. For instance to set up audio streaming, both devices need to agree on a codec to use. There is a default base level codec. As I have found that the issue is worse on some bluetooth receivers than others, I can only guess that the issue relates to Android's selection of a codec or other parameter on some devices. I certainly have no issue with any device streaming from my windows laptop (no matter how busy it is).

I have the exact same issues with bluetooth stuttering.
Using 4.2.2 PACman rom on my Note 2 with a Sony MW600 bluetooth adapter, the audio would switch off for a second every minute or so, whether using Google Play music or PowerAmp, but it seemed to happen less on the former.
Updating to 4.3 has made it worse, the audio now switches off for at least 5 seconds to the point where i have to check if the phone or app has crashed each time.
I never had an issue with the Revolution HD rom (I think its called?) but I believe that's mostly stock?
It kinda feels like the bluetooth can't handle the bandwidth depending on the size of the file. I think there's less stuttering on lower quality files - could just be in my head though.

I have a Galaxy S3 i747 running latest 4.3 CM10 rom. My audio stuttering actually got worse when upgrading from 4.2.2. Using platronics 903+ and a bluetooth stereo unit for my motorycle helmet.
Very disappointed. My work iPhone doesnt skip a beat.

[Q] Note 3 Bluetooth and Car Radio ?

Hi everyone, first post here (though I've been following the forums for about 2 months now).
I have a fairly specific question regarding the Note 3's Bluetooth capabilities and my car radio (Pioneer AVH 8400). I have been a Wazer for about two years now and use the app almost every day. I wanted to know if anyone has experience with using even a past Note 1 or 2 (or I guess any recent Samsung phone for that matter) in their car. My question is, will Waze (on a Note 3) interrupt the radio to report an accident or new direction, and then return back to the radio?
To be more clear, I tried using it with my uncle's Note 1 and had one issue. When I am on my Bluetooth setting on my receiver, say listening to spotify. The song that is playing will decrease in volume, Waze will report the notification and then song will resume. However, the phone that I am coming from (iPhone 5) would do the same while on my radio setting. It would fade out, report the notification and then return to the station. However, I could not get that to work on the Note 1.
Is it a Note 1 Bluetooth limitation or will this not just work?
Thanks in advance.

cbr09123 said:
Hi everyone, first post here (though I've been following the forums for about 2 months now).
I have a fairly specific question regarding the Note 3's Bluetooth capabilities and my car radio (Pioneer AVH 8400). I have been a Wazer for about two years now and use the app almost every day. I wanted to know if anyone has experience with using even a past Note 1 or 2 (or I guess any recent Samsung phone for that matter) in their car. My question is, will Waze (on a Note 3) interrupt the radio to report an accident or new direction, and then return back to the radio?
To be more clear, I tried using it with my uncle's Note 1 and had one issue. When I am on my Bluetooth setting on my receiver, say listening to spotify. The song that is playing will decrease in volume, Waze will report the notification and then song will resume. However, the phone that I am coming from (iPhone 5) would do the same while on my radio setting. It would fade out, report the notification and then return to the station. However, I could not get that to work on the Note 1.
Is it a Note 1 Bluetooth limitation or will this not just work?
Thanks in advance.
Click to expand...
Click to collapse
The way in which an app will interact with other apps using the audio engine is controlled by the app in question. As such, certain music players will simply decrease volume when another app grabs the audio engine while others will do a hard pause. Others even will allow you to specify the behavior you wish. Look at PowerAMP for an example of such an app.

[Q] Track/Artist Metadata Issue Over Bluetooth?

Hey everyone!
I'm having an issue that I can't seem to resolve. I have a Galaxy S5 that recently received the lollipop update. Prior to this update when playing music from Google Play Music the track/artist metadata would pass and show up on my car's stereo display. Post update I can still connect, play music over bluetooth, and control the music with steering wheel/dash controls, but the metadata no longer displays (using Google Play Music).
I did some different tests and if I play a mp3 file from the stock music app the metadata is passed. I also connected my wife's phone ( Moto X still on KitKat) and tried streaming music though GP Music and the metadata shows up as expected. I've tried deleting/pairing my phone again and even did a factory reset on my S5 last night, but nothing seems to resolve this.
I know there seems to be hit or miss with AVRCP. I haven't been able to find much in terms of actual information and thought I'd check in to see if anyone has had a similar experience or would possibly have a solution.
Thanks!

I am also having the same issue. Sprint basically told me that it isn't their problem and to wait it out. I've downloaded suggested apps and everything else except doing a hard reset.

MP3 metadata not showing over Bluetooth in car - T-Mobile
I just updated to the latest release for my Galaxy S5, Lollipop, and everything seems to work like a champ, except the streaming of music from my phone to my car's in-dash receiver. Prior to the upgrade, everything worked great. All metadata was passed along, as well as the track progress, and skip forward and backward. After the update, the music will play just fine, but I cannot skip tracks from my car stereo or steering wheel controls any more, I have to do it from my phone. Also, none of the metadata is passed along to my stereo.
I use the stock music app on my phone, but I also tried the Google Play Music app, and it does the same thing. The MP3 files are all stored locally on my SD card.
I'm hoping someone else out there has had this problem, and has solved it. Thanks.

Galaxy S5 SongTitle/Artis Display Problem
blinduvula said:
Hey everyone!
I'm having an issue that I can't seem to resolve. I have a Galaxy S5 that recently received the lollipop update. Prior to this update when playing music from Google Play Music the track/artist metadata would pass and show up on my car's stereo display. Post update I can still connect, play music over bluetooth, and control the music with steering wheel/dash controls, but the metadata no longer displays (using Google Play Music).
I did some different tests and if I play a mp3 file from the stock music app the metadata is passed. I also connected my wife's phone ( Moto X still on KitKat) and tried streaming music though GP Music and the metadata shows up as expected. I've tried deleting/pairing my phone again and even did a factory reset on my S5 last night, but nothing seems to resolve this.
I know there seems to be hit or miss with AVRCP. I haven't been able to find much in terms of actual information and thought I'd check in to see if anyone has had a similar experience or would possibly have a solution.
Thanks!
Click to expand...
Click to collapse
I have exactly the same problem. After the lolipop upgrade of S5 I was not able to see the track/artist name on the display of my car anymore. However the there is no problem with streaming of music to car speakers. I'm using spotify but I tried playing mp3 files and different applications. None of them worked. Car display only shows the device name of the S5. I contacted Samsung support with the hope to get an answer and the first thing they asked was whether I tried the device with another bluetooth capable device. No way! I have another car but no bluetooth capability. Recently Samsung deployed another update after lolipop upgrade but the same again.
Having the artis/track name; does it contribute too much? won't make you fly but it was there when we had the kit kat on S5 and missing at the moment. Yes I have the same problem but don't have a resolution... Would be great to hear different ideas or a workaround from Samsung!
Thanks.

Same problem here on my Galaxy S5 with TW Lollipop. I'm so disappointed about all the stuff that changed (e.g notifications) or does not work like Bluetooth avrcp. I start to regret the update to LP. And I wated over a year...

A temporary fix could be to download Music mate from the app store, (it can pull songs from play music onto your device). Not sure if this would help you guys as it seems some of you have already got local access to the mp3s etc.
Just thought I'd say anyway just incase.
Good luck

Shaolin36 said:
A temporary fix could be to download Music mate from the app store, (it can pull songs from play music onto your device). Not sure if this would help you guys as it seems some of you have already got local access to the mp3s etc.
Just thought I'd say anyway just incase.
Good luck
Click to expand...
Click to collapse
Thanks for the suggestion. Music Mate needs a Google Play account which I don't have. I tried another suggested app which should fix this temporary (Bluetooth something) but it did not work. Which I had suspected because the root cause seams to be AVRCP 1.5 inside Android Lollipop instead of older backward compatible versions 1.3 or 1.4. The suspicion is that Google's engeenier didn't have older / legacy / enough different Bluetooth car cits to test. Compiling the source code with a compiler switch, which disables AVRCP 1.5 leads to working meta information. Because Bluedroid is a new proprietary stack newly build by Google it doesn't help to have its source open. There is no APK which we can exchange with a working older version. Instead it seams to be compiled into core components of Android. So the only two chances seams to be:
1. Samsung / Your Handset provider pushes an update which fixes this
2. somebody finds a way through XPOSED to patch the relevant stuff into a life Lollipop.

AVRCP Bluetooth Issues with S7 Edge

Hello all,
I have tried Googling but a working solution hasn't come up for me yet. Ever since getting my S7 Edge in April I've had issues getting AVRCP to work correctly with in car head unit.
It's an Alpine CDE-133BT (actually, I have two of them both with the same problem) supporting AVRCP v1.3 and it worked perfectly on my old HTC One M8 and HTC One X before it (makes me wonder why I ever changed to a Samsung). I've tried clearing the cache as described everywhere online but no luck and I'm getting bored of keep having to manually control my music on my phone. Not only is it dangerous, but also highly irritating.
The only 'control' I can get it work is Pause/Play but only once I have manually started music playing on Google Play Music. Forward and Back don't work, and I certainly can't get any metadata.
I was hoping that Samsung would have fixed this by now; clearly not.
Any advise?
Dave.

Forgot to add; I also hear some loud 'clicking' sounds when listening to something quiet at high volumes.

Anybody?

dsgoody said:
Hello all,
I have tried Googling but a working solution hasn't come up for me yet. Ever since getting my S7 Edge in April I've had issues getting AVRCP to work correctly with in car head unit.
It's an Alpine CDE-133BT (actually, I have two of them both with the same problem) supporting AVRCP v1.3 and it worked perfectly on my old HTC One M8 and HTC One X before it (makes me wonder why I ever changed to a Samsung). I've tried clearing the cache as described everywhere online but no luck and I'm getting bored of keep having to manually control my music on my phone. Not only is it dangerous, but also highly irritating.
The only 'control' I can get it work is Pause/Play but only once I have manually started music playing on Google Play Music. Forward and Back don't work, and I certainly can't get any metadata.
I was hoping that Samsung would have fixed this by now; clearly not.
Any advise?
Dave.
Click to expand...
Click to collapse
did you try updating the software on your alpine, it may not recognize the marshmellow.

I have a 2012 VW Golf and AVRCP works perfectly fine on my end. I don't think it's the phone. Possibly try repairing the phone and make sure to hit allow when the phone prompts you to, to allow your car access to contacts, music, etc... when pairing it.
Sent from my SGP612 using Tapatalk

Cosmic Blue said:
did you try updating the software on your alpine, it may not recognize the marshmellow.
Click to expand...
Click to collapse
My understanding was the AVRCP was a standard protocol; not unique in anyway to the different versions of OS. My old HTC One M8 had Marshmallow on it towards the end of it's life and it worked fine.
While Alpine do provide updates; the mechanism for applying them appears to be very buggy and almost unusable as I have tried it in the past.

siphyn said:
I have a 2012 VW Golf and AVRCP works perfectly fine on my end. I don't think it's the phone. Possibly try repairing the phone and make sure to hit allow when the phone prompts you to, to allow your car access to contacts, music, etc... when pairing it.
Sent from my SGP612 using Tapatalk
Click to expand...
Click to collapse
What version of AVRCP does your car support? The reason I ask is because I borrowed an almost brand new Mazda3 towards the end of last week and AVRCP worked perfectly; but the car supported AVRCP 1.4 (possibly higher - I was able to browse track lists).
Is it possible that AVRCP 1.3 is broken? I'm not alone in this issue after months of Googling; and I have tried all of that previously multiple times but thanks for the suggestion.

dsgoody said:
What version of AVRCP does your car support? The reason I ask is because I borrowed an almost brand new Mazda3 towards the end of last week and AVRCP worked perfectly; but the car supported AVRCP 1.4 (possibly higher - I was able to browse track lists).
Is it possible that AVRCP 1.3 is broken? I'm not alone in this issue after months of Googling; and I have tried all of that previously multiple times but thanks for the suggestion.
Click to expand...
Click to collapse
It supports avrcp 1.3. No track lists for me. Just song, track, album info and ability to use steering wheel controls. My head unit is the stock VW RNS-315.
Sent from my SM-G935U using Tapatalk