After a lot of testing and hours of hard-work, I have developed a kernel based on the latest sources. As the name of the kernel suggests, the primary focus of the kernel is speed and performance. As a result, I have fine-tuned and optimized this kernel to perform in the best possible manner. However, I haven't missed to look into the Battery issues of the phone. A lot of effort has been made to fix unnecessary consumption of battery along with regulated CPU usage. Further, I have worked really hard to include almost all features and fixes so as to make my kernel the most feature-packed All-in-One solution.
Main Features---
Display---
Support for kCAL Colour Control v2.0 (enhances Colour Vibrance and Intensity). (available as a Screen TAB in Kernel Adiutor).
Up-to-date LiveDisplay Driver.
Support for Colour Enhancement (Updated).
Support for HotPlugs---
MSM (Fast Lane Load)
Mako
AluCard
IntelliPlug
ThunderPlug
AutoSMP (Modified and Enhanced for big.LITTLE architecture by ME )
State Helper v2.0 (Modified and Enhanced for big.LITTLE architecture by ME )
MSM mP-Decision (Bricked)
Support for Governors---
Conservative
Darkness
ElementalX
LionFish
IntelliDemand
Interactive
OnDemand
Performance
PowerSave
SmartMax
Hyper
Wheatley
YankActive
AluCard
Support for I/O Schedulers---
FIOPS
BFQ v7r8 with Hierarchical Scheduling
ROW
NOOP
DeadLine
CFQ
SIO
CPU---
Fixed High-Load Average from UnInterruptible Waits (reduces CPU-Load even more in idle state).
Overclocked CPU upto 1.7GHz (big Cluster) and 1.2GHz (LITTLE Cluster) for Extreme Performance (Modified and Enhanced by ME ).
Proper and Uniform Frequency Table Format with 200MHz Gap between each Frequency
Support for Fast-IDLING of CPU (should reduce Power-Consumption a lot).
Support for Power Efficient WorkQueue to reduce Power-Consumption (available in CPU tab of Kernel Adiutor).
GPU---
Support for ADRENO-IDLER algorithm (saves a lot of Battery by reducing GPU Frequency to minimum when there is less load).
Altered GPU-Frequency Table for more Power-Savings without noticeable decrease in Performance.
Memory---
Support for Swap, FrontSwap, and zSwap techniques (improve performance significantly when zRAM is full).
Support for Memory Compaction (improves performance).
Support for CleanCache Driver (improves I/O performance).
Support for zsmAlloc with Page-Table Mapping techniques (improve memory performance).
Support for zRAM with LZ4 compression algorithm (improves performance by saving memory).
Battery---
Support for ARCH_Power to reduce Power-Consumption and increase Battery-Life.
Support for the new PowerSuspend algorithm (improves Battery-Life).
Support for preventing unnecessary WakeLocks (improves Battery-Life). (available under the Misc. Tab of Kernel Adiutor)
Support for ThunderCharge Current Control Driver v2.1 (accelerates Charging by a large margin).
Optimizations and Tweaks---
Based on the latest sources of CyanogenMod (CM) for Yu Yureka/Yureka PLUS.
Disabled CRC-Check for upto 30% faster I/O.
Support for FRandom RNG Driver (upto 50x faster than the default one).
Compiled with UberTC 4.9.4 Optimized for 64-BIT (Uber uses the latest of every component as well as increases the Battery-Life too).
Support for Touch-Boost and CPU-Boost (Updated).
Support for Vibration Intensity Control (available in Misc. TAB of Kernel Adiutor).
Lowest Possible CPU-Usage (a lot of tweaks have been implemented system-wide).
Support for various Wake-Up Gestures including D2W.
Disabled Debug-Info (should reduce the size of the kernel making it lighter).
Support for HMP Aware and Power-Aware Task Allocation (should improve Performance and Battery-Life).
Support for Faux Sound Control v4.1 (Modified and Enhanced by ME ).
Support for a Custom Thermal Driver with Optimized Core Control v2.0 (Better Heat-Management with Flexible Controls, Modified and Enhanced by ME ).
Support for Load Shifter Mechanism (allows more Power-Savings, built by ME ).
The above mentioned features are just the main ones (many are omitted due to word limit), there are many more small technical changes done to improve the overall experience. By the way, the number written after the # symbol in the "Kernel Version" available in About Phone section, tells the number of times I have compiled the kernel. That number alone is an evidence of the amount of time, hard-work and patience I have applied in developing this kernel.
I have tried my best to make my kernel the most polished one. From minor tweaks to major improvements, everything is perfectly done. Moreover, I'll update my kernel whenever a useful feature or new sources come out so as to make you people experience the best and the latest of everything.
I encourage all the people here to try this kernel and squeeze out every bit of performance from our hot-tempered Yu Yureka/Yureka Plus.
Notes---
1. This kernel performs best when used with ROMs based on the latest sources of CyanogenMod.
2. My kernel doesn't requires any other app except for Kernel Adiutor to control the features. Therefore, you people are free to uninstall any other Kernel-Management app. #NoHassles
3. The *NEW word written after a feature indicates that this feature is NOT present in any other Kernel at the time of release.
4. The words 'Modified and Enhanced' written after any Feature indicate that I, myself, have modified that feature to make it more Efficient for our specific Device.
Installation Instructions---
1. It is recommended to clean-flash the kernel if you face any problems such as LED not blinking, unstable frequencies, etc.
2. To download the kernel, head over to the ChangeLogs and Downloads post and select the version of kernel you want.
3. To install the kernel, just flash the .zip using TWRP recovery.
Credits---
1. Google (for everything related to Android)
2. Cyanogen (for Source Code)
3. Varun Chitre (for ThunderCharge)
4. Savoca (for kCAL Colour Control v2.0)
Changelogs and Download Links---
v14.0---
For Changelog and Download Link, refer here.
Recommended Settings---
Note---
1. Use Kernel Adiutor-MOD to apply settings!
Download Link for Kernel Adiutor-MOD---
https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk
2. Always set the Apply on Boot Delay to 20 seconds or more. This is useful to avoid situations in which a certain feature malfunctions everytime after it is enabled at boot and thus results in a bootloop. Setting the delay to a higher value allows to disable that particular feature before it gets enabled.
CPU TAB---
For Balanced Performance---
1. Set Min. to 200MHz and Max. to Max. Available for both Clusters.
2. Interactive/Impulse Governor for both Clusters.
3. Enable Schedule WorkQueues Toggle.
For Battery-Saving and Less Heat---
1. Set Min. to 200MHz and Max. to 1200MHz for big Cluster.
2. Darkness/LionFish Governor for both Clusters.
3. Enable Schedule WorkQueues Toggle.
CPU HotPlugs TAB---
Use AutoSMP if you want more Battery-Life and Decent Performance with Less Heating than Stock Kernel.
State Helper---
1. Max. Core Online (Screen On) at 6 (Useful for Gamers)---
More Battery-Saving and Lesser Heating than Stock Kernel.
2. Max. Core Online (Screen On) at 4 (Useful for Normal Usage)---
Excellent Battery-Saving and Minimal Heating but Lesser Performance than Stock Kernel.
3. Max. Core Online (Screen On) at 2 (Useful for those who don't play Games or do much Browsing)---
Extreme Battery-Saving and Least Heating but much Lower Performance than Stock Kernel.
Thermal TAB---
1. Least Heating Profile---
Enable Core Control.
Temperature Throttle at 45 C.
2. Balanced Heating Profile---
Enable Core Control.
Temperature Throttle at 60 C.
3. Gaming Heating Profile---
Disable Core Control.
Temperature Throttle at 75 C.
Note---
Keep rest of the Thermal Settings at Default Values for all Profiles!
GPU TAB---
Enable Adreno IDLER.
Screen TAB---
Improved Colour Enhancement is in-built in kernel. Still, this is what I use---
LiveDisplay---Night Mode
Minimum RGB Value---32
Saturation Intensity---48
Wake Controls TAB---
As per your own preference.
Sound TAB---
As per your preference.
Battery TAB---
I don't use ThunderCharge as I feel that the stock values provided by YU charge the phone within a decent time. So, again, use as per your preference. However, using Charge Rate beyond 1250mAh may damage the hardware.
I/O Scheduler TAB---
BFQ for both Internal and External Storage.
WakeLocks TAB---
Disable all (to Save Power). However, if you face any problems, then re-enable all.
Misc Controls TAB---
Disable Android Logging.
Init.d TAB---
Enable Emulate Option.
Leave the rest TABs as they are.
Note---
In order to reset settings to default, just Disable the Apply On Boot option of the particular TAB in Kernel Adiutor and reboot the phone.
ENJOY!!!
Reserved.
Shoaib05 said:
Reserved
Click to expand...
Click to collapse
Will this kernel work on stock cm12?????
as currently I'm using Sandy kernel
And getting average battery life and performance ????
gtsfreak said:
Will this kernel work on stock cm12?????
as currently I'm using Sandy kernel
And getting average battery life and performance ????
Click to expand...
Click to collapse
Since the stock CM12 ROM is based on the older sources, I doubt that my kernel will work perfectly. However, you may try and tell me whether it works or not. It would be really helpful.
By the way, which version of Sandy Kernel are you using?
Shoaib05 said:
Since the stock CM12 ROM is based on the older sources, I doubt that my kernel will work perfectly. However, you may try and tell me whether it works or not. It would be really helpful.
By the way, which version of Sandy Kernel are you using?
Click to expand...
Click to collapse
Sandy kernel v1.5
Battery life and performance is average
gtsfreak said:
Sandy kernel v1.5
Battery life and performance is average
Click to expand...
Click to collapse
Try mine if you're unhappy with the results you're getting with your current kernel.
However, I don't think everything will work i.e., LED or Camera but you'll get better performance and Battery-Life, this I can promise.
Support for Android Marshmallow (6.0) has been added!!! Check 2nd post for Download Link!!! (thanks to Hriday Sharma for the commits!)
From now onwards, this thread will not be maintained. Head to Yu Forums to stay updated!!!
Edit---
Thread will be maintained here on XDA too.
Kernel Manager ?
Shoaib many thanks for creating this for us ! God bless you !
Hi Dev Champs !
I am a noob when it comes.to Kernel and Kernel manager. I am a user of Yu Yureka running custom CM13 rom (Created by SantoshM) and im running Velocity 2.0+.
Can you pls suggest the best Kernal Manager in ur opinion. I am using Ex Kernal Manager right now.
Can you also walk me through the steps of setting up the best units for saving battery as well... Of course if thats not a lot of trouble.
download links not working , wanted to check this out with cm13 latest built
Update---
Velocity Kernel v14.0!!!
Changelog---
1. Merged Latest CM's Source Updates into Velocity's Source (contains many improvements).
2. Updated the Linux Base Version to the latest one of 3.10 branch i.e., 3.10.104 (contains BUG-Fixes). *NEW
3. Updated the PowerSuspend Drivers to the latest version i.e., v1.7 (should improve Battery-Life).
4. Added Support for Impulse 2016 Edition Governor (a Balanced Governor for smooth performance and decent Battery-Life). *NEW
5. Added Support for State Notifier Driver (an Optimized mechanism for knowing about Panel's State). *NEW
6. Tuned the LionFish Governor (for better Performance). *NEW
7. Modified the Touch-Boost to be user-controllable (In CM, it is enabled by default and is not user-controllable. This makes the Battery deplete much faster. In my kernel, it is disabled by default and is also user-controllable.). *NEW
8. Improved the Thermal Mechanism (better Heat-Management without much degradation in Performance). *NEW
9. Tuned the Interactive Governor for Efficient operation and more Power-Savings. *NEW
10. Removed Franco's Sound Control (Although, I ported it in the best possible manner, it still wasn't quite upto my standards.).
11. Removed the stock CyanogenMOD Core Control Feature (the current implementation wasn't as Efficient as it should have been in reducing Heat and improving Battery-Life). *NEW
12. Minor BUG-Fixes and Improvements.
Now, the Highlights of v14.0 (unique features which only Velocity Kernel offers for Yu-Devices)---
1. Core Control v2.0---
Built from scratch by me, this version of Core Control is much more efficient than the stock one. In this version, Cores are disabled according to temperature in a much more optimized manner. Further, this Core Control of mine, offers efficient Heat-Management as well as improved Battery-Life. To sum up, this is the best Core-Based Heat-Management Technique for Yu-Devices.
2. Faux Sound Control v4.1---
In this Sound Control, I have used Faux Sound v3.6 as base and on top of it, I have modified, fixed and enhanced the Driver. All of the changes are done by me! I have named this version as v4.1 because I have made 5 changes to the Driver (v3.6 + 5 Changes = v4.1). Coming to the point, this Sound Control is finally the best one. I have worked hours on it to port and fix it in the best way. Thus, now, there is no Low-Volume issue. Further, even the Negative Values work too. Also, the Volumes are boosted without distortion now i.e., higher Volumes can be achieved easily. Also, now, there is a fully functional Enable/Disable Toggle for Sound Control. To bring this feature and make it Compatible with the Modified Kernel Adiutor, I did a very clever workaround too. To sum up, this is indeed the best Sound Control for Yu-Devices with No BUGs.
3. Perfect Core-HotPlug Mechanism---
In this version of my kernel, I have added two HotPlugs, AutoSMP and State Helper. Now, you may ask what is unique about it? Well, I have just used these HotPlugs as base. On top of these HotPlugs, I have done huge modifications, wrote many new Codes and worked on them many hours and I am very happy with the results.
AutoSMP (Modified)---
I have modified this HotPlug to only work as an On/Off Toggle. I have removed all the Options and Codes to make this HotPlug lightweight. Th only function of this HotPlug now is to turn an Octa-Core Soc into a Quad-Core one retaining the HMP or big.LITTLE technique. This will allow much more Power-Savings without degrading Performance as well as lesser Heat too.
State Helper (Modified) v2.0---
I have modified this HotPlug to a great extent. The original State Helper was only meant for Normal Architectures and not big.LITTLE architectures. I worked on this HotPlug to make it support big.LITTLE architecture as well as I have Optimized it to Perform in an efficient way too. Also, I have fixed a critical BUG of this HotPlug. Further, I have removed the unnecessary Codes to make it lightweight. Since I have Optimized this HotPlug for big.LITTLE architecture, this HotPlug now offers the ability to disable the big Cluster completely. Further, this HotPlug also offers the ability to turn an Octa-Core HMP Soc to a Hexa-Core one just like the setup of Snapdragon 650. This Optimization allows for Extreme Power-Savings.
These Core-HotPlug mechanisms offer the best way to Control the Cores for managing Heat and Improving Battery-Life. The best part is that users can control these HotPlugs to find the Perfect Combination according their usage. Also, an important point about these HotPlugs is that they are not Load-Based ones. These HotPlugs don't use CPU-Resources and thus offer Better Battery-Life and Lesser CPU-Usage. To sum up, I have Modified and Optimized these HotPlug in the best possible manner. These HotPlugs are the best ones for Yu-Yureka/Yureka PLUS.
4. Perfect OverClock for Snapdragon 615 1st Gen SoC---
As you all know, our devices seem to use the 1st Gen of SD615 SoC. Probably, that's why, we have 1.5 GHz of Max. Frequency. Further, due to great variations among the same SoC, developing OC to work on every device is a very difficult task. The Max. Frequency that our SoC can run properly is 1.7GHz. Above it, the SoC fails to boot. Further, kernels which were offering OCs above 1.7GHz were containing fake OCs i.e., only the numbers change, not the actual Frequency. Now, after weeks of testing by myself as well as some very good testers, I have managed to find the perfect way of implementing the 1.7GHz and 1.2GHz OC Frequency for big and LITTLE Cluster respectively. In my implementation of the OC, I have applied an Efficient Voltage Distribution technique. This allows to not only consume the least amount of Power but also helps in achieving Perfect Stability i.e., the OC will work on every Device irrespective of Revisions. Further, people who choose to not use the OCs, then the kernel will return to use the stock voltages thus providing the same level of efficiency as the stock kernel.
5. Load Shifter---
As I have already discussed in the Load Shifter's own thread, this feature transfers the Workload from the big Cluster to the LITTLE CLuster. Even the Android Background Processes are forced to run on the LITTLE Cluster with the help of this feature. Since we use LITTLE Cluster for most of the tasks except Gaming, there are considerable Gains in Battery-Life as well as Lesser Production of Heat.
Notes---
1. Due to variations in SoC, the Sound Control will work properly at different levels of Volume for different people. For ex, value 5 of Mic Gain may be too loud for some but too low for others. So, you people have to find out the perfect value for yourselves. By the way, value 10 of Mic Gain is known to be the most suitable for every device.
2. In order to avoid conflicts, I have added a failsafe regarding Core-Control and Core-HotPlug Mechanism. This means, out of AutoSMP, State Helper and Core Control, only one can be used at a time. Even if you try to enable each one of them simultanouesly, they won't get enabled. I have done this to avoid malfunctions.
3. After manually changing the CPU Governor or Frequency, all the Cores will come online even if any HotPlug is enabled. So, you just need to re-enable any HotPlugs you were using in order to disable the Cores again.
4. Currently, AOSParadox ROM and a few other voLTE enabled ROMs too have 100% Core-Load Issue. This leads to more Heat-Generation. Further, High CPU-Usage makes Charging Time a lot slower as well as decreases the Battery-Life by a large margin. Until this BUG is fixed, nothing much can be done to improve upon these areas.
5. Sometimes, enabling Core Control may cause the ROM to hang. In this case, rebooting via ROM doesn't work. So, just press and hold Power button until the phone restarts.
6. When Core 0 gets disabled (due to Core Control or State Helper HotPlug), Adiutor fails to get Frequency and Governor information and hence shows 0MHz in Frequency Panel and Blank Space in Governor Panel. This is normal. In this case, if you need to change Governor or Frequency, then you need to disable Core Control or State Helper HotPlug as the case may be. After this, force close Adiutor and then re-open it. This will make Adiutor get CPU information again.
Recommended Settings are also updated!!!
That's it folks! My best creation till date for Yu-Devices. My aim was always to improve the experience we get from our phones and provide the users with control over everything. Today, I have achieved that goal. This became possible only due to months of hard-work by me and testing-work done by some very reliable testers.
Testers (without these people, developing a Stable and BUG-Free Kernel would be near to impossible)---
dixan43
Bijendra barman
Frozen_Lemon
Ryuk and many others were there, thanks to all of you!!!
Download Links---
For all Lollipop (5.1.1) and Yu-OS ROMs---
https://www.androidfilehost.com/?fid=385035244224394352
For Marshmallow (6.0.x) ROMs only---
https://www.androidfilehost.com/?fid=529152257862677379
For AOSParadox 3.x (6.0.x) ROM only---
https://www.androidfilehost.com/?fid=529152257862677377
Enjoy the most efficient and thoughtfully made Kernel.
Shoiab I always use urs kernel as a daily driver but there is low mic volume issue in V14 and unable to resolve that so back to V13 ...so plz share the recommended settings for V13 ....
I hv yu yureka plus running on RRrom6.0.1.Is this kernel good for the rom
Will it work for my yu yureka plus 5510?I have RR rom installed based on Android MM6.0.1
Does this kernel work for 7.1.1 yureka builds?
Sent from my YU5510 using Tapatalk
Same question here does this kernel work for yu yureka on LineageOS 14.1 ?
Sent from my AO5510 using XDA-Developers Legacy app
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
Shoaib05 said:
Update---
Velocity Kernel v14.0!!!
Changelog---
1. Merged Latest CM's Source Updates into Velocity's Source (contains many improvements).
2. Updated the Linux Base Version to the latest one of 3.10 branch i.e., 3.10.104 (contains BUG-Fixes). *NEW
3. Updated the PowerSuspend Drivers to the latest version i.e., v1.7 (should improve Battery-Life).
4. Added Support for Impulse 2016 Edition Governor (a Balanced Governor for smooth performance and decent Battery-Life). *NEW
5. Added Support for State Notifier Driver (an Optimized mechanism for knowing about Panel's State). *NEW
6. Tuned the LionFish Governor (for better Performance). *NEW
7. Modified the Touch-Boost to be user-controllable (In CM, it is enabled by default and is not user-controllable. This makes the Battery deplete much faster. In my kernel, it is disabled by default and is also user-controllable.). *NEW
8. Improved the Thermal Mechanism (better Heat-Management without much degradation in Performance). *NEW
9. Tuned the Interactive Governor for Efficient operation and more Power-Savings. *NEW
10. Removed Franco's Sound Control (Although, I ported it in the best possible manner, it still wasn't quite upto my standards.).
11. Removed the stock CyanogenMOD Core Control Feature (the current implementation wasn't as Efficient as it should have been in reducing Heat and improving Battery-Life). *NEW
12. Minor BUG-Fixes and Improvements.
Now, the Highlights of v14.0 (unique features which only Velocity Kernel offers for Yu-Devices)---
1. Core Control v2.0---
Built from scratch by me, this version of Core Control is much more efficient than the stock one. In this version, Cores are disabled according to temperature in a much more optimized manner. Further, this Core Control of mine, offers efficient Heat-Management as well as improved Battery-Life. To sum up, this is the best Core-Based Heat-Management Technique for Yu-Devices.
2. Faux Sound Control v4.1---
In this Sound Control, I have used Faux Sound v3.6 as base and on top of it, I have modified, fixed and enhanced the Driver. All of the changes are done by me! I have named this version as v4.1 because I have made 5 changes to the Driver (v3.6 + 5 Changes = v4.1). Coming to the point, this Sound Control is finally the best one. I have worked hours on it to port and fix it in the best way. Thus, now, there is no Low-Volume issue. Further, even the Negative Values work too. Also, the Volumes are boosted without distortion now i.e., higher Volumes can be achieved easily. Also, now, there is a fully functional Enable/Disable Toggle for Sound Control. To bring this feature and make it Compatible with the Modified Kernel Adiutor, I did a very clever workaround too. To sum up, this is indeed the best Sound Control for Yu-Devices with No BUGs.
3. Perfect Core-HotPlug Mechanism---
In this version of my kernel, I have added two HotPlugs, AutoSMP and State Helper. Now, you may ask what is unique about it? Well, I have just used these HotPlugs as base. On top of these HotPlugs, I have done huge modifications, wrote many new Codes and worked on them many hours and I am very happy with the results.
AutoSMP (Modified)---
I have modified this HotPlug to only work as an On/Off Toggle. I have removed all the Options and Codes to make this HotPlug lightweight. Th only function of this HotPlug now is to turn an Octa-Core Soc into a Quad-Core one retaining the HMP or big.LITTLE technique. This will allow much more Power-Savings without degrading Performance as well as lesser Heat too.
State Helper (Modified) v2.0---
I have modified this HotPlug to a great extent. The original State Helper was only meant for Normal Architectures and not big.LITTLE architectures. I worked on this HotPlug to make it support big.LITTLE architecture as well as I have Optimized it to Perform in an efficient way too. Also, I have fixed a critical BUG of this HotPlug. Further, I have removed the unnecessary Codes to make it lightweight. Since I have Optimized this HotPlug for big.LITTLE architecture, this HotPlug now offers the ability to disable the big Cluster completely. Further, this HotPlug also offers the ability to turn an Octa-Core HMP Soc to a Hexa-Core one just like the setup of Snapdragon 650. This Optimization allows for Extreme Power-Savings.
These Core-HotPlug mechanisms offer the best way to Control the Cores for managing Heat and Improving Battery-Life. The best part is that users can control these HotPlugs to find the Perfect Combination according their usage. Also, an important point about these HotPlugs is that they are not Load-Based ones. These HotPlugs don't use CPU-Resources and thus offer Better Battery-Life and Lesser CPU-Usage. To sum up, I have Modified and Optimized these HotPlug in the best possible manner. These HotPlugs are the best ones for Yu-Yureka/Yureka PLUS.
4. Perfect OverClock for Snapdragon 615 1st Gen SoC---
As you all know, our devices seem to use the 1st Gen of SD615 SoC. Probably, that's why, we have 1.5 GHz of Max. Frequency. Further, due to great variations among the same SoC, developing OC to work on every device is a very difficult task. The Max. Frequency that our SoC can run properly is 1.7GHz. Above it, the SoC fails to boot. Further, kernels which were offering OCs above 1.7GHz were containing fake OCs i.e., only the numbers change, not the actual Frequency. Now, after weeks of testing by myself as well as some very good testers, I have managed to find the perfect way of implementing the 1.7GHz and 1.2GHz OC Frequency for big and LITTLE Cluster respectively. In my implementation of the OC, I have applied an Efficient Voltage Distribution technique. This allows to not only consume the least amount of Power but also helps in achieving Perfect Stability i.e., the OC will work on every Device irrespective of Revisions. Further, people who choose to not use the OCs, then the kernel will return to use the stock voltages thus providing the same level of efficiency as the stock kernel.
5. Load Shifter---
As I have already discussed in the Load Shifter's own thread, this feature transfers the Workload from the big Cluster to the LITTLE CLuster. Even the Android Background Processes are forced to run on the LITTLE Cluster with the help of this feature. Since we use LITTLE Cluster for most of the tasks except Gaming, there are considerable Gains in Battery-Life as well as Lesser Production of Heat.
Notes---
1. Due to variations in SoC, the Sound Control will work properly at different levels of Volume for different people. For ex, value 5 of Mic Gain may be too loud for some but too low for others. So, you people have to find out the perfect value for yourselves. By the way, value 10 of Mic Gain is known to be the most suitable for every device.
2. In order to avoid conflicts, I have added a failsafe regarding Core-Control and Core-HotPlug Mechanism. This means, out of AutoSMP, State Helper and Core Control, only one can be used at a time. Even if you try to enable each one of them simultanouesly, they won't get enabled. I have done this to avoid malfunctions.
3. After manually changing the CPU Governor or Frequency, all the Cores will come online even if any HotPlug is enabled. So, you just need to re-enable any HotPlugs you were using in order to disable the Cores again.
4. Currently, AOSParadox ROM and a few other voLTE enabled ROMs too have 100% Core-Load Issue. This leads to more Heat-Generation. Further, High CPU-Usage makes Charging Time a lot slower as well as decreases the Battery-Life by a large margin. Until this BUG is fixed, nothing much can be done to improve upon these areas.
5. Sometimes, enabling Core Control may cause the ROM to hang. In this case, rebooting via ROM doesn't work. So, just press and hold Power button until the phone restarts.
6. When Core 0 gets disabled (due to Core Control or State Helper HotPlug), Adiutor fails to get Frequency and Governor information and hence shows 0MHz in Frequency Panel and Blank Space in Governor Panel. This is normal. In this case, if you need to change Governor or Frequency, then you need to disable Core Control or State Helper HotPlug as the case may be. After this, force close Adiutor and then re-open it. This will make Adiutor get CPU information again.
Recommended Settings are also updated!!!
That's it folks! My best creation till date for Yu-Devices. My aim was always to improve the experience we get from our phones and provide the users with control over everything. Today, I have achieved that goal. This became possible only due to months of hard-work by me and testing-work done by some very reliable testers.
Testers (without these people, developing a Stable and BUG-Free Kernel would be near to impossible)---
dixan43
Bijendra barman
Frozen_Lemon
Ryuk and many others were there, thanks to all of you!!!
Download Links---
For all Lollipop (5.1.1) and Yu-OS ROMs---
https://www.androidfilehost.com/?fid=385035244224394352
For Marshmallow (6.0.x) ROMs only---
https://www.androidfilehost.com/?fid=529152257862677379
For AOSParadox 3.x (6.0.x) ROM only---
https://www.androidfilehost.com/?fid=529152257862677377
Enjoy the most efficient and thoughtfully made Kernel.
Click to expand...
Click to collapse
Shoaib05 please can you make it for Yu yureka on LineageOS 14.1 ?
CAN YOU MAKE IT FULL VOLTE FOR IT CAN DO HD VOICE CALLING BUT VIDEO AND WI-FI CALLINGS ARE STILL MISSING , i searched all threads on XDA but still can't find what i am looking for.
Sent from my AO5510 using XDA-Developers Legacy app
I Clean Flash the Velocity Kernel 14.0 Old but after flashing WiFi and WiFi Hotspot Not Working
How to Solve this Issue
Flashed on CM 12.1
Sent from my YU5510A using Tapatalk
O
Sent from my AO5510 using XDA-Developers Legacy app
Niropa Kernel for the Zenfone 2
this is my kernel based on CM's. the purpose of it is to have a slimmed down minimal kernel with no bloat or pointless placebo add-ons. this is the initial release and I plan on doing alot more work on it
Features
-all governors except interactive and performance ondemand removed
-tcp cubic optimizations
-fs performance optimizations
-bfq scheduler optimizations
-entropy tweaks
-ext4 tweaks
-Selinux set to permissive (completely removed enforcing mode)
-disable tons of logging for better performance
-reduce time to go to sleep
-reduced latency
-disable I/O stats
-readahead tweaks
-sio scheduler added
Downloads
https://www.androidfilehost.com/?fid=24438995911971588 Z00A
https://www.androidfilehost.com/?fid=24438995911971589 Z008
Source
https://github.com/AODP/android_kernel_asus_moorefield
good man
Start of another massive project
finally one more kernel thread
Sent from my ASUS_Z00A using IOS
AICP kernel ?
Very good
the purpose of it is to have a slimmed down minimal kernel with no bloat or pointless placebo add-ons
Click to expand...
Click to collapse
Amen.
This or FlareM what do you guys think....I installed this today and i liked it very much but i use interactive everytime and i was dissapointed to see that there is no interactive governor i hope you will add it soon.
Sent from my ASUS_Z00A using Tapatalk
say99 said:
finally one more kernel thread
Sent from my ASUS_Z00A using IOS
Click to expand...
Click to collapse
Thats what I'm saying, tho thats not to say im leaving Say99 cause he is a fantastic dev with his Flare kernel for Marshmallow but im happy to see more options up online now.
This kernel really makes XOSP 4.1 really fly.
Is this kernel included in the AICP package?
Sent from my ASUS_Z00A using Tapatalk
TOT_tomdora said:
Is this kernel included in the AICP package?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
yup
LiRi2000 said:
This or FlareM what do you guys think....I installed this today and i liked it very much but i use interactive everytime and i was dissapointed to see that there is no interactive governor i hope you will add it soon.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
It's up to you. FlareM has a lot more features. And also you can choose a lot more governors and I/O scheduler with it.
This kernel, is made as close as stock kernel for rock stability. Because of it, this kernel has less features compared to FlareM.
Sent from my Galaxy S4
@Niropa,
Some feedback:
* please enable ondemand governor. That is the default on CM (and will be for more ROMs as they pull in our changes). Right now, I think you are likely causing any build based off of up-to-date CM to use the performance governor.
* forcing selinux permissive, unconditionally, is really not very nice. If you want to choose to make your phone less secure, that's okay. If you want to force anyone using your kernel to abandon the security provided by selinux then that's just not cool.
crpalmer said:
@Niropa,
Some feedback:
* please enable ondemand governor. That is the default on CM (and will be for more ROMs as they pull in our changes). Right now, I think you are likely causing any build based off of up-to-date CM to use the performance governor.
* forcing selinux permissive, unconditionally, is really not very nice. If you want to choose to make your phone less secure, that's okay. If you want to force anyone using your kernel to abandon the security provided by selinux then that's just not cool.
Click to expand...
Click to collapse
Thanks for the feedback , as of now yea it defaults to performance but I'll be changing that to interactive, I don't see any advantage of ondemand over interactive. Also selinux is permissive as default because some apps like viper audio still don't work with it enforcing.
Niropa said:
Thanks for the feedback , as of now yea it defaults to performance but I'll be changing that to interactive, I don't see any advantage of ondemand over interactive. Also selinux is permissive as default because some apps like viper audio still don't work with it enforcing.
Click to expand...
Click to collapse
You haven't tried ondemand recently then... It's pretty sweet now. It's patched up to 4.5-rc4 which includes a lot of performance tweaks and then I added some new code to tone it down a little bit to make it more battery efficient. RIght now my feeling is that it provides a snappier phone and uses less battery at the same time.
Wrt selinux, the problem that I see is that you force it be permissive. That means because some people want to run viper, all people are being forced to permissive with no way to change back to enforcing.
crpalmer said:
You haven't tried ondemand recently then... It's pretty sweet now. It's patched up to 4.5-rc4 which includes a lot of performance tweaks and then I added some new code to tone it down a little bit to make it more battery efficient. RIght now my feeling is that it provides a snappier phone and uses less battery at the same time.
Wrt selinux, the problem that I see is that you force it be permissive. That means because some people want to run viper, all people are being forced to permissive with no way to change back to enforcing.
Click to expand...
Click to collapse
Yea its been probably over a month since I tried ondemand, I know you know your stuff (much more then I do) so I'll add it back and see how it goes. I forced Selinux to permissive a while back because aicp added a built in selinux switcher that would put it in enforcing on every boot so I was getting messages daily from users saying sim/camera etc were broken. I agree with you though preferably I'd want to have it default permissive but the option to make it enforcing for people who want that, next release that's what I plan to do.
please add pocket mode feature
I tried the kernel as far as the heatup goes It's a bit high than stock CM I can say, because in PPSSPP game I had hiccups with the CMs stock but this Interactive doesn't the tradeoff being 2.3GHz most time since CPU spy reloaded with both kernels gave me higher 2.3 speed with this kernel (gaming + normal usage combined) Will observe more....but I think both CM's stock governor and Interactive here should be more efficient, I wonder what's the governor for the Stock ASUS. Btw default governor on performance leads to massive heatup when flashed a ROM upgrade, in TWRP then booting into OS rebuilding ART caches.
Thanks for the slim footprint kernel with AnyKernel format good to flash any kernel on top of it..:good:
Edit : very snappy performance.
Edit 2 : Multitasking apps, background running apps with PPSSPP lags drops frames vs CM stock.
Edit 3 : The earlier fps drop in CM stock I guess it's the thermal throttle kicking in, could be fixed I guess.
Ashtrix said:
I tried the kernel as far as the heatup goes It's a bit high than stock CM I can say, because in PPSSPP game I had hiccups with the CMs stock but this Interactive doesn't the tradeoff being 2.3GHz most time since CPU spy reloaded with both kernels gave me higher 2.3 speed with this kernel (gaming + normal usage combined) Will observe more....but I think both CM's stock governor and Interactive here should be more efficient, I wonder what's the governor for the Stock ASUS. Btw default governor on performance leads to massive heatup when flashed a ROM upgrade, in TWRP then booting into OS rebuilding ART caches.
Thanks for the slim footprint kernel with AnyKernel format good to flash any kernel on top of it..:good:
Edit : very snappy performance.
Edit 2 : Multitasking apps, background running apps with PPSSPP lags drops frames vs CM stock.
Edit 3 : The earlier fps drop in CM stock I guess it's the thermal throttle kicking in, could be fixed I guess.
Click to expand...
Click to collapse
When booting the ROM it defaults to performance mode with stock cm kernel so it wouldn't make any heat difference here, the only difference is after it boots it switches to ondemand and in this kernel it doesn't yet (well it does in version 2.0 I just haven't gotten around to updating z008 version so I haven't updated the thread)