The default XenonHD, LOS and Carbon kernels don't have as many features. Additionally XenonHD hasn't been updated in a while so flashing this kernel would bring in some security updates too.
[KERNEL][Z017/Z012][TREBLE][P5] Advanced Kernel for Custom ROMs
- Thread starter planet9
- Start date
so, there should be no problem 'dirty flashing' this kernel via TWRP ?
(i.e. no need to wipe data and losing all settings, to flash this kernel? )
EDIT:
i just saw the first post:
i'll try flashing this kernel then.
thanks, planet9 !
Last edited:
You don't have to wipe anything, not even the cache.
Advanced Kernel V0.8 has been released!
Changes:
To change the MAC adress, place the "wlan_mac.bin" file with 644 permissions under /system/vendor/firmware/wlan/prima/.
This is a binary file so it has to be edited with a hex editor. The first six bytes represent the MAC adress.
A sample file can be found here: https://drive.google.com/open?id=1qRA3BJ0naOBPXf89A49FauvNnLXnLxgo
Remove the wlan_mac.bin again to restore your original MAC.
Changes:
- Added ability to change the wifi mac adress via wlan_mac.bin.
- Updated kernel to Linux 3.18.109, CAF Tag LA.UM.6.6.r1-08500-89xx.0.
To change the MAC adress, place the "wlan_mac.bin" file with 644 permissions under /system/vendor/firmware/wlan/prima/.
This is a binary file so it has to be edited with a hex editor. The first six bytes represent the MAC adress.
A sample file can be found here: https://drive.google.com/open?id=1qRA3BJ0naOBPXf89A49FauvNnLXnLxgo
Remove the wlan_mac.bin again to restore your original MAC.
Here's info about all the cpu governers @planet9 has added in the order that they appear in the menu:
Source is the xda post by @Saber
110. Relaxed
Description:
Relaxed is based on chill, and has been altered in order to achieve more gradual frequency boosting providing battery life benefits. Relaxed uses a boost ceiling variable in order to achieve this. Rather than boosting straight to the max frequency, relaxed finds the difference between boost_counter and boost_ceiling, then boosts to max minus that difference. This governor doesn't completely replace chill, but is intended to be used alongside it.*
105. Chill
Description:
A conservative based governor by frap129 (Electron kernel). It's aims to provide more aggressive battery savings while screen is off.
Electron: (as told by @planet9)
Description:
It's a modified version of interactive. It should be more battery-friendly but with a little less performace.
53. Impulse
Description:
An improved version of interactive modified by neobuddy89. Impulse aims to have a balance between battery and performance just like interactive but has some tweaks to save battery.*
32. ZZmoove
Description:
The ZZmoove Governor by ZaneZam is optimized for low power consumption when the screen off, with particular attention to the limitation of consumption applications in the background with the screen off, such as listening to music. The unique feature with ZZmoove is that it has predefined profiles and allows profile switching.*
67. Alucard
Description:
Alucard is based on ondemand but has been heavily tweaked to bring better battery life and performance. It has been known to be battery friendly without sacrificing much performance.
66. Darkness
Description:
It's based on nightmare but more simple and fast, basic configs but very complex structure. It is an updated nightmare gov and improved stability, so far it is quite stable in tests
31. Nightmare*
Description:
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.
52. Yankactive
Description:
A slightly modified interactive based governor by Yank555.lu. It has battery tweaks added onto it so expect better battery life! Based on user reports, this governor behaves more battery friendly than the original interactive governor without sacrificing performance.*
29: IntelliActive
Description:
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. Therefore, it avoids CPU hotplugging.*
Created by Faux
60. Blu_active
Description:
A governor developed by eng.stk (featured in his Code_Blue kernels) based on interactive with upstream caf patches and ondemand governor bits too. This governor is mainly focused on performance like the other things the developer creates but it is also well balanced for gaming and general usage.*
8: Interactive:
Description:
Interactive scales the clockspeed over the course of a timer set by the kernel developer (or user). 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. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. It is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
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.*
Interactive is the default governor of choice for today's smartphone and tablet manufacturers.
5: Conservative:
Description:
This governor 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". The original and unmodified conservative is slow and inefficient. Newer and modified versions of conservative (from some kernels) are much more responsive and are better all around for almost any use.*
1: OnDemand:
Description:
Ondemand is one of the original and oldest governors available on the linux kernel. When the load placed on your CPU reaches the set threshold, the governor will quickly ramp up to the maximum CPU frequency. It has excellent fluidity because of this high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand was commonly chosen by smartphone manufacturers in the past because it is well-tested and reliable, but it is outdated now and is being replaced by Google's Interactive governor.*
6: Userspace:
Description:
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.
4: Powersave:
Description:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
3: Performance:
Description:
The performance governor locks the phone's CPU at maximum frequency.*
Source is the xda post by @Saber
110. Relaxed
Description:
Relaxed is based on chill, and has been altered in order to achieve more gradual frequency boosting providing battery life benefits. Relaxed uses a boost ceiling variable in order to achieve this. Rather than boosting straight to the max frequency, relaxed finds the difference between boost_counter and boost_ceiling, then boosts to max minus that difference. This governor doesn't completely replace chill, but is intended to be used alongside it.*
105. Chill
Description:
A conservative based governor by frap129 (Electron kernel). It's aims to provide more aggressive battery savings while screen is off.
Electron: (as told by @planet9)
Description:
It's a modified version of interactive. It should be more battery-friendly but with a little less performace.
53. Impulse
Description:
An improved version of interactive modified by neobuddy89. Impulse aims to have a balance between battery and performance just like interactive but has some tweaks to save battery.*
32. ZZmoove
Description:
The ZZmoove Governor by ZaneZam is optimized for low power consumption when the screen off, with particular attention to the limitation of consumption applications in the background with the screen off, such as listening to music. The unique feature with ZZmoove is that it has predefined profiles and allows profile switching.*
67. Alucard
Description:
Alucard is based on ondemand but has been heavily tweaked to bring better battery life and performance. It has been known to be battery friendly without sacrificing much performance.
66. Darkness
Description:
It's based on nightmare but more simple and fast, basic configs but very complex structure. It is an updated nightmare gov and improved stability, so far it is quite stable in tests
31. Nightmare*
Description:
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.
52. Yankactive
Description:
A slightly modified interactive based governor by Yank555.lu. It has battery tweaks added onto it so expect better battery life! Based on user reports, this governor behaves more battery friendly than the original interactive governor without sacrificing performance.*
29: IntelliActive
Description:
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. Therefore, it avoids CPU hotplugging.*
Created by Faux
60. Blu_active
Description:
A governor developed by eng.stk (featured in his Code_Blue kernels) based on interactive with upstream caf patches and ondemand governor bits too. This governor is mainly focused on performance like the other things the developer creates but it is also well balanced for gaming and general usage.*
8: Interactive:
Description:
Interactive scales the clockspeed over the course of a timer set by the kernel developer (or user). 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. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. It is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
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.*
Interactive is the default governor of choice for today's smartphone and tablet manufacturers.
5: Conservative:
Description:
This governor 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". The original and unmodified conservative is slow and inefficient. Newer and modified versions of conservative (from some kernels) are much more responsive and are better all around for almost any use.*
1: OnDemand:
Description:
Ondemand is one of the original and oldest governors available on the linux kernel. When the load placed on your CPU reaches the set threshold, the governor will quickly ramp up to the maximum CPU frequency. It has excellent fluidity because of this high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand was commonly chosen by smartphone manufacturers in the past because it is well-tested and reliable, but it is outdated now and is being replaced by Google's Interactive governor.*
6: Userspace:
Description:
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.
4: Powersave:
Description:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
3: Performance:
Description:
The performance governor locks the phone's CPU at maximum frequency.*
Last edited:
Can i use for Lineage 14.1?
Hi I would like to know if I can use these kernels per lineage 14.1.
Thank you
Hi I would like to know if I can use these kernels per lineage 14.1.
Thank you
Can't speak for everyone else but ElementalX is pretty sweetWhat governor do everyone use here?
But we don't have that in this kernel...Can't speak for everyone else but ElementalX is pretty sweet
Advanced Kernel V0.9 is up!
Changes:
Changes:
- Added elementalx cpufreq governor.
- Updated Toolchain to GCC 8.1.1.
- Updated kernel to Linux 3.18.112, CAF Tag LA.UM.6.6.r1-08600-89xx.0.
Good day, i'd installed the oc version of this ak then tried overclock to 2.2ghz the 1st day it works but now everytime itap the 2.2ghz it will automatically clock down to 1.8ghz even the 2.0ghz will not work..
One more thing want to know ,how the fast charge work will it use maximum current (1600mA on my fone 5.2) even if you reach 80% charged? Because when im using the stock rom it will lower the mA to 600mA.
One more thing want to know ,how the fast charge work will it use maximum current (1600mA on my fone 5.2) even if you reach 80% charged? Because when im using the stock rom it will lower the mA to 600mA.
Hello guys, Can this be used on zc520tl? Its basically the same phone but zc520tl is the gold one
NO.
It is only for ZE520KL & ZE552KL.
If you wanna brick your phone, go ahead and flash it.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone