Related
As being discussed in various threads, some people are having BT problems with EB13 based ROMs.
The Problem
Inability to connect at some future time after having paired device with phone. Rebooting doesn't help. Only solution is to unpair, and re-pair, then device will both pair and connect with phone.
Also seen by some people are audio routing problems after disconnecting BT. Not sure if this is confined to devices that support (and connect) A2DP... more investigation/testing needed.
The Workaround
I tested various conditions to see how the BT subsystem behaved under various usage modes. In particular, across boots, turning BT on and off on the phone, on the device, etc. -- and then observed if automatic connection would re-establish after each combination of conditions.
I found that the problem seems to only happen if I turn off BT on the phone. If I leave it on, pair and connect with a BT device, then I can turn the device on and off at will, and it will automatically connect.
This (normal) function persists across reboots, at least for the few I tested.
I don't know how power-hungry the BT radio is when idle and not connected. My gut feel is that it is a pretty small drain, so leaving BT on all the time as a workaround probably won't have much of an impact on battery drain. I use Juice Plotter, and have a good history with BT off to compare to. I'll post JP measurements/results tomorrow after a 24 hour cycle.
Caveats
I also changed my Epic BT device name before I explored this situation with toggling the BT radio on the phone. While the name change did not correct the problem on its own, I can't rule out that the combination of name change and leaving BT on is what is making things work, rather than just the latter alone. So, to try this workaround, you must also change your BT device name on the phone, and leave BT on. Then, clear pairing and re-pair for the target BT device.
My Request
Would people that are having this problem please try this out, and report back in this thread success/failure, and any other observations. What we see in testing these different modes will be very helpful to the devs in trying to trouble-shoot an fix this problem (which I have no doubt they will long before Samsung does).
It should be noted that some folks are having issue connecting to a device, even after un-pairing and re-pairing. If that is the case, you might try this-
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Also, some folks are reporting an issue with multiple pin requests before a device will finally pair. I haven't seen that one myself, but just thought I'd mention it.
For what it's worth, other than the BT routing issue, I haven't seen any of these pairing or connection issues on my stock rfs Epic. It wasn't until I converted my other Epic to ext4 that Bluetooth had any issues, and they were all fixed by wiping data and have not returned since.
I have tried the workout around before in the past, and it changed nothing. Also I have noticed I seem to have more issues with particular audio bluetooth ear pieces, like BlueAnt Q2. It will show pairing is connected but after a couple hrs on the bluetooth connection is gone, but like I said it shows paired. My cheaper Plantronic ear pieces seem to work much better, except the fact I have to re-pair after each reboot of the Epic.
Ive tried leaving bluetooth on all the time, but after a reboot,
i have to repair ive tried all suggestions to fix it and the only way it seems is once it gets connected is always have the phone on and cant die and bluetooth always has to be on,
even after a long period of time somehow it loses the connection even if bluetooth is on and phone stays on,
There must be somethng the developers can patch with a flashable fix or another work around to get squash this annoying bug.. ill try to get a logcat today and try your method again see if i have luck
I will try to leave mine on and see what happens. Name change did not help.
But short on time. But given the chance I want to go back to bonsai 3.0.1 and see if I have the same problem. I don't recall it giving me a problem.
Edit: of I leave BT on, on the phone and just turn the BT device on/off it will not pair back up.
Edit: May have figured something out. I have been toggling BT with a widget. When I toggle from the notification bar it seems to work (so far). Which would also explain why it quite working as I added apps. As from clean install is used the notification bar and later used my power widget. But I have always used a widget before. I will test this out at work and see if this work around keeps working for me.
Sent from my SPH-D700 using XDA Premium App
I have to re-enter the PIN after every reboot. Mildly annoying.
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
automator said:
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
Click to expand...
Click to collapse
In my experience, the BT radio does not use any power when not connected to a device. If it does, it's not noticeable in Spare Parts or in performance.
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
blackdragon79 said:
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Have the pairing issue with ACS EB13 Frozen ROM 1.0.3/ Twilight kernel. The BT headset I use is Plantronics 975. Never had a problem with any of my phones until now... even my Treo 755 connected properly, not to mention BB Tour FWIW, my headset supports A2DP and I wiped/reflashed ROM/kernel several times without resolving the BT issue. Will leave BT on, but does it mean after every reboot I have to re-pair? That's not good if true, I hope a permanent fix can be found soon.
davidrules7778 said:
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Click to expand...
Click to collapse
I'm using syndicate frozen
Sent from my SPH-D700 using XDA Premium App
Update: For me at least, this workaround is still working 3 days later without a hitch, and across more reboots than I can count.
While I don't _know_ with tech/spec/engr certainty, as mentioned above it seems that BT uses negligible power when it is only listening for connection requests, and has had no discernible impact on battery drain at all.
So, this seems to be a viable workaround for the time being for some of us... it's real. What we need to work on as a community is figuring out what the critical difference is between those for which it works, and those for which it doesn't. KEEP POSTING AS MUCH DETAIL AND INFO IN THIS THREAD AS YOU CAN, EVERYONE... DATA IS WHAT WILL GET US TO THE BOTTOM OF THIS.
Personally, I think the key difference between the two groups is the size of your junk -- People with small equipment seem to be having all the failures
Sent from my mind using telepathitalk
I've had this issue on all Froyo builds. I have tried 7 different BT headsets from Samsmsung, Plantronics, Jabra & Blue Ant, all of them a2dp compliant with the same result, after a while, they stop connecting and I have to re-pair. As for the "workaround" since I have several extended batteries I've never turned BT off, and while it does take much longer to lose pairing, it eventually stops syncing or syncs only the headset protocol but not A2dp. For myself, the only solution I've found is to go back to DI18 which, although has its faults, works flawlessly with BT
I have been trying to get my brother's Epic working properly. It is rooted with EB13 installed. If this bluetooth error is not related to what others are having, let me know and I will create a different thread. I got his motorola H520 paired. I press the button and it starts the bluetooth voice dialing. It beeps and says please speak and then immediately gives and error saying the connection to the bluetooth was lost but the settings shows it to still be conneceted and it is as you can answer calls with the bluetooth without having to reconnect it.
My plantronics backbeat is paired and for phone calls is working, but sometimes no audio through music or video players. I had to un-pair, then re-pair then audio will work for a while.
I am using CWM 3.0.0.6 with midnight ROM with its installed kernal
Happening on my Plantronics Voyager Pro+ - It seems that everytime I pick up my phone the BT disconnects and then after about 15 to 30 seconds reconnects as long as I don't push any buttons.
There is also a lag "thingy" that occurs when I'm on a call and then another person calls - while the the second call is coming in, it seems like the packets get interrupted from the handset to the headset. Then once the incomming call goes to VM, the audio from the current call gets restored. Not sure if this is helpful or not, but I wonder if there are some routines in the BT transmission that have common "hooks" which are used when a second call comes in - Hope that is not too much of a noob statement...
Is anybody else having that "laggy" issue in the same circumstances?
Hey all, just "upgraded" from a Note4 to the OP5.
I was mostly expecting this to happen, but still it disappointed me; the new handset doesn't connect to my Kenwood car h/u via USB. It's a Kenwood X500. I seem to have read that Android 7+ has a lot of issues with usb audio out. I stream almost all my music via google music, so something like usb audio player won't work for me (I haven't tried it).
I tried playing with the USB setting in developer options, but that didn't do anything for me. USB debugging on/off made no difference. Selecting USB mode from the notification drop down didn't change anything. Sometimes it would outright "no device", but usually it just sat there at "reading device". I get the "Open Kenwood blah blah app?" message when I plug in initially, but selecting yes doesn't launch the app, selecting cancel doesn't do anything. Manually opening the app both before and after plugging the phone in results in the same non-connection.
My last 3 phones did, obviously the Note4(TW), a S6(TW), and the Nexus 5(stock/AOSP).
On my last 2 Samsung TW phones, I'd plug in, the notification would appear. I'd ignore the first one and it would go away after 2 seconds, then a second later the same message would come back up. I could click cancel or hit the back button on the second one, and I'd be in streaming mode, or what the deck calls "hands mode". I could then play whatever music from whatever app I wanted.
I'm currently in the process of flashing a AOSP based ROM to see if it'll help, but wondering if anyone has any help on the topic. Yes yes, bluetooth this, bluetooth that.. bluetooth sounds terrible even with aptX.
Thanks for any kind of help.
For the record, the latest LineageOS reacts the same.
I may have screwed up by flashing a new firmware for the deck, I have to do some research and see if I can find older versions and flash some others.
So I seem to be having issues with bluetooth. Most of the BT devices work, but my TomTom Raider 400 does not seem to want to work.
I was able to pair it to the device, but thats all I get, the TomTom says it won't connect or anything, It was working great nougat now it does not work anymore. I cleared out all network settings, still no go.
Anyone having issues with devices that perhaps require data? anyone have any ideas?
eatonjb said:
So I seem to be having issues with bluetooth. Most of the BT devices work, but my TomTom Raider 400 does not seem to want to work.
I was able to pair it to the device, but thats all I get, the TomTom says it won't connect or anything, It was working great nougat now it does not work anymore. I cleared out all network settings, still no go.
Anyone having issues with devices that perhaps require data? anyone have any ideas?
Click to expand...
Click to collapse
I'm having similar BT problems since the update. Sometimes my car doesn't connect. Quite often my Gear S3 disconnects when the phone is still well within range. My Sat Nav will only connect via BT if I search for it. There is definitely a glitch but I haven't found a fix
Sent from my SM-G950F using Tapatalk
Same issues here, with Tomtom GO 510 and with asus Chromebook too (via Bluetooth only)
I've updated to CRC7 today using the SD card update method described here.
https://forum.xda-developers.com/showthread.php?t=3746561
The BT is much more stable this afternoon and a persistent problem that I had with my home Wi-Fi seems to be gone too. Early days, but it does seem better [emoji106]
Sent from my SM-G950F using Tapatalk
I updated to Oreo 8.0 on my S8 today and have had bluetooth connectivity issues ever since. Listening to music in the car, it will randomly drop connection. Also, some track information is no longer showing on the headunit (the playback time and the overall song length). Everything worked perfect before update. Seems to have been a known problem that may have been addressed with the 8.1 update on Pixel and Nexus phones. Unfortunately my carrier (ATT) just rolled out the 8.0 update today for my S8. I'm at a loss for what to do.
It's failing left and right.
I turn it on and it turns off apprx 1 min later.
I turn it back on and it does the same thing (each time).
removing and re-setting up everything fails.
rebooting fails (same as turning on and off)
safe mode does not help.
So far, Oreo has made Bluetooth useless on my S8
thecolor said:
It's failing left and right.
I turn it on and it turns off apprx 1 min later.
I turn it back on and it does the same thing (each time).
removing and re-setting up everything fails.
rebooting fails (same as turning on and off)
safe mode does not help.
So far, Oreo has made Bluetooth useless on my S8
Click to expand...
Click to collapse
So glad I'm not the only one. It's driving me mad
Sent from my SM-G955F using Tapatalk
STandy469 said:
So glad I'm not the only one. It's driving me mad
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
After Oreo update my S8's BT became spotty working 20% of the time on calls in the car. So i searched & read that resetting network connections would do the trick. It wasn't under connections->more settings - instead i found it in about phone-at the bottom under Looking for something else-> Reset->Reset Network Settings . Yehey i found it & reset my network settings!
Now my BT won't turn ON! From 20% to 0% function!!!
What a what!
Fix this Samsung!
Sent from my SM-G950F using Tapatalk
Same issue here. My S8+ was rock solid on Nougat, but since the update to Oreo yesterday my Bluetooth does not connect 19 out of 20 tries in my car. I factory reset my phone thinking it may have been an issue with the update process, but that did nothing to fix the issue. I really need a solution as I need to talk while in my car.
Haven't tried using Bluetooth on anything else, but my phone stays consistently connected to my Gear watch.
Anyone have any solutions to this? I'm experiencing the same issues. Won't connect consistently with my gear s2, drops certain speakers all the time, although it seems to stay connected more consistently to my car. Really frustrating and don't want to wait for the glacial pace of Verizon update rollouts.
bstarr3 said:
Anyone have any solutions to this? I'm experiencing the same issues. Won't connect consistently with my gear s2, drops certain speakers all the time, although it seems to stay connected more consistently to my car. Really frustrating and don't want to wait for the glacial pace of Verizon update rollouts.
Click to expand...
Click to collapse
Did you do a fresh install ( download, install, clear cache, wipe phone, rebuild or restore backup) or just install the update and go from there?
Sent from my SM-G950U1 using Tapatalk
A0425A said:
Did you do a fresh install ( download, install, clear cache, wipe phone, rebuild or restore backup) or just install the update and go from there?
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
I just installed the update, but up the thread above several people say that factory reset didn't fix this issue for them.
It won't make a difference. I factory reset my phone after the update to Oreo and reconfigured everything from scratch, no restore, and it made no difference. My Bluetooth still does not work with my car. It works with my Pebble, my Sony Bluetooth headset, and a Marley speaker with no issues. Why is it that only my car fails? It is the most important one.
I am having the same issue when listening to music with Bluetooth in my car. The music gets choppy and does not play back the way it should. I have been looking everywhere online for a fix and I haven't come up with anything. If anyone has any suggestions it would be greatly appreciated.
Same issue with Sony XAV-68BT headunit. Music plays through Bluetooth, then drops rendomly, then manually have to reconnect. Very distracting while driving. Phone calls do not seem to be affected though, so... There's another little tidbit.
Actually I did notice the other day that my Gear Sport was on standalone mode instead of Bluetooth, so I was missing texts from people. Really annoying. Samsung better address this.. going to take ages for Verizon to get the update though, I'm sure.
Any chance that the Bluetooth apk file for the Galaxy S9 would work on our phones? Maybe it would help?
I'm having similar issues here too. I was on Nougat with zero problems. Did an OTA update to Oreo and suddenly my Kenwood car stereo keeps losing bluetooth connectdion. Used ODIN to flash back to Nougat and it's rock solid. Decided to flash Oreo instead of doing it OTA, and suddenly the bluetooth is flakey again. Flashed back to Nougat, and it's rock solid. I've also tried factory resetting and reconfiguring the car stereo, did a factory reset of the Galaxy S8, cleared the cache, and nothing works. The only way of getting Bluetooth to maintain a connection to the car stereo is to be on Nougat.
Interestingly though, I have no problems with my Gear S3 maintaining a bluetooth connection.
It appears it's only some devices that have the issue. I don't hold out much hope that Samsung will fix it though. Weren't people complaining about the same thing during the betas?
I guess this can solve your problems too, I had an issue since the oreo update, cant select anything but SBC reverting to default, even with the level u app not showing UHQ, I started a chat with samsungs members app and they told me that is an error in the update, not all devices are presenting this problem. well, the solution: 1. back up your data with smartswitch app(I backed up with a sd card, 10Gb info) if you have whatsapp do a chat backup because they dont backup with smartswitch. 2. delete your samsung and google account. 3. Do a hard reset(witch the phone powered off press volume+, bixby and power, until you see the recovery menu), wiping cache and then wipe data/factory reset(move trough the menu with volume+- and select with power). 4. start the phone and add your google and samsung account, then restore your data with smarwitch app. this will let you select the BT codec again.
worked for me and the bluetooth conection is more stable
Seems that we may have that memory leak solved
Yes, must have bug fix as 330Mb download. Updated, all good (no mods)
Is the haptic feedback on opening recents menu new? Or just stronger than before?
Is there a setting I'm not seeing to change it?
GandalfTehGray said:
Is the haptic feedback on opening recents menu new? Or just stronger than before?
Is there a setting I'm not seeing to change it?
Click to expand...
Click to collapse
it's in
accessibility>vibration
I received my phone and downloaded the ROM yesterday, seems to be good.
Anyone else's Bluetooth totally screwed up after update? After update, Bluetooth turns on by itself, won't add new devices, and won't auto connect to devices?
svrasputin said:
Anyone else's Bluetooth totally screwed up after update? After update, Bluetooth turns on by itself, won't add new devices, and won't auto connect to devices?
Click to expand...
Click to collapse
Mine has been pretty flaky as well. It seems to connect most of the time, but if I call with my android auto head unit, even though it says it's using bluetooth, the sound still comes out of the speakers. Sometimes a toggle of the bluetooth switch fixes it, sometimes it needs a reboot. I may factory reset and see if it clears up.
svrasputin said:
Anyone else's Bluetooth totally screwed up after update? After update, Bluetooth turns on by itself, won't add new devices, and won't auto connect to devices?
Click to expand...
Click to collapse
I don't have problem with the Bluetooth.
Using my Sony ch700n without a problem..
Mmm... I'll be waiting for more feedback before applying the update. Hope it's just specific issue with device because I use BT every day...
Still haven't been able to fix Bluetooth issues. First I reset all the network settings. Not fixed. Then I factory reset without restore. No fix. Finally factory reset with restore. No fix. Contacted support last night with no answer yet. Will have to resort to back up phone until there is a solution.
svrasputin said:
Anyone else's Bluetooth totally screwed up after update? After update, Bluetooth turns on by itself, won't add new devices, and won't auto connect to devices?
Click to expand...
Click to collapse
Nope, all good here. How did you take the update, ota or fastboot?
At this point my Bluetooth is behaving normally. All though I never have had any of the previous Bluetooth or wifi issues people have posted about. Totally stock locked bootloader with February update.
As of this Monday Miracast on my PH-1 is totally flakey. Since it uses Bluetooth I guess this is part of the update bug. The problem I'm getting is casting crapping out, for no reason, rotating the phone, or just launching the app that I want to cast. Any possible fixes?
bfmetcalf said:
Mine has been pretty flaky as well. It seems to connect most of the time, but if I call with my android auto head unit, even though it says it's using bluetooth, the sound still comes out of the speakers. Sometimes a toggle of the bluetooth switch fixes it, sometimes it needs a reboot. I may factory reset and see if it clears up.
Click to expand...
Click to collapse
I can't get my PH1 to connect via BT to my Pioneer A.A H/U at all...... not sure what the issue is.
I factory reset and still having issues as well, I'm completely stock with locked bootloader. Only real Bluetooth issue I have is phone calls going through my phone speakers even though it says it's using Bluetooth, audio for music and podcasts is fine. Very strange
bfmetcalf said:
I factory reset and still having issues as well, I'm completely stock with locked bootloader. Only real Bluetooth issue I have is phone calls going through my phone speakers even though it says it's using Bluetooth, audio for music and podcasts is fine. Very strange
Click to expand...
Click to collapse
I used AA this morning in wifes car, music was playing, made a phone call & it used car speakers as normal & then went back to music when call ended, so seems OK with Hyundai HU.
IronRoo said:
I used AA this morning in wifes cam, music was playing, made a phone call & it used car speakers as normal & then went back to music when call ended, so seems OK with Hyundai HU.
Click to expand...
Click to collapse
I'm kind of wondering if it has something to do with my Wear OS watch being connected. May have to disable it for a day and see if it makes a difference. Worked perfectly before the update though.
Edit: I played a little. If I turn off Bluetooth on my watch, then pair with my Bluetooth headphones calls work normally, if I connect to the buds while connected to the watch, no-go. Very odd as well is that the watch won't connect then while connected to the buds, once I disconnect them, it connects fine. I'll try with my truck at lunch and see if I can repeat this there.
mine seems do not have the Bluetooth issue.
new update seem to be more aggressive on turning off nfc . in the past, i do not have to wake on phone to 'tap' (as a smart card) on chargepoint ev charger. now i have to at least wake up phone to do so.
i noticed on essential website. the OTA file for February is only Open Market. the others have said Alll. Whats the difference anyone know.
After I have installing the update patch, the usage of battery is a bit faster than before. The sot drop from 4 hours to 2 and a half hours. Is there getting The same issue?
Ok, so I am sure someone has already answered this question but right now I can't find it. I'd like to know how to set the launcher so it can remember the last app that was playing before shutting down.
For example, I may be listening to a sat radio channel when I stop for gas. 10 minutes later I am back in the car and start, yet FCC doesn't launch the sat radio app, even though I have tried setting this feature in "AUTOSTART".
Is there anyone here who can help with this. ? There's also a feature under "SOUND" that is supposed to restart whetver audio you were listening to before the last shut down. This doesn't seem to work for me, either.
Thanks in advance for any help on this.
Depending on your head unit you need to play around with the timing in Fcc.
Wait before Autostart --> try first 30 sec and reduce the time until the autostart does not work anymore. Then just go back to the working timing.