Database Develop

[Q] Bluetooth Problems on CM7

I can't seem to get bluetooth to enable on my Nook. I've tried using CyanogenMod 7 nightly and the CynogenMod-7.0.0-encore as well. No luck. I've tried turning off wireless hard rebooting, fixed permissions ect... When I click the bluetooth icon it blinks and within a quarter of a second it turns off. It doesn't even have an icon that says it's trying to turn it on. Anybody have any ideas on what I can do to fix it?

tons of threads about that - just go to ROM Manager, click Fix Permissions then after that is done and you see a popup asking you to reboot, don't select this, rather press the power switch down until the nook powers off, then turn it back on again

animatechnica said:
tons of threads about that - just go to ROM Manager, click Fix Permissions then after that is done and you see a popup asking you to reboot, don't select this, rather press the power switch down until the nook powers off, then turn it back on again
Click to expand...
Click to collapse
If you would of read, I have already tried it. It didn't work.

I have the same exact issue as the OP.
Tried all the recommended fixes including fixing permissions.
Tried one additional step I found mentioned somewhere.
Go into spare parts uncheck compatibility mode and reboot.
Apparently this worked for some but not me.
Hoping someone with same problem can ping in with what might have worked for them.

Please guys try this.
Firstly, you switch off you wifi.
Secondly, you reboot.
Thirdly, you switch on your bluetooth and get it running. (it seems the bluetooth would not start after Wifi)

Sadly It still isn't working. I've already tried the hard boot with wireless off and quickly starting up the bluetooth as soon as my nook is started. Any other suggestions?
Edit: Do you guys think it just might not work/ dead?

Azamatka said:
Please guys try this.
Firstly, you switch off you wifi.
Secondly, you reboot.
Thirdly, you switch on your bluetooth and get it running. (it seems the bluetooth would not start after Wifi)
Click to expand...
Click to collapse
This. Always works for me. As he said, turn off wifi entirely, POWER DOWN. Boot back up, turn on Bluetooth. Once it's up, turn on Wifi.

khaytsus said:
This. Always works for me. As he said, turn off wifi entirely, POWER DOWN. Boot back up, turn on Bluetooth. Once it's up, turn on Wifi.
Click to expand...
Click to collapse
Nope didn't work if you read my posts... When I find my camera I'll try to post a video of what it does to "try" to enable bluetooth.

Azamatka said:
Please guys try this.
Firstly, you switch off you wifi.
Secondly, you reboot.
Thirdly, you switch on your bluetooth and get it running. (it seems the bluetooth would not start after Wifi)
Click to expand...
Click to collapse
Thanks got it working. I was wondering why it would shut down after clicking turn on. But now if it says paired but not connected does that mean my holux GPS isn't going to work with the nook?

had the same behaviour until tried this:
1 turn off wireless
2 fixed permisions with rom manager
3 turned off nook, by pressing power button
4 restarted nook
5 turned on bluetooth
after this, i could freely turn on/off wifi and bluetooth without complaining
btw, i'm on CM7 stable running on verygreen SD card with 04/04 dal's kernel

@brento1
You have to use an app such as GPS Provider to connect your GPS to android. Otherwise you will get that error.
___________________
- Derek

I have tried all suggestions but bluetooth will not turn on.

don_ernesto said:
had the same behaviour until tried this:
1 turn off wireless
2 fixed permisions with rom manager
3 turned off nook, by pressing power button
4 restarted nook
5 turned on bluetooth
after this, i could freely turn on/off wifi and bluetooth
Click to expand...
Click to collapse
This worked for me.

sanvara said:
This worked for me.
Click to expand...
Click to collapse
Yes above steps works for me too.

don_ernesto said:
had the same behaviour until tried this:
1 turn off wireless
2 fixed permisions with rom manager
3 turned off nook, by pressing power button
4 restarted nook
5 turned on bluetooth
after this, i could freely turn on/off wifi and bluetooth without complaining
btw, i'm on CM7 stable running on verygreen SD card with 04/04 dal's kernel
Click to expand...
Click to collapse
That didn't work... But I figured it out! I was running on Dal's OC kernel and for some reason it was clashing BT! Thanks everyone for trying!

