Has anyone else had issues with Bluetooth audio stutter/dropping out during music playback?
Main issue is while driving and pixel xl is playing (offline) music to car stereo via Bluetooth, in areas with open wifi , the music stutters.
I currently have an open case with google regarding this.
I carried some of my own troubleshooting as follows :
I have tested connecting to my Bluetooth JAM speaker at home and toggling wifi where the signal is strong.
While disconnecting and being joined to my 802.11AC network, no issues.
While being connected to my 802.11N network however the audio DOES have dropouts.
With wifi off, 4G on - No issues
This is while playing offline music so the internet connection is not required to play the music.
Tried with Spotify and google play music
The fact that the 802.11n network seems to be what causes the issue matches the issues while driving in my car, listening to music via Bluetooth to car stereo.
I think while driving the dropouts/stuttering audio are caused as the phone tries to connect to the many open 802.11n networks around when driving down streets etc.
I don't get any issues when driving on motorways, away from any networks.
Neither my galaxy s7 edge or LG G4 exhibit this issue with the same setup.
Does anyone else experience this?
I found a Reddit thread mentioning the same issue: https://www.reddit.com/r/GooglePixel/comments/5e3nio/pixel_xl_bluetooth_skipping/
this is super interesting... I was having the same problems and so I turned off the WiFi while listening over BT in my car stereo. with WiFi on I would probably get about 20 interruptions in a 30 minute drive. this was reduced to one with WiFi off. it makes sense since Bluetooth and WiFi operate at similar wavelengths but I've never had this issue on any previous phone. it's really shi++y that we have problems like this and then crackling phone speakers on such a high end and expensive device. I'm really disappointed in google
diabl0w said:
this is super interesting... I was having the same problems and so I turned off the WiFi while listening over BT in my car stereo. with WiFi on I would probably get about 20 interruptions in a 30 minute drive. this was reduced to one with WiFi off. it makes sense since Bluetooth and WiFi operate at similar wavelengths but I've never had this issue on any previous phone. it's really shi++y that we have problems like this and then crackling phone speakers on such a high end and expensive device. I'm really disappointed in google
Click to expand...
Click to collapse
So far Google have asked me to provide debug reports, which I have.
I have also factory reset and get the same issue.
I seemed to get more dropouts after the new Google play services installed but not sure if that is the cause yet as it coincided with the wi-fi being idle but connected.
With wi-fi connected and the phone busy restoring all my apps, it didn't seem to dropout hardly.
I have also had drop out issue during playback. Mine stutters no matter what. Wi-Fi on and off I get stutters. I started experiencing this a few days back. At first I thought it might have been viper FX but after turning off the app I still got the stutters. It is coming to be very annoying as I listen to music all the time. I'm running on 7.1.2 stock, rooted.
I finally got a reply from google regarding my case on this and they advised this is fixed in an upcoming update due in the "next few weeks".
I installed 7.1.2 (NOT beta) from the OTA image and sure enough it now appears to be fixed! Happy days!
I got 7.1..2 OTA this morning and it has not fixed my issue. If I turn my BT headphones off and wait 30 mins and turn them back on the stuttering is there. At least all I have to do is turn BT off/on (while leaving the headphones on) and no more stuttering (at least for as long as I played music). So no love for me I guess
aspexil said:
I got 7.1..2 OTA this morning and it has not fixed my issue. If I turn my BT headphones off and wait 30 mins and turn them back on the stuttering is there. At least all I have to do is turn BT off/on (while leaving the headphones on) and no more stuttering (at least for as long as I played music). So no love for me I guess
Click to expand...
Click to collapse
My issue was 100% directly related to 802.11n wifi networks though, doesn't sound like yours is as this would only happen when it would try to join 802.11n wifi. Turn wifi off and it never happened for me.
I gave them detailed information and debug logs which proved what caused the fault and looks like they have fixed it.
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
I've been having a weird experience with my Moto 360. I listen to music from Spotify or Google Play Music in my car (Audi) over Bluetooth every day and have done for months with every phone I've had - Nexus 4, Nexus 5 and most recently, my OnePlus One. Everything has always worked flawlessly - audio quality is good, no disconnections and generally perfect.
Now my Moto 360 is connected to my phone as well, it seems to occasionally "interfere" with the Bluetooth audio stream periodically. It's more pronounced when I lift my wrist and turn the watch to activate the display, but sometimes happens without this going on too. The audio starts to skip and jump as though there's not enough bandwidth to both communicate with the watch and the car. It usually lasts around 10-15 seconds and is very frustrating. If I put the watch in airplane mode, the issue goes away, but it will restart when I take it out of airplane mode. I've had some success with disabling and re-enabling Bluetooth on the phone to force reconnections, although there is still occasionally some interference after this too. It doesn't always happen and is usually worse in the evenings than the mornings - almost feels like after the watch has been connected to the phone for a long time, there isn't room for anything else to use the connection.
Has anyone else experienced issues like this? I run nightly builds on my phone (which are otherwise absolutely flawless) and I've tried several different ones without any improvement. The 360 is on the latest OTA software update but had connectivity issues before that too. It's definitely the watch causing the issues as when it's nowhere nearby or is disconnected from the phone, there are no audio quality problems at all.
webvictim said:
I've been having a weird experience with my Moto 360. I listen to music from Spotify or Google Play Music in my car (Audi) over Bluetooth every day and have done for months with every phone I've had - Nexus 4, Nexus 5 and most recently, my OnePlus One. Everything has always worked flawlessly - audio quality is good, no disconnections and generally perfect.
Now my Moto 360 is connected to my phone as well, it seems to occasionally "interfere" with the Bluetooth audio stream periodically. It's more pronounced when I lift my wrist and turn the watch to activate the display, but sometimes happens without this going on too. The audio starts to skip and jump as though there's not enough bandwidth to both communicate with the watch and the car. It usually lasts around 10-15 seconds and is very frustrating. If I put the watch in airplane mode, the issue goes away, but it will restart when I take it out of airplane mode. I've had some success with disabling and re-enabling Bluetooth on the phone to force reconnections, although there is still occasionally some interference after this too. It doesn't always happen and is usually worse in the evenings than the mornings - almost feels like after the watch has been connected to the phone for a long time, there isn't room for anything else to use the connection.
Has anyone else experienced issues like this? I run nightly builds on my phone (which are otherwise absolutely flawless) and I've tried several different ones without any improvement. The 360 is on the latest OTA software update but had connectivity issues before that too. It's definitely the watch causing the issues as when it's nowhere nearby or is disconnected from the phone, there are no audio quality problems at all.
Click to expand...
Click to collapse
My plantronics legend is multipoint paired to my HTC one max and a blackberry. Since getting the 360 I have noticed a crackle in the audio. If I reboot my phone I can usually clear it up. Seems like interference isn't causing Bluetooth channel hops like it should.
I am having the exact same issue. Moto 360 connected to LG G2 (Verizon) running Cloudy G3 ROM and every time I play a song to any Bluetooth device it stutters for the first 10-15 seconds of the song, then plays fine until the next song. It resolved for a bit when I re flashed, but started again a few days later. Can't correlate it to any changes or installs. Totally stumped.
This is a huge problem! I can't even use Google maps in the car if I have my moto 360 and phone connected to Bluetooth at the same time. I could not use moto voice or Google now as well. Even when my phone rings in the car my speaker crackles.
All this is cured as soon as I leave the car. It's obviously a big Bluetooth issue and moto needs to know about this! This thread should be pinned!
I am having the same issues with my Moto 360 and OnePlus One. It is very annoying and I'm seriously considering returning the Moto 360 now!
It's every phone that does this not just the OnePlus one. Also in my moto x. It's clearly linked to the moto 360 and it's Bluetooth issue.
Yes, that looks like the case and so I'm returning the Moto 360 before the 30 day return window expires!
I was experiencing this issue as well in my Q5. But after experimenting, I don't think it's actually interference with the Bluetooth radios. The issue only seems to happen when my phone is asleep and when it is happening, all I have to do is wake up the phone and it stops. I wonder if maybe the governor is causing the CPU to sleep too quickly after the kernel gets a wakelock from the Bluetooth stack. Oddly enough, the issue hasn't happened since I updated to KGW42R on the watch.
If you're still experiencing the issue, maybe try changing your CPU governor to performance (if supported by your kernel/ROM) just to see if you get any improvement.
Yep, experiencing this as well with my HTC M8 + Moto 360 on my Volvo.
I had intermittent stuttering issues with the M8 in the past, but now I could never get a flawless playback whenever I have the Moto 360 connected. Big problem..any solutions yet anyone?
Motorola probably has no idea about this problem. Can/does anyone know how to make them aware of this horrible bug?
stu5797 said:
Motorola probably has no idea about this problem. Can/does anyone know how to make them aware of this horrible bug?
Click to expand...
Click to collapse
I just contacted them about it in Live Chat and the person was completely dumbfounded, then cut me off. Going to try to call them tonight. Oddly, I didn't have the issue with My Nexus 4, but it did surface with my new Moto X, which was around the time of the most recent update to the 360.
I have the moto x and the OnePlus one and this darn issue happens on both phones. So frustrating!
Bad audio issues
I have the same issue with my new Moto X, Moto 360 while using my car audio. I do have a fitbit as well so that means three bluetooth devices while trying to stream audio. Even music that is downloaded on my phone has the same issues.
I have the exact same issue with my Moto X 2014! Extremely frustrating.
Solution..connect your phone via 3.5mm jack (wire/cable) to your vehicle audio, to free up the frequency/frequencies..
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Yeah, unfortunately that's not a solution at all. My car doesn't have a 3.5mm input for me to use and besides, the whole point of Bluetooth audio is not to have any wires.
I agree that the issue seems to be present on either downloaded or streamed music. Sometimes disabling and re-enabling Bluetooth on the phone will help, sometimes it won't. Often I won't have any trouble when driving to work in the morning but will have constant interruptions going home in the evening. Sometimes it's the other way round. There isn't really a consistent pattern.
I tried to call Motorola support yesterday but they were closed.
I didn't have any problem with bluetooth at first, but now my car audio skips at random times and then goes back to normal. Feels like the '90s all over again. Additionally, sometimes my calls through the car will sound like I am underwater. I disabled the HTC bluetooth low energy profiles on my phone in hopes this will resolve it. Will test and report back later. Hopefully it won't have any impact on my phone's battery life.
Newest version of Android Wear came to my Moto 360 yesterday, and I was in high hopes that it would resolve this issue, at least to some degree. With the bluetooth updates it seemed like they made some serious changes, but the issue has gotten even worse. I can barely get any audio now, the skips are no longer short, and are now just 1-2 seconds of silence. I reported this issue numerous times to Motorola, and they refuse to respond to me. This is a huge letdown, and had I not passed my 30 days, I would return the device.
Official response from Motorola forums.
forums. motorola. com/posts/167e5af808?page=2
"We've spent some time looking at this. The team feels it's a matter of overloading the BT capacity of the phone. There is simply a limit to the traffic it can handle, and the extra link is slowing it down. Not a very satisfactory answer, but this seems to me a case where the simplest explanation is probably the right one."
Anyone know if the new Bluetooth LE changes in Android 5.0 would possibly improve this?
webvictim said:
Has anyone else experienced issues like this? I run nightly builds on my phone (which are otherwise absolutely flawless) and I've tried several different ones without any improvement. The 360 is on the latest OTA software update but had connectivity issues before that too. It's definitely the watch causing the issues as when it's nowhere nearby or is disconnected from the phone, there are no audio quality problems at all.
Click to expand...
Click to collapse
Oh my god.
It's exactly the same issue I have!
I turn on my 360 in the morning and connect to my alpine car audio, 90% of the time no problems.
I leave the office at 5pm, the watch has been connected the whole day, I notice lags in audio playback like whenever a new song begins for the first 5-10 seconds.
When my 360 stays on over night I get this issue in the morning too.
Putting the 360 in airplane mode solves it - but turning airplane mode off brings the problem back.
Restarting car audio, moto 360 and oneplus one while driving is a pain but works...
I also noticed that the lags occur more often when I turn my wrist (just like you said).
When navigating to the settings menu on the 360 while playing music it totally messes up the sound until I turn the display off again.
My setup:
Alpine CDE-178BT
Moto 360 4.4W2
OnePlus One 4.4.4 (Update 38R) Stock Kernel / Franco Kernel - same **** on both kernels
A bit of google told me that the problem can occur with every bluetooth LE device (like fitbit wristbands)
I hope this will be fixed but don't really know what the problem is... Bluetooth stack in ROM? Moto 360?
Hi Guys,
I've been using my unit for quite a while now. Everything works fine except for Bluetooth. I'm using the latest Condu's ROM on a KLD device with up to date MCU. When I connect my iPhone and use it to stream songs the sound gets choppy as if it had a RAM outage. However I checked (and purged all processes) the RAM and it's fine, not even near full. What's interesting is that all other apps that are played locally (Spotify, Pandora, TuneIn) works fine. I already formated multiple times without success. Also tried Malaysk ROM once and the problem persisted. Is there any known solution for this?
Thanks,
Turn off the phone's WiFi, it is a known problem for all bluetooth audio devices when streaming close to WiFi as they share the same channel as WiFi.
Hi timk,
I tried with all WiFi off (my phone, the head unit, both combinations) and the problem persistis. I haven't had this problem in any other bluetooth audio device. Any other suggestion?
Thanks,
I have the same problem, electronical fizz in the sound, and it starts after a while not immediately.
I'm having similar issues from my Note 5. Even my Gear S2 seems to have weak connection as I get disconnected on the other side of the room.
Even with iPhones the bluetooth connection was horrible, popping like crazy and drove me crazy after 10 minutes.
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!
Like I get disconnects from my car. The phone audio won't come through ones I turn on media audio. It's a mess. Anyone experiencing this? Is there a way to clear the Bluetooth cache? I googled and see how to do it on earlier versions but not pie. Tia
Sent from my Pixel 3 XL using Tapatalk
@DrUnkeN_TiGeR My car only supports telephone/contacts, not audio. I had to buy a cheap BT audio receiver and now everything works fine. What is the year/make/model of your car? Was it working with your previous phone and which one was that? You can find network reset in settings to reset bt.
I had an issues popup the last few days of playing music via BT to a BT Speaker.. after I stopped playing music, the volume rocker/popup would randomly show up, I was still connected to the BT Speaker but not playing anything and quit out of Spotify. I turned off BT and it stopped. Also, when I was playing music connected to BT, I randomly quit playing through the speaker. I had to turn off BT and turn it back on to resume play. Just sharing my issues.
Before the December update, all was perfect with one exception, the audio information would not show in my car while using certain music apps. After the December patch, audio now cuts out every once in a while. Like the pixel 2xl did the entire year I had it... Google seems to have issues making their bluetooth work like it should. Hopefully the January patch will fix things (not holding my breath).
Glad to hear not just me thanks guys
Sent from my Pixel 3 XL using Tapatalk
DrUnkeN_TiGeR said:
Like I get disconnects from my car. The phone audio won't come through ones I turn on media audio. It's a mess. Anyone experiencing this? Is there a way to clear the Bluetooth cache? I googled and see how to do it on earlier versions but not pie. Tia
Click to expand...
Click to collapse
This exact thing has happened to me. I think it has only occurred with Play Music but I don't know if that's the cause. Didn't occur before December update.
More details. It seems to happen when I've advanced a song but that could be coincidence. I get no audio. I have a Subaru and I can see on the even display BT disconnected. Then it starts to cycle between connected and disconnected until I just turn on BT on my phone. Even though it briefly reconnects it doesn't actually function. No audio