Could the notification light (ie. from Wordfeud or text) keep phone at 200 Mhz instead of deep sleep? CPUspy shows my phone at 7 hrs at 200 Mhz overnight, then only 2 hours of deep sleep. I had a late night notification and didn't turn it off until morning. Thanks.
kennyglass123 said:
Could the notification light (ie. from Wordfeud or text) keep phone at 200 Mhz instead of deep sleep? CPUspy shows my phone at 7 hrs at 200 Mhz overnight, then only 2 hours of deep sleep. I had a late night notification and didn't turn it off until morning. Thanks.
Click to expand...
Click to collapse
ANSWER/HELP/SUGGESTIONS:
If the notification awakened your phone's display, then the answer is yes. If the notification didn't awaken your phone's display from sleeping, then no.
Also your screen's on/off min/max CPU frequency could be apart of the "problem" (if this is a problem you're having) you're dealing with.
- Knowledge
XDA-Dev-Knowledge said:
ANSWER/HELP/SUGGESTIONS:
If the notification awakened your phone's display, then the answer is yes. If the notification didn't awaken your phone's display from sleeping, then no.
Also your screen's on/off min/max CPU frequency could be apart of the "problem" (if this is a problem you're having) you're dealing with.
- Knowledge
Click to expand...
Click to collapse
Thanks, but the phone normally sleeps fine, but only been checking it a few days. I know I got a Wordfeud notification in the middle of the night and when I responded this morning and checked and hour or two later, saw only a little deep sleep and 7 hours at 200 Mhz. Display was not on, and don't think it lights up when I get the notification. Just a tone and blinking red light. I can't add the 100 Mhz step because then the phone won't wake from sleep.
kennyglass123 said:
Thanks, but the phone normally sleeps fine, but only been checking it a few days. I know I got a Wordfeud notification in the middle of the night and when I responded this morning and checked and hour or two later, saw only a little deep sleep and 7 hours at 200 Mhz. Display was not on, and don't think it lights up when I get the notification. Just a tone and blinking red light. I can't add the 100 Mhz step because then the phone won't wake from sleep.
Click to expand...
Click to collapse
I understand what you mean by underclocking the phone too low, so that isn't an option.
Let's try troubleshooting the problem, then shall we?
Tonight I'd like for you to go to sleep, take note of what apps were all running and also sleep with the Wordfeud notification off. Wake up in the morning and see if the same problem persist. From there I'll have enough information to work with. Oh and make sure that no app is waking the phone while you sleep. So that your phone's display and yourself do one thing that it needs to do, sleep.
XDA-Dev-Knowledge said:
I understand what you mean by underclocking the phone too low, so that isn't an option.
Let's try troubleshooting the problem, then shall we?
Tonight I'd like for you to go to sleep, take note of what apps were all running and also sleep with the Wordfeud notification off. Wake up in the morning and see if the same problem persist. From there I'll have enough information to work with. Oh and make sure that no app is waking the phone while you sleep. So that your phone's display and yourself do one thing that it needs to do, sleep.
Click to expand...
Click to collapse
I haven't used my phone much today and my wordfeud buddy must be sleeping one off today so have not got any notifications and phone is sleeping 75% of the time whereas last night with the notification I only got 22% deep sleep. So whether it is the wordfeud notification or notification in general, there is something holding the phone at 200 Mhz.
kennyglass123 said:
I haven't used my phone much today and my wordfeud buddy must be sleeping one off today so have not got any notifications and phone is sleeping 75% of the time whereas last night with the notification I only got 22% deep sleep. So whether it is the wordfeud notification or notification in general, there is something holding the phone at 200 Mhz.
Click to expand...
Click to collapse
Start with the wordfeud notification being off....then try just notification in general. I thought you were a moderate user of your phone. From the looks of it you use your phone lightly which makes solving the problem easier.
Post back after tonight as to if turning off the wordfeud's notification solved the problem.
XDA-Dev-Knowledge said:
Start with the wordfeud notification being off....then try just notification in general. I thought you were a moderate user of your phone. From the looks of it you use your phone lightly which makes solving the problem easier.
Post back after tonight as to if turning off the wordfeud's notification solved the problem.
Click to expand...
Click to collapse
Normally I am, but had a virus past 2 days so been real mild use, like you said, makes it easier to notice strange behavior. Probably best test would be to reboot and get a text and see after 15 minutes or so, then do the same with Wordfeud to see what is going on...thanks.
kennyglass123 said:
Normally I am, but had a virus past 2 days so been real mild use, like you said, makes it easier to notice strange behavior. Probably best test would be to reboot and get a text and see after 15 minutes or so, then do the same with Wordfeud to see what is going on...thanks.
Click to expand...
Click to collapse
You could also do a fresh install of the rom after a fresh install do this:
- Send a text with all notifications off, to about 3 people, put phone in sleep mode, come back 15 minutes later, check if that's the problem
IF NOT MOVE ON
- Send a text with all notifications on, to about 3 people, put phone in sleep mode, come back 15 minutes later, check if that's the problem
IF NOT MOVE ON
- Install Wordfeud and have its notifications off, put phone to sleep and come back 15 minutes later, check if that's the problem
IF NOT MOVE ON
- Install Wordfeud and have its notifications on, put phone to sleep and come back 15 minutes later, check if that's the problem
Simple troubleshooting method right there...it should hit the nail on the head for ya
Thank you...good stuff there. So far my text notification beeps, flashes the red light for about a minute then stops, phone goes into deep sleep. Wordfeud must be having issues tonight because I can't get a notification from it. Will try again tomorrow for Word Feud. This may have all been fixed with the reboot.
I always thought text message keeps flashing light until you aknowledge it though.
kennyglass123 said:
Thank you...good stuff there. So far my text notification beeps, flashes the red light for about a minute then stops, phone goes into deep sleep. Wordfeud must be having issues tonight because I can't get a notification from it. Will try again tomorrow for Word Feud. This may have all been fixed with the reboot.
I always thought text message keeps flashing light until you aknowledge it though.
Click to expand...
Click to collapse
No actually they flash for a specified period of time (dependent upon the rom's/phone's setting for it). Also the problem with not getting a notification from wordfeud could be simply solved by wiping the app's data & cache, then rebooting and it'll be like a fresh install of the app.
So again the above post should hit the nail on the head for you. If it does please post what the problem was so that others can learn from it.
- Knowledge
XDA-Dev-Knowledge said:
No actually they flash for a specified period of time (dependent upon the rom's/phone's setting for it). Also the problem with not getting a notification from wordfeud could be simply solved by wiping the app's data & cache, then rebooting and it'll be like a fresh install of the app.
So again the above post should hit the nail on the head for you. If it does please post what the problem was so that others can learn from it.
- Knowledge
Click to expand...
Click to collapse
OK, figured it out. The phone stays at 200 Mhz while charging. Is that normal? Plugged in for 7 hrs, sat at 200Mhz for 7 hrs.
kennyglass123 said:
OK, figured it out. The phone stays at 200 Mhz while charging. Is that normal? Plugged in for 7 hrs, sat at 200Mhz for 7 hrs.
Click to expand...
Click to collapse
What is the lowest you can underclock your phone while sleeping? Because if its 100Mhz then use setCPU and make two profiles and that is the set the min to 100Mhz while charging and sleeping. But if you can't underclock that low then what is the lowest you can underclock to besides 200Mhz? Because if you can't underclock any lower than your phone sitting at 200Mhz for 7hz is GOOD
XDA-Dev-Knowledge said:
What is the lowest you can underclock your phone while sleeping? Because if its 100Mhz then use setCPU and make two profiles and that is the set the min to 100Mhz while charging and sleeping. But if you can't underclock that low then what is the lowest you can underclock to besides 200Mhz? Because if you can't underclock any lower than your phone sitting at 200Mhz for 7hz is GOOD
Click to expand...
Click to collapse
I am using Voltage Control and when I add the 100 Mhz step with no undervolting, my phone will not wake from sleep without battery pull. My GF's phone has SetCPU and it appears to show some usage at 100 Mhz (1%) and also sits at 200 Mhz while on the charger. I guess that is the battery charge monitoring circuit and code running.
As long as it is normal that is cool. Thanks for helping me figure this out. I guess sometimes too much info can cause problems...damn you CPUspy! LOL!
kennyglass123 said:
I am using Voltage Control and when I add the 100 Mhz step with no undervolting, my phone will not wake from sleep without battery pull. My GF's phone has SetCPU and it appears to show some usage at 100 Mhz (1%) and also sits at 200 Mhz while on the charger. I guess that is the battery charge monitoring circuit and code running.
As long as it is normal that is cool. Thanks for helping me figure this out. I guess sometimes too much info can cause problems...damn you CPUspy! LOL!
Click to expand...
Click to collapse
Lol yeah damn you CPUspy!!!! But 200Mhz is normal just, from your first post I thought you were trying to go 100Mhz underclock/undervolt. But since you can't 200Mhz is good for you then Glad we could figure this out together buddy.
I'll see ya around
- Kevin
Related
When I run the latest android build on my Tilt 2, it flies through battery like no other.
Are there any settings I can tweak to get at least a full day's worth of use out of it (mostly in standby anyways)?
Thanks
Regards
Smith
I'd love to hear anyone's tips as well. As mentioned here:
http://forum.xda-developers.com/showpost.php?p=7959929&postcount=7622
Setting the sleep mode = 1 doesn't seem to work for me. The processor seemingly goes to sleep and enters a coma (yes, I set the clock speed back to stock in the startup.txt).
One quick tip to the OP is set the clock speed to stock.
Edit: sleep mode = 0 seems to work (GSM phone here). However, deleting the "acpuclock.oc_freq_khz=XXX" line from the startup.txt and setting sleep=1 just might work as well.
Edit2: sleep mode = 0 seems to result in the phone functionality breaking. It stopped waking up to phone calls after a while, and calling out wouldn't work either. Damn.. Just a heads up.
1. Close every program that you don't use on startup of android. You can do this with advanced task killer.
2. Run stock speeds.
3. Turn down the screen brightness.
4. Make sure your phone goes to sleep when you are not using it (green led = sleep)
Is advanced task killer installed by default?
Also, how can I clock it to stock? I wasn't aware that it was overclocked past stock.
Screen brightness makes sense, I'll definitely do that.
So, if green is sleep, what is the orange?
Thanks
Smith
I reckon hepatic feedback would drain a little battery on its own probably best to turn that off
This is all true. I'll have to do that.
Still figuring it all out. Once I can get a solid 18-24 hour charge cycle out of it, Android will become my primary OS, easily. Simply works better, IMO
For me sometimes it's green, sometimes it's Orange - not sure how to change it back green -
I use Advance Task Killer, but then i also read that Froyo 2.2 doesn't need a task killer?
The two things that have helped battery life the most were:
-Switching to stock clock speed (the reference over the overclocked BLZN which i loved but killed the battery life)
-turning off background processes... i only turn it on when i have to (using the market, etc)
I would love to hear more tips
The colours are not that hard.
Red/orange = awake
Green = sleeping
If the LED stays red, then your device is doing something, you can either wait or try closing the programs with the task killer. That will help sometimes.
For returning to stock speeds read the faq And advanced task killer can be downloaded in the market.
Thank you guys all so much, big, big help to me!
Android is definitely going to be my full time OS shortly
Smith
Its kind of tough trying to go anywhere without a charger nearby. The battery drains quickly and on top of that the actual battery meter is off.
So sometimes that is a main issue
Sent from my MSM using Tapatalk
throwback1718 said:
Its kind of tough trying to go anywhere without a charger nearby. The battery drains quickly and on top of that the actual battery meter is off.
So sometimes that is a main issue
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
Indeed but that is something that they are working on it as we speak. Give them time
I ran a test last night before going to sleep to see how long the phone lasts.
Charged my phone fully. Ran advanced task killer and killed all the programs. Put the phone in deep sleep ( green light).
Woke up 7 hours later and phone was completely dead. I do have auto sync turned on, but only over wifi, so it should not have used any data as i have the data turned off and no widgets on my home screens that auto-update.
I'll try again tonight for a shorter time (5 hours).
Running the blazn aug 30th build.
karan1203 said:
I ran a test last night before going to sleep to see how long the phone lasts.
Charged my phone fully. Ran advanced task killer and killed all the programs. Put the phone in deep sleep ( green light).
Woke up 7 hours later and phone was completely dead. I do have auto sync turned on, but only over wifi, so it should not have used any data as i have the data turned off and no widgets on my home screens that auto-update.
I'll try again tonight for a shorter time (5 hours).
Running the blazn aug 30th build.
Click to expand...
Click to collapse
How did you 'put the phone in a deep sleep'
I turned off all auto updates.
The next day i did the test again, charged the phone to 100% and used the phone moderately for 8 hours before the battery died.
Without overclocking i can safely say i can get the phone to last 8 hours with moderate to heavy usage, which is excellent.
My main problem with the new updates are that it constantly restarts or crashes after using it for less than 30 minutes while before I could use it for several hours. Not sure whether it's to do with battery life or not as when it boots back in WM the battery is near full.
The biggest things that have helped conserve battery life for me are disabling GPS and background syncing but some apps require this to be enabled. :S
Phone seems to recover from "sleep"
FWIW, I set sleep mode = 1 and removed the overclock line from the startup.txt and the phone SEEMS to sleep and "wake up" just fine. Previously, I had problems with the phone going to sleep and when waking up, everything seemed fine, but the phone didn't work. With the overclock line removed, it seems to "wake up" with the phone working now.
Just a heads up to anyone who wants to save battery life.. might want to remove the overclocking line in the startup.txt..
I tried using the app called Light Flow in order to control the LED notification colours, seems to have been draining the battery..anyone else experience this?
Yeah I've noticed something causing my cpu to 'wake' more than it should when it should be idle. I've been thinking it might Light Flow, think I'll uninstall it tonight and see how much I lose overnight.
Don't know whether it's been the updates it has been getting or if it's done it all the time, but I know my battery certainly didn't drain this quickly before when idle.
whyamihere said:
Yeah I've noticed something causing my cpu to 'wake' more than it should when it should be idle. I've been thinking it might Light Flow, think I'll uninstall it tonight and see how much I lose overnight.
Don't know whether it's been the updates it has been getting or if it's done it all the time, but I know my battery certainly didn't drain this quickly before when idle.
Click to expand...
Click to collapse
yeah same thing happens to me, in the battery stats Android OS is the main contributor to drain and the CPU Awake time is always pretty high
interesting I havent suffered much noticeable effect on the battery. I juhst crashes every time i reboot the phone.
I disabled it earlier because I was having problems with it flashing after the notification was gone. Didn't notice any extra strain on battery though, although it could have been there.
At the moment it's 1 day 16 min on battery, with 20% Android OS and 5h 38m awake CPU time, is that high? (the Android OS bit/awake time)
Not noticing any drain with Lightflow... I notice that when an email/text comes in the phone wakes up briefly but whether that's Lightflow or normal I don't know... but the phone is asleep from then until I turn it on, even though the LED is flashing away merrily in the meantime. And I looked at this overnight - so getting an alert at maybe 2 or 3am and then actually checking it at 8am or so. Nothing abnormal between 2am and 8am, and noticed no extra battery drain.
case0 said:
I disabled it earlier because I was having problems with it flashing after the notification was gone. Didn't notice any extra strain on battery though, although it could have been there.
At the moment it's 1 day 16 min on battery, with 20% Android OS and 5h 38m awake CPU time, is that high? (the Android OS bit/awake time)
Click to expand...
Click to collapse
Had this problem but I think I understand how it works now.
It will keep flashing if you have "individually" removed the notifications out of the notifications bar. Removing notifications this way doesn't seem to register in Light Flow but you can solve this by:
(a) running that app
(b) hit the "X" button to clear all notifications in the notifications bar.
Can anyone find a way to see if it really is Light Flow that consumes that much battery? I cannot really tell.
Hi.
Light flow will cause some battery drain, but I try to keep it as little as possible.
You will see a fair amount of time partially awake (not the screen on, but showing as awake in the battery usage) because of the app as every time you have more than one outstanding notification (of different colors) the app has to do a partial phone wake to run the alarm manager that changes the color.
There's a few things that can help this, firstly slowing down the frequency of cycling colors ("Notification - battery", in general settings).
Fast = 2.5 seconds
Medium = 5 seconds
Slow = 10 seconds
Very slow = 20 seconds
The other option is just to show the highest priority notification that's currently outstanding - then you'll just get 1 color (e.g. if you have an e-mail, missed call and sms message all outstanding - if you have priority of 1 set on missed call then only that will display of the 3)
Unless you really need them, all the additional light controls in the general settings menu e.g. button backlight, flash etc should be disabled to keep things minimal.
With the latest 2.7.x releases I found (on a nexus one) that the partial wake is for less than 100th of a second on every cycle change (previous version had got to about 400ths of a second)
As for not clearing the notification, at the moment I've got no hooks into swiping away individual notifications from the notification bar so they will keep flashing.
I'm thinking of adding an extra battery saving option where just the most recent notification type is shown as there wouldn't be the need for partial wakes for that.
The good news is I just got a Galaxy Nexus yesterday and after quite some time got the adb drivers working so I'll be looking into seeing what's possible with ICS soon.
So far I've just made one ICS specific change for the next release which is to remove the nag screen on upgrading about restarting accessibility as it seems google have finally sorted out the accessibility bug that caused the need for a restart!
Cheers for the clarification and help, andrewpmoore. Great app.
The option that makes the LED shows only the most recent notifications will be VERY WELCOME! Look forward to the update
Good Job, glad you finally have the handset! can't wait for the next release!
No issues here. I think it really depends on your settings those. Especially the color cycles.
SweetPAIN225 said:
Good Job, glad you finally have the handset! can't wait for the next release!
Click to expand...
Click to collapse
Don't get too excited about the next release. It'll just be a bug fixes one (and the nag removal for ICS)
If there are any devs on here that can work out a way to pick up on the swipe to remove notifications could they get in touch. I've not found anything useful in the accessibility service so far.
Probably didn't see my question in another thread, but can you add a full RGB colour picker? Seeing as it's an RGB LED I assume this is possible, rather than just having the current, fixed, selection of named colours?
Great job andrewpmoore, will definitely use this as soon as my GN arrives
Don't need to worry about battery drain from Light Flow any more andrewpmoore.
I first tried disabling the app then uninstalling, I still had the same battery drain from Android OS, so my problem lies elsewhere.
I've reinstalled Light Flow now, great app!
whyamihere said:
Don't need to worry about battery drain from Light Flow any more andrewpmoore.
I first tried disabling the app then uninstalling, I still had the same battery drain from Android OS, so my problem lies elsewhere.
I've reinstalled Light Flow now, great app!
Click to expand...
Click to collapse
That's good to know, thanks.
---------- Post added at 08:03 AM ---------- Previous post was at 08:02 AM ----------
jabok said:
Probably didn't see my question in another thread, but can you add a full RGB colour picker? Seeing as it's an RGB LED I assume this is possible, rather than just having the current, fixed, selection of named colours?
Click to expand...
Click to collapse
It's something I've had on my todo list for a while. It'd be relativley simple for phones line the Nexus One and Galaxy Nexus, the difficult part is fitting it in with the "direct mode" settings and mapping colors between them.
I'll see what I can do.
Light Flow also caused Sleep of Death on my phone. I've uninstalled and all is well now.
AMoosa said:
Light Flow also caused Sleep of Death on my phone. I've uninstalled and all is well now.
Click to expand...
Click to collapse
same here.. massive battery drain/phone got hot and she went night night.. had to pull battery. uninstalled
Considering other people are getting the sleep of death without Lightflow it seems a little rash to decide that Lightflow is causing it.
AmesCell said:
Considering other people are getting the sleep of death without Lightflow it seems a little rash to decide that Lightflow is causing it.
Click to expand...
Click to collapse
Add to that the cases where people are using Lightflow and NEVER had the Sleep of Death, it's fair to say Lightflow is not the (sole) cause. It MAY be behaving badly with some other app I guess... but I've been running it since day 2 (18th) and never had the sleepy death thing.
All, i'm having a huge problem. beginning last weekend, whenever I wake up I find my phone clock has become nearly 5 minutes slower.
Because of my sleep schedule on the weekdays, its always 5 minutes late by the time i wake up. strange thing is, within 10-15 min of my phone being "awake" I assume the auto clock sync corrects the wrong time and by the time i'm i'm driving to work the clock's time is right.
i tried turning off wifi one night i think a couple days ago to see if it was some type of strange wifi issue and i found that with wifi turned off, my phone was almost 20 minutes off on the time.
This has affected strangely my alarm clock as well and sometimes it doesn't even go off and i naturally wake up and check and it shows the screen where the alarm clock is running, asking me to "dismiss" or "snooze"
This is super cumbersome, is ANYONE else having this issue with the hox? my only conclusion is while i am sleeping and my phone is on standby for many hours something isn't quite doing its job. maybe something like the phone time being off, i don't know, like 30 seconds an hour or something. I'm still on 1.73.
during the day while my phone is turned on every 30 min to an hour, my clock is perfectly sync'ed.
please help.
turn off auto updating and manually set it - does it still happen?
it could be a conflict between phone time and network time, and the phone stops checking when asleep?
phil112345 said:
turn off auto updating and manually set it - does it still happen?
it could be a conflict between phone time and network time, and the phone stops checking when asleep?
Click to expand...
Click to collapse
that's a good test to try. will do that tonight, turning off network sync and leaving it on manual. will report back tomorrow AM
chillsen said:
All, i'm having a huge problem. beginning last weekend, whenever I wake up I find my phone clock has become nearly 5 minutes slower.
Because of my sleep schedule on the weekdays, its always 5 minutes late by the time i wake up. strange thing is, within 10-15 min of my phone being "awake" I assume the auto clock sync corrects the wrong time and by the time i'm i'm driving to work the clock's time is right.
i tried turning off wifi one night i think a couple days ago to see if it was some type of strange wifi issue and i found that with wifi turned off, my phone was almost 20 minutes off on the time.
This has affected strangely my alarm clock as well and sometimes it doesn't even go off and i naturally wake up and check and it shows the screen where the alarm clock is running, asking me to "dismiss" or "snooze"
This is super cumbersome, is ANYONE else having this issue with the hox? my only conclusion is while i am sleeping and my phone is on standby for many hours something isn't quite doing its job. maybe something like the phone time being off, i don't know, like 30 seconds an hour or something. I'm still on 1.73.
during the day while my phone is turned on every 30 min to an hour, my clock is perfectly sync'ed.
please help.
Click to expand...
Click to collapse
Are you using a custom kernel? Some kernels can have time slew issues. Most people don't notice it. I use Clocksync from the market to keep synced.
Sent from my HTC One X using Tapatalk 2
Evil-Dragon said:
Are you using a custom kernel? Some kernels can have time slew issues. Most people don't notice it. I use Clocksync from the market to keep synced.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
i've only rooted it for titanium back up. kernel is factory. i am definitely going to look into clocksync as well after tonight's test. thank you.
i can confirm after i turned off network clock sync that it indeed was not the problem and that there is something inherent in the software that is slowing down my clock on my phone overnight. thing is i don't have any crazy apps. this is so strange.
anyways i have downloaded ClockSync and seeing if this will fix the problem. thanks
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
I have autorotation turned on but not the face orientation sensing. I haven't noticed a significant battery loss, at 19 hours with 10 left according to battery spy, but I'll give this a try and see if it increases it any.
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
madsquabbles said:
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
Click to expand...
Click to collapse
I have noticed Google Talk drains batteries when your signed in. By default your phone will sign in. If you don't use TALK, sign-out of the app and you will see increased battery life. Your wont ping the internet as much which saves batteries.
Thanks viperboy I took your suggestion and so far it seems to be helping.
I haven't tried that app yet, however I have definitely noticed an improvement in battery life by disabling auto rotation. Thanks for the info.
THIS NOTE 2 IS SENT FROM A GALAXY WHERE SAMSUNG SPRINTS TO THE TOP, AND JELLY BEANS EAT APPLES!!!!
after a bit of troubleshooting i found that battery monitor widget pro was the cause of my drain. after removing it i went from 2 to 3% an hour to 3% overnight. this really sucks as i love the info bmw colleects. this is the only device i have that suffers drain from the app.
Thanks for the info. I have been losing % 15 battery every night while I'm asleep and was wondering why
...from a Galaxy Note II
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Thank you for this info. I consistently get a full days charge of of my phone but was pretty clueless when it came to what was draining my battery. I've used the rotation lock app and will report my results to see if I get even more remaining battery each day.
Sent from my SPH-L900 using xda app-developers app
Thanks for the helpful advice Viperboy! I've definitely been having wake lock issues with my phone. Hopefully these apps will help me eliminate the problems.
kat3k said:
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Click to expand...
Click to collapse
As viperboy mentioned, BetterBatteryStats is your friend. It really will help you figure out why your phone isn't sleeping like it should. It definitely takes some time to monitor and figure out what the readings mean to help point you to the apps or settings that're affecting your battery, but well worth it. I also like having a better understanding of how things work on my phone.
i did a double check on battery monitor widget pro and it started draining my phone again. as soon as i uninstalled it everything was fine again. this is with both cleanrom and blazer. i'll just wait til official support comes and try it again.
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
ZenInsight said:
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
Click to expand...
Click to collapse
I'm on it now, but I haven't looked to see if it fixed the auto rotation bug yet,
rudyrude432 said:
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
That app is unnecessary. Pegasusq governor already does that by default. Goes to 1 core and 200mhz when screen off, at least that's how my Note 10.1 was. I assume it is the same here since the International GS3, GN 10.1, and GNII basically share the same kernel with a few minor differences.
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Interesting... I have a script that reports on CPU freq and, when plugged into USB (maybe the wall charger too, didn't check), it appears that the kernel runs cpu0 and cpu3 all the time, even when screen off. With the phone unplugged, it went to using only cpu0 but didn't cap the freq. It was spending a good amount of time at the higher frequencies even though I had nothing running.
MiguelHogue said:
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1959898&page=5
Post #42
I installed the app to turn the rotation off when the screen is off so far everything good but when I get a call this goes crazy because the screen goes while in call. I know this because I have an smartwatch which it has a notification app and every message that the phone has my watch vibrates with that message and I had a call few minutes ago my watch started vibrating non stop until I hang up.
Sent from my SPH-L900 using Tapatalk 2
I'm on stock, rooted, s-off
my device is getting extremely hot during normal use.(i dont play games at all, just whatsapp, facebook, news etc..)
sync is off, auto brightness.no google location reporting and history, no google now or history.
and using bbs to see what is going on ,i have no wakelocks and looking at battery screen, screen on time and awake time are almost identical.so nothing is keeping my device awake.
but for some reason, when the device is idle, the cpu goes nuts!
i installed cpu status bar xposed module so i could monitor cpu on real time, and i see the device jumping allot from 300mhz to 960 and 1000+ for no reason.(without touching it, and no apps running).when i touch the screen it scales to maximum.
it drives me crazy because i dont understand why the cpu behave like that.there is no logical reason for cpu going to max when i'm typing text.
its unbearable, cause its getting really hot while i hold it.
i have tried various kernels(elementalx, skydragon, faux, ionx, hacker kernel, but all of them shows that behavior.
on my old i9100, i never got that behavior, ondemand governor was perfect and i could reach 4 hours of screen on time.with the m8, i can barley pass it , going for 4-5 hours, because its draing too fast.
any suggestions?
*EDIT*
tried a factory reset, and i just installed xposed with cpufreq status bar module, and the device is still going nuts.WTF?
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
thebobmannh said:
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
Click to expand...
Click to collapse
i know there are background process and apps, and i don't except the device to stay at 300mhz all the time, but its quite annoying to hold on to a device and feel its temperature rising to insane levels without doing anything fancy with it.just texting.and every touch ramp the cpu to the max frequency, its weird.and unnecessary.
i don't know if its normal behavior, as i mentioned, my old i9100(galaxy s2) would not act like this. and i could get 4 hours of screen on time, and here, i get 4-5 hours max.it dose not seem logical.
I'm not using lte of nfc or BT.my reception is full(both wifi and cell).
i just want to know if this a normal behavior? anyone else having this heat buildup on light use?
I have a similar problem there on M8S. I killed half the background tasks, disabled syncing, auto backups, and then I open FBreader(or any other app) at 30% brightness and all the cpu cores go to 50 degrees C, heat up my battery to 43 degrees C. It results in loss of 40% of battery charge in just an hour. With screen off my device usually consumes 1-2% an hour. Whatever I do, I have never seen at least one core sleeping, they always work at 600-900MHz.