Database Users

[Battery Stats] JI6 Stock VS. Bionix Fusion 1.0 (Updated 10/29)

Background
I wanted to figure out a test I could conduct while keeping variables minimal. I figure a standby battery drain test would be as consistent as I could get by not using the phone or turning it on once during the test. Any other test would be too subjective depending on use.
Constants
In attempt to keep the different tests constant, I powered off the device, rebooted, removed all syncs, updates, emails etc. I made sure I charged the phone to 100% and left it on for 30 minutes after the 100% was charged to get the maximum amount possible. Removed usb cord, turned off screen, did not touch for approximately 10 hours.
Pre JI6 Results
I'm not sure if I should even have this here since I didn't do an official test for pre-JI6. Pre-JI6 update my standby battery drain was moderate. From memory it was approximately 1%-1.5% drain per hour while in standby. I used stock for about 3 months.
Post JI6 OTA Standby Results
Time on 10 hours 20 minutes
Battery life left 60%
Battery used 40%
Cell Standby - 40%
Phone Idle - 30%
Android System 20%
Calls (1 missed call) 5%
Display 3%
Maps 2% (Why does maps show up?)
Post Bionix Fusion 1.0 w/ JI2 Modem Results
Time on 10 hours 33 minutes
Battery life left 97%
Battery used 3%
Cell Standby - 57%
Phone Idle - 43%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After flashing the default rom, I removed all applications I did not want, I removed all 3 DRM instances via Titanium Backup, and removed Media Hub. Also removed these via root explorer:
drmUa.apk
drmprovider.apk
SisoDrmProvider.apk
Final Results
1%-1.5% - Pre JI6 Standby Drain
4%+ - Post JI6 OTA Standby Drain
.3% - Post Bionix Fusion 1.0 Standby Drain
Conclusion
Out of the 3, Bionix Fusion 1.0 w/ JI2 Modem is by far the best for standby drain times. According to these small series of tests I can get 330+ hours in standby and possibly more under optimal conditions.
Post Conclusion
I am now passed my third day on a single charge. Granted I am not using the phone heavily, I am using it on a daily basis. I still have a 60%+ charge after 3 days of light use.
Media Hub + DRM
Looking at everyone's comments and tests it looks like the major culprit behind battery drain is Media Hub + DRM. Regardless of using a Stock ROM or a custom ROM people are universally reporting significant gains by removing all traces of Media Hub + DRM related instances.
Kubernetes said:
... As far as I can tell, all it affects is MediaHub. The DRM services constantly ping the CPU checking to see if you're stealing content, which kills your battery life.
Click to expand...
Click to collapse

Any lag issues? Does it lag while typing a message? Does the gps work any better? Does the Map work any better. Does voice recognition work any better as mine sucks. My G1 worked better at all of these then this phone does.
I really hate the stock phone and I am about to either install a rom or switch to a different phone. Maybe a Mytouch HD.

sj_martin said:
Background:
I wanted to figure out a test I could conduct while keeping variables minimal. I figure a standby battery drain test would be as consistent as I could get by not using the phone or turning it on once during the test. Any other test would be subjective depending on use.
Constants
In attempt to keep the different tests constant, I powered off the device, rebooted, removed all syncs, updates, emails etc. I made sure I charged the phone to 100% and left it on for 30 minutes after the 100% was charged to the maximum amount possible. Removed usb cord, turned off screen, did not touch for approximately 10 hours.
Pre JI6 Results
I'm not sure if I should even have this here since I didn't do an official test for pre-JI6. Pre-JI6 update my standby battery drain was moderate. From memory it was approximately 1%-1.5% drain per hour while in standby. I used stock for about 3 months.
Post JI6 OTA Standby Results
Time on 10 hours 20 minutes
Battery life left 60%
Battery used 40%
Cell Standby - 40%
Phone Idle - 30%
Android System 20%
Calls (1 missed call) 5%
Display 3%
Maps 2% (Why does maps show up?)
Post Bionix Fusion 1.0 w/ JI2 Modem Results
Approximately .3% drain per hour while in standby:
Time on 10 hours 23 minutes
Battery life left 97%
Battery used 3%
Cell Standby - 57%
Phone Idle - 43%
After flashing the default rom, I removed all applications I did not want, I removed all DRM instances via Titanium Backup, and removed Media Hub.
This was my first time rooting / flashing new roms which took a whole 15 minutes to complete.
Results
Pre JI6 Drain - 1%-1.5%
Post JI6 OTA Drain - 4%-5%
Post Bionix Fusion 1.0 Drain - .3%
Conclusion
Out of the 3, Bionix Fusion 1.0 w/ JI2 Modem is by far the best for standby drain times.
Click to expand...
Click to collapse
You said you removed all instances of DRM with Titanium.. I show 3 in mine, but I'm afraid to remove them lol.
I have:
Download Manager 2.1-Update 1
DRM Protected Content Package 2.1-Update 1
DRM Protected Content Package 2.1-Update 1
DRMContentLauncher 1.0
those are in my Titanium...
I've noticed that even with MH gone, after a reboot I kill oaDRM and DM Services, I get pretty good battery life..

