Develop Bugs

[Q] Anyone else getting frequent disconnects (3-4 times per day)

I haven't been able to get through one day without having to do a complete reset of my 360. It will disconnect from my phone about 3 or 4 times per day and the solution is some random combination of massaging the watch and Nexus 5 through restarting the phone/watch, connecting/disconnecting in the Android Wear app, or ultimately resetting the watch and going through the whole setup again. I am using a Nexus 5 with CM11 on it. Is anyone else having this issue?

Using an ancient GS2 with CM11 and get an issue where my bluetooth turns off and can't be turned on so I have to restart, but I think my bluetooth module is damaged, your phone bluetooth doesn't turn off does it?

v3ngence said:
Using an ancient GS2 with CM11 and get an issue where my bluetooth turns off and can't be turned on so I have to restart, but I think my bluetooth module is damaged, your phone bluetooth doesn't turn off does it?
Click to expand...
Click to collapse
No, I don't have that problem.

mzimmer88 said:
I haven't been able to get through one day without having to do a complete reset of my 360. It will disconnect from my phone about 3 or 4 times per day and the solution is some random combination of massaging the watch and Nexus 5 through restarting the phone/watch, connecting/disconnecting in the Android Wear app, or ultimately resetting the watch and going through the whole setup again. I am using a Nexus 5 with CM11 on it. Is anyone else having this issue?
Click to expand...
Click to collapse
I am having a few maybe 3 or 4 disconnects but the watch reconnects for me.

I get about 1-2 disconnects a day but it reconnects immediately afterwards.

Nexus 5 CM 11 user with the same problem, well, erm, had a problem...-ish.
I've made a couple posts on the is problem and created a Log of my first day here.
I made this post here telling an XDA member how to remedy their disconnects:
When you lose connection with your 360, if you open the Wear app on your phone, does it still say connected? If so, try and reconnect with Android Wear to your 360, does it not reconnect? (This is happening to me)
Try reconnecting on Wear, your 360 may say that you've lost connection (Cloud with a slash icon). Try reconnecting again from the Wear app, if that doesn't work, try repairing your 360, that should work. (4/5 times it works for me)
Resetting does seem to work as well, I did it yesterday and went 16 hours without a disconnect, previous day was 7 in 6 hours. But this morning I walked away from my 360 with my phone and lost connection and it started disconnecting again.
Click to expand...
Click to collapse
When I did a reset of my 360, it got my through the day without any disconnects the count not reconnect. But I think I had one or two minor ones where all I needed to do was wake my phone and it reconnected.
Now, the final solution? Yesterday CM11 M10 came out and if you have upgraded, I highly suggest making a backup and doing so. It seems to of fixed the issues on my N5. I made a post here preCM10 (Before it came out) and decided it was probably a BT problem with CM, not the 360 and I think I was right.
The BT fix apparently made it into CM11 M10 and I seem to be doing alright. But Battery life kind of sucks still, I only made it 7 hours yesterday with moderate usage, so I'm starting to suspect that I'm still getting some kind of disconnect, but it's reconnecting instead of hanging, thus decimating my battery life.
My Nexus is also seeing pretty bad battery life since I started using my 360. Granted, it's never been the best at making it through the day, but it definitely seems to drain about 20% faster.

what about stock Nexus 5?
B3RL1N said:
Nexus 5 CM 11 user with the same problem, well, erm, had a problem...-ish.
[...]
.
Click to expand...
Click to collapse
I use a N5 stock Android 4.4.4
Will I have the same problem or is it linked to the CM thing?
Thanks in advance and, by the way, great graphic analysis, dude!

Galaxy S4 here
CM11 had constant connection problems. Always showed "Connected, running sync loop" in the Wear notification.
I switched to a GPE ROM and haven't had one disconnect.

I experienced 5-6 disconnects a day, at least, before the update. Afterwards, it has disconnected once, but I was in a very crowded area, and it could have simply had a lot of electronic interference. Otherwise, the update has definitely made a difference. Wear Aware is actually useful now!

Random disconnects when right next to phone

Anyone else having random disconnects when right by the phone? Disconnecting and reconnecting via the wear app on my phone doesn't seem to fix the issue either. Could it be that I'm on a network extender attached to my wifi for cell signal boosting because it appears to sync the apps, just nothing internet related.

I'm having the same issues. Just got mine yesterday and I have frequent connection drops and have to reset Bluetooth on my phone to reconnect. The android wear app says that it is connecting, but no matter what I do it won't pair up again until I reset that Bluetooth.
I saw somewhere else someone said they had a similar issue on CyanogenMod. I'm running the latest CM11 nightly on a VZW S4. What phone and ROM are you using? May help us troubleshoot.
Sent from my SCH-I545 using XDA Free mobile app

The GPE 4.4.4 on GS4.
I'll say "Ok, Google Call X" and it just does the spinning circle and soon after disconnected. Resetting bluetooth, restarting watch and phone does nothing for it. I'm thinking maybe it's the phone rom. I may go back to stock and try completely stock with it just to rule out any 3rd party bluetooth issues and what not.

Regarding the spinning circle after saying something after "OK Google", ...
I had this too. To help diagnose, I took my phone out and said "OK Google" and the phone didn't respond. So I concluded it was the phone. To fix this, I kill'ed the Google process and let it start again by trying "OK Google" on the phone again. After that works, I then try using the Moto 360 and then it responds.
The "OK Google" functionality makes up a big chunk of what the Moto 360 can do (and perhaps all other Android Wear watches). Without a reliable Google process working, that functionality falls apart.
In my case, my ROM was not quite right. I ended up doing a factory reset and re-flashing. I'm on Note 3 N900T DNF9. So far so good. But as soon as I see the spinning circle, I don't even wait. I test it by saying "OK Google" followed by "weather".
Dennis

Notifications not showing

Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks

Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk

nijom said:
Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Happens with ever ROM I've tried

stevoh84 said:
Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers

Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
jschill31 said:
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers
Click to expand...
Click to collapse

stevoh84 said:
Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
Click to expand...
Click to collapse
After 4 Android Wear updates they finally fixed the connection issue. I sent them several bug reports and I swear they didn't even look at them.
Cherrs
Nexus 6

I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?

Ramer said:
I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?
Click to expand...
Click to collapse
For anyone who runs across this at some point, I solved the problem (at least for me). I unistalled Light Manager and now I'm getting all notifications.

Arrrgh mine has started doing this again! It had been fine for a few weeks. Seriously needs sorting out

I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.

aayushjoshi said:
I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.
Click to expand...
Click to collapse
Still isn't resolved for me sadly and restarting the phone doesn't work. I'm just flashing a new ROM to see if that helps. My watch has randomly been saying Google Play Services isn't installed on the phone when it is. Strange happenings here!

I have exactly the same problem! Saying Google play services are not installed, no whatsapp or text notifications until I get an email then they mysteriously appear. also if I toggle notification to priority and back they appear. doing my head in

You need to restart the phone and the watch, not just the phone.
Also can try removing your phone from your watch's bluetooth pair list then also "forget" the watch in your phone's bluetooth menu, then re-pair the two. Should work no problem after that.
I find this only happens if i stray away too far from either device or one of them gets restarted for some reason.. but yeah, restarting both the phone and the watch, removing the phone and watch from both bluetooth lists, and then re pairing, has fixed it every time for me. No having to factory reset the watch or reflash rom or anything drastic like that.
Now if you're phone is always in your pocket/purse which is on you all the time and the watch is on your wrist too and it just drops connection randomly... then i'd say something is messed up with your watch or phone.

DND mode turns on and off repeatedly

I am curious whether anyone else is having this problem as I cannot find anything about it online. I have an issue that my Pixel XL starts turning DND mode on and off repeatedly with no interaction from me. It cycles back and forth every second or so and the DND icon comes and goes from the notification bar as it does this. This also seems to run down the battery and heat up the phone. No clearing out of applications seems to fix this but if I reboot the phone it goes away. I should also note that I find my Pixel goes into DND mode all the time unintentionally . About half the time I take it out to make a call I see that DND is on. This happens even when it is not cycling like this repeatedly. Anyone else having problems like this?

Are they any DND rules setup that might be triggering? Do you have any other automation app installed, like Tasker, that could be causing thisre

I have seen this happen on my phone a few times - during the day, which is against the schedule that I set. It's not often enough to bother me, but it is somewhat worrisome.
These bugs man!

also experienced it. i wondered if it was impacted by android wear because i dont see it when i dont have my watch on.
i also noticed it goes into that DND mode when you make a call. so maybe it's not coming out of it when you hang up

DND is flaky
dr_gibberish said:
I am curious whether anyone else is having this problem as I cannot find anything about it online. I have an issue that my Pixel XL starts turning DND mode on and off repeatedly with no interaction from me. It cycles back and forth every second or so and the DND icon comes and goes from the notification bar as it does this. This also seems to run down the battery and heat up the phone. No clearing out of applications seems to fix this but if I reboot the phone it goes away. I should also note that I find my Pixel goes into DND mode all the time unintentionally . About half the time I take it out to make a call I see that DND is on. This happens even when it is not cycling like this repeatedly. Anyone else having problems like this?
Click to expand...
Click to collapse
I tried using DND when i first got the phone but it was inconsistent and flaky.
Went back to silence premium and havent had any issues since.

i have the same problem, but also using android wear.. very odd.

I also have a smartwatch connected. Perhaps the bug is related to Android Wear.

nabbed said:
I also have a smartwatch connected. Perhaps the bug is related to Android Wear.
Click to expand...
Click to collapse
So that's really interesting. I have a first gen Asus Zenwatch and I removed the Zenwatch Manager app late last week and the problem appears to have stopped. I still get the occasional DND turning on when I don't think I have activated it, but the cycling back and forth appears to have stopped. I should also note that I apparently got an upgrade to the watch firmware last week (it said upgrading when I woke up) so this could have resolved the issue as well. Regardless it does not seem to have happened in several days.

Android wear related I'm sure. When I go to hit volume down it says dnd- android wear
Sent from my Pixel XL using Tapatalk

Im using android wear and i am seeing the same problem.

Same here. Huawei watch.
Sent from my Pixel XL using XDA-Developers mobile app

Only notice it when on phone call. Zenwatch 2. But, currently my watch isn't paired with phone.

Happens with Samsung Gear Fit 2 as well.
Sent from my Pixel XL using XDA Labs

Here to add to the Android wear list, using an LG urbane.

Someone in another thread suggested deleting the three default automatic rules for do not disturb. I did that a couple days ago and haven't had the problem since. I have an Android Wear watch connected too.

Happens to me also, while connected to my Misfit Ray.

Bluetooth turning off since NMF26U

Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.

I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.

nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk

thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).

I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.

millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.

I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.

Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.

Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk

I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently

I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.

I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!

Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!

t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!

Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.

BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.

I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.

Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.

I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol

Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.