[BATTERY LIFE] How to get up to 7+ hours of screen-on-time with the Xperia Z - Xperia Z General

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.

Related

[Ultimate GUIDE] Increase your battery life on Android

What can you expect from these tips?​
*Increase battery life by 3 times compared to a situation without any tip implemented!
My target is to unplug my phone at 6am in the morning and have it around 10% at 11pm. The below tips enabled me to reach this target whereas, without them, I would run out of battery at noon (same usage, of course)!
Disclaimer: I consider that manually "swith off location" or "switch off wifi" as well as having Juice Defender on "extreme" are not acceptable. Why? Because we all need tips that enable battery savings without decreasing the user's experience! If you need to operate manually each time you want to connect and/or have 3G... this is not a solution. If Juice Defender just cut-off every communication and don't let e-mails flow, etc... this is not a solution!
However, for those who want those kind of tips, I created a special section in post 2!
Red % signification: Well, those % in red are gut feeling of "tip contribution" to the total battery saving.
My settings which enable best battery savings without reducing user's experience!​
1. Use a NAND ROM
2% of battery improvement
Yes, compared to an SD ROM, a NAND ROM is less battery demanding. But as you can see, 2% is not a big part of the total improvement.
2. Use "SetCPU" with appropriate settings
5-10% of battery improvement
My Main is:
Max: 1190400 / Min: 245000 / Scaling: ondemand - yes! I want light speed HD2!
Click to expand...
Click to collapse
My profiles are (in order - this is important):
Screen Off
Max: 384000 / Min: 245000 / Scaling: ondemand
Battery <5%
Max: 614000 / Min: 245000 / Scaling: powersave
Battery <15%
Max: 614000 / Min: 245000 / Scaling: ondemand
Battery <30%
Max: 806000 / Min: 245000 / Scaling: ondemand
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3. Lower VDD values as low as you can (till device becomes unstable)
5-10% of battery improvement
I am using Tyween settings from his ROM Typhoon.
Code:
#!/system/bin/sh
# set vdd_levels on boot by tyween (XDA Developers)
echo '245000 850' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '384000 875' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '422400 900' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '460800 925' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '499200 950' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '537600 975' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '576000 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '614400 1025' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '652800 1050' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '691200 1075' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '729600 1100' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '768000 1100' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '806400 1125' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '844800 1150' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '883200 1150' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '921600 1175' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '960000 1175' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '998400 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1036800 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1075200 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1113600 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1152000 1250' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1190400 1275' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
I tested even lower values, but my phone was not stable.
I read that each single piece of hardware is unique and could have its own minimum values, so your device could accept lower values (i.e. you're lucky compared to me) or on the contrary higher values (here I am luckier than you are )
Tip "easy way to test a new set of undervolting values": If you want to test undervolting values, themadproducer recommends to use the CONSERVATIVE CPU profile. Why? Because CONSERVATIVE seems to use the full range of scaling frequencies as it climbs up to MAX and falls back down to MIN. This way, if any particular frequency is set too low, it will complain and freeze the CPU. ONDEMAND and SMARTASS would skip over these middle frequencies or at best, never use them for more than an instant.
4. Use "Setting Profiles" for location-based WiFi
10-15% of battery improvement
This soft enables you to switch on/off wifi according to your location (based on cell towers - which does not use battery!).
Be careful: if your location is determined by GPS (instead of cell towers) than you will use more battery through GPS than you save by switching off wifi!!!
Example: you can define to have wifi ON when you are at home, and OFF when you leave home. Same with "work" or any other place where you know there's a wifi network to which you can connect.
Setting Profiles can also be used for automatic phone profiles switching (all kind of opitions from volumes, ringtones to screen brightness airplane mode, etc...)
However, I recommend you let Setting Profiles governing the wifi only. For phone profiles, I use Pocket weaver which is better I think - it can trigger profiles according to Touchdown calendar for example. Moreover, I need wifi on/off independently from hour or calendar status and these apps don't do well when it comes to integrate several conditions together.
5. Use "Phone weaver" for a night phone profile
% of battery improvement depending on situation
I am using a night profiles which goes "Air plane mode" from 11pm to 7am. But usually, I plug my phone overnight, so battery consumption is irrelevant overnight - my night profile is just to prevent radio waves to kill my brain too prematurely as the phone is nearby for morning alarm!
6. Properly setup your Internet apps
% of battery improvement depending on situation
Sounds obvious, but still! Do you really need your phone to check e-mails each 5 minutes? Or would 15 minutes be ok and in return get instantly a lot more of battery life?
Seriously, you need to setup your apps wisely.
e.g.: for those who use Touchdown (exchange sync), this app has awsome options: you can define "peak hours" during which you have a certain setting and the rest (off-peak hours) you will have another setting + the "push" option is very clever: it does not use much battery and on the top of the push option, you setup a period when it will go and check e-mails...
7. Use Auto brightness for your screen
10% of battery improvement
If your are running CM7, there is a function that let you set your own auto-diming values.
First you need to enable auto-dimming in Settings/Brightness and then check the box. After that, go in Settings/CyanogenMod settings/Display/Automatic backlight and set the following:
Light sensor filter=enabled
- Activated: checked
- Window length = 10 s
- Reset Threshold = 400 lux
- Sample interval = 0.5 s
Light levels
- Use custom = checked
- Screen dim level = 1
- Edit other levels…
Lower / Upper / Screen / Buttons
0 / 10 / 1 / 255
11 / 149 / 20 / 255
150 / 229 / 40 / 0
230 / 499 / 50 / 0
500 / 999 / 60 / 0
1000 / 2999 / 100 / 0
3000 / 9999 / 200 / 0
10000 / infinite / 255 / 0
Set number of levels = 8 (you need to set this before editing levels above)
(hit Save & Apply)
- Allow light decrease = checked
- Decrease hysteresis = 20%
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you are not running a CM7 ROM, then just enable auto-dimming in Settings/Brightness and then check the box.
8. Use "Juice Defender Ultimate" + "Juice Plotter"
50% of battery improvement
All of the above tips are very useful. However, this one is the one tip! I came to it almost depressed by my battery life (I had all of the above tips in place already).
I did not believe this soft could really help, and I thought "ok, yeah, this app will just cut-off all communication etc... but then I will have no more auto-sync and/or push e-mail"... I thought it would be a kind of "well just don't use your phone and you will get great battery life!"...
I was wrong. This app is a must! There are all kind of options in settings. Of course the first time you have to go through it and read-read-read learn-learn-learn. But in basically 20 minutes, you are setup and you have a huge battery life improvement! I can share my own settings if anybody is interested.
And the beauty of it, is that in the huge amount of options available, Juice Defender sort out everything by itselft and as a result - I don't feel the difference from a usage point of view (K9 e-mail flowing, Touchdown is pushing e-mail, everything works like a clock). From a battery point of view: wow! The app says it increases my battery life by a 2.5 factor! And this is pretty much what I observe!!!
Juice plotter is also a must: it tells you how long you will last on your battery and I find it to be the most accurate app of this kind!
9. Condition / Calibrate your battery
This one is also a must – and you should do it time to time, let’s say once a month and always first thing to do after you flashed a new ROM!
1. Plug the phone overnight.
2. In the morning: don’t unplug! Check you have 100%, check you have CurrentWidget showing 0 mA if yes/yes, restart the phone / if not, wait until you got a yes/yes answer.
3. After reboot, don’t unplug! Wait again 15 minutes charging. Check you have 100%, check you have CurrentWidget showing 0 mA if yes/yes, go to step 4 / if not, wait until you got a yes/yes answer.
4. Don’t unplug! Clear battery statistics: use a small app named “BatteryCalibration” for that!
5. Unplug your phone, use throughout the day - Don’t charge until you reached 0% battery (when the phone switches-off itself).
6. Charge again overnight up to 100% and CurrentWidget at 0 mA.
7. You’re good to go, on daily use, you can charge upon need even if not at 0%.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
By the way, if you use GPS navigation and/or Bluetooth system in your car, you must invest in a car charger – and plug the phone every time you are in your car (if not the day during which you are calibrating)… it’s another way of increasing battery life – ok, I admit, it’s more a “trick”!
10. Use small apps that help switch on/off the screen when needed
I also tested 2 small apps that actually could help battery saving on the one side, but also increase the user experience on the other side.
Screebl pro: this app is just fantastic! According to screen orientation, it senses if you are using your phone or if it is resting (lying) on the table.
Before screebl: in order to save battery I had the screen timeout set to minimum (15sec). But each time I was reading a long e-mail, I was "playing" with the screen (up-down-up-down) in order to prevent the screen to switch-off and then unlock, etc... This was really annoying. And disturbing: I could not read an e-mail or a webpage without think: "oh, I need to play with the screen somehow or it will switch-off very soon"...
After screebl: the screen timeout is now 5sec! (through screebl) so if the phone is resting, it switches-off more rapidly = you save more battery! And when I read an e-mail or a webpage, I just relax, concentrate on the content! Anyway, the "ON" time is the same because you had to read this e-mail anyway...
ProximityScreenOff:this is also an app to have. It switches-off the screen according to the proximity sensor status: if proximity is detected, the screen goes off. If you are left-handed as I am, you need to take care of not hiding the proximity sensor when you drag the notification bar down, but it is manageable. Not only it is easier to switch-off screen now. It is also saving battery if the phone accidentally switches-on in your pocket! We already had the lockscreen which prevent your phone doing silly things in your pocket. Now even better: in your pocked, the screen switches-off almost instantly!
There is also an option to switch screen ON when proximity is detected, but warning! this drains battery - so I don't use it!
And last but not least...
11. Track any bad app
% of battery improvement depending on situation
Yes, you should know about the Email.apk bug (thanks to themadproducer - I think you learn me that). And generally: you should monitor what is going-on.
I use Watchdog which will alert you as soon as an app uses CPU above a certain threshold that you set. So you know for example that a particular app eats a lot of CPu, which means battery! Watchdog also has a "white list" function for those app that you know are consuming quite a bit of CPU but that you absolutely want to keep!
Go time to time in Spare parts / Battery history / partial wake usage and see which apps are preventing your phone to sleep - they are eating your battery instead!!!
Use CurrentWidget (with log if you want) in order to track instant high current consumption but remember you have to double check with the other above tools as current might be quite high time to time, but it is a normal situation.
Edit: I had an issue with CurrentWidget. In my case, I was logging too much and in Settings / About Phone / Battery usage, CurrentWidget was showing 12%!!! Unistalling / reinstalling might correct the issue (to be confirmed).
Use Battery Monitor Widget Pro: this will draw a graph with the battery % history in a widget, so that you can see at a glance if your battery have been decreasing with a higher rate than usual (by checking visually the slope of the curve). This also to alert you that there is something to track!
I recommend you read this thread which completely describes in a very comprehensive way how to track a battery drain!
Additional thoughts
Of course, if you are on this forum, there is a chance that you like flashing ROMs, tweak it, change settings, etc… All these activities of course use more battery than what I would call the “normal” use…
Also, some activities literally pump out the battery: games, movies, camera, camcorder, GPS navigation, bluetooth headset/earset/car system… There’s no much to do about that – just just need to be aware that they use a huge amount of battery to run; after that you make your choice: game or battery / movies or battery / do I really need the GPS navigation from work to home / etc…
Additional improvements for your phone
I strongly recommend the use of Tyween's Typhoon NAND ROM it is the most stable and complete ROM ever. I tested all of them and as soon as I flashed Typhoon, I understood it was the best... I then continued testing others, but eventually, I went back to this one!!! It is fast, reliable and updated very often! Tyween's Typhoon is here.
My Juice Defender settings
Status Tab
JuiceDefender Ultimate: Enabled
Profile: Advanced
Control Tab
Mobile Data: Enabled
WiFi: Enabled
Options: wifi preferred
3G: not working on Typhoon
AutoSync: ping
Keep enabled: none
Timeout: disabled
Keyguard: none
Home WiFi network: your home network
Brightness/CPU/Speeds/Governor: none
Schedules Tab
Schedule: enabled
Frequency: 1h
Duration: 2m
Controls: default
Night: enabled
Start/End: 0:00 -> 7:00
Adaptive start/end: start +1h max, end -1h max
Option: none
Peak/Frequency/Duration/Controls: disabled
Weekend: disabled
Triggers Tab
Battery: enabled
Battery threshold: 15%
Charger: usb ac
Screen: enabled
Options: ignore on low battery
Controls: default
Traffic: enabled
Traffic threshold: Normal / 15s
Apps: enabled
Configure: interactive
Controls: default
Location: enabled
Properly setup "SettingProfiles"
1. Open SettingProfiles
2. Go on the "Locations" tab
3. "Menu/New Location"
4. In the pop-up menu select "Cell Towers identified" (do not select "Lat/Lon Identified": this would deplete your battery)
5. A window opens-up with the current cell tower id open "Menu/Save as Cell Location"
6. In the pop-up menu, give a name to this location: e.g. "Home" or "Work" depending on the place you are right now
7. Still in this menu, you can check the "auto-save for 60 minutes". If you do so, then during the next hour, all new cells that are seen will be saved automatically as a cell for the just created location. Be careful: if you check this function, you need to be sure you will stay in this very location (e.g. stay at home) during the next hour.
You're done the "Location" is created and and several Cell Towers are saved for this location. Now it appears in the list in the Location tab.
After that, you need to do the following:
1. In the "Profiles" tab, create a profile named "Wifi ON" which leaves everything as it is except Wifi that it will switch-on
2. Still in the "Profiles" tab, create a profile named "Wifi OFF" which leaves everything as it is except Wifi that it will switch-off
3. In the "Rules" tab, create a new rule. Add condition: "Location" and then select the appropriate location where you want Wifi on. Add action: "Activate profile" and then select "Wifi ON". Back key: your rule is appearing now in the "Rules" tab.
4. Still in the "Rules" tab, create a new rule. Add condition: "Location" and then select the appropriate location where you want Wifi off and check "inverse logic". Add action: "Activate profile" and then select "Wifi OFF". Back key: your rule is appearing now in the "Rules" tab.
You're all set!
The beauty of SettingProfiles is that in the rules created on point 3 and 4, you can add several locations in the same rule. e.g. it will activate "Wifi ON" when you are at Home or at Work...
Follow-up: if in future you realize that SettingProfiles has selected "Wifi OFF" when it should have selected "Wifi ON", it means that there is a new Cell Tower accessible from (let's say) Home. In this case, go on the "Locations" tab, click on "Home" and if this Cell Tower is not in the list, there will be automatically a "save" button on the top of the list. Hit "save" to say to the app that this Tower is also part of "Home".
If you realize that SettingProfiles has selected "Wifi ON" when it should have selected "Wifi OFF", well that's nothing to do about. A Cell Tower that is accessible from (let's say) Home can also be accessible 1km from Home... However, this is not a major drawback: you are experiencing this situation only during commuting transitional times.
Extreme Users section
For those users who are ready to decrease their user experience (refer to disclaimer in post 1) here are additional settings!
Warning: if you apply these tips, you may not be happy with:
* too much involvement from your side (go switch-on switch-off things)
* widgets and other functions not properly working (i.e. auto location)
* e-mail that are not flowing / not syncing with the period you defined
Tips:
A. Turn off network location, GPS and auto sync (dorimanx)
B. South to 2g (dorimanx)
C. Set Juice Defender on "extreme" (beston94)
D. ... suggest yours!
Changelog
July 12th
* Added tip #10: Use small apps that help switch on/off the screen when needed
* Moved old tip #10 to #11: Track any bad app
July 6th
* Added the "Properly setup SettingProfiles" in post 2
July 1st
* Added disclaimer and "red %" signification in beginning of post 1
* Updated SetCPU profiles (Tip 2)
* Tips to test Undervolting values (Tip 3)
* Potential issue alert with CurrentWidget (Tip 10)
* Added JD stettings in post 2
* Added "Extreme Users" section is post 2
* Added Changelog in post 3
Nice thread.
I hope people look at this before posting "my battery life sucks.."
Do you have your statistics for the percentage gain/loss of the battery?
settings
Well you said anybody who is interested in settings on juicedefender ultimate?
Well i am on cmylxgo rom i got 37 hours on and still had 30% left with moderate usage.
But maybe your settings are better ;P
parker09 said:
Do you have your statistics for the percentage gain/loss of the battery?
Click to expand...
Click to collapse
The % I wrote are from "gut feeling"...
However, I know for sure that: before applying any tip, my battery was lasting 6 hours. Now with those tips, it lasts 18 hours!!!
You should try for yourself and report results!
beston94 said:
Well you said anybody who is interested in settings on juicedefender ultimate?
Well i am on cmylxgo rom i got 37 hours on and still had 30% left with moderate usage.
But maybe your settings are better ;P
Click to expand...
Click to collapse
Uh... So you mean that you drain your battery in 50+ hours? More than 2 full days?
Mmmmmm...
So if it's not fake, you would share with us your "tip" from another world... And also elaborate a little bit on what you mean by "moderate" usage!
We are listening to you...
Hmmm... you get over 50 hours on your battery... do you use it?
Wow i see you got a nice Tread WELL DONE!!! One more Step to perfect Phone!
And Thanks for adding my tread on your main PAGE! it's an Honor!
I am now your follower
By the way my phone cant go under 925 Voltage if i set 900 on 245MHZ it's stuck in 2 seconds!
But as you know i have configured the minimal voltage script that work for me in my tweaks. bummer that my CPU like more battery!
Good Job
Thanks for your support!
This evening, I plan to:
Update first post with new settings/information
Load my JD settings (will be in post 2)
Check it out!
Thank you. Very interesting thread!
Now i feel inspired to do something for my battery...
I have a tip for battery save.
turn off network location and GPS and auto sync and switch to 2g if you can.
then when you need one of the futures just turn it on and when finish turn off.
this can save 15% battery or more.
Sent from my HTC HD2 using XDA Premium App
Looki75 said:
Uh... So you mean that you drain your battery in 50+ hours? More than 2 full days?
Mmmmmm...
So if it's not fake, you would share with us your "tip" from another world... And also elaborate a little bit on what you mean by "moderate" usage!
We are listening to you...
Click to expand...
Click to collapse
Here are my secrets juice defender ultimate on extreme and I turn on wifi whenever I want to. I also have auto killer on strict mode don't remember the exact numbers and as for my moderate usage I took 6 1minute calls and 10message received and 3 sent and a Couple of times on xda 5 minute each. Lets not forget setcpu was on on demand not over or under clocked and my profile was screen off 245 499 and my charge was 245 1190 and when battery goes under 40 its undervolted to 245 to 780. Btw I was using cmylgxo rom the lite one since I'm on European HTC hd2.l
Press thanks if I helped anyone.
Sent from my HTC HD2 using XDA Premium App
If it is everything ok with yours builds/kernell everybody should have more than 24hours on moderate use...
I mean normal batterry consumption in stand-by should be around 3-10ma depending of reception and what is turned on...
If that is not the case than you have litlle bit more than 8 hours... i mean that sucks
I thought also it's imposible but some experimenting with different build's and kernells get me to this that i can use my device for almoust day and a half without turning wifi off.
p.s. juicedefender is enabled at balanced...
Hi everybody!
I just added a lot of things in the first 3 posts!
Check-out changelog in post 3!!!
* New SetCpu profiles
* My JD settings
* and much more... !!!
Check it out!!!
very nice tips here, but am struggling with JD atm as it says the rom i use doesnt support mobile data, does your 3g work with JD activated ? if so how do i get it working for me,
thanks, great thread btw
Found room for this useful thread in my signature
To enable JD notifications or not? Because I think notifications eat battery.
LaneyEFC said:
very nice tips here, but am struggling with JD atm as it says the rom i use doesnt support mobile data, does your 3g work with JD activated ? if so how do i get it working for me,
thanks, great thread btw
Found room for this useful thread in my signature
Click to expand...
Click to collapse
Thanks for linking to my thread in your signature
If you mean Controls Tab / 3G then JD asks you to "Proceed".
When you hit the "Proceed" button, it proposes you to install "Juice Defender AOSP Helper". You should install this app and then hit "enable" in Controls Tab / 3G.
However, some ROMs do not support this function and in this case, "Juice Defender AOSP Helper" will not install. Typhoon for example does not support this soft.
Now here is something for you: you can install a soft named "Toggle2G-update.zip" (the update through CWM if you are running Gingerbread 2.3.4).
"Toggle2G-update.zip" is in this thread, with all explanations:
http://forum.xda-developers.com/showthread.php?t=739530
You can also choose another similar app (there are a lot of them).
This will perform the same than JD / Controls Tab / 3G but with a separated software.
Cheers!
radee85 said:
To enable JD notifications or not? Because I think notifications eat battery.
Click to expand...
Click to collapse
Hello,
I enabled JD notifications.
Why? Because in a glance you can know what is JD status (I use the graphical notifications).
I never noticed any particular drain related to JD notifications, and let's say to any notifications... I also heard about that but could not reproduce the drain.
If you have any precise information about a notification-caused drain, this is an interesting information that you can share in this thread.
Thanks to report your observations!
Cheers!

[Q] [JUL 24] cpu settings cynogenmod 7.1

Hi!
I actually found the settings to change the cpu frequency today the warning I was given when i pressed " Performance " have scared me of, but not anymore.
So I was wondering, what are the best settings in your opinion, about the settings, for the Hd2 only. For heavy use, medium ( just listening to music , from-to-work) and for preserving the battery as long as possible.
And I would also like some help with the combinations of the different types of governors with the min/max cpu settings.
I know what RJackson wrote about the different governors
http://forum.xda-developers.com/showthread.php?t=843406
Thanks!
first thing first - congrats for overcoming your fears!
for daily use I have the on demand governor with 245-998 Mhz. I find it to be the best because you can get the performance when you need it and yet the CPU can "calm down" at times you don't run the heavy apps, thing that also saves you some battery
settings
I use the same as above. on demand gov. also.
thanks for your replies =)
Any information about how long the battery last for you guys?
(my battery is 4201mV @ 100%)
I use the setting as I posted above, I unplugged my phone about 17 hours ago made a few calls and texts, gmail and viber are updating every 15 mins via wifi. still got 73% of juice left (I have the stock battery, don't know about V, mA capacity)

[GUIDE] SGS2+Android can be power efficient - One successful configuration

1. Abstract
2. Approach
3. Baseline configuration and results
4. References
5. Disclaimer
1. Abstract
Initially I was quite dissapointed with the battery life of the Samsung Galaxy S II i9100 with Android 2.3.4 out of the box. Coming from the Symbian world Nokia E71 I have been used to 6-7 days without recharging, while on SGS2 I got barely 1.5 days of normal usage. I started to optimize, and felt that the hardware is very capable for power saving, but the software is not optimized. After turning off all synchronization, going thru every program settings to switch to manual sync, switching to 2G network (EDGE in my area), turning off WiFi/Data/GPS/Background data I've got a busy day full of meetings at work (didn't touch the phone apart from 2 incoming calls and a few notes) and only 10% decrease of battery for 24h (100%->90%) which is amazing by itself. But I wanted to optimize more.
I have heard that other things like Custom ROM, freezing of system applications, task killers, Under Volting (UV), Under Clocking (UV) would help me too, but I was about to discover which one really helps in real use.
One lazy Sunday like today while being a bit sick allowed me to conclude an experiment of how far did I get in optimizing the power usage for a "baseline configuration" - WiFi/Data/GPS/Background data off, 2G network, all possible sync to manual - and the results are astonishing.
2. Approach
The approach to optimize the battery life is only one - PUT IT TO SLEEP AND DON'T LET IT AWAKE.
Having read a ton of articles on xda-developers.com and other places I have concluded that the strategy for optimizing includes these major steps:
2.1. Get a clean baseline Custom ROM where much of the "bloatware" is removed, so you have less to optimize - optional step but it helps to do it
This probably helps although not necessary. I'm not sure if the stock ROM will allow you to put custom kernels which will be needed in the next steps to optimize further.
But in any case you need to be at least "rooted" to apply some of the advice - either via a rooted kernel like CF-Root [8], or via an exploit like the DooMLoRD'a zergRush exploit [7].
2.2. Optimize the screen-on time
This is up to how frequently you use the phone
What you can optimize is to set a default "conservative" CPU Governor profile from 200MHZ to 1200MHz for regular usage - nothing really special, it's only slower on jumping to high frequencies.
If you have a kernel like RedPill Kernel [9] you can add an additional In-Call profile with "conservative" CPU Governor from 100MHZ to 800MHz - while you talk and phone to the ear it idles at 100MHz, but if you start a let's say Notes taking application, or go to turn on Bluetooth it will be snappy enough. Same holds true for listening to music or listening to books - but it's up to your imagination how to set a 100MHz profile in this case (maybe via Tasker). Have in mind that the 100MHz setting may be unstable on some phones because it's not standard, but mine is absolutely fine with that setting.
For setting the CPU profiles software like Voltage Control [5] (paid version for many profiles) is used.
CPU Governor "conservative" is crucial so you don't instantly jump to the highest frequency as it happens with the default "ondemand" governor (or its clones).
You can choose an I/O Scheduler appropriate for your CPU Governor based on the MagicConfig article in my references [14].
People also say that the following helps and I use it: turn off button LED lights, darker wallpapers, auto-rotation disabled, auto brightness on (I have to see the screen after all).
If you use kernel like RedPill Kernel [9] the button LED lights are undervolted by default, so you can leave them "on for 1.5s" for example.
If you have a Custom ROM like CheckROM Revolution HD V6 [10] with JKay Deluxe Settings you can set a Dark or Darker auto brightness profile - also usable to some extent.
One article in my references [12] also gives the power drain in milliwatts (mW) for each hardware device - go read it and you will understand how much the Amoled Display (Average - 370mW), LED lamp next to camera (1.3W), Camera (700mW), Bluetooth and GPS (110 to 180mW) etc. hardware actually consumes.
2.3. Optimize the screen-off time
2.3.1. Analyze Wakelocks
Wakelocks indicate when some application prevents the phone from going to sleep for some time. It does not necessarily mean that it does something significant at that time, and may be only a bad application design. Some applications really like to hold wakelocks periodically during the day for no reason, even if set to Manual sync etc. Examples of such applications are Facebook, 3G Watchdog... You milleage may vary but you can be sure that this hurts your battery life a lot. Any such application can be frozen with Titanium Backup or uninstalled if it's not a system application. Both count and total duration of the wakelocks are important.
BetterBatteryStats [1] has a screen to debug Partial Wakelocks and Kernel Wakelocks. You can also obtain the raw information via the console command "cat /proc/wakelocks".
2.3.2. Analyze Alarms
Alarms are a way to start jobs in the system at a predefined time. Many applications set alarms to get awaken and check/poll something before sleeping again. You should note that firing an Alarm is not necessarily connected to having a Wakelock - you can see many alarms firing but very few wakelocks. The problem is that too many applications set too many alarms for no reason. These activities also hurt your battery life a lot. Examples of such applications are Google Maps (at least for me)... As long as I have another GPS application with offline maps, I've simply frozen Maps with Titanium Backup. Another example was let's say Social Hub, but as long it was firing once per 24h, I didn't bother to touch it.
BetterBatteryStats [1] has a screen to debug Alarms which requires Root access. You can also obtain the raw information via the console command "dumpsys alarm".
2.3.3. Analyze Network Connections
If you get lost in the Wakelocks and Alarms, you can help yourself by checking what connections are kept alive while Internet is connected. OS Monitor [3] has a Connections screen which is equivalent to "netstat". This is also a good indicator what may be drawing unnecessary battery and respectively freeze/uninstall. In my case I can point that I've discovered that K-9 Mail had a bug with IMAP accounts - if I connect to an IMAP account set to manual/poll sync once, it keeps a connection open forever, until you restart or kill the process, but for POP3 account there is no problem... Being aware of such things really help with the battery life.
2.4. Optimize deep idle and sleep time
This is the most important goal in this article - how to get into deep idle/sleep and stay there, because this is the only real way to save energy on such a powerful device
CPU Spy [2] can show you how much time you spend in deep idle/sleep - with my baseline testing I've managed to get 99% deep idle/sleep which is amazing - only if the manufacturers gave us the phones in this state and we can build on that...! But it's the other way round.
Unfortunately the sleep mode on the stock kernel and the CF-Root kernel is not too deep. Entropy512 in my references [15] describes the following modes of idle/sleep:
IDLE - clock is gated but power remains (does not eliminate any static power consumption)
AFTR - clock is gated, CPU core power removed, cache power remains - this eliminates a great deal of static power consumption - cannot be entered if second core is active
LPA - AFTR + removal of cache power - cannot be entered if second core is active
IDLE is entered if the CPU is expected to be free for 4 msec (40 msec stock)
AFTR is entered if the CPU is expected to be free for 10 msec (disabled stock)
LPA is entered if the CPU is expected to be free for 40 msec (40 msec stock)
This compares to suspend, aka deep sleep, which takes around 150 msec to enter and 650 msec to resume, and the CPU must be at 800 MHz (or at least have enough voltage to support 800 MHz operation) during this time. Entering suspend/resume is very costly in terms of power due to heavy interrupt load.
Unfortunately my knowledge ends here, but flashing a kernel like RedPill [9] with Power Saving features and patches enabled improved the deepness of the idle/sleep very significantly, let's say 2 fold compared to the stock kernel. Sleep is entered faster and with more savings.
2.5. Optimize the modem/baseband
If all the points above are done, you can consider some savings from trying to flash newer modem/baseband compatible with your Custom ROM for better power savings during Calls and Data transmission. I did not get deep into this yet, but it's rather a big Voodoo, because the contents of the various modems are not public and you can only read feedback like "works very good for me" and "totally awful", which is not very scientific. Initially you can try staying with your original modem or the one provided by the Custom ROM, and optimize the previous points.
2.6. Optimize other stuff
2.6.1. Under Volting - will probably help, but for every frequency you need to choose voltages that are not too low to keep the phone stable. You can try the UV profile from the MagicConfig article from my references [14].
2.6.2. Under Clocking - I consider trying to use 100MHz useful for some scenarios, but only as an additional profile. After all the phone is very powerful and snappy to cripple it with 100MHz-1000MHz profile as default.
2.6.3. Automatic Task Killers - absolutely worthless peaces of software [16]. Android OS is good at power saving. It is very power saving conscious actually, of course combined with capable to sleep hardware. The only reason to kill a process is if it locked on holding some resource/connection forever, and OS Monitor [3] can kill it.
2.6.4. Battery charging - charge the battery as frequently as you want, but be sure to not keep it constantly on high charge (90-100%) [18], as long as this is not a good state for storage. Making bigger cycles helps to maintain better battery life. Some sources say cycling from 0% to 100% is not optimal [17], but from my experience through the years this way also works good for battery longevity, and maintaining small loss of capacity. I can give an example of losing up to 10% of battery capacity per year compared to design capacity with this method. You can view such statistics in Power Management tools in Lenovo ThinkPads etc.
Note that the battery indicator has some tweaks around 100% so consider the following:
- When charging for me it hops from 98% straight to 100%. If you disconnect now, it drops to 98% again, and this is what other people complain from too. Just wait some more time and it will charge to real 100% to have more battery life.
- The indicator stays at 100% longer than at any other value. So when testing, always test from the same baseline, e.g. always charge to 100% before comparing results.
3. Baseline configuration and results
CheckROM Revolution HD V6 PDA XWLA4 (Android 2.3.6) + modem XXKI4 (was XWKL1 but changed for no reason) + kernel RedPill 1.3.
WiFi/Data/GPS/Background data/Auto-rotation/Button LED lights - OFF
Any type of Sync or Polling - OFF/MANUAL, using local Contacts and local Calendar
Widgets - AccuWeather.com on MANUAL and Today view from Calendar.
Network: 2G (EDGE in my area)
Background and lock screen: Dark wallpapers
CPU default profile: conservative 200MHz-1200MHz
CPU in-call profile: conservative 100MHz-800Mhz
Because I don't want to wait a full day for the statistics, I'll post now for 8 and 12 hours, and tomorrow add for 24 hours.
(See the attached images, because I'm not sure how to embed them in the text)
4. References
[1] BetterBatteryStats XDA Edition - http://forum.xda-developers.com/showthread.php?t=1179809
[2] CPU Spy - https://market.android.com/details?id=com.bvalosek.cpuspy
[3] OS Monitor - https://market.android.com/details?id=com.eolwral.osmonitor
[4] Titanium Backup (paid version) - http://matrixrewriter.com/android/
[5] Voltage Control - https://market.android.com/details?id=com.darekxan.voltagecontrol
[6] Android Terminal Emulator by Jack Palevich - https://market.android.com/details?id=jackpal.androidterm
[7] DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit) - http://forum.xda-developers.com/showthread.php?t=1321582
[8] CF-Root Kernel - http://forum.xda-developers.com/showthread.php?t=788108
[9] RedPillKernel_Rev1.3 - http://forum.xda-developers.com/showthread.php?t=1288850
[10] CheckROM Revolution HD V6 - http://forum.xda-developers.com/showthread.php?t=1312240, http://checkrom.com/
[11] Premium Dark Wallpapers - http://forum.xda-developers.com/showthread.php?t=1474798
[12] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks - http://forum.xda-developers.com/showthread.php?t=1369817
[13] Getting the Most out of the Battery on your Android device - http://softbanksucks.blogspot.com/2011/10/getting-most-out-of-your-battery-on.html
[14] MagicConfig for UV and CPU Governor + I/O Scheduler combinations - http://forum.xda-developers.com/showthread.php?t=1466017
[15] Entropy512 explained CPU idle states - http://forum.xda-developers.com/showpost.php?p=23252902&postcount=17
[16] Android Task Killers Explained - http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
[17] Li-Ion Battery Charge Cycles, Voltages and Storage analysis - http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
[18] IBM/Lenovo recommendations on Li-Ion battery treatment - http://forum.xda-developers.com/showpost.php?p=23258191&postcount=19
5. Disclaimer
Paid apps are mentioned here for clarity. You can of course find an alternative if such exists. Free (no ads) versions of software were listed where possible.
Needless to say that all advice here must be applied only under your own responsibility.
Results at 25h usage: The battery indicator has dropped down to 94%.
However it's a bit hard to predict how much is it going to last this way as long as after initially staying at the value "100%" the indicator decreases a bit faster.
See attached screenshots.
Thanks for the detailed post but i still don't understand why people insist on having a smart phone and then turning off any good feature in it to get 2 days of work out of it.
Agent_Adodas said:
Thanks for the detailed post but i still don't understand why people insist on having a smart phone and then turning off any good feature in it to get 2 days of work out of it.
Click to expand...
Click to collapse
That depends if you dont want xxxx app running every day why run it and why let it connect on a daily basis . Its a Smartphone not a dumbphone that controls the user .Nothing in the Smartphone design says hey guy you are really uncool if you don't have everything turned on .
I turn on what i want when i want but then again i am not sad enough to live my life on facebook .
jje
there's nothing wrong with killing background tasks that eats your battery, but to me it looks funny to turn off WIFI, 3G, Sync or polling.
anyway, that's what i think, other people may think different and will prefer to save on battery life.
Agent_Adodas said:
there's nothing wrong with killing background tasks that eats your battery
Click to expand...
Click to collapse
:facepalm:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Unless you love using terribly coded apps.
This is a Baseline - my initial starting position. Yeah I don't feel cool for running tons of unneeded stuff Actually after 15 hours of uptime I feel pretty bad and a slave of the charger.
I hope to tell more people in a single post what can be optimized, stripping off any superstition, voodoo and some pointless beliefs circulating in the web
I don't say "do like me", but instead what a great hardware SGS2 + core Android software actually seems to be
Please also note I didn't limit myself to 1000MHz, do not recommend reducing voltages etc... the struggle is to put the software in control, not to cripple the experience.
Additionally, I have WiFi at work, at home, at the gym, and between them I'm driving... for that reason I don't need unlimited data. And for new mails I actually get SMS and know when to fetch the mail. If it's important I can turn on the data as well. On business trips abroad there is no unlimited data anyway too - only WiFi at the office and at the hotel. So there are different scenarios...
Serious Observations Bro!
Must say, very clear,simple and awesome way to put together things...will try this out and post again!
Thanks a ton bro! Love the efforts and for helping us out!
Great tips mate... I knew many of them before but i will not use them so much.. I have a feeling that it criples my phone... Limiting my usage of the phone... Instead i have a custom rom,custom kernel ,an extra standard battery,car charger...
I even tryed once to apply most of your tips but they gave me a couple of hours extra batt life. My problem is network signal coverage-edge is fine(but who can surf on egde ?!? ) ,3g and hspda signal is not so good (i travel a lot by car all over my country) and the phone keeps trying to get better network signal and uses more battery...
So most of your tips work if u want to criple your phone and if ur network has great coverage...
Sent from my GT-I9100 using XDA
Using a slow scaling cpu governor defeats the purpose of battery savings. You want something that will scale up fast and scale down just as fast. That way the task gets completed quicker and the cpu can go back to an idle state faster.
Slower governors take longer to complete a task and that uses more battery.
I rather OnDemand complete something in 2 seconds jumping immediately to 1.2Ghz than Conservative in 4 seconds scaling it's way up each step and then scaling back down slowly.
Sent from my GT-I9100 using Tapatalk
Elisha said:
Using a slow scaling cpu governor defeats the purpose of battery savings. You want something that will scale up fast and scale down just as fast. That way the task gets completed quicker and the cpu can go back to an idle state faster.
Slower governors take longer to complete a task and that uses more battery.
I rather OnDemand complete something in 2 seconds jumping immediately to 1.2Ghz than Conservative in 4 seconds scaling it's way up each step and then scaling back down slowly.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Not true if I'm typing notes. Ondemand will struggle to take me on high frequency, while I'm browsing the texts... Do you need high frequency when reading forums?
Actually I have no problem to play Asphalt 6 and Angry Birds on 1200MHz with this setup
It takes you more cpu cycles to get Asphalt or Angry Birds fully loaded with Conservative than it would with OnDemand.
And you have to remember we have dual-core cpus. It's to your benefit to get both cores scaled up faster to finish the task.
You don't notice this as much because the difference is probably in the milliseconds. But Conservative is more of a power hog than OnDemand.
Sent from my GT-I9100 using Tapatalk
Wow, thats massive and informative! Too good job Sir! Hats Off!
Elisha said:
It takes you more cpu cycles to get Asphalt or Angry Birds fully loaded with Conservative than it would with OnDemand.
And you have to remember we have dual-core cpus. It's to your benefit to get both cores scaled up faster to finish the task.
You don't notice this as much because the difference is probably in the milliseconds. But Conservative is more of a power hog than OnDemand.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Agree. All that advice is mostly targeted to battery conscious people, this is not a gaming setup There is no one best configuration for all.
It's also not about what exact values to choose, but what approach to take for battery life improvement.
Can't wait to run a UV kernel once the sources drop. That there helps quite a bit to conserve battery.
Sent from my GT-I9100 using Tapatalk
I know pretty much all of this already but it's a useful guide for noobs for sure.
I don't bother anymore with SetCPU or any of that anymore and to be honest it's had little or no impact on battery life which is still excellent.
gingingingin said:
0: IDLE - CPU not clocked
1: AFTR - something not totally clear to me, but an alternative way to IDLE the CPU - ARM Off Top Running with L2 cache keeping its state
2: IDLE+LPA - IDLE + DEEP IDLE - also some parts of hardware are powered down
3: AFTR+LPA - AFTR + DEEP IDLE
Click to expand...
Click to collapse
These are not deep sleep states. Deep sleep is also known as "suspend" - where almost the entire system is shut down.
These are CPU idle states, which allow the core to save power even when the system is "running". They take significantly less time and energy to enter, but save less power. Also, there are only three of them - IDLE, LPA, AFTR. See arch/arm/mach-s5pv310/cpuidle.c in the kernel source for more details.
As an example, with kernels that have the cpuidle backport from the Tab 7 Plus:
IDLE is entered if the CPU is expected to be free for 4 msec (40 msec stock)
AFTR is entered if the CPU is expected to be free for 10 msec (disabled stock)
LPA is entered if the CPU is expected to be free for 40 msec (40 msec stock)
There are some rules that can cause lower states to be entered even if the cpuidle governor chooses LPA or AFTR. (cpuidle governor has nothing to do with cpufreq governor).
Your descriptions of the states are pretty close to what I understand them to be:
IDLE - clock is gated but power remains (does not eliminate any static power consumption)
AFTR - clock is gated, CPU core power removed, cache power remains - this eliminates a great deal of static power consumption - cannot be entered if second core is active
LPA - AFTR + removal of cache power - cannot be entered if second core is active
The above are why 100 MHz is pointless on our device, and in my experience, actually can increase power usage. The achievable voltage difference between 100 MHz and 200 MHz is insignificant for most peope, and if the voltages for two frequencies are the same, it's better to run at the higher frequency and drop into AFTR/LPA to shut off core power more often. The PDF linked from Ezekeel's post at http://forum.xda-developers.com/showthread.php?p=21785924#post21785924 is a useful read on this topic, especially section 6. While it's fairly old, most of the concepts remain valid. For this reason, 500 MHz also doesn't consume much more power than 200 for a given fixed amount of load due to having the same voltage stock as 200 (however, it does increase some internal clocks I believe, leading to slightly increased power) - so when the screen is on I have it set to 500 MHz minimum.
This compares to suspend, aka deep sleep, which takes around 150 msec to enter and 650 msec to resume, and the CPU must be at 800 MHz (or at least have enough voltage to support 800 MHz operation) during this time. Entering suspend/resume is very costly in terms of power due to heavy interrupt load, which is involved in 90% of complaints about high "Android OS" battery usage on Gingerbread. However I believe from some of the testing I've run that improved cpuidle greatly reduces this penalty.
With the improved cpuidle patch, even when I use the Wake Lock app to hold a permanent wakelock for testing purposes, my standby drain is only 1.5%/hour or so. When not holding a wakelock, 0.5%/hour on wifi is easily achievable. It gets much worse at my desk at work, where the signal is weak and the cell radio eats huge amounts of power - there it's around 1%/hour.
Edit: As to task killers - all of the people saying "task killers are worthless" talk about memory management only. The fact is, unfortunately, that there are some crappy apps out there that use too much CPU or hold insanely long wakelocks that you just have to use occasionally. Facebook is still the #1 example here - Facebook is a major battery hog, therefore when you're done with it, you must kill it with fire. However, NEVER use an autokiller and never use it for memory management!
Regarding battery charging, I wonder have you read this article before : batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries (please add http)
The fact seems to be completely opposite from your theory in 2.6.4.
Sent from my GT-I9100 using xda premium
Not sure, the battery article is a bit doubtful. For me at least the testing sequence is strange:
1. Charging current of 1C is a bit high, to say the least. Quick chargers have never been optimal for any type of batteries.
2. Discharge current of 1C is huge and far from being realistic for a mobile phone.
Also if we interpret the results it becomes that at 10% DoD we get 4700 small cycles, which is close to 100% DoD with 500 big cycles... Actually the results are in favor of the 100% DoD.
Of course my interpretation can be wrong, but so far I have got the opposite idea of that.
For practical purposes I can give an example of a Nokia Li-Ion battery thoroughly fully discharged and for 2 years it retained at least 80% capacity. I'd estimate the number of cycles to be 120-150.
On my current laptop the ThinkPad Panasonic battery was always almost completely discharged via settings, attaching screenshots. At 328 cycles and 3.5 years since first use it retains 88% of the design capacity. This is quite a good achievement for a tortured battery I'd say
Note: See the advice/sentence written in the top box by my good old IBM manufacturer (now Lenovo). "... battery deterioration may occur faster if the battery is constantly charged at 100%. Lowering the charge thresholds ... will help increase its lifespan". These guys know their job... I think their sentence almost surely relates to storage though. Storage at 50% is much better than storage at 100% charge. There is room for interpretation again.
Note: This is my second battery on this laptop, the first one Sanyo was a bit worse with the same treatment (maybe older technology) and after 2 years its electronics suddenly failed, while at around 150 cycles.
Entropy512 said:
The above are why 100 MHz is pointless on our device, and in my experience, actually can increase power usage. The achievable voltage difference between 100 MHz and 200 MHz is insignificant for most peope, and if the voltages for two frequencies are the same, it's better to run at the higher frequency and drop into AFTR/LPA to shut off core power more often.
Click to expand...
Click to collapse
First of all, thanks for the detailed explanation of the states.
I remember from the school/uni that the power used is proportional to the frequency. If we have static consumption in the chip it will not be affected by changing the frequency, but the dynamic part of the consumption is essentially doubled when running on 200MHz compared to 100MHz. I don't know the ratio dynamic_consumption:static_consumption for my chip, but it may be around 1:1.
The formulas were something like that: http://forums.anandtech.com/showthread.php?t=119229

