Related
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.
I am getting an audio crackle in my 2005 mini cooper s with a kenwood radio over bluetooth on stock 12b. When on a CM based rom this doesn't happen (lg roms have a built-in equalizer?). If someone knows how to remove the stock eq please post how. Thanks
"I have a similar issue in my 2011 Hyundai Genesis Coupe. The static is only present during loud levels on songs, not at all times during the track. Seems like it is most noticeable on the higher frequencies also. Please reply here if your issue is the same.
I did not have this problem on my HTC One X in the same car.
I have searched all over Android and Hyundai forums and found little to work with. What I have found is that this is not affecting everyone, otherwise it would be all over the forums. I appears to me that it is related to our cars bluetooth receivers and how they communicate with the phone.
I found some posts from a user CBaronne where he had what appeared to be the same issue on another phone and modified the "Bitpool" value with good results. He wanted to do the same on this phone but the variable is buried in a system file and modifying it was beyond his expertise.
I have also flashed several sound mods with no success, as well as different tricks to ensure that APT X is enabled. Nothing has helped.
I think until we get a developer with this phone and has this issue there will not be any attempt made to resolve. You can always just buy another car..."
I have been posting this comment in several threads to try an get some attention on it. This issue is not common enough for it to have consistent comments or investigation. I also can confirm that it does not happen on CyanogenMod, so that's what I use now.
Are you on LG's stock Kit Kat?
Other threads:
http://forum.xda-developers.com/show...0#post47418870
http://forum.xda-developers.com/show...9#post47423589
http://forum.xda-developers.com/show...5#post49735305
Reading other Android forums and Hyundai threads it DOES appear to be a compatibility issue, meaning that it is about the combination of two devices, it does not affect every G2 bluetooth connection. From the first link I posted it DOES appear that if we can adjust the bitpool values of the G2 we could improve the quality.
Slinkynose said:
"I have a similar issue in my 2011 Hyundai Genesis Coupe. The static is only present during loud levels on songs, not at all times during the track. Seems like it is most noticeable on the higher frequencies also. Please reply here if your issue is the same.
I did not have this problem on my HTC One X in the same car.
I have searched all over Android and Hyundai forums and found little to work with. What I have found is that this is not affecting everyone, otherwise it would be all over the forums. I appears to me that it is related to our cars bluetooth receivers and how they communicate with the phone.
I found some posts from a user CBaronne where he had what appeared to be the same issue on another phone and modified the "Bitpool" value with good results. He wanted to do the same on this phone but the variable is buried in a system file and modifying it was beyond his expertise.
I have also flashed several sound mods with no success, as well as different tricks to ensure that APT X is enabled. Nothing has helped.
I think until we get a developer with this phone and has this issue there will not be any attempt made to resolve. You can always just buy another car..."
I have been posting this comment in several threads to try an get some attention on it. This issue is not common enough for it to have consistent comments or investigation. I also can confirm that it does not happen on CyanogenMod, so that's what I use now.
Are you on LG's stock Kit Kat?
Other threads:
http://forum.xda-developers.com/show...0#post47418870
http://forum.xda-developers.com/show...9#post47423589
http://forum.xda-developers.com/show...5#post49735305
Reading other Android forums and Hyundai threads it DOES appear to be a compatibility issue, meaning that it is about the combination of two devices, it does not affect every G2 bluetooth connection. From the first link I posted it DOES appear that if we can adjust the bitpool values of the G2 we could improve the quality.
Click to expand...
Click to collapse
sorry for late reply, I was on 4.2.2 stock. right now I am on cloudyflex 4.2.2 and I have yet to see if it makes a difference.
I had the issue on every 4.2.x ROM I tried. When I moved to Cyanogen 11 the crackle went away. I don't want to switch away until I know that this issue is not present on the 4.4 Stock ROM.
My recommendation is that you try a 4.4 Stock ROM if this is important, if that doesn't resolve, go with Cyanogen.
welcome to the world of botched standards, its often appliences with same technology dont always work, just check compatability of devices such as car radios with mobile phones. contact them and ask if they have or can update compatability with newer tech.
its possible kenwood already has an update
send from the jungle
I have a new issue, and need some ideas...
I have a Mazda 3 2014 with built in Infotainment system, and I can of course place calls from it over bluetooth. My Nexus 5 would dial, and as you expect the car remains connected and the audio and dialling occurs through the car system. With my Nexus 6P, the car talks to my phone, and then immediately cuts off the bluetooth, a bit like a failure to communicate, but the phone will then carry on calling, and only if I try to dial from my car, and if the person has answered does it then lock on and maintain the call via the car system.
I can not find anything in either settings to explain it.
So, anyone have any ideas crutually why the 6P fails me where the 5 worked.
I have the exact same issue. I have a Mazda CX-5.
nahuelarg86 said:
I have the exact same issue. I have a Mazda CX-5.
Click to expand...
Click to collapse
Would be the same system if yours is the current model too. Guessing it was fine on your previous phone too?
Yes, I think so. It is a 2016, so it is the latest system I suppose. I had a Samsung Galaxy S5 previously and it worked perfectly. This is my first Nexus, so I thought it was a Nexus thing at first, however it is really annoying. It is hard to explain because the bluetooth kinda works, it just has this thing that it drops and picks up again...
Bluetooth working fine with my 2013 kia forte. Maybe something to do with Marshmallow and Mazda Bluetooth system?
Yea, it is kind of hard to explain. Only found out today, so not been able to test it over and over, but seems that unless the other person answers, you have no idea it is dialling. It is like it (Mazda system) is being told it an not carry on. I once had the same issue (Nexus 5) when there was another phone option and it was waiting for a default to be set on the phone before it dials. It did not do it today, but I wonder if I make sure it is set in settings as the default right....
... nope, only app for calls is the inbuilt.
It seems like some people are having similar issues? --> http://forum.xda-developers.com/nexus-6p/help/bluetooth-phone-completely-borked-t3241196
I had the phone for a couple days and tried some things like upairing/re-pairing with no results. I discovered it when I called my wife, the call dropped (or the car did the call drop sound) but all of the sudden my wife answered. I tried calling different numbers and it's the same deal. I haven't tried receiving a call.
nahuelarg86 said:
I have the exact same issue. I have a Mazda CX-5.
Click to expand...
Click to collapse
And I have the same issue with a 2015 Honda Accord Hybrid. I don't have the issue with any of my other phones. Google Support doesn't know why it's happening.
Reading this https://code.google.com/p/android/issues/detail?id=189188 it seems clear it is Marshmallow on many devices and systems
AllyGraham said:
Reading this https://code.google.com/p/android/issues/detail?id=189188 it seems clear it is Marshmallow on many devices and systems
Click to expand...
Click to collapse
Nice find. I'll chime in in that thread. I hope Google can solve this soonish since it is kinda a major annoyance at the moment.
Hello, I have Android 8.0 and tried to use some JVC headphones. But it doesn't see them at all.
I read this is an issue on many phone models, acknowledged by Google, that will be fixed eventually. I see 8.1 has some mention about bluetooth, so the first question is if there is any chance of getting that update sooner on A1?
When I turn on bluetooth outside it sees quite a long list of devices, so apparently the receiver is strong (can pick up signal from far away). But most of the devices are not listed by name, but by a string of numbers and letters. The headphones are not among them. I could pair it, instead with another phone running Miui.
I tried playing with all settings in Developper options with no effect. (They seem to go back to default option anyway.)
Did anybody find a solution to this?
I'm wondering if anyone has issues with and solutions for bluetooth connectivity problems. Specifically, constant dropouts and stuttering.
Background of problem
I recently purchased my phone, which was already on Android 10 (Build QP1A.190711.122). From the start, bluetooth has been unbearable: if I move the phone in any way, or I move the connected bluetooth device (headphones, earbuds, speakers, etc.) it stutters and cuts out momentarily. Sometimes the stuttering continues incessantly. In short, my bluetooth is useless for listening to audio, making phone calls, etc. I basically have to be next to be perfectly still and right next to the phone, and even then it may act up.
Failed troubleshooting efforts
I installed the September update, rooted the phone and tried various options many times, including:
*Hard resetting the phone
*Flashing and re-flashing the stock rom several times (even after full wipes)
*Wiping the cache in recovery
*Clearing the bluetooth cache
*Playing with the bluetooth options in Developer Options
*Unpairing and re-pairing various bluetooth devices
I'm lost and wondering if the gyroscope is messing with bluetooth connectivity in someway. I have no idea whatsoever.
Thoughts and comments appreciated.
@droctii
I have not had an issue like this, sounds like a low power/weak signal issue or interference or conflicting devices
Which sounds like this
https://forum.xda-developers.com/essential-phone/help/awful-bluetooth-connection-t3713280
users report 2 or 3 fixes scanning through thread
Same here. bluetooth connectivity has rather worsened since android 10.
however the recent ota updates on android 9 have been a hit or miss since march 2019. Before that, bt was working perfectly fine.
Coming back to android 10, as an example, the link with my bose soundwear with minor exceptions had been really strong bt -wise but since the update I get even with it random disconnects, and infrequent stutter/cuts etc. The same for my sony wh1000x m3, it behaves a little better but only using sbc codec, so i stick to that. However, older devices such as my car's bt, tv soundbar or even google mini when phone's just next to it are unusable with this phone. Also, the more crowded an environment (interference-wise) more likely to experiment issues.
For comparison, all other older phones I have still work fine within same parameters
I haven't taken my PH-1 to A10 yet, but my pixel 3XL had been struggling with Bluetooth. Today is the first time it's been useable, but I made a bunch of random changes in developer options. I haven't worked out which had helped. FWIW, I'm attaching a screen shot of the settings I'm using.
ktmom said:
I haven't taken my PH-1 to A10 yet, but my pixel 3XL had been struggling with Bluetooth. Today is the first time it's been useable, but I made a bunch of random changes in developer options. I haven't worked out which had helped. FWIW, I'm attaching a screen shot of the settings I'm using.
Click to expand...
Click to collapse
A lot of Bluetooth devices don't implement the protocols properly, especially on the cheaper side. You disabled A2DP so that probably helped.
You should be able to enable A2DP but use the highest version of AVRCP available, yours seems rather low. Should work fine.
Verlog5454 said:
A lot of Bluetooth devices don't implement the protocols properly, especially on the cheaper side. You disabled A2DP so that probably helped.
You should be able to enable A2DP but use the highest version of AVRCP available, yours seems rather low. Should work fine.
Click to expand...
Click to collapse
What makes you think A2DP is disabled? The hardware handoff is disabled. Not the same thing. And that is the solution to my stuttering and disconnect issues. Toggling that makes the problems come and go.
Same problem on my car with 1+7pro and android10, music is discontinued, or freezed, stuttered...
But for me line with disable bt ad2p hardware offload is greyed and swith is to left
salva52 said:
Same problem on my car with 1+7pro and android10, music is discontinued, or freezed, stuttered...
But for me line with disable bt ad2p hardware offload is greyed and swith is to left
Click to expand...
Click to collapse
You would be better served looking/posting in your own device forum. This is the Essential PH-1 and your software is very different.
I have had such problems with various devices and while disabling A2DP offload always solved the problem, so did playing around with the AVRCP versions.
My essential phone has been sitting on my desk for the last 3 months due to these insolvable bluetooth issues. Neither AVRCP nor A2DP solved the issues, the bluetooth is stuttering constantly when I move my phone around and not in direct sight of my receiver(s).
I tried 3 different wireless earbuds and they all suffer from random stutters or disconnects if I'm actively walking with my phone. The closer the phone is to my upper body, the better the signal is (most of the time). If I connect my phone to any Bluetooth device at home or in the car where the phone isn't moving, the connection is perfect. I've tried the different methods mentioned in this thread and nothing fixes it. I've given up and just hoping my next phone doesn't suffer from the same thing.