So I spent about four hours researching this. From flashing kernels removing apps and installing modems nothing worked. EXCEPT putting phone in airplane mode, rebooting, then disabling airplane mode. Phone enters deep sleep quickly and consistently after performing this. I encourage anyone with this issue to try the steps above and report back. Note to devs if this is in fact a fix, can you incorporate some kind of script that places phone in airplane mode on reboot and automatically disables on boot? I believe a lot more people are affected by this than we know. Does anyone NOT have this issue? if you know for a fact your phone spends a lot of time in deep sleep please identify which modem you are using. Supposedly this occurs due to a lack of response from modem to os.
from chewable on ics forums:
Bad battery drain due to a wakelock being held for an unspecified length of time. BetterBatteryStats shows it to be RILJ holding the wakelock. I've narrowed it down to a RIL request named RIL_REQUEST_SET_TTY_MODE. I dumped out RILJ.mRequestsList during the held wakelock and I see this request staying around and waiting for a response from the RIL. It's as if the RIL is not responding to this request and I don't see RILReceiver processing a response to this request.
anyone know what tty is?
Sent from my SGH-I777 using xda app-developers app
topiratiko said:
So I spent about four hours researching this. From flashing kernels removing apps and installing modems nothing worked. EXCEPT putting phone in airplane mode, rebooting, then disabling airplane mode. Phone enters deep sleep quickly and consistently after performing this. I encourage anyone with this issue to try the steps above and report back. Note to devs if this is in fact a fix, can you incorporate some kind of script that places phone in airplane mode on reboot and automatically disables on boot? I believe a lot more people are affected by this than we know. Does anyone NOT have this issue? if you know for a fact your phone spends a lot of time in deep sleep please identify which modem you are using. Supposedly this occurs due to a lack of response from modem to os.
from chewable on ics forums:
Bad battery drain due to a wakelock being held for an unspecified length of time. BetterBatteryStats shows it to be RILJ holding the wakelock. I've narrowed it down to a RIL request named RIL_REQUEST_SET_TTY_MODE. I dumped out RILJ.mRequestsList during the held wakelock and I see this request staying around and waiting for a response from the RIL. It's as if the RIL is not responding to this request and I don't see RILReceiver processing a response to this request.
anyone know what tty is?
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Dunno how to fix it besides the airplane mode. Have you tried another kernel?
All siyah fluxxi and dream. All have shown the issue at some point
Sent from my SGH-I777 using xda app-developers app
topiratiko said:
All siyah fluxxi and dream. All have shown the issue at some point
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
What rom are you running?
I am having the same issue. Task's AOKP from 7/3, fluxxi kernel from 7/17.
Modem: UCPLC5.
Strangely, I've been unable to replicate it for the past 2 hours - phone sleeps fine. W T F.
jthatch12 said:
What rom are you running?
Click to expand...
Click to collapse
AOKP 7-3
Seems like rebooting with airplane mode is the only option
topiratiko said:
Seems like rebooting with airplane mode is the only option
Click to expand...
Click to collapse
I remember I had similar issue - RILJ wakelock after using headphones to listen music. It's disappeared by itself a couple of months ago (I'm on a latest CM9).
But, at the time I was able to get off RILJ wake lock by unplugging headphones, turning airplane mode on, screen off, wait a couple of mins and turn airplane mode off. This should get rid of RILJ wakelock.
hope this helps.
-- vlad
Well, I don't know if the OP's issues had to do with unplugging headphones but it doesn't seem to be. I'm glad this was posted as I couldn't figure out why I was only getting 85% deep sleep in CPUSpy and the phone would keep showing 10%-11% as 200Mhz in the background. Kernel Wakelocks didn't show any issues and I didn't see anything in Partial Wakelocks at first...then I charged up my phone and saw RILJ showing as 59.8%!!!!!
In fact, RILJ was showing up very high every single time I would charge my phone - even if I rebooted my phone after a full charge.
Eventually, after several hours, it would drop and show about 3.7% or lower depending on how long the phone was sitting on standby without being used. But this explains why I was losing about 4%-5% an hour.
I tried the Airplane Mode on > Reboot > Airplaine Mode off and my phone is now entering Deep Sleep at 94%!
No apps removed or frozen. Just followed OP's instructions!
I'm on AOKP 7-03 (running the stock task650 kernel but switching kernels didn't improve or worsen battery life).
This RILJ may have been fixed in the latest CM9 nightlies.
(Yes, I know taskt650 is currently working on an AOKP JB build so I'm pretty certain that this will be fixed in that build.)
Did this before going to bed and drained 4 points in 6 hours!
Sent from my Samsung Galaxy S II
Aokp/Team Skyfire
I too am having this problem using task & ktoonsez's AOKP 7/3. For me, it mainly occurs with headphone use. I switched to Semi v16c and the problem went away, but I really want to go back to AOKP! I just got tired of obsessing about this wakelock and switched....
Hopefully JB will bring a final cure.
Sent from my Nexus 7 using xda app-developers app
h3lluvaninjuhneer said:
I too am having this problem using task & ktoonsez's AOKP 7/3. For me, it mainly occurs with headphone use. I switched to Semi v16c and the problem went away, but I really want to go back to AOKP! I just got tired of obsessing about this wakelock and switched....
Hopefully JB will bring a final cure.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
There is no escape from RILJ on JB(as of now). Blame Samsung RIL, its complete horsebleep.
Ahh, I have been seeing this on my wife's skyrocket so I'm gonna try this on her phone.
Sent from my SGH-I777 using Tapatalk 2
Sunuva **%&$ muther %&%$## I HATE RILJ!!!!
Sent from my Samsung Galaxy S II
Aokp/Team Skyfire
I have tried several kernels (with task's AOKP), full wipe and reflash, etc., but the only solution was to go to a Samsung based ROM. I noticed the following over on the international GS2 cm9 development thread, but don't see any evidence this was chased to ground: http://forum.xda-developers.com/showthread.php?p=25047473
At this point, I'm just hoping one of the devs figures out a solution....
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
I've got the same problem using the 3g turbocharger from zeppelinrox and setting the experimental 1 values; try it with every other settings to see if it works I think it's a problem with some ROM settings!
In the Unix world tty is teletype, or another word to describe a terminal / console session.
Sent from my SGH-I777 using xda app-developers app
So any way to get a script for this? Since the airplane mode > reboot > airplane mode seems to be the only fix... can we get a script that will run this automatically somehow? It's not a big deal if we can't... after all it only takes a few second to turn airplane mode on but sometimes I forget...
I'm definitely having the issue with headphones on the latest builds of AOKP and Fluxi.
Could our RILJ partial wakelock issue be related to TTY (specifically: RIL_REQUEST_SET_TTY_MODE)? It appears to have been fixed in CM9 - see here:
http://review.cyanogenmod.com/#/c/16190/
Also, post #3028 on this page seems to exactly describe how & when I get the RILJ partial wakelock:
http://forum.xda-developers.com/show...10400&page=303
lmarr28 said:
I'm definitely having the issue with headphones on the latest builds of AOKP and Fluxi.
Could our RILJ partial wakelock issue be related to TTY (specifically: RIL_REQUEST_SET_TTY_MODE)? It appears to have been fixed in CM9 - see here:
http://review.cyanogenmod.com/#/c/16190/
Also, post #3028 on this page seems to exactly describe how & when I get the RILJ partial wakelock:
http://forum.xda-developers.com/show...10400&page=303
Click to expand...
Click to collapse
From what I have read regarding TTY on cellular, it requires a special cable for the headphone jack, so that makes sense it has something to do with the headphones.
Related
Hi
I installed watchdog lite due to weird wakes up at night the last 2 days (I thought they were gone for good with last updates but it seems to have come back) and more battery drain than I used to have, although it still good enough for me, it was excellent just 2 days ago.
I found that there are two processes that had activate watchdog alerts: "events/0" and "suspend"
Any ideas what they are? any way to solve wake ups at night I did not have before?
See pictures attached
Thank you
Villainrom 2.4.2
Kernel ninphetamine 2.1.1
Modem KH3
Wifi on at home (otherwise off)
bluetooth off most of the time
gps off most of the time
at night everything off except 3g that I never disconnect (lazyness)
I use to get these causing the alarm on watch dog, both using up to99% , every 30-60 mins during the night when the phone is in standby till i white-listed them.
I dont know what they are some heavy system process or something, watchdog will not let me blacklist them.
Tinderbox (UK) said:
I use to get these causing the alarm on watch dog, both using up to99% , every 30-60 mins during the night when the phone is in standby till i white-listed them.
I dont know what they are some heavy system process or something, watchdog will not let me blacklist them.
Click to expand...
Click to collapse
But if you whitelisted, it is just like shutting notifications off for those processes.. right? any way of keeping them sleep at night? like the rest of us ?
for me it's WLAN related, when i switch wlan off, events/0 and suspend wont go mad in standby at my SGS2...
someone proposed a while ago that this could be router related, and therefore not all users experience this!
this is the normal android gingerbread bug.. these are the two processes that keep it from going to complete sleep and chewing up battery. white listing them just removes them.. if you check they will still be chewing up cpu.. which is why you only get 1 day max on this phone with both wifi and 3g on vs. 2-3 days with my older sgs now running gingerbread.
turning off 3g and wifi gets rid of it but that is not really a solution...
I always manually turn wifi blue-tooth and gps off at night, and i still get events/0 and suspend waking up watchdog with 99% cpu usage?
So the solution until there is a better one is to turn off wifi and 3g...
I think I will do it at night, but during the day...
I had this phone to use it (internet, gps, etc...) not to keep it off all time, I already underclocked and undervolted... (that improved battery life a lot). If it only would go to sleep when not in use it would be great.
Thanks for help
Update: I turned off wifi and 3g and no watchdog alert from these processes or any other.
I will turn it on during the day and we'll see.
Sent from my GT-I9100 using XDA App
I turned on 3g this morning and have 8 alarms from this 2 in 8 hours with 99%...
Sent from my GT-I9100 using XDA App
but heres the issue
turning off 3G AND Wifi does not really tell you whats doing it. is it the data being on thats causeing the problem or a app that is syncing that is causing the problem.
How do I know which app? Watchdog only says events/0 and suspend...
Sent from my GT-I9100 using XDA App
i also have this issue running CM7 build #36
i posted the issue in the q&a thread hopefully someone will get back to me
Hi,
What wi-fi routers do you have?
router: wrt610n with ddwrt firmware as wireless bridge.
modem: epc3825 who is actually serving dhcp.
Sent from my GT-I9100 using XDA App
I have the same problem with very similar ROM/Kernel/Modem configurations.
Now I may be wrong, but I thought this bug was supposed to be fixed in 2.3.4 which VillainROM runs?
Also of note is that this "bug" does not seem to drain my battery anywhere near as badly as it did with my Captivate. On my Captivate suspend would usually sit at around 15% when bugged, and drain my battery like crazy. Suspend and events/0 both sit at anywhere from 30-60%+ on my SGS2 but it doesn't seem to affect my battery at all (or much, at least).
Could this possibly be a display bug? I've noticed Watchdog doesn't seem to update every minute a lot of the time, whereas it always updated on my Captivate.
So I've also found that the longer my phone is idle, the higher events/0 and suspend usually are. Doesn't seem to happen when the phone is plugged in though, as I never seem to get alerts from Watchdog overnight.
It is true that doesn't seem to affect much, but there are awakes, and should not be there any (or at least only a few). I gave up, uninstalled watchdog and forget it... I will enjoy the phone and will check periodically for updates.
Thank you everybody.
Sent from my GT-I9100 using XDA App
tonovcp said:
It is true that doesn't seem to affect much, but there are awakes, and should not be there any (or at least only a few). I gave up, uninstalled watchdog and forget it... I will enjoy the phone and will check periodically for updates.
Thank you everybody.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
umm.. just whitelist the two event and then Watchdog wont give you any warning for thoes too..
What's the point of whitelist? they are running anyway, so I just uninstall watchdog and 1 less app running.
Sent from my GT-I9100 using XDA App
tonovcp said:
What's the point of whitelist? they are running anyway, so I just uninstall watchdog and 1 less app running.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
well, a whitelist is for a process or event that you know might spike past your set % in watchdog. so for example if you know that Events/0 will spike past 50% for example, and you don't care to be warned of this process. So you can keep Watchdog installed and working, and when Facebook decides to sit there doing god only knows you WILL be notified.
Its kinda like a boy who cried wolf scenario, but with logic.
Watchdog catches a lot of apps that I mess around with, I think it is a super helpfull program.
After experiencing extremely bad battery life and searching everywhere around the web for answers i have found a solution for wakelock problems that solved all my battery woes.
Thanks goes to the people that originally found these fixes.
This step stops the AudioOut_1 partial wakelock bug from keeping device in awake mode:
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
Sent from my GT-I9100 using Tapatalk
Hi!
Can you describe, please, how did you find that this exactly steps (and no other) solved your battery life problems?
Thanks.
Regards.
Good to know. Thanks
Sent from my GT-I9100 using Tapatalk
For starters,I tried everything else I could and this is the only thing that helped.
I found the fixes all around different forums for GS2,GNote and GNexus.
I tried it for myself yesterday and my battery life has doubled.
Install BetterBatteryStats from the thread on XDA and you can see if you have these wakelock problems,look under Partial Wakelock and Kernel Wakelock.
I just wanted to share these dead simple steps to spare some people from the agony that is 7h battery life :banghead:
Sent from my GT-I9100 using Tapatalk
Nice info. Might come in handy someday. Thanks for sharing.
sent from my fingers to your face.
there is another trick to disable apps sync or the famous ! CALENDAR sync wake ups go in "account and sync'' and click on your account and uncheck what you want to stop sync!
for facebook wake ups the only thing I found is freezing it with titanium and make sure your disconnected from it every time you quit this app
HOP FOR A FIX FROM FACEBOOK SOON !
for the rest I don't think we can make something unless sammy release the source and finally an official ICS !
Mister Jozo said:
For starters,I tried everything else I could and this is the only thing that helped.
I found the fixes all around different forums for GS2,GNote and GNexus.
I tried it for myself yesterday and my battery life has doubled.
Install BetterBatteryStats from the thread on XDA and you can see if you have these wakelock problems,look under Partial Wakelock and Kernel Wakelock.
I just wanted to share these dead simple steps to spare some people from the agony that is 7h battery life :banghead:
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I asked how did you find those steps because in my old days of Motorola Motoronga MotoFAIL Milestone (TM) there were a bunch of Black Magic Recipes like this in order to save battery and none of them worked, unsurprisingly, of course.
Please, don't get me wrong, I'm not here to troll you or your thread, but just to know how people find these "steps".
Anyway, very interesting.
Thanks.
Regards.
These fixes will help your battery only if you have wakelock problems,they don't do anything otherwise.
I also resent black magic recipes. Some time ago I read that many common battery saving apps and tips don't help the battery,sometimes even causing more battery drain.It was an independent research where they regularly tested the battery itself with ampermeters.
Sent from my GT-I9100 using Tapatalk
usually turning off touch sounds and screen lock sounds should solve the "AudioOut_1" problem, at least it worked for me
---------- Post added at 07:31 PM ---------- Previous post was at 07:27 PM ----------
zamana said:
I asked how did you find those steps because in my old days of Motorola Motoronga MotoFAIL Milestone (TM) there were a bunch of Black Magic Recipes like this in order to save battery and none of them worked, unsurprisingly, of course.
Please, don't get me wrong, I'm not here to troll you or your thread, but just to know how people find these "steps".
Anyway, very interesting.
Thanks.
Regards.
Click to expand...
Click to collapse
You neet to find out which wakelock are draining your battery when the screen is off before you trying out some "Black Magic Recipes".For instance ,if you installed some instant message app which keeps pulling something from the server and prevent your phone from going to deep sleep, disabling sound will not help you get better battery life.
Mister Jozo said:
After experiencing extremely bad battery life and searching everywhere around the web for answers i have found a solution for wakelock problems that solved all my battery woes.
Thanks goes to the people that originally found these fixes.
This step stops the AudioOut_1 partial wakelock bug from keeping device in awake mode:
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks, worked perfectly for my ICS Galaxy note !!
Originally Posted by Vaddy23
Can someone help me out with a proper wiping technique or if a full wipe is even neccesary before/after I update to ICS. I'm on the latest stock firmware Gingerbread 2.3.6 with a unlocked UK Note that has never been rooted. Do I even have to wipe? I don't want any issues with battery life so on and so forth. Or do I wipe after I perform the update to ICS? Along with a factory reset? Someone please help, thanks..
Click to expand...
Click to collapse
I had issues with reboots and poor battery life after upgrade. I went back to gingerbread and done factory reset. Once booted I immediately went to kies and upgraded to uk ics. I have no issues now with reboots or battery. Very happy now and speed is great. Remember to factory reset in gingerbread and not ics. Just reinstall apps from the play store after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sent from my GT-N7000 using xda premium
Mister Jozo said:
After experiencing extremely bad battery life and searching everywhere around the web for answers i have found a solution for wakelock problems that solved all my battery woes.
Thanks goes to the people that originally found these fixes.
This step stops the AudioOut_1 partial wakelock bug from keeping device in awake mode:
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks!! It worked for me when my Galaxy Note was running ICS and now again when I have downgraded to GB.
CPU Spy showed 200 Hz to be the lowest state touched and there was no Deep Sleep. After these steps, it goes to Deep Sleep when not used.
I'm aware that turning of screen/touch sounds will help remedy the problem of AudioOut_1 being a battery-sucking vampire, but are there any actual fixes yet (turning off the sounds seems like more of a workaround than a fix, I think)?
Most posts I've found regarding AudioOut_1 are not very recent, so I'm not sure if that means the problem is solved or if everyone has simply turned off touch sounds and screen lock sounds. In my experience, the issue persists (at least in the most recent versions of AOKP/CM9 that I've used, which are I think one version behind the latest). It may be stupid, but I enjoy the CM9/AOKP touch sounds and would like to hear them without my battery suffering quite so much in the process.
For what it's worth, searching "audioout" on either the CM9 thread or the AOKP thread turn up zero results. Surely I'm not the only one still getting this wakelock, am I?
Also, regarding this wakelock: is it kernel-related? I'm really quite unfamiliar with how this sort of thing works, but I'd like to know a little more if only to satisfy my curiosity.
Turn off lockscreen sounds. Should help
Sent from my SGH-I777 using xda premium
jthatch12 said:
Turn off lockscreen sounds. Should help
Click to expand...
Click to collapse
I don't have any sounds enabled and I still have a problem with this wakelock.
Sent from my SGH-I777 using xda premium
I am also struggling with this wakelock and seeking additional help (using BBS too). I'm running AOKP build 37 on the Epic 4g Touch (also SGS2). I hope we find something out.
I don't really have any battery drain from this but still looking for an answer! Taskkkkkkk where are youuuuuuu???????????????
Download latest version. Do a full wipe. (Full wipes are not just cache. Its everything) and see if issue persists. If a full wipe isn't done before posting about an issue it shouldn't be posted.
Sent from my SGH-I777 using Tapatalk 2
I haven't had this wakelock for a while now, with my sounds on. I fully wipe each time I update, and that includes formatting system along with a factory reset and wiping caches
Sent from my SGH-I777 using XDA
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?!
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.