Pretty often, the clock jumps to the next minute, when I turn the wrist or tap the screen (display switches from dimmed to bright mode).
In reality, the new minute should have been displayed some seconds earlier. So in practice, the clock is often a little late.
If I choose a watch face with seconds, I can see this even better, because for example, in dimmed mode it shows 2:00, then I turn the wrist and it suddenly shows 2:01:20.
Sometimes, it even jumps 2 minutes when I activate the display.
So, screen refresh on change of minute does not always work.
I have already uninstalled all non-Google apps with Wear components and I did a factory reset on the watch.
Anyone else with this kind of problem? Is there any fix for that? Or is the hardware of mine not OK?
Thanks!
It seems to happen less often with Android Wear 5.0.1, but still happens.
I have noticed, it happens with standard watch faces and Facer watch faces sometimes. But it happens very often with WatchMaker watch faces.
Related
So my moto display will constantly light up every other second when I have notification such as E-mail etc. I feel like that kills a lot of battery when I just put it on the table. Is there are way to change the setting or something so it only light up for once or twice. I can always reach to the phone to check the notification so there is no need for notification always light up. Also, I found out that if I block the IR blaster it will not light up anymore but as soon as I remove the cover it will constantly light up again. I think constantly light up screen really burn down a lot of battery.
It doesn't use as much as you'd think. Moto Display (formerly Active Display on Moto X 2013) only lights the pixels that you can see. The rest of the screen is off.
With the Moto X, the display "breathes" when there are notifications pending. It flashes every 2-3 seconds, but does flash slower if left alone for a while. Placing the phone face down turns it off. You can also define quiet hours that disable the Active Display completely. Lastly, you can turn it on or off for specific apps that you don't want to trigger the notifications. For example, you may want your Gmail and text messages, but not Twitter. You can also dismiss the notifications by swiping left/right when selecting them (not certain if that is still true for Turbo as it has multiple notifications whereas the Moto X 2013 only shows one at a time).
I don't know of any way to turn it off after some amount of time, it's either on or off, but you can change the apps that are included. And as I said, it does blink slower (more time between blinks) if you don't touch the phone for a while.
Ok thanks that really helps... I just hope they can add a setting so it won't always light up. I'm also wondering if battery consumption by moto display count as part of the cell standby because it is still quite high compare to other smartphone I had used before.
emptydream said:
Ok thanks that really helps... I just hope they can add a setting so it won't always light up. I'm also wondering if battery consumption by moto display count as part of the cell standby because it is still quite high compare to other smartphone I had used before.
Click to expand...
Click to collapse
The Moto Display battery usage falls under the "Android System" app in the battery stats. You can confirm it in by opening the app in the battery stats and observing the "Active Display System Process" listed.
You can turn off moto display...or you can swipe the notification to the right or left to "dismiss it" without opening the phone...or you can leave the phone face down on the table
I am unsure if I will buy this device.
Someone who has moto maxx can download an application from the notification screen and test if it works well?
These applications promise to pick a different light for each application notification screen on moto maxx. (Since he does not have conventional LED)
I will be very grateful if someone could do this to me
I think Moto should definitely change the Moto Display behavior so that it uses the front sensors instead of the gyro (movement) when there is no current notification. This would allow you to wave for the time and it would be displayed when you pulled it out of your pocket, but it would not be shown by bumps in the road or other movement. If there is a notification waiting the behavior should stay the same because it is up to the user to acknowledge/dismiss it.
neyes said:
I think Moto should definitely change the Moto Display behavior so that it uses the front sensors instead of the gyro (movement) when there is no current notification. This would allow you to wave for the time and it would be displayed when you pulled it out of your pocket, but it would not be shown by bumps in the road or other movement. If there is a notification waiting the behavior should stay the same because it is up to the user to acknowledge/dismiss it.
Click to expand...
Click to collapse
On the Moto X 2013 at least, it doesn't turn on every time it moves. If you're holding it in your hand and walking, it doesn't just stay on all the time. Once you set it down on the table and let it sit for a moment, then touch it again, it lights up.
I usually leave mine sitting on my desk at work and if there are no notifications pending (to make it breathe), I just touch it so it rolls slightly on the curved back and it shows me the time.
In Wear 1.3.x, all notifications(which have no LOCAL_ONLY|ON_GOING...flags) in smartphone is sent to smartwatch immediately.
But I realized that, after wear 1.4, only some notifications(maybe vib. notification) are sent to watch immediately, and
the others are sent in piggyback fashion when vib. notification or notification remove or any synchronization happend.
Is it right? or only my problems?
It's seem very important changes but I can't find the details.
I'm using a LG Watch Urbane, Nexus 5.1
and tested on Wear 1.3.0.2369832(10/28), 1.4.0.2392391(11/07), 1.4.0.2462440.(12/04) in same environments.
Wear 1.3.X
notification w/o vib : immediately, dim screen
vib{0,0} : immediately, dim screen
vib{0,1} : immediately, screen on, vib
Wear 1.4.X
notification w/o vib : piggyback
vib{0,0} : immediately, dim screen
vib{0,1} : immediately, screen on, vib
you can test any notification test app.
(play.google.com/store/apps/details?id=com.sloy.jbnotif
apkmirror.com/apk/google-inc/android-wear/
'adb install -r -d wear.xxx.apk' make no need to re-paring with watch or factory reset)
Make any 3 notification will not be popped in watch after Wear 1.4.
In short, if you make any notifications without vib., it may not notified to watch on time after Wear 1.4.
Thank you.
Realized this as I use a timer constantly at work - it'd be really useful to have it show the remaining time on the 2nd screen. Right now all that shows is a little hourglass icon, but I have to unlock the screen to see remaining time.
Same question for me as well. I currently have the Note Edge. My edge displays the countdown time on the edge screen. I was wondering if the V20 has the same capability on the second screen as well?
probably a bit off topic (but not too much)
I use the timer a lot and can't disable the vibration in it nor change the tune (both options are available in the Alarm)....any idea? Of course I'd like to have the timer on the second screen too.
Timer tone can be changed on a rooted device. I'm going to see if I can find Timer vibrate and maybe disable it.
I'm starting to notice that there's a significant lag from the time a notification goes off on the phone and the time the watch goes off. If I receive a text, it's a solid 2 minutes before the watch goes off. I re-paired with my S7 to see if it was the watch and the delay was a couple seconds.
Anyone else experiencing this?
Hi,
I have this phone for little over 2 years. For over 1 week now I'm experiencing my phone not being able to wake up when I use the power button/home button. Whenever I push the button, the screen flashes for like 1s blue color, you can also see that the notification panel is blacked out and part of it green and it doesn't wake up. Sometimes it doesn't even flash. It used to take about 10 tries to wake it up but today I couldn't wake it up. I performed soft reset, I couldn't see the booting animation at all but it rebooted, buttons lit up and I was able to get in. It's like the phone is working fine in the background but the screen doesn't light up. I can turn down/up the volume, take a screenshot, get into settings, open apps, write a message but the screen is black. Even my alarm went off this morning but I couldn't dismiss it.
I downloaded an Always On Display app. Although I don't actually see the screensaver when it's locked, it's still on and it's easy to get in beacuse of it.
It all started with the screen flickering on minimum brightness. In February this year I had the screen replaced for the same issue but this time it's worse because of the blacked out screen.
Any ideas what it could be? Faulty display again?
Thank you
tessicorn said:
Hi,
I have this phone for little over 2 years. For over 1 week now I'm experiencing my phone not being able to wake up when I use the power button/home button. Whenever I push the button, the screen flashes for like 1s blue color, you can also see that the notification panel is blacked out and part of it green and it doesn't wake up. Sometimes it doesn't even flash. It used to take about 10 tries to wake it up but today I couldn't wake it up. I performed soft reset, I couldn't see the booting animation at all but it rebooted, buttons lit up and I was able to get in. It's like the phone is working fine in the background but the screen doesn't light up. I can turn down/up the volume, take a screenshot, get into settings, open apps, write a message but the screen is black. Even my alarm went off this morning but I couldn't dismiss it.
I downloaded an Always On Display app. Although I don't actually see the screensaver when it's locked, it's still on and it's easy to get in beacuse of it.
It all started with the screen flickering on minimum brightness. In February this year I had the screen replaced for the same issue but this time it's worse because of the blacked out screen.
Any ideas what it could be? Faulty display again?
Thank you
Click to expand...
Click to collapse
It's over to have this phone for little over 2 years now you should have to change
TIP:
Flash a new stock rom of your phone from sammobile via ODIN.
Sophia.xda said:
It's over to have this phone for little over 2 years now you should have to change
TIP:
Flash a new stock rom of your phone from sammobile via ODIN.
Click to expand...
Click to collapse
That would be great, but I'm not a person that buys new phone every 2 years. I was thinking about it though .
When it comes to flashing. Do you think that would help? I don't want to end up with a black screen unable to set the phone up again. Cause overall it's working great .
Hi, i have the same problem, i'm from Belgium, and I have blinking screen problem and wake up screen problem :s
is it a software issue (nougat???)
before the big update (marshmallow i dont have any problem)
i'm on firmware A510FXXS7CRJ6_A510FLUX7CRJ1_A510FXXU7CRJ6_HOME.tar.md5
Turn screen brightness up abit to stop the blinking of screen. It's an issue of the screen hardware itself at low brightness after wear and tear. As for the hanging issue, maybe it has to do with your AOD app? Try uninstalling the AOD app OR flashing a stock Rom OR custom rom OR factory reset and use your phone at a higher brightness that the screen does not blink and see whether it still persists.
conanDO98 said:
Turn screen brightness up abit to stop the blinking of screen. It's an issue of the screen hardware itself at low brightness after wear and tear. As for the hanging issue, maybe it has to do with your AOD app? Try uninstalling the AOD app OR flashing a stock Rom OR custom rom OR factory reset and use your phone at a higher brightness that the screen does not blink and see whether it still persists.
Click to expand...
Click to collapse
Thanks, because of my past experience with the same problem earlier this year I know about that "solution". Unfortunately, it makes the battery die faster as expected. Which is sad because I used it mainly on low brightness. So it's really not a solution at all.
I got rid of the AOD app because I found out that the phone lights up on 2nd try. AOD didn't work at all. I have to wake it up, put it to sleep and wake it up again which is always successful and the screen lights up. The screen flashes white about 3 times in a row now otherwise it works.
I haven't flashed it yet although I wanted to. But I will see what can I do. Thank you though!
I'm having the exact same issue using LineageOS.
It's already been 2 years, but since this thread is one of the first results on Google, I'll gladly add a solution.
Exact same problem for me, went through two screen repairs under warranty, and it would always come back a year later. No difference between Samsung OS and LineageOS, though I haven't tried rooting it.
Found on Ifixit: this issue is related to the AMOLED screen technology used by Samsung (among others). You can look it up, apparently there is a bad (?) voltage management in low brightness which worsen with time.
I could fix it with the "OLED Saver" application on Play Store. It works around this voltage management and allows you to reduce the brightness without the green flickering.
I still got white flashes after the installation, but not anymore the day after. I could even disable this application without the issue coming back.
I don't know what kind of magic cleanup this app performed, but it really is a (screen) life saver.