Related
I just updated to the newest SetCPU and am confused with all of the new schedulers and governor setting. I am looking for good battery life. Does someone have settings to share with me? Much appreciated.
What governors are available? I haven't messed with CPU clocking on this phone. But on my old Desire Z, conservative with screen off, and on-demand for screen on was a pretty good setup.
ondemand, powersave, performance, and usersave. Do you have any other specific tips on how to adjust settings under the governor tab?
You should try the new SetCPU. The Dev added a lot more custom profiles that might make it more useful.
I used this on my GSII, is it worth plugging it in for the HOX? I'm on CleanRom 2.4. I don't even remember what I used it for.
I've been getting excellent battery life with the following profiles:
Screen on:
Min: 384
Max: 1512
ondemand
Screen off:
Min: 384
Max: 384
powersave
Battery <= 15%:
Min: 384
Max: 384
powersave
Thanks to deedii for posting this in another forum:
http://forum.xda-developers.com/show...65&postcount=2
Android CPU governors explained
1: OnDemand
2: OndemandX
3: Performance
4: Powersave
5: Conservative
6: Userspace
7: Min Max
8: Interactive
9: InteractiveX
10: Smartass
11: SmartassV2
12: Scary
13: Lagfree
14: Smoothass
15: Brazilianwax
16: SavagedZen
17: Lazy
18: Lionheart
19: LionheartX
20: Intellidemand
21: Hotplug
22: BadAss
23: Wheatley
24: Lulzactive
25: Pegasusq/Pegasusd
26: hotplugx
27: AbissPlug
28: MSM DCVS
29: IntelliActive
30: Adaptive
31: Nightmare
32: ZZmove
INFO I/O Scheduler go here: SCHEDULER
1: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.
OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.
This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.
2: OndemandX:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
4: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
5:Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.
The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.
6: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.
7: Min Max
well this governor makes use of only min & maximum frequency based on workload... no intermediate frequencies are used.
8: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.
9: InteractiveX Governor:
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
10: Smartass
Is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
11: SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
12: Scary
A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
13: Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
14: Smoothass:
The same as the Smartass “governor” But MUCH more aggressive & across the board this one has a better battery life that is about a third better than stock KERNEL
15: Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery
16: SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
17: Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
18: Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source.
The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
19: LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
20: Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors)
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
21: Hotplug Governor:
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."
22: BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing)
Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
23: Wheatley:
Building on the classic 'ondemand' governor is implemented Wheatley governor. The governor has two additional parameters:
target_residency - The minimum average residency in µs which is considered acceptable for a proper efficient usage of the C4 state. Default is 10000 = 10ms.
allowed_misses - The number sampling intervals in a row the average residency is allowed to be lower than target_residency before the governor reduces the frequency. This ensures that the governor is not too aggressive in scaling down the frequency and reduces it just because some background process was temporarily causing a larger number of wakeups. The default is 5.
Wheatley works as planned and does not hinder the proper C4 usage for task where the C4 can be used properly .
For internet browsing the time spend in C4 has increased by 10% points and the average residency has increased by about 1ms. I guess these differences are mostly due to the different browsing behaviour (I spend the last time more multi-tabbing). But at least we can say that Wheatley does not interfere with the proper use of the C4 state during 'light' tasks. For music playback with screen off the time spend in C4 is practically unchanged, however the average residency is reduced from around 30ms to around 18ms, but this is still more than acceptable.
So the results show that Wheatley works as intended and ensures that the C4 state is used whenever the task allows a proper efficient usage of the C4 state. For more demanding tasks which cause a large number of wakeups and prevent the efficient usage of the C4 state, the governor resorts to the next best power saving mechanism and scales down the frequency. So with the new highly-flexible Wheatley governor one can have the best of both worlds.
Obviously, this governor is only available on multi-core devices.
24: Lulzactive:
Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
25: Pegasusq/Pegasusd
The Pegasus-q / d is a multi-core based on the Ondemand governor and governor with integrated hot-plugging.
Ongoing processes in the queue, we know that multiple processes can run simultaneously on. These processes are active in an array, which is a field called "Run Queue" queue that is ongoing, with their priority values arranged (priority will be used by the task scheduler, which then decides which process to run next).
To ensure that each process has its fair share of resources, each running for a certain period and will eventually stop and then again placed in the queue until it is your turn again. If a program is terminated, so that others can run the program with the highest priority in the current queue is executed.
26: hotplugx
It 'a Hotplug modified and optimized for the suspension in off-screen
27: AbissPlug
It 'a Governor derived hotplug, it works the same way, but with the changes in savings for a better battery.
28: MSM DCVS
a very efficient and wide range of Dynamic Clock and
Voltage Scaling (DCVS) which addresses usage models from
active standby to mid and high level processing requirements.
A Krait CPU can smoothly scale from low power, low
leakage mode to blazingly fast performance.
Believe it's a governor that is mfg'd by qualcomm to utilize new on chip features.
MSM is the prefix for the SOC (MSM8960) and DCVS is Dynamic Clock and Voltage Scaling. Makes sense, MSM-DCVS
29: IntelliActive
Based off Google's Interactive governor with the following enhancements:
1. self-boost capability from input drivers (no need for PowerHAL assist)
2. two phase scheduling (idle/busy phases to prevent from jumping directly to max freq
3. Checks for offline cpus and short circuits some unnecessary checks to improve code execution paths
30: Adaptive
This driver adds a dynamic cpufreq policy governor
designed for latency-sensitive workloads and also for demanding
performance.
This governor attempts to reduce the latency of clock
increases so that the system is more responsive to
interactive workloads in loweset steady-state but to
to reduce power consumption in middle operation level level up
will be done in step by step to prohibit system from going to
max operation level.
31: Nightmare
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery.
In addition to the SoD is a prevention because it usually does not hotplug.
32: ZZmove
ZZmove Governor optimized for low power consumption with the screen off, with particular attention to the limitation of consumption applications in the background with the screen off, such as listening to music. It has three settings: battery saver, balanced and performance. In addition to a performance boost, there is also the governor zzmove optimized.
Credits goes to:
http://icrontic.com/discussion/95140...m-tuner-tegrak
http://forum.xda-developers.com/show....php?t=1369817
NICE!
Really nice job there but badass governor is missing
Sent From My Sexy Sensation.
Very informative, thanks..could u also add a description for the new pegasus governor
Sent from my HTC Sensation 4G using Xparent Blue Tapatalk 2
I'll put to work
Where does bricked kernels badass fit in? What is it most similar to?
This was a good read, thanks for taking the time to write it up
kingston73 said:
Where does bricked kernels badass fit in? What is it most similar to?
Click to expand...
Click to collapse
perhaps because the translator, but I can not understand the question
Show-p's bricked kernel has a governer called "badass" and I wanted to know which kernel is most like his?
kingston73 said:
Show-p's bricked kernel has a governer called "badass" and I wanted to know which kernel is most like his?
Click to expand...
Click to collapse
I put badass to the list so you can compare and see which governor is right for you
thanks for the explanations, i was confused about what governor to choose and what each one did, but this explains everything in one place well done!
julio_rdz said:
thanks for the explanations, i was confused about what governor to choose and what each one did, but this explains everything in one place well done!
Click to expand...
Click to collapse
thanks, I'm glad this is useful for users
There are waaay to many governors(incl custom), many actually aren't even significantly different from another. If you ask me I say all we need is conservative, ondemand, and not performance(pointless+battery rape). Although I don't mind the x versions of the ones I listed, but that's just b/c I like the x nomenclature.
Excellent explanation!
Thank you very much!!
Anyone know a mod to keep my device cool-er while on badass
@OP great job on the explanation extremely useful.
Mr.Highway said:
Anyone know a mod to keep my device cool-er while on badass
@OP great job on the explanation extremely useful.
Click to expand...
Click to collapse
reflash the kernel using the below settings
keep 2d and 3d to default (most of the heating issues comes from gpu overclocks) and freq to default
also use battery saver configuration (it handles cpu freq transitions) (its not laggy btw)
on the contrary you can use iba's badass mod's but they are told to be placebo's (by the badass dev itself)
Mr.Highway said:
Anyone know a mod to keep my device cool-er while on badass
@OP great job on the explanation extremely useful.
Click to expand...
Click to collapse
You can also use this mod, it works great :http://forum.xda-developers.com/showthread.php?t=1641605
Several requests by, before long new incoming governor
Can you find an explanation for, and include, the wheatley governor please?
slopra said:
Can you find an explanation for, and include, the wheatley governor please?
Click to expand...
Click to collapse
I'm also working on it, just realized the work I insert
[MOD]Governor, Freq. & Voltage Tweaks: aospX, BlackoutICS, JellyTime & CM 10.1 Rom's
Frequency and Voltage Tweaks for Blackout ICS 3.2.0
These tweaks adjust maximum processor frequency and voltages by replacing the 01sysctl file in your devices /system/etc/init.d folder.
a) Blackout-01sysctl-RTS.zip
This file will return your device to its default processor speed (1024MHz) and voltages.
b) Blackout-UV806-1025vdd.zip
This is a small tweak I made which adjusts the vdd level of the 806 MHz from 1050 vdd to 1025 vdd. By default the ROM uses 1050 vvd for both the 1024 MHz and 806 MHz speeds. If the phone is stable at 1024 MHz @ 1050 vdd, it should be stable at 806 MHz @ 1025 vdd.
c) Blackout-1200MHz.zip
Changes maximum processor frequency to 1.2 GHz.
Adjust vdd level of 806 MHz to 1025 vdd.
d) Blackout-1200MHz-1100vdd.zip
e) Blackout-1200MHz-1125vdd.zip
f) Blackout-1200MHz-1150vdd.zip
Changes maximum processor frequency to 1.2 GHz.
Adjust vdd level of 1200 MHz to 1100vdd, 1125 vdd or 1150 vdd as indicated in the name of the zip file (from ROM default 1175 vdd)
Adjust vdd level of 806 MHz to 1025 vdd (ffrom ROM default 1050vdd).
I provided three zips to allow you to optimize you device. The lowest vdd setting where your device is stable would be the most favorable.
g) Blackout-1401MHz.zip
Changes maximum processor frequency to 1.4 GHz.
Adjust vdd level of 806 MHz to 1025 vdd.
h) Blackout-1401MHz-1200vdd.zip
Changes maximum processor frequency to 1.4 GHz.
Adjust vdd level of 1401 MHz to 1200 vdd (from the ROM default of 1250vdd).
Adjust vdd level of 1200 MHz to 1100 vdd (from the ROM default of 1175vdd).
Adjust vdd level of 806 MHz to 1025 vdd.
i) Blackout-1401MHz-1225vdd.zip
Changes maximum processor frequency to 1.4 GHz.
Adjust vdd level of 1401 MHz to 1225 vdd (from the ROM default of 1250vdd).
Adjust vdd level of 1200 MHz to 1150 vdd (from the ROM default of 1175vdd).
Adjust vdd level of 806 MHz to 1025 vdd.
j) Blackout-1497MHz.zip
Changes maximum processor frequency to 1.5 GHz.
Adjust vdd level of 806 MHz to 1025 vdd.
k) Blackout-1497MHz-UV.zip
Changes maximum processor frequency to 1.5 GHz.
Adjust vdd level of 1401 MHz to 1200 vdd (from the ROM default of 1250vdd).
Adjust vdd level of 1200 MHz to 1100 vdd (from the ROM default of 1175vdd).
Adjust vdd level of 806 MHz to 1025 vdd.
l) Blackout-1497MHz-UV2.zip
Changes maximum processor frequency to 1.5 GHz.
Adjust vdd level of 1401 MHz to 1225 vdd (from the ROM default of 1250vdd).
Adjust vdd level of 1200 MHz to 1125 vdd (from the ROM default of 1175vdd).
Adjust vdd level of 806 MHz to 1025 vdd.
DISCLAIMER AND AGREEMENT
THESE FILES ARE FOR V3.2.0 ONLY.IF YOU USE THESE FILES, YOU DO SO AT YOUR OWN RISK.
How to install
1. Copy the .zip file to the root of your SDCard.
2. Reboot into recovery.
3. Flash the .zip
4. Reboot.
Like my work?
If you like my work, and want to make a donation, go to thread of the ROM you are using and Donate to the ROM developer instead.
Credits:
I learned to edit init.d system files thanks to LeeDroid's tutorials.
I learned to make flashable zips studying mike1986's flashable zips for ARHD.
Killersloth for inspiration and advice.
Governor Tweaks for Blackout ICS
There files are designed to be used together with the Frequency and Voltage Tweaks above
Blackout iCS uses the smartassV2 governor by default. These files fine tune governor performance.
General info on smartassV2:
SmartassV2 "has an 'ideal' frequency which it will quickly ramp up to, then more slowly ramp up once past it, and vice-versa for down-ramping. A separate "ideal" frequency is used when the screen is off." (Source)
Smartass tracks the state of the screen, and when screen is off (a.k.a sleep or suspended in the terms of this governor) a different ideal frequency is used. This is the only difference between the screen on and screen off states. Proper tuning of the awake_ideal_freq and sleep_ideal_freq should allow both high responsiveness when screen is on and utilizing the low frequency range when load is low, especially when screen is off (Source).
Click to expand...
Click to collapse
"C3" - CONSERVATIVE TWEAKS FOR THE SMARTASSV2 GOVERNOR TWEAKS FOR BLACKOUT ICS INCREDIBLE V3.2.0
a) Blackout-smartassV2-C3.zip (attached below)
What will this file do:
Adjust max_cpu_load from 55 (default for this ROM) to 85. This means the cpu will ramp up slower.
Adjust ramp_up_step from 200000 (default for this ROM) to 100000. This means the cpu will ramp up slower.
Adjust min_cpu_load from 25 (default for this ROM) to 35. This means the cpu will ramp down a bit faster.
Adjust down_rate_us from 99000 to 49000. This means the cpu will ramp down faster.
These settings are more conservative than default ROM smartassV2 settings and should result in longer battery life.
"P1" - PERFORMANCE TWEAKS FOR THE SMARTASSV2 GOVERNOR TWEAKS FOR BLACKOUT ICS INCREDIBLE V3.2.0
b) Blackout-smartassV2-P1.zip
What will this file do:
Adjust max_cpu_load from 55 (default for this ROM) to 60. To minimize unnecessary ramp up/down loops between 384 MHz and 768 MHz.
Adjust ideal sleep frequency from 200 MHz to 368 MHz. Intended to make sleep and wake transitions smoother.
"P2" - PERFORMANCE TWEAKS FOR THE SMARTASSV2 GOVERNOR TWEAKS FOR BLACKOUT ICS INCREDIBLE V3.2.0
c) Blackout-smartassV2-P2.zip
Adjust ideal wake frequency from 800 MHz to 1024 MHz.
Adjust ideal sleep frequency from 200 MHz to 368 MHz.
Adjust max_cpu_load from 55 (default for this ROM) to 60.
How to return to stock?
Flash Blackout-02governor-RTS.zip
DISCLAIMER AND AGREEMENT
THESE FILES ARE FOR V3.2.0 ONLY.IF YOU USE THESE FILES, YOU DO SO AT YOUR OWN RISK.
How to install
1. Copy the .zip file to the root of your SDCard.
2. Reboot into recovery.
3. Flash the .zip
4. Reboot.
Voltage Tweaks for aospX 1.0.0-MR1
Voltage Tweaks for aospX 1.0.0-MR1
I made a flashable voltage tweaks for aospX 1.0.0-MR1
What will the aospX-vos1.zip file do:
Adjust the vdd level of the 269 MHz from 925 vdd to 900 vdd.
Adjust the vdd level of the 346 MHz from 950 vdd to 925 vdd.
Adjust the vdd level of the 1037 MHz from 1075 vdd to 1050 vdd.
The lower voltages should result in marginally longer battery life.
DISCLAIMER AND AGREEMENT
THIS FILE WAS TESTED ON aospX 1.0.0-MR1 ONLY. . IF YOU USE THIS FILE, YOU DO SO AT YOUR OWN RISK.
I CANNOT GUARANTEE THAT YOU DEVICE WILL BE STABLE AT THE LOWER VOLTAGES, BUT IF YOU CAME FROM ARHD OR VIRTUOUS AFFINITY, THE LOWER VOLTAGE ARE SIMILAR TO THE RANGES YOU FIND IN THOSE ROM's.
STILL, GIVEN THAT I AM THE ONLY BETA TESTER, A SAMPLE OF ONE IS NOT VERY BIG
How to install
1. Copy the .zip file to the root of your SDCard.
2. Reboot into recovery.
3. Flash the .zip
4. Reboot.
How to return to stock - aospX-01sysctl-RTS.zip (Return to Stock)
Want to go back to stock. Just flash the aospX-01sysctl-RTS.zip below.
Like my work?
If you like my work, and want to make a donation, go to thread of the ROM you are using and Donate to the ROM developer instead.
Credits:
I learned to edit system files thanks to LeeDroid's tutorials.
I learned to make flashable zips studying mike1986's flashable zips for ARHD.
Killersloth for inspiration and advice.
Performance smartassV2 Governor for ViperDHD - "P1" - NO FURTHER DEVELOPMENT
ViperDHD 2.0 has moved to using Virtuous_oc, an excellent system for managing governors and frequencies. As such, it would seem to be more worthwhile getting a stable Deamon controller working than using init.d scripts. Hence, no releases of these scripts for ViperDHD 2.0 will be made.
I made a set of flashable governor tweaks for ViperDHD v1.2.3
ViperDHD uses the ondemand governor by default. The flashable zips attached below will enable the smartassV2 governor and tweak some settings.
"P1" - PERFORMANCE ORIENTED SMARTASSV2 GOVERNOR TWEAKS FOR VIPERDHD 1.2.x
a) ViperDHD-smartassV2-1_GHZ-p1.zip (attached below)
What will this file do:
Enable smartassV2 as your governor at the default 1024 MHz frequency
Adjust max_cpu_load from 55 (default for this ROM) to 60. To minimize unnecessary ramp up/down loops between 384 MHz and 768 MHz.
Adjust ideal sleep frequency from 200 MHz to 368 MHz. Intended to make sleep and wake transitions smoother.
Adjust the vdd level of the 806 MHz from 1050 vdd to 1025 vdd. By default the ROM uses 1050 vvd for both the 1024 MHz and 806 MHz speeds. If the phone is stable at 1024 MHz @ 1050 vdd, it should be stable at 806 MHz @ 1025 vdd.
b) ViperDHD-smartassV2-1_2GHZ-p1.zip (attached below)
Enable smartassV2 as your governor.
Set default max frequency to 1.2 GHz.
Adjust ideal wake frequency from 800 MHz to 1024 MHz.
Adjust ideal sleep frequency from 200 MHz to 368 MHz.
Adjust max_cpu_load from 55 (default for this ROM) to 60.
Adjust the vdd level of the 806 MHz from 1050 vdd to 1025 vdd.
c) ViperDHD-smartassV2-1_2GHZ-badass.zip (attached below) ---> This is the one I am using :laugh:
Enable smartassV2 as your governor.
Set default max frequency to 1.2 GHz.
Adjust ideal wake frequency from 800 MHz to 1024 MHz.
Adjust ideal sleep frequency from 200 MHz to 368 MHz.
Adjust max_cpu_load from 55 (default for this ROM) to 60.
Adjust the vdd level of the 806 MHz from 1050 vdd to 1025 vdd.
[*]Adjust the vdd level of the 1200 MHz from 1175 vdd to 1100 vdd.
d) ViperDHD-smartassV2-1_2GHZ-p2-deadline.zip (attached below)
Made at the request of Pop Tarantula
Same as ViperDHD-smartassV2-1_2GHZ-badass.zip
Plus scheduler set to "Deadline"
e) ViperDHD-smartassV2-1_4GHZ-p1.zip and ViperDHD-smartassV2-1_4GHZ-p1.zip(attached below)
Enable smartassV2 as your governor.
Set default max frequency to 1.4 GHz or 1.5 GHZ.
Adjust ideal wake frequency from 800 MHz to 1024 MHz.
Adjust ideal sleep frequency from 200 MHz to 368 MHz.
Adjust max_cpu_load from 55 (default for this ROM) to 60.
Adjust the vdd level of the 806 MHz from 1050 vdd to 1025 vdd.
f) ViperDHD-smartassV2-1_2GHZ-c3.zip(attached below) - At the request of chrisafpa27
Enable smartassV2 as your governor.
Set default max frequency to 1.2 GHz
Adjust the vdd level of the 806 MHz from 1050 vdd to 1025 vdd.
Adjust max_cpu_load from 55 (default for this ROM) to 85. This means the cpu will ramp up slower.
Adjust ramp_up_step from 200000 (default for this ROM) to 100000. This means the cpu will ramp up slower.
Adjust min_cpu_load from 25 (default for this ROM) to 35. This means the cpu will ramp down a bit faster.
Adjust down_rate_us from 99000 to 49000. This means the cpu will ramp down faster.
f) ViperDHD-smartassV2-1GHZ-c3.zip(attached below)
Enable smartassV2 as your governor.
Adjust the vdd level of the 806 MHz from 1050 vdd to 1025 vdd.
Adjust max_cpu_load to 85.
Adjust ramp_up_step to 100000.
Adjust min_cpu_load to 35.
Adjust down_rate_us to 49000.
How to return to stock?
Flash the ViperDHD_00kernel_modules-RTS.zip below and all traces of my work will be gone :crying:
DISCLAIMER AND AGREEMENT
THESE FILES ARE FOR VIPERDHD V1.1.0/1.2.0/1.2.1 ONLY. IF YOU USE THESE FILES, YOU DO SO AT YOUR OWN RISK.
How to install
1. Copy the .zip file to the root of your SDCard.
2. Reboot into recovery.
3. Flash the .zip
4. Reboot.
How to return to stock - ViperDHD_00kernel_modules-RTS.zip (Return to Stock)
Want to go back to stock. Just flash the BViperDHD_00kernel_modules-RTS.zip below. Flash this file and your back to the ondemand governor. This file does not enable the performance governor. It just restores the default /etc/init.d/00kernel_modules file.
Like my work?
If you like my work, and want to make a donation, go to thread of the ROM you are using and Donate to the ROM developer instead.
Credits:
I learned to edit init.d system files thanks to LeeDroid's tutorials.
I learned to make flashable zips studying mike1986's flashable zips for ARHD.
Killersloth for inspiration and advice.
Voltage Tweaks for JellyTime
Voltage Tweaks for JellyTime R28/R29/R30
I made a flashable voltage tweaks for JellyTime which I have tested on R28, R29 and R30. Compared to a HTC DHD stock ROM, JellyTime heavily undervolts the lower speeds (245-341 MHz) but runs the higher speeds at stock. I created these two scripts to correct this.
JellyTime-VOS-1.zip
JellyTime-VOS-2.zip
These files adjust the ROM's voltages as listed in the chart below:
Frequency > JT Stock > VOS-1 > VOS-2
245760: > 850
341640: > 900
614400: > 1000
768000: > 1050 > 1025 > 1025
806400: > 1100 > 1025 > 1050
1024000: > 1200 > 1050 > 1075
1200000: > 1200 > 1100 > 1150
1305600: > 1225 > 1150 > 1200
1401600: > 1250 > 1200
1516800: > 1300
1612800: > 1325
1689600: > 1375
1766400: > 1425
1843200: > 1450
1920000: > 1500
1996800: > 1500
2016000: > 1525
The lower voltages should result in longer battery life during load.
The JellyTime-VOS-1.zip are the best settings I could run on my phone and tested up to 1.4 GHZ, but I really on test extensively up to 1.2 GHz.
The JellyTime-VOS-2.zip contains less aggressive settings incase the first file is not stable. The voltage is at about the same level as you will find in other custom ROM's. Basically, if you have run ARHD, aospX, Blackout ICS, ViperDHD, or Virtuous Affinity/Infinity in the past, you should be able to run these settings comfortably.
DISCLAIMER AND AGREEMENT
THESE FILES WERE TESTED ON JELLYTIME R28 AND R29 ONLY. IF YOU USE THESE FILES, YOU DO SO AT YOUR OWN RISK.
I CANNOT GUARANTEE THAT YOU DEVICE WILL BE STABLE AT THE LOWER VOLTAGES.
How to install
1. Copy the .zip file to the root of your SDCard.
2. Reboot into recovery.
3. Flash the .zip
4. Reboot.
How to return to stock
Want to go back to stock. Just flash the JelltyTime-RTS-vdd.zip below.
Like my work?
If you like my work, and want to make a donation, go to thread of the ROM you are using and Donate to the ROM developer instead.
Credits:
I learned to edit system files thanks to LeeDroid's tutorials.
I learned to make flashable zips studying mike1986's flashable zips for ARHD.
Killersloth for inspiration and advice.
Voltage Tweaks for CyanogenMod 10.1
Voltage Tweaks for CyanogenMod 10.1
I made a flashable voltage tweaks for PipelinerArd's JJB-JOP40 (Unofficial CM 10.1). These files also are compatible with Mustaavalkosta's CM 10.1 Nightlies and M1 ROM's. I have not tried the other CM10.1 ROM's. Zeitraffer reports the files work with the CodefireX 4.2.1 ROM's. ai6908 reports that the files work with JellyTime 4.2 ROM's.
Compared to a HTC DHD stock ROM, JellyTime heavily undervolts the lower speeds (245-341 MHz) but runs the higher speeds at stock. I created these two scripts to lower voltages at the higher frequencies.
JB-JOP40-VOS1.zip
JB-JOP40-VOS2.zip
JB-JOP40-VOS3.zip
These files adjust the ROM's voltages as listed in the chart below:
Frequency > CM Stock > VOS-1 > VOS-2 > VOS-3
245760: > 850
341640: > 900
614400: > 1000
768000: > 1050 > 1025 > 1025 > 1025
806400: > 1100 > 1025 > 1050 > 1050
1024000: > 1200 > 1050 > 1075 > 1100
1200000: > 1200 > 1100 > 1150 > 1175
1305600: > 1225 > 1150 > 1200
1401600: > 1250 > 1200
1516800: > 1300
1612800: > 1325
1689600: > 1375
1766400: > 1425
1843200: > 1450
1920000: > 1500
1996800: > 1500
2016000: > 1525
The lower voltages should result in longer battery life during load.
DISCLAIMER AND AGREEMENT
IF YOU USE THESE FILES, YOU DO SO AT YOUR OWN RISK.
I CANNOT GUARANTEE THAT YOU DEVICE WILL BE STABLE AT THE LOWER VOLTAGES.
How to install
1. Copy the .zip file to the root of your SDCard.
2. Reboot into recovery.
3. Flash the .zip
4. Reboot.
How to return to stock
Want to go back to stock. Just flash the JB-JOP40-RTS-vdd.zip below.
Like my work?
If you like my work, and want to make a donation, go to thread of the ROM you are using and Donate to the ROM developer instead.
Credits:
I learned to edit system files thanks to LeeDroid's tutorials.
I learned to make flashable zips studying mike1986's flashable zips for ARHD.
Killersloth for inspiration and advice.
I would highly recommend these tweaks, I use them pretty much exclusively and it's way easier and cleaner than uaing an app from the market.
cstayton said:
I would highly recommend these tweaks, I use them pretty much exclusively and it's way easier and cleaner than uaing an app from the market.
Click to expand...
Click to collapse
Whoah, I was not expecting this.
Here are links to some of my older files
TrickDroid ROM (Discontinued)
These scripts were written with v3.0 in mind, and while are compatible with v.4, I was thinking they should be re-tweaked to account for the heavier system requirements of Sense 4.1. Only the last script, Performance Governor for TrickDroid v.4 was designed around the latest version, but I did not have time to test it long term. This ROM is not discontinued.
Original Governor Tweaks for the TrickDroid ROM (Posted Oct. 13 2012) - Tested with TrickDroid v3/Compatible with v4.
Version 3 Governor Tweaks for the TrickDroid ROM (Posted October 16, 2012) - Tested with TrickDroid v3/Compatible with v4.
Performance Governor for TrickDroid v.4 (Posted on October 21, 2012) - Zip works, I just have not tested the settings over an extended period of time.
Older link to Blackout governor tweaks.
Version 3 Governor Tweaks for Blackout ICS (Posted on October 16, 2012) - Tested with Blackout v3.1/Compatible with Blackout 3.0.
Click to expand...
Click to collapse
Hi Roberto. Would it be possible to have these tweaks also for XxXPachaXxX NERO XL Rom? Thank you
[email protected] said:
Hi Roberto. Would it be possible to have these tweaks also for XxXPachaXxX NERO XL Rom? Thank you
Click to expand...
Click to collapse
Should be. I flashed version 2 of the ROM. Can you use a file manager and go to:
a) /etc/init.d - List down the names of the files you see in the folder inside.
b) /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels - any chance you can copy and paste the contents, or just copy the, vdd_levels file and attached it to your reply
c) /sys/devices/system/cpu/cpu0/cpufreq/available_scaling_governors - any chance you can copy and paste the contents, or just copy, the available_scaling_governors file and attached it to your reply
IN ORDER TO UPLOAD THE FILES AS AN ATTACHMENT, YOU PROBABLY HAVE TO ZIP THEM.
This information should be enough so I can answer your question definitively
cstayton said:
I would highly recommend these tweaks, I use them pretty much exclusively and it's way easier and cleaner than uaing an app from the market.
Click to expand...
Click to collapse
+1 used for trickdroid really good . Nice work
Sent from my HTC Desire HD using xda premium with TrickDroid V4 Sense 4.1
Really a great post, i learned a lot just reading it.
thank you very much!
wilken said:
Really a great post, i learned a lot just reading it.
thank you very much!
Click to expand...
Click to collapse
Thanks.
@all
Now we will be moving on to fine tuning governors? Which governor interest you the most?
amazing job man
Q-what is the difference between the first post and the second post
i wish if i can learn what are u doing but i have bad english
Thank you Roberto! You're amazing! I think that I can learn a lot of things thanks to you
So thank you very much!! I just reverted back to gingerbread after trying several ICS roms with low battery life, but the next time I will be on ICS I promise that I will surely help you and test your fantastic tweaks (surely better than using setcpu or similar)
Responding to tour question; I think that smartassV2 is the best governor and your edits that cause the cpu to ramp up slower and to ramp down faster should make it even better! But what does it mean exactly fine tuning governors?? Sorry for my ignorance
IMTLD said:
amazing job man
Q-what is the difference between the first post and the second post
i wish if i can learn what are u doing but i have bad english
Click to expand...
Click to collapse
No problem. No one should apologize for bad English. It's just a language equal to any other. Could also be bad writing.
The files on the festival post try to keep the processor running more on the lower speeds.
The files on the second post will keep the processor running faster.
Sent from my HTC Desire HD powered by Blackout ICS Incredible v3.1.1
[email protected] said:
But what does it mean exactly fine tuning governors?? Sorry for my ignorance
Click to expand...
Click to collapse
Basically with an app, and depending on the ROM you can adjust:
1. CPU speed
2. Governor type
3. Some will allow you to adjust voltages
With the scripts you can also adjust:
4. When the processor will go faster or slower.
5. How much the processor will speed up and speed down.
6. A few others but 5 and 6 are the most important.
I guess we start with ondemand. Than differentiate it from smartassV2.
Sent from my HTC Desire HD powered by Blackout ICS Incredible v3.1.1
Roberto_Lim said:
No problem. No one should apologize for bad English. It's just a language equal to any other. Could also be bad writing.
The files on the festival post try to keep the processor running more on the lower speeds.
The files on the second post will keep the processor running faster.
Sent from my HTC Desire HD powered by Blackout ICS Incredible v3.1.1
Click to expand...
Click to collapse
thank u man
Roberto_Lim said:
Basically with an app, and depending on the ROM you can adjust:
1. CPU speed
2. Governor type
3. Some will allow you to adjust voltages
With the scripts you can also adjust:
4. When the processor will go faster or slower.
5. How much the processor will speed up and speed down.
6. A few others but 5 and 6 are the most important.
I guess we start with ondemand. Than differentiate it from smartassV2.
Sent from my HTC Desire HD powered by Blackout ICS Incredible v3.1.1
Click to expand...
Click to collapse
So the fine tuning governor means adding also scripts to what you did in the forst post?
In that case, why don't you start directly with smartassV2? It has a better battery life than ondemand
CodefireX
Hello. Create tweaks for CodeFireX, it will be interesting.
[KERNEL] [Jan 28] [Sense][GPE] Hypernova_2.0.3-Mallow && Flar-Port_6.03.3-Mallow
{
"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"
}
HTC One M8_WL Sense Kernel
(All Variants)
This kernel has been
MassStashed
Kernel Features
FEATURES - FlarPort
Latest Pre-Release optimized -O3 linaro 4.9.3 toolchain
Easy installation with Aroma installer - Special thanks to flar2
overclocking
gboost for enhanced gaming performance
choose voltage profile in installer
full user voltage control
underclock CPU or GPU
i/o schedulers: FIOPS, SIO, CFQ, NOOP, ROW, deadline
optional sweep2sleep
Optional custom wake gestures (no motion required!)
Optional pocket detection (with custom wake gestures)
Option to disable volume button wakes camera (with custom wake gestures)
High Definition Audio capability
Optional USB fastcharge
Option to reduce vibration strength
Remove /system write protection
NTFS r/w, CIFS, exFAT support
Option to disable fsync
Option to disable magnetic cover
/dev/frandom support
Color control
DriveDroid support
Stereo call recording
Unified dtb's to make work with all variants (Thanks captain_throwback)
Kernel Features
FEATURES - Hypernova
Latest Pre-Release optimized -O3 linaro 4.9.3 toolchain
Everything from flar2's amazing kernel (Gboost removed in favor of interactive and hotplug cpu control. Not necessary with this setup)
Franco's mako_hotplug
*cpu-boost* (Removed currently)
Franco's enhanced interactive governor set to default (Tweaked settings thanks to Dan)
NTFS support
Many other enhancements not normally added to sense kernels that I've seen
F2FS
INSTALLATION
1. Install zip from recovery
2. Follow the instructions, if you don't know what to do, use the pre-selected options
3. Wipe cache/dalvik cache
4. Reboot
It is recommended to disable or increase the screen timeout in TWRP recovery. If the screen timeout is enabled in TWRP, there may be a black screen after exiting the Aroma installer. This is nothing to worry about. Simply hold power and volume down and volume up buttons until it reboots. The installation will be fine. If things get stuck in aroma, simply do this reboot method and immediately hold down to get to bootloader mode, then select recovery and start from the beginning.
Donate to franciscofranco!
A lot of this is thanks to franciscofranco’s commits, so donate to him!
Donate to Flar2!
A lot of this is thanks to flar2’s commits, so donate to him!
Here’s mine if you would like to donate to me specifically
DOWNLOADS
Sense 5.0.1 & 5.0.2
GPE 6.0
NOTES AND OTHER IMPORTANT STUFF YOU SHOULD KNOW!!!
ElementalX Configuration File
Your choices in the Aroma installer are used to build a configuration file. The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
If settings are not sticking:[*]Make sure you have busybox installed correctly and updated to the latest version[*]Make sure the file permissions for /etc/init.d/99elementalx or 99msx are set to execute.[*]Check to see if any /etc/init.d scripts or apps (such as Kernel Tuner or TricksterMod) are interfering with your settings.
ElementalX Log File
Every boot, a log file is created at /data/local/tmp/elementalx-kernel.log or msx-kernel.log. This file shows the date and time and all settings that have been applied. Use this to verify and troubleshoot configuration options. Also, in this file is your devices PVS number. Please refer to the links down below as to what the heck the PVS means. Helps with troubleshooting OC/voltage related reboots device specific. Not all devices were created equal!
Overclocking
Overclocking is optional. The installer lets you choose the maximum frequency. Whatever frequencies you chose in the installer will be set at boot for each CPU. Not all devices can handle overclocking. I don't recommend overclocking, this device is fast enough. If you overclock, the CPU frequency will likely be throttled due to heat. I recommend the stock frequencies, as this device is plenty fast.
CPU voltages
The installer allows you to choose from several undervolting options: stock, -15mV, -30mV, or -45mV. This only undervolts the lowest frequency, which happens to be the frequency used the most, and this is safer. Be careful, lowering voltages can cause instability.
gboost
gboost enhances gaming performance by giving a slight boost to cpu frequencies when the graphics load is high (e.g. while gaming). It should have no effect on battery life during regular usage, so it's safe to leave it enabled all the time.
fsync
fsync can be disabled if you're looking for the last ounce of performance. I recommend leaving it enabled as there is a slight risk of data loss if your phone shuts off unexpectedly before filesystems are synced.
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.
Sweep2sleep
Sweep2sleep allows you to put your device to sleep by swiping right to left across the bottom of the screen where the back, home, recent buttons are. I find this useful since the stock motion gestures do not provide a good way to turn off the screen.
/sys/android_touch/sweep2wake
0= disabled
1= sweep2sleep right enabled
2= sweep2sleep left enabled
3= sweep2sleep left and right enabled
USB fastcharge
USB fastcharge is optional. This will allow you to charge at a faster rate when connected to a USB port. The default limit for USB ports is 500ma, this increases it to 1100ma. Be sure that the computer/laptop/whatever you are plugged into can handle it. Some will automatically cap it at 500ma. Please note that this does not force AC charge mode like previous implementations of force fastcharge. Your battery setting will still say USB mode. You can edit /etc/elementalx.conf to change the setting on boot.
Wake Gestures
There are three modes
Mode 1: Stock Motion Launch Gestures
For stock motion launch gestures, /sys/android_touch/wake_gestures, /sys/android_touch/sweep2wake and /sys/android_touch/doubletap2wake must all be set to 0. Enabling any of these overrides the stock gestures. Obviously Motion Launch Gestures must be enabled in the system settings.
Mode 2: Remove motion requirement
For this, you must set /sys/android_touch/wake_gestures to 1 and enable at least one gesture in /sys/android_touch/sweep2wake or /sys/android_touch/doubletap2wake and Motion Launch Gestures must be enabled in system settings. In this mode, when you sweep or doubletap, the appropriate input events are generated and acted upon the EasyAccessService (i.e., the system app that handles gesture actions).
Mode 3: Traditional S2W/DT2W
In this mode, wake gestures and actions are handled entirely by the kernel. The gestures will turn on the screen and that's it. For this, you must set /sys/android_touch/wake_gestures to 0 and enable at least one gesture in /sys/android_touch/sweep2wake or /sys/android_touch/doubletap2wake. It doesn't matter if Motion Launch Gestures is enabled or disabled in system settings, the gestures don't interact with it in this mode.
Options
For modes 2 and 3, there are several options.
Sweep2Wake
Gesture........Value
Sweep right......1
Sweep left........2
Sweep up.........4
Sweep down.....8
Add up the values for each gesture you want to enable and put the total in /sys/android_touch/sweep2wake. For example, to enable all gestures, the value is 15 (1+2+4+8). To enable sweep right, sweep left and sweep up, the value is 7 (1+2+4)
DoubleTap2wake
Set /sys/android_touch/doubletap2wake to 1 to enable DT2W, and set to 0 to disable it.
Pocket Detection
Set /sys/android_touch/pocket_detect to 1 to enable pocket detection, and set to 0 to disable it. Pocket detection is experimental right now, I'd say it's about 90% functional, but there is an occasional bug where it either doesn't work or works too well.
Vibration Strength
Haptic feedback can be enabled for the wake gestures in /sys/android_touch/vib_strength. This setting takes a number between 0 and 60. Default is 20, which is the same vibration as the stock gestures. Setting this to 0 disables haptic feedback.
SOURCE
https://github.com/MassStash
https://github.com/flar2
https://github.com/franciscofranco
..........................................................................................
XDA: DevDB Information
MassStashed-m8whl, Kernel for the HTC One (M8WHL)
Contributors
franciscofranco
flar2
Evolutionmods
MassStash
Version Information for FlarPort
Status: Solid as ****
Current Stable Version: 6.03.3 & 4.04 & 3.04
Stable Release Date: 01-28-2016
Version Information for Hypernova (mako_hotplug)
Status: Solid as ****
Current Stable Version: 2.0.3
Stable Release Date: 01-28-2016
Created 06-20-2014
Last Updated 01-28-2016
Zee Changelog
CHANGELOG (Cliff-Notes) Here's a GDoc for Latest
If this is first time flashing these updated packaged kernels, please dirty or full wipe flash the rom you’re on, let it boot to system, then reboot to twrp and flash one of these kernels. Also recommneded to flash ROM’s boot.img or just dirty flash if switching between these kernels.
Feb 27, 2015 - Lollipop
All compiled with latest linaro 4.9.3 prerelease toolchain and are all also packaged with anykernel method to allow for zImage and dt.img injection into rom’s stock boot.img, thus keeping ramdisk with any specific optimizations made for that exact rom. Also anykernel script now used to inject kernel settings script, formerly referred to as init script, into ramdisk to be loaded without need for init.d, and thus no need for setting selinux to permissive (Thanks Flar2).
May 30, 2015
Hypernova 1.5.1
GPE 5.1 & Sense 5.0.2
Add f2fs support …
Add support for M8TL
arm: crypto: Add optimized SHA-256/224 …
fs/namei.c: fix potential memory leak in path_lookupat …
sched/nohz: Fix rq->cpu_load[] calculations …
sched/fair: Let minimally loaded cpu balance the group …
input: touchboost: conservative samples every 10ms, no point in limit… …
ASoC: msm: Correct RTAC mutex lock …
cpuidle: remove cross-cpu IPI by new latency request. …
cpufreq: Break out early if freq equals to target_freq …
cpufreq: conservative: don't tear up sysfs and governor dirs to preve…
cpufreq: conservative: make the code a little bit prettier …
cpufreq: conservative: add input_boost_freq and input_boost_duration …
cpufreq: conservative: how did this end up here?
cpufreq: conservative: add sane input_boost and duration values …
cpufreq: conservative: notify the policy of the current load …
cpufreq: conservative: add micro idle accounting and touch boost support …
Update lz4 …
msm: slimbus: use interruptible wait to reduce system's load average …
ASoC: msm: audio-effects: Check for array index …
ARM: arch_timer: add support to configure and enable event stream …
ARM/ARM64: arch_timer: add macros for bits in control register …
tick: don't update idle time if cpu offline …
mako_hotplug: don't use PAGE_SIZE for snprintf …
mako_hotplug: don't offline cores if the load at that sample is above… …
arm: msm8974: enable Motorola's enhanced memory routines …
Update to dev branch of lz4 …
Update to vzw lolli dts …
Update dts for m8 to 5.0.1. DUG and WL still 4.4.4. …
Flar-Port
GPE - 3.04
Flar’s ElementalX updates
Sense - 4.04
All previously commits in changelog ported to new 5.0.1 base
selinux: Report permissive mode in avc: denied messages
KCAL update
Hypernova
GPE - 1.4.3
Based on flar2’s GPE
Added all commit’s from sense hypernova to date (see directly below)
Sense - 1.4.3
All 5.0.1 updates from elementalx
SoC: msm: Add Buffer overflow check
KEYS: close race between key lookup and freeing
msm: pm: Notify secure code of L2 power mode from last core only
sched: Implement smarter wake-affine logic
Fix nr_exclusive tasks which lead to ... Avoid spurious wakeup IPIs
sched: Fix inaccurate accounting for real-time task
arm: lib: Fix makefile bug
msm: memutils: memcpy, memmove, copy_page optimization
selinux: conditionally reschedule in hashtab_insert while loading sel…
selinux: conditionally reschedule in mls_convert_context while loadin…
selinux: no recursive read_lock of policy_rwlock in security_genfs_sid()
selinux: fix a possible memory leak in cond_read_node()
selinux: simple cleanup for cond_read_node()
selinux: fix inode security list corruption
qseecom: Save appname in qseecom when loading app by kernel client
arm: arch_timer: add arch_counter_set_user_access
mako_hotplug: remove screen off frequency cap and other optimizations
sched, smp: Correctly deal with nested sleeps
smpboot: Add missing get_online_cpus() … in sysfs
cpufreq: let's remove cpu-boost for now
input: add a generic touch input notifier
EXPERIMENTAL: mako_hotplug: make cpu2 and cpu3 less nervous
Dec 17, 2014
Added some awesome updates to hotplug and interactive from franco
Dec 15, 2014
All compiled with latest linaro 4.9.3 prerelease toolchain and are all also packaged with anykernel method to allow for zImage and dt.img injection into rom’s stock boot.img, thus keeping ramdisk with any specific optimizations made for that exact rom.
Flar-Port
GPE
Add all variant dtb’s from capt
Add NTFS
Sense
Added high perf audio and set to default on
Add all variant dtb’s from capt
NTFS support
Couple lz4 compression updates
Hypernova
GPE
Based on flar2’s GPE
Added all commit’s from sense hypernova to date (see directly below)
Sense
Couple updates to mako_hotplug, cpu-boost, and interactive governor
Couple lz4 compression updates
Enhance power efficiency patches
Fix bad hashing of dentries
Add support to validate pixel extension calculations
New relation for freq selection
Nov 17, 2014
Flar-Port
Port all commit’s from flar2’s 4.4.4 ElementalX kernel to make new 4.4.4 MassStashed Flar Port
Hypernova
Started with 4.4.4 Flar Port and then ported all commit’s I got from Franco’s One Plus One kernel to new 4.4.4 Hypernova kernel.
Added prima wlan module to compile with kernel from lypota, from htc source
Updates to wlan module
Updates to mako_hotplug
Added unified DTB from captain_throwback for vzw and gsm/intl support build in one zImage. Still need proper zip because I chose to use repack each with their specific ramdisk as opposed to using anyernel for now. Will look into anykernel at a later date for a one zip for all solution. Thank you captain for introducing me to anykernel method.
Added NTFS support
Oct 10, 2014
Enable compatibility with all M8 variants
wcd9320: Enable class AB mode, AKA high perf audio headset mode, be d…
high perf audio - fixed m8 incompatible
sound high perf - clean code
Update defconfig with version number
added high perfomance sound
wake_gestures: re-enable proximity sensor after phone call end and sc…
backlight_dimmer: give two dimmer options and create sysfs node
Revert "i2c: reduce remaining clocks"
i2c: reduce remaining clocks
Revert "Add backlight dimmer option"
Sep 15, 2014
Update aroma for brightness compatibility
Sep 14, 2014
Add backlight dimmer option
Sound Control: add line gain to cached and register lock …
Sep 12, 2014
kexec-hardboot: based on @Tasssadar
msm-sleeper: add ex_max_freq interface
Bump scripts for building with 2014.08 linaro 4.9.2
Aug 26, 2014
msm: Fix high load average from uninterruptible waits
GPU: start at 200MHz instead of 320MHz
Net/l2tp: don't fall back on UDP [get|set]sockopt
Update defconfig
MHL adapter fix from HTC
Charger updates from HTC
Aug 10, 2014
Update to Venom Int Ramdisk for packaging kernels to not break root and init.d on int based ROM
Aug 01, 2014
Update Stockish to 4.4.3 source
Update FlarPort to latest 1.0.0 ElementalX 4.4.3 | Most everything from 4.4.2 has been brought over
Jun 24, 2014
Fix touch in aroma installer - Gigantic thanks to badseed team for the fixed binary, and capt for bringing this to my attention
Jun 21, 2014 - MassStashedX_v0.19.1
Fix implicit declaration of function ‘wait_for_completion_io_timeout’… …
Switch baconMaker to elementalx_defconfig
Jun 20, 2014
Revert "cpuidle: Quickly notice prediction failure in general case" …
Revert "cpuidle: Get typical recent sleep interval" …
Revert "cpuidle: Fix finding state with min power_usage" …
Revert "cpuidle: remove the power_specified field in the driver" …
media-device: fix infoleak in ioctl media_enum_entities() …
futex: Make lookup_pi_state more robust …
futex: Always cleanup owner tid in unlock_pi …
futex: Validate atomic acquisition in futex_lock_pi_atomic() …
futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == u… …
futex: Add another early deadlock detection check …
futex: Prevent attaching to kernel threads …
Update cwmcusensor
Wake Gestures: fix dot view mode
stereo call recording support …
msm: kgsl: Fix nice level for higher priority GPU start thread …
arm: lz4: faster boot-up process. …
lz4: fix compression/decompression signedness mismatch …
lib/lz4: correct the LZ4 license …
crypto: add lz4 Cryptographic API …
lib: add lz4 compressor module …
arm: add support for LZ4-compressed kernel …
lib: add support for LZ4-compressed kernel …
decompressor: add LZ4 decompressor module …
DRIVERS: SLIMBUS: some more tweaks, which is double what we had befor… …
Wake Gestures: add proximity enabled flag
Wake Gestures: debugging messages
Wake Gestures: increase boot delay, add timeout to sweeps, fix irq en… …
Wake Gestures: add boot time delay for proper initialization of sensors
Wake Gestures: option to disable volume buttons launch camera in land… …
Jun 20, 2014
Wake Gestures: fix typo
Wake Gestures: more fixes for pocket detection, mcu initialization an… …
Wake Gestures: fix custom gestures in dot view mode
Wake Gestures: various improvements and fixes
DRIVERS: SLIMBUS: slimbus enhancements mkII …
Wake Gestures: Allow customization of the screen wake gestures on HTC… …
Downgrade CIFS …
GCC 4.9.1: fix compile warnings
GCC 4.9: fix compile warning …
cpufreq: interactive: fix compiling warnings …
Adjust some voltages
Set up underclocking and overclocking
Disable magnetic cover event
Change auto undervolting to use min freq only and adjust oc voltages …
Adjust min and max voltage limits …
msm: clock-krait-8974: User voltage control for msm-cpufreq device …
Add gboost
Bump overclocking voltages a bit
[qpnp-vibrator] sysfs interface from GPE source
Sound Control 3.x: adaptation for HTC One (M8) …
sound control: add register cache …
Sound Control: (OPTIONAL) add power amp registers access control as well …
Sound Control: (Optional) work around for Nexus 4/5 audio issues …
sound control: WCD9320: update speaker gain control for Z1 …
Jun 20, 2014
sound control 3.x: Initial GPL release for WCD9320 Audio Codec …
Sound Control: WCD9320: expose additional controls …
Add option to lower vibration
Overclocking: fix and add more steps
msm: cpufreq: Add API to allow limiting of min and max cpu frequencies …
msm-sleeper: limit max freq when screen is off
Show pvs in sysfs
Revert "sched: Micro-optimize the smart wake-affine logic" …
Revert "sync: don't block the flusher thread waiting on IO" …
Revert "FS: import F2FS" …
Revert "exFAT support" …
Revert "sched: add wait_for_completion_io[_timeout]" …
Revert "block: account iowait time when waiting for completion of IO … …
Disable HTC /system write protection …
Overclocking and undervolting options
Jun 10, 2014
Fastcharge for HTC One m8
LCD_KCAL Colour Control for m8
SELinux: Fix memory leak upon loading policy …
Jun 10, 2014
block: account iowait time when waiting for completion of IO request …
sched: add wait_for_completion_io[_timeout] …
deadline: Allow 0ms deadline latency, increase the read speed …
exFAT support …
Add fsync option
Add sweep2sleep …
FS: import F2FS …
ARM CPU Topology and cpu_power driver …
softirq: reduce latencies …
nohz: Reduce overhead under high-freq idling patterns …
ext4: fix memory leak in xattr …
cpuidle: Get typical recent sleep interval …
cpuidle: Quickly notice prediction failure in general case …
cpuidle: Quickly notice prediction failure for repeat mode …
cpuidle: move field disable from per-driver to per-cpu …
AIO: Don't plug the I/O queue in do_io_submit() …
Add SIO and FIOPS i/o schedulers …
Jun 09, 2014
warning: argument to 'sizeof' in 'memcpy' call is the same pointer ty… …
Add built crap and touch on cook script
warning: operation on 'ret' may be undefined [-Wsequence-point] …
dtb: binary to bring out dt.img …
Add cook my bacon script
Double flip a switch + setup ignores
May 08, 2014
initial switch flip
Great info to actually read and know!
Hypernova version has all kinds of stuff that's been added from the good @franciscofranco, and the most important and amazing, IMHO, is the mako_hotplug_driver. With this, we have eliminated most governors, and now exclusively run interactive. We now also have some extra options with this interactive governor that we can set to customize the user experience smoothness, and battery life. Down below is how to work init.d scripts, which is suggested as a great set it and forget it method, but if you are trying to mess with things quickly and in user land with an app, you will have to use francos. Unfortunately, our phone is only supported by the paid version also, so looks like it's time to open the wallets and show your appreciation! Bought this personally as soon as I got the hotplug up and running. 100% worth it.
Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
Here's some info on the pieces used from his kernel, and the app, and the guy himself it seems.
Code:
Information about the kernel
People generally change kernels for battery savings and to add features the stock one doesn't offer.
Franco's kernel has several advantages over the stock one in terms of battery saving saving features,
one of my favourite being the removal of MPdecision which in lay-mans terms changes the min and
maximum speed the CPU can run at based upon live battery temperature checks. Franco's hot plug
driver always keeps 2 cores online and always them to scale from 300mhz to 2.3ghz and based upon
load conditions will online cores 3 and 4 if required. When you touch the screen the screen the CPU
speed is boosted to approximately 1.5ghz for just over a quarter of a second and when load is reduced
the CPU speed is able to lower quickly back to lower speeds thanks to his tuned interactive
governor. Franco has created a governor for the GPU named interactive which works very much like
how the CPU equivilant does. Franco has added some newer drivers for WiFi which also helps reduce
idle battery drain while your on a busy WiFi network. Franco has also added an interface where you
can boost microphone, speaker and headphone gain levels for audio enthusiasts as well as an
interface to allow screen calibration and load pre set profiles to improve your experience with how
your display looks! There's clock speed control, voltage control, governor control, hot plug control.
You get the idea its full of cool features which can be controlled with the paid Franco.Kernel
Application (see later in the thread)
[img]http://img.tapatalk.com/d/14/02/23/5y7egebu.jpg[/img]
Here are some lines I've found around the interwebs as a reference for myself for some time now. All of this is set, but hey, it never hurts to learn how it all works behind the scenes.
This is not a shell script, and cannot be run as one as-is; it's just a bunch of commands. UV should never be set with init.d in case they are unstable.
These are old values, some may be good, some may not. Please ask, or do some research on what is suggested for current cpu and phones.
Code:
# CPU Clock
echo 1228800 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 537600 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
# UV
echo "1450 1425 1400 1375 1350 1250 1225 1200 1050 900 850 800" > /sys/class/misc/customvoltage/mpu_voltages
echo "1375 1291 1140 950" > /sys/class/misc/customvoltage/iva_voltages
echo "1150 1050 950" > /sys/class/misc/customvoltage/core_voltages
# SR
echo 1 > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
echo 1 > /sys/kernel/debug/smartreflex/sr_iva/autocomp
echo 1 > /sys/kernel/debug/smartreflex/sr_core/autocomp # CORE no longer SR calibrated on FK
# Governor
echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 15000 > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/boost
echo 80000 > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
echo 95 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo 729600 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo 45000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 15000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo 80000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
# I/O Scheduler
echo 1024 > /sys/block/mmcblk0/queue/read_ahead_kb
echo "deadline" > /sys/block/mmcblk0/queue/scheduler
echo 500 > /sys/block/mmcblk0/queue/iosched/read_expire
echo 5000 > /sys/block/mmcblk0/queue/iosched/write_expire
echo 4 > /sys/block/mmcblk0/queue/iosched/writes_starved
echo 0 > /sys/block/mmcblk0/queue/iosched/front_merges
echo 1 > /sys/block/mmcblk0/queue/iosched/fifo_batch
echo "row" > /sys/block/mmcblk0/queue/scheduler
echo 100 > /sys/block/mmcblk0/queue/iosched/hp_read_quantum
echo 100 > /sys/block/mmcblk0/queue/iosched/rp_read_quantum
echo 1 > /sys/block/mmcblk0/queue/iosched/lp_read_quantum
echo 2 > /sys/block/mmcblk0/queue/iosched/hp_swrite_quantum
echo 1 > /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum
echo 1 > /sys/block/mmcblk0/queue/iosched/rp_swrite_quantum
echo 1 > /sys/block/mmcblk0/queue/iosched/rp_write_quantum
echo 10 > /sys/block/mmcblk0/queue/iosched/read_idle
echo 20 > /sys/block/mmcblk0/queue/iosched/read_idle_freq
echo "cfq" > /sys/block/mmcblk0/queue/scheduler
echo 8 > /sys/block/mmcblk0/queue/iosched/quantum
echo 125 > /sys/block/mmcblk0/queue/iosched/fifo_expire_sync
echo 250 > /sys/block/mmcblk0/queue/iosched/fifo_expire_async
echo 16384 > /sys/block/mmcblk0/queue/iosched/back_seek_max
echo 2 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty
echo 93 > /sys/block/mmcblk0/queue/iosched/slice_sync
echo 39 > /sys/block/mmcblk0/queue/iosched/slice_async
echo 2 > /sys/block/mmcblk0/queue/iosched/slice_async_rq
echo 7 > /sys/block/mmcblk0/queue/iosched/slice_idle
echo 0 > /sys/block/mmcblk0/queue/iosched/group_idle
echo 1 > /sys/block/mmcblk0/queue/iosched/low_latency
echo "bfq" > /sys/block/mmcblk0/queue/scheduler
echo 4 > /sys/block/mmcblk0/queue/iosched/quantum
echo 125 > /sys/block/mmcblk0/queue/iosched/fifo_expire_sync
echo 250 > /sys/block/mmcblk0/queue/iosched/fifo_expire_async
echo 16384 > /sys/block/mmcblk0/queue/iosched/back_seek_max
echo 2 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty
echo 7 > /sys/block/mmcblk0/queue/iosched/slice_idle
echo 0 > /sys/block/mmcblk0/queue/iosched/max_budget
echo 4 > /sys/block/mmcblk0/queue/iosched/max_budget_async_rq
echo 125 > /sys/block/mmcblk0/queue/iosched/timeout_sync
echo 39 > /sys/block/mmcblk0/queue/iosched/timeout_async
echo 1 > /sys/block/mmcblk0/queue/iosched/low_latency
echo 20 > /sys/block/mmcblk0/queue/iosched/raising_coeff
echo 256 > /sys/block/mmcblk0/queue/iosched/raising_max_time
echo 7000 > /sys/block/mmcblk0/queue/iosched/raising_max_softrt_rate
echo 304 > /sys/block/mmcblk0/queue/iosched/raising_rt_max_time
echo 2000 > /sys/block/mmcblk0/queue/iosched/raising_min_idle_time
echo 500 > /sys/block/mmcblk0/queue/iosched/raising_min_inter_arr_async
echo "" > /sys/block/mmcblk0/queue/iosched/weights
# CAB
echo 1 > /sys/class/backlight/s6e8aa0/acl_set
# TCP Congestion Avoidance Algorithm
echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control;
# N7-specific
echo 500 > /sys/devices/system/cpu/cpu0/cpufreq/cpu_lp_max # LP core no longer used on FK
echo "1125 1100 1075 1050 1025 1000 975 950 925 900 875 850 825" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo 2 > /sys/class/misc/tegra_hotplug_control/cores_on_touch
echo 60 > /sys/class/misc/tegra_hotplug_control/first_level
echo 50 > /sys/class/misc/tegra_hotplug_control/second_level # No longer used in newer driver in FK
echo 25 > /sys/class/misc/tegra_hotplug_control/third_level # No longer used in newer driver in FK
echo 0 > /sys/devices/tegradc.0/smartdimmer/enable
Here's an awesome breakdown and research page for voltages most importantly pertaining to PVS values and overclocking.
Code:
download link:
PVS Research.xls (http://forum.xda-developers.com/attachment.php?attachmentid=2836827&stc=1&d=1404681790)
best max frequency (sweet performance/power spot):
MSM8974AB 2.3ghz - 1.34ghz
MSM8974AC 2.5ghz - 1.57ghz
MSM8974v2 2.2ghz - 1.34ghz
APQ8064 1.7ghz - 1.24ghz
APQ8064T 1.9ghz - 1.35ghz
best screen-off frequency (this varies if you try higher pvs settings):
Snapdragon 801 2.3ghz MSM8974AB - One M8
MSM8974AB 2.3ghz PVS 0 - 300mhz
MSM8974AB 2.3ghz PVS 1 - 346mhz
MSM8974AB 2.3ghz PVS 2 - 422mhz
MSM8974AB 2.3ghz PVS 3 - 499mhz
MSM8974AB 2.3ghz PVS 4 - 576mhz
MSM8974AB 2.3ghz PVS 5 - 652mhz
MSM8974AB 2.3ghz PVS 6 - 499mhz
MSM8974AB 2.3ghz PVS 7 - 576mhz
MSM8974AB 2.3ghz PVS 8 - 652mhz
MSM8974AB 2.3ghz PVS 9 - 729mhz
MSM8974AB 2.3ghz PVS 10 - 806mhz
MSM8974AB 2.3ghz PVS 11 - 883mhz
MSM8974AB 2.3ghz PVS 12 - 960mhz
MSM8974AB 2.3ghz PVS 13 - 1036mhz
MSM8974AB 2.3ghz PVS 14 - 960mhz
MSM8974AB 2.3ghz PVS 15 - 1036mhz
Snapdragon 801 2.5ghz MSM8974AC - Galaxy S5
MSM8974AC 2.5ghz PVS 0 - 422mhz
MSM8974AC 2.5ghz PVS 1 - 499mhz
MSM8974AC 2.5ghz PVS 2 - 576mhz
MSM8974AC 2.5ghz PVS 3 - 652mhz
MSM8974AC 2.5ghz PVS 4 - 729mhz
MSM8974AC 2.5ghz PVS 5 - 806mhz
MSM8974AC 2.5ghz PVS 6 - 652mhz
MSM8974AC 2.5ghz PVS 7 - 729mhz
MSM8974AC 2.5ghz PVS 8 - 806mhz
MSM8974AC 2.5ghz PVS 9 - 883mhz
MSM8974AC 2.5ghz PVS 10 - 960mhz
MSM8974AC 2.5ghz PVS 11 - 1036mhz
MSM8974AC 2.5ghz PVS 12 - 1113mhz
MSM8974AC 2.5ghz PVS 13 - 1190mhz
MSM8974AC 2.5ghz PVS 14 - 1113mhz
MSM8974AC 2.5ghz PVS 15 - 1190mhz
Snapdragon 800v2 2.2ghz MSM8974v2
MSM8974v2 2.2ghz PVS 0 - 345mhz
MSM8974v2 2.2ghz PVS 1 - 499mhz
MSM8974v2 2.2ghz PVS 2 - 422mhz
MSM8974v2 2.2ghz PVS 3 - 499mhz
MSM8974v2 2.2ghz PVS 4 - 576mhz
MSM8974v2 2.2ghz PVS 5 - 499mhz
MSM8974v2 2.2ghz PVS 6 - 576mhz
Snapdragon 600 1.7ghz APQ8064 - One M7
APQ8064 1.7ghz PVS 0 - 594mhz
APQ8064 1.7ghz PVS 1 - 594mhz
APQ8064 1.7ghz PVS 2 - 702mhz
APQ8064 1.7ghz PVS 3 - 810mhz
APQ8064 1.7ghz PVS 4 - 702mhz
APQ8064 1.7ghz PVS 5 - 810mhz
APQ8064 1.7ghz PVS 6 - 702mhz
Snapdragon 600 1.9ghz APQ8064T - Galaxy S4
APQ8064T 1.9ghz PVS 0 - 702mhz
APQ8064T 1.9ghz PVS 1 - 702mhz
APQ8064T 1.9ghz PVS 2 - 702mhz
APQ8064T 1.9ghz PVS 3 - 810mhz
APQ8064T 1.9ghz PVS 4 - 702mhz
APQ8064T 1.9ghz PVS 5 - 702mhz
APQ8064T 1.9ghz PVS 6 - 702mhz
best min frequency:
lowest possible setting (300mhz in case of MSM8974)
i highly recommend to run those values (exept if you are actually playing demanding 3d games).
use trickster mod frequency lock feature to do so. you will experience amazing battery life.
how to get the maximum battery life:
if you have a MSM8974AB pvs 6 for example, try the following steps:
try the next higher pvs levels (pvs7). don't try AC pvs values on AB chips.
AB chips are binned for lower frequencies while AC are binned for higher frequencies (duh).
so if you have a AB chip, work your way up the AB pvs values until you have freezes or similar and move back.
if you have a AC chip, work your way up the AC pvs values etc...
if you found highest setting that does not cause any problems after intensive testing and usage:
congratulations, you did it.
how to get the maximum frequency:
first try higher than stock maximum clock and see how it behaves.
if you don't reach your desired clockspeed, try the next lower pvs setting of your chip. yes, i said LOWER.
this gives the processor more voltage to reach higher overclocks.
i don't recommend it tho since we all want our phones to last as long as possible usually.
Thank you very much to @flar2 for all his work, and assisting people like me to port it to a device that otherwise would have no such love!
Gigantic thanks to @franciscofranco for his additions, fixes, and mako_hotplug!
Thank you to @Evolutionmods for helping me get this started, and for crucial fixes I would have no idea how to fix!
Thank you to @NineInchNails
@Captain_Throwback
@Vinchenzop
@Dubbsy
@Grommish
@Treken
These guys all have helped in very pivotal ways ,and I would not be at the understanding of android that I am today without them. Truly, thank you for being awesome helpful people!
Last but not least, thanks to these doods for helping test before release!
@kaosb0x
@shadowxaero
@stovo06
@dandan2980
Good one on mpdecision among other good stuff
Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
PVS explained:
https://developer.qualcomm.com/forum/qdn-forums/general-discussion/27244
http://forum.xda-developers.com/showthread.php?t=2228246
http://www.oppoforums.com/threads/qualcomm-cpu-binning-is-yours-slow-nominal-fast-or-faster.2842/
First. And thanks for this. Been looking for a new kenel to try.
What is a good app to use to modify CPU setting?
Also, is there a way that you could post recommended settings to use with this rom?
I'm glad to see another rom for this device. Thank you!
ironbesterer said:
What is a good app to use to modify CPU setting?
Also, is there a way that you could post recommended settings to use with this rom?
I'm glad to see another rom for this device. Thank you!
Click to expand...
Click to collapse
Trickster Mod is pretty good.
I just flashed the kernel, so far so good. I've been waiting for a kernel like this to drop for VZW Sense. Currently I'm running stock speeds, -15mV undervolt, no throttle and Multicore Power Saving 1. I think its going to be good.
Nice Scott, This is a very nice kernel. Here is a little hint too for you guys if you want total control over the CPU freq pick max frequency when you go thru the installer. Then after installation with file explorer go to system/bin and look for pnpmgr. Either just delete it or rename iwith a .bak at the end of it. Every time you flash the kernel this will be replaced back in system/bin.
What this does is allows the freq to stick on all 4 cores for example if you choose max freq in installer and use trickster to lower the freq you will notice that the other 3 cores will still go above what you have set the freq at. Another example is you will notice that your min freq will sometimes be higher than 300 MHz.
There is no ill side effects deleting this it just stops the Freq from doing what pnpmgr is telling it to do and allows you to tell it what to do.
So this is why I choose max delete pnpmgr and set the freq how ever I feel and don't worry about the freq changing on me.
Sorry for the long post MassStash [emoji12]
Awesome, thanks for dropping the info in here too bro!
Thanks !! Been looking for a Sense kernel I could use fauxsound on and this is it !! Thanks again !
Not sure how this works, but since only 4.4.2 is posted, will it hurt anything if I flash this on my firmware updated VZW M8? just want to do some testing while I wait for 4.4.3 of this kernel. Thanks
Chuckd610 said:
Not sure how this works, but since only 4.4.2 is posted, will it hurt anything if I flash this on my firmware updated VZW M8? just want to do some testing while I wait for 4.4.3 of this kernel. Thanks
Click to expand...
Click to collapse
I can tell you that it really doesn't like ViperOne 2.4 which is a 4.4.3 base. Very slow and laggy, lots of reboots. Works great on ViperOne 1.8 which was a 4.4.2 base.
HTC needs to drop that kernel source fast. I've been so excited to having OC, UV, and especially fast charge that I'm not leaving 4.4.2 until Mass works some magic for 4.4.3.
This will work with any Sense ROM? (I use CleanROM.)
Also, about call recording, that means recording is built in, or it will work with an app? I have call recording but it requires speakerphone. Will this allow recording with Bluetooth?
changt34x said:
HTC needs to drop that kernel source fast. I've been so excited to having OC, UV, and especially fast charge that I'm not leaving 4.4.2 until Mass works some magic for 4.4.3.
Click to expand...
Click to collapse
Agreed, I need more 4.4.3 kernels to play with.
Digitized from my M8 directly to your eyeballs.
Chuckd610 said:
Not sure how this works, but since only 4.4.2 is posted, will it hurt anything if I flash this on my firmware updated VZW M8? just want to do some testing while I wait for 4.4.3 of this kernel. Thanks
Click to expand...
Click to collapse
Just waiting for source of 4.4.3
Lykarsis said:
I can tell you that it really doesn't like ViperOne 2.4 which is a 4.4.3 base. Very slow and laggy, lots of reboots. Works great on ViperOne 1.8 which was a 4.4.2 base.
Click to expand...
Click to collapse
Not for 4.4.3
changt34x said:
HTC needs to drop that kernel source fast. I've been so excited to having OC, UV, and especially fast charge that I'm not leaving 4.4.2 until Mass works some magic for 4.4.3.
Click to expand...
Click to collapse
Will get that out asap when 4.4.3 drops
Dark Reality said:
This will work with any Sense ROM? (I use CleanROM.)
Also, about call recording, that means recording is built in, or it will work with an app? I have call recording but it requires speakerphone. Will this allow recording with Bluetooth?
Click to expand...
Click to collapse
Yea, should work with any Rom 4.4.2 based. It's call recording support, so I believe so. The apps capability may also matter of course tho
Just installed it, stock options all the way. The M8 is the first phone I've had where I haven't thought, "This could be faster." And I don't play really intensive games, so I just left it all alone.
I want to say it feels snappy, but I know it'll take a day or two for the kernel to really settle in.
Thanks man
The one thing I didn't like about my M8 was that there wasn't a decent kernel to install on it. I nudged flar2 to come over, but there was no budging him. This is exactly what I was hoping for.
Since I've had a few minor issues with kernel flashing in the past, is there a flashable version of the stock kernel anywhere that I can keep on hand before putting this on my phone?
Thanks
Maj
MajikUF said:
The one thing I didn't like about my M8 was that there wasn't a decent kernel to install on it. I nudged flar2 to come over, but there was no budging him. This is exactly what I was hoping for.
Since I've had a few minor issues with kernel flashing in the past, is there a flashable version of the stock kernel anywhere that I can keep on hand before putting this on my phone?
Thanks
Maj
Click to expand...
Click to collapse
Like the OP says, I'm gonna build out stock and post, just haven't had time to yet. Wanted to get the goods out first, and if need be you can dirty flash a Rom or somthin ya kno? Looks like I may have some time today prior to work, so ima try and get that out here for ya.
Just a quick question.
I thought I read before that the major difference between at&t/intl kernels and verizon is the partitions are in different places. Is this the case? If so, we wouldn't necessarily have to wait for VZW to release the 4.4.3 source, correct?
Thanks from topser
-MTP For GSI
-Samsung securities disabled
-Default compressor as LZ4
-Works with Magisk 23
-Powersuspend v2.0
-wakelock blocker driver v1.1.0
-Dynamic Fsync2.0
-Battery saver mode
-CPU Governors: all
-Interactive is default governor
-GPU thermal & voltage control
-Spectrum support enabled
-edit bus performance mif
-CPU overclocked and underclocked
-Max Big = 2.29 GHz
-Min Big = 208MHz
-Max Little= 1.79 GHz
-Min Little = 208MHz
Enforcing:
https://github.com/topser9/kernel_samsung_universal7885/releases/download/Big/hypersonic-enforce-a30.zip
Permissive: https://github.com/topser9/kernel_s...es/download/Big/hypersonic-permissive-a30.zip
If your cores are online and on high always install this: (hit thanks from minker) this is a little mod not change kernel
MinhKer_ModVip_a30_v1.1_R.zip
drive.google.com
After install any kernel use 3c cpu manager from play store and check cpu clocks to not damage kernel to your device