Database Users

Cpu tunner guid for noob ( --> me )

Hi
i found CPU Tuner app
https://play.google.com/store/apps/details?id=ch.amana.android.cputuner&hl=de
but i don't understand, what Settings are good
can you assist me ?
I found some guides, but they look not very good
Thanks

well ..
One option is to study/read the kernel threads in the android development and original android development nexus 4 sections - you will learn about cpu tuning from the kernel developers themselves. Many of them make specific applications for tuning their kernels.Thats how I approached it ...

I seems like it is mainly based on governors which generally change cpu frequency ramp up times and what kind of demand is loaded to cpu itself. So if you are not a pro about configuring kernels I advise you to flash franco, faux or some battery saver kernel and use their defaults. As I'm still a newbie I did modify cpu voltages and select "interactive" governor and it seems fine about battery life, but best way is; you need to read about kernels it may be dangerous also to play with hardware settings.

[GUIDE] Tips for Getting the Most from Your Custom Kernel

These tips are based in my study and experience of using different programs and techniques to get solid and stable performance from custom kernels. It's a long read, but a good read if you really want to minimize heat and maximize performance. This information works on any custom kernel that can be used with Synapse. This guide is aimed at beginner and intermediate users who are interested in custom kernel settings but don't know where to start. These are the most commonly optimized settings on Android.
***DVFS Rule #2 is exclusive to Samsung devices (so if you don't have a Samsung device don't use it!)***
Rule 1: What works for some won't work for others - This has always been the most important rule of custom kernels. One person using Barry Allen governor, overclocked to 3.07 GHz, and not using intelliplug will never hit 70C while your phone using those same settings might immediately cause the phone to reboot. All synapse changes made to a device must be tested by you to ensure compatibility for your hardware. Some of you may be curious, if this is the case, why Google would have everyone use the interactive governor by default? I would respond to you that they originally assigned everyone to OnDemand while they worked to make a better and more compatible Interactive governor. But as you know there are a LOT of governors out there and knowing what is best for your device is to read and to test it. The good news is that once you find something that works well you can stick with it as long as you own the device.
Rule 2: DVFS (Dynamic Voltage and Frequency Scaling) Disabler - This is mentioned in a few threads, but requires a repeat. Samsung uses DVFS to contol your CPU frequencies and voltage levels. This isn't an issue when you're running a stock kernel because it works in conjunction with MP-Decision to decide on the proper frequency level. When you're running emotion kernel you don't want DVFS to control anything. You want it to let Faux's Intellithermal work together with the kernel routines to shut down cores it doesn't need.
R2 Part 1: If your phone is running hot: Install Xposed, download Wanam Xposed (enable the module), Open Wanam, click "Advanced" menu, Uncheck "Enable TouchWiz DVFS" and reboot.
R2 Part 2: Following the reboot open Synapse, scroll over to CPU Drivers scroll down and put a checkbox in "Enable Intelli-hotplug", leave the rest alone, and click the check mark at the top of the screen to save changes. Scroll over one more screen to "Thermal" and put a check in the box, "Enable or Disable Intelli Thermal Control" and leave the settings below as they are unless you know what you are doing.
Note: The phone will be still be warm for awhile, but if you give the phone a break and allow the heat to dissipate it should run cooler and more consistently with the added bonus of shutting down 3 out of the 4 cores unlike MP-Decision which always leaves 2 cores live. After doing this if you are noticing performance loss or stuttering it's time to find a new governor that makes the most of these settings. Which leads me to Rule 3....
Rule 3: Choosing a new governor - This part is going to require some reading on your part, but I can assure you that it is worth your time. This guide http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957 by @gsstudios is OUTSTANDING (please thank him while you are there) and carries a LOT of information about the governors and other performance informations. So find something you like from the guide descriptions to try out and leave it in place for 24 hours or more as long as you aren't experiencing excessive lag or reboots. If it performs well under normal usage the next step is to watch battery life. There won't be a single governor that does everything perfectly, but finding something that fits your needs is key. And it's OKAY if you decide to stick with Interactive, it is a very well made governor and many are based off of that design, but I equate it to finding a good pair of shoes. Lots of things will protect your feet from the ground, but shoes that you enjoy and work well make all the difference in the world.
NOTE: You can use Antutu for stability testing but do not pick a new governor and then run benchmarks and expect top score unless you chose the performance governor. Antutu specifically maxes out your device voltage and frequency to see what the device can handle which is not what intelliplug is for. If you are following this guide benchmarks are the least of your concerns.
Rule 4: Don't forget your Scheduler - Believe it or not, everything runs off of your phone storage. So using an optimized scheduler for you device could make great strides in battery and performance improvements. Unlike choosing a governor, you can absolutely benchmark your flash memory to find out which scheduler works best for you. I only use one and I am going to shamelessly plug it here: I use Android Tuner to benchmark my flash speed with different schedulers and it works great for me. How it works:
Note:To help with choosing where to start with schedulers you can use the guide I linked to above which will give you an idea of what to use. That guide has an exceptional amount of information about how these types of schedulers work and what you should use for getting what you want from your phone. What follows is my advice for testing benchmark write performance and those steps are completely optional, but it never hurts to see how your device does with your chosen scheduler.
R4 Part 1: Launch Android Tuner, from the main menu accept root, acknowledge that root is powerful, scroll all the way to the far left screen, choose "SD Card Read Speed", click "Benchmark in the center, and then notice at the top you have /storage/emulated/0 which is your faster internal memory (which you should optimize first) and then /storage/ExtSdCard which you can benchmark second.
R4 Part 2: When you are ready to benchmark choose your "I/O Scheduler" from the drop down menu and click "Run". Your results will be listed with the fastest read-ahead size on the left and the speed at which it read on the right. Higher = Better -- Then you would choose the other test size (10MB in my case) and you see which readahead value is the fastest for those files. If you manage to get a readahead that the 100MB and 10MB test highest values are the same, then you've won the lottery. Since that is almost impossible try to remember what your top 5 fastest are and choose the one that performs well in both tests. If you want to keep testing and check other schedulers for raw read speed just switch them at the top and re-run both tests.
After you've found which scheduler gives you the performance you want, go back to Synapse, scroll to "I/O" tab, and adjust pick your scheduler and readahead value, and finally click the check mark to apply it.
Rule 5: Undervolting (IMO) does more harm than good - I'll let you Google it but it follows the rule of diminishing returns. You might be running Synapse and are able to undervolt 75mV and still cruise through menus and apps like it's no problem. But I promise you at some point the CPU is going to call for that voltage you starved it of and it will reboot. It's not a matter of if it will happen, but when it will happen. This comes down to your personal silicon and I do not recommend undervolting at all. Other more advanced users may disagree with me, but for the average user there are better ways to save battery and negate heat than starving your CPU and GPU at a kernel level. Especially with DVFS disabled.
And that's all I have for you. These tips work for any custom kernel that uses Synapse to manage their settings. I've personally test my setup with Emotion and the kernel we are not to speak of on XDA. If you like the idea of getting the most out of your device then a custom kernel might be for you, but it requires a lot of patience. If you just need something that works I definitely recommend the stock kernel because they really did a good job with the Lollipop release of our kernel.
I hope this helps some of you and I hope that everyone can take something away from this guide. Feel free to let me know if this helped you in some way or if you need some guidance on the topic. I'll do my best to backup my claims with proper research and documentation.
Thanks
Google - For research help and a great phone OS
Linux - The foundation of this OS
gsstudios - For his outstanding guide and work on researching this information (Definitely hit 'Thanks' on his post)
Note 4 ROM and Kernel Devs - we are very lucky to have a lot of great devs for our device; their work is appreciated and gives me something to write about
XDA and their members - where I've learned most everything about one of my favorite operating systems