So I've tried everything suggested multiple time with and does not work.
Thanks for discoverying the OC kernel connection. I am also running it. I will try to install a fresh nightly without OC tonight.
Are any of you with working BT also using the OC kernel?

As of this moment, I'm not going to install an OC kernel because I'm afraid I won't be able to get BT to work. Can anyone recommend one?

I have phiremod 6, with the OC kernal and it works, but initially, I had the problem.
Shut down the nook and start it up again. NOTE, Do not do a reboot, do a shut down!
Hope it works for you.

i think i have the same problem that I'm using the OC kernel, do anyone have a suggested kernel to intro?
thanks in advance..

Disconnected...

OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?

I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?

Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app

skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty

I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?

shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.

I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification

disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...

Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.

I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.

Notification problems

I seem to be having an intermittent problem with notifications on my new Moto G, when using the device and a notification comes through everything works 100%, however I sleep the device by tapping the power button as you do, occasionally notifications will not come through and then I tap the power button and the phone buzzes and the notification light starts flashing like they just came through at that second (when the time on the notification shows as X minuets previous).
I can't seem to replicate this in any fashion, it seems completely random and effects all types of notification, Gmail, WhatsApp and also the Ringer from Android Device Manager.
The Ringer from Android Device Manager is where I first confirmed the problem, I was playing with the Android Device Manager locating my phone which was sleeping right next to me, it located it fine so I hit ring and it said 'successful' or words to that effect, but the device was not ringing at all, picked up the phone and woke it, it immediately started ringing. I tried it a 2nd time and the same thing happened again, the 3rd time it worked as designed.
I've tried restarting the phone and clearing the data of effected apps, but neither worked, a reset of the device is the next logical step but I would like to hear if anyone else has this problem or has any other solutions.
This is happening when the device is connected to WiFi (even while sleeping) with the mobile data either enabled or disabled, I have not tried what happens if WiFi is not turned on, because when I'm at home I want it to use WiFi.
TLDR: sometimes by random I don't get notifications until I manually wake the device when they did actually come through X minutes previous it just didn't tell me.

Try resetting it! I never had such a problem
Sent from my XT1068 using XDA Free mobile app

Droids king said:
Try resetting it! I never had such a problem
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Ok will do, is the 'Factory Reset' option in the menu sufficient, or is there something else I should do?

Check your advance wifi settings and also check Motorola Assist just in case!

sahil kaul said:
Check your advance wifi settings and also check Motorola Assist just in case!
Click to expand...
Click to collapse
I have keep WiFi on during sleep set to Always, and Avoid Poor Connections and WiFi Optimisation both ticked everything else is off, I've never used Motorola Assist.
I'll untick Avoid Poor Connections but I doubt it could be that as I have very good WiFi signal where I am.

jay2the1 said:
I have keep WiFi on during sleep set to Always, and Avoid Poor Connections and WiFi Optimisation both ticked everything else is off, I've never used Motorola Assist.
I'll untick Avoid Poor Connections but I doubt it could be that as I have very good WiFi signal where I am.
Click to expand...
Click to collapse
How about Wi-Fi optimization, its usually Checked. Uncheck it. It should work.

sahil kaul said:
How about Wi-Fi optimization, its usually Checked. Uncheck it. It should work.
Click to expand...
Click to collapse
OK when I find out that Avoid poor connections being unticked is not working (which I've just had a notification suggesting it isn't) I'll untick WiFi optimisation, I'm hesitant to untick it right now as it says it saves battery life.

OK new development I was listening to music on the phone (the phone is sleeping) the song ended but the next one didn't start, as soon as I tapped the power button the next song started.
I'm going to try resetting the phone as soon as I get chance, I just need to use a voucher in an app first as I'd loose it otherwise.

Double post

