GorillaTheHutt
Well-Known Member
i somehow missed that you had actually found a ROM/kernel combo that fixed this. have you had any luck finding any other ROMs that work? if not, i might just switch to your combo.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Galaxy Nexus Bluetooth bug
- Thread starter Dignan17
- Start date
-
- Tags
- galaxy nexus
i somehow missed that you had actually found a ROM/kernel combo that fixed this. have you had any luck finding any other ROMs that work? if not, i might just switch to your combo.
I am currently getting good performance using AOKP Build 31 with the default kernel. I'm using a Jabra Clipper as my A2DP adapter. I don't know if the reason the Jabra Clipper is working for me because it is made by Jabra or if it operates at lower power since it is intended to be used with headphones. I gave this device a try because i discovered I had an old Jabra Extreme headset that seemed to be able to coexist with my car. My other A2DP adapters (Bluetrip and BB Gateway) still have the same interference problem. If you haven't already, I suggest you use BootManager so that you can flash multiple Roms/Kernel combos without having to setup your phone again. I learned the hard way. I know this is fixable because on many Roms when I first flash the Rom A2DP/Handsfree work perfectly together until I reboot. I'm going to try AOKP M5 this weekend.
So did you have the same problem with this Jabra before you put the other ROM on there?
I already had the Jabra Extreme headset laiyng around, I hadn't thought to use it, as I haven't used it for a couple of years since I bought a car that has hands free. I tested it with the phone by disabling the handsfree profile and only using A2DP. After I discovered that this particular headset worked, I bought the clipper, since it is basically a headset with an audio out jack. Both Jabra devices worked with AOKP M3/Codename kernel 1.4 and AOKP build 31/stock kernel.
I'm a little confused. I was asking whether - at any point - you had experienced the issue brought up in my first post in this thread. If you never did, then it's hard to say that the ROM made any difference, isn't it?
Granted, if the problem is with the phone (as I believe it is), I agree that this SHOULD happen with any combination of A2DP device and bluetooth calling device, but I'm happy to be proven wrong here and be able to go back to Tunelink with more ammo...
I experienced the issue in your first post starting when I bought the phone in mid December, that was the main reason I started flashing different ROMS/Kernels as they came out. The ROM was the only part of the equation I could change until April when I remembered that I had the Jabra A2DP headset I could test in addition to the A2DP adapter I was already using in my car. Every time I flashed a new ROM (Stock 4.03, CM9, MIUI) I would see if either device performed differently while paired with the car. Eventually I found ROM/Kernel combo that worked with one of the A2DP adapters. It's not a 100% solution, more of a workaround. I agree with you that there should be a software update that let's this phone pair with any handsfree and still work with any A2DP adapter a customer might buy.
JayBomb999
Lurker
I just wanted to add a "me too" to this thread. I have a Verizon Galaxy Nexus, TuneLink Auto for Android and a Cadillac CTS. Like the OP, I get garbled, robotic voice during any phone conversation when connected to the vehicle and A2DP (TuneLink) simultaneously.
Has a resolution to this bug been found? Is it true that using an AOKP rom fixes this issue?
J
Has a resolution to this bug been found? Is it true that using an AOKP rom fixes this issue?
J
GorillaTheHutt
Well-Known Member
from the google code case (this worked for me):
Very cool! I need to ask, because it wasn't entirely clear, is it necessary that the phone be rooted in order to make these edits? It wasn't clear whether that was the case, or if it was just to flash with the attached file...
I don't really want to root my phone, so it would be great if I could just make some changes. But I'm assuming that's not possible
I don't really want to root my phone, so it would be great if I could just make some changes. But I'm assuming that's not possible
TheyCallMeBT
Android Enthusiast
I'd like to know the same. Someone just wrote this.
So he's not rooted, but has the bootloader unlocked. I don't really know what that means. lol. Is this something that those of us who are not rooted can do, without erasing data?
So he's not rooted, but has the bootloader unlocked. I don't really know what that means. lol. Is this something that those of us who are not rooted can do, without erasing data?
GorillaTheHutt
Well-Known Member
the process to unlock the bootloader is not the same as rooting, but is of similar complexity:
http://androidforums.com/verizon-ga...gs-root-samsung-galaxy-nexus.html#post3736593
i'm not really sure why you wouldn't root if you've unlocked, but hey, it's a personal preference
for the record i'm rooted and made the edits using the Root Explorer app, which was super easy.as far as i know, unlocking the bootloader still causes all the data on your phone to be wiped. not sure if there's a way around that yet, since that was the first thing i did once i got my phone
if you can root without unlocking the bootloader, that would be a way to make the change to audio.conf without losing your data. i found this thread:
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
but i haven't actually done that, so make sure to read up on it if you decide to go that route.
TheyCallMeBT
Android Enthusiast
Thanks Gorilla!
So I was streaming a radio station in the TuneIn Radio app and playing it through the Tunelink to my head unit yesterday. And then I got a phone call, I answered and started to unplug the Tunelink and tell them to wait 10 seconds. And then I realized that the call was completely clear. After that, I tried calling another number and it was clear.
I haven't had chance to test it today to see what it does. There may be something different between streaming radio and mp3's on the internal storage.. I don't know. But I haven't done anything to potentially fix the problem (yet). I'll report back when I test again.
So I was streaming a radio station in the TuneIn Radio app and playing it through the Tunelink to my head unit yesterday. And then I got a phone call, I answered and started to unplug the Tunelink and tell them to wait 10 seconds. And then I realized that the call was completely clear. After that, I tried calling another number and it was clear.
I haven't had chance to test it today to see what it does. There may be something different between streaming radio and mp3's on the internal storage.. I don't know. But I haven't done anything to potentially fix the problem (yet). I'll report back when I test again.
Thanks so much again for posting this. I rooted without unlocking the bootloader (thanks to Gorrilathehutt for the link), but I have no idea how to "flash the audio.conf" file or how to edit it. What do I do now?
JayBomb999
Lurker
@Dignan17
In order to flash the blutooth2.zip file, you would need to unlock the bootloader and flash a custom recovery. CWM is a very popular one.
While I recommend that option, it is not the only way if you're rooted. The easiest in my opinion is to download RootExplorer from the Android market. It's 4 bucks and worth every penny. This would allow you to edit the audio.conf file directly. Reboot and then you're done.
If you don't want to spend money, you can use adb from the android SDK. It's free, but command line based. It will allow you to log in to the the Android shell and modify the audio.conf also.
There is also the Galaxy Nexus Toolkit over at XDA. I've never used it, but it is a GUI for Windows that allows you to do these things pretty easily (I hear).
Good luck.
In order to flash the blutooth2.zip file, you would need to unlock the bootloader and flash a custom recovery. CWM is a very popular one.
While I recommend that option, it is not the only way if you're rooted. The easiest in my opinion is to download RootExplorer from the Android market. It's 4 bucks and worth every penny. This would allow you to edit the audio.conf file directly. Reboot and then you're done.
If you don't want to spend money, you can use adb from the android SDK. It's free, but command line based. It will allow you to log in to the the Android shell and modify the audio.conf also.
There is also the Galaxy Nexus Toolkit over at XDA. I've never used it, but it is a GUI for Windows that allows you to do these things pretty easily (I hear).
Good luck.
Hallelujah!
It's still early, but in my very limited testing, it appears that the problem has been fixed, thanks to the awesome people posting here and in the Google Code issue thread.
I rooted my phone using the instructions linked to here (without unlocking the bootloader, thus avoiding a phone wipe), and I then installed Root Explorer and made the changes mentioned on the Google Code entry and SUCCESS!!!
I am now able to use the Tunelink AND make/receive calls. This is a HUGE deal for me. I'm in my car all day every day, making frequent stops. The only way I stay sane in the car is by listening to podcasts or rdio, but I also need to field frequent phone calls from my clients.
Because of this bug, I have been having to accept the call, wait for it to connect to bluetooth, then switch to "handset earpiece" mode on the phone and talk to clients that way. Clearly this was not a good thing, as it required me to be looking at my phone AND then holding it to my ear. Plus, whenever I drove into DC, where they have hands-free laws, I just couldn't answer or use the phone at all.
But no more! YES! Thanks to everyone who contributed to this thread. I think we can reasonably call this issue as closed as it can be right now. The only solutions available are to follow the instructions available in this thread, or wait for the next ICS update and hope that it has the right changes to the audio.conf. But considering there's really no drawback to just going ahead and solving this ourselves, I'd encourage folks to go for it.
It's still early, but in my very limited testing, it appears that the problem has been fixed, thanks to the awesome people posting here and in the Google Code issue thread.
I rooted my phone using the instructions linked to here (without unlocking the bootloader, thus avoiding a phone wipe), and I then installed Root Explorer and made the changes mentioned on the Google Code entry and SUCCESS!!!
I am now able to use the Tunelink AND make/receive calls. This is a HUGE deal for me. I'm in my car all day every day, making frequent stops. The only way I stay sane in the car is by listening to podcasts or rdio, but I also need to field frequent phone calls from my clients.
Because of this bug, I have been having to accept the call, wait for it to connect to bluetooth, then switch to "handset earpiece" mode on the phone and talk to clients that way. Clearly this was not a good thing, as it required me to be looking at my phone AND then holding it to my ear. Plus, whenever I drove into DC, where they have hands-free laws, I just couldn't answer or use the phone at all.
But no more! YES! Thanks to everyone who contributed to this thread. I think we can reasonably call this issue as closed as it can be right now. The only solutions available are to follow the instructions available in this thread, or wait for the next ICS update and hope that it has the right changes to the audio.conf. But considering there's really no drawback to just going ahead and solving this ourselves, I'd encourage folks to go for it.
TheyCallMeBT
Android Enthusiast
Is this something that if you do the fix you'll have to re-do with 4.0.4? I looked in the files from the system update that went out a few weeks ago and there are a couple of files dealing with the bluetooth radio.
If anyone here followed the instructions to fix the audio.conf file, and also rooted their phone, I just wanted to confirm that upgrading to 4.0.4 appears to be okay for my phone. Everything seems to be working fine, including my bluetooth situation. I would be curious to hear if anyone who didn't go through this process now has functioning bluetooth in their car. In other words, I wonder if 4.0.4 fixes this problem.
Okay, I am now more frustrated with the technologically advanced Galaxy Nexus than I ever was with my Nexus One or even my G1.
I had about a week there where everything was working perfectly. I was listening to podcasts with my Tunelink, and making calls through my car.
Then the 4.0.4 update came.
Now, when I receive/place calls, the other person sounds terrible, cuts in and out, and the quality just generally sucks. To be clear, this is NOT what I was getting when I started this thread. It's a different kind of crappy call quality. There is a thread on the subject here.
To make matters worse, it appears that the update has screwed up my phone. There are all kinds of aspects to the my phone that don't seem to work anymore. Light Flow no longer gives me ANY notifications, the Power Control Plus widget still controls stuff but gives no visual feedback (the bluetooth icon doesn't toggle when it's pressed), and other things are messed up too. Lastly, is it normal for my phone to have become un-rooted after the update? It appears that I don't have root access anymore, and Super User doesn't show up in my installed apps list (though it's still on my home screen and still launches).
What can I do? If I factory reset my phone, will it appear like new to any Verizon peeps? I'm asking in case I need to return this thing...
Thanks for your help, everyone.
I had about a week there where everything was working perfectly. I was listening to podcasts with my Tunelink, and making calls through my car.
Then the 4.0.4 update came.
Now, when I receive/place calls, the other person sounds terrible, cuts in and out, and the quality just generally sucks. To be clear, this is NOT what I was getting when I started this thread. It's a different kind of crappy call quality. There is a thread on the subject here.
To make matters worse, it appears that the update has screwed up my phone. There are all kinds of aspects to the my phone that don't seem to work anymore. Light Flow no longer gives me ANY notifications, the Power Control Plus widget still controls stuff but gives no visual feedback (the bluetooth icon doesn't toggle when it's pressed), and other things are messed up too. Lastly, is it normal for my phone to have become un-rooted after the update? It appears that I don't have root access anymore, and Super User doesn't show up in my installed apps list (though it's still on my home screen and still launches).
What can I do? If I factory reset my phone, will it appear like new to any Verizon peeps? I'm asking in case I need to return this thing...
Thanks for your help, everyone.
Dignan17,
Was this an Over the Air 4.0.4 update? If so, I'm guessing that is the reason you lost root. The same thing happened to me with 4.0.2. You may need to reapply the audio.conf changes posted by GorillaTheHutt, if not already done. AOKP 4.0.4 has been working well for me for the past two weeks with the audio.conf changes. If none of this works for you and you do want to return the phone, you can reflash the OTA 4.0.4, unroot, and relock the bootloader.
Was this an Over the Air 4.0.4 update? If so, I'm guessing that is the reason you lost root. The same thing happened to me with 4.0.2. You may need to reapply the audio.conf changes posted by GorillaTheHutt, if not already done. AOKP 4.0.4 has been working well for me for the past two weeks with the audio.conf changes. If none of this works for you and you do want to return the phone, you can reflash the OTA 4.0.4, unroot, and relock the bootloader.
Yeah, that's what it's looking like.
The problem doesn't seem to be the same one. I'm seeing other users (in that thread I linked to) with the same issue, and it's just with a plain old bluetooth connection to a single device (like your car). It's unrelated to the Tunelink, so I'm skeptical that the audio.conf fix will apply to this issue, but I suppose it's a possibility.
Question: what if I used the instructions that let you root without unlocking the bootloader? Would VZW be able to tell if I'd rooted it at some point? I'm just worried I wouldn't have enough ammunition for a return. We all know that I probably didn't screw up the phone with the help of the good people of Android Forums, but VZW will likely look for any excuse to deny my request... You can see I'm a tad worried about that...
Your logic with regards to your new issue sounds good. Your thread fixed my issues, so I was hoping there was a way for you to keep a fully functioning GNex. If at the end of whatever root method you choose, you perform a full wipe and flash an OTA ROM, I don't see what evidence there could be. I have returned a couple of other phones to my local store in the past and the first thing they will do is their own wipe/reflash in an attempt to fix the phone. At this point either they should be able to demonstrate a working bluetooth or replace the phone. I am guessing that so many of these phones have been returned for similar issues that they will hardly be surprised.
Hello friends,
My mobile phone's (Samsung Nexus S) bluetooth disconnects after 1-2 minutes when I am in my car.
I managed to discover that, when I shutdown the Wifi of my mobile phone, everything works fine (pairing is successful and the mobile phone is connected via the bluetooth).
Does this make sense?
Why does it happen? What is the relation between the nexus S Wifi and bluetooth? I thought these are separate technologies that utilize separate spectrum...
Waiting for any advice,
Amit.
My mobile phone's (Samsung Nexus S) bluetooth disconnects after 1-2 minutes when I am in my car.
I managed to discover that, when I shutdown the Wifi of my mobile phone, everything works fine (pairing is successful and the mobile phone is connected via the bluetooth).
Does this make sense?
Why does it happen? What is the relation between the nexus S Wifi and bluetooth? I thought these are separate technologies that utilize separate spectrum...
Waiting for any advice,
Amit.
TheyCallMeBT
Android Enthusiast
Amit, I don't think you're going to get any answers in this thread. Try the Nexus S forum.
Nexus S - Android Forums
So, if any of you update to a JB ROM, I'm interested to hear how this problem turns out. I've still been reluctant to root and ROM just to fix this issue. But I'm considering a JB ROM once I'm sure they're stable, and then fixing the one file would be a walk in the park once that is done.
Nexus S - Android Forums
So, if any of you update to a JB ROM, I'm interested to hear how this problem turns out. I've still been reluctant to root and ROM just to fix this issue. But I'm considering a JB ROM once I'm sure they're stable, and then fixing the one file would be a walk in the park once that is done.