Is there something out there that listens for the OK google while screen is off on android wear? I find it a bit annoying that my screen needs to be on to be able to active OK google
You can have the screen on by flicking your wrist and than talk to it. Is that still too annoying?
1979Sentinel said:
You can have the screen on by flicking your wrist and than talk to it. Is that still too annoying?
Click to expand...
Click to collapse
I do that currently but idk sometimes it's annoying. There are times where I have to flick a couple times before it turns on or sometimes the screen turns off to fast requiring me to repeat
c_86 said:
I do that currently but idk sometimes it's annoying. There are times where I have to flick a couple times before it turns on or sometimes the screen turns off to fast requiring me to repeat
Click to expand...
Click to collapse
True, happens with my watch as well. And keeping screen all day is not possible with battery of your watch?
1979Sentinel said:
True, happens with my watch as well. And keeping screen all day is not possible with battery of your watch?
Click to expand...
Click to collapse
I prefer to not have to charge everyday so I don't turn on leave screen on and when I did I found it to be a bit buggy.
Related
here is my issue.
unless i manually change my screen timeout my screen turns of no matter what im doing unless i touch it. watching something on hulu or playing need for speed it doesn't recognize that im doing something and black. is there a fix for this or do i have to change it every time.
dro3432 said:
here is my issue.
unless i manually change my screen timeout my screen turns of no matter what im doing unless i touch it. watching something on hulu or playing need for speed it doesn't recognize that im doing something and black. is there a fix for this or do i have to change it every time.
Click to expand...
Click to collapse
i did notice thie issue with need for speed as well
IN MY CASE, THE SCREEN NEVER TURNS OFF! ONE TIME, I left out alone without my phone and three hours later I come back and the battery is 20 percent and the screen still on.
Sent from my Nexus S using XDA App
For games, the publisher needs to fix it and add permissions to keep the screen on.
nxt said:
For games, the publisher needs to fix it and add permissions to keep the screen on.
Click to expand...
Click to collapse
this.
it may be annoying playing NFS:S but just tap the break when you see the screen dim a bit
I'm currently running cm7.02 nightly #94 with a color theme.
I can see that sometimes my phone doesn't sleep properly. There are periods of time 1-2 hours long when the phone is awake with the screen still off.
What is the quickest and the most efficient way to figure out which process is doing that?
Thanks.
Spare parts, download it click battery history and them partial wake lock or something. I'm not sure if it still works. It would force close on sense 2.3 don't know about asop
Sent from my Evo using XDA app.
nabbed said:
I'm currently running cm7.02 nightly #94 with a color theme.
I can see that sometimes my phone doesn't sleep properly. There are periods of time 1-2 hours long when the phone is awake with the screen still off.
What is the quickest and the most efficient way to figure out which process is doing that?
Thanks.
Click to expand...
Click to collapse
I like using Process Monitor Widget. Download it from the market. Open it up, then hit menu>record. keep the phone unplugged, turn the screen off, and let the phone sit for like 5-8 hours with Process Monitor Widget recording (preferably overnight). Then, stop recording, and hit analyze. It should be evident what is causing the wake lock.
k2buckley said:
Then, stop recording, and hit analyze. It should be evident what is causing the wake lock.
Click to expand...
Click to collapse
Could you please explain in more detail?
I'm going to second and say use Spare parts, super easy and it will tell you what is keeping the phone awake.
Man best way to tell is to go to the menu and click on about phone all the way at th e bottom and check your battery there is a uptime and awake time if you are having wake issues both of these numbers will be the same even when the phone is off.
Been running synergy nightlys with latest OTA no wake issues for me.
reaper24 said:
Man best way to tell is to go to the menu and click on about phone all the way at th e bottom and check your battery there is a uptime and awake time if you are having wake issues both of these numbers will be the same even when the phone is off.
Been running synergy nightlys with latest OTA no wake issues for me.
Click to expand...
Click to collapse
But this will not tell him which app is causing that awake time.
splmonster said:
But this will not tell him which app is causing that awake time.
Click to expand...
Click to collapse
Most of the time it's when WIFI is on it will keep phone awake I noticed this when it's off phone sleeps like a baby. Some apps can do this also but mostly WIFI seems to do it for me on some nightlys depends on the rom tho .
reaper24 said:
Most of the time it's when WIFI is on it will keep phone awake I noticed this when it's off phone sleeps like a baby. Some apps can do this also but mostly WIFI seems to do it for me on some nightlys depends on the rom tho .
Click to expand...
Click to collapse
I have never suffered a Wi-Fi issue like that. Never once have my problems with awake time ever been that. Always is a bad app... Which Spare Parts will show you which is doing it specifically.
nabbed said:
Could you please explain in more detail?
Click to expand...
Click to collapse
Sorry for the delay. When you have process monitor widget open, if you press menu, one of the options is record. Press that to start recording. Let it sit for a few hours, then go back into process monitor widget. When you press menu, you'll see it says recording. Press that to stop recording, then press the analyze button and review the results.
Sent from my PC36100 using XDA App
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Pretty old. Used to happen on my S2 too.
i guess it is an intent that gets activated upon waking of the phone (by turning on the screen)... when you do that, it updates the screen and thats why.
but then again... that is only what i think.. if it should update it while the screen is turned off it would be an active process and use battery
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
malybru said:
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Click to expand...
Click to collapse
Yes it always jump to the correct & exact time....it seems like a battery saving feature...if it is, other people with S4 should also experience it,no?
Tomo1971 said:
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
Click to expand...
Click to collapse
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Xxxdevilxxx said:
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Click to expand...
Click to collapse
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
malybru said:
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
Click to expand...
Click to collapse
oh...will do
New to XDA. Hello all!
I am experiencing this clock lag as well. :/
It doesn't matter if I use a custom lock screen or the Samsung lock screen with "swipe to unlock".
It's easily reproducible, let phone sit for 10-15 min and if you press the unlock button you'll see the wrong time for anywhere from a fraction of a second to a few seconds! and then it will update to correct time. Super annoying if I just want to know the time. Also, I've found that the amount the clock is behind is proportionate to the amount of time the phone as been idle....to a point...
I've seen the clock be over an hour off but it doesn't drift much more than than. Like a few folks mentioned, this should be running in the back ground. What is confusing to me is the clock in the top right is correct, so the phone is monitoring the clock...it's just not updating the lock screen clock.
Hopefully we can find a work around.
Not too keen on a new launcher...at least not until others who have seen that lag switch over and confirm it as a fix...but I don't think it will help, because the lock screen is still a Samsung process not controller by the launcher (i don't think)
Any thoughts?
The clock on the main unlock screen is essentially a widget. As a power saving feature, it only updates as necessary, which would be when you turn your phone on to look at the time. The time at the top of the screen in the notification bar is not a widget, it is a built in process that is always active. That is why it is current and the large clock, "the widget", is off until you turn your phone on to look at it.
My phone does the same thing. As does pretty much everyone's. It is not anything wrong with your phone, it is just the way it is set up. It is usually only delayed by a second or two, at best.
If it is an issue, you can always just remove the widget and use the time at the top of the screen to check. Or try a different app and set the update frequency.
It's not that big of a deal to me, I know it's always off until it refreshes, so I just give it a second to update.
I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
fhblake04 said:
I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
Click to expand...
Click to collapse
Surprised you're the first to bring this up, lol! Been watching this device closely on on youtube reviews on this device you can see it right infront of your eyes. Doesn't ALWAYS wake on double tap but does ALWAYS turn off, weird. Idk what to tell ya but yes it isn't just you...
Are you using the stock launcher?
I switched to Nova and noticed its very finicky for me ever since I stopped using the stock launcher.
Still on stock launcher.
I just tap it 4 times when turning on, no big deal.
The only time it fails for me is if I tap too softly. I notice that when turning it on, it does take two distinct forceful taps. It seems to register anything else as a touch. So, while I think it could be better, I don't see it as inconsistent. If it was too sensitive, it might end up turning on in your pocket.
I think it has to do with the motion sensor in the phone. Mine works fine if I just tap it twice while it's in a steady position (even in my hand), but when I'm riding my bicycle I can't get it to tap "on" most of the time (unless I stop). Tap off works much more reliably.
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Tapping near top of screen seems to work much better.
geoff5093 said:
I just tap it 4 times when turning on, no big deal.
Click to expand...
Click to collapse
Exactly.
Can't have both battery life and also expect the Knock feature not to go to deep sleep. I prefer to eat my cake.
Also, I like that it does not accidentally turn in my pocket or when gripping the screen in my hands, etc.
The Korean version has gotten a few updates to make KnockOn smoother, so you might not have that update yet.
Well, I have a VZW version so updates will not be plentiful lol. Knocking on it several times, rather than twice seems to work better. Thank you guys for your suggestions.
jayochs said:
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Click to expand...
Click to collapse
Maybe we should shake it a few times and then double-tap the screen. It would be like a Moto X/LG G2 hybrid!
I’m doing a study right now with this feature by recording the time and results. So far 3 quick knocks resulted in successful power ups 100% of the time (7 for 7). When doing 2 knocks (prior to the study) it was intermittent to the point of driving me crazy.
Come to think about it when you knock on someone’s door do you knock 3 times or 2? I always knock 3 times but the video reviews of this feature messed my thought process up with 2. First world problems I guess. LOL
I will report back with my results tonight.
BaronInkjet said:
Tapping near top of screen seems to work much better.
Click to expand...
Click to collapse
Same for me. It says you need to either tap in the middle or top of screen. Anywhere else doesn't work as well.
Sent from my LG-D801 using xda app-developers app
Seems to work best if you tap where the lock screen widgets are located -- top center, but not at very top.
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
I have an explanation. I think this happens because when the phones asleep (screen and touch panel is off), knockon uses the motion of the phone, read by the accelerometer, to recognize that two-tap pattern and subsequently turn on.
When the phone and screen are on though, the mechanism happens by direct touch input and is much more reliable, so it should happen every time.
This would explain why in moving situations like riding a bike, or when I was trying to turn it on while it was on the bed, which probably absorbed the motion from the taps it doesn't work as well.
I did hear that the Korean version got a firmware update that helped, though who knows when we'll see that in America.
razball said:
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like a defective phone.
Factory reset time!
Good to know dam lol that's annoying well I guess I'll wait till it happens again to be really sure
Sent from my LG-D801 using Tapatalk 2
Anyone else having a bug where the screen does'nt turn off after the designated time out is reached? I have set mine to 15 seconds but it only dims down after 7 seconds and remains dimmed forever and ever.
Only way to get phone to work normally is to restart it. But the bug keeps coming back every day, sometimes serveral times a day.
Now I have to turn off screen manually by pressing the powerbutton.
Update Solution:
I actually had locked(in recents) Edge browser into the memory so it always would be available lightning fast. I just unlocked and closed it from recents app, and now the screen shuts off normally. Apparantly there was probably a hidden ads-page active somewhere keeping the screen from shutting off properly.
corb06 said:
Anyone else having a bug where the screen does'nt turn off after the designated time out is reached? I have set mine to 15 seconds but it only dims down after 7 seconds and remains dimmed forever and ever.
Only way to get phone to work normally is to restart it. But the bug keeps coming back every day, sometimes serveral times a day.
Now I have to turn off screen manually by pressing the powerbutton.
Click to expand...
Click to collapse
Any developer options turned on?
dottat said:
Any developer options turned on?
Click to expand...
Click to collapse
Not much, only the Force all apps to be resize:able.
The screen awake while charging is off. USB-debbuging also.
corb06 said:
Not much, only the Force all apps to be resize:able.
The screen awake while charging is off. USB-debbuging also.
Click to expand...
Click to collapse
I have encountered this bug occasionally, a few times this happened some web page was open (No video was playing) not sure if this was the case with you sometimes some ads or something on the web page can keep the browser active. I did not think much of it nor explored it much but will keep an eye out if it reoccurs.
Turn off Developer options for now.
Does it happen in Safe Mode?
Make sure a 3rd party app isn't the cause.
Clear system cache on the boot menu.
.
warriorvibhu said:
I have encountered this bug occasionally, a few times this happened some web page was open (No video was playing) not sure if this was the case with you sometimes some ads or something on the web page can keep the browser active. I did not think much of it nor explored it much but will keep an eye out if it reoccurs.
Click to expand...
Click to collapse
Big Thanks! I actually had locked Edge browser, Telegram and File Manager+ into the memory so they would never be killed off. I just unlocked and removed them all, and now the screen shuts off normally. What a relief [emoji846]!
Using Adguard adblock and Edge content blocker so it might have been a hidden ad of sorts keeping phone screen active.
Sent from my SM-N986B using Tapatalk
corb06 said:
Big Thanks! I actually had locked Edge browser, Telegram and File Manager+ into the memory so they would never be killed off. I just unlocked and removed them all, and now the screen shuts off normally. What a relief [emoji846]!
Using Adguard adblock and Edge content blocker so it might have been a hidden ad of sorts keeping phone screen active.
Sent from my SM-N986B using Tapatalk
Click to expand...
Click to collapse
Glad it worked, I suggest copy paste above text, what you observed the reason was for this to happen and what you did to fix it and add that information to the first post. Trust me it will help many.
Also change the title to: [Solved] - Screen won´t turn off - only dim down