Related
[ROM][08-06-2012] ~×~ EliteMod & Kernel CM7 ~×~ [sd-ext/swap] (ics has own thread)
EliteMod 120316 + EliteKernel 120319
Turbo just got a new meaning.
This mod is a custom ROM based on CyanogenMod7 nightly and modified CM7 Kernel.
The primary aim is to dramatically increase device speed without requiring frequencies above 1GHz in daily use.
The secondary aim is to improve battery consumption where possible by fine-tuning system settings.
The bonus is getting rid of some annoying post-flash steps and settings.
To achieve this required highly experimental steps outside of the scope of Android's security system and direct intervention in userspace.
Be aware that I made this mod primarily for myself, I went to extremes to squeeze the last bit of performance out of my device. Expect no flashy stuff, just raw power and great base for your customization. I guarantee no support whatsoever and any modifications you make to your device are solely your responsibility. It's a good idea to nandroid backup first!
Warnings - must read:
1) Do a nandroid backup, this ROM is not for everyone.
2) Full /data /cache wipe is mandatory before moving to EliteMod, even from CM7! Not kidding!
3) This ROM relies heavily on the bundled EliteKernel. Flashing any other kernel unless I explicitly put a link in download area is probably a bad idea.
4) Flashing gApps or any performance-boosting packages is not recommended. Latest gApps are already included and tweak scripts may in some extreme cases break sd-ext support.
The ROM requires a manual reboot after account setup, you will see REBOOT REQUIRED on screen. Tap it and reboot the device as usual to apply additional tweaks. Any settings done before this reboot may be lost.
6) If you want to do a "Factory Reset" of this ROM, wiping /data /cache /sd-ext wipe is not enough. You must re-flash the zip to really start clean.
The usual: Do not use TitaniumBackup to restore System components unless you know what you're doing. Restoring LauncherPro user data will forfeit fine-tuned launcher settings. Wipe deletes battery stats and recalibration is necessary to see real battery usage. You can backup your battery stats first before wiping - just use my tool - EliteMod will automatically restore the backup and save you the need to recalibrate. If you really want LWP or ADW, mv them yourself from /data/local/ as well as live walpapers and other useless garbage.
Some screenshots of the default launcher + my customized homescreen:
{
"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"
}
Changes from stock CM7 nightly:
- moarrr speeeed (optimized for lower frequency range to save power)
- kernel tweaks for better snappiness/battery balance
- more battery 100% guaranteed
- replaced ADW with LP (it crashes once after boot but still the damn fastest out there) and Go Ex
- replaced gallery with QuickPic
- Opera with performance tweaks
- added some MIUI stuff
- extra sounds and bootanim for my convenience
- removed LWP
- more in changelogs
Credits:
Big thanks to all the amazing devs who made this compilation possible.
Cyanogen and crew for his amazing ROM base
Federico Carnales for the smoothest launcher
Nanling Zheng for the best gallery app
SparksCo for the original sd-ext mounting script
JaeKar99 for the boot anim
Sybregunne for his OC daemon
nhnt11 for the gorgeous NTSense themes
MIUI team
Virtuous team
And many others I'm sure I forgot to mention - thank you and keep it up.
Download Link
Download from my high speed server:
High speed download:
http://elite-force.eu/elitemod/EliteMod120316.zip (see THIS for sd-ext and ext4 migration)
Mirror (slower):
http://www.mediafire.com/?3k5bvbk5uinn4no (see THIS for sd-ext and ext4 migration)
Standalone CM7 Kernel:
http://elite-force.eu/elitemod/MOD_EliteKernel_120319.zip (for any CM7 nightly based ROM, including EliteMod specifics)
Standalone ICS Kernel:
http://elite-force.eu/elitemod/MOD_EliteKernelICS_120608-79.zip (for any CM9 or AOKP based ROM = do not use with CM7 based EliteMod)
(SEE THIS if you have sd-ext or swap partition on your SD card)
Old versions:
Old versions:
I will be trimming old versions soon, here are most mirrors http://www.mediafire.com/?613ufmrzd2ovt
Click to expand...
Click to collapse
Undervolting tools (Windows only):
http://elite-force.eu/elitemod/UV_TOOLS.zip
Click to expand...
Click to collapse
Mods, fixes and tools:
http://elite-force.eu/elitemod/TOOL_BackupBattStats.zip (flash to save battery stats to SD)
http://elite-force.eu/elitemod/MOD_OldVending2.zip (flashable/default)
http://elite-force.eu/elitemod/MOD_NewVending3.zip (flashable)
http://elite-force.eu/elitemod/MOD_GTalk2.zip (flashable)
http://elite-force.eu/elitemod/MOD_OriginalDockIcons.zip (flashable, restores LauncherPro dock icons to EM default)
http://elite-force.eu/elitemod/MOD_GPS_Stock.zip (flashable/default)
http://elite-force.eu/elitemod/MOD_GPS_CM7.zip (flashable)
Click to expand...
Click to collapse
Old mods only up to #244:
http://elite-force.eu/elitemod/MOD_UmaroKernel_106.zip (flashable/default)
http://elite-force.eu/elitemod/MOD_TiamatKernel_114.zip (flashable)
Click to expand...
Click to collapse
Kernel source:
http://elite-force.eu/elitemod/elite_kernel_vision_source_120122.rar
Click to expand...
Click to collapse
Frequently Answered Questions:
- if the phone is not smooth, make sure you only have ONE app that controls CPU active at a time. Daemon OR SetCPU OR System Tuner etc. You can disable other apps by not giving them superuser access.
- changing your locale to english-us fixes the new market issue if you have problems but don't want to flash the old market.
- to save even more battery, undervolt your CPU by following the guide below and my easy to use UV TOOLS package. Alternatively use this program to modify your voltages https://market.android.com/details?id=com.incredicontrol .
- please include your ROM and kernel name if you ask an undervolting question in this thread and you are not running EliteMod
Click to expand...
Click to collapse
Recommended SetCPU settings (daily driver - EliteKernel only):
P7 (Temp > 46C) @ 122-768 smartassV2
P6 (Charging) @ 768-1248 smartassV2 (do not set too high, it can get hot if you use navigation in a car)
P5 (Screen Off) @ 122-768 smartassV2
P4 (B < 15%) @ 122-864 smartassV2
P3 (B < 30%) @ 122-902 smartassV2
P2 (B < 50%) @ 122-940 smartassV2
P1 (B < 101%) @ 122-1036 smartassV2
Click to expand...
Click to collapse
These settings implement my own "Final Fortress"(tm) philosphy of battery management. The speed will decrease progressively with battery discharge - basically this will make your battery last longer the longer you are not charging. The goal is to save that precious last drop of power you might need in a tight situation at the end of a long day. All that without sacrificing speed when you have plenty of charge left. You should not notice significant speed decrease until you hit the reserve @ 15%.
UV hint: If you've built your own stable undervolting table, you can maximize speed with no impact on battery by aligning the max frequencies to your specific voltage peaks. (example: if there are 3 different frequencies stable on the same voltage, always use only the fastest of the group)
~CHANGELOG:
(changes with ! require full wipe)
120319 (kernel only)
+ allowed undervolting all the way down to 700mV
120316
+ updated to latest kang
+ updated apks
+ much more resilient sd-ext mounting
+ verbose mounting script (see logcat for debugging)
+ tiny sd-ext performance increase
120315
+ latest kang
+ updated apks
+ new performance tweaks
+ optional sd-ext and/or swap support
+ relaxed swap priorities compared to experimental build
+ tweaked sd-ext I/O speed (ext4 only)
+ tweaked internal storage I/O speed (need ext4 on /data and /cache)
+ fixed Opera settings transfer
+ new set of Opera tweaks for sick performance
+ removed ROM Manager, recommend using 4EXT recovery from now on to take advantage of ext4 I/O tweaks
+ forcing dalvik-cache to internal memory for performance reasons
120310
+ latest kang
+ updated all apks
+ Scary not used by default (screen-off is now @ smartassV2 /w 768MHz max)
+ OC Daemon disabled by default, use control app to enable
+ default UV not applied by script (it is built into the kernel anyway)
+ new boot anim
+ different default theme
+ speedy postsetup script on update (second boot no longer takes eternity)
+ enabled swap support in kernel
+ improved kernel performance
120122
+ 22-01-2012 Kang build
+ added freqs below 245MHz with heavier UV
+ switched to andrev_oc and daemon
+ changed default wake frequency settings to 122-1036, SmartassV2
+ reverted ondemand gov to CM7 defaults
+ updated all apks
+ greatly improved ROM update speed (second boot)
!+ lockscreen clock not centered by default (weird in landscape)
+ changed default data mode to auto instead of preferred
+ updated default UV table in userinit.sh to match kernel internals
+ updated UV_TOOLS package to match EliteKernel
+ added tweaked Go Launcher Ex + most widgets + Sense theme
+ added 2 Sense themes to CM7 theme manager
120107
+ Updated to 05-01-2012 kang
+ Fixed garbage collection bug
+ Tweaked garbage collection and hardcoded defaults to standalone
+ Tweaked SmartassV2 for better scaling (EM + standalone)
+ Tweaked Scary for better battery to do better what it's supposed to do (EM + standalone)
+ Tweaked SIO scheduler for better I/O speed and battery (EM + standalone)
+ raised default frequency from 940MHz to 1GHz
+ lowered default frequency from 768MHz to 245MHz (raise back for more smoothness if you don't care about battery)
+ Tweaked storage subsystems for better I/O performance (EM + standalone)
+ moved hard-coded kernel settings from ROM to Kernel config (better maintainability)
+ updated all bundled APKs
+ updated SU
+ if you're using SetCPU, I recommend to update your profiles
111227
+ improved kernel performance
+ fixed undervolting support
+ released a standalone kernel
+ Important: Use the 111224 to 111227 patch instead of standalone kernel to improve stability above 1200MHz
111224
+ changed versioning to a date string until nightlies resume
+ updated all apks
+ updated to latest kang build 111222
+ faster new market as default
- dropped support for Umaro and Tiamat Kernel
+ EliteKernel 111224
+ major performance improvements
+ SmartassV2 governor
244
!+ new Opera tweaks
!+ wifi sleep fix
!+ updated settings template for 2.3.7
+ new GPS driver
+ camera fixes
+ performance and battery tweaks
+ updated all bundled apks
+ fixed goggles and youtube
+ new superuser + binary
227
+ loads more speed
+ dramatically reduced stuttering under heavy load
+ highly optimized Opera for butter-smooth browsing (tweaks for full wipe only)
+ QuickPic is now default gallery
+ set K9 mail as default email app
+ re-based on latest nightly, obviously
+ more
209
+ fixed camera effects
+ updated DSP speaker profile
+ some performance tweaks
+ support for Virtuous OC daemon (install SetCPU to disable it, uninstall to enable)
+ default undervolting profile (for people who don't care, the tailored real deal is far better)
+ default market is now the old one to prevent problems on non-us locales
186
+ first public release (CM7 nightly #186 + Umaro 1.0.6)
Click to expand...
Click to collapse
Changelog
NIKER's UnderVolting Tools Manual
Friendly warning: If you use this guide with any ROM or Kernel other than EliteMod and need to ask a question here - mention your ROM and Kernel in your post or I can't help you.
Be aware: This guide and the default voltage file assume you are using EliteKernel, other kernels will require different starting point voltage table.
Introduction:
By undervolting I mean decreasing voltages at which your CPU operates on specific frequencies.
If done properly, this can lead to dramatic increase of battery life with no performance loss, it also decreases CPU temperatures.
If done wrong, this can lead to freezes, graphic stuttering under heavy load or unability to boot without reflashing. Do a nandroid backup NOW!
I take no responsibility for your modifications, burned CPUs due to too high voltage and/or frequency, data loss, nuclear explosions, your girlfriend breaking up with you etc. You know the drill.
You should know this takes time - a lot of time. I spent 3 long evenings optimizing my table but I didn't have these tools to help.
You should also know this has to be done just once and you can reap the benefits of insane battery life with any ROM or kernel that supports undervolting - forever.
Essentials:
I am assuming you have a Windows PC at hand. SetCPU installed (disable profiles and on boot for safety), YouTube installed and Angry Birds or similar graphically intensive game of your liking for stability testing.
Next download the UV_TOOLS package I provided above, extract it somewhere and let me explain what each file does:
tools folder just contains ADB essentials and a simple free unix-capable text editor
voltages.txt - this is THE file you are going to edit and consequently THE file you never want to lose after you are done.
voltages.default.txt - this is a copy of the starting point for your convenience
start_edit.bat - this will open the voltages.txt file in an improved text editor capable of unix line endings, we are going to use this editor to make modifications to the voltage table within voltages.txt. Windows notepad is not sufficient for this task!
undervolt_temp.bat, undervolt_temp_periodic.bat - these two files are your best friends, they will push the voltages.txt to your device and apply it temporarily. It's effects will be lost after reboot. Periodic variation will push the file every 10 seconds, allowing you to always have the latest saved version of your voltage table on your device. Some may prefer the normal variant that will only re-push on a keystroke.
undervolt_persistent.bat - be careful with this baby, it does the same job as undervolt_temp.bat, but permanently so, simple reboot will no longer save your ass after you use this. You don't need to wait until you have all 4548648 frequencies optimized but do not use this unless you are pretty sure you have a stable voltage table.
remove_screwup.bat - did you just use undervolt_persistent.bat and your vision threw it back in your face and wouldn't boot? This will save you - 100% guaranteed.
Step by step guide:
First send your girlfriend to sleep, get a huge cup of tea, kick back, run a movie and connect your device, this is gonna be a long night and a lot of reboots.
Do a nandroid backup. Copy it to your PC, **** happens and we don't want that.
Run start_edit.bat - voltages.txt will open, this is not the stock voltage table, it is my own table with +25 overvolt added to every entry. Let's take a look:
Code:
echo '245760 900' > ./vdd_levels
...this says that for frequency of 245MHz the voltage will be 900mV. Valid voltages for vision are ranging from 750 to 1525.
Our objective is to find the LOWEST stable voltage for each frequency (yes - I know there's a lot of them). If you set it too low, your device will freeze and you will need to pull the battery and reboot (suggest removing your battery cover now). Too high frequency should not freeze your device but they will increase operational temperatures slightly and of course battery drain.
As I said the provided voltages.txt is specific for my device with slight overvolt, so let's see if your device can handle it or not - run undervolt_temp.bat to push and activate the default table. SetCPU to 122-1036 ondemand. Now if by now the device haven't froze, it's a good sign.
Next step we will test stability - connect to wifi and disconnect charger. Run youtube app, run a demanding test video with high quality - in high quality mode. The video should not stutter weirdly and the device should not freeze. Actually everyting should be pretty much normal. After 30s try to run your game instead for a half minute. After that hit the power button, let the device sleep for 30s and then try to wake it from standby. Should any of these steps fail, edit the voltages.txt, increase all the voltages by 25, push the changes and try the stabily test again.
Everything went smoothly? Well congratulation, you have taken the first step towards awesomeness. These settings should already improve your battery life compared to stock.
But we want moar battery! There's never enough when it comes to battery life. Well here it comes.
Take frequency 122880, it is the lowest ever used by your device out of standby. We currently have it set to 825, so let's try 800. Save the file and push the voltages to the device if you're not using periodic updater. Now SetCPU to 122-192 ondemand- it will be slow and tedious, frequencies below 768 can't run videos well so just play with your device a bit and watch for a total freeze. Short freezes that fix themselves are to be expected at those speeds. The good thing is, if your device starts suffering from sleep of death - the culprit is most likely one of these two frequencies - remember that.
Everything went well? Set all frequencies below 122880 to 800 as well. If not, leave them all at 825. Going any lower than 775 is asking for a sleep of death - just don't
Don't forget to always save voltages (floppy button) and then push them using the bat or use the periodic update - otherwise your changes have no effect, obviously.
Now move to the next frequency 192000 and set it -25 to 850. Leave SetCPU at 122-192 ondemand- we always want two adjacent frequencies switching while testing - it is during this frequency change when the device is most likely to freeze. It also triangulates the problem to these two frequencies, making it easy to fix a problem. Test stability by whatever means - no videos yet. If everything works you can try for 825.
Do this for every frequency up to 768.
Undervolt 122-192 then 245-368 then 768-806.
By now you have the sleep frequencies covered and your device should last incredibly long on standby.
Now optimize each and every frequency up to the maximum you want to use on daily basis. For 768MHz and more use additional video stress test.
Hints:
Never lower voltage more than 25 at a time between tests.
Always test with ondemand between previous and current frequency to ensure stability.
Consequently never lower more than two adjacent frequencies in one step - and even that is unsafe (but twice as fast, obviously), missing one unstable frequency means long and tedious testing process to find the culprit - you have been warned so don't try to cheat
Best tests for stability are streaming movies, they stress every component to the limits much more than any synthetic test. Even when SetCPU stability tests succeed, video streams tend to have much lower tolerance for low voltages - the video will stutter before it's even low enough to freeze whole device, do not underestimate this. Also do not mistake buffer stuttering for a CPU problem, the device would eventually freeze if it's CPU, stay close to your wifi AP.
Secondary test could be a game that doesn't stress the device as much - that will test frequency switching. Angry birds worked well for me and its fun
SetCPU profiles:
when you've finally built your own stable undervolting table up to your maximum desired frequency, you can maximize the impact of your hard work on battery by aligning the max frequencies to your specific voltage peaks. (example: if there are 3 different frequencies stable on the same voltage, always use only the fastest of the group)
Does your table look like this?
Code:
echo '368640 875' > ./vdd_levels
echo '768000 875' > ./vdd_levels
In this case always use 768 instead of 368 in setCPU where possible!
Higher frequency will do same work much faster
and in turn the CPU can sleep longer - saving battery.
kewl thanks bud
Isn't umaro an older kernel? Why not use a newer kernel. Just curious
Sent from my HTC Vision using XDA Premium App
A month old kernel is not enough to justify one that is not tried and tested unless it offers something extraordinary. Besides it offers all features one could ever dream of. Smartass, greaselightning, undervolting, very granular OC steps and mainly great stability. If you have a better candidate I will gladly take a look
I've used tiamat kernel it's pretty good and should have vipermod now so you can control voltage
Sent from my HTC Vision using XDA Premium App
If we can't flash the Gapps over the ROM, then how are we supposed to use it properly? Are they included in the ROM itself?
Mardenator said:
If we can't flash the Gapps over the ROM, then how are we supposed to use it properly? Are they included in the ROM itself?
Click to expand...
Click to collapse
Probably prepacked already
Sent from my HTC Vision using XDA Premium App
Any type of screenshots?
nik3r said:
A month old kernel is not enough to justify one that is not tried and tested unless it offers something extraordinary. Besides it offers all features one could ever dream of. Smartass, greaselightning, undervolting, very granular OC steps and mainly great stability. If you have a better candidate I will gladly take a look
Click to expand...
Click to collapse
**** the haters. Bleeding edge is not always the best edge to have.
I'll check into this in the next day or two.
This is really fast, so far no problems except market. I had to replace the new market with old one because it was force closing within 15 seconds whenever I opened it. Anyone else having similar issue with new market? I seem to have it on ILWT cm7 too.
Other than that, I think I'll keep this rom for awhile. Will see about battery life..
Sent from my HTC Vision using xda premium
miksa666 said:
This is really fast, so far no problems except market. I had to replace the new market with old one because it was force closing within 15 seconds whenever I opened it. Anyone else having similar issue with new market? I seem to have it on ILWT cm7 too.
Other than that, I think I'll keep this rom for awhile. Will see about battery life..
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
same market issue here, anyway the new market has never worked for me on cm7.
the rest is quite flawless, ill see how my battery does later and report back.
That is an old issue and it had an easy fix. If I remember correctly all you had to do was change the language of the system to "English US" in Settings->Language&Keyboard. It happened to some people on CM based roms, not sure about other roms.
tsubus said:
That is an old issue and it had an easy fix. If I remember correctly all you had to do was change the language of the system to "English US" in Settings->Language&Keyboard. It happened to some people on CM based roms, not sure about other roms.
Click to expand...
Click to collapse
go it working right away. thanks for the tip!
Does any body have a quadrant score for this rom yet? just curious.
Quadrant is not the best way to determine anything else than gaming performance but just fyi I reached 3000 points at 1440MHz @ performance, didn't bother to try more.
EDIT: Curiosity got the better of me - 3591 points at 1.9GHz.
The market issue is weird, I am not EN-us myself and it never acted up. I can provide old Vending.apk in flashable form if you want.
As for the screenshots argument - its your regular CM7, nothing special visually except LP.
AWESOME!
This is by far the SMOOTHEST, FASTEST, SEXIEST rom i have ever flashed and i have been lurking for a really long time. Thank you so much for this ROM.
Will try your rom.
would quake3 (kwaak3) timedemo benchmark be a decent way to test gains? I know it's mostly video but still, how to tell between roms?
Sometimes I want to be able to see an actual speed difference from the roms than just placebo effect but it seems hard to find the right benchmark..
Thanks
eagerly waiting for the next CM7 nightly to play some more with it but looks like the automatic compiler has some problems.
kaijura:
Graphic benchmarks will not tell you much about day to day performance.
You need to take storage and sdcard r/w speeds, governor's ability to scale the CPU properly and garbage collecting efficiency into account to tell the difference - they have all been tweaked for better experience in this ROM. Synthetic benchmarks just can't test all of that.
Battery Life on a SmartPhone - The Riddle, The Enigma
I have been asked to port my original Battery Guide over to the SGS3 threads, so here it is in all it's glory.
This thread was also recently featured on the XDA Portal. Thanks to Haroon Q. Raja for the write up.
Attaining 20+ hours of battery life is not only possible it is totally attainable with most phone configurations. The secret to making this happen is, understanding what are the contributing factors are and knowing what to do first.
This guide will help. After reading this guide, you will be able to understand how to end power eating culprits and answer those same questions we see over and over in the threads...... that is .... solving the passive battery drain and get the 20 hours of battery life we all want and desire.
As we all know, all Samsung Galaxy S 3's and their Chipsets are not created equal. So if something works for one person and not the other, then is it a software, hardware or human error. Chances are it is a combination of all three. Hopefully this can slim those down a bit and answer some questions that you might have or have seen. I have tried to get almost everything I can think of and put it in one place.
You can click on the Post # below and it will take you directly to that post if you wanted to skip some things (although I don't know why you would want to do that)
Post 1: Tips and Tricks
Post 2: Roms/Kernels, OverClocking/Undervolting, Governors & I/O Schedulers
Post 3: Memory Management
Post 4: Apps (for your download pleasure)
Post 5: Proof
I will be using satirical stories and anecdotes to get my point across below. Not meant to offend or point fingers at anyone. I am just using real life references to get to the point. Also I am not much for fancy colors. I tried it at the top here but not so much further down. If there is something specific I want to call attention too, I will BOLD it and maybe RED it too.
This is not a GUIDE to get better battery life but rather a GUIDEline to get it. What is the difference, you say? A Guide is a step by step process that you must/should follow to get the outcome that the person who created it wanted you to get [A+B+C+D should = E]. A Guideline is more of a recommendation that allows some choice or flexibility in the understanding, execution or use [A +B-(C+D) can = E].
TopShelf10 has this to say about getting the most out of your battery life
the problem is, people want to believe that they can save battery without changing their usage habits. this simply is not possible. no rom or kernel will realistically do this for you. if you remove 1 brick from a bag full of 15 bricks, the bag will be lighter, but still very heavy. you need to download "spare parts" or "process monitor" from the market and start analyzing the way your apps are acting. also look into data syncs that are happening in the background. apps that stay open behind your back/what they are doing 9an app called "autostarts" can prevent apps from self-running under certain scenarios). animation speed. polling for notifications. gps. wifi scans. overclocking. cpu/ram usage. proper sleep. widgets. brightness. 2g/3g. data usage. call time. text volume. - THESE are the things that really affect your battery life.
bottom line is, if you truly want to save battery you are going to have to get your hands dirty...there simply isnt a one-click (or one-flash) solution.
Click to expand...
Click to collapse
Below is a list of fundamental things that can be done without rooting or custom ROM/Kernels. (Standard disclaimer applies: You use it, you set it and you are responsible)
1. Be Realistic -
Do you really think that you can get two whole days out of your battery? If you do, then you must have a very important pile of papers it is sitting on to not even pick up your phone for that long. These are phones. These are mini-computers. These are arcade games. And they want, dare I say, need to be played with, talked on or downloaded to. USE YOUR PHONE.
2. Syncing –
I know you are very important and you need to know what LeBron is doing right now, just in case you get a cup for a coffee and he might be in Starbucks at the same time and you get your picture taken with him and upload it to Facebook, Twitter or Google+. That is fine and I applaud you for it and will probably download the picture and Photoshop myself in your place. This is not the problem. Syncing your accounts is. That is what is causing battery drain. Do you really need to have your FB widget (see widgets section) streaming all day long? Does Kim K.’s endorsement of a potato chip really affect your everyday life? I doubt it. Kill them (not LeBron or Kim K. but rather the auto-syncing). Every time you “friend” someone their numbers, contact info gets sync’d to your phone. Also, there are settings in Facebook, Twitter and Google+ that you can upload pictures instantly. Don’t do that. Once you do, it is out in the Ether-World and just swallowed a bunch of battery doing it too.
Settings>Accounts and Sync>Auto-sync>uncheck it
3. Widgets –
They look cool. But widgets are nothing more than RAM and battery hungry monsters that you purposely put in your home screen. Think about it. What does a widget really do? All it really does is monitor an app that you have running. So not only is it running and taking up battery and RAM but the app that it is linked to is running in the background al’ a Facebook, Twitter, Google+, CNBC, MSNBC, BBC,… the list goes on and on because they want us to put THEM on our home page.
What a great marketing campaign the widget is.
“Hey look at me new home screen”
“Cool. Hey what widget is that?”
“Oh, it is X”
“Nice, I’ll have to download that tonight when I get home” and then and there they have you and your battery.
4. Apps –
You have to pay attention to your apps. I repeat. You have to pay attention to your apps. Especially if they run in the background. This can be anything from a harmless .99c game to a monster like Live Wallpaper. The battery drain threat is twofold here because the app is running in the background but it could also be using its anonymous data collection abilities and sending that back to the Mothership. Ever wonder why you have a 4/3G with up and down arrows in your status bar when your phone is just sitting there? This is because some app is transmitting data, whether you are using it or not. There are apps in the market that monitor these situations like Watchdog or kill the data link when the lock screen is enabled like Juice Defender (see Apps below) or you can adjust app permissions like LBE Privacy Guard. Data transfer is #2 on the What Kills My Battery list.
5. Display/ Wifi/ Airplane Mode/ Animations/ Location –
Display:
#1 when it comes to what is eating your battery. Always has been and always will be. Accept it and try to do something about it. This part is easy. Just lower the brightness. You can use Auto or set it as a brightness that is low but you are still able to see well enough to function. Live Wallpapers fall into this category. They are cool to look at but static ones take up less RAM and also less display because they are not running all the time in the background. These screens are bright at 100%, so tone it down. (see Apps below).
WIFI:
Another helpful tip is setting your WIFI sleep policy to Always. This can be done by going here Setting>Wireless>WIFI> Menu key>Advanced>WIFI Sleep Policy and set it to Always.
--->Then you can also do this Build.Prop edit as well (this is if you are Rooted, of course)
Allows your wifi to scan less, saving more battery:
wifi.supplicant_scan_interval=240 (I have mine set to 420)
Airplane Mode Toggle:
DocHoliday77 has this very helpful trick regarding Airplane Mode and how it effects your Data/Battery life.
I generally suggest toggling Airplane Mode on/off as a recommended step before running data speed tests, and to help with signal strength.
When you move from one area to another, generally your phone will automatically switch to another tower as the signal/connection to the current tower degrades. This is perfectly fine while travelling since you are not in a single location for very long. The problem comes into play once you have reached your destination. For many people, when they get home from work, for example, their phone will remain connected to the last tower they switched to on their drive home. However, there is very often a tower closer to their home that can provide better signal. The phone does not automatically switch to the better tower because it is still close enough to the current one to have adequate signal. By toggling Airplane Mode on/off, when the radio turns back on it will search for the strongest signal and will now connect to the closer, better tower!
Stronger signal will directly translate to a better battery. The better your signal, the less power is consumed for ALL radio operations (Including Cell Standby, Data, and Voice)! When the signal is weak, the radio requires more power to transmit to the receiver (the tower), which translates to higher battery use.
Toggle Airplane Mode on then off again to force the phone to connect to the best possible tower.
Animations: Set Settings > Display > Animations to .5 animations.
Location:
As pointed out by Arlanthir if your device is broadcasting your location, then you may need to rethink whether or not that is good for you and your battery. Generally, your location is based off GPS, Wifi or Mobile Networks. If these are on, then battery drain is occurring. Sometimes you need your location to work with Maps, Google Now, but most of the time, it is because of the unholy trinity, Facebook, Twitter and Google+. I mean, how do you think you "Check-In' at places right?
If you don't utilise these types of features on those three, then go into Settings>Location and untick them. Now there are also other apps like MLB At-Bat and the like that require location for blacked out games or services based on your location. I find that there is always a toast in those applications that notifies me and allows me to turn then on as needed. Then when I am done, I can turn them off.
These are 5 fundamental things that you can do to help reduce battery drain and get some more life out of your phone. Anyone can do these. All you have to do is watch your phone and use some common sense. “Why does my battery drain after only 6 hours? All I was doing was checking Facebook.” Do you really need to be on Facebook for that long of a time? I doubt it. How many services do you have running? How many tasks do you have running? (Android does a good job of shutting down tasks on its own, but if you are using a task killer, it takes more juice to start up an app than to turn it back on, so to say.) Think of it like an airplane. Takes more fuel to get up in the clouds, but once you are up there, it is pretty much coasting along with way less burn.
*******************
A special thanks to DocHoliday77 for convincing me to port this over and also for some of his helpful tips as well. You know who he is, so hit his thanks button to show your appreciation for all he does for this community.
ROMs are key things to think about when it comes to battery life. They can be fully established and working fine, can be RCs and still in development or they can be Alpha/Betas and completely experimental or just beginning. Choosing the best ROM or Kernel is going to depend on what YOU want out of your phone. Do you want a stable 4.0 ROM that has great battery life but not the customizability as MIUI or CM10 or AOKP? Because we have so many versions of 4.0.x ROMs that are official and almost all the sources have been attained, they have been Optimized to their fullest and some outstanding tweaks have really brought them to the forefront in daily drivers. Again, the choice is up to you.
Kernels go hand-in-hand with your ROM. Does the kernel support Overclocking or Undervolting. How much RAM and what tweaks are included in the kernel? Does THIS kernel work with THAT ROM? These are all spelled out for you in the OP of each kernel (and ROM) for you to find out. Read them because if you don’t, you’ll bork your phone and then your next post will be, “Help. I Bricked my phone”.
Overclocking/Undervolting –
If you don’t already know what Overclocking is, well it is pretty much self-explanatory. You can Overclock your CPU above the clock-speed that Samsung, T-Mobile governed it at. This can be done with apps like SetCPU (here and here and CPUtuner,…Generally have to be ROOTed to do these but if you are flashing ROMs and Kernels then you probably already are. UnderVolting is basically what it sounds like too. You are Undervolting your CPU to conserve battery.
This can be one of the best ways for a more advanced user to save battery. Overclocking is great to see those really cool Quadrant scores. Wow!!! But it also ramps up the battery drain, as well as temperature which can shorten your battery’s TOTAL life. If you want to Overclock to 1.8-2.1 just to see what you score on Quadrant or SmartBench, then do it for that time. Most ROMs/Kernels run stable and smooth at or about 1.2-1.6 with minimal effects on battery (as long as you do tweaks in above post). If you decide to Undervolt you can use Pimp My CPU, Voltage Control, SetCPU,... to do this but take care to step it down slowly until you find the right settings for you or you will see random reboots or phone freezes and those suck trying to diagnose.
***Please note that whether you Overclock or Undervolt, do NOT “Set on Boot” until you know that they are going to work. Otherwise if it doesn’t work and your phone randomly reboots, you will get into a boot cycle (not a bootloop) because you put them in “Set on Boot”. You must test before you should do this.***
Example scale of OC/UV setting from Ktoonsez' thread:
[KERNEL][TMO][AOSP/Touchwiz][JELLYBEAN & ICS][10/31/2012] KT747 - LJ7 - KTweaker
Stock___________________Undervolt startoff point___________________jerrygooch
Mhz - mV___________________Mhz - mV___________________________Mhz - mV
1890 - 1300___________________1890 - 1300____________________________1890 - 1200
1809 - 1275___________________1809 - 1250____________________________1809 - 1150
1728 - 1250___________________1728 - 1200____________________________1728 - 1100
1674 - 1200___________________1674 - 1175 ____________________________1674 - 1075
1512 - 1200___________________1512 - 1200 ____________________________1512 - 1075
1458 - 1187___________________1458 - 1187 ____________________________1458 - 1050
1404 - 1187___________________1404 - 1187 ____________________________1404 - 1050
1350 - 1175___________________1350 - 1175 ____________________________1350 - 1025
1296 - 1175___________________1296 - 1175 ____________________________1296 - 1025
1242 - 1150___________________1242 - 1150 ____________________________1242 - 1000
1188 - 1150___________________1188 - 1150 ____________________________1188 - 1000
1134 - 1125___________________1134 - 1125 ____________________________1134 - 975
1080 - 1125___________________1080 - 1125 ____________________________1080 - 975
1026 - 1075___________________1026 - 1075 ____________________________1026 - 925
972 - 1075____________________972 - 1075 _____________________________972 - 925
918 - 1050____________________918 - 1050 _____________________________918 - 900
864 - 1050____________________864 - 1050 _____________________________864 - 900
810 - 1025____________________810 - 1025 _____________________________810 - 875
756 - 1025____________________756 - 1025 _____________________________756 - 875
702 - 975_____________________702 - 925 ______________________________702 - 825
648 - 975_____________________648 - 925 ______________________________648 - 825
594 - 950_____________________594 - 850 ______________________________594 - 800
540 - 950_____________________540 - 850 ______________________________540 - 800
486 - 925_____________________486 - 850 ______________________________486 - 800
384 - 925_____________________384 - 825 ______________________________384 - 800
192 - 900_____________________192 - 825 ______________________________192 - 800
Governors and I/O Schedulers
Governors and I/O schedulers also have a huge impact on how your CPU regulates.
Here is about everything you need to know about them from Recognized Contributor droidphile from his thread:
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs .
If you haven't checked out his thread do yourself a favor and do it. A vast amount of information. Be sure to hit his THANKS too.
Governors
I) MANUAL:
These are the 19 governors we're talking about.
1) Ondemand
2) Ondemandx
3) Conservative
4) Interactive
5) Interactivex
6) Lulzactive
7) Lulzactiveq
8) Smartass
9) SmartassV2
10) Intellidemand
11) Lazy
12) Lagfree
13) Lionheart
14) LionheartX
15) Brazilianwax
16) SavagedZen
17) Userspacce
18) Powersave
19) Performance
NOTE: Info on Samsung's own multi-core aware governor - Pegasusq is here
1) Ondemand:
Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.
2) Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3) Conservative:
A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
4) Interactive:
Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why??
Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
5) Interactivex:
This is an Interactive governor with a wake profile. More battery friendly than interactive.
6) Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
7) Lulzactiveq:
Lulzactiveq is a modified lulzactive governor authored by XDA member robertobsc and is adapted in Siyah kernel for GS2 and GS3. Lulzactiveq aims to optimize the second version of luzactive from Tegrak by a) providing an extra parameter (dec_cpu_load) to make scaling down more sensible, and b) incorporating hotplug logic to the governor. Luzactiveq is the first ever interactive based governor with hotplugging logic inbuilt (atleast the first of its kind for the exynos platform). When CPU comes out of idle loop and it's time to make a scaling decision, if load >= inc_cpu_load CPU is scaled up (like original luzactiveq) and if load <dec_cpu_load, CPU is scaled down. This possibly eliminates the strict single cut-off frequency for luzactiveq to make CPU scaling decisions. Also, stand hotplug logic runs as a separate thread with the governor so that external hotplugging logic is not required to control hotplug in and out (turn On and Off) CPU cores in multi core devices like GS2 or GS3. Only a multi core aware governor makes real sense on muti-core devices. Lulzactiveq and pegasusq aims to do that.
8) Smartass:
Result of Erasmux rewriting the complete code of interactive governor. Main goal is to optimize battery life without comprising performance. Still, not as battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off. Smartass would jump up to highest frequency too often as well.
9) SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
10) Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors )
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
11) Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
12) Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
13) Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
14) LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
15) Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery.
16) SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
17) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.
18) Powersave:
Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).
19) Performance:
Sets min frequency as max frequency. Use this while benchmarking!
So, Governors can be categorized into 3/4 on a high level:
1.a) Ondemand Based:
Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions. Members: Ondemand, OndemandX, Intellidemand, Lazy, Lagfree.
1.b) Conservative Based:
Members: Conservative, Lionheart, LionheartX
2) Interactive Based:
Works on "make scaling decision when CPU comes out of idle-loop" principle. Members: Interactive, InteractiveX, Lulzactive, Luzactiveq, Smartass, SmartassV2, Brazilianwax, SavagedZen.
3) Weird Category:
Members: Userspace, Powersave, Performance.
I/O Schedulers
1) Noop
Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
2) Deadline
Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.
Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
3) CFQ
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.
4) BFQ
Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.
Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
5) SIO
Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
Advantages:
Simple, so reliable.
Minimized starvation of requests.
Disadvantages:
Slow random-read speeds on flash drives, compared to other schedulers.
Sequential-read speeds on flash drives also not so good.
6) V(R)
Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.
7) Anticipatory
Based on two facts
i) Disk seeks are really slow.
ii) Write operations can happen whenever, but there is always some process waiting for read operation.
So anticipatory prioritize read operations over write. It anticipates synchronous read operations.
Advantages:
Read requests from processes are never starved.
As good as noop for read-performance on flash drives.
Disadvantages:
'Guess works' might not be always reliable.
Reduced write-performance on high performance disks.
Some Kernel Settings from Users out "there" (Note: These are for the SGS3 kernels):
Swifks using LeanKernel (4.3 kernel/4.2 OS):
Swiftks said:
Just thought I'd share my settings:
Governor: InteractiveX
Custom Settings:
go_hispeed_low = 95
screen_off_maxfreq = 486000
Scheduler: ROW
Min: 192 MHz
Max: 1512 MHz
Frequency Lock: ON
MP-Decision: OFF
Multicore Power Saving: 1
GPU Governor: On Demmand
GPU Max Frequency: 480
Voltages:
192 MHz = 775mv
384 MHz = 800mv
486 MHz = 800mv
594 MHz = 825mv
702 MHz = 850mv
810 MHz = 900mv
918 MHz = 950mv
1026 MHz = 1000mv
1134 MHz = 1025mv
1242 MHz = 1050mv
1350 MHz = 1075mv
1458 MHz = 1100mv
1512 MHz = 1125mv
Enjoy
Sent from my SGS III
Click to expand...
Click to collapse
liltitiz from his thread [KT747: Share & discuss your settings]+[govs & scheds info] using ktoonsez' KT747 kernel.
Post is here
liltitiz said:
With my new settings I can get up to 5-6 hour of screen on with a discharging time of around 24 hours. Before I start playing with cpu1, I couldn't get more than 4hours of screen on with a discharging time around 15hours since the Linux 3.4 kernel
Note that I also use greening to hibernate apps and Tasker to turn on things like gps, data, wifi, auto rotate only when I need them.
I readjusted my settings yesterday to test something out if you got no loss in performance yet you can try them out:
Ktoonservative setup to input in ktweaker:
Boost 2nd core on button:0
Boost cpu:540
Boost gpu: doesn't matter
Boost hold cycle :0
Boost turn on 2nd core:0
Cpu down block cycle:0
Down threshold:75
Down threshold hotplug:60
Freq step:3
Ignore nice load:0
No 2nd cpu screen off:1
Sampling down factor:3
Sampling rate: 25000
Sampling rate screen off: 45000
Up threshold:94
Up threshold hotplug:96
---------------------------------------------------
Command lines to apply my asswax settings on cpu1 :
echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq
echo 200 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us
echo 189000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq
echo 95 > /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load
echo 65 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load
echo 250000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step
echo 50000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step
echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq
echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq
echo 5000 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us
---------------------------------------------------
If you set your ktoonservative to turn off 2nd core(cpu1) when screen is off, then it doesn't matter because your cpu1.will be off so only your ktoonservative(cpu0) settings matter. Personally I use 486 as my max freq when screen is off.
Click to expand...
Click to collapse
Before we begin on the below, I must continue something about kernels from above due to character limits in posts.
A word of advice from vikas.mishra via XDA RD dorimanx in this post:
This is long INFO post from real chip designer that help to create CPU/GPU and other chips for the living for 14 years now, so respect
He sent me PM, for now he cant post that by him self.
Vikas is monitoring our thread and want to say his professional stand about UV/OV and why it's works for some and why not for others.
==================
I am calling Vikas(vikas.mishra) to the speech stand
Hello people.
Let me introduce myself - my name is Vikas Mishra and I am a chip designer by profession. .
I have worked on critical parts of design of TI OMAP4, OMAP5, Nvidia Tegra 3 etc and have been doing this for the last 14 years.
Of late - I have seen a lot of folks posting BUGS about undervolting of the GPU/CPU.
I think I can explain what are the possible issues with undervolting/overclocking in a laymans language.
It is a little long winded but I think the length is needed for providing the appropriate context.
* What is inside your Cellphone
Your cellphone is an amazing device. It is a full fledged computer
that fits into your pocket. They have all the standard components
that a computer has - except that they are all usually soldered on
the motherboard directly and are not meant to be user-servicable.
The chief components inside your cellphone are
1. Application Processor (AP)- this is the heart of a modern
cellphone. These are manufactured by many companies - the main
ones are Qualcomm, Nvidia, Samsung and Apple. The other not so
well known ones are made by Texas Instruments, ST Ericsson,
Marvell and Broadcom.
A modern AP has logic to control the camera and process the image
that it generates, to do video encoding (video recording) and
video decoding (movie watching), Audio processor etc. in addition
to the well known CPU and GPU.
2. Power Management Controller - This is the chip that is
responsible for generating and regulating the voltages that are
used by all the components on the board.
3. DRAM - not very different from the DRAM found on a PC (except
that it is lower voltage)
4. Flash - for storage
5. Touchscreen controller
6. Logic for microphone, speaker
7. Battery
One of the most complex piece of circuitry on the phone is the AP
and the power management controller.
* Circuit Basics
A modern AP has millions of circuit units called (Flip
Flops). These flip flops have two parameters associated with them
called Setup time and Hold time. More details on what a flip flop
can be found on the wikipedia at
http://en.wikipedia.org/wiki/Flip-flop_(electronics) . This is a
nice bit of bedside reading if you are interested.
A setup time roughly indicates what frequency you can run a design
or an AP at before it becomes unstable.
A hold time roughly indicates the maximum voltage till which a
design is stable.
A fully technical analysis of what is involved in these timing
parameters requires a degree in electrical engineering but in broad
terms the problem is described below.
Chip designers diligently ensure that all of the millions of the
flip flops in a chip meet the setup and hold time across a broad
range of voltages and silicon parameters. They do a pessimistic
analysis to ensure that a chip will run reliably across a wide
range of voltage/frequency combinations.
However, contrary to the popular belief, chips vary widely in their
silicon parameters. Even chips on a the same wafer and different
flip-flops within the same chip can have widely different silicon
parameters. This is why what works on one particular chip will not
work on the other chip.
Your silicon manufacturer provides a range of voltages and
frequencies across which the device can work reliably. The phone
manufacturer will further narrow down the range depending on the
other components they choose within the phone board.
* How does voltage affect the design
Reducing voltage makes the design slower and increasing voltage
makes the design faster.
So can I keep on increasing the voltage for ever and make the
circuit faster and faster. The answer is no - a point will come when
the circuit will become unreliable. This becomes unreliable because
the "hold time" of one or more of the flops will start
violating.
As you reduce the voltage of the design, the circuit will start
becoming slower. However typically it will continue to work till at
apoint it starts failing - this failure occurs due to violation of
"setup time" of one or more flops in the design.
So what happens when the setup time or the hold time of a design
fails - the answer is that it is unpredictable. Meaning suddenly if
you ask the processor what is the value of 2+2, the answer it will
provide could be unreliable - in some cases it could be 3, in some
cases it could be 4 in some cases it could be -2349783297 (a random number).
I am of course oversimplifying but I hope you get the picture.
* How does undervolting affect your phone processor
The reason undervolting is so appealing to people because they
thing that undervolting will save power and improve battery
life. While this is true in theory, in practice there is a caveat.
It will reduce the power of the chip, but the power consumed by the
phone as a whole will not improve. In some cases in fact it can
deteriorate. Let me explain.
The most power hungry part in the phone is not the AP - it is the
LCD screen. All of these screens consume a ton of power. So even
though your AP is now consuming lesser power, the overall impact to
the phone as a whole is not that much.
If you accompany undervolting with a frequency reduction (which you
should), the total time taken for doing a web page rendering (for
example) would increase. During this time the screen is on and it
has more than compensated for the power that you saved in the
AP.
You could of course come up with examples where this wouldn't
happen - but on a whole, IMHO, you should leave the voltage of the
AP/GPU/CPU to the guys who know the system best - the guys who
designed the chip and people who manufactured it.
* How does overvolting/overclocking affect your phone processor
If you want that last drop of performance from your phone and you
over clock it, at a point some of the design flops will start
violating the hold time and the design will stop working reliably.
Again, in some anecdotal cases this would work - but this is not a
reliable means/mode of working. Just because your friend's or your
first cousin's girlfriend's phone works - doesn't mean yours will
work as well.
* What are the user observable impacts of undervolting/overclocking?
It is hard to say - simply because there are so many of flops in
the design.
In some cases - you wouldn't see anything wrong with the phone
until one day you do. In some cases it will result in a SOD
immediately. In some cases it will result in your phone not waking
up reliably.
IMHO the risks of issues with undervolting/overclocking far
outweighthe potential gains you may get out of it. Usually there
is no lasting damage to the phone/AP if you overlock/undervolt but
it is possible to do it. For example, You run the phone at such a
high frequency that the chip temperature becomes more than what it
was designed for and the Silicon just fails.
So "Just say No" . Don't overclock or undervolt your phone -
leave it to the guys who really understand what they are doing.
Thanks,
Vikas
Click to expand...
Click to collapse
^*v*^*v*^*v*^*v*^*v*^*v*^*v*^*v*^*v*^
Memory Management
Did you know that you can also free up some internal memory space by just basic maintenance? You can install a Cache Cleaner from the market. I use Cache Cleaner NG (root) and CacheMate (root) which will clear your cache for you, Cache Cleaner NG will even clear your cache on your SDcard. Open Root Explorer and if you see a bunch of free floating cache files, those need to go. Wasted space. Small in the scheme of your SDcard, but still wasted.
So here we go (best part is at the bottom though):
Ok so you go into XDA on your phone, go to the themes page and look at what and how people are theming their phones or see some pix of someone's SetCPU profiles. All those develop a cache that takes up space on your phone. Now lets say that you go to the market and look through some apps or update your apps (more on this later). This also generates cache, usually up to 2-4mb. Ever try to download something from the market and it says something like "not enough space". This not needed cache may be some of the reason.
Here are some tricks and apps that some of you may know and also some tricks that I have found that I am sure most don't know about.
SOME GOOD LOW MEMORY APPS:
Cache Cleaner NG and Cache Mate (both root and free-Cache Mate has a paid but the free one works just fine.)
Diskusage (free) ~ This one will show you a graphical version of your /data/apps and also you SD card to show you exactly what is taking up so much space. You can click on that item and hit "Show" and it will take you to the app's page in Manager Applications. It also has a root function too that will allow you to see what is in /system, /cache, /data,…
Some sort of file manager to get to some things I'll mention below. (I use Root Explorer)
SOME MEMORY CLEARING TIPS AND TRICKS:
Home Launcher ~ If you have a 3rd party home launcher, see if it has the ability to long-press an icon to take you to its screen in the Manage Apps section. I use APEX and if you long-press on say Market, it takes me to the same place as is I were to go to Settings->Applications->Manage Apps->Market. Instead of all that, just long-press on the icon and BAM! it takes you there. Here you can clear out your cache for the market or delete the data (if you need to do that). Or clear the cache of the XDA app b/c you looked at too many pix.
Browsers ~ These develop cache that takes up memory and space, especially the stock browser. If you use a 3rd party, you can get the settings to clear cache, cookies, passwords,…on exit. I use Dolphin, but I am pretty sure that most have something like this on them. (side note: most 3rd party browsers once exited will not run in the background unlike the stock one)
Media ~ So you download a bunch of mp3's from the net or click on some pix and save it to your SD card. Or maybe you just felt like wiping your card and having a fresh start. Every time you reboot, you phone will scan media. No big deal, but the more you criss-cross things from PC to phone and back again, it can create a bunch of double files in your media cache on the phone. With the proper placement of .nomedia files (this prevents your media scanner from doing just that, scanning media- i.e. pix, jpegs,…Don’t place a .nomedia in your music, album art or DCIM files**bad).
Every once in a while, I'll hit the Diskusage or go to Manage apps and clear the media cache. Then I got to my file manager and the DCIM->Thumbs and delete the .Thumbnails files (should be 2). Unmount the SD card and remount to start the media scan, pull up the Gallery and wait for the thumbs to come back (depending on how many you have, this could take awhile). By doing this you can get almost 5 mb back if you have a bunch of double scans in your media folder.
AND NOW FOR SOME TIPS THAT MOST COULD NOT KNOW:
LOSTDIR - Lets say that you have your phone plugged into your PC and for some reason you, in a fit of rage, jerk the plug out without unmounting it first. This creates a file that is put into your LOST DIR folder on your SD card. Anytime you don't safely unmount the SD card, it will create a file in that folder. In the scheme of the SD card, it isn't too much, but I don't like having useless items free floating about.
Here is a good explanation of what the Lost.dir is for, seems legit, I buy it.
TOMBSTONES - So you are downloading an update from the market and for some reason your phone freezes and the Force Close-Retry-Wait doesn't work out for you. You have to do a battery pull. Frustrating I know and the memory takes a hit too. Every time you have to do a battery pull because of a freeze up or something of the like, it creates a TOMBSTONE file in /data. These are useless and can be deleted. If you are flashing ROMs and are constantly having to do battery pulls b/c market crashes or an app freezes, then you are creating a Tombstone file.
**Here is where your file manager (with root) will help. Go into /data and scroll all the way to the bottom and open /tombstone. There should be some files in there and depending on how many there are, I could be a nice chunk of wasted memory. Just select all and delete. They are not needed. Your internal memory should go up by doing this.
LOST & FOUND - Same scenario, but now go into /data/ cache or /cache and you'll see Dalvik-Cache (don’t mess with this), Lost & Found and Recovery. If you tried to download an app and it got frozen for some reason and had to do a battery pull, the apk will be free floating in there, uninstalled (free floating radical). You can delete this. While it isn't in the Dalvik-Cache folder, it is taking up space. Once you are able to download something completely and correctly from the market, it will populate into Dalvik-Cache correctly and won't be a free radical, as I like to say.
Useful Apps
These are some apps that will help you get the most of your battery life. I will put a brief descpition of them and you can also click on their names to take you directly to their market link. Note that some of these are ROOT apps and almost all of them also have PAID versions that greatly expand their functionality. Use the free ones and see how you like them and then kick in for the PAID ones if you want. The only one that I really suggest paying for right out of the gate to get the most out of your battery is Juice Defender Plus.
Tasker –
Paid app from the Market. This app is highly technical and not for noobs. Use at your own risk.
I would love for some of you out there to give me your Tasker Battery Saving Profiles. Either put them in the thread here or PM to me directly.
Here is a thread about how it works by brandall:
[TUT] The Ultimate Noob/Beginners Guide to Tasker
Greenify –
XDA Thread is here: READ IT (at the very least, read the OP)
This app is probably one of the best battery saving apps that has come out in quite a long time. It allows you to "Hibernate" apps that are not being used at the time, get them out of the foreground and prevents them from running when not in use, thus eating battery.
It is really easy to use. All you have to do is fire it up, grant Root and then select the apps that you want to "Hibernate". (Note: be very careful what types of apps that you do this with, i.e. /system/apps, as it could cause adverse effects like missed notifications, missed SMS/MMS, misbehaving apps,...you get my point I hope).
Batstat Widget –
I know, I know. Above I said that widgets were nothing more that monitoring apps on your home page, but this one works great, has low memory and is very, very simple. It shows Charge in %, Volts to know when you are FULLY charged and Temperature F/C to tell you that your phone is getting hot and exactly how hot it is.
BetterBatteryStats –
This app will show you what exactly is eating at your battery. Processes, Running Services, Wakelocks, Partial Wakelocks. It is a PAID app but for XDA users it is free. See here for more extensive details, instructions, screenies, change-logs,... and credits go to Chamonix and his development team for this app.
JuiceDefender (Plus) [Since I use JD+, that is what I am going to refer too.]
–
This app’s ability to kill Radio/Data has NO EFFECT on phone calls or messaging. You will still get that call in the middle of the night you were expecting.
If you set it to custom, the go into the settings tab on the right and then all the way at the bottom, there is two buttons to push, The first in Interactive which will pull up Juice Defender for up for any app that isn't already configured and the other is Configure Apps. This is the one that you can customize on an app-to-app basis where if you are no using an app and the screen is locked, it kills the radio/data traffic for that app.
Say you are listening to IHeartRadio, this you would want either Enable or Enable/off (which means the screen will be locked but the radio/data will be working). Now take the browser. If you are not using the browser, then you don't need it transmitting data right? So you would set that one to Enable (which means that it will only enable data traffic when that app is being used).
Juice Defender only works when the screen is locked (WidgetLocker lock screens interfere with JuiceDefender), don't forget and all widgets are battery drains b/c all they really are is a monitoring app and if it is tied to something like Facebook or Google+, then that data will be running constantly.
Settings:
Enable = Radio/data on when app is in use (front)
Enable/off = Radio/data on for background apps (when screen is locked)
Disable = Disables radio/data traffic completely when that app is running
Do Nothing = What is says
Examples:
Angry Birds = Disable (Here is a little known trick that I use for this and any game with Ads. With this and something like Adfree, no more ads in Angry Birds even though the ads are embedded in the .apk)
Pandora/Jango/ Tune-in = Enable/Off (this will keep your battery temp down when streaming)
Browser/ Market = Enable (not enable/off b/c then it will keep your radio/data open)
Beautiful Widgets = Enable/off
mClock/Clockr = Enable/off
SMS/MMS = Enable or Do Nothing (why would you push disable)
I have been using JD+ for over a year on 3 different phones and multiple ROMs and have noticed a considerable difference in battery life. Just takes some time to figure out YOUR settings and what YOU like. I have also used it on Stock kernel and had no problems either.
Here are my personal setting but I am on JD+ and not Ultimate
Profile - Customize
Notification - Graphical
Settings
Mobile Data and WIFI both Enable
Options - Auto Disable
Location - Disable
Schedule -Enable --->2hrs
Night Enable --->12a to 9a (user take priority)
Apps --.Set to Interactive
E = Enable
ESo = Enable/Scrren Off
D = Disable
DN = Do Nothing
At-Bat12 = ESo
IHeartRadio = ESo
Jango = ESo
Sticher = ESo
Dolphin = E
Google Play Store = E
Messaging = E
Twitter = E
XDA pre = E
Zedge = E
Angry Birds (all variants) = Disable --->You get no ads this way wink wink
These are all Do Nothing
Addfree
Apparatus
BW
Betterbatterystats
Cachemate
Elixir
Fasterfix
FlickGolf
Google Search
Maps
Moboplayer
PowerAmp -->I can listen to music without it looking for Album Art b/c it is set to do nothing, so one of the above apps take priority and when the screen is off, data is off when I am listening to music
Quadrant
Blah, blah, blah you get the idea.
If you have every app you own and in the phone set to do "something", then you are going to run into priority issues when multi-tasking which will kill your battery for 1 b/c it is opening and closing radios and 2 for the RAM it is taking to figure out which priority take the lead. Hence why I have so many set to Do Nothing.
LBE Privacy Guard –
There may or may not be some issues with this app and Jelly Bean, so make sure you read the Market Comments and hit their website to make sure. Thanks to mypenismighty for the tip.
This will go good with JuiceDefender, as they both prevent unwanted data transfer. Protect your privacy by controlling the permission of each application to access your sensitive data. Block malicious operation from Mal-wares and Trojans. Block unwanted network traffic if you don’t have a unlimited data plan. Find out which application is trying to steal your privacy by checking the security log.
RAM Munchers eat battery too. These will fix that for you.
Autostarts (paid-CAUTION this is for advanced users) –
Keep control over your phone: See what applications do behind your back.
Shows you what apps run on phone startup, and what other events trigger in the background. Root users can disable unwanted autostarts and speed up their phone boot.
Watchdog –
See what is eating your RAM. Hint: if it is using RAM,then probably it is also using battery too.
Spare Parts –
Spare Parts allows you to enable some settings
that are not found in the default setting menu
Process Monitor –
List the running process on your Android device.
Long click item to kill application or open application.
Fastboot –
This is a handy little app that kills all your services at once and lets them restart back up. I use this right before I hit the lock screen, so that if any app-services are running that I don’t have configured in Juice Defender Plus they will be killed, frees up about 50-70mb of memory, and then I lock the screen and JD takes over. This one is optional if you want it or not. I like it just fine and it works for me.
Matte Screen Filter –
Puts a sort of Dim setting on your screen. Almost like a display overlay, ok? And I did mean to rhyme those. I don’t use it because I have my display set how I want it but you can.
Battery Calibrator –
Pointless, but if you want to check out more info, click the hide tag below.
If you are having some haywire battery readings, this is for you. THIS WILL NOT INCREASE YOUR BATTERY LIFE, but will give you a truer reading if your battstats somehow get corrupted.
When you flash a new ROM, it is always best to wipe the old battery stats associated with that ROM, so you can start fresh as a daisy. How this works is you plug you phone in and charge to 100%, do not mess with it or surf the net (I do this overnight). While still plugged in, hit the apps, grant SU permission and hit the Calibrate Battery button. Grant SU permission again and once done, unplug your phone. Your Batterystats.bin has been deleted. You running your phone down by just using it normally. Most say to run it until it shuts off, but I have had bad experiences doing this, so I let it get to 10-15% and plug it in then. Charge fully up to 100% (again no surfing or games) and you will notice a dramatic increase in battery life.
**Note that this can be done two other ways. You can boot into CWR or Custom Recovery and go to Advanced Settings and there will be the Wipe Batterystats.bin option. Or you can do it manually by going into /data/system/ and deleting the batterystats.bin in there. Any of the three methods work to get the entirely same result in the end. I just like using the app or manually myself. **
Why battery calibration is important and what it is doing.
The app and what it does is more for when you are flashing a ROM and have around 60% and then once booted up fully, you charge it up to 100%. Decided you don't like your ROM and go back to your original ROM via backup, it will show 60% instead of the 100 or 90% you had before you went back to back up b/c you backed up the batstat bin when you nandroided your original ROM. Also simply charing your phone up to 100% and shortly after you unplug it, the Battstats will reset.
Recently (about this time last year) there has been information debunking this process. I will post it below. Here is the post by Dianne Hackborn, a Google Dev on her G+ account.
Dianne Hackborn - Jan 12, 2012 - Public
Today's myth debunking:
"The battery indicator in the status/notification bar is a reflection of the batterystats.bin file in the data/system/ directory."
No, it does not.
This file is used to maintain, across reboots, low-level data about the kinds of operations the device and your apps are doing between battery changes. That is, it is solely used to compute the blame for battery usage shown in the "Battery Use" UI in settings.
That is, it has deeply significant things like "app X held a wake lock for 2 minutes" and "the screen was on at 60% brightness for 10 minutes."
It has no impact on the current battery level shown to you.
It has no impact on your battery life.
Deleting it is not going to do anything to make your more device more fantastic and wonderful... well, unless you have some deep hatred for seeing anything shown in the battery usage UI. And anyway, it is reset every time you unplug from power with a relatively full charge (thus why the battery usage UI data resets at that point), so this would be a much easier way to make it go away.
Click to expand...
Click to collapse
Here is a post from this thread with ERD Entropy512 and I discussing the Battery Calibration app.
Proof that these things work. Stock battery by the way. Sorry for the huge pix. I'll tag them with a Hide Parse for better viewing real estate.
{
"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"
}
Battery screenshots as of 12/13/12
View attachment 1561698View attachment 1561700View attachment 1561701
Change Log:
9 August 13 -Added in Greenify, Tasker, Kernel settings, cleaned up a bit.
13 December 12 - Added more battery screenies
2 November 12 - Initial Post
***********
If anyone has any tips or tricks that they want to share, by all means post them in here and I will link it in the OP. We are all in this together.
After reading this posts I am afraid to even use my phone cuz battery will drain lol jkjk! Thanks great thread!
Awesome thread man! Really glad to see you brought it over here!
Thanks for taking the time! I know it'll come in very handy for just about everyone.
Great job on a great guide!
:thumbup::thumbup:
Sent from my SGH-T999 using xda app-developers app
Woodrube said:
Y U Quote the whole OP
Click to expand...
Click to collapse
Awesome guide.. We thank you
Sent from my SGH-T999 using xda premium
This is some really great information. Thank you for taking the time to share it with everybody.
I knew it wouldn't take long for this to get to the top!
:thumbup:
Sent from my SGH-T999 using xda app-developers app
Great thread thank you
Sent from my SGH-T999 using xda app-developers app
I wanted to warn people that LBE Privacy Guard caused crazy boot loops for me. The reviews from the Play Store suggests that it's a Jellybean issue. Anyway, I was able to go into recovery, fix permissions, and force stop and uninstall before it went crazy again. Other than that, thanks for the great tips!
Woodrube good post, I remember seeing this in the vibrant section. Keep up the good work mod.
Sent from my SGH-T999 using Tapatalk 2
Thanks man. I ported the meat and bones of it over, but I added a ton of stuff specific to the SGS3, plus the sections about Governors and I/O schedulers.
If anyone reads this, I could use more OC/UV examples to put in the OP. It would be much appreciated.
This is great, what really got me is how the phone doesnt automatically go to the best tower for the best signal, so I will defnitely start toggling airplane mode when I travel, thanks a lot for all this helpful information and apps that can help up save battery as much as possible!
Be sure to turn off Latitude updates in
Maps > Menu > Settings > Location settings > Location reporting > Do not update your location
Already on the portal.
Great Great Great!
Thanks a lot.
Plus Post for anyone.....we seem to forget the things that kill us....back stab us the most when it comes to Battery Life!!
GOOD POST!!! VERY DETAILED AND INFORMANT!!!!
Great advice on the whole, but I don't agree with the stuff about app widgets.
Widgets don't use a bunch of resources just because they are widgets - I think you could almost say the opposite: the design of widgets allows them to be visible on your desktop without using any resources because the app code that controls the widget only needs to be loaded when the widget changes.
In the end, the resources used by an app widget depend on what it does and how it is designed - same as for any app. If your widget is supposed to go to the network and update some info for you every few minutes then this will drain your battery. However, there are tons of utility widgets that do nothing (and are not in memory) unless they are pressed or one of the phone states they are listening to changes (e.g. a radio is turned on).
Of course, a badly designed app will hurt your battery regardless. Personally I think apps need to get away from creating a custom Application object since these get instantiated whenever the system creates the app's (or app widget's) process, even if it is just to update a widget.
Nice thread
Thxs for this nice thread Any ore would be appreciated.
I have learned a few things besides already being techy.
Nice to see whole lot of apps for android
Welcome to decimalman's kernel playground!
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
Underclocking down to 54 MHz, with stability improvements
Undervolting compatible with most apps
Fast charge without unplugging first
Glorious animations for the notification and softkey LEDs
Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
Automatic mpdecision and auto-hotplug are only enabled when needed
Adjustable minimum voltage for stability on finicky processors
Optimized UKSM to free up some extra memory
Code optimizations for size and speed
Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
Nandroid!
last_kmsg and/or logcat or it didn't happen.
Other kernels have their own threads or forums. Discuss them there.
Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
Be silly. We're here to have fun.
Installation:
Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.
Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
FauxSound support
Strip more useless stuff
A few bonus optimizations
4/8/13 (3.4):
Port everything except erandom from 3.0
Enhance cpufreq for easier configuration
4/24/13 (3.4):
Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
Lots of CM/CAF/Linux updates
Working AssWax governor
Trinity colors support
sio, zen I/O schedulers
erandom is back!
Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
Probably lots more, but there's hundreds of commits to sort through...
5/29/13 (3.4):
Bugfixes: better overclocking support, better hwrng support, etc.
Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
Automatic auto-hotplug
New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
6/14/13 (3.4):
Bugfixes: fix several critical bugs in the 5/29 release.
9/7/13 (3.4):
Fixes for OC, UV, auto-hotplug.
A few new optimizations.
Synced up with CM.
9/20/13 (TW):
Ported everything from AOSP to TW.
9/20/13 (4.3):
Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
Nothing interesting at the moment.
Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
Create a folder on your internal storage named "dkp"
Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
Code:
su
dkp
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.
sysfs:
It's possible to adjust all the settings available in dkp without using apps. Because they show up as files, settings can be adjusted with file managers, terminal emulators, adb and initscripts. Here's the most interesting files inside sysfs:
/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors (not available on newer AOSP builds): display tint (0 = very red, 2 = default, 4 = trinity colors)
/sys/class/misc/gammacontrol (only available on newer AOSP builds): various color controls. See this post for details on enabling Trinity colors on builds that use these controls.
/sys/devices/system/cpu/cpu<N>/cpufreq/UV_mV_table: voltage table
/sys/devices/system/cpu/cpu<N>/cpufreq/scaling_...: scaling_governor is the governor, scaling_min_freq and scaling_max_freq are the minimum and maximum frequencies, scaling_available_governors and scaling_available_frequencies show the available governors and frequencies
/sys/kernel/dkp/force_fast_charge: fast charge
/sys/kernel/dkp/link_core_settings: when linked (the default), frequency settings and some governors are automatically copied to the other core
/sys/kernel/dkp/vmin: minimum processor voltage in mV
/sys/kernel/mm/uksm/run: activate UKSM
auto-hotplug tuners:
These show up in the governor settings for any governor that doesn't do its own hotplugging. They only take effect when using auto-hotplug, so you'll probably need to disable mpdecision in Trickster.
hotplug_intpulse: when set to 1, automatically turns core 2 on whenever the screen/buttons/whatever is pressed. Default is 0.
hotplug_sampling_periods: number of samples to use for average number of running tasks. Default is 15.
hotplug_sampling_rate: number of 'jiffies' (currently 1 jiffy = 10 ms) between each sample of running tasks. Default is 20 (0.2 sec).
hotplug_enable_one_threshold: the average number of running tasks required to turn core 2 on, multiplied by 100. Default is 125 (1.25 tasks on average).
hotplug_disable_one_threshold: the average number of running tasks required to keep core 2 on, multiplied by 100. Default is 250 (2.5 tasks on average).
freelunch/nanolunch tuners:
freelunch and nanolunch aren't materially based on other governors, so their configuration is quite different than other governors. There's lots of tuners, since I haven't really decided on an ideal tuning. I encourage experimentation! I'll explain a bit of how these governors work before actually listing the tuners.
Generally speaking, there are two modes: in "normal" mode, sampling is done occasionally and frequency is generally increased slowly; in "interactive" mode, sampling is done much more quickly, and frequency increases much more quickly. "Interactive" mode ends after several samples of very low usage. The idea of a "hispeed" frequency is used in lots of governors, and it refers to the frequency that the CPU will jump to when more CPU usage is needed; generally, it's a generous estimate of how much CPU will be needed. Here, the hispeed frequency is adjusted on-the-fly, increasing when more CPU is needed and gradually decreasing when the CPU is idle. In "interactive" mode, the hispeed frequency is kept fairly high so that everything will feel snappy.
Hotplugging is taken care of in the least complicated (and in my opinion, most reasonable) way possible: if core 1 is using lots of CPU, and there are several tasks running (in other words, if it's likely that core 2 will have something to do), core 2 is turned on; if either core isn't doing much except using power, core 2 is turned off.
sampling_rate: the usual
hotplug_up_cycles: number of consecutive heavily-loaded samples before core 2 is turned on
hotplug_down_cycles: number of consecutive lightly-loaded samples before core 2 is turned off
hotplug_up_load: number of running tasks required to bring core 2 online
hotplug_up_usage: number of used CPU cycles (in thousands per second) required to bring core 2 online
hotplug_down_usage: number of used CPU cycles (in thousands per second) required on both cores to keep core 2 online
overestimate_khz: number of CPU cycles to overshoot usage by in "normal" mode
hispeed_thresh: if CPU usage is within this many cycles (in thousands per second) of the maximum frequency, frequency will be increased to the hispeed frequency. Generally, hispeed is pretty low in "normal" mode, and fairly high in "interactive" mode.
hispeed_decrease: when the CPU is sitting idle, the hispeed frequency is decreased by this amount each sample (this isn't ideal, but it works)
interaction_hispeed: the initial hispeed frequency when switching to "interactive" mode
interaction_return_cycles: number of consecutive lightly-loaded samples before returning to "normal" mode
interaction_return_usage: number of used CPU cycles (in thousands per second) required to stay in "interactive" mode
interaction_panic (nanolunch only): when set to 1, allows aggressively jumping past the current hispeed frequency under some circumstances
interaction_sampling_rate/overestimate_khz: equivalent to the "normal" versions of the tuners, these take effect in "interactive" mode
Just loaded it on pa 3.15
Sent from my SAMSUNG-SGH-I747 using xda premium
It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app
rmead01 said:
It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It doesn't, but I'll merge it and put out a test build.
decimalman said:
It doesn't, but I'll merge it and put out a test build.
Click to expand...
Click to collapse
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app
rmead01 said:
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae
Thnx for this kernel
decimalman said:
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae
Click to expand...
Click to collapse
Maybe I was just seeing things, had just watched jurassic park in 3d.
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
rmead01 said:
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
+1 on these questions
Sent from my AT&T Samsung Galaxy S III
rmead01 said:
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
Click to expand...
Click to collapse
Answered my own problem. I installed trickster as mentioned in OP and all voltage settings stick no problem with no issues.
rmead01 said:
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this into 3.0 and 3.4, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).
decimalman said:
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this in, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).
Click to expand...
Click to collapse
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that figured out I removed kernel tuner. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point. just as an example, some governors would be better for screen on/off and tasker could switch these to edge out battery life.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both governor and voltage adjustments well. i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.
rmead01 said:
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that was made it was no problem. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both well, i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.
Click to expand...
Click to collapse
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Edit: I think I've got Voltage Control fixed. I should be able to get Kernel Tuner working without too much work. I haven't even looked into Performance Control yet.
decimalman said:
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Click to expand...
Click to collapse
well good job so far. batt life has been top notch. minimal drain in use and my over night idle drain was only a few %. I have things setup to disable wifi when sleep and also turn off mobile data when wifi is connected. A bit over the top but every bit helps.
:good::highfive:
I know I've been grilling you today but...
Kind of curious what the new tunables do. I haven't touched anything since it's working so well but there is always that part of me that wonders what adjust parameters will do. Is there any kind of reference for this governor that could indicate that type of info?
Does your kernel support faux sound app?
stevehkim said:
Does your kernel support faux sound app?
Click to expand...
Click to collapse
Yes. 3.0 and 3.4 both have support.
As for tuneables, I've been meaning to post a writeup but haven't gotten around to it. You're not the first to ask about it.
Sent from my SPH-L710 using xda app-developers app
This is a fantastic Kernel! The battery life has been outstanding so far. Thank you for your amazing work!
KT-SGS4 [Kernel] Builds [Discussion] ◆ALL VARIANTS◆ [AOSP/TW/GE] ★KTWEAKER SHOP★
ALL CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR THIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.
Welcome!
Some of you may know me from the S3 forums but to clarify, I had offered a number of kernel builds for users to easily obtain all within a single thread. I am proud to say it has gained a significant amount of feedback. So I come to YOU today with the same purpose in mind. I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on updated builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS4 kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for users to experiment with and see which versions function properly on each of their respective phone models. I'm also bringing to you my Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S4 users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for T-MOBILE users
POST #3: Reserved for AT&T users
POST #4: Reserved for SPRINT users
POST #5: Reserved for VERIZON users
POST #6: Reserved for INTERNATIONAL users
POST #7: Reserved for the KTWEAKER SHOP
POST #8: Reserved for SCRIPTS & TEST PROFILES
No need for flashing previous builds to receive OTA's as all posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
Please make absolutely sure you are downloading from the post intended for your phone. Nor I or Ktoonsez will be held liable for anything that may occur to your device. So please...
***FLASH AT YOUR OWN RISK***
"Smart stay and smart scroll on pre-MF4 TouchWiz ROMs require the 2013-06-10 TW build."
Click to expand...
Click to collapse
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
Click to expand...
Click to collapse
If you are manually UPDATING the kernel, follow my recommended procedure for best possible results:
1) Backup current Ktweaker settings
2) Navigate to Settengs > Apps > Ktweaker
3) Clear cache and data then force stop
4) {Optional} Open any root browser, mount as r/w, then navigate to /system/app/ and delete Ktweaker apk
5) {Optional} Clear all Superuser logs
6) Reboot Recovery
7) Flash kernel
8) Wipe cache/dalvik
9) Fix permissions
10) Reboot
11) Restore Ktweaker settings
12) Profit?
If you get this message after booting up the kernel:
"The device has detected an application attempting ..."
Go to the "/system/app/" folder and delete the files that begin with "knox"
Click to expand...
Click to collapse
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945
**********T-MOBILE**********
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/k9ryAE0dwLHs
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/hsciC7dkz66V
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/9Gtgf0GUJkS4IU8
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/4ZzqCaMCwfDx
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/kEWuwwaGj8j2
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/EGHYzNqxuLGd
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/P0SYiTNnxfIj
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/doRqwyyJgbNz
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2289140
**********AT&T**********
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Canadian users, DO NOT FLASH the kernel from this post. You MUST flash the TMO version from post #2
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/bTEPKJuknXn3
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/X0ZwwQVRHPKd
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/6a8eptTrL6gD3hT
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/lSb0xRxqmICV
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/deGgFdixXTXW
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/BIusi3ksxYws
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/hfKGlCGgCSB1
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/O02Gej8ozbOw
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2292341
**********SPRINT**********
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/aNXcVH2QVfB9
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/fj30ECCfQzVf
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/lpekDcQZijcg
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/ujl1pB38cP7W
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/oinxlW3Uq9Ai
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/WLvmsMj4YCdr
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/jsvgAUpq39ti
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2288309
**********VERIZON**********
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM for TW version
•Must have a AOSP Rooted ROM for the AOSP version
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/87bRx3sudelf
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/hgsxlxegZ3WD
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/6JDHcwscMNuzQyq
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/XxBonTWMjCwf
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/Z7WeSmat4YTN
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/3PkFEpycgAqU
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/rTDTNhruhpsR
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/HtHyI4MhQyPc
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2294083
**********INTERNATIONAL**********
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/jcvkN6ELhSyw
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/ajiB89TGosd0
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/UQPuEEUNYc04
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/sw8XSJUsZk09
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/rDjb2DBt6C2A
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/Wk9iHznO3haQ
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/yUl248Xo2RcU
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/ZyuctnlWseGE
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2297379
{
"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"
}
Welcome to the Ktweaker Shop!
Here you will find all of the pre-configured settings provided by myself and some of our fellow users. As a proud member of Team Kernelizers, I am offering a variety of profiles specifically for S4 users with their personal needs in mind as it's pretty clear no one favors the same governor, scheduler, etc.. Any suggestions are always welcome. All future settings will be added here for sharing and discussing our settings as well as gaining approval on a profile to be added into the built-in Shop in Ktweaker. Keep in mind that results will always vary per device regardless on the settings being used.
All profiles have been grouped into 3 sub-categories; "Conservative", "Balanced", and "Performance", which are used to classify each profile based on their overall performance and what they are expected to deliver to your device. The 4th sub-group is where you can find some of our best "Projects" in which offers 2 or more profiles for each. Make your selections based on your usage and apply what works best for you and your phone. We're here to help eachother out and with more options comes better experiences for everyone running this kernel. Big thanks to ALL who have contributed!
So shop around.. pick and choose.. load and go!!
Installation
Download links will include the specified profile(s) as well as an "Adjustments" and an "About" file. The "Adjustments" file is just for easy view of all the changes made to a profile compared to stock settings.
1. Download the file(s) to your phone.
2. Copy ONLY the XML(s) (DO NOT copy the "Adjustments" or "About" file) to /sdcard/KTweaker/Profiles folder using a file Manager of your choice.
3. Open Ktweaker app and click on "Profiles & Scripts" then click "Restore Prefs from sdcard".
4. The file you just copied should be listed there. Select the one you want to apply.
5. After applying, make sure the "Set options on boot" setting on the main menu of KTweaker has a little green text bellow confirming that the settings will be applied upon reboot.
6. Profit!
Conservative
Asking Alexandria
This is a battery driven profile in which focuses on saving as much juice as possible while also maintaining stability and providing an extremely snappy feel to your phone. It is quite possibly one of the smoothest and snappiest battery saving profiles available.
Why Asking Alexandria?
It's named after yet another one of my top favorite metalcore bands and I chose this because Alexander The Great basically ruled the world at one point and "Alexandria" is the female equivalent to that name, which has become known to mean the "one who comes to save warriors".
"Asking" was an addition to the title name as an indication in the sense that we are all asking Alexandria what she can really do to our phone.
https://copy.com/kqIXuJ1N8LLh
Bless The Child v3 (updated: 10~25~13)
Based on Ktoonservateq and aimed towards battery. This is specifically for all the battery hungry users out there wanting to conserve as much power as possible. So don't expect the BEST but rather decent performance out of this one.
https://copy.com/K1bNhNx6nFYd
Dead By April v2.2 (updated: 11~15~13)
This profile attempts to bring some of the best battery life possible to your device. It is similar to Bless The Child but takes things a step further . It now focuses more on snappiness but still maintains it's well known battery conservation. It manages to maintain a smooth ui for your average daily use.
https://copy.com/J8lnimxbvwpF
Infamous 1.0 by @PiggySmalls502
Infamous is a work of pure and utter boredom, and a desire to use the SLP governor. Profile uses very low CPU frequencies, yet still runs very smooth, while still seeing great battery life.
Click to expand...
Click to collapse
https://copy.com/qqCrRDZiZBNh
Moonlight v3 by @Tunasty (updated: 2~12~14)
This profile is based on Ktoonservateq and Mamba's Daylight profile. This profile is aimed towards battery and be able to use your phone without any lags. Performance has not been sacrificed either. Max Mhz is 1890 which works out pretty awesome. KT's AWESOMEEE kernel and Moonlight profile will make you fall in love with your phone
Click to expand...
Click to collapse
https://copy.com/yoLhPpe1QY0Q
Smooth Criminal by @ORT14
Why Smooth Criminal you ask? Simple, this profile will keep your phone running as Smooth as ever, so smooth that it is Criminal to still get this type of battery life. Last test my phone went over two days with six plus hours of screen time without a charge (see below) while still running super smooth. This profile will change your life (well maybe not). Give it a try and let me know what you think.
Click to expand...
Click to collapse
https://copy.com/yQyI4ejR7uPE
Super Battery Saver 3.0 by @MavereXx (updated: 10~7~13)
This profile is not about performance, even though its surprisingly smooth. Gentle Undervolting.. your s4 now has only a 1.1ghz processor. .. but remember: This is when battery life is all you care about!
Click to expand...
Click to collapse
https://copy.com/GKQ0OqDVociy
What Lies Beneath
This is an extreme battery performance setup in which essentially transforms your quad-core device into a dual core device.
Why "What Lies Beneath"?
You'll find that during light to moderate operations the cpu remains at lower frequencies for an extended period of time and will only jump to max when needed. Although it's clocked at a max of 1.3ghz it maintains a surprisingly smooth and snappy feel to your device at such low frequencies. This is where battery life is also expected to come in to play as well.
https://copy.com/m0EnRGUpkEMp
Balanced
3hands by @sew3521
This profile is a combination of my 3 favorite profiles; Ktoonsified v2, Project Icarus-Kamikaze, and Balanced Bull: Reloaded. Each of these 3 different profiles has great aspects however I thought I could combine them to make one super efficient profile and this is what I came up with. There is an extreme amount of undervolting going on here however my S4 runs extrmely stable (Sprint S4 purchased on release day) and thanks to the Balanced Bull and Ktoonsified portions of this the interface is very snappy.
Click to expand...
Click to collapse
https://copy.com/wEHQOssGuSVw
Balanced Bull: Reloaded v2 (updated: 4~17~14)
These settings are very special to me as they were my very first, dating back to the Galaxy S3, and has gained an incredible amount of feedback. It has become notable for it's fairly smooth interface and amazing battery life. If this stacks up to your standards then I encourage you to use it!
https://copy.com/4XbEpD6HRYx6Qzw
Day Of Reckoning
Very similar to Nightmare To Remember but is aimed slightly more towards battery without deteriorating much of the performance. It is based off the Pegasusq governor.
https://copy.com/NkNqyUKjaudY
ECLIPSE v2 (updated: 10~25~13)
This is a performance oriented option where great battery life is also expected to intervene. This not only will bring an incredibly stable, smooth, and snappy feel to your device but will also benefit towards longer lasting battery so you can love and enjoy your phone the way you were meant to.
https://copy.com/BDIln0KrVplK
Hydra
Eclipse and Kamikaze clash with one another in this hybrid profile (BIG thanks to @mamba720027 for the amazing work done on Kamikaze!). This is perfect for those who favor one or both of these profiles. With the merging of some of the essential performance and battery elements of each profile as well as a few minor adjustments, this one also stands as it's own profile and it flies!.
https://copy.com/GuQZmkARaHKI
Ktoonsified v6 (updated: 4~17~14)
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a performance oriented option in which also offers a great deal of battery life. Haven't tried these settings yet? then what are you waiting for!! Load em up and be prepared for one of the smoothest and snappiest experiences ever!
https://copy.com/yJJgpIi40Ddp
Lateralus v2 by @CamFlawless (updated: 1~15~14)
This profile was designed in an attempt to strike a balance between battery and performance with a focus on conservative CPU scaling to maximize battery life while maintaining a smooth, fluid, and stable UI. I tested it with the Hydra script, but your personal favorite will work all the same.
Click to expand...
Click to collapse
https://copy.com/H6bXpcr0bEJr
Misanthrope by @CamFlawless
The misanthrope profile seeks to optimize the balance between battery life and a smooth, lag-free UI by following the sampling logic laid out by LuigiBull23. By allowing frequent sampling and increased polling, the profile will result in the CPU being at the optimal frequency more often and quickly. Additionally, the hotplugging parameters should allow the secondary cores to come online when needed and quickly turned off following the boost. Misanthrope is named as such, because this profile hates lag and battery drain.
Click to expand...
Click to collapse
https://copy.com/LljHyKj384rk
Nightmare To Remember
This will likely become your beautiful, never ending nightmare.. It offers a unique balance between battery and performance but unlike Balanced Bull, it is slightly more performance oriented due to the more aggressive scale up to max CPU. However, only 2 cores will be used for the majority of the time so you can still enjoy a nice buttery smooth interface with just enough juice to last you through the day.
https://copy.com/VMFboPCy2CwU
Ragnarok v2 by @mamba720027
This profile is tweak with 2 things in mind. Normal usage and gameing.
when doing normal tasks the governor would scale the frequency less aggressive and use minimum cores but would also climb to higher frequencys as required to complete a task depending on what apps you are useing.
Gameing or other high intensity tasks will have all cores active and cpu will utalize max cpu frequency.This will provide smooth gameplay for games such as Asphalt 8 and of course other similar games that requires a powerfull processor to justify its awesomeness. So if you want a low profile setup for regular usage to conserve battery and high profile setup for gameing and other high performance demanding tasks and dont want to swap between two profiles then this profile configuration should work nicely in such a scenario.
Click to expand...
Click to collapse
https://copy.com/rM3YflojYz9k
SRV v3.1 by @s3icc0 (updated: 2~14~14)
This profile focuses on excelent battery life with no restraints to performance but still keeping pretty conservative settings to allow all users to be able to use this profile (and script) without any problems. The Core 0 is driven by heavily tuned ktoonservativeq governor, ROW scheduler is used to maximize the read performance. The frequency used is 189Mhz - 1890MHz for CPU and max 450 for GPU, the voltages are -35mV for CPU and -50mV for GPU. There is no Screen Off profile. Vibrator strength is set to 50. Read Ahead is set to 1024. LED fade mode is set to slow blinking once a time.
Click to expand...
Click to collapse
https://copy.com/77TRXloQfKRm
Smooth Operator v5 by @mamba720027 (updated: 4~17~13)
This profile utalize all 4 cores on demand and serves as being a balance between battery and performance. Its as smooth as possible and utalize the full cpu power while operateing sensibly in governor scaleing.
Click to expand...
Click to collapse
https://copy.com/vmLLvFKhwwqV
*Stardust v2* by @mamba720027 (updated: 12~7~13)
This Profile I put together is based on the "AbyssplugV2" governor.
Everything is tweaked and the profile can run by itself or either use the "smooth operator V2" Script or Luigi's "Hydra" Script.
Both are found in Post#8 of the OP. The choice is yours.
Click to expand...
Click to collapse
https://copy.com/EalqZpGb4Gnh
Super Bull 2.1 by @MavereXx (updated: 9~24~13)
A derivative of Balanced Bull but aiming towards more extreme polarity of performance and battery life. Stable Undervolting for i337, i337m, m919, and i9505 CPU and GPUs. Overclocks up to 1998mhz going all the way down to 81mhz without causing severe lag or stuttering or slow wake ups. Tries to find the right balance between ultimate performance and battery life.
Click to expand...
Click to collapse
https://copy.com/Opsu7y1FLJx9
Undisputed 3 (updated: 12~11~13)
This is a universal performance setup in which combines the essential elements of other profiles by providing equal battery life, speed, performance, and stability to bring the ultimate experience to your device.
https://copy.com/UFreCzB1Wcpt
Performance
Crimson Dragon v2.1 by @mamba720027 (updated: 1~8~14)
This is a profile that i put together from a lost in the thread Dual Core profile "Lazy Dragon". What was suppose to be a V2 Update of it turned into a 4 Core profile and something totally new, Crimson Dragon. This profile is a variable of Performace and keeping things balance. Its very smooth on TW and produce great results on AOSP as well threw testing and feedback. Please enjoy this new addition :good:
Click to expand...
Click to collapse
https://copy.com/QjuMNNyyucBD
Feed The Machine
The exact opposite of Bless the Child. This is a performance oriented option for all hardcore users. If battery isn't a priority for you then this is a great option.
https://copy.com/oKLPQmmgzc1C
Ghost Rider by @galaxys3man30
this setup can benchmark on 1890,1944 and 1998 and its been really good on battery even thou its a performance setup think im going to call it ghost rider cuz its a sleeper yea it shows good battery life but behind that is the raw performance that is on demand when needed.
Click to expand...
Click to collapse
https://copy.com/pKAMrciYgUFo
KTGaming
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a super performance oriented option which allows me to play any game with ZERO LAG!!!!!!!
Click to expand...
Click to collapse
https://copy.com/iJzItwZxSYlp
Lightning Blade v2.2 by @mamba720027
This profile is aimed at performance and efficiently uses the 4 cores somewhat better than my first performance base profile.Â
Although it's aimed at performance it could conserve on battery as well because of the way cores are handled. If you play lots of games that require speed and processor power then this profile provides both.
Click to expand...
Click to collapse
https://copy.com/zs89qlw4CQr2
Notorious by @PiggySmalls502
This is a derivative of Feed The Machine. Hotplugging was turned back on and I/O scheduler was switched to ZEN along with a few other minor changes to the profile. It's aimed towards slightly better battery life but doesn't deviate too much from the performance aspect of things found in the original profile.
https://copy.com/Ip1PJtY7LCdI
Overactive Imagination by @CamFlawless
The profile aims to be as smoooooth as possible and draws inspiration from @LuigiBull23's Rebirthing profile.
Click to expand...
Click to collapse
https://copy.com/YyyJat03RZMtH7o
Projects
Comatose
This project was inspired by the album of the same name by my #1 favorite rock band of all time, Skillet. It consists of 3 profiles of which are also named after 3 of my favorite tracks from this album (included in the "Extras" folder) and all focus on one key element; VARIETY.
As the name suggests, "Comatose" is geared towards battery conservation. It focuses on keeping CPU low for a prolonged period but utilizes 3 of the 4 cores on touch and the 4th on demand for fluidity. Sample rates have been decreased heavily as to increase polling and allow the other cores to quickly spike towards higher frequencies for a given task then immediately drop back down as if the component had been knocked unconscious.
The second profile is "Rebirthing". This profile will counteract the affects of Comatose by heavily boosting performance as a means to bring life and energy back into this profile that remains unconscious. Rebirthing is intended for those seeking a performance-based version of Comatose but who knows... For such a power hungry profile you may just be surprised by the great battery life it also delivers.
Some of you may not favor the heavy battery conservation that "Comatose" offers or the overall power consumption of "Rebirthing" and much prefer a mashup of elements delivered between the 2 and that is the purpose of "Whispers In the Dark". This profile is directed towards finding the right balance between these 2 profiles while still acting as a it's own profile. It utilizes most of the performance aspects from "Rebirthing". The only major differences from that are touch_boost_cpu_all_cores has been disabled and touch_boost_cpu is set at 1134Mhz instead of 1458Mhz.
Like "Comatose" it uses super_conservative_screen_on as well as a high up_threshold for that extra boost in battery performance. The profile also idles at the same minimum cpu and gpu frequencies as "Comatose" but ALL profiles run at stock 1890Mhz.
All profiles maintain the same concept of rapid cpu polling. So yes, cpu will be working consistently but my theory here is that more polling will allow the kernel to rapidly check CPU usage, thus allowing CPU to change more frequently according to the load, which in turn will prevent persistent pegging of even higher frequencies and instead consume various amounts of power in various scenarios depending on your usage and consume even less when a specific task has completed and immediately drops the load.
This also applies to screen off states but that goes back to what was explained in this post regarding high vs low sampling rates and how they can greatly increase idle times depending on your screen off max.
https://copy.com/VMuyGiGJbxIc
Lucretia by @CamFlawless
The name draws inspiration from a Megadeath song with the same title. Great tune.
Balanced
This profile is based on my V1 of Lucretia and seeks to strike a balance in terms of performance and battery life. Offering exceptional performance and a fluid experience, Lucretia Balanced is a great profile for all your needs.
Performance
This profile is based on my V2 of Lucretia and is intended for those seeking high performance from their devices for the likes of gaming and such. Lag should be non-existent and your experience should be smooooooth. :fingers-crossed:
Click to expand...
Click to collapse
https://copy.com/sjCgexEGB1jo
Project Daylight v2 by @mamba720027 (updated: 12~23~13)
Day Light is focused mainly on battery conservation. I felt that its useless if its not smooth and lags alot so I add performance into the mix createing a profile that offers both while its first and foremost goal "battery performance" is still preserved and not diminish. This profile is yet unique and on a different level from my early release of "Icarus"
The contents are 3 profiles unique in their own way, "Daylight", "Daybreak" and "Experimental" along with a "Extra" folder containing wallpapers I created on our S4 for fun while testing . Kind of gives me some inspiration and sense of feel of what my objective is.
Daybreak is a crossbread profile of my Icarus Performance profile and Daylight. Its simply utilizing the performance power behind Icarus Performance profile while useing Daylight profile governor settings as its core to boost battery performance
The experimental profile is heavily undervolted/Underclocked with tweaked scheduler and governor. I taught if some of you could run it stable then it may produce great or mix results
Click to expand...
Click to collapse
https://copy.com/2vBCFVZP68gV
Project Icarus by @mamba720027
So some may wonder why the name "Icarus",why not Hyper Performance or Deadly Good Battery.
Well the reason and to begin explination,short history.
Icarus is a greek mythology who is seen today as a mythical pioneer that tried to conquer the skies.
I like that mythology cause it kinda corresponds to my own saying "fly high or fall hard" which means to aim high or fail trying. So their you have it folks and thus the profile name "Icarus".
And onto explination of each profiles.
The first is "Performance" which is catered for straight out performance with also good battery performance.
This one is for when u dont give a rats flying balls about battery really and just want everything super fast and smooth. But you maybe surprise of battery performance. I recommend everyone try this profile first. My current favorite
The second is "Conservative" this is for those seeking performance but also better battery performance than the first.
This one is the middle man or lady as u may want to refer to it. It gives the best of both worlds,performance and battery. So if the first leave you stranded then fear not, this is the one to turn too
The third is "Kamikaze" which means "god wind". It either knocks the daylight out of your Galaxy S4 due to its high undervolteing and mean intent on Battery Performance but still snappy.
This one the undervolting is of my personal voltage table that runs stable for me with other tweaks. If it runs successfully for anyone else then battery performance may be great.
This one is for those that likes the thrill of trying something new and unsure if it will work
Click to expand...
Click to collapse
https://copy.com/87kzjPQShn3Z
Sleeping Dragon by @mamba720027 (updated: 12~23~13)
Sleeping Dragon V2.1 Single Core
This is a single core profile aimed at consumeing the least battery for a time when you will be away from home or at work and away from the charger. It was a profile i played with at first as i did not expect it to mount as much with apps and system UI needing a right amount of performance from a CPU to meet todays tasks in performance. In the end i was able to tame the dragon and make it work as best as possible to achieve its goal
Sleeping Dragon V1.2 Quad-Core
This is the counter part of Sleeping Dragon Single Core but with many tweaked parameters to make it a fully functional 4 Core base profile in hopes to achieve close or same battery performace as its single core entity. Unfortunately i still am not sure if it measures up but what i know from previous test with settings @Stock it hold its own in battery department. I am pleased with the results although i would wish to see some light usage results from users. I am pleased to present users with this 4 Core or Quadcore profile
Click to expand...
Click to collapse
https://copy.com/vkDfMNiu2Sbs
If you'd like to contribute to the Ktweaker Shop all you need to do is post a profile/script you want to share and include a brief description of it's purpose. It will then be tested thoroughly by the community and based on feedback will be submitted here in the Shop for approval and sent out to the dev for confirmation on adding to the Shop in Ktweaker!
Useful Links
Information about our scripts/profiles can be found HERE
Interested in learning how to fine tune the kernel but not sure of where to start?
Please refer to this Ktweaker User Guide (thanks to @Perseus71) and you'll be tweaking in no time!
What in the world are CPU block cycles? Please check HERE
HERE is a great app by @elesbb that will allow the end user to set individual governor options for Ktoonservativeq when turning on the screen, charging, keyboard typing, or playing media.
Link to downloadable zip for all available ktweaker Profiles (Thanks to @CamFlawless)
https://www.copy.com/s/EhjYpSmACIyz
Profile scripts
Post #8 is dedicated to Scripts that will be used with some profiles. I also added a section for current test profiles and old test/experimental profiles.
[[Quick information]]
These scripts will either control CPU Cores 2,3,4 or all 3 and are only intended to work with the Ktoonservativeq governor. They may bring performance improvements or battery improvements based on the script governor parameters and how well they function for each user's daily activities.
[[#Ktweaker Script Guide#]]
First I want to thank KT aka Ktoonsez for provideing us with his kernel and all the wonderfull features and options at our disposal to tweak and make all these profiles and script possible. Also for implementing the Ktweaker Shop into his Ktweaker app so that it would be more convenient and easy for users to utilize these custom profiles and script as to maximize users experience.
I also want to thank Luigi for letting me join his band of misfits and being part of the Shop community. This opportunity have help me to use my potential to provide profiles and scripts that users have come to enjoy and help further in the thread.
Also thanks to everyone else that is actively supporting in the thread, some that are working behind the scene to help provide improvements and better experience for everyone. Big thanks.
::#Beginning of Guide#::
This is a quick step by step guide put together to help clear up any questions or help out those new to the Profile and Scripts section found in Ktweaker.
:#Before continuing take note#:
Swapping profiles and scripts you need to apply them in the following order first:
*Script first
*Profile Second
This order is to ensure Superuser Permission is given to both the script and profile.
Also note that you could choose to run a profile without the script. Running it with the script is optional. But for best results it's advised to first try the profile with the script it was intended to use with.
#
So now you're ready to try a script with your own profile or one from the shop but undecided as which to choose or how to go about loading the script.
#
Step#1
[[Chooseing a Script]]
To choose a script navigate to "Profiles and Script/Ktweaker Shop Scripts".
Here you will find a list of Scripts. Each script is named after its designated profile that it is intended to be used with. Choose one to view "ABOUT" which gives a brief description and additional information of the script and how it can be used with addition profiles. Some may or may not give this option to be used with other profiles as it may produce undesirable results but you are free to experiment.
Choose to download the script you want to use and in the "Profiles and Scripts" section choose "LOAD SCRIPT ON BOOT". This will allow the script to run on every boot of the device once their is a script loaded.
On the go you could also choose to load another script then apply another profile in this order as to let Ktweaker give both the script and profile SU permission to run.
Step#2
[[Chooseing a profile]]
Decide on how you want to use your device for the specific day,occasion or you may just want to set it and forget it based on being a performance user, conservative or needing a Balance of both to suit your demanding needs. You could also just be curious and want to try them all to see what works for you.
So open the Ktweaker app. Navigate to the "profiles and scripts" section.
Choose "ktweaker Shop Profiles" to bring up a list of profiles avaliable to you.
Here you can choose to view "ABOUT" which gives a brief profile description as to help you decide if the profile fits what you're looking for. You can also choose to view "ADJUSTMENTS" to see the tweaked parameters of the profiles or choose the option to "DOWNLOAD" the profile which will be saved in the ktweaker folder on your internal storage.
Now that you have chosen a profile,downloaded it and want to apply it. In the profiles and script section choose "RESTORE PROFILE FROM SDCARD" and you're done.
Click to expand...
Click to collapse
[[ Script Download Section]]
Dead by April V2.2 Script
This script utilizes the Conservative governor for CPU1. It was decided to apply this to the 2nd core and leave the others at default interactive in order to better serve battery life while still maintaining the only true performance aspects of the profile within the other cores. However, as CPU1 serves more priority over any other remaining cores, this governor was tweaked with slight performance enhancements as to allow for a faster ramp up to max CPU for that core during middle to heavy operation levels but will scale back down almost instantly and thus maintaining it's goal of keeping things low as often as possible, conserving battery. It's highly recommended to use with a balanced or straight performance profile very similar to Dead By April if applying this to any other profile.
Created by: LuigiBull23
Click to expand...
Click to collapse
Dead by April V3 Script
Core 1 - Conservative
Core 2 - asswax
Core 3 - interactive
A more detailed description about this script will be updated when the script is official.
Created by: LuigiBull23
Click to expand...
Click to collapse
Balanced Bull Reloaded Script
This script applies the Asswax governor to cpu1, Intellidemand to cpu2, and Adaptive to cpu3. Much like the profile it's twealed to focus on a direct balance between performance and battery. With the utilization of these 3 governors, CPU will spend less time at higher frequencies making scaling less aggressive during light to moderate activity but use the on demand performance of Intellidemand during performance critical situations, such as in game.
It can be used with other profiles much like this one in which uses moderate thresholds as well as a touch boost of 1134 or greater. As always redults will vary.
Created by: LuigiBull23
Click to expand...
Click to collapse
Smooth Operator V3 Scripts
This Smooth Operator script uses the Abyssplugv2 governor for Core1 ,badass for Core 2 and Adaptive for Core3. Each governor is set as to not scale too quickly nor too aggresively. The smooth operator profile on the other hand was tweaked with parameters to allow these cores to run when it is truely needed and to deliver performance with the right amount of cores online and save on battery.
So on another profile this script could deliver performance or save on battery depending on how the profile is tweaked. It's Characteristics will vary. It would be interesting to see how it performs with a performance base profile
Click to expand...
Click to collapse
Smooth Operator Infinity
Core 1 - Intellidemand
Core 2 - Intellidemand
Core 3 - Intellidemand
This script was tweak to work as a univeral and future here forth along side the 3 profiles smooth operator V5, Lite and Ultra.Thus the name "Infinity" at the end. The older scripts are also welcome to be used with these as users favor or see fit.
Created by: Mamba720027
Click to expand...
Click to collapse
Hydra script
This script uses the Dancedance governor for CPU1, Wheatley for CPU2, and Badass for CPU3. This script focused mostly towards battery conservation with some performance elements. With the high ramp rates of Dancedance and Badass's limited frequency logic, the script will bias the CPU at low frequencies and will scale up conservatively or immediately shift to an optimal frequency, depending on the task at hand if or when a larger and more persistant load is placed on the CPU. Wheatley will act more as the "On demand" partner here for that extra call in performance such as in games but for the most part the last 2 cores will remain off due to the adjustments within the profile.
This can also be used alongside other profiles but is recommended to apply to those similar to Hydra in which serves as a balance between battery and performance or one that merely performance oriented.
Created by: Luigibull23
Click to expand...
Click to collapse
Stardust Script
This Stardust script uses the badass governor for Core 1 and 2 while Core 3 uses the intellidemand governor.
This script was put together specifically for the Stardust profile as it is a profile based on the AbabyssplugV2 that utilizes the Autohotplugging feature in Ktweaker. This method of hotplugging was too aggresive to acquire the desired results needed to conserve on battery so I put together this stardust script as my other option to limit the scaleing up frequency for Core 1,2 and 3. Each respective governor limits the scaleing of their assigned core to a specific frequency which can be seen useing a software to monitor core activity. This way the script helps saves on battery as the same way the theory of underclocking applies.
So if you're gonna use this script on another profile I recommend it being on a performance or balanced profile as a already aggressively tweaked powersaveing profile may deem its outcome very laggy or sluggish.
Click to expand...
Click to collapse
Undisputed 3 Script
This script utilizes the badass governor for CPU1, Intellidemand, and Asswax for CPU3. Much like the Balanced Bull Reloaded script this is a balance between battery and performance. The only mere difference is that this script ALONE is slightly more battery conservative compared to BBR but results will obviously vary, especially depending on the profile this is used with.
It can be used alongside other profiles such as Balanced Bull Reloaded as the these 2 are very similar.
Created by: LuigiBull23
Click to expand...
Click to collapse
Crimson Dragon V2 Script
This Crimson Dragon script utilizes the wheatley governor for Core 1, intellidemand for Core 2 and Dancedance governor for Core 3.
The script is focus to use these 3 cores as to help conserve on battery threw the wheatley and dancedance governor while provideing ondemand performance useing Intellidemand.This script should work best with the Crimson Dragon profile but could also be used on similar profiles that's focus on delivering a balance between battery and performance.
Click to expand...
Click to collapse
Sleeping Dragon Quad- Core Script
This Sleeping Dragon quad-core script uses the intellidemand as core 1, Adaptive as Core 2 and Asswax as Core 3. Asswaxing is probably not for everyone but whatever works right. It works wonderful for Core3 here. Anyways these 3 governor helps mainly to Balance battery and performance here as with Sleeping Dragon profile it is tweaked in a way to keep things smooth/performance enough without scaleing the cpu too high frequently and extend the battery usage per cycle.
So this script you could try it with other profiles as well that have a touch boost value higher than 810mhz implemented to simulate a similar output that Sleeping Dragon profile and script combine produces or evin better with this script
Click to expand...
Click to collapse
Day Break V2 Script
This Daybreak script uses the Adaptive governor for Core 1,dancedance for Core 2 and intellidemand for Core 3. Each of these governor is tweaked to scale each core more of on-demand as to provide fluidity and performance to the Daybreak profile because of its high conservative property. Thus this script makes it possible to add performance into a profile that may not scale aggressively to highest frequencys often as to maintain battery conservativeness.
This script could also be used with similar profiles that fits similar description as Daybreak or shows similar properties threw monitoring of the profile to learn it's characteristics
Click to expand...
Click to collapse
Day Light V2 Script
This Daylight Script uses the dancedance governor for both core 2 and 3 as core 4 is locked offline in the daylight profile. The script delivers a fast rampup of speed boost and quickly sends the cores back offline to help the profile remain true to its severe battery saveing properties.
This script could also be used with other profiles that have the cpu underclocked to help maintain battery conservative fairness.
Click to expand...
Click to collapse
Lateralus Script
This profile uses
- CPU1 = Badass
- CPU2 = Conservative
- CPU3 = Adaptive
The governors for each cores tend to keep things on the conservative side. Its a script with potential to tweak upon and use as a base.
The combination of this script along with any profile should provide a good user experience in terms of battery.
Created by : CamFlawless
Click to expand...
Click to collapse
SRV V2 Script
The script is trying to keep the philosophy of the SRV profile therefore for Core 1 wheatley governor is used and intellidemand is used for Cores 2 and 3. Works best with SRV profile or any profile with ktoonservativeq or wheatley governor for Core 0.
Click to expand...
Click to collapse
3hands Script
- CPU1 = intellidemand
- CPU2 = abyssplugv2
- CPU3 = dancedance
Click to expand...
Click to collapse
●Ragnarok Script ●
- CPU1 = Asswax
- CPU2 = Wheatley
- CPU3 = abyssplugv2
This script is tweak to work along side the Ragnarok profile to help balance out performance and battery conservativety.
Click to expand...
Click to collapse
[[Experimental Profiles]]
This section all old or new test and experimental profiles will be deposited and accessed by anyone to try or test and provide feedback by PM to the respective profile creators.
New Test and Experimental
Old Test and Experimental
This section covers preset scripts geared to help save battery and deliver performance on almost any available profile with or without an available script. These scripts also give users the ability to mix and match profiles with a wider variety of scripts of their own choosing which in-turn delivers the result they desire.
It is very important to read the description of each scripts before trying one as they contain important information to help have a successful experience.
Profiles not mention in the recommended list of each scripts are still ok to be used with any of the scripts providing you read the description before proceeding . Scripts marked with a ES (Energy Saveing) symbol means dureing my test run doing medium/heavy usage i was able to achieve screen usage times of 5 hours and higher. This does not guarantee same results for users but a guideline to follow and try.
General Battery Saveing Scripts Presets
*Conservative Preset 1
The following governors are assigned to each core
Core 1 - Badass
Core 2 - Adaptive
Core 3 - Conservative
This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Some recommend profiles tested on to use with are
-3hands
-Asking Alexandria
-Daybreak
-Lateralus
-Sleeping Dragon Quadcore
- ¤Skyline Profile¤ llllll
- ¤Skyline Profile¤ llllllll
- Ktoonsefied
- Ktoonsefied Mod
- Rebirthing
- Whispers in the Dark
Click to expand...
Click to collapse
*Conservative Preset 2
Each cores consist of the following governors
Core 1 - Asswax
Core 2 - Badass
Core 3 - Abyssplug V2
This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Recommended Profiles tested on to use with are
- Daybreak
- Ktoonsefied
- Ktoonsefied Mod
- ¤ Skyline Profile¤
- Whispers in the Dark ES
- Lateralus
Click to expand...
Click to collapse
*Conservative Preset 3
Core 1 - SmartassH3
Core 2 - Dancedance
Core 3 - Adaptive
::Note::
This script keeps the cores scaleing frequency very low to save on battery. It is not recommended to be use if you play games that require a lot of cpu power.This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Recommended profiles tested on to use with are
- ¤Skyline Profile¤ l
- ¤Skyline Profile¤ ll ES
- ¤ Skyline Profile¤ lll
- ¤Skyline Profile¤ lllll
- ¤Skyline Profile¤ llllll
- Whispers in the Dark
- Bat Pig ES
- Crimson Dragon V3
- Icarus Conservative V2
- Misanthrope
- Balanced Bull Reloaded
- Dead by April V2.2
- Ghost Rider 1.0
- Hydra
- KT Gameing
- Ktoonsified V5
- Lucretia Balanced
- Lucretia Performance
- Notorious
- Project Daylight Experimental
- Project Icarus Conservative
- Project Icarus Kamikaze
- Project Icarus Performance
- Rebirthing
- Smooth Criminal
- Undisputed 3
- Sleeping Dragon Quad - Core
Click to expand...
Click to collapse
Conservative Preset 3 V2
The following Cores are assigned:
Core 1 - Asswax
Core 2 - Dancedance
Core 3 - Adaptive
This updated version of the script brings asswax governor to be uses as core 1 while the other cores uses same governors as V1 but with updated tweaked parameters to help manage core activity more efficiently to extend your battery usage per cycle. This script was tested extensively on the profile Smooth Operator Lite V2 as a substitute to help extend battery performance. It will also work along side any other profiles based on the ktoonservativeq governor.
Click to expand...
Click to collapse
*Conservative Preset 4
Core 1 - Wheatley
Core 2 - Wheatley
Core 3 - Wheatley
This script was tweaked to provide a balance between battery and performance. This script should work on just about any profile but should not be pared along with a profile useing the Wheatley governor.
Some profiles tested on and recommend to be tried with are
- ¤Skyline Profile¤ lllll ES
- ¤Skyline Profile¤ llll
- ¤Skyline Profile¤ lll
- ¤Skyline Profile¤ llllll
- Whispers in the Dark
- Crimson Dragon V3
Click to expand...
Click to collapse
*Conservative Preset 5
Core 1 - Adaptive
Core 2 - Adaptive
Core 3 - Adaptive
This script was tweaked to keep a balance in performance and battery using the Adaptive governor for the 3 cores.
This script should work on just about any profile but should not be pared along with a profile useing the Adaptive governor.
Some recommended profiles it was tested on are
- ¤Skyline Profile¤ llllll
- ¤Skyline Profile¤ lllll ES
- ¤Skyline Profile¤ llll
- Sleeping Dragon Quad-core
- Crimson Dragon V3 ES
Click to expand...
Click to collapse
*Conservative Preset 6
Core 1 - Asswax
Core 2 - Asswax
Core 3 - Asswax
This script is tweak to be used with a balanced or performance based profile such as the "Rebirthing" profile where the CPU polls very quicky and cpu ramps up frequently. It is aimed at keeping the rest of cores activity to a minimum and use lower clock frequencies as often as possible to help reduce battery drain and provide a better experience.This script should work on just about any profile but should not be pared along with a profile useing the Asswax governor.
Profiles tested on are
- Rebirthing ES
- whispers In the Dark
- Crimson Dragon V3
Click to expand...
Click to collapse
General Performance Scripts Presets
*Performance Preset 1
All 3 cores are controlled by the wheatley governor. This script should work on just about any profile but should not be pared along with a profile useing the Wheatley governor.
Recommend profiles tested on to use with are
- Sleeping Dragon Quad-Core
- ¤Skyline Profile¤ ll
- ¤Skyline Profile¤ llllll
- Icarus Performance V2
Click to expand...
Click to collapse
*Performance Preset 2
Core 1 - SmartassH3
Core 2 - Dancedance
Core 3 - Adaptive
This profile was tweaked to maximize overall performance.
This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Recommended profiles tested on to use with are
- ¤Skyline Profile¤ l
- ¤Skyline Profile¤ ll ES
- ¤Skyline Profile¤ llllll
- Icarus Performance V2
Click to expand...
Click to collapse
*Performance Preset 3
Core 1 - Dancedance
Core 2 - intellidemand
Core 3 - Abyssplugv2
This script was tweak to have cores 1&2 scale very quickly delivering performance on demand while the last core 3 works in a slight conservative manner and not too very aggressive although it will still deliver excellent performance considering the nature of governor assigned.This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Some recommended profiles tested on to use with are
- Icarus Performance V2
Click to expand...
Click to collapse
*Performance Preset 4
Core 1 - Asswax
Core 2 - Adaptive
Core 3 - Abyssplugv2
This was tested on unknown profiles with incomplete data entry. It should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Click to expand...
Click to collapse
*Performance Preset 5
Core 1 - Abyssplugv2
Core 2 - Abyssplugv2
Core 3 - Abyssplugv2
This was tested on unknown profiles with incomplete data entry. It should work on just about any profile but should not be pared along with a profile useing the Abyssplugv2 governor.
Click to expand...
Click to collapse
Performance Preset 6
Core 1 - Interactive
Core 2 - Interactive
Core 3 - Interactive
This script is tweaked to deliver a more fluid performance oriented interactive governor experience. Do not use this script if useing interactive as the primary governor at Core0. Will work nicely with any other governors such as ktoonservativeq and the rest found in ktweaker.
Click to expand...
Click to collapse
~~Screen Brightness Adjustments To Save Power~~
=[[Lux Autobrightness]]=
I use the app Lux Autobrightness to set the screen brightness of my device. I find it helps to miminize power consumption used by the screen and taught of shareing my profile.
To use this profile just download it from the provided link below. Be sure to backup your current LUX profile settings. Useing a file manager,navigate to the "Lux" folder on your internal storage and rename your current profile to "lux_profiles.bak". Then move the downloaded profile to your "Lux Folder" and restore it from within the Lux app.
You may want to set your method of backlight adjustment to "ON WAKE" as i have or leave it to your own desire preference as their are 4 to choose from which can be found by running the Lux App settings wizard or by going into settings/brightness and chooseing one of the 4 prefered method of backlight adjustment.
Lux Autobrightness Profile 1 Download
This lux profile is more of a balanced brightness to make the screen not too dark or bright under various light conditions.
Click to expand...
Click to collapse
Lux Autobrightness Profile 2 Download
This profile is adjusted with lower brightness values and takes more of a gradual step to make the screen brighter compare to the above profile 1
Click to expand...
Click to collapse
.
Lux Autobrightness Profile 3 Download
This Profiles uses higher screen brightness percentage as its min and upward lux thresholds to deliver a more alive and vivid screen viewing experience in just about any surrounding with little to maximum ambient lighting source. This profile is not as conservative as profile 1 or 2 but will deliver exceptional experience.
Click to expand...
Click to collapse
TIP
To help lower the screen power consumption along with the lux profile,leave the "Screen Power Saveing" mode feature turned on in your Rom power saveing mode section.
Nice!
Great work, Luigi my friend!!! Not driving an S4 yet, but I like to keep up with emerging trends and new technology...
Besides, I'll support you anytime!
shenry1307 said:
Great work, Luigi my friend!!! Not driving an S4 yet, but I like to keep up with emerging trends and new technology...
Besides, I'll support you anytime!
Click to expand...
Click to collapse
Thanks buddy!! Hopefully when and if you get the S4 this thread will come of use to you
Hey bud. Thanks for doing this thread! It was well needed. Sometimes the updated kernels don't sit right and I'm sure that's for alot of folks. I'm looking for his second set of settings that he posted in his thread. I've searched all over and cant find them. Not the ones in the op of his thread but they were extra settings about all instances of boost or something like that. Thanks in advance.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
jdub251 said:
Hey bud. Thanks for doing this thread! It was well needed. Sometimes the updated kernels don't sit right and I'm sure that's for alot of folks. I'm looking for his second set of settings that he posted in his thread. I've searched all over and cant find them. Not the ones in the op of his thread but they were extra settings about all instances of boost or something like that. Thanks in advance.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Thanks buddy. Really appreciate the feedback. The only thing I recall him saying was that setting "sync_extra_cores" and "touch_boost_cpu_all_cores" to 1 should help with battery and responsiveness but for some users who have issues with lags or reboots should set those to 0. I have them both set to 0 and my phone runs smoothly just fine like that. All the other settings are the recommended settings by Ktoonsez.
LuigiBull23 said:
Thanks buddy. Really appreciate the feedback. The only thing I recall him saying was that setting "sync_extta_cores" and "touch_boost_cpu_all_cores" to 1 should help with battery and responsiveness but for some users who have issues with lags or reboots should set those to 0. I have them both set to 0 and my phone runs smoothly just fine like that. All the other settings are the recommended settings by Ktoonsez.
Click to expand...
Click to collapse
Man awesome. Thanks. Ok you guys are att correct? I'm verizon and what I've found is the 6/23 is the most smooth with our new base me7. Just my findings but there is zero lag. For the first time man I've set my transition scales to 1. I know you know what that means for the s4. And with our VZW me7 roms the stock kernel has been the smoothest but pip and smart stay didn't work. This is odd cause this is the very Ktoonsez kernel that broke these features in mdk. So I flashed it on me7 and all things in the world are marvelous. Lol
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
jdub251 said:
Man awesome. Thanks. Ok you guys are att correct? I'm verizon and what I've found is the 6/23 is the most smooth with our new base me7. Just my findings but there is zero lag. For the first time man I've set my transition scales to 1. I know you know what that means for the s4. And with our VZW me7 roms the stock kernel has been the smoothest but pip and smart stay didn't work. This is odd cause this is the very Ktoonsez kernel that broke these features in mdk. So I flashed it on me7 and all things in the world are marvelous. Lol
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Actually Ktoonsez is ATT while I'm on T-Mobile but as you can see, like the S3, I've been collecting every build from each variant of the S4 just because Ktoonsez is awesome in what he does and I'd do anything to help him out!
Glad to hear all is running smoothly
boterkaaseneieren said:
I really don't get this thread, you mean to say all these builds are the original kernels of KT? And you post it in dev section. You can only make a thread in dev section of its your build. Going to report this and see wat a moderator think of this. Why make a mirror thread?
Click to expand...
Click to collapse
You obviously don't know who luigibull23 is. You'll thank him later.
Sent from my SGH-M919 using xda premium
boterkaaseneieren said:
In general where this belongs.
Click to expand...
Click to collapse
LuigiBull23 said:
Yup. Me and a mod spoke about it and all is well now
Click to expand...
Click to collapse
That shut you up didn't it boterkaaseneieren! Stop hating on people! and chill out! The guy gave plenty of credit and as he mention he got permission so why you on his cause like a nagging women? even on his thread!!! stop trying to seek brownie points please!
Sent from my GT-I9505 using Tapatalk 4 Beta
So...just flashed Liquid Smooth, my first aosp rom on the S4. For some reason the on demand governor which I usually use stays at max clock speed and doesn't go down. So I'm going to try out ktoonsez now. What settings do you recommend for that crazy 7 hour battery life you were able to get on the S3 @LuigiBull23? Lol
Sent from my SGH-M919 using xda premium
marcoxx626 said:
So...just flashed Liquid Smooth, my first aosp rom on the S4. For some reason the on demand governor which I usually use stays at max clock speed and doesn't go down. So I'm going to try out ktoonsez now. What settings do you recommend for that crazy 7 hour battery life you were able to get on the S3 @LuigiBull23? Lol
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I'll pm you my current setup. Nothing fancy.. Just warming up lol
LuigiBull23 said:
I'll pm you my current setup. Nothing fancy.. Just warming up lol
Click to expand...
Click to collapse
What Rom are you currently running Luigi?
ahoslc said:
What Rom are you currently running Luigi?
Click to expand...
Click to collapse
Slim Bean
{
"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"
}
Kernel for Google Play Edition and Sense-based ROMs
FAST • STABLE • FULL-FEATURED
ElementalX brings the best performance and battery life on the HTC One. Stable and full-featured, you get complete control over your phone. The only kernel that offers individual control of all CPU cores without third party apps, automatic undervolting options, full compatibility with paid apps, thermal options, fully working sweep2wake, doubletap2wake and pocket detection to prevent accidental wakes. Other features include button light notification, 60Hz refresh rate for HDMI, HTC logo as menu button, sleep/wake with long press of the HTC logo, support for many gamepads and more.
Click to expand...
Click to collapse
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems you may have!
FEATURES:
easy installation and configuration with Aroma installer
optimized for extended battery life
overclocking/underclocking options
select independent frequencies for each core
choose auto minimum voltage (725mV to 850mV)
complete user voltage control
mpdecision options (battery saving, stock, performance)
optional GPU overclocking
GPU governors: ondemand, simple
CPU governors: ondemand, intellidemand
i/o schedulers: FIOPS, SIO, CFQ, NOOP, deadline
kernel based thermal control
thermal options (extra cool, run cool, default, and run hot)
sweep2wake
doubletap2wake
logo2wake
pocket detection
logo2menu
button light notification
optional max screen off frequency
optional graphics boost
/system writable
init.d support
force fastcharge
NTFS r/w support
exFAT support
CIFS support
OTG support
optional disable HTC color enhancement
color control (faux123)
remove/restore 3-dot menubar
support more game controllers (including PS3)
maintains compatibility with all paid apps
increased refresh rate for HDMI output via MHL adapter
optimized -O3 linaro 4.8.1
Please hit the Thanks button if you download this
If you really like it, please consider a donation to encourage continued development
Thanks to those who have donated!
Click to expand...
Click to collapse
DOWNLOAD
Sense 5.5 Android 4.4 and Google Play Edition Android 4.4.2
ElementalX-m7-Verizon-13.1
Note: I do not have a Verizon HTC one. Please look through the thread to find what ROMs this works with and any workarounds that are needed.
INSTALLATION
1. Install zip from recovery
2. Follow the instructions, if you don't know what to do, use the preselected options
3. Reboot
For installation, it seems a lot of people have finicky phones when it comes to flashing stuff with aroma.
If the installer gets stuck at 0% then you need to reboot to bootloader and do fastboot erase cache
If the installer reboots at 10%, you need to do a nandroid backup of /system partition and restore it. I think a dirty flash would also work.
After you install it, if you get a black screen or stuck at the HTC logo, no need to worry. Just hold down the power button untill the capacitive buttons start flashing and the phone restarts. The kernel installed correctly.
As always, with overclocking, not all phones can handle all frequencies. If it doesn't boot, or randomly reboots, or freezes, your first course of action should be to reinstall with a lower frequency.
Previous versions:
ElementalX-m7-Verizon-11.4.1
Special thanks:
@tbalden for l2m and bln and cam fix on sense 4.3
@amarullz for installer
@backfromthestorm for fstrim
@crpalmer for kernel based thermal control
@mkasick Fix for empty app-mounted directories
@jonas2295 for elementalx logo
@faux123 for simple GPU governor and color control
NOTES:
ElementalX Configuration File
Your choices in the Aroma installer are used to build a configuration file. The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
The settings can be changed by editing /etc/elementalx.conf and rebooting. Advanced users can apply settings on the fly by running /etc/init.d/99elementalx as root.
There is no need to edit /etc/init.d/99elementalx. All settings are configured in /etc/elementalx.conf.
If settings are not sticking, make sure the file permissions for /etc/init.d/99elementalx are set to execute. Every time the settings are applied, a log file is created at /data/local/tmp/elementalx-kernel.log. Problems can be diagnosed by looking at the log file.
Please check to see if any /etc/init.d scripts or apps (such as Kernel Tuner or Trickstermod) are interfering with your settings.
ElementalX Log File
Every boot, a log file is created at /data/local/tmp/elementalx.log. This file shows the date and time and all settings that have been applied. Use this to verify and troubleshoot configuration options. Also shows your PVS bin.
Kernel Tuner/TricksterMod/Venom Tweaks, etc
You don't need these apps because the ElementalX installer sets everything up automatically, but if you want to check or change settings, you can use these apps. Just be aware that some of them (e.g. Kernel Tuner) are set by default to apply settings on boot, which can interfere with the settings you chose in the ElementalX installer.
Note: on the most recent versions, fauxclock interferes with GPU overclocking unless you disable pnpmgr (not recommended)
Overclocking
Overclocking (or underclocking) is optional. The installer lets you choose a maximum between 1134MHz (underclocked) and 2160MHz (overclocked). You can set the maximum frequency individually for each CPU core in the installer. Whatever frequencies you chose in the installer will be set at boot for each CPU. Not all devices can handle overclocking. The stock maximum CPU frequency is 1.7GHz. I recommend a mild overclock, like 1836MHz. Clocking higher creates heat and wastes battery for very little performance gain.
CPU voltages
The installer allows you to choose from several undervolting options. These automatically undervolt the lowest frequency (384MHz) where the CPU spends most of its time. The voltages for other frequencies are assigned based on the PVS bin of your phone. CPU voltages are fully customisable with apps such Kernel Tuner or Trickster Mod, but I recommend leaving these other voltages as-is unless you are prepared to do a lot of testing. Be careful, lowering voltages can cause instability. Generally, having reboots while the phone is asleep is a sign that your minimum voltage is too low. The minimum voltage allowed is 700mV.
Be careful with undervolting. If you have bluetooth or sound issues, try increasing the minimum voltage.
Minimum CPU frequency
The minimum CPU frequency in this kernel is 384MHz. This chip was not designed to operate below 384MHz and I am respecting Qualcomm's design decision to have the CPU idle on pll8 at 384MHz. There is a way to achieve lower frequencies using the high frequency pll, however, this is likely to cause instability and inefficient operation (battery drain, ui stuttering)
GPU frequencies
You can choose stock GPU frequency of 400MHz or overclock. If overclocked, you can choose from a range of frequencies up to 585MHz. Overclock frequencies can be changed on the fly, but you can't use the stock frequency. Conversely, if you choose stock GPU, the overclocking frequencies will not be available. To change between stock and overclocking mode, you need to reinstall. The same voltages are used no matter if the GPU is overclocked or not.
GPU Governor
The default GPU govenror is ondemand. It works well and is recommended for best balance between performance and batter life. The simple governor is also available, but ramps up the GPU frequency much quicker than ondemand, so may impact battery life. The governor can be set in /etc/elementalx.conf
Graphcis Boost
The latest versions include graphics boost, which lowers the up_threshold for ondemand governor when GPU is at max frequency. This helps mostly with graphics intensive games that use gyro controls, such as racing games. It can be enabled or disabled in /etc/elementalx.conf or through sysfs.
/sys/devices/system/cpu/cpufreq/ondemand/gboost
0=gboost disabled
1=gboost enabled
Thermal Control
I've added kernel based thermal control and throttling. HTC's thermald is very aggressive and throttles the CPU frequency pretty much anytime you use all four processors. This kernel based implementation allow better performance while still protecting your phone from overheating. There are three levels of thermal control, which can be chosen in the installer or changed in /etc/elementalx.conf. The default option is recommended. With the run cool option, your CPU will run about 5C cooler than default while under heavy load. With the run hot option, the CPU will run about 5C warmer than default under heavy load.
MPDecision settings
There are three mpdecision settings available: battery saving, stock and performance. I think they are self explanatory. These can be changed in /etc/elementalx.conf
Max screen off frequency
This is optional and must be selected in the installer. I recommend enabling it. This limits the max cpu frequency while the screen is off. The default max screen off frequency is 702MHz, which is a good balance between limiting the voltage/frequency and the time required to complete tasks while the screen is off. You can adjust this with applications such as Venom Tweaks.
CPU Governors
The default governor is ondemand (recommended). Intellidemand is also available.
I/O Schedulers
The default i/o scheduler is FIOPS. Other available schedulers are CFQ, FIOPS, SIO, NOOP and deadline.
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.
Sweep2Wake
Sweep2wake (S2W) allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep). The options are: sweep2wake/sweep2sleep, sweep2sleep only, and disabled. If you use apps such as Kernel Tuner, the sweep2sleep only option can be selected by choosing "On with backlight". You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/sweep2wake
0=disabled
1=enable sweep2wake + sweep2sleep
2=enable sweep2sleep only
Sweep2wake button timeout
In earlier versions, sweeping to sleep brought you back to the homescreen. Starting in version 3.3, if you swipe fast enough, it will not register a home button press in the sweep, and your last app will be there when you unlock the phone again. Depending on how quick your fingers are, double tapping home could put the phone to sleep instead of opening recent apps. I've made the default button_timeout such that it is almost impossible for this to happen in normal use (button_timeout = 6). If you find that it happens too often, you can set button_timeout to a lower number, or disable it completely by setting it to 0.
/sys/android_touch/button_timeout
Accepted values are 0 to 15. 0 disables button timeout
• Higher values make it more likely that your last app will be open after you sweep to sleep, but there is a higher risk of accidentally putting the device to sleep when double tapping home.
• Lower values make it less likely that your last app will be open after you sweep to sleep, but reduces the chance of a double tap of home being mistaken for a sweep2sleep.
• Setting button_timeout to 0 disables this feature completely
The setting can be changed after installation in /etc/elementalx.conf
DoubleTap2Wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping in the bottom inch or so of the screen, above the capacitive buttons. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/doubletap2wake
0=disabled
1=enable doubletap2wake
Logo2Wake
Logo2Wake (L2W) allows you to sleep or wake the device by long pressing the HTC logo. You have to press just slightly above the HTC logo. The screen will automatically turn on or off with a long press. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/logo2wake
0=disabled
1=enable logo2wake
Pocket Detection
Pocket detection protects against accidental wakes while S2W, DT2W or L2W are enabled and the phone is in your pocket. Pocket detection uses the proximity sensor. A few people have a problem with their proximity sensor that makes DT2W not work, so I've made an option to disable pocket detection. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/pocket_detect
0=disabled
1=enable pocket detection
Logo2Menu
Enabling Logot2Menu (L2M) allows you to use the HTC logo as a menu button. You must press just slightly above the HTC logo. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/logo2menu
0=disabled
1=enable logo2menu
Button Light Notification
With Button Light Notification (BLN), the capacitive buttons will blink on and off when you have a new notification. As soon as the screen comes on, BLN is canceled and the lights will no longer blink until you have another notification. Please note that if you have your screen set to turn on when a message arrives, you will not see the buttons blinking because once the screen comes on, the button light notification is canceled. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/class/leds/button-backlight/blink_buttons
0 = disabled
1 = BLN enabled
NTFS and exFAT support
This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS and exFAT filesystems. You will need Stickmount or a similar app, HTC Sense does not automatically detect these filesystems.
Paid Apps
All the cryptographic modules load properly, so you shouldn't have an issues with paid apps.
Other stuff
This kernel supports many game pads and controllers, including PS3 controllers and some X-Box controllers. It has full OTG support. A refresh rate of 60Hz for HDMI output allows you to play games on the big screen without choppiness. CIFS support is built into the kernel. Faux sound control is also supported.
Source:
Github
................
CHANGELOG
Changes
ElementalX Sprint & Verizon Downloads -kernel source
This is ElementalX kernel from http://forum.xda-developers.com/show....php?t=2249774 just compiled for Sprint and Verizon.
Downloads
ElementalX 17.0 http://forum.xda-developers.com/show...&postcount=796
ElementalX 17.2 http://forum.xda-developers.com/show...&postcount=871
ElementalX 17.2-3 http://forum.xda-developers.com/show...&postcount=875
ElementalX 18.0 http://forum.xda-developers.com/show...&postcount=901
ElementalX 19.3 http://forum.xda-developers.com/show...&postcount=993
kernel source : https://github.com/smokin901
Credits
@flar2 - Kernel Sources
@poondog : help making it work on sprint and Verizon
and others i may have missed.
I'll test now, will report back any issue i find!!
Flashed this choosing all default options in aroma. After the boot I ended up with a black screen with capacitive buttons lit. Would you like me to try to get a logcat?
Sent from my HTC6500LVW using Tapatalk
Edit: just reread the OP, after a second and third reboot the phone still did not boot fully. I'm using ViperOne if that matters.
I will need /proc/last_kmsg please
And also the installation log.
Will look at them tomorrow
flar2 said:
I will need /proc/last_kmsg please
And also the installation log.
Will look at them tomorrow
Click to expand...
Click to collapse
here the last_kmsg and installation logs. https://dl.dropboxusercontent.com/u/60449348/LOGS.zip
flar2 said:
I will need /proc/last_kmsg please
And also the installation log.
Will look at them tomorrow
Click to expand...
Click to collapse
I reflashed, and system booted fully on first try. Here are the logs anyway: https://www.dropbox.com/s/9fc9pm8dqq1wldf/logs.zip
Only difference between first and second attempts was I did not wipe dalvik/cache after the second attempt.
Sent from my HTC6500LVW using Tapatalk
Just flashed. I messed around with the cpu settings and got a bootloop. I'll flash again with defaults and get back to you. Thank you for your time and effort.
Sent from my HTC6500LVW using Tapatalk
unctucker said:
Just flashed. I messed around with the cpu settings and got a bootloop. I'll flash again with defaults and get back to you. Thank you for your time and effort.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
unctucker said:
unctucker said:
Flashed Elemental....bootloop after. Went back to my "STABLE" Viper 4.1 with the 4.2 OTA.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Flashed again with all defaults and I'm good.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Just thought this should be shared on this thread.
Sent from my HTC6500LVW using Tapatalk
ran all day with stock settings good work
Virus said:
ran all day with stock settings good work
Click to expand...
Click to collapse
Ran all day OC'd and UV'd with intellidemand. No problems here since the first install failed. Great work @flar2 !
Sent from my HTC6500LVW using Tapatalk
So it does work?
flar2 said:
So it does work?
Click to expand...
Click to collapse
Yes. Works great!
Sent from my HTC6500LVW using Tapatalk
flar2 said:
So it does work?
Click to expand...
Click to collapse
Works real well
Gonna run it all day tomorrow and report my findings.
Great! Thanks (I ran out of thanks for the day)
Let me know if everything is working as it's supposed to. I always get a bit nervous when I can't test things out myself.
flar2 said:
Great! Thanks (I ran out of thanks for the day)
Let me know if everything is working as it's supposed to. I always get a bit nervous when I can't test things out myself.
Click to expand...
Click to collapse
What kinds of things should be tested/how should they be tested?
Sent from my HTC6500LVW using Tapatalk
bschram said:
What kinds of things should be tested/how should they be tested?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Mostly that the settings chosen during install are actually applied.
It should run nice and smooth with default settings. If performance or battery or worse than stock, something is not right.
flar2 said:
Mostly that the settings chosen during install are actually applied.
It should run nice and smooth with default settings. If performance or battery or worse than stock, something is not right.
Click to expand...
Click to collapse
All the settings I applied in aroma stuck (I confirmed them in venom tweaks), and my battery life was great today. Everything has been running smooth.
Sent from my HTC6500LVW using Tapatalk
My logo2menu doesn't seem to be working.