Related
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!
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.
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
My issue today is that my bluetooth will not pair properly and remember its configurations. My initial pairing on my phone with my car's flexsmart X3 works perfect, however when I turn off my bluetooth on the phone or turn off my car and turn it back on the phone will still see the flexsmart and it will say it is paired but I get no sound. Upon further investigating I find that in the options setting that neither the call nor music tick box is checked. If I try to tick them it will think for a few seconds and then gray out and do nothing again.
I never had a problem with my note 2 or my temp replacement evo 3d remembering these settings. All I would do with those phones was pair it once and then any time I hopped in the car I would just turn onm,y phone's bluetooth and go. Now with my note 4 I have to unpair and repair the devices each and every time which is a huge pain.
I have read a little bit that this is due to samsung note 4 using a newer bluetooth standard than its predecessors. Is there anyway to circumvent this issue by maybe rolling back the bluetooth drivers or something? I even thought about creating a tasker profile to help with this but still I would have to physically press the search button on the flexsmart eachtime.
Any and all suggestions would be great. Also right now I am on rooted stock 5.0.1
PS: I will try and post some photos to help when I get the chance to get to my car.
I've been start for a solution to this since the phone came out as well. I have the same Bluetooth issues with my phone in my car. Nothing more annoying than having to turn Bluetooth on and off for 10-15 minutes of your drive before you can use the damn thing. Oh wait, more annoying would be when it's been working for a solid 45 minutes or so and then suddenly, with no warning, the Bluetooth connection ends for no reason and your cars stereo comes on instead of what you were streaming only the volume on the cars radio is far louder and it scares the ever living crap out of you
flyhighx said:
I've been start for a solution to this since the phone came out as well. I have the same Bluetooth issues with my phone in my car. Nothing more annoying than having to turn Bluetooth on and off for 10-15 minutes of your drive before you can use the damn thing. Oh wait, more annoying would be when it's been working for a solid 45 minutes or so and then suddenly, with no warning, the Bluetooth connection ends for no reason and your cars stereo comes on instead of what you were streaming only the volume on the cars radio is far louder and it scares the ever living crap out of you
Click to expand...
Click to collapse
Odd....I dont seem to have that issue. Once I have initially paired the bluetooth it will stay connected without any interruptions. Also pairing for me is really fast and only takes a minute or so. My problem is that instead of my phone remembering the current device settings that it is paired with, it will forget to associate it with calls and data after I turn the bluetooth off and then later back on even though the phone will still remember it is paired with the car bluetooth.
First world problems I know but it gets a tad annoying having to unpair and repair my phone each and everytime I hop in my car to go somewhere if I want to listen to my music.
In the car I don't get a lot of skipping. But when connected to my BT speakers audio does skip a lot and starts playing in ffw then disconnects completely. It's driving me nuts. I've tried all the usual trouble shooting also. No help. Wtf Samsung/Google
Hi all,
I have a Tune2Air Bluetooth adapter in my car which works great with my Nexus 9 and my partner's iPhone. But when I'm connected to it with my G4, the Blueooth connection drops out almost exactly every 12 minutes (+/- 1 minute). After 30 seconds or so the phone reconnects but it's annoying as hell, especially when the dropout occurs when Google Maps is giving me a crucial navigation instruction. My phone is an international H815, totally stock, running build 20D of Marshmallow.
Here's what I've tried/observed:
The phone stays connected without any problems to my Bose Bluetooth speakers at home.
I have made sure that all power saving modes are turned off. I have added Bluetooth to the Ignore Optimizations list in case MM's Doze mode is causing this.
I noticed that when on long drives in the country the phone seems to stay connected to the Tune2Air without the usual dropout. This made me wonder if it could be an interaction to do with the cell radio that is causing the dropout. I tried just sitting in my driveway (in case it was cell-tower handoff) but the dropout still occurs. I have tried disabling mobile data and WiFi while driving but the dropout still occurs.
My mobile provider supports Fast Dormancy and I usually have this enabled. I wondered if maybe this is causing the problem (because of some difference between the city and country cell towers) so I tried disabling it, but the problem persists.
I looked in the log using logcat but couldn't see anything indicating why the connection is dropping. I tried enabling Bluetooth logging from the Developer Menu but unfortunately this doesn't seem to work.
I'd really like to solve this problem but I'm running out of ideas. Can anyone suggest anything else that I could try? Are there any other Bluetooth or mobile network timers of this approximate duration that could be causing the problem? Or any other settings in the service menu that I could try?
Thanks,
james
You can try Flashing the 20e version, much more stable than D
I don't see an update to 20e, either OTA or using LG Bridge. Reading the forums, the consensus seems to be that 20e does not differ significantly from 20d. I think I'll stick with 20d for the time being as I can't bear the thought of doing another factory reset right now.
sladflob said:
I don't see an update to 20e, either OTA or using LG Bridge. Reading the forums, the consensus seems to be that 20e does not differ significantly from 20d. I think I'll stick with 20d for the time being as I can't bear the thought of doing another factory reset right now.
Click to expand...
Click to collapse
then downgrade to a previous version of MM
Hi, This is a bit of a wild stab in the dark but with the seeming regularity it could be a service / polling issue. Have you checked the location based profiles - Perhaps the "turn off Bluetooth when I'm away from home" option is set and this is happening every 12 minutes? Like I said, bit of a wild stab in the dark/ suggestion but might be worth a check. You could also check it whilst sitting in your driveway and see if it happens....
monkeydogger said:
Hi, This is a bit of a wild stab in the dark but with the seeming regularity it could be a service / polling issue. Have you checked the location based profiles - Perhaps the "turn off Bluetooth when I'm away from home" option is set and this is happening every 12 minutes? Like I said, bit of a wild stab in the dark/ suggestion but might be worth a check. You could also check it whilst sitting in your driveway and see if it happens....
Click to expand...
Click to collapse
Ooh, you could be onto something here. I'm going to try disabling "Bluetooth scanning" setting under the Scanning menu on the location screen and see what happens. Another possible culprit is Google Location History so I can try disabling that. As a last ditch effort I will try switching my Location Mode from High Accuracy to Device Sensors Only and see if that helps. I'll report back once I can get a chunk of time in the car.
Thanks!
So I tried all of the things I mentioned previously, rebooted, and it was still doing it - disconnecting every 12-13 minutes.
BUT after some more experiments last week the problem seems to have "fixed itself". Here's what I did...
I was wondering if it wasn't an app that was interfering and causing the dropout so I decided to boot the phone into Safe Mode and see if it helped. Unfortunately it exhibited the same behaviour... Google Play Music played for 12 minutes and then dropped out. So thinking that was pointless I rebooted back to normal mode. My phone then connected to the car stereo but was in this strange mode where audio was still coming out of the speaker rather than being sent across Bluetooth. So I deleted the phone pairing and re-paired and since then, whenever I've gotten in the car, the phone has stayed connected to the car stereo without dropping. Note that this isn't the first time I've deleted and redone the pairing... I'd tried that several times to try and fix the problem. The only new ingredient was going into Safe Mode. Not sure if this cleared something some state in the Bluetooth settings but I'm not complaining.
On the other hand, this is also fairly unsatisfying as it's not clear what "fixed it", and should it happen again I don't have a great degree of confidence that I'll be able to fix it again. Still, it's a step in the right direction and I'm going to enjoy it while it lasts.
So I think I've finally fixed this once and for all. Thought I'd share here in case it's useful to someone one day.
The problem started happening again after I accidentally deleted the pairing and had to re-pair it. Not sure why but I thought to tap the little cog next to the Tune2Air entry in the Bluetooth Devices list. I was surprised to see that under PROFILES both Call Audio and Media Audio were selected (the Tune2Air device I am connecting just supports Media Audio and doesn't do phone calls). So I unticked the Call Audio, reconnected the device, and everthing's been fine since.
I'm not sure whether the device is advertising that it supports Call Audio or whether the G4 is just assuming that it does. Actually the G4 connects just fine to my Bose soundlink (and just shows the Media Audio profile) so I'm think there's something funny with the BT implementation of the Tune2Air device.
Nevertheless, it seems odd that the phone should drop the whole BT connection after 12-13 minutes if it can't connect to call audio. Maybe someone more familiar with the Bluetooth stack can tell me if this is acceptable behaviour or if the G4 is doing something weird.
sladflob said:
So I think I've finally fixed this once and for all. Thought I'd share here in case it's useful to someone one day.
The problem started happening again after I accidentally deleted the pairing and had to re-pair it. Not sure why but I thought to tap the little cog next to the Tune2Air entry in the Bluetooth Devices list. I was surprised to see that under PROFILES both Call Audio and Media Audio were selected (the Tune2Air device I am connecting just supports Media Audio and doesn't do phone calls). So I unticked the Call Audio, reconnected the device, and everthing's been fine since.
I'm not sure whether the device is advertising that it supports Call Audio or whether the G4 is just assuming that it does. Actually the G4 connects just fine to my Bose soundlink (and just shows the Media Audio profile) so I'm think there's something funny with the BT implementation of the Tune2Air device.
Nevertheless, it seems odd that the phone should drop the whole BT connection after 12-13 minutes if it can't connect to call audio. Maybe someone more familiar with the Bluetooth stack can tell me if this is acceptable behaviour or if the G4 is doing something weird.
Click to expand...
Click to collapse
Just wanted to give a huge thankyou to you from the future, sladflob. Doubt I'd ever have thought to disable call audio for pairing to my bodged Bovee bluetooth adapter, and this has solved my constant dropout and reconnects.
Happy days!