Hi,
I have recently installed GLaDOS kernel on my Nexus S, and activated the DEEP IDLE, however, under idle stats both DEEP IDLE (TOP=ON) and (TOP=OFF) are shown as 0ms (checked in NStools).
What could be causing this, how can I fix it?
Thanks.
Jujo12 said:
Hi,
I have recently installed GLaDOS kernel on my Nexus S, and activated the DEEP IDLE, however, under idle stats both DEEP IDLE (TOP=ON) and (TOP=OFF) are shown as 0ms (checked in NStools).
What could be causing this, how can I fix it?
Thanks.
Click to expand...
Click to collapse
Well, does your rom have deep idle activated?
Sent from a sandwich using my Nexus S
Well, I have turned it on in NStools
Jujo12 said:
Well, I have turned it on in NStools
Click to expand...
Click to collapse
Ok, in some roms you can turn it on but it don't work. What rom are you using?
MIUI 2.6.1
OK, we have progress. I don't know what I did, but now my Nexus enters DEEP IDLE, however only with TOP=ON. TOP=OFF is still at 0ms. What could be causing it?
Bluetooth fast switch. Needs a framework fix. May not work in miui.
Haha, I have been thinking about moving to CM9 for some time, and decided to install it. Deep idle works without any problems.
Thanks a lot
Related
Hey all, quick question hopefully you all can help me out with. I am currently having terrible battery issues ever since I flashed my phone initially. Terrible as in 6 hours stand-by my phone would be dead.
Anyhow, I am just trying to figure out who's (which) kernel I am running. The kernel version is 2.6.35.7-I997RUXKG3-CL366622 . I have done searches but biggest problem is, threads usually do not post the version number for me to check what I am running.
I am on Infused 2.1.0 (thx GTG!), but battery life has been garbage on all ROMs so I am certain that is not the issue. Can anyone let me know, me love you long time.
iConformed said:
Hey all, quick question hopefully you all can help me out with. I am currently having terrible battery issues ever since I flashed my phone initially. Terrible as in 6 hours stand-by my phone would be dead.
Anyhow, I am just trying to figure out who's (which) kernel I am running. The kernel version is 2.6.35.7-I997RUXKG3-CL366622 . I have done searches but biggest problem is, threads usually do not post the version number for me to check what I am running.
I am on Infused 2.1.0 (thx GTG!), but battery life has been garbage on all ROMs so I am certain that is not the issue. Can anyone let me know, me love you long time.
Click to expand...
Click to collapse
Just the community kernel you can download CPU spy to help with that as well.
Sent from my SAMSUNG-SGH-I997 using xda premium
Maybe u just have a bad battery 6 hours is horrible off stand by.
unless you have some other things running thats eating it up. when you check your battery stats whats eating the most power. Display? Android Proccess?
check that out.
tyshemi said:
Just the community kernel you can download CPU spy to help with that as well.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for suggesting CPU Spy, looks like I am running Infusion-GB which is what I wanted. So something else is killing my battery
the2rrell said:
Maybe u just have a bad battery 6 hours is horrible off stand by.
unless you have some other things running thats eating it up. when you check your battery stats whats eating the most power. Display? Android Proccess?
check that out.
Click to expand...
Click to collapse
Problem is I bought 2 extra batteries and get exact same life. When I initially bought the phone I would get a days use surprisingly. After that, I have had nothing but god awful drain. I have had almost a dozen android phones and have never encountered such terrible battery life.
I do not have fetch data enabled/gps/widget updates or anything that would normally keep the processor/data churning while in my pocket. Battery use is usually around 40-80% on display, all other categories being minimal (which seems correct).
I'm banging my head on this one, I appreciate you guys replying to my thread
iConformed said:
Thanks for suggesting CPU Spy, looks like I am running Infusion-GB which is what I wanted. So something else is killing my battery
Click to expand...
Click to collapse
I'm running GB 1.0 Kernel and I loose 1% every 3 hrs. on standby.
iConformed said:
Problem is I bought 2 extra batteries and get exact same life. When I initially bought the phone I would get a days use surprisingly. After that, I have had nothing but god awful drain. I have had almost a dozen android phones and have never encountered such terrible battery life.
I do not have fetch data enabled/gps/widget updates or anything that would normally keep the processor/data churning while in my pocket. Battery use is usually around 40-80% on display, all other categories being minimal (which seems correct).
I'm banging my head on this one, I appreciate you guys replying to my thread
Click to expand...
Click to collapse
Send me a pic of your battery screen I settings
Sent from my SAMSUNG-SGH-I997 using xda premium
Ltilt2 said:
I'm running GB 1.0 Kernel and I loose 1% every 3 hrs. on standby.
Click to expand...
Click to collapse
That's solid! I'll try flashing 1.0 then instead of the 1.1 I'm currently on. Are you using this with Infused 2.1.0?
iConformed said:
That's solid! I'll try flashing 1.0 then instead of the 1.1 I'm currently on. Are you using this with Infused 2.1.0?
Click to expand...
Click to collapse
No, I'm running this with Apex 9.2 JVR
tyshemi said:
Send me a pic of your battery screen I settings
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Can't post outside links since I'm newer, sent PM with screen capture
1% per 3 hours standby is FREAKING AWESOME..!!!!
Maybe u have some stray app in the background that's using CPU/whatever it is that's eating up ur battery.
Some subtle things u cud try since u said display is taking up 40-80% of battery:
1. Turning off screen auto rotation, turning it on when needed
2. Turning off auto brightness, turning it on to auto when needed
Use SetCPU like people above pointed out and this would let u see what processor states ur phone is spending most time in.
It sounds like for some people, Infusion 1.1 really flakes out. No clue why. I don't overclock so I don't run it.
It's either Infusion 1.1 flaked out, or if you continue having problems with other kernels, you have a rogue app.
Kernels rarely make any significant difference in battery life unless they're broken.
Entropy512 said:
It sounds like for some people, Infusion 1.1 really flakes out. No clue why. I don't overclock so I don't run it.
It's either Infusion 1.1 flaked out, or if you continue having problems with other kernels, you have a rogue app.
Kernels rarely make any significant difference in battery life unless they're broken.
Click to expand...
Click to collapse
Are there any apps I could get that could monitor packets in/out from what I have installed? I have a lot of apps but most are from trusted sources
Running Infusion-GB 1.1 and Infused 2.1.0: I get 1% drain every 3 hours on standby with radio on (reasonable H+ reception) and 1% every 6 hours on flight mode.
It's most likely a defect in your phone or a configuration issue. You really have to be using your phone for at least 4 or 5 hours (screen-on time) over those 6 hours to cut through battery that fast.
superweapons said:
Running Infusion-GB 1.1 and Infused 2.1.0: I get 1% drain every 3 hours on standby with radio on (reasonable H+ reception) and 1% every 6 hours on flight mode.
It's most likely a defect in your phone or a configuration issue. You really have to be using your phone for at least 4 or 5 hours (screen-on time) over those 6 hours to cut through battery that fast.
Click to expand...
Click to collapse
Dang, I'd think it's a defective unit too except for when I first got it battery was fantastic. But I'm definitely not a heavy user, most my time is at work and I only occassionaly turn it on to check time/sms
Sent from my SAMSUNG-SGH-I997 using xda premium
iConformed said:
Dang, I'd think it's a defective unit too except for when I first got it battery was fantastic. But I'm definitely not a heavy user, most my time is at work and I only occassionaly turn it on to check time/sms
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
when you go to settings > applications > running services - is there anything there that looks like it shouldn't be there?
i know that there is a process that starts with an "o" that is tied into media hub's protected content (DRM) - eats a ton of battery, and isn't really necessary.
it's also possible that you have the SNS service going, but constantly in a restarting state. this seemed to eat a lot of battery also.
otherwise, i'd do what others have suggested and monitor with CPU spy, and i'd also suggest an app called Better Battery Stats (not available in the market - find it here on XDA by a developer named chamonix). this will let you know if you have any wakelocks that are preventing your phone from reaching deep sleep when it is idle.
definitely sounds like you could have a wakelock or 2 interfering with your phone trying to get into those lower frequencies.
wipe battery stats?
Did you try wiping battery stats?
iConformed said:
Are there any apps I could get that could monitor packets in/out from what I have installed? I have a lot of apps but most are from trusted sources
Click to expand...
Click to collapse
Packets in/out isn't what you want unless you also have unusual data usage too. It's wakelock stats you want - look at the BetterBatteryStats app. It used to be only on XDA but apparently it's on the market now.
iphone4 said:
Did you try wiping battery stats?
Click to expand...
Click to collapse
I've said it before, and I'll say it again - Wiping battery stats does NOTHING on our phone. Don't go blindly telling people to do something on our devices just because it worked on another device. The fuel gauge chip on GalaxyS series phones works in a very different way than HTC phones. (Exception: I think the GSII has a more traditional fuel gauge.)
was running great for a week but today i noticed on cpuspy that it didnt go into deep sleep last night. im even using auto airplane.
prime rom 2.1.1
prime oc kernel
cwm
Do you have overclocking turned on? It may be due to the OC settings in Prime only allowing a minimum freq of 216.
Albert Pittman said:
was running great for a week but today i noticed on cpuspy that it didnt go into deep sleep last night. im even using auto airplane.
prime rom 2.1.1
prime oc kernel
cwm
Click to expand...
Click to collapse
Using on demand?
or interactive?
I found nothing else would give me deep sleep
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
Using on demand?
or interactive?
I found nothing else would give me deep sleep
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
I think I have the same issue. I couldn't figure out why and posted last night but my dock died in a matter of 7 hours without any use. Checked and 60% was 216mhz and practically no deepsleep.
Prime 2.1.1 and PrimeOC kernel.
I may try to change the kernel to clemsyn or something else to see if it fixes it.
---------- Post added at 01:06 PM ---------- Previous post was at 12:45 PM ----------
Installed Clemsyn 21 kernel, reboot and closed the screen and left it for a good 15 minutes. Deep sleep 89%. Hopefully it stays that that. Could be related to an app that's not been opened or run yet.
Update: Still at 90% dock and 98% tablet and haven't used it all day. Deep sleep is over 89% on CPUSPY. This is after getting rid of Prime2010 kernel and using Clemsyn. Seems to have been the problem for me.
I'm not saying that the kernel will do this to everyone but in my case, it could've been a case of complications with applications or what. Battery use under systems shows that around 45% is due to "Cell standby" which is related to mobile data but it's off.
Only reflashing to a different kernel fixed it for me.
i am running interactive mode, i ended up shutting down wifi, gps and trying that it still didnt go into deep sleep. then i turned off all background activity. then i finally got deep sleep. turned everything back on and am getting deep sleep now. wondering if there was something hangin up in the background and cycling the background services did it. ill keep updating to see how it goes.
when first rooted by the oh so awesome razorclaw! man i was hoping for it , checking everyday like 3 times a day wishing....but anyway, when i first rooted and was running just thestock rom rooted stock kernel and cwm i didnt even need to use auto airplane mode i could set everything to turn off with screen and it was fine, which was really the first time it was really good. i think it was the .18 update that was the first time i got good deep sleep and i was only on that for a few days before .19 came out and razorclaw rooted the same day.then flashed primeand was fine for a week almost.
im gettin sleep now so ill see
Hello Guys.What is deep sleep?and how can I know that it is working in cm10 or not?
Reply
Android Daymon said:
Hello Guys.What is deep sleep?and how can I know that it is working in cm10 or not?
Click to expand...
Click to collapse
Basiclally deep sleep is when your phone's cpu is going into a low state but in most cases the Deep Sleep is already enabled.
You can try to put the cpu's governor on conservative.:victory:
nstool will give you the info whether it is active or not
Hi there,
I'm using the latest Air Kernel (Weekly #298) with Stock ROM on my Nexus S. But in NSTools I don't get features like Deep Idle or Live OC at the CPU tab – although they should be there. Already tried "fix permissions" in CWM but this doesn't seem to be the solution. Maybe, did I forget something else? Couldn't ask at the corrensponding development thread because of my noob status.
They are not included in the kernel. Read air kernel's features list.
Hm, okay, "Live OC" is listed as removed in the changelog. But I couldn't find anything about Deep Idle because it was a feature in the past. Maybe it's also removed because of stability issues!?
.stendeck said:
Hm, okay, "Live OC" is listed as removed in the changelog. But I couldn't find anything about Deep Idle because it was a feature in the past. Maybe it's also removed because of stability issues!?
Click to expand...
Click to collapse
Deep idle has not been included in latest batches of kernels because of stability issues. Nobody was ever able to get it perfectly stable so the glitches, freezes, screen of death and so on outweight the battery saving. Nothing really changed from GB to ICS and JB in terms of deep idle stability, just that everyone somehow agreed to let it die a peaceful death.
Thanks for the explanation. That would explain a few things.
Hey,
Having a problem with my N5 draining my battery @ 4% / hr even when idle. According to the battery screen in settings the culprit is Android OS @ 32%.
I'm running CM M2 (stock kernel) on TMobile. I've got WiFi + Bluetooth on. NFC is off.
For comparison the phone has been on battery for 6hrs with only a few minutes screen on time and is at 61%.
Thoughts?
Sent from my Nexus 5 using xda app-developers app
Any apps draining that shouldn't be? Turn auto brightness off and keep around 30%. Screen always takes the most.... clearly. Could be fault of CM since they are nightlies and those are always a work in progress. Post in CM thread, always read previous post in that thread for battery issues.
I'm running stock ROM, and getting the same amount of battery drain as you. I'm pretty sure this is coming from wlan_rx_wake wakelocks if you have wifi on while this is draining. Though having data on doesn't help me, I just get bam_dmux_wakelocks. Try better battery stats to see what wakelocks are keeping your phone awake. I have tried everything to get wlan_rx_wake to stop, yet it hasn't. Would love if someone knew how to fix this battery drain.
Just installed better battery stats. Will report back in a few days.
I do suspect WiFi as well. I was out on LTE all day yesterday and the drain was < 1% / hr and after 12+ hrs I was at 80%.
I have geenified a lot of apps. No luck so far
Sent from my Nexus 5 using xda app-developers app
Turn off bluetooth. Android OS being the main culprit means an app is keeping it awake. Also, I've bad experience (at least in my s3 days) with CM with regards to battery. Try switching ROMS and try franco kernel as well (great battery life without gimping performance)
Your coverage can have a huge impact on battery drain. At work I have poor coverage and my battery will be low by the end of the day at home its good I will have less battery drain with more usage.
Sent from my Nexus 5 using Tapatalk
Cpudan80 said:
Just installed better battery stats. Will report back in a few days.
I do suspect WiFi as well. I was out on LTE all day yesterday and the drain was < 1% / hr and after 12+ hrs I was at 80%.
I have geenified a lot of apps. No luck so far
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I think the easiest thing to see if it's ROM related or app related is to just backup your current ROM and re-flash the ROM without anything (besides your basic absolute must need app but try and avoid if possible) and try it for a day. If you still have the battery drain, then it's the ROM, in which case, I suggest using a different ROM. I recommend Omni or Cataclysm. If not, then it might be an app burning through your battery then.
I am not able to let my phone go on for 24 hours without charging. I definitely need to charge it daily. I tried turning off the wifi and data and all background apps and services, just the android stuff is running, still can't go over 24 hours. At most is around 20 - 22 hours on standby.
I'm having same issues. On stock rom.
Sent from my Nexus 5 using xda app-developers app
And I thought that getting 5.5% / h is normal (with LTE on) with syncing accounts and stuff.
Mine used to be so good. What's happened
Does the above screen shot mean anything?
Sent from my Nexus 5 using xda app-developers app
kraven001 said:
And I thought that getting 5.5% / h is normal (with LTE on) with syncing accounts and stuff.
Click to expand...
Click to collapse
Anything over 1% per hour while idling, whether wifi or lte, is unacceptable.
Post your BBS logs people. If you're going to post screenshots, at least post all of the screens. Less work for you to hand over the log.
Aerowinder said:
Anything over 1% per hour while idling, whether wifi or lte, is unacceptable.
Click to expand...
Click to collapse
+1 just disable feauteres you don't use. I have auto-sync enabled but I check only the very necessary syncing (gmail for me). Disable location report from google, Google now, OK Google hotword detection... And even greenify those battery killing apps (check partial wakelocks and alarms)
I have the same behavior with about 4% drain per hour screen
off idle when I use a CM nightly from about the last 10 days with bricked kernel. So I'm still with my january 07th. CM Nightly which has no drain at all.
The culprit for me is an EntriesRefresh wakelock coming from google.quicksearchbox. No idea what that is -- but it appears to be a common source of problems on KK ROMs across all devices.
i do like Google Now so I don't want to greenify that. Hopefully google will fix the app soon enough.
Anyone have any other thoughts/suggestions?
-- Dan
If I disable everything on my phone , maybe I can get the 1% / hour, but frankly I don't see the point.
I like google now, I like my emails syncing and getting notified about things - that's why I use a darn smartphone, otherwise I would get a "dumb" phone that idles.
How do you export all on bbs?
Sent from my Nexus 5 using xda app-developers app
Does your battery screen for Android OS look like this -
Or this -
Sent from my Nexus 5 using Tapatalk
Cpudan80 said:
The culprit for me is an EntriesRefresh wakelock coming from google.quicksearchbox. No idea what that is -- but it appears to be a common source of problems on KK ROMs across all devices.
i do like Google Now so I don't want to greenify that. Hopefully google will fix the app soon enough.
Anyone have any other thoughts/suggestions?
-- Dan
Click to expand...
Click to collapse
Google Now isn't inherently bad on battery. Are you using GEL?
I do Greenify it, but only because it has no purpose for me.
Aerowinder said:
Google Now isn't inherently bad on battery. Are you using GEL?
I do Greenify it, but only because it has no purpose for me.
Click to expand...
Click to collapse
Not using Google Experience Launcher just the regular AOSP launcher, but Google Now is enabled and the search box is on my launcher (but its not voice activated.)
What is the quick search box exactly? When I went to greenify it, greenify said that it was a system app and that greenifying it could cause problems.
-- Dan