Related
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.
Have been running unnamed 1.3.1 for about a week. Battery life is good, but it still drops pretty quickly while not being used. Cpuspy is reporting that the phone is spending over 30% of its time at 200mhz, and about 50% deep sleep. This includes my 4 hour work period when I barely even pick up my phone. Any ideas on a cause? I already deleted the Facebook App fyi. Thanks in advance.
I'd suggest installing BetterBatteryStats. You can get it on the Market or search here on XDA for a free version provided from the author.
Fully charge the phone and try not to use it at all for a few hours or more if possible. You can then go back into BBS and it will show you all the Wakelocks and Partial Wakelocks that are running since you last charged it.
You can also set a Custom Ref. point and it will wipe out all history and start over if you want to simply do it midday but you have to keep it running in the background or else you'll lose the Custom Ref. point. Hope that makes sense. BBS is a GREAT program to help identify what's eating away at your battery during sleep.
Also, keep in mind that anytime you have it plugged in and charging, it will never go into deep sleep. It will always be showing as time spent at 200Mhz instead.
.
I recommend upgrading to unnamed 1.3.2 and sirrah kernel 2.4.2 (whichever latest one is). I have and I get really great battery life. Tweaked kernels and stoophs FTW.
Thanks for the insight. Better battery stats is exactly the App I was looking for. Also, I have updated to 1.3.2, I tried siyah kernal for a bit, but I didn't notice a difference
Sent from my SAMSUNG-SGH-I777 using xda premium
Also, make sure to reset CPUSpy stats after removing it from the charger.
Charging inhibits deep sleep.
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
I recently took the dive and installed the Helly Bean build from the 23rd onto my Vibrant, and this thing rocks. I am amazed at how smooth the hardware runs with this new CM10 based build. It has run so well that I've decided not to bother with getting a new phone, just need to get a new battery.
That being said, I've been trying to push my old battery as far as it can go. As such I have tried two things that so far are not working:
1) I wanted to enable Deep Idle. After doing so, I've found that often when I turn off the screen, it will not come back. Only a long hold on the power button or battery removal will bring back the phone, albeit in a rebooted state.
2) Each time I select the lowest CPU frequency to be 100mhz, it gets reset back to 200mhz.
Any help / pointers would be greatly appreciated.
Cheers!
jm-dev said:
I recently took the dive and installed the Helly Bean build from the 23rd onto my Vibrant, and this thing rocks. I am amazed at how smooth the hardware runs with this new CM10 based build. It has run so well that I've decided not to bother with getting a new phone, just need to get a new battery.
That being said, I've been trying to push my old battery as far as it can go. As such I have tried two things that so far are not working:
1) I wanted to enable Deep Idle. After doing so, I've found that often when I turn off the screen, it will not come back. Only a long hold on the power button or battery removal will bring back the phone, albeit in a rebooted state.
2) Each time I select the lowest CPU frequency to be 100mhz, it gets reset back to 200mhz.
Any help / pointers would be greatly appreciated.
Cheers!
Click to expand...
Click to collapse
It looks like the default 100mhz and 200mhz mV settings were 950. I read in another thread its not recommended to go below 1000mV. Now the phone is not freezing when turning off the screen, but at the same time the idle stats aren't showing any deep sleep. Is there a way to check why the deep idle may not be occuring? Without this I can't be sure raising the mV setting will is a fix.
jm-dev said:
It looks like the default 100mhz and 200mhz mV settings were 950. I read in another thread its not recommended to go below 1000mV. Now the phone is not freezing when turning off the screen, but at the same time the idle stats aren't showing any deep sleep. Is there a way to check why the deep idle may not be occuring? Without this I can't be sure raising the mV setting will is a fix.
Click to expand...
Click to collapse
Good question. I've had almost the same experience and would like to know also.
You cannot set 100mhz on the kernel anyway, and deep idle causes the sleep of death, I recomment not to go that low cause it can be slower at times.
Sent from my SGH-T999 using xda app-developers app
iKoolkid said:
You cannot set 100mhz on the kernel anyway, and deep idle causes the sleep of death, I recomment not to go that low cause it can be slower at times.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
lol, that's a good name for it! So I'll take it this is a known issue? If so, is this specific to this kernel? Or is it a known issue with the vibrant in general?
jm-dev said:
lol, that's a good name for it! So I'll take it this is a known issue? If so, is this specific to this kernel? Or is it a known issue with the vibrant in general?
Click to expand...
Click to collapse
Sleep of death is a known issue, on kernel however it is only known when in deep idle.
Sent from my SGH-T999 using xda app-developers app
iKoolkid said:
Sleep of death is a known issue, on kernel however it is only known when in deep idle.
Click to expand...
Click to collapse
Darn. Well I only got 9 hours out of my battery today, but the battery is from june 2010 so I don't blame the build or the kernel. This battery is so used up I haven't had good battery life for months, even with the original stock firmware.
I was curious to see if I can get even more hours before buying a new battery with the deep idle but if no one has had it working then I guess its not reliable. Perhaps thats why these phones didn't have it enabled in the first place. At any rate, I'll be ordering a new battery soon.
Thanks for the help! If anyone has more to add feel free to, I'm all ears!
Well I'm on the 9/04 build (lazy, but haven't had issues.. am updating soon lol) I keep Deep Idle toggled on, and Devil Idle on Automatic and have not had any issues with not returning from Deep Sleep.
The Deep Idle stats show the phone is reaching Deep Idle. I've had the same setting over several builds, on the other /datadata setup and on this more current /datadata setup.
You keep deep idle on? Mine still goes into SOD with it on. We are running the same CPU settings and everything. Its weird how the same phone same settings run so different.
sent from the depths of helly bean
samsgun357 said:
You keep deep idle on? Mine still goes into SOD with it on. We are running the same CPU settings and everything. Its weird how the same phone same settings run so different.
sent from the depths of helly bean
Click to expand...
Click to collapse
If I use devil idle and deep idle I get SOD. I normally just turn off devil idle and keep deep on. Which one would be better of the two?
samsgun357 said:
You keep deep idle on? Mine still goes into SOD with it on. We are running the same CPU settings and everything. Its weird how the same phone same settings run so different.
sent from the depths of helly bean
Click to expand...
Click to collapse
Yeah. Back when I first started using HB, I notices that I couldn't reach deep idle. I tried toggling deep idle, and it started to deep idle then. After talking to you and know it SODs for you I always expected it, but that was never the case. It is weird how things aren't universal for our devices in that respect.
ToStymiedBoar said:
If I use devil idle and deep idle I get SOD. I normally just turn off devil idle and keep deep on. Which one would be better of the two?
Click to expand...
Click to collapse
If you can run deep idle without SOD, then use it.
sent from the depths of helly bean
---------- Post added at 03:42 PM ---------- Previous post was at 03:06 PM ----------
I just disabled devil idle and enabled deep idle then rebooted. As expected, SOD so back to devil idle for me.
sent from the depths of helly bean
samsgun357 said:
If you can run deep idle without SOD, then use it.
sent from the depths of helly bean
---------- Post added at 03:42 PM ---------- Previous post was at 03:06 PM ----------
I just disabled devil idle and enabled deep idle then rebooted. As expected, SOD so back to devil idle for me.
sent from the depths of helly bean
Click to expand...
Click to collapse
It's the opposite for me. If I run devil idle I get SOD. So, I took this opportunity to flash up to 0925. Do suggest calibrating battery even staying on the same ROM?
I do suggest calibrating, I have always done it even when updating the same ROM.
sent from the depths of helly bean
I have Devil Idle, and Deep idle as "automatic" and "enabled" respectively. (smartassv2 governer and SIO).
I AM hitting Deep Idle (TOP=ON)
AM NOT hitting DEEP IDLE(TOP=OFF) via Devil Kernal Config
I am not hitting "DEEP SLEEP" via CPU_SPY.
Is this good or bad?
And I can't seem to find what the difference is between
Deep Idle (TOP=ON)
Deep Idle (TOP=OFF)
Deep Sleep
hellybean 1001
I am with you Bobo.. same settings. I have ondemand governor but no other changes.
I too reach top=on and not top=off..
Its my understanding that in order to reach top=off the Bluetooth has to be killed and wifi killed. Never messed with it really. Your reaching Deep Sleep IMO, just not the Deepest sleep possible.. If that makes sense.
Not sure if top=off is possible yet. May not be achievable until kernel progresses a little more.
The problem where you can't set 100mHz is due to the way the system locks the minimum frequency while the gpu is active because of something with the bus speed changing when below 200. This ideally should override, but not change, the minimum frequency set by the user.
This was fixed by mkasick by using a dvfs lock in the epicmtd kernel. We've merged that change into the stock kernel so hopefully that's fixed now in stock.
Sent from my Galaxy Nexus using xda premium
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.