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
Related
Sometimes my Moto will recognize my voice as I'm saying it an execute the command quick, like I think it should all the time.
Sometimes I'll say something and it'll take forever, and sometimes completely fail. I can then open my phone and do a voice command with immediate results, so it's not my connection.
I removed commander and autovoice which seemed to help some at first, but I'm not sure it made a long term improvement. Removing some apps I didn't use from the watch also seemed to help some, freeing up RAM.
Is too much of the voice processing happening on the watch instead of the phone? Or is there a bluetooth issue? My S4 processes voice very quick almost always.
Anyone else experiencing this? I can't seem to find any time this does it more than others. Quit or loud room, doesn't seem to matter.
Any suggestions would be a great help. I use the moto for voice commands a lot and it defeats the purpose of not pulling my phone out when it takes so long.
ThePublisher said:
Or is there a bluetooth issue?
Click to expand...
Click to collapse
That one.
My old, decrepit galaxy s2 has what you describe but worse, sometimes phone bluetooth just turns off and can't turn back on... but mine is probably broken and dying.
Try re-pairing, cycling bluetooth on phone, or changing roms to one with a better bluetooth stack
If your S4 processes it fine, then it certainly is the connection between it and the watch. If cycling the antenna doesn't work try resetting either device, and if you're running a custom ROM check its dev thread for any BT related issues.
Going to try flashing an updated ROM. Currently on GoldenEye NB1 and going to update. I will let you know if this fixes the issue. Thank you two for your help.
Problem fixed
So I deleted the 360 from my phone's bluetooth. Then reset the 360. Upon reconnecting this time it worked great and has been excellent in recognition for a couple days now. Not sure what the difference is now, but it kept me from flashing my phone.
Anybody else using a moto 360 with their nexus 6 on Verizon?
I am having connectivity problems between the watch and the phone. Sometimes I speak into the watch and Google is thinking, thinking, and then stops. Like it can't reach the phone. Anyone else?
I don't know if this is a Nexus 6 on Verizon, nexus 6 in general, or moto 360 problem.
As I'm reading about this, it seems like this might be not only a Nexus 6 and Moto 360 problem, but an Android Wear/ Lollipop problem. Hopefully if 5.1 comes out soon, it'll fix this.
No issues here since xmas with my 6.
Thanks for the reply. Weird.
funkpod said:
Anybody else using a moto 360 with their nexus 6 on Verizon?
I am having connectivity problems between the watch and the phone. Sometimes I speak into the watch and Google is thinking, thinking, and then stops. Like it can't reach the phone. Anyone else?
I don't know if this is a Nexus 6 on Verizon, nexus 6 in general, or moto 360 problem.
Click to expand...
Click to collapse
This definitely happens to me too. After giving it a command the little circle keeps spinning until it comes back displaying "offline" even though I'm in an area with good reception. Sometimes though it just keeps spinning until I eventually swipe right to dismiss it and try again. Sometimes when trying to get directions from my watch it'll tell me to open Maps on my phone in order to continue.
An issue that persists for me is immediately upon plugging my Nexus 6 into its charger my 360 disconnects. I notice this immediately because the lost phone notification pops up on my watch and it vibrates sporadically. This is an issue that has really puzzled me because I can't tell what it could possibly be related to.
I used to have issues with text notifications not being pushed, but this has stopped happening. From time to time my watch will disconnect from my phone for seemingly no reason, and I'll get a "did you leave your phone?" notification. This happened today even, while I was using my phone. Other times when I walk out of range and then walk back into range it won't automatically reconnect. When this happens I have to open Android Wear, select Disconnect (even though Android wear will display "connecting...) And then Connect, and it'll connect again.
Almost half the time I go to send a text by voice I get the issue the OP mentioned, where the circle keeps spinning and nothing happens, or "offline" is displayed. I would really love a solution to this as sending texts is a core feature of Android Wear, and it totally defeats the purpose of the smart watch if it's supposed to save you from having to pull out your phone.
BTW I have an AT&T Nexus 6
Sent from my Nexus 6 using XDA Free mobile app
No issue for me, mine working perfectly but mine is international edition Nexus 6 and running CM 12 ROM.
osiris010 said:
This definitely happens to me too. After giving it a command the little circle keeps spinning until it comes back displaying "offline" even though I'm in an area with good reception. Sometimes though it just keeps spinning until I eventually swipe right to dismiss it and try again. Sometimes when trying to get directions from my watch it'll tell me to open Maps on my phone in order to continue.
An issue that persists for me is immediately upon plugging my Nexus 6 into its charger my 360 disconnects. I notice this immediately because the lost phone notification pops up on my watch and it vibrates sporadically. This is an issue that has really puzzled me because I can't tell what it could possibly be related to.
I used to have issues with text notifications not being pushed, but this has stopped happening. From time to time my watch will disconnect from my phone for seemingly no reason, and I'll get a "did you leave your phone?" notification. This happened today even, while I was using my phone. Other times when I walk out of range and then walk back into range it won't automatically reconnect. When this happens I have to open Android Wear, select Disconnect (even though Android wear will display "connecting...) And then Connect, and it'll connect again.
Almost half the time I go to send a text by voice I get the issue the OP mentioned, where the circle keeps spinning and nothing happens, or "offline" is displayed. I would really love a solution to this as sending texts is a core feature of Android Wear, and it totally defeats the purpose of the smart watch if it's supposed to save you from having to pull out your phone.
BTW I have an AT&T Nexus 6
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for all that input. I definitely see the beginning part as being the problem that I am having.
My 360 and Nexus 6 don't seem to have an issue.
Have you tried updating Google Play Services?
kmcla said:
My 360 and Nexus 6 don't seem to have an issue.
Have you tried updating Google Play Services?
Click to expand...
Click to collapse
Everything appears to be up to date...
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.
My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?
gadgetgaz said:
My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?
Click to expand...
Click to collapse
No fixes but same problems here
I'm having the same issue also very frequently with WiFi dropping all the time. These two reasons are linked from what I been told. Google telling me to RMA. The pain of that
Mine has done this with my Gear S3 watch since I first got the phone a few months ago, it had me seriously considering returning it for a while. Sometimes it would just disconnect from the bluetooth, but often it would unpair causing me to have to go through the whole set up process again. It did this on Android O, various DP builds of P but so far (touch wood) has been good with the latest version of the Samsung software and Android P.
I'm having the same issues as well and currently searching for answers.
I'm getting tired of it, wifi disconnects and reconnects or flat out doesn't work, mobile data flat out doesn't work most times unless I reboot the phone for either of them to work. I'm rebooting about 4-5 times a day just to get either working. I'm at my wit's end and about to get rid of this thing as soon as I can.
I generally love this phone, but I'm seeing similar issues. WiFi says connected, but I don't get any data. I thought it was my network at first, but noticed other devices working. Tested network while my phone was acting like this, and my WiFi and network were working great.
Separately, my phone sometimes won't dial out. I use Google Voice, so I'm not sure if it's the phone or Google that's not working, but it's very frustrating. The dial screen comes up, then immediately disappears. No errors or anything to indicate that it ran into problems. The dial screen just flashes. Rebooting seems to fix that. But all very frustrating. Especially when I'm trying to call someone while driving. I don't want to have to look at the screen. I want to be able to tell the phone to call and know it's going to do it. Instead, I tell it to call, it confirms it will call, then nothing.
chris.arney said:
I generally love this phone, but I'm seeing similar issues. WiFi says connected, but I don't get any data. I thought it was my network at first, but noticed other devices working. Tested network while my phone was acting like this, and my WiFi and network were working great.
Separately, my phone sometimes won't dial out. I use Google Voice, so I'm not sure if it's the phone or Google that's not working, but it's very frustrating. The dial screen comes up, then immediately disappears. No errors or anything to indicate that it ran into problems. The dial screen just flashes. Rebooting seems to fix that. But all very frustrating. Especially when I'm trying to call someone while driving. I don't want to have to look at the screen. I want to be able to tell the phone to call and know it's going to do it. Instead, I tell it to call, it confirms it will call, then nothing.
Click to expand...
Click to collapse
I'm getting the same problems and it's annoying the hell out of me I'm paying this phone off but I'm about to just ditch it buy a pocofone and just pay im this off separately or try to trade it in for a one plus 6T