From a guy who was unrooted, now rooted, and tried everything I can tell you there is a DEFINITE blue tooth issue since ota 4.0.4.
It is reproducible and correctable too. If you flash any radio prior to official 4.0.4 radio (including leaked 4.0.4 radio) blue tooth works PERFECTLY. But, if you then flash the 4.0.4 or jelly bean radio the issue reoccurs.
The issue may be subtle or severe, depending on how you use the bt device, but it has to do with fixed vs variable volumes. I myself, in my car cannot use bt on newer radios as I struggle to hear.
I cannot however use jb sourcery with the old radios as for some reason they drain battery so fast (had a 'sleep' issue with battery on older radios)
Sent from my Galaxy Nexus using Tapatalk 2
The Following User Says Thank You to Jeffruby For This Useful Post:
From a guy who was unrooted, now rooted, and tried everything I can tell you there is a DEFINITE blue tooth issue since ota 4.0.4.
It is reproducible and correctable too. If you flash any radio prior to official 4.0.4 radio (including leaked 4.0.4 radio) blue tooth works PERFECTLY. But, if you then flash the 4.0.4 or jelly bean radio the issue reoccurs.
The issue may be subtle or severe, depending on how you use the bt device, but it has to do with fixed vs variable volumes. I myself, in my car cannot use bt on newer radios as I struggle to hear.
I cannot however use jb sourcery with the old radios as for some reason they drain battery so fast (had a 'sleep' issue with battery on older radios)
Sent from my Galaxy Nexus using Tapatalk 2
I'm still shaking my head about this. It's probably an easy fix. I can't believe they won't even acknowledge it! It's a big deal to me since my professional life revolves around bluetooth and it's VERY inconvenient to try to work without it, and speaker phone is unprofessional.
there must be some other combination of issues that causes this to happen. has anyone tried to narrow it down to type of connection perhaps? only on wifi, 3g, 4g, etc?
i have a vzw galaxy nexus fwiw...
3G for me.
And, the only thing that got better with the JB radios was a little more volume. No clarity at all.
Is this issue with in car bt only or with ear pieces too?
It's interesting that only a handful of people are mentioning this issue or even able to replicate it. Especially considering the views on this thread and the size of the community here. That's also probably why there's been no acknowledgment from Samsung or Google.
That said, I'll continue to keep an ear out for any bt anomalies. Good luck to those who are having the problem.
Got my 4.1.1 update, BT better but still sucks. Media however, always sounded great. I just don't get that.
I've only experienced it in calls. Otherwise, the sound quality is great. I just wish they would reverse that part of it to the earlier version that worked or fix the newer version. It can't be too hard. The problem is that they don't seem to be willing to acknowledge it.
Last edited by paleodust; October 11th, 2012 at 06:14 PM.
I've only experienced it in calls. Otherwise, the sound quality is great.
Same here. Streaming Pandora works just fine, but when I try to use the phone over bluetooth in my car, the other person can barely make out what I'm saying. Makes the handsfree function absolutely useless.
Hi. Am new to this forum...googled the BT issue.....
I have gotten a total of 3 headsets from VZ, the BT phone audio is horrible on all of them. Am very frustrated wasting my time configuring new phones, they won't let me go for a new model, and the clock is ticking on the one year "warranty".....
As others have posted, this all started w/the first update, which fixed some things and screwed up BT. I've used many earpieces, eg Jawbone, Moto, Plantronics. The sound is fine on the AD2DP profiles, eg navigation, music etc. But cuts in and out and distorted on phone calls. on the other end, my voice is fine as per my friends.
Somewhere on android central I read that this issue is similar on the S3 w/JB, not sure. I'm going to try to raise a complaint w/VZ and tell them that the phone is not functional for me......What a waste of everyone's time, shipping and reshipping bad phones. I do wonder why this is not a "known issue" w/the service dept.
Is there any way to get them to fix it for the next update? It's frustrating the heck out of me! And rooting shouldn't have to be the answer.
Well, now they are giving the GNEX for free; I have a feeling they have said to hell w/those of us who have it; my problem w/waiting for another upgrade is it will prob. be past the 1 year I got the phone. I don't root, etc, but it seems like there is a solution if you do. Don't know why the S/W people can't just implement it.
Device(s): Samsung Galaxy Nexus HSPA+,
HP Touchpad w/ CM10 and Nook Color (previously rooted)
Carrier: T-Mobile
Thanks: 87
Thanked 350 Times in 216 Posts
Quote:
Originally Posted by samkatz
Well, now they are giving the GNEX for free; I have a feeling they have said to hell w/those of us who have it; my problem w/waiting for another upgrade is it will prob. be past the 1 year I got the phone. I don't root, etc, but it seems like there is a solution if you do. Don't know why the S/W people can't just implement it.
Verizon seems to take about two months to release the update. Apparently Verizon puts the updates through their own QC (not that you can really tell) and put their own software on the phone.
We'll hope they can get 4.1.2 out before Christmas -- if not you have to wonder if it won't be further delayed a week or two for the holidays. After that, it will likely be an extra month or two for 4.2.1 -- with the minor issues that people are having with 4.2, it would be best if they skipped that update. Hopefully one of these will fix the bluetooth.
Verizon seems to take about two months to release the update. Apparently Verizon puts the updates through their own QC (not that you can really tell) and put their own software on the phone.
We'll hope they can get 4.1.2 out before Christmas -- if not you have to wonder if it won't be further delayed a week or two for the holidays. After that, it will likely be an extra month or two for 4.2.1 -- with the minor issues that people are having with 4.2, it would be best if they skipped that update. Hopefully one of these will fix the bluetooth.
didn't realize there was another 4.1....x update. Am using 4.2 on
Google nexus tab. pretty good except a few 3rd party apps don't work.
Just in case you need any more me too's. Audio on Plantronics Legend was awful and I love my Plantronics headsets. I fixed the problem with aforementioned install of 4.0.4 (IMM30B) radios. This gives the best of both worlds for bluetooth call quality and 3g/4g switching, though I wonder what the downside of using leaked radios might be.
Would love an official radio fix but this thread leaves me doubtful.
Just the uncertainty. They didn't officially ship it for a reason. (Though for this thread, it looks like the reason was that they hadn't messed up BT yet). I'm on 4.2.1 (CM10.1) now and I notice a bit of wonkiness when switching between 3G/4G/Wifi. I'm not sure it's the radios and most times everything works fine so I would still recommend it to anyone having the audio quality trouble mentioned in this thread.
The Following User Says Thank You to Alguy For This Useful Post:
Just the uncertainty. They didn't officially ship it for a reason. (Though for this thread, it looks like the reason was that they hadn't messed up BT yet). I'm on 4.2.1 (CM10.1) now and I notice a bit of wonkiness when switching between 3G/4G/Wifi. I'm not sure it's the radios and most times everything works fine so I would still recommend it to anyone having the audio quality trouble mentioned in this thread.
I just hope the rumored 4.2.2 release finally fixes this issue. I'm really getting sick of it. It's amazing that they've made us put up with it for so long without even acknowledging it!
I've tried the leaked 4.2.2 (JDQ39) and the new radios (LTE FK01/CDMA FK02) and neither seemed to fix the in-call bluetooth audio problem introduced in 4.0.4 (IMM76K). After also trying the new radios on CM 10.1 and getting no joy, I'm back to leaked radios LTE-FA02 / CDMA-FA02 (IMM30B). Has anyone else had a different experience with latest radios?
The Following User Says Thank You to Alguy For This Useful Post:
I've tried the leaked 4.2.2 (JDQ39) and the new radios (LTE FK01/CDMA FK02) and neither seemed to fix the in-call bluetooth audio problem introduced in 4.0.4 (IMM76K). After also trying the new radios on CM 10.1 and getting no joy, I'm back to leaked radios LTE-FA02 / CDMA-FA02 (IMM30B). Has anyone else had a different experience with latest radios?
That's not the answer I was hoping for, but thanks.
The Galaxy Nexus is the third official phone contracted by Google and the first phone to come with Android 4.0 Ice Cream Sandwich. Specs include a 1.2GHz dual-core processor, 1GB of RAM, 16/32GB of internal storage, a 4.65 inch 720p HD Super AMOLED... Read More
18Likes
