Related
Last night I was at home and noticed my wifi wasn't on, so I used the quick settings in the shade to toggle it. After a few seconds, wifi connected, and some unknown app took focus and closed repeatedly. After a few moments, it stopped and all was well.
I thought it was strange, so I turned wifi back off and the same thing happened. I rebooted, tried again, and got the same result. I was trying to think of a way to see what was happening, so I tried using the Screen Record function in Gravity Box, which didn't help much, because it happens so fast, and no info is displayed, just a black window that goes away quickly.
I then turned on the CPU usage in Developer Options to see if anything consistently came to the top when toggling. I saw a few apps each time Plume (Twitter), and Maildroid (email) were two of them. Both of these apps behave differently on wifi and 3G/4G (push vs. pull), so thought -maybe- it could be something with that. I uninstalled both of those, rebooted and tried again, getting the same result.
I recorded the screen when this was happening with the CPU usage displayed, and was wondering if anyone has any ideas? I don't really want to uninstall and reinstall EVERY app on my phone, so I was hoping someone may have seen this before or see something I'm missing when watching it happen.
Video: https://copy.com/8L6VTsqcdbUjVTz
Thanks for any input anyone can offer!
Do you check virus from your phone ?
I am also having this, seems to be due to 4.4.2 OTA, which I continue to delay as I am rooted.
Mine doens't only happen with wifi change, but also just randomly when using hangouts, keyboard stays out but hangouts min -> maxes quickly. I have tried freezing the update apps but it apparently didn't do anything as I was still asked to update earlier.
Only hangouts? I have that app disabled.in the app settings.
I can't say for sure that being on 4.4.2 fixed it, but I am on 4.4.2 now and it is not happening anymore.
I unlocked my bootloader and did the 4.4.2 SBF, unlocked and rooted. I installed probably 99% of the same apps (only ditched 1-2 that I never used anymore) and I am not having the flashing issue anymore.
Hard to tell for certain if the pending OTA was the cause, but it may have been.
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 Sony Xperia Z1, bought used but had it a while now, running fine on 5.0.2. on EE contract. But recently it started throwing up the above message randomly (I'll probably see it while typing this!). I haven't done an update, though it's asking for an OTA update, which I don't want to do, because the update it wants messed up my Nexus tablet, and I don't use location much-most of the time it's off, only using location occasionally to tag photos. I put the phone in Airplane mode overnight as I use it as an alarm clock.
What is causing it and how do I turn off the notification, which pops up randomly.
Many thanks, Larry
Nobody got any info?
Location provider 'Network' is disabled
I have an Xperia Z5c and have been getting the same pop-up message. It's becoming quite annoying.
Please help, people.
I've also had the same message. Happened on my Samsung S7, now have S8 with back up from S7 and get it still so must be an app causing it, trouble is not sure which one.
Possibly solved
In case anyone wants to know I think I've located the problem app! I have the lightning app Blitzortung lightning monitor and in its settings you can select location mode. Mine was set to network, so changed to manual and now seems okay!
Start from the beginning. Back a few weeks ago, when 4.1.5 was leaked but not officially announced, I downloaded 4.1.5 and flashed it through TWRP. Then 4.1.6 was released officially right after I've done my upgrading. So I CLEAN FLASHED 4.1.6 again on my phone.
Now the weird part: after 2 days of normal use (no flashing, no new apps installed), I left my phone charging today while went asleep. After I woke up, my phone is at 15% of battery. Although connect to the DASH charger, the phone doesn't charge at all with its LED showing red.
More weird is I can't open the notification center. I can pull the 5 toggles down, but can't open the whole menu.
Plus, notifications don't show up (no toast notification, no icons while in the homepage either).
My access to developer options is also blocked (says "Developer options is not available to this user").
The home button, recent apps button DOESN'T work - no matter if u switch the buttons in settings, or toggle the on-screen soft buttons. Although the "return" button and the fingerprint sensor DOES work.
Root access is still there (using Magisk).
While using TitaniumBackup, the app warns "This device's Android ID has changed". And a few apps have logged themselves out (I guess because of the ID change).
I think I can solve the problem by simply factory reset it. But Questions is : what's going on with my phone?
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
elmarian756 said:
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
Click to expand...
Click to collapse
Wow! I can't image someone had the same issue. So i actually re-flashed 4.1.6 and it's working.
But the charging problem persists. I've tried multiple power sources from the room, the kitchen, etc. None seem to be working.
Strangely, I was able to charge the device once a few hours ago at evening. And then it stopped charging again after I got the system working.
Any idea?
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