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?!
Related
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...
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.
I had home screen loading lag before but fixed it by disabling s-voice and after a few days the home screen loading lag (a few seconds) came back. What is making it take so long to load?
Sent from my GT-I9300 using XDA
uf21 said:
I had home screen loading lag before but fixed it by disabling s-voice and after a few days the home screen loading lag (a few seconds) came back. What is making it take so long to load?
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
I agree, its just as bad as the SG2 for lag. It can be as long as 2 seconds or more to come on.
S-Voice made no difference really for me, which for the record is complete rubbish!
I must admit though, it may be since i rooted it with the CF kernel... I can't recall the issue before, but then I did root it within minutes of powering it on.
I wanted to share this with the forum. I bought the Galaxy S3 as soon as it came out and immediately installed the same apps that I had on the S2. My S2 never lagged and had a brilliant low battery usage, so my dissapiontment was great that the S3 consumed battery like cold beer on a summerday and was lagging up to several seconds between home screens. Finally today after reading this thread I thought of removing my widgets one after one and checking lag each time. Lag could be confirmed with 100% certainty by going to settings>wifi and then going back to home screen and switch. Every single time it would lag up to several seconds. When I uninstalled Palmary weather widget, every single trace og lag was completely gone. I have tested this about 100 times now, restarted the phone several times. The result is, no lag at all without palmary and every single time I add Palmary weather as a widget again, it starts lagging. Maybe it isn´t Palmary for everyone experiencing this problem, but try removing widgets one after one and testing or remove them all and add them one after the other, while testing in between. The only problem I have with the S3 now (stock rom updated and rooted) is the terrible cell standby power consumption. I solved this by only using only gsm for now, but this is not acceptable and I expect Samsung to confirm this problem and fix it, and do it fast. My S2 is a far superior phone as things are now, except from design.
Regards
John
Cell standby isn't using a lot of power, its being calculated incorrectly.
In the stats it should be a draw of 3.4ma but instead someone forgot the . So it thinks its using 34ma.
It isn't
Its only a mistake in stats.
This had been well documented here.
Sent from my GT-I9300 using xda premium
Ok, but nevertheless, it´s eating up the juice way too fast with mobile data enabled. The S2 didn´t do that.
ducknaldo said:
Ok, but nevertheless, it´s eating up the juice way too fast with mobile data enabled. The S2 didn´t do that.
Click to expand...
Click to collapse
Flash a different modem and test.
Sent from my GT-I9300 using xda premium
Thanks for the info John. I tried your thought of removing the weather widget but it didn't improve my 1-2sec lag from switching on and off for me. It happents intermittently and I dnt have too many things running anyway. Its strange to say the least.
sent with WSGS3
Use nova and set animation scale to 0.5x
Sent from my GT-I9300 using xda premium
But if there are other handsets that don't have lag with the touchwiz, then we shouldn't have to install nova to cure the problem. I already have 0.5 for the animations. I'm pretty sure that its widget/app related but hey. This is what happens in complicated machines.
sent with WSGS3
vasp3690 said:
But if there are other handsets that don't have lag with the touchwiz, then we shouldn't have to install nova to cure the problem. I already have 0.5 for the animations. I'm pretty sure that its widget/app related but hey. This is what happens in complicated machines.
sent with WSGS3
Click to expand...
Click to collapse
Agreed, it's just ****ty programing from Samsung
Sent from my GT-I9300 using xda premium
Noticed something else. I had cpu reduction for power saving. Once I cancelled that the lag is gone unless I had multiple apps running in the backround. So that may play some role as well.
sent with WSGS3
This isn't exactly a scientific answer but when I press my home button lightly there is a delay for the screen to come on but if I push it harder the screen comes on right away. True Story
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 folks,
New guy here, just picked up a new LG Optimus G on AT&T yesterday afternoon to replace my aging Samsung GS2. This was a somewhat quickly made decision (for me anyway) so I haven't done as much research on the LGOG as I typically do before purchasing a new device...it's quite possible I missed something stupid. If so, flame away...
As of right now, I'm stock/unrooted, with a small number of primary use apps installed. While screwing around getting familiar with the device yesterday, I noticed a high level of msm_hsic_host wakelocks, with an apparently related but smaller amount of suspend_backoff wakelocks in Better Battery Stats. CPUSpy indicated approximately 25% deep sleep for the run, which was about10 hours from purchase to going to bed - with a partial charge in the middle.
This concerned me slightly, so I let the device charge overnight, then unplugged this morning and let her go on a screen-off draindown test. Did a 50 minute run, which resulted in zero battery drain (still at 100% for a few moments when I lit the screen up at the end of the run) but ZERO deep sleep. The vast majority of the run was spent at 384 MHz, with small amounts at 1512. This run was done while on an ATT microcell for calls and WiFi on for data (set to stay on with screen off). Background data was on. While I am quite impressed that I'm seeing 1-2% drain per hour with no deep sleep, I have to believe this is not how the device is supposed to operate.
Prior to buying the LGOG, while looking at the forums here, I noted that Jank4AU was here - a name I recognized from the Aria and SGS2 forums. He provided an excellent overview of the device (via PM - Thanks Jank4AU) and mentioned the need for rooting to disable fast dormancy, which apparently AT&T, in their infinite wisdom, left enabled by default, to improve battery life. My limited experience with chasing wakelocks indicates that HSIC is likely radio related. Is this msm_hsic_host wakelock triggered by the fast dormancy system? My searches have turned up little to indicate either a yes or a no...
forum search turns up this (partially related??): http://forum.xda-developers.com/showthread.php?t=2144927&highlight=msm+hsic+host
Google search turns up a bit more, but very Nexus 4 focused (I realize they are similar devices -- possibly similar fixes??):
https://productforums.google.com/forum/?fromgroups=#!topic/mobile/jO65dcM7J2Y[1-25-false]
On the sprint version (wifi related for us too? WiFi off drain test is next for me I think.): http://forum.xda-developers.com/showthread.php?t=2106529
It looks like Thracemerin is chasing it in kernel development for 4.2.2: http://forum.xda-developers.com/showthread.php?t=2102986 Is this less of an issue on JB than on the stock ICS for our devices?
At any rate, I'm still digging though the ROM threads, but will likely be rooted and maybe off stock by the end of the day today. I'm looking forward to spending some time with the LGOG community, and hopefully I'll be able to contribute meaningfully at some point!
Sorry for the great wall o' text...
DD
Yep. My wife's phone running rooted stock has it. Mine so far doesn't
gunnyman said:
Yep. My wife's phone running rooted stock has it. Mine so far doesn't
Click to expand...
Click to collapse
Interesting. Can you elaborate on what may be different, set up wise, between yours and your wife's phones? Particularly radio/Wi-Fi settings or presence/absence of Wi-Fi use environments?
Sent from my LG-E970 using Tapatalk 2
Nothing different between our phones bloatware frozen. She spends a lot more time away from wifi than I do. I just disabled fast dormancy and installed better battery stats on both of our phones. I'll keep an eye on things and compare both at the end of the day
I made a thread a few months back about this wakelock. As I've flashed ROMs and have fast dormancy disabled, the problem has vanished. I had the wakelock on stock unrooted, stock rooted, and stock ICS ROM.
Sent from my LG-E970 using xda app-developers app
I applied the fast dormancy fix and all is well here too
I was seeing this wakelock a lot too, but only noticed it (only ever installed BBS) AFTER disabling fast dormancy. In the process of trying to tack this down, I froze a bunch of apps, turned off a bunch of background syncing type stuff, re-enabled FD, and I've had wifi off the past 2 days, and now the wakelock is still the highest on the list, but it's usually < 10% now instead of 44%, and my deep sleep percentage has reversed, from 25% to 75% now. Re-disabling FD doesn't seem to have made any difference. Is FD only relevant for LTE? I only have 4G here.
Yeah, there's a fast-dormancy toggle app in the themes and apps section. It will greatly reduce your wake-locks.
Sent from my LG-E970 using xda app-developers app
Murasakiii said:
I made a thread a few months back about this wakelock. As I've flashed ROMs and have fast dormancy disabled, the problem has vanished. I had the wakelock on stock unrooted, stock rooted, and stock ICS ROM.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
gunnyman said:
I applied the fast dormancy fix and all is well here too
Click to expand...
Click to collapse
Thanks for the input folks, looks like it's time to root for me. FWIW, I tried running with wifi off, and saw small (8ish) percentage deep sleep.
jdock said:
I was seeing this wakelock a lot too, but only noticed it (only ever installed BBS) AFTER disabling fast dormancy. In the process of trying to tack this down, I froze a bunch of apps, turned off a bunch of background syncing type stuff, re-enabled FD, and I've had wifi off the past 2 days, and now the wakelock is still the highest on the list, but it's usually < 10% now instead of 44%, and my deep sleep percentage has reversed, from 25% to 75% now. Re-disabling FD doesn't seem to have made any difference. Is FD only relevant for LTE? I only have 4G here.
Click to expand...
Click to collapse
Hmmmm...if I understand you correctly, you're seeing the opposite behavior of those two above? I am also in a Non-LTE area...be interesting to see what I see.
Jank4AU said:
Yeah, there's a fast-dormancy toggle app in the themes and apps section. It will greatly reduce your wake-locks.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Sweet. I'm missing Google Now an awful lot...I'm thinking a switch to the SnowJB ROM might be in order...appears that has "built-in" fast dormancy "fix" - I assume this means it's disabled by default on that ROM.
Got revert to stock all set up on my PC, so now I get to go root. This will be the soonest after purcahse I've rooted a new device (previous quickest was 4 days for the SGS2). Thank you all for the warm and helpful welcome to the LGOG device forums!
Edit: just out of curiosity, what do you guys typically see for deep sleep percentages? On the SGS2 85% or so was about my average on ICS with my full complement of apps and background data running. That dropped to 75-80% with Google Now running in the background.
DD
http://forum.xda-developers.com/showthread.php?t=2050582
The zv9 zvb root works on 11c.
I am seeing the opposite of some of the others in a way.... I can't say that disabling FD hurt me and I can't say that enabling it helped me. All I can say for sure is in my case it doesn't seem to make any difference one way or another.
Also, the FD toggle app doesn't require root. Not that you shouldn't root, just that you don't need to in order to try this.
adfurgerson said:
http://forum.xda-developers.com/showthread.php?t=2050582
The zv9 zvb root works on 11c.
Click to expand...
Click to collapse
LOL, Thanks adfurgerson (another i777 convert iirc?). By the time I got back to read this I was already rooted and unlocked via the guide sticky procedure! Went without a hitch.
dandrumheller said:
LOL, Thanks adfurgerson (another i777 convert iirc?). By the time I got back to read thCFC I was already rooted and unlocked via the guide sticky procedure! Went without a hitch.
Click to expand...
Click to collapse
Yes I had I777, so far this is a good group here. Seen you found irc channel. If you can do without camera and GPS cfx is nice.
adfurgerson said:
Yes I had I777, so far this is a good group here. Seen you found irc channel. If you can do without camera and GPS cfx is nice.
Click to expand...
Click to collapse
Yeah...I might be able to live without one or the other (GPS is easier to get along without for me) but without both, it's not quite to daily driver status for me. I thought I saw some comments from the dev that kernel work towards getting the camera going is almost ready. At that point I might give it a shot.
Edit: OK, first dumb question of my time here (won't be the last): Is there a key combo to get into recovery? Google pointed me to either vol-/power or vol+/home/power. Neither of these worked for me, all I can seem to get with keys is fastboot. Had to ADB into recovery to make my backup...gonna flash SnowJB once that's done.
dandrumheller said:
Yeah...I might be able to live without one or the other (GPS is easier to get along without for me) but without both, it's not quite to daily driver status for me. I thought I saw some comments from the dev that kernel work towards getting the camera going is almost ready. At that point I might give it a shot.
Click to expand...
Click to collapse
I believe that I put up an ICS version of Google Now in my inverted apps thread if you aren't ready for JB yet. Also, in that same thread, there is probably still a copy of Google Now (not inverted) for ICS as posted by XsMagical. If you can't find it, PM me and I'll send the file to you.
Jank
Jank4AU said:
I believe that I put up an ICS version of Google Now in my inverted apps thread if you aren't ready for JB yet. Also, in that same thread, there is probably still a copy of Google Now (not inverted) for ICS as posted by XsMagical. If you can't find it, PM me and I'll send the file to you.
Jank
Click to expand...
Click to collapse
Thanks, appreciated. Just got SnowJB flashed (glad to be rid of that damn carrier id in the notification bar, since it says ATT Microcell at home and takes up most of the notification bar!). If I run into issues, I'll jump back and take a look at your ICS GNow...
dandrumheller said:
Thanks, appreciated. Just got SnowJB flashed (glad to be rid of that damn carrier id in the notification bar, since it says ATT Microcell at home and takes up most of the notification bar!). If I run into issues, I'll jump back and take a look at your ICS GNow...
Click to expand...
Click to collapse
Good deal, that SnowJB is pretty smooth.
Itnis hidden menu for recovery, volume up and power for bootloader then volume up twice then power. Quickboot app also works.
adfurgerson said:
Itnis hidden menu for recovery, volume up and power for bootloader then volume up twice then power. Quickboot app also works.
Click to expand...
Click to collapse
Gotcha...thanks. I have quickboot now, so all good. knowing that combo is nice in case I get in a pinch sometime though and am working from stock without ADB available (hopefully that never happens ). Is that button combo/hidden menu stuff posted somewhere? If so I missed it. Might be a good thing to add to one of the "read me first" kinda stickies (assuming it's not already there and I missed it)...
Edit: And first short duration drain test after root/unlock/SnowJB1.1 is giving me 68% deep sleep - with GNow enabled and full complement of apps (a bunch more apps than previous test).
Edit 2: Initial 3 hour test after SnowJB install - 5% total battery drain over 3 hours, including 20 minutes screen on for browsing. 70.4% deep sleep, with minimal (1min 30sec) running at max CPU. I'm used to seeing 5% drain just from that much screen on time, so this is excellent performance in my book!
Oddly enough,my phone was kept awake by msm_hsic_host wakelock for over 7 hours last night. I'm abroad at the moment, with my phone in airplane mode all the time, wifi was turned off during that time, and the fast dormancy toggle was doing its thing. Weird. I'll see if it happens again tonight.