Hey, didn't find any topic about this so I thought I'd make a thread for it.
Does anyone know for sure if the dreaded wake-up lag (e.g. SII) is still present when we wake the phone from deep sleep mode?
This is one of the things that really bother me about my SII, even if it "just" takes roughly about 1/1.5 seconds to get the screen powered on.
Would be awesome if this minor issue had been sorted out by Samsung in the newest Galaxy S generation
OMG I hate that topic !!!
Dude, the so called wake-lock is due to the phone clocking from deep sleep/200mhz to 1,4 ghz.
If you don't want that "lag" you would have your phone run at "full speed" all the time.
Then the battery drains big time. You wouldn't even be able to use it for half a day
Do you really want that?
Actually, apparently the wake up lag on the S2 was from the phone waiting for the modem to become active.
So the S2 should wake up faster, but the hardware design is a bit... silly?
Anyway, I hope the S3 wakes up a LIL faster. I don't have a problem with the S2's wake up time, but I wouldn't mind it being faster
Master05 said:
OMG I hate that topic !!!
Dude, the so called wake-lock is due to the phone clocking from deep sleep/200mhz to 1,4 ghz.
If you don't want that "lag" you would have your phone run at "full speed" all the time.
Then the battery drains big time. You wouldn't even be able to use it for half a day
Do you really want that?
Click to expand...
Click to collapse
Well I know that mate, but there are phones out there which doesn't have this "issue" so one might think Samsung may have improved this in their newest iteration of the Galaxy S series.
This topic should evaluate whether this lag still exists or not. Simple as that.
No need to roll your eyes, dude
GalaxyFan88 said:
Hey, didn't find any topic about this so I thought I'd make a thread for it.
Does anyone know for sure if the dreaded wake-up lag (e.g. SII) is still present when we wake the phone from deep sleep mode?
This is one of the things that really bother me about my SII, even if it "just" takes roughly about 1/1.5 seconds to get the screen powered on.
Would be awesome if this minor issue had been sorted out by Samsung in the newest Galaxy S generation
Click to expand...
Click to collapse
Gotta ask the reviewers who have touched the phones for that.
i just bought the SGS3 and it take around 1.5 secs to wake up. is this normal? my sensation XE didn't do that
essamrafie said:
i just bought the SGS3 and it take around 1.5 secs to wake up. is this normal? my sensation XE didn't do that
Click to expand...
Click to collapse
Well mine was pretty instant when i was using it for the first time yesterday, have noticed that there is slightly more lag tonight when unlocking the phone from sleep mode..
Dunno if theres anything we can do? Maybe the more experienced galaxy users might know more
The lag is present for me too (but about 0.5 - 1 second), but I guess when custom kernels with additional governors and maybe modded rils come up it will get way better, just have patience.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Master05 said:
OMG I hate that topic !!!
Dude, the so called wake-lock is due to the phone clocking from deep sleep/200mhz to 1,4 ghz.
If you don't want that "lag" you would have your phone run at "full speed" all the time.
Then the battery drains big time. You wouldn't even be able to use it for half a day
Do you really want that?
Click to expand...
Click to collapse
Dude you've never seen an HTC or Motorola or LG or Sony Android phone have you? Everyone makes Android phones and only Samsung products have wake up lag. Competitors phones don't have to run full speed all the time to wake up instantly. If everyone else can do it, why can't Samsung do it?
Even if you want to check the clock, you have to wait 1-1,5 seconds. That's epic fail for me.
The phone goes into deep sleep and this permeates to other devices such as the modem.
Wake up occurs and the exynos soc has to wait for the modem to wake up. Just a silly way Samsung does things.
Speeding up the CPU won't help much, deep sleep is effectively 0mhz just because the min freq is say 1000mhz or even 1400mhz deep sleep c states are what they are.
The solution is wake lock, it keeps the entire motherboard active full time. The most reliable method that doesn't find itself getting killed in the background is android terminal emulator app. I'll attach a screenshot on where the option is. The ongoing notification icon is the magic trick that makes the app reliable, stops the android task manager/memory manager from killing its process occasionally.
There is no fix, there will never be a fix there will be workarounds. I pull this off by using a combo of very efficient CPU settings and the official sgs2 exbatt.
Related
I'm running JT's vanilla GB [over Heimdall'ed stock EH03] on my fascinate.
I use my fascinate as my alarm clock, and I woke up this morning to a extremely choppy ringtone. < and that is is the understatement of the day.
Anyway, I try to press "dismiss" to dismiss my alarm, and it feels like the screen is not responding. I press the power button, and it takes probably like 5 seconds to complete the CRT animation. After that, I can see the screen is still on (hard to tell unless in the dark with the AMOLED), and it won't do a thing after that until I 3-button-combo or take out the battery.
As a side note, it was also doing this on my previous rom, SuperClean3 v8.1. One of the main reasons I switched back to JT's vanilla gb.
The first night the alarm worked fine. [2 days ago] Yesterday, I was watching some video files, I pressed the power button, I left for a few minutes, I came back and it was frozen. [Took foreverrrrrr for the CRT turn-on animation, and screen did not respond].
This is really really annoying, and I would really like to find out what is wrong with my phone.
One more thing I should mention.. this same kind of thing happened once in a while on the stock froyo firmware, when I bought it on craigslist. I would come to it sometimes and turn it on, and the lockscreen would show and the touchscreen wouldn't respond. I had to take the batt. out then cuz I didn't know about 3-button-combo.
The USB would only charge and not transfer files and only would charge.
So I sent it in cuz samsung said I had 1 mo. warranty left, and then they said they fixed everything in the ticked, and I got it back and it seemed to work. [the usb file transfer worked..]
So can anybody give me any advice? Like logcat? Would that tell me what is causing this problem?
Any help is appreciated!
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
k_nivesout said:
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
Click to expand...
Click to collapse
Thanks for the reply. I will look into this 'sleep of death' thing.
And I haven't edited my cpu settings. I went to superuser to be sure and the only apps listed are Superuser, Terminal Emulator, and Titanium Backup.
So I just went on a 1-hour trip, and when I got to where I was going, this happened to me again. The screen-on animation was slower than a slug on salt. 3-button-combo reset, I let it reboot, and it was fine.
I just got home 1/2 hr ago and it did it again.
Sigh.. well I only have like 2 apps that always run, 3G Watchdog and Equalizer. I've uninstalled 3G WD just to see if it does anything.
Edit: I will install ROM Manager and set the absolute minimum freq to 200mhz, and see what happens. That would make sense if it's messing up at 100mhz when the screen goes off, and then it's not able to think fast enough to up it back to 1ghz.
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have much expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
k_nivesout said:
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
Click to expand...
Click to collapse
My bad, I meant ROM Toolbox. It has lots of apps built in including a CPU slider. Anyhow disabling 100mhz did not fix anything. So tonight I will set the minimum frequency to 800 or even 1000 mhz because I want to see if that stops the freezing up. If it does, then I'll know it's a clock speed issue.
I should also mention I sent it in for USB repair. It wouldn't connect to PC, it'd only charge. I also mentioned to Samsung it would lock up every so often from waking up. They upgraded froyo to gingerbread and said it passed all tests, sent it back, I never stayed on the firmware they gave me long enough to see if it froze up.
So on the stock roms, do they underclock the cpu frequency by default??
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
k_nivesout said:
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
Click to expand...
Click to collapse
Lol, when I sent it in there was like half a month or so left on the warranty, the person said it expires at the end of this month [Dec] so I figure maybe a day or two.
What's the IRC channel info? freenode?
EDIT: I forgot to ask something. So you are saying, the stock firmware [EH03 or froyo EH09] runs the cpu clock constantly at 1GHz? Even when it's sleeping? Wouldn't that give bad battery life? [lol, speaking of batteries, I just got a new one and it's charging]
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
gotsflat4love said:
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
Click to expand...
Click to collapse
This is bad news indeed, since I am not even sure how many days I have on the warranty. But I think I will Odin EH03, and then set the alarm tonight. If I wake up and it's done it again, I will call up samsung and tell them and hopefully I have warranty.
But please, tell me, when you tried to turn on the phone did the CRT animation go very slowly? and then when you pressed power, it wouldn't come on again?
Edit 2: alright! I call samsung and I have warranty until Jan 9. Woot.. So I set up an RMA with samsung, I will Odin EH03 tonight. If I wake up to a choppy alarm and a non-responsive screen, I shall send it to samsung ASAP and I hope they gimme a brand new Fascinate. that would be awesome..
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
k_nivesout said:
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
Click to expand...
Click to collapse
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
So this morning, I woke up to my iPod's alarm, which I had set as a backup a few minutes after my Phone alarm should have gone off. I went to see if the phone was frozen, like I was hoping, so that it would reliably broken , but instead it was off. I turn it on, it shows the full green battery.. then it boots up like nothing was wrong. But I think that turning off randomly every night [which I assume it should do every time] is enough for Samsung to realize my phone really is screwed and that they need to do something about that.
So anyway, I printed out the label, packed my phone, and dropped my phone off at the local UPS drop off.
Hopefully I will be receiving some good news from samsung soon [i.e. that they will give me a replacement... ]
mvmacd said:
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
Click to expand...
Click to collapse
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
k_nivesout said:
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
Click to expand...
Click to collapse
1. I'm not the original owner
2. I'm not a Verizon subscriber. PagePlus Celluar [A verizon MVNO] is my service provider. They have much better plans, including monthly, and prepaid, if you ask me.
Kernel issue.
sent from my Sensation XD
Yess..
Good news! Got an email saying my phone has been shipped:
Code:
Original Problem:
TECHNICAL INQUIRY - PHONE FREEZING / LOCKED UP - FREEZE/DELAY BETWEEN MENU FUNCTIONS
Problem found:
BAD BGA COMPONENT
Solution:
REPLACED PBA
I guess the PBA is basically the motherboard? I suppose that could have been the cause of overnight freezing, and so my phone should be fixed.
Nice.. Just 2 days left on my warranty. Cutting it kinda close, I know lol
Very well done sir
sent from my Sensation XD
Just wondering if there are any fixes out there for the lockscreen lag / delay that seem to be an ongoing issue in Samsung based ROMs.
For anyone not knowing what I mean, its the way that the homescreen appears briefly after waking the phone before the lock screen appears. Its not a big deal, but does look a little "unpolished". Its an issue, that, if I can fix, would solve one of my last remaining issues with the phone.
Try cm7,cm9 or miui. It wakes before you press home
Sent from my GT-I9100 using xda premium
I know they do, as I've tried them all... but I'm on a Samsung based ROM, and as I've got my phone set up exactly how I want it, I'll be staying on it. I'm using the Samsung based ROM because (shock horror) I quite like the way it looks, and is the most "fluid" / smoothest I've tried so far.
Any new about this delay?
Why is it happens? Maybe because the cpu clockdown or something so its take another second to wake the screen on?
PsyOr said:
Any new about this delay?
Why is it happens? Maybe because the cpu clockdown or something so its take another second to wake the screen on?
Click to expand...
Click to collapse
You can try to bump up the min to 500mhz
Sent from my GT-P7510 using xda premium
I'm trying to figure this out too,but no one seems to know the answer.
norpan111 said:
Try cm7,cm9 or miui. It wakes before you press home
Click to expand...
Click to collapse
What a load of BS. The S2 will always take at least 0.65 seconds to wake-up, no matter what Rom, kernel, whatever you use.
ionutz727 said:
I'm trying to figure this out too,but no one seems to know the answer.
Click to expand...
Click to collapse
Everybody knows the answer. There are countless threads already on this subject. Search for Entropy512 and his thorough explanation and don't believe people who say they have no lag.
Pfeffernuss said:
What a load of BS. The S2 will always take at least 0.65 seconds to wake-up, no matter what Rom, kernel, whatever you use.
Everybody knows the answer. There are countless threads already on this subject. Search for Entropy512 and his thorough explanation and don't believe people who say they have no lag.
Click to expand...
Click to collapse
I know there are many threads regarding this, I have myself one. One of my friends said to me that his s2 wakes up instantly after he presses the home/power button. It is also said that the new aokp roms solved this issue,and users reported this too. But there are others,like me, who still have the lag (1-2 seconds). So i guess i did something wrong with the installation of the roms or anything else. I can't figure it out.
Well,i tried both cm9 and miui roms and i still have the lag.
seems like it should be a 'lag' because the deep sleep mode, its save much more battery on idle..
i'v just notice it too, maybe it always was ...
correct me if i'm wrong...
PsyOr said:
seems like it should be a 'lag' because the deep sleep mode, its save much more battery on idle..
i'v just notice it too, maybe it always was ...
correct me if i'm wrong...
Click to expand...
Click to collapse
+1, ur very true ma8 as long as the phone is in perfect deepsleep mode this lag of 1~2 sec do remain and its nothing when compared to the better batt life with good deepsleep
PS- just check the same when ur phone is charging and u dont see that lag since its @ 200mhz always
PsyOr said:
seems like it should be a 'lag' because the deep sleep mode, its save much more battery on idle..
i'v just notice it too, maybe it always was ...
correct me if i'm wrong...
Click to expand...
Click to collapse
i know about deep sleep mode. but i don't understand why some people have this lag and others don't.
Maybe for them 1-2 sec ain't call 'lag'.
Until you'll see it in your own eyes, you could judge.. . I bet they didn't waited at least 10 sec to get into the deep sleep...
When I lock the screen of my Galaxy S3, then press either the power button or the home button to show the lockscreen, about half the time it takes about 2 seconds to show the screen after button press. I've searched and seen S-Voice caused this problem so I disabled that. I also removed my SD card and rebooted but the same issue still occurs.
Any way to fix this because my HTC One X didn't have this problem...
Thanks.
wman2 said:
When I lock the screen of my Galaxy S3, then press either the power button or the home button to show the lockscreen, about half the time it takes about 2 seconds to show the screen after button press. I've searched and seen S-Voice caused this problem so I disabled that. I also removed my SD card and rebooted but the same issue still occurs.
Any way to fix this because my HTC One X didn't have this problem...
Thanks.
Click to expand...
Click to collapse
Flash other ROM can make it faster...
Or tune off power saving mode.
photomrq said:
Flash other ROM can make it faster...
Or tune off power saving mode.
Click to expand...
Click to collapse
Power saving mode is already off. I don't particularly want to flash a ROM unless I have to because I've had warranty troubles in the past. Are you certain a ROM would fix it? Which ROM?
And I also tune lock screen off.
Do you install any power save app??
Two Whole Seconds close your eyes and count to ten not worth the bother wait for JB release ,
jje
I get this also. Got it on the Stock ROM and ARHD. I have also seen this on my gf's Galaxy Ace, but only when upgraded to GB. On Froyo (Yes, that old version) it turns on instantly. So think it might be a Samsung thing. Not yet tried an AOSP ROM on my S III yet so may give that a go as itching to get some Jelly Bean on it.
Hello! I am new to xda forums and this is my first post
I also have a problem with slow wake up time from sleep after flashing the latest Synergy rom. Any ideas why this lag happens?
Thank you in advance!
this lag is killing me. it's mega retarded that high end phone is having this kind of bug.
any rom without slow wake lag to reccommend?
bojler said:
this lag is killing me. it's mega retarded that high end phone is having this kind of bug.
any rom without slow wake lag to reccommend?
Click to expand...
Click to collapse
Is a one second lag really spoiling your experience? Then flash to a non TW rom.
Sent from my GT-I9300 using xda app-developers app
kofiaa said:
Is a one second lag really spoiling your experience? Then flash to a non TW rom.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Lag is hardware-related looks like. Present on CM10 based ROMs as well. On stock-based disabling S-Voice helps just a little bit when it comes to waking up from Home button...
Killing me as well. :\ What I getting used to is to press Home while pulling phone out - straight away so by the time I get it in position to work with, the screen is either already on or will be on in a 200-500 ms.
Still this is a most frustrating "feature" of SGS3 that will most likely force me to look for replacements once those are available on the market.
The issue is still present even in the latest Paranoid Android ROM.
After tweaking a bit, I found that if you have WiFi enabled, will cause this lag.
Just disable the WiFi and you get instant screen wake up.
inteq said:
After tweaking a bit, I found that if you have WiFi enabled, will cause this lag.
Just disable the WiFi and you get instant screen wake up.
Click to expand...
Click to collapse
No difference here
Sent from my GT-I9300 using xda premium
This problem annoys me to death too. I've tried many ICS/JB stock ROM and custom ROM (including CM10), but none of them could solve the problem.
I did notice some trend: right after a reboot, the screen turns on fairly quickly. Then after turning on the network (mobile data or wifi) and use facebook or other apps that access network for a few minutes, the delay starts to increase to the usual ~2sec. Looks like some network process might be causing the problem. FYI, My cousin's Note 2 don't seem to have this problem.
Any hacker out there can give some hints or help find out what process might be the culprit?
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
mingan84 said:
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
Click to expand...
Click to collapse
"not as good" would be too soft of a term. It'll kill your battery life probably
mingan84 said:
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
Click to expand...
Click to collapse
From what I see, I don't believe deep sleep is the problem. My LG P500 (running ICS) goes into deep sleep all the time (per CPU spy et al), and it never has this problem. Seems to me like something else is causing this...
ligu said:
From what I see, I don't believe deep sleep is the problem. My LG P500 (running ICS) goes into deep sleep all the time (per CPU spy et al), and it never has this problem. Seems to me like something else is causing this...
Click to expand...
Click to collapse
no other brands have this problem. only samsung, thats so strange.
I too suffer from wakeup delay of 1-2 seconds and it's driving me crazy.
After 2 long years I had to live with majestically f**ed up LG Optimus 2X, I finally decided to throw that junk away and get a phone that works as expected, phone performance of which would be equal to it's price (and the price was not something that limited me).
Now I own a phone which even though is snappy and nice and everything, takes ages to wake up. And what pisses me off the most is that Samsung is OK with that, because obviously majority of the customers / owners is OK with that. How is that possible ffs. Low end devices for fraction of that price resume from deep sleep almost immediatelly (in time I don't consider waiting). How's that this is not a big issue ?!
Sorry, I'm just frustrated
EDIT: To add something constructive ... the deep sleep really is the problem here. If the phone doesn't go to deep sleep, wake up to lockscreen is instantaneous (try that by yourselves with SoftLocker app). It's believed that S3 suffers from this issue because of the way the GSM modem is integrated with (or in ? I am not sure) Exynos4 - source.
I just smacked my phone in the table, while in my pocket and now I"m experiencing the same problem. Is this even possible, or I had it before and just didnt notice till now?!
Hi guys, I'm running the latest version of Slim Bean with stock modem XXLE8 and whatever kernel comes with Slim. I've noticed that there is a 1.5-2 second delay upon hitting the power or home button to the screen turning on and being ready to use. It's pretty annoying as you can imagine, I've actually figured out what the problem is, my phone is going to deep sleep too early and is taking up to 2 seconds to wake up, I wouldn't mind this if the phone has been left alone for 2 hours or so, but if I leave my phone for 5 minutes I shouldn't have to wait 2 seconds to unlock it. I came to this conclusion by using the app softlocker from the market, which disables sleep, and the lockscreen is perfectly fine with no lag, so should I try a new modem or a new kernel or is there something else I have to try to solve this issue?
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
DeadVirus said:
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
Click to expand...
Click to collapse
I've read both but neither seem to provide much of a solution. It is pretty ridiculous a phone like the S3 with such powerful hardware suffers from unlock lag. My HTC Desire Z used to unlock instantly... Kinda disappointing.
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
theslashy said:
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
Click to expand...
Click to collapse
I've been looking but can't seem to find one. The delay is about 1.5-2 seconds on Siyah, was about the same with YANK kernel.
jj92942000 said:
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmmmmm I might flash a stock rom and check it out because I don't remember it happening when I was running stock, tho that was for a grand total of 3 days lol.
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
0semaj0 said:
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
Click to expand...
Click to collapse
sure, but i own quite a view other android phones and none behaves like the s3, not even the superlow-budget htc one v
i installed the omega 4.2 AOKP rom today, but the lag is there, too....i got back to arhd for now...
theres a app called softlocker, but with that the cpu never gets to deepsleep, my s3 gets warm and the battery drains badly
Hey guys, I'm currently using Samsung's 4.3 ROM (XXUGMJ9) with DerTeufel1980's Devil2 kernel.
After leaving my phone for a few hours, I return to it and notice that the phone lags a lot. It wakes up quickly but the entire UI is very laggy. CPU stats shows that the phone is using all cores at 1.4Ghz with usage typically above 80%. If I leave my phone on idle for just a hour or two, it does begin to lag but not as much as if I left it for 5+ hours. If I leave my phone overnight, I'll return to it switched off (I do believe that this is related to the lag issue). If I restart the phone, the problem disappears - is anybody else getting this or is this just me?
Samsung have just re-released fixed 4.3.
Gold_Diesel said:
Hey guys, I'm currently using Samsung's 4.3 ROM (XXUGMJ9) with DerTeufel1980's Devil2 kernel.
After leaving my phone for a few hours, I return to it and notice that the phone lags a lot. It wakes up quickly but the entire UI is very laggy. CPU stats shows that the phone is using all cores at 1.4Ghz with usage typically above 80%. If I leave my phone on idle for just a hour or two, it does begin to lag but not as much as if I left it for 5+ hours. If I leave my phone overnight, I'll return to it switched off (I do believe that this is related to the lag issue). If I restart the phone, the problem disappears - is anybody else getting this or is this just me?
Click to expand...
Click to collapse
Search google and u will know the first release of 4.3 by samsung for the gs3 is very buggy. Like JJEgan said, samsung is re-releasing a new one over time.
Sent from my GT-I9300
JellyYogurt said:
Search google and u will know the first release of 4.3 by samsung for the gs3 is very buggy. Like JJEgan said, samsung is re-releasing a new one over time.
Sent from my GT-I9300
Click to expand...
Click to collapse
I've heard about today's release, been trying to get my hands on it but it doesn't seem like anyone has posted anything reliable. But yeah, I know the current ROMs are very buggy, I was just wondering if this was one of the bugs or just me doing something that messed it up somehow
Gold_Diesel said:
I've heard about today's release, been trying to get my hands on it but it doesn't seem like anyone has posted anything reliable. But yeah, I know the current ROMs are very buggy, I was just wondering if this was one of the bugs or just me doing something that messed it up somehow
Click to expand...
Click to collapse
Its the rom's fault. Dun worry I always advise tat u wait for a week after samsung releases 4.3 to see if others reported bugs or anything.
Sent from my GT-I9300