yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] Sp1tfire:
Rofl, now that made me laugh. Yeah, the phone lags a bit when pressing home or power button to wake it up, it even lags when getting an incoming call. My phone was ringing for quite some time until the screen decided to pop-up. I can live with it, even if it shouldn't behave like that. For the money i paid, i expected a "make coffee" button :rolleyes:
[Galaxy S II Q&A, Help & Troubleshooting] MasK:
I've made a short video describing this problem:

http://youtu.be/mQ3pMWTdWHY

Show this to the world to see if they have this problem!
[Galaxy S II Q&A, Help & Troubleshooting] EarlZ:
The SGS1 also had this issue as the firmware (stock) update. With 2.1 and 2.2 this never was an issue, I think it started with 2.2.1
[Galaxy S II Q&A, Help & Troubleshooting] Isadora:
I have a very low-tech solution for anyone's who's bothered by the "lag" - (I'm not, never actually noticed it to be honest) but... learn to press the button and blink just as you release it... by the time you've got your eyes re-opened, your screen should be on :D after a while you'll probably do it naturally and won't even realise you're doing it. That's a trick I've learnt do with my ebook readers because of the etch-a-sketch effect of the e-ink on page turn :p
[Galaxy S II Q&A, Help & Troubleshooting] Sp1tfire:
Lol, i was almost afraid to read on how you learned than trick :p
[Galaxy S II Q&A, Help & Troubleshooting] MasK:
Ya know.. its really strange that this problem doesnt affect everyone.

Some discussions abt it on Samsung Mobile SG facebook:

https://www.facebook.com/SamsungMobileSingapore/posts/133604343387332?notif_t=share_comment
[Galaxy S II Q&A, Help & Troubleshooting] appro77:
I'm beginning to suspect that this problem does effect everyone, it's just that some people aren't worried about it or don't notice it. Another reason it may not be showing itself on some phones is that there is an app running stopping the phone from going into deep sleep.

This is really really poor performance from a phone in this class. Not happy Samsung. Anyone who is not happy with the problem should be letting Samsung know by emailing them via their website. I have done this.
[Galaxy S II Q&A, Help & Troubleshooting] rantzzz:
Even more annoying is the brief view of the background before the lockscreen appears
[Galaxy S II Q&A, Help & Troubleshooting] jr866gooner:
The KF3 update seems to have done a good job! Lets just see as i only updated last nite..
[Galaxy S II Q&A, Help & Troubleshooting] bilboa1:
that's rite wakeup lag is everywhere but its short and most don't care. I don't. its 1 full second, big deal. in exchange we get deep sleep. its prolly hardware to "fix" although it could also be bypassed in the drivers. haven't looked.

some think its fixed while in fact its because their device doesn't enter deep sleep anymore.
[Galaxy S II Q&A, Help & Troubleshooting] JaX3RiR:
I didn't actually even notice the wakeup lag before I read this topic, but my SGS2 does actually take a second or two to wake up after pressing the home or power buttons.

I'm using standard TouchWiz with a 24-hour clock and what annoys me even more is that the phone shows the time in 12-hour AM/PM format for a split second after waking up.

Also whenever someone calls me the phone rings with really low volume for a second before turning on the full volume. And it annoys the hell out of me, to the point where I'm wishing no-one would even call. Ever. Again.
[Galaxy S II Q&A, Help & Troubleshooting] Coinz:
ye this is the only thing that really bothers me about the wakeup lag
[Galaxy S II Q&A, Help & Troubleshooting] ithehappy:
That is normal mate. Every Samsung phone used to have that feature and I like it ;)

Sent from GT-I9100
[Galaxy S II Q&A, Help & Troubleshooting] Razer(x):
Why do you like it?
[Galaxy S II Q&A, Help & Troubleshooting] ithehappy:
I don't like loud ringtones or any ringtones for that matter. So that feature helps me to silent the ringtone before it gets loud.

Regards.
[Galaxy S II Q&A, Help & Troubleshooting] kbiz90:
I didn't notice a lot of things until I came here! Sometimes, ignorance is bliss! :D

Some of the custom ROMs remove the ascending ringtone - like the Cognition ROM. I don't like ascending ringtones either.

Getting a different launcher might fix your TouchWiz problem.
[Galaxy S II Q&A, Help & Troubleshooting] MasK:
When I flashed KG1 stock, my wake up lag reduced from abt 1200ms to 700ms (rough figures) - using stock KG1 kernel (thats what makes the difference)

