Related
Does overclocking have effect on my battery life? not successful in searching a thread on this. Thanks.
HI
I mentioned a few things about it in this thread, if you scroll to my bit, but this is no hard and fast tes, just my observations.
http://forum.xda-developers.com/viewtopic.php?t=59473
use xcpuscalar and set it to scale up and down based on proc. percentage, i find i can even save battery like this, whilst having the performace of a permanent OC when i need i.
@fa147 will do that.
i actually noticed that when i removed xcpuscalar and returned to normal i was able to save almost 2X my bat life.
@midget_1990 I have not tried auto scale but wouldn't this make the system slower instead because it would only speed up when there is already a lot of load and might cause hangups?
I used to hackmaster to a) save battery when i'm not using my device by underclocking and b) to scale up and o/c the performance when I need it (like with media playback etc)
[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.
Not sure if this is the right thread to talk about it, but recently I flashed the 5.4 version of this kernel http://forum.xda-developers.com/showthread.php?t=2775998 and so far so good, it fixed the 4.4.2 S Pen problem. However, I've noticed that, when I use multitask mode (2 apps open at the same time stacked on top of each other), there is some light stuttering(?). Not laggy, but when I scroll it kinda stutters a bit. Strangely enough, this only happens during multitask mode, not if I have a lot of apps open in the background. This isn't the real problem though, the real problem is that the kernel seems to cause the S Note app to lag so much that it's almost unusable. Another problem i've found was that SOMETIMES when listening to music when the screen is off, the music lags so much that it's inaudible. Not often, though, and I dorn know what specifically causes it, other than the low GPU speed. The kernel specifically states this:
"GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel"
I'm taking a guess here but I think that the low, non editable GPU settings are causing the slowdowns.
Is there any way to somehow increase the GPU, even though it says that it's uneditable? Has anyone used this kernel before and found out how to fix it? Would downgrading to a lower version of the kernel fix the slowdowns? This is the only kernel I found that fixed the slowdown for my device, I can't really install a different one, but I can downgrade this specific kernel, which I think could fix it but I'm not sure. Are there any other fixes?
Hey guys, this will be my first major post on XDA. I've been scouring through the forums looking for ways to improve on our restricted stock kernel and ran across a few very useful threads. In the Nexus 5X and 6P forums they've created kernel profile scripts that tune the Interactive governor present in all Android kernels. I took the courtesy of going through the threads and compiling a list of all the noteworthy profiles I could find. Huge shoutout goes out to @soniCron, @phantom146, and @Alcolawl for creating the basis behind the governor tuning and scripts to implement them. I converted all the profiles to use the LITTLE cluster settings for our devices since they are a bit lower spec, and taking the EXKM designated profiles and converting them into bash scripts that we can use in a terminal emulator. I gathered as much info as I could on each profile and it's original author. All the profiles scripting layout was customized by myself to look more uniform and stylish.
The original thread can be found here: https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
And the revamped updated thread is here: https://forum.xda-developers.com/nexus-6p/general/guide-advanced-interactive-governor-t3290605
You need to remove the ".txt" extension at the end of the file when you download it, and then you can run it from a terminal emulator directly using source "." or "bash". You can also easily execute the scripts from a file explorer that supports source execution (such as MiXplorer or FX File explorer), then you can simply select the ".sh" file and select "execute" in the explorer. Its recommended to use Kernel Adiutor to tune the variables of the governor if you find you need to.
Feel free to try them out and leave feedback! I can't give any technical help with the profiles as they are not mine. My best advice would be to try them all for at least a full charge cycle each, and then refer to the threads above to tune the one that best suits you until it's perfect. Good luck!
_______________________________________________
******Disclaimer: I am not responsible for you nuking your phones or any other damage caused by using these scripts. Just a friendly reminder.******
AmanuensisOne - @RogerF81: It's mainly based on the StableV2 settings and on EclipseR2, but with a bit smoother experience than with the EclipseR2 profile. It also goes further and tweaks more kernel settings in proc/sys/kernel and sys/module, as well as readahead cache, I/O schedulers, net TCP settings, swappiness, Low Memory Killer parameters, and more Virtual Memory tweaks. This is more of an all-in-one, flash and forget script for users who want a simple way to tweak most major areas of the kernel settings.
Blazer_V4 - @sireangelus: Based on Ghostpepper and Amanuensis, with better battery life for everyday tasks like scrolling and texting. Does not utilize Input Boost and also tweaks some proc/sys/kernel settings as well as Low Memory Killer parameters.
DarkSpiceR7.5 - @xSilas43: Based upon the Ghostpepper settings with some added tweaks to further optimize the battery life and performance of the governer. With revisions to mainly the timer rate and min sample time with the addition of input boost @672mhz for 40ms, this irons out some of the UX issues people may have while also encourages the CPU to use lower clock rates.
DeusEx Revolution - @xperator: Based on AmaneunsisOne and BlackPepper, a bit different than the original DeusEx. More performance oriented. Great for gaming. Almost no lags.
DragonFly @xperator : A profile based on DarkSpiceR7.5 and EclipseR3. It's similar to Butterfly profile meaning its aimed for performance and responsiveness but its snappier and faster than Butterfly. It jumps to mid frequencies all the time even for small tasks. You shouldn't expect great battery life! Even though It should be more battery friendly than Butterfly.
Excalibur - @xperator: Based on DragonFly and GhostPepper. It's almost fast as DragonFly and it has great battery life.
GhostPepper - @soniCron: A medley of Silverfish, MadDog and the Stable settings with a few additional but crucial tweaks aimed at giving extremely smooth performance in all situations, even while multitasking, without sacrificing the battery life as experienced with MadDog.
GlassCannon - @phantom146: Provides the smoothest interface, great performance while bestowing the lowest frequencies available. Ramping up quickly to maximize "inputs" from I/O overheads then immediately ramping down once tasks are done. The perfect balance between lowering down your frequency, and finishing up tasks quickly.
Hawktail_v1.2 - @Alcolawl: An Interactive Governor profile focused on fluidity and UX. Butter smooth in all situations. Minimal heat during web browsing and heavy texting sessions and gamers are praising this profile as well. Great SOT and battery life. The complete package and new candidate for the 'Stable v3.0' Settings.
MadDog - @Alcolawl: Using a new approach, this profile distributes workloads evenly. Drops CPU frequencies as quickly as possible in all circumstances. Performs quite well albeit inconsistently at times.
Saber V2 - @xperator: Designed to work without InputBoost. Mostly no lags/heat issues. Suitable for heavy texting users. Probably not good for gaming. Based on DeusEx family.
First "share my work" post and ya jabbed it in there 4 times, lol. Nice to take some initiative though bro. I know some folks will love it.
madbat99 said:
Most post and ya jabbed it in there 4 times, lol. Nice to take some initiative though bro. I know some folks will love it.
Click to expand...
Click to collapse
I figured somebody else would want to try these out like I did, so I did what XDA was made for and spread my knowledge and I had some issues with posting the OP but I deleted the other 3 so all should be good now. I appreciate your words of encouragement man
Sent from my perry using XDA Labs
Hey, quick update. 3 of the profiles had a few minor typos that I ironed out real quick, and I'm not sure how to edit the attachments in the OP lol. So here's those profiles for anyone who wants them! They are the Blazer, Hawktail and MadDog profiles
Sent from my perry using XDA Labs
@RebelLion_ You have to change attachments on the xda site with a browser. Go to the control panel. Options are there.
Options, then scrool down to attachments.
Credits to the developers of the modified GCam project. Please donate to them if possible to keep the development going.
After using it daily on my Pixel 2 XL it is now confirmed working on the Pixel 6.
There are alot of custom options to take that perfect shot available for this modified version, as time passes there will be more releases on the main page on the same site.
Enjoy!
Older version
https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/f/dl23/
Latest version
MWP: Gcam_8.4.300_beta5_MWP
Download Gcam_8.4.300_beta5_MWP by MWP.
www.celsoazevedo.com
Detailed info I found on Google for the app:
What is the lib patcher?
Libpatcher - is a custom setting where you can set all the settings to your liking
Radius Temporal changes the graininess of the image by affecting noise, the higher the image is more blurry and less noise, the lower the more noisy, but more detail
Tone Curve is where you can adjust dark points, white points, shadows, highlights. It is recommended to enable and leave the default values or tweak them (advanced users)
Sharpness allows you to control the sharpness of the image. Zoom in for low-light shots, and zoom out for selfies.
Luminance Noise Reduction is what controls the “graininess” in images caused by high ISO. Decrease it to get more detail at the expense of high noise, or increase it if the noise is unacceptable to you
Color Noise Reduction: Controls color spots. There is usually no need to adjust it as this will not improve the quality, but you can increase it slightly if you see colored spots in the dark. Too much chroma noise can cause a decrease in saturation. Also known as color noise. Be careful with this setting it can mess with the fine details of an image.
Contrast settings allow you to control the contrast of the image. Increase it if you want darker shadows, and decrease it to make it brighter is the general idea. This is again a personal preference
Saturation is what allows you to control the saturation of the image. Increase it if you want more saturated colors in your photos. Obviously decrease if your HDR is getting too saturated. This is again a personal preference
Now there are some advanced settings. These affect the morphological processing. Naturally thats a very basic overview. I took the course while finishing up my engineering degree. It was difficult stuff past the basic level. I wont get into what these settings do beyond a decent generalization.
Warning to all these settings can absolutely have a drastic negative effect on your images. A lot of testing would be necessary by the end user
Luminance noise reduction levels
Level 1 (Detail) changes the photo very slightly, slightly smoothing out small elements in the image.
Level 2 (Rough Surfaces) seriously alters the image by smoothing grain
Level 3 (Edges) doesn’t change much. Smooths edges slightly
Level 4 (Smooth Surfaces) radically alters the image by making it posterized by smoothing out large areas of the same color. Avoid magnification over 1.0
Color noise reduction levels
Level 1 (Detail) fine textures, but the same applies to rough details
Level 2 (Rough surfaces) fine textures, but the same applies to rough details
Level 3 (Edges) Edges are mainly defined by the contrast between one object and another
Level 4 (Smooth Surfaces) Smooth surfaces are generally uniform areas of the image. Like wallpaper with few small details
Tips:
If you notice a certain color of spots on your low light photos. Check its frequency spectrum. Look where its at in the photo and go to the specific wavelet reduction setting and tweak it. See if you can remove it. More often than not these settings are used to improve astrophotography, low light and high detail images.
My sensor has more higher frequency color noise than others. Ive seen some XDA users where they had to turn down denoise. It really all depends on a lot of stuff. Its fun to tweak and squeeze out what you can.
YMMV
I can do most, if not all, of this stuff in GIMP/Photoshop, more easily, with finer control (to include undo), and on a much larger screen
All most of us really want (I can't be the only one) in a "great" camera app is total control of:
1. Shutter speed
2. "ISO"
3. Aperture
4. Lens selection
just like my Galaxy S8's "pro mode"
Everything else can be "fixed" in post.
-But then I'm just an old guy with camera and a darkroom
biTToe said:
I can do most, if not all, of this stuff in GIMP/Photoshop, more easily, with finer control (to include undo), and on a much larger screen
All most of us really want (I can't be the only one) in a "great" camera app is total control of:
1. Shutter speed
2. "ISO"
3. Aperture
4. Lens selection
just like my Galaxy S8's "pro mode"
Everything else can be "fixed" in post.
-But then I'm just an old guy with camera and a darkroom
Click to expand...
Click to collapse
Yeah I totally get that, photo editing software is better on a computer and is more fine tuned.
This is an easy way to get more customized results. I've seen way too many complaints about the built in app being too restricted and plain.
This adds additional functionality and is my go to application when taking photos for years now.
legend221 said:
Credits to the developers of the modified GCam project. Please donate to them if possible to keep the development going.
After using it daily on my Pixel 2 XL it is now confirmed working on the Pixel 6.
There are alot of custom options to take that perfect shot available for this modified version, as time passes there will be more releases on the main page on the same site.
Enjoy!
MWP: Gcam_8.4.300.v1_beta3
Download Gcam_8.4.300.v1_beta3 by MWP.
www.celsoazevedo.com
Detailed info I found on Google for the app and recommended settings:
What is the lib patcher?
Libpatcher - is a custom setting where you can set all the settings to your liking
Radius Temporal changes the graininess of the image by affecting noise, the higher the image is more blurry and less noise, the lower the more noisy, but more detail
Tone Curve is where you can adjust dark points, white points, shadows, highlights. It is recommended to enable and leave the default values or tweak them (advanced users)
Sharpness allows you to control the sharpness of the image. Zoom in for low-light shots, and zoom out for selfies.
Luminance Noise Reduction is what controls the “graininess” in images caused by high ISO. Decrease it to get more detail at the expense of high noise, or increase it if the noise is unacceptable to you
Color Noise Reduction: Controls color spots. There is usually no need to adjust it as this will not improve the quality, but you can increase it slightly if you see colored spots in the dark. Too much chroma noise can cause a decrease in saturation. Also known as color noise. Be careful with this setting it can mess with the fine details of an image.
Contrast settings allow you to control the contrast of the image. Increase it if you want darker shadows, and decrease it to make it brighter is the general idea. This is again a personal preference
Saturation is what allows you to control the saturation of the image. Increase it if you want more saturated colors in your photos. Obviously decrease if your HDR is getting too saturated. This is again a personal preference
Now there are some advanced settings. These affect the morphological processing. Naturally thats a very basic overview. I took the course while finishing up my engineering degree. It was difficult stuff past the basic level. I wont get into what these settings do beyond a decent generalization.
Warning to all these settings can absolutely have a drastic negative effect on your images. A lot of testing would be necessary by the end user
Luminance noise reduction levels
Level 1 (Detail) changes the photo very slightly, slightly smoothing out small elements in the image.
Level 2 (Rough Surfaces) seriously alters the image by smoothing grain
Level 3 (Edges) doesn’t change much. Smooths edges slightly
Level 4 (Smooth Surfaces) radically alters the image by making it posterized by smoothing out large areas of the same color. Avoid magnification over 1.0
Color noise reduction levels
Level 1 (Detail) fine textures, but the same applies to rough details
Level 2 (Rough surfaces) fine textures, but the same applies to rough details
Level 3 (Edges) Edges are mainly defined by the contrast between one object and another
Level 4 (Smooth Surfaces) Smooth surfaces are generally uniform areas of the image. Like wallpaper with few small details
My Settings
Now I have done A LOT of testing on my phone, with my case (affects light angles coming in slightly) and just about everything I can to nail these in for my device and my tastes so please dont just copy and paste. This is more of an informative post.
Libpatcher Switches:
Force System Noise Model (I tweaked the tweaked one but I cant post that code (license issues)) ON
Disable Dehave ON
Sharpness: 1.13
Saturation: 1.21
Global Chroma Denoise: Set to wavelet
Global Luma Denoise: Set to wavelet
Wavelet Luma Denoise Settings:
Level 1 - 0.875
Level 2 - 0.875
Level 3 - 1.0
Level 4 - 1.125
Wavelet Chroma Low Frequency Denoise Settings: (556 THz - 792 THz) 89
Level 1 - 1.0
Level 2 -1.0
Level 3 - 1.1
Level 4 - 1.2
Wavelet Chroma High Frequency Denoise Settings: (403 THz - 555 THz) 89
Level 1 - 0.875
Level 2 - 1.0
Level 3 - 1.0
Level 4 - 1.3
Those work far better for me and ive noticed my pictures have less sports
Tips:
If you notice a certain color of spots on your low light photos. Check its frequency spectrum. Look where its at in the photo and go to the specific wavelet reduction setting and tweak it. See if you can remove it. More often than not these settings are used to improve astrophotography, low light and high detail images.
My sensor has more higher frequency color noise than others. Ive seen some XDA users where they had to turn down denoise. It really all depends on a lot of stuff. Its fun to tweak and squeeze out what you can.
YMMV
Will post occasional pics displaying some of the modded apps performance on occasion
Why didnt your wavelet settings work for me
Factors that affect settings
Your phone
When it was made
The chip itself
The silicon in your sensor
Ambient weather conditions
The image processing firmware on the Pixel Visual Core
Other properties of silicon unique and intrinsic to your device
FAQ
Why are your colors listed as frequencies?
Light is an electromagnetic phenomenon and as an RF engineer its easier for me to refer to spectra as a frequency but one could easily refer to it in wavelengths or color (but color wont be accurate as thats up to perception)
What are wavelets?
A wavelet is how we define a center frequency and some deviation. We use wavelets because a color is not just one frequency its a range see here : Spectral color - Wikipedia 10 Its also an entire subset of mathematics used by anyone who works with the spectrum (i.e RF engineers, optical engineers (fiber stuff), biomedical engineers). They are helpful because we can take the average of a color spectrum (say blues) and convolve it with the signal to find the center frequency of blue or the blues in a subset (image). It basically the magic behind the IM processing math.
Just tried a sample of my night time “light bleed” mode and its okay. It still need more tweaking but heres an example of what tweaking your denoise settings can do. The image is far better than a stand night photograph (even with some longer exposure)
Keep in mind you wont remove all the noise. In fact it sometimes takes noise to remove or smooth noise (dithering). Dithering is a process where we add a bit of noise to a data set in an attempt to constructively perturb the signals we want to convolve, isolate and amplify over the average.
Click to expand...
Click to collapse
See the problem with copying stuff off Google without knowing what your doing is that you have added all this and the cam doesn't have the majority of it so you are misleading users dude. You sure you have mentioned the correct cam version?
enerGy said:
See the problem with copying stuff off Google without knowing what your doing is that you have added all this and the cam doesn't have the majority of it so you are misleading users dude. You sure you have mentioned the correct cam version?
Click to expand...
Click to collapse
You can try it if you'd like or keep using the built in one. I've been using this version on my Pixel 6.
There are also other builds on the same site.
Honestly I don't even use the stock one that came with the phone. Not too many options or settings to adjust vs this Mod.
These guys have been doing this for years I've personally used it on my Pixel 2 XL since I can remember.
I'm very confident they have the knowledge and experience to release this Mod to the public.
legend221 said:
You can try it if you'd like or keep using the built in one. I've been using this version on my Pixel 6.
There are also other builds on the same site.
Honestly I don't even use the stock one that came with the phone. Not too many options or settings to adjust vs this Mod.
These guys have been doing this for years I've personally used it on my Pixel 2 XL since I can remember.
I'm very confident they have the knowledge and experience to release this Mod to the public.
Click to expand...
Click to collapse
What do you mean? I didn't say anything about the guy who builds it or him not having knowledge lol, I know him. You just replied with something totally different to what was questioned dude, doesn't make sense. Many of the options and values you gave are not in this cam as you can see below thus why I'm asking have you posted the correct version. Also I'm no noob as you might be suggesting lol I've plenty of experience with GCam on many many devices creating configs for personal use and for public.
enerGy said:
What do you mean? I didn't say anything about the guy who builds it or him not having knowledge lol, I know him. You just replied with something totally different to what was questioned dude, doesn't make sense. Many of the options and values you gave are not in this cam as you can see below thus why I'm asking have you posted the correct version. Also I'm no noob as you might be suggesting lol I've plenty of experience with GCam on many many devices creating configs for personal use and for public.
Click to expand...
Click to collapse
We are both Senior Members I know. I should edit the posting as the settings were taken from another source online.
Let the users try it and keep using it if they like it. Let him know he is an amazing guy and I hope he gets alot of well deserved donations.
Thank you for your work on the configs as well.
Hi, I strongly recomend last NOT BETA version of this great app, so Gcam_8.3.252_V2.0c_MWP (https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/) Gcam_8.3.252_V2.0c_MWP
novaq72 said:
Hi, I strongly recomend last NOT BETA version of this great app, so Gcam_8.3.252_V2.0c_MWP (https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/) Gcam_8.3.252_V2.0c_MWP
Click to expand...
Click to collapse
Thank you @novaq72
I tried out the last stable version and my P6 was not saving the pictures. I have been running without problems on 8.4.300 v1 beta3.
If anyone has any issue from the OP definitely try out the one above.
It's a pity, I don't have a problem with not saving pictures (P6P). But I use a gallery other than Google Photos, so maybe that's why. The stable version by MWP has a lot more settings options than the beta version, I think. But I use the MWP app mainly because of the names of the photos, which the built-in version has, politely speaking, 'awkward'.
legend221 said:
Thank you @novaq72
I tried out the last stable version and my P6 was not saving the pictures. I have been running without problems on 8.4.300 v1 beta3.
If anyone has any issue from the OP definitely try out the one above.
Click to expand...
Click to collapse
It's a pity, I don't have a problem with not saving pictures (P6P). But I use a gallery other than Google Photos, so maybe that's why. The stable version by MWP has a lot more settings options than the beta version, I think. But I use the MWP app mainly because of the names of the photos, which the built-in version has, politely speaking, 'awkward'.
Can you share the config file?
nchmaster said:
Can you share the config file?
Click to expand...
Click to collapse
I'm sorry unless it's on the official website I don't have it.
The app is working great without any additional files at the moment.
Google Camera Mod 8.4.300 v1 beta 5 by MWP
===============================
Changelog from previous version, plus:
1. Replacing Libpatcher with Rampatcher. Thanks Eszdman & Hasli.
2. Rearrange the settings menu.
3. Enable all fps selection in video mode.
4. Added Super res zoom / merge method.
5. Added max shutter speed limitation.
6. Added developer settings help.
7. And more
NOTE: All the previous configs (.xml) can't be use in this version.
MWP: Gcam_8.4.300_beta5_MWP
Download Gcam_8.4.300_beta5_MWP by MWP.
www.celsoazevedo.com
The download link on the site seems to be dead.
Fixed.
Google Camera Mod 8.4.300 beta 6 by MWP
==============================
Changelog from previous version, plus:
Minor changelog:
1. New libs ( xHDR & NoiC )
2. Optimized some code and added some parameters to libpatcher
NOTE: Clear app data & cache before use.
MWP: Gcam_8.4.300_beta6_MWP
Download Gcam_8.4.300_beta6_MWP by MWP.
www.celsoazevedo.com
Thanks for this. But the currently google camera in the store is 8.6?
Utini said:
Thanks for this. But the currently google camera in the store is 8.6?
Click to expand...
Click to collapse
Different developers use different Google Camera versions. Let's say it this way.. Latest is not always the greatest
Dayuser said:
Different developers use different Google Camera versions. Let's say it this way.. Latest is not always the greatest
Click to expand...
Click to collapse
Thanks! If i understand correctly the this does better pictures than the stock gcam? No .xml needed?
Utini said:
Thanks! If i understand correctly the this does better pictures than the stock gcam? No .xml needed?
Click to expand...
Click to collapse
It depends what you like. Every gcam versions with stock settings is little different but it is better use xml if somebody has created xml.