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
Related
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
I am running BAMF Sense 3.0 RC3 (Imo's leanKernel running at Extreme with MR2), and I use WidgetLocker. Quite often, I will go to unlock my touch screen and my touching capabilities are not working - I can slide my slider, or do anything. I can hold down the power button to come up with the shutdown/restart options, but I cannot touch them to make it work. Sometimes if I wait a while it works again, or if I get another message/e-mail, but one time I had to pull the battery! I am not sure if this is a known issue or if maybe this is something with WidgetLocker, but does anyone know what I can do to fix this or have any suggestions? Any help would be appreciated! Thanks!
Bump - anyone else have this problem? Is it WidgetLocker, and maybe I need to make it no longer use RootHelper or something? When this happens (it currently is), only the power button works - all others do no effect, although they make a vibrate noise when pressed as if there are. After 10 minutes it will work again...)
Just a thought... Bump your min cpu setting to 368 and see if that helps.
Sent from my ADR6400L using XDA Premium App
Thanks, I did not think of that - I will change from Extreme to Normal (since Extreme undervolts it) and I will give that a try. Any other suggestions in case that does not work?
That's all I know man. I bet its a setting issue on the kernel.
Sent from my ADR6400L using XDA Premium App
You could always try switching to dream kernel 2.3.0 or 2.3.2, which are updated versions of the sense 3.0 stock kernel from das bamf. But I'm guessing that your min cpu setting is too low, especially if its undervolted. I have lag setting it to 245/368 with screen off, but its just laggy.
I tried changing settings on Imo's kernel, still no avail. His kernel gives me great battery life so I am trying to not switch to a different one; I was looking in Das BAMF toolkit and originally I had Sense Lock Screen off, which is when the lock screen froze, and when I turned it back on, I still had the lock screen froze but now sometimes the Sense one came into view, frozen. And by frozen, I mean the touch screen doesn't work - I can wake on with the volume keys and power button, but none of the bottom buttons work too. I am baffled... What could cause this?
Aup808 said:
I tried changing settings on Imo's kernel, still no avail. His kernel gives me great battery life so I am trying to not switch to a different one; I was looking in Das BAMF toolkit and originally I had Sense Lock Screen off, which is when the lock screen froze, and when I turned it back on, I still had the lock screen froze but now sometimes the Sense one came into view, frozen. And by frozen, I mean the touch screen doesn't work - I can wake on with the volume keys and power button, but none of the bottom buttons work too. I am baffled... What could cause this?
Click to expand...
Click to collapse
No idea, but the easiest solution is likely to wipe and flash again. For other lockscreen issues this has been the most successful solution.
Sent from my ADR6400L using XDA Premium App
Yeah, I was thinking about this... Considering I have Bamf 3.0 RC3, might just wipe and get RC4. I will let you guys know how I make out! Thanks for the suggestions!
Off topic question though... How do I edit the Swype dictionary?
Sent from my ADR6400L using XDA App
Aup808 said:
Yeah, I was thinking about this... Considering I have Bamf 3.0 RC3, might just wipe and get RC4. I will let you guys know how I make out! Thanks for the suggestions!
Off topic question though... How do I edit the Swype dictionary?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Don't forget to check out the preview of the rc5. It can be found on teambamf dot net. It is like rc4 but is very nice, especially with the new radio.
Sent from my ADR6400L using XDA Premium App
And as for swype, I think in options, by hitting that button on bottom right or through settings, there's a way to reset or tell it to not remember, but no way to edit I don't believe. There's a way to get it to ignore some words but its been so long I've forgotten.
Sent from my ADR6400L using XDA Premium App
Is there a way to make the home button respond instantly?
Does anyone else have this problem?
Sent from my GT-I9100 using XDA Premium App
It has something to do with the Voice control samsung built into the phone, people were saying you can freeze/ delete the app and your home button will be instant, i can personally vouch for this because I'm using CM7, a rom that doesn't have the voice control and my home button actually is instant.
it something to do with the processor and power management.
The delay is present in CM too but not as bad
drgopoos said:
it something to do with the processor and power management.
The delay is present in CM too but not as bad
Click to expand...
Click to collapse
I thought that had to do with the wakeup "lag" i.e. just waking the phone up from sleep, if you are talking about that yes its present in CM as well. I thought he was asking about home button when exiting out of apps and such, as i noticed a slight delay in that when i was using the stock rom.
I've froze voice commands with Bloat Freezer and this hasn't made any difference :/
Since KG1 firmware, home button lag has been solved. Home button acts normal now.
The OP hasn't explained what his problem actually is, so there's no point telling him to freeze apps!
@jameslfc5
Do you mean it takes a couple of seconds when the screen is off and you wake the phone with the home button, or do you mean it pauses when you're running an app and you press home to go back to your home screen?
jameslfc5 said:
Is there a way to make the home button respond instantly?
Does anyone else have this problem?
Click to expand...
Click to collapse
It responds instantly when connected to a charger. So it must be software related. I haven't found any 2.3.3. or 2.3.4 ROMs that remove the lag entirely. I'm sure someone will figure it out though.
When connected to charger the phone does not sleep. So no lag.
I have same problem as OP.
Note - it's not the wake-up delay, which is also annoying. It's the regular "go back to home screen" delay when using the phone.
I'm running Cognition 1.31, and problem was present on Stock ROM, VillainROM, Cognition 1.15 and 1.31.
I had voice control only on Stock ROM, and don't have it now - no difference. Delay is about 0.5-1 second.
Super annoying. Makes it feel slow. Was not present on any of the SGS ROMs.
+1
I just think of an iPhone... it's better in only this thing
CM7 fixes it. I think I know what you mean, I had it in Cognition 1.31 and litee'ning rom. Now I don't or don't even notice it.
Sent from my GT-I9100 using XDA App
DarkDvr said:
I have same problem as OP.
Note - it's not the wake-up delay, which is also annoying. It's the regular "go back to home screen" delay when using the phone.
I'm running Cognition 1.31, and problem was present on Stock ROM, VillainROM, Cognition 1.15 and 1.31.
I had voice control only on Stock ROM, and don't have it now - no difference. Delay is about 0.5-1 second.
Super annoying. Makes it feel slow. Was not present on any of the SGS ROMs.
Click to expand...
Click to collapse
Yeah this is my exact problem I don't think removing voice command has helped to be honest
Sent from my GT-I9100 using XDA Premium App
Did this actually get fixed in 2.3.4? The home button lag not the waking lag.
Nope.
Sent from my GT-I9100 using Tapatalk
Anyone know of a fix?
Sent from my GT-I9100 using XDA Premium App
if u r using CM then there is no home lag.
THe wakeup lag is still there but i would say very minimal
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.
Hi all,
I've recently flashed my GS3 to UltimaRom 4.0. (Very nice Rom btw)
I have no complaints, other than this one small thingy. (don't know if it's a known issue or not but a search didn't reveal anything)
When I press the 'power' button to turn off the display and to put away my phone, it sometimes keeps turning the display on.
Pressing the power button turns it off and immediately turns it back on.
I have to unlock the phone first before I can lock it again and the display stays disabled.
It's not a big deal but annoying if you just want to check something fast and the screen keeps popping up.
Is there any known fix for this? Or am I just forgetting something configuration wise?
Thx for any advise.
No issue here. Maybe one of your apps is causing this.
Sent from my GT-I9300 using xda app-developers app
Same here
I've got the same problem, I've not managed to nail it down to a single rogue app yet that may or may not be causing the issue. I'm running Omega v28 Jelly Bean, so I presume this isn't something wrong in either ROM, just an app like Arsaw says.
It could be:
The CRT bug (fixed in 5.1)
or
Something waking your screen a rogue app, or perhaps something asking for permissions and waking to do that (I had that once).
I'll place money on it being the CRT bug, though
Update to 4.1. There's lots of new features
So it was a bug, I had that too at 4.0 but I didn't pay much attention to it.
Quite late reply, but only had yesterday the chance to flash v4.1 i havent had the issue yet.
So it was probably indeed the problem mentioned above.
Thanks for you help!
Sent from my GT-I9300 using xda app-developers app