Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
I am having the same issues on a Verizon Galaxy Nexus V4.02. If I turn bluetooth off mid-call the earpiece sounds fine. The static only happens during voice calls, streaming A2DP sounds fine. There are bluetooth improvements listed in the 4.03 changelog, hopefully this will be resolved.
I had some problems with my BT speaker phone. I turned off the key press sounds and the screen off sounds and that pretty much fixed it.
I have an off topic question for you guys that use bluetooth streaming. Can start the car and press play from the HU to start music? I can with my old D2, but not my TB. I have to actually start the music player on the thunderbolt, then I can control it from my HU. I would like to upgrade, but I don't see a huge advantage in upgrading if I still can't start my music without having to actually take the phone out of my pocket. (Yes, I know it's stupid, but I'm lazy.)
I have this same issue in one of my cars. I ran a number of tests and the issue only occurs on my vehicle when the phone is connected to both for telephony and a2dp music. The static occurs whether or not a2dp is actually being used to stream music or not. This particular vehicle has two separate devices for music and telephony. If I unpair or disconnect the music device, then telephony works without the audio distortion. As soon as I reconnect the music device, the static is re-introduced.
v0yeur said:
Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
Click to expand...
Click to collapse
I am experiencing this issue as well and have not been able to resolve it. I've tried disabling the touch sounds, screen off sounds, etc. but to no avail.
It pretty much makes handsfree unusable while driving. What have you guys done in the meantime? Have you been able to resolve the issue yet?
Here's my specific details:
Phone: Verizion LTE Galaxy Nexus v4.02 stock/unrooted
Handsfree Car System (phone audio): Stock 2007 Audi A4
Separate A2DP Module (media audio): Dension Gateway Five connected to factory Stereo
All of my previous phones (Thunderbolt, Droid X, Incredible, OG Droid) have fully supported this setup with no issues whatsoever.
On a sidenote, my A2DP streaming is also unreliable. It first has trouble connecting to the device. If/when it does, audio constantly cuts out when streaming Pandora, Slacker Radio, Google Music... pretty much any streaming over network connection. I have not tried locally stored music yet as I don't have any currently stored on my device. Are you guys experiencing this A2DP issue as well?
I wonder how widespread this is and if it warrants opening an official issue with Google.
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
radi0chik said:
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
Click to expand...
Click to collapse
I appreciate the suggestion but unfortunately, I have the issue even if WiFi is off (I never use WiFi).
I'm going to try and toggle a few of the sound and haptic feedback settings a little more to see if it's pertinent to a certain on/off configuration. It's a shot in the dark but I'll try anything at this point.
ok it was worth a shot. Maybe on a whim turn off 3g/data so basically its airplane mode except BT is on? Just to eliminate any RF interference. Other than that I dont know
Spent quite a bit of time in the car today to try and pinpoint a cause and I have had no luck.
Phone audio will sound great and then all of the sudden turn digitized and distorted for a random period of time, then revert back to sounding great. One thing to note is that the distortion is both ways - the person I'm talking to also hears it when I speak and cannot understand what I'm saying. It's very frustrating not being able to use this feature.
I am on my 2nd replacement phone and ALL of them have had this issue (returned two others to VZW due to this issue and the speaker clicking issue). I am still wondering if it is software/OS releated or if it's due to poor hardware.
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Stowegy said:
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Click to expand...
Click to collapse
I've got the same issue. Even with NFC disabled. Makes listening to Pandora in the car unbearable. I've gone through the same steps as you, but hasn't exchanged the phone yet. I've had previous Androids and it was a hit/miss with the distortion, but with an iPhone or BB never had this issue. Go figure.
thanks to all the replies, will update to 4.0.3 and try out some more options.
- unplugging my music dongle had no effect on call quality
- NFC on or off had no effect
I also find that the music adapter never auto-connects and needs me to go in to the BT settings page and manually select it.
thanks all.
Hello again. So I have an update that adds to the flakiness ...
Updated to the Bugless Beast ROM and Franco's kernel. My intent was to completely reset the phone and hopefully get a new Bluetooth stack in the process.
Initially everything paired OK, but after a while my audio randomly disconnects after about 20minutes and then reconnects depending on its mood.
My phone connection is more controllable now: if the BT is enabled on my phone when I turn on the car, the sound quality is entirely digitized and unusable. If I turn on the car and THEN enable my phone, the sound quality is flawless every time.
Still not ideal, but manageable. For the music audio part, I lay the blame entirely on the Audi Music Interface BT adapter: the thing is crap and always in pair mode even with the car turned off! The telephone BT in the car head unit has seen several phones pair with it without any issues (I do mobile development so I get to play with many phones) so in that case, I can't blame anything but the Nexus.
I really hope someone at Google or Samsung reads these threads since it would be tough to troubleshoot, but there's no doubt an issue exists with general BT compatibility.
Sent from my Galaxy Nexus using xda premium
Anyone have an update on this issue? Does anyone know of a ROM with a different Bluetooth stack than AOKP? I love everything else about AOKP. I have had the same garbled bluetooth audio from stock - 4.03 with franco and faux kernels with the same result. I had similar problems with Cyanogen 7 ROM I was using on my Incredible the week before I bought the Nexus.
Update - I experimented with a couple of additional devices, and the multiple connections problem with my Nexus is limited to A2DP only devices.
I am now using a Garmin BlueTrip with "phone audio" deselected in bluetooth options. As long as the additional bluetooth device is handsfree profile capable, the A2DP functions perfectly, calls are clear, and the device reconnects after a power cycle consistently. I'm glad this appears to be a software issue and not something we will have to live with for the life of the phone. I'm sure a future update will correct this issue.
I'm also having a problem with Bluetooth calls sounding very digitized and/or choppy. It is bad enough that it can be extremely difficult to make out what the caller is saying. A2DP, on the other hand, has performed pretty flawlessly and the device consistently reconnects each time I get in the car (although it can take up to 30 seconds or so).
I'll have to do a little experimenting with some of the settings mentioned in this thread to see if they have any affect.
On a related note, I feel like sometimes calls made/recieved on the handset can sound digitized as well (although not nearly as bad as over bluetooth). Has anyone else experienced this?
My hardware is:
Verizon GNex (4.0.2)
Parrot MKi9000
I came upon a dealbreaker issue with bluetooth. I haven't used bluetooth since long before i rooted my desire and have had this issue since last week when i started using bluetooth again.
My headsets are two Sony Ericsson MW600 and the issue is with cm7.2 based ROMs.
I have tried with Mildwild 5.0 and Cronmod 1.05.
The issue consists of sound not being transferred to and from headset at incoming call. Ringtone plays when call comes in and phone button works on headset. Otherwise media plays satisfyingly but not flawless.
A forum search revealed one previous post with same phone, same issue, cm7.2 base and different headset. No answers to that thread, though.
I'd like to collect some experiences on the matter, to present devs with.
Thanks
Problem solved. Bt in conflict with call recording app. Changed to skvalex's call recording app and all good.
I have a similar issue with MIUI rom. how can i change / disable the recording application?
Try uninstalling or freezing it. Then make a call.
As far as i can see, there is no way to remove the recording option.
The recording is disabled (not recording) by default, and i never enabled it.
I did all my checks on clean install.
Try to find a suspicious service and stop it. Any weird thing might be what's interfering with your bt. Try altering every setting that has anything to do with calls. T n' E
I was unable to find some service responsible.
Buy chance, a friend of mine came with the same phone and asked me to root in and install the same rom i have.
in his case the headset worked with original rom and with the rom i use.
the only difference i noticed was different Radio version.
His is 5.10.05.30
and mine is 5.17.05.23
I also think that his device use OLED display and mine SLCD
So, of course you secretly switched phones with him?
Unfortunately no. So the problem is still there.
Is anyone else having problems with Bluetooth Audio on Kitkat. Mine glitches quite oftemn with my Sony MW600 headphones and also my Bose Soundlink 2 Speaker, I didn't notice it before KitKat? I have also tried the Headset-Bluetooth-Fix_CWM but no change really?
Any solutions out there? anyone else using similar Hardware to mine without problems?
wilx said:
Is anyone else having problems with Bluetooth Audio on Kitkat. Mine glitches quite oftemn with my Sony MW600 headphones and also my Bose Soundlink 2 Speaker, I didn't notice it before KitKat? I have also tried the Headset-Bluetooth-Fix_CWM but no change really?
Any solutions out there? anyone else using similar Hardware to mine without problems?
Click to expand...
Click to collapse
Hi,
I also have all sorts of problems with bluetooth, but I have not been able to find a good fix. To me it seems like issues with 4.4.2 and not specifically the Galaxy Note II. Looking at a LG forum, some guys adviced that switching off WIFI seemed to help. I have tried it out for one of my problems (microphone on BT headset stopping in the middle of a phone call), and it actually seemed to help. You could try it out.
Initially I thought it was issues with a Sony SBH-52 headset, but now that I also have issues (though different) with a Jabra Play, I have come to the conclusion that it must be the phone (software).
I am in contact with my local Samsung support team, and trying to see if they want to take the phone in for service.
Good luck!
spip72 said:
Hi,
I also have all sorts of problems with bluetooth, but I have not been able to find a good fix. To me it seems like issues with 4.4.2 and not specifically the Galaxy Note II. Looking at a LG forum, some guys adviced that switching off WIFI seemed to help. I have tried it out for one of my problems (microphone on BT headset stopping in the middle of a phone call), and it actually seemed to help. You could try it out.
Initially I thought it was issues with a Sony SBH-52 headset, but now that I also have issues (though different) with a Jabra Play, I have come to the conclusion that it must be the phone (software).
I am in contact with my local Samsung support team, and trying to see if they want to take the phone in for service.
Good luck!
Click to expand...
Click to collapse
Thanks, I may try the Wifi next time I use, let me know what Samsung say please
I've been trying to use LineageOS on my OP3 lately, but have always returned to OxygenOS because of one problem: bluetooth audio quality, both input and output. Whenever I make a call, no matter where it is (Skype, Teamspeak, Discord) it always makes a fax machine sound and then proceeds to bomb me with static. I can listen to music without any issues but there is something about calls that are causing problems with bluetooth specifically.
I've tried custom kernels to no avail. The only thing that seems to work is using OxygenOS. What are your thoughts on this? Have you have the same/similar issue? What do you think I can do?
Thanks for your time.