FYI - Not sure if ya guys feel this too.
[Galaxy S II Q&A, Help & Troubleshooting] jlevy73:
Not really. I'm using KG1, with sorg's KG1 cf-root kernel and the lag feels about the same as it did in 2.3.3
[Galaxy S II Q&A, Help & Troubleshooting] Hikari0307:
I don't have a rooted phone so I haven't tried this yet but just in case anybody else wants to try and see if it works

blog.clove.co.uk/2011/07/16/how-to-root-required-sgsii-fix-screen-wake-delays/#more-8027[/url]
[Galaxy S II Q&A, Help & Troubleshooting] MasK:
Do you have a microSD card inserted? With any cards inserted, this lag is extended. This is the reason why I don't have any SD cards in my device. Similar behavior is observed in SGS1 too. It's like it takes time to re-connect with the card or something...
[Galaxy S II Q&A, Help & Troubleshooting] EleCtrOx666:
No that's not working.
[Galaxy S II Q&A, Help & Troubleshooting] pham818:
softlock sucks balls
[Galaxy S II Q&A, Help & Troubleshooting] Swi7chblade:
I'm going to quote the famous Hacre, the creator of the Ninphetamine Kernel.

"Q: WAAAAHHHHHHH QQ I have to wait ONE ENTIRE SECOND for my phone to wake up from standby!!!111oneeleven. This is totally unacceptable and it is ruining my life!!!

A: Of course it takes a second to wake up from deep sleep. Everything has been shut off, the CPU placed in low power mode and the entire OS placed into suspend. I don't know about you but it takes me far longer than one second to be fully coherent and responsive when I wake up in the morning and I've only got one brain to worry about, the SGS2 has two of them! Shut the whining up about this complete and utter non issue."
[Galaxy S II Q&A, Help & Troubleshooting] biffsmash:
Quote - "Q: WAAAAHHHHHHH QQ I have to wait ONE ENTIRE SECOND for my phone to wake up from standby!!!111oneeleven. This is totally unacceptable and it is ruining my life!!!

A: Of course it takes a second to wake up from deep sleep. Everything has been shut off, the CPU placed in low power mode and the entire OS placed into suspend. I don't know about you but it takes me far longer than one second to be fully coherent and responsive when I wake up in the morning and I've only got one brain to worry about, the SGS2 has two of them! Shut the whining up about this complete and utter non issue."

Non issue?

And this quote from a Dev? Someone who should really be in the know? Bull.

The wake up lag IS an issue. It's an annoying issue.

When you are trying to show someone your phone, and you've built it up, and their HTC Wildfire wakes instantly, to the lockscreen, without any graphical glitches or lag, but the awesomely awesome SGS2 takes 2 seconds and shows the desktop before it goes to the lock screen, it kind of takes the p.

In the grand scheme of things, it's forgotten because the phone is so good, but it is still unacceptable, and no amount of bullcrap excuses about deep sleep, which is complete and utter nonsense as all phones deep sleep, will take away the fact that the issue is real, and should never of slipped the net on such a high end smartphone.

Quotes like that from devs are one of the many reasons I will not allow dev roms anywhere near my phone, as devs like the above obviously have zero interest in users, their phones, personal information or whether their roms work or not, despite taking donations.

Seems devs just havent a clue what the issue is or how to fix it, so they are not the all knowing programming gods they want us all to believe.
[Galaxy S II Q&A, Help & Troubleshooting] brussel:
The issue is an issue and it does not have anything to do with deep sleep because on the equivalent HTC device the Sensation the problem is not there. Instant wakeup.

it is a Samsung firmware issue.

come on Samsung FIX IT! :mad:
[Galaxy S II Q&A, Help & Troubleshooting] beaver2233:
It's not samsung specific... It is also evident on Apple products AFAIK
[Galaxy S II Q&A, Help & Troubleshooting] freemini:
If you want instant wake up that means no deep sleep or low CPU freq. sleep. Both known as 3 hours of battery. The CPU needs time to change frequency and wake up the rest of the phone.
[Galaxy S II Q&A, Help & Troubleshooting] marsexpress:
Agree with this!! What annoys me the most is not even the delay, it's the flash of the application you had running at some point in your life previously, or the desktop that you see that looks so cheap and nasty, I'd rather stare at a black screen for 1-2 seconds that would be fine. My previous HTC Desire S and prior to that a Desire never exhibited this issue even slightly.

