This might prove trivial, but I have not had success yet.
When I go to navigation mode, my display will dim after ~15 seconds (not turn off). Periodically, it will go back to the set brightness after ~30 seconds. This is while a charger is connected.
What setting do I change to cancel this behavior? I find it a feature when not connected to a charger or when not in certain applications.
....One thing to note and will likely work for me...
Testing in "Car Home" appears to resolve the problem.
Related
I know it's something to do with the dock, but I don't know what service I can freeze to stop this behavior. If I've rebooted the phone and used it for whatever length of time, it will go to sleep at the time I've set for the screen to go off. If I plug it into the dock, the clock comes on as expected. If I then remove it from the dock, it won't go to sleep. The screen will dim but only remain dimmed.
I've tried to use TiBackup to freeze whatever says dock, but it doesn't seem to work. Anyone know how to stop this?
Hi guys!
I noticed over quite a time, that while I leave my phone charging over the night, any random notofication will cause the screen to stay on until I wake up and manually turn it off.
On my galaxy s2 I have VillainRom 2.1.0 (Android 2.3.4) with ninpho's 2.0.4 kernel.
However I did notice the problem before with VR 1.4 and CF-Root kernel (didn't use anything else yet), so I figure it might not be related to this.
This is rather annoying, as I don't want any burn in effects on my screen, but there's a much worse part about it:
It's noch 100% limited to the time of being charged. If I remove the charger at 100%, play around a little with the phone and then go to sleep, some random notification (whatsapp/sms etc.) will still cause the phone to wake up and not go back to sleep mode.
What happens is, I wake up with a phone at 50% battery (at it's best!), or I don't even wake up because my phone is dead and therefore my alarm clock stays quiet..
I read about some people having this problem with their SGS1 and it might help to go to Settings -> Applications -> Development -> uncheck Stay awake.
SGS2 does not have this "stay awake" option (or I'm seriously stupid)..
Anyone an idea what I might want to try?
Best greetings, Alex
At that screen I have "Standby" and you need to have it unchecked. Also, what's your screen-off delay? You don't have any apps like screebl keeping you screen on, I assume?
prodygee said:
At that screen I have "Standby" and you need to have it unchecked. Also, what's your screen-off delay? You don't have any apps like screebl keeping you screen on, I assume?
Click to expand...
Click to collapse
I do not have this option. my screens stays on all the time.
You're problem sounds similar to mine.
http://forum.xda-developers.com/showthread.php?t=1224117
I have tested with a stock rom of which I made no input and had the same issue.
Hope we can solve our problems. Cheers
cjackway said:
You're problem sounds similar to mine.
http://forum.xda-developers.com/showthread.php?t=1224117
I have tested with a stock rom of which I made no input and had the same issue.
Hope we can solve our problems. Cheers
Click to expand...
Click to collapse
mine just started doing it. i have been running custom rom for awhile now.
apps recently installed:
words free
launcher pro 806
extended controls
impossible level game
I have uninstalled:
words free
impossible level game
my issue is still happening.
when unplugged screen turns off.
I can get a text, it will light up then turn back off.
when plugged in (charging)
display will not turn off unless i press the lock button.
if i get a text the screen turns back on and stays on unless i press the lock button again.
I have recently re-flashed, complete wipe of phone and factory reset wipe.
I still have the screen on when charging and no option to disable.
I need an option to disable the "stay awake"
As my fault occurs with the phone completely reset on a stock rom it must be hardware so I am going to return it and see what happens from there.
I have flashed CM7 and there is an option to turn stay awake off.
This option is removed in DarkyRom.
Finally figured out how to turn it on or off!!!!
install the app extended controls and add stake awake as a toggle.
Turn it off!!!
then remove app
FINALLY!
UPDATE: CapnPez's suggestions seems to have worked. Screen on/off needs to be set as an event, not a state!
Thanks for the help!
My setup:
Rooted
Running SnowJB 1.1
Tasker Installed...no profiles or task setup to toggle the Bluetooth radio. Do use a Screen On/Off state profile to turn on Wifi/Data/Gps/NFC when screen is on. When screen is off, they are all off. Also have Secure Settings plugin installed to toggle NFC and GPS.
NFC Task Launcher installed...Only one tag exists for my "car mode". When I place the phone in the car dock it launches CarHome Ultra
CarHome Ultra installed....turns on BT when it launches.
So with all of this setup, let me explain the issue. When I place the phone in my car dock and turn the screen on, NFC radio should turn on, NFC task launcher should then read the tag in the car dock which launches CarHome Ultra. CarHome Ultra turns on BT when it launches.
What has been happening lately is when CHU launches, the bluetooth starts toggling on and off VERY rapidly. I can see the BT toggle icon in the notification power bar flashing or blinking. Pressing the BT icon does nothing. Closing CHU does nothing. I have to restart the phone to get out of this strange blinking loop. I have frozen/uninstalled Tasker and everything seems to behave as designed. However, I reinstall tasker, DO NOT CREATE ANY BT TOGGLE ACTIONS, and the blinking BT returns.
Has anyone experienced similar behavior?
I'm not sure if this is the problem, but my first thought is that you mentioned that you are using the screen on STATE. Perhaps you should use the screen on EVENT. What it might be doing with the state is that it checks that the screen is on and toggles your wifi/data/gps/nfc and the turned on nfc now detects the tag again and then tries to re-turn on your bluetooth. It might be doing this each time it detects that you are still in that state (as quick as the interval it takes to recheck that state). With an event, it should just trigger once.
This is my first guess, but it might be worth a shot to change it to the event. I may be mistaken with what Tasker is doing when it is in the state. Good luck and I'll keep thinking what else it might be (there are others out there who are better Tasker Gurus than I).
Thanks, I have made this change and will give this a try. It's strange that the thing most affected is the Bluetooth and I have no Tasker profiles set up to toggle the BT radio.
CapnPez said:
I'm not sure if this is the problem, but my first thought is that you mentioned that you are using the screen on STATE. Perhaps you should use the screen on EVENT. What it might be doing with the state is that it checks that the screen is on and toggles your wifi/data/gps/nfc and the turned on nfc now detects the tag again and then tries to re-turn on your bluetooth. It might be doing this each time it detects that you are still in that state (as quick as the interval it takes to recheck that state). With an event, it should just trigger once.
This is my first guess, but it might be worth a shot to change it to the event. I may be mistaken with what Tasker is doing when it is in the state. Good luck and I'll keep thinking what else it might be (there are others out there who are better Tasker Gurus than I).
Click to expand...
Click to collapse
My Tab 4 turns itself on every night at specific time. I cannot figure out why, or what setting may be the culprit.
Every evening, I tap the power button to "sleep" my tablet before I put it in its cradle to charge. However, every evening at a specific time the tablet display lights up showing the lock screen, which wakes me up. This is making me nuts! I can't find any setting that would affect this behaviour, and there are no alarms set to "wake" the tablet at some specific time.
Any ideas where I should check?
I've been documenting my struggles with my lock screen in another thread. But I just had a major breakthrough and didn't want this to get buried.
To recap, my lockscreen has been a buggy mess from day one. The fingerprint sensor barely works, the fingerprint icon randomly disappears, and the gray border that's supposed to appear around the fingerprint icon simply doesn't show up. The lockscreen doesn't light up when I pick up the phone either (it stays dimmed). Also, wallpapers don't show up on the lock screen, and the big ugly clock sometimes disappears or moves itself to the top-left.
I've tried just about everything to fix this. As a last-ditch effort, I added a new user profile only to find that the lockscreen works perfectly well for this new profile (but still not for my main one).
Here's my main profile with the unusable lockscreen:
broken lockscreen of main profile
Watch "broken lockscreen of main profile" on Streamable.
streamable.com
And here's what it looks like when using the other profile:
working lockscreen on new profile
Watch "working lockscreen on new profile" on Streamable.
streamable.com
So there's clearly some obscure bug that most people aren't experiencing here. I'd love to just figure it out so I can move on.
When I didn't have the "always on display" turned on, the phone was very consistant about turning on properly when I picked it up. I ran it this way for 3-4 days without any issues.
After reading some articles on the P6, I realized that it has an AOD and that it was turned off. So I turned the AOD on while leaving all the other settings set the same. At first, the finger print icon wouldn't appear consistantly, but that is because I had adjusted the animation scale settings in the Developer settings. Changing that back to stock fixed the issue with the finger print icon not showing up.
That beings said, I have experienced the same "unresponsive" screen many times over the last couple of days that I have had the AOD turned on. The screen stays dimmed (or even turned off if I pull the phone out of my pocket) and the finger print reader is inactive (even though the icon is displayed). The screen is suppose to turn on when I lift the phone up, but it doesn't always do it. When this happens, I have to either manually turn the screen on using the power button, or double tap the screen to wake it. This is clearly a bug in the system somewhere. I probably need to report it to Google, but hopefully it is fixed soon.
After spending way too long on this, I've determined that the bug occurs consistently with these specific settings (although it may also occur for similar ones):
Lock after screen timeout: 30 minutes (or anything high enough to prevent it from locking between tests)
Power button instantly locks: disabled
Lift to check phone: disabled
Tap to check phone: disabled
Always show time and info: enabled
Replication steps:
1) Enter the above settings
2) Press the Power button to go to the lockscreen
3) Set your phone down for a couple seconds
4) Pick your phone back up and try to use the fingerprint sensor
Result: The fingerprint sensor won't work the first time.
I think all the other issues I had were actually stemming from this one issue.