Related
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
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.
EDIT: Doing a factory reset will solve many of the issues mentioned, specially the battery drain, I suggest you to do a factory reset and do the initial setup, then leave the watch on charge overnight, the next day restart both your phone and your watch (don't take the watch of the charger yet), wait 20 minutes and then unplug the watch from the wall and just use it as usual, you should see a huge battery improvement. I did.
Bugs I noticed so far, please check if you can reproduce these yourself and let us know yours so we make a list. This is a thread I started on Asus forums and it might help ppl here to to iron some of these out.
1- After a call (accepted or not) the blue MIC image stays on the watch even after the call has ended (this happened on AW 1.5 already) - Multiple reports
2 - Watch vibrates non-stop during a call, even if you picked the call allready on the phone, the watch will start vibrating with no reason. - Multiple reports - SUPER ANNOYING!!!
3 - Battery drains much faster, with same usage I end a day with 30% on AW 2.0 instead of 65 to 70% on AW 1.5 - Multiple reports
4 - When not trough Wifi the "ok Google" command gives an error saying Google is out of reach, restarting phone fixes it, but if connection of phone and watch is broken, the "OK Google" voice command (or long-pressing the main button) won't work again, nor will other apps like the App store - Multiple reports
5 - if I pick one phone number with the "text message' icon, the watch does not go into listening mode to get the text content. Instead it keep on loading with the loading icon and no message can be sent out. However if I use "OK Google" command instead of go thru the Contact app I can send text messages - One report
6 - Turning theater mode on seems to break the alarm. Thankfully the alarm will still go off, but the screen becomes unresponsive. Clicking dismiss or snooze won't work. Restart of watch is needed. Only happens when the watch is in theater mode. - One report
7 - Huge delay when phone receives a call to when watch shoes that call. - Multiple reports.
8 - Dowload speed on watch is most of the times terrible slow - Multiple reports
9 - "Ok Google" actions takes much longer to activate than on previous version - Multiple reports
10 - WhatsApp-ing someone is impossible it keeps asking "to whom?" indefinitely. - One report
11 - Pairing seems to be having problems - One report
12 - UI losing frames - One report
13 - Keyboard missing some symbols - Multiple reports
1. This occurred to me on 1.5 but hasn't reproduced it for me on 2.0
3. Battery draining around 4% per hour. Seems very similar to 1.5
9. Seems about the same to me.
Clean cache!
None of them, except for keyboard symbols.
All the same issues until I clean the cache.
1. Turn off the watch
2. Press the main and bottom button about 15 seconds "asus logo and reboot bootloader message apears" then a green android with a "!" symbol appears.
3. swipe on the screen
4. a bootloader menu appears, then swipe up or down until "Clear cache" is selected, then swipe right.
5. after is done swipe to select "reboot to sytem" swipe right and you're done.
Many problems fixed even the google assistant lag.
1. Works good, no issue
2. Works good, no issue
3. Battery almost same as 1.5
The rest i do not use or no problems with.
Annoying : swipe left change to change watchface. I do not like it this way
I received my watch off of Amazon two days ago, let it go through it's initial updates and then took the 2.0 update. It seemed to be working okay, but I did an FDR as I often do after major updates and it completely screwed the watch up. It reboots every five minutes now.
I unlocked the bootloader, downgraded back to 1.5 and tried the process over again to no avail. Not sure if it was the upgrade or just a dud watch, but I'm glad I'm still within my return policy deadline.
mkengel said:
None of them, except for keyboard symbols.
All the same issues until I clean the cache.
1. Turn off the watch
2. Press the main and bottom button about 15 seconds "asus logo and reboot bootloader message apears" then a green android with a "!" symbol appears.
3. swipe on the screen
4. a bootloader menu appears, then swipe up or down until "Clear cache" is selected, then swipe right.
5. after is done swipe to select "reboot to sytem" swipe right and you're done.
Many problems fixed even the google assistant lag.
Click to expand...
Click to collapse
I did this now, if it fixes the bugs listed, well, fantastic.
mkengel said:
None of them, except for keyboard symbols.
All the same issues until I clean the cache.
1. Turn off the watch
2. Press the main and bottom button about 15 seconds "asus logo and reboot bootloader message apears" then a green android with a "!" symbol appears.
3. swipe on the screen
4. a bootloader menu appears, then swipe up or down until "Clear cache" is selected, then swipe right.
5. after is done swipe to select "reboot to sytem" swipe right and you're done.
Many problems fixed even the google assistant lag.
Click to expand...
Click to collapse
I did this too. Helped with a lot of the lag issues
I've tried this and still having terrible battery after wear 2.0 upgrade. I can barely make it through a day.
c_86 said:
I did this too. Helped with a lot of the lag issues
Click to expand...
Click to collapse
I recommend doing what @artur777 explains bellow, it fixed some of the issues for me, to the point where I'll no longer go back to AW1.5, even so, some bugs persist and won't be solved by the factory reset.
Hi Everyone,
I highly recommend doing a factory reset (see my post from 2017/07/24). It solved many problems for me and the watch OS works now like brand new! Give it a try and maybe it will do the trick for some of you too. It will definitely not make things worse, I think.
You can restore your watch OS to the factory settings either on your watch or on your phone through the Android Wear app:
On the watch:
Settings -> System -> Disconnect & reset
On the Android Wear app (phone):
Settings -> tap ASUS ZenWatch 3 under Device settings -> UNPAIR WATCH (at the bottom of the screen)
The process of resetting your watch will take a while until your watch is ready to be paired with your phone again. In my case it took about 15 minutes, so don't panic if it takes too long.
Mind that unpairing your watch from your phone will reset it to the factory settings and delete all the apps and settings you had configured on your watch. The fatory reset will NOT roll your watch OS back to AW1.5 though, but it will flash the AW2.0 to it's original state as if it were freshly installed on a brand new device.
Once the watch OS has been successfully restored (you should see this on the screen) you will need to pair your watch with your phone again through the Android Wear app and re-install all the apps and set the settings up to your liking and preference.
Good luck to everyone!
When i press the do not disturb option the phone does not turn silent where in 1.5 it used to make it silent...any suggestion?
One more Bug
Reminders notification, marked as complet, causing not to be seen in watch or phone. In some exceptions when there is a bad comunication with phone the reminder stay a few seconds.
Google is aware of this bug, and they are working on it with a promise to fix it soon with an update to their google app. (Working right in wear 1.5).
By the way many bugs listed, happen to me, but were fixed with a factory reset in watch, unpair and erase (forget any bluetooth reference) and clear dalvik cache in phone.
Some things doesnt improve immediately like google now or battery.
But I have to say that I own a zenwatch 2 too. Recently updated to wear 2.0 and it works better maybe in every task by example google now, speed downloading apps and battery so far (today from 8:15 to 22:05 65 % available, screen always on brightness level 3, 21 notifications and 1 hour monitoring google fit activities, 3 apps updated (13 MB))
So I think Asus need to put attention on whats going on.
I will make a comparison video in 2 days. Zenwatch 2 vs. Zenwatch 3 both android wear 2.0
Have a good time
My watch is not updating the day and date on the watchface unless I change watchfaces or reset the watch. I.E: It's saturday and it shows Friday. It will keep showing Friday for days unless I change watchfaces or reset.
Does anyone else have this problem as well?
battery drain formost!
my battery drains very fast. Faster than aw 1.5
---------- Post added at 02:52 PM ---------- Previous post was at 02:49 PM ----------
battery drain totally unacceptable in AW 2.0
MK24ever said:
Bugs I noticed so far, please check if you can reproduce these yourself and let us know yours so we make a list. This is a thread I started on Asus forums and it might help ppl here to to iron some of these out.
1- After a call (accepted or not) the blue MIC image stays on the watch even after the call has ended (this happened on AW 1.5 already) - Multiple reports
2 - Watch vibrates non-stop during a call, even if you picked the call allready on the phone, the watch will start vibrating with no reason. - Multiple reports - SUPER ANNOYING!!!
3 - Battery drains much faster, with same usage I end a day with 30% on AW 2.0 instead of 65 to 70% on AW 1.5 - Multiple reports
4 - When not trough Wifi the "ok Google" command gives an error saying Google is out of reach, restarting phone fixes it, but if connection of phone and watch is broken, the "OK Google" voice command (or long-pressing the main button) won't work again, nor will other apps like the App store - Multiple reports
5 - if I pick one phone number with the "text message' icon, the watch does not go into listening mode to get the text content. Instead it keep on loading with the loading icon and no message can be sent out. However if I use "OK Google" command instead of go thru the Contact app I can send text messages - One report
6 - Turning theater mode on seems to break the alarm. Thankfully the alarm will still go off, but the screen becomes unresponsive. Clicking dismiss or snooze won't work. Restart of watch is needed. Only happens when the watch is in theater mode. - One report
7 - Huge delay when phone receives a call to when watch shoes that call. - Multiple reports.
8 - Dowload speed on watch is most of the times terrible slow - Multiple reports
9 - "Ok Google" actions takes much longer to activate than on previous version - Multiple reports
10 - WhatsApp-ing someone is impossible it keeps asking "to whom?" indefinitely. - One report
11 - Pairing seems to be having problems - One report
12 - UI losing frames - One report
13 - Keyboard missing some symbols - Multiple reports
Click to expand...
Click to collapse
Doing a factory reset will solve many of the issues mentioned, specially the battery drain, I suggest you to do a factory reset and do the initial setup, then leave the watch on charge overnight, the next day restart both your phone and your watch (don't take the watch of the charger yet), wait 20 minutes and then unplug the watch from the wall and just use it as usual, you should see a huge battery improvement. I did.
I have seen some of these issues on my watch running AW 2.0.
The delay with the calls is the most annoying one. Also if u have wrist gestures on and u turn your wrist when the Call Ui is up, the gestures removes the notifcation and u have to answer call on phone.
I experience another bug. I have a pattern password set on my watch and I placed watch in Eco mode. After the watch is locked in Eco mode, the screen is unresponsive to enter the pattern and none of the buttons work. A restart is neccesary.
Also. I have disabled Smart replies, yet whenever i go in whatsapp chats there are atleast 5 smart reply otions.
hi all, just got this watch, so far so good. only problem is that my watch does NOT notify me when I have an incoming call - except if I set the watch to play voice on incoming call. I'd rather not do this, just the straight up notification. does anyone know how I can adjust this? thanks!
---------- Post added at 08:57 PM ---------- Previous post was at 08:38 PM ----------
jco23 said:
hi all, just got this watch, so far so good. only problem is that my watch does NOT notify me when I have an incoming call - except if I set the watch to play voice on incoming call. I'd rather not do this, just the straight up notification. does anyone know how I can adjust this? thanks!
Click to expand...
Click to collapse
Disregard, it works now.
I had to give full permission to Android Wear.
Sent from my DROID Turbo using XDA-Developers Legacy app
Hello friends!!
Someone has been able to resolve incoming call delay
MK24ever said:
Doing a factory reset will solve many of the issues mentioned, specially the battery drain, I suggest you to do a factory reset and do the initial setup, then leave the watch on charge overnight, the next day restart both your phone and your watch (don't take the watch of the charger yet), wait 20 minutes and then unplug the watch from the wall and just use it as usual, you should see a huge battery improvement. I did.
Click to expand...
Click to collapse
What do you recommend to do factory restoration ?; only "clear data" or "Factory reset", help me pls
Davis26 said:
What do you recommend to do factory restoration ?; only "clear data" or "Factory reset", help me pls
Click to expand...
Click to collapse
You can restore your watch OS to the factory settings either on your watch or on your phone through the Android Wear app:
On the watch:
Settings -> System -> Disconnect & reset
On the Android Wear app (phone):
Settings -> tap ASUS ZenWatch 3 under Device settings -> UNPAIR WATCH (at the bottom of the screen)
The process of resetting your watch will take a while until your watch is ready to be paired with your phone again. In my case it took about 15 minutes, so don't panic if it takes too long.
Mind that unpairing your watch from your phone will reset it to the factory settings and delete all the apps and settings you had configured on your watch. The fatory reset will NOT roll your watch OS back to AW1.5 though, but it will flash the AW2.0 to it's original state as if it were freshly installed on a brand new device.
Once the watch OS has been successfully restored (you should see this on the screen) you will need to pair your watch with your phone again through the Android Wear app and re-install all the apps and set the settings up to your liking and preference.
MK24ever said:
You can restore your watch OS to the factory settings either on your watch or on your phone through the Android Wear app:
On the watch:
Settings -> System -> Disconnect & reset
On the Android Wear app (phone):
Settings -> tap ASUS ZenWatch 3 under Device settings -> UNPAIR WATCH (at the bottom of the screen)
The process of resetting your watch will take a while until your watch is ready to be paired with your phone again. In my case it took about 15 minutes, so don't panic if it takes too long.
Mind that unpairing your watch from your phone will reset it to the factory settings and delete all the apps and settings you had configured on your watch. The fatory reset will NOT roll your watch OS back to AW1.5 though, but it will flash the AW2.0 to it's original state as if it were freshly installed on a brand new device.
Once the watch OS has been successfully restored (you should see this on the screen) you will need to pair your watch with your phone again through the Android Wear app and re-install all the apps and set the settings up to your liking and preference.
Click to expand...
Click to collapse
I appreciate your help, do not recommend doing it from the boot loader?
Again thank you
Hi, a few months ago I've noticed that when I try to turn on bluetooth (which is usually turned off) everything freezes the moment I 'click' on the turn on/off switch. After the freeze it takes around one-two minutes to restart the phone and then I can normally turn the bluetooth on.
The strange thing is that I can turn it off and on then and it will work, but when I turn it off and leave it off for a few days, and then try to turn it on the phone will freeze again...
Did anyone had the same issue?
Android version: 7.0 (B394)
I installed B395, but the problem hasn't gone away. Anyway, for the first time after this 'freeze' the message box saying that 'the interface app stopped working' showed up and I could 'stop' the interface app.
However, the update did not solve the problem.
Same problem here did you find a solution?
Same problem here for years! Android 7.0. Did anyone found any solution yet?
My build number is EVA-L09C432B505. Stock firmware, regulary updated.
@zozo77, Have you regularly updated your stock firmware?
What is your full build name/number, like EVA-L09c432b504 or what?
PS: @Chelmiannin
Since this was a question for help, it should have been opened as a regular thread, not for voting, so that people can normally cite and answer
Hey guys,
Switched from an lg v20 (which had no problems with the watch) to a note 9 on Verizon and can't seem to keep this phone connected to the Huawei watch (version 1) to save my life. Bluetooth disconnects probably once per hour or so and stays disconnected until I reboot watch or turn watch bt on and off.
I've tried hard resetting watch, reinstalling wear os app, clearing cache, and nothing seems to work.
Thoughts?
bump
I'm not sure it's correct form to bump one's own thread?