I'm not a developer but don't tell me it's because the OS is asleep-it's plain bad coding. Yes it is *because* the OS is asleep but the phone can still sync, receive SMS and calls, wake for alarms etc so the device is clearly not 100% 'asleep' even when the CPU is in deep sleep. Other phones do not exhibit this issue.....
[Galaxy S II Q&A, Help & Troubleshooting] ambar_hitman:
I have not experienced this wake up lag at all in my SII I9100G. Its instant on 2.3.6 stock firmware. In fact, barring a few jitters in menu while using Go Launcher EX that too for the first time, I haven't experienced any lag in my device.
[Galaxy S II Q&A, Help & Troubleshooting] SimboXXX:
No fix for this yet?

I just got my phone yesterday and it's very annoying to have this wake-up delay. I was on 2.3.3 and upgraded to 2.3.6 without any change.

Are people getting the same problem with custom roms?
[Galaxy S II Q&A, Help & Troubleshooting] xmfpdlemalnz@hotmail.com:
desperately in need of a fix!!
[Galaxy S II Q&A, Help & Troubleshooting] AJ.Rockwell:
Solution is really simple guys:

1) Get SiyahKernel

2) Get WidgetLocker (great lockscreen app, relatively cheap)

3) ???

4) Profit
[Galaxy S II Q&A, Help & Troubleshooting] ambar_hitman:
Is there any video which demonstrates this lag?

EDIT: Found the video: http://www.youtube.com/watch?v=mQ3pMWTdWHY

I can confirm that there is no such lag on my Galaxy SII I9100G 2.3.6 stock.
[Galaxy S II Q&A, Help & Troubleshooting] dinan:
I have the lag... I attribute it to the phone being in deep sleep. If I turn it on and off repeatedly the lag isn't there obviously since it hasn't had time to go into deep sleep. Also if it's plugged in it won't have the lag.

I get pretty good battery life as it is so if that's the price of good idle battery life then I'll gladly pay it. Also as mentioned before apple products have the same lag. Maybe samsung also has it because they make the chips for apple's processors and decided to incorporate the same technology into their Exynos chip?
[Galaxy S II Q&A, Help & Troubleshooting] SimboXXX:
I just tried with widgetlocker on stock kernel. Works fine.

Edit: It started with no lag but after a few hours began to lag again.

I flashed SiyahKernel and am using WidgetLocker and it still lags. Unhappy.
[Galaxy S II Q&A, Help & Troubleshooting] SimboXXX:
Bump.

No one has this problem anymore?

Tried NEAK kernel without any noticeable difference. Currently using phone without sd card which is slightly better, but a real solution would be nice.
[Galaxy S II Q&A, Help & Troubleshooting] jonny68:
Haven't had this problem now in a long time
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
As far as I know, its not fixable, when the phone is in deep sleep, most of the hardware is shut down. When it wakes up, it has to bring it back online, some of the hardware hangs off the cpu via a usb bus (pretty sure its usb) and it takes somewhere in the order of 500ms+ for it to wake up, thus "wakeup lag".

The only way to not get this supposed lag, is for the phone to never go to sleep.

Also disabling double tap home to launch the voice app thing removes the home button lag.
[Galaxy S II Q&A, Help & Troubleshooting] SimboXXX:
So that would imply everyone has this wake lag, but I don't think that's the case. I would be happy if it were only half a second, but it's a second or more and even worse with SD card.

One of the rom devs here suggested doing a repartition and flash pit, but I've read a few times that's a bit risky so I haven't done it.
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
Just saying, theres always lag, running apps, tweaks (sleep frequency, etc) will make it better or worse.
[Galaxy S II Q&A, Help & Troubleshooting] naturalb0rnkiwi:
Ive found that different ROMS work better than others, not that I use anymore, but criskelo rom was excellent in terms of speed to wake the phone or return home after using and closing apps.
[Galaxy S II Q&A, Help & Troubleshooting] SimboXXX:
Only had the phone a couple of weeks so haven't tried many ROMS. Using now v3rtr3ma 4.3 with NEAK 1.3 and it's lag-free apart from waking lock screen.

2 seconds delay between pressing power button and screen wake is not normal or acceptable in my opinion.
[Galaxy S II Q&A, Help & Troubleshooting] htc9420:
Do you mind bringing some more details about it?

Don't get mad, really, but I won't ever get it why and how come that it takes 500ms+ for a dual core to wake up ( running under Linux):

- assume there are no active wake locks on kernel- other than radio ( and home+ 1/0 buttons) so it's deep sleep state

- input received

Where's the time lost?

It doesn't initialize HDDs, cooling fans, fingerprint devices, Screen lamp, charge the resistive screen, nope

Everything is on stack, all the threads suspended but there...the GPU might take a while but remember, this is SOC just to avoid this...

