Related
Hi,
I have a bluetooth phone in my car, when I first connected the HTC Desire HD up, it had no problems, it paired and everything looked fine... around 10 minutes later, I noticed the bluetooth had simply disconnected from the car but was still running on the phone. I tried to reconnect it up to the car but it wouldn't, I then turned it off, and turned it back on.. it struggled to come back on, but after a few attempts it did come on and the car connected again...
About 5 minutes later the same thing happened again. At this point my phone started to really slow down, I looked in watchtower and the bluetooth was at the top of the list, soon as I turned off bluetooth the phone was responding fine again.
I have since tried connecting to the car multiple more times and have contacted HTC about it, but it seems to disconnect at random times.
Has anyone else experienced similar problems? I heard of similar problems with the original desire so wondering whether it could be something similar.
Kev
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
I also noticed this the last few days with my Bury CC9056 carkit. I have my DHD since October 18th, and up till last friday it connected fine. Since then it connects to the carkit, but within a few seconds the connection is lost...
Sent from my Desire HD using XDA App
Me too. My connection to my Jabra car kit is stable once connected... but trying to get it connected in the first place is a total headache.
Never had this problem with my Desire, so why HTC should change the Bluetooth function in the HD is a mystery.
Sent from my Desire HD using XDA App
tbh i'm glad its not just me thats experiencing problems meaning it could be a software problem rather than something with my handset in particular.
I have been in touch with HTC about this, and I have just sent them the link to this thread so they can see i'm not the only one with this issue, so if anyone else has this issue it may be good to try and keep it all in here.
quentin_rayner said:
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
Click to expand...
Click to collapse
Mines also the audi in car system - do you find that you struggle to turn the bluetooth off and on again once it disconnects or that your phone becomes a little laggy until you turn the bluetooth off?
Yeah - I use the bluetooth widget on the home screen and once it disconnects, it will either take ages to turn off and on again, or it takes 2 presses to turn off.
I have just purchased a Plantronics 230 headset as need bluetooth for my job and it works perfectly - it's no where near the quality of the in car one though.
Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
I would of thought though, that as long as the phone does connect to the phone system in the car that it is compatible.
I have had 30mins once out of it before it disconnected and it was absolutely perfect in that time, including the phone book etc.
I do believe its something to do with the bluetooth on the phone as its a bit strange the way it struggles to turn on again once it fails.
quentin_rayner said:
.. Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
Click to expand...
Click to collapse
That really hacks me off. I mean, BT is a standard. The only reason Audi can give for not supporting a phone that supports at least the same level of BT as them is that they (Audi) do not adhere to the BT standard.
Now, we all know in real life that cars and phones have problems/bugs/whatever BUT unless they can show that there is indeed a *bug* with the phone then the onus should be on Audi to support it.
Dave
Just for the record, it is not just Audi. With me it is together with the Bury carkit, where it first worked fine. (and also works with all other phones...)
Leon
Sent from my Desire HD using XDA App
I can confirm the issues with the BT. I have a parrot Mki9000 in my car and the first time when i tried to connect the DHD , the phone stopped to respond and I was forced to restart it. Since then the phone is paired with the car kit and works fine in a2dp mode for playing music, but when i try to make a call it simply not work. Yo better discribe the problem I will give an example:
The phone i properly connected and playing music, then it's ringing, but the ring sound is coming from the phone speaker not from the car. Then If i answer the call the sound comes from the phone (it shows that there is connection to the car kit). I've tried to press the speaker icon and there is a list with output devices (the phone, loudspeaker, and my car kit) I've tried to select the car kit several times , but there was no success. When I close the phone the music start to play from my car's BT system , so I think there is a problem with the handsfree function/protocol only a2dp works great , and I didn't have any issues with it. Also I've tried file transfer via BT, it works fine two.
Mitsubish Outlander carkit
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
ZoidAndroid said:
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I have a Pioneer head unit with BT in the car and that seems to work OK, not withstanding the fact that the HU has BT issues of its own (hardware fix needed - I'll get a new unit rather than fix it as I want one with A2DP) but once connected it works fine.
I have a Plantronics headset that seems to exhibit the same problems as your Jabra. At least if I use the phone to answer the call the sound comes through the phone. Also, if I have been using the headset the next call I make goes through the phone speaker which is a pain.
I'm wondering if HTC are routing the sound through the device that's actually *controlling* the call? So even if a headset is paired and connected to the phone, if you use the phone to make the call, as most people would, then it assumes that that's where the sound should get routed. If so, doh .....!!!!!
Just to add, if the sound does get routed to the phone you can use the 'choose speaker' option on the screen to route it to the headset but you shouldn't have to do this.
Anyone reported these issues to HTC and got a meaningful response?
Dave
I did send an email to HTC. Their wonderfull answer was about: "is your phone mentionned in the compatabilylist of the carkit, if not drop the problem there"...
I am still waiting for a response from HTC.
Mines got to a point now where I cant even make a call, it connects to the car, I go through phone book (on car) choose person to call, press call.. it tries for a couple of seconds then comes up disconnected, about 10 seconds later the phone disconnects from the car and will nto reconnect.
My phone then lags like mad until I turn bluetooth off which according to watch tower is taking up about 80% of the CPU.
any updates/solution to all these problems ?
I need it to work with MW600 before buying Desire HD
Last contact I had with HTC is they told me it had been escalted to the software team, so i'm guessing next time a software update comes out it could come about in that, but at the minute no still not fixed.
ZoidAndroid said:
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I've always thought that that's the way it is on all BT headset phones, it makes sense, if the incoming call was for my girlfriend, she can answer from the phone itself, and it automatically routes this through the phones speaker, and if it was answered from the headset, then it routes to the headset.. makes sense to me, I think it's quite good that it does that!
Do any of you have the process com.android.phone crashing when making a phone call through BT?
Ditto my mitsubishi outlander factory bt system. Seemed to work fine first time but then disconnected during first call and would not reconnect for days. Then after connecting not all functions would work ...no incoming call alert on car system, no dialling from car etc. I know the car system is fine as all functions work perfectly with my old nokia xpress music.
Sent from my Desire HD using XDA App
I trust that all of you bother to report this to HTC, at least once per instance ?
- otherwise I don't know when they'll fix this..
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!
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
I wish I had an answer; just got my Galaxy Nexus yesterday; it won't pair with any of my bluetooth(s) -- they were all working fine in my Droid so I know how to pair. Any suggestions? Help!! Thanks
After further investigation, it seems it's just outgoing connections that don't work on mine. I can transfer files from other devices to the GN fine, just can't transfer from the GN to any other devices. Haven't tried connecting to a headset or anything like that as I don't have one.
I asked an acquaintance who also owns a GN to test it out on theirs and they experienced exactly the same thing - everything works ok except for outgoing connections/transfers.
I'm wondering if its a software bug if that's the case. If it were hardware related you'd have thought the whole bluetooth thing would be broken.
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Bt phonebook pairing
I'm having BT issues as well with my G-Nex on Verizon. Will connect/pair with my car, works for making/receiving phone call audio, but will not synch the contact list. Thus, cannot use voice dial in my car (Nissan).
Have searched all over the internet, no real answers. Tried to disable the existing bluetooth PBAPservice as suggested somewhere else - no dice, and it just restarts itself anyway. I've seen some suggestion about rooting the phone and replacing the PBAPservice which may be my next step. Hate to root a phone this new when I may end up returning it if I can't make this work ... sorta a deal breaker for me.
Anyone have any suggestions? Could my phone just be defective? Seems like there are a number of BT issues around, but I can't find anything "official" acknowledging the issue(s) ..
Thanks ...
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Having problems with Bluetooth as well. I have a BlueFusion unit installed in my car. Worked perfectly fine with my Droid X. Every time I got in the car, it just connected and calls and music both played over the stereo fine. Got my Galaxy Nexus paired and it worked great. However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
DoubleVision81 said:
...Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
Okay, I don't feel so bad now. Ouch.
---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------
cam30era said:
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Click to expand...
Click to collapse
Does A2DP work properly? And what sort of bluetooth device are you pairing with?
Same here, sending files works, receiving doesn't. Pairing with my bt headset also works fine....
Sent from my Galaxy Nexus using XDA App
mattots said:
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
Click to expand...
Click to collapse
I had this problem when I fist boot the Nexus and after the first boot of the update to 4.0.1. Reboot the phone, re-pairing the devices and everything is fine since then.
Sent from my GT-P7300
I can't even get my Nexus to pair with my car (Kufatec FISCON unit for Volkswagen). Just straight up error "unable to pair" when I try it. :/
And I have a problem as well. I did get it to pair with my PC but I can't send any files from my PC to Nexus (it works fine with Desire).
I have two Nexus (one is my wife's) and both car have Blackberry Bluetooth Gateways in them. In both cases I am seeing the same issue as the OP, the bluetooth will not connect automatically. However if I manually power on the bluetooth on the phone when the gateway is in connecting mode than they will connect. I never had a problem like this with previous phones.
Is there a official way to inform Samsung of this issue?
I'm also having problems with bluetooth on my Galaxy Nexus. I wanted to transfer files via bluetooth from my old Incredible 2 to my new Galaxy Nexus and it just wouldn't work.
Edit: A reboot appears to have fixed the problem.
DoubleVision81 said:
However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
I have this same issue exactly - and had this issue after a System Update on my Droid Incredible for a few weeks before I ended up buying the Galaxy Nexus. I had hoped the new phone wouldn't have this issue. Anyways, it also seems to happen when I take a phone call.
Scenario: I'm listening to music over bluetooth to my bluetooth audio enabled headunit in my car. I receive a phone call, and toggle the bluetooth off so I can take the call privately over my phone's earpiece. When the call is finished, I toggle the bluetooth back on and the phone will connect - however the music is playing, but no audio comes through the phone nor the speakers of my car.
I started having this -exact- scenario issue when System Updates started rolling out for Droid Incredible, and they added the options for "Phone Audio" and "Media Audio" under the bluetooth options. Before these System Updates, my Droid Incredible had worked perfectly with bluetooth audio in my car.
Bluetooth Phone and Stereo
SnarfvsMaximvs said:
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Click to expand...
Click to collapse
I am having similar problems with both my car's BT phone and BT audio.The phone through my car gets terrible static until I stop and start Bluetooth again, which is dangerous on the highway.
I hope it can be fixed with a little software update.
I have the same problem with new nexus galaxy, pairs well with car bluetooth audio, can hear a confirmation beep on car speakers but no luck in the phone. It just stays on paired but not connected. It doesnt allow to remove pairing and redo it untill rebooting the device.
I'm also having issues with the bluetooth audio in my car. I pair okay with my Sony Xplod head unit, then when I turn off the car and reconnect, the GN starts playing music through the internal speaker instead of the car speakers.
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
AdamUpNorth said:
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
Click to expand...
Click to collapse
Yes. I just got mine last night...ran some errands today. Paired fine in my car, can make and receive calls through the car's audio system, but no sound. I'm running 4.02. Tried this with my BT headphones and the same thing happens.
The airplane mode trick works, however. Thanks!
Hopefully this will get fixed rather quickly!
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