Related
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?
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
I have a Pebble Classic smartwatch (I know, old, unsupported, and discontinued) and a Huawei Honor 6X. My Pebble watch is able to pair and receive notifications fine. After some time, it stops receiving notifications. Sometimes after 5 minutes or even an hour. It doesn't re-sync till I disconnect it via the Pebble app (or settings on the watch) and then reconnect it. After that, it begins the process over by staying in sync after some time then stops receiving notifications.
Also, a strange thing I notice is it syncs in the morning when I wake up just fine without having to do anything.
When it stops receiving notifications both devices say they're still paired.
I have tried forgetting the device and then reconnecting. I have checked that my Pebble app isn't in the lock-screen cleanup list for the Huawei management. The Pebble app has Permissions to notifications. I do have the persistent notification within the Pebble app enabled. This happened before the Pebble servers went down and even after switching to Rebble. I do have Google Wear OS installed. Should I try using GadgetBridge?
My brother has the exact same watch with his iOS device and it works flawlessly.
Phone: Huawei Honor 6x Android 7.0
Pebble: v3.12.3
Is there something happening with the phones Bluetooth connection? Is it the Android operating system putting the app into sleep or something. Is it going into power save mode or something? If rooting my phone will provide a fix I am willing to do so.
phcreery said:
I have a Pebble Classic smartwatch (I know, old, unsupported, and discontinued) and a Huawei Honor 6X. My Pebble watch is able to pair and receive notifications fine. After some time, it stops receiving notifications. Sometimes after 5 minutes or even an hour. It doesn't re-sync till I disconnect it via the Pebble app (or settings on the watch) and then reconnect it. After that, it begins the process over by staying in sync after some time then stops receiving notifications.
Also, a strange thing I notice is it syncs in the morning when I wake up just fine without having to do anything.
When it stops receiving notifications both devices say they're still paired.
I have tried forgetting the device and then reconnecting. I have checked that my Pebble app isn't in the lock-screen cleanup list for the Huawei management. The Pebble app has Permissions to notifications. I do have the persistent notification within the Pebble app enabled. This happened before the Pebble servers went down and even after switching to Rebble. I do have Google Wear OS installed. Should I try using GadgetBridge?
My brother has the exact same watch with his iOS device and it works flawlessly.
Phone: Huawei Honor 6x Android 7.0
Pebble: v3.12.3
Is there something happening with the phones Bluetooth connection? Is it the Android operating system putting the app into sleep or something. Is it going into power save mode or something? If rooting my phone will provide a fix I am willing to do so.
Click to expand...
Click to collapse
You can try to exclude the app from androids Power saving. Also gadgetbridge can be tested(I'm using it with my PTS).
I tried gadget bridge and that does the same thing. Also I have it removed from my power management, nothing. I downloaded an app that supposedly keeps the Bluetooth alive. I'll give that a go.
I found a workaround.
I installed an app called BluetoothKeepActive and that seemed to fix the problem. It seems that my presumption was correct. The Bluetooth is going into standby mode or power management mode or something.
phcreery said:
I found a workaround.
I installed an app called BluetoothKeepActive and that seemed to fix the problem. It seems that my presumption was correct. The Bluetooth is going into standby mode or power management mode or something.
Click to expand...
Click to collapse
Seems to be an kernel issue of your phone imo.