Reset the device today, my plan was to use the Recovery but none of the options would appear it would only display the Android laying down (even when pressing buttons), so instead used the Factory Reset option in the menu, only time will tell but fingers crossed it seems to be working OK now :fingers-crossed:

Reconnection Problems

Whenever my phone and watch are disconnected for an extended period (>1-2 minutes), they rarely will reconnect. The only solution I have found is to force stop the android wear app on the phone and restart it, or reboot the phone. Anyone else having this issue? I have completely reset the watch (G Watch R), reset the BT profiles, cleared the Android Wear app data, reconfigured the phone connection and still have the issue.

I have the same problem but if disconnect and reconnect the BT it's ok
Bye
V

thats by design
when disconnected, the AW phone app will try to reestablishe a connection periodically
however, in order not to kill your battery, the period between the connection attempts gets longer and longer
(starts at 2 sec and goes up to 256 sec - you can see this if you have developer options enabled on your phone)
so your watch should definitely reconnect within 5 min
instead of killing the AW phone app, I open the app and click on disconnect and immediately afterwards on connect again

I have the same problem. If I get out of range of my phone, the bluetooth will disconnect. rarely does it reconnect on it's own. Turning bluetooth off/on on my phone doesn't seem to fix it. Usually a watch reboot fixes it or both a watch and phone reboot is needed.
Anyone have any ideas...?

scott500 said:
I have the same problem. If I get out of range of my phone, the bluetooth will disconnect. rarely does it reconnect on it's own. Turning bluetooth off/on on my phone doesn't seem to fix it. Usually a watch reboot fixes it or both a watch and phone reboot is needed.
Anyone have any ideas...?
Click to expand...
Click to collapse
thats strange, turning bluetooth off and on again should lead to an immediate reconnection
if you disable bluetooth, the Android Wear notification should disappear from your phone and reappear once you turn bluetooth on again
is that the case for you?

having similar problems from time to time. Even more bad is when i update my Phone with a new Rom, i need to Reset the Watch to Factory Default otherwise it will not connect at all!

I'll keep an eye on it I just tried to disconnect and reconnect Bluetooth under normal conditions and it worked fine.. So it must be a bug which hangs up the watch periodically.
Thanks for the input.
Sent from my HTC One_M8 using XDA Free mobile app

Losing Bluetooth Connection

I have a weird problem with my Moto X 2014 (Pure Edition). It's randomly losing bluetooth connection in a background (basically any BT connection – to auto, smartwatch, etc.) but the phone itself says everything is fine (Bluetooth is on and devices are connected). But actual connection is not working: unable to play music via BT, unable to discover a new BT device, notifications not coming through to a smartwatch, etc. Bluetooth devices continue to show as connected even if I power them off, and when I turn them back on, they won't reconnect.
I meet this problem every 1-2 hours, sometimes even 10-20 minutes. The only way to fix this problem - to turn off BT and then turn it on again. Or keep Wi-Fi always off.
I tried to use another Moto X (2014, same software build version), to pair and unpair devices, to clean cache and even do a factory reset (with and without backup restoring) – the problem is still here. That's weird but this problem start appears 2-3 weeks ago, before everything was just fine.
Phone: Moto X 2014 Pure Edition @ T-Mobile, Lollipop 5.1 (TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US)
Devices: Pebble Time, Pebble Time Steel, Ford SYNC2, Moto Stream.
Things I tried that didn't help: deleting and re-pairing devices, deleting all old device profiles, clearing cache, reflash, factory reset, safe mode, flash CM12.

BT HCI Logs:
A disconnect at 1:28pm
dropbox.com/s/q3pka5egagq3e5g/01_btsnoop_hci.log?dl=0
A disconnect at at 3:09pm (or so)
dropbox.com/s/f2kl4rowr12lypt/02_btsnoop_hci.log?dl=0

Same issue here with a VZW XT1096, since OTA to 5.1. Factory reset does not help.

Up

Same issue here, same device & carrier & software build version & Pebble Time Steel. As long as I'm constantly making use of a BT connection, it seems to stay alive just fine, but as soon as it sits idle for more than a couple minutes, the connection drops (according to the BT device, but not according to the phone). I've tried all the same things with the same total lack of success. I have nothing new/helpful to offer, but at least you're not suffering alone.

That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.

Just to say I have the same problem with a Pebble Time Steel and my 2014 Moto X. Have e to disable BT and dependable BT to get phone to connect to Pebble to only be dropped a few minutes later from Pebble side.
Lyre

AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
I'm having the same problems and have also had it "go away" for extended periods of time only to reappear after a day or two. Mine will drop the BT connection even if I'm actively listening to audio over my headset.

Registered because I'm having the same issue. I'm running stock 5.1, no root. The connection to my Pebble Time Steel is very unreliable. The Bluetooth settings thinks it's still connected, the Pebble Time app on my phone thinks it's still connected, but my watch shows no connection and there's no communication to or from my watch. Sometimes it'll work for hours just fine and then drop, sometimes it'll only be a few minutes. It seems to be when the phone screen is off. Turning BT off and on always fixes it, it'll immediately automatically reconnect and show it on the watch.
I've tried the Pebble troubleshooting online (factory reset & recovery mode on watch, uninstall Pebble Time app, forget pairing on all devices, remove all other BT apps, reboot phone, reinstall Pebble Time app, re-pair) but the problem remains.
In the past, I've had it where my Fitbit One seems to have dropped the connection. Since the sync is so infrequent, I don't notice it much but I did catch it where it hadn't synced in a few days. (That app was uninstalled while I try to figure the Pebble thing out)
Next step is factory reset on the phone, but it sounds like that's not a fix for some people. That, or design a watchface that sends a keep alive signal to the phone, which runs an app to reset the BT when the connection drops. Since it's still listed as connected, I don't think Tasker will fix it.

Same issue. My phone is a Verizon Moto X and I've tried factory reset. Hoping that whenever they update to 6 that it will fix the issue, but I'm ready to smash my Moto x over this

AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
While I hope your problem is "fixed" I would not be too hopeful. I have had this problem as long as I've had the phone. Sometimes it goes away for a while but it always returns. Right after I unlocked my bootloader and it did a complete factory reset the problem went away for a week but it eventually returned. I've seen similar problems reported with all the MX14 variations and nobody seems to have a solution. There was a thread on the Moto forums with folks reporting these issues to Moto but nothing ever came of it. Seems to be connected to wifi somehow because I don't seem to drop the BT connection if wifi is turned off. Not really a useful solution but it does seem to work. I just gave up and put a BT toggle button on my homescreen.

I had the same problem using marshmallow, I downgraded to 5.1 and it went to normal

Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?

jimbo0914 said:
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
Click to expand...
Click to collapse
Update: I changed over to Android M on CM13 and no longer have this issue. Nice not to have to power toggle the BT function a couple times a day anymore.
YMMV

Met the same problem after updating to Android M.
I often connect to BT during driving and after a few days working normally, my headset will be disconnect without any "notification".
My solution is to wipe cache, after that BT connection will work well for another few days.
Never met this issue in Android L, but I just love M so much.
Looking for better solution / fix.

I found this thread while searching for some solution for my BT+Android Wear problems. I have them since circa february / march 2017.
But today, I got a problem with non-Wear watch (Fossil Q Grant). I noticed my phone was locked even if I have smart lock set up. I checked fossil q app, the watch was connected, it received notifications so far. But in the phone settings, in smart lock, all my devices vanished. I checked the BT setting and saw the same. All my paired devices disappeared! It happened after nothing more than a restart, after my fossil lost connection earlier today and did not want to reconnect. So I restarted the phone.
This happened to me the second time already, but first time I somehow did not pay attention because I was frustrated by the Wear app problems and weekly factory resets to get my Wear watches working.
Could our issues be related? Some bluetooth software bug in phone? THIS IS PURE HELL!
Moto X4 cant come soon enough.