Related
Talk: 3.00 hours (180 minutes)
Standby: 180 hours (7.5 days)
Click to expand...
Click to collapse
Is the advertised battery life correct ... because i cant seem to get anywhere close to the standby stated hours. Is standby mode equal to shutting off your magician [ie. red button on right side]?
Anyways, with the screen on, but the backlight off, i can only get roughly 5-6 according to my battery indicator [battery pack pro]. Its even less if i use the pocket pc to play music
Just wondering if this is the norm, or should I try to get a new battery? Any tips to conserve precious battery life ... aside from dimming backlights?[/quote]
standy times are always absolute BS, no matter what phone they're plastered to :wink:
mine gets about 2 days use with few calls, about an hr of mp3s and perhaps an episode of the chaser's war on everything.
toomuchdogfur said:
mine gets about 2 days use with few calls, about an hr of mp3s and perhaps an episode of the chaser's war on everything.
Click to expand...
Click to collapse
damn, thats awesome.
(1) You just using the main battery? or do you also use the backup internal battery as well?
(2) How frequently are you charging? I mean, do you wait till you battery is low after 2 days to charge? or are you charging it every so often during those 2 days of use?
(3) What kind of battery indicator software or program are you using [if not the one already installed in settings/system/battery]?
(4) Do you leave your screen off or on when you arent using it?
...mine: 9 hrs. wmplayer playing with screen off and 1½ hrs internet browsing; standby? why should i?
Now i bought a 2400 mAh battery instead off 1200 and indeed it's doubled now...
(1) which backup internal battery?
(2) i'm charching as soon as it's below 10%
(3) i use batterymemstatus including overclock
(4) i prefer shutting off the screen especially to prevent touching any button by accident...
dream_sequence said:
toomuchdogfur said:
mine gets about 2 days use with few calls, about an hr of mp3s and perhaps an episode of the chaser's war on everything.
Click to expand...
Click to collapse
damn, thats awesome.
(1) You just using the main battery? or do you also use the backup internal battery as well?
(2) How frequently are you charging? I mean, do you wait till you battery is low after 2 days to charge? or are you charging it every so often during those 2 days of use?
(3) What kind of battery indicator software or program are you using [if not the one already installed in settings/system/battery]?
(4) Do you leave your screen off or on when you arent using it?
Click to expand...
Click to collapse
1: Just the main battery, the standard 1200mAH that comes with the Mini. btw you can't actually 'use' the internal backup battery - thats just there to prevent the data in your main memory from being wiped out if your main battery goes dry!
2: I usually charge when the battery drops below 20% (ie. the first 'low battery' warning) as if it drops below 10% then certain functions are disabled (accessing your SD card for example )
3: Resco Today Plugin, comes bundled with Resco Explorer. It uses the built-in battery monitor anyway, like most today screen battery monitor plugins.
4: Off. Backlight switches off after 30s of inactivity, screen off after 3 minutes, but I usually press the power button before I slip it back into my pocket.
I use PocketMusic for mp3s, which switches the screen off automatically after 30s (but still keeps playing!), and TCPMP for video - my videos are all encoded in XviD, which requires significantly less processing power than WMV (in TCPMP anyway) while keeping a good compression ratio, meaning less battery drain.
By the way! Make sure that in Settings > Connections > Beam that your PPC isn't set to recieve incoming beams... that can have a noticeable effect on battery life.
This weekend, when my battery got below the 25% mark after a long time of keeping it always between 40 and 100%, I noticed that my device suddenly went black while playing Sudoku.
After 1 minute I could switch it back on, presenting the boot screen. No data was lost. However, as soon as it gets to log on to the cell network, it would shut off again. I had to charge it to at least 30% to be able to get a cell connection again.
Would this be a sign of a dying battery?
Unfortunately yes, it's the start of the death spiral. :?
Mine was worst; my Mini would shut off suddenly at around the 40% level. Upon closer examination of the battery it appears a little bloated in the centre, so I guess all that accumulated heat from charging did kill my battery eventually.
I changed a new battery a few months back and could now go as low as 3% before the device shuts off.
Re: Battery Life - How long? Tips to conserve precious power
Krinkiespijer said:
Now i bought a 2400 mAh battery instead off 1200 and indeed it's doubled now...
Click to expand...
Click to collapse
Hey Krinkiespijer,
Where did you get hold of the 2400 mAh battery? Are they expensive?
Cheers,
James
I would bet ebay. ebay.com.au used to be swarming with 2400mAH batteries but they seem to have disappeared .
They are a bit pricey, but I still see a couple of them in ebay. But remember that they're quite large and your Magician wont fit into the stock case.
Also, try tools such as Pocket Hack Master which allow you to underclock the CPU, consuming less power. You can also use em to set CPU speed based on process usage.
Hi to all of you,
I am using the SPB mobile shell 2.0 (http://www.spbsoftwarehouse.com/products/mobileshell/?en) on my official WM6 HTC touch cruise and see a hughe battery drain problem !
Can anyone tell me if this battery drain also occurs using WM 6.1 rom?
Thanks a lot for your help!
Dag
No battery problem on my Cruise (bepe 0.58, SPB Mobile Shell 2.0, 3G).
how long last your battery please?
mine last 2days max is it normal or not?
thx
2 days is pretty much OK under normal use of the phone with some calls, 20 min WiFi and 10 min GPS. Also depends on how much you play around with the phone. The display sucks a lot of power
With a clean fresh install (hard reset) my battery goes to 0% WITHOUT USING THE PHONE in 48 hours !!
DO you find it normal as well?
With SPB mobile shell installed it is even quicker (about 36 hours) !
Dag
Try to use "Advanced Configuration Tool" to enable:
- SD Memory power managment
- AsyncMac1 power managment
- PPTP1 power managment
- L2TP1 power managment
Alo problems may be usage of 3G connection or Push Email
I use WM6.1 bepe .58 and Mobile Shell 2 and have no battery drain problem.
daghood said:
With a clean fresh install (hard reset) my battery goes to 0% WITHOUT USING THE PHONE in 48 hours !!
DO you find it normal as well?
With SPB mobile shell installed it is even quicker (about 36 hours) !
Dag
Click to expand...
Click to collapse
Your TC possibly is defective ..... ( or your battery ) ..
With Black Widow Skinny wm6.1 & SPB mob. Shell v2 my TC lasts for 2.5 days.
(medium use of phone, wifi & radio) ....
im also noticed power drain increased.im using battery status and monitoring cpu and power all the time. before installing spb ms 2.0 normal drain was 37-40 mah(light off),cpu 0-2, after install everything was ok,but next day power drain become around 90! nothing else changed. Uninstalled this nice thinny and back to normal.
Timekiller Pro said:
im also noticed power drain increased.im using battery status and monitoring cpu and power all the time. before installing spb ms 2.0 normal drain was 37-40 mah(light off),cpu 0-2, after install everything was ok,but next day power drain become around 90! nothing else changed. Uninstalled this nice thinny and back to normal.
Click to expand...
Click to collapse
I have done the same test using battery status and my measurements where: lights off 31-48 mA (avg: 33 mA) and with full lights on: 120-135mA. I use spb shell 2 on WM6.1 for a week now and had no problems.. The battery usage depends on many factors. But two days while phone is in suspend mode is not good.
AG_Uni said:
I have done the same test using battery status and my measurements where: lights off 31-48 mA (avg: 33 mA) and with full lights on: 120-135mA. I use spb shell 2 on WM6.1 for a week now and had no problems.. The battery usage depends on many factors. But two days while phone is in suspend mode is not good.
Click to expand...
Click to collapse
Dear Uni, 33mA means that your battery lasts for 1350/33 = 40.91 Hours.
Less than 2 days.....
With 120 mA current flow your battery lasts for 1350 / 120 = 11.25 Hours ...
If your cell provider has no good signal in your area, then
current flow is about 60 - 70 mA . Your battery lasts for 1360 / 65 = 20.76 Hours ...
So you realize that power consumption depends on many factors ....
swtos said:
Dear Uni, 33mA means that your battery lasts for 1350/33 = 40.91 Hours.
Less than 2 days.....
With 120 mA current flow your battery lasts for 1350 / 120 = 11.25 Hours ...
If your cell provider has no good signal in your area, then
current flow is about 60 - 70 mA . Your battery lasts for 1360 / 65 = 20.76 Hours ...
Click to expand...
Click to collapse
40.91 hours while mobile is continuously is on (with backlight turned off) I think it’s pretty good! Also the reception is less that 50%...
Do you mean 60-70mA while device is in suspend mode? or with display on without backlight?
AG_Uni said:
40.91 hours while mobile is continuously is on (with backlight turned off) I think it’s pretty good! Also the reception is less that 50%...
Do you mean 60-70mA while device is in suspend mode? or with display on without backlight?
Click to expand...
Click to collapse
60-70 mA while display is on & backlight at level 4/10 .... mobile reception 0-1/4 bars.
I'd like to say that power consumption depends on many factors ....
My experience with mobile shell would suggest that you look at the weather options, particularly at the download of weather maps. These maps are large downloads which keep the HSDPA engaged and busy. If you are seeing the 'H' symbol connected then your TC is actively downloading. I found the battery drain to be corrected by not selecting the option to automatically download weather maps. (perhaps this applies to your experience)
Well, i'm getting about 4-5 days worth. In these days: 20mins calls, some sms'ing, WiFi 15mins, GPS 10mins, e-book reading 20mins.
Display at setting 2 (1-4: no BL to full BL), WiFi at medium performance and only switched on when i use it, hsdpa and BT switched off.
Are you guys having the same issue with the cooked 6.1 rom ???
Does 6.1 consume less power or is there no change between wm6 and wm6.1??
Dag
Hello,
I am using MossiROM V2.1 GER, also tried Touch V4.01 WM6.1 editions. My battery lasts only 1.5 days. I talk about 30 min, 15min WIFI daily. I also use SPB Shell 2.0.
I dunno but the battery seems to last better when I was using WM6.0.
But while in standby battery cunsomption seems to be 21mAH.
I using Bepe 0.66 ROM and have 75mA with 4/10 backlight, full GSM bar and nothing in background.
When I used GPS, calls and other stuff my device lived over 1 day from 100 to 4-5.
Just measured with BatteryStatus:
1. Standby (no light, power off) - 5 mA
2. Power On (light on 4/10, no BT, no WiFi, nothing) - 77 mA
3. Power On (the same but light off) - 65 mA
4. Call (full bar of GSM net) - 200-220 mA
5. GPS on (light, GPStest) - 200mA
UPDT.
On original O2 ROM I have follow result:
1. Standby (no light, power off) - 5 mA
2. Power On (light on 4/10, no BT, no WiFi, nothing) - 51-62 mA
3. Power On (the same but light off) - 33 mA
4. Call (full bar of GSM net) - 180-190 mA
4.1 Call (light off) - 163 mA
4.2 Call (light 0ff, sound) - 202 mA
4.3 Call (screen off, sound) - 140 mA
5. GPS on (light, GPStest) - 190mA
It mean, ROM from Bepe more suck battery.
UPDT2.
Test result of BlackWidow show the same result as original ROM.
Henry_Lee said:
I using Bepe 0.66 ROM and have 75mA with 4/10 backlight, full GSM bar and nothing in background.
When I used GPS, calls and other stuff my device lived over 1 day from 100 to 4-5.
Just measured with BatteryStatus:
1. Standby (no light, power off) - 5 mA
2. Power On (light on 4/10, no BT, no WiFi, nothing) - 77 mA
3. Power On (the same but light off) - 65 mA
4. Call (full bar of GSM net) - 200-220 mA
5. GPS on (light, GPStest) - 200mA
UPDT.
On original O2 ROM I have follow result:
1. Standby (no light, power off) - 5 mA
2. Power On (light on 4/10, no BT, no WiFi, nothing) - 51-62 mA
3. Power On (the same but light off) - 33 mA
4. Call (full bar of GSM net) - 180-190 mA
4.1 Call (light off) - 163 mA
4.2 Call (light 0ff, sound) - 202 mA
4.3 Call (screen off, sound) - 140 mA
5. GPS on (light, GPStest) - 190mA
It mean, ROM from Bepe more suck battery.
UPDT2.
Test result of BlackWidow show the same result as original ROM.
Click to expand...
Click to collapse
has anyone come across a bepe's ROM that would have about the same battery consumption as the Black Widow?
thanks in advance lads
Well, On a fresh install, all programs going (save for spb mobile shell (tried both 2.0 and 2.1)) i was getting about 40 hours. with spb mobile shell i was gettin 11-12. that's huge. i noticed shell32.exe is constantly running-doing what, i don't know. but i see a definite battery drain.
Take notice that when you are using any HTC device with SPB Mobile 2.0 or 2.1 and you are roaming the battery drain in fast Lasts only 6 or 7 hours with very low phone use.
With the HD2's pretty short battery life compared to my previous HTC phones, and also as I was a bit bored , I decided to have a look at how much the different systems drain in the HD2, and did some tests.
So for anyone interested, here are the results:
Base consumptions: (pick the one that suits your situation)
Standby, phone on, WIFI+BT off, no connections active: 5mA
Processor running idle, screen off, connections as above: 55mA
100% CPU usage (Coreplayer benchmark), connections as above: 315mA
USB connected, connections as above: 125mA
Additions: (add this to the base one depending on what you have on)
Connections:
BT on, idle: +1mA
Wifi on, idle: +5mA BUT!! If you enable wifi during standby (with BsB Tweaks or the WifiNoStandby CAB), the processor does NOT go to standby
anymore, so the base needs to be the 55mA above!
Connected to EDGE, idle: not measureable
Connected to 3G, idle: +4mA
Beware those 2 will occasionally and unpredictably send data every now and then, so this doesn't necessarily mean much.
BT transfer (file copy through ActiveSync, 120kB/s, CPU usage ~2%): +80mA
Wifi transfer (file copy with Wifi Remote access, 1MB/s, CPU usage ~3%): +200mA
EDGE/3G transfer: Pretty impossible to measure due to so many variables, but can be extreme (total current consumptions of 850-1150mA, so very approximative 500-800mA draw from the data connection during page loads are common!), and leads to most of the energy draw when using the net a lot. EDGE uses more power than 3G, consumption is higher when network coverage is lower, bad network throughput or congestion also mean lots of retries/overhead and less effective data transfer, using power for a longer time until the data is finally there.
Memory access (large file transfer):
Internal read/write through ActiveSync (speeds 2.5 / 2.1 MB/s respectively): +20mA / +130mA
Card read/write through ActiveSync (speeds 3.2 / 2.7MB/s respectively): +25mA / +40mA
Card read/write in USB disk mode (speeds 7.5 / 5MB/s respectively): +40mA / +45mA
Backlight:
10%: +65mA
20%: +78mA
30%: +90mA
40%: +105mA
50%: +121mA
60%: +136mA
70%: +154mA
80%: +170mA
90%: +190mA
100%:+210mA
GPS:
+95mA
Flashlight (with HTC Flashlight):
Level 1: +32mA
Level 2 (same as camera flash on): +107mA
Level 3 (same as camera "bright flash during shot"): +530mA
And remember the battery capacity: 1230mAh
So with this you can calculate your battery life for various activities. For example:
- Playing a video with full backlight: Let's say the video is well encoded (30% CPU use, for example 720x400 1Mbps DivX), that's about 150mA base, + 210mA backlight = 360mA, resulting in about 3h20 battery life.
- Same at night with only 40% backlight: Life goes up to about 5h!
- Wifi during standby for an 8h night, or a program that somehow prevents the phone from entering standby: 60mA or 55mA respectively, draining about 40% of the battery during that time.
- GPS program, with 70% backlight: Let's assume 150mA for the processor as it has some work to do, 90mA for the GPS, 154mA for the backlight = 394mA, or 3 hours.
- Music through wired headphones, screen off: the 55mA base plus a little 5mA as MP3 decoding is nothing for the CPU = 60mA or 20h.
- Same with a BT headset, with about half the BT bandwidth: 60+40 = 100mA or 12h
etc.
Charging
[EDIT 14.04.10]
This is now a dedicated section as I did some more thorough charging tests.
So, as some of you might know, the HD2 has 2 charging "modes".
- One is USB, that is used if the phone is connected to a PC, or an unknown device. In this mode, the current the HD2 will draw from the port/charger is limited to approx. 470mA, to stay within the maximum of 500mA a USB port can supply.
- The other is "dedicated charger", which is recognised on the original HTC charger (and some others, it's becoming a standard for a "dedicated charging USB port") by shorting of the 2 data pins of the USB connector in the charger.
USB charge
Important to know, during USB charge, the phone will NOT go to sleep, as it's supposed to be connected to a PC, and be running either ActiveSync, Disk drive mode, or modem, and in all 3 cases would be expected not to shutdown. So not only the current supplied to the HD2 is low, but the phone draws some of it for itself, leaving very little for actual charge - so expect loooong charge times.
USB charge with screen on (backlight dimmed, 10%): 285mA
USB charge with screen off (standby): 345mA (which shows the processor still runs and draws the "base USB" current)
Dedicated charger
When used with a charger that has the 2 USB data pins shorted, such as the original charger, the HD2 will draw a current that is proportional to the voltage on the USB power lines. To measure this I have used the original supplied USB cable, a variable regulated power supply, USB socket (with data pins shorted), and 2 meters for voltage/current. Voltages are measured at the "PC" end of the USB cable, so not taking account of losses in the USB cable. Will talk more about this later on.
Current vs Voltage diagrams are attached. Charge current is proportional to voltage, linearly until it reaches the max charge current, approx 830mA. This was measured so that the only draw is charge. If the phone is turned on while at max charge current, it will draw extra, until it reaches about 980mA, and will then stop to respect the 1A rating of the stock charger.
Now, to the influence of USB cables. I initially had some trouble with inconsistant numbers, phone only drawing 670mA from the stock charger, i.e matching neither the ~350mA from USB, or ~830mA from stock charger in "normal" condition. Turns out that to make it more convenient on my workplace I was using an USB extension between charger and HD2 cable. It was a $2 extension I bought on Dealextreme. Removing it solved the problem... and after making those measurements I poked with it again. Turns out that at 1A current, the voltage drop in the extension (which by the way isn't longer than the HD2's USB cable) was 1.8V! Yep, nearly 2 Ohms for a 1.5m extension! Couldn't believe it.
I have a cheap Chinese microUSB cable that wasn't as bad,but still significantly more resistive than the stock one, hence me noting I used the stock cable for my tests. So, quality of the cables, extensions, adapters IS important! Note the phone correctly reaches full charge current a little bit under the 5V USB spec, so everything is well tuned.
Now, important to know, Most 3rd party chargers will not have the 2 USB data pins shorted, and will thus result in the same behavior as mentioned under USB charge, the processor will also be running continuously drawing the "base USB" current.
It is often possible to modify 3rd party chargers by opening them and shorting the pins, speeding up charge. The voltage/current curve behavior is actually helping there, because thanks to it if the charger is overloaded its voltage will most likely fall a bit, and the HD2 will thus draw less and find a nice balance point. This DOES NOT mean there's no possiblilty of damaging the charger, but all 3 I modified did well. One that was really weak resulted in not much more current being drawn after the mod than before (i.e voltage fell very low, approx. 4.4V), however the gain from not having the processor running like in USB mode still sped up charge a little.
Thank you, that is one useful chunk of comprehensive information
Could you please explain the exact measuring method for these tests?
40% backlight at night is a tough example tho, Lumos on my device is set to 10% for 0 sensor value, and only because I can't set it to lower than 10%... nice to know battery drain goes up twice from 10% to 60%!
Also, 100% is usually really necessary under direct sunlight, in a normal lit room probably 40% backlight is more than enough to watch a video... all in all, with your superinteresting info, the battery doesn't look like lasting "too short" now, but more or less "the right amount considering the battery capacity".
My iPaq 210 has a 2200mAh battery, just to make a comparison... that's why I could go for 8 hrs during some bus trips while watching tv series, and I just needed to swap battery and used a little of the second one.
What's your estimate of the drain caused by activating push email? I've recently been doing some rather crude experiments myself, and one provisional conclusion is that push email on a hotmail account uses a lot more battery than push email on an Exchange server.
Excellent stuff, you are to be congratulated.
I have a long held theory and I wonder if you are in a position to to test it?
I believe that battery consumption is greatly increased when an app is run from mem card and would be intrigued to see a comparison between an install to this as opposed to phone mem.
Any chance?
Battery levels
I found that power consumption of the battery got even worse after I went to Rom 1.66.707.1. However, after a few days, I let it run all the way out, switched back on, it ran out after a few minutes. Then after an overnight charge I found the battery (on standby) only went down by about 10 -12 % in 24hrs. I'm hoping this performance will continue.
What did you use for the testing?
pa49 said:
Excellent stuff, you are to be congratulated.
I have a long held theory and I wonder if you are in a position to to test it?
I believe that battery consumption is greatly increased when an app is run from mem card and would be intrigued to see a comparison between an install to this as opposed to phone mem.
Any chance?
Click to expand...
Click to collapse
That would be reasonable as reading from an external media will need energy to access its contents... still, once the app files have been loaded into the device's RAM, it shouldn't matter much
You could also test by comparing:
1) copy say 30mb from one location to another of the internal mem
2) copy from microsd to microsd
3) copy from mem to microsd
4) copy from microsd to mem
ephestione said:
Could you please explain the exact measuring method for these tests?
Click to expand...
Click to collapse
Simply using the built-in current sensor, getting the reads from AEBPlus battery information screen, and methodically turning things on/off once the others are evaluated and can be subtracted from the total reading.
ephestione said:
40% backlight at night is a tough example tho, Lumos on my device is set to 10% for 0 sensor value, and only because I can't set it to lower than 10%...
Click to expand...
Click to collapse
Really? You should force the backlight off then
I love bright images myself, so even in my bed in total darkness if I watch a video or photos I'll force 100% backlight I have Lumos set to force 100% for Coreplayer, Resco Photo manager and HTC album
Of course not for browsing or just messing around, in that case it's 20% for me
Shasarak said:
What's your estimate of the drain caused by activating push email? I've recently been doing some rather crude experiments myself, and one provisional conclusion is that push email on a hotmail account uses a lot more battery than push email on an Exchange server.
Click to expand...
Click to collapse
That's one thing I'd have no idea about... I've never used push email at all. And that's "standby usage", so hard to evaluate, as you never know when it kicks in.
Measuring that would need to be done on a long time. I'd say to leave your phone one night with push email off, one night with Exchange only, and one night with hotmail only, and then check the difference, preferably with a battery at about 80% charge at the start (mine seems to fall from 100% to 90% in a few minutes before becoming more regular, so I'd say the top of the scale isn't that reliable).
And I should really try push email once, that would be nice, but I *think* I have no provider that can do it for me... well I have a gmail account I never use, I should try to see if I can have it check my usual 3 mail accounts, aggregate and push... never really looked into that stuff.
pa49 said:
Excellent stuff, you are to be congratulated.
I have a long held theory and I wonder if you are in a position to to test it?
I believe that battery consumption is greatly increased when an app is run from mem card and would be intrigued to see a comparison between an install to this as opposed to phone mem.
Any chance?
Click to expand...
Click to collapse
Thanks
Well I'd tend to refute that theory, because when I tested the BT and Wifi in use I tried read from internal memory, write to internal, read from card and write to card, and all 4 were identical. I should have mentioned it indeed, but I was mostly interested to seeing if reads (wifi/BT "sending") and writes (wifi/BT "receiving") would have an influence on consumption, which wasn't the case, as well as whether the throughput was different, which wasn't the case either.
But I've done a few more tests, see the updated first post
One intersting thing is firstly that when the HD2 is connected to USB, the current draw grows significantly, so I've made a new "base consumption".
Next, the card is actually faster than the internal memory both in reads and in writes, tested both through activesync for consistency. Writing to the internal memory eats a LOT more than writing to the card. Reading from the card eats a little more than reading from internal memory, probably evens out as the reads are shorter due to faster transfer rate.
I've added some charging tests as well. Apparently, even if the phone "disconnects" from USB when turned off, the processor still runs and uses about the "USB connected" base current.
kilrah said:
Simply using the built-in current sensor, getting the reads from AEBPlus battery information screen, and methodically turning things on/off once the others are evaluated and can be subtracted from the total reading.
Click to expand...
Click to collapse
d'oh aebplus has a battery information screen, checking it right away In that case you'd have to take into consideration aebplus' current absorption anyway... which is not measurable as you cannot check the current intake of aebplus without aebplus being running
I have the cab on the sd already, but didn't install if after noticing that didn't work for button assignments with later versions of the rom... does it work for you on that side? I used the program all the time on my previous ipaq because it was oh so useful but never got around to notice it had a battery info subsection.
Really? You should force the backlight off then
Click to expand...
Click to collapse
Wouldn't have much sense doing it in the dark would it (admitting it's possible altogether on the HD2!)
But I actually used my oooold casio cassiopeia, about 7 years ago, with backlight turned off, while reading ebooks with speed reader plus during train trips, as the neon lights created a reflection good enough on the display so that I didn't need backlight...
in the end, the backlight died altogether and until I bought a new device, I managed to use it with light turned off
A flashing LED (incoming SMS warning, e.g.) seems to add consumption of 1-3mA.
Running FlexMail in background with a push service (IMAP IDLE) adds up to 30mA.
ephestione said:
does it work for you on that side?
Click to expand...
Click to collapse
AEBPlus works fine for me yes... but I don't have a "latest version" ROM AFAIK. I don't like WM6.5.x new softkey arrangement, so I'm staying with 6.5.
Anyway more about Push, I configured that through gmail yesterday, and it works just fine. I left it on during the night, and this morning I had lost 8% battery. So it's pretty much negligible. I received 2 e-mails during the night and was on 3G network.
this is a nice topic! i am interested in how much extra it uses when you are playing a MP3 with the build in HTC app?
maybe it would be a nice idea to make a program that outputs results like you pasted fast and easy (something like a benchmark app) so we can test different rom's fast? too bad i cant write anything otherwise i would try..
OK, seems MP3 uses 120mA screen off, both with Sense player and Coreplayer, so:
Processor running idle, screen off base + 65mA
But it seems to make some pretty big "jumps" once in a while. Maybe they both decode ior fetch from memory by "batches"...
my test,
HD2 rom 1.66
with BT on and BT off (configured but no connection to headset) difference in consumption is 60mA .!
BT is draining my HD2 .!
kilrah said:
OK, seems MP3 uses 120mA screen off, both with Sense player and Coreplayer, so:
Processor running idle, screen off base + 65mA
But it seems to make some pretty big "jumps" once in a while. Maybe they both decode ior fetch from memory by "batches"...
Click to expand...
Click to collapse
OK, I can't confirm the BT issue. Did you observe over a long period of time? The "quiet" current for MP3 I seem to get is 185mA with screen on and backlight at 10%, but sometimes it will climb to 280-320mA for a moment and go down again, both with BT on and off. With screen off for a while it seems to stabilise at the "quiet" level.
BTW, it seems that Advanced task manager isn't reporting CPU usage levels properly. Does someone know of a CPU monitor that works correclty on the HD2?
Yup. review over multiple 6 mins. all baseline(3g/brightness) setting the same. resetting each time for off on BT.
kilrah said:
OK, I can't confirm the BT issue. Did you observe over a long period of time? The "quiet" current for MP3 I seem to get is 185mA with screen on and backlight at 10%, but sometimes it will climb to 280-320mA for a moment and go down again, both with BT on and off. With screen off for a while it seems to stabilise at the "quiet" level.
BTW, it seems that Advanced task manager isn't reporting CPU usage levels properly. Does someone know of a CPU monitor that works correclty on the HD2?
Click to expand...
Click to collapse
Another consideration:
Data connection sucks power when used actively. Badly. As mentioned in the OP I haven't made comprehensive tests due to low monthly allowance, but I've had a look during normal use.
I'm pretty regularly doing 1hr train rides, during which I will be listnening to music , and browse the net at the same time. It's usually bright, so backlight will probably be at 70%. Signal is relatively low most of the time, on EDGE, inbetween small towns. When I'm on a "static" page (reading an already loaded page), current drain varies between 250 and 350mA.
But while loading a page, it will easily soar to 800mA+. Considering it takes 30-60 seconds to read a page, 20 to load a new one, and repeat... you can quickly see that this kind of usage leads to serious drain... in less than 2 hours the battery would be dead.
So be aware of how much power data connection will use. It's directly proportional to the amount of transferred data, and the worse the reception the more power it uses.
I should try using opera mini again, like I was always doing on my Kaiser. I never noticed excessive drain with it, but opera mini easily divides traffic by a factor of 10...
Just wanted to report that the new version of the superuseful BattClock has now a builtin battery current output, even if it's not really update once per second... seems more like one every 10 seconds.
I get ~240mA playing fullscreen stretched Frasier in lowest backlight (but that's with the keypad leds turned on all the time, I don't know why they don't go off, and I don't have keypadledcontrol installed... so that's a problem), and I get a total 630mA with HTC flashlight at maximum.
Good news! Bye bye Batti
Normal about the refresh time, the sensor only updates every 20 secs or so.
Some new considerations I posted somewhere else but should have put here.
After some time the HD2 seems to have better battery life, but usually it's not your battery lasting longer, it's just you not spending your day playing with the thing anymore.
It's always the same thing, the more a device can do, the more you do with it. On my first 1h train journeys after getting my HD2, I was able to kill 50% battery in 1hr. My first thought was "wow, with my Kaiser I would only use like 15%!!"
But then I took a second thought. I used 50%, but I was browsing the web, in bad reception areas, while listening to music the whole time. With my Kaiser, I'd put music on, check 3 webpages, then put it on the tray with just MSN connected and just pick it up to read/type a message once in a while.
On a next trip, I "forced myself" to do the same with the HD2. Just checked the news for 5 mins, then only listened to music and picked up msn once in a while, plus an unexpected 10min phone call. Guess what? I've only used 20% battery during the trip this time
The "problem" is that browsing with the Kaiser was just painful, so I'd just check the news and put it away. On the HD2 it's so comfortable I forget it and just spend my whole trip browsing heavy pages, which obviously kills battery in no time...
exactly my thoughts and findings
Last week I found a thread which had an overview of the most phone functions, which their battery consumption in mAh.
I don't know if it was a recent or older thread, but I can't find it anymore
Does anyone have a clue?
"Base consumptions: (pick the one that suits your situation)
Standby, phone on, WIFI+BT off, no connections active: 5mA
Processor running idle, screen off, connections as above: 55mA
100% CPU usage (Coreplayer benchmark), connections as above: 315mA
Connections:
BT on, idle: +1mA
Wifi on, idle: +5mA
BT transfer (file copy through ActiveSync, 120kB/s, CPU usage ~2%): +80mA
Wifi transfer (file copy with Wifi Remote access, 1MB/s, CPU usage ~3%): +200mA
Backlight:
10%: +65mA
20%: +78mA
30%: +90mA
40%: +105mA
50%: +121mA
60%: +136mA
70%: +154mA
80%: +170mA
90%: +190mA
100%:+210mA
GPS:
+95mA
Flashlight (with HTC Flashlight):
Level 1: +32mA
Level 2 (same as camera flash on): +107mA
Level 3 (same as camera "bright flash during shot"): +530mA
And remember the battery capacity: 1230mAh"
C/P from some thread here, i'm lazy to find it now
SWINXNL said:
Last week I found a thread which had an overview of the most phone functions, which their battery consumption in mAh.
I don't know if it was a recent or older thread, but I can't find it anymore
Does anyone have a clue?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=632684
Try that one.
Is there a program for that? Like for example Android has built in app that shows what % of battery was used by display, apps, radio, ...
Is there similar program for winmo?
rp-x1 said:
http://forum.xda-developers.com/showthread.php?t=632684
Try that one.
Click to expand...
Click to collapse
Thanks! .
Many battery-life-tips mentioned here DON'T need any modifications to your Z.
Please don't post discouraging things like...
-"Why all the fuzz? Buy a external battery"
-"Why BLunlock/undervolting/-clocking/rooting and voiding warranty?"
...we all know that.
There are many factors influencing screen-on-time. Please read the must-read-section before you judge my thread.
THIS THREAD IS ABOUT OPTIMIZING BATTERY LIFE OF THE SONY XPERIA Z WITHOUT SACRIFICING TOO MANY FEATURES OR MUCH OF USER EXPERIENCE/PERFORMANCE. THIS IS A UNFINISHED ONGOING PROCESS.
Don't forget: If you like what you read, please press the thanks-button.
TABLE OF CONTENTS
I. INTRODUCTION
I.1 Prologue / Must read
I.2 My average usage pattern
I.3 Change-Log
I.4 To-do
II. BATTERY SAVING TIPS
II.1 General-section (tips everyone can apply)
II.1.1 Tips I use
II.1.2 Tips I don't use (but you can)
II.2 Root-section (additional: tips for rooted devices)
II.2.1 Tips I use
II.2.2 Tips I don't use (but you can)
II.3 Bootloader-section (add.: tips for bootloader-unlocked devices)
II.3.1 Tips I use
II.3.2 Tips I don't use (but you can)
III. MISC
III.1 Thanks to
III.2 Translations
III.3 Results
I. INTRODUCTION
I.1 Prologue / Must read !
Hi everyone,
First I should introduce myself a little: I'm from germany, 24 years old and currently studying technology of information systems. Since xda helped me alot, I also want to share with you all I know about optimizing battery life.
A XZ with all-standard-settings (without my tips) currently only gets approx. 4,5-5 h with my average usage pattern. And max. 3,5 hours with heavier usage (while travelling e.g.). With heavy games even less.
After implementing my tips I often get 7h+ of REAL USAGE battery life (=screen-on-time = SOT =s-o-t) with my Xperia Z. Sometimes I even get more SOT: see e.g. my screenshots of 7:09 h SOT with remaining 6% and 20 hours since last charging. But I also sometimes only get 5 hours (with heavier usage, while travelling e.g.).
I'm not bragging, please do not misunderstand me. If we crippled all smartphone-features, turned everything off and only read books with the XZ, we could even get 9-10 hours SOT...but thats not what I want to achieve!
There are many factors influencing screen-on-time: Your individual usage, your individual apps, your apps' (obligatory) wakelocks, your cell/data/wifi receiption during the day, provider-support of fastdormancy, your XZ's undervolt capability, ...
Also everyone has his own taste:
Some like 1.5 GHz+4cores+100% brightness all day+5 homescreens+... And some don't.
I only write down ALL tips I know/find. I do not use every single one of them, because some would lower my comfort. But I write them down for you, because I respect everyones individual usage. So please don't blame me for everything or talk bad about my thread in other threads.
You can decide which tips you like to use, which you don't.
Greetings
Seb
I.2 My average usage pattern
- browsing a lot with dolphin browser (sonar etc. disabled with elixir; 'Google Chrome' consumes too much battery, causes many wakelocks and has no flash-support)
- reading hundrets of tech-news with gReader (almost all news include pictures and some videos; hardware acceleration on)
- listening to music with walkman (20 min/day)
- watching some youtube (at least 3-4 videos; each 2 to 15 min long)
- reading for about half an hour (with kindle app or adobe reader)
- usung tapatalk for xda a lot
- whatsapp a lot
- reading many mails with KAITEN MAIL (many include pdf) and let synchronize 2 of 4 email accounts every 3 h and the remaining 2 every 6 h
- sms: 1/day
- calls: 20min/day
- photos: 2/day
- using wunderlist
- checking ebay: 1x/day
- VNC to enter business-pc remotly 2x/day (5-10 min)
- a lot 9gag
- Widgets on 2 homescreens:
4x Kaiten Mail-Widgets (counters for unread emails)
1x Walkman-Widg.
I.3 Changes to this post
31.12.13
- corrected formatting
27.12.13
- Updated and added many new tips to bootloader section (e.g gpu-undervolting!)
- Updated and added many tips to root section
- Updated general section slightly
- Updated prologue slightly
- Updated usage pattern slightly
- NEWS1: Switched to XzKernel by alnikki25k because it currently offers more features, runs smoother and gets updated more frequently
- NEWS2: Lifted my max. cpu-freq from 1.24 to 1.35ghz, which won't effect battery life too much anylonger ( -15 min SOT)
Earlier changes: deleted because of limited space
I.4 To-do
- add measurement-section
- give some milliampere-values
- Shorten all sections/texts/tips
- Find the holy grail of battery life saving
II. BATTERY SAVING TIPS
II.1 General-section
II.1.1 TIPS I USE:
- Update to Android 4.2.2 (currently use stock-sony-firmware .67), but will switch to 4.3 as soon as we get a working custom kernel for it
- if contract has no LTE/4G, so set the network mode to wcdma/gsm (the LTE/4G-chip sucks a lot of battery (better disable it, if you don't need more than the 21 Mbit/s 3G/hsdpa+ provides)
- If you can choose: use Wifi over 3G over LTE (in general). But if 3G connection is fast and wifi very slow, use 3G! Avoid LTE/4G if you do not need more than 21 Mbit/s.
Use "ONLY 2G" only if 3G receiption is extremly poor and as slow as 2G, but 2G receiption is great.
- stamina on (only whatsapp whitelisted). Reset stamina mode if it doesn't work properly (clear cache). Stamina is (mostly) better than turning phone off several times per day, because boot consumes too much battery (especially if many apps load at boot).
- battery settings > battery save mode: on (from 100%; excluding wifi+auto sync)
- wifi set to not search for networks/no notification,
- wifi set to stay always on (turning off during standby will help battery, but every custom kernel has an issue with the wifi drivers, so set wifi to "always on" which circumvents this issue),
- Brightness set automatically to 25% during the day and 0% in the evening with my TASKER-profile (below). more info in root-section.
- NFC off (only on when needed)
- Bluetooth off (only on when needed)
- GPS off (only on when needed)
- charging at 6-10% remaining battery (below could harm your battery and decrease battery life over time...but this is a highly controvertial topic, so I charge at 10% to be on the safe(r) side)
- Reduce wakelocks:
- Install 'Wakelock Detector' to find partial wakelocks and alarms which wake the XZ during standby. Many unnecessary wakelocks can easily be reduced (like fastdormancy). But some may need root access. Here is a very helpful link for wakelocks: http://forum.xda-developers.com/showthread.php?p=38629490#post38629490
- In settings > apps > all apps > select an app: Deactivate the notifications of all apps you don't want to be notified by. Can reduce wakelocks!
- Turn OFF 'developer settings' when not using it (stops their services, wakelocks)
This section will grow in time!
- Google Now off: long-press on home-button > google search > settings > turn google now off
- Let your Wifi-Router always work with 100% signal-power, wifi g+n. This way you will get better wifi-receiption with your Z (might squeeze some minutes/your phone won't connect to data unnecessarily)
- Don't overprotect your phone with metal cases over metal cases Receiption of Cell, 2G/3G/LTE, Wifi, Bluetooth etc. will decrease and your battery life too (a lot)
- Turn Restore & Backup off: settings > restore & backup
- Google Settings App > Location > Turn OFF: Location history + location protocol /summary(? don't know the english name of that button)
- Google Settings App > Search > Turn OFF: Webprotocol + search-results shall not include apps/... (deactivate anything you don't need)
- Deinstall or deactivate FACEBOOK, if you don't use it. If you really need it, change the notification settings + update settings + push-settings according to your REAL needs. This app is a hugh battery consumer and it causes far too many wakelocks which will prevent the phone from entering sleep modes (even when the phone is not being used).
- Settings > Sound(?) > Turn OFF: vibration when touching screen + sound for every screen press + sound for unlocking + xloud + sound for call-buttons
- Settings > Accounts > Google > Turn OFF: google-personalized-advertising + every synchronization you don't need (I don't sync apps and google books because I use Titanium Backup)
- Often forgotten but basic tip: Search for unnecessary settings or battery saving features in the settings of your favourite apps. E.g. many apps allow to deactivate unnecessary settings or ugly special effects/animations which drain battery. OR many apps let you deactivate (maybe in your case: ) unnecessary push notifications...
- Settings > Display > Sleep > After 1 Minute (mostly sufficient)
- Update your apps regularly, because new versions often improve performance, battery drain, wakelock-issues etc. Still: make backups!
[/HIDE]
II.1.2 TIPS I DON'T USE (but you can):
- Display brightness always at 0%
- Wifi set to "save battery when connected" (may cause problems with some custom kernels, so I currently don't use it!)
- Data/cell/wifi/bluetooth always off (e.g. if you only play games/read books)
- Calibrate your battery (this can bring back 5-10% of your battery life, depending on its condition). This tip was discussed a lot. I didn't calibrate my Zs battery yet. Everyone says something different and the manufacturers like sony give instructions for (first) battery cycles... So I leave it up to you to decide if its a myth or not
- Set all animations in dev-settings to 0 x (settings > about phone > press 10 times on the built-number > go back and now you got the dev-settings below)
- Sleep screen after 15 sec
- Turn background sync and auto-sync and google account sync OFF
-Reduce every wakelock possible by spending hours for finding their causes, deinstalling/deactivating all thats necessary to reduce it...etc...
II.2 Root-section
II.2.1 TIPS I USE
- Installed TITANIUM BACKUP PRO and deleted all bloatware/google apps/..
All I didn't need or like or which drained too much battery.
Here is a list of all deleted apps:
com.android.providers.partnerbookmarks.res.overlay
com.sonyericsson.android.socialphonebook.res.overlay
com.sonyericsson.trackid.res.overlay
com.sonymobile.connectivitycenter
Sapphire 10.0.A.0.16 (com.sonyericsson.bluetheme)
Silk 10.0.A.0.16 (com.sonyericsson.blacktheme)
VerifyCertificatesDummyApp
Xperia Twitter Setup
com.sonymobile.datadisclaimer
Anonymous Usage Stats
com.sonymobile.cameraautoupload
Backup-Restore
com.sonyericsson.lockscreen.uxpnxt
Black Hole
Bubbles 1.0
com.android.backupconfirm
com.android.providers.partnerbookmarks
com.android.sharedstoragebackup
com.google.android.voicesearch
com.sonyericsson.unplugchargerreminder
Converter 6.1.1 (com.sonyericsson.androidapp.converter)
Device Usage 1.0.A.0.11 (com.sonymobile.phoneusage)
E-Mail 4.0.1 (com.android.email)
com.sonyericsson.retaildemo
Emerald
com.sonyericsson.music.wikipediaplugin
com.sonyericsson.music.youtubeplugin
com.sonyericsson.music.youtubekaraokeplugin
com.sonyericsson.music.googlelyricsplugin
Exchange Services
Face Unlock 4.1.2-509230 (com.android.facelock)
foursquare 2012.03.09 (com.joelapenna.foursquared)
Infinite view 10.1.A.0.0 (com.sonyericsson.infiniteview)
com.sonyericsson.androidapp.memorycardinstaller
Market Feedback Agent
Mono 6.1.A.0.1 (com.sonyericsson.android.pobox.skn.mono)
com.sonyericsson.metadatacleanup
OMA Client Provisioning
Oma Download Client
OmaV1AgentDownloadServices
Picasa Uploader
Pico TTS
POBox Touch
Quartz
Remote Control Service
com.sonyericsson.vendor.backuprestore
SkinSelector
Smart Connect
com.android.voicedialer
Tags
TalkBack
TrackID
Update Center
com.sonyericsson.verifycertificatesdummyapp.application
com.sonyericsson.verifycertificatesdummyapp.platform
com.sonyericsson.verifycertificatesdummyapp.shared
com.sonyericsson.advancedwidget.weather
Wfd Service
Woody
Xperia AppShare
Xperia Calendar Sync
Xperia FB Setup
Xperia Friends’ Music
Xperia Link
Xperia Music Likes
com.sonyericsson.facebook.proxylogin
com.sonymobile.twitter.account
Xperia Share
Xperia Social Engine
com.sonyericsson.socialengine.plugins.facebook
com.sonyericsson.socialengine.plugins.picasa
com.sonymobile.socialengine.plugins.playmemories
com.sonymobile.socialengine.plugins.facebook_sharefrwk
com.sonymobile.socialengine.plugins.twitter_sharefrwk
com.sonyericsson.androidapp.everchwallpaper
Google Chrome
+ all branding-/carrier-specific apps
- Installed ELIXIR2 and deactivated all kinds of entries I don't need. Examples of activities/receivers/services you can disable:
BE CAREFUL:
If you deactivate vital activities/services/receivers of an app the apps won't work properly anylonger or the app will crash. But thats no problem! Just check the apps and and activate activities/services/receivers e.g. one-by-one to find the cause of the crash and leave it activated.
Deactivate e.g. every ACTIVITY that says (differs from app to app):
-facebook.login
-.analytics.
-.tracking.
- google.ads.AdActivity
- .googleplus.
- .gtalk.
-.ads.
-.voicesearch.
And all kinds of RECEIVERS that will boot apps at boot (if not necessary):
-.onboothandler.
-.bootreceiver.
-.devicestartup.
And SERVICES:
-again: .analytics.
-.gtalk.
-googleplus.
- Install GREENIFY+donation-version (needs Xposed Framework!). Then activate all experimental options like boost mode, gcm push, greenify system apps...
and after that greenify some system apps like google maps etc. (according to your needs)
- Installed Xposed Framework and following modules:
1. "Greenify" (donation-version necessary) and activate all options
2. "BootManager". Deactivate all apps you don't want to load when starting up
3. "ReceiverStop" (if you didn't like Elixir2): Deactivate all unnecessary receivers
4. "App Settings": reduce permissions if necessary
5. "Per App Hacking": prevent services and wakelocks, but becareful...
It can cause apps to not work anymore!
6. "YouTube AdAway": especially helpful fot those watching alot. Why drain battery for ads?!
- Installed TASKER and SECURE SETTINGS (and its helper; see settings).
I currently automated following things (you can also download my tasker-backup below):
Tasker is consuming little power in the background, but is a powerfull tool.
My Tasker-Profile isn't very sophisticated. Working on it, but don't want to use other peoples profiles. You can deactivate/change any feature easily in tasker, if you don't want to use it:
- 18:00 until 08:00 o'clock (6PM till 8AM): Brightness set to 1% (in the evenings 1% is enough mostly and reduces consumption by a high margin) + Turn Rotation off
- Rotation only ON with certain apps and automatically turn off
- Hibernate with Greenify every 3 hours (sometimes the built in autohibernation of greenify won't work, so tasker triggers
- GPS ON when GOOGLE MAPS, NAVIGATION start and turn OFF automatically when closed
- Turn OFF Data when connected to Wifi since 5 Minutes
- Install BuiltProp Editor and add these lines to the end of the built.prop:
(Thanks to …… for this tip):
#signal tweak
ro.ril.enable.3g.prefix=0
ro.ril.enable.dtm=0
ro.ril.hep=0
ro.ril.hsxpa=5
ro.ril.enable.a53=1
ro.ril.gprsclass=12
ro.ril.hsupa.category=9
ro.ril.hsdpa.category=36
____
This will increase receiption by lifting 2G/3G-settings. It increases battery consumption, but over the day the better receiption makes up for that (at least for me).
II.2.2 TIPS I DON'T USE
- ELIXIR2 is hardcore...you could even deactivate EVERY button/activity/service (those which you asume you won't ever need) of all your apps...could save some processing time and therefore battery life
-Installing ES EXPLORER and deleting in the apps-folder:
fast dormancy.apk and .odex ( both ONLY if your provider doesn't support fastdormancy)
-Reducing Wifi-consumption by editing the ini-files in etc/firmware/wlan/prima/
-Reducing 2G/3G/LTE-consumption by editing their ini-files
-With Overlays (App) we can make buttons/switches hovering over apps. In some cases it could save battery (especially in combination with tasker and zoom).
-I tested wether the LTE-Switch for the upper menu will switch back the network mode to "GSM" (=2G) if I activate and then deactivate LTE... Worked! The LTE-switch turns on 2G+3G+LTE but my contract doesnt have LTE so maybe the LTE-chip won't consume anything after a first connection attempt... Then the LTE-switch would effectivly be a 2G/3G-switch for me Update: Switching back and forth is uncomfortable and automation isn't possible without deep rom-modifications... a dead end currently
II.3 Bootloader-section
II.3.1 TIPS I USE:
- Flash @alnikki25k 's custom stock kernel XzKernel
- In TRICKSTER MOD + FAUXCLOCK (!!) do following:
0. Set CPUs to 384 mhz - 1,35 ghz
1. Governor to intellidemand (settings: see below)
2. Set scheduler to 'sio'
3. Underclock the GPU to 325mhz and set gpu-scheduler to "ondemand"
4. Multicore power saving = 0
5. Dynamic FSYNC = on
6. Ecomode = on
7. Mp-decision = off
8. Intelli-plug = on
9. ZRam = off
9.1 Delete VFS cache after boot: on
9.2 Auto FS Writeback: on
9.3 swappiness: 0%
9.4 vfs cachepressure: 150%
9.5 dirty ratio: 20%
9.6 dirty background ratio: 5%
9.7 TCP congestion control: westwood
10. Read_ahead (emmc + sdcard): 2048 mb
10.1 Entropy (emmc + sdcard): off
11. Frequency Lock = on
12. In faux clock: activate c0, c1, c2 and c3 states
13. IMPORTANT TIP FOR SMOOTHNESS: Deactivate gpu's vsync (activate it if you are a egoshooter-gamer)
14. In faux clock: Set a profile for every app which does (or does not) need much performance. Here is an examples:
'Whatsapp' doesn't need high cpu-freq and 400 mhz gpu-freq to run smoothly. We can set a profile for it with these settings:
Min freq: 384 mhz
Max freq: 1188 mhz
gpu freq: 200 mhz
ecomode: on
FOR GAMES you could e.g. slightly overclock frequencies, turn ecomode off and use 450 mhz gpu-freq
14. CPU: Undervolt to these VOLTAGES (ONLY IF YOU KNOW WHAT YOU ARE DOING !!) :
Please ONLY undervolt when you already know all about it...and undervolt slowly (in -25 or -50 mV steps e.g.)
until you reach a stable new voltage for each frequency. Always test several times with benchmarks and all your apps and for 1h at least
MY (VERY LOW) VOLTAGES MIGHT NOT WORK FOR YOUR XZ !
MAKE BACKUPS BEFORE YOU TRY ! IF YOU DON'T HAVE ACCESS TO A PC: KEEP A ROM AND A KERNEL ON YOUR SD-CARD. ALSO MAKE BACKUPS WITH CWM
I assume everyone trying this will know about
the dangers of playing with voltages.
*
[Mhz : sony's standard mV : mV working properly for my Z ]
192 : ---- : 712
384 : 850 : 712
432 : 875 : 712
486 : 875 : 725
540 : 900 : 725
594 : 900 : 725
648 : 925 : 750
702 : 925 : 750
756 : 975 : 750
810 : 975 : 800
864 : 1000 : 800
918 : 1000 : 825
972 : 1025 : 850
1026 : 1025 : 875
1080 : 1075 : 900
1134 : 1075 : 912,5
1188 : 1100 : 912,5
1242 : 1100 : 935
1296 : 1125 : 962,5
1350 : 1125 : 975
1404 : 1137 : 977,5
1458 : 1137 : 987,5
1512 : 1150 : 1025
-Governor-Settings (BE CAREFUL):
As the intellidemand governor got a big update (but almost no descriptions for the new features/settings), here you get my latest settings:
Governor = intellidemand
____
freq_step = 15
enable_boost_cpu = 1
input_event_min_freq = 384000,384000,384000,384000 // #
down_differential = 8 // #
ignore_nice_load = 0
io_is_busy = 1
optimal_freq= 1350000 // #
powersave_bias = 0
sampling_down_factor = 9 // #
sampling_early_factor = 9 // #
sampling_interim_factor = 9 // #
sampling_rate = 50000 // #
smart_each_off = 0
smart_high_slow_up_dur = 5
smart_high_slow_up_freq = 1350000
smart_slow_up_dur = 5
smart_slow_up_freq = 1350000
smart_slow_up_load = 90 // *
smart_up = 0
step_up_early_hispeed = 1242000 // #
step_up_interim_hispeed = 1242000 // #
sync_freq = 810000 // #
two_phase_freq= 384000,0,0,0
ui_sampling_rate = 50000
ui_timeout = 100
up_threshold = 86 // *
up_threshold_any_cpu_load = 90 // *
up_threshold_multi_core = 93 // *
_____
If its laggy for your taste:
1. make sure its no thermal issue or related to the rom itself;
2. Turn these ( // *) down. And these ( // # ) up. But search for their meanings first!
-GPU: undervolting (ONLY IF YOU KNOW WHAT YOU'RE DOING!):
Easiest way I know (until fauxclock/trickster support this feature):
Install "universal init.d", choose any available init.d-script (custom kernels often flash some along the way), add following in it and save:
echo "930000 1000000 1100000" > /sys/devices/system/cpu/cpu0/cpufreq/gpu_mv_table
The numbers (e.g. 930000) are in uVolt for See alnikki25k 's XzKernel-Thread for more info! I highly recommend reading that first!
Becareful: after flashing a new kernel(-version) this added code will likely vanish.
If you know how: just make your own init.d-script, wait for fauxclock/trickster
or just readd it manually again
II.3.2 TIPS I DON'T USE (but you can):
- Thanks @Destroyedbeauty: Instead of using apps like fauxclock/trickster mod you could also just write your own init.d-scripts which would cost nothing and lead to slightly less battery drain (+5 min). I don't use this tip YET, because these apps really don't consume that much. Still a very clever tip!
III. MISC
III.1 Thanks to
People I need to thank for various reasons (in no special order):
@DooMLoRD
@alnikki25k
@gm007
@[NUT]
@Dsteppa
III.2 Translations
I'm very thankful for everyone helping me translate this thread!
(Don't forget: translations can't be always up to date and won't be monitored by me)
-French-Forum (thanks to @monsieur_debile):
http://forum.frandroid.com/topic/16...-plus-de-7-heures-dautonomie-en-écran-allumé/
III.3 Results
-Antutu Benchmark 4: Instead of approximativly 20500 points (standard Z) I currently get approx. 15000. I currently give a damn about benchmarks Will try to improve in the future as promissed
RESULTS WITH REAL USAGE (For those who think I only leave the screen on):
- with my average usage pattern (see beginning of post) in "one sit" I got 7h S-O-T with 10% left battery charge and 9 hours since last charge: See screenshots.
- With my average usage pattern (see beginning of post) on a NORMAL day going to office etc. I got 7:09 h screen-on-time with 6% charge left and 20h since last charge: see screenshots.
- (almost) ONLY reading books, xda, news with gReader, surfing and with a bad phone receiption all day(!) I got 8h screen-on-time with 3% charge left and 12,5 h since last charge.
- Playing Deadtrigger for 0,5h I lost 14% battery life (graphics set to high), so with a full charge I approximativly could get 3,5 h (consider: Deadtrigger isn't optimized very well for non-nvidia-tegra3-hardware so it uses the Z inefficiently and I played with 'high' graphic settings)
If you like what you read: press the thanks-button and rate my thread with 5 stars
One question: Was this done indoors. Like in your room or office, just sitting playing with the device?
And that was a short "stint", I mean 7 hours of screen and 8 hours since the last charge. If you counted idle times, in like a 15 hour stint, screen time would be greatly reduced, plus, if you commute the phone is constantly looking for antennas, thus reducing screen time further.
7 hours is great. But this seems to be on "ideal conditions".
As for my methods of saving battery? 2G all the time. Undervolt. No Underclock. Greenify. Stamina Whatsapp only.
The important question is, what have you been doing ? Did you play games? YouTube? Or did you just let the screen active?
Gesendet von meinem C6603 mit Tapatalk 4 Beta
sea2605 said:
Since xda and its forum helped me alot in many ways, I also want to share something with you, that might solve many users biggest complaint: battery life.
I optimized my battery life so I regularly get 7 hours of battery life (sometimes even more, see screenshot with 10% remaining battery at 7:00h screen on time)... and all that with very normal usage (but no games) and without any sacrifices for me.
Tried many (...!!) methods to optimize but sticked only with those truly making a difference after testing.
________________________________
!!
I'm going to update this thread regularly until I wrote down all details and until I stop optimizing battery life
Lets work together: Tell me your battery life tricks!
Maybe in some weeks/months we can get to 8-9 h of battery life without too large sacrifices
!!
________________________________
HOW I did it (roughly summed up for the moment):
0. Updated to 4.2.2 (no 4.1.2 didn't give me more battery life).
1. Bootloader unlocked (essential, but will void warranty).
2. Rooted
3. Flashed doomkernel v9 via fastboot
4. Installed kernel tuner and underclocked the cpus to 1,24 ghz, changed governor to ondemand,
Undervolted like this (phone is still veeeery fast! No perfomance issues!):
Coming soon
5. Installed titanium backup pro and deleted all sony bloatware/google apps/other apps... All I didn't need or like or which drained too much battery. Here is a list of all deleted apps etc.:
Coming soon
6. Installed elixir2 and deactivated google-ad- and/or google-analytics-entries in all of my apps. Also all features I didn't need in my apps (e.g. I dont want to share everything in.every app with facebook so I deactivated those entries).
I deactivated all voicesearch-entries as I don't like it yet...(Even apples siri isn't great yet in my opinion...maybe in 2-3 years . I also deactivated google now-entries (not google-search!) since it drains a lot and I don't need it.
7.
X. Rather standard things:
- My contract has no LTE so I set the network mode to wcdma/gsm,
-stamina mode on (only whatsapp whitelisted),
- battery save mode on (from 100%; excluding wifi and auto sync),
- wifi-location-based on,
- wifi set to not search for networks,
- wifi set to stay on during standby only when connected (turning off during standby might help some of you, at least those who don't look at/need their phone and need it to be instantly connected),
- Wifi set to save battery
- To be continued
________________________________
I see more potential (but some with sacrifices):
1. With Tasker (thats an app) you could get a little (or quite much) extra battery life (depending on what you are willing to sacrifice...)
2. Future doomkernels could allow for more finetuning of the cpu and gpu (e.g. gpu-underclocking hat sticks; maybe we have some luck and we could undervolt the gpu )
3. elixir2 is hardcore...you could even deactivate EVERY button/activity/service (those which you asume you won't ever need) of all your apps...could save some processing time and therefore battery life
4. Governor wheatley and optimizing it's governor settings would give more juice but it slows all too much down in my opinion...but can lead to +0,5 h!
5. Even further killing some wakelocks with betterbattery
6. Reducing tx of the Wifi-antenna (but reducing tx only helps while downloading, I guess...)
or other antennas...
7. Installing es explorer and deleting fast dormancy app and odex ( both only if your provider doesn't support fast dormancy) in the apps-folder
8. Underclocking min. Frequency to 192 mhz (might help +5-10 minutes but slows phone down a little)
9. Maybe a little further undervolting (+5-10 min, but stability might be a problem...)
10. To be continued
THIS IS NOT READY YET...please wait patiently for more details etc!
Lets work together: Tell me your battery life tricks!
Click to expand...
Click to collapse
I easily get 8+ hours of screen-on time....my tricks for that are as follows,,
1)Root(obvious )
2) download greenify (a must-have by oasis feng)and greenify almost all apps(including games) expect some messaging apps(apps shown with gcm logo in greenify) ,,,and if you want to get that lil extra minutes then go for the donation version of greenify, it lets you greenify some system apps to....also don't kill apps with appkillers(real battery hog)
3) Switching Stamina mode On(especially after the 4.2.2 update)...and carefully selecting only "most needed" apps to be excluded (if you don't want to break notifications)
4)download startup manager..and disable all unwanted apps at startup
5)remove all unwanted bloatware and battery saving apps(they usually do nothing to save your battery,instead they run in background and eatup your battery)
6) no under-clocking, no over-clocking
7) maintain a healthy battery charge history ( don't charge unless battery is less then 20%.,,then charge without interrupting to 100%(don't keep it charging for to long if it reaches 100%,,this will over-charge the battery)
8 ) If you're on 4.2.2 ,,surely you're facing the battery bug,which is really dangerous for the battery (because it bring the battery % down to zero ,without giving you a chance to reach your charger)....So to fix this you'll need to recalibrate your battery by downloading easy battery calibration from playstore (I've calibrated my battery and fixed the bug )...the app will guide you how to calibrate the battery(easy)
9 ) Don't use the "trickle charging" method recommended by some battery saver apps...I've used that method and it shows no improvement in battery life instead it'll drain the battery in a very strange manner ("modern"Li-on batteries should not be trickle charged Google it if you need more info on this subject)
Use this tricks and you'll definitely notice improved juice
More tweaks and tricks for a better battery going to be updated soon(as soon as I'll test and confirm them)...
If you feel that I've helped you in any way,,please hit the thanks button
Sent from my Xperia ZL (C6502) using Tapatalk 4 Beta
Point nr 6 is not true. Best for batery is when working between 50-85%. Battery will not overcharge because phone turn off charging, when battery reaches 100%. You can charge phone even when reaches 90% or 60%. Dont have to wait till 20% (sooner pluged - better for battery).
Sorry for bad english. Regards...
Media Server
Place a ".nomedia" file in directories of your sdcard(s) you don't want scanned so media server doesn't suck all the battery!
Grenify works but not sure about the effectiveness of startup manager. Apps disabled seem to load at startup regardless.
adielee said:
Place a ".nomedia" file in directories of your sdcard(s) you don't want scanned so media server doesn't suck all the battery!
Grenify works but not sure about the effectiveness of startup manager. Apps disabled seem to load at startup regardless.
Click to expand...
Click to collapse
Once you grant root access to startup manager it disables all the apps you've selected not to start at the startup...try it for yourself
If you feel that I've helped you in any way,,please hit the thanks button
Sent from my Xperia ZL (C6502) using Tapatalk 4 Beta
Rumman Shaikh said:
I easily get 8+ hours of screen-on time....my tricks for that are as follows,,
1)Root(obvious )
2) download greenify (a must-have by oasis feng)and greenify almost all apps(including games) expect some messaging apps(apps shown with gcm logo in greenify) also don't kill apps with appkillers..
3)download startup manager..and disable all unwanted apps at startup
4)remove all unwanted bloatware and battery saving apps(they usually do nothing to save your battery,instead they run in background and eatup your battery)
5) no under-clocking, no over-clocking
6) maintain a healthy battery charge history ( don't charge unless battery is less then 20%.,,then charge without interrupting to 100%(don't keep it charging for to long if it reaches 100%,,this will over-charge the battery)
Use this tricks and you'll definitely notice improved juice
Click to expand...
Click to collapse
Sure you get 8 hours screen on time with only that and a normal usage (see my average usage)? If yes: I'm an idiot... why did I even bother with all the other crap
adielee said:
Place a ".nomedia" file in directories of your sdcard(s) you don't want scanned so media server doesn't suck all the battery!
Grenify works but not sure about the effectiveness of startup manager. Apps disabled seem to load at startup regardless.
Click to expand...
Click to collapse
nomedia is a great idea ! Will try it ! :good:
ckyy said:
The important question is, what have you been doing ? Did you play games? YouTube? Or did you just let the screen active?
Gesendet von meinem C6603 mit Tapatalk 4 Beta
Click to expand...
Click to collapse
Updated my first post! See "average usage pattern" on that single day.
DrKrFfXx said:
One question: Was this done indoors. Like in your room or office, just sitting playing with the device?
And that was a short "stint", I mean 7 hours of screen and 8 hours since the last charge. If you counted idle times, in like a 15 hour stint, screen time would be greatly reduced, plus, if you commute the phone is constantly looking for antennas, thus reducing screen time further.
7 hours is great. But this seems to be on "ideal conditions".
As for my methods of saving battery? 2G all the time. Undervolt. No Underclock. Greenify. Stamina Whatsapp only.
Click to expand...
Click to collapse
In some way you could say I tested in ideal conditions as I tested only in "one sit", right (weekend, got bored; but see my
usage pattern...great battery life considering that). But nevertheless:
Roughly we can say, all these methods aggregated will give everyone at least 40-60% more battery life (in relation to their
previous battery life). Thats no exaggeration...UnderVOLTing alone will lead to approx. 15-25% more battery life
...thank @DooMLoRD and his kernel for that!
So someone who only got 4h with his very own usage pattern will now get 6h.
Someone who only played games will get 3 h instead of 2 h...
Someone with a similar usage pattern to mine will get 7 h instead of 4,5 h (my starting point when I bought it)
etc. pp.
EDIT:
even on a normal workday (not "one sit") I get 7+h screen on time and 20 hours since last charge and 6% remaining battery. See my post of 2. August !
I didn't find an option to stop searching for Wifi networks, but I installed an app from google play to automatically turn off wifi when not connected, disbled NFC because I never used it, installed Juice Defender to disable 3G when I don't need it, used greenify on most of my apps, lowered brightness a bit and underclocked and I see some substantial improvement right away.
thanks for sharing your undervolt settings, might try later.
sea2605 said:
Sure you get 8 hours screen on time with only that and a normal usage (see my average usage)? If yes: I'm an idiot... why did I even bother with all the other crap
nomedia is a great idea ! Will try it ! :good:
Updated my first post! See "average usage pattern" on that single day.
In some way you could say I tested in ideal conditions as I tested only in "one sit", right (weekend, got bored; but see my
usage pattern...great battery life considering that). But nevertheless:
Roughly we can say, all these methods aggregated will give everyone at least 40-60% more battery life (in relation to their
previous battery life). Thats no exaggeration...UnderVOLTing alone will lead to approx. 15-25% more battery life
...thank @DooMLoRD and his kernel for that!
So someone who only got 4h with his very own usage pattern will now get 6h.
Someone who only played games will get 3 h instead of 2 h...
Someone with a similar usage pattern to mine will get 7 h instead of 4,5 h (my starting point when I bought it)
etc. pp.
Click to expand...
Click to collapse
Yes,,I'm really getting great screen times(one thing in my favour is that we don't have LTE here in India,& I use a 2g network(since I've a great lan ) so I've disabled wcdma network type & selected only gsm) I even play some graphic intensive games for "sometime" in my normal usage ...see the attached screenshot for details of my usage... Also I would like to add that the switching on the stamina mode is a must(mainly after the 4.2 update) But I'm still trying to squeeze even some extra juice...will update with some more extra tweaks,, after I try them out
If you feel that I've helped you in any way,,please hit the thanks button
Sent from my Xperia ZL (C6502) using Tapatalk 4 Beta
Ill rather use the charger then unlock the bootloader and spend numerous more hours just to get a couple of extra hours screen time as if its a competition lol.
Seriously I can get 6 hours+ screentime with stock 4.22 rom, no root, no bootloader unlocking.
Wifi on, auto sync on, brightness at lowest, stamina on. All I do is read a book from amazon kindle app, lol.
Well, of course no one has to chase maximum battery life... I'm chasing for it out of curiousity... Its only a challenge
But along the way I learn something new about android, smartphone-architecture, linux, ... Might someday be useful (I'm about to study technology of information systems)
Thats all forums/xda/communities exist for: Learning something new and sharing your knowledge
My undervolt goes from
192mhz @ 662mV to 1512mhz @ 975mV on Doom's Kernel.
On FXP Kernel I could go lower. 650mV to 950mV. Although even at those voltages, battery life on CM or AOSP is like 30% lower.
rotkiv3451 said:
I didn't find an option to stop searching for Wifi networks
Click to expand...
Click to collapse
Bump for op. How did you do that?
Turning of that it stops searching for wifi networks.
Now that I arrived home I can write my whole voltage list:
192 mhz @ 662 mV
384 mhz @ 675 mV
432 mhz @ 700 mV
486 mhz @ 700 mV
540 mhz @ 712 mV
594 mhz @ 712 mV
648 mhz @ 737 mV
702 mhz @ 737 mV
756 mhz @ 737 mV
810 mhz @ 787 mV
864 mhz @ 787 mV
918 mhz @ 837 mV
972 mhz @ 837 mV
1026 mhz @ 887 mV
1080 mhz @ 887 mV
1134 mhz @ 912 mV
1188 mhz @ 912 mV
1242 mhz @ 937 mV
1296 mhz @ 937 mV
1350 mhz @ 962 mV
1404 mhz @ 962 mV
1458 mhz @ 975 mV
1512 mhz @ 975 mV
Tested throughout 3-4 weeks. Rock solid stability.
There is a way to know beforehand if your chip can go as low voltages as this:
http://forum.xda-developers.com/showpost.php?p=39373866&postcount=124
First entry is deactivating the intervall-searching for wifis, as far as I can tell
sea2605 said:
First entry is deactivating the intervall-searching for wifis, as far as I can tell
Click to expand...
Click to collapse
I don't think so. As far as I can understand, that option just activates or deactivates the notification for open wifi networks, not the wifi scanning.
Sent from my C6602 using xda app-developers app
mikii100297 said:
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
I'm not a big fan of not charging the phone every day. If I leave home with less than 100% chances are I don't feel confortable.