Note!
Only for stock 4.3
Click to expand...
Click to collapse
Features
Gamma Control - HOW-TO
DoubleTap2Wake - HOW-TO
Sweep2Wake - HOW-TO
Advanced Xperia Recovery - HOW-TO (Only v5 and above)
Based on 10.4.1.B.0.101 kernel sources
Xperia Advanced Recovery Bootloader
CPU overclock upto 1.944 GHz
Undervolting
Built with Linaro 4.8.3 toolchain using -O3 optimisation
Updated Prima WLAN drivers
Additional CPU governors - SmartMAX | SmartMAX_eps | Intellidemand 5.0 | Intelliactive | Preservative
Tweaked SIO and added FIOPS, Zen, VR, BFQ (7.2) and ROW block schedulers
USB force fastcharge
Updated Ondemand and interactive governor
Compressed kernel using XZ
Tweaked voltage regulators
Interactive GPU Governor
Uses CPUQuiet from Nvidia
Click to expand...
Click to collapse
Installation instructions
Flash in CWM/TWRP
Click to expand...
Click to collapse
Un-Installation instructions
Use the AROMA Installer in the zip to uninstall
Click to expand...
Click to collapse
Credits
Sony - I love what they do and only wish they got more recognition. They deserve it.
faux123 - For almost all kernel features
DoomLord - For the RAMDISK
Click to expand...
Click to collapse
Donors
Source
http://bitbucket.org/nikhiljan93/xzkernel
Click to expand...
Click to collapse
XDA:DevDB Information
[Stock-Kernel] XzInnere [Linaro-4.8.3], a Kernel for the Sony Xperia Z
Contributors
alnikki25k
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2014-03-29
Created 2014-01-27
Last Updated 2014-03-28
Reserved
HOTPLUG CONTROL, GOVERNORS, SAMPLE CONFIGS:
Thanks to n3ocort3x
With cpuquiet + load stats governor u get a brilliant battery life while keep it snappy.
I recommend leaving the governor on load stats (hotplug depended on load) to get the best results.
If you want to keep it balanced, and yeah, most users want that:
governor: smartmax
cpuquiet governor: load_stats
If you want ultimate performance:
governor: interactive (up treshold 65) or smartmax (lower tresholds)
cpuquiet governor: load_stats
SMARTMAX GOVERNOR
===============
awake_ideal_freq 594000
boost_freq 1242000
suspend_ideal_freq 384000
touch_poke_freq 1242000
Leave the rest untouched
Click to expand...
Click to collapse
For a more power-saving governor (Recommended)
New! Preservative
Click to expand...
Click to collapse
Thanks to bedalus
This is just for the record, and for those interested. The previous version of Preservative worked like a combination of smartass and conservative. It would scale straight up to the optimum frequency if there was any load (like smartass), then scale up one step at a time (like conservative) if the load was above the required threshold. This worked pretty well, and helped keep the frequency low. But sometimes it was keeping it low for too long, and a few users (myself included) noticed occasional hangs, presumably caused by a pile up of critical code that didn't get executed in time.
To improve responsiveness, but keep the frequency as low as possible was quite a challenge. I took the existing logic and chucked most of it in the bin...
(Remember, it's keeping the frequency low, and not UV that saves power - read this thread, especially post #2 for more background on this issue)
...what came to replace it was a fairly original hybrid, inspired by ondemand. Ondemand works by jumping to the top frequency when there is any load. This is usually overkill. So, you might have been at 100% CPU utilisation at 384MHz, so ondemand will jump straight to 1512MHz. However, when it gets there, the utilisation is now only 30%, so it will scale down to 486MHz.
Preservative now works a little like this. Whatever frequency it is currently at, if the utilisation hits 100%, it will scale up. But scaling up to max like ondemand? In the example above, this was the worst kind of overkill. Scaling up to max just to find scaling up one step would have been sufficient. But do we need to scale up one step, or as many as possible? There's no way to know for sure. You have to scale up before you can measure if the extra CPU cycles were enough or not.
This issue is what Preservative attempts to overcome: if the load is high, it will scale up, but not always to max. Let's label the frequency steps: 384=A 486=B 594=C 702=D 810=E 918=F 1026=G 1134=H 1242=I 1350=J 1458=K 1512=L
Conservative would take 11 calls to the governor to get from A to L, if L was required. Ondemand would go straight there. Ondemand is often overkill, conservative is often underkill. I'd like a compromise. Here's what Preservative would do:
Code:
L <- 4th step selected by preservative
K <- 3rd step selected by preservative
J <- 2nd step selected by preservative
I
H
G <- 1st step selected by preservative
F
E
D
C
B
A <- sat here until there is load
It splits the difference between whichever frequency it is at and the top frequency, and jumps there. If it is still under high load, it will do it again. So if it is idling, then needs to get to the top, it takes three more calls than ondemand, but seven less than conservative. Not only that, but it has also skipped over a large chunk of the slower steps that conservative would crawl through.
Scaling down also works in a similar way. Preservative will work out what step would be sufficient to manage the load, then jump halfway to that step on the first call. This is because, unlike ondemand, there is no down-threshold. Preservative will scale up when the load exceed the up threshold, but as soon as this is no longer the case, it will start attempting to scale back down to save power. It does not wait for load to reduce to drop below a certain point. Loads fluctuate. If went straight back to A, only to come back back to L, it would have to scale through G J and K again. However, dropping to G then D then B before A means if it does have to scale back up towards L, it doesn't have as far to climb, meaning less calls to the governor, and that the best step can be achieved quicker.
There has also been an adjustment to the up threshold. When the device is idle, the up threshold will automatically adjust to be more relaxed about scaling up. This means while the device is idle (e.g. when you are just reading some text) it becomes increasingly sensitive to changes in demand. When you touch the screen it will extremely responsive.
Conversely, when the device is hitting the top frequency, the up threshold will become increasingly strict. So if you are gaming, and putting a lot of load on the CPU, it will aim to be as efficient as possible, and only scale up if it really has to, to ensure that no cycles are wasted at these high power hungry frequencies.
Whenever it goes from hitting L to hitting A, or visa versa, the threshold will reset to default. The sysfs location of this tunable remains at:
Code:
/sys/devices/system/cpu/cpufreq/up_threshold
It will accept values of up to 127, higher being more power-saving. The default is 100, but editing the file changes this value. If you want to use a different value on a permanent basis, add the line
Code:
[B]echo 84 > /sys/devices/system/cpu/cpufreq/up_threshold[/B]
to /etc/init.d/00config
and it will then restore your setting of 84 (or whatever) every time you reboot. Remember it will be overwritten if you flash updates to the kernel, so make a copy of your edited file. However, I believe 100 is a pretty good default.
Click to expand...
Click to collapse
Reserved
Changelog
Next-Release-TO-DO
XzI - v6
Kitkat - 230 Sources
Massive changelog
Large amounts of debugging code removed
Click to expand...
Click to collapse
Current-Release
XzI - v5
Intelliactive CPU governor
New! Advanced Xperia Recovery Bootloader
New! Preservative CPU Governor (Read more)
Kernel mode NEON
MSM CPU Frequency Limiter / a.k.a Snake Charmer(in faux app) support
Kernel Futex tweaks
MSM Memcopy enhancements from Motorola Mobility
Higher Bus Speeds @ Lower cache clocks = Higher performance @ Lower Temperatures + More Power Savings
Generic tweaks
Click to expand...
Click to collapse
Previous releases
XzI - v4
Sony 10.4.1.B.0.101 Sources
Tap2Wake/Sweep2Wake using evgen method
New Power-Aware Workqueue algorithms
AROMA Installer
XzDualRecovery
Lots of debugging removed
BFQ-v7r1
Interactive GPU Governor
Removed Simple GPU Governor
Removed MultiROM
Click to expand...
Click to collapse
XzI - v3
MultiROM Xperia for Xperia Z - http://www.youtube.com/watch?v=9f9gG1sRNog
- Initial implementation. Not functional. Just testing boot.
Revert Power-Supply drivers back to 4.2.2
Intellidemand Governor 5.0
Click to expand...
Click to collapse
XzI - v2
Lower undervolt to 600 mV
Sound Control 2.0
Gamma Control
SLUB updates
Updated Adreno drivers
Use O3 Optimisation
Tune BFQ
System Config Clean-up - Quite experimental
Click to expand...
Click to collapse
XzI - v1
Initial Release
Click to expand...
Click to collapse
Download
Click here
Click to expand...
Click to collapse
MultiROM
Coming Soon
Placeholder
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Kocayine said:
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Click to expand...
Click to collapse
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
alnikki25k said:
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
Click to expand...
Click to collapse
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Kocayine said:
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Click to expand...
Click to collapse
Yup. May not include that. But will have Gamma control.
No sound control right?
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
You sure you cant make a version with doubletap? I dont need very advanced kernel, just some governors and stuff and now I got used to the tapping as well : (
BTW, how about the wakelock fixes and so from XzKernel, are they included here?
beniamin24 said:
No sound control right?
Click to expand...
Click to collapse
This is just the first release. It'll be added next.
my phone reboots after trying to undervolt in trickster mod app
braacic17 said:
my phone reboots after trying to undervolt in trickster mod app
Click to expand...
Click to collapse
It works for me. Clear all settings in TricksterMOD and try again.
alnikki25k said:
It works for me. Clear all settings in TricksterMOD and try again.
Click to expand...
Click to collapse
nope. still not working i tried everything even in faux123 app but it just reboots.
well its not so important for me right now. kernel is awesome and i can see better battery life on my xz 4.3 !!
thanks ! :laugh:
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
What about exFAT? Is it work properly?
-totonio- said:
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
.. and doubletap.. then we got all that is needed
Not for deodexed right?
Inviato dal mio C6603 utilizzando Tapatalk
Exactly what i need, a battery oriented / balanced kernel, while keeping it slim.. Keep up the good work!
Waiting for gamma control.. ??
Edit Note: i've missed the part which state that double tap wont be included here.. Sorry..
Sent from my C6602 using Tapatalk
Related
Introducing the new variant of Bali kernel, Bali for CM7. The main goal of this kernel is the same as other Bali kernel, balanced performance and battery life. I can't guaranteed you will get the same battery life as Bali for Froyo but you will definitely get an improve battery life over stock kernel.
Features:
- OC/UV up to 1.4GHz (Safe boot to 1GHz) [require setCPU from market]
- Voodoo Sound v10
- Voodoo Color
- Multiple CPU governor, smartass included (default: ondemand)
- Multiple IO scheduler (default: BFQ)
- LED notification support (no external app required)
- CIFS support
- Support SetCPU screen off 100/400 profile
- Dock sound redirector support [need Galaxy Dock Sound Redirector app from market]
Disclaimer:
As always, I'm not responsible with any damage cause to your phone.
Special Thanks:
- Team Whiskey - you guys are awesome.
- Alexia - for great work on the new splash image.
- Supercurio - for awesome work on Voodoo
- xcaliburinhand - for wonderful work on dock sound redirector.
- Everybody at CM dev community for their hard work on this awesome ROM.
- Everybody at #teamwhiskey for beta testing this kernel and their support.
I apologize if I miss anyone ..
Flashing Instruction:
- If you're coming from another kernel, flash "Ultimate Kernel Cleaning Script" by lippol94 first (http://www.multiupload.com/XFH1GCK4MB)
- Once that's done .. then flash Bali-CM
If you don't know how to flash then this is not for you.
Download:
Bali-CM_v2.2.2
Change Log:
Code:
- 2.2.2 [10/18/2011]
CM update
Re-enabled LED by default
- 2.2.1 [9/12/2011]
Fixed screen jitter issue
- 2.2 [9/10/2011]
Upgraded BFQ to v2
Added Smartass v2 with extra tweak
Fixed ondemand and tweaked for smoother experience
Set ondemand as default governor
Other fixes and tweaks
- 2.1 [9/1/2011]
Disabled SLQB and revert back to SLUB
Disabled LED notification for the time being
Added more UV settings
GPU tweaks
Added v(r) scheduler
Added Tiny Preempt RCU
And other tweaks and fixes
- 2.0 [8/25/2011]
Disabled ramzswap and switched to zram
Enabled zcache for better IO performance
Memory tweak, now gives you 340MB
More tweaks
- 1.2.1 [8/19/2011]
Fixed video playback issue
Fixed battery report when charging, it goes to 100% now
- 1.2 [8/18/2011]
Updated source with the latest CM patches
Added SLQB slab allocator for better memory management
Added more tweaks
- 1.1.1 [7/26/2011]
Fixed kernel instability that cause random reboot
- 1.1 [7/26/2011]
Added Voodoo color V2
Fixed UV portion to make it easier to manage
Added Voltage Control support
Added compiler tweak
- 1.0 [7/22/2011]
Initial release
A little explanation on different governors (taken from Lord ClockAn thread):
- interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
- smartass - Is an improved version of interactive governor
- ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
- performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
- powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
- userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Q and A:
My screen has green, yellow, or orange tint.
Use Voodoo Control to set color profiles (courtesy of d_phekt)
Screen RGB Multipliers:
Red = 230996000
Green = 230996000
Blue = 2704668800
Screen v1 Gamma Hack:
Red = -50
Green = -53
Blue = -44
is GPS still functional with this kernel?
gamikzone said:
is GPS still functional with this kernel?
Click to expand...
Click to collapse
Yes .. GPS still functional.
drhonk said:
Yes .. GPS still functional.
Click to expand...
Click to collapse
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
gamikzone said:
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
Click to expand...
Click to collapse
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
drhonk said:
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
Click to expand...
Click to collapse
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
gamikzone said:
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
Click to expand...
Click to collapse
Try smartass with this kernel ..
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
i think i will try this out tonight
I believe this will be ok to use with miui.
Nice animation.
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
jay661972 said:
I believe this will be ok to use with miui.
Nice animation.
Click to expand...
Click to collapse
Trying it out , any recommeneded UV settings?
Sent from my T959 using XDA App
jay661972 said:
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
It does work on miui,
Sent from my T959 using XDA App
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
Really, how did you do that? I did the clean script first and flash Bali.
es7241 said:
It does work on miui,
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Okay I will try this one more time.
jay661972 said:
Okay I will try this one more time.
Click to expand...
Click to collapse
confirmed .. it works on MIUI since I just flashed MIUI with it.
jay661972 said:
after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
Same here except im flashing from trigger redux #12 and ive tried flashing from trig w/glitch and w/du jour
Sent from a cell tower to the XDA server to you.
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
drhonk said:
confirmed .. it works on MIUI since I just flashed MIUI with it.
Click to expand...
Click to collapse
jay661972 said:
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
Click to expand...
Click to collapse
So you can't flash bali on miui energy? You have to revert to stock miui?
Sent from my T959 using XDA Premium App
Current Release: 12/20/2012(JB)/10/03/2012(GB+ICS)
Important, Please read: There are now two kernel versions starting with 8/10/2012 release, one for GB+limited ICS(no HWA) support and another for the ICS branch with HWA. Changes will be loggged separately for each kernel type. If you see no changelogs specifically for that type, then there's no release made. For example, 8/10/12 for GB is a continuation of the 3/21 release with none of the post-3/21 kernel ICS changes made.
Update 9/21/12: As of 9/21/12, jellybean is officially supported with the JB specific kernels.
First of all, I started this thread to make commenting and tracking easier for the incredikernel releases following Chad's latest release (8/15/2011).
I also wanted to make a distinction between Chad's initial kernels and the ones I've updated since that release and this is one way to do it. Initially I didn't want to do that but now I regretted not splitting sooner.
If you want the changelog for anything prior to my first kernel please refer to:
Chad's Incredikernel thread
Changelog:
11/30/2013 JB 4.3
Android 4.3 support
synced with updates from Android 4.3 Evervolv kernel
04/25/2013 ICS Sense+JB 4.2
dynamic fsync control
WiFi driver updates
Interactive governor updates - see Tinykernel
Entropy Tweaks
Netfilter updates
New sysfs location for fast charge for broader app compatibility - still compatible with latest incredicontrol
FUSE filesystem support
12/20/2012 JB 4.2 ONLY
add back governors that were removed in 12/15
12/15/2012 JB 4.2 ONLY
enabled UHID support
updated msm_fb for 4.2
12/11/2012 JB ONLY
cpufreq: enable overclocking of 1.15Ghz and 1.19Ghz
numerous interactive and ondemand governor tweaks
cpufreq: send uevent when governor changes
ondemand: boost pulse for JB's powerHAL
10/11/2012 JB ONLY
defconfig: several config changes to fix data usage not working
10/06/2012 JB ONLY
defconfig: enable conservative governor by request
10/03/2012 ICS+JB+GB
defconfig: remove rarely used governors and set max frequency to preventing booting higher than 998mhz
lower default hispeed_freq to 614Mhz
cpufreq: interactive: always limit initial speed bump to hispeed_freq
09/21/2012 ICS+JB+GB
ALL: New Interactive governor
ALL: Built with GCC 4.6 toolchain from Google
GB: interactive governor tweaked for battery
ICS+JB: interactive governor tweaked for butter
JB: genlock patched for JB support
JB: new wifi driver for compatibility with JB ROMs
08/11/2012 ICS+GB
KSM wasn't enabled as it should have been in the last build - fixed that - also nothing needs to be done to enable it on GB as it's on by default
08/10/2012 ICS ONLY
fixed data usage features for ICS
added mamarley's fastcharge USB patch to enable fastcharge without needing to unplug the charger
enabled KSM (Kernel Samepage Merging) - still need to enable in CM settings
08/10/2012 ICS+GB
added mamarley's fastcharge USB patch to enable fastcharge without needing to unplug the charger
07/07/2012 ICS ONLY
Merged in multiple driver updates to support HWA (chad0989)
Updated adreno kernel drivers to latest
added xtqta_guid - for ICS' data usage feature, also seems to have resolved stability issues
Added lazy CPU governor
Added back intellidemand
03/21/2012 ICS+GB
Added lazy CPU governor
02/26/2012 ICS+GB
Smartassv2 default governor for sure - doesn't override ramdisk settings though
new governor lagfree - balance between ondemand and interactive
new I/O scheduler SIO
tweaked deadline for better performance
removed CFQ/BFQ schedulers and smartass, conservative, and interactive govenors (still have interactiveX and smartassv2)
01/03/2012 ICS+GB
Tweak intellidemand and interactiveX governors for battery life
Add ZRAM and swap support and add script to toggle ZRAM - see bottom of OP for more info
SmartassV2 default governor again
12/26/2011 ICS+GB
Added faux123's intellidemand governor (thanks faux123!)
Added imoseyon's interactiveX governor (thanks imoseyon!)
Works on GB and ICS currently
interactiveX may not play nicely with ICS so intellidemand is default
Conservative is disabled, let me know if you need it back
12/08/2011 (Chad) ICS+GB
Added ICS support (limited)
11/27/2011 GB
Use ondemand, performance, and conservative governors from the Android Linux 3.0 kernel
Set minimum voltage back to 800 as the voltages will not go below 800 anyway. Anything lower is placebo effect. This is a hardware limitation.
11/14/2011 GB
Update OJ driver
BT fix for newer CM nightlies
WIFI module updates
Update and re-add BFQ scheduler as well as disable deadline
Ondemand is back
Fixes/Tweaks to ondemand and interactive
10/08/2011 GB
Adjusted smartassV2 parameters for 1GHz processor (originally for 500Mhz device)
10/01/2011 GB
Set smartassv2 to default governor
09/30/2011 GB
Added SmartassV2 governor
Current CPU governors as of the latest release:
SmartassV2
Ondemand
Interactive
Lagfree
Lazy
Technical doc on CPU governors (most of the ones in this kernel anyway)
https://raw.github.com/tiny4579/android_kernel_common/android-2.6.38-incredikernel/Documentation/cpu-freq/governors.txt
Update: 11/30/13 - removed link to incredikernel.com as the site has no content - fully on goo.im now
http://goo.im/devs/tiny4579/inc/kernels
Kernel Source
https://github.com/tiny4579/android_kernel_common
Here are a couple notes if you want to build this kernel from source:
Jellybean kernel branch is android-2.6.38-incredikernel-jb.
ICS kernel branch is android-2.6.38-incredikernel-ics.
Gingerbread kernel branch is android-2.6.38-incredikernel.
The config for the kernel is in arch/arm/configs/incrediblec-incredikernel_defconfig. If you want to switch branches I recommend doing a make incrediblec-incredikernel_defconfig after checking out that branch.
I use the GCC 4.4.3 toolchain for this kernel due to GCC 4.6 causing build issues.
Frequently Asked Questions
Some key differences between smartass and smartassv2 so users can decide which they prefer and learn a bit more about the differences:
Smartass
1. Screen off profile built in maxed at 384mhz.
2. Wakeup frequency is 998mhz.
3. Min screen on is 245mhz.
4. Improved by Chad to run better on our devices.
5. Purely load based, no ideal value.
Smartassv2
1. This is the same exact governor in Erasmux's Nexus One kernel (github.com/erasmux/n1-kernel)
2. Ideal wake frequency is 768 (also default that can be changed).
3. Screen on min is actually 128mhz).
4. No screen off profile.
5. Ideal sleep frequency 245mhz.
6. Improved upon from erasmux's version, not Chad's.
Basically the smartassv2 ideal wake frequency allows the phone to favor a certain speed to attempt to save battery life. It can still go above ideal wake and below ideal sleep so there's no caps on max and min while awake or sleep.
Some tips/info on various governors:
Smartass/smartassv2/interactive:
Use 128 min so the governor can scale as it needs to. Max speed I'd recommend at least 768Mhz.
Ondemand:
Try 128 min and if it lags use 245 min. Max speed I'd recommend at least 768Mhz.
Performance:
Only recommended for benchmarks but speed will always run at max.
InteractiveX:
Same as interactive except it has an auto screen off set to the min. Ideal with 245 min in setcpu but try 128 for battery life but it you have wake lag then set to 245.
Intellidemand:
Based on ondemand with a built in screen off. Any speed settings should be fine.
Interactive:
Some new features with this one. Starting with 9/21/12 release I am using the interactive kernel from Google which features a new kernel option called input_boost.
It is off by default but can be enabled by writing a 1 to /sys/devices/system/cpu/cpufreq/interactive/input_boost. Also there is another parameter for interactive called hispeed_freq in the same location. The hispeed_freq is where the governor jumps to first. Hispeed_freq by default in 10/3/12 is 614400 to help save battery. In the older interactive governor there was a maxspeed freq which meant the governor was a bit jumpier to the max speed. This should be a good blend of performance and battery.
Lagfree:
Based on ondemand but with a softer CPU scaling which should help with battery life. It also seems to be very responsive (starting with 2/26)
Lazy:
Based on ondemand as well (Ezekeel is the developer of this governor). I cannot explain this too well but its apparent behavior seems to be to switch between low and high frequencies pretty evenly.
A note from Ezekeel on this governor:
"Thus I took the ondemand governor and implemented an additional parameter 'min_timeinstate' defining a minimum time the CPU will stay in a certain frequency state before it will be allowed to switch frequencies again. This way one can have a fine grained polling by setting the sampling_rate to a low value without running into problems with these fast frequency changes.
I did some extensive testing with a sampling_rate of 10000, min_timeinstate of 40000 and up_threshold of 90 and FLAC, mp3 and video playback all seem to work flawlessly. So it seems the root of the problem was indeed that the CPU does not handle fast frequency changes well.
I tested several apps and games and so far I have not found anything that this governor cannot handle. Thus I dare to say that it seems to be the superior choice over ondemand."
ZRAM, what is it and how to I add it? (starting officially with 12/31/11)
If you are familiar with swap space in linux or virtual memory in Windows it is a similar concept. Except instead of using the hard drive as swap space it compresses swap space in RAM for faster access times than conventional swap. This will also wear out our storage memory less than typical swapping.
Enable ZRAM is simple thanks to a script built by imoseyon which is provided in the kernel zip file. To enable, use adb shell or download a terminal app and run zram enable. This will persist across reboots (if init.d is setup in your ROM) so if you don't want it anymore run zram disable and it will remove the bootscript and deactivate it.
You need to have root privileges to enable/disable zram. Run the su command in terminal emulator to request root.
I was wondering when lazy was gonna make it's way to aosp...
Sent from my ADR6300 using xda premium
OMG_VTEC said:
I was wondering when lazy was gonna make it's way to aosp...
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
The name of the new governor says it all....
You just answered your own question. I took my own sweet time releasing it. It was built like 2 weeks ago. I was being lazy.
tiny4579 said:
Scripts/Mods if I think of something...
Click to expand...
Click to collapse
Tiny, this new thread is great, as is the work you and Chad have done on these kernels. Keep up the great work. Thank you.
jlokos said:
Tiny, this new thread is great, as is the work you and Chad have done on these kernels. Keep up the great work. Thank you.
Click to expand...
Click to collapse
Yeah, the old way was sloppy. Tired of it. I think this thread is cleaner than the sense one and it took me less time to write it.
To help out users (and document the probable future deviation), how about adding a tag to each kernel stating whether it works with froyo (which I believe is none), GB, ICS, or a multiple (which is only the last couple or so, I think).
Great work, by the way.
PonsAsinorem said:
To help out users (and document the probable future deviation), how about adding a tag to each kernel stating whether it works with froyo (which I believe is none), GB, ICS, or a multiple (which is only the last couple or so, I think).
Great work, by the way.
Click to expand...
Click to collapse
Done. 10char
Nice.....great work to you and Chad. Thanks.
Sent from my ADR6300 using Tapatalk
Thanks for the thread tiny, I was wondering what the benefits of the lazy governor were
I'm running my CPU at 128/806 Mhz with Lazy and it's been nice and smooth all day. Battery life has been as good or better than SA2 for me.
It also seemed to drop my ping time and increase the throughput in SpeedTest. I was getting really discouraged with ICS and >400ms ping times but I'm attributing the Lazy governor with right around 100ms ping and smoother data rates. When I switch back to the SA2 governor that I've been running for months data gets choppy again. The system itself seems smooth enough with SA2 but data has been very choppy.
Thank you to all you great developers for all your time, effort, and hard work. We really do appreciate it.
azradiohead said:
I'm running my CPU at 128/806 Mhz with Lazy and it's been nice and smooth all day. Battery life has been as good or better than SA2 for me.
It also seemed to drop my ping time and increase the throughput in SpeedTest. I was getting really discouraged with ICS and >400ms ping times but I'm attributing the Lazy governor with right around 100ms ping and smoother data rates. When I switch back to the SA2 governor that I've been running for months data gets choppy again. The system itself seems smooth enough with SA2 but data has been very choppy.
Thank you to all you great developers for all your time, effort, and hard work. We really do appreciate it.
Click to expand...
Click to collapse
The ROM/kernel/governor have no impact on data signal or speed so what you're seeing is coincidental. Network speed varies on so many factors outside of the control of the ROM or kernel. I'm glad to hear you like the new kernel and the lazy governor. I'm a fan of the dev of the lazy governor's work and run his kernel on my nexus.
My concern is that others will assume it will improve network performance and be disappointed when it doesn't.
Thank you for your compliments!
I just want to make sure I clarified this matter.
chocolate8175 said:
Thanks for the thread tiny, I was wondering what the benefits of the lazy governor were
Click to expand...
Click to collapse
I was looking around for something good that would make sense but I couldn't find anything so far.
Basically I added this governor on a whim. So far it seems to like lower frequencies even more than smartassv2 without too much sacrifice on speed. It might have better battery life. It seems smooth on Nil's Business Sense 3.5 though.
Interesting post here on smartassv2 from the developer of the lazy governor:
User:
and smartassV2 too but let him fix find the cause of the reboots before
Dev:
I will not integrate any new stuff until I have the cause for reboot problems tracked down. I will look into lulzactive, but I definitely will not include smartass since it is an inefficient governor.
Not sure why he said it was inefficient but could see no post about it.
Needless to say, I like lazy and lagfree so far. Give lazy and lagfree a try for a week and see what you think.
azradiohead said:
I'm running my CPU at 128/806 Mhz with Lazy and it's been nice and smooth all day. Battery life has been as good or better than SA2 for me.
It also seemed to drop my ping time and increase the throughput in SpeedTest. I was getting really discouraged with ICS and >400ms ping times but I'm attributing the Lazy governor with right around 100ms ping and smoother data rates. When I switch back to the SA2 governor that I've been running for months data gets choppy again. The system itself seems smooth enough with SA2 but data has been very choppy.
Thank you to all you great developers for all your time, effort, and hard work. We really do appreciate it.
Click to expand...
Click to collapse
may be placibo effect but I have noticed this too and confirmed with speedtest.
Sent from my incredible incredible.
RebelShadow said:
may be placibo effect but I have noticed this too and confirmed with speedtest.
Sent from my incredible incredible.
Click to expand...
Click to collapse
How does it fare with ondemand or lagfree? I still think its placebo. I can't test on my phone as I don't have data on the incredible.
Sent from my Galaxy Nexus using Tapatalk
Running GB and just installed the new Incredikernel, I saw no appreciable difference with data usage on Lazy, Lagfree, SAV2, Ondemand. Depending on your wireless signal, just moving your body by even a few inches could have an impact on data speeds (high frequency shadowing of transmission waves). The ping, might have some more sway by the CPU of the device if the program doesn't get as much processor in when communicating with the server, but not in the order of milliseconds (would be my though).
tiny4579 said:
I was looking around for something good that would make sense but I couldn't find anything so far.
Basically I added this governor on a whim. So far it seems to like lower frequencies even more than smartassv2 without too much sacrifice on speed. It might have better battery life. It seems smooth on Nil's Business Sense 3.5 though.
Interesting post here on smartassv2 from the developer of the lazy governor:
User:
and smartassV2 too but let him fix find the cause of the reboots before
Dev:
I will not integrate any new stuff until I have the cause for reboot problems tracked down. I will look into lulzactive, but I definitely will not include smartass since it is an inefficient governor.
Not sure why he said it was inefficient but could see no post about it.
Needless to say, I like lazy and lagfree so far. Give lazy and lagfree a try for a week and see what you think.
Click to expand...
Click to collapse
I'm using your latest GB kernel with the lazy governor on Warm TwoPointThree 3.5 rom. It is very smooth with very good battery life (undervolted).
jlokos said:
I'm using your latest GB kernel with the lazy governor on Warm TwoPointThree 3.5 rom. It is very smooth with very good battery life (undervolted).
Click to expand...
Click to collapse
Better than SAV2? I can't really comment myself but I like it so far.
Also, try to keep Sense kernel talk in the sense thread and aosp kernel talk in the AOSP thread. It makes tracking easier. But I also brought up the comment in this thread so it makes sense why you posted here.
tiny4579 said:
Better than SAV2? I can't really comment myself but I like it so far.
Also, try to keep Sense kernel talk in the sense thread and aosp kernel talk in the AOSP thread. It makes tracking easier. But I also brought up the comment in this thread so it makes sense why you posted here.
Click to expand...
Click to collapse
I have used both the GB and AOSP versions of the lazy governor. The GB version appears to make the Sense 3.5 rom smoother. As far as battery life, I haven't been able to tell if its better than SA2 since I have a much longer history with SA2. In any event, thanks for adding this governor to both versions (as I switch between the new ICS roms and Sense 3.5); it's another great choice for us to experiment with.
Could you make lulzactive possible tiny?
Sent from my DROIDX using Tapatalk
dyn.Kernel
*Discontinued*
I want to share with you my own kernel builds. My focus is on performance improvements and energy efficiency.
Things I want to achieve:
- more battery life
- same more performance as stock
- smooth ui / games
- less heat
Highlights:
GPU idle detection:
We don't need high performance if there is nothing moving on the screen. Therefore the kernel will detect when the gpu is offline or at very low load (for litte moving objects, like battery charging animations). This feature is used for nearly all my other modifications.
Advanced Dynamic Scaling:
I have added additional values for idle (nothing moving), busy (action on the screen) and (touch)boost. Everything is explained below.
Dynamic Touchboost:
The touch boost is only active if something is rendered on the screen, that means the boost will pause as long as there is no movement, but it will resume when it is actually necessary. The boost is configured in boost_target_loads.
New Hotplug Solution:
I wrote a new hotplug driver which is completely configurable. You can change the behavior for every cpu core and gpu_idle state.
https://github.com/aventu90/android_kernel_lge_v500/blob/dyn/arch/arm/kernel/hotplug.c
All interactive and hotplug values explained (build r4+):
Many values are grouped into boost, busy and idle.
boost: A short period of time while or after touching the screen.
busy: The gpu has work to do, nearly always active when something is moving on the screen.
idle: The opposite from busy. A good time to save energy with conservative values.
Interactive governor:
I have added boost, busy and idle values to get the best performance / battery life in every situation.
Read this to understand what the new interactive governor values do: https://android.googlesource.com/kernel/common/+/android-3.4^/Documentation/cpu-freq/governors.txt
Hotplug driver:
You have different values for every gpu_idle and online-cpus state. So your phone will scale differently when playing games, doing nothing or just swiping on the screen. Here is an example:
pm_busy_up_threshold -> 55 60 65 100
1 CPU cores online: 55% up threshold
2 CPU cores online: 60% up threshold
3 CPU cores online: 65% up threshold
4 CPU cores online: 100% up threshold, because we can't get more
All values explained:
up_threshold: If the cpu load gets higher than x%, the hotplug driver will start counting up to max_up_counter
down_threshold: If the cpu load gets lower than x%, the hotplug driver will start counting up to max_down_counter
max_up_counter/max_down_counter: Every sample_time_ms the hotplug driver can count +1, -1 or nothing, when the max_ value is reached, 1 core can go on- or offline. Both counters will be reset when a core goes on- or offline.
sample_time_ms: It will take this long until the driver will check again all the things, mentioned above.
So the minimum time until a cpu core goes on or offline is: sample_time_ms * max_counter. For example:
busy_max_down_counter[3 cores online] * busy_sample_time_ms => 100 * 30ms = 3000ms = 3 seconds
You must set 4 values or 1 for sample_time_ms.
Configure the kernel (optional, build r4+):
If you want to use custom values, this is the best way for now:
1. Download the kernel_config.zip and extract it
2. Put the file somewhere on your sdcard
3. Install and open Script Manager
4. Click the file and select "Su" and "boot" (values will be automatically set at boot)
5. Click "start" and all values will be set
You can use an app like Kernel Tuner for undervolting.
Installation:
- make a nandroid backup first (boot)
- flash .zip via custom recovery (CWM/TRWP)
- flash SuperSU
Button combo for recovery:
http://www.youtube.com/watch?v=uo3YfszOPsQ
Github:
https://github.com/aventu90/android_kernel_lge_v500/commits/dyn
MD5
4cbae4bf1f6d39db020a131284d1c7a3 dyn.Kernel-r1-0110.zip
f63e212848f018a4d5615c997bed3757 dyn.Kernel-r2-0118.zip
a32828474a31dc2ae3f7885bae7caae3 dyn.Kernel-r2-0120-CM.zip
588af2b55f05f71d84ccb9bd845fd29d dyn.Kernel-r3-0204.zip
0ba565860bad16bb8ecfb94f28dad902 dyn.Kernel-r3-0204-CM.zip
511e888d74d24caa2328685c287c4738 dyn.Kernel-r4-0318.zip
247f49ef0e7d9474f500670cb9daa859 dyn.Kernel-r4-0321-CM.zip
Big thx to:
rmcc
djrbliss
Mahdi786
FranciscoFranco
Faux123
Hit thanks if you like it.
You can also buy me a coffee.
I'm testing all my builds and use them daily, but I am not responsible for any kind of damage on your device.
Which kernel should I choose?
There are V500 KitKat roms which work with G Pad 8.3 Google Play Edition stock code (GPE) or with code from Code Aurora Forum (CAF).
"CM" build for:
- CM11
- Mahdi-Rom 01/17 or later
- other CM/CAF based roms
build without suffix:
- Mahdi-Rom before 01/17
- AOKP
- PA
- SlimKat
- CMB
- other stock GPE based KitKat roms
This list could change quickly, please let me know.
Not made for V510 (GPE)!
(build r4+) clear your kernel app settings, compare them with the values from the 02kernel_config script
Changelog:
Code:
r4:
- hotplug driver: another big update, all values are now configurable
- smartcover support
- updates for CAF build
- (03/21) Cyanogenmod ramdisk update
r3:
- major cpu interactive governor update
- - newest version from CAF
- - added a lot of dynamic values
- hotplug updates
- touchboost updates
- rewritten gpu interactive governor
r2:
- cherry-picks from Cyanogenmod/Code Aurora
- - 100% cpu idle bug should be fixed
- - great improvements in idle/sleep time
- - faster charging through bugfix
- hotplug: lower threshold for 4th core
- touchboost: gpu_idle stays false now for at least 100ms
r1:
- undervolting added
- new hotplug solution
- modified interactive governor is default
- franco's interactive gpu governor
- gpu idle detection
- franco's generic touchboost driver
- set readahead to 512kb
- other things (github)
Good to see some kernel love
Could you elaborate as to why you don't think cm11 won't work please?
Sent from my LG-V500 using XDA Premium 4 mobile app
whoamigriffiths said:
Good to see some kernel love
Could you elaborate as to why you don't think cm11 won't work please?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CM uses different kernel sources usually, but I am not sure if it is still compatible.
reborn90 said:
CM uses different kernel sources usually, but I am not sure if it is still compatible.
Click to expand...
Click to collapse
I can confirm that this doesn't work on cm
Sent from my LG-V500 using XDA Premium 4 mobile app
Stock ROM Supported ?
Does this support or do you plan to make one for the stock rom ?
naruto.ninjakid said:
Does this support or do you plan to make one for the stock rom ?
Click to expand...
Click to collapse
I could, yes. But there must be enough demand. I personally don't like manufacturer roms, they are often antiquated and overloaded, so it's up to the community.
reborn90 said:
I could, yes. But there must be enough demand. I personally don't like manufacturer roms, they are often antiquated and overloaded, so it's up to the community.
Click to expand...
Click to collapse
I believe many of us are running the stock ROM but you could do a poll or something to be sure. Anyway thanks for your work.
Thank You
reborn90 said:
I could, yes. But there must be enough demand. I personally don't like manufacturer roms, they are often antiquated and overloaded, so it's up to the community.
Click to expand...
Click to collapse
Thank you for branching out in this direction. I'm keen to try it but am currently on Malladus 4.2.2 because it's the only custom rom that works with XBMC.
Would your kernel on Mahdi change that?
Thanks man. Glad you like mahdi
Sent from my LG-V500 using Tapatalk
Exciting to see new kernel. Does this have the possibility of modifying the gamma or color? Also is this for only K it kat rooms or stock too
Sent from my SM-N900W8 using Tapatalk
Awesome!! So glad to see this here!! And many thanks to OP for the recommendation!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Moose0704 said:
Awesome!! So glad to see this here!! And many thanks to OP for the recommendation!!
Click to expand...
Click to collapse
Moose Mahdi is no joke..
Without Question.. The best ROM for the 8.3.. And now we have a Kernel.. :good: Nice Start to 2014..
Thank You OP for sharing this with us.
reborn90 said:
dyn.Kernel
I want to share with you my own kernel builds. My focus is on performance improvements and energy efficiency.
Things I want to achieve:
- more battery life
- same more performance as stock
- smooth ui / games
- less heat
Highlights:
GPU idle detection:
We don't need high performance if there is nothing moving on the screen. Therefore the kernel will detect when the gpu is offline or at very low load (for litte moving objects, like battery charging animations). This feature is used for nearly all my other modifications.
Advanced Dynamic Scaling:
The interactive governor will now use different values for up_threshold, timer_rate and min_sample_time for every cpu_core and gpu_idle state. If the gpu is busy, the governor will use values for more performance and if it is idle, it will use conservative settings.
The current values, feel free to suggest other.
Code:
/* up_threshold, timer_rate, min_sample_time */
static unsigned int interactive_val[GPU_STATE][ACTIVE_CORES][TUNABLES] =
{{
/* gpu idle */
{100, 40000, 10000},
{100, 40000, 20000},
{100, 40000, 30000},
{100, 40000, 40000}
},{
/* gpu busy */
{90, 20000, 40000},
{90, 20000, 40000},
{95, 20000, 60000},
{95, 20000, 80000}
}};
Dynamic Touchboost:
The touch boost is only active if something is rendered on the screen, that means the boost will pause as long as there is no movement, but it will resume when it is actually necessary. It will double the actual cpu load and calculate the frequency, the maximum is input_boost_freq. This aggressive calculation offers a smooth ui, but it can also save battery, because you will often don't need input_boost_freq when the screen is touched.
New Hotplug Solution:
The load is calculated with the average of all active cores to get the performance we actually need. Most of the time two cpu cores are online to guarantee enough performance for ui interactions. After some time and not touching the screen, only 1 core will stay online to save a bit more battery.
It will use different up and down thresholds for each gpu_idle and cpu core state.
Code:
/* down threshold, up threshold */
static unsigned int hotplug_val[GPU_STATE][ACTIVE_CORES][TUNABLES] =
{{
/* gpu idle */
{0, 70},
{40, 80},
{50, 90},
{60, 100}
},{
/* gpu busy */
{0, 60},
{30, 60},
{30, 70},
{40, 100}
}};
https://github.com/reborn90/android_kernel_lge_v500/blob/dyn/arch/arm/kernel/hotplug.c
Recommended settings (default):
Interactive governor:
dynamic_scaling: true (strongly recommended)
input_boost_freq: 1350MHz
input_boost_freq_duration: 1500ms
Interactive gpu governor:
up_threshold: 60
down_threshold: 25
sample_time_ms: 60
You can use an app like Kernel Tuner for undervolting.
Installation:
- make a nandroid backup first (boot)
- flash .zip via custom recovery (CWM/TRWP)
Github:
https://github.com/reborn90/android_kernel_lge_v500/commits/dyn
MD5
4cbae4bf1f6d39db020a131284d1c7a3 dyn.Kernel-r1-0110.zip
Big thx to:
FranciscoFranco
Faux123
djrbliss
Mahdi786
Hit thanks if you like it.
You can also buy me a coffee.
I'm testing all my builds and use them daily, but I am not responsible for any kind of damage on your device.
The Kernel should work with (need confirmation):
- AOKP
- PA
- SlimKat
- CMB
- other stock based KitKat roms
It does not work with:
- CM11
Not made for V510 (GPE)!
Recommended ROM: Mahdi-Rom
Click to expand...
Click to collapse
can u make a kernel for stock rom? thanks for this btw
So glad for this kernel. Would be ecstatic if gamma adjustments ala faux kernel could be implemented
Sent from my SM-N900W8 using Tapatalk
UV every Step about 50mv looks good
RaiderWill said:
Moose Mahdi is no joke..
Without Question.. The best ROM for the 8.3.. And now we have a Kernel.. :good: Nice Start to 2014..
Thank You OP for sharing this with us.
Click to expand...
Click to collapse
Totally agree! Very happy right now!!
+1 for gamma adjustments and if you can adjust the colors to remove the yellow whites. And a kernel for stock?
Sent from my LG-V500 using XDA Premium 4 mobile app
Any impressions from an actual user?
mzfckr993 said:
Any impressions from an actual user?
Click to expand...
Click to collapse
Yep been running on mahdi. Runs great
Sent from my Nexus 5
Spirit Kernel
This kernel is ONLY for AOSP based ROMs. This will NOT work on the stock Moto roms.
I will update this regularly as I have time and will add new features and fixes as well.
If you have any feature requests or ideas that haven't been seen before, don't hesitate to post it here!!
PLEASE READ
How to report a bug?
Include the following in your bug report:
The ROM you are currently using + a link to the ROM's thread
A log, preferably dmesgs or kmsgs (use Google to find out how to pull these from your device)
The version of SpiritKernel you use (=rx, e.g.r3)
Bug reports not meeting these requirements will be ignored.
NO BUG REPORTS ON EXPERIMENTAL BUILDS!
Features
This Hybrid kernel contains features from great kernel devs with like faux,franco and neobuddy,optimized for titan to make it work.Initially there are less features but I will add much more soon
[*]Based on the Latest CyanogenMod sources
[*]Patched 3.4.107 kernel
[*]Governors: ondemand/userspace/powersave/performance/interactive/IntelliMM/inteliidemand/intelliactive/smartmax/pegasusQ
[*]Hotplug: MPDecision/MSM Hotplug/Intelliplug(default)
[*]Intellithermal v2
[*]DT2W/S2W/S2S Wake controls
[*]CPU Underclocking 192Mhz
[*]GPU OC 533Mhz | UC 100Mhz
[*]Add MSM Hotplug Driver
[*]Asynchronous Fsync extracted from HTC
[*]Sweep2Sleep driver
[*]Dynamic management of timer slack
[*]Slimbus OC thanks to neeobuddy89 and poondog
[*]increase Torch power 20mA
[*]Dynamic management of dirty page writebacks
[*]IO: BFQv7r7/FIFO/SIO/FIOPS/ZEN/VR IO Schedulers
[*]Faux Sound Control 3.2
[*]KCAL v2 by @savoca
[*]USB forced fast charge
[*]Stereo call recording support by skvalex
[*]Powersuspend from Faux and yank555-lu *updated to 1.8 after r8*
[*]Kernel Compression: XZ
[*]psx2usb controller
[*]Use Android device as USB keyboard/mouse
[*]optimized ARM RWSEM algorithm.
[*]Ultra Kernel Samepage Merging {UKSM}
[*]FRandom
[*]Dynamic FSync Control
[*]Added Simple GPU Algorithm
[*]WQ_POWER_EFFICIENT for bettery battery life. Hello Battery!!
[*]ANY Kernel
[*]Kexec hardboot patch for Multirom support
[*]TCP: HTCP/HSTCP/HYBLA/VEGAS/SCALABLE/LP/VENO/YEAH/ILLINOIS/WESTWOOD
Optimizations
[*]Compiled Using UBER 5.0 GCC
[*]Added optimized ARM RWSEM algorithm.
[*]Disable add_random
[*]Pocketmode and deepsleep for dt2w/s2w
[*]Optimized VFP Module
[*]FIx integer-overflow in veno,vegas
[*]Add sysinterface for GENTLE_FAIR_SLEEPERS
[*]NOATIME and NODIRATIME as default
[*]New 99LMK script by @Pizza_Dox
[*]Nvidia Patches to enhance power efficiency.
[*]Sched optimizations
[*]Increase battery level check interval
[*]writeback: increase bdi_min_ratio to 5
[*]block: cfq: merge tweaked tunables.
[*]Wait just 1 second for other CPU to halt
[*]net: combat buffer bloat
[*]PM: Introduce suspend state PM_SUSPEND_FREEZE
[*]Disable -fconserve-stack on ARM v2
[*]Enable power efficient workqueues by default
[*]do not use msm_run_queue_stats
[*]enable/disable cpu-boost via sysfs
[*]softirq: reduce latencies
[*]Built with Ofast flags
[*]Force SELinux permissive
[*]LowMemoryKiller management of non killable processes
[*]Headset High Performance Mode
[*]Allow CPU-supported unaligned accesses
[*]Enable UNALIGNED_ACCESS
[*]enable ARCH_POWER
[*]lower swappiness
[*]vfp: remove double entries
[*]Disable disable crc check for 30% extra performance in IO
[*]Optimized SLUB memory allocator
[*]Optimize Sfck Compression
[*]set sched_mc_power_savings to 2 (moar powarrrrrrr! saving)
[*]readahead to 256
[*]Built with Graphite flags
[*] Enabled Pipe Flag
TO-Do List
IntelliMM-intelliminmax
New Govs and I/Os
Intelliplug 4.0
GPU OC and UC
* Recommended app for tweaking the kernel: FauxControl,Kernel Auditor or TricksterMod
Recommended settings :
Governor: Intelliactive
I/O Scheduler: Fiops or row
TCP Congestion : Westwood
GPU Governor : Simple Ondemand Or Msm-adreno-tz
Hotplug : Intelliplug ( Keep screen off frequency to 787 MHz )
Powersuspend : Hybrid
Simple GPU Algorithm : On
How DO I flash this?
Reboot to recovery.
Install zip from SD Card.
Choose the SpiritKernel-Rx-titan.zip
Insatll and Reboot.
Changelog:
Click Me
Downloads:
Basketbuild
Source:
Github(branch:spirit)
Wiki containing changelogs,settings and more
Antutu Score: http://forum.xda-developers.com/showpost.php?p=59736983&postcount=136
Credits goes to these SUPERHUMAN for Inspiration and support (In no specific order)
faux123
Cl3Kener
slukk
luca020400
savoca
Anas Karbila
hurtsky
pinkflozd
YoshiShaPow
Flashhhh
flar2
And more
XDA:DevDB Information
Spirit kernel for peregrine, Kernel for the Moto G
Contributors
DC07
Source Code: https://github.com/DC07/spirit_msm8226
Kernel Special Features: DT2W/S2S+S2W/FRandom/Powersuspend/Hotplugs/GPU OC/UC/CPU Underclock/GCC 5.0 Compiled and More
Version Information
Status: Stable
Current Stable Version: r3
Created 2015-03-13
Last Updated 2015-04-21
Reserved for Changelogs and Reviews
F.A.Q. - Read this before complaining!
1. My phone exploded, HALP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on pastie.org and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
2. This kernel works on Y or X rom?
A: Doesn't work with ROMs having different ramdisk or any derivates due to their irresponsibility of using a different ramdisk which needs patches that break stock rom users. Use a different rom and don't bother me.
3. OMG BETTARY SUCKZ, IT DEAD IN 45 MINUTAS, HALP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
4. How do I flash this?
A: Reading the OP, theres a reason why I added instructions on it.
5. What is a data loss? Did I just had one?
A: Data loss is simply having the connection cut for X periods of time, usually few seconds. Grey bars means the device is not connected to Google services for some weird reason, but you'll still have internet connection.
6. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it.
Settings recommended by our users: Copied shamelessly from my titan thread
metalrules321 said:
Heres what I use and it gives me exceptionally good battery life and perfomance (may differ for others) /using faux-clock app
1.CPU Hotplug
-Intelliplug (I use fauxclock, so cant find the msm hotplug)
-Touch boost on
-Screen off frequency 787 mhz
-Hysterisis value : 8
-Profile : Ecoconservative
-Threshold value 350
2.Thermal Manager
-Intellithermal
-Frequency Throttle temp; 70
-Core throttle temp: 65
3.GPU manager
-Governor: msm-adreno-tz
-simple gpu algorithm
-gpu clock:320
-Simple governor (laziness); 5
-Ramp Threshold: 5
4. IO scheduler
-ROW (for both emmc and sd)
-Read ahead :1024
-Entropy: off
5.Memory Manager
-Zram: Off
-All the other options on
- Swappines:80
-VFS cache pressure : 120
-Dirty ratio:20
-background ratio:5
6.Same page merge
-Intelli ksm enable
-Activation treshold :24
-Cycles per activation 3
-Pages to scan:400
-Scan delay interval :500
7.Battery Control
-Throttling - On
-Temperature threshold :45
-Throttle frequency:787
8.Miscellaneous
- Powe suspend mode: Userspace
-powesuspend: On
-Dynamic file sync: on
-TCP congestion control:Westwood
*Sorry for an awfully long post *:silly:
Click to expand...
Click to collapse
Great! I will test it today if I can. This is for lollipop right?
rodsayd said:
Great! I will test it today if I can. This is for lollipop right?
Click to expand...
Click to collapse
Yes.AOSP/CM based roms only! No stock
Wow
Loved the features! Great work mate! :good:
Gr8 to see a kernel
Do tell me if u have any problems!!
it is possible to have cpu overclock for gaming please
I cant find avy kernel with working oc for cpu , just a little be very nice if is possible thank
Continu good work sorry my bad english
DC07 said:
Spirit Kernel
This kernel is ONLY for AOSP based ROMs. This will NOT work on the stock Moto roms.
...
Click to expand...
Click to collapse
Would you add the intelliactive governor and the RAW IO? Whille keep the Intelliplug out?
Great Kernel
Excellent! Thanks to @DC07 for your great job!
I hope greats news in the future! :fingers-crossed:
Nice work - thanks for that! I really appreciate the minimum frequency and OndemandPlus Nevertheless I got a bug which prevents my phone from going into deep sleep.
Can anyone confirm or provide a fix?
BlueFlame4 said:
Nice work - thanks for that! I really appreciate the minimum frequency and OndemandPlus Nevertheless I got a bug which prevents my phone from going into deep sleep.
Can anyone confirm or provide a fix?
Click to expand...
Click to collapse
I didn't encounter any problems with the phone going to deep sleep when I tested it bro, I did have problems with the headphones not working but it got fixed... Did you check with WakeBlocker to see which app(s) are not letting it go to sleep?
hhrokarvi said:
I didn't encounter any problems with the phone going to deep sleep when I tested it bro, I did have problems with the headphones not working but it got fixed... Did you check with WakeBlocker to see which app(s) are not letting it go to sleep?
Click to expand...
Click to collapse
So I let my phone settle overnight and it goes into deep sleep now. The causing wakelock was PowerManagerService.Wakelock which is now gone. Looks like some app went nuts - thanks for your support, mate!
Just want to know if it's work for KK rom and specially for slim rom in 4.4.4?
Thanks
patgou.007 said:
Just want to know if it's work for KK rom and specially for slim rom in 4.4.4?
Thanks
Click to expand...
Click to collapse
It works on CM based ROMs.. Won't hurt to give it a try thou
Right to make a try but before, just want to be sure that this kernel is for kit kat rom.
patgou.007 said:
Right to make a try but before, just want to be sure that this kernel is for kit kat rom.
Click to expand...
Click to collapse
I guess since 99% of us are already on Android 5.x.x nobody can answer that question, make a Nandroid or use Flashify and backup your current kernel,
if it does not work or behave well you can simply restore your backup/kernel backup and report if it works or not, for other users
cheers
Right. I 'll try later and report. Thanks
Damn, this Kernel is really noice !
I tried it on BlissPop v3.0 - well this ROM is amazingly fast and awesome out of the box but with this Kernel i feel a slightly performance boost.
I had also some little micro animations lags here and there, with this Kernel, they are completely gone and my device is flying as * like never before on Android 5. :good:
One thing though, WIFI does not work, the button to activate it is simply grayed out.
Regards
gr3ud said:
One thing though, WIFI does not work, the button to activate it is simply grayed out.
Click to expand...
Click to collapse
judging by your screen shot, your phone may be in airplane / battery save mode cause low battery, and maybe thats why your wifi may be disabled ?
Hastaloego said:
judging by your screen shot, your phone may be in airplane / battery save mode cause low battery, and maybe thats why your wifi may be disabled ?
Click to expand...
Click to collapse
WiFi still works in Low battery mode, it just restricts the background data from the apps. He is also not in Airplane Mode because we can see full signals for the SIM Card, and it would have been an airplane logo in place of that.
I've tested it too, No WiFi but other stuff works perfectly, not to mention the performance is also good.
Extended kernel, for Android 9.0 ROM's (ks01lte).
Disclaimer:
use this kernel at your own risk. Flashing it without any knowledge of what you're doing may brick your device. I'm not responsible for any software/hardware damage.
Click to expand...
Click to collapse
only Pie is supported.
Features/Changelog:
v1
built with 4.9.x-sabermod GCC toolchain
* Custom CPU governors: Nightmare, Alucard, and Intelliactive.
* GPU: Adreno idler by arter97 disabled by default for better responsiveness, Simple GPU governor by faux123.
* Sound Control V3.
* Screen: KCAL support for post processing control [v2].
* Custom Schedulers: Fiops, Fifo, VR, SIOPlus, Tripndroid, ZEN.
* USB/AC Fastcharge V1.3.
* Optimizations: reducing the amount of debug logs!!, add clean Ramdisk files.
v1.5
* Built with the Bleeding edge GNU GCC 8.2.1
* BACKPORT: Power Efficient Workqueues from Kernel 3.10
* Add Link Time Optimization support v3
* CPU Underclock and Overclock: 268MHz to 2496MHz
* GPU Underclock and Overclock: 100MHz to 600M
* Add New Custom CPU governors: Elemental-X and zzmoove.
* Enable KSM and and support for UKSM
Downloads
MEGA
Thanks to:
@kyasu
@jprimero15 aka Lolz-Kernel
and all the authors of commits in Extended kernel github repo!
XDA:DevDB Information
Extended kernel, Kernel for the Samsung Galaxy S4
Contributors
darkness
Source Code: https://github.com/1bdellatiF/platform_kernel_samsung_msm8974
Version Information
Status: Beta
Current Beta Version: v1.5
Beta Release Date: 2019-07-20
Created 2019-07-20
Last Updated 2019-08-01
Reserved
Reserved +
Bóng tối đang đến
Is there a zzmoove governor in this kernel?
Will test for week with intelliactive governor and NFS magisk module. Will update again after a week. Thanks for the kernel!
AOD fixed by wiping cache and dalvik-cache
@darkness I just found this thread. If you are interested in adding more govs, I have the source to add the following (the below list includes default ones as well) to the Havoc-OS kernel, ie @kyasu LOS Kernel
==================CPU==================
abyssplugv2
arteractive
badass
bioshock
conservative
conservativex
dancedance
darkness
dyna-interactive
electroactive
impulse
intelliactive
intellimm
interactive
interactivex2
lazy
lionheart
nightmare
ondemand
ondemandplus
optimax
pegasusq
performance
powersave
slim
smartassH3
smartmax
tripndroid
uberdemand
userspace
wave
==================IO==================
bfq-iosched
cfq-iosched
deadline-iosched
fifo-iosched
fiops-iosched
noop-iosched
row-iosched
sio-iosched
sioplus-iosched
tripndroid-iosched
vr-iosched
zen-iosched
Click to expand...
Click to collapse
XerusKunZE said:
Is there a zzmoove governor in this kernel?
Click to expand...
Click to collapse
I have seen a lot of people get excited about ZZMove. I think it is a LOT of effort to configure correctly, and if not configured correctly its really bad. And on top of that, I think the true battery saving advantages are over rated as compared to if you get Doze working correctly.
XerusKunZE said:
Is there a zzmoove governor in this kernel?
Click to expand...
Click to collapse
New build is available v1.5
New Custom CPU governors: Elemental-X and zzmoove.
DiamondJohn said:
@darkness I just found this thread. If you are interested in adding more govs, I have the source to add the following (the below list includes default ones as well) to the Havoc-OS kernel, ie @kyasu LOS Kernel
I have seen a lot of people get excited about ZZMove. I think it is a LOT of effort to configure correctly, and if not configured correctly its really bad. And on top of that, I think the true battery saving advantages are over rated as compared to if you get Doze working correctly.
Click to expand...
Click to collapse
Which CPU governor has the minimum battery consumption
darkness said:
Which CPU governor has the minimum battery consumption
Click to expand...
Click to collapse
If you want the ABSOLUTE min battery consumption without compromise, then the Gov does not really matter. Simply set your max CPU to the lowest frequency available.
The real practicality is about selecting a gov that provides YOU the best compromise for how YOU personally use your phone. eg I don't use my phone for gaming, while others might.
My personal experience is that there are two main paths for battery consumption. Screen on and screen off. Screen on is heavily affected by Gov, so the most conservative you can bear. And if you are really committed for small gains, adjust the ramp-up etc
see:
https://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
https://forum.xda-developers.com/showthread.php?t=1767797
https://forum.xda-developers.com/nexus-4/general/guide-android-governors-explained-t2017715
For screen off, then Doze becomes the controlling factor, BIG TIME! I got my phone into doze in 30 sec of screen off, and the battery consumption is brilliant!
To investigate your current state, see:
https://forum.xda-developers.com/showpost.php?p=79135309&postcount=74
That post and the following one shows the difference how my phone is either screen on or in Doze. As compared to a LOS device which sits in maintenance (a higher battery state) for some time after the screen is off.
Doze's deep-idle is your batteries lowest power state, apart from off
PS, not that it means anything, I personally run Tripndroid CPU Gov (and sched) based on how it is described and from personal checks where it appears to like the lower frequencies while still staying very responsive. It jumps around a bit which to me means it is attempting to find the the lowest appropriate freq, while some act more like a min-max, ie not the lowest appropriate, but min when not in use and max when in even the lowest use. I don't notice any lag.
share the link resurrection remix v7.0.2 ks01ltexx
onenett said:
share the link resurrection remix v7.0.2 ks01ltexx
Click to expand...
Click to collapse
is there a please in there somewhere?
https://github.com/ResurrectionRemix/platform_manifest
I tried version 1.5, but it got stucked on splash screen and goes to download mode. Sometimes the system boots fine, but as soon as I shutdown my phone the problem persist again... I tried to reflash my rom and reflash the kernel but the same thing happens. I tried to wipe dalvik cache and cache, still the problem is the same. I'm using Havoc 2.7
XerusKunZE said:
I tried version 1.5, but it got stucked on splash screen and goes to download mode. Sometimes the system boots fine, but as soon as I shutdown my phone the problem persist again... I tried to reflash my rom and reflash the kernel but the same thing happens. I tried to wipe dalvik cache and cache, still the problem is the same. I'm using Havoc 2.7
Click to expand...
Click to collapse
A last_kmsg may help the dev decipher where its failing.
DiamondJohn said:
PS, not that it means anything, I personally run Tripndroid CPU Gov (and sched)
Click to expand...
Click to collapse
I've switched to the Impulse CPU Gov, as it appears to quickly scale down and like the lower frequencies and switch off (hotplug) other cores, while still being very responsive ie I haven't noticed any lags. It was created by the main dev who worked Oreo crDroid.
I *may* of also noticed that when plating music with the screen off, sometimes there was a stutter when using Tripndroid and switching songs, and I haven't had this occur with Impulse, as yet. I also have an app that momentarily switches the screen on between songs, to display the cover art, which I am sure wouldn't help.
It could be a random thing, but it looks good thus far.
just flashed, i do see more options for cpu frquencies but i don't see gpu frequencies like 100mhz or 600mhz???
Latest one cause bootloop in Havoc 9.0
Hi, i has benn flased last reléase, bootlock after reboot, somebody have this bug?
Thanks.
Samsung S4 GT-i9505 Kernel
Hello, can anyone tell me where I can download the most updated Kernel for S4 GT-i9505?
Hello to everyone
Would this kernel work with android 10 ?