I can't post in development section yet. Running the release 1.7 and the 6/28 nightly, When I shut off the screen from my home page, the screen will not turn back on for about 15-20 seconds. This does not happen from the lockscreen.
Anyone else experience this or know a soliution?
Thanks
mustangl3 said:
I can't post in development section yet. Running the release 1.7 and the 6/28 nightly, When I shut off the screen from my home page, the screen will not turn back on for about 15-20 seconds. This does not happen from the lockscreen.
Anyone else experience this or know a soliution?
Thanks[/QUOTE}
After playing with the security settings, it seems the setting which delays the phone from locking is causing the problem. When the phone is set to lock immediately, the screen turns on immediately. If i set the lock delay, the screen will not come on for the amount of time it is set to delay.
Click to expand...
Click to collapse
Should this be a problem with your launcher software?
I hv flashed CARBON b4 but never experience this and neither do any other ROMs.
Right now I'm using MIRAGE V2.6, it's just perfect for me!
Related
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
I have looked through this forum, in the QandA and have not seen anyone post this problem. Is anyone experiencing the issue where your screen wont auto turn off? I have changed display timeout to 30 seconds, 1minute, 2 minutes, 5 minutes and so on... display wont turn off on its own. Also, when charging, if a notification comes up, screen awakes, but wont shut off again. Just curious if other users are having a similar issue or if I am the only one. I know this was a problem for S3 owners, but there was no real problem identifying what was causing it. Any help would be appreciated.
Set up as follows:
Stock JB Build
Rooted
Stock Kernel
(Only Titanium app data {not system} restored)
Almost all syncing data set to 1 hour refresh or greater
Smart Stay is turned off
Pattern Lock enabled
I think that covers most bases and options, but if I am missing something, I would love to know.
jdmadonna said:
I have looked through this forum, in the QandA and have not seen anyone post this problem. Is anyone experiencing the issue where your screen wont auto turn off? I have changed display timeout to 30 seconds, 1minute, 2 minutes, 5 minutes and so on... display wont turn off on its own. Also, when charging, if a notification comes up, screen awakes, but wont shut off again. Just curious if other users are having a similar issue or if I am the only one. I know this was a problem for S3 owners, but there was no real problem identifying what was causing it. Any help would be appreciated.
Set up as follows:
Stock JB Build
Rooted
Stock Kernel
(Only Titanium app data {not system} restored)
Almost all syncing data set to 1 hour refresh or greater
Smart Stay is turned off
Pattern Lock enabled
I think that covers most bases and options, but if I am missing something, I would love to know.
Click to expand...
Click to collapse
settings>developer options>Stay awake
Interesting thing though, i turn off stay awake, and it snaps back on at random. don't know why.
crazy talk said:
settings>developer options>Stay awake
Interesting thing though, i turn off stay awake, and it snaps back on at random. don't know why.
Click to expand...
Click to collapse
Thank you for your input. However, I had checked that option, it was not on to begin with, I turned it on, and then off again, it did not reenable itself, but it still is not the culprit. I am baffled right now.
jdmadonna said:
I have looked through this forum, in the QandA and have not seen anyone post this problem. Is anyone experiencing the issue where your screen wont auto turn off? I have changed display timeout to 30 seconds, 1minute, 2 minutes, 5 minutes and so on... display wont turn off on its own. Also, when charging, if a notification comes up, screen awakes, but wont shut off again. Just curious if other users are having a similar issue or if I am the only one. I know this was a problem for S3 owners, but there was no real problem identifying what was causing it. Any help would be appreciated.
Set up as follows:
Stock JB Build
Rooted
Stock Kernel
(Only Titanium app data {not system} restored)
Almost all syncing data set to 1 hour refresh or greater
Smart Stay is turned off
Pattern Lock enabled
I think that covers most bases and options, but if I am missing something, I would love to know.
Click to expand...
Click to collapse
I had this problem too I disabled stay awakenin dev settings, but that didnt fix it. Then I think I found another setting I. Accessories or dock settings and unch3cked something in there....man I just cant remember
Sent from my SGH-T889 using Tapatalk 2
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
nomad4ever said:
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same thing here, never had an issue with 4.1.2 but now it happens 2-3 times a day
Sent from my Galaxy Nexus using xda premium
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
andQlimax said:
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
Click to expand...
Click to collapse
Let me know how that works... I have been having this problem also. Screen is blank every 2 days it happens once. Ever since 4.2 update. Before that I had no issues like this.
Also un related but I've started to notice faint horizontal lines in my screen. I use auto brightness. Is this normal or return for warranty?
i can confirm this happens to me too.
4.2 stock only rooted with custom recovery.
Same here folks, It may a bug in the 4.2 builds since Sprint did not officially release 4.2 yet.
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
same issue here, I'll try to keep the brightness to manual to see if it works
chanchan305 said:
same issue here, I'll try to keep the brightness to manual to see if it works
Click to expand...
Click to collapse
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
MondoMor said:
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
Click to expand...
Click to collapse
bfprd0 said:
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
Click to expand...
Click to collapse
I experience this issue, but not that frequent. Once every 4 or 5 days, i don't know. I've managed to pull a logcat today as i was near of pc, as posted before, adb/phone is responsive, it even locks the screen normally, there was nothing useful on dmesg. I don't normally use auto-brightness, but enabled it a little while ago, although now i'm not sure if it was enabled the first time it happened. This last time, it wasn't enabled, that I'm sure.
It happened to me both when I was using XDA-app. I have almost 0 user apps installed right now, also uninstalled XDA. Reporting back in a few.
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
ogdobber said:
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
Click to expand...
Click to collapse
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
bk201doesntexist said:
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
Click to expand...
Click to collapse
ok...star this issue https://code.google.com/p/android/issues/detail?id=40019
I was wondering if any has encountered this.
1) After a reboot and when I'm on my main screen, it would take a while for it to load the launcher. If I attempt to scroll with Nova, it would say its unresponsive, and if i wait, it would work.
I recall on stock ICS, after reboot, i'd unlock screen and pretty much immediately i can use the main screens.
2) Sometimes when I try to unlock the screen it would freeze up. The screen remains blank, but the capacitive buttons light up.
I can reboot to enter the phone.
I can wait it out and it would eventually load and say something is unresponsive, sometimes the launcher. And if i wait, it would work again.
Or I can increase min cpu to 486 instead of 384hz, and i dont see this problem. Can someone explain to me whats happeneing? Why would 384Hz create Sleep of death?
Any insights would be helpful. I would like to get rid of the sod or lock screen freezing thing without having to mess with my cpu settings.
And resolve the lag issue at during reboot. it would take like 10 plus seconds for it to be responsive. I'm not saying 10 seconds is long, but the point is that i never had this issue with stock TW.
I am rooted on paranoid android/CM10 latest build. with SuperchargerV6.
Thanks in advance guys.
bump
anyone?
mikoal said:
bump
anyone?
Click to expand...
Click to collapse
try dirty flashing the rom. that usually clears up issues in cm10-based roms. make a nandroid if you havent already. cheers
Is anyone else using 10.1.3 RC2 or the stable version?
If i switch my sleep settings to anything above 15seconds, the screen will not sleep but it will dim. Sometimes i found my phone hot for no reason when it is not being used, and i think that is due to my screen constantly being on. I do not recall this issue in 10.1.3 -RC1. I don't mind using 15 seconds right now but the timer is not exactly at 15 seconds, it hard to read something on my phone when i have it set to 15 seconds because the screen keeps going into dim mode and sleep after 5-7 seconds.
Screen off animation and day dreaming settings are set to off at this point.
Android 4.2.2
Kernel 3.4.53
10.1.3 -dt2mo
Please feel free to recommend any other rom that is better than CyanogenMod.
peacesam said:
Is anyone else using 10.1.3 RC2 or the stable version?
If i switch my sleep settings to anything above 15seconds, the screen will not sleep but it will dim. Sometimes i found my phone hot for no reason when it is not being used, and i think that is due to my screen constantly being on. I do not recall this issue in 10.1.3 -RC1. I don't mind using 15 seconds right now but the timer is not exactly at 15 seconds, it hard to read something on my phone when i have it set to 15 seconds because the screen keeps going into dim mode and sleep after 5-7 seconds.
Screen off animation and day dreaming settings are set to off at this point.
Android 4.2.2
Kernel 3.4.53
10.1.3 -dt2mo
Please feel free to recommend any other rom that is better than CyanogenMod.
Click to expand...
Click to collapse
I had this issue once, I ran a Fix Perms and then rebooted, no problems since.
DJ_SpaRky said:
I had this issue once, I ran a Fix Perms and then rebooted, no problems since.
Click to expand...
Click to collapse
I just ran the permission fix and tested out on sleep after 30 seconds but no dice. I will play around with it...thanks!
peacesam said:
I just ran the permission fix and tested out on sleep after 30 seconds but no dice. I will play around with it...thanks!
Click to expand...
Click to collapse
OK, have you checked for Wakelocks? Such as G+ Location Reporting.
DJ_SpaRky said:
OK, have you checked for Wakelocks? Such as G+ Location Reporting.
Click to expand...
Click to collapse
I will give it a shot, right now it needs to collect more battery data first. I tried one minute as well, the screen becomes dimmed instead of sleep. I don't know what was difference really..i updated from rc1 and ever since then, rc2 and stable 10.1.3 hasn't been good.
peacesam said:
I will give it a shot, right now it needs to collect more battery data first. I tried one minute as well, the screen becomes dimmed instead of sleep. I don't know what was difference really..i updated from rc1 and ever since then, rc2 and stable 10.1.3 hasn't been good.
Click to expand...
Click to collapse
Weird, I only had the problem right after flashing, once all of my apps loaded and I ran Fix Perms then rebooted, no issues since.
Do you have a 3rd party lockscreen or widget on the CM lockscreen? I turn the lockscreen off (set screen security to none)
DJ_SpaRky said:
Weird, I only had the problem right after flashing, once all of my apps loaded and I ran Fix Perms then rebooted, no issues since.
Do you have a 3rd party lockscreen or widget on the CM lockscreen? I turn the lockscreen off (set screen security to none)
Click to expand...
Click to collapse
I do have a widget and it's called HD widget. I have been using that for my home screen clock and date. I would like to have lockscreen on as a security purpose tho.
peacesam said:
I do have a widget and it's called HD widget. I have been using that for my home screen clock and date. I would like to have lockscreen on as a security purpose tho.
Click to expand...
Click to collapse
For testing purposes, disable it then reboot and see if that fixes it.
DJ_SpaRky said:
For testing purposes, disable it then reboot and see if that fixes it.
Click to expand...
Click to collapse
That didn't work .
peacesam said:
That didn't work .
Click to expand...
Click to collapse
Yikes. Not sure where to go from here. I would backup your data,then wipe everything then redownload the ROM & GApps, then reflash, and then see if it happens before you load your data/apps back.
DJ_SpaRky said:
Yikes. Not sure where to go from here. I would backup your data,then wipe everything then redownload the ROM & GApps, then reflash, and then see if it happens before you load your data/apps back.
Click to expand...
Click to collapse
I think i will try that again. I did a full wiped, and i think since the issue was there after a fresh start so i restored everything back to normal.
Thanks for the help , i will post an update if i figured out the problem.
I switched to CyanFox! So far so good..i don't have any issue i got from 10.1.3 and 10.2.