Related
Hello guys,
I just got a Sony bluetooth headset and I am trying to use it with my HTC TYTN II. At first I paired the phone and the headset and I was able to listen to music and talk through the headset, all perfect. When I was listening to music, the bluetooth icon on my phone represented a music note and a headset over it.
When I turn the headset off once and then on again, it connects automatically with the phone but in some other mode. The bluetooth icon now represents the bluetooth sign with a headset over it. Now when I listen to some music, it comes from the speaker of the phone, not from the bluetooth headset. Talking through it is not a problem.
If I pair the phone and the headset again, it works just fine (showing again the music note) but once I turn the headset off and on again, I lose the music mode.
Does anyone know how to fix that? Thanks in advance.
I fixed the issue by installing AutoA2DP (found in this forum).
I've had a similar problem on my Tilt. I originally posted the following on the ROM thread. Since then, I have found that the AutoA2DP has not fixed the problem. I still have this issue about 70% of the time, and sometimes I can't get the bluetooth to work at all, not even after a soft reset. Sometimes it seems as if the bluetooth has no power, the phone can't communicate with the headset except when within a few inches of one another. Then it magically seems to resolve itself. Anyway here's my original post from the ROM thread.
The other day I installed an app on my phone called Schaps Network Plugin, which allows you to map network drives to the phone the same way you can do with a desktop. It allows me to access the home network directly via my wifi. It was something I needed and it seemed to work great, for a day. The next day my bluetooth headset would not connect. Long story only slightly shorter, it seems the problem was with the headset connecting via A2DP and doing so automatically. This always worked just fine in the past. Suddenly it wouldn't work. I tried a ton of things including a "fresh" install of everything and formatting my memory card to start with nothing on it. I flashed the original rom and then flashed this rom. I did hard resets each time. Did this twice. Even tried the bluetooth in the oem rom to see if I still got the problem. I did, and it is still with me. I can manually get the headset to connect via A2DP using the bluetooth settings, though even then it may take reconnecting several times to get it to work. However, when I turn the headset off and then on again, the A2DP does not reconnect, just the hands free. But the sound is not routed through the phone's speaker either, at that point. In fact you often get no sound at all, nothing via the headset or the speaker. OTOH, if you activate Voice Command, the headset does work while Voice command is running. After it shuts off, you are back to no sound. It seems as if the hands free works fine, but the audio gets partly routed to A2DP but does not connect to the headset. If I reset the phone, the headset connects correctly and efverything works until I turn the headset off again. Also if I pair the headset again, everything works correctly until I turn the headset off. Though pairing is not as trouble free as it used to be either. Sometimes it will not pair up wihtout repeated attempts. I did find this program, AutoA2DP which has patched the problem. It detects when a paired bluetooth device connects, and forces a connection via A2DP as well. But I never had this issue in the past, and my wife's phone still has no problem. I am not sure the Schaps Network plugin had anything to do with it, other than the timing. Seems odd to me that the bluetooth stack would suddenly develop issues that persist even after two fresh flashes of the rom. Any ideas, suggesitons, etc.? This is really bugging me, and although the patch seems to be working, the phone is still not acting "right." In the past, and on my wife's phone, if a bluetooth headset is turned on, it automatically connects, and all sounds, including the system sounds, are routed through the headset. Now, sometimes they are, and sometimes they aren't.
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
So by a weird turn of events, I've gone from an HTC Rezound back to a Gnex I am having two issues with Bluetooth in my car (2012 Subaru Impreza).
First, I can pair the device without a problem, but any time I leave and come back to my car, I have to go back into the Bluetooth settings and reconnect the device every time. This never happened with the Rezound, as the Bluetooth would automatically reconnect and start playing whatever I was listening to.
The second issue is the sound quality. When I first start playing music over Bluetooth, the bass is stripped out and everything sounds tinny. I actually found a fix, which is to plug in an AUX cable for a few seconds and then remove it so the music goes back to Bluetooth. After that, the sound quality is perfect. Again, never had this issue with the Rezound.
I will note that I previously had a Gnex before the Rezound, and that never had the reconnection issue or sound problems.
Anyone have any idea what may be happening here?
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
I've been having issues with bad static/noise in voice calls when connected to my car's Bluetooth. Music streaming over Bluetooth is fine, however. Does anyone else experience this issue. I used to have an S6 paired to my car and it was perfect for both voice calls and music.
My audio for like music is fine but tried making a car handsfree the other day for the first time and couldn't hear the other person who said they didn't hear me either. I had to click on the dialer app to switch out it to phone speaker and then back to Bluetooth then it worked.
It's been like this since I first got the phone...it's almost unusable for phone calls in the car. I wonder if this is a software or hardware defect and if it will be corrected in a future update. I don't want to have to RMA this phone if I don't have to.
I'll try your workaround, acheney...thanks for the tip
Pixel XL connects via Bluetooth to both of my cars without problems. And call audio is fine both ways.
I have had zero issues with music streaming or phone calls. 2014 Infiniti q50
I'm having this issue too. Music and video play fine, but when someone calls i can hardly understand what they are saying due the static. Was hoping the update would fix the issue. I'm not sure what to do at this point.
Same issue. Audio over BT is fine. GPS navigation over audio was playing up, but now appears to be ok. The moment I call someone (or they call me) the call is all garbled and I have to switch to speakerphone.
My Bluetooth earpiece however works fine. Not sure if headunit issue or phone bt stack.
i have this same issue. so annoying. so far there's no solution?
eddyz said:
i have this same issue. so annoying. so far there's no solution?
Click to expand...
Click to collapse
None that i have found. Flashed AptX codec and still have same issue. Don't think it is hardware because the phone works fine when paired with other Bluetooth items like speakers, headphones, my watch, and other car stereos. Just doesn't like my factory pioneer unit in my Tc for some reason.
Audio issues for me have always been carrier issues.
Redialing the number usually fixed the call
I ended up finding if I mounted my phone far away from the head unit (near the door/drivers window for example) and tilted the phone in a weird way, the calls were fine.
I don't quite understand it, but seems like there is interference from the head unit when using BT to make calls, which for some reason isn't a problem when you play music (or GPS navigation is on).
Either the Pixel needs better shielding or there's something borked with the Bluetooth chipset.
I would like to use wireless headphones, but the in-channel headphones with a large battery and with good sound have not yet been invented
Yes!
I've only made a few calls over my cars bluetooth, but yesterday I ran into this:
Conversation was fine for several minutes, and then every word the other person said came through as static. When they paused between words or stopped talking, it was quiet. But as soon as they said a word again, it was static.
I toggled the call back to handset and it was fine. So I switched back to bluetooth, and it was fine for a minute or two, and then it became static voice again. I switched back and forth again and it was back to normal voice and remained that way.