Related
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.
Is anyone else getting Android OS around 50-60% battery use?
I have tried every ROM included going back to stock. I have ran the phone with nothing but Stock and no apps installed for a day and still get the same drain so I can only assume its a kernel issue.
I am not familiar with LG products in the slightest, but I had a yellow screen of death the other day...something I have never seen in my years with samsung android products. Anyone have any idea what this is maybe it is pointing to a hardware issue?
LG made a great phone, but I don't think I will keep it much longer. Locked boot loaders, no sources, and history of terrible updates have me regretting purchasing this phone. I tried my hand at building a working jb release when I first got the phone and it is going to take a skill set I do not have and I hate waiting on a company to do what they've never done in the past..
jivy26 said:
Is anyone else getting Android OS around 50-60% battery use?
I have tried every ROM included going back to stock. I have ran the phone with nothing but Stock and no apps installed for a day and still get the same drain so I can only assume its a kernel issue.
I am not familiar with LG products in the slightest, but I had a yellow screen of death the other day...something I have never seen in my years with samsung android products. Anyone have any idea what this is maybe it is pointing to a hardware issue?
LG made a great phone, but I don't think I will keep it much longer. Locked boot loaders, no sources, and history of terrible updates have me regretting purchasing this phone. I tried my hand at building a working jb release when I first got the phone and it is going to take a skill set I do not have and I hate waiting on a company to do what they've never done in the past..
Click to expand...
Click to collapse
Easy, brother. I have only had one of my apps/utilities run higher than AndroidOS ever on this phone; however, that said, I think there is a problem with the way it's being calculated. I'm getting really good battery life with good sleep and still AndroidOS shows the highest by far. I know that's abnormal for it to be so high and still get good battery life, but it is what it is.
Edit: you've installed the fast dormancy toggle, right? As for the yellow screen, I've seen it once in my two months with the phone, just rebooted and carried on. Forgot what they said it was...but it is here in this forum somewhere.
Sent from my LG-E970 using xda app-developers app
I was just about to post something similar. Andriod OS being high kind of makes sense if nothing else is using the battery, although you would expect that number to fall significantly with increased screen on time and heavy app usage, which it doesn't ever seem to.
I've been having horrible battery drain lately. I'm currently traveling for business, and just use my OG for web surfing and stuff when I'm in my hotel. I leave the phone in airplane mode, with WiFi on. About two weeks ago, when I was on The Base 0.4 in that same configuration, my battery would drain maybe 1% an hour while I was sleeping.
Recently I've been on The Base 0.7.3, and my battery drains over 5% an hour while I'm sleeping. This means no screen on, no apps running, and even turning WiFi off! How does it use that much battery when it's not doing anything? Now, I'm not entirely sure what kernel I'm running. The first time I installed The Base 0.7.3 I used sk8's kernel. After getting poor battery life, I reflashed 0.7 and 0.7.3, this time choosing the freegee kernel. I'm not actually sure if the kernel changed though.
Anyway, I think I'll post again tomorrow with some screenshots from Better Battery Stats+ and CPU Spy.
I'm wondering if this recent botched update had the battery fixes we need. Hopefully they'll re-release it soon.
Jank4AU said:
Easy, brother. I have only had one of my apps/utilities run higher than AndroidOS ever on this phone; however, that said, I think there is a problem with the way it's being calculated. I'm getting really good battery life with good sleep and still AndroidOS shows the highest by far. I know that's abnormal for it to be so high and still get good battery life, but it is what it is.
Edit: you've installed the fast dormancy toggle, right? As for the yellow screen, I've seen it once in my two months with the phone, just rebooted and carried on. Forgot what they said it was...but it is here in this forum somewhere.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Yea I've tried fdt but I think it has to be kernel related drain issues
Sent from my LG-E970 using Tapatalk 2
Digil said:
I was just about to post something similar. Andriod OS being high kind of makes sense if nothing else is using the battery, although you would expect that number to fall significantly with increased screen on time and heavy app usage, which it doesn't ever seem to.
I've been having horrible battery drain lately. I'm currently traveling for business, and just use my OG for web surfing and stuff when I'm in my hotel. I leave the phone in airplane mode, with WiFi on. About two weeks ago, when I was on The Base 0.4 in that same configuration, my battery would drain maybe 1% an hour while I was sleeping.
Recently I've been on The Base 0.7.3, and my battery drains over 5% an hour while I'm sleeping. This means no screen on, no apps running, and even turning WiFi off! How does it use that much battery when it's not doing anything? Now, I'm not entirely sure what kernel I'm running. The first time I installed The Base 0.7.3 I used sk8's kernel. After getting poor battery life, I reflashed 0.7 and 0.7.3, this time choosing the freegee kernel. I'm not actually sure if the kernel changed though.
Anyway, I think I'll post again tomorrow with some screenshots from BatteryStats+ and CPU Spy.
I'm wondering if this recent botched update had the battery fixes we need. Hopefully they'll re-release it soon.
Click to expand...
Click to collapse
When I would get bad drain, which has happened several times, I could narrow it down to a couple things in order to solve the problem.
In my case it would always happen after installing Google+. Uninstall and reboot would usually fix the issue. If I got drain on a fresh install without g+ installed, I found that if I installed the 2.2 kernel separately as a stand alone zip, that would fix it. Don't know why but it may work for you too.
I don't have screen shots, but today I recharged at 38% after 3:10 of phone use and 1:55 screen on time and about 15 hours off charger. That's with Wi-Fi on the whole time and Bluetooth for about 9 hours. I have my work exchange account on active sync with push notifications. Facebook and Twitterer to 4 hour intervals. I'm underclocked to 1350 and using powersave gov with deadline.
Sent from my LG-E970 using xda app-developers app
jivy26 said:
Yea I've tried fdt but I think it has to be kernel related drain issues
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Believe you are correct. There were issues on the Samsung Infuse and even the international SGS3 for a while... it was referred to as 'memory leak.' Has been worked out by devs on XDA. You can put memory leak in the XDA search above... it's above my pay grade.
Edit: It's great to see another RD here... hope you will reconsider keeping the phone and stay !!
Jank4AU said:
When I would get bad drain, which has happened several times, I could narrow it down to a couple things in order to solve the problem.
In my case it would always happen after installing Google+. Uninstall and reboot would usually fix the issue. If I got drain on a fresh install without g+ installed, I found that if I installed the 2.2 kernel separately as a stand alone zip, that would fix it. Don't know why but it may work for you too.
I don't have screen shots, but today I recharged at 38% after 3:10 of phone use and 1:55 screen on time and about 15 hours off charger. That's with Wi-Fi on the whole time and Bluetooth for about 9 hours. I have my work exchange account on active sync with push notifications. Facebook and Twitterer to 4 hour intervals. I'm underclocked to 1350 and using powersave gov with deadline.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. I have Google+ uninstalled, but part of me thinks Google Now may be partially the culprit (although why that would be the case with all radios off, I don't know).
I'll try a fresh install of the 2.2 kernel and see if that helps. Thanks.
I can't speak for anyone else but FDT did wonders for my battery life. I was only able to go about 12 hours prior to disabling FD.
Sent from my Optimus G
Digil said:
Thanks for pointing me in the right direction. I have Google+ uninstalled, but part of me thinks Google Now may be partially the culprit (although why that would be the case with all radios off, I don't know).
I'll try a fresh install of the 2.2 kernel and see if that helps. Thanks.
Click to expand...
Click to collapse
I always install GNow, love the inverted version.
Sent from my LG-E970 using xda app-developers app
johnbyebye said:
I can't speak for anyone else but FDT did wonders for my battery life. I was only able to go about 12 hours prior to disabling FD.
Sent from my Optimus G
Click to expand...
Click to collapse
This is good for sure... it's just that compared to other phones, Android OS and Android System should not be that high.
Pony Express said:
This is good for sure... it's just that compared to other phones, Android OS and Android System should not be that high.
Click to expand...
Click to collapse
That's what leads me to believe it's a faulty measure...
Sent from my LG-E970 using xda app-developers app
Jank4AU said:
That's what leads me to believe it's a faulty measure...
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
^^^ This is indeed worth considering.... I think the question then becomes why is it consistent among the 3 roms we are using? Maybe when JB source is out and something is built from source all will be good.
Pony Express said:
^^^ This is indeed worth considering.... I think the question then becomes why is it consistent among the 3 roms we are using? Maybe when JB source is out and something is built from source all will be good.
Click to expand...
Click to collapse
I would be less inclined to believe it is a faulty measure if we had a different ROM not built off stock (AOKP/CM10) that could produce different values. However, I seriously doubt anything built into either of the two custom ROM's is geared toward normalizing that reading. That's why they are both the same as the stock AndroidOS percentages. Jivy is probably right that it's a kernel issue. With the size battery we have, imagine the potential if it is a true reading (androidOS out-of-control) and we can get it under control down the road. We're talking double the current best battery life you've ever had on this phone at the very least.
Sent from my LG-E970 using xda app-developers app
+1
LOL
v
v
v
+43
Get BetterBatteryStats, select Since unplugged and Alarms to see what is waking the device (making it not go into a deep sleep). eBay was a big culprit for me.
The wakelock that keeps the phone awake during background data transfer (screen off) lasts 6 seconds (I am guessing it does it in multiples of 6s) regardless of how long the sync takes. Everytime email, facebook, gmail, drive, picasa, twitter, g+, google maps, ebay, calendar, contacts.. whatever wakes the phone to check something, it will be a minimum of 6 seconds.. This adds up over the course of the day and it is counted in the Android OS. Shut down syncs you don't absolutely want/need and this number will go down. All phones with the Snapdragon S4 Pro has it, especially the Nexus4. It seems they've done some kernel work to fix/reduce it but I havent really looked into it since I don't have that phone. I've seen complaints in the Droid DNA forum as well.
snacsnoc said:
Get BetterBatteryStats, select Since unplugged and Alarms to see what is waking the device (making it not go into a deep sleep). eBay was a big culprit for me.
Click to expand...
Click to collapse
This. EBay for me too. BetterBatteryStats is your friend.
Anyone else experiencing scrolling lag or delay. Clearing cache and wiping dalvik fixes it but the issue returns after about two days.
Sent from my LG-E970 using Tapatalk 2
jivy26 said:
Anyone else experiencing scrolling lag or delay. Clearing cache and wiping dalvik fixes it but the issue returns after about two days.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1987032
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.
Over the past couple days I've noticed this as the top partial wakelock on my device. This seems to be at least partially coincident with info propagating across the internet about Google games. There is an apparent associated wake alarm, which ends in .Gms.
While these aren't insanely bad wakelocks, they are irritating to me as I'm not sure where they are coming from. The number of wake alarms from this is pretty aggressive... Previous to this maps was my most aggressive waker by a large margin, and this new one is twice as aggressive as maps.
Is anyone else seeing these? Anyone have any insight as to the source?
Screenies attached...
Sent from my Optimus G using Tapatalk 2
Yes, same problem here but with a Nexus 4
It looks like that's caused by Messenger.
I can say for certain that it Might be caused my Messenger, as I do not have it installed ,and do not suffer that wakelock.
I do got a lot from Maps, but Greenify takes care of that.
OMGMatrix said:
It looks like that's caused by Messenger.
I can say for certain that it Might be caused my Messenger, as I do not have it installed ,and do not suffer that wakelock.
I do got a lot from Maps, but Greenify takes care of that.
Click to expand...
Click to collapse
What specifically is pointing you to messenger? You're referring to G+ messenger I assume. There haven't been any updates to G+ or messenger recently...
Sent from my Optimus G using Tapatalk 2
dandrumheller said:
What specifically is pointing you to messenger? You're referring to G+ messenger I assume. There haven't been any updates to G+ or messenger recently...
Sent from my Optimus G using Tapatalk 2
Click to expand...
Click to collapse
No, but I have seen com.google.gms implicated in recent Google Play Services updates, in reference to the upcoming game center-thing Google is launching, so That could potentially have something to do with it.
DId you get rid of this wakelock. this error is not lettign my phone to sleep.
atrix4nag said:
DId you get rid of this wakelock. this error is not lettign my phone to sleep.
Click to expand...
Click to collapse
No. It seems to have gotten slightly better with a different kernel, but still present. I'm still getting decent deep sleep and awake: screen on ratios... It isn't completely preventing deep sleep for me.
Sent from my Optimus G using Tapatalk 2
dandrumheller said:
No. It seems to have gotten slightly better with a different kernel, but still present. I'm still getting decent deep sleep and awake: screen on ratios... It isn't completely preventing deep sleep for me.
Sent from my Optimus G using Tapatalk 2
Click to expand...
Click to collapse
I saw this wakelock first time on my phone.. i installed a new ROM today. I used this rom before also, but i never saw this wakelock. What you have done to reduce this wakelock
atrix4nag said:
I saw this wakelock first time on my phone.. i installed a new ROM today. I used this rom before also, but i never saw this wakelock. What you have done to reduce this wakelock
Click to expand...
Click to collapse
Is been around for a few days... I think it is being caused by updates to background Google services, but I'm not sure. Since I don't know what's causing it, chasing it down by freezing stuff or using greenify odd going to take time. I haven't had that time yet. So I am living with it for now.
Sent from my Optimus G using Tapatalk 2
dandrumheller said:
Is been around for a few days... I think it is being caused by updates to background Google services, but I'm not sure. Since I don't know what's causing it, chasing it down by freezing stuff or using greenify odd going to take time. I haven't had that time yet. So I am living with it for now.
Sent from my Optimus G using Tapatalk 2
Click to expand...
Click to collapse
ok, let me try different options.
I tried all the options given in Better Battery Stats app, to minimize gsf wakelocks and disabling maps. I tired these settings for the first time..
atrix4nag said:
ok, let me try different options.
I tried all the options given in Better Battery Stats app, to minimize gsf wakelocks and disabling maps. I tired these settings for the first time..
Click to expand...
Click to collapse
Did it help? Just out of curiosity..
Karpfenhai said:
Did it help? Just out of curiosity..
Click to expand...
Click to collapse
yes,it helped after fully recharging and restarting the phone. now no more nlpcollector wakelock on my phone
This sounds very much like the aggregated Network Location Provider that was introduced in the I/O Keynote?? Or is this something different?
It's supposed to use far less power not more... :what: It got a very good reception from the crowd tho.
wolfboy1984 said:
This sounds very much like the aggregated Network Location Provider that was introduced in the I/O Keynote?? Or is this something different?
It's supposed to use far less power not more... :what: It got a very good reception from the crowd tho.
Click to expand...
Click to collapse
Could be. I haven't had really any time to chase this yet. But for grins, I installed the app AutomateIt, which if I understand correctly takes advantage of some of those new Google features. I turned on a couple options in the app to trigger things "when in a vehicle". I subsequently saw more of this wakelock.
Sent from my Optimus G using Tapatalk 2
Anyone fount out what is the solution ?
wolfboy1984 said:
This sounds very much like the aggregated Network Location Provider that was introduced in the I/O Keynote?? Or is this something different?
It's supposed to use far less power not more... :what: It got a very good reception from the crowd tho.
Click to expand...
Click to collapse
Sounds like it to me too. And yeah, it probably does use less power than the old default way of doing location services. Our problem is that we have tuned our phones to avoid location services as much as possible, and now we are getting them again.
I'm sure someone will figure out the best way to tame it... or we may find out it's battery-friendly enough to actually use location services now
jdock said:
Sounds like it to me too. And yeah, it probably does use less power than the old default way of doing location services. Our problem is that we have tuned our phones to avoid location services as much as possible, and now we are getting them again.
I'm sure someone will figure out the best way to tame it... or we may find out it's battery-friendly enough to actually use location services now
Click to expand...
Click to collapse
It may be battery friendlier than the old location services - it doesn't seem particularly drain inducing to me - but it is running on top of the old location services (I haven't noticed any reduction in wakelocks from them) so it does result in some additional drain.
Sent from my Optimus G using Tapatalk 2
jdock said:
Sounds like it to me too. And yeah, it probably does use less power than the old default way of doing location services. Our problem is that we have tuned our phones to avoid location services as much as possible, and now we are getting them again.
I'm sure someone will figure out the best way to tame it... or we may find out it's battery-friendly enough to actually use location services now
Click to expand...
Click to collapse
It aggregates it from wifi, data and gps remember.
If you are using wifi - it will be there.
Keep your smart phones smart.
dandrumheller said:
It may be battery friendlier than the old location services - it doesn't seem particularly drain inducing to me - but it is running on top of the old location services (I haven't noticed any reduction in wakelocks from them) so it does result in some additional drain.
Sent from my Optimus G using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I was under the impression that it's kind of up to the apps to actually USE the new service. If they still go about things the old way then the new service doesn't help anything.
I posted the following on my own thread but I'll be moving my discussion here because it's pretty much the same thing.
I noticed recently that I have two Google related networking services running constantly. They are GoogleLocationService and NetworkLocationService. Are both necessary? I remember only one was there before the new Google Services update. I also have noticed an increase in Android OS under Battery usage and a slight decrease in battery life. I think the two maybe related. Anyone have some insight?
Click to expand...
Click to collapse
I think the issue is that the old service and the new service are running simultaneously and is negatively impacting battery instead of saving like what was promised with the new service. Maybe we need to find a way to remove/freeze the old service.
Hi all,
I love my DNA (stock) and I haven't had any issues until the past couple of weeks, when I noticed that my phone started draining battery much more quickly than normal without me changing my usage habits. I'm consistently draining about 10% per hour even when I just pull it out of my pocket every hour or so to check notifications. I've also noticed sluggish behavior as well (lag when unlocking especially).
I got the Wakelock Detector app to see what was causing me issues, but I'm pretty new to it--I'm not sure what is normal and what is a problem. I've disabled a lot of my location services as a result, but that doesn't seem to have solved anything as of yet, which is why I'm posting.
I'm attaching a few screenshots from WLD so you can see what I've got going on. Android System looks awful, but I don't want to disable backup (I like having my app choices and such saved, and don't want to lose them). What should I really chase after to get this draining issue solved?
View attachment 1998865
View attachment 1998866
View attachment 1998867
View attachment 1998881
There's a known issue with Google services causing drain, its been mentioned in a few places around here, it started with an update a little while ago. You can try removing updates if it let's you, may help, or just have to wait out an update to correct it. I think for now disabling all of the location stuff helps.
Tapatalked from my HTC DNA - ReVolt
you could also try the newly released Qualcomm Snapdragon BatteryGuru.
If you can I would change kernels. crpalmer's kernel fixed my wakelock issues. I had a maps issue related to location services and disabled maps in Titanium Backup and then later I had wakelock issues that I couldn't pin down but switching to crpalmer's kernel fixed it for me.
Xpiatio said:
you could also try the newly released Qualcomm Snapdragon BatteryGuru.
Click to expand...
Click to collapse
This app looks great! I'll certainly give it a try. I used JuiceDefender on my old Droid Charge and it helped (back in 2011), but I don't think the app is maintained any more.
I'll let you know if it helps.
I have a theory, which may be wrong, is that apps set up all sorts of events that the system tracks and acts upon. As a result, when tracking CPU usage and wake locks, it is often hard to find the culprit behind most of the activity because it registers under system processes rather than directly from the offending app.
So the solution may be to do a factory reset (which is painful) or just freeze some apps to see what difference it makes.
Sent from my HTC6435LVW using Tapatalk 2
petrivka said:
This app looks great! I'll certainly give it a try. I used JuiceDefender on my old Droid Charge and it helped (back in 2011), but I don't think the app is maintained any more.
I'll let you know if it helps.
Click to expand...
Click to collapse
That itself causes wakelocks and is 90% placebo effect.
Having same issue and it is definitely Google. I use Google Maps a lot so disabling location renders it useless. Bad deal since its killing my battery.
123421342 said:
That itself causes wakelocks and is 90% placebo effect.
Click to expand...
Click to collapse
If so, this is the best placebo effect ever. Once BatteryGuru trained for 2 days, my battery life has improved dramatically, back to where it used to be (if not better). My phone now can enter deep sleep for longer than 2 minutes over a 10 hour period.
I did see that BatteryGuru was the cause of additional wakelocks, but my real cause for concern was the lack of deep sleep.
I can now make it through a 16 hour day without getting range anxiety.
123421342 said:
That itself causes wakelocks
Click to expand...
Click to collapse
Ok... Just about every app causes wakelokcs, big whoop.
123421342 said:
90% placebo effect.
Click to expand...
Click to collapse
Yep, getting an extra couple of hours of battery life due to that app is definitely placebo.
Sent from my HTC6435LVW using xda app-developers app
It isn't mentioned in this thread and is a really important recent development. The new play store solves the excessive drains that google play services was having. I've seen mentioned in a few posts above some issues that will be solved by installing the new play store.
The problem I had with battery guru was that it required turning location services on. Since I normally don't run location services unless I need them, having to enable them for the battery savings app to run kind of negates the purpose of the app. It would be nice to hack it up and delete the business that requires location services.
For the poster above who wasn't getting deep sleep, I would try removing battery guru, solve the deep sleep problem and then reinstall battery guru, it might make your battery life even mo betta.