I deleted those exact 3 a few days ago. Have not noticed any side effects yet other than significantly better battery life. But as always, delete at your own risk.

sj_martin said:
I deleted those exact 3 a few days ago. Have not noticed any side effects yet other than significantly better battery life. But as always, delete at your own risk.
Click to expand...
Click to collapse
sj_martin... you are the best!
Been wondering which one to delete!
[thanks to presence06 for pointing out the services running].
I'll be deleting those and see if I get any bad results.
or Freezing them using Titanium for that matter.

rbcamping said:
Any lag issues? Does it lag while typing a message? Does the gps work any better? Does the Map work any better. Does voice recognition work any better as mine sucks. My G1 worked better at all of these then this phone does.
I really hate the stock phone and I am about to either install a rom or switch to a different phone. Maybe a Mytouch HD.
Click to expand...
Click to collapse
Regardless of which ROM I was using I never had lag on input. Possibly a rouge app you have running?
GPS and Map work significantly better with Bionix Fusion. It did not work well with JI6 OTA. 1 minute lock times down to 3 seconds.
Definitely give Bionix Fusion a shot before jumping ship. My phone is performing a lot better than stock. I've been using stock for a little over 3 months.

presence06 said:
You said you removed all instances of DRM with Titanium.. I show 3 in mine, but I'm afraid to remove them lol.
I have:
Download Manager 2.1-Update 1
DRM Protected Content Package 2.1-Update 1
DRM Protected Content Package 2.1-Update 1
DRMContentLauncher 1.0
those are in my Titanium...
I've noticed that even with MH gone, after a reboot I kill oaDRM and DM Services, I get pretty good battery life..
Click to expand...
Click to collapse
I froze Download Manager 2.1-Update 1 using Titanium Backup... i got FC's on using the market. Defrost- Market works again.
Just FYI.

HG! said:
I froze Download Manager 2.1-Update 1 using Titanium Backup... i ot FC's on using the market. Defrost- Market works again.
Just FYI.
Click to expand...
Click to collapse
Not sure why you froze the download manager, nowhere did I mention messing with that one. Fortunately you didn't delete it
Only the 3 DRM's + Media Hub should be removed.
But at least we have a confirmation now to definitely not mess with the download manager.

Has anyone else who's disabled these DRM instances with Titanium become incapable of downloading anything via the market? I kind of expected I might, so I tried to back them up with Titanium, but unfortunately it's not letting me restore them (they're crossed out at the bottom; the only button that highlights is "delete", which I tried on one of them out of curiosity, and sure enough it deleted the backup. Oops.)
Before I go through the pain of reflashing the ROM [bionix fusion 1.1] I'd like to know if anyone else has this problem, and more importantly whether anybody has the .apk files for each of those four DRM instances (couldn't hurt trying) or other suggestions (delete more stuff? )
Thanks!

Disregard...

If you guys are having issues doing this with Titanium, there's also a neat little app called SDX System App remover. All it does is allow you to backup/delete/restore system apps. The DRM files are really easy to identify with this app.
Sent from my SGH-T959 using XDA App

Deathsnapper said:
Has anyone else who's disabled these DRM instances with Titanium become incapable of downloading anything via the market? I kind of expected I might, so I tried to back them up with Titanium, but unfortunately it's not letting me restore them (they're crossed out at the bottom; the only button that highlights is "delete", which I tried on one of them out of curiosity, and sure enough it deleted the backup. Oops.)
Before I go through the pain of reflashing the ROM [bionix fusion 1.1] I'd like to know if anyone else has this problem, and more importantly whether anybody has the .apk files for each of those four DRM instances (couldn't hurt trying) or other suggestions (delete more stuff? )
Thanks!
Click to expand...
Click to collapse
Looks like the problem was that I accidentally deleted DownloadProvider.apk . If you do that the market FCs when you try to download. Easy fix by simply pushing the apk to the /system/apps folder (I figure out after way too much time trying to get the install command to work, in ADB, realizing my cmd.exe exe has to be in the tools folder for that (it doesn't need to for any other ADB command I tried - but otherwise it was searching the wrong directories for the apk) getting it to attempt to install right before throwing an error for an unsigned apk, which was another little joust altogether).
So if your market dies, get yourself DownloadProvider.apk from your ROM's .zip and push it to /system/apps . Simple solution

sj_martin said:
Not sure why you froze the download manager, nowhere did I mention messing with that one. Fortunately you didn't delete it
Click to expand...
Click to collapse
Because "presence06" mentioned that one in addition to the three you deleted. And, you confirmed his post. So, either you need to or he needs to edit the post.

wow. great results, happens to me the other way around using fusion 1.1

presence06 said:
DRM Protected Content Package 2.1-Update 1
DRM Protected Content Package 2.1-Update 1
DRMContentLauncher 1.0
Click to expand...
Click to collapse
sj, or anyone else know what these 3 DRM packages do? sj deleted them, I froze them with Titanium... and no issues at all. And why are these eating up the battery?
[froze them... and battery life is awesome so far.]

@sj_martin what version of Bionix Fusion are you using? are you using Stock kernel or Jac's OC or KK's OC?

krazie1 said:
@sj_martin what version of Bionix Fusion are you using? are you using Stock kernel or Jac's OC or KK's OC?
Click to expand...
Click to collapse
Im running the stock version with no oc and no voodoo. Ill likely try out voodoo when a 1.2 fusion comes out.

HG! said:
sj, or anyone else know what these 3 DRM packages do? sj deleted them, I froze them with Titanium... and no issues at all. And why are these eating up the battery?
[froze them... and battery life is awesome so far.]
Click to expand...
Click to collapse
Many people in the bionix thread suggested that removing these has helped their stats so i blindly followed with great results. Not one person knows what exactly they do. One person is looking into it and researching but no official response from what ive read.

sj_martin said:
Many people in the bionix thread suggested that removing these has helped their stats so i blindly followed with great results. Not one person knows what exactly they do. One person is looking into it and researching but no official response from what ive read.
Click to expand...
Click to collapse
once you removed it can still be returned right?

I turned off the drm services stuff seven hours ago I went from 70 to 65% with about 30 minutes of use in the last seven hours. Whatever drm does its draining battery.
Using rooted stock ji6 with wifi in always on mode.
Sent from my SGH-T959 using XDA App

*UPDATED* HTC EVO Best Practices for Battery Management on AOSP ROMs

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.

[INVESTIGATION] Battery drain bug in 2.3.4 (JVP build for now)

It seems that our beloved Samsung did it again!
Now we can enjoy a fully functional, long waited, Gingerbread 2.3.4.
Although some sources say that it is only a leak, the JVP build seems to behave really well, according to the reports of many users.
Gingerbread 2.3.4 was build in order to fix some Android bugs and make the interface even faster. We have seen that the second task is a success, the user experience and crazy Quadrant scores being the best witnesses. But what about the first task, are there any android bugs in this build? Maybe we could find out together.
The key purpose of this thread is to find out if that Android OS bug, which made Gingerbread users a hard life, is still present.
You can help this investigation by keeping an eye on the battery stats and reporting the consumption (in percents, of course) of the Android OS. It is even better if you can add some screenshots.
Please don't forget to mention:
- The ROM and kernel you are using.
- Some apps or games you are using (known to fire this bug on previous builds).
- Whether you have autorotation on or off (some users reported they had no drain if kept off on 2.3.3 builds).
- What type of usage you applied to the phone (not really necessary, only you are kind enough).
If you have any kind of suggestion regarding some modifications for this thread you are welcomed to post them. It will helps us become more efficient.
Thank you very much for your effort!
EARLY CONCLUSIONS*:
- Battery life is indeed an improvement on JVP 2.3.4
- The Android OS bug is less aggressive. The reports show a maximum consumption of approx. 20%. We can't say for sure if we can talk about a bug anymore. Anyway, the drainage is not so bad, comparing to 2.3.3 versions.
- The Android System consumption is a bit scary (15-20%) especially after a flash. However, it tends to stabilize in time.
- A clean flash, factory resets, avoiding apps restoration with Titanium or similar, reducing consumers when you don't need them always helps. With or without battery draining bugs.
- JVP is a better alternative for previous versions due to improvements for battery life, speed and stability, even if it's a beta release. So you should go for it, it really is an upgrade!
*The statements above are based on reports and poll results collected until now and they may change. I take no responsibility if you will find those informations incorrect or incomplete. Flash JVP at your own risk, you could loose data or brick your phone, although there aren't reports that say that. Follow the instructions and you should be ok!

is this a new craze insted of train spotting or stamp colecting ....battery watching ....most of us have got a life and have better things to do then watch how much a battery uses ...do what i do charge the phone and enjoy these phones do use loads of battery

Updated with 2.3.4 I9000XXJVP,CSC = I9000OXAJVP and kept it on without sim and without even touching but fully charged. The battery life was just for one and half days.

Android OS running at 3%
using Damian's GTO Alpha kernel for JVP and Brotuck's gingerMod ROM.
Autorotation off.
Consistent q scores in the 2600 range, phone running very smoothly and very fast in daily use (internet, twitter, pics, camera, messaging, phone), 130+ apps installed, no issues. Seems a much better base firmware than any of the 2.3.3 variants.

It's a bit early to investigate this stuff.
Wait for Samsung to release 2.3.4 sources and devs to make some stable kernels based on this.
Until this time many stuff can be broken (well, you're free to beta test though ).

batery is much beter in 2.3.4

no since i flash JVP 2days ago!

anukilimanoor said:
Updated with 2.3.4 I9000XXJVP,CSC = I9000OXAJVP and kept it on without sim and without even touching but fully charged. The battery life was just for one and half days.
Click to expand...
Click to collapse
Keep in mind that after a reflash the battery life will stabilize after a while.
In my opinion, the cell standby may be the cause. If left without SIM, Airplane mode off, your phone will continue to search for signal and this really drains the battery.
If you can make a test again, check the battery usage and post your conclusion.
Thanks for your contribution!

got-petrol said:
is this a new craze insted of train spotting or stamp colecting ....battery watching ....most of us have got a life and have better things to do then watch how much a battery uses ...do what i do charge the phone and enjoy these phones do use loads of battery
Click to expand...
Click to collapse
This kind of activity is normal in community, especially here in XDA.
It will be useful for those kind of people who don't like to experiment in order to find some answers.
We could do like you but, what if we need to charge it again, after 8 hours, without using the phone?
That's why this "new craze" exists, because we want to avoid that kind of problems.

Tatsuya79 said:
It's a bit early to investigate this stuff.
Wait for Samsung to release 2.3.4 sources and devs to make some stable kernels based on this.
Until this time many stuff can be broken (well, you're free to beta test though ).
Click to expand...
Click to collapse
You're right but the 2.3.4 concentrates on fixing bugs, so even in beta stage we should see some changes.
Anyway, the thread is intended to test the firmware regarding this problem, so it can become an indicator for people asking weather they will experience this problem of they can enjoy using their phone without even thinking about this.

lgsshedden said:
Android OS running at 3%
using Damian's GTO Alpha kernel for JVP and Brotuck's gingerMod ROM.
Autorotation off.
Consistent q scores in the 2600 range, phone running very smoothly and very fast in daily use (internet, twitter, pics, camera, messaging, phone), 130+ apps installed, no issues. Seems a much better base firmware than any of the 2.3.3 variants.
Click to expand...
Click to collapse
Thanks for your feedback, happy user!

I must say that 2.3.4 battery is performing better than 2.3.3 so far.
After 11 hours with gps and auto rotate on, battery still have 30% of juice left.
EDT: Attached screenshots
Sent from my GT-I9000 using XDA App

Comming from Froyo JPY to stock deodexed JVP, I have noticed a higher battery drain.
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
I'm using stock deodexed rom from ramad, Dark core kernel and screen off animation. that's all I've changed to this rom, no games, and a few apps like titanium backup and atk.
When I tapped on the android system there was a huge list of included packages, I will list them here, maybe one of them (or all together) is causing that huge battery use:
com.samsung.InputEventApp
Service mode
Software update
Google Backup Transport (actually, I turned off google backup, idk why this is here)
Settings Storage
Mobile tracker
Account and Sync Settings
EncryptApp
Task manager
Error
Perso
com.sec.android.app.lcdtest
VPN Services
Factory Test
wssyncmlnps
PopupuiReceiver
Preconfig
BluetoothTest
Self Test Mode
WlanTest
Status Bar
Settings
Mobile tracker settings
Android System
DRM content
MTP Application
PhoneSetupWizard
Security Storage
Licence Settings
PhoneUtil
Those are all......

gtluis said:
Comming from Froyo JPY to stock deodexed JVP, I have noticed a higher battery drain.
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
I'm using stock deodexed rom from ramad, Dark core kernel and battery off animation. that's all I've changed to this rom, no games, and a few apps like titanium backup and atk.
When I tapped on the android system there was a huge list of included packages, I will list them here, maybe one of them is causing that huge battery use:
com.samsung.InputEventApp
Service mode
Software update
Google Backup Transport (actually, I turned off google backup, idk why this is here)
Settings Storage
Mobile tracker
Account and Sync Settings
EncryptApp
Task manager
Error
Perso
com.sec.android.app.lcdtest
VPN Services
Factory Test
wssyncmlnps
PopupuiReceiver
Preconfig
BluetoothTest
Self Test Mode
WlanTest
Status Bar
Settings
Mobile tracker settings
Android System
DRM content
MTP Application
PhoneSetupWizard
Security Storage
Licence Settings
PhoneUtil
Those are all......
Click to expand...
Click to collapse
It seems that you have a normal consumption on Android System. Also that app list is present on every ROM which has all system apps. On lite ROMs you can get a smaller list, because some of those apps are removed by the chefs.
Maybe your network coverage is not that good
After a flash, the battery needs stabilization, until then it can drain fast. Try to recalibrate it. Please tell me if you need a good guide.
Try a lite ROM. Maybe you will experience a good Android System consumption.
Thanks for the feedback!

Look at the poll results so far 72% say they have no battery issue, so it must be the apps on your phone that are at fault for any unusual battery drain.
Look at your own apps first before you blame the rom, mostly it's not the rom that's at fault.

gtluis said:
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
Click to expand...
Click to collapse
When you're not really using your phone, Android System will have a higher battery use percentage, because nothing else is using battery.
Long periods of idle, you will see higher Cell Stanby and Android System percentages.
The more you use the phone, those percentages will lower.

mammenj said:
I must say that 2.3.4 battery is performing better than 2.3.3 so far.
After 11 hours with gps and auto rotate on, battery still have 30% of juice left.
EDT: Attached screenshots
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Good job! Enjoy your phone!

turn off data connection or wifi when youre not using them
and it will least even longer...

This is what i had with the previous JVO (2.3.3) and not using any task killer anymore. I moderately used the phone, made some calls, wrote some SMS, had blutooth on in the car, listening mp3. Ah, and i set display brightness to "auto" always, i don't use the manual setting with lowest brightness value anymore.
But i also can get the battery down in less than a day...
I'll give the new 2.3.4 a try.

It's funny to see that there is always somebody who needs to torture the board with reinventing the battery wheel. Strange battery behavior usually shows up (and is often dependent on them) in threads with special roms or kernels. The only thing this thread will brings us is more of the same on how to save juice if you don't want to fork for a larger/extra battery.

[Q] About WP7.5

Hi guys, just a quick question.
Which Windows phone 7.5 mango rom is best on battery life?
I'm currently using Pdaimatejams V8 VERSION of his wp7.5 rom, and the battery life on that is terrible. 8:30am to 1pm and battery is dead .
Advice on this would be nice as these roms are huge and take ages to download, so manually checking one by one would take years.
Regards,

Not as simple as that mate, they are all more or less the same ROM.
you have the defunct BTTF line which was complicated but by far the best overall ROM with the least problems
then you have Ultrafruit Clones
the really killer on battery life comes from the radio your using and any live tiles, also BT and Wifi can kill it pretty quick too.
in short try the 2.12 hardware radio ROM and the 51t software radio, the hardware radio can be flashed whenever but the software must be installed when you flash the initial ROM.
With those you can also try the camera trick, which is tap the camera button, put it in to video mode, let it auto focus then tap the home button.
its thought that for some reason the camera doesn't stop focusing or something like that unless you do the above, loading up the camera again will mean you need to reapply the fix
anyhow, so make sure you have no background tiles killing you, your running those radios, and you have done the camera trick, all with BT and wifi off as much as possible, and it will last a day with heavy use.

dazza9075 said:
Not as simple as that mate, they are all more or less the same ROM.
you have the defunct BTTF line which was complicated but by far the best overall ROM with the least problems
then you have Ultrafruit Clones
the really killer on battery life comes from the radio your using and any live tiles, also BT and Wifi can kill it pretty quick too.
in short try the 2.12 hardware radio ROM and the 51t software radio, the hardware radio can be flashed whenever but the software must be installed when you flash the initial ROM.
With those you can also try the camera trick, which is tap the camera button, put it in to video mode, let it auto focus then tap the home button.
its thought that for some reason the camera doesn't stop focusing or something like that unless you do the above, loading up the camera again will mean you need to reapply the fix
anyhow, so make sure you have no background tiles killing you, your running those radios, and you have done the camera trick, all with BT and wifi off as much as possible, and it will last a day with heavy use.
Click to expand...
Click to collapse
Right thanks for the tips! I had 4 live tiles, moved them.
Although i'm not quite sure what you meant by the camera trick?
Say i've done a fresh boot of the phone and not opened the camera app since, will that affect the battery life?
What's the camera trick meant to do exactly and how does it increase battery life?
Thanks for your response though!

Tenpin said:
Right thanks for the tips! I had 4 live tiles, moved them.
Although i'm not quite sure what you meant by the camera trick?
Say i've done a fresh boot of the phone and not opened the camera app since, will that affect the battery life?
What's the camera trick meant to do exactly and how does it increase battery life?
Thanks for your response though!
Click to expand...
Click to collapse
well you need to remember that this phone was only a test phone for WP7, it never had proper drivers made for it, hence some of the issues.
if you have the 51T soft radio then you can do the "camera trick"
I don't think there is any real answer (feel free to correct me folks!) to this other than guessing but I think it goes along the lines of, the camera even when off or not even ran that session can continue to focus, which eats up the battery, its like leaving the camera on. by opening the camera, then turning to video mode, then let it focus and finally tapping the home button, it seems to dramatically reduce the discharge rate, in some cases to as low as 2-5mA
Now to be honest that sounds very low, but I guess if you turn everything off and live in a good signal strength area you may get that., ive not had it lower than 10mA, before the trick it could use anything from 30mA - 80mA for some reason it can jump up to 300mA, this is all in standby mode, putting the screen on with it set to high will zap your battery, the backlight settings are next to useless as well so its worth turning off the backlight if you can. I think the choices are, Burn your eyeballs out, wheres my sunglasses and finally Off, auto doesn't work.

dazza9075 said:
well you need to remember that this phone was only a test phone for WP7, it never had proper drivers made for it, hence some of the issues.
if you have the 51T soft radio then you can do the "camera trick"
I don't think there is any real answer (feel free to correct me folks!) to this other than guessing but I think it goes along the lines of, the camera even when off or not even ran that session can continue to focus, which eats up the battery, its like leaving the camera on. by opening the camera, then turning to video mode, then let it focus and finally tapping the home button, it seems to dramatically reduce the discharge rate, in some cases to as low as 2-5mA
Now to be honest that sounds very low, but I guess if you turn everything off and live in a good signal strength area you may get that., ive not had it lower than 10mA, before the trick it could use anything from 30mA - 80mA for some reason it can jump up to 300mA, this is all in standby mode, putting the screen on with it set to high will zap your battery, the backlight settings are next to useless as well so its worth turning off the backlight if you can. I think the choices are, Burn your eyeballs out, wheres my sunglasses and finally Off, auto doesn't work.
Click to expand...
Click to collapse
battery life is subjective...it depends on the types of apps you have installed, their use of wireless services, your personal usage habits, etc.

Yea we already established that, but what is not clear is why it can go on a melt down and drain the battery very quickly for no apparent reason one day to the next. My theory on that is that ita not fully charged. IE. its half full but reporting full, thus it may appear to drain twice as fast
Sent from my HD2 using XDA Windows Phone 7 App

dazza9075 said:
Yea we already established that, but what is not clear is why it can go on a melt down and drain the battery very quickly for no apparent reason one day to the next. My theory on that is that ita not fully charged. IE. its half full but reporting full, thus it may appear to drain twice as fast
Sent from my HD2 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
what day to day melt down? he only described one day's battery life of 6 hrs of use. 6hrs is not a meltdown.
it's an issue with the rom. if you READ the v8 rom thread, the v8 rom has lots of power issues. i've read many posts complaining about the poor battery life.

hjhjhj said:
what day to day melt down? he only described one day's battery life.
it's an issue with the rom. if you READ the v8 rom thread, the v8 rom has lots of power issues. i've read many posts complaining about the poor battery life.
Click to expand...
Click to collapse
I've only described one days, although for this entire week it has been pretty much the same. Only lasting around 6 hours.. and are you suggesting it is Pdaimatejam v8 that's causing the immense drain? Perhaps I should try this rom: http://forum.xda-developers.com/showthread.php?t=953078?

Tenpin said:
I've only described one days, although for this entire week it has been pretty much the same. Only lasting around 6 hours.. and are you suggesting it is Pdaimatejam v8 that's causing the immense drain? Perhaps I should try this rom: http://forum.xda-developers.com/showthread.php?t=953078?
Click to expand...
Click to collapse
i'm not suggesting anything. just conveying what other users have posted. you've posted to the v8 thread and you've seen all the posts about battery life issues since v8 was released. if you like pdaim's rom...why don't you just flash v7.9?

hjhjhj said:
what day to day melt down? he only described one day's battery life of 6 hrs of use. 6hrs is not a meltdown.
it's an issue with the rom. if you READ the v8 rom thread, the v8 rom has lots of power issues. i've read many posts complaining about the poor battery life.
Click to expand...
Click to collapse
I see you've not change in the months since our last encounter.
Im running the V8 as I have been running just about all his updates and there are many, as well as HD2s, xbmods and even the Ultrafruit original that this comes from, the issues are the same on all of them. But If you care to read and follow all the information available in here you will see that its quite common for the HD2 running WP to draw ~300mA in standby, that its a huge amount of power to draw when its off and would empty the battery in 4 hours, without even using it.
when it comes to battery life, nothing is clear, however we do know that it doesn't always charge the battery fully, we do know that it can incorrectly report the available charge, we do know what despite devices using identical ROMs some folk can get <7mA in standby, others get >300mA in standby.
In short its a mess.
If you have an external charger and spare battery use it, it will help with half the problem, high current usage can be down to several things and probably many more that we do not know about, all things being well, if you use your phone a lot, use an external charger, make sure you have good radios for your area installed including the 51T soft radio an then do the camera trick, you may get a working day out of it without issue.
Thats with a lot of usage, making calls, BT, excel, music, 2 email accounts set to push etc

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a meltdown. Overnight, no wifi, just sleeping. Tried camera trick. Nice rom and my first try at WP7.
I call this a fail.
Back in ICS now.
Sent from my HD2 using the power of ICS

just reminding, there are some problem with HD2 wp7 battery indicator which always shows wrong battery percentage...
altough it shows 0%, you still can use it for several hours....
try to change the radio SW and HW, and do camera trick...

wazzzuuuup2 said:
just reminding, there are some problem with HD2 wp7 battery indicator which always shows wrong battery percentage...
altough it shows 0%, you still can use it for several hours....
try to change the radio SW and HW, and do camera trick...
Click to expand...
Click to collapse
ok, there maybe some problems with the battery indicator, but for sure it was deader then a dead thing. after pluggin in and restarting in android it was on 1%
i had what seemed to be the best radios and tried the camera trick.
but... apart from that, the phone was asleep (or pretending to be) with wifi and bt off.

New firmware V2.19.40.18 (available now !)

Another update from Asus is rolling out!
【Version】
V2.19.40.18_20150612 (ZE551ML)
V2.19.40.12_20150612 (ZE550ML)
【Release Date】
2015/06/18
【Release Note】
1 Update phone APN version to 105.
2 Update Houdini 5.0.2
3 Fixed camera can not open sometimes when using zenflash
4 Improve volume of recording video will increase and decrease alternately.
5 Do not config Routing.Configure.HWCodec.Playback.Mixers.Headset when using FM.
6 Fixed some BLE device can not auto reconnect
7 Improve service stability
8 Improve modem stability from crash
9 Improve call stability
10 Improve signal bar stability for sim 2
11 Quick Settings: Change "Reading Mode" button as "Bluelight filter"
12 Improve SysteM UI stability and modify Japanese strings
13 Improve lockscreen UI and stability
14 Fix Homescreen Wallpaper randomly lost previous settings and half black screen issue
15 Snap View-add reset Snap View password function
16 Fix Contacts search failure issue when default language was set as HK Chinese
17 Improve Auto start manager stability and fix FB broadcast issue
18 Improve Task Manager UI and rotation stability
19 Fix calculator stability issue and UI bug under Quick Memo App
20 Improve Launcher and Multi user stability from System and framework
21 Fix Google Voice incoming call source issue and the failure to change to Google Voice number
22 Fix the issue that miss call counts failed to disappear on home when Multi user
23 Improve File Manager stability
24 Add ASUS ZenUI PC Suite
25 Fix all touch gestures to be enabled when change back to owner mode
26 Fix ASUS Browser issue
27 Fix the issue that Audio Wizard cannot be launched when turn off BT
28 3rd party app update
29 Update touch FW
30 Update JP IME ATOK to v 1.0.1
31 Modify Japanese strings in Power Saver App
32 Fixed turn on the camera must unlock by using zenmotion issue
33 Fixed an error message shows up after removing privacy mode and adding new user immediately issue.
34 Fixed wallpaper needs to have second clicks for reaction issue.
35 Fixed built-in browser features a new incognito window has no effect issue.
36 Fixed close contacts shows other programs issue.
37 Fixed built-in calendar Click settings will flash issue.
38 Fixed ringtones into vibrate mode when the camera is off camera sounds issue.
39 Fixed volume keys to adjust the ring abnormaliy issue.
40 Fixed wallpaper Figure has been broken issue.
41 Fixed after the system optimization, message management have stopped running issue.
42 Add Battery charging ready reminder feature.
43 Enable FM Radio for Turkey.
Click to expand...
Click to collapse

"33. Battery-Add Battery charging ready reminder feature: User could set battery level under charging to receive the reminder."
seems they have given up on fixing the issue therefore just adding an alarm to recharge the battery... not good!

I saw the update but they deleted it on their download support page for now.

SBFarooq said:
"33. Battery-Add Battery charging ready reminder feature: User could set battery level under charging to receive the reminder."
seems they have given up on fixing the issue therefore just adding an alarm to recharge the battery... not good!
Click to expand...
Click to collapse
I am optimistic about the development department of Zenfone, atleast they are working deep enough about their flagship. The battery drainage is an issue for almost every Android L(5.0) user. I hope this issue will be fixed after we get update for 5.1.1 .
Asus is also expending their QA inspection team this will help for the end user to have stable releases afterwards.
Thumbs up Asus for the efforts.

I just received my phone this morning. it's a CN model. I charged it to 100%. Played a bit with it at work when I had the chance. I've spent the rest of the evening setting it up. The latest update is sitting waiting for download but I won't take it until tomorrow. I want to see how it goes overnight.
Even given the short time I've had it I'm pretty sure the battery stats are simply misreported and the poor battery life that some people are experiencing are down to individual setups or faulty devices. I've done nothing yet to conserve battery other than turning off the stupid ASUS battery saver, deleting some Chinese bloat and setting Wi-Fi to switch off when screen is off. From what I can see battery is comparable to my G2 which I was very happy with. As you can see from the screen shots it's pretty good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ASUS_Z00ADA using Tapatalk

corrsea said:
I just received my phone this morning. it's a CN model. I charged it to 100%. Played a bit with it at work when I had the chance. I've spent the rest of the evening setting it up. The latest update is sitting waiting for download but I won't take it until tomorrow. I want to see how it goes overnight.
Even given the short time I've had it I'm pretty sure the battery stats are simply misreported and the poor battery life that some people are experiencing are down to individual setups or faulty devices. I've done nothing yet to conserve battery other than turning off the stupid ASUS battery saver, deleting some Chinese bloat and setting Wi-Fi to switch off when screen is off. From what I can see battery is comparable to my G2 which I was very happy with. As you can see from the screen shots it's pretty good.View attachment 3365068View attachment 3365069
Sent from my ASUS_Z00ADA using Tapatalk
Click to expand...
Click to collapse
so does this mean your device is running on CN firmware? so maybe the biggest culprit for battery drain in WW is google playstore and other gapps, because CN firmware didnt preinstalled with gapps..

corrsea said:
I just received my phone this morning. it's a CN model. I charged it to 100%. Played a bit with it at work when I had the chance. I've spent the rest of the evening setting it up. The latest update is sitting waiting for download but I won't take it until tomorrow. I want to see how it goes overnight.
Even given the short time I've had it I'm pretty sure the battery stats are simply misreported and the poor battery life that some people are experiencing are down to individual setups or faulty devices. I've done nothing yet to conserve battery other than turning off the stupid ASUS battery saver, deleting some Chinese bloat and setting Wi-Fi to switch off when screen is off. From what I can see battery is comparable to my G2 which I was very happy with. As you can see from the screen shots it's pretty good.View attachment 3365068View attachment 3365069
Sent from my ASUS_Z00ADA using Tapatalk
Click to expand...
Click to collapse
Trust me. The battery life is aweful and is not just down to user error. I've used many, many android devices set up using similar parameters. Wether android 5.0 is to blame or something else, it is not my user error causing my excessive battery drain.

SBFarooq said:
"33. Battery-Add Battery charging ready reminder feature: User could set battery level under charging to receive the reminder."
seems they have given up on fixing the issue therefore just adding an alarm to recharge the battery... not good!
Click to expand...
Click to collapse
Um, what issue are you talking about and why are you jumping to conclusions? Don't jump to conclusions. You literally have no idea what ASUS' intent is and why would you complain when our phone has received an update every 2wks so far?
---------- Post added at 02:53 PM ---------- Previous post was at 02:49 PM ----------
bobsie41 said:
Trust me. The battery life is aweful and is not just down to user error. I've used many, many android devices set up using similar parameters. Wether android 5.0 is to blame or something else, it is not my user error causing my excessive battery drain.
Click to expand...
Click to collapse
Um, even with Android OS battery usage at 21% and screen at 12%, according to batt stats screen, I still managed around 5.25hrs SoT.... With 32% battery left.
Granted this is just from last night to this morning and is mainly just Web browsing and playing some music (was up late couldn't sleep!). WiFi/Bluetooth/GPS/autosync on.I've frozen/disabled most pre-installed apps and services.

Glad to see updates with Google Voice, I've had some issues with outgoing calls not using voice.

I am not jumping to conclusions... Merely stating the obvious statement made by Asus... Secondly.. I believe in Asus and their commitment to this device .. But building up another wakelock is not the way to go IMO..

dasklney said:
I saw the update but they deleted it on their download support page for now.
Click to expand...
Click to collapse
Yup they removed it.
Posted using my phone.

jose makalolot said:
Yup they removed it.
Posted using my phone.
Click to expand...
Click to collapse
Yes, but you still can download with the old link

dasklney said:
Yes, but you still can download with the old link
Click to expand...
Click to collapse
Old does not work either.
Posted using my phone.

cangcan said:
so does this mean your device is running on CN firmware? so maybe the biggest culprit for battery drain in WW is google playstore and other gapps, because CN firmware didnt preinstalled with gapps..
Click to expand...
Click to collapse
Yes, that's why I'm running with CN for a while. I don't have to have google apps as system apps. Once I have a setup I'm happy with I'll back up and test it for a while with them moved to system to see if there is any difference. I'll then switch to WW and compare that. (I'll also pick up my google drive offer at that stage.)
It has lost about 3% overnight so it's heading for about 6 - 7 hours SOT. I'm guessing that that will drop to about 5 hours in normal use given other people's reports.
I've already ruled out the android OS in battery stats as causing any real drain. I've encountered this before with a previous device. All the manufacturer did was adjust the way battery stats was reported. There was no underlying bug to fix.
I'm taking things slowly and methodically with setup so if I do run into any real battery issues I should be able to easily identify the culprit(s).
I'll take the OTA some time in the next day or so and see how it compares. I'll feed back in this thread but I guess the WW update will be out by then.

jose makalolot said:
Yup they removed it.
Posted using my phone.
Click to expand...
Click to collapse
dasklney said:
Yes, but you still can download with the old link
Click to expand...
Click to collapse
jose makalolot said:
Old does not work either.
Posted using my phone.
Click to expand...
Click to collapse
they haven't deleted it... here is the direct link http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.19.40.16-user.zip
Source: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/

corrsea said:
Yes, that's why I'm running with CN for a while. I don't have to have google apps as system apps. Once I have a setup I'm happy with I'll back up and test it for a while with them moved to system to see if there is any difference. I'll then switch to WW and compare that. (I'll also pick up my google drive offer at that stage.)
It has lost about 3% overnight so it's heading for about 6 - 7 hours SOT. I'm guessing that that will drop to about 5 hours in normal use given other people's reports.
I've already ruled out the android OS in battery stats as causing any real drain. I've encountered this before with a previous device. All the manufacturer did was adjust the way battery stats was reported. There was no underlying bug to fix.
I'm taking things slowly and methodically with setup so if I do run into any real battery issues I should be able to easily identify the culprit(s).
I'll take the OTA some time in the next day or so and see how it compares. I'll feed back in this thread but I guess the WW update will be out by then.
Click to expand...
Click to collapse
Everything you have said is exactly what I said even down to the G2 similarities. I see no issue with battery in comparison to other android phones.
Sent from my ASUS_Z00AD using Tapatalk

Did it fix the notifications bug?

7. Fixed some BLE device can not auto reconnect
Click to expand...
Click to collapse
I hope this update fix the issue of my Mi Band can not auto reconnect

The file size is over 1 Gb, this OTA should be contain a lot of fixes... i hope ....

CN 2.19.40.16 is removed again from ASUS website. (https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/)
I guess it got some serious BUG that has made ASUS remove it
=============================
corrsea said:
I just received my phone this morning. it's a CN model. I charged it to 100%. Played a bit with it at work when I had the chance. I've spent the rest of the evening setting it up. The latest update is sitting waiting for download but I won't take it until tomorrow. I want to see how it goes overnight.
Even given the short time I've had it I'm pretty sure the battery stats are simply misreported and the poor battery life that some people are experiencing are down to individual setups or faulty devices. I've done nothing yet to conserve battery other than turning off the stupid ASUS battery saver, deleting some Chinese bloat and setting Wi-Fi to switch off when screen is off. From what I can see battery is comparable to my G2 which I was very happy with. As you can see from the screen shots it's pretty good.View attachment 3365068View attachment 3365069
Sent from my ASUS_Z00ADA using Tapatalk
Click to expand...
Click to collapse
Are you sure by TURNING OFF ASUS Battery Saver will Make this phone has a lot better battery life?