CM13 Bluetooth Issues
I'm running the latest nightly of Cyanogenmod 13 on my HTC One M8 Verizon phone, ran a clean install wiping all partitions and updating to the latest firmware. For some reason my Bluetooth turns off when the screen is locked. Any help?
There has been many issues with Bluetooth. I had constant disconnecting while streaming. The only option is to look at the change log for each nightly & look for Bluetooth fixes.
I'm also running the latest nightlies of CM13 on my verizon m8. I have clean flashed each version (probably 10 days in January). So far I have noticed the following issues:
I see Bluetooth audio stuttering - where the streaming connection to car (ford sync), headset, or speaker (bose) gets quite choppy. 3 seconds of silence, burst of audio, then more silence.
It appears to me to happen when connections change - If i drive away from my house and lose wifi or if I am underground on the subway and gain cell service for a moment, or I drop cell service in an area of sporadic coverage. In every case a reboot solves the problem until the next "connection change". When I am static, or in constant coverage, I have no issues streaming for hours.
Version CM 13.0-20160201-nightly-m8
Baseband 1.12.20.1211
Kernel 3.4.0-gf52bf8c
Related
I pair my phone with my car (VW Golf 6) and can listen to music. After a short while, maybe 2-10 minutes, it randomly loses the connection. The problem first started with CarbonRom, so i decided to flash stock rom with ElementalX Kernel and the problem persists, even with Franco's Kernel the connection drops. 1-2 weeks ago, i haven't had this issue and was on stock + franco.
The logcat seems very overfilled with bluetooth message, but I can't understand a thing or what it causes the problems.
Thank you!
Mine does that also not sure why though, but I'm on Mahdi Rom.
I've done a factory reset of my car's radio and it seems to be stable. I will keep an eye on that and report after some days..
Does it give you the bluetooth share has stopped error message?
Nope, the connection just drops and the car thinks they are still connected. I have to restart my car to reconnect again.
The issue seems to be fixed by resetting my car's radio to factory defaults. Since then I had no issues.
BT problems are often related to the BT devices itself. You should sometimes try it with other phones i.e.
It seems that i.e. moto 360 is good to go with the n5 but bad with lg g3. reviewers said lost connection 20x/day.
I've noticed that ever since I upgraded to 38R I keep getting disconnected from my bluetooth car stereo. When it disconnects the Bluetooth icon on the OPO goes grey. It looks like the Bluetooth module is crashing and then getting reset by the OS. I just got done with a 30 minute drive and it happened 3 times. Has anybody else noticed anything funky with the Bluetooth stack?
I've also had the phone itself hard crash several times. Not sure if 38R is ready for prime time.
I'm not running anything custom, just pure 38r on a rooted/twrp device. No exposed or other mods.
I updated manually last night and this morning on the drive in, I had it suddenly switch from my Ford's Sync system to the internal speaker. The dash display showed the phone was attached and when I switched from Pocket Casts to Play Music, it reflected what was playing, but the sound came out of the phone, not the car stereo. I went into the settings and toggled music off and on, switched Bluetooth off and on, then switch the stereo to AM radio then back to Bluetooth and it behaved properly.
I was using Waze which keeps the screen on and things were fine until I got off the freeway and shut down Waze. The screen shut off after a minute as normal, but when I double-tapped the screen to wake the display up, the audio dropped from the stereo and started playing from the phone. Hmmmm. I unpaired Sync and deleted the OPO from the car's side and I re-paired the phone.
It seemed OK until my drive home just now when once again, tapping the screen to wake it up cause the audio to drop back to the speaker. Since I don't use nav apps all the time, this is clearly an unacceptable bug that makes me wonder HTF they're beta-testing. It's nice that the GPS doesn't seem totally broken and the touchscreen goofiness is gone, but being unable to maintain Bluetooth connectivity for media is a huge gaffe.
Ok, I'm still trying to figure out what is going on here. I restored my TWRP backup from 33R and I had two bluetooth crashes on the way home today. Could there be a firmware update that is causing this that would not have been rolled back as part of the restore? I've read online that there is no new radio in 38R? Is there something else causing it?
I ran the full 33r factory image and it fixed the Bluetooth issues. I ran that way for a couple of days and had no BT problems even on a 2+ hour drive. I did a clean 33r to 38r OTA and within the first 30 minutes in the car had a BT freeze and disconnect. Its pretty clear, at least with my device, that there is something wrong with the BT stack on 38r.
I have little different but seems to related with BT.
When BT is enabled, my wifi performance drops significantly. I tried to remove all paired devices and reset BT config, but nothing really fixed the issue. I need to turn off BT completely, if my wifi speed goes down. I'm running 38R. I don't think I noticed any issue on 33R.
https://forums.oneplus.net/threads/...with-cell-data-turned-on.143815/#post-6381709
DirkBelig said:
I updated manually last night and this morning on the drive in, I had it suddenly switch from my Ford's Sync system to the internal speaker. The dash display showed the phone was attached and when I switched from Pocket Casts to Play Music, it reflected what was playing, but the sound came out of the phone, not the car stereo. I went into the settings and toggled music off and on, switched Bluetooth off and on, then switch the stereo to AM radio then back to Bluetooth and it behaved properly.
I was using Waze which keeps the screen on and things were fine until I got off the freeway and shut down Waze. The screen shut off after a minute as normal, but when I double-tapped the screen to wake the display up, the audio dropped from the stereo and started playing from the phone. Hmmmm. I unpaired Sync and deleted the OPO from the car's side and I re-paired the phone.
It seemed OK until my drive home just now when once again, tapping the screen to wake it up cause the audio to drop back to the speaker. Since I don't use nav apps all the time, this is clearly an unacceptable bug that makes me wonder HTF they're beta-testing. It's nice that the GPS doesn't seem totally broken and the touchscreen goofiness is gone, but being unable to maintain Bluetooth connectivity for media is a huge gaffe.
Click to expand...
Click to collapse
I'm having this exact same issue since upgrading to 38r. Bluetooth audio works fine until screen goes off and I turn it on again. Then audio comes out of the phone, but Bluetooth icon is still lit up and otherwise still connected to the car. VERY annoying.
Sent from my A0001 using Tapatalk
Yeah... Right now when I get into the car, audio plays though the speaker (despite bluetooth connection) unless I open Play Music specifically. Somehow that does something that also fixes other apps (Slacker, book readers, etc).
menos08642 said:
I've noticed that ever since I upgraded to 38R I keep getting disconnected from my bluetooth car stereo. When it disconnects the Bluetooth icon on the OPO goes grey. It looks like the Bluetooth module is crashing and then getting reset by the OS. I just got done with a 30 minute drive and it happened 3 times. Has anybody else noticed anything funky with the Bluetooth stack?
I've also had the phone itself hard crash several times. Not sure if 38R is ready for prime time.
I'm not running anything custom, just pure 38r on a rooted/twrp device. No exposed or other mods.
Click to expand...
Click to collapse
I'm on 44S, and have a similar issue. Had the issue since 38R though. Bluetooth stays connected to my car fine if I'm not using the OPO or if I'm just streaming music. But in phone calls, it drops the bluetooth all the time. Really really annoying.
menos08642 said:
I ran the full 33r factory image and it fixed the Bluetooth issues. I ran that way for a couple of days and had no BT problems even on a 2+ hour drive. I did a clean 33r to 38r OTA and within the first 30 minutes in the car had a BT freeze and disconnect. Its pretty clear, at least with my device, that there is something wrong with the BT stack on 38r.
Click to expand...
Click to collapse
I'm having same problem. Disconnects but just on calls and this happens with my BT headset. This doesn't actually happen on my stock Nexus 5. I'm thinking CM must be using different BT drivers? It's been the same on 33 and 44. I'm betting it carries to 5.0. If I don't find a workaround I may be forced to go to a different ROM. Just have no idea which one may be unaffected?
any fix for this?
I have a d2vzw running cyanogenmod CM, build M11. I recently bought a new car, a Mazda 3 with full infotainment system.
Frequently, while on a phone call through bluetooth, the call will stall (dead on both ends) and the infotainment screen will reboot. I have taken the car to the dealer and they say it is likely to be my modified phone that is the culprit since they show no issues with stock firmwear.
It is also common for the sound system to stop and not allow BT or USB audio through. It still lets FM radio, though. The screen does not reboot in this case, though.
So, the question: Is it possible/likely that this is my phone causing the reboots? So far, I have only noticed the reboots and stalls when connected via BT, but that has been most of the time.
And second: is there anything to be done other than going back to stock on my phone?
Has anyone else had this issue?
I have had a random and unpredictable bluetooth disconnection issue while driving. This issue occurred on pure stock device. So, I tried to "fix" this issue by trying various techniques including CPU governor, firmware updates (equivalent ROM upgrades/downgrades).
The phone is such a beauty. So fast and such great battery life.
However, I just can't deal with the distraction of the bluetooth dropping randomly. Maybe my device is defective?
64GB One+
Car: Honda Pilot 2013
Have you tried the CM12 nightlies? I haven't had issues with my moto 360 disconnecting ever..it doesn't like several devices being connected at once though. Maybe that's it?
Yes, tried each nightly with full wipe up to just a couple days ago.
Sometimes I would go 15 minutes with no Bluetooth drop.. And sometimes one whole day.. It's so random.
Sent from my SM-N910T using XDA Free mobile app
okay I think I have found a workaround which is working perfectly for me. I don't know why and how this has an impact but here is the workaround.
It seems like my calls while on bluetooth may have been dropping randomly due to something to do with Wifi.
I setup a system profile where it automatically turns my wifi off as soon as my car bluetooth is connected. And, I have another system profile which turns the wifi back on upon bluetooth disconnection.
For reference, below is my actual configuration.
Vanir Exodus Lollipop Rom
Build #: LRX22G
Build Date: Feb 11 22:01:59 CET 2015
- Not using custom kernel or tweaks
- Not using any CPU governor customizations
Ever since I upgraded to the new ViperOneM8 4.3.0 ROM I have been experiencing bluetooth issues every now and again. For example, I typically have my Moto360 watch and my Plantronics earpiece connected. In the middle of a call it will do weird things like spudder some crazy noises really fast for about 10 seconds then disconnect, or just plan disconnect. When it does disconnect, my phone still thinks the earpiece is connected and does NOT switch back to phone headset (like it used to). Then if I wait another 10-30 seconds it will reconnect and pick up the call on my earpiece again.
Anyone else having bluetooth issues on this ROM? It's a brand new install with nothing other than the basic google apps (and a few remote apps like LogMeIn, TeamViewer, and RD Client).
arvo.bowen said:
Ever since I upgraded to the new ViperOneM8 4.3.0 ROM I have been experiencing bluetooth issues every now and again. For example, I typically have my Moto360 watch and my Plantronics earpiece connected. In the middle of a call it will do weird things like spudder some crazy noises really fast for about 10 seconds then disconnect, or just plan disconnect. When it does disconnect, my phone still thinks the earpiece is connected and does NOT switch back to phone headset (like it used to). Then if I wait another 10-30 seconds it will reconnect and pick up the call on my earpiece again.
Anyone else having bluetooth issues on this ROM? It's a brand new install with nothing other than the basic google apps (and a few remote apps like LogMeIn, TeamViewer, and RD Client).
Click to expand...
Click to collapse
Mods should probably move this to the Q&A forum.
In general, I had weird bluetooth issues with audio. After flashing HK BS switcher INCLUDING the ADSP, all my issues went away. You need to be S-OFF, if you're not, don't even bother.
You want version 4.3.1 of this mod, considering you're running Lollipop.
Choose the Verizon install, not the ViperOne or anything else (even though you have Viper rom)
It's your choice what sound system you want. HK or Boomsound. I chose HK but that's just me.
I'd make a nandroid and give it a shot. Not sure if it's going to work, but can't hurt, especially if you make a nandroid.
http://forum.xda-developers.com/htc-one-m8/development/mod-audio-hk-bs-aroma-switcher-4-1-0-t3035354