Hi!
About month ago I have bought an Asus Zenwatch and updated it to latest firmware. Last update that adds interactive watch faces also was installed several days ago.
Yesterday evening I have discovered weird issue that after some time in ambient mode the screen turns off. On tap it goes to normal mode and displays all colors and watch face correctly.
I have tried Reset settings option in Settings menu, enabling and disabling ambient mode from watch and Wear app, reinstalling Wear app and cleaning Play Services data, but it didn't help.
Could you, please, help me with this issue? Maybe this issue can be tracked using ADB?
Also in the Saturday morning I have a trip at town for a long time and the weather was hot. Temperature was about 30 Celsius degrees. Maybe this information can help.
Best regards, Mikle.
It is normal for the screen to go blank after a period of inactivity (about 30 mins), at least it is with mine.
I have the same issue
Related
I seem to be having an issue with the screen turning on at random. I have Always-on screen set to ON and tilt-to-wake set to OFF, but the screen will turn on sometimes seemingly at random and multiple times in a row. I have done Factory Reset a couple of times and it does not help.
Is there anyone else with this occurance and is there a fix for it?
Sent from my VS980 4G using Tapatalk
I have this issue too. I've tried several configurations and it keeps doing it.
Sent from my SM-N910V using Tapatalk
Any apps that send a lot of notifications or any notifications that are automatically dismissed/very briefly show up? Can't think of anything else that would wake your watch.
No, not on mine.
Sent from my SM-N910V using Tapatalk
I have the exact same issue. At first I thought it was tilt-to-wake having poor gesture recognition so I turned it off. However I noticed without touching the screen it would turn on and then turn off after the stand-by time. To verify that was the case I left it sitting on my desk all day and observed that it would in fact randomly turn on and off. I also noticed that when the issue occurs the battery life decreases rapidly.
Also this issue will continue to occur even in theater mode.
Have you find a solution yet? My smartwatch 3 does the screen turn on randomly and then also touch screen issue occurs, and it makes random touches, swipes going into settings and so on, without touching the screen. I'am on the latest wear version mwd49b.
For more info search on youtube for my video about this problem: Sony SmartWatch 3 screen problem.
I recently began having the same problem. The screen does not turn off after it randomly turns on - I have to manually press the button to turn it off. Needless to say, this tend to run down the battery. I did a factory reset this morning, but the problem persists.
EDITING POST JULY 20:
After factory reset, I actually had the watch doubly connected to the phone, so I have corrected that now. However the problem with the random turn-ons began occurring well before the factory reset. I'm not sure what triggers it, or what stops it, but when it begins to happen, it drains the battery very quickly. The problem only began recently (within the past few weeks), so I'm not sure what changed to bring this on.
A bug in Android Alarm Clock keep the watch active after alarm ring. Just corrected yesterday by an update on Google Alarm/Clock app.
On the phone > android wear app > settings icon on top right > device settings (smartwatch 3) >tilt to wake set to off
I recently upgraded my android wear device from an LG G watch to the 1st Gen Moto 360. I have the same apps installed on both (other than a couple dormant watchface apps), and I've never experienced this on my LG...
After I set my watch to any brightness value (1-5 or Auto), once the screen goes to sleep then the display turns back on (via button press, screen tilt, etc.), the brightness is immediately back to the brightest setting... You can imagine what this is doing to my battery life!
I have factory reset my watch 4 times now and the problem persists. I have toggled on and off the Ambient Screen, Tilt to wake and Card previews, just in case... No luck
My best guess is that a third party app is overwriting the phone's settings, but I can't track it down (especially since I have the identical setup on my LG G watch with no issues).
I regularly use the brightness slider with Wear Mini Launcher and after a sleep, the slider is all the way back at Max again.
Has anyone else experienced this phenomenon on their Moto 360 or other Android Wear devices? Any suggestions on how to fix or troubleshoot this issue?
Currently, I can't go but a few hours before I have to charge my watch
Update...
As it turns out, the culprit was Smart Wear System SWS... I'm reaching out to the developer now
Huawei watch
AW 1.5
Sometimes ambient mode doesn't kick in, no matter how still I keep the watch or how long I wait. Only a reboot will fix it. On reboot, ambient mode works correctly. The problem will happen randomly, about once a day. It can happen with stock or Watchmaker watch faces.
Settings:
brightness - 1
wrist gestures - off
always on - on
screen lock - off
Phone AW settings:
always on - on
tilt to wake - off
Note, this is not the 'ambient always on' problem. Also, it's not a watchface problem. Yes, all the watchfaces have an ambient mode. When the problem occurs, switching to another watchface doesn't fix it.
Anyone else have this problem?
mageus said:
Huawei watch
AW 1.5
Sometimes ambient mode doesn't kick in, no matter how still I keep the watch or how long I wait. Only a reboot will fix it. On reboot, ambient mode works correctly. The problem will happen randomly, about once a day. It can happen with stock or Watchmaker watch faces.
Settings:
brightness - 1
wrist gestures - off
always on - on
screen lock - off
Phone AW settings:
always on - on
tilt to wake - off
Note, this is not the 'ambient always on' problem. Also, it's not a watchface problem. Yes, all the watchfaces have an ambient mode. When the problem occurs, switching to another watchface doesn't fix it.
Anyone else have this problem?
Click to expand...
Click to collapse
Someone just posted a bug where his ambient mode doesn't kick in after an alarm goes off until he reboots. Could this be your case too?
I have this too. Been happening about a week. Either an alarm or a timer going off will cause it.
Yes, that's it!
This morning I figured out that it always happens first thing in the morning. I thought it was from being on the charger all night long.
I can confirm this 100% reproducible bug.
Nicholb, did you notice this after the 1.5 update?
Although this is a major bug, there are some relatively easy fixes:
- If you only use the alarm to wake up in the morning, restart your watch after you wake up.
- Try another alarm app (the ones I saw were all pay apps or didn't work).
- For timers, use another app. I recommend MoveUp! MultiTimer.
mageus said:
Nicholb, did you notice this after the 1.5 update?
Click to expand...
Click to collapse
No, it was working fine after the 1.5 update. Something else must have updated within the last week. I did notice that last night there was an app update to "clock". I'll know tonight if that helped. I've just been rebooting the watch after an alarm goes off as a workaround.
That was it. The update to the clock app has fixed the problem for me.
Hi guys, any advice will be helpful.
Last day i was at office and was charging my Huawei watch, later i saw a yellow blink on the screen and when i tried to turn on the screen by taping on the screen or using wrist gesture the screen wont display.
Observations
1. Watch completely works perfect only the display is not showing up when you wake the or want to use the screen.
2. The touch is working. (can select even the screen is fully black and navigate)
3. On the "always on" mode the notifications and the always on display is showing. only the bright display is not working.
Disclaimer
Im new in posting threads in XDA, english is weak
I had a similar thing happen when I had a brightness app installed, I think it was Wear Brightness Control: https://play.google.com/store/apps/details?id=com.edgecontrols.android&hl=en
It took me forever to figure that out and get the app uninstalled, but my watch has been fine ever since. You might check to see if you have the same or a similar app installed on yours.
Hi all, I started using my Pixel 2 XL yesterday and I got the first issue!
I set every settings into ambient display to off, anyway my pixel 2 xl yesterday decided to turns on the screen itself randomly for 4 times. Every time the screen turned on itself I could see the numeric pad of the lockscreen, the same use case you get when you have the fp scanner set and you just try to unlock the phone just swiping up on the lockscreen. The second and the third times were almost consecutive, while the first and the fourth times were quite far from the others.
As I wrote....I set the ambient display to off when I set up the phone the first time. I don't have any particular app installed dealing with screen nor battery management.
Today (second day of usage) I haven't got any spontaneous screen turned on yet...
Anyone else had a similar issue?
Thanks in advance
Aratheba said:
Hi all, I started using my Pixel 2 XL yesterday and I got the first issue!
I set every settings into ambient display to off, anyway my pixel 2 xl yesterday decided to turns on the screen itself randomly for 4 times. Every time the screen turned on itself I could see the numeric pad of the lockscreen, the same use case you get when you have the fp scanner set and you just try to unlock the phone just swiping up on the lockscreen. The second and the third times were almost consecutive, while the first and the fourth times were quite far from the others.
As I wrote....I set the ambient display to off when I set up the phone the first time. I don't have any particular app installed dealing with screen nor battery management.
Today (second day of usage) I haven't got any spontaneous screen turned on yet...
Anyone else had a similar issue?
Thanks in advance
Click to expand...
Click to collapse
Nope....it's just done it again!
The screen has just turned on itself few seconds ago...I had a Netatmo notification in the notification bar....but checking it I saw it was 6 minutes old....then I think it's not the cause of this issue! :/