I installed CyanogenMod 7.0.2 beta6.4.2(http://forum.xda-developers.com/showthread.php?t=946354) and Kernel with minimized touchscreen bug(http://forum.xda-developers.com/showthread.php?t=929941) some time ago. Everything was ok but yesterday I've got wake up screen lag. When I'm pushing any button to turn on screen I need to wait for long or sometimes push the button and touch screen for aproximately 2 seconds screen. I Should immidiately get unlock screen but it doesn't happen :/ Any solution??
Reflash CyanogemMod WITHOUT wiping anything.
At the cpu settings, in cyanogen menu, increase the minimum cpu speed, should fix that
Try to disable the animation lock to off. I never faced such issue with Cm7.
Sent from my LG-P500 using Tapatalk
Just swipe on blank screen like unlock it on blank screen.
Sent from my LG-P509 using XDA Premium App
daX! said:
I installed CyanogenMod 7.0.2 beta6.4.2(http://forum.xda-developers.com/showthread.php?t=946354) and Kernel with minimized touchscreen bug(http://forum.xda-developers.com/showthread.php?t=929941) some time ago. Everything was ok but yesterday I've got wake up screen lag. When I'm pushing any button to turn on screen I need to wait for long or sometimes push the button and touch screen for aproximately 2 seconds screen. I Should immidiately get unlock screen but it doesn't happen :/ Any solution??
Click to expand...
Click to collapse
Me too had the same problem...... i solved it... go to settens....cm7 setteng...performance...cpu settings..... minimum 245 and maximum 729 and governer must be interactive..... and suggest to use launcher pro .... its fastrer den adw.....
Better use mik's kernel since he customized and fixed so many bugs for gingerbread.
Sent from my LG-P500 using XDA App
Related
Hi guys,
I am currently on Checkrom v4 with darky kernel. Most of the time, when i open the phone from a sleep state or screen of state, the screen will not respond to unlock gesture. I have to turn the unit off for at least 2 times before the screen would eventually respond. Sometimes, when turn it of again, the will just turn black but with button lights open. Then after i turn it off again, the screen will eventually light up and respond.
I also have experience this with other samsung roms such as criskelo, batista which is why i always flash back to Cm7 wherein I don't experience this. BTW, i also dont seem to remember experiencing this on CM9... your thoughts would be appreciated... TIA
yeah buddie.i am facing the excact the same problem.............
dont know how to get rid of this........
Maybe it's kernel related?
Sent from my GT-I9100 using xda premium
Happens to me too with Siyah 2.6.11.
Maybe it's undervolting.
Sent from my GT-I9100 using XDA App
This used to happen to me when I had a screen off profile enabled on SetCPU. If you're using SetCPU, try disabling it to see if that solves the problem.
I think i've found out what's causing this... it's the touch screen tune app... after.I removed this, it seems to be not freezing upon wake up of the device... HTH
Sent from my GT-I9100 using XDA Premium App
What govenor are you using?
I'm new to the SGS2. Coming from my old SGS1 running ICS I couldnt go back to gingerbread.
Leaked ICS on SGS2= No custom kernels BUT!...
With root access and NS tools app you can tweak stock "Ondemand" govenor. Its at 100000micro seconds which is 10th of a second stock sampling rate. This is SLOW. Couple with waking from sleep and known On-demand delay issues I think this might be the culprit... Cant wait for sources
am i the only one who experienced too much wake up delay?. i mean it took about 10-15 sec to wake it up. normally, when we press the home key, it'll wake up our ace within 1-2 secs, but in me it took 10 - 15 sec and i need to press the volume just to wake up my ace. i tried to reflash with odin, change my rom into cm 9, but no luck. what can i do to solve this problem?
Does it happens always? If so try setting min. frequency at 245 Mhz... Also governor to smartass v2
Prashanthme said:
Does it happens always? If so try setting min. frequency at 245 Mhz... Also governor to smartass v2
Click to expand...
Click to collapse
yes. it happens every time the screen turn off. i already did that, but nothing changed. i dont know what the problem of m ace
can someone tell me how to fix it?. it's really annoying. i always use my ace to check time, or check if there is any email, message received. but it always took about 10 - 15 secs to wake it up. dunno how did this happen to my ace. all i remember is i removed the sd card, then boom. it start to happen. and it always happen.
what is your internal memory free space and the RAM usage?
I also get the laggy problem when my dolphin browser is opened.
try RAM manager from pstore.
dianpadi said:
what is your internal memory free space and the RAM usage?
I also get the laggy problem when my dolphin browser is opened.
try RAM manager from pstore.
Click to expand...
Click to collapse
i have 83mb free in internal memory. dunno what is my RAM usage.. BUT, even if it is newly reflashed from odin, it still happens too much delay in wake up. so i try to flash a custom rom, CM 9 by mclaw, wipe the cache, wipe the delvik, restore factory settings, i already did all of them. but still, the the delay is there. 10-15 seconds delay in wake up..
how can i fix this?
I don't have this phone but i know it's related to the kernel
Sent from my LG-P500 using xda premium
FPChaim said:
I don't have this phone but i know it's related to the kernel
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
i'll try to flash a new kernel.
EDIT: already tried to flash a new kernel. still no luck..
what rom are you using? cm variants have a known issue of having delayed wake up lags, and if you alread had tried flashing over odin try flashing over customized stock rom which are aboundantly found in the development section
maybe your phone using default min. frequency, if yes, change to 245 MHz
but in my case, my min-max freq is default, and it didn't affect my phone's wake up time
My screen off profile in SetCPU is 120Mhz Min and 320 at Max. I never had wake up problems in my phone. My question is, 15 seconds waiting is looong. Do you press just middle (HOME) button and wait for 15 seconds? Because in either case if you were/are on stock ROM flashed via ODIN. That must not be happening on stock.
If you're using CM based ROM, Is everything check in "buttons" section in Settings > CyanogenMod Settings > Input Settings?
I'm just checking which buttons you've assigned to wake up your device.
mawnstermew said:
what rom are you using? cm variants have a known issue of having delayed wake up lags, and if you alread had tried flashing over odin try flashing over customized stock rom which are aboundantly found in the development section
Click to expand...
Click to collapse
i already tried stock rom from odin, still it has the wake up extreme lag that took 10-15 secs. then i tried to flash custom rom, cm9, cm 7.1, 7.2, stock based rom, still no luck.. i think, it's the hardware of my ace that has problem.
Rushyang said:
My screen off profile in SetCPU is 120Mhz Min and 320 at Max. I never had wake up problems in my phone. My question is, 15 seconds waiting is looong. Do you press just middle (HOME) button and wait for 15 seconds? Because in either case if you were/are on stock ROM flashed via ODIN. That must not be happening on stock.
If you're using CM based ROM, Is everything check in "buttons" section in Settings > CyanogenMod Settings > Input Settings?
I'm just checking which buttons you've assigned to wake up your device.
Click to expand...
Click to collapse
i dont set any buttons to wake up my ace, means, it was using the default. even in stock rom flashed via odin, it still have the extreme lag wake up. i press the home button, the light turn on in the menu and back button (left and right of the home button), and if i just wait, it wont turn the lights on in the screen, sometimes, if i just wait the 15secs, it'll wake up and imediately sleep again bout less than 1 second. that's why i need to press the volume to wake it up
can someone know how to fix it?
Try to set Minimum Clock Frequency to 245 or flash Adrenaline Boost v2 then if you feel that you are running low on memory just give your Ace a Boost.
Sounds weird, but you mentioned earlier that you removed your SD card without unmounting? Try formatting the card and insert it when the phone is off OR erase it when in CWM recovery. Never know this might just work out. If it doesn't use Kies to update your phone to stock.(Tedious process I know). Hope it helps.
I'm surprised nobody thought of this as a hardware problem.
Do you still have a warranty?
consegregate said:
I'm surprised nobody thought of this as a hardware problem.
Do you still have a warranty?
Click to expand...
Click to collapse
my warranty is already void/expired. i really think that this is a hardware problem. because, i already tried what they said.. but nothing happens. still the same. i already tried to reflash again via odin twice. still got the extreme wake up delay. tried to flash a custom rom based on stock, still no luck, tried to flash a cm rom (7.1, 7.2, 9) still the same. tried to set the minimum frequency to 245, still the same. and i think, im the only one experiencing the 15 second wake up delay. that's why i think, it's the hardware that has the problem.
Xr01d_GT said:
Sounds weird, but you mentioned earlier that you removed your SD card without unmounting? Try formatting the card and insert it when the phone is off OR erase it when in CWM recovery. Never know this might just work out. If it doesn't use Kies to update your phone to stock.(Tedious process I know). Hope it helps.
Click to expand...
Click to collapse
i already did that. i think, it's not on SD. because it still happen with or without sd on my ace.
Hi!
I'm using a recent CM9 nightly with default kernel.
I would like to have your opinion : about 3/4 a week my SGS3 is "stuck" when it's locked : impossible to wake up using home or power button, the screen stays black.
The weird thing is that when it happens, the phone is not frozen : I can still hear music on the headphones and control volume using Up/Down buttons.
Sometimes I let it stuck and receive a notification some minutes later and the phone magically can be unlocked again, screen wakes when I push Home button.
Very weird and annoying when that happens.
My question is : what do you think it could be? An app? How can I debug this and know what prevents the screen to wake up when that happens?
Thanks.
Wipe and reflash the rom
zodiaxe66 said:
Wipe and reflash the rom
Click to expand...
Click to collapse
Thanks, but is that the kind of easy answer you all tell when you don't know the exact answer?
When I installed CM9 a week ago, I did do a full wipe...
I think that next time it happens, I will try to connect my SGS3 on USB and do a adb logcat, maybe I'll find useful information.
Have you tinkered with any of the could settings or voltage settings?
Sent from my GT-I9300 using xda premium
ricey1986 said:
Have you tinkered with any of the could settings or voltage settings?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Nope
slainer68 said:
Nope
Click to expand...
Click to collapse
Having a similar problem to yourself. Installed CM9 rom had a play and then went back to omegaV9 performing a full wipe using the instructions on this site before reflashing.
Since then when my phone is locked screen off then i unlock either via swipe or using security code (digits ) it looks like the phone unlocks but sort of does a warm boot with black screen for a few seconds with the two buttons down the bottom light up.
When it starts it looks like all the apps have stopped and are restarting again.
I re flashed again omega 9 thought i had it sorted but it started playing up again this evening.
If anyone has any ideas please post..
Hi, I'm a newbie here. I also exprience this problem with my samsung GT-i9300. I hoping to see a fix with this problem.
This forum has been so helpful to new android users. Thank you guys.
When I press the home button/power button on my Galaxy S3 it takes 2-3 seconds before the screen turns on so i enter my password or pattern. I don`t mean turning the device on, but rather from having a black screen in "sleeping mode" and press the button to open the phone. Can someone help me by making it faster?
I didnt have that problem with my HTC Desire or any other Android mobile i had before.
I did a factory reset but still the same.
I have same problem. I tried different ROMS, kernels. Problem stays. Even I revert completely to factory state.
Delay on phone waking up is a known issue. If you mean lag when your screen is on and you press the home button, go into s-voice settings and disable the top setting.
I ment the wakin up thing ... it worked fine the past 2 weeks i had the phone but i noticed this thing today ... is there any solution for this ?
ajay5137 said:
When I press the home button/power button on my Galaxy S3 it takes 2-3 seconds before the screen turns on so i enter my password or pattern. I don`t mean turning the device on, but rather from having a black screen in "sleeping mode" and press the button to open the phone. Can someone help me by making it faster?
I didnt have that problem with my HTC Desire or any other Android mobile i had before.
I did a factory reset but still the same.
Click to expand...
Click to collapse
What roms have you tried so far?? I'm currently on Paranoid Android v2.18.1 and I'm experiencing no lags at all. I've also tried some other roms such as Wanamlite and Checkrom. Both of them worked perfect for me.
alvaretto said:
What roms have you tried so far?? I'm currently on Paranoid Android v2.18.1 and I'm experiencing no lags at all. I've also tried some other roms such as Wanamlite and Checkrom. Both of them worked perfect for me.
Click to expand...
Click to collapse
I have the original ROM ... the thing is that i never tried to play with these things before... if its the only way to make the phone works as it should then how should i do it???
What about you otheres ... do you have the same problem?
any help?
try installing app called SoftLocker FREE from play store .. it worked for me
This has been evident in all Galaxy S models - you're going to have to get used to it.
Sent from my GT-I9300 using Tapatalk 2
This lag is evident and it is usual because pur phone will go into 'deep sleep' mode to save extra battery juice and you certainly want that don't you? Since you are on stock ROM then you got no choice but to 'bare' with the lag. Unless you go custom such as Resurrection Remix ROM with have absolutely no lag. Paranoid android doesn't have the lags too.
Try it out yourself mate.
Sent from my GT-I9300 using xda app-developers app
amosljl1995 said:
This lag is evident and it is usual because pur phone will go into 'deep sleep' mode to save extra battery juice and you certainly want that don't you? Since you are on stock ROM then you got no choice but to 'bare' with the lag. Unless you go custom such as Resurrection Remix ROM with have absolutely no lag. Paranoid android doesn't have the lags too.
Try it out yourself mate.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
the app i posted earlier - SoftLocker FREE disables 'deep sleep', so there's no need to go custom. it works also on stock roms. I use it and the difference in battery drain isn't noticable at all.
Oh ok, I didn't know that cause I'm on custom
Sent from my GT-I9300 using xda app-developers app
I used to have lag problems before rooting but ever since I rooted and flashed Omega 27.2, no lags whatsoever. What's strange for me is how we all run into varying issues when we are sharing pretty much the same hardware.
Just my thoughts.
Sent from my GT-I9300 using Tapatalk 2
I've found that turning the ripple effect on the home screen off helps a lot, reduces most of the lag I was experiencing.
I recently updated my stock SCH-i605 to JellyBean's ROM build 21, with saber kernel. Now, once or twice a day, it will freeze after it's been in low power / locked for 10 minutes or more. When I try to unlock it, the screen turns on, and it is frozen as the last image that was displayed (e.g. I set it down and let it go to sleep, or lock it, from the web browser, and it then shows the page) It's completely frozen, and won't do anything. The only thing I've noticed is that it will do a quick single vibrate after holding down the lock or home button for a second. The only way to fix it is to take out the battery, since no other button combos work, like the force reset/shutdown.
Has anyone seen anything like this? Any ideas on what could be causing it or how to fix it?
Raise the minimum cpu speed up from 100. Some phones can't handle that low. Use the standard 200mhz minimum and you should be fine
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Raise the minimum cpu speed up from 100. Some phones can't handle that low. Use the standard 200mhz minimum and you should be fine
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I did set the minimum speed to 100MHz it one point, but switched it back to 200 shortly after. I just double checked, and its still set to the default 200. What else could cause this?
Also, I've noticed that it only happens when I leave it at an app, it's never frozen at the home screen. I've mostly had it freeze at settings and in the browser.
Slovedon said:
I did set the minimum speed to 100MHz it one point, but switched it back to 200 shortly after. I just double checked, and its still set to the default 200. What else could cause this?
Also, I've noticed that it only happens when I leave it at an app, it's never frozen at the home screen. I've mostly had it freeze at settings and in the browser.
Click to expand...
Click to collapse
Have you undervolted or underclocked anything? Messed with the gpu speed? Used the touch wake features?
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Have you undervolted or underclocked anything? Messed with the gpu speed? Used the touch wake features?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I'd overclocked and enabled touchwake, but the issue was actually forgetting to disable the ripple effect in with the AOSP lock screen enabled.
Slovedon said:
I'd overclocked and enabled touchwake, but the issue was actually forgetting to disable the ripple effect in with the AOSP lock screen enabled.
Click to expand...
Click to collapse
Glad you figured it out buddy. Cheers. Glad to see it wasn't even saber. Good to know. btw we've all made that lockscreen ripple sleep of death on aosp lock screen error. You're not alone haha
Sent from my SCH-I605 using Tapatalk 2