Hi everyone
As title shows, this is a WIP project
(I don't own the device, all builds are blind!)
What is EAS?
Energy Aware Scheduling (EAS) is an enhancement to Linux power management, unifying CPU power control under the Linux kernel. EAS extends the Linux kernel scheduler to make it fully aware of the power/performance capabilities of the CPUs in the system, to optimize energy consumption for advanced multi-core SoCs including big.LITTLE. With EAS, the Linux kernel will use the task load and a CPU ‘Energy Model’ to control task placement to select the optimal CPU to run on.
Google thinks, EAS is the way to go for the future. With this kernel you can get pixel (2) experience even before the pixel (2) is released.
Interesting links for further research:
https://www.xda-developers.com/google-pixel-fastest-android-phone-eas/
https://developer.arm.com/open-source/energy-aware-scheduling
Features
- Full EAS 1.3 implementation (based on EAS Project and LineageOS official kernel)
- Works on HMP ROMS too (you need to use sched/schedutil, HMP stuff are removed from kernel, otherwise you'll face freqs stuck at 100%)
- STune Boost for better battery and performance
- F2FS supported
- Tweaks and changes under the hood
Feel free to try and report your feedback (and logs too)
Download here
Installation
- Reboot to TWRP
- Backup your current boot.img
- Flash the kernel
- Reboot!
Sources here
Credits
@OrdenKrieger
@jcadduono
@joshuous (EAS Project)
And everyone worked for this device and LineageOS bring-up
Changelog
04/11
- Initial release
07/11
- Completely rebased over the latest CAF Oreo Tag (LA.UM.6.6, it *should* work on Pie, but not guaranteed!)
- 3.18.124
- Completely re-done EAS
- New LMK for better RAM managment
- Android upstream for AIO (check if MTP works better or worse than before)
- Better battery and performance
EAS - Energy Aware Scheduling
WIP - Work in Progress
HMP - Heterogeneous Multi-Processing
HAL - Hardware abstraction layer
Do you plan to update the kernel on a regular base?
sklaes said:
EAS - Energy Aware Scheduling
WIP - Work in Progress
HMP - Heterogeneous Multi-Processing
HAL - Hardware abstraction layer
Do you plan to update the kernel on a regular base?
Click to expand...
Click to collapse
When there are major changes to be applied - then yes
Otherwise makes no sense to push update with little to no changes at all
You tested it?
Currently testing it on LOS16. Boots just fine, I'm charging the phone to 100% now to give it a go and I'll be back with some feedback tomorrow. So far everything I've tested works fine.
Not jet, but EAS sounds interesting
Update: installed - currently testing
@sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
[/COLOR @sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
i use this now on dotos oreo with f2fs data.But on interactive the cpu freq stays on max,whatsup with this?
@Predatorhaze: So, you say this kernel works with F2FS data on DotOS Oreo? I literally just tried that a few days ago, but with Hellsgate/Schwifty kernels, no go. But maybe I'll try again now. Thanks for the heads up!
Predatorhaze said:
i use this now on dotos oreo with f2fs data.But on interactive the cpu freq stays on max,whatsup with this?
Click to expand...
Click to collapse
This is an EAS kernel, you need to use sched/schedutil (interactive gov won't work anymore)
AnonVendetta said:
@sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
[/COLOR @sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
Click to expand...
Click to collapse
F2FS is supported, I'll update the thread to explain that better
AnonVendetta said:
@Predatorhaze: So, you say this kernel works with F2FS data on DotOS Oreo? I literally just tried that a few days ago, but with Hellsgate/Schwifty kernels, no go. But maybe I'll try again now. Thanks for the heads up!
Click to expand...
Click to collapse
i have data in f2fs,and yes it boots and everything works till now.
Only is that dolby atmos dont work anymore,dont know why.On previous build with ext4 it worked.
I was confused because the freq on interactive,but already read a answer and that is due its eas kernel.
good we have eas now,i use helix engine also
if anyone got a working dolby atmos,pls let me know
sys01 said:
This is an EAS kernel, you need to use sched/schedutil (interactive gov won't work anymore)
Click to expand...
Click to collapse
ok.untill now everything seems stable.
can you set schedutil as default on next update? and you think about adding kcal feature (saturations etc) and some wakeblocks?
running on dotos 2.5 oreo,magisk 17.3,crimson kernel,f2fs data partition and los universal v2 bootstack
an update to the current lineage OS kernel would be great since September has changed a lot on the go kernel
Your kernel works with AOSP Basis Rom
(have your kernel briefly tested with the havoc 2.0 Rom)
Running this right now on LOS 15, for the entire day, without any issues that I can see. :good:
Used EX Kernel Manager to set governors.
The kernel runs pretty well on Pie, but I think it's pretty aggressively throttled. Once the temp gets to 40°C the LITTLE cores get set to 960 MHz and the big cores to around the same. It's also kind of sluggish when the phone is taken out of deep sleep, and scrolling isn't that great. However, deep sleep works wonders. The discharge rate with screen off is ~0.3% per hour.
Oh, and it may just be me, but playing audio thtough the speakers makes the phone temp get pretty high, which again makes it get throttled and really slow.
Gases said:
The kernel runs pretty well on Pie, but I think it's pretty aggressively throttled. Once the temp gets to 40°C the LITTLE cores get set to 960 MHz and the big cores to around the same. It's also kind of sluggish when the phone is taken out of deep sleep, and scrolling isn't that great. However, deep sleep works wonders. The discharge rate with screen off is ~0.3% per hour.
Oh, and it may just be me, but playing audio thtough the speakers makes the phone temp get pretty high, which again makes it get throttled and really slow.
Click to expand...
Click to collapse
New version coming soon, hopefully this time around should be way more smooth and stable
Also, EAS takes time to make it perfect, but soon or later it will!
Thank you for your work. This kernel is great and really shows the benefits of EAS on an older SOC like the S820. Sure, it needs polishing, but it's a great start
sys01 said:
New version coming soon, hopefully this time around should be way more smooth and stable
Also, EAS takes time to make it perfect, but soon or later it will!
Click to expand...
Click to collapse
For sure, not complaining at all! Just wanted to give some honest feedback in case you wanted to keep tweaking it
sys01 said:
New version coming soon, hopefully this time around should be way more smooth and stable
Also, EAS takes time to make it perfect, but soon or later it will!
Click to expand...
Click to collapse
Thank you very much! Great work
Related
This is a kernel for Cyanogen Mod 12.1, which is based on the EvoMix kernel by Alx31TLse, olivieer and SuperHanss (full credits to them). It is compiled by a Linaro 4.9.3 toolchain, which was optimized for Cortex A9 CPUs (thanks to Christopher83). It has a focus on stability, performance, endurance and overclock-ability (roughly in that order).
It uses the original ramdisk of the installed kernel (thanks to osm0sis), for maximum compatibly in the long run and instant adaptability to most source changes of CM. For now, it probably only works with the very latest unofficial CM12.1 built by qsnc (http://forum.xda-developers.com/showpost.php?p=58006383&postcount=1), due to the introduction of new sensor drivers! It should now works with other CM12.1 based ROMs, like crDroid and PAC, too. Please don't report bugs to qsnc, if you are using this kernel!
Features:
CPU: over/under-clock 1728MHz-192 MHz possible
governors: ondemand(plus), intelliactive, wheatley, ElementalX, ...
GPU: over/under-clock 487MHz-27MHz
governors: simple, performance, powersave, ondemand, conservative
File-systems: ext2/3/4, F2FS, exFAT, NTFS
Schedulers: noob, deadline, row, cfq, bfq, sio, fiops, zen, vr
intelli-plug hot-plugger and power saver (disable MPDecision first!)
Voltage Control (OC/UV)
Sound Control 3.x
poweramp controls (loudness enhancements)
screen colour tweaks
full NEON support
KSM support (Kernel Samepage Merging)
multicore power saver (recommended: enabled)
multirom compatibility
...
Performance: about 10% faster than original CM12.1-kernel with same settings, and some additional 20% speed by using maximum over-clocked frequencies (use at your own risk, every device is different!)
Configuration: Kernel Adiutor (https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor) or PerformanceControl 2.2.6 (http://forum.xda-developers.com/devdb/project/?id=600#downloads)
Install: just flash the attached zip with CyanogenMod Recovery, TWRP (http://forum.xda-developers.com/xpe...very-twrp-2-8-7-0-pollux-polluxwindy-t3187811) or CWM
Install a custom recovery first! The simple CyanogenMod Recovery, which comes with most ROMs, is pretty useless anyway..
Uninstall: re-flash the complete ROM (just re-flashing the original kernel is not enough!)
Sources: https://github.com/EvoMix/kernel_apq8064 (to obtain the defconfig: run "unpigz -cd /proc/config.gz")
Special thanks to Alx31TLse for his help and permission to post it!
Changelog:
2015-08-23:
rebuild using latest optimized Linaro 4.9.4 compiler by Christopher83
re-signed zip-file in order to make it compatible to file signature verification
refuses now to be installed by CyanogenMod Recovery
2015-06-13:
added Pollux version (use official nightly or recent unofficial build)
fixed bug in Sound Control's loudness enhancement, that only one speaker worked
removed inteli-active governor, due to random reboots
2015-05-31:
enhanced boot speed and file-system performance
buggy auto-hotplugger removed
reintroduction of CM's MPDecision (re-flash CM12.1 first, before installation!)
2015-05-28:
initial release
IF INSTALLATION FAILS: If the kernel installation is not working (i.e. installation takes less than 5 seconds and you don't see the new bootlogo), reflash latest ROM, reboot into recovery and try to install the kernel again!
XDA:DevDB Information
EvoMix Kernel for CyanogenMod 12.1, Kernel for the Sony Xperia Tablet Z
Contributors
BlackAfghan, Alx31TLse, olivieer and SuperHanss
Source Code: https://github.com/EvoMix/kernel_apq8064
Kernel Special Features: CM12.1 EvoMix kernel, compiled by a Linaro toolchain, which supports OC/OV, intelli-plug, Sound Control, NTFS, exFAT, F2FS, NEON, KSM, ...
Version Information
Status: Stable
Just installed latest unofficial CM12.1 built by qsnc and this kernel. Seems great so far! Boots a lot faster and kritika plays faster!
I'm trying the overcloacking with Kernel Adiutor set to 1728MHz, I've to 3C widgets installed to monitor temperature and such. Great job!
May seem a bit offtopic but how is the combination intelliplug-ondemandplus?
I think i get some lag with this but it may be a placebo
pangiotis24 said:
May seem a bit offtopic but how is the combination intelliplug-ondemandplus?
I think i get some lag with this but it may be a placebo
Click to expand...
Click to collapse
First, I also used this combination, but experienced some lag, too. It is not necessary to enable intelliplug and I'm not sure if it does any good, since hot-plugging is handled by auto_hotplug. Actually it is not even included in the original EvoMix kernel.
I'm now using only intelliactive, which seems to keep the frequencies low most of the time, while producing only minimal lag.
But maybe it is really a matter of believe..
Teella said:
I'm trying the overcloacking with Kernel Adiutor set to 1728MHz, I've to 3C widgets installed to monitor temperature and such. Great job!
Click to expand...
Click to collapse
The over-clocking capabilities of the EvoMix kernel are rather conservative. I personally use it with maximum CPU and GPU frequencies and even a general -50mV under-voltage, and it seems to be perfectly stable. But no guarantee, every device is different!
Thanks for Kernel !
Multirom Patch inclusive ?
phillipssat said:
Thanks for Kernel !
Multirom Patch inclusive ?
Click to expand...
Click to collapse
Yes, I think so. But please try it out and confirm if it works, since I have not tested it!
BlackAfghan said:
First, I also used this combination, but experienced some lag, too. It is not necessary to enable intelliplug and I'm not sure if it does any good, since hot-plugging is handled by auto_hotplug. Actually it is not even included in the original EvoMix kernel.
I'm now using only intelliactive, which seems to keep the frequencies low most of the time, while producing only minimal lag.
But maybe it is really a matter of believe..
Click to expand...
Click to collapse
Traced the cause.After some time with intelliplug+ondemandplus cores 2,3,4 are permanently disabled.Now i am on intelliactive.Very good so far
I've been using Wheatley and OC 1728 for couple days now. No lag, no heat issues, everything is just peachy!
Hi! Can I use this kernel on my sgp321 Pollux? Tried to flash but get error.
Pollux build will be released later...
New build in first post!
pangiotis24 said:
Traced the cause.After some time with intelliplug+ondemandplus cores 2,3,4 are permanently disabled.Now i am on intelliactive.Very good so far
Click to expand...
Click to collapse
Could you please retry it with the new version?
bgx said:
Hi! Can I use this kernel on my sgp321 Pollux? Tried to flash but get error.
Click to expand...
Click to collapse
If you, or anybody else, is able to re-flash the original CM12.1 kernel via fastboot (in case something goes wrong) and is willing to beta-test, write me a PM!
Yes its kexec patched, but we need to make tab z official to multirom app support, problem is...im running out of time, full time job, 10 months old baby ...kernel is time consumer, thanks to BlackAfgan to maintaining it.
More goodies to come
Tapatatrached from my Yuga
So apparently my tablet hates me. I can't get this kernel to actually flash for ****. I'm using the 5/27 CM 12.1 from the OP. Tried both versions of the kernel. It acts as if it flashes but is much too fast and the kernel version is the same. TWRP 2.8.5.0 from the OP link too.
EDIT: Nevermind I guess. Moved it to the root of the internal and renamed it to a shorter filename and it pushed it properly. No idea what was going on.
DarkStarr said:
So apparently my tablet hates me. I can't get this kernel to actually flash for ****. I'm using the 5/27 CM 12.1 from the OP. Tried both versions of the kernel. It acts as if it flashes but is much too fast and the kernel version is the same. TWRP 2.8.5.0 from the OP link too.
Click to expand...
Click to collapse
Try to format /system, reflash CM 12.1, reboot into recovery again, then flash the latest kernel, please.
Alx31 said:
Yes its kexec patched, but we need to make tab z official to multirom app support, problem is...im running out of time, full time job, 10 months old baby ...kernel is time consumer, thanks to BlackAfgan to maintaining it.
More goodies to come
Tapatatrached from my Yuga
Click to expand...
Click to collapse
Great! Thanks for your excellent work. I wish you all the best for your family! They are more important than any device..
BlackAfghan said:
Try to format /system, reflash CM 12.1, reboot into recovery again, then flash the latest kernel, please.
Click to expand...
Click to collapse
Yea I had done that. It only worked after moving it. I also renamed it at the same time so I dunno which fixed the issue.
DarkStarr said:
Yea I had done that. It only worked after moving it. I also renamed it at the same time so I dunno which fixed the issue.
Click to expand...
Click to collapse
I had the same problem, especially when I flashed an already flashed kernel. I never found the actual reason, but at one point it started to work perfectly all the time..
This is due the pretty complicated process of splitting the original kernel of and recreating the new one in real time, on the device. Normally the developer does this on his PC, and releases a directly flashable combination of the actual kernel and a custom ramdisk.
If other people have the same problem persistently, I may publish an conventional kernel. Please report!
Does this work on "[Rom][UB][5.1.x][SGP311]☆Dirty Unicorns v9.3☆ Unofficial +EvoMix Kernel" rom??
So i tested the latest version.I use intelliplug+intelliactive
No issues so far.Intelliplug is shutting down cores faster which will propably save some juice
Also feels a little colder than before when gaming(asphalt 8)
PixN KernelSo this is the only custom kernel currently available. It's got a custom hotplugging solution and built-in exfat support. The camera fixes are iffy at 2.99b, works in 2.99
This is best used with my custom rom, here, but will work with any AOSP N based rom.
Maybe it'll work on CM devices too but I'm not sure. You may lose recovery on flashing this. Don't panic, just flash Zach's TWRP recovery after the kernel.
Eventually this will see many optimizations.
Built with the regular 4.9 toolchain. (Uber from 3.2)
About the screen dimmer:
You can echo 0 to disable and echo 1 to enable it via the sys path /sys/module/mdss_fb/parameters/backlight_dimmer
Click to expand...
Click to collapse
Or just use ExKernel Manager.
Downloads
In the DevDB Downloads tab. Since for some odd reason DevDB is giving me 410 when I tried to upload the newest kernel, it's uploaded as a 7z file. Extract it and flash/profit.
DevDB is down right now so the latest release is hosted on MEGA (from version 3.4)
The link to the folder is here
Changelogs
Release 1
Initial Release
Added (off by default) brightness dimmer.
Several tweaks for memory management/performance
Some commits for camera management, may or may not help.
Release 2
Interim Release
Added sdcardfs (test exfat behavior?)
Elementalx Governor
Row i/o scheduler
Westwood TCP Congestion Algorithm
Release 2.99
Beta Release
Fixed Camera
Bluetooth temporarily broken
Memory, touch input fixes
Fixed a rare random reboot
Fixed the ipa wakelock and some others
Release 2.99b
Beta Release
Bluetooth still temporarily broken (Will be broken on all 2.99, wait for 3.)
Added the impulse, intelliactive and intellidemand governors
Added proper powersuspend
Also added the Alucard Hotplug
NATIVE EXFAT SUPPORT! (Forgot to enable, sorry)
Release 2.99b1
This is a MAJOR release, but the bluetooth isn't working so still 2.99. Everyone should please use this one for battery and performance. Can't comment on the camera.
Beta Release + Super Stable Battery
Bluetooth still temporarily broken (Will be broken on all 2.99, wait for 3.)
Massive zswap and zram improvements
Fsync on/off support
Frandom
Faster Boot
Adreno Idler
Overclocking
NATIVE EXFAT SUPPORT!
Release 2.99b1b
This is a bugfix release.
Fixed slow charging.
Release 3.1b
This is a major release.
Added color control.
Fully tickless.
Bunch of other stuff.
FIXED BLUETOOTH!!
Rebuilt kernel for single sims with an older config to hopefully fix the SD Card (Needs testing)
Release 3.1b
This is a major release.
Built with Uber.
Also with Clang optimizations.
Rebase config to stock to fix bugs.
Added CPUQuiet.
Release 3.3
This is a major release.
Built with Uber 6.
Bunch of optimizations.
Added Nightmare, Darkness, Chill governors.
Added Alucard Boost.
Also added the Thunderplug Hotplug.
There's a new fiops interactive i/o scheduler.
A lot of wakelocks have been exposed but don't disable them and start filing bug reports, they're as per user discretion.
Release 3.4
This is a major release.
Fixed the Optimizations
More Wakelocks
Updated sources to reflect latest upstream additions
Might have fixed Bluetooth disconnects
Release 3.4
This is a major release. Go for it. It's on DevDB
Lots of Optimizations
Uses Power Efficient Workqueues
Added ARM64 cpuidle
Fixed Zen_interactive
XDA:DevDB Information
PixN Kernel, Kernel for the Sony Xperia Z5
Contributors
HaoZeke
Source Code: http://github.com/HaoZeke/kernel
Kernel Special Features: Camera, Dimmer, Sdcardfs, Overclock, Adreno Idler, Frandom, exFAT
Version Information
Status: Beta
Current Stable Version: 3.3
Stable Release Date: 2016-12-25
Current Beta Version: 3.5
Beta Release Date: 2017-01-12
Created 2016-11-16
Last Updated 2017-01-11
The e6653 kernel will be uploaded in a few hours...
HaoZeke said:
The e6653 kernel will be uploaded in a few hours...
Click to expand...
Click to collapse
Couldv you add exfat support?
albertobom said:
Couldv you add exfat support?
Click to expand...
Click to collapse
Sure, but I think that also needs the rom to specifically add the module too..
(I'll add that to the linked rom)
@HaoZeke, I have been using your rom for almost 2 days now. It is much similar to the other AOSP Nougat. In both the cases, the battery drains fast. Does not even last half a day. The UI is not very smooth. The touch also needs some work on it.
ganeshbiyer said:
@HaoZeke, I have been using your rom for almost 2 days now. It is much similar to the other AOSP Nougat. In both the cases, the battery drains fast. Does not even last half a day. The UI is not very smooth. The touch also needs some work on it.
Click to expand...
Click to collapse
Ok... Did you try the new kernel? The latest version (coming) has elementalx as the governor (enable by kernel auditor mod)..
My battery seems to do ok with the suggestions in the op...
Touch seems ok too.. Actually I build multiple times a day, it's possible an issue sneaked in.
The main reason for this rom is basically the native substratum support..
Does your substratum app show substratum or substratum legacy? In the uploaded release 1 for e6653 there was a small bug which was fixed for 1.1
EDIT:- I'm grateful for the feedback but this thread is for the kernel and related issues... Please post in the right thread...
HaoZeke said:
Ok... Did you try the new kernel? The latest version (coming) has elementalx as the governor (enable by kernel auditor mod)..
My battery seems to do ok with the suggestions in the op...
Touch seems ok too.. Actually I build multiple times a day, it's possible an issue sneaked in.
The main reason for this rom is basically the native substratum support..
Does your substratum app show substratum or substratum legacy? In the uploaded release 1 for e6653 there was a small bug which was fixed for 1.1
EDIT:- I'm grateful for the feedback but this thread is for the kernel and related issues... Please post in the right thread...
Click to expand...
Click to collapse
Sorry for posting in the wrong section. I recognized this after posting, so left it at that.
I am contnuing this in the right section.
Latest version uploaded for both variants. Extract the 7z and fastboot (or twrp) flash the kernels. This release fixes camera issues.
Could e6653 users with sdcard issues please test this kernel?
albertobom said:
Couldv you add exfat support?
Click to expand...
Click to collapse
Added exFAT support...
HaoZeke said:
Added exFAT support...
Click to expand...
Click to collapse
I will wait for a full flashable zip file with your amazing rom and kernel.
Keep up the amazing work.
albertobom said:
I will wait for a full flashable zip file with your amazing rom and kernel.
Keep up the amazing work.
Click to expand...
Click to collapse
Actually a full flashable version isn't currently a priority, since actually the system.img is a bit large to be zipped (cuz of the addition of gapps).
Eventually I'll start zipping the kernels, but again, not a priority..
It should be easy enough to set up.
First download the latest system.img from the ROM thread.
Then get the latest kernel here. (or whichever feature-set you want)
Also grab the recovery.
Put the phone in bootloader mode.
fastboot flash boot boot.img (or whatever the kernel is called)
fastboot flash recovery recovery.img
fastboot flash system system.img
Hey the latest build is up for anyone interested... This might be the last release for a while...
I feel like it's significantly improved... The camera needs work and some other bugs...
Battery life is around 1-1.5% idle.
Testers please post feedback.
@HaoZeke i flash the rom yesterday and the kernel. For me everything was working fine except the camera, whis is upside down. I like the rom, very smooth, i cant tel the battery cause i have 12 hs with it. The kernel you put for test for me is working fine. This kernel will work on CM?
Zaisesl said:
@HaoZeke i flash the rom yesterday and the kernel. For me everything was working fine except the camera, whis is upside down. I like the rom, very smooth, i cant tel the battery cause i have 12 hs with it. The kernel you put for test for me is working fine. This kernel will work on CM?
Click to expand...
Click to collapse
Excellent, I'm glad the test kernel is working, could you try 2.99b1? That has many battery and performance fixes, the older kernels were giving me around 2-3% battery usage per hour, with the new one it's 1-1.5%..
CM I'm not sure, it should maybe work with cm-14.0 but cm-14.0 has been depreciated in favor of cm-14.1 ...
I don't know if there is a cm14.0 for the Z5..
By the way, if I may ask, why are you interested in CM ? Any particular feature?
I ported substratum on AOSP since the cyanogen theme engine wasn't ready for nougat...
So I was wondering if there was anything else people particularly wanted...
HaoZeke said:
Excellent, I'm glad the test kernel is working, could you try 2.99b1? That has many battery and performance fixes, the older kernels were giving me around 2-3% battery usage per hour, with the new one it's 1-1.5%..
CM I'm not sure, it should maybe work with cm-14.0 but cm-14.0 has been depreciated in favor of cm-14.1 ...
I don't know if there is a cm14.0 for the Z5..
By the way, if I may ask, why are you interested in CM ? Any particular feature?
I ported substratum on AOSP since the cyanogen theme engine wasn't ready for nougat...
So I was wondering if there was anything else people particularly wanted...
Click to expand...
Click to collapse
I will give a try tonight. I line cm cause allways works very good for me. Mm.. I like you dont need to flash supersu to get root. But with your rom and cm. There is no diference. Just cm is 7.1 and yours 7.0. I really like both, the only thing i dont like and more useful for me are camera and fingerprint, which both arent working. I will test the new kernel and will tell you in a few hours. Thanks!
Zaisesl said:
I will give a try tonight. I line cm cause allways works very good for me. Mm.. I like you dont need to flash supersu to get root. But with your rom and cm. There is no diference. Just cm is 7.1 and yours 7.0. I really like both, the only thing i dont like and more useful for me are camera and fingerprint, which both arent working. I will test the new kernel and will tell you in a few hours. Thanks!
Click to expand...
Click to collapse
I'm glad the rom is working well... Actually hold off the kernel, in a short while I'll upload another (really the last for a few days)
Actually the sony sources for 7.1 aren't ready since sony uses 3.18 as a Linux kernel base...
The integrated su I was planning to add for the next rom release..
I used to be a huge cm fan but recently I feel cm has left supporting sony phones.. So.. I switched to aosp
HaoZeke said:
I'm glad the rom is working well... Actually hold off the kernel, in a short while I'll upload another (really the last for a few days)
Actually the sony sources for 7.1 aren't ready since sony uses 3.18 as a Linux kernel base...
The integrated su I was planning to add for the next rom release..
I used to be a huge cm fan but recently I feel cm has left supporting sony phones.. So.. I switched to aosp
Click to expand...
Click to collapse
Yes, al cm roms are unofficial. I like aosp and cm cause the battery was allways better. But i do love stock for the camera, fingerprint and stability. And im allways changing roms. I like your aosp rom. For now is very stable. When can i try the kernel i will tell you. Thank!
Camera fix out.
New release fixing the charging.
Here's my release of a slightly modified kernel for Zuk Z2 Pro. It's all somewhat basic, but still, maybe someone is interested.
void3.5(oc): Old AEX4.5 Android 7.1 Nougat
void5.1bat is only for AEX 5.3.
void5(oc/ocx) for AEX 5.4 <= 0411
void5ocx-mracar: Special version for Cosmicos and RR before full treble (before April 18)
For AEX 5.4-0418 and similar full-treble vendor-partition-enabled ROMs (RR working!) use void5.4.
max GPU frequency raised from 624Mhz to 653MHz (710 for ocx-Edition)
Actually I wouldn't consider this as an overclock because 653Mhz is default for Snapdragon 821, which also has Adreno 530 GPU. Yields around +2-3k in Antutu 3D score, if you're not hitting temp throttling. For that, I've included a modified thermal-engine.conf, which simply makes sense because the default limits are ridiculously low imo. There is no danger involved anyway because there are additional kernel/hardware mechanisms in place to prevent serious overheating. In fact, thermal-engine.conf can be empty (like on RR), but I'd say it's a good idea to keep it in place and prevent the phone from getting uncomfortably hot to touch. It does get warm now though!
Westwood+ TCP congestion algorithm (default)
Supposedly superior for moblie devices, but well, who knows. This had to be benchmarked and profiled in great detail, which is a difficult thing to do. I've made it default anyway, mainly because it seems to be popular and I cannot notice any negatives so far.
Zen I/O scheduler (from dorimanx OP3T kernel)
As above, hard to quantify. But I don't like CFS/BFQ for mobile devices and am in fact leaning towards Deadline, which is also included. Kernel defaults to ZEN nevertheless, but note that this is probably overwritten by the ROM's custom startup scripts. Check with kernel tools like "Kernel Adiutor" and change to Zen if you want to give it a try.
(But beware of Kernel Adiutor - it doesn't quit cleanly and hogs cpu, at least sometimes. Check with some task manager app like "System Panel" and kill it!)
F2FS enabled (untested!)
People seem to be keen on F2FS, so I thought, why not include it. Note that AEX builds from 0825 onwards also have this by default. Untested, because I don't have any F2FS partitions. Might try it in the future though - certainly makes sense.
Cleanup kernel config / Optimize build options
Remove unecessary kernel config options, optimize build, silence debug syslog output.
Ignore specific min CPU frequency request from userspace
Well, yes, totally stupid. But I couldn't find any other way to "disable" AOSP CPU-boost on touchscreen interaction (or whatever it is called). I don't like this feature - we have input boost in the kernel for that. Trying to control CPU freqs from userspace is just no good idea imo.
(Actually... I'd suggest disabling kernel's input boost also. CPUs are fast, even the small cores, and there shouldn't be any noticable lag. And if so, tune/optimize scheduler and/or governor instead.)
This change certainly helps with battery life, but how much exactly... I don't know.
Voltage Control (from optimumpr)
Added voltage control through sysfs interface (/sys/devices/system/cpu/cpuX/cpufreq/UV_mV_table). Use for example Kernel Adiutor to tweak, but beware, undervolting _together_ with overclocking does not play well on this device.
Overclock-Xtreme-Edition (ocx)
CPU is raised to 1.80/2.32 GHz and GPU to 710 MHz (!). Bus speeds are also slightly increased and performance should be a bit better than what the small increase in pure CPU-speed might suggest.
Note that the ocx-kernel is really borderline and certainly depending on the specific phone. If it doesn't boot, blue-led-of-death, and/or random apps are crashing, just use the normal oc-edition. The difference is not that big and battery life of ocx is somewhat worse. This is just for fun!
Underclocked aka battery-optimized edition (bat)
CPU underclocked to 1.4/1.92 per default, GPU 510Mhz. Underclocks can be disabled on runtime, enabling 1.67/2.23 CPU and 653 MHz GPU, which is still oc'd compared to stock, but lower than ocx. To disable underclock:
Code:
echo 0 > /sys/module/msm_performance/parameters/void_underfreq
Big thanks to all involved kernel devs and especially davidevinavil for maintaining Z2 Pro for AEX. :good:
UPDATE 20180418 - void5.4bat - void5.4ocx - AEX/RR full treble with vendor partition
UPDATE 20180402 - void5.1bat Underclocked - AEX 5.3 only!
UPDATE 20180324 - void5oc - void5ocx
UPDATE 20170916 - void3.5 - void3.5oc - For AEX 4.5
3.3 adds a more extensive "tuning"-script, located in /system/etc/void_tuning.sh. This is executed after boot and activates the default profile qpwr. Here's a list of the available profiles with a short description:
qpwr: Goal is congesting tasks on the silver cores, kicking in the bigger cluster only when more capacity is needed. All this with focus on prolonged battery life. (default)
qperf: Somewhat similar to qpwr, but with focus on performance. Freqs ramp up faster and schedulers generally act more "quickly". You can use this for benchmarks, should give the best results, but in real life usage I think the benefits are really non-existent.
qmix: No, this is _not_ intended to strike a balance between pwr/perf. Instead, the idea is to distribute the load evenly across all cores, effectively keeping freqs on a lower level on average. I'm not sure yet how this turns out with regards to battery life, but on SD820/821 it might be a valid strategy. You know, power requirements for the golden and silver cores are about equal for any given freq and both are (nearly) equally efficient. A point against this strategy might be, at least in theory, that esp. the golden cores are more frequently prevented to enter deep sleep states, even during light usage. But well, I'm not sure how big the impact on battery life really is and whether the non-linear power characteristic of these cores make up for it. I am running/testing qmix myself right now...
Currently this is not working. Still trying to figure out how to run the script automatically on boot for these 8.1 ROMs. Ideas?
My suggestion as of now is to run the script manually. There might be some apps helping with that. /system/etc/void_tuning.sh. Just execute it.
BACKUP YOUR DEVICE BEFORE FLASHING THIS PACKAGE! (use latest TWRP for Oreo ROMs!)
I CANNOT GURANTEE IT WILL WORK UNDER ALL CIRCUMSTANCES, ESPECIALLY WITH PREVIOUSLY MODIFIED BOOTPARTITIONS / RAMDISKS / WHATEVER !!!
Kernel source: https://github.com/virtvoid/android_kernel_zuk_msm8996-1
Kernel source: https://github.com/virtvoid/android_kernel_zuk_msm8996-5
---
Other things worth mentioning:
o void5.4ocx Antutu 7.0.6 score on an idle AEX5.4-1704 system is expected to be around 172k, +- 2k. If not, then there's something hogging cpu. Try a reboot, let it settle down and/or check with some task manager app if you still cannot reach these scores.
CHANGELOG
20180418 void5.4ocx - void5.4bat
o Full Treble with vendor partition
o ocx-edition + bat-edition
o switched to cosmedd's kernel base (latest caf updates)
20180324 void5oc - void5ocx
o Linaro GCC 7.2.1
o oc-edition + ocx-edition
o DD3Boh kernel base
20170916 void3.5 - void3.5oc
o Linaro GCC 6.4.1
o Normal + OC-edition
o lots of small patches, mainly battery-related (see Github)
20170905 void3.3
o Hopefully fix camera slomo issue
o more extensive void_tuning.sh script
o drop series 1/2 kernels for now
20170830 void3.2
o Enable Qualcomm HMP scheduler
o some scheduler tuning (/system/etc/void_tuning.sh)
o Enable cpu overclocking as default
20170827 void1.2 - void2.2 - void3.1
o void1.2: Based on AEX kernel 0810 (and prior?)
o void2.2: Based on CallMESuper kernel from AEX 0820, completely different source
o void3.1: Based on AEX kernel 0825, which is somewhat of a rollback/remake/enhancement of 0810, afaict.
o update each branch to latest version
o Voltage Control
20170826 void2.1
o Tone down kcal default saturation a bit
o Linaro GCC 5.4.1 toolchain
o Optimized CFLAGS
o Add (back) a few config options
20170824 void2
o initial release
Thank you ! I already flashed it and it's working perfectly on AEX last version.
I'm thinking to keep your kernel definitively.
Bryandu13 said:
Thank you ! I already flashed it and it's working perfectly on AEX last version.
I'm thinking to keep your kernel definitively.
Click to expand...
Click to collapse
Thanks, great to hear. Have you tried enabling CPU overclocking?
void23 said:
Thanks, great to hear. Have you tried enabling CPU overclocking?
Click to expand...
Click to collapse
Yeah, It's the 1st thing I did and it's working normally
Envoyé de mon Z2 Pro en utilisant Tapatalk
Downloading, I want test it on RR 5.8.3 F2FS data and cache!
Ninnix96 said:
Downloading, I want test it on RR 5.8.3 F2FS data and cache!
Click to expand...
Click to collapse
Great, that's interesting. Tell us your findings!
void23 said:
Great, that's interesting. Tell us your findings!
Click to expand...
Click to collapse
bootloop , thanks for your work, I hope to test a new version soon!
Ninnix96 said:
bootloop , thanks for your work, I hope to test a new version soon!
Click to expand...
Click to collapse
Hmm...
I don't have any experience with F2FS partitions, but I'm going to try booting RR 8.5.3 with this kernel later...
void23 said:
Hmm...
I don't have any experience with F2FS partitions, but I'm going to try booting RR 8.5.3 with this kernel later...
Click to expand...
Click to collapse
The only version work with F2FS is 5.8.3 of 26/6
I can report that it works well with lineage-14.1-20170803-UNOFFICIAL so far.
No boot loop or other issues.
Ninnix96 said:
The only version work with F2FS is 5.8.3 of 26/6
Click to expand...
Click to collapse
Ok, I've just checked with 5.8.4, no F2FS partition, boots up fine. So it either has to do with F2FS partitions, and/or this specific 26/6 version of RR.
But testing this is a good opportunity to give F2FS a try. Give me a few days...
void23 said:
Ok, I've just checked with 5.8.4, no F2FS partition, boots up fine. So it either has to do with F2FS partitions, and/or this specific 26/6 version of RR.
But testing this is a good opportunity to give F2FS a try. Give me a few days...
Click to expand...
Click to collapse
No hurry you've done too much
@void23
Thanks for the excellent work. First time antutu crossed the 160k mark with ur kernel.
@void23
One issue though, camera is force closing. Have tried stock cam on AEX, Moto camera, PMS next mod camera and camera zoom FX. All FC.
Anyway to revert to AEX or another kernel short of flashing full ROM?
sanjay0501 said:
@void23
One issue though, camera is force closing. Have tried stock cam on AEX, Moto camera, PMS next mod camera and camera zoom FX. All FC.
Anyway to revert to AEX or another kernel short of flashing full ROM?
Click to expand...
Click to collapse
Just flash ROM again.
But in my case on AEX there is no problem.
Envoyé de mon Z2 Pro en utilisant Tapatalk
Bryandu13 said:
Just flash ROM again.
But in my case on AEX there is no problem.
Envoyé de mon Z2 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
Dirty flashed AEX 2407 after dalvik and cache wipe again and then flashed void kernel, still camera FC
Now flashed AEX without void kernel and camera working.
Maybe some issues with my apps so will try a clean flash and see. Have been having frequent issues with battery drain also recently with AEX 4.5 2010 so flashed back to 2407 which seems to suit my phone better.
sanjay0501 said:
Dirty flashed AEX 2407 after dalvik and cache wipe again and then flashed void kernel, still camera FC
Now flashed AEX without void kernel and camera working.
Maybe some issues with my apps so will try a clean flash and see. Have been having frequent issues with battery drain also recently with AEX 4.5 2010 so flashed back to 2407 which seems to suit my phone better.
Click to expand...
Click to collapse
Sorry to hear about your camera FC'ing. For me, standard AEX cam and cameranextmod7 both are working flawlessly, so I can only suspect it has to do something with your specific AEX installation. A clean reflash of AEX 0820 should solve the issue.
I noticed I got worse pictures with CNMv7 after flashing this; re-flashed ROM without kernel, and now CNM is giving me great shots again.
In all other aspects, the kernel delivered. Scores were 20000-30000 higher than standard AEX.
Thanks for your efforts, working without problem!!!
Antutu 2nd run after reboot...Excellent scores, no OC.
Introduction
Hi everyone, after building the updated los kernel I decided to build a fully custom kernel for our device. So why call it "baddar" ? it was the first name I used for the kernel and its my family name so I kept using it .
in this kernel I'm following these rules :
Security. Always updated to latest available stable Linux & CAF patches.
Stability. Tested first by myself and with many other users before posting it here.
Smoothness. Smooth navigation is must, I hate lag.
Balanced. Performance and battery must be balanced.
Features
Fully based on CAF 3.18 kernel source with latest Linux-stable merged in.
Always updated to latest drivers i.e WiFi, sdfat, etc
Built using latest GCC 9.1.1.
Custom features are heavily based on Franco work.
Vibration intensity control.
Wakelock blocker enabled by default with user control (boeffla wakelock blocker).
Fsync control.
USB fast charge up to 900mA.
Westwood TCP enabled and used by default.
zRAM optimization. (Disabled by default)
Fingerprint boost. Slightly increase the unlock speed and make it respond faster.
Interactive governor tweaks and optimization.
Kcal support.
VR & low persistence support (WIP).
50% battery bug fix.
CAD project support.
Common android kernel fixes and optimization.
Wireguard Support
and many more.
Future plans
Adding more governors & I/O that favor performance / battery when needed.
Attempt to fully fix low persistence issue in daydream.
Making the kernel better after every release.
Telegram Group
Want to test latest betas? feature request? a suggestion ? or report your issue , join my kernel group , I'm much more active there and the group community there is the best.
Join Here
Kernel Version : RC1.2
Linux kernel version : 3.18.140
CAF tag : LA.UM.7.5.r1-05300-8x96.0
last update : 11/7/2019
TREBLE ONLY
Kernel Source
Downloads
Here
Credits
@Unjustified Dev
@OrdenKrieger
@nathanchance
@franciscofranco
@deega
@SaintZ93
All telegram testers who without them this kernel would not possible , Huge thanks to them
reserved for future use (FAQ & Changelog)
Changelog :
Update RC1.2
New in this update :
Merge latest CAF updates for both kernel and wifi (LA.UM.7.5.r1-05300).
Merge latest linux stable updates 3.18.140.
Merge latest aosp msm updates (up to 3 of july)
Add input boost again (disabled by default), enable it for extra performance using EXM or similar apps.
Remove Wireguard (temporary)
Compiled with GCC 10.
thank you, i will try it.
Edit: It works amazing! phone is much cooler than before but remained snappy performance. Awesome!
Great work baddar,thank you! My axon 7 has great performance and battery life again with the new os systems
Testing it right now
Does this kernel support DriveDroid? That's a feature I have been missing for a long time.
SkaboXD said:
thank you, i will try it.
Edit: It works amazing! phone is much cooler than before but remained snappy performance. Awesome!
Click to expand...
Click to collapse
Yep , very smooth and fast without any warm up during normal usage , any improvement in battery life ?
Predatorhaze said:
Great work baddar,thank you! My axon 7 has great performance and battery life again with the new os systems
Click to expand...
Click to collapse
you are welcome , enjoy it.
Fuilares said:
Testing it right now
Click to expand...
Click to collapse
how was your test ?
Kingo64 said:
Does this kernel support DriveDroid? That's a feature I have been missing for a long time.
Click to expand...
Click to collapse
Don't know what is this so I would say no.
@king1990 I went back to stock because aex and other custom ROMs i tried have delay when opening apps and it's very annoying. it open apps significantly slower than stock ROM. I set animations same as stock rom, 0.5x,0.5x and 1.0x. I can disable animations but it will look stuttery. Kernel is good, no question, but it wasn't enough for me to stay on custom rom.
With the current corruption happening on 5.x with GCC9, you're brave to use it. I would wait to know more about the issue first.
SkaboXD said:
@king1990 I went back to stock because aex and other custom ROMs i tried have delay when opening apps and it's very annoying. it open apps significantly slower than stock ROM. I set animations same as stock rom, 0.5x,0.5x and 1.0x. I can disable animations but it will look stuttery. Kernel is good, no question, but it wasn't enough for me to stay on custom rom.
Click to expand...
Click to collapse
No problem here and none of the users who tested the kernel reported that.
geearf said:
With the current corruption happening on 5.x with GCC9, you're brave to use it. I would wait to know more about the issue first.
Click to expand...
Click to collapse
what issue you mean ?
king1990 said:
what issue you mean ?
Click to expand...
Click to collapse
https://bugzilla.kernel.org/show_bug.cgi?id=203573
geearf said:
https://bugzilla.kernel.org/show_bug.cgi?id=203573
Click to expand...
Click to collapse
how is this related to android ?
king1990 said:
how is this related to android ?
Click to expand...
Click to collapse
It's the same kernel and the same compiler.
The corruption may only be limited to bcache, but maybe not.
geearf said:
It's the same kernel and the same compiler.
The corruption may only be limited to bcache, but maybe not.
Click to expand...
Click to collapse
We are using 3.18 kernel and a CAF one so nothing to worry about.
THis should work on RR6 right? I have vendor also but RR6 does not use it if I am remembering correct. anyway I am not getting a boot with RR 6 and I cant figure out why. I was on hellsgate before and i just went back and its booting again. Any ideas Maybe I cant simply flash over hellsgate, annoying.
madhits45 said:
THis should work on RR6 right? I have vendor also but RR6 does not use it if I am remembering correct. anyway I am not getting a boot with RR 6 and I cant figure out why. I was on hellsgate before and i just went back and its booting again. Any ideas Maybe I cant simply flash over hellsgate, annoying.
Click to expand...
Click to collapse
yeah if you get any ROM to boot then you can use my kernel and flash it over any other kenerl
king1990 said:
Yep , very smooth and fast without any warm up during normal usage , any improvement in battery life ?
you are welcome , enjoy it.
how was your test ?
Don't know what is this so I would say no.
Click to expand...
Click to collapse
So after few days I must say, that I got much better performance, but comparing to Hellsgate Reborn kernel battery life is worse.
Fuilares said:
So after few days I must say, that I got much better performance, but comparing to Hellsgate Reborn kernel battery life is worse.
Click to expand...
Click to collapse
well you can't get this performance for free but I doubt the hit in battery life is big.
king1990 said:
yeah if you get any ROM to boot then you can use my kernel and flash it over any other kenerl
Click to expand...
Click to collapse
Ok so any tricks to getting it to boot after flashing over hellsgate?
---------- Post added at 06:25 PM ---------- Previous post was at 06:24 PM ----------
Fuilares said:
So after few days I must say, that I got much better performance, but comparing to Hellsgate Reborn kernel battery life is worse.
Click to expand...
Click to collapse
How did you flash over hellsgate, I could not get it to boot. I cleared cache and no dice, anything else you did?
madhits45 said:
Ok so any tricks to getting it to boot after flashing over hellsgate?
---------- Post added at 06:25 PM ---------- Previous post was at 06:24 PM ----------
How did you flash over hellsgate, I could not get it to boot. I cleared cache and no dice, anything else you did?
Click to expand...
Click to collapse
it does not boot ? which RR are you trying and what vendor ?
Hello,
I started making kernel builds again.
CHECK BELOW FOR IMPORTANT INFORMATION!
YOU MUST USE MIUI Q FIRMWARE PACKAGE FOR THIS KERNEL TO WORK. OTHERWISE YOU'LL END UP IN FASTBOOT MODE FOREVER.
Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs too, thus won't work until Xiaomi releases it's kernel source code.
FLASH THIS BEFORE FLASHING MY KERNEL. I UPLOADED FIRMWARE PACKAGE FOR YOUR CONVENIECE!
DOWNLOAD LINK FOR MIUI Q FIRMWARE PACKAGE
Flashing procedure is standard - through recovery. Magisk is optional, only if you want root.
*big thanks to rama982 for possible insights and some help from his side*
*nathanchance for android-linux stable and helping upstream our kernels*
*franciscofranco for commits that made our phone happier and snappier*
*sultanxda for his beastly development in Android scene and ridiculous understandment in kernels in general*
*also thanks to osm0sis for Anykernel3. Without this, flashing kernels would be a harder process to do*
XDA:DevDB Information
JellyKernelAlpha, Kernel for the Xiaomi Redmi Note 7
Contributors
airidosas252, rama982, nathanchance, Qualcomm, Code Aurora Forums, osm0sis, other developers
Source Code: https://github.com/airidosas252/Xiaomi_Kernel_OpenSource
Kernel Special Features: Stability, latest kernel sources
Version Information
Status: Testing
Created 2019-11-22
Last Updated 2020-02-01
DOWNLOAD LINK FOR GITHUB RELEASES
Due to different kernel base, older releases are irrelevant from now on.
UPDATE: I added a link for MIUI Q firmware package in the OP. Check it out and remember to flash it first before flashing my kernel. Thanks.
-------------------------------CHANGELOG------------------------------
Jelly Kernel Alpha 1.1.1 Hotfix
ALSA: pcm: Add missing copy ops check before clearing buffer (bootloop after voip videocall should be gone now)
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.1 beta release
IMPORTANT INFO! Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs, thus won't work until Xiaomi releases it's kernel source code.
If this kernel is not booting for you (going straight to fastboot mode), you need to use MIUI Q firmware package.
Changelog:
*Bringup for Clang 10 and it's now compiled with Clang 10
*Using LZ4 compression for zRAM
*Forcefully load modules (this should fix Wi-Fi problems on various ROMs)
*Rapid GC for F2FS filesystem
*Added fsync and crc check switches
*kgsl fixes and optimizations included
*Introduce additional NEON accelerated arm64 routines
*cfq io scheduler fixes and optimizations
*Tick rate increased to 300HZ for improved responsiveness
*CPU mask affinity set to 4 cores for improved efficiency
*Enabled F2FS filesystem support with encryption
*F2FS fixes
*Increased slmk's aggression rate to 192MB per app kill
*Enabled Dolby DS2 audio standard
*And more I don't really remember, check commit history for more detailed changes
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.0 beta release (don't use this release, it's deprecated)
*Complete rebase on jasmine's Q tag.
*Linux 4.4.211
*Adrenoboost enabled and set on low parameter
*Workqueques reworked for better responsiveness and lower power consumption
*Small UV for both CPU and GPU
*CPU Bitmasking
*DTB debloat (reduced kernel's footprint)
*LA.UM.8.2.r2-00600-sdm660.0 CAF tag
*Using older Wi-Fi CAF tag for better down/up speeds
And more stuff I don't remember.
-----------------------------------------------------------------------------------------
DISCLAIMER:
-There will be 1-3 kernel builds per week, unless there's nothing I can improve, then builds will be as is.
-Anyone, who has tested it already, give me some feedback in the comments.
-If you get freezes, crashes, restarts, write me up with a attached dmesg, log, anything, that can give me a clue what's wrong. Thanks. Happy JellyKernel'ing ^^
Where is the download link?
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Use the browser - there's a section DOWNLOADS above the thread. There you will find my kernel build. Cheers.
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Here, for short: https://forum.xda-developers.com/devdb/project/dl/?id=32079
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
airidosas252 said:
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
Click to expand...
Click to collapse
Does it support Kcal? Regards :good:
rubentkato77 said:
Does it support Kcal? Regards :good:
Click to expand...
Click to collapse
Yes it does. Look up using kernel manager.
airidosas252 said:
Yes it does. Look up using kernel manager.
Click to expand...
Click to collapse
Thnk you, will flash to test :good:
Is the any chance to get the turbo frequencies on the GPU?
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
tekkaman7 said:
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
Click to expand...
Click to collapse
I believe Qcom left off this frequency just because CPU is already close to some of their flagship SOCs in terms of CPU performance.
Everything in the source code is left done, you just need to modify a code a bit and you have higher frequency. If you want to go any higher, you would need to modify the code a lot more. Tried it and gave up on that.
It could be anything, really.
Moreover, you don't see too many phones using this exact SOC.
P.S. Funny thing though, this OC feels like placebo effect, like CPU is running faster but it's really not.
Think about it, when sdm660 came out, it was between SD821 and SD835 in terms of CPU performance. GPU is more or less the same as Adreno 430.
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
airidosas252 said:
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
Click to expand...
Click to collapse
Thanks for your work, we will waiting :good:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
airidosas252 said:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
Click to expand...
Click to collapse
thank you, downloading. :good:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
xiaomi.lim said:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
Click to expand...
Click to collapse
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
airidosas252 said:
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
Click to expand...
Click to collapse
Overclocked to ? 2.46GHz?
xiaomi.lim said:
Overclocked to ? 2.46GHz?
Click to expand...
Click to collapse
Yes, but I don't think I'll keep the OC for much longer. I really don't see the benefit of it.
Phone is already really fast and snappy.
I did a build with stock clocks and compared it to the OC one. And here's the surprise - there isn't almost any difference.
I fixed several known issues which bugged me a lot and those seem to remedy all of the problems I had.
Moreover, I hate overbloated kernels with features I don't use. I like being clean and compact.
Hi, the sound control (for speaker, earpiece and headphones) available or do you plan to add it in future? They get pretty handy really. I do appreciate keeping the kernel without much bloat though. : D