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!
Related
I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.
restart
humpty123 said:
I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.
Click to expand...
Click to collapse
I had the same problem and restarted my device. At first it displayed the same (incorrect) time, but then it quickly changed to the correct time. Mine was about 20mins ahead.
not fixed...
melscheld said:
I had the same problem and restarted my device. At first it displayed the same (incorrect) time, but then it quickly changed to the correct time. Mine was about 20mins ahead.
Click to expand...
Click to collapse
A few hours post-restart and it looks like the time is off again. It seems to be a cumulative effect...
Fix
humpty123 said:
I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.
Click to expand...
Click to collapse
I had the same issue - got mine a few days ago - after reading the post here I did a full device reset and set it up again with my phone. Been going for about a day and no issues. I wonder if it was an issues with having the new update right out of the box. Who knows. But if your having this issue a quick reset and setup and no issues. Will repost if something changes.
Moto 360: consistently wrong time now
alandashby said:
I had the same issue - got mine a few days ago - after reading the post here I did a full device reset and set it up again with my phone. Been going for about a day and no issues. I wonder if it was an issues with having the new update right out of the box. Who knows. But if your having this issue a quick reset and setup and no issues. Will repost if something changes.
Click to expand...
Click to collapse
I've had my Moto 360 for over a week now ... love it, recommend it to everyone I know
But I'm having the same problem now. My watch just won't keep time, and it's getting worse and worse (i.e. farther off of the real time). Everything else seems fine - I still get notifications so I know the watch is paired to my phone correctly, my phone's time is set by the carrier and remains correct throughout the day, etc. But now my Moto 360 will "slip" forwards in time by over 20 minutes! I have to double-check the time on my phone every time I check on my watch now, which needless to say is not a very good feature in a watch.
Restarting the watch and reconnecting in Android Wear does fix the time syncronization, but having to reboot my watch a couple times a day is not very desirable obviously. I've reset my watch (Reset device in settings) twice now, rebooted my phone, wiped Android Wear's settings on my phone and uninstalled then reinstalled it - same thing, incorrect time on my watch after anywhere from 1 to 6 hours.
It was perfectly fine when I first got it, and perfectly fine (even better!) after the update. It would be marginally less awful if I could re-sync the time without having to restart my watch, but disconnecting via Android Wear and/or turning Bluetooth off then on again, un-pairing the watch then re-pairing it, etc., all have no effect for me. Super lame :crying:
If I could manually set the time, I could deal with that.
I have time problems as well, but only....
chimpster said:
I've had my Moto 360 for over a week now ... love it, recommend it to everyone I know
But I'm having the same problem now. My watch just won't keep time, and it's getting worse and worse (i.e. farther off of the real time). Everything else seems fine - I still get notifications so I know the watch is paired to my phone correctly, my phone's time is set by the carrier and remains correct throughout the day, etc. But now my Moto 360 will "slip" forwards in time by over 20 minutes! I have to double-check the time on my phone every time I check on my watch now, which needless to say is not a very good feature in a watch.
Restarting the watch and reconnecting in Android Wear does fix the time syncronization, but having to reboot my watch a couple times a day is not very desirable obviously. I've reset my watch (Reset device in settings) twice now, rebooted my phone, wiped Android Wear's settings on my phone and uninstalled then reinstalled it - same thing, incorrect time on my watch after anywhere from 1 to 6 hours.
It was perfectly fine when I first got it, and perfectly fine (even better!) after the update. It would be marginally less awful if I could re-sync the time without having to restart my watch, but disconnecting via Android Wear and/or turning Bluetooth off then on again, un-pairing the watch then re-pairing it, etc., all have no effect for me. Super lame :crying:
If I could manually set the time, I could deal with that.
Click to expand...
Click to collapse
My time-problems comes only when I load any of the clockfaces from "Facer", then it goes a whole hour off.
Some watch faces do not move the hour hand until the second hand advances thru the full hour. Could that be the case?
I got the same problem!!
It was 15 mins ahead and all the sudden the time was corrected by itself...
humpty123 said:
I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.
Click to expand...
Click to collapse
Just restart the watch. Once it pairs again, the time will be set correctly.
sreymj said:
Just restart the watch. Once it pairs again, the time will be set correctly.
Click to expand...
Click to collapse
This is not a solution?? You can't look at the watch and not be able to trust the time, without checking your phone to see if it's right?? then sync again. It's a watch!!! It's it's core job. It should be able to be trusted to be right!!!
Mine has been out between 5 and 15 mins 3 times in the last 2 days, always fast. So not a refresh of screen issue.
I use Facer too, but even when I swipe to a standard watch face they are out too, until I do some sysnc with the phone.
I'm going to keep on a standard watch face today, and see what happens. Can't it really be facer? surly it just report the time on the device, will not change anything??
i have reported to Moto too, they know of no issue. Suggest everyone does the same.
On moto forum too;
https://forums.motorola.com/posts/75d3867b9d
Reads like it's a bug in latest firmware. Anyone got confirmation from Moto of this?
I just read on Android Forums that this may be related to wifi router software being out of date. YMMV.
Am I the only one having this problem? I'm so bummed out about how choppy and horrible my bluetooth is after I updated to Lollipop. Is there any fix for this aside from the workaround I've seen people do, keep the screen on?
FuzzRaven said:
Am I the only one having this problem? I'm so bummed out about how choppy and horrible my bluetooth is after I updated to Lollipop. Is there any fix for this aside from the workaround I've seen people do, keep the screen on?
Click to expand...
Click to collapse
Try a factory data reset from the settings menu. I know it's not the most desirable option but it seems to be the fix for other problems as well. It's a good idea to reset after a major update anyways.
Just streamed for an hour and no issues here. Reset your phone if you have issues.
My Bluetooth skipped a lot before the lollipop update. I will try out the Bluetooth in the car today and let you know what I'm experiencing.
dapimpinj said:
My Bluetooth skipped a lot before the lollipop update. I will try out the Bluetooth in the car today and let you know what I'm experiencing.
Click to expand...
Click to collapse
Yep I use bluetooth headset (Back Beat go 2) and it did that when my battery was low,on lolipop right after update it was happening for few minutes ,then it was ok.
I was using iPhone 5S before note4 and did not have this issue even once.
I wonder why that happens?
I just streamed for a couple hours. No skipping. I did a factory reset when I upgraded.
Do you have any devices near the phone? My work radio interferes with Bluetooth.
On a side note the phone auto connects to my Bluetooth adapter in my car.
If you trying to start a flame war, move along. It's mostly a software glitch and is easily fixable.
Verizon lollipop pdf mentioned that the OS would be updating/optimizing apps/their data for a few hours in background after the install.
Perhaps you should wait a few hours before the system has settled.
UPDATE:
Installed updates, no problems with BT music. No reset required.
After using it for several days, not just hours my bluetooth problem has resolved on its own! Thanks guys. Had me worried about it. No reset needed.
I am having the exact same problem, have tried all of the remedies to no avail. Never happened once when I was on Kitkat. It does it all the time now with Lollipop, I really hope they get this fixed.
Going to see if my wifes Note 4 on Lollipop does the same thing tonight and I'll report back.
A friend of mine just tried out Bluetooth from Note 4 to his car. It would cut out then when it came back it would speed up the same then go back to normal. Almost like it was trying to catch back up. He is on lollipop, Bluetooth works great for me on KK.
Mines doing the same.. no matter what bluetooth device or where I am, it'll "skip" every few minutes. Never did it before 5.0.1 update. Not sure where it started cause I used it factory stock for a couple months then did all the updates at once about a month ago. I haven't tried audio through the headphone jack, but I'm guessing that's fine since playing on the phone speaker is fine as well. I'll have to try the factory reset method and see if it fixes it.
Any other options or resolutions for this since it's been a few months since the last post?
stillthisguy said:
A friend of mine just tried out Bluetooth from Note 4 to his car. It would cut out then when it came back it would speed up the same then go back to normal. Almost like it was trying to catch back up. He is on lollipop, Bluetooth works great for me on KK.
Click to expand...
Click to collapse
This is the exact issue I'm having with my Note 4 using 5.1.1. No resolution yet
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.
Anyone else have the issue of their phone restarting when using Google Maps? The phone also happens to be plugged into Dash Car Charger as well.
Yes it has happened to me a few times.... Knock on wood I haven't had any issues recently. I used tasker to setup a profile so when I use my nav apps (maps, waze, etc) it turns off Bluetooth and sets the location mode to gps/device only vs. high accuracy. Not sure if there's any correlation, but I've gone about 1 week with no issues. I use waze to and from work daily.
Sent from my ONEPLUS A3000 using Tapatalk
I had that happen the other day while on the highway. Not the most convenient place to have to get things up and running again.
Not sure why it happened, but I hope it gets sorted out.
Sent from my ONEPLUS A3000 using Tapatalk
Never happened to me, commonly use both
Happened to me a few days after upgrading to OOS 3.2.2. On a secondary highway in mountains where signal was spotty. Have a feeling it was related to loss of LTE/4G signal while in maps.
Silly22 said:
Happened to me a few days after upgrading to OOS 3.2.2. On a secondary highway in mountains where signal was spotty. Have a feeling it was related to loss of LTE/4G signal while in maps.
Click to expand...
Click to collapse
I can also say this happened to me. Everytime it did happen I just so happened to "switch" over to edge network. After using data on the other sim, which has better coverage, it didn't happen.
Tested using one carrier sim on way up, and other carrier sim on way down. I was also using Bluetooth streaming Pandora the entire time each way. It never happened before oos 3.2.2, only Pandora would cut out when hitting the edge network.
Sent from the OnePlus 3...
making it "RAIN!"
acheney1990 said:
Anyone else have the issue of their phone restarting when using Google Maps? The phone also happens to be plugged into Dash Car Charger as well.
Click to expand...
Click to collapse
Same Here..
I've had this happen as well, but only when my phone has been plugged into a charger in my car.. it's possible that it has been shutting down thinking that something was going wrong with charging?
Rebooted when using Google Maps.
OnePlus 3 (3.2.2 OS)
Rebooted 3 times in a row
Was not charging at the time.
Rebooted when using Google Maps and Radardroid.
5-6 Reboots in 2 hours . No troubles in 6-7 hours before.
Reboots with and without original car charger.
Enviado desde mi ONEPLUS A3003
Same here. Restarts while driving
Maps in the background. BT on. The phone restarts when the screen timeout function tries to shut down the display.
3.2.4 unlocked, rooted, Xposed.
That's a little bit disappointment...
I've occured this, too
I found case :
1. car-charging
2. use GPS
3. connect Bluetooth.
when I don't charging in car, that was never again.
jsuch2362 said:
I've occured this, too
I found case :
1. car-charging
2. use GPS
3. connect Bluetooth.
when I don't charging in car, that was never again.
Click to expand...
Click to collapse
Mine restarts without being charged in the car
EP2008 said:
Not the most convenient place to have to get things up and running again.
Click to expand...
Click to collapse
Yeah...especially since even if you have a fingerprint lock, you still have to enter your password after a reboot. OOS 3.2.4 fixed some of these issues, at least according to the change log. But I mostly use custom ROMs (Resurrection Remix at the moment), so I haven't tested OOS 3.2.4 yet.
Edit: well, never mind about 3.2.4 fixing the issue:
geminium said:
Same here. Restarts while driving
...
3.2.4 unlocked, rooted, Xposed.
That's a little bit disappointment...
Click to expand...
Click to collapse
You know, there is actually another thread about this, if you dig around the Q&A section. Now, several people said they thought random rebooting is a hardware issue. The thing is, I get random reboots too, but it only happens while driving, BT connected, Pandora playing, and navigation going. Outside that one particular scenario, I have never had a random reboot. I don't call myself an expert, but that doesn't sound like a hardware failure to me if it only happens under one (very particular) set of circumstances.
Pandemic187 said:
You know, there is actually another thread about this, if you dig around the Q&A section. Now, several people said they thought random rebooting is a hardware issue. The thing is, I get random reboots too, but it only happens while driving, BT connected, Pandora playing, and navigation going. Outside that one particular scenario, I have never had a random reboot. I don't call myself an expert, but that doesn't sound like a hardware failure to me if it only happens under one (very particular) set of circumstances.
Click to expand...
Click to collapse
agree. i tried to make this problem reoccured at home (meaning bt on; played music over the bt; maps on) -- no restarts.
smthng telling me it's related to gps. BUT i haven't had this problem before 3.2.4 update.
i only hope the OP team will take a deep look into this.
me too, while using Android Auto (so the phone is plugged in and charging, and connected by bluetooth, if it matters)
once it starts it will repeatedly reboot every few minutes.
If I close maps and clear cache it seems to help.
So what do we do?
I have the same restarting problem, using Waze as satnav and gps,on non Dash charger in car, and with 3.2.4 update. What can we do to get Oneplus to take this problem seriously?
I have exactly the same set up and exactly the same problem: Waze, OxygenOS 3.2.4, with or with out charger in the car.
This problem only started yesterday. On my 1 hour commute last night the phone restarted 5 time. On the 1 hour commute this morning it rebooted 5 times in 30 mins before I gave up and drove without it.
Anyone found a fix for this?
Maps running without issues
Maps ver9.36.1
nottheusualtoday said:
I have the same restarting problem, using Waze as satnav and gps,on non Dash charger in car, and with 3.2.4 update. What can we do to get Oneplus to take this problem seriously?
Click to expand...
Click to collapse
Well, I don't know about what OP is going to do, but for me, the problem seems to have been fixed by EX Kernel.
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.