These boot images should work on any LOS-based or CAF-source based ROMs (in theory).
Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
Kernel Information
ROM Target Device: Samsung Galaxy Grand Prime SM-S920L | SM-G530MU | SM-G530M | SM-G530H | SM-G530FZ | SM-G530P | SM-G530T | SM-G530T1 | SM-G530W
Kernel Status: Beta
Project GitHub Repositories: https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
Project GitHub Branch: cm-14.1-experimental
Project Gerrit Review site: https://review.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Bug reports: https://bugs.msm8916.com/
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530M[/B] - [COLOR="DarkSlateBlue"][B]fortunalteub[/B][/COLOR]
[B]SM-G530H (XX)[/B] - [COLOR="DarkSlateBlue"][B]fortuna3g[/B][/COLOR]
[B]SM-G530H (XC)[/B] - [COLOR="DarkSlateBlue"][B]fortunave3g[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
[B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]
Click to expand...
Click to collapse
Features
Code:
[B]
[COLOR="Red"]
* Latest CAF kernel source merged into kernel.
* CPU overclock to 1612 MHz
* GPU overclock to 650 MHz
[/COLOR]
* If you have any (reasonable) suggestions
for anything, tell me.
[/B]
DownloadAll Jenkins builds are testing builds, and as such, are likely to be extremely unstable or unusable.
This goes doubly for these kernels: You know the risks associated with overclocking, and, though stable,
there may be hiccups in the kernel.
Kernel Builds: https://jenkins.msm8916.com/job/Boot_Images/job/Overclocked_Images/job/Samsung_Galaxy_GRAND_Prime/
RSS: https://jenkins.msm8916.com/job/Boot_Images/job/Overclocked_Images/rssLatest
Click to expand...
Click to collapse
Instructions
If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).
You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.
Click to expand...
Click to collapse
Installation via recovery (TWRP)
* Download a recent .tar file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Plug in your phone into your computer, extract the tar file and place the .img to a location on your Internal or External Storage on a device.
* Click Install on TWRP on your phone and locate the img file in the phone.
* Enjoy your kernel.
Click to expand...
Click to collapse
Installation via odin
* Download a recent .tar file from the links above for your device.
* Reboot into ODIN mode [Press Power+Volume Down+Home].
* Plug in your phone into your computer, and open the Odin application, and place the .tar file in the AP slot and flash it.
* Enjoy your kernel
Click to expand...
Click to collapse
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
PLEASE, don't PM @vince2678, as he's busy right now, and your questions can be not answered. PM @kentone instead, write here on the post, or on the telegram group, your questions will be responded as soon as we can Understand that we have family, studies and jobs aside of this project. Thanks for your understanding
XDA:DevDB Information
[KERNEL] Overclocked Kernel for Galaxy Grand Prime [SM-S920L|SM-G530M/MU/H/P/T/T1/W], Kernel for the Samsung Galaxy Grand Prime
Contributors
vince2678
Source Code: https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
Kernel Special Features:
Version Information
Status: Beta
Created 2017-04-16
Last Updated 2017-08-29
Reserved
Changelog
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added support for SM-G530M (fortunalteub)[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the
latest build. This was due to the failure to set a
critical kernel variable at boot because the kernel init
system was not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
mounting and formatting should be working fully.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
Code:
[B][U]14/04/2017[/U][/B]
* [B] [ [COLOR="Red"]ALL[/COLOR] ][/B] [B] Created DevDB project [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built into the kernel. Should
(slightly) improve speed of enabling/disabling wifi. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.14[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]fortuna3g[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] Brightness adjustment is broken[/B]
Thanks!
Reserved.
Great work Vince! Gonna try it soon nd will let you know.
Maybe stupid question
But if CPU overclocked to 1612
It won't be damaged or something
I mean why Samsung didn't make GP stock CPU like this ??
Sorry if its stupid question
But if it won't damage the phone CPU
The performance will increased as hell
abooooood said:
Maybe stupid question
But if CPU overclocked to 1612
It won't be damaged or something
I mean why Samsung didn't make GP stock CPU like this ??
Sorry if its stupid question
But if it won't damage the phone CPU
The performance will increased as hell
Click to expand...
Click to collapse
All processors are put limits, snapdragon 410 goes up to 2.1ghz, but it's like asking the mobile phone does not last a month, Do you use xxu or xcu?
Play4NoobWin said:
No boot in xcu
Got stuck in the samsung logo
Tested in aex 4.0
Click to expand...
Click to collapse
Sorry, my fault. Meant to write 'XXU' instead of 'XCU'.
Will make a build for that soon, keep wacthing the thread.
abooooood said:
Maybe stupid question
But if CPU overclocked to 1612
It won't be damaged or something
I mean why Samsung didn't make GP stock CPU like this ??
Sorry if its stupid question
But if it won't damage the phone CPU
The performance will increased as hell
Click to expand...
Click to collapse
I've been using it myself for about a month with no adverse effects.
I chose 1612Mhz because it's fast enough without risking instability. At higher frequencies the memory might not be able to keep up with the cpu/gpu clock, so I have not gone higher than that (though they may work).
vince2678 said:
I've been using it myself for about a month with no adverse effects.
I chose 1612Mhz because it's fast enough without risking instability. At higher frequencies the memory might not be able to keep up with the cpu/gpu clock, so I have not gone higher than that (though they may work).
Click to expand...
Click to collapse
OK thanks for reply
I will keep watching thread for xcu ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:44 PM ----------
Play4NoobWin said:
No boot in xcu
Got stuck in the samsung logo
Tested in aex 4.0
Click to expand...
Click to collapse
What are the bugs of that ROM bro ?
No boot un xxu LOS 14.1
You only see SAMSUNG GALAXY GRAND PRIME.
I USE TRANSLATOR
I Test 13.0
when will you make XCU build ?
@[email protected]
vince2678 said:
I've been using it myself for about a month with no adverse effects.
I chose 1612Mhz because it's fast enough without risking instability. At higher frequencies the memory might not be able to keep up with the cpu/gpu clock, so I have not gone higher than that (though they may work).
Click to expand...
Click to collapse
+1
On 2GB devices it could've been useful but battery consuming as well. Whats the minimum frequency you've set? I suggest you to set to 200Mhz, that will greatly save the battery.
abooooood said:
OK thanks for reply
I will keep watching thread for xcu ?
Click to expand...
Click to collapse
AhMaD eLMoMaNi said:
when will you make XCU build ?
@[email protected]
Click to expand...
Click to collapse
You should wait but please ETA is not allowed.
He'll soon make a build for xcu as well but till then Keep Calm nd Enjoy!
Has.007 said:
+1
On 2GB devices it could've been useful but battery consuming as well. Whats the minimum frequency you've set? I suggest you to set to 200Mhz, that will greatly save the battery.
Click to expand...
Click to collapse
The minimum was already at 200MHz, but thanks for the insight anyways .
he already mentioned for LOS so it may not work for aex
G530T on LOS 13. All seems fine here and over clock is functional. Thanks Vince.
At first thanks alot for this great work ,this OC is very safe and SUPERFAST .but Unfortunately Wifi isn't working on 530H (XCU) LOS 14.1 .This is the Logcat that I've got
I've a few skills on Linux system I can help you to test things if you want.
Code:
04-19 00:20:18.061 1612 2587 D WifiService: setWifiEnabled: true pid=8244, uid=1000
04-19 00:20:18.063 1612 2407 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
04-19 00:20:18.072 1612 2407 D WifiHW : finit_module for "/system/lib/modules/wlan.ko" failed: Exec format error
04-19 00:20:18.072 1612 2407 E WifiStateMachine: Failed to load driver
04-19 00:20:18.075 1612 1612 E WifiController: WifiControllerWifi turn on failed
----I've not found fast charge on Kernel Adiutor , i think you've upload a kernel for another device or something like this ,cuz wlan.ko seems to now be loaded
SM-G530H (XXU) wifi not working
Wifi also isn't working for me on the G530T with the 4/7 build of cm13, but when i use the nightly for 4/16 it works, but then I get no outgoing call audio, but then again I was still getting no outgoing call audio without using the kernel on that build
AhMaD eLMoMaNi said:
At first thanks alot for this great work ,this OC is very safe and SUPERFAST .but Unfortunately Wifi isn't working on 530H (XCU) LOS 14.1 .This is the Logcat that I've got
I've a few skills on Linux system I can help you to test things if you want.
----I've not found fast charge on Kernel Adiutor , i think you've upload a kernel for another device or something like this ,cuz wlan.ko seems to now be loaded
Click to expand...
Click to collapse
The fast charging is not something that has an exposed sysfs interface so it's not configurable.
Clvers said:
SM-G530H (XXU) wifi not working
Click to expand...
Click to collapse
As for the wifi, it has to do with the fact that your devices use a wifi module instead of one built into the kernel. I'll work on a flashable fix for this later this week.
DanteDFG said:
Wifi also isn't working for me on the G530T with the 4/7 build of cm13, but when i use the nightly for 4/16 it works, but then I get no outgoing call audio, but then again I was still getting no outgoing call audio without using the kernel on that build
Click to expand...
Click to collapse
Yes, we switched to using a built in wifi module on the roms i make, so an upgrade is necessary to use the kernel.
vince2678 said:
Yes, we switched to using a built in wifi module on the roms i make, so an upgrade is necessary to use the kernel.
Click to expand...
Click to collapse
So since we'd have to upgrade to use it, and that 4/16 one was a test build and not nightly is it safe to assume the next LO13 nightly will have the in-call audio fixed? I can't hear anything not even if it's ringing the phone unless i switch speaker phone on and off. Or the gprimelte not recieving any more LOS13 builds? I see only LOS14 avail now for it but it has no themes and doesn't update/refresh the screen when watching videos on the browser unless i start dragging my finger across the screen while it loads...
Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This ROM is an unofficial build on CyanogenMod 12.1. Originaly (back in November 2014), the project was only about the kernel but I thought that a full ROM might a better.
So, why would you install this ROM ?
The main reason would be to upgrade significantly the kernel :
- get rid of the old LNX.LA.3.5.1 kernel base (from February 2014) and switch to a brand new LA.BF lollipop base
- to get a smoother experience of CyanogenMod
- to enjoy some CAF taste in all of his glory
- if you are an enthusiast
This ROM uses custom HALs so I'm not responsable of incompatibility with eventual custom kernels and I won't "Add support"
ROM Features :
- Based off latest generic CyanogenMod 12.1 nightly source
- OTA updates via built-in CMUpdater (LZMA Compressed)
- Vanilla CAF LA.BF.1.1.1.c5 display HAL (improved display performance)
- Vanilla CAF LA.BF.1.1.1.c5 media HAL (improved video performance)
- Vanilla CAF LA.BF.1.1.1.c5 audio HAL (improved audio performance)
- Latest Motorola LPB23.13-37 5.1 Vendor Files
- Latest kernel.org f2fs binaries
- Vanilla CAF LA.BF.1.1.1.c5 Media Codecs / Audio Policy / Bluetooth configs
- LZMA Compressed recovery images
- QCOM Bionic Optimizations
Kernel Features :
- Based off latest CAF LA.BF.1.1.1.c5 kernel source from Qualcomm
- As clean as possible, it matches CAF
- Vanilla CAF LA.BF.1.1.1.c5 Wi-Fi Prima driver (better wifi performance)
- Uses ZEN i/O Scheluder by default
- First Lollipop Overclock
- Underclocking
- Smartmax Governor
- My own akm8963 driver re-work for LPM/HBM mode
- The best is in comming
But, why is it in alpha ?:
It's in alpha state because not many people tested it and maybe there are some unknown bugs.
Speaking of bugs here they are :
Code:
[B]Known bugs[/B]
- 5 sec blackscreen at boot (doesn't affect bootime) [B][COLOR="red"][/COLOR]the first boot blackscreen is even longer so just wait and it will boot, builds or tested do not worry[/B]
- Offline charge is broken (same reason as blacksreen)
I released even if those bugs because they doesn't break the ROM experience itself (and because I wait for realeasing this ROM since ages)
They will, of course, fixed as soon as possible.
Download :
cm-12.1-20150909-UNOFFICIAL-h2o64-falcon.zip - 206.7 mo (AFH Mirror) #CHANGELOG
Old Downloads :
cm-12.1-20150827-UNOFFICIAL-h2o64-falcon.zip (AFH Mirror)
How to install ?
If you are coming from an official CM12.1 Nightlies you should dirty flash (flash my ZIP on top of your existing rom without too much issues). If you encounter any issues (report and) do the method detailled bellow.
1) Place ROM & Gapps in your virtual SD
2) Reboot in Bootloader Mode
3) Go to "Recovery" (Vol -) and confirm (Vol +)
4) Wipe Data/Factory Reset
5) Wipe Dalvik cache
6) Install the ROM zip
7) Install the Gapps zip
8) Install SuperSU zip
9) Reboot
Sources :
All repositories are on the cm-12.1-caf branch
device/motorola/falcon : https://github.com/h2o64/android_device_motorola_falcon
kernel/motorola/msm8226 : https://github.com/h2o64/kernel_msm
manifest and build instructions : https://github.com/h2o64/android_local_h2o64
Credits :
- CyanogenMod and its contributors
- CAF (aka Qualcomm)
- Motorola
XDA:DevDB Information
Unofficial Cyanogenmod 12.1 with CAF Kernel 3.4.0, ROM for the Moto G
Contributors
h2o64
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Alpha
Current Beta Version: 2015-09-09
Beta Release Date: 2015-09-09
Created 2015-08-27
Last Updated 2015-09-11
Changelogs
New build 20150616
Code:
- Initial release
Download :
cm-12.1-20150827-UNOFFICIAL-h2o64-falcon.zip (AFH Mirror)
Click to expand...
Click to collapse
@h2o64 Good work!
Flashhhh said:
@h2o64 Good work!
Click to expand...
Click to collapse
1000 posts YAY !
I'm not a fan of CM but my brain forces me to try this...
Can't try this ROM right now since I use my moto g as my daily driver but good to see some nice development going on!
pfufle said:
Can't try this ROM right now since I use my moto g as my daily driver but good to see some nice development going on!
Click to expand...
Click to collapse
It's fully stable, you just don't see 5 sec from the bootanimation.
I will install it and try it but I need to charge my Moto G Good job !!!
Damn, bootanimation doesnt show at all, i reflashed three times thinking something was wrong, and i lost patience thinking my phone turned off after google logo, but it booted. It works great btw, stable and all, and overall fast. Nice work. Now just remove the stupid cm theme engine and implement layers, and you have most custom unoffical cyanogenmod rom.
DeHuMaNiZeD said:
Damn, bootanimation doesnt show at all, i reflashed three times thinking something was wrong, and i lost patience thinking my phone turned off after google logo, but it booted. It works great btw, stable and all, and overall fast. Nice work. Now just remove the stupid cm theme engine and implement layers, and you have most custom unoffical cyanogenmod rom.
Click to expand...
Click to collapse
Yeah, the bootanimation bug is annoying, but you'll see that you get just a 5 sec blackscreen on reboots. It was just the first boot xD
Hmmm ... I don't think I will remove the CM Theme Engine : as I said, this project wasn't a ROM originally (I made a ROM to avoid HAL issues actually) I just wanted to make big background optimizations. So on the apparence/look part, I won't differ from CM.
My opinion (is still black screen after flashing). Just make optimizations and don't change the features or other things. To be just an optimized CM 12.1 ROM.
h2o64 said:
Yeah, the bootanimation bug is annoying, but you'll see that you get just a 5 sec blackscreen on reboots. It was just the first boot xD
Hmmm ... I don't think I will remove the CM Theme Engine : as I said, this project wasn't a ROM originally (I made a ROM to avoid HAL issues actually) I just wanted to make big background optimizations. So on the apparence/look part, I won't differ from CM.
Click to expand...
Click to collapse
Too bad, well i guess i'll stay with the stock theme then, because i seek for stability, and that's pretty rare nowadays.
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
And we can expect updates on this project? I'm not asking for ETA, i just want to be shure this is not a one time thing
omg, thanks for this @h2o64.. gonna try it out...
Eurofighter_ty said:
My opinion (is still black screen after flashing). Just make optimizations and don't change the features or other things. To be just an optimized CM 12.1 ROM.
Click to expand...
Click to collapse
This 5 sec black screen will stay until I fixed SOL in MDSS.
DeHuMaNiZeD said:
Too bad, well i guess i'll stay with the stock theme then, because i seek for stability, and that's pretty rare nowadays.
And we can expect updates on this project? I'm not asking for ETA, i just want to be shure this is not a one time thing
Click to expand...
Click to collapse
All my working projects (AOSParadox, TWRP, or CM now) are getting continuous work and updates. I just don't like to post "empty" updates with an un-interessting changelog.
I just made the first stage of this project xD So much is about to come
Thanks for supporting
forgot to ask, if compile the kernel and use to latest nigtlies. it will be okay? @h2o64
hurtsky said:
forgot to ask, if compile the kernel and use to latest nigtlies. it will be okay? @h2o64
Click to expand...
Click to collapse
Sure
Oops
Forgot to add a kernel feature in the list
- My own akm8963 driver re-work for LPM/HBM mode
Click to expand...
Click to collapse
h2o64 said:
Forgot to add a kernel feature in the list
- My own akm8963 driver re-work for LPM/HBM mode
Click to expand...
Click to collapse
Dual sim working ? I mean this is cm so hopefully it is working .. But when I flashed it , it stays on black screen..... For almost 2 min
sachoosaini said:
Dual sim working ? I mean this is cm so hopefully it is working .. But when I flashed it , it stays on black screen..... For almost 2 min
Click to expand...
Click to collapse
Yes it should be supported
It's normal don't worry
Hi,
I installed all my apps about 30 apps and every app work without problems fc or other problems except one: Zonga - it's a music streaming app developed by Vodafone Romania and in other ROMs it's working but here it doesn't have sound and If I press play doesn't play from first I need to skip the track and the next one plays without music.
I will attach soon a logcat.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
Features
You get the usual set of well known tweaks, mods and other improvements. Please check commits of the source repo which will be mentioned below for detailed list of changes. The key ones are -
Live Kernel flashing with backup support for previous kernel - Liverepack implementation of @psych.half is used, which also backs up your previous kernel (boot.img) and other system files which would be changed.
KCAL - A well known display parameters calibration driver for MSM devices, written by @savoca.
Dynamic Fsync 1.2 - We all know what it is about, dont we? Credits - @faux123
ThunderPlug - A hotplug driver by @varun.chitre15.
Kernel Add-on support - For CM based ROM only. More about it in later posts.
More features will be eventually added.
Kernel Adiutor will list 90% of stuff that can be tweaked by the kernel, rest will be mentioned in further posts.
What does not work?
Various display tweaks by Xiaomi like Reading mode etc in MIUI ROMs - That is because Xiaomi did not open source that aspect of the kernel. The same will probably not work on any Kernel that is compiled from source. But thanks to KCAL, this tweaks can be worked around, check further posts.
Compatibility
This kernel is only meant to be flashed on lollipop based MIUI 7/8 ROMs.
This kernel is also compatible with Official CM and other similar source based ROMs.
Version naming
I gave up on maintaining proper versions of a kernel, its lot of hard-work. Instead, naming scheme of CyanogenMod and other prominent ROMs has been used, reflected in the zip naming. LOCAL_VERSION will be same for all versions hence we will talk about versions on date of build basis.
Installation
Make sure the ROM on which you are going to flash is compatible. Once done, simply flash it through TWRP.
Reporting Bugs
In case an error has occurred during flashing, please report it with /sdcard/liverepack.log.
In case of kernel errors, please get me a dmesg.
Feature Requests
I mainly focus on quality rather than quantity. But still, you can request a feature you would like and I will see what can be done.
Download - Here
If you want to download MIUI version, please download the file with no suffix (zd-20160803-kenzo.zip). Suffix will come in the next MIUI update.
If you want to download CM version, please download the file with cm suffix (zd-20150806-kenzo-cm.zip).
Add-ons can be found in Addons folder. Only CM based kernel supports Addons.
Source/ Tools used
Source - https://github.com/TeamButter/android_kernel_xiaomi_kenzo
Toolchain used - Aarch64 4.9 by google
XDA:DevDB Information
ZD Kernel, Kernel for the Xiaomi Redmi Note 3
Contributors
corphish
Kernel Special Features:
Version Information
Status: Stable
Created 2016-08-02
Last Updated 2016-08-06
Reserved
Kernel Addons
There are certain features which some people want in the kernel, whereas others do not want that at all (they even dont want the feature to be present in the kernel ).
So to meet the needs, we would have to maintain to separate kernel builds, one with the feature, one without it.
Which is where kernel add-on comes to play,
Here the users will need to flash the main kernel. Then, if they choose to, they can flash the kernel addon (which generally contains a feature).
If users choose not to, that feature wont be present at all (just as they wanted), whereas for those who flashed the addon, the feature will be present.
It makes lives of both us and users easier, right?
Addons are low in size flashable zips, as the name suggests. You will need to flash addons if you choose to, after flashing the kernel.
Only CM based ROMs support addons, as init.d support is needed, which is not present in MIUI.
Also, by distributing addons, I guarantee that no copyright infringements are made.
Addons available
-Thunderplug
Workaround for Xiaomi's display tweaks
We will use different values for tweaking offered by KCAL. To do that, open Kernel Adiutor and go to 'Screen' page.
Reading mode
Set Blue to 196.
Colour mode: Warm
Set Green to 240, Blue to 208
Colour mode: Cool
Set Red to 208.
You can also tweak contrast values and other stuffs.
If you are not satisfied, feel free to tweak similarly.
Thunderplug
For some reason, TZ app crashes on MIUI, and kernel adiutor does not fully have support for ThunderPlug.
By default, ThunderPlug does sched based hotplugging. Hence stuffs like endurance mode wont work as it only works when hotplugging is done on per-core basis.
To enable hotplug on per-core basis, open terminal and type:
Code:
su
echo 1 > /sys/kernel/thunderplug/hotplug_style
To go back to sched based hotplug:
Code:
su
echo 2 > /sys/kernel/thunderplug/hotplug_style
Reserved
Changelog
20160803
-Fixed -2% battery bug and camera bug on devices shipped with newer hardware.
20160802
-Initial release for MIUI ROMs
Wow, zapdos was my fav kernel on condor, let's see on kenzo xD
Flashed, no problems for now great work :good:
Working great here, thank you, I have one question, Did you implement Adreno idler? Because my gpu is going to 19mhz, and also Can you please explain the sched and per core mods of thunderplug? Thax
It has the bug of the battery of -2%
dmesg: http://pastebin.com/df8fBgme
donalberto17 said:
Working great here, thank you, I have one question, Did you implement Adreno idler? Because my gpu is going to 19mhz, and also Can you please explain the sched and per core mods of thunderplug? Thax
Click to expand...
Click to collapse
No Adreno idler is not implemented yet.
In sched based hotplugging, the load is shared among cores, there are no practical differences with the stock setup.
In per core basis of hotplugging, cpu cores are only plugged in when its really required, otherwise they are off.
mega-samu said:
It has the bug of the battery of -2%
dmesg: http://pastebin.com/df8fBgme
Click to expand...
Click to collapse
Alright, could you tell me when does this happen? When the battery is very low?
And looks like its a well known bug heh?
Ok thank you for your answer, based on your experience wich one it's better? Per-core or sched?
Waiting for CM version, nice work!
corphish said:
Alright, could you tell me when does this happen? When the battery is very low?
And looks like its a well known bug heh?
Click to expand...
Click to collapse
The mistake happens after flash the kernel. I think that it is for that xiaomi the new one put in indicator of battery, in the recent xiaomi.
I leave this post you, for if it can use you as help:
http://forum.xda-developers.com/redmi-note-3/how-to/fingerprint-battery-issues-custom-roms-t3429464
Well I discovered 2 bugs, when I change the style to per-core basis it doesnt stick after a reboot, another bug is when I change to per-core basis the Fingrepint sensor stops working
mega-samu said:
The mistake happens after flash the kernel. I think that it is for that xiaomi the new one put in indicator of battery, in the recent xiaomi.
I leave this post you, for if it can use you as help:
http://forum.xda-developers.com/redmi-note-3/how-to/fingerprint-battery-issues-custom-roms-t3429464
Click to expand...
Click to collapse
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
donalberto17 said:
Well I discovered 2 bugs, when I change the style to per-core basis it doesnt stick after a reboot, another bug is when I change to per-core basis the Fingrepint sensor stops working
Click to expand...
Click to collapse
That change wont persist through reboot, you will have to do it everytime, or perhaps write an init.d script. Not any app supports this toggle which can provide set on boot.
And all I can make from this FP sensor issue when per core basis is it requires like all 6 cores to function, because in stock, I never saw any core go offline.
corphish said:
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
Click to expand...
Click to collapse
In cm13 santosh with the patch camera fix or in mokee official, does not happen to me.
Nowadays I have the miui 8 of xiaomi.eu, that does not happen with the kernel stock either.
corphish said:
Ok. Have you flashed any other ROMs or kernel in which this issue isnt there.
Looks like xiaomi has done quite some changes in kernel since release.
Click to expand...
Click to collapse
I havn't tried your kernel but as i'm one of people with newer devices that have this problem, i can answer the question
mokee rom doesnt have this problem and the camera fix mentioned in here fixes the problem on CM maybe you can take a look and see what is the fix in that file.
mega-samu said:
In cm13 santosh with the patch camera fix or in mokee official, does not happen to me.
Nowadays I have the miui 8 of xiaomi.eu, that does not happen with the kernel stock either.
Click to expand...
Click to collapse
Alright, I am making a new build and will upload it as soon as its done.
Unfortunately I cant verify whether the battery bug is fixed or not.
Could you flash it and see then?
Thanks both of you for bringing this to my notice.
Let me know if there are any other breakages.
Edit
Here it is - https://www.androidfilehost.com/?fid=24659325368664523
Could you flash this and see? @mega-samu
corphish said:
Alright, I am making a new build and will upload it as soon as its done.
Unfortunately I cant verify whether the battery bug is fixed or not.
Could you flash it and see then?
Thanks both of you for bringing this to my notice.
Let me know if there are any other breakages.
Edit
Here it is - https://www.androidfilehost.com/?fid=24659325368664523
Could you flash this and see? @mega-samu
Click to expand...
Click to collapse
I have just proved it and it continues the bug.
Edit: The camera does not work
Edit2: In the kernel radon they finish of fix.: http://forum.xda-developers.com/redmi-note-3/development/kernel-t3414884/post68012485#post68012485
Enviado desde mi Redmi Note 3 mediante Tapatalk
mega-samu said:
I have just proved it and it continues the bug.
Edit: The camera does not work
Edit2: In the kernel radon they finish of fix.: http://forum.xda-developers.com/redmi-note-3/development/kernel-t3414884/post68012485#post68012485
Enviado desde mi Redmi Note 3 mediante Tapatalk
Click to expand...
Click to collapse
Alright, could you test yet another build soon?
Edit:
Here you go, this build has same name as previous one but they are different build, separately made and uploaded - https://www.androidfilehost.com/?fid=24591000424951734
Also check whether camera works fine or not @mega-samu
corphish said:
Workaround for Xiaomi's display tweaks
We will use different values for tweaking offered by KCAL. To do that, open Kernel Adiutor and go to 'Screen' page.
Reading mode
Set Blue to 196.
Colour mode: Warm
Set Green to 240, Blue to 208
Colour mode: Cool
Set Red to 208.
You can also tweak contrast values and other stuffs.
If you are not satisfied, feel free to tweak similarly.
Thunderplug
For some reason, TZ app crashes on MIUI, and kernel adiutor does not fully have support for ThunderPlug.
By default, ThunderPlug does sched based hotplugging. Hence stuffs like endurance mode wont work as it only works when hotplugging is done on per-core basis.
To enable hotplug on per-core basis, open terminal and type:
Code:
su
echo 1 > /sys/kernel/thunderplug/hotplug_style
To go back to sched based hotplug:
Code:
su
echo 2 > /sys/kernel/thunderplug/hotplug_style
Click to expand...
Click to collapse
if i change to echo1 fingerprint sensor is misbhaving ... one finger works other doenst and also a little bit of irresponsiveness
sasaboor64 said:
if i change to echo1 fingerprint sensor is misbhaving ... one finger works other doenst and also a little bit of irresponsiveness
Click to expand...
Click to collapse
Yeah I realized that.
Looks like all CPU cores are needed for it properly function.
As in stock all cpu cores are always on, I never saw anyone go off.
I might remove hotplug in next build.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
Support for Governors---
Interactive
Performance
PowerSave
Userspace
Optimizations and Tweaks---
Disabled CRC-Check for upto 30% faster I/O.
Support for Dynamic-FSync (adjusts FSync according to usage resulting in a significant boost in the I/O performance).
Reduced RQ Lock-Contention for upto 0.7% increase in Performance.
Install
Copy the zip to your external or internal memory
Boot to twrp
Select the zip.
Reboot to system
Download-- Note 3 Neo (3g/4g)
XDA:DevDB Information
FireKernel for LP (5.1.x) ROMs (3g/4g), Kernel for the Samsung Galaxy Note 3 Neo
Contributors
FireLord, franciscofranco,Shoaib05
Source Code: https://github.com/FireLord1/android_kernel_samsung_smdk5260/commits/FireKernel-lp
Kernel Special Features: battery life
Version Information
Status: Beta
Created 2016-10-08
Last Updated 2016-10-08
ChangeLog
v1
Code:
FireLord1 - script: use google gcc 4.8
franciscofranco - Reduced RQ Lock-Contention for upto 0.7% increase in Performance
Shoaib0597 - Optimized task_sched_runtime for upto 20% increase in Performance
Shoaib0597 - Added support for CRC Toggle
Shoaib0597 - Reduced OverHead
Shoaib0597 - Enabled ARCH-Power feature
Joonsoo Kim - slub: fix a possible memory leak
franciscofranco - Remove '+' symbol from kernel version string
franciscofranco - drivers: mmc: according to the comment left by the original author disabling a cyclic redundancy check on data blocks by yield a a performance improvement hovering ~30%
Francisco Franco - backport https://lists.linuxfoundation.org/pipermail/ltsi-dev/2013-December/002683.html from Kernel 3.10 workqueue: use a higher bit to give more space to actual non-internal flags
franciscofranco - ksm: check and skip page, if it is already scanned
franciscofranco - sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire. From http://ripke.com/loadavg/moire
franciscofranco - Added fsync on/off support.
Greg Kroah-Hartman - Linux 3.4.40
FireLord1 - Linux: FK: r1
FireLord1 - script: zip: add building script and all
FireLord1 - defconfig: renamed to match script
Reserved
* This is my Kernel from osprey (moto g3). this may not have much features as compared to my first kernel release bcz that is for qcom and in exynos i cant do much BUT ill try to maintain main thing which is common. i.e battery life
* osprey: http://forum.xda-developers.com/2015-moto-g/orig-development/firekernel-v1-0-mm-6-0-x-roms-t3401538
* This is for single sim exynos galaxy note 3 neo.
* Compatible with all the custom roms.
* Can work for stock rom too but one thing will not work that is USB PC connection bcz i have edited the files for cm so..
* Its still using google GCC, will test uber GCC if that seems stable ill cook and give here.
* Well not much features but but.. ill upstream till 3.4.112 one Day!
* As always i dont own note 3 neo but i like to make stuff for it. Thanks to my testers 3g and 4g both.
It's very nice to see this Kernel coming from our osprey. It's the nice kernel for Osprey. Hope it's smooth & stable like osprey for exynos too
Huge kudos for you to work on 'Exynos' like SoC. Best of luck.
Thank you for your dedicated work brother. Appreciate it, and keep it up ?✌?
Thanks, waiting for N7502 custom ROM
Good job @FireLord
It doesn't save wifi when I reboot...I am on stock Why? :/ please help me cause I really need a costume kernel and I really appreciate your work! @FireLord
JimmygreecePanathinaikos said:
It doesn't save wifi when I reboot...I am on stock Why? :/ please help me cause I really need a costume kernel and I really appreciate your work! @FireLord
Click to expand...
Click to collapse
Wooah. Sorry to hear that.. Can you tell your device? I'm not sure if I can fix..
Sent from my MotoG3 using Tapatalk
FireLord said:
Wooah. Sorry to hear that.. Can you tell your device? I'm not sure if I can fix..
Click to expand...
Click to collapse
Samsung galaxy note 3 neo 4g version stock Android 5.1.1 Thanks for the fast reply I hope you will find something to fix this.. You always do!!
JimmygreecePanathinaikos said:
Samsung galaxy note 3 neo 4g version stock Android 5.1.1 Thanks for the fast reply I hope you will find something to fix this.. You always do!!
Click to expand...
Click to collapse
umm dunno how stock works.. try deleting /system/lib/module (whole module folder) it is not required cuz kernel has it inbuilt now.. please make backup before doing anything
FireKernel for SM-N7507 (hlltezt)
This is FireKernel with fixed Deadlock bug
Download: AFH
FireLord said:
umm dunno how stock works.. try deleting /system/lib/module (whole module folder) it is not required cuz kernel has it inbuilt now.. please make backup before doing anything
Click to expand...
Click to collapse
I always have backups... You don't say on the steps if we have to do a simple wipe/cache after installing the rom.. Could this be my problem for no savings wifi passwords after reboot??
JimmygreecePanathinaikos said:
I always have backups... You don't say on the steps if we have to do a simple wipe/cache after installing the rom.. Could this be my problem for no savings wifi passwords after reboot??
Click to expand...
Click to collapse
Yea try wiping after flashing kernel.. But hey? Why you keep on rebooting ?
Sent from my MotoG3 using Tapatalk
FireLord said:
Yea try wiping after flashing kernel.. But hey? Why you keep on rebooting ?
Click to expand...
Click to collapse
I installed a xposed module after your kernel so I had to soft reboot
JimmygreecePanathinaikos said:
I installed a xposed module after your kernel so I had to soft reboot
Click to expand...
Click to collapse
Oh.. Then try wiping cache
Sent from my MotoG3 using Tapatalk
Thx for your work. Will try the new kernel with stock rom in a few days.
Sent from my SM-N7505 using XDA-Developers mobile app
does this kernel fix camera issue or calling audio in cm-based roms ?
SAMSUNG Galaxy Note 3 neo
moss20 said:
does this kernel fix camera issue or calling audio in cm-based roms ?
SAMSUNG Galaxy Note 3 neo
Click to expand...
Click to collapse
Its just custom kernel.. Not bug fixing kernel please test it may fix
Sent from my MotoG3 using Tapatalk
biggoof75 said:
Thx for your work. Will try the new kernel with stock rom in a few days.
Click to expand...
Click to collapse
When you try please tell us if your wifi passwords are deleted after every reboot
KaminariKernel
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now more void than it already was.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will simply grab my popcorn and laugh at you.
*
* Tl;dr: if your device crashes and burns, and if that gets you in trouble, it's entirely your fault. [STRIKE]Might be my fault as well, because I'm not a developer, but I don't care. lol[/STRIKE]
*/
Hey folks!
After being a Falcon exclusive for quite a long time, KaminariKernel's LineageOS edition is now available for Peregrine. Have fun.
Features:
Sources & Optimizations
- Based on Lineage's shared falcon/peregrine/titan/thea sources
- Compiled with Linaro 4.9
- Optimized ARM RWSEM & Square Root algorithms
- Kernel-side NEON mode
- Some miscellaneous armv7 tweaks
Click to expand...
Click to collapse
Hotplugging Drivers
- MSM Hotplug
Click to expand...
Click to collapse
Extra CPU Governors
- Impulse
- Smartmax
- Yankactive
- Zzmoove
Click to expand...
Click to collapse
Extra I/O Schedulers
- Bfq
- Fiops
- Sio
- Vr
- Zen
Click to expand...
Click to collapse
Sound
- Faux's Sound Control
- Headset High Performance Mode
Click to expand...
Click to collapse
Screen/GPU
- Kcal Screen Control
- Dt2w/s2w
- Simple GPU Algorithm
- GPU overclock & underclock (533MHz/100MHz)
Click to expand...
Click to collapse
Extra Sh*t
- CPU Overclock (up to 1.6 GHz) (Overclocked version only)
- USB Fast Charge
- Disabled gentle fair sleepers
- Extra TCP Congestion Controllers
- Fsync enabled by default
- Kexec-hardboot patch (for multirom compatibility)
- Power-efficient workqueues
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Unified Marshmallow & Nougat (CM/LineageOS 13 & 14.x)
Click to expand...
Click to collapse
Looking for previous releases?
Go here.
Click to expand...
Click to collapse
Flashing & Tweaking Instructions (Follow this very carefully!!!):
- Place the zip at the root of your phone's internal storage
- Reboot into recovery
- Flash the zip
(Another way: Reboot into recovery without copying the zip, and flash it via adb sideload)
- Reboot again and have fun!
Coming from another kernel which isn't mine? Don't worry, no need to dirty flash the ROM/kernel anymore. The install script now does all the dirty work for you.
If you wanna tweak stuff, use Kernel Adiutor! (Synapse is NOT supported!)
Click to expand...
Click to collapse
Want some info on what this kernel offers you?
Then go here! (Credits to @AssToast for suggesting and to @gsstudios for creating the site!)
Click to expand...
Click to collapse
"Thank You" Section
- Motorola/Lenovo
- Qualcomm/CodeAurora
- The CyanogenMod team
- @Flashhhh, his work kinda inspired me to do this
- @faux123, for Sound Control & Intellithermal
- @savoca, for Kcal Screen Control
- @hurtsky, a huge load of cherry-picks came from his sources
- @YoshiShaPow, for some more stuff
- Some more fellas whose names I can't remember
Click to expand...
Click to collapse
XDA:DevDB Information
KaminariKernel (AOSP/LineageOS, Peregrine), Kernel for the Moto G
Contributors
Kamin4ri
Source Code: https://github.com/Kamin4ri/KaminariKernel/
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R4
Stable Release Date: 2018-03-04
Created 2016-11-21
Last Updated 2018-03-04
Reserved
Reserved
RESERVED!!!
Reserved too
The standard R1-M release is now available. The others shall be available soon.
Good job m8.
Does it feature the CPU overclock?
What is the difference between Standard and Alternative version? I know there says what is the difference but I want to know how will that affect phone. And which is better for battery life? And why no extra governors? Just curious. Anyways thanks for your hard work! Flashed the Alternative version and no problems so far
Edit: Tried installing Standard version, now the Hotplug menu in Kernel Adiutor is gone, that's intended right?
Edit2: I have a problem, sometimes my phone gets stuck and I have to reboot pressing power button for like 10 seconds. Also happenned that it was locked and led was blinking but I couldnt unlock the phone, black screen. Also happenned since I installed this kernel.
Fedray said:
What is the difference between Standard and Alternative version? I know there says what is the difference but I want to know how will that affect phone. And which is better for battery life? And why no extra governors? Just curious. Anyways thanks for your hard work! Flashed the Alternative version and no problems so far
Edit: Tried installing Standard version, now the Hotplug menu in Kernel Adiutor is gone, that's intended right?
Edit2: I have a problem, sometimes my phone gets stuck and I have to reboot pressing power button for like 10 seconds. Also happenned that it was locked and led was blinking but I couldnt unlock the phone, black screen. Also happenned since I installed this kernel.
Click to expand...
Click to collapse
I'm still thinking about putting extra governors. You went from Alternative to Standard, right? Then no, it shouldnt be gone. I must've done a typo in the updater-script (actually, i did just that, but fixed - hopefully - in R2). And about your phone locking up, could you send me a log or something? (Preferably dmesg)
Kernels updated to R2. Yeah, I skipped R1-N. It was built but i forgot to upload it. It had a messed-up installer script anyway.
Kamin4ri said:
Kernels updated to R2. Yeah, I skipped R1-N. It was built but i forgot to upload it. It had a messed-up installer script anyway.
Click to expand...
Click to collapse
Installed standard version r2, CPU hotplug menu still not available. Working with alternative version.
Enviado desde mi XT1040 mediante Tapatalk
Release 3 is now available! This one supports both Marshmallow and Nougat (single zip for both).
Changes:
- Synced with latest CM (Lineage) source code
- Build optimizations from kwoktopus
- Built with Linaro 6.2
You'll find the download links at the OP.
I'm in Resurrección Remix Marshmallow, this kernel should works? Sorry my bad english
[email protected] said:
I'm in Resurrección Remix Marshmallow, this kernel should works? Sorry my bad english
Click to expand...
Click to collapse
Of course!
Does this kernel support ExFat ?, thanks in advance.
J0hnick said:
Does this kernel support ExFat ?, thanks in advance.
Click to expand...
Click to collapse
It does support it via Filesystem in Userspace (FUSE). But the ROM must have an exFAT FUSE driver, and be able to actually recognise and mount USB sticks or memory cards formatted to the exFAT filesystem. CM and its derivatives/forks fulfill both requirements, whilst the stock firmware fulfills neither (even if you install fuse-exfat binaries, your USB stick or memory card won't automount because the version of vold which is shipped within the stock firmware doesn't support exFAT - you'll have to mount it manually via command line).
I've tried to implement exFAT support by using a kernel driver, but it didn't work well. That was a long time ago
Why did you remove the overclock? Which version has overclocked?
Sent from my XT1040 using XDA-Developers Legacy app
The cell phone gets very hot, the processor frequency drops to 1094mhz and 998mhz, and it gets very slow. Can you disable SoC's Temperature Control?
Joel Oliveira said:
The cell phone gets very hot, the processor frequency drops to 1094mhz and 998mhz, and it gets very slow. Can you disable SoC's Temperature Control?
Click to expand...
Click to collapse
Kernel Auditor is your friend
@Kamin4ri, I found on your AFH dev page the R4 version of this kernel, build date January 31, a bit old & not posted here, yet. Thinking of flashing it on my peregrine running RR N 5.8.2, is it safe enough ?
Since you haven't posted it here, I thought it maybe an experimental kernel & not stable enough.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
RZ Kernel aims for as stock experience as possible. It is made from Samsung's stock kernel with stability updates thanks to great guys who made ELS (exynos-linux-stable) branch
It also attempts to increase overall multitasking performance while maintaining good battery life with proper settings
Features
Adapted new Samsung EMS scheduler from Samsung 4.14 kernel (with 16ms PELT)
Gaming optimizations (reduce heat while maintaining performance stability)
Disabled battery-hogging WAKELOCKS
WireGuard and DriveDroid support
Security patch fixes adapted
Thanks to corsicanu for helping me with initial kernel support
XDA:DevDB Information
RZ Kernel, Kernel for the Samsung Galaxy S9
Contributors
remilia15
Source Code: https://github.com/diepquynh/android_kernel_samsung_universal9810
Kernel Special Features:
Version Information
Status: Testing
Created 2020-04-11
Last Updated 2020-08-27
Download link: Drive folder
CHANGELOG:
20200412: Initial release
20200823 [FINAL]: Post #10
Notices and Q&A
The kernel is based on tw10-android-4.9-q branch of ELS, which is currently at stable state from my experience
Other related features of the kernel were picked from other sources. Credits belong to the owner
The kernel's energy costs table is remade in favor of new EMS scheduler
Questions and Answers (Q&A)
Q: AnTuTu scores please?
A: This kernel isn't made for benchmarks so let's not talk about it
Q: My phone gets hot while using this kernel?
A: Short answer: It's your own issue, fix it yourself. Nobody makes a kernel just to burn your hands
Long answer:
Install Termux app from Play Store
Enable screen rotation, open Termux in landspace mode
Type this command: su -c top -d 2
A list of processes will appear and refresh with 2s interval. Find which process consumes the most CPU usage with [%CPU] column and the package name in ARGS column. You should see the culprit of your issue
Reminder: There is no such thing as "I have nothing in background but the phone still heats up". There definitely something happen and 99% of the time it's some of the rogue apps running in background
Q: Can you add X Y Z feature to this kernel?
A: I want to keep the kernel clean and simple. However, if the feature is really useful, I'll consider adapting it with proper performance check before releasing
Q: Installation procedure?
A: Simply flash the kernel with supported ROM and forget. No Magisk reinstallation needed
Reversed for future usage
Another kernel for S9 devices, awesome.?
Thanks
Updated initial release with latest defconfig base for DTC5 vendor
Limit of downloadings from google...
Hey. Will this kernel Work with dtc4 vendor?
Build kernel from scratch
I need help with building kernel outside of android build system.
I have downloaded sources from here: https://github.com/LineageOS/android..._universal9810 , installed cross-compiler, configured with "make exynos9810-starlte_defconfig", build with "make". For now I have file arch/arm64/boot/Image .
How to build correct dtb and pack it with the Image file to bootable image?
Thank you.
Second public build is coming, and this will be the final build of the kernel project!
We have been going through lots of ups and downs in the testing group, so here are the results
Changes:
Fixes zram on boot
Adapted a new kernel scheduler, supporting 32/64-bit task scheduling
Critical scheduler performance fixes
Adapted newer vendor support
As this is the final build of the whole kernel project, I'd like to say thank you to all supporters/developers who helped me improving the kernel. The whole project hasn't lasted long, but it was a great time. This and the RZ Kernel project for Exynos 8895 will also be abandoned, unfortunately
Once again, thank you for all your support!
remilia15 said:
Second public build is coming, and this will be the final build of the kernel project!
We have been going through lots of ups and downs in the testing group, so here are the results
Changes:
Fixes zram on boot
Adapted a new kernel scheduler, supporting 32/64-bit task scheduling
Critical scheduler performance fixes
Adapted newer vendor support
As this is the final build of the whole kernel project, I'd like to say thank you to all supporters/developers who helped me improving the kernel. The whole project hasn't lasted long, but it was a great time. This and the RZ Kernel project for Exynos 8895 will also be abandoned, unfortunately
Once again, thank you for all your support!
Click to expand...
Click to collapse
Arigathanks! I've been using the kernel for quite sometime and I like how it's underclocked by default. What device would you be moving to?
Sad to see such a nice kernel getting abandoned.
What needs to be done to keep it updated and relevant? Would love to keep it alive.
Using this kernel with havoc os, all is good as a daily driver battery life with this combo is awesome
Revontheus said:
Arigathanks! I've been using the kernel for quite sometime and I like how it's underclocked by default. What device would you be moving to?
Click to expand...
Click to collapse
I'm still using my daily driver (S8+) and currently don't have plans buying any other devices
BackToAndroid said:
Sad to see such a nice kernel getting abandoned.
What needs to be done to keep it updated and relevant? Would love to keep it alive.
Click to expand...
Click to collapse
Perhaps you can clone my kernel repo and do something with it. The most contemplating thing is to handle future vendor updates from Samsung. The kernel might go unbootable on latest One UI at some point, so someone must be doing the stock defconfig update (that's the least requirement to boot One UI ROMs with newer vendor)
Hmmm....Usually I can verify that the kernel has been installed by checking it's build date. But it still shows the same like before. I'm running official LOS and flashed the kernel in LOS recovery. According to the log it went fine. Maybe it doesn't work with that recovery?
Edit: Ok, in TWRP it works fine.
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
BackToAndroid said:
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
Click to expand...
Click to collapse
It works without issues for the most part except for USB C audio output which stutters compared to stock kernel.
BackToAndroid said:
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
Click to expand...
Click to collapse
I tried it. Some tweaks not working like showing download speed and reverted back the old power menu (no emergency call) which is baked in the rom and the settings menu changes like 2 battery options in the menu. One is fixed at maximum power saving and cant change while another is on the device health or something which can be change. I also found that sometimes it ramps up the clocks without any reason i still manage to get 4.5-5.3hrs of sot with light usage. The chrome is unusable since it bugged out like its inverted color and cant see sh*t.
BackToAndroid said:
Anyone tried using with the latest vendor / security patch? I'm on Alexis ROM 1.8 would love to continue using this kenel.
Click to expand...
Click to collapse
Just flashed it - seems to work fine with 1.8
UweRammelt said:
Just flashed it - seems to work fine with 1.8
Click to expand...
Click to collapse
How was the standby drain? What twrp did you use? I used 3.4.0.0 of TWRP. The chrome is super dark and cant see. Can you confirm this or im an isolated case? Do you think its because of not using twrp 3.3.1.1 that bugged mine? Hope you can help me. Thanks!