Related
I hooked up an ammeter from my XPERIA's battery to my Xperia to monitor battery levels. You can use this information so you know what is sucking the most power from your phone and what you can close to prevent it and what ever.
Set up:
Phones Specifications:
X1i
ROM: R2A (Vodafone UK)
Official Sony Ericsson Battery
Remember: 0.1 Amps = 100 mA/milliamps
Current Settings:
Screen Backlight: 50%
Phone: On
-Signal: (H) + 1 Bar
Wifi: Off
Data Connection: On
Location: Home Screen (No plugins)
Power Consumption: 0.10 Amps
With the same settings as above i will open programs and record the power used:
Windows Media Player (Playing a movie, full screen, full volume): 0.33/0.32 Amps
Windows Media Player (Playing music at full volume (screen on)): 0.31 Amps
Windows Media Player (Playing music at full volume (screen off + headphones)):0.07/0.08 Amps (Is that low or what! - Thats like being idle at the today page with the screen on)
Core Player (Playing the same movie, full screen, full volume): (Movie Unwatchabe because of low frame rates, same movie but since core player has no hardware acceleration) 0.30/0.31 Amps
Scrolling up and down with Programs file: 0.29/0.3 Amps
Send/Recieve in outlook - (Aol Email): 0.45 to 0.49 Amps
Turning on the Wifi and then returning to the home screen Idle: 0.14 / 0.16 Amps
*Turned Wifi Off after last test*
Bluetooth On (idle): 0.11 Amps
Bluetooth Sending file (10.5 MB Music File):0.22 Amps
Bluetooth Recieving file (10.5 MB Music File): 0.26/0.28 Amps
Making A phone call:
Screen on: 0.34/0.28 Amps
Screen off:0.19/25 Amps (Thats about 7.5 hours talk time)
Drawing in the notes application: 0.28 Amps
Playing Bejewelled: 0.25 / 0.3 Amps
**NEW CHANGES**
Screen Backlight: Lowest
Phone: On
-Signal: (G) + 4 Bars
Wifi: Off
Data Connection: On
Location: Home Screen (No plugins)
Power Consumption: 0.07 Amps
**NEW CHANGES**
Screen Backlight: 30% (Usually around this when auto brightness is on)
Phone: On
-Signal H (2 Bars)
Wifi: Off
Data Connection: On
Location: Home Screen (No plugins)
Power Consumption: 0.08/0.09 Amps
**NEW CHANGES**
Screen Backlight: Lowest
Phone: Off
Wifi: Off
Data Connection: Off
Location: Home Screen (No plugins)
Power Consumption: 0.06 Amps
**NEW CHANGES**
Screen Backlight: 50%
Phone: On
-Signal: (G) + 4 Bars
Wifi: Off
Data Connection: On
Location: Home Screen (No plugins)
Today Scren (No Plugins)(Screen Turned Off): 0.01 Amps
PANEL TESTS (All at idle/not being used):
Today (No Plugins): 0.10/0.11 Amps
Today (SPB Pocket Plus): 0.11 Amps
Today (SPB Pocket Plus + Digital Clock): 0.11 Amps
Today (SPB Pocket Plus + Digital Clock) (Screen Turned off): 0.01 Amps
Today (SPB Pocket Plus + Digital Clock + G-Profile):0.11 Amps, sometimes goes to 0.16 Amps
Today (SPB Pocket Plus + Digital Clock + G-Profile) (Screen Turned off):0.1 Amps, sometimes goes to 0.4 Amps
SE Panel: 0.14/0.15 Amps
Media Panel: 0.27 Amps
3D Fish Panel: 0.28 Amps
On-The-Road: 0.27 Amps
SPB Mobile Shell 2 (pre-installed): 0.11 Amps
Point UI Home 2: 0.19 Amps
Google Panel: 0.10/0.11 Amps
SPB Mobile Shell 3 Build:6411 (Lifestyle Page): 0.10/0.11 Amps
SPB Mobile Shell 3 Build:6411 (Professional Home): 0.09/0.10 Amps
SPB Mobile Shell 3 Build:6411 (Screen Off): 0.01 Amps
TOUCH FLO 3D:
Touch Flo 3D (Home Screen): 0.11/0.16 Amps
Touch Flo 3D (Music - Playing at full volume): 0.35 Amps
Touch Flo 3D (Music - Playing at full volume with headphones attached and screen off): 0.9 Amps
More Programs:
TomTom Navigator - Couldnt Connect to GPS Satelite but Idle: 0.34 Amps
Opening "Windows" folder in file explorer (loading):0.25 Amps
Opera Browser (Loading eBay.co.uk): 0.46 Amps to 0.53 Amps
Opera Browser (Idle on eBay.co.uk): 0.18 Amps
Internet Explorer (Loading ebay.co.uk):0.45 to 0.85 Amps
Internet Explorer (Idle on eBay.co.uk): 0.14 Amps
G-Profile (on homescreen with SPB Pocket Plus - set up with 1 profile to switch at a later time but using another): 0.11 sometimes goes to 0.16 Amps
G-Profile (on homescreen with SPB Pocket Plus - set up with 1 profile to switch at a later time but using another) (SCREEN OFF): 0.1 sometimes goes to 0.4 Amps
Watching a video on the Offical YouTube application - streaming over data connection0.46 Amps somtimes down to 0.38 Amps (after buffering is complete)
Parlingo0.27 Idle, 0.38 amps sending messages 0.38 to 0.40 Amps logging in
Windows Live Messenger 0.35 Idle, 0.40 Sending/Recieving
Coming Soon:
Auto Backlight (does depend on surroundings though so will record that):
Recieving Mail with everything else off:
I will add more over time!
Notes: I was pretty amazed by how little power is drawn by listening to music with the screen off - its less than being idle at the today screen with the screen on in windows media player.
And when using the data connection, that is what seems to suck a lot of juice, so those people who have they email check very frequently may decrease battery life by a lot
Thank you for carrying out such an informative research, dude!
Since you are on it, can you install HomeScreen plus plus and compare how accurate is the consumption reported by the software. http://www.chi-tai.info/cs_batterystatus_xda_neo_wm5_im_cs.htm
Would you consider trying "auto adjust backlight" among your valuable research criteria
Also, maybe G-Profile and bluetooth file transfer 1MB, 5MB
Thank you
Thanks for the info!! Can you also try loading something with Opera Mini and see if it eats less power compared to the other browsers? Thanks!
some really useful info here, thanks! just as DaHiA asked, could u try measuring it with auto backlight on vs. like 30%-50% brightness?
Yeah - i'll do all of those at some point
tnx for the info comeradealexi..
jackleung said:
Since you are on it, can you install HomeScreen plus plus and compare how accurate is the consumption reported by the software. http://www.chi-tai.info/cs_batterystatus_xda_neo_wm5_im_cs.htm
Click to expand...
Click to collapse
Just installed it and it is not very accurate - Its too low most of the time
comeradealexi said:
Just installed it and it is not very accurate - Its too low most of the time
Click to expand...
Click to collapse
Slow is expecting since it's polling the system too frequently would waste too many cpu cycle. But how accurate it is if we wait for let's say a 10 sec period?
Can you please test the following:
All apps Closed
Screen Off
GPRS On
(WiFi/BT OFF)
I'm interested in the power consumption when nothing is happening AND when Outlook is auto-checking E-mails (You can set Outlook to regularily check your e-mails).
And what would also be very interesting is power consumption of Garmin Mobile XT while navigating, with both screen off and on.
Thank you for your very helpful information!
Firefall! said:
Can you please test the following:
All apps Closed
Screen Off
GPRS On
(WiFi/BT OFF)
I'm interested in the power consumption when nothing is happening AND when Outlook is auto-checking E-mails (You can set Outlook to regularily check your e-mails).
And what would also be very interesting is power consumption of Garmin Mobile XT while navigating, with both screen off and on.
Thank you for your very helpful information!
Click to expand...
Click to collapse
well when checking for mail before it was around 50 and the screen takes up about 0.03 so i dont think it will be much less but i will check
also btw I dont have Garmin XT :S - do you know if it is free or not??
comeradealexi said:
also btw I dont have Garmin XT :S - do you know if it is free or not??
Click to expand...
Click to collapse
Garmin can be downloaded from here: http://www.garmin.com/support/collection.jsp?product=010-11034-00 However it needs a Key and a Map (I believe you can download 1 local map for free). I can give you the KG if you want to install it, but I don't want to cause you too much trouble. But the other thing with constant e-mail polling would be nice to know!
I'll download all these applications ready to test later today
@firefall: dw i'll get it working fully -
ALso this time i will take my test outside and test the gps and how much juice that sucks!
comeradealexi said:
I'll download all these applications ready to test later today
@firefall: dw i'll get it working fully -
ALso this time i will take my test outside and test the gps and how much juice that sucks!
Click to expand...
Click to collapse
Thank you Can't wait for the results!
Thanks for those great informations
amazing
GREAT WORK. if you add more info, it should be stickied as its really really useful to far too many people especially cookers
a few requests and questions that are worth doing if you can and if you have time
1- how did you do the setup. i would like to do the same
2- keep updaTING the first post
3- can you test mobile shell 3. many are complaining about battery life
4- can you do a youtube video so we get a better idea about the overall battey usage of applications.
5- can you test the diference between edge and HSDPA battery usage.
6- can you test with different roms.
7- can you test streaming youtube video with wifi/hsdpa/edge
8- at somepoint in the future you may want to test total power over
9- test with pushmail enabled/disabled
I've updated with a few more things - i'll get more - if you have any more requests then let me know
could you do tests when using parlingo, I always feel like my battery is dying extremely quickly when I have it running, thanks
A lot of problems are related to old batteries and when buying new ones you don't know how "new" they are and if the keep their promise.
Worry no longer, with just
mortscript
your device
your battery (or more)
and a spreadsheet (optional)
you can take control of the facts.
The method is descibed in this generic thread.
There you also find the files you need and some apetizers to start.
Method specific discussions go there please!
Please report here in this forum only the results of your measurements in the following format:
Battery type (Producer + Model)
Battery serial number
nominal capacity (in mAh)
your device (it should only be Typhoon/Amadeus here!)
rundown time to 10% capacity with the standardized conditions as descibed in the generic thread
attach the file if you like, but I will not collect them
My current drain measurement for the Amadeus is:
full lit display: 65 mA
dim display: 23 mA
display on, but no backlight: 5 mA (roughly)
display off: 2 mA (roughly)
Let me start with my data:
Code:
Type Battery Serial Battery Capacity [mAh] PBA File 10% time [s]
Samsung-ST26A 5t4x15a5004173 1150 Amadeus battery-data-1264807779.csv 47434
Samsung-ST26A 5yex149f000725 1050 Amadeus battery-data-1264933115.csv 44737
Samsung-ST26A 5yea14ak006610 1050 Amadeus battery-data-1264765340.csv 42025
Sanyo ST26C at3a35am000417 1150 Amadeus battery-data-1264875160.csv 50783
enjoy!
Hi,
Everyone might knew "Quadrant", app to benchmark our Android phone.
However, so far, there is no app to benchmark battery.
NONE!!!
The idea is quite easy. Run the battery benchmark app and show the result at the end.
It should not be too difficult, too bad I am not Android developer.
Anyone can take up the challenge? To be THE FIRST creator of battery benchmark for Android
Here is the basic idea for the app:
Start the app with 100% Battery life
Some options in the app (for features that might NOT be in an Android phone or might not be available at the time?):
[ ] Turn on Wifi
[ ] Turn on GPS
[ ] Turn on Bluetooth
Set the app to WAKE all the time, display turned ON all the time of the test
Set Keyguard to OFF (device will not be locked)
Set Brightness to AUTO
Set all speakers to SILENT
Set vibration to OFF
Then loop until battery down to 5%, perform the below tasks in sequence:
* Play movie for 15 minutes [speaker muted]
* Browse to website??? be careful not to overload the website
* Doing arithmatic (counting pi?) that increase to 100% CPU
* Doing 3D animations
* Play MP3 [speaker muted of course]
* File I/O
* etc.
As soon as the battery down to 5%, app stop and display result ...
"Battery Benchmark result: XX hours YY minutes ZZ seconds
And of course restore all the settings.
App should use generic and known to work Android API, not hack or proprietary library.
Anyone???
BE THE FIRST!
Good idea
In fact I am surprised this app hasn't been created yet.
We could imagine automatic tests to be conducted for 1 or 2 hours on a clean ROM (fresh install with no additional apps installed).
The tests could be such as:
- taking pictures
- playing a music file
- playing video
- standby consumption testing
- ...
Browsing could be tested but it depends a lot on wifi or Network infrastructure so it might not be a good idea to compare the results.
Every minute some data could be saved to then generate some graph:
- current (mA)
- Battery Voltage (mV)
- CPU freq
- Battery %
Of course the tests initial conditions have to be clearly established (screen brightness, wifi/BT/Network status...).
At early stage of development such an application could perform very simple tasks but would nevertheless be a great tool to compare ROMs in terms of consumption.
stability test from marked would do the trick. With 100 % battery run the app for 30 min and see how much power was used. You would probably not be able to compare with other users as kernel, modem(3g) and rom might differ.
ICS KERNEL TESTS - AOKP/AOSP/CM9
Netchip | Siyah | N.E.A.K | Thoravukk | Abyss | Fluxi
This thread is only intended for reference purposes to those using AOSP/AOKP/CM9 ROMS
Purpose
I conducted these tests in order to help all users of AOSP/AOKP/CM9 ROMS to have a reference base when flashing a custom kernel. In no way am I supporting you to do so and I will not be held accountable of any wrong doing resulting from your part. I know it's sounds harsh, but do not jump out there flashing kernels if you do not have the minimal knowledge about how things work. I will be posting up a few links to other informative threads in order to help everyone (a.k.a noobs) These tests are done through my own will and I spend quiet a lot of time writing these results in a presentable manner so everyone could benefit from this. If you do not like the way I do my tests or would like to share some improvements, please do so in a respectable manner. If you cannot follow this simple rule, I strongly advice you not to use this thread as a reference and I suggest you do your own test which would satisfy and meet your requirements.
How to flash a kernel?
There are different ways of flashing a kernel, but the one I use is through CWM, because I do not trust ODIN, simple as that.
Step 1: Download Kernel Cleaning Script if your coming from a different kernel and flash it before flashing the new kernel. If it's just an upgrade of the same kernel, wipe cache and dalvik before flashing.
*Using a Cleaning Script is not mandatory to flash a new kernel, it is just recommended to use it to make sure modules and such are cleaned for a fresh installation
Step 2: Flash desired kernel.
Step 3: Wipe Cache and Dalvik once kernel is done flashing.
Step 4: Reboot System.
*Hint: If you're having fc right after boot, reboot into recovery mode and try fixing permissions. It happened to me once, and after fixing permissions everything went back to normal.
How to flash back to stock kernel?
Step 1: Extract "boot.img" from ROM zip file
Step 2: Rename "boot.img" to "zImage"
Step 3: Place zImage in Internal Storage
Step 4: Use CWM app and flash "zImage" as kernel
If you're unsure of this method and do not want to try it because you're scared of doing something wrong, I'll post a flashable one for you upon request.
Kernel Cleaning Script
**Use these scripts at your own discretion**
GS2WiperV1.6
Does the following: (Bold are changes since V1.5)
1. Wipes cache+dalvik cache
2. Saves all current startup scripts to /sdcard/init.d_backup
3. Removes Voltage Control and NSTools startup scripts (only if saved as init.d, and not as a service) along with specific Siayh startup scripts from /system/etc/init.d
4. Removes old kernel-specific files (currently Void, Andoidmeda, Siyah and NEAK are cleared)
5. No longer removes modules (/system/lib/modules) as this can affect certain ROMs
6. Removes old CPU settings from /sys/devices/system/cpu
7. Removes /data/user.log
8. Re-wipes cache+dalvik cache
Samsung Ultimate Kernel Cleaning Script ICS 2.6.4
Does the following:
Formatting cache partition
Wiping Dalvik-Cache
Deleting old kernel settings files ** [only GT-i9000]
Cleaning up old Modules
Formatting cache for Security Purpose
Wiping Dalvik-Cache for Security Purpose
Cleans after Kernels:
Thoravukk KERNEL
Abyss KERNEL
CF-Root
FLUXI Kernel
N.E.A.K. Kernel
Ninphetamine
Phenomenal
RedPillKernel
SiyahKernel
SpeedMod
Void.echo
Credits to:
Hawker - My GS2 Kernel Cleaning Scripts (WIper V1.6)
buster041284 - Samsung Ultimate Kernel Cleaning Script ICS
You guys made it easy for us! Thanks for your hard work guys!
________________________________________
You don't play too many games?
You use your phone mainly for texting, calling, browsing, twitter, facebook, XDA and other small stuff?
You want to save battery?
Then here's some good battery optimized settings.
Lulzactive Settings - Battery Optimized
Governor/Scheduler: Lulzactive/VR
Lulzactive Tweaks:
inc_cpu_load: 90%
pump_up_step: 2
pump_down_step: 2
screen_off_min_step: 500MHz
up_sample_time: 28000
down_sample_time: 40000
debug_mode: 0
Voltage Tweaks:
200Mhz - 825 mV
500Mhz - 950 mV
800Mhz - 975 mV
1000Mhz - 1050 mV
1200Mhz - 1150 mV
GPU Tweaks
2 Step:
133 - 850 mV
267 - 950 mV
3 Steps
100 - 850 mV
160 - 900 mV
267 - 950 mV
Want to save even more battery:
200MHz-1000MHz
or
200MHz-800MHz
________________________________________
Currently Testing:
On Hold
Testing Soon:
Vanilla RootBox JB + Stock
Vanilla RootBox JB + Siyah
Completed Tests:
- HyDrOG3N 14.04 + N.E.A.K 2.0.2x (Completed - April 17)
- HyDrOG3N 14.04 + Thoravukk 2.28 (Completed - April 18)
- HyDrOG3N 18.04 + Siyah v3.1 rc6 (Completed - April 20)
- HyDrOG3N 18.04 + Netchip Stock Kernel (Completed - April 21)
- HyDrOG3N 18.04 + Siyah v3.1.2 (Completed - April 25)
- HyDrOG3N 27.04 + N.E.A.K 2.0.3x (Completed - May 1st)
- HyDrOG3N 27.04 + Thoravukk 2.50 (Completed May 2nd)
- HyDrOG3N 05.05 + Abyss 1.6b (Completed May 7)
- HyDrOG3N 05.05 + Fluxi XX.01 RC3 (Completed May 8)
- HyDrOG3N 12.05 + Netchip (Stock) (Completed May 14)
- HyDrOG3N 12.05 + Fluxi XX.01 RC4 (Completed - May 16)
- HyDrOG3N 12.05 + Abyss v2.0 (Completed - May 18)
Bajee Scale(ºB): (Will be implemented Soon)
0-50 = Stay away from this!
51-70 = Could be better, keep looking.
71-80 = Not bad, I like it.
81-90 = Damn, I'm impressed.
91-100= Why isn't everyone using this!
Thanks to Definitus for the scale idea.
Press Thanks If this thread was useful.
If your downloading the xxTweaker app that I translated, I'm not asking for any donations, just press thanks to show your appreciation.
Test Results - HyDrOG3N + Siyah + Fluxi
HyDrOG3NICS + Siyah + Fluxi
Test Results - HyDrOG3N 12.05 + Fluxi XX.01 RC4
Rating: 95 ºB
Fluxi ICS Kernel
Original Thread
XDA Thread
Governor/Scheduler Used: On Demand/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday May [email protected]~10PM
Woke up: Tuesday May 15 @ 8AM (WiFi + Data was on throughout the night)
Usage: Regular usage + Twitter +Tapatalk + Games + Instagram
Phone died: Wednesday May 16 @ 2:21AM
Screen On Time: 6h 13min (6h15min when phone died)
Type of usage:
- WiFi ON (Disconnected once when I went out)
- Data ON (Always ON)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (250+ texts)
- ~ 30 minutes talk time
- Google + (~5 mins)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)*
- Instagram (Used 5-6 times)
- Osmos HD (5 mins)
- Angry Birds Space (10 mins)
- Youtube (1 Movie Trailer)
As expected, this kernel came up to the highest expectations I had. Implementation of Touch Presets is probably one of the best thing Fluxi did for this release. Bringing in new BLN/LED functions was really nice to see, but it's too bad I don't use BLN (due to wakelock) and LED fadeout is really nice but I didn't use it for this test. So for the bad things now, I had one (1) reboot.. Unfortunately true but to recomfort you guys: It was only a soft reboot. So for that reason, I couldn't post CPU SPY and BBS screenshots as they get reset after any boot. Once again, I will highly suggest this kernel to all users. I realized that after posting results for HyDrOG3N 05.05 + Fluxi XX.01 RC3, lot of users jumped in and started using Fluxi. The translated app might of helped too, who knows. But I'm glad everyone knows that Fluxi exists out there and is doing really well with battery and performance. So I'll take this time to thank Fluxi for this amazing kernel, Paradoxxx because he got swagg beyond my understanding with amazing HyDrOG3NICS releases, xator91 for opening a thread for this kernel on XDA, KS_Ho for testing out my translated xxTweaker app and finally all the subscribers of this thread.
How to install translated xxTweaker for RC4
1) Unzip file and transfer net.fluxi.xxTweaker-1-0.3.2_signed.apk to internal storage
2) Uninstall the original xxTweaker
3) Install net.fluxi.xxTweaker-1-0.3.2_signed.apk from internal storage
4) You should now have xxTweaker in English
5) Create empty file: /data/.notweaker (Should stop autoupdate)
xxTweaker Settings:
General
Idle Mode: AFTR + LPA
SCHED_MC: Disabled
Screen
Brightness/Gamma: -5
Touch Presets: xxKernel Gingerbread
BLN
No BLN (But I gotta say, Breathing effect is really amazing)
Led time out: 1 second (No Fadeout effect)
CPU
Max Suspend: 400
Min Suspend: 200
Hotplug settings: 75%UP/30%DOWN/Dynamic Hotplug
Bus Frequency: Voltage table(1050, 950, 950)
GPU
100(850) 160(900) 267(950)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time
{
"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"
}
Test Results - HyDrOG3N 05.05 + Fluxi XX.01 RC3
Rating: 95 ºB
Fluxi ICS Kernel - Original Thread Link
Governor/Scheduler Used: OnDemand/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday May [email protected]~10PM
Woke up: Tuesday May 8 @ 8AM (WiFi + Data was on throughout the night)
Usage: Regular usage + Twitter +Tapatalk + Games
Phone died: Tuesday May 8 @ 10:05PM
Screen On Time: 6h 12min (6h14min when phone died)
Type of usage:
- WiFi ON (Disconnected twice when I went out)
- Data ON (If I receive MMS and Data is OFF, it drains battery by attempting to download MMS. So from now on, Data will be on for all my tests)
- AutoSync ON (Google Services, Twitter)*
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (250+ texts)
- ~ 45 minutes talk time
- Google + (~15 mins of usage)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)*
- Instagram (Opened a few times)
- Draw Free
- Osmos HD
- Angry Birds Space
- Youtube (3 movie trailers)
Wow, seriously, this kernel just blew me away with its performance and battery. It's been a while since I've seen a kernel with this much of customization with it's own app. Unfortunately, this is a kernel made in Germany, so the app that comes with the kernel for customization was in German only. So I took the liberty of decompiling the apk, translating the string.xml, recompiling it and finally testing it on my phone. I omitted to translate one or two words, but the translated app works like a charm! You could download it from the first Post of this thread. Just make sure you hit Thanks when downloading. By the way, this kernel does not have lulzactive governor, so I used OnDemand for the test. For all those following all my tests, I think this might be my favorite kernel for now. I highly suggest for everyone to try this.
How to install translated xxTweaker
1)Unzip file and transfer xxtweaker_signed.apk to internal storage
2)Uninstall the original xxTweaker
3)Install xxtweaker_signed.apk from internal storage
4)You should now have xxTweaker in English
xxTweaker Settings:
General
Idle Mode: AFTR + LPA
SCHED_MC: Disabled
Screen
Brightness/Gamma: -5
BLN
No BLN
Led time out: 1 second
CPU
Max Suspend: 400
Min Suspend: 200
Hotplug settings: 75%UP/30%DOWN/Dynamic Hotplug
Bus Frequency: Voltage table(1050, 950, 950)
GPU
100(850) 160(900) 267(950)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU spy, BBS
Test Results - HyDrOG3N 18.04 + Siyah v3.1.2
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1200MHz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 24 @~6:30 PM
Woke up: Friday April 25 @ 8 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (200 texts +)
- ~ 50 minutes talk time
- Google + (~10 mins of usage)
- Tapatalk (All day)
- Browsing (Once or twice for a few mins)
- Camera (3 Photos + 1 Video)
- Osmos HD ~20 mins
- Angry Birds Space ~10 mins
- Youtube (2 videos ~3 mins/each)
- Netflix (TV show: Lie To Me 45 mins)
Phone died: Friday April 25 @ 17:10 PM
Screen On Time: 4h 11 min (4h 20 min when phone died)
Hey guys, I've been a little busy these days, but here I am with new results. Yup much lower than the one before but I have a pretty reasonable explanation. First of all, last Siyah's test with rc6, I only had 17hours of run time and this time I had 23 hours. That's because I didn't have the opportunity to use my phone much today (except for texting and tapatalk) since I was busy with some things of my own. During my study break, I played a little bit of Osmos HD, which is a game I bought on Play Store while it was on special for 0.49$ and I gotta say, it's pretty addictive at times (Specially when you're tired of studying) But I did end up using the phone a lot more at the very end when I was really bored and started watching a show on Netflix(which drastically killed the battery). Once I was done watching the show, I received a phone call from a friend and talked for almost an hour which also decreased the battery by a few %. Overall, I am very satisfied by the amount of time this phone actually stayed on after all these usage. I don't think this time the screen time actually mattered due to the fact that it was balanced out with 23 hours of run time. Unfortunately I couldn't post up CPU Spy or BBS, because this morning I had a random fc with my camera app and the phone had to be rebooted, so CPU Spy and BBS stats were reset.. Very strange but it only occurred once. I changed two things during this test: I noticed my lulzactive settings were giving me a little bit of lag at times. It wasn't big at all, just small lag, but I didn't like that, So i switched to these lulzactive settings and it got much better. (Values changed are in red)
Lulzactive app by Tegrak (Play Store)settings:
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
*** For better results: Boot into CWM> Kernel specific settings> battery profile and reboot. I froze Voltage Control Extreme with TB. Then used "Rom control >Performance>Voltage Control" for CPU UV. ExTweaks for everything else + lulzactive app for tweaking
*** Mounting Points haven't changed with HyDrOG3N-ICS and Siyah v3.1.2: /emmc=external /sdcard=internal ***
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart and Screen Time
Test Results - HyDrOG3N 18.04 + Siyah v3.1 rc6
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1000MHz) (100MHz/160MHz/267MHz)
CPU UV: None (under clocked CPU instead)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 19 @~9 PM
Woke up: Friday April 20 @ 9 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (150 texts +)
- ~ 35 minutes talk time (Had a phone interview + few calls)
- Google + (~15 mins of usage)
- Tapatalk (Used the most)
- Browsing (Not much today)
- Camera (2 pictures)
- Temple Run ~15 mins
- Angry Birds Space ~10 mins
- Youtube (4 videos ~3 mins/each)
Phone died: Friday April 20 @ 2:10 PM
Screen On Time: 7h 10 min (7h 13 min when phone died)
I did not expect this combination of ROM+Kernel to kill the other two, seriously didn't . Ever since there was a battery drain on previous version, I was convinced Siyah v3.1 rc6 wouldn't perform as much. As you could see in the screenshots, the hours of CPU SPY and hours of battery chart do not correspond. Why? Explanation: I turned on the Torch Light through the Power Button in order to answer a question on HyDrOG3N's thread. But after doing that, I kept having "TORCH_WAKE_LOCK" and it wouldn't go away, hence keeping my device awake. So I decided to do a "hot boot" through an app in order to conserve battery stats/cpu spy time and make that wakelock go away. Cpu Spy kept it stats, but Android's battery chart did not(but the wakelock disappeared). So in reality I had 17h44min of run time and not 17h16 as displayed. So carrying on, I did not heavily used my phone but I used it like I normally would use. I think what made the difference this time was to tweak Lulzactive. I used the Lulzactive app by Tegrak (Play Store) and tweaked it to these settings:
inc_cpu_load = 90
pump_up_step = 1
pump_down_step = 2
up_sample_time= 50000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
Screen off min step is 4 because of available range. That means, when screen off, cpu usage shouldn't go over 500MHz frequency step.
1400= 0
1200= 1
1000= 2
800= 3
500= 4
200= 5
*** For better results: Boot into CWM> Kernel specific settings> battery profile and reboot. I froze Voltage Control Extreme with TB. Then used "Rom control >Performance>Voltage Control" for CPU UV. ExTweaks for everything else + lulzactive app for tweaking
I want tho thank Gokhanmoral for his nonstop effort in order to eliminate battery drain and I think he really achieved that with Siyah v3.1 rc6 Keep up the good work mate!!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time and CPU SPY
Test Results - HyDrOG3NICS + N.E.A.K
HyDrOG3NICS + N.E.A.K + Abyss
Test Results - HyDrOG3N 12.05 + Abyss 2.0
Abyss ICS Kernel - Original Thread Link
Governor/Scheduler Used: AbyssPlug/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(950mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday May 17 @~2:45AM
Woke up: Monday May 17 @ 9AM (WiFi+Data was on throughout the night)
Usage: Regular usage + Twitter + Instagram +Tapatalk
Phone died: Friday May 18 @ 1:30 AM
Screen On Time: 5h 43min
Type of usage:
- WiFi ON (Disconnected 3 times when I went out )
- Data ON
- AutoSync ON (Google Services, Twitter, Friendcaster)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (200+ texts)
- ~ 30 minutes talk time
- Tapatalk (Used a lot)
- Twitter Usage: All day (Auto sync)
- Instagram (Used once)
- Draw Free
- Youtube (2 small clips)
This kernel was very good as I expected it would be. Due to lot of demands for me to try Abyssplug instead of Lulzactice, I decided to give it a go and it seems like this governor has the proper tweaks in order to keep performance and also save battery. So during this test, it was a regular usage of phone. There was a fair load of cpu when playing Draw Free but except that, it was minimal processes. I had to disconnect WiFi twice since I went out and I don't leave my WiFi on when I go out. So i didn't have any reboots or fc this time and it was a very pleasant and smooth experience. Only issue I had was Gmail draining my battery overnight with a 20min wakelock, but I'm sure that didnt affect the battery that much. I guess that's it for Abyss Kernel. Hope this could serve as a reference and if you got any questions about AbyssScript or anything kernel related feel free to ask.
Abyss settings in recovery mode:
Enabled AFTR+LPA
Enabled Hotplug
Disabled sched_mc
Disabled BLN
Installed Abyss script
S90abyss script file modification as follows:
GPU Clock:
GPU_STEP_LOW=100
GPU_STEP_MIDDLE=160
GPU_STEP HIGH=267
GPU Voltage:
GPU_VOLT_LOW=850000
GPU_VOLT_MIDDLE=900000
GPU_VOLT_HIGH=950000
*You could modify abyss script through a root enabled file explorer by going to /system/etc/init.d/ and editing "s90abyss" file. I used ES File Explorer. Make sure you give root access to the file explorer and don't forget to mount /system. You could always pull the file to your computer and edit it there if it's easier for you.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Test Results - HyDrOG3N 05.05 + Abyss 1.6b
Abyss ICS Kernel - Original Thread Link
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday May 6 @~3AM
Woke up: Monday May 6 @ 9AM (WiFi+Data was on throughout the night)
Usage: Regular usage + Twitter + Instagram +Tapatalk
Phone died: Monday May 7 @ 1:35 AM
Screen On Time: 5h 24min (5h31min when phone died)
Type of usage:
- WiFi ON (Disconnected once when I went out to the movies)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h (No More Facebook)
- High amount of texting (200+ texts)
- ~ 25 minutes talk time
- Google + (~5-10 mins of usage)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)
- Instagram (Used twice)
- Draw Free
- Youtube (2 movie trailers)
One of the best kernel I have tried so far. Really smooth, no reboot, no fc! I really don't care if I only got 5:24min of screen time (which is quiet a lot for some people), I had a good 22 hours of usage. The only low point with this kernel, it will give some hard time to noobs because you have to know how to use scripts, set permissions etc.. Everyone could easily learn if you put your mind to it. So it was a normal day of usage today for me, lots of texting, Tapatalk and twitter. The settings I used for Abyss are displayed below and they're really easy to be applied. If you need help setting it up, don't hesitate to post on this thread or pm me. I will do my best to answer you the fastest I can if not, there's always someone around to answer you in here.
Abyss settings in recovery mode:
Enabled AFTR+LPA
Enabled Hotplug
Disabled sched_mc
Disabled BLN
Installed Abyss script
S90abyss script file modification as follows:
GPU Clock:
GPU_STEP_LOW=100
GPU_STEP_MIDDLE=160
GPU_STEP HIGH=267
GPU Voltage:
GPU_VOLT_LOW=850000
GPU_VOLT_MIDDLE=900000
GPU_VOLT_HIGH=950000
*You could modify abyss script through a root enabled file explorer by going to /system/etc/init.d/ and editing "s90abyss" file. I used ES File Explorer. Make sure you give root access to the file explorer and don't forget to mount /system.
Lulzactive Settings
Lulzactive app by Tegrak - Play Store
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 3 (500mhz)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU spy, BBS
Test Results - HyDrOG3N 27.04 + N.E.A.K 2.0.3x
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday April 30 @~1 PM
Woke up: Tuesday May 1st @ 8 AM (WiFi was on throughout the night)
Usage: Regular usage + Twitter
Phone died: Tuesday May 1st @ 1:04 PM
Screen On Time: 5h 04min (5h11min when phone died)
Type of usage:
- WiFi ON (Disconnected twice when I went out)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS (Used for 20 Mins)
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h (No More Facebook)
- High amount of texting (150+ texts)
- ~ 20 minutes talk time
- Google + (~5-10 mins of usage)
- Google Maps Navigation (~20 mins)
- Tapatalk (Used a lot to keep track of thread)
- Twitter Usage: All day (Auto sync)
- Draw Free (~10-15 mins of usage)
Here you go guys, another test with latest HyDroG3NICS 27.04 + N.E.A.K 2.0.3x. Good results overall due to the usage throughout the day. Unfortunately, I experienced one(1) freeze when I had 13% left and as you guys know, that causes the CPU SPY and BBS stats to get erased if rebooted, so no cpu spy/bbs screenshots this time, sorry . Except that, I was satisfied with this release and how smooth scrolling was. BLN apps works but of course, it will be a wakelock, so I did not use it during the test but I tested it before I started. I modified led_timeout to 500(0.5sec) because 1000(1sec) is too long for me and also UV CPU/GPU. No more freezes with BBS and I also used NEAK Configuration app to Enable AFTR Idle Mode and Lulzactive app for my tweaking. I guess this concludes the test. If you have any questions don't hesitate to post on this thread, I will try my best to respond in a timely manner. By the way, I started using Twitter now so that's why there's 4% of twitter. If you want to follow me or ask me questions there, you guys are always welcome. @bajee11
Lulzactive app by Tegrak (Play Store)
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 3 (500mhz)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time
Test Results - HyDrOG3N 14.04 + N.E.A.K 2.0.2x
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(925mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday April 15 @~11 PM
Woke up: Monday April 16 @ 8 AM (WiFi was on throughout the night)
Usage: Used phone throughout the day but not maximal use. (Had to study for exam)
Type of usage:
- WiFi ON (except when i was in school for 3 hours: 3G was activated at that time)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of texting
- ~ 10-15 minutes talk time
- Google + (~5-10 mins of usage)
- Tapatalk (Used a lot to keep track of thread)
- Browsing
- Camera (~10-15 pictures)
Back to Bed: Tuesday April 17 @ 1 AM
Woke up: Tuesday April 17 @ 7 AM (yes only had 6 hours of sleep , kinda got used to it with exams period)
Phone died: Tuesday April 17 @ 8:40 AM
Screen On Time: 4h 45min (4h50min when phone died)
Overall, this combination of ROM+Kernel was really impressive to experiment with, performance and battery wise. Although I had some random freezes when charging the phone, but I later found out BetterBatteryStats RC2 was the cause of it. Uninstalled it, and everything worked flawlessly. N.E.A.K 2.0.3 soon to be released and promises a lot of improvements with HyDrOG3n and expected to solve freezing issue.
I'll gladly accept any comments I receive from anyone. If you think this test is not representative/unfair/fake please share your thoughts. This was only done for reference purposes, so whoever wants to use it, do so. HyDrOG3N-ICS is an amazing ROM and Para's enormous input and effort, made all this possible. Let's not forget Simone201 and his amazing N.E.A.K kernel, which seems to be pretty optimized with our ROM and built to save battery without sacrificing performance. So what's the moral of the story? Get your Swag On!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY.
Test Results - HyDrOG3NICS + Thoravukk + Netchip (Stock)
HyDrOG3NICS + Thoravukk + Netchip (Stock)
Test Results - HyDrOG3N 12.05 + Netchip (Stock Kernel)
Governor/Scheduler Used: OnDemand/SIO
CPU/GPU (200MHz-1200MHz) (66MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 66MHz(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday May 13 @~11AM
Phone died: Monday May 14 @4:01 AM (Went to sleep late)
Screen On Time: 6h 25 min (~6h 28 min when phone died)
Type of usage:
- WiFi ON (During the whole test- Except when I went out)
- Data ON (Always)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of Texting (250 texts +)
- ~ 35 minutes talk time*
- Tapatalk (Used a lot of course)
- Browsing
- Twitter
- Youtube (~10 mins)
Here's another test guys. One of the best releases of HyDrOG3NICS so far with excellent performance and battery life. Scrolling was smooth and very touch responsive. I realized that having more frequency is actually better for me (I was thinking the opposite before, Less the Better). Just like in Fluxi and Abyss, having a lot of frequency steps allows the usage of multiple steps according to the needs of the CPU. Instead of being stuck with 5 steps we now have 11 steps (Assuming your using 200-1200). But it all breaks down to the governor and how it will use those frequencies. This is where UV comes in handy, if you could lower voltage for these extra frequency steps, you could minimize battery consumption. It won't be enormous but it'll still help. This kernel is really an amazing work and the device tweaking app integrated with the system is simply amazing. Yes, there are still a few bugs, but nothing major to refrain us from using all the features. The only issue I had, was with the backlight staying on forever. But of course, that's not a big deal by now, Everyone knows how to disable them by changing values of led_timeout. So I made a few flashable scripts to change the values. They're available on OP.(Disable, 1 secoond and 3 seconds). I know this time I only had 17 hours of runtime but that's because I used a lot of data when I went outside this time, mainly for Instagram, Youtube and Browsing. I could say, I had a really busy day with my phone.
The On Demand included with stock kernel has these tweaks as default and they are very battery oriented.
On Demand Tweaks (Default):
up_threshold= 85 (You could always increase this to 90% or 95% to save even more battery, but it might lag)
sampling_rate= 100000
sampling_down_factor= 1
down_differential= 5
Hotplug enabled(Default):
loadh= 80
loadl= 30
loadh_scroff= 1000
loadl_scroff= 80
So when cpu load is more than 80% second core is activated and when cpu load goes below 30% the second core is deactivated. The other two values, I have to ask Netchip, because 1000 seems off for scren off values.
AFTR+LPA enabled (Default)
enable_mask= 3 , which stands for AFTR+LPA
If you want to save an extensive amount of battery and you're not a heavy CPU usage I suggest you underclock your CPU from 1200 to 1000 or even 800 for some. This might result in some FCs for some or even reboot, but it really depends of each person. I suggest you give it a try.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Test Results - HyDrOG3N 27.04 + Thovarukk 2.50
Rating: 80 ºB
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Wednesday May 2nd @~3:30 PM
Phone died: Thursday May 3rd @3:28 AM
Screen On Time: 5h 20 min (5h 23 min when phone died)
Type of usage:
- WiFi ON
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of Texting
- ~ 15 minutes talk time
- Google + (~10 mins of usage)
- Twitter (throughout the day)
- Tapatalk
- Youtube (3 videos of ~4mins/each)
- Draw Free (45 mins) Got carried away with this
Really good results with Thoravukk 2.50 but unfortunately I had two random reboots. I did not investigate the cause of the boot since I was too busy with other stuff these days, but it happened once when I openned Twitter and the other time, when opening BBS. The kernel itself is really stable if we do not take into consideration these reboots and still keeps up with the high standard of saving up battery. Of course, my lulzactive settings actually play a big role in battery saving but the kernel itself is not bloated with too many features which actually makes it interesting and very battery friendly. So this concludes the test, hope this helped you guys. More tests to come!!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time.
Test Results - HyDrOG3N 14.04 + Thovarukk 2.28
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(925mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1125mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Tuesday April 17 @~10:30 PM
Woke up: Wednesday April 18 @ 8 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (WiFi was off when i was out, 3G Activated)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting
- ~ 20 minutes talk time
- Google + (~15-20 mins of usage)
- Tapatalk
- Browsing (Several times during the day)
- Camera (~5 pictures + 2 Videos)
- Temple Run ~10 mins
- Cut The Rope ~15 mins
- Youtube (3 videos of ~4mins/each)
Phone died: Wednesday April 18 @ 8:30 PM
Screen On Time: 5h 50 min (5h 59 min when phone died)
This combination of ROM+Kernel was more impressive than the previous test I did with N.E.A.K. 2.0.2x . Only disadvantage with this kernel was to use so many frequency steps, which I find reduces battery time. (yup battery could of lasted even more if it weren't for all these frequency changes.) But this issue has been fixed in version 2.30 (released today) with the typical frequencies of 100, 200, 500, 800, 1000, 1200, 1400 and 1600. Unfortunately, I couldn't screenshot CPU SPY this time due to my carelessness: I tried testing a script on Script Manager but it froze and had to reboot phone. For that only reason, CPU SPY had a reset and results were no longer representative. Another big thanks to Para for his amazing Swag and Pingpong for his battery optimized Thoravukk Kernel.
Once again I'll gladly accept any comments I receive from anyone. If you think this test is not representative/unfair/fake please share your thoughts. This was only done for reference purposes.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time.
Test Results - HyDrOG3N 18.04 + Netchip (Stock Kernel)
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1200MHz) (133MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 20 @~10:30 PM
Woke up: Pulled an all-nighter to study for exam (fml) (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (200 texts +)
- ~ 10 minutes talk time
- Tapatalk (Used a lot)
- Browsing (Not much)
- Youtube (20-25 videos ~3 mins/each)
- Updated new version of Facebook (Battery killer!! Update installs FB Messenger + Camera)
Phone died: Friday April 20 @4:46 PM
Screen On Time: 7h 29 min (~7h 35 min when phone died)
Trying to keep my tests representative and due to some useful feedback I received from users, I'm going to UV CPU/GPU like I did for my first two tests. (I didn't do it for Siyah, sorry guys) When I started using this kernel, I right away noticed the difference in smoothness. It's been so long I actually used the stock kernel that I even forgot how it felt like. Unfortunately, I had some issues with UV and my usual settings wouldn't work and I was getting random freezes right after boot so I had to add up +25mV for 500MHz/1200MHz. I still applied my Lulzactive app settings and I will be doing so in all my future tests as well. So now for the results: since I was studying for my exam and wasn't using my phone much, I decided to take a few breaks here and there to play games and I left YouTube ON for a long time in order to listen to music.(I have music on my phone but I needed an app that would consume battery) So as you guys read above, I didn't sleep all night... stupid me should of studied earlier instead of fooling around with my phone Lol.. But I still managed to send more than 200 text messages.(Got into a serious texting convo in the middle of the night with one of my friends )
So let's talk about screen time now.. DAMN, 7h29!! HOW DID I DO THAT? well let me tell you something: DON'T TRY THIS AT HOME! because you most probably wont reach close to 7hrs because we all use our phones differently and I get these crazy screen hours because I don't do hardcore cpu usage. As you guys could notice, most of the time, my phone joggles between 200MHz-500MHz. Other frequencies are being used as well duhh, but not as much as these two. I had some issue with deep sleep due to F#@[email protected]^% Facebook update that kept my phone awake for no reason and some how MMS as well! Well yea, I've been sending a lot of pictures through text/mms but it's weird that it actually stayed on for such a long time. But everything went back to normal after a point and MMS stopped messing with my Deep Sleep. That's right, don't mess with my Deep Sleep! Okay enough with the jokes, I guess it's time to conclude this test. A++ Loved the battery life. Those rumors were actually true: Stock is Amazing. Shock of the day: I rushed to take screenshots of my screen before walking into my examination room because my battery was at 1%!! I figured it would die during my exam of 3 hours. This beast stayed alive till I was done my exam and even let me take more screenshots, browse and post about it on this thread!!! Hats off S II, your too cool for me. Hope you enjoyed the review and if you didn't laugh at my lame jokes, I'll make sure you do in my next review
Lulzactive app by Tegrak (Play Store)
inc_cpu_load = 90
pump_up_step = 1
pump_down_step = 2
up_sample_time= 50000
down_sample_time= 40000
screen_off_min_step= 11 (500mhz)
Tricky stuff: GPU UV is not available through Voltage Control extreme and obviously you can't use ExTweaks. So I had to use init.d script. I used the same script I had for my led_timeout, since backlight value was only "2". That value is really useless because it feels like your phone is having a seizure everytime your trying to touch the soft keys and "Hold back to kill" does not work with that value. So I changed it to 500, and added GPU frequencies of 133/267 with 850mv/950mv. Also used Lulzactive app for tweaking. One thing I didn't check with this test: AFTR+LPA. Don't know if it's default or not. Have to check that next time.
I want tho thank Netchip for his effort and input in creating a remarkable kernel. I believe someone said he was only 12 yrs old. So Netchip, if you really are 12, FML!! You're [email protected]#$% awesome bro!! Nop, I didn't forget you Para! You guys make a nice team, seriously.. Keep up the good work!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Great work dude... I'll keep on this track.. will subscribe to this!!
Sent From Galaxy S II BEAST
U know what... even we will get another kernel with superb battery back up n more. . Coming soon.. from Dorimanx .. see my signature..
Sent From Galaxy S II BEAST
Can't wait for Siyah's results
From my calculations according to the teaser that you PM'd me, I am guessing a screen on time of around 6 hours 30 minutes
Nice to see all your results in one thread. Curious to see your Siyah 3.1RC6 results!
I'm on NEAK, so from the looks of it I'm on the "worst" one Not that your NEAK results are bad.
Btw, again I'm amazed how people with a stock 1650mAh battery get better batterylife then myself with the 2000mAh. Do you use whatsapp?
XDA mark said:
Nice to see all your results in one thread. Curious to see your Siyah 3.1RC6 results!
I'm on NEAK, so from the looks of it I'm on the "worst" one Not that your NEAK results are bad.
Btw, again I'm amazed how people with a stock 1650mAh battery get better batterylife then myself with the 2000mAh. Do you use whatsapp?
Click to expand...
Click to collapse
No i dont. I basically use a lot of fb, google+, tapatalk, youtube, browser a little and lots and lots of texting.
Nice thread! Nicely done.
Sent from my i9100. No HyDrOG3NICS? No SWAGG..
Paradoxxx said:
Nice thread! Nicely done.
Sent from my i9100. No HyDrOG3NICS? No SWAGG..
Click to expand...
Click to collapse
Thanks mate, I appreciate it!
Cool.. exactly what i was looking for..
Why did you underclock for Siyah? I mean, from what I've read, underclocking just decreases battery life as it takes longer for the task to be completed...
darkgoon3r96 said:
Why did you underclock for Siyah? I mean, from what I've read, underclocking just decreases battery life as it takes longer for the task to be completed...
Click to expand...
Click to collapse
Most tasks I do, do not require high amount of CPU usage, except for my games. Which I don't play that often. So a range from 200-1000 is actually enough for my usage.
Rc6 results soon?
Sent from my GT-I9100 using XDA
Dark Emotion said:
Rc6 results soon?
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
its up
Insane Siyah results! ****ing insane! Sorry for my language but this is crazy xD
One question: did you still have a smooth experience with those Lulzactive settings? No lags when swiping, everything fast and like it should be?
I tried Lulzactive on GB, but it really start lagging and ruins the experience (if you tweak it to much towards battery)
XDA mark said:
Insane Siyah results! ****ing insane! Sorry for my language but this is crazy xD
One question: did you still have a smooth experience with those Lulzactive settings? No lags when swiping, everything fast and like it should be?
I tried Lulzactive on GB, but it really start lagging and ruins the experience (if you tweak it to much towards battery)
Click to expand...
Click to collapse
I did experience a small lag while scroling in Tapatalk, but somehow that lag wasn't there while scrolling through system settings. I figured it's because Tapatalk is a beta version. But you're right, I really tweaked it towards battery and there is that small lag which is barely noticeable. You guys could reduce the tweak towards performance/battery with this:
inc_cpu_load = 90
pump_up_step = 4
pump_down_step = 1
up_sample_time= 10000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
Wow dude! Amazing Siyah results! Gokhan really is a genius, great battery life with easily the most features
By the way, what font did you use in Siyah's battery testing?
darkgoon3r96 said:
Wow dude! Amazing Siyah results! Gokhan really is a genius, great battery life with easily the most features
By the way, what font did you use in Siyah's battery testing?
Click to expand...
Click to collapse
Sansation Regular
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.