I'm running the lates 3.21 quantum release with either the included kernel or using ktoonsez's kt747. Bluetooth issues were never an issue with 4.2.x ROM's but seem to be an issue on every ROM/Kernel I've found on the SGS3.
Does anyone know what the actual issue is? Seems like one driver worked possibly with the BMS kernel in early december but hasn't worked since.
I never get disconnects after connection, but once I turn off a bluetooth device I can't reconnect to it without a reboot.
I've been having a nightmare with bluetooth in my car.
It works flawlessly the first time - new connection, pair, works. Then if I disconnect by any method after that and try to reconnect, it spends about 10 minutes reconnecting and then is very sporadic and will disable/crash my phone. When my phone restarts, same thing unless I forget the pairing and recreate from scratch.
Related
Hi, I was wondering if anybody has come up with a fix for AOSP roms for Bluetooth yet. Sense roms connect to my bluetooth stereo perfectly, but none of the AOSP roms (Cyanogen, ect.) can connect consistently.
The very odd issue is that yesterday I thought I came up with a solution, so I flashed CM7 on and tested. It worked. However I couldn't connect to the market because I forgot to install the gapps addon, so I did, and didn't think twice until last night when going to work, and bluetooth wouldn't work again. It seemed like the gapps addon broke bluetooth, but it could have been some unknown external factor. I can test this later today to see if the gapps addon does in fact kill it somehow.
Can anybody shine light on the bluetooth issues and maybe enlighten me as to a fix if there is one?
Not one response? That's disappointing. I was doing some testing with CM7 today and I could not reproduce the bluetooth breakage that I have experienced every other time. I was trying to isolate what was causing the issue by lashing the rom, then booting, testing, then flashing the RIL, booting, testing, then flashing the gapps package, booting, testing, then re-installing all apps one at a time from titanium backup (the same as I did before) and nothing broke it. Over a full day now and bluetooth is rock solid.
This poses a problem because I don't know WHY it is working. The only variable I actually changed is booting after each thing I flashed. This still will not change issues with any other AOSP roms even if the solution is to flash each separately, because the rest come with gapps installed, and they are broken both before and after a RIL flash.
Also to further convolute things, I started the day testing LeeDroid. Bluetooth would not connect. This is a rom that should have connected just fine.
Hi mrcandyman,
I too have noticed that a lot of AOSP roms have (imho) severe BT problems, mainly with connection to earpieces in my case (voice dialling). I have tried AOSP roms on both my desire and sgs2 and had the same problems on both. Flashing back to rooted stock roms has always cured my problems with BT. I am not a dev or programmer so have no idea what or where the problem lies only that stock roms I've tried don't have BT problems and AOSP do.
feeling your pain,
Night....
This annoying problem popped out of nowhere I can think of.
Originally running AOKP #37. Since then I've tried all version of AOKP back to M5, wiping, formatting /system, CM9, faux123 16m, 17m, 18 b3. Each ROM the same problem.
I can connect to a media device once, either the car of speakers then a reboot is needed to [play] media again. The phone does show it being connected to the car but it's phone only.
If music is playing, through the phones speaker, and a call is placed the music plays [with] the call.
I've restored to AOKP b34 which seems to work, and totally wiped the phone to factory 4.02 which also seemed to work. Wiped flashed b37 back and was fine for a day.
I'm lost. It's annoying having to reboot at every 7-Eleven, gas station or Starbucks.
rinse and repeat? try a different rom? different kernel?
I rinsed and repeated constantly over the last week.
It's with all the ROMS I tried except for returning to stock, I think, I didn't keep it more than half a day and with AOKP b34 restored.
Oh, I had the "hybrid" radios, I've since installed 4.0.2 radios, 4.0.4 radios and am back to 4.02 thanks to returning to factory.
This is a VZ Galaxy Nexus.
I think I found my issue finally. I think a few more tests will confirm it's the MIUI permissions mod.
I've found the Bluetooth on the GN a bit buggy too. Though i manage to live with it.
When connecting to bluetooth devices i usually get the device to do the connection. If that doesnt work i just toggle Airplane mode on and off, and then it's working again.
If I manually turn off bluetooth it will end up hanging when turning on again.
After i switched to CM9 I think bluetooth overall is working a little better (might be placebo effect though).
The problem is definitely the MIUI permission mod.
Reinstalled it today and the issue returned immediately.
The stock Bluetooth system actually worked pretty good. from Nexus WAS controllable from the car stereo to an extent.
Hi guys I'm experiencing deep sleep issues. Sometimes my phone won't wake up. I have to keep pressing the power button for 10 seconds for the phone to reboot. It usually happens when the phone is in my pocket while I'm driving (it's paired to my car). I'm thinking there's an issue with the bluetooth pairing. I had the same problem with my s3 but it stopped when I disabled bluetooth. I'm running latest stock rom with Perseus kernel. Anyone else with same issue?
Swyped from another galaxy
I experience similar problems when I connect a bluetooth keyboard and a mouse at the same time. Usually everything works flawlessly, but after some use the phone rejects to get out of sleep. I can only resolve this by taking the battery out.
Need to investigate more. But my s3 hasn't been paired with my car for months and I haven't experienced any lockups since then. I'm sure it's the same issue on the gn2
Swyped from another galaxy
OK 2 days with bluetooth off= no reboots or lockups. So I'm assuming bt needs some fixing
Swyped from another galaxy
Try uneak or redpil kernel
My mom has the Gnex on Verizon, which has just recently updated to Android OS 4.2.2 (Stock ROM). It seems that since the update, the phone automatically changed its displayed Bluetooth ID that other devices see. Now it seems that when the phone sleeps and is connected to her car radio (2012 Hyundai Elantra w/ built in Bluetooth connection), the connection interrupts itself for about 15-30 seconds and then automatically re-connects to the radio. Making a call on the phone practically impossible.
I was going to just try to set up a Tasker event to keep the display on when connected to power, but that option is unavailable in 4.2.2 without rooting the phone.
As odd as this sounds, any non-rooting solutions would be appreciated.
Thanks.
Sent from my SCH-I605 using xda premium
sbdunn1992 said:
My mom has the Gnex on Verizon, which has just recently updated to Android OS 4.2.2 (Stock ROM). It seems that since the update, the phone automatically changed its displayed Bluetooth ID that other devices see. Now it seems that when the phone sleeps and is connected to her car radio (2012 Hyundai Elantra w/ built in Bluetooth connection), the connection interrupts itself for about 15-30 seconds and then automatically re-connects to the radio. Making a call on the phone practically impossible.
I was going to just try to set up a Tasker event to keep the display on when connected to power, but that option is unavailable in 4.2.2 without rooting the phone.
As odd as this sounds, any non-rooting solutions would be appreciated.
Thanks.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I assume you tried to delete the pairing (both sides) and pair again?
You could buy an app like CarHome Ultra (or maybe try the free version if it has the option). It has a setting to keep the display on when plugged in (though I have not tested it as I use tasker with root/secure settings).
I've the same behaviour and my is a Maguro device (GSM).
During a phone conversation there is no problem at all but when in idle phone continuously connect and disconnect (I can see the BT status on the display of my car).
I tried to revert back to 4.1.x ROMs and problem disappear so I can the same recognize it's something in 4.2.x ROMs.
In these last days I tried (and report my feedback, of course not general to anyone else)
- CM 10.1 without BT disruption
- PitchBlack 1.7 with BT disruption
- PitchBlack 1.7 + Franco Kernel 3.0.70 with BT disruption
- PA3.1 with BT disruption (last PA which worked fine for BT is 2.54)
Any ideas?
What part of ROM/Kernel/bootloader/... is in charge to manage BT?
Can it be a problem of sleeping/deep sleep?
Sadly enough, I had not tried that. At any rate, the phone "magically" (I use this term loosely, mind you) appeared to sort itself out and is working fine once again. I don't know if Google had pushed another update to it in the meantime of trying to sort the problem out the first time or what, but at any rate all is well. Thanks for the tips.
Sent from my SCH-I605 using xda premium
Hi all,
I was wondering if anyone else was experiencing this, and/or had any solutions - as it's slowly driving me mad.
I do love my M8, but it's getting old and slow running Sense 6/7, and I much prefer the 'pureness' of GPe/CM12.
My phone is SuperCID'd and fully unlocked, and currently flashed the latest RUU for GPe (full firmware) then Candy5 ROM v2.5.5 flashed (based on CM12).
I've tried various Sense firmwares, and other hacked/full GPe firmwares... Bluetooth seems the same on all - works fine on Sense, but not as reliable on non-Sense.
The biggest issue I have is that I have a LG G Watch R and it will disconnect after a few hours, sometimes days, and won't reconnect unless I turn off and on Bluetooth on the phone. Even then it's temporary - I find Wiping Data on com.share.bluetooth makes it stable again for a few more hours/days.
And no, it's not the watch, as if I'm in the car at the same time - that will disconnect and not reconnect either. It's definitely the phone...
Now I generally keep Bluetooth and WiFi on at all times. I only use WiFi at home.
I have noticed it seems to become unreliable if WiFi is on, but hasn't been connected to anything for a while. It's almost like it's "scanning" buffer is full and it's affecting both WiFi and BT (as it's the same chip).
If I keep WiFi off, and only on at Home where it stays connected - my Bluetooth seems really reliable and I don't have an issue.
This isn't a fix, though. As I don't want to have to rely on Llama to switch my WiFi on and off based on my location. Surely a potential battery drain versus just keeping it on at all times.
I've tried a Tasker task to wipe com.share.bluetooth every couple of hours, but it didn't fix it. Would still die beforehand.
I've tried various GPe ROMs, and CM12 ROMs - all as Clean Flashes and not restoring Bluetooth data in Titanium Backup (I only restore user aps + data).
Just wondered if anyone had any ideas!!
Thanks for reading.
I'm having the exact same issue.
Gpe and sense work fine, but cm12,1 just won't stay connected to my car or watch. Very frustrating.
I really want to run cm as my daily driver, but it's totally incapable of keeping Bluetooth up.
Is anyone running cm 12.1 and has working Bluetooth? If so, can you let us know which radio firmware you're using?
I took a stab in the dark and applied firmware 4.16.401.10. So far my watch's connection has been solid. Still haven't tested the car, but will test today. Hopefully it'll be stable - if it is then I'll finally be able to use CM as my daily driver!
Full commute without Bluetooth disconnecting from my car, and I've had a solid connection to my watch for over 24 hrs! WOOOOOOOT!!!!
4.16.401.10 is the trick. Anyone having Bluetooth issues on CM12.1 should go download and apply the firmware. (must be s-off, obvs.)
Firmware is here (courtesy of Mike1986 of ARHD fame)
Ah great news - thanks.
I'll give it a go later!
Should know within 15 mins after if the bug is fixed!
Thanks again.
Update - looks like that's the fix!
Strange it doesn't seem to be mentioned anywhere else but at least it's now here for anyone else.
Thanks for the tip!