Develop Bugs

[Q] Best Kernel on G2 with MIUI

Trying to find out to anyone using or not using MIUI which kernel is the best for the G2, i am also trying to find out what SetCPU profiles work best with that kernel from personal experience.

Curious myself.
*bump*

I'm on the latest Pershoot and battery and performance is some much better than stock kernel. In fact, battery life is possibly better than Sense! I OC'd to 825-1497 MHz screen on and 245-368 with the screen off. I get the occasional (once in the few days I've been running the ROM) refusal to wake up, but I heard that's a bug in CM (which MIUI is based off) to do with OCing + screen on/off animations. I did, however, get tons of freezes and reboots when my maximum frequency was set at 1516MHz, which seems to be above the threshold my phone can take.
Anyway, that's my experiences, YMMV!
Hope I helped
Sent from my HTC Desire Z using Tapatalk

I have been in MIUI_1.07.15_OsiMood v1.0 (just flashing to 1.2)
atleast in 1.0 FM-radio on desire z didn't work whit Streamline5 and Pershoot 2.6.35.13 kernels. on default kernel it works.
i dont think i'm going to try out those kernels in 1.2... any kernel suggestions whit smartass/conservative governors and hopefully working FM-Radio?

Which version of MIUI are your running?
I'm currently running Carpes' Miui Version, "Light Gets Lighter"
The kernel I use is Eugenes' Streamline5 Kernel which can be found here Streamline5
He has a MIUI version but for some reason doesn't run well so just download the Original.
Here is the download link if you have trouble finding it > kernel download <
As for Setcpu settings
Max/Min
Main:
1000/800, smartass
Profiles:
Screen Off: 384/245, smartass
I only find the need for a screen off profile because I like my phone kept on low hz and it's pretty much the same as battery charging profiles if you have the same hz
Its also recommended not to underclock lower then 245 as it will cause a lock up or freeze being unable to wake up due to slow processing speed
1 Day, 13 Min, 56 Seconds = 21% Battery Left
Total about 1 hour browsing internet, maybe 20min total of youtube videos and moderate texting

xArcane1x said:
Which version of MIUI are your running?
I'm currently running Carpes' Miui Version, "Light Gets Lighter"
The kernel I use is Eugenes' Streamline5 Kernel which can be found here Streamline5
He has a MIUI version but for some reason doesn't run well so just download the Original.
Here is the download link if you have trouble finding it > kernel download <
As for Setcpu settings
Max/Min
Main:
1000/800, smartass
Profiles:
Screen Off: 384/245, smartass
I only find the need for a screen off profile because I like my phone kept on low hz and it's pretty much the same as battery charging profiles if you have the same hz
Its also recommended not to underclock lower then 245 as it will cause a lock up or freeze being unable to wake up due to slow processing speed
1 Day, 13 Min, 56 Seconds = 21% Battery Left
Total about 1 hour browsing internet, maybe 20min total of youtube videos and moderate texting
Click to expand...
Click to collapse
I was coming in to say just about the same thing. Funny because I'm usung the exact same SetCPU settings. Streamline5 is the absolute best way to go.
Sent from R2's G2 using the XDA Premium App!

Are.Two said:
I was coming in to say just about the same thing. Funny because I'm usung the exact same SetCPU settings. Streamline5 is the absolute best way to go.
Sent from R2's G2 using the XDA Premium App!
Click to expand...
Click to collapse
Happy to hear and yes, Streamline5 is awesome!
If Both our reviews still don't help then maybe this will. Another great thing about Streamline5 is that it will still run smooth even if you leave it clocked at just 800 alone and maybe squeeze a little more juice out .
Reason I scale it to 1000 is I like the little speed boost it gives me

Yes, got Tiamat kernel runing in my MIUI, and looks like everything is working fine, even FM-radio...
has all the necessary governors, and goes up to 2ghz
http://forum.xda-developers.com/showthread.php?t=1180071

xArcane1x said:
Which version of MIUI are your running?
I'm currently running Carpes' Miui Version, "Light Gets Lighter"
The kernel I use is Eugenes' Streamline5 Kernel which can be found here Streamline5
He has a MIUI version but for some reason doesn't run well so just download the Original.
Here is the download link if you have trouble finding it > kernel download <
As for Setcpu settings
Max/Min
Main:
1000/800, smartass
Profiles:
Screen Off: 384/245, smartass
I only find the need for a screen off profile because I like my phone kept on low hz and it's pretty much the same as battery charging profiles if you have the same hz
Its also recommended not to underclock lower then 245 as it will cause a lock up or freeze being unable to wake up due to slow processing speed
1 Day, 13 Min, 56 Seconds = 21% Battery Left
Total about 1 hour browsing internet, maybe 20min total of youtube videos and moderate texting
Click to expand...
Click to collapse
I can't get past the bootanimation after flashing streamline5 on CarpeNoctem"s miui. any help would be appreciated.
also, can I manually change the min mhz up to 245?

Best SetCPU Config for Desire

Hello
Does anybody use set cpu with HTC Desire ?
I would like to know wich settings work the best for you. I am trying to get the best compromise between battery life and performance.
Thanks

128MHz - 998MHz ondemand. I get more than enough life out of it. I found that if your using AOSP and not really doing much on it like just texting or calling people, capping the max to about 600MHz or 500MHz if you want, works a dream and you get even longer out of it.

Smartass is better or worse ?

I do not see any real difference between smartass and interactive in term of battery live and performance.
On demand seems to drain slightly faster than smartass.
I set my Desire to 384-1136 with interactive govenor.
I charge it once i a day each time before I go to bed anyways (sleeping time usually23.00 - 05.00), so further battery saving is not necessary to me
Edit...my normal usages are:
Syncs (no auto sync by opening):
Friendstream 4 hrs
News 4 hrs
Weather 6 Hrs
push Yahoomail
push Googlemail
push Whatsapp
push EBuddy
Active background :
Lookout antivirus
No app killer used
Phone calls : about 1-2 hrs each day
Music listening mit DSP add-on : 4 hours
Fruit ninja (man! this is addictive!) : 1 hrs
Browsing (Dolphin HD + Android market) : 2 hrs
welll....every time I charge my battery it is about 15-25% left till out of juice...if I use my phone more than those, I have to charge it earlier (more than once a day)

245 - 985 MHz Conservative give mere 36 hours power and running smooth.
Sent from my HTC Desire using XDA Premium App

For me the battery has never lasted more than a day... Even on my un-rooted one...

BTW: Battery live depends on many things
1. Your ROM and kernel
2. Your runnning application, syncs, etc.
3. your usage and settings such as cpu freq, display brightnes, airplane mode, etc.
4. Received signal quality.
5. The condition of the battery...is it top fit for example?
It is difficult to measure the battery live.
@atuladhikari : battery live has nothing to do with rooting..

aaa said:
BTW: Battery live depends on many things
1. Your ROM and kernel
2. Your runnning application, syncs, etc.
3. your usage and settings such as cpu freq, display brightnes, airplane mode, etc.
4. Received signal quality.
5. The condition of the battery...is it top fit for example?
It is difficult to measure the battery live.
@atuladhikari : battery live has nothing to do with rooting..
Click to expand...
Click to collapse
It's LIFE not live
Sent from my HTC Desire using XDA Premium App

kpyhere said:
Smartass is better or worse ?
Click to expand...
Click to collapse
I don't like using any of the other governors since I get lag. I hate lag. OnDemand gets rid of the lag for me. I've had it before where I was using smartass and it took ~30 seconds for my screen to turn back on from idle. I wasn't too impressed.

setcpu
thanks meaple for your advice
i think that set cpu is fine on "ondemand" for some roms and for others roms no
set cpu is included on oxygen settings and running well

Cool, I need to download Setcpu

128-998 ondemand
screen off 128-384 ondemand
in call 128-384 ondemand
I get very good battery and performance with theses settings.

Which app do you guys recommend? Tried overclock widget doesn't seem to be working.
Am on Insertcoin stock GB rom.

dezpo said:
Which app do you guys recommend? Tried overclock widget doesn't seem to be working.
Am on Insertcoin stock GB rom.
Click to expand...
Click to collapse
Maybe SetCpu?

bates060 said:
It's LIFE not live
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
DidI do that?....I did.... LOL.

I used to use set cpu
set a profile like
Smartass
on charge - 1113mhz
80% - 100% - 998mhz
59% - 79% - 600mhz
35% - 58% - 500mhz
Screen Off - 300mhz
Priority was higher for lower battery %
BUT I stopped using it because of the little bugs, like when it changes to 384mhz for no reason after unlocking screen
It also affects the standard script with the rom you install, so you can never uninstall it properlu, you have to do a full wipe install and never install it, until I did that my phone was always a little laggy
I prefer my phone without it Each to their own

@shankly1985 - you didn't noticed wakeup lag with 128 MHz?
I must use 245 - x MHz to properly and fast unlock my phone.

Best Setcpu config for Desire is - no Setcpu at all.
BigMrB said:
BUT I stopped using it because of the little bugs, like when it changes to 384mhz for no reason after unlocking screen
It also affects the standard script with the rom you install, so you can never uninstall it properlu, you have to do a full wipe install and never install it, until I did that my phone was always a little laggy
I prefer my phone without it Each to their own
Click to expand...
Click to collapse
I couldn't agree more with you. Experienced all of the above so no go.

245-1033mHZ with smartass give me two day out of my desire loaded with insercoin 1.0.9 with v06 kernel !
I am mostly sending Text message and some calls.

drakexpl said:
@shankly1985 - you didn't noticed wakeup lag with 128 MHz?
I must use 245 - x MHz to properly and fast unlock my phone.
Click to expand...
Click to collapse
Not at all mate, I get zero lag on my phone. when I check the info on the setcpu app and time in state 128 is at 85% so my phone is using very little cpu.

[KERNEL][AOSP4.4/5.1/6.0/7.1] dkp - d2att - 2/4/18

Welcome to decimalman's kernel playground!​
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
Underclocking down to 54 MHz, with stability improvements
Undervolting compatible with most apps
Fast charge without unplugging first
Glorious animations for the notification and softkey LEDs
Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
Automatic mpdecision and auto-hotplug are only enabled when needed
Adjustable minimum voltage for stability on finicky processors
Optimized UKSM to free up some extra memory
Code optimizations for size and speed
Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
Nandroid!
last_kmsg and/or logcat or it didn't happen.
Other kernels have their own threads or forums. Discuss them there.
Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
Be silly. We're here to have fun.
Installation:
Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.

Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
FauxSound support
Strip more useless stuff
A few bonus optimizations
4/8/13 (3.4):
Port everything except erandom from 3.0
Enhance cpufreq for easier configuration
4/24/13 (3.4):
Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
Lots of CM/CAF/Linux updates
Working AssWax governor
Trinity colors support
sio, zen I/O schedulers
erandom is back!
Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
Probably lots more, but there's hundreds of commits to sort through...
5/29/13 (3.4):
Bugfixes: better overclocking support, better hwrng support, etc.
Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
Automatic auto-hotplug
New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
6/14/13 (3.4):
Bugfixes: fix several critical bugs in the 5/29 release.
9/7/13 (3.4):
Fixes for OC, UV, auto-hotplug.
A few new optimizations.
Synced up with CM.
9/20/13 (TW):
Ported everything from AOSP to TW.
9/20/13 (4.3):
Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
Nothing interesting at the moment.

Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
Create a folder on your internal storage named "dkp"
Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
Code:
su
dkp
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.
sysfs:
It's possible to adjust all the settings available in dkp without using apps. Because they show up as files, settings can be adjusted with file managers, terminal emulators, adb and initscripts. Here's the most interesting files inside sysfs:
/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors (not available on newer AOSP builds): display tint (0 = very red, 2 = default, 4 = trinity colors)
/sys/class/misc/gammacontrol (only available on newer AOSP builds): various color controls. See this post for details on enabling Trinity colors on builds that use these controls.
/sys/devices/system/cpu/cpu<N>/cpufreq/UV_mV_table: voltage table
/sys/devices/system/cpu/cpu<N>/cpufreq/scaling_...: scaling_governor is the governor, scaling_min_freq and scaling_max_freq are the minimum and maximum frequencies, scaling_available_governors and scaling_available_frequencies show the available governors and frequencies
/sys/kernel/dkp/force_fast_charge: fast charge
/sys/kernel/dkp/link_core_settings: when linked (the default), frequency settings and some governors are automatically copied to the other core
/sys/kernel/dkp/vmin: minimum processor voltage in mV
/sys/kernel/mm/uksm/run: activate UKSM
auto-hotplug tuners:
These show up in the governor settings for any governor that doesn't do its own hotplugging. They only take effect when using auto-hotplug, so you'll probably need to disable mpdecision in Trickster.
hotplug_intpulse: when set to 1, automatically turns core 2 on whenever the screen/buttons/whatever is pressed. Default is 0.
hotplug_sampling_periods: number of samples to use for average number of running tasks. Default is 15.
hotplug_sampling_rate: number of 'jiffies' (currently 1 jiffy = 10 ms) between each sample of running tasks. Default is 20 (0.2 sec).
hotplug_enable_one_threshold: the average number of running tasks required to turn core 2 on, multiplied by 100. Default is 125 (1.25 tasks on average).
hotplug_disable_one_threshold: the average number of running tasks required to keep core 2 on, multiplied by 100. Default is 250 (2.5 tasks on average).
freelunch/nanolunch tuners:
freelunch and nanolunch aren't materially based on other governors, so their configuration is quite different than other governors. There's lots of tuners, since I haven't really decided on an ideal tuning. I encourage experimentation! I'll explain a bit of how these governors work before actually listing the tuners.
Generally speaking, there are two modes: in "normal" mode, sampling is done occasionally and frequency is generally increased slowly; in "interactive" mode, sampling is done much more quickly, and frequency increases much more quickly. "Interactive" mode ends after several samples of very low usage. The idea of a "hispeed" frequency is used in lots of governors, and it refers to the frequency that the CPU will jump to when more CPU usage is needed; generally, it's a generous estimate of how much CPU will be needed. Here, the hispeed frequency is adjusted on-the-fly, increasing when more CPU is needed and gradually decreasing when the CPU is idle. In "interactive" mode, the hispeed frequency is kept fairly high so that everything will feel snappy.
Hotplugging is taken care of in the least complicated (and in my opinion, most reasonable) way possible: if core 1 is using lots of CPU, and there are several tasks running (in other words, if it's likely that core 2 will have something to do), core 2 is turned on; if either core isn't doing much except using power, core 2 is turned off.
sampling_rate: the usual
hotplug_up_cycles: number of consecutive heavily-loaded samples before core 2 is turned on
hotplug_down_cycles: number of consecutive lightly-loaded samples before core 2 is turned off
hotplug_up_load: number of running tasks required to bring core 2 online
hotplug_up_usage: number of used CPU cycles (in thousands per second) required to bring core 2 online
hotplug_down_usage: number of used CPU cycles (in thousands per second) required on both cores to keep core 2 online
overestimate_khz: number of CPU cycles to overshoot usage by in "normal" mode
hispeed_thresh: if CPU usage is within this many cycles (in thousands per second) of the maximum frequency, frequency will be increased to the hispeed frequency. Generally, hispeed is pretty low in "normal" mode, and fairly high in "interactive" mode.
hispeed_decrease: when the CPU is sitting idle, the hispeed frequency is decreased by this amount each sample (this isn't ideal, but it works)
interaction_hispeed: the initial hispeed frequency when switching to "interactive" mode
interaction_return_cycles: number of consecutive lightly-loaded samples before returning to "normal" mode
interaction_return_usage: number of used CPU cycles (in thousands per second) required to stay in "interactive" mode
interaction_panic (nanolunch only): when set to 1, allows aggressively jumping past the current hispeed frequency under some circumstances
interaction_sampling_rate/overestimate_khz: equivalent to the "normal" versions of the tuners, these take effect in "interactive" mode

Just loaded it on pa 3.15
Sent from my SAMSUNG-SGH-I747 using xda premium

It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app

rmead01 said:
It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It doesn't, but I'll merge it and put out a test build.

decimalman said:
It doesn't, but I'll merge it and put out a test build.
Click to expand...
Click to collapse
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app

rmead01 said:
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae

Thnx for this kernel

decimalman said:
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae
Click to expand...
Click to collapse
Maybe I was just seeing things, had just watched jurassic park in 3d.
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?

rmead01 said:
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
+1 on these questions
Sent from my AT&T Samsung Galaxy S III

rmead01 said:
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
Click to expand...
Click to collapse
Answered my own problem. I installed trickster as mentioned in OP and all voltage settings stick no problem with no issues.

rmead01 said:
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this into 3.0 and 3.4, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).

decimalman said:
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this in, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).
Click to expand...
Click to collapse
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that figured out I removed kernel tuner. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point. just as an example, some governors would be better for screen on/off and tasker could switch these to edge out battery life.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both governor and voltage adjustments well. i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.

rmead01 said:
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that was made it was no problem. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both well, i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.
Click to expand...
Click to collapse
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Edit: I think I've got Voltage Control fixed. I should be able to get Kernel Tuner working without too much work. I haven't even looked into Performance Control yet.

decimalman said:
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Click to expand...
Click to collapse
well good job so far. batt life has been top notch. minimal drain in use and my over night idle drain was only a few %. I have things setup to disable wifi when sleep and also turn off mobile data when wifi is connected. A bit over the top but every bit helps.
:good::highfive:

I know I've been grilling you today but...
Kind of curious what the new tunables do. I haven't touched anything since it's working so well but there is always that part of me that wonders what adjust parameters will do. Is there any kind of reference for this governor that could indicate that type of info?

Does your kernel support faux sound app?

stevehkim said:
Does your kernel support faux sound app?
Click to expand...
Click to collapse
Yes. 3.0 and 3.4 both have support.
As for tuneables, I've been meaning to post a writeup but haven't gotten around to it. You're not the first to ask about it.
Sent from my SPH-L710 using xda app-developers app

This is a fantastic Kernel! The battery life has been outstanding so far. Thank you for your amazing work!

[GUIDE] [ROOT] ExtremE Battery Life, ie Ultra power saving mode!

GUIDE TO EXTEND YOUR BATTERY LIFE UP TO THE LIMIT
20% Enough For A Day!​It is one of the best option if you left home with less juice, and are going to be in a trouble!
Yesterday, when I was on a trip with my friends, I forgot to charge my battery, and guess what: just 17% of juice left on my device at early 6 AM! So, I used this simple method, which I am going to explain down there, then while returning home at 9:30, 6% of juice was available!
The thins that I did was, listened to music for more than 10 hours (via earphones), Took photos for more than 15 mins (altogether), Surfed 3G for about 7-10 mins (on way back to home! ), and some phone calls!
Click to expand...
Click to collapse
App required:-
No-frills CPU Control: Most of the custom ROMs have this app integrated, but you can also download from Play store! https://play.google.com/store/apps/details?id=it.sineo.android.noFrillsCPU
STEPS:-
1. Go to No Frills Cpu Control or Cpu Settings(on most ROM's settings)
2. Select:
-Ondemand (Extreme Battery life)
-Powersaver/Conservative (Ultra Extreme battery, but laggy)
3. Tick Apply on boot and choose Apply!
4.Youre done, Enjoy ur maximum battery life!
-P.S: To have these governer, i.e. "ondemand/Powersaver/Conservative" you must be on Custom kernel bcoz, its not available for stock kernel!
Click to expand...
Click to collapse
Here's the pic of mine battery within 2 hours (27%-22%). And post your best battery status too!
Click to expand...
Click to collapse

Non Sense and Requires custom kernel

bt its too lag, and the cpu always 126 mhz

GalKill said:
bt its too lag, and the cpu always 126 mhz
Click to expand...
Click to collapse
Its for emergency, and you can use ondemand governer to reduce lags!
Ondemand governer takes phone to deep sleep while screen turned off, and required CPU value, when needed!

myaservip said:
Non Sense and Requires custom kernel
Click to expand...
Click to collapse
It works fine, give it a try during emergency!

i mean not suitable for all

myaservip said:
i mean not suitable for all
Click to expand...
Click to collapse
Indeed, It is not suitable for multi tasking

lionelsuyog said:
Its for emergency, and you can use ondemand governer to reduce lags!
Ondemand governer takes phone to deep sleep while screen turned off, and required CPU value, when needed!
Click to expand...
Click to collapse
well for your kind information all the governers (if have custom kernel) take phone to deepsleep while screen off. And as per your thread title i don`t think the guide is that effective becoz this governer thingy is known by almost every one here.Not trying to flame but just wanted to say that don`t open new threads for such known things.

stock kernel have 2 governor
bcm21553 and performance
this trik can be apply when we use custom kernel
i know about this long time ago
:cheers:

Best kernel configuration (for rooted G4) to improve speed and battery

With root we can modify some kernel parameters of a stock or modded kernel. What is the best configuration you have found to improve speed and battery?
I start first.
ROM Genisys 3.4 Marshmellow 6.0
Kernel SuperXe 1.6 (stock cpu freq)
App Kernel Adiutor
CPU Governor (for big and LITTLE cores): interactive
GPU Governor msm-adreno-tz
Adreno idler: on
Scheduler I/O: Zen with 512kB Read-ahead (for internal memory); BFQ with 2048kB Read-ahead (for external SD - 64GB)
TCP congestion: Westwood
Doze settings: GeraldRudi profile
With that settings, apps and games run fast and smooth and I have a great battery life for a day full of work. And yours?

Stock.
Everything runs fast and stable. Battery lasts all day, 4h SoT :good:

I am the battery champion around here - lol
I routinely get 22-30 hours!
running Stock 20B, rooted, unlocked bootloader and a few little tweaks here and there (chase down what apps are running when idle and kill them off if not necessary with Autostarts or similar program and debloat anything your do not need - I use Link2SD and convert system apps to user apps then reboot and uninstall them)
and don't run silly stuff you don't need, such as CPU governor - the one already running on your phone works as well as any, having two just wastes CPU time and confuses things

WTF? said:
I am the battery champion around here - lol
I routinely get 22-30 hours!
Click to expand...
Click to collapse
22 hours SoT indeed is very impressive. 22 hours runtime is nothing special, at all :good:

Pfeffernuss said:
22 hours SoT indeed is very impressive. 22 hours runtime is nothing special, at all :good:
Click to expand...
Click to collapse
your comment seems silly, what kind of moron would keep his screen on continuously for 22 or 30 hours?
like when you are talking on the phone, typically don't need the screen on for that! - or using the phone for music, or as a wifi hotspot, etc.
the trick I was trying to convey here is to keep the screen *off* as much as possible, and as few apps and processes running as possible, both background and foreground!
but I certainly didn't mean the phone was idle either, it's always being used :good:

WTF? said:
your comment seems silly, what kind of moron would keep his screen on continuously for 22 or 30 hours?
like when you are talking on the phone, typically don't need the screen on for that! - or using the phone for music, or as a wifi hotspot, etc.
the trick I was trying to convey here is to keep the screen *off* as much as possible, and as few apps and processes running as possible, both background and foreground!
but I certainly didn't mean the phone was idle either, it's always being used :good:
Click to expand...
Click to collapse
So the result is normal and/or really bad, without stating the SoT.
22/30 hours is nowhere near champion level, at all. Hence my ironic remark.