Hi,
I am currently running a stock ROM (4.2.2) with latest Franco kernel.
My Nexus 4 doesn't turn the screen off automatically after a period of inactivity. Is this the expected behaviour? The display is set to sleep after 15 sec and I can see that it dims the brightness, but the screen is still on unless I manually lock it with the power button.
Can you tell me if this is "normal"?
Thanks
connor32 said:
Hi,
I am currently running a stock ROM (4.2.2) with latest Franco kernel.
My Nexus 4 doesn't turn the screen off automatically after a period of inactivity. Is this the expected behaviour? The display is set to sleep after 15 sec and I can see that it dims the brightness, but the screen is still on unless I manually lock it with the power button.
Can you tell me if this is "normal"?
Thanks
Click to expand...
Click to collapse
Nevermind, I re-flashed the kernel and the screen gets turned off properly after a period of inactivity.
Related
I'm running jack's ROM v2.
I've set the screen-lock to automatically activate when idle for "0 minutes". I expected this to mean that if my phone dims, then it'll screen lock.
But the problem is, after 30-60 secs (I haven't counted), it will screen lock. I've set the screen to dim at 3 mins, but the lock comes on a lot sooner.
Anyone have any ideas how to change the registry so that I can make the screen lock only when I press the screen-off button at the top of the phone?? Or at least make it screen-lock only when the phone naturally dims at 3 minutes??
Any suggestions would be great
THANKS!!
bump? someone?
Ok I have Enom 1.8.1 + latest NExtheme + IntersecRaven Kernel.
My N1 screen's time out is set to 30sec but the screen only turn half dark after 30sec and doesn't shut off unless I press the power button.
Is it a problem of kernel or Nextheme?
Not a kernel problem. Running the same kernel as you posted (but on CM 5.0.6), just checked - after 30 seconds the phone was off.
Nobody has the same problem?
i am currently using a nexon one build called NexusHD2-FRG83 V1.5 PPP + RMNET
it works perfectly expect for one thing
the screen shuts off on itsz on and when it does the screen wont come back on
the led lights from my HD2 just stay on when i press them and no picture it is really annoying to have to take out my battery everytime this happens
some help plz
make sure under screen brightness for both WM and android it is not on AUTO. Set it to your liking. and change the screen timeout to 30 mins.
does the screen have to be on or can we turn off the screen to save battery? i notice if i turn the screen off after a few min it wont turn back on.
I have owned many Android devices over the years. Every one except my Nexus 7 would dim a few seconds or so before completely turning off the display. However, my N7 just turns off when the screen timeout timer expires. Every time it turns off, you have to use the power button to turn it on. I much prefer the behavior of my other devices when it comes to the screen timeout. Is there a way to get the N7 to dim for a few seconds before going off completely like my other devices do?
After official KK update when I leave my phone with unlock screen it fade down, and instead turning off it stay fade down.
When double tap it, or press power screen turn off.
I'm thinking its some kind of software setting - but can't find any.
I have 15sec till screen turn off but it fade after 11 seconds and stay that way. I tried cover sensors with hand but same thing.
Im on stock KK, D802.
Display > Auto off, bright 60%, Screen Saver 15sec, Screen saver: fade, auto rotate: on, dream settings: off, smart screen: off, smart video: off, led: on
When i turn off screen saver it dosn't fade.
When I change screen saver effect it just fade, so it looks like screen saver is broken in KK ?
Anyone ?
sapsa said:
Anyone ?
Click to expand...
Click to collapse
I have the same problem on stock 4.2.2 D80210b-HKG-XX.
But I can fix it on a time when reboot a phone.
Kolandr said:
I have the same problem on stock 4.2.2 D80210b-HKG-XX.
But I can fix it on a time when reboot a phone.
Click to expand...
Click to collapse
first few reboots didn't help. Now it self fix'd.