PS. If the frustration is an unknown feeling yet, I want to suggest a little experiment for some ( only for those unfortunate that experience the lag):

you only need a decent, dual core X86 laptop, press the power button to sleep ( make sure in setting it's configured to sleep). OK, npw press it to wake up. Time? 1 sec. Do it side by side with the SGS2. Hmmm...

- for more frustration try with an I3,I5,I7 + LED screen + SSD ...heh, Windows, anyone?
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
My sgs2 comes out of deep sleep in like.. 1.5s give or take.

And its not the SoC waking up, its the modem that hangs of a usb bus that takes ages to come online (I am not 100% on the info, I am trying to track down my source).

Okies.. I cant find the post anymore, but it basically said that hardware wakeup is surprisingly slow on the sgs2 which accounts for some of the "wakeup lag"
[Galaxy S II Q&A, Help & Troubleshooting] androidkid311:
Wake up lag due to deep sleep of the cores. :D. Mine is about 1.5-2secs. Doesnt bother me. Glad my phone is sleeping. But i hear what u mean... u wont see it on a iphone lool.

Also this isnt to do with wake up lag as such. But i was dwnloading n.o.v.a the other day and my phone was lagging so bad it was frozen for a few secs at times..then would respend then freeze again. I know ita due to the dwnload in the background but damn...thats bad lol. My keyboard got it worse...key inputs didnt register for like...4secs.. :(. Anyone else had this? Or simular.

looks like an iphone but powered by android baby!!!!
[Galaxy S II Q&A, Help & Troubleshooting] htc9420:
I find it hard to believe...if it was the modem, it would have behave the same regardless of the charging state- and we all noticed that it doesn't lag while on charger...also the "USB bus" is a kernel service...

It was suspected that a really bad coded driver does that, I guess it's a bout a call-back handler that double registers and creates a small havoc for 1 sec...

What's interesting about this issue is that it got worse over GB... at least for me.

anyway, I was called an IDIOT here for saying that my device lags at wake up and has an A/os bug...
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
I'm pretty sure the phone doesn't go into deep sleep when on charger, right?

Also, well I wish i could find the post with more info :(
[Galaxy S II Q&A, Help & Troubleshooting] deathst:
Correct, On a charger it will remain clocked at 200mhz
[Galaxy S II Q&A, Help & Troubleshooting] Entropy512:
Correct. If the modem and/or the internal USB bus (which is partially if not fully independent of the external USB port) don't go to sleep, they don't need to wake up. No Android device I know of in existence will enter deep sleep when on a charger of any sort - charging holds a wakelock.

It takes about 650 msec for a complete resume from suspend at the kernel level, and nearly all of this time is waiting for the modem (or at least the main interface between the CPU and modem) to come up. Don't believe me? - look at a dmesg (specifically, timestamps leading up to resume completion) and read the kernel source.

Older Samsung devices used a serial interface to the modem that woke up more quickly. For example, the Infuse completes resume in about 150 msec.
[Galaxy S II Q&A, Help & Troubleshooting] happily1986:
don't understand what is all these fe fi fo fum regarding wake lag. The phone is in deep sleep. I suppose the wake "lag" by any measure is reasonable since it is about 1 second or so. Try to yank yourself out of bed and transit into a fully alert state when you are in deep sleep. sheesh.

I wouldn't be surprised if the same people who complain about wakelag, end up complaining about battery drain when their "wake lag" is "fixed"
[Galaxy S II Q&A, Help & Troubleshooting] aydc:
That's because unlike you, we have had many other phones which also went into deep sleep, but none of them woke up this slowly.
[Galaxy S II Q&A, Help & Troubleshooting] happily1986:
so how slow is slow? 1/2/3 seconds? What was your clock frequency set to in deep sleep?

Anything lower than 200MHz? :rolleyes:
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
I knew you where the one who posted more info, i just couldn't find where, cheers for turning up and saving me from looking like a idiot ;)
[Galaxy S II Q&A, Help & Troubleshooting] htc9420:
I didn't quite dig into the lag for some time, but isn't the modem supposed to have a "partial" wakelock?

1.As for the charging part, I think that the wakelock is from USB service, keeping the kernel up for charging seems like a bad implementation since not the CPU exclusively has the charging part ( you CAN charge the battery while the device is off, unlike WP7 where the OS is required to be running in order to charge).

650 ms is not bad implementation, it's sloppy job. 650 ms reflected in waking up is pure insult, they could've codded the handler at low priority ( for waking up) and let the services like the screen and touch input react without waiting for the modem. 650ms is nothing to us but it's like a full day for the CPU.

2. How come that other SGS2s haven't got the wake-up lag, since it was proven that 650ms is supposed to be present?

PS@ Veyka: You weren't even close to looking like an idiot, really. No way I could think or call someone like that, just for posting some info. If there was to be an idiot, he would be me for not searching more. I just couldn't believe that modem could take that much time to wake up, but it seems that it is like you said.
[Galaxy S II Q&A, Help & Troubleshooting] biffsmash:
For such a high powered phone, the wake lag and lock screen lags are rediculous to be honest.

I've never used a mobile that didn't wake almost instantly.

Let's hope it's fixed in official ICS. I also hope the lock screen unresponsiveness to touch could do with being tweaked too.
[Galaxy S II Q&A, Help & Troubleshooting] lolthrash:
didn't bother to read the whole thread, far too many whingers.

BUT, I used to have this issue a fair bit, but it is basically 100% gone since I flashed the void #echo kernel. Wakes from deep sleep in well under a second and is completely responsive the instant the screen turns on.

While I'm at it plugging that void #echo kernel, I'd like to add that the game "Asphalt 6 HD" is practically unplayable due to lag/glitches (also heats up a crapload and has caused force closes/restarts) on every other kernel I've tried (siyah, speedmod, NEAK etc), yet it runs perfectly on void echo.

I think the answer to everyones problem is to run that kernel.
[Galaxy S II Q&A, Help & Troubleshooting] SimboXXX:
Unfortunately, using void kernel did nothing to speed up the wake time for me.
[Galaxy S II Q&A, Help & Troubleshooting] veyka:
Thats kind of you to say, but I dont normally like posting unsubstantiated info without something to back it up ;)

And I would imagine that there is always some "wakeup lag" but that some people have it worse due to running loads of stuff, eg the crappy FB app in the background and other random bloatware.

Also you have people who lock there screen off frequancy to 100mhz or less so it takes the phone forever to get everything in order!

The only thing I know about the charging is that there is a "kernel wakelock" (According to better battery stats, link in my sig) called "vbus_present" that keeps the phone at 200mhz (according to cpuspy) whenever the charger (and maybe usb cable) are plugged in.
[Galaxy S II Q&A, Help & Troubleshooting] htc9420:
I don't get it why it bothers you so much if people are bothered by the wake up lag. It really bothers you that much that you have the urge to post your distress. This thread is not a spam thread, it's called "wake up lag" and it's the proper way that posts should be made. There is a certain amount of people regarding the lag as unacceptable, some find it inexplicable also. You're lucky to have the device that doesn't have the lag. This does not make the rest of us, just a few, whining psychos.

Just like someone posted before, how come other devices don't have this issue? Is the first time that an dual core enters deep sleep? Human sleep has nothing to do with Android deep sleep. You just can't compare. What is a cold boot then, resurrection from the dead?

An X86 CPU should wake up in about 30 ms running win kernel ( latency is generally regarded as steps of 10 ms for C0 to C1~whatever whatever). X86 design is a hundred fold more complex than in Arm architecture. Yet, it's been known that under certain conditions, the Java machine can induce a big latency under Linux in multicore systems( big was 70- 100ms- at the end it was proven that the C state transitions from deep sleep took most of the time- yet, win7 kernel has no problem waking up in 18 ms). After all, this could have been a Linux+ Dalvik issue. But it isn't an OS issue, it's a latency induced by the modem thread, as Entropy512 explained. Which is not good. 650 ms is huge in terms of CPU handling.

The lag might also prove "deadly" if you were right. The state transition latency ( and implicit the wake up time) is vital for the time it takes pass objects between two threads, producer and consumer. If you regard the time it takes from C0 to C1,C2,C3 as to be inside limits at 600ms+ you just couldn't do anything on that device.

Lags are derived from other links ( like Ram latency and bus speed), CPU is the strongest link in wake-up chain.

I repeat, you are lucky that your SGS2 is free from these flaws. I had 3 devices so far; each had AoS showing high ( thus draining battery), wake up lag and also sleep lag, pink spot on camera. All these issues were posted as early as May, 2011 and no one had rectified a thing. Galaxy Nexus snaps and so does Nexus S, notice that I quoted Sammy devices. HTC snaps. IPHONE 4 does not, but I think it's the IPS lag. Focus and Omnia7 are instant on also.

Wake up lag was present on the SGS1 but some users reported it got solved by Sammy, it was a driver issue.
[Galaxy S II Q&A, Help & Troubleshooting] SimboXXX:
This technical stuff is way over my head, all I know is that not everyone has this issue, so it can be fixed. Now if only someone had a solution...