OK. My wife phone is really crazy draining battery like it's crack. Soo would like to know anyone using this. What's your set up. Should I do load on bootup etc? Scaling set to? When screen off so forth. She's on SC 2.9.2 with jt kernel lastest one. Thx for the help guys.
Sent from my ADR6400L using XDA Premium App
Interactive. Ondemand. Conservative. Performance. Pretty much self explanatory right? Does anyone have a nice guide for fascinate? Maybe. I set up 400mhz on sleep and.it would power on after putting on lock.
Sent from my ADR6400L using XDA Premium App
I'm not having battery issues and I'm running just the 2.2 leak with JT's 327-2 kernel. Just set CPU to conservative and maybe drop it down to 800 mhz. I spent the majority of my day today talking on my phone and playing cordy and I was at 50%.
You can give this a shot it could just be giving weird info on the battery level. while the phone is on, charge the battery to 100% full. Turn off phone plug it in and charge to 100% again. Boot phone into CWR and clear the battery stats. Start phone like normal.
Hope that helps.
Install spare parts and use the Battery History feature and check for a wakelock. Thats the prime reason why a phone will drain like crazy.
To check for a wake lock Spare Parts> Battery History >And look to see how long it's running. If it's a really high % and the screen has been off you have a wake lock.
To find out what's causing the wakelock click "other usage" and choose "partial wake usage".
If it's Android system it's probably the GPS doing it. So turn off the GPS unless you're using it.
Cool ill check those out.
Sent from my ADR6400L using XDA Premium App
So setcpu useless then? Or does it even make a little difference with the battery? On sleep at least?
Sent from my ADR6400L using XDA Premium App
I find the phone to do a good job of managing itself but I also haven't played with setcpu alot. A sleep profile probably wouldn't hurt things... but someone else is probably better suited to answering your question.
The only thing I'm using it for now is for a temperature profile to act as a failsafe if the phone/battery start gettting too hot.
bobloblaw1 said:
I find the phone to do a good job of managing itself but I also haven't played with setcpu alot. A sleep profile probably wouldn't hurt things... but someone else is probably better suited to answering your question.
The only thing I'm using it for now is for a temperature profile to act as a failsafe if the phone/battery start gettting too hot.
Click to expand...
Click to collapse
Thx for the info. I'm running into screen freeze with setting up sleep profile... Grrrrr.
Sent from my ADR6400L using XDA Premium App
dadsterflip said:
Thx for the info. I'm running into screen freeze with setting up sleep profile... Grrrrr.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Just speed up the minimum mhz for the profile. I believe 400 would be okay, try it.
Dread This Day said:
Just speed up the minimum mhz for the profile. I believe 400 would be okay, try it.
Click to expand...
Click to collapse
No luck..... Freezes
Sent from my ADR6400L using XDA Premium App
Freezes only on conservative. But ondemand works great
Sent from my ADR6400L using XDA Premium App
dadsterflip said:
So setcpu useless then? Or does it even make a little difference with the battery? On sleep at least?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
SetCPU may help with battery life however you are better off with JuiceDefender in my opinion. This will automatically turn off items not needed when phone screen is off.
If battery draining is your real problem, this thread may also help:
http://forum.xda-developers.com/showthread.php?t=987529
Set CPU isn't really fully compatible with the fascinate. The author says use a certain profile but it doesn't help much. When i used set CPU, my phone would go to sleep endlessly and I wasn't able to turn the screen on. This is because there was a bug causing it to go down to 19.2Mhz even though I set it at around 400. I had to pull the battery to solve this.
I have found that running Setcpu freezes mine up anytime it goes into sleep mode not matter what speed it is set at. The only way I was able to fix this was by removing the app, reflashing the kernel, and reinstalling it.
Have you tried to charge to 100% with the phone off, boot into recovery, and clear the battery stats? Run the battery to death before charging and you will have improved battery life.
Ill try to do all those advices guys. Thx for the info.
Sent from my ADR6400L using XDA Premium App
SuperFan86 said:
Run the battery to death before charging and you will have improved battery life.
Click to expand...
Click to collapse
Do NOT run the battery to "death". This actually is bad for the battery. Every time you do this you will kill cells that will never come back giving you less life per charge of the battery.
Suicide Shift said:
Do NOT run the battery to "death". This actually is bad for the battery. Every time you do this you will kill cells that will never come back giving you less life per charge of the battery.
Click to expand...
Click to collapse
You are right.
I meant run it super low, it may even display 0. This allows for better calibration of the battery.
Zacisblack said:
Set CPU isn't really fully compatible with the fascinate. The author says use a certain profile but it doesn't help much. When i used set CPU, my phone would go to sleep endlessly and I wasn't able to turn the screen on. This is because there was a bug causing it to go down to 19.2Mhz even though I set it at around 400. I had to pull the battery to solve this.
Click to expand...
Click to collapse
The profiles definitely do not work on the SF. The app doesn't really get along well with any of the Galaxy S phones. I run mine at 800 max, 100 min and on conservative. It brings it down to around 100 mhz when sleeping, and back up to 400 or 800 when using it. Don't enable any profiles, as it will cause your phone to freeze when the screen goes off.
There are two things you can use SetCPU to change/edit that I have found won't cause problems. You can change the min/max clock speed the phone will run at and you can change the cpu governor. I had issues with Set on Boot enabled, though Profiles are the biggest issue. The info tab is also useful for looking at information about the kernel and system.
Related
How can I make my battery last longer? I am using set cpu and various profiles to give me the best optimization I can, however my phone barely makes it 10 hours with light use *1hr web browsing, avid txting, light music listening via music on phone ~ 1 hr as well.* I'm not faulting the phone. I just want to know what can be done to get the most out of the stock battery as I see people getting results twice as good as mine and just done get what I'm doing wrong here.
Thanks for the help in advanced.
I have the exact same problem as you. Are you using unnamed with Enthropy's experience kernal as well? I'm about to flash cm7 to see if I can get better results.
Sent from my SAMSUNG-SGH-I777 using xda premium
xAnimal5 said:
I have the exact same problem as you. Are you using unnamed with Enthropy's experience kernal as well? I'm about to flash cm7 to see if I can get better results.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I used cm7 for a while now using UnNamed and cm gave marginally better battey life but
Just use the dang phone . You dont need to do anything special for great battery life. Try a factory reset if theres a problem though. Im rooted on cog beta 4 getting amazing battery life. I talked my mom imto getting this phone over the new iphone and hers is completely stock and she knows nothing and doesnt close any apps and gets the same amazing battery life as i do.
Reset and use it. If you cant get through a day of heavy use the phone is defective.
Sent from my SAMSUNG-SGH-I777 using xda premium
roadrash7 said:
If you cant get through a day of heavy use the phone is defective.
Click to expand...
Click to collapse
+1....or you have wakelocks. Find BetterBatteryStats and CPUSpy. BetterBatteryStats will tell you if something is preventing the device from going into deep sleep. I like to use "wakelocks since unplugged." CPUSpy will tell you the amount of time your device spends in each frequency, including deep sleep. For this, you'll need to reset the timers each time you unplug the phone.
Its add easy as flashing cm.... I went 15 hours and still had 60% left. with OC. Nothing else special (aka no juice defender our set CPU). The only trick is deleting everything in the dcim folder (known medias bug ) you'll see 1% battery loss per hour, with fb and GV sync
Sent from my SGH-I777 using XDA App
Simba501 said:
+1....or you have wakelocks. Find BetterBatteryStats and CPUSpy. BetterBatteryStats will tell you if something is preventing the device from going into deep sleep. I like to use "wakelocks since unplugged." CPUSpy will tell you the amount of time your device spends in each frequency, including deep sleep. For this, you'll need to reset the timers each time you unplug the phone.
Click to expand...
Click to collapse
BBS sometimes misses wakelocks, for even more info, grab the contents of /proc/wakelocks and post them here.
my solution: keep a charger with you anywhere you go
I have a car charger, home charger and work charger (as do most people)
Thanks for all the replies. I'm sure there's go to be a work around for this
Not sure about a workaround. From everything I've seen, the max battery life is around six hours when the screen is on. Basically, if your screen has been on for 4-5 hours, it's time for a recharge.
Sent from my Galaxy S II using Tapatalk
arctia said:
Not sure about a workaround. From everything I've seen, the max battery life is around six hours when the screen is on. Basically, if your screen has been on for 4-5 hours, it's time for a recharge.
Sent from my Galaxy S II using Tapatalk
Click to expand...
Click to collapse
Well based on all I've read it seems like the battery is a mixed bag depending on the OC profiles, roms and kernels being used with the device.
Is it true that setting a screen off profile in set cpu will cause the device to not be able to enter a deep sleep mode and thus will kill the battery faster?
Sent from my SAMSUNG-SGH-I777 using xda premium
Alucardis666 said:
Well based on all I've read it seems like the battery is a mixed bag depending on the OC profiles, roms and kernels being used with the device.
Is it true that setting a screen off profile in set cpu will cause the device to not be able to enter a deep sleep mode and thus will kill the battery faster?
Click to expand...
Click to collapse
Not true. It is true, however, that on stock kernels and ones without the "sleep of death" fix, setting a screen off profile with a clock limit lower than 800 MHz can cause "sleep of death" issues. Right now I think only my kernel and the Cyanogenmod kernel have the SoD fix.
Entropy512 said:
Not true. It is true, however, that on stock kernels and ones without the "sleep of death" fix, setting a screen off profile with a clock limit lower than 800 MHz can cause "sleep of death" issues. Right now I think only my kernel and the Cyanogenmod kernel have the SoD fix.
Click to expand...
Click to collapse
Thanks for clearing that up
I'll post here as I don't have enough posts for the development forum yet.
I'm running Entropy's 16th exp kernal, and Cog4 and I noticed my battery draining far too fast, CPUSpy then showed that the phone simply isn't entering deep sleep. I had previously been undervolting with Voltage Control but I uninstalled the program just to be safe, still not deep sleeping. I also uninstalled Widgetlocker, and I don't think I have any apps that would cause infinite wakelock. What are some possible causes of this issue? Just so I have an idea where I should be changing things.
UPDATE: Reflashing the kernal fixed the problem for a while but then I reinstalled voltage control and now I seem to have it again. Uninstalling and reflashing again however, did not fix the problem. I am utterly confused
On another subject, has anyone actually noticed better battery life after undervolting?
Freaking SWEET! My battery lasted 33 hours and 13 minutes! I've only owned the phone for 3 days now and this is off of teh very 1st FULL charge! Usage was between light & moderate. Data sync on, Wifi On, GPS OFF, BT OFF, FB Data Sync OFF, Capacitative buttons set to light up only in the dark & NO haptic touchback...mmm, can't remember what else I tweaked at the moment but I think that's fantastic battery life! I'm upgrading from a G1 that couldn't last more than 17 hours when it was on standby ONLY with maybe 2 phonecalls and less than 20 text messages. I usually only averaged 6-8 hours and with SIMILAR usage in the last couple of days, I've been able to get 33+ HOURS? ^_^ <-- I'm very, very happy so far! This is on a stock root - NO custom ROM for me at the moment...I'm actually digging TouchWiz 4.0 which I thought I was going to hate when I played with the previous version of TW on the T-Mo Vibrant. (yes, my G1 was running CM 7.1 and battery life still sucked and I went through 2 different aftermarket batteries w/o any luck!)
Don't know what the voodoo in the programming is with this bad boy, but I think Sammy did a nice job this time!
The best thing you can do is having "Autostart" to prevent App to start automatically. I saved 25-30% on my SGS 1 and the same on my SGS 2 (i777). My son on the I9000 SGS 2 saved also 30%.
poker_rick said:
The best thing you can do is having "Autostart" to prevent App to start automatically. I saved 25-30% on my SGS 1 and the same on my SGS 2 (i777). My son on the I9000 SGS 2 saved also 30%.
Click to expand...
Click to collapse
Thanks for the tip
selfassembled said:
I'll post here as I don't have enough posts for the development forum yet.
I'm running Entropy's 16th exp kernal, and Cog4 and I noticed my battery draining far too fast, CPUSpy then showed that the phone simply isn't entering deep sleep. I had previously been undervolting with Voltage Control but I uninstalled the program just to be safe, still not deep sleeping. I also uninstalled Widgetlocker, and I don't think I have any apps that would cause infinite wakelock. What are some possible causes of this issue? Just so I have an idea where I should be changing things.
UPDATE: Reflashing the kernal fixed the problem for a while but then I reinstalled voltage control and now I seem to have it again. Uninstalling and reflashing again however, did not fix the problem. I am utterly confused
On another subject, has anyone actually noticed better battery life after undervolting?
Click to expand...
Click to collapse
Check for wakelocks in BetterBatteryStats, and if that doesn't find anything, do the following in an Android Terminal Emulator shell:
Code:
cat /proc/wakelocks > /sdcard/wakelocks.txt
or better, using ADB (Google it and if you're on Windows, Droid Explorer)
Code:
adb shell cat /proc/wakelocks > wakelocks.txt
Then post wakelocks.txt here
All the apps,camera n everything works on that rom? ??? I installed cm7 bt now stock it cuz some apps and camera app didn't work.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
It's very frustrating, ESPECIALLY when you're trying to show people how cool your phone is ;-)
Sent from my GT-I9100 using xda premium
Well, you could download an app from the market which prevents deep sleep.. Forgot the name..
Sent from my GT-I9100 using xda premium
Yep but that will kill the juice drastically. I don't know whatever this Deep Sleep state is, all I know is that it does save a lot of juice and I hate it
In ICS I hope this should be fixed, without dramatic drain of battery of course.
Deep Sleep? My a$$.
ithehappy said:
Yep but that will kill the juice drastically. I don't know whatever this Deep Sleep state is, all I know is that it does save a lot of juice and I hate it
In ICS I hope this should be fixed, without dramatic drain of battery of course.
Deep Sleep? My a$$.
Click to expand...
Click to collapse
As always, spreading misinformation without knowing what you're talking about, eh?
Anyway @OP: the phone is limited by the hardware when the SoC is being resumed, the processor and buses are being re-initialized and going through a lot of routines, and also because apparently the radio is connected as a internal USB device to the system and it takes a lot of time, of around 500 to 600ms depending on the phone which you simply cannot avoid.
I've seen that undervolting too much or underclocking too low will additionally increase the resume time above that, so make sure that doesn't affect you if you are using it. Other than that, there's nothing that can be done and it won't be fixed anytime soon, if it's even fixable.
rickytenzer said:
It's very frustrating, ESPECIALLY when you're trying to show people how cool your phone is ;-)
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Here's a thought. Press the button two seconds before you decide to show it off.
'Problem' solved. Battery saved.
What exactly is deep sleep? Is the CPU running at all?
Sent from my GT-I9100 using xda premium
Mine jumps out of deep sleep very quickly? Faster than any other phone ive seen, its almost instantly at the lock screen?
I am no my second GS2 and the issue persists.
Issue:
When charging overnight, the battery gets extremely hot. So much it warps the sim card. The first phone overheated until it died. Last night the second phone overheated until the warning message “charging paused due to temp” came up. I do use a CPU intensive app that uploads files to my server when plugged in. (so it doesn’t drain the battery). I have used all these apps on my old captivate with no issues with overheating.
I have tried Unnamed 2.2.1 and ICSreweD 1.6.1 roms, but the battery still overheats. Unless this might be a faulty batch from the store, what areas should I look into? At the end of the day, I would really like to continue to allow the app to run while charging. Especially since I have used it with less powerful phones prior. I have read others have this same issue with the GS2 but no solutions as of yet. Is there a different ATT phone that does not have this issue?
Silly question, but I know many who do this...
Do you place your phone under your pillow overnight while charging?
When charging and running a app that requires high cpu usage will overheat the battery. So close it at night while charging.
Damn warping the card. **** that's bad.
One time at football camp i put my shoulder pads in my ass
If you need to keep the app running while plugged in all night, what about using a plugged in profile in set CPU to throttle to 800 mhz Max or something...
Sent from my SGH-I777 using XDA App
dandrumheller said:
If you need to keep the app running while plugged in all night, what about using a plugged in profile in set CPU to throttle to 800 mhz Max or something...
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Is there a specific app you recommend? Also, is there an app to limit the cpu useage of a service/app?
quy said:
Is there a specific app you recommend? Also, is there an app to limit the cpu useage of a service/app?
Click to expand...
Click to collapse
Set it with setcpu or tasker. It's likely running at 1200 mhz all night right now. (assuming you don't OC). Try throttling it down to 500 or 800 mhz, it should help. Not sure if there's anything that limits specific apps though.
Sent from my SGH-I777 using Tapatalk
Try the lulzactive CPU Governor.
Sets max CPU clock to 200mHz while phones asleep.
Also great for battery life
twiggums said:
Set it with setcpu or tasker.
Click to expand...
Click to collapse
If you absolutely have to leave your phone performing such intensive tasks all night, this is what I would try.
As twiggums said, it is probably running at 1200 all night and just melting itself. Unlike most computers, everything in our phones is passively cooled. Something else you might try is removing the battery cover (and any phone case) and placing a fan blowing directly on it. I know that is extreme, but so is what is happening to your phone.
Hope this helps.
I have also experienced this and it's really annoying. I couldn't love a human child as much as I love this phone but the overheating is not cool. I was using my phone to navigate while charging and once it got so hot that it locked up and another time it paused the charging due to thermal issues.
Sent from my SGH-I777 using XDA App
MonFrayr said:
Something else you might try is removing the battery cover and placing a fan blowing directly on it. I know that is extreme, but so is what is happening to your phone.
Hope this helps.
Click to expand...
Click to collapse
I had to do that sometimes when downloading some big files and tethering. Lol
Since my PC is caseless it wasn't that hard pointing a 120mm fan to it.
And yes it did work.
DJSLINKARD said:
I have also experienced this and it's really annoying. I couldn't love a human child as much as I love this phone but the overheating is not cool. I was using my phone to navigate while charging and once it got so hot that it locked up and another time it paused the charging due to thermal issues.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
IIRC entropy mentioned some time ago that he throttles CPU to 800 mhz when using nav and charging...keeps it cooler and allows for slight charge rather than drain...
Sent from my SGH-I777 using XDA App
Yeah I'd suggest possibly throttling the CPU. I charge my phone while driving and stream Pandora and use navigation. I've got mine set to Max out at 500 while screen off and it works fine.
Ideally our phones should be able to handle sustained 1200 mhz. But then when you add a case and the heat generated while charging I guess it's too much for some. Guess it's the price we pay to have a beast of a CPU
Sent from my SGH-I777 using Tapatalk
thanks for the tips on throttling the cpu. i had thought about that and will probably do it but i still thinks its really lame that we have to do this. i dont even have a case on my phone. what are people who arent rooted and cant underclock their cpus supposed to do? oh well i guess
I have started to notice this on my phone. it happens when I'm in the car only though. Here's the situation.
It seems anytime I run Navigation my phone cranks up in heat to the point that I can't touch it. Is this a ROM/Kernel issue, or a problem in the phone itself?
stalked_r/t said:
I have started to notice this on my phone. it happens when I'm in the car only though. Here's the situation.
It seems anytime I run Navigation my phone cranks up in heat to the point that I can't touch it. Is this a ROM/Kernel issue, or a problem in the phone itself?
Click to expand...
Click to collapse
Well if your sig is correct and you're running at 1600 MHZ, I'd say that's probably why. Running at that speed for prolonged periods is likely to generate some heat.
twiggums said:
Well if your sig is correct and you're running at 1600 MHZ, I'd say that's probably why. Running at that speed for prolonged periods is likely to generate some heat.
Click to expand...
Click to collapse
I run Set CPU and my sig isn't correct. Well, the 1600 mhz isn't at least. I have it capped at 1000. It's just odd that I can multi task any number of applications without a problem. I use navigation and instantly, the only application I can use is that one. Running Pandora or the phone or the phone interrupts pandora or the phone interrupts navigation and I get this error and the screen gets untouchable.
stalked_r/t said:
I run Set CPU and my sig isn't correct. Well, the 1600 mhz isn't at least. I have it capped at 1000. It's just odd that I can multi task any number of applications without a problem. I use navigation and instantly, the only application I can use is that one. Running Pandora or the phone or the phone interrupts pandora or the phone interrupts navigation and I get this error and the screen gets untouchable.
Click to expand...
Click to collapse
Hmm possibly reflash your ROM. I can run nav and Pandora fine, and my phone limits my CPU to 500mhz while screen is off. Or at least try reinstallin maps/nav, sounds like its gobbling up way too much CPU for some reason.
twiggums said:
Hmm possibly reflash your ROM. I can run nav and Pandora fine, and my phone limits my CPU to 500mhz while screen is off. Or at least try reinstallin maps/nav, sounds like its gobbling up way too much CPU for some reason.
Click to expand...
Click to collapse
I told Pandora to not turn off the screen. I would think that Nav would do that natively or else it would negate the purpose of it. I wonder if maybe telling Pandora to keep the screen on and Nav keeping it on natively makes it think really hard and heat up.
stalked_r/t said:
I told Pandora to not turn off the screen. I would think that Nav would do that natively or else it would negate the purpose of it. I wonder if maybe telling Pandora to keep the screen on and Nav keeping it on natively makes it think really hard and heat up.
Click to expand...
Click to collapse
That's probably why
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Lately I've been having major issues with my processor getting extremely hot. It only warms up when the screen is on. Normally I wouldn't care but it gets hot enough I can barely touch the screen (over 100° F) and results in major battery drain (battery drain doesn't bother me because in using it, but it still seems too high). Does anyone know a few tips or tricks to keep the temp down? Currently I'm running on AOKP and have the default kernel but I also experience the issue with siyah kernel as well. Thanks I will advance B-)
Sent from my SGH-I777 using xda app-developers app
More likely than not you probably have some kind of rogue app running in the background, but without any more information, that's all I can tell you. Try installing BetterBatteryStats for wakelocks, or tell us what apps you have installed, or a screenshot of what's draining your battery.
Did u full wipe before installing the Rom? If not, there's no reason to post this issue until u have. If u already have, then as stated above,u need to find which app is causing the problem. Definitely not a Rom problem, just an fyi for others who may read this.
Sent from my SGH-I777 using Tapatalk 2
I also have been having problems with my cpu overheating. And my screen does not want to turn back on and phone reboots into safe mode. And will randomly turn on and off. Any one has any ideal what could be causing it, and is it bad for your phone to go into safe mode.
Sent from my SAMSUNG-SGH-I777 using xda premium
No it's not bad for your phone to go into safe mode, but once again, please provide more details!
It's definitely not because I did not wipe... However I will check out better battery stats I didn't think it would be an app causing the over heating because as I said it only occurs when the screen is on. I was thinking it would be more kernel related (voltage levels or governor related). Thanks tho I'll report back with battery stats
Sent from my SGH-I777 using xda app-developers app
I thought getting hot with AOKP was just par for the course, like the weird keyboard bug.
Mine gets pretty hot all the time, with normal use. I full wipe each update, most recently when installing the update on 7/3. I use Fluxxi kernel as is with no oc or voltage changes. Its hot while using wifi or data, and battery life seems normal.
Over the last 13 hours I have 3% time above 800 MHz, 35 seconds of wake lock for network location.
Sent from my SGH-I777 using xda app-developers app
The Rez I'm using now is an Asurion replacement. Before, this thing was saving battery like a champ. Used to get a full 24 hours or more plus 2 hours screen on time.
Now it's just terrible. I'm 34% on battery after less than 5 hours off the charger with far less than an hour of screen on time.
I'm running Snuzzo's 2.2 funky kernel and Newt's One XxX 6.0.2 rom, S-OFF. CPU is tweaked, running dancedance governor and SIO. 386 MHz to 1 GHz (or whatever they exactly are) when in use. Various profiles are set to run lower, as ive always done.
I'd appreciatw the help, guys. Thanks.
Sent from my ADR6425LVW using xda app-developers app
check with gsam what drain the battery
Proz00 said:
check with gsam what drain the battery
Click to expand...
Click to collapse
Yes, what he said. I'm running Newt's with ExtraFunky 2c and don't have any problems. In the past when my battery life suddenly nose dived, it turned out to be some app that decided to keep wakelock for some unknown reason. Check recently updated apps.
Yeah probably an app or service running in the background.
Turn off GPS and blue tooth when not in use
Use WiFi when you can
Turn off Google Now
Turn off location history and location reporting in Google maps settings
Make sure you have no widgets constantly refreshing
Increase the times between sync for Gmail, Facebook et al
Try running a more conservative cpu governor supported by your kernel, such as Wheatley or Intellidemand.
Sent from my Rezound using Tapatalk 2
I don't really use Bluetooth that often and keep it off, and gps is always off. And got rid of Google now for the regular Google search. Only the clock widget is running. Though, I should spacing sync times.
Uninstalling some apps seems to have helped for the most part (which makes sense, as I just recently restored a nand backup). But, it's still not as good as it was. I guess it's best to just keep tinkering at this point.
Thanks
Sent from my ADR6425LVW using xda app-developers app
Well for example, I use fancy widgets for my clock/weather. If you use a program like better battery stats (search xda for the free version), you will see fancy widgets causing the device to wake up more than almost anything else.
That's when you can do stuff like spacing out weather sync to 3 hours, prefer sync over wifi, and maybe even setting a default fixed location for your weather.
But with the kind of battery loss you described, something more than a widget is grabbing power. Make sure you are on auto brightness, btw.
I also use a program called system panel to see what all background services are running. For example, you would be surprised to see services for Google Talk, social apps, even some games running in the background. Then you can use titanium backup to freeze them or un install.
Sent from my Rezound using Tapatalk 2
I've been using Gsam, but what I see use up more resources than anything is the kernel I typically uninstall anything I do not use. Stuff sitting higher up are things like the Kernel, Android System, Camera, Wallpaper Lockscreen and Android Core Apps. That's everything that goes 1% or higher. Everything is under 10%.
And, surprisingly, wake times aren't that high. Typically, screen on time is about equal to the awake time, so all seems well on that end.
I think removing and re-installing apps that were using excessive amounts of energy has probably done the trick, though.
What tuner app do you use?
You might just try running Intellidemand with no underclocking and see how that works for you.
The problem with underclocking is, if you don't give an app enough juice it will take longer to complete a task and the cpu will run longer.
Look closely at your deep sleep times. I barely lose any battery overnight bc I run Wheatley underclocked to 1242 for screen off only.
Glad removing the apps helped some, those buggers.
Sent from my Rezound using Tapatalk 2
I think I'm in a better area now.
I'm using setCPU (always has been reliable for me in the past). I'm running 385-1512 with dancedance and noop. I think this is where I need to be. It's kind I'd feeling like it used to again.
I'm going to try Funky 2.3 now.
Sent from my ADR6425LVW using xda app-developers app
Screen On time is not that great for 8 pct battery left. But it could have been bc you were listening to music for part of that time. Otherwise your screen shot looks normal, good total life.
Sent from my Rezound using Tapatalk 2
I'm getting pretty crazy battery reports using the newest funky kernel for cm10. I could have the phone off charger for hours and it still reports 100% battery. Granted I wasn't using the phone that much, if at all,but to still see 100% battery after that long even idling is weird. Using dancrdance governer with deadline scheduler. It doesn't take much tho to get my battery draining. After about 4-6 hours of use (playing music, games, looking on forums and such) I'm down to about 25% or less. Any suggestions?
Sent from my Rezound using Tapatalk 2
Oooooh, yes. I listen to a lot of music during the day. That day, though, was while listening to less than usual. My deal is going screen on and watching the battery drain 2-4 percent in a 2-5 minute time frame. I understand that the screen is heavy on the battery, but it's never really been like this before. I'm sure I'll have this figured out sometime soon.
What kernel are you on? You might look into undervolting. For example, funky kernel is undervolted by 50 by default. Ermahgerd isn't undervolted by default but supports it. You can safely go down as many as 75-100 without stability issues. It does dramatically reduce battery drain.
Sent from my Rezound using Tapatalk 2
I'm using the Tonked world edition with the kernel that came with it and I get great battery life. About 34 hours with 6+ hours of talk time and just under 4 hours of screen time with Bluetooth wifi and mobile data (4g turned off) always on. And almost 3 days with light use. Does help to have the HTC extended battery.
Sent from my SCH-I815 using XDA Premium HD app
czach5932 said:
I'm using the Tonked world edition with the kernel that came with it and I get great battery life.
Does help to have the HTC extended battery.
Sent from my SCH-I815 using XDA Premium HD app
Click to expand...
Click to collapse
It's been a while since I last used 3.6, but why not. And yeah, I bet it does. They're just getting harder to find and more expensive.
Sent from my ADR6425LVW using xda app-developers app
brenuga said:
What kernel are you on?
Click to expand...
Click to collapse
I'm on funky 2.3. I understand that underclocking can help a lot, though.
Sent from my ADR6425LVW using xda app-developers app
What do you guys think about this battery stat pic? Is this good? I've been running Bluetooth while streaming Pandora almost non stop at work. Stats are from about 11:30am to now, at 4:15pm here. Phone on time is different because I was also messing with settings that required me to reboot a few times.
Sent from my Rezound using Tapatalk 2
I am quoting Neo, but here are extreme settings for maximum battery life.
A little something I suggested to someone earlier on the fly:
*Don't use auto brightness and keep your screen brightness low but not too low that causes you to strain.
*Undervolt all frequencies by -50mv using kernel tuner.
*Underclock the rom to 1,080mhz
*Change I/O scheduler to noop
*Change governor to Lionheart (if you have it) or DanceDance.
*Disable all haptic feedback including soft keys and keyboard
*Disable data or account sync overnight (unless you plug your phone into a charger over night)
*Enable 16-bit transparency
*Disable dithering
*Disable HW overlays
*Disable all animations
*Ensure GPS, WiFi, and Bluetooth are turned off when not in use
*Use WiFi where available instead of 4G
*Disable weather refreshing and leave it to manual refresh
*Disable wallpaper scrolling and animations if possible in the launcher
That's all I can think of at the moment.
-Neo
Sent from my Rezound using xda premium
Again, all the credit goes to Neo here, I have used these settings and they seem to help quite a bit
Since you have tested these settings provided by Neo, what is your battery life like? Better then what I have shown above?
Sent from my Rezound using Tapatalk 2
Drop your screen off profiles. They will hurt more than help. I already have max screen off cpu clock in place set to 432mhz.