Related
Couldn't really see any discussion on this yet, and personally it's in a location on the forum that I rarely visit but I've found an overclock tool that is slowly becoming very good indeed for our processors. Link to thread is here. I'm soo far up from 528Mhz to 748Mhz (been stable for the past 6 hours no problem). Just make sure to follow the thread (instructions are linked to ensure overclock remains applied through scripts and 3rd party apps). Should take no longer than 30mins for a well versed user to set up. Please don't try this if you haven't got a clue what you are doing as there is soo much scope for error and dead phones! You may also need to customise any scripts to your specific phone/software build. CDMA phones as usual are different from what I've heard. But anyway good luck, I'm gonna keep trying to push the Mhz up (aiming for 850Mhz ).
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
It's actually remained pretty cool, and when it's in my pocket it's only running at stock clocks anyway. Only when I'm using it does it get to the full 748Mhz. Running wifi router and charger and temps are not noticeably hotter than usual...
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
recommendations: Download v1, not v2. ESP if you dont know what you're doing. Then download the zip im attaching, there's 2 mortscripts in there and a registry addition, THESE MUST BE IN THE STORAGE CARD ROOT. use the regisitry addition FIRST (just associate w/e regedit software you use, then run the .reg file in total commander), then go back to total commander, edit the .mscr "Toggle_boost" and adjust the value boost = "x" to whatever value you want the phone to OC at, eg boost = 41 is 787mhz which is stable for me, test yours out.
THEN, open and install rhodiumkbdcontrol (attached), reboot, go to settings>system>keyboard config> add key
1st pick which key you want to be the OC boost swtich, I have it mapped to my PTT button. click the plus sign, drop down menu, run program, then highlight "run program" in the list then click "..." then type in
Program: \windows\mortscript.exe
Arguments: "\storage card\toggle_boost.mscr"
This time you wanna use the power key.
same general instructions except
Program: \windows\mortscript.exe
Arguments: "\storage card\boost_off.mscr"
then plus sign again, drop down menu, default key action, and click extended emulation. THEN hit update config. should work like a charm, also autoover clocks to 610, the boost button with send you up the w/e the boost = "x" is set to, and then back again, most find 710mhz to be the stable point, and feel free to ask questions
sorry, heres the zips
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Edit:
I just read threw the above links and guides and was wondering if there is a more automated way of setting this up rather than having to link it to a button press. I'm guessing this has not been figured out yet (or the guides would have mention of it ). Just curious.
dantegl36 said:
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Click to expand...
Click to collapse
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Check it!
Outlaw78a said:
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
Click to expand...
Click to collapse
I have used this, NRG also does. I have NEVER had any problems and mine is as high as 787 as long as I'm running it which is constantly.
XITruthiX said:
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
Click to expand...
Click to collapse
100% agreed. Been running at the highest speeds with NO problems, no batt drain, no heat probs, nothing.
XERO_Racer said:
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
Click to expand...
Click to collapse
Not unless you are having excessive heat problems. Since there are basically no people reporting these problems, I wouldn't worry.
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Once again as stated earlier, 100% agreed.
Do I have to keep plugged in?
miked79928 said:
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Click to expand...
Click to collapse
I thank you for this, but I'm not sure how to implement it. I have installed Mortscript, I've copied the code into a file I called overclock.mscr and modified the code reflect the reg values on my Tilt 2. and I've placed the script on the root on my SD card. I've installed MSM7kCpuSpeed on to my SD card. How do I make the script run automatically?
Thank you!
I take no responsibility for w/e happens to your phone with this advice.
Try putting a pointer in your start up to the over clocking script. Its highly unstable and could brick your phone or require a hard reset... thats why I do it with a toggle switch, i dont mind manually applying the OC with a hard key knowing its safe, esp because the situations where I actually NEED 787mhz are less common than needing to just wake the phone to answer a call or make a txt message.
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
dirtypiratehooker said:
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
Click to expand...
Click to collapse
Just a note, I'm not sure the insurance would cover burning a custom ROM into the phone, or overclocking the CPU. And if the chip is fried you can't burn the stock ROM back in. But then, they probably couldn't figure out it was updated without in stalling a new CPU. Umm, it would probably work.
Would a .cab for this ever be conceivable?
At this point, we have finally got a script that will work for most Rhodiums, Topaz (Diamond 2), and a few guys with other phones seem to be having good luck.
The device has to have Mortscript installed, and nettrip's MSM7 v2.
It is a single script solution that requires no pre checks in the registry, no key/button assignment, and you can change the speed settings from the script instead of the registry.
It throttles the OC up and down for calls, lock, and sleep, to avoid freezing on wake up and in a call. Some problems that still need to worked out by nettrip in the script. I don't envy him the work as the script(s) were bad enough. Four of us have hit that original script (by jpc) from about page 13.
You copy the script to the SD or the device root, create a shortcut to the file, copy the shortcut to Windows\Startup directory, reset/reboot the device and you are off.
You can use the MSM7 app to read the OC, but you should make sure to exit the app before sleep, lock, or power off, as it will error on reboot if left open.
To be honest, you never have to open the MSM7 app, as the script controls it in the background.
I believe the script is set for a low over clock. 691. My experience has been a 710 average, but a lot get a stable OC at 750+. I am running 748 and I think I will stop there. A 200MHz overclock will just have to do.The phone does not get hot, though with intense use, it does get warmer. Never warmer than when the battery is charging, tho.
I am running the nrg Sense Reference ROM, 23xxx based on Sense 2.5. I added the CHT 1.8x and the editor to save a few MHz, no biggy.
The overclock allows the Sense to work MUCH smoother, actually noticeable as even the weather animation is smooth.
And all the vid players seem to work better.
I have noticed NO extra battery drain than usual.
The script is only a stop gap measure until nettrip finishes his app, but it does work well with little effort. WAAAAY better now than even last week.
However, use the script at your own risk, as you can get too Medieval on the OC. Some guys are running 800+, more nerve than I have.
Anyway, if interested in the script or want to read some more about the app, you can start here
http://forum.xda-developers.com/showthread.php?t=725290&page=89
post #882 has the script.
Plenty of instructions on how to use (and make changes to the settings) in the last 30-40 pages.
Sorry if this is already explained, but can someone tell me in simple details how to keep my overclock at 729mhz even after screen lock or sleep mode? I've tried to follow previous posts but it keeps reverting back to 528mhz after locking and sleep.
Ok so this seems legitamite,everyones checking in with no problems.
other than the increased risk factor that always accompanys speed,
it seems our ppc's cpu was underclocked beforehand ?
i will try this and see if i get a gpu boost as well.
but ivr already experienced my phone overheating to the point
of shutting itself down,and the god-damned orange light is permenantly on...
Hey guys. sorry if theres a thread like this already. im new to this forum and searched for nearly 3 hours but didnt find much of what i was looking for.
i have a t-mobile 1024 Hd2 with a custom windows mobile ROM LEO_firestorm_v7.4.23135-FX
and a android ROM (installed to SD)
mattcfroyo 1.5
and i also have setcpu installed. the phone(and both rom's) work great. the only issue is the battery life. my phone even when i would barely use it would maybe make it about 12 hours on a charge(doing very little web browsing, turning wifi/ bluetooth off when not in use, brightness around 30%). what have you guys done to get better battery life? should i install different ROMS? is there a WM rom that is basically barebones so it takes less resources and improves battery life? i dont care what the WM side looks like as i only want to use android anyways. i want to use Android as my main OS and how should i setup setcpu? really sorry if this thread is a repeat. if there is another asking exactly what i am please give me a link. im very new to this, so guides are very appreciated aswell.
i did find the thread "HOW TO: Wipe Battery stats to improve battery life" and ill be trying that. what i mainly want to know is how to guys have your roms and setcpu setup.
links to better roms/guides etc. are very appreciated. thanks allot guys.
any rom needs to be compatible with the 1024 hd2 though.
Hi and welcome to XDA,
I've my phone set up as shown in my signature. I don't use bluetooth, basically have no calls, some texts and fairly heavy browsing (web, tapatalk pro, newsrob pro) when I'm on the train. I have a 3mA-5mA drainage in standby. My phone will last 10-12 hours on a charge, after which I have to plug it in. I'm kinda used to it now, but last week I thought I'd give UltimateJuice a try. My phone lasted a little over 17hrs, though I probably used it a bit less intensive that day. The days after I got about 14-15 hours a day with regular use.
I have JuiceDefender installed, which also manages cpu speed. Basically it allows the cpu up to 614 Mhz when the phone is sleeping and 1190 Mhz when awake. Screen brightness is set to 15% currently. When I'm at home, JuiceDefender switches WiFi on automatically, when I'm outside it connects to 3G every 15 minute during 1 minute (adjustable).
Drainage is still somewhat heavier compared to WM, but I can live with it.
Sincerely,
Mac
looks like i found a solution today. last night i underclocked my cpu to 700mhz and i have not seen any performance difference and the battery is lasting allot longer. i have been using it moderately and the battery has gone down 8% in 3 hours of use which is already allot better than before.
i checked my battery power and after it was fully charged it showed 4.2mah so i knew that wasnt the problem. does anybody have the problem that their contacts(in android) are removed if they soft reset their phone? and if so does saving contacts to sim work to fix it? thanks
adrenalinechild said:
does anybody have the problem that their contacts(in android) are removed if they soft reset their phone? and if so does saving contacts to sim work to fix it? thanks
Click to expand...
Click to collapse
No, that doesn't sound familiar. Are you syncing your contacts with your Google account?
Sincerely,
Mac
Sent from my reborn HD2 using Tapatalk Pro
no i just manually put in a few to my phone. does saving contacts to sim work in android on the hd2?
adrenalinechild said:
no i just manually put in a few to my phone. does saving contacts to sim work in android on the hd2?
Click to expand...
Click to collapse
yes it does, but why don't you have all your contacts sync with google?
roloracer said:
yes it does, but why don't you have all your contacts sync with google?
Click to expand...
Click to collapse
backup everything before you do this though. it's known to cause crash at startup and you won't be able to use your android again.
im having a problem with my hd2. i made a call today. and all the incoming voice sounded like a decepticon. kinda cool but definately not useful to actually talking to a person. what should i do to fix this? is it the rom i am using?
adrenalinechild said:
im having a problem with my hd2. i made a call today. and all the incoming voice sounded like a decepticon. kinda cool but definately not useful to actually talking to a person. what should i do to fix this? is it the rom i am using?
Click to expand...
Click to collapse
it's a known issue. read the faq.
Last Edited 4/25/2011 @ 1:00PM EST
*** I’ve updated on my previous post on HTC EVO Best Practices for Battery Management that I’ve put together. There were certain steps that were fine tuned and others that were either added or removed. I just wanted to share with everyone in order to save the time I spent researching, applying and testing these fixes on my EVO and a couple of other EVO’s I’ve tested. ***
*** Just an FYI, I didn’t write any of the apps/codes listed below. I just spent a lot of hours researching methods to improve the battery life on my EVO on several different sites. I’ve linked the sites where I got the information and giving ALL credit to the original posters. If I missed any names and If there are anybody that needs credit to be added for any of the steps below, please let me know and I’ll add them right away. ***
*** These steps have been ONLY tested to work on AOSP ROMs like Destroyer v2, CyanogenMod and MIUI. ***
*** Finally, this is meant to just be a guide for Best Practices for Battery Management. I’ve tested these steps on several HTC EVO’s which had Destroyer v2, CyanogenMod 7 or MIUI and had no issues. If you decide to try these steps in the guide, I take no responsibility for any items that might go wrong with your phones . ***
All that said, let’s get started. I’m looking to keep this as a “Living Document”, so I will continue to update and edit this original post with any new info that is shared by others or get discovered over the next few weeks. For anyone that’s new to rooting and flashing ROMS, I’ve added the first two steps. Most 99% of everyone else on this site, please move onto Step 3.
Step One, Root Your Phone.
Easiest way to do that is to go to http://unrevoked.com/ and select your phone. Then select Unrevoked3 “Painless root and flash”. If you’re a MAC or Linux user, just download the software. If you’re on a Windows computer, download and install the HBoot Drivers by clicking on “More Info?” Once you launch the software, just follow the onscreen prompts and your phone should be rooted within 5-10 minutes.
Step Two, Backup and then Flash a ROM.
Easiest way to do that, is after you’ve rooted the phone, go to the market and download the app ROM Manager by ClockworkMod. Once you access the app, it's very important to first backup the ROM that came prepackaged with your phone in case you ever need to flash back to it. Click on "Backup Current ROM", I even saved a copy of that backup on my computer incase I need to copy it back to my phone.
To flash a new ROM, click on click on “Download ROM” and you’ll be able to install CyanogenMod 7.0.0 Stable Release. Or you can go to their site and download the ROM from them at http://www.cyanogenmod.com/ Another ROM that this works well with the steps below is MIUI and you can download that ROM from http://www.miuiandroid.com/
Step Three, Upgrade the Kernel.
I’ve found that every person’s phones are setup differently. Also different kernels work better on certain phones then others. The two best kernels are SavagedZen and Tiamat. Personally, just my opinion, I got better performance from SavagedZen kernels, so that’s what I go in detail below. Although test for yourself, as Tiamat 3.3.7 has gotten great reviews also.
There are also different type of kernels as CFS, BFS or SBC and no-SBC. What are the differences?
SBC is Super Battery Charge. Basically, it enables a trickle charging effect on the charger. It fills the battery up to 100% so when you pull it off of the charger, it's absolutely full. The noSBC kernels use the stock battery driver and charge differently. Some users are not comfortable with SBC and prefer not to use it. They do not trust it and believe it may cause failure although there has been no evidence that it will actually do so. Again, this is a user preference and why both builds are created at this time.
As for CFS or BFS, they are schedulers. CFS is the default Android scheduler that all stock kernels use. Its called the Completely Fair Scheduler and schedules the CPU fairly. BFS, or Brain F*** Scheduler, gives the present task a higher priority and background tasks less CPU. Which one to use is more or less on the user.
Most people wouldn't notice any difference. In theory, watching videos, playing games, and listening to music should be smoother with BFS, because it emphasizes the foreground task. CFS should be better for running background tasks, because it gives equal priority to everything. And some peoples' phones don't play nicely with BFS, so CFS is generally the reliable fall-back option.
Above is just a summary, although if you want to read more in detail about kernels, I got all the info above from this link http://www.cs.unm.edu/~eschulte/data/bfs-v-cfs_groves-knockel-schulte.pdf
Finally, once you’ve installed CM7 or MIUI, next step is to upgrade the kernel to Savaged-Zen. Go to this link http://mirror.savaged-zen.com/ and download the kernel from April 7th named “SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB-signed.zip” and copy it to your SD card. Then turn off the EVO and turn it back on in recovery mode (Holding down the down volume button then then pressing power). Once ClockworkMod Recovery loads up, scroll down and select “Install zip from sdcard”, then scroll down and select “choose zip from sdcard”. After that, just scroll down to where you’ve saved the Savaged-Zen kernel and install it. Once the phone reboots, check to see if the kernel has been applied properly by going into Settings\System\About Phone (from MIUI menu) and then click on More Information. Kernel version should now have SavagedZen listed.
Step Four, Lower voltages on AOSP kernels.
–viperboy- had a great post on this topic, below is the link for his instructions http://forum.xda-developers.com/showthread.php?t=1028322 . I usually start off first by flashing the 50mV.zip and if it’s stable for a day or two, then I upgrade to 75mV.zip. On one EVO, I went up to 100mV and it started rebooting until I lowerd it back to 75mV. Haven’t had any issues with it since. On another EVO, I had to lower it from 75mV to 50mV to resolve freezing issues and haven’t had any issues with it since. Point is, you have to find the best voltage level that works best for your phones.
Step Five, change the Heap levels.
After updating the kernel and voltage levels, download VM Heap Tool from the Market. That tool will let you adjust the heap size on your phone, which Heap is the amount of memory each application can use. By default, your phone is set to 32m, which has issues with force closers of the launders and files. After you download the app, adjust the heap level to 40+. I've gone with 44m and haven't had any force closers, where before I would get 1 or 2 a day.
People running the latest build of MIUI release 1.4.22 Beta 7, stiffspliff changed the default MIUI Heap level to 64. So any MIUI users on the new release do not need to install\use this tool anymore.
Step Six, download BatteryCalibration app from the Market.
Useful tool especially if you like to keep switching\testing new ROMs on your phone. Calibration needs to be done after flashing a new ROM, since the program will remove the batterystats.bin system file. The OS generates a new clean batterystats file soon, thus any fake information from the previous ROM is removed.
Step Seven, manually setup the display settings.
When checking the Battery Settings\Battery Use, the Display is usually the biggest battery drain. To help offset this a little bit, go to Display Settings and turn automatic brightness off. Then manually setup the display at 25-30% brightness. Usually just take it down as far possible that you feel you’re comfortable seeing the screen properly.
Step Eight, condition the battery
Below are the steps to follow from a XDA member HipKat that have worked nicely to condition the battery.
1 - The "HTC Method w/10 Time Unplug"
Charge to full, unplug, turn off the phone, charge while off for another hour. Unplug, turn the phone on for 2 minutes, turn it off again, charge for another hour.
Unplug til the light goes off, plug back in til it turns green.
Do that 10 times.
Boot to Recovery, while plugged in. Clear battery stats, boot to system. And wait 2 mins, THEN unplug.
Also, I keep my GPS, mobile data and WiFi off unless I need it. You don't need either of those to make phone calls or texts.
Step Nine, what to AVOID
This step isn’t anything to install or update on your phone, it’s more meant for what type of apps to avoid.
First is Juice Defender, who with more research I’ve found could either help or drain your battery life. If you have JD on all day when you're not really using your phone much, in an area where your phone would normally be searching for data all day, wasting power, the battery savings are HUGE.
Although, if you're constantly using your phone, the battery savings are negligible at best, and negative at worst, since it would be constantly turning your data service on and off. So depending on each person’s definition of how they use the phone, JD might be an application to avoid, especially if you’re a mid to heavy user of your phone.
Next is any type of Task Killers. XDA poster Justin.G11 has a in detail blog on this topic and below is the link for anyone interested.
http://egotoobigtovirtualize.blogspot.com/2011/03/android-battery-goodies.html
In a quick summary, using a Task Killer puts a little program in memory that will routinely scan your phone for running applications and forcefully close them, returning that memory to your phone. The problem is that this is a bad idea and the result of people assuming that multi-tasking in android is the same thing as multi-tasking in a desktop OS.
In it’s best moment, a task killer does absolutely nothing for your phone. It kills apps in memory that the process lifecycle service would have freed the moment it was needed anyway. The power consumed by your memory is constant weather it’s storing a 0 or a 1. So that doesn’t save you in battery at all. Instead, it nearly costs you battery because you just added a regular 15min scheduled task to monitor your apps. Which gives your android system more to do. Not only that but remember normally android stores the “activities” before it kills the app. Something the force close of a task killer will skip. This why you often have to re-login to apps that were force closed by a task killer, as opposed to that illusion of always running when android does the job. What’s funnier is because it registers background tasks with android, they will simply re-launch anyway. Meaning task killer will constantly find itself shutting down the same process over and over again, making the whole thing extra pointless.
Short of it is: 100% of any battery gains are placebo, and better battery gains could be easily achieved by changing the polling cycle of your apps so the android service doesn’t have to launch so many things so regularly. Forcefully closing apps with a task killer does not go to the root of your battery problem, does nothing to help, and simply impacts the user experience by skipping the storage of activities.
Step Ten, Control the polling of e-mail
Again another great write up by Justin.G11 in his blog linked above is Control the polling of e-mail. What we need to do is ratchet down on the polling and and background syncing our phones do to keep our battery life up. Most times, our #1 offender is e-mail, and more times than that, it’s POP3 or IMAP.
Let’s just throw it out there: POP3 is terrible for battery life. We are basically telling our phones to launch an email app every x minutes and sync/download. This means I have to choose between fast polling intervals to get mail instantly (5 minutes or faster) which will drain my battery with regular processes, or save battery with slower polling but mean that I may not get important emails for 30 minutes or more (in the land of instant gratification and IT support … this could be a deal breaker).
Thankfully ActiveSync provides us with an easy way out (ditto for Google Gmail, but that’s not my focus at them moment.)
Systems like Gmail and ActiveSync use a clever mechanism known as long-lived http to do their mail polling. What happens is a client will log into the target server, check for mail, then say “if any mail comes in the next 30 minutes, ping me at this IP” then stop. The actual time is a variable, that the phone cranks up slowly until it’s too long to make through the firewalls in the path of communication, but 30mintues is not uncommon. So after the initial poll the mail program can stop, be removed from memory/CPU, and a simple listener trigger is left on android for 30minutes incase the Exchange Server decides to “wake up” the mail client in order to deliver a new message.
This is really nice because it means I can have a slow 30minutes polling interval and save battery while having the email delivery time of a constant poll. But it means I have to stop using POP3… and start using ActiveSync for work, and perhaps Gmail for home use.
So how do I do that? Well you have Gmail if you have an android phone, and in the Accounts and Imports section of your mail settings you can setup Google to poll your various POP3 services for you. Bingo: best of both worlds. As a final “but I like keeping my messages separate”, you can label each message as it gets delivered to your gmail inbox so you can keep your messages sorted by POP3 account, and even register multiple smtp names for sending. A full solution.
By doing this I can now bring my battery down _significantly_ without sacrificing the ability to get emails at all. Major win in that department. Once I have all my personal POP sources tunneled through Gmail, I can simply rely on ActiveSync for work!
That’s it guys! Hope this post has been helpful in extending your phones battery life.
Here are my phones specs at the time of the testing...
HTC EVO
Model Number: PC36100
Build Number: MIUI-EVO-1.4.15-ENG
Kernel version: 2.6.38.2-SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB+
Battery type: Stock battery that came with device (prior shelf life 4-6 hours of heavy use)
After following all 10 steps I get the following performance from my battery
Heavy Use - 15+ Hours
Only about 4-5 hours phone is idle
30-60 minutes on the phone
Using WiFi at home and work, 3G while in my car or out on the town
20+ text messages
Download 5-10 apps per day
Play games 2-3 hours, maybe more if stuck in a meeting
Listen to music to and from work, about an hour per day.
On the internet most of the day, especially since I like to access facebook and twitter via my phones browser instead of their apps.
Watch 2-3 hours of videos\Youtube
Spend about 1 hour customizing my themes and\or downloading new themes
Finally, did a movie test on Sunday. After a 100% full charge, disconnected and played two movies on the phone. After about 4 hours when the movies were done, battery was still at 52%.
On Average, battery would drain 8-12% per hour of constant continual use when playing games, watching videos or listening to music.
As I said earlier in this post, I want this Best Practices for Battery Management to be a Living Document and I’ll be constantly updating\editing it once new or better practices\apps have been discoved for improving the battery life.
CREDITS
unrevoked.com for the “Painless root and flash”
ClockworkMod for “Rom Manager”
Guys at CyanogenMod for a great ROM
Guys at MIUI for a great ROM
Guys at Savaged-Zen for a great kernel
Taylor Groves, Jeff Knockel and Eric Schulte on their indetail info on kernel differences
-viperboy- for his instruction on how to lower voltages on AOSP kernels
Martino for “VM Heap Tool”
stiffspliff for increasing the MIUI default Heap level to 64
HipKat for the battery conditioning method
NeMa for “Battery Calibration”
Justin.G11 for his blog about Task Killers and Control the polling of e-mail
Define 15+ hours of heavy use. If the phone is on for most of that time and using data, then JD is not going to be doing much is it?
Your tips are well written - a good starting point for someone new.
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Good read though.
goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Click to expand...
Click to collapse
Obviously, you should that someone is talking about the stock battery unless otherwise noted.
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
instructions are a little biased.
jalai said:
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
instructions are a little biased.
Click to expand...
Click to collapse
maybe he didn't think sense users deserved attention?
Definitely I good starting point. I would recommend tasker over jd, but that's just me
Swyped from my cyanogenized and gingerbreaded EVO
Step 11. Get a kernel with SBC for maximum battery life!
Sent from my EVO using Tapatalk
I found this useful. I knew everything else but it introduced me to the battery calibration app and lowering my voltages.
goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Good read though.
Click to expand...
Click to collapse
would these instructions be applicable to someone using an extended battery? If so, should the battery life be extended in that scenario?
ECrispy said:
Define 15+ hours of heavy use. If the phone is on for most of that time and using data, then JD is not going to be doing much is it?
Click to expand...
Click to collapse
Sorry, I just signed up to this site and this was my first post. I've edited my original post above to reflect what my definition of 15+ hours of heavy use was and give a detailed breakdown.
goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Click to expand...
Click to collapse
I edited my original post to detail that I'm using just the stock battery that came with the phone. I also added the specs of my phone for those that were interested in what ROM and Kernel I was running during these tests after I did all 10 steps.
jalai said:
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
Click to expand...
Click to collapse
Good ideal, I just edited the subject.
twiz0r said:
maybe he didn't think sense users deserved attention?
Click to expand...
Click to collapse
Meant no disrespect to any sense ROM users.
I'll be testing a few sense ROMs next weekend, I'll do a similar post once I've tweaked these steps to fit sense ROMs I'll upload and do some more battery tests.
twiz0r said:
Definitely I good starting point. I would recommend tasker over jd, but that's just me
Click to expand...
Click to collapse
Thanks for the feedback, that's exactly what I'm looking for. As I want to best tweak these Best Practices for Battery Management on AOSP ROMs as much as possible. I'll test out tasker compared to juice defender to see if it'll help my battery life.
another good tip would be to spell AOSP correctly. What the hell is ASOP? a fable?
if you can't remember how to spell it, here's a tip:
Android Open Source Project
deathsled said:
another good tip would be to spell AOSP correctly. What the hell is ASOP? a fable?
if you can't remember how to spell it, here's a tip:
Android Open Source Project
Click to expand...
Click to collapse
LOL.....great tip, that's what I get for trying to edit my posts quickly.
Madvillebuck said:
would these instructions be applicable to someone using an extended battery? If so, should the battery life be extended in that scenario?
Click to expand...
Click to collapse
As long as your running an AOSP ROM like CM7 or MIUI, these instructions would be applicable to anyone, including those using an extended battery.
Since I don't have an extended battery, I'd love to hear feedback on performance from anyone who tried all these steps on an extended battery.
NYG27 said:
Thanks for the feedback, that's exactly what I'm looking for. As I want to best tweak these Best Practices for Battery Management on AOSP ROMs as much as possible. I'll test out tasker compared to juice defender and will try a kernel with SBC to see if they help my battery life.
Click to expand...
Click to collapse
Are you sure you're not already using an SBC kernel? SZ are SBC unless you specifically download the non SBC version. Also, kernel performance is phone dependent. Some people may see better battery life on the stock kernel or Tiamat (AOSP).
Which kernal should i get for improved battery performance? Im on Destroyer v2 mod & battery drains fast...Link would help to kernal!
Maybe I think too logically, but wouldn't all those apps you say to d/l be using battery to run in the background??
No offense, but I get excellent battery life just by keeping data off when I'm not using it.
jstalford said:
Are you sure you're not already using an SBC kernel? SZ are SBC unless you specifically download the non SBC version. Also, kernel performance is phone dependent. Some people may see better battery life on the stock kernel or Tiamat (AOSP).
Click to expand...
Click to collapse
Reason I mentioned “SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB-signed.zip” as the kernel to download, is that I've read about and tested that kernel to be more stable. (Maybe just my personal preference).
By all means test out the BFS kernel and see if you get better performance. There are also none non-SBC kernel but I haven't tested them out yet.
I try to flash a different ROM and kernel each week and test them out. As I do, I'm going to update my original post as much as possible to try to get a true Best Practices for Battery Management for both AOSP and Sense ROMs. So far I've only tested these steps with CM7 and MIUI, which is why I only caution people to test these steps with those ROMs or other aosp roms. The more testing I do with sense roms, I'll update my original post on this thread to be compatible with both aosp and sense roms.
HipKat said:
Maybe I think too logically, but wouldn't all those apps you say to d/l be using battery to run in the background??
Click to expand...
Click to collapse
If you look at Battery Settings\Battery Use, those apps hardly take up 1-2% of my battery running in the background. That's a trade off I'll take for having them improve the overall performance of my battery.
HipKat said:
No offense, but I get excellent battery life just by keeping data off when I'm not using it.
Click to expand...
Click to collapse
No offense taken. Although truth be told about your comment, you have listed in your sig that you use the Sedio Extended battery 3500 mAh. If I had an extended battery and kept data off when I'm not using it, I'd have great battery life also. Although I don't like the look and the bulkier feel of the extended battery (no offense, just my personal preference).
That's why I created this thread to help people extend the life of their stock battery that came with the EVO.
Tiamat>SZ for battery life.
i bought my galaxy SII 1 week back and im not much happy with my battery consumption ...its average but from two days i dont know why but the Android OS consumption usage is increasing.....can any1 plzz xplain me what to do and if i do rooting will it help with the android OS issue in battery
im attaching my screen shots...
Moved thread here, where it belongs.
This high Android usage seems to have gone in newer unoficial SGS2 builds.
Rooting and flashing a ROM based on anything Post KF2 might resolve this after a full Wipe of device.
(Full Wipe Then Flash new Rom)
stranzer said:
i bought my galaxy SII 1 week back and im not much happy with my battery consumption ...its average but from two days i dont know why but the Android OS consumption usage is increasing.....can any1 plzz xplain me what to do and if i do rooting will it help with the android OS issue in battery
im attaching my screen shots...
Click to expand...
Click to collapse
what kind of software do u use to monitor ur battery life ?
qwerty warrior said:
what kind of software do u use to monitor ur battery life ?
Click to expand...
Click to collapse
that is built into android now.
menu > settings > applications > battery.
If you click the graph at the top of the page you get more info too.
as for the OP, the easiest way to gain battery life is to get a good custom rom, and also underclock!! (even if its just for screen off). Most of us at VillainRom have underclocked to 800mhz and you honestly cannot tell the difference you can easily get 24 full hours of heavy use out of it.
yeah, updating the official stock rom would help or just get litening rom 1.5, few people complain about battery drain there cause thats definitely what you've got, most of my battery usage is from display and i only last 12 hrs cause i use it so much
This worked for me:
Root.
Backup, then uninstall certain systemapps with Titanium backup pro.
Advanced task killer pro.
Much better battery life after i did this
The percentage given for android OS is the percentage out of the total battery usage. If you don't use your phone, then android OS will be the one consuming the largest proportion since the operating system still runs while the screen is off.
Lennyuk said:
that is built into android now.
menu > settings > applications > battery.
If you click the graph at the top of the page you get more info too.
as for the OP, the easiest way to gain battery life is to get a good custom rom, and also underclock!! (even if its just for screen off). Most of us at VillainRom have underclocked to 800mhz and you honestly cannot tell the difference you can easily get 24 full hours of heavy use out of it.
Click to expand...
Click to collapse
I was using an app to get the same graph, i guess that way will consume less battery when i check it, as it doesnt have to run any app...=)
Thanks too for the 800mhz advise!
thanks for the reply im totally new to this android amateur....so can any 1 have a guide for the step by step process...so how should i install this villian rom...im guessing rom means operating system right....so rooting also include in it.........
stranzer said:
thanks for the reply im totally new to this android amateur....so can any 1 have a guide for the step by step process...so how should i install this villian rom...im guessing rom means operating system right....so rooting also include in it.........
Click to expand...
Click to collapse
Villain Rom custom/rom/rooting voids your warranty .
http://forum.xda-developers.com/showthread.php?t=1081368
jje
From my finding, disable following features can totally kill the "Wifi Sharing" service and help battery performance a lot.
Accuweather Widget (preloaded on GS2)
Uncheck Settings -> Enable current location
Voice Command & Voice Talk (preloaded on GS2)
Uncheck Settings -> Use location
hi thanks for ur advice ..after installing villain rom i dont know why but still Android OS is consuming a lot of battery so can you plz help me out to fix this probs...and one of the thing i observed i s camera shutter sound is off which is nice....but do u know how to on it.....and do u know how to use the camera app even ur battery <15% bcz when ur battery is at 14% SII doent allow to use it....
Well, it worked with three other testers, some friends of mine that found the same problem. If you're facing this, try and feedback me. Just want to make sure that I've helped someone.
This guide is for those who have the 0% battery issue, found the fix by Bazoocaze (thanks a lot !!!) and are experiencing some quick battery drain. If you're not, then you can go read something else In two or three weeks of testing, I believe that this does not have something related to the ROM that we're using. The processes on background and the use of CPU is relative, but maybe a process is using too much energy, and if we keep the energy level on a low status, I think this process won't have so much energy to use. And maybe the kernel, or the kernel's governors are affecting something, not sure of this last one. I've also concluded that this don't have anything to do with the Wi-Fi modules, because I've already tried that fix, and it drains pretty quick anyway, some believe that there is a bug affecting the Wi-Fi, and it doesn't turn off, even if we turn it off on the menu.
First of all, if you haven't find the fix, read this: http://forum.xda-developers.com/showthread.php?t=1312398
You can also use the DooMKerneL ICS v4 that DooMLorD developed, and it already has the patch built-in (I recommend for this guide): http://forum.xda-developers.com/showthread.php?t=1520654
1 - Flash the kernel, the one of Bazoocaze or the DooM Kernel
2 - Turn on your phone, normally, make all your configs, and do a little test, BEFORE following this guide. See how many time your battery can hold on. If you feel that it's going out too fast, keep going on the guide.
3 - For this operation, I suggest you buy or download the free version of SETCPU, never forget that name. NoFrills didn't work very well to me..
4 - Overclock, if you want and if you're using DooMKerneL. Keep the MHz min on 364 (will explain later)
5 - Go to the profiles tab and press the ''plus'' button. Change the MHz max to 768 and keep the min at 364. In profile, select Screen Off, and change the governor to powersave or smartass and set priority to 100%
6 - Save it, and press Enable and Notifications on the bottom of the screen.
7 - Now test it for some time. Try not to keep your screen always on, as it ''cancel'' the effect of this guide.
Explanations:
a) The reason to keep the min MHz at 364 is that you won't face stuttering in the screen on/off, because the app will only change the max value, and not the min value, which makes the system still work fine (I believe, if some dev could correct me..). It behave better in AOSP alike roms.
b) NoFrills didn't give me the same results as SetCPU, that's why I'm recommending SetCPU. Make some effort to buy the Pro app.
c) The main trick is to reduce the power usage and capacity when the screen is off, because you don't use your phone 100% of the day, and because the process that may exist (mentioned above) would not use the whole capacity of the energy and the CPU as well. That's why it works. At least worked for me.
d) There is absolutely no hardware of software issue if you try this guide, you can uninstall the SetCPU app and use kernel other than DooM's. It's safe and quick, if it doesn't work, you can always revert everything.
Please, if you want to try this guide, give me the feedback. As I've said, I just want to confirm that theory and make sure that I've helped someone.
Thanks Bazoocaze and DooMLorD for being life savers!!!!!!!!
Bye
Thanks for your help
Sent from my LT18i using xda premium