Hi.
It seems, my defy+ can't be undervolted as much as most other devices. I'm currently wondering, if there is an app that might help me find optimal values. Something that logs cpu-clock-changes and reboots, so i know which individual setting is problematic.
Thanks
There is an app in the forums called vsel calculator, but the formula is pretty well known for stable (in most devices) minimal Vsel; take the CPU clock, divide by 20 and add 2 to 4. Change Vsel for one clock at a time to see if it´s stable and you are good to go
I recommend SetVsel. For finding stable values you should run the stability test at each vsel.
Related
I need maximum battery time. So what is the best kernel for this and it´s configuration? I don´t need answers like "search for it" . Go hell those stupid guys.
voidvader said:
I need maximum battery time. So what is the best kernel for this and it´s configuration? I don´t need answers like "search for it" . Go hell those stupid guys.
Click to expand...
Click to collapse
there is no such thing as perfect kernel or perfect configuration,
the factors that can determine the amount of battery usage depends heavily on the nature of the usage under the user itself,
most kernels with undervolt support and underclocking will do fine,
i'd suggest you try out tweaks and preferences yourself since no one can guarantee you an exact time frame,
but i'll give you mine,
ROM: WP8 Monochromatic 5.1
Kernel: Built-in rom (savie's)
Tweaks: Built-in rom
Scaling freq: 156min 624max
CPU Governor: ondemandx
reduced all bloatwares even gmail and maps,
Battery Time (heavy usage): 4hrs max (medium usage): 1-1.5 day max (minimal usage) 2-3days max
that's just about it,
please take the time to conduct a research on what is your best prefered battery saving method,
don't call anyone stupid,
it's bad and potato disapproves
Rom doesnt matter really if you manage the applications well.
Use kuros kernel + kuros tweaks. Thats the best battery saving combo Ive tried.
For governor, use ondemand, the most battery efficient governor and use deadline for i/o
deathnotice01 said:
there is no such thing as perfect kernel or perfect configuration,
the factors that can determine the amount of battery usage depends heavily on the nature of the usage under the user itself,
Click to expand...
Click to collapse
Not really. Change between Merruk #206 and kuros latest, you can really notice the battery drain difference. Its battery efficient than stock kernel in my tests.
Here u go:
Before all id reccomend updating the software to the latest version xD
Use the latest white kernel
Use v6 supercharger and some other tweaks
Reduce the screen brightness
Lower the system volume in the sounds options
Disable animation
Disable auto-sync
Disable backup settings
Disable roaming ^^,wifi,mobile internet,bluetooth when you dont use it(gps even if turned on allways is only actually active when theres a open app that uses gps ^^)
Disabling more sound effects will make it ugly and not cool lol,so do as u wish with thease:
Keyboard sounds
Lock screen sounds and vibration
set a boot frequency in set cpu like:
312-832,conservative,sio
Set up proper profiles in set cpu like
Screen off
312-312,powersave,noop
Charging
312-832,ondemand,sio
Battery 50 F
312-832, conservative,noop
Battery <16
312-832, conservative, noop
here just take my setcpu profiles, i made it in setcpu 3.07 just put it in the root of your sdcard and in setcpu enable profiles and click on restore profiles and click on that
http://www.mediafire.com/?ru786ho4o9i7jdp
Here are some build.prop tweaks
ro.ril.power.collapse=0
ro.ril.disable.power.collapse=0
dalvik.vm.heapstartsize=4
dalvik.vm.startheapsize=4
this one is alredy in v6 supercharger ;P
pm.sleepmode=1
remove some useless apps that u dont use but their allways running in the background(yeah remove anything u will never use)
Google maps
email(not gmail)
software update
and buying a new, better battery isnt a bad idea too ? is it (obviously xD)
I hope i Helped, this and some of my other build.prop tweaks made my battery go like lol xD it was lasting so long idk how much was it
Thank you all! Thanks so much guys!:good:
Filip98 said:
Here are some build.prop tweaks
ro.ril.power.collapse=0
ro.ril.disable.power.collapse=0
dalvik.vm.heapstartsize=4
dalvik.vm.startheapsize=4
this one is alredy in v6 supercharger ;P
pm.sleepmode=1
I hope i Helped, this and some of my other build.prop tweaks made my battery go like lol xD it was lasting so long idk how much was it
Click to expand...
Click to collapse
the correct one is "dalvik.vm.heapstartsize". dalvik.vm.startheapsize is not exist. nevertheless, this script only work for ICS. GB based rom doesnt have these prop. please be carefull with any prop for virtual memory like this one. if you clean your dalvik-cache you might ended up in bootloop.
Lots of information.
Thanks guys.
Sent from my GT-S5360 using xda premium
You can search all you want and still come up short, I'm trying to use system tuner to change the cpu and gpu settings and I cant find any help on how to use this app. Im running the latest Kaos Droid rom for 4.1.2, the latest Motley kernel and twrp, props to all developers:good:. Im looking for what the optimal settings are and how to use system tuner to change them. Can someone tell me or show me the right thread that can help? Im not sure what the min/max cpu settings should be and I cant seem to find where to change the gpu settings. We are all noobs at some point. I just want to beef my nexus up a little, nothing crazy.
aww for real?
I wouldn't use system tuner for this because it doesn't have the ability to change the GPU speed. I'd recommend TricksterMOD which is available here for free. Depending on your kernel (not sure if motley's kernel has configurable GPU now, it didn't when I used it) you can change different settings. It is personally up to you how you want to configure your device and change things depending on how it runs. Anyway, I'll give you an idea of my settings that I have changed.
CPU - Governor is Interactive (my kernels default but another alternative would be ondemand) running @ 102mhz min - 1600mhz max
IO - Governor is deadline (again default but imo the only one you should use) with cache at 1024.
GPU - 600mhz
VOLTAGES - My kernels defaults.
Make sure that you set the settings to be applied at boot (I use a delay of 1 because it didn't seem to apply without it) and also make sure your kernel has the powerHAL fix included, or else (in the case of trinity kernel) you will need to download this file (this is for Android 4.2.x). This will allow your CPU overclock to stick and not be reset to stock.
Hopefully this helps! But again, just play around with your frequency's and maybe look into voltage tweaking to get your personal balance between performance and power consumption. And if you are going for performance, I'd look at turning off fsync and using the ext4 mount script to boost your I/O dramatically (this will result in things such as faster app installs)
smt8544 thanks alot man! now I can start somewhere, I didnt wanna do anything stupid without some knowledge, I appreciate it!
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.
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
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