[Q] bluetooth audio issues - intermittent - Samsung Galaxy Nexus

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

Related

[Q] Sound stuck in earpiece after disconnecting bluetooth headset?

I've used many ROMs (Viper, Bonsai, Nebula, currently ACS Syndicate) and I've had this problem on all of them. I've even ODIN'd back to stock before and it still didn't fix my problem.
After disconnecting my Epic from my Jawbone Icon headset, the sound often gets stuck inside the earpiece. Music, movies, games, ringtones will all play from the earpiece instead of the speaker behind the phone.
Is there some software fix to correct this? Can any of the devs point me in the right direction as to how I might troubleshoot this (maybe at the kernel level)?
Thanks in advance!
This doesn't really go in Development, and I suspect it will be moved soon.
I can tell you, though, that I've experienced similar problems, intermittantly, and here's what I've observed.
If I'm listening to music through bluetooth, before I disconnect, I'll stop the music. Then I'll turn the bluetooth device off. Then I'll turn bluetooth off on the phone. If I do it in that order, I don't seem to get the bug.
If you do still get the bug, rebooting fixes it.
Hope that helps!
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
daddymikey1975 said:
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
Click to expand...
Click to collapse
This stuff has been going on since DK28 and before. I believe Rodderick was looking into fixing it from the kernel side, but I'm not sure how much progress has been made. I know it's not as bad as it was on DK28, but still very annoying. It used to happen to me all the time (audio going through earpiece instead of speaker after disconnecting Bluetooth) when I would turn my car off and it would disconnect the Bluetooth to my car stereo. Now that I have the Samsung Car Dock, I just connect Bluetooth for phone only, and use the audio out on the Car Dock for Navigation and Media.
Moved to Q&A.
i am having a simular issue but mine is that when i connect to bluetooth headset i have to have media playing before i get a call or i will not hear the other person in the call.
it seems to me that ANY bluetooth headset with A2DP is doing this and i have tried 3 diffrent headsets. Jabra Stone, Jawbone Icon, and the Blueant T1.
all 3 of these headsets do this. does anyone have any solution yet?
Even if there isn't a fix, I wish there was an app to reset the sound settings post facto. Anyone know of one?
I just want to add my name to the list of those who are affected by this. Glad it's not just me, though. Hopefully it can be debugged easily.
For the record, a Quickboot Hot Reboot (reboot of Android only, not phone) does NOT solve the issue. Only a full reboot works for me. Seems like it may not be a software issue but something hardware-related.
Sent from my SPH-D700 using Tapatalk
Just want to add this happened to me the first time just now. I'm on rooted EC05. I was scared for a bit that the speaker had blown. Then when I discovered it all coming from the earpiece, I remembered this thread. A reboot did make it go away.
I wonder if it has any relation to the issue I see once in a while since the upgrade where my BT devices need re-pairing and ask for a passcode, when they really shouldn't.
I Also Have This Issue
I have had this exact issue since DI18.
After I hang up a Bluetooth call, I have popping sounds coming out of the earpiece. Turning off Bluetooth doesn't fix it. Turning Bluetooth back on after turning off doesn't fix it. In addition, after this happens, all devices sounds (phone ranging, notifications) all come through the earpiece and *not* the main speaker.
I've had all of the stock ROMs up until EC05 loaded on this Epic and have had the same issue throughout. I am now running midNIGHT ROM, which has cured most problems I’ve had with my device, except this issue.
I was just poking around trying to find some sort of tool or the name of the service(s) that I need to restart to fix this issue.
Same issue for me. Quite annoying as I listen to audible over bluetooth quite a bit, and then pretty much know I have to reboot when I turn bluetooth off.
SRF users have reported Bluetooth issues being cleared vs. stock builds. I can't say exactly why, but it does seem to work.
What are SRF users?
Nope...
Syndicate Rom Frozen...
Well, I'm on SRF 1.1.1 and I've got the same incredebly annoying audio issue.
Please, someone, come up with a fix!

no sound after bluetooth unpairing