[Tweaks] Basic Kernel tweaks for CM13

Hi guys,
Sharing with you'll few kernel tweaks that will betterment your battery backup and also maintain good performance on the default kernel of CM13 ROM and it's variants.
Won't bore you'll with lengthy description Head on straight to my screenshots and tweak accordingly.
These have resulted me with less drain in foreground usage and more solid backup in standby.

Thanks to you sir for writing this up! I'm going to try these settings on stock, just to
see if it'll work. If they do I'll let you know. May I ask you why you have set the minimum frequency higher?
EDIT:
The settings won't stick, not even through standby. Oh well. One probably needs a custom ROM then.

TVD1903 said:
Thanks to you sir for writing this up! I'm going to try these settings on stock, just to
see if it'll work. If they do I'll let you know. May I ask you why you have set the minimum frequency higher?
EDIT:
The settings won't stick, not even through standby. Oh well. One probably needs a custom ROM then.
Click to expand...
Click to collapse
Yes CM13 or its variants.
Stock ROM kernel is good by itself. In stock you can try only change IO Scheduler as deadline.
Edit: one small change in TARGET LOADS uploaded in last screenshot

Boeffla Configuration: Make Oxygen Fly

I figured I'd share my post with you guys here on XDA. My original post can be found on the OnePlus Forums.
Thanks to @Lord Boeffla OnePlus X users finally have the Boeffla kernel. This kernel brings several features which can aid in improving the fluidity and battery life of Oxygen. Hopefully someday we'll see his work with CM 13. That aside, let's get to my configurations
1. Governor/IO
I decided to use zzmoove alongside it's optimal profile. It provides smooth scaling between frequencies while maintaining great battery life. It also seems to fix performance in games. It should be noted though that Lord Boeffla did warn me against stability issues. I don't have any but it's something to keep in mind.
In place of ROW I switched over to FIOPS for the general performance benefits.
Everything else was left alone.
2. CPU
I increased the frequency to 2572mhz and applied an undervolt. I will not post undervolt settings. Every device is different and that's something you need to take into your own hands. Just because it works for me doesn't mean it'll work for you.
I did change the hotplug to zzmoove native default.
Everything else was untouched.
3. GPU
I just lowered the minimum frequency to 27mhz.
4. Boeffla Sound
I just enabled it. That's it. If anyone wants to share their configuration I'll upload it to this post.
5. Display + LED
Am I the only person that finds the display a little warm? I set red to 248 and green to 250.
Nothing else was changed
6. Miscellaneous 1
I enabled Boeffla system tweaks
Notice: if it wasn't mentioned I never changed it. This was done with the Boeffla app. Here's a link to the original thread:
http://forum.xda-developers.com/one...ernel-boeffla-kernel-4-0-beta1-18-02-t3317638
Flash Procedure:
Find your device and download the kernel here:
http://www.boeffla-kernel.de/
Alternative (Uber/Linaro):
http://boeffla.df-kunde.de/zanezam/linaro/oneplusx/oos2xx/test/
How does Uber compare to other tool chains?:
https://plus.google.com/ ChetKener/posts/YzMJEkzPQgp
Download the stock ROM here:
http://downloads.oneplus.net/
Download any third party tweaks such as Xposed that you use
Launch TWRP
Tap wipe, advanced wipe, and select everything except for internal storage.
Flash the ROM and then the kernel.
Reboot.
TWRP can be found here:
https://twrp.me/devices/oneplusx.html
Instructions to unlock the bootloader can be found here:
http://devs-lab.com/2015/11/how-to-root-oneplus-x.html
Disclaimer:
I'm not responsible if you void you're warranty, kittens fly out your ***, or phone explodes in your pocket in an attempt to boil water
02/28/16: Antutu results are no longer applicable. They are scattered all over the place. Some tests, I get 71k, others 44k. The kernel isn't at fault as all other benchmarks report consistent results. Geekbench seems to provide the most accurate representation at the moment so I'll keep it updated. As for Antutu, I will no longer update the scores until they change their entire algorithm.

General Recommendations
1. Don't enable multicore power saving as it's unpredictable in terms of stability and doesn't really aid battery life. I'd get locked cores and random reboots with it on.
2. Be cautious when undervolting and over clocking. Settings that may work for others, may not work for you. Every processor is binned differently.
3. Do not flash this over Blu Spark or any other kernel. Flash the ROM and then the kernel. Dependencies for each kernel differ.
4. Do not seek me expecting a fix or patch for any issues that you may have. This doesn't mean spam the author with requests either. I will try to help to the best of my abilities, but there may be an issue I can't remedy.

Profile Downloads
Attached you'll find my custom profile. Simply take it and copy it to the folder boeffla-kernel-data and then open the Boeffla Oxonfiguration app. Tap on Default and then load. My profile should show up as Swell.bcprofile.
https://drive.google.com/file/d/0B7CLqaEGT92AWWl3NFFybUt6X00/view?usp=docslist_
Refer to my disclaimer above please. My settings may not work for you.

Help regarding Franco Kernel Manager?

Just downloaded the latest version of franco kernel manager 6.1. Im a total noob in terms of using this tool, so I've been looking for a guide or a tutorial that can assist in using it. Also what is the method of flashing the franco kernel from this tool? Where can I download the franco kernel.zip? I have been looking all over, cant seem to find it. Plz help
Im currently on RR Rom latest version 8.6.3. Im looking for a setting to enhance battery life and overall performance of the Phone.

rigerp said:
Just downloaded the latest version of franco kernel manager 6.1. Im a total noob in terms of using this tool, so I've been looking for a guide or a tutorial that can assist in using it. Also what is the method of flashing the franco kernel from this tool? Where can I download the franco kernel.zip? I have been looking all over, cant seem to find it. Plz help
Im currently on RR Rom latest version 8.6.3. Im looking for a setting to enhance battery life and overall performance of the Phone.
Click to expand...
Click to collapse
Hey there
What I did to get Franco kernel was flash it during my first time rooting (so it was a clean flash, as the phone had be factory reset). Once you're in TWRP, you flash Franco kernel and then magisk. This is one way to do it. I can't advise you to flash a new kernel without clean flash because I personally didn't do it and I don't know if issues will come from that. If you can do it, my personal advice is to just do a clean flash. You know the drill, wipe system data and that stuff > flash ROM > Kernel > Magisk, and done
As for where you can get the zip, there is a thread here in the OP5 XDA forum on ROMs and Kernels I think and that's where franco posted the kernels. He's got a website too linked in the same post
HOWEVER, he hasn't updated them since last year, and I don't think they have support for Android 10, only 9
As for settings, well, in my own experience, you won't get any noticeable boost in battery life or performance without doing some drastic change.
If you want better battery life, you can decrease the maximum CPU frequency, change the governor to Conservative or Powersave, disable some cores, or all of those at once, but they WILL degrade performance, sometimes you won't notice but then you'll try to load a heavy webpage on Chrome and then you'll REALLY notice it.
The inverse is also true. To increase performance you change the governor to performance; usually the CPU frequency is set to its maximum by default, and the cores are all enabled anyway so you don't have to change anything. BUT, keeping the governor in Performance will also keep the CPU clocks at its maximum, and that's going to drain your battery like CRAZY, plus it'll overheat it. Usually there is no practical need for this setting, but I use it to play games on Dolphin emulator since thats when I can actually make use of that performance.
A better alternative is to keep the governor on Interactive, which will scale up CPU clocks depending on the load (if doing light stuff, low clocks. Heavy stuff > high clocks). Otherwise, Conservative does the same thing but takes longer to use higher clocks, so battery is saved.
Always use 1 governor for all cores. Do NOT use multiple governors (example: powersave for big cores, performance for little cores) because that will cause instability issues
Also, if you make any changes, you gotta tap the toggle on it, which will say something like "stay on boot: true". Otherwise, if you for instance change your governor to Performance, and then reboot, all your changes will reset to Default
Personally I just keep my governor in Conservative and roll with the defaults.
Hope that helps ya

sorry for digging but I was loooking for solution..
just make a backup of present kernel (tuned with FKM) and then flash it from backup menu
I was trying flash with twrp, magisk, 'set on boot' at first and many other things but it was so simple, it's there all the time