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!
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
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.
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.
Hi, well the Nokia 6.1 is my first Nokia after many, many years on Motorola. It's a good and very beautiful fon. But tow problems annoy me. First thing, the Camera App. Laggy, sometimes, the fon frezze. When In take a Shot from Whatsapp directly, the fon is freezing. Please Update!
Second, so many Problems with Bluetooth-Connect. I'll paire the Nokia with my Garmin Vivoactive 3 - the initial Pair and the intial Synch will works fine. Leave the Connection-Area, the Nokia doesen't reconnect the Watch. I'll test with a Motorola fon and a Amazon Fire Tabelt, the reconncet works very well - it's must be a problem on the Nokia / Oreo Side...
Well, hope your undersand my pooooooor English Greetings from Germany, Andreas
Andreas_SQL said:
Hi, well the Nokia 6.1 is my first Nokia after many, many years on Motorola. It's a good and very beautiful fon. But tow problems annoy me. First thing, the Camera App. Laggy, sometimes, the fon frezze. When In take a Shot from Whatsapp directly, the fon is freezing. Please Update!
Second, so many Problems with Bluetooth-Connect. I'll paire the Nokia with my Garmin Vivoactive 3 - the initial Pair and the intial Synch will works fine. Leave the Connection-Area, the Nokia doesen't reconnect the Watch. I'll test with a Motorola fon and a Amazon Fire Tabelt, the reconncet works very well - it's must be a problem on the Nokia / Oreo Side...
Well, hope your undersand my pooooooor English Greetings from Germany, Andreas
Click to expand...
Click to collapse
Keep in mind that the phone is just released here in Europe. We can't expect them to just have fixed every problem in the universe.
I too have sometimes problems with some minor lag, but I just think we need to be a little more patient for Nokia/Google to release improvements.
Same problems here with Bluetooth connections and overall phone lagginess...
TA-1068 - two different Bluetooth headsets connect flawlessly, but when the phone is in my pocket I experience some connection problems, like losing connection for a moment. If it's out of the pocket and near the headset, connection is ok. Guess some range problems...
I was experiencing the lagging as well, very very noticeable and not good considering previous phone was Moto g2015 and felt just as slow as the Nokia.
So I decided to try something which seems to have fixed all lagging. I disabled the camera app that came with the phone, installed Google camera, and then restarted. Lag is now gone. It really sucks they shipped this phone with a buggy camera app but glad I figured out a fix
Andreas_SQL said:
Second, so many Problems with Bluetooth-Connect. I'll paire the Nokia with my Garmin Vivoactive 3 - the initial Pair and the intial Synch will works fine. Leave the Connection-Area, the Nokia doesen't reconnect the Watch. I'll test with a Motorola fon and a Amazon Fire Tabelt, the reconncet works very well - it's must be a problem on the Nokia / Oreo Side...
Click to expand...
Click to collapse
I'm having very annoying audio problems with the 6.1, with both Bluetooth and the audio jack.
When I connect my phone to a speaker or headset via Bluetooth, the audio is constantly dropping out. Once every 10-20 seconds it sounds like someone turns the sound to 0, pauses, then slowly turns the volume back up again. And this happens with the phone sitting less than 2 feet away from the speaker/headphones. I've tried with two Bluetooth devices (3-4 year old jLab Crasher; brand new Anker headphones) and 2 apps (Amazon Music; Podcast Addict) and all 4 combinations had the constant drop outs. I've tried rebooting the phone. I've used the Bluetooth headset on a different, much older, device and had no issue, so I'm nearly positive it's the phone. Are other people experiencing these frequent drop outs too? Or do I just have a defective Bluetooth radio in my phone?
Normally I don't even use Bluetooth because I prefer the consistency of a plugged in cable. I probably wouldn't have even discovered the Bluetooth problem were it not for the audio jack. It's not as consistent but just as annoying. I'll be listening to Podcast Addict and suddenly the audio will just stop playing through my headphones. I'll look at the app and about half the time the podcast will be paused but the other half it'll still be playing and I'll have to do a weird combination of unplugging and re-plugging the headphones combined with closing and reopening the podcast before it'll play through the headphones again. Again, is anyone else experiencing headphone jack issues?
Similar 3.5mm audio plug problems here also.
Tremelo said:
I'm having very annoying audio problems with the 6.1, with both Bluetooth and the audio jack.
When I connect my phone to a speaker or headset via Bluetooth, the audio is constantly dropping out. Once every 10-20 seconds it sounds like someone turns the sound to 0, pauses, then slowly turns the volume back up again. And this happens with the phone sitting less than 2 feet away from the speaker/headphones. I've tried with two Bluetooth devices (3-4 year old jLab Crasher; brand new Anker headphones) and 2 apps (Amazon Music; Podcast Addict) and all 4 combinations had the constant drop outs. I've tried rebooting the phone. I've used the Bluetooth headset on a different, much older, device and had no issue, so I'm nearly positive it's the phone. Are other people experiencing these frequent drop outs too? Or do I just have a defective Bluetooth radio in my phone?
Normally I don't even use Bluetooth because I prefer the consistency of a plugged in cable. I probably wouldn't have even discovered the Bluetooth problem were it not for the audio jack. It's not as consistent but just as annoying. I'll be listening to Podcast Addict and suddenly the audio will just stop playing through my headphones. I'll look at the app and about half the time the podcast will be paused but the other half it'll still be playing and I'll have to do a weird combination of unplugging and re-plugging the headphones combined with closing and reopening the podcast before it'll play through the headphones again. Again, is anyone else experiencing headphone jack issues?
Click to expand...
Click to collapse
You can start this problem at the Nokia support app. They can help you through chat. Maybe they know the solution for that
I too came from Moto
BrunkBeard said:
Keep in mind that the phone is just released here in Europe. We can't expect them to just have fixed every problem in the universe.
I too have sometimes problems with some minor lag, but I just think we need to be a little more patient for Nokia/Google to release improvements.
Click to expand...
Click to collapse
the camera issues can be remedied by side loading the 7 plus camera apk and with BT try disabling BT "scanning" in the settings. I also noticed an improvement with Wifi by disabling "scanning" as well .
john.r.m said:
and with BT try disabling BT "scanning" in the settings. I also noticed an improvement with Wifi by disabling "scanning" as well .
Click to expand...
Click to collapse
At the risk of jinxing things, I think that fixed it! I had seen something for the Nokia 6 (2017) about disabling BT scanning but I couldn't find it anywhere on my menu so I thought it was specific to that model. Dopey me. Finally found it and switched scanning off and now I've listened over 5 minutes without a single drop out. Thanks!
Edit: Well, that worked for one night. Turned off the Bluetooth and Wifi scanners and was able to listen over Bluetooth for over an hour with just one drop. Then this morning got 5 drops in a minute. Rebooted the phone and got even more. Will contact Nokia support.
Strange. I have obviously switched off the scanning at first set up, but Bluetooth problem is there...
Tremelo said:
At the risk of jinxing things, I think that fixed it! I had seen something for the Nokia 6 (2017) about disabling BT scanning but I couldn't find it anywhere on my menu so I thought it was specific to that model. Dopey me. Finally found it and switched scanning off and now I've listened over 5 minutes without a single drop out. Thanks!
Edit: Well, that worked for one night. Turned off the Bluetooth and Wifi scanners and was able to listen over Bluetooth for over an hour with just one drop. Then this morning got 5 drops in a minute. Rebooted the phone and got even more. Will contact Nokia support.
Click to expand...
Click to collapse
Same here. Tried disabling scanning (after finding it under security of all places!!!) still have dropouts on bluetooth.
divvykev said:
Same here. Tried disabling scanning (after finding it under security of all places!!!) still have dropouts on bluetooth.
Click to expand...
Click to collapse
I used the Nokia support app and this is what transpired:
1) They had me try the Bluetooth in Safe Mode (while holding power button down tap Restart and then a prompt should pop up for Safe Mode; Click that).
2) In Safe Mode listened to 10 minutes of YouTube drop-free
3) Rebooted into Normal Mode and got 3 drops in the first 1 minute.
4) Back to the chat, where Support had me clear the Bluetooth cache (Applications --> Show System Apps (from 3 dots drop down in upper right corner) --> Bluetooth --> Storage --> Clear cache --> Restart) Did not help me. 3 drop outs in first 60 seconds after restart.
5) Next Support had me Reset Network Settings. (Settings --> Network & Internet--> 3 dots in upper right corner --> Reset WiFi, Mobile & Bluetooth)
6) This works!... For now at least. I'll use it and slowly re-add other Bluetooth devices like my car, my Fitbit, etc. If the audio drops suddenly reappear it may give me a clue on what is causing the problem.
Tremelo said:
I used the Nokia support app and this is what transpired:
1) They had me try the Bluetooth in Safe Mode (while holding power button down tap Restart and then a prompt should pop up for Safe Mode; Click that).
2) In Safe Mode listened to 10 minutes of YouTube drop-free
3) Rebooted into Normal Mode and got 3 drops in the first 1 minute.
4) Back to the chat, where Support had me clear the Bluetooth cache (Applications --> Show System Apps (from 3 dots drop down in upper right corner) --> Bluetooth --> Storage --> Clear cache --> Restart) Did not help me. 3 drop outs in first 60 seconds after restart.
5) Next Support had me Reset Network Settings. (Settings --> Network & Internet--> 3 dots in upper right corner --> Reset WiFi, Mobile & Bluetooth)
6) This works!... For now at least. I'll use it and slowly re-add other Bluetooth devices like my car, my Fitbit, etc. If the audio drops suddenly reappear it may give me a clue on what is causing the problem.
Click to expand...
Click to collapse
Thanks for this. Will give it a go and report back. Thanks
I don't remember if I mentioned, but the may update for pixels fixes a similar problem, so in a couple of days it might get fixed for us also.
Anyone else having issues with connecting the 7T to their car and getting audio going out of it? My OG Pixel didn't have a problem, but I have to toggle off/toggle on Bluetooth and then manually tap the car's bluetooth listing to get it to actually 'connect' the audio portion.
Rather annoying, considering I'm only in the car for a few minutes at a time, this either eats into the time entirely, or makes me sit in my car for a couple minutes before even driving to fiddle with the bluetooth settings.
Car has stock headunit, 2015 Evo X. Like I said, original Pixel XL had no issues, but this is annoying. I've tried changing bluetooth versions to no avail. I can see it connecting and dropping the bluetooth connection fairly frequently while staring at it and trying to 'get it going'. But once it connects, it stays there.
My bluetooth headphones (Some knock off cheap Chinese ones for $20) don't seem to have an issue.
My connection to my aftermarket stereo is fine. Just seems a little quieter than my last phone. Connecting is kind of slow too when I start my car but it is automatic.
I don't have any issues with connecting to all 3 cars (2014 Honda Accord, 2009 Pontiac G8 Gt and a 2018 Honda Fit) but I do agree that the volume seems a little lower than my previous phone (Galaxy S8).
Sent from my [device_name] using XDA-Developers Legacy app
Hmm. Weird. Is there anyway I can check for logs to find out what exactly is happening? I haven't rooted, just don't know if it's something I can naturally pull from Android as a whole.
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
My bluetooth is quiet, but its also static-y. I never had any issues with my G6 and now I get static clipping every 10 or so seconds. Its unbearable.
jagadeesh16 said:
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
Click to expand...
Click to collapse
I'm not really having an issue pairing it, but it's just connecting after pairing is the problem.
I have changed the default pin. I can see it popping up and down the car stereo a few times in the bluetooth settings before it just gives up.
As for the other issues, I'm not having a problem at all with audio volume, nor popping/static when it finally does connect.
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Phreak411 said:
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Click to expand...
Click to collapse
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Milkshakes00 said:
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Click to expand...
Click to collapse
LOL that would be my luck
.
My OnePlus 7t connects fine and phone works for calls on 2014 cts. The sound comes out of phone can change song on head unit but I can't get audio to play through car. Anyone else get this?
Yeah music stutters with car player... Only calls work. Music works on headphones etc. I couldn't find solution, did network reset, cleared cache. Nothing works.
Seriously!
I've wasted at least two hours already trying all the recommended steps: from flicking icons on and off to a full phone reset.
Still no connection to my Suzuki S-cross car. Multiple previous phones have connected effortlessly.
Even the $50 temporary five year old borrowed phone could handle it.
Anyone got any other suggestions? Yes, tried the AVRCP setting change from 1.4 to 1.6. That didn't work either...
Barebones system reset from scratch running O2 OS 10.0.6HD65AA
Any suggestions greatly appreciated.
I need to be able to talk and drive!
Reset the car radio and clear all pairing data if you can. Then try again.
autosurgeon said:
Reset the car radio and clear all pairing data if you can. Then try again.
Click to expand...
Click to collapse
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
mikefnz said:
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
Click to expand...
Click to collapse
Yep most have lots of tedious steps that are different model to model and if not followed exactly will cause this problem on occasion..
In my case music starts to be scrambled after 10 minutes or so of listening. When I take the phone (so the watch pops up) or turn on the screen it immediately works fine again, but when being put aside and the screen turns off, the issue starts again ..
Also in the early days of my previous 5t I had the same issues but some fix was delivered together with oxygen os update. And now the same story again
I have a different issue with Bluetooth:
- OP7T connects to car Bluetooth fine
- I can make/answer calls
- Bluetooth media works fine
The problem is with Google Assistant & car audio:
- it was working as intended until the latest update - 10.0.15 - I was pressing the button on the steering wheel the google assistant was answering questions through the car bluetooth, no need to switch to bluetooth media.
- after the latest update, when I press the button on the steering wheel, Google assistant pops on the phone , starts to answer question, but cuts off after 5 seconds. the command still goes through and Assistant still runs, but does not come up on the car audio.
- it looks like the Assistant is not connecting to the car as a hands free, but as to a bluetooth handsets.
Anyone experiencing this?