Related
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 I bought my Smartwatch 2 a few weeks ago (imported it from the UK) and it's great, the only problem is that it interferes with bluetooth music streaming and bluetooth call quality. I have a 2012 Chevrolet with bluetooth for calls and for media streaming, and I have not had any issues with streaming content over bluetooth until I purchased the Smartwatch. I also have an LG G2 on Verizon, and I thought that might be causing the issue, so I isolated the true cause; when I turn off the watch while playing music, the quality instantly improves. Also when I make or receive any calls in my car the quality is so tremendously bad that I can not understand a word of what the other person is saying. If I switch back to the normal handset via the in call menu on my phone, the call quality improves again.
Am I the only one out there with issues like this? And If not, has anyone found a way around this issue or know of what should be done?
(I know this isn't a Q&A forum, but I was not able to locate a section for Q&A on the smartwatch)
Here no problem with the smartwatch 2, htc one and parrot bluetooth car kit. Maybe your phone needs custom kernel or rom for optimised bluetooth emissions.
Envoyé depuis mon ASUS Transformer Pad TF700T avec Tapatalk 4
For me it's the same watch, car, headphones, any mix works without problems.
Sent from my GT-N7100 using xda app-developers app
Tonio78370 said:
For me it's the same watch, car, headphones, any mix works without problems.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Sometimes my phone doesn't connect anymore to my car Bluetooth, untill I switch off my watch! When I then switch my watch back on it does not connect to the phone anymore.
This behaviour is intermittent so difficult to troubleshoot. What seems to help is to reboot my phone, so maybe it is phone related (HTC One X+).
I only have problems when I get out of reach BT wise. Mostly they reconnected but when they don't I have to unpair, reboot both and pair from start. Luckily it doesn't happen too often
Sent from my GT-N7100 using xda app-developers app
turnturn1225 said:
So I bought my Smartwatch 2 a few weeks ago (imported it from the UK) and it's great, the only problem is that it interferes with bluetooth music streaming and bluetooth call quality. I have a 2012 Chevrolet with bluetooth for calls and for media streaming, and I have not had any issues with streaming content over bluetooth until I purchased the Smartwatch. I also have an LG G2 on Verizon, and I thought that might be causing the issue, so I isolated the true cause; when I turn off the watch while playing music, the quality instantly improves. Also when I make or receive any calls in my car the quality is so tremendously bad that I can not understand a word of what the other person is saying. If I switch back to the normal handset via the in call menu on my phone, the call quality improves again.
Am I the only one out there with issues like this? And If not, has anyone found a way around this issue or know of what should be done?
(I know this isn't a Q&A forum, but I was not able to locate a section for Q&A on the smartwatch)
Click to expand...
Click to collapse
I have exactly the same problem! I have the note 3 on att and a 2012 Audi Q5. I noticed it was only an issue when I receive a call...and shutting off the watch doesn't help.
I realize that this is because as long as I am on the call, the phone is sending a signal to the watch (keeping the number on the watch face). Even if I turn off the watch, the phone is still sending. The caller's voice is totally garbled. If I turn off the bluetooth, audio quality to the phone is fine. This is a killer for the watch! I can't use it in the car! If it only rang but didn't keep the info on the screen, it would be fine. I wonder if there is an app out there that will buzz the phone when the call comes in but then stop transmitting to the watch.
I guess I could turn off the phone handling app.. but that would defeat the purpose of the watch.
Does ANYONE have an idea how to fix this? I am at my wits' end!
radman2020 said:
Even if I turn off the watch, the phone is still sending.
Click to expand...
Click to collapse
If you mean that you have switched the SW2 completely off, in this case sending is clearly not possible, bluetooth is an handshaked protocol....
themissionimpossible said:
If you mean that you have switched the SW2 completely off, in this case sending is clearly not possible, bluetooth is an handshaked protocol....
Click to expand...
Click to collapse
I have switched it off.. Eventually the distortion clears. Maybe the interference continues a bit because the car - phone bluetooth connection was somehow altered by the watch transmission?
I don't know how these things work but the distortion of the voice only happens when the watch is connected!
I am amenable to any suggestions.
radman2020 said:
the distortion of the voice only happens when the watch is connected!
Click to expand...
Click to collapse
Probably this is due to concurrent BT connections limitations or reciprocal radio interferences, or to a BT stack overload in one of those devices (likely the phone that has to keep 2 connections going at the same time).
themissionimpossible said:
Probably this is due to concurrent BT connections limitations or reciprocal radio interferences, or to a BT stack overload in one of those devices (likely the phone that has to keep 2 connections going at the same time).
Click to expand...
Click to collapse
so I figured that... but how can sony put out a watch they expect people to use that destroys the voice connection? Is there any workaround?
radman2020 said:
but how can sony put out a watch they expect people to use that destroys the voice connection? Is there any workaround?
Click to expand...
Click to collapse
If the source of the problem should lie in the phone BT, the Sony SW2 couldn't be blamed.
themissionimpossible said:
If the source of the problem should lie in the phone BT, the Sony SW2 couldn't be blamed.
Click to expand...
Click to collapse
I'm not blaming anyone. I just want it to work. Sony's big advantage over the Gear is that it is supposedly compatible with any android phone. It seems to have an issue here.
radman2020 said:
It seems to have an issue here.
Click to expand...
Click to collapse
Of course I can't agree, but it doesn't matter..
themissionimpossible said:
Of course I can't agree, but it doesn't matter..
Click to expand...
Click to collapse
not sure what you are saying. I have an issue that has something to do with the watch, phone and car interface. I am looking to the people on this board for suggestions. You telling me that I shouldn't blame the watch and rolling your eyes is not helpful.
I am happy to not blame anyone and just have this work. I love the concept. I paid a lot of money for it... and I am hoping to find a workaround.
radman2020 said:
and I am hoping to find a workaround.
Click to expand...
Click to collapse
My personal advise is that probably the first (and only) workaround to try could be to change or modify the phone that apparently has some problems with double BT connections.
radman2020 said:
not sure what you are saying. I have an issue that has something to do with the watch, phone and car interface. I am looking to the people on this board for suggestions. You telling me that I shouldn't blame the watch and rolling your eyes is not helpful.
I am happy to not blame anyone and just have this work. I love the concept. I paid a lot of money for it... and I am hoping to find a workaround.
Click to expand...
Click to collapse
I stream, and take calls in my truck, with no issue in sound quality. How can Sony be blamed... are the supposed to account for every app combination, Bluetooth drivers, roms ect? Now its possible u have a defect.... if it was a detrimental design flaw I think a high percentage of us would experience the same, n that's just not the case....
canecbr600 said:
I stream, and take calls in my truck, with no issue in sound quality. How can Sony be blamed... are the supposed to account for every app combination, Bluetooth drivers, roms ect? Now its possible u have a defect.... if it was a detrimental design flaw I think a high percentage of us would experience the same, n that's just not the case....
Click to expand...
Click to collapse
I totally agree, but for somebody it's apparently too hard to believe...
I have 3 Bluetooth audio devices: car kit, Bluetooth speaker and Bluetooth stereo headphones.
The car kit and speaker work fine when the watch is connected but the headphones (Blueant X5) stutter while playing music and behave badly when trying to talk on a call. If I disable Bluetooth on the watch, it works fine.
I wonder if it's related to the Bluetooth version of the respective devices. Both the car kit and speaker are much newer than the old headphones.
Maybe your issue is similar. Do you have access to another phone you could test the watch against?
mckenzis said:
I wonder if it's related to the Bluetooth version of the respective devices. Both the car kit and speaker are much newer than the old headphones.
Click to expand...
Click to collapse
I suspect that if a device (for ex. a phone or a headset) hasn't at least Bluetooth version "3.0 + HS" (released in 2009) it's likely to have problems keeping 2 BT connections correctly working at the same time.
themissionimpossible said:
I suspect that if a device (for ex. a phone or a headset) hasn't at least Bluetooth version "3.0 + HS" (released in 2009) it's likely to have problems keeping 2 BT connections correctly working at the same time.
Click to expand...
Click to collapse
The car is a 2011. The watch and phone are state of the art....
I installed call handling pro which allows me to limit the number of seconds the watch displays info on an incoming call. This secondarily limits the time this phone-watch communication disrupts the voice bluetooth communication between phone and car. It has helped. The downside is that, when not in the car, I lose some of the benefit of the watch. I'm ok with the tradeoff. It is a workaround.
Original thread modified after i finally figured out what the problem was, original text can be found in the quote below this post.
Edit:
Ok so this is a very old annoying HARDWARE glitch.
For some reason android detects regular headphones as a special headset sometimes and this causes many annoying problems such as a nonexistant contact point causing random headset special functions to trigger. (skip music, open google voice, random volume changes, even make random calls)
Software solutions to this problem either don't work on latest Android versions or cause numerous problems and resource overhead.
Solution:
Keep plugging and unplugging headphones slowly, quickly, forcefully, etc etc until you see the headphones icon appear instead of a headset icon. Once this happens the problem is GONE until you unplug headphones and plug them back in again and don't get lucky.
It will presumably not happen with most headphones or else manufacturers would have been made to care by millions of pissed off customers. As it is they don't appear to give a damn to the plight of some of us.
Dinger558 said:
In the last 2 days for some reason Google Now keeps being randomly triggered. Sometimes for a whole minute without end.
When the device is locked I keep hearing that woman's voice of how I need to unlock the device to use Google Now.
it's getting incredibly annoying.
I tried killing it, it just restarts itself. In settings it's already set to "Off" and it still pops up. Uninstalling it just resets it to factory and solves nothing.
Please someone tell me how to get rid of the damn thing.
I'm having exactly this problem on my G3:
android.stackexchange.com/questions/62417/google-search-appears-out-of-nowhere
android.stackexchange.com/questions/66135/google-now-launches-when-headphones-are-plugged-in
Click to expand...
Click to collapse
If you're rooted install greenify and xposed. Greenify will tell you what is triggering Google now to start. And you need xposed for that added feature in greenify
Sent from my LG-D850 using XDA Premium 4 mobile app
3085
Ok so this is a very old annoying HARDWARE glitch.
For some reason android detects regular headphones as a special headset sometimes and this causes many annoying problems such as a nonexistant contact point causing random headset special functions to trigger. (skip music, open google voice, random volume changes, even make random calls)
Software solutions to this problem either don't work on latest Android versions or cause numerous problems and resource overhead.
Solution:
Keep plugging and unplugging headphones slowly, quickly, forcefully, etc etc until you see the headphones icon appear instead of a headset icon. Once this happens the problem is GONE until you unplug headphones and plug them back in again and don't get lucky.
It will presumably not happen with most headphones or else manufacturers would have been made to care by millions of pissed off customers. As it is they don't appear to give a damn to the plight of some of us.
Dinger558 said:
Ok so this is a very old annoying HARDWARE glitch.
...
Click to expand...
Click to collapse
First of all, thank you so much! Your trick helped
But are you sure that this is a Hardware Problem?... If I just need to plug my headphones in and out, doesnt that imply that this is more of a software issue?
Kalaidos said:
First of all, thank you so much! Your trick helped
But are you sure that this is a Hardware Problem?... If I just need to plug my headphones in and out, doesnt that imply that this is more of a software issue?
Click to expand...
Click to collapse
It could be a software but likely both at fault.
Android OS appears to mistake regular headphones for a headset, this does not happen consistently making a hardware aspect to this problem certain.
A very simple fix would be to include in a future android the option to disable headsets entirely or allow manual switching by tapping the icon.
But they probably wouldn't do that, after all, why care about a minority?
Wait is that what the little microphone icon is? I've had that a few times, was wondering what the heck it was.
Dinger558 said:
It could be a software but likely both at fault.
Android OS appears to mistake regular headphones for a headset...
Click to expand...
Click to collapse
I cant convince myself that this is a hardware issue, the G3 is a flagship and they just can't use faulty hardware that affects everyone
Kalaidos said:
I cant convince myself that this is a hardware issue, the G3 is a flagship and they just can't use faulty hardware that affects everyone
Click to expand...
Click to collapse
It's a very old issue. You can find mention of it in smartphones going back years.
I can't be sure but I think the headphone jack gets a faulty contact with a non-existent third contact point that only headsets use. Thereby convincing the OS that it's a headset and not headphones,
This doesn't appear to happen to all headphones.
Dinger558 said:
Ok so this is a very old annoying HARDWARE glitch.
For some reason android detects regular headphones as a special headset sometimes and this causes many annoying problems such as a nonexistant contact point causing random headset special functions to trigger. (skip music, open google voice, random volume changes, even make random calls)
Software solutions to this problem either don't work on latest Android versions or cause numerous problems and resource overhead.
Solution:
Keep plugging and unplugging headphones slowly, quickly, forcefully, etc etc until you see the headphones icon appear instead of a headset icon. Once this happens the problem is GONE until you unplug headphones and plug them back in again and don't get lucky.
It will presumably not happen with most headphones or else manufacturers would have been made to care by millions of pissed off customers. As it is they don't appear to give a damn to the plight of some of us.
Click to expand...
Click to collapse
My issue is a little different. Whenever I insert headphones (have tried 3 now). The only thing I've not yet tried was unrooting. I had Viper installed as well as Xposed and a few modules all of which I've since removed. All with no improvement. Anyone ever seen this or find a post I may have missed?
This is crazy, one day I just put my headphones that I always use in and they just worked, and every time I put them in they register as normal!
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!
So I had been on the beta version since it was released and participated a few times in the thread here: https://forum.xda-developers.com/pixel-xl/how-to/android-o-beta-issues-t3609335 and others were having the same issue.
The issue is no song/artist information being displayed on my touchscreen stereo, and I cannot use the stereo to pause/skip to the next track (I have to do it through my phone). Ive tried a local audio player, Google Music, and Pandora all to no avail. The deck is a Pioneer double-din AVH-P8400BH.
In my daily car, my phone bluetooth name appears and I can change song ect thru the deck. It is not a touchscreen and it probably 10 years old.
Ive gone into the bluetooth settings and have tried changing the AVRCP from 1.4 to 1.6 (neither work), and audio codec from default to enable optional (neither worked).
Anything else I should try out?
TIA
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
marcjc said:
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
Click to expand...
Click to collapse
Ill throw in my comments, thanks for the link!
mjc2251 said:
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
Click to expand...
Click to collapse
Ill have to give this a shot!
mine has awful streaming. It has so many skips...snags...audio blanks...whatever term you want to call it....its not "uninterrupted".
I was hoping google IMPROVED Bluetooth. I don't understand why they have this struggle to be honest. Its 2017....Bluetooth is not new technology.
Maybe they should stop expanding their department to provide data to the government to spy on private citizens using smart devices, and they would use those resources to fix bluetooth
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
speedingcheetah said:
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
Click to expand...
Click to collapse
Pioneer uses a cheaper bluetooth and never updates the firmware of the chips to fully support the available Bluetooth profiles even when they are developing their units and new profile updates are available. I have had a very long and annoying history with them to the point where I was in direct contact with their build team after all my complaining. That was back in 2012. Never used another of their products again. :good:
I have the same issue on my Chevy Colorado 2017. Everything works fine on Spotify on my Huawei Mate 9, and iPhone 7. It also worked fine on 7.1.2. Spotify works and music comes through but no info is displayed. I unpaired both things with no success. Frustraring.
I tried unpairing mine as well, no luck either
stupidchicken03 said:
I tried unpairing mine as well, no luck either
Click to expand...
Click to collapse
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
pcriz said:
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
Click to expand...
Click to collapse
I have not. Ill give it a shot today.
No idea if this problem is related or not but might be worth a check if you have time. First time I put Oreo on my phone it was fine. Then I screwed something up and just ADB flashed the image again. Everything was fine until I tried bluetooth a few days later. It wouldn't connect until ticking that media box many times. Then I flashed the image again and it worked fine again.
So I just got the 8.0 OTA (not on beta). I see in the dev options that it shows what BT codec it is using.
I have noticed that only the option "Bluetooth AVRCP Version:" is the only value that changin it does it stick. The other setting appear to be on auto and revert to auto depending on what device u pair supports.
My first test on my Kenwood KDC-BT762HD it paired fine and it said it was using AptX. Streamed for a few min fine. Then after I got back in the car and it auto paired, music started skipping every several seconds. I turned radio off then on to repair it and it started streaming fine again....but was using SBC according to Dev options.
When I changed AVRCP version to 1.6.....it connects and uses AptX fine. However, the radio display no longer displays the BT media metadata(title/artist), but the controls on the radio still work. I change to AVRCP ver 1.4 and that restores metadata, but then it uses SBC again. (using ver 1.5 results in SBC and no metadata).
I don't really care about the song info not being displayed on my radio....but definitely seems to be something fishy with BT in this new update.
EDIT Update: so now I am noticing it auto re-connecting and using SBC all the time now. WOnt use aptX unless i delete the device and re-pair it. then it works for a few reconnects, but then drops to sbc cagin.
Thanks for posting, I won't be updating. The Bluetooth has never been right and now seems to have regressed.
Sent from my SM-T280 using Tapatalk
i think i'm having slightly fewer drop outs with oreo than with nougat. my moto x pure on marshmallow was really bad.
FZ1Darren said:
i think i'm having slightly fewer drop outs with oreo than with nougat..
Click to expand...
Click to collapse
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
fletch33 said:
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
Click to expand...
Click to collapse
If you switch to a rom that uses the CAF based bluetooth (all lineageos based ones should, crDroid does for sure as that is what I use) implementation this won't happen. Still haven't been able to track down exactly why, but for now I'm sticking with CAF based ROMs to avoid this.
Do any of you guys having this issue have an Android wear watch? I've had heaps of issues with Bluetooth streaming being all "jittery" and just skipping since the update. However, I found this is basically completely fixed when I turn my android wear (LG urbane) off, or at least the Bluetooth on it.
Tried all the developer options for BT but hasn't made a difference. At the moment, my solution is turning off BT on my watch when I'm listening to music. Bit crap but it works.
I have factory reset the watch and cleared BT cache on pixel.
Any other ideas?
Is anyone else still having problems with Bluetooth on Oreo? I was hoping the official 8.1 release would help me, but I'm seeing no change. I have a Kenwood BT952HD, and experience issues similar to what the OP describes. Audio is plays fine, no unreasonable stuttering. But I get no song info, and can't skip tracks. Also, the pairing isn't as automatic. Every time I turn on the car, I have to wake the phone up, and wait for the pairing to complete, which takes longer than usual.
I've tried playing with the AVRCP settings, along with clearing registrations at both ends and repairing, with no luck. Is anyone else still seeing similar issues?
8.1 working fine with my Kenwood BT762HD. I use PowerAmp v2 alpha build 704 app.