Hi, I have been searching and can't seem to find anything on this. My wife's and my epics pair, and work, great with with our car stereos (clarion). but, when we get out of the car, and the phone unpairs, we have no more system sounds. we miss calls and texts because we never hear them. the sounds now only come out the ear piece. Only a reset corrects it and then we hear sounds from specker again. Of coarse until we get in the car, and it all starts over again.
any ideas? I'm stumped.
thanks!
have you tried turning bluetooth off entirely when u leave the car?
also are you using any applications to send media with bluetooth such as BTmono?
I have the same problem -- as does my wife. I'm using a Motorola BT in the car, but it seems to be a problem with any BT connection as she primarily connects to our BT phone connection in the house. I saw this problem mentioned in a couple other threads, but no real solutions other than things like turning off BT on the phone before disconnecting, etc. Frankly, that's a hassle and I never remember to do it. I was hoping the latest version of Syndicate ROM might fix it, but just had it happen again this morning. So, I can confirm it's a problem on both Froyo stock and Syndicate ROMS. At least it seems like rebooting is a bit faster on Syndicate, so that's my solution for now as soon as I realize sounds aren't coming through. Just gotta remember to check before I miss a call!
Sent using Tapatalk.
thanks for the replies. I am not using anything that starts to stream to the car stereo. Music player use to, but I removed it. I did notice today that the specker sound loss only happens if i make/receive a call. Today I drove to store and while in store away from car sound was fine. got back to car, called wife, and then when I was at home sound was gone. I will try to toggle off BT before phone is unpaired. what a pain.
Wouldn't ya know I found a thread about this after I post this.
http://forum.xda-developers.com/showthread.php?t=1029198
This post has worked for me: thanks mattallica76. I had to be in car paired to do this.
http://forum.xda-developers.com/showpost.php?p=13102385&postcount=31
This problem is a bug that exists while using Bluetooth on a device for both ad2p and phone calls. The only workaround (until Sammy or one of our great devs comes up with a fix) is to use the BT device for one or the other. This will prevent the audio from being routed to the phones earpiece after BT disconnects. To do this, go into the phones BT settings. Then long press the device that you are having trouble with. Next uncheck "Media Audio" or "Phone Audio", depending on which purpose you want for the device.

Bluetooth A2DP Audio Stream Issues

Hey Fellas,
Coming from a Note 2, I instantly loved the form factor of this phone. Built well
I'm having some issues connecting my bluetooth and streaming music on it.
My receiver is a Tunelink bluetoothwireless and the programs i'm using on it is mainly spotify. I did try beyondcast, but still having the same issue.
When streaming music or any sort of audio, I'm getting very spotty audio output. I would hear a slight static, then it'll cut out and resume at a different location. It seems to me that there is somekind of lag that goes into the system.
Calls made through my car does not have these issues. I've tested the tunelink and it seems to work fine. Anyone else having this issue?
I'm not understanding where its coming from. A possible fix would be greatly appreciated
Thanks
There seem to be issues with the bluetooth on this thing. Another forum member and myself both have problems staying connected to some of our bluetooth devices. I can connect to my car without any problems, but I can't connect to my bluetooth enabled housephone properly. If I try to make or receive a call, it's instant disconnection.
I'd lump your problem in with what's been described as faulty software.
my.ads0 said:
There seem to be issues with the bluetooth on this thing. Another forum member and myself both have problems staying connected to some of our bluetooth devices. I can connect to my car without any problems, but I can't connect to my bluetooth enabled housephone properly. If I try to make or receive a call, it's instant disconnection.
I'd lump your problem in with what's been described as faulty software.
Click to expand...
Click to collapse
I use Jaybird Bluetooth earphones at the gym. I have had zero problems with bluetooth, I can keep connection at about 30 feet. Just
my lil bit of info.
mrjasenr said:
I use Jaybird Bluetooth earphones at the gym. I have had zero problems with bluetooth, I can keep connection at about 30 feet. Just
my lil bit of info.
Click to expand...
Click to collapse
Yep. And my car will stay connected for over 2 hrs, through phone calls and hangups; never an issue. Then when connecting to my home phone, it's disconnect-mania. Most people don't seem to have problems, but some, like myself, certainly do.
And the reason I blame it on the LGOG is because my old phone (LGOS) always had a solid connection to the home phone. Only thing that changed is my cell.
I have no problems streaming, from a motorokr s305, a nokia bh-505, and a JVC unit in the car. I do get somewhat of a poor connection with the motorokr s305, though. I just figured it was the age of the headset itself.
I do not have issues with my LG stereo Bluetooth, and with my Kenwood head unit, my only problem seems to be auto-connecting. It also has some skips, which has happened on all my phones since I got the head unit. Need to updates its firmware and see if that helps with any issues.
Sent from my LG-LS970 using xda app-developers app

Potential issue with 802.11n networks causing Bluetooth audio dropouts?

Has anyone else had issues with Bluetooth audio stutter/dropping out during music playback?
Main issue is while driving and pixel xl is playing (offline) music to car stereo via Bluetooth, in areas with open wifi , the music stutters.
I currently have an open case with google regarding this.
I carried some of my own troubleshooting as follows :
I have tested connecting to my Bluetooth JAM speaker at home and toggling wifi where the signal is strong.
While disconnecting and being joined to my 802.11AC network, no issues.
While being connected to my 802.11N network however the audio DOES have dropouts.
With wifi off, 4G on - No issues
This is while playing offline music so the internet connection is not required to play the music.
Tried with Spotify and google play music
The fact that the 802.11n network seems to be what causes the issue matches the issues while driving in my car, listening to music via Bluetooth to car stereo.
I think while driving the dropouts/stuttering audio are caused as the phone tries to connect to the many open 802.11n networks around when driving down streets etc.
I don't get any issues when driving on motorways, away from any networks.
Neither my galaxy s7 edge or LG G4 exhibit this issue with the same setup.
Does anyone else experience this?
I found a Reddit thread mentioning the same issue: https://www.reddit.com/r/GooglePixel/comments/5e3nio/pixel_xl_bluetooth_skipping/
this is super interesting... I was having the same problems and so I turned off the WiFi while listening over BT in my car stereo. with WiFi on I would probably get about 20 interruptions in a 30 minute drive. this was reduced to one with WiFi off. it makes sense since Bluetooth and WiFi operate at similar wavelengths but I've never had this issue on any previous phone. it's really shi++y that we have problems like this and then crackling phone speakers on such a high end and expensive device. I'm really disappointed in google
diabl0w said:
this is super interesting... I was having the same problems and so I turned off the WiFi while listening over BT in my car stereo. with WiFi on I would probably get about 20 interruptions in a 30 minute drive. this was reduced to one with WiFi off. it makes sense since Bluetooth and WiFi operate at similar wavelengths but I've never had this issue on any previous phone. it's really shi++y that we have problems like this and then crackling phone speakers on such a high end and expensive device. I'm really disappointed in google
Click to expand...
Click to collapse
So far Google have asked me to provide debug reports, which I have.
I have also factory reset and get the same issue.
I seemed to get more dropouts after the new Google play services installed but not sure if that is the cause yet as it coincided with the wi-fi being idle but connected.
With wi-fi connected and the phone busy restoring all my apps, it didn't seem to dropout hardly.
I have also had drop out issue during playback. Mine stutters no matter what. Wi-Fi on and off I get stutters. I started experiencing this a few days back. At first I thought it might have been viper FX but after turning off the app I still got the stutters. It is coming to be very annoying as I listen to music all the time. I'm running on 7.1.2 stock, rooted.
I finally got a reply from google regarding my case on this and they advised this is fixed in an upcoming update due in the "next few weeks".
I installed 7.1.2 (NOT beta) from the OTA image and sure enough it now appears to be fixed! Happy days!
I got 7.1..2 OTA this morning and it has not fixed my issue. If I turn my BT headphones off and wait 30 mins and turn them back on the stuttering is there. At least all I have to do is turn BT off/on (while leaving the headphones on) and no more stuttering (at least for as long as I played music). So no love for me I guess
aspexil said:
I got 7.1..2 OTA this morning and it has not fixed my issue. If I turn my BT headphones off and wait 30 mins and turn them back on the stuttering is there. At least all I have to do is turn BT off/on (while leaving the headphones on) and no more stuttering (at least for as long as I played music). So no love for me I guess
Click to expand...
Click to collapse
My issue was 100% directly related to 802.11n wifi networks though, doesn't sound like yours is as this would only happen when it would try to join 802.11n wifi. Turn wifi off and it never happened for me.
I gave them detailed information and debug logs which proved what caused the fault and looks like they have fixed it.

Question Pixel 6 pro Bluetooth issue...ice crashing

Been having problems with the blue tooth crashing my car stereo during a call... After a few minutes it completely crashes the head unit.
Phone has been changed and problem persists..
Ice is fine with p4,p4a,and p3 phones. Toyota touch ice.
Safe mode doesn't make any difference..
Now I may have found the issue...
I was talking on the phone thru Bluetooth on using the ice.
I wasn't moving in the car and the Bluetooth didn't crash the ice...
So I suspect the issue is on the call side and how the phone is dealing with phone signal and changing phone transmitters when driving which is affecting the Bluetooth side.
I will add streamed music via Bluetooth is fine when driving.
Anyone else having a similar issue ?
Any of the XDA god's got any thoughts..
Google help have suggested I change the phone a 3rd time....
Tia paul
I have not had this issue yet. I do use wired Android Auto (in my Subaru) all the time, which I believe still uses the Bluetooth for the calls as normal - however, I'm not certain I've been on calls long enough while driving to necessarily trigger the issue.
Might take someone's experience with using it with a Toyota setup similar to yours to report back more useful feedback, since different car manufacturers are notorious for having different Bluetooth experiences.

Categories

Resources