[KERNEL TESTS] [ICS] [AOKP/AOSP/cm9] [SIYAH|NEAK|THORAVUKK|NETCHIP|FLUXI|ABYSS]

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

[Guide] Battery Tweaking – When squeezing battery is not enough!! - Tips

Hello, taken that I came from a mammoth battery of 6000 mA of the Ulefone Power, the 3000 mA of the ZTE Axon 7 just fails short to lasting me a day.
I felt in love with the screen of the Axon 7, just to find is the highest ranking sucker for battery, which makes me have to set it black and white and dim it…. This really sucks. ;-(
I have excellent sleeping battery savings 0 to 1% using the wakelock software, but is just when I turn on -> the screen starts draining the battery quick!.
I have installed 341 user apps and 163 system apps (I debloated heavily the phone, stock launcher, gmail, photo)…. Please notice that I have paid for the PRO versions off all the software shown here. Please respect the developers and show support by buying software that help us improve our day by day usage of the Phone.
By the way I have a A2017G with a ZTE A2017GV1.0.0B03 with rooted phone + locked boot loader
I atached a file to be opened with “My App List” which is a free Google Play app so you can download all the files I mention in the thread that belong to Google Play. The apps missing are Xposed files and you have to find them in the repository - > Xposed modules will be identified with (X). Some of the titles are in Spanish (I am a Spaniard) so I have provided a screen capture so you can identify the apps icon in Google play or use “My App List”.
I will not provide the configurations, at this point, per app (just a short description)…. Maybe we can do that in another thread to define optimum performance of the Axon 7 battery once we filter out which apps we shall use
My idea is that people share their 5 cents of which apps/tricks they use for battery savings so we could create an “optimal configuration” with the recommended settings.
[No message]
Phone Signal (2g/3g/4g) + Wifi
1. Intelli3G (X) : Switch to 2g when phone off, turn off data when Wifi connected
2. PNF Root: Changes the pulse interval of the Cellphone and the Wifi
3. Auto Pilot: If phone signal drops bellow a certain value then the phone goes into airplane mode and checks every xminutes for good signal, instead of pinning all the time
4. Gestor de red wifi: Uses gsm towers to localize the wifi hot spots for the network you connect to. If you are in an area where you do not have a network it will disconnect Wifi. Good option if you forget, like me, to turn off the Wifi when I leave home
CPU / System Tweaks
1. BootManager (X): Turn Off apps in the StartUp list
2. Auto Start Manager: Turn off apps in any event (aka if you turn the GPS on I do not want Google Maps to go on until I click it, etc)
3. CPU Turner: change governors / CPU speed in per profile configuration
4. Smart Booster Pro (X) : Control RAM and close apps as needed
5. HEBF Optimizer: Kernel Optimizer, FStrim,Zipalingn, Battery Savings, etc..
Wakelock / Sleep
1. DS Ahorro de Bateria (X): Deep sleep when screen off and control how often it wakes to ping Email/Whatsapp, etc..
2. Force Doze: Force doze right away after screen off
3. Amplify: Turn off wakelocks or control pulse
4. Greenify (X): Hibernate apps
5. No Wakelocks: Block all wakelocks per app, useful for killing wakelock of games or non notification apps, for example.
6. Power Nap: Stop wakelocks/services/alarms from waking the phone during standby
7. XDA forum thread: [Guide]0%[0,0%/h] Idle Battery Drain on Stock Rom (Xposed & Amplify Required!) from Celestial Fury . This is the BIBLE of wakelock management!!
8. Doze: Prevent apps from using cell or wifi internet connection when in sleep mode.
Screen Savers
1. Color Changer: Set the screen Black and White. It is the only app that I have found that allows setting a widget to on/off both in the launcher and in the pull down notification menu.
2. Pixoff Battery Saver: Huge battery saver – Turn off (a.k.a black) leds of a pixel so you save battery, I can achieve 50% savings with acceptable resolution. You can generate also your own pattern.
3. Screen Filter: Filter to dim the screen
4. Screen Saver: Black
5. Any App that I can set black theme
6. Substratum: Theming app, I use Dark themes (paid for them): Domination / Inversion UI/ Swift Black
7. Boot Animation: Change your Boot animation to a dark one
8. TeamBlack: Change to black multiple apps: Whatsapp, Tapatalk,Playstore,Keep, etc..
9. GravityBox: Set swipe the notification bar on, so you swipe your finger left and right to quickly change the DIM.
Battery Checkers and Wakelock Analizers
1. Wackelock Detector : Wackelocks / Greenify apps
2. GSAM Battery Monitor: Wakelocks / Plot
3. BetterBatteryStats: Wakelocks / Plot
Miscellaneous
1. Root Toolbox Lite: Clean Dalvink / Cache after TRWP .zip installation
2. Prevent Running: App will only execute if on intentionally clicked
3. Battery Calibration: After each rom installation, reach 100% charge and erase Battery_Stats
4. Battery Draining: After calibration, a quick cycle of discharge to 0%.
[No message]
WoW! @j77moduss you've done a great work here. One petition, please add links to the apps and to that Bible guide for wakelock management.
Well I did this:
1. Install a debloated ROM and my list of apps. I have about 190 apps.
2. Use Amplify to detect and limit wakelocks.
At this point the deep sleep is almost nothing so I did not focus on wireless signal optimization. It wouldn't bring any significant juice.
3. Find a good CPU and I/O governor/scheduler. I am using ATK Balanced Zhana profile for the Interactive governor, initially designed for the One Plus 3 and working excellent on our Axon 7. This balanced profile can increase the SOT to 7-10 hours without any lack of performance. There are more aggressive profiles such as X.A.N.A. for ramping up and down the cores, able to provide up to 14h of SOT. But the lag and the jittering when scrolling is very annoying when using an extreme battery saver CPU profile. However those profiles are there just in case. In a charging emergency they could be very useful. Kernel Adiutor is my favorite app for Kernel tuning, and it is compatible with our stock kernel.
I am happy with the current setup. I am benchmarking (Using BetterBatteryStats) the current battery performance with different profiles. I am planning to install Naptime or ForceDoze (Naptime seems to be better, What do you think?), however I do not use much the Doze mode except at night. While at work I need to receive emails, messages, etc, while driving I use Spotify and At home I often browse internet when I am not playing with it. And again, The battery problem is more related to the screen and CPU than any other subsystem of the device after working out the software wakelocks.
Saludos
100 % stock here, no debloated, no unlocked bootloader, nothing. Just using out of the box.
5:35 hours SOT is a fantastic battery performance.
Go thru 25 apps installs, unlock bootloader, etc etc for let's see... +1:30 Hs of SOT ? Really worth the pay and time spend in this?
I am missing something here?
Sorry but is a honest question, not trolling at all.
Enviado desde mi ZTE A2017U mediante Tapatalk
Altomugriento said:
100 % stock here, no debloated, no unlocked bootloader, nothing. Just using out of the box.
5:35 hours SOT is a fantastic battery performance.
Go thru 25 apps installs, unlock bootloader, etc etc for let's see... +1:30 Hs of SOT ? Really worth the pay and time spend in this?
I am missing something here?
Sorry but is a honest question, not trolling at all.
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
It all depends on the mix of apps you use. There are some apps that are not well polished and they have too many wakelocks, or incompatibilities with some combinations creating too much battery drain. When you install more than 150 apps and you use more than 4 or 5 social apps along the day you begin noticing a huge reduction in your battery. Not to mention Spotify, Google app, Google fit, etc. Well know for keeping your phone from going to a low power mode.
As I said before, the culprit of all this problem is basically 3:
1. Wakelocks: avoid your device to enter into low power mode, this makes your phone to waste too much battery at night or when you are not using it for some minutes.
2. CPU throttle configuration: Default governors and schedulers are usually not tuned. The manufacturers do not pay special attention to this and it is critical for having a smooth device with good battery. The ramp up and down parameters are critical here. A good profile can provide you more than 10 hours SOT without any lack of performance. Sincerely, ZTE should pay attention to this since the hardware is much more powerful than just the default 5 or 6 hours of SOT.
3. AMOLED screens are very good at saving power, and if you have your theme configured in black then the screen can contribute a lot in expanding the SOT figure. Some people use the phone more than 6 hours per day and they require to apply those mesures. probably +1:30 H of battery juice can be the difference between requiring a power bank or the battery charger.
With this phone I do never have to charge it during the night. And the car charger during commuting to work is in excess enough for keeping it alive and healthy the whole day and night and with better performance when I need it. You do not need 25 apps to do so, and probably the package @j77moduss is sharing with us is excessive and for sure overwhelming to the standard user. Maybe not 25 but 5 or 6 apps to fix the 1, 2, 3 problems and another 5 or 6 to monitor the behavior in case of excessive drain is really common and can help you on extending several hours the SOT of your terminal while reducing the idle consumption.
Altomugriento said:
100 % stock here, no debloated, no unlocked bootloader, nothing. Just using out of the box.
5:35 hours SOT is a fantastic battery performance.
Go thru 25 apps installs, unlock bootloader, etc etc for let's see... +1:30 Hs of SOT ? Really worth the pay and time spend in this?
I am missing something here?
Sorry but is a honest question, not trolling at all.
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
Based on your numbers (even though they're anecdotal we can use them as a point of reference), that's giving you a 26% increase in battery with software optimization alone. I would say that's pretty damned good and worth the effort.
However, I do agree that getting 5:35hrs of SOT is pretty awesome straight out of the box. That's one of the first things that blew me away with this phone. All this power and you're getting 5:30 SOT. I light game, mid user with videos/music, but I have all my google/exchange sync to push, and have an Android Wear device connected pretty much all the time. So I expect to hit the battery a little harder than most users.
Another thing that stood out to me was the stock build. Granted, it's not as polished as some of your heavy hitters out there, but it also has a lesser footprint than most (I'm looking at you HTC and REALLY looking at you Samsung) Rooting and debloating the stock ROM has been absolutely perfect for me. I like to know exactly what my phone is running and honestly, it's worked out quite well.
Hello again, a suggestion like Lord Kelvin said "what you do not measure you cannot improve"
I have a suggestion to verify how is really running the best configuration and it is Untutu Battery test.
Maybe we could post our configuration and the Untutu result.
Any other suggestions?
@j77moduss, these are my comments on the battery extension app pack in blue:
Phone Signal (2g/3g/4g) + Wifi
1. Intelli3G (X) : Switch to 2g when phone off, turn off data when Wifi connected
2. PNF Root: Changes the pulse interval of the Cellphone and the Wifi
3. Auto Pilot: If phone signal drops bellow a certain value then the phone goes into airplane mode and checks every xminutes for good signal, instead of pinning all the time
4. Gestor de red wifi: Uses gsm towers to localize the wifi hot spots for the network you connect to. If you are in an area where you do not have a network it will disconnect Wifi. Good option if you forget, like me, to turn off the Wifi when I leave home
I leave wifi, bluetooth and LTE signal activated the whole day and night. During nigh I have about 1% drain so the cell phone signal (very low at home) or wifi are not significant energy drainers lately. Probably the monitoring task of those apps are consuming about the same wireless energy you are saving with them.
CPU / System Tweaks
1. BootManager (X): Turn Off apps in the StartUp list Usually you install things you need. Stopping push notifications removes part of the functionality, otherwise they are not started.
2. Auto Start Manager: Turn off apps in any event (aka if you turn the GPS on I do not want Google Maps to go on until I click it, etc) What are you using this for? GPS is not by any means a huge battery drainer in this phone.
3. ]CPU Turner: change governors / CPU speed in per profile configuration This is the main cause of battery drain. An optimized profile can even duplicate the screen on time.
4. Smart Booster Pro (X) : Control RAM and close apps as needed This is actually a very bad idea. Free RAM equals to wasted RAM. reading from RAM take less energy than reading from the flash storage. While the app is cached in the RAM it is not using energy until it is required. If you flush the RAM then next time your phone will use a lot more energy and time to reopen the app. This was an issue Jellybean. Nowadays clearing RAM is something we should avoid at all cost. RAM is a cache for the apps, so use it as much as possible.
5. HEBF Optimizer: Kernel Optimizer, FStrim,Zipalingn, Battery Savings, etc.. Filesystem optimizations could be improved by just switching to F2FS filesystem. This doesn't require zipaligns and it helps on saving energy and extending the life of your flash storage.
Wakelock / Sleep
1. DS Ahorro de Bateria (X): Deep sleep when screen off and control how often it wakes to ping Email/Whatsapp, etc..
2. Force Doze: Force doze right away after screen off
3. Amplify: Turn off wakelocks or control pulse
4. Greenify (X): Hibernate apps
5. No Wakelocks: Block all wakelocks per app, useful for killing wakelock of games or non notification apps, for example.
6. Power Nap: Stop wakelocks/services/alarms from waking the phone during standby
7. XDA forum thread: [Guide]0%[0,0%/h] Idle Battery Drain on Stock Rom (Xposed & Amplify Required!) from Celestial Fury . This is the BIBLE of wakelock management!!
8. Doze: Prevent apps from using cell or wifi internet connection when in sleep mode.
Numbers 1,2 and 6 seems to be somehow doing the same thing. What is the best from your point of view? why? Numbers 4 and 5 seems to be the same, however I do not find any use for them without losing functionality. No. 8 falls into the phone signal group. In this group the true game changer is Amplify.
Screen Savers
1. Color Changer: Set the screen Black and White. It is the only app that I have found that allows setting a widget to on/off both in the launcher and in the pull down notification menu.
2. Pixoff Battery Saver: Huge battery saver – Turn off (a.k.a black) leds of a pixel so you save battery, I can achieve 50% savings with acceptable resolution. You can generate also your own pattern.
3. Screen Filter: Filter to dim the screen
4. Screen Saver: Black
5. Any App that I can set black theme
6. Substratum: Theming app, I use Dark themes (paid for them): Domination / Inversion UI/ Swift Black
7. Boot Animation: Change your Boot animation to a dark one
8. TeamBlack: Change to black multiple apps: Whatsapp, Tapatalk,Playstore,Keep, etc..
9. GravityBox: Set swipe the notification bar on, so you swipe your finger left and right to quickly change the DIM.
We have one of the best screens in the market. This AMOLED Samsung panel is excellent. The absence of backlight is a great for battery savings so the more black you have, the less relevant the screen is for the SOT. Number 2 and 3 seem to be similar and I am curious about them and have my fears regarding the extra CPU required to process the screen. Which one is better? The big thing here is number 5. Number 8 is also interesting. The rest are not providing a significant advantage.
Battery Checkers and Wakelock Analizers
1. Wackelock Detector : Wackelocks / Greenify apps
2. GSAM Battery Monitor: Wakelocks / Plot
3. BetterBatteryStats: Wakelocks / Plot
I really recommend everyone to use Accubattery for at least one week to learn how to properly charge the battery. The rest of the statistics are provided by the las couple of apps you listed. Nonetheless all the battery apps are needed when you are actively tuning your phone, after a while they become useless garbage until you face another huge change such as a new ROM.
Miscellaneous
1. Root Toolbox Lite: Clean Dalvink / Cache after TRWP .zip installation This is useless in current OS. Now since the huge transition to the new ART (Android Run Time), the OS detects new installed apps so cleaning dalvik / Cache is just adding more useless drain to the battery since the AOT compiler has to process all the apps instead of only the new one. In the old times this was beneficial, not it is something you must do only if it is absolutely required.
2. Prevent Running: App will only execute if on intentionally clicked I am curius about this. what is the purpose of it regarding battery saving?
3. Battery Calibration: After each rom installation, reach 100% charge and erase Battery_Stats Why? Battery stats are aso wiped when you do a clean flash. If the OS is good enough it should take cate of recalibrating the battery. It only takes a few seconds.
4. Battery Draining: After calibration, a quick cycle of discharge to 0%.[/QUOTE] NEVER!!!!!!! There are 2 states really dangerous for the battery. One is full charge. If you reach full charge, it means that you have stressed the battery a lot in order to reach that state. New hardware battery managers just avoid reaching 100% charge just to extend the battery life. It is a common technique for PC laptops. Accubattery is one of the few battery managers that is actually focused in extending the life of your battery. You won't want to have 20% less battery after 1 year of charging it to 100% each night. Well, the second and most dangerous state for a Li-ion battery is to reach full depletion. A state of deep discharge can make it impossible to recharge again since some batteries require an extra kick not provided by the charger. Do never leave any device on until depleted, if you leave it fully discharged for a while, chances are that you will need to replace the battery. The bottom line of this is: avoid 100% charge, 85% is fair, as much as %90 and do NEVER reach full depletion. If you r phone reaches 6% just turn it off completely.
There are other ways to improve the battery such as switching to F2FS filesystem with optimized mount options. F2FS is specifically designed for flash storage. It reduces the write cycles and optimizes the use of the cache so it is far more energy efficient than the linux etx4. On the other side, it extends the life of your flash storage, including the emmc and the micro SD card die. Less writes means less wear.
Also avoid unnecessary apps, they will drain battery when rebuilding the ART AOL cache and requires extra processing for the launcher as well as for the OS in general.
I am quite happy you opened this thread with this discussion. There are other users around here such as @JeromeLeung also looking for the best performance vs. battery balance for the Axon 7.
I attach some screenshots of my battery evolution and stats for today.
Basically it drained about 1% during 5 hours at night. At work the signal is even worse and depend on the place in the building. However I spend a lot of time on wifi. At work and during the morning the screen was on for 8 hours while the battery level only drop 50%.
Extrapolating these values to a full battery level, the SOT is about 16 h
During the day I attended 3 phone calls and multiple Skype and WhatsApp calls. I used Spotify during the round trip commuting using Bluetooth. I browsed internet, I used XDA labs app, mail (tons of them), text messages, Skype, hangouts and WhatsApp messages. 4 pictures and I also had to install one app.
I only applied 4 tweaks to get this:
1. Optimized F2FS filesystem
2. Amplify
3. balanced AKT Xhana CPU profile (amazing performance)
4. Dark themes in several apps
All that using ZADmix7 ROM with stock kernel as the base system. I also enjoy premium sound with Viper4Arise that takes some CPU for the audio enhancement while playing music during commuting.
So yes, only 4 tweaks can almost triplicate the screen on time, increase performance and solve the deep sleep problem.
Oki said:
I attach some screenshots of my battery evolution and stats for today.
..... snip .....
I only applied 4 tweaks to get this:
1. Optimized F2FS filesystem
2. Amplify
3. balanced AKT Xhana CPU profile (amazing performance)
4. Dark themes in several apps
.... snip ....
Click to expand...
Click to collapse
Thanks for the in-depth analysis. Can you explain "Amplify", which of the 5 "Xhana Balanced" profiles you used & looks like you are fine-tuning an update to the application of F2FS? How will that change F2FS implementation for those of us that haven't made the change yet?
amphi66 said:
Thanks for the in-depth analysis. Can you explain "Amplify", which of the 5 "Xhana Balanced" profiles you used & looks like you are fine-tuning an update to the application of F2FS? How will that change F2FS implementation for those of us that haven't made the change yet?
Click to expand...
Click to collapse
I think they released a new all in one script called AKT that only has 2 Xana and 1 Zhana profile. Simpler! :laugh:
JeromeLeung said:
I think they released a new all in one script called AKT that only has 2 Xana and 1 Zhana profile. Simpler! :laugh:
Click to expand...
Click to collapse
Thanks, I'll check again. I had downloaded the AKT just yesterday.
amphi66 said:
Thanks for the in-depth analysis. Can you explain "Amplify", which of the 5 "Xhana Balanced" profiles you used & looks like you are fine-tuning an update to the application of F2FS? How will that change F2FS implementation for those of us that haven't made the change yet?
Click to expand...
Click to collapse
The one I was using yesterday was the Xhana profile. It is under the balanced submenu of the AKT command. It won't work on stock kernel unless you enable init.d support before flashing the AKT profiles ZIP. Regarding the F2FS optimization, please read the updated OP of that thread, In my latest posts in that thread I explain the procedure to integrate the mount options in init.d. The rebuild of the filesystem structure with optimized values is about to be simpler, since we are tuning the new TWRP 3.0.3-f2fs with backported F2FS drivers from Android 4.10. Do not use it yet since it can destroy your data partition if you use it as any other TWRP!!!! 3.0.3-1 is the safest so far. But you are safe if you already have a backup of your /data and /sdcard folders.
Oki said:
The one I was using yesterday was the Xhana profile. It is under the balanced submenu of the AKT command. It won't work on stock kernel unless you enable init.d support before flashing the AKT profiles ZIP. Regarding the F2FS optimization, please read the updated OP of that thread, In my latest posts in that thread I explain the procedure to integrate the mount options in init.d. The rebuild of the filesystem structure with optimized values is about to be simpler, since we are tuning the new TWRP 3.0.3-f2fs with backported F2FS drivers from Android 4.10. Do not use it yet since it can destroy your data partition if you use it as any other TWRP!!!! 3.0.3-1 is the safest so far. But you are safe if you already have a backup of your /data and /sdcard folders.
Click to expand...
Click to collapse
Got it. I have HawkPepper, just above "Project'. The F2FS optimizations look interesting, but a bit confusing at this point. I used F2FS on my N5, but it was simply a question of having a kernel that supported, saving sdcard contents, changing structure from TWRP and copying tbe data back again.
amphi66 said:
Got it. I have HawkPepper, just above "Project'. The F2FS optimizations look interesting, but a bit confusing at this point. I uses F2FS on my N5, but it was simply a question of having a kernel that supported, saving sdcard contents, changing structure from TWRP and copying tbe data back again.
Click to expand...
Click to collapse
Axon 7 stock kernel supports F2FS, so you just have to do basically what you did with the N5. However there are some mount options that can optimize the structure created during the data restore, and that depends on the F2FS implementation. There are also some problems with the encryption, this is why I wrote the guide for the Axon 7.
Oki said:
The one I was using yesterday was the Xhana profile. It is under the balanced submenu of the AKT command. It won't work on stock kernel unless you enable init.d support before flashing the AKT profiles ZIP. Regarding the F2FS optimization, please read the updated OP of that thread, In my latest posts in that thread I explain the procedure to integrate the mount options in init.d. The rebuild of the filesystem structure with optimized values is about to be simpler, since we are tuning the new TWRP 3.0.3-f2fs with backported F2FS drivers from Android 4.10. Do not use it yet since it can destroy your data partition if you use it as any other TWRP!!!! 3.0.3-1 is the safest so far. But you are safe if you already have a backup of your /data and /sdcard folders.
Click to expand...
Click to collapse
Do you mind sharing the Amplify wakelocks/alarms/services settings you have on your phone? Just bought the app, but have no idea what is safe to tweak without breaking the phone </3
Pollito788 said:
Do you mind sharing the Amplify wakelocks/alarms/services settings you have on your phone? Just bought the app, but have no idea what is safe to tweak without breaking the phone </3
Click to expand...
Click to collapse
I haven't limited the system too much. I do not want to get rid of receiving messages or limiting location services, so I allowed the wakelocks to be active every 180 sec. I limited: GCoreFlp, Location ManagerService, NlpWakeLock, AudioIn, bluedroid_timer, NlpCollectorWakeLock.
Same for alarms: com.droid27.twc.ACTION_TIMER_TICK, ch.bitspin.timely.widget.UPDATE_ACTION and com.android.chrome/com.google.ipc.invalidation.external.client.contrib.AndroidListener$AlarmReceiver.
I have not limited any service. I do not want to save battery while losing features.
I was losing about 1% through the night so I do not need to go very aggressive on Amplify configuration. I just force close Spotify after using it since I see it drains the battery when not in use. Amplify is not per-se a battery saver, it helps you on controlling rogue apps.
As you could see, the magic for saving battery is not Amplify, but the good tunables for the Interactive CPU governor and IO scheduler provided by AKT. These days I have been testing different Governors and I have found that BurnoutPR3 is best for benchmarks but for a daily driver Balanced Shana profile is awesome. With it I get from 10 to 16 hrs. of SOT depending on the high load time I put on the CPU (pictures, video recording time, youtube...).
I never charge the phone by night with the Axon 7 since I do not need it, all thanks to QC 3.0, I barely charge it in my car while commuting to work and by night, if I am under 40%, I load it about 25 mins to 70% and next morning while my 15 mins commuting time it reaches about 85-90% (never full charge it if you want your battery to last more than a few months). Short sessions of quick charge are healthier than long sessions to 100%. On the other hand do never leave your battery run out of charge or close to 0%. AccuBattery app can teach you how to get healthier charging habits.
Saludos
Oki said:
I haven't limited the system too much. I do not want to get rid of receiving messages or limiting location services, so I allowed the wakelocks to be active every 180 sec. I limited: GCoreFlp, Location ManagerService, NlpWakeLock, AudioIn, bluedroid_timer, NlpCollectorWakeLock.
Same for alarms: com.droid27.twc.ACTION_TIMER_TICK, ch.bitspin.timely.widget.UPDATE_ACTION and com.android.chrome/com.google.ipc.invalidation.external.client.contrib.AndroidListener$AlarmReceiver.
I have not limited any service. I do not want so safe battery while losing features.
I was lust losing about 1% through the night so I do not need to go very aggressive on Amplify configuration. I just force close Spotify after using it since I see it drains the battery when not in use. Amplify is not per-se a battery saver, it helps you on controlling rogue apps.
As you could see, the magic for saving battery is not Amplify, but the good tunables for the Interactive CPU governor and IO scheduler provided by AKT. These days I have been testing different Governors and I have found that BurnoutPR3 is best for benchmarks but for a daily driver Balanced Shana profile is awesome. With it I get from 10 to 16 hrs. of SOT depending on the high load time I put on the CPU (pictures, video recording time, youtube...).
I never charge the phone by night with the Axon 7 since I do not need it thankls to QC 3.0, I barely charge it in my car while commuting to work and, if by night I am under 40% I load it about 25 mins to 70% and next morning while my 15 mins commuting time it reaches about 85-90% (never full charge it if you want your battery to last more than a few months). Short sessions of quick charge are healthier than long sessions to 100%. On the other hand do never leave your battery run out of charge or close to it. AccuBattery can teach you how to get healthier charging habits.
Saludos
Click to expand...
Click to collapse
I appreciate the detailed explanation. Thanks a bunch !

Categories

Resources