I am closing this thread as I no longer have valid download links available, I can't maintain this project anymore, and I'd like to make sure everyone understands that any links uploaded by other users cannot be confirmed to be unmodified. Proceed at your own risk!
This thread is for the N900W8 and N900T variants of the Galaxy Note 3.
You can find the other thread for N9005, N900A, N900P, N900V, N900R4, N900K, N900L, N900S, SC-01F, and SCL22 variants here.
idleKernel is a fork from Imoseyon's leanKernel starting at his v6.3 Touchwiz release.
It adds a few more features, escaping somewhat from the minimalist approach while still staying battery friendly.
It hopes to support many ROMs. You can request support for your ROM through private message or on this thread.
You can also find Imoseyon's leanKernel here, which still has ongoing development.
DOWNLOAD
Current version: 7.1.0 (2016-03-27)
Note that there are both SELinux Enforcing and SELinux Permissive versions.
If you are using a custom ROM or f2fs, you will need the permissive version.
All Note 5 ports are forced permissive, and have no enforcing version due to invalid SEPolicy.
TouchWiz 5.0 kernels cannot have their SELinux mode changed by any means, they are compiled as either enforcing or permissive.
idleKernel is also used in the Kali NetHunter project! For full idleKernel functionality in Kali NetHunter, flash one of the images here before flashing NetHunter.
Please be careful to download the right version for your actual phone model, not your ROM.
N9005: hlte-eur
N900A: hlte-att
N900W8: hlte-can
N900P: hlte-spr
N900R4: hlte-usc
N900T: hlte-tmo
N900V: hlte-vzw
N900K: hlte-ktt or hlte-kor
N900L: hlte-lgt or hlte-kor
N900S: hlte-skt or hlte-kor
SC-01F: hlte-dcm
SCL22: hlte-kdi
DOWNLOAD LINKS REMOVED
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact kernel zip/tar you downloaded
Your device model (N9005, etc)
A link to the XDA thread of the ROM you're having trouble with
Optional: A logcat during the duration of when the bug is happening
Optional: A `cat /proc/kmsg > /sdcard/kmsg.log` (su required) during the duration of when the bug is happening
You may be able to fix the bug by updating to the latest bootloader and modem for your device.
See: (Direct Download) Latest Bootloaders & Modems
FEATURES INCLUDED FROM LEANKERNEL
overclockable to 2.72GHz, but limited to 2.2GHz during boot
interactiveX V4 (screen_off_maxfreq), renamed back to interactive for compatibility
/sbin/lkconfig script (via terminal emulator, superuser required)
user adjustable panel temperature: -60 to 0, 0 is kernel default (via lkconfig & sysfs)
user adjustable panel colors: 0 to 4, 2 is kernel default (via lkconfig & sysfs)
fix for purple hue/push at low brightness (via panel temperature or panel colors)
cpufreq modified to play better with thermal-engine
compiled with stable Linaro GCC Cortex-A15 4.9 toolchain
built-in supersu and init.d support
DriveDroid compatibility for USB mass storage emulation
interactive governor updated to latest android source (but ondemand left default)
outdated Samsung code updated to later CodeAurora source (cpufreq, mdss, gpu, msm-bus, etc.)
cpufreq issues fixed
exFAT support
ram console enabled for /proc/last_kmsg for kernel crash debugging
FauxSound 3.0
default USB charge speed @ 1200mA
based on N900TUVUFOB6 (February 23, 2015)
IDLEKERNEL FEATURES
rebased on N900TUVUFOL1 (December 5, 2015) and SC01FOMUGOI4 (September 9, 2015)
updated to latest 3.4 Linux (currently 3.4.111)
tailored individually to support all variants of TouchWiz 5.0, CyanogenMod 12.1 & 13.0, SlimRom 5.1 & 6.0, and Note 5 Ports
ramdisk and kernel compressed with xz-crc
FauxSound updated to 3.6
CodeAurora fixes up until December 8, 2015
new IO schedulers available: sio, fiops (default)
new TCP congestion control available: westwood
cubic (default) TCP congestion algorithm updated to Linux 4.3 sources
f2fs full /system /data /cache support (except in enforcing mode TouchWiz)
f2fs updated to latest kernel.org Samsung sources
ext4 updated to latest kernel.org sources
performance governor included for benchmarking & games
adreno idler updated to latest arter97 sources (now with 27 MHz idle)
forced fast charge support by Yank555.lu
full sysfs & in rom vibration control with extended range
compiled with -O2 optimizations
some kernel errors and logging functions fixed
lkconfig rewritten and extended, renamed to ikconfig
support for KCAL advanced color control by savoca
USB mass storage toggle for external SDcard, open Terminal Emulator and type: ums on.
USB 3.0 is turned on if you add 3 to commands: mtp on 3, ptp on 3, ums on 3.
SuperSU uses system install method even on marshmallow, adjustable via ikconfig (set on first boot)
USB HID keyboard and MIDI gadget support (added in 6.7.1!)
INSTALLATION
You can flash idleKernel from Odin 3.x in AP slot using tar.md5 files.
You can also flash from TWRP 2.8.x.x using zip files.
CONFIGURATION OPTIONS
Open Android Terminal Emulator or adb shell, become superuser by typing su, press enter, and type /sbin/ikconfig (on most ROMs you can just type ik), press enter again.
Code:
[email protected]:/ $ su
[email protected]:/ # /sbin/ikconfig
idleKernel configurator (based on lkconfig by Imoseyon)
---
0) display current settings
1) panel temperature
2) panel color
3) cpu max frequency
4) cpu governor
5) gpu governor
6) tcp congestion control
7) io scheduler
8) mmc crc
9) supersu install method
10) check top 10 wake locks (ie. wakeup sources)
please enter a number (or press enter to exit): 0
current settings
----------------
1) panel temperature: 0
2) panel color: 2
3) cpu max frequency:
screen on: 2265600
screen off: 1267200
4) cpu governor: interactive
5) gpu governor: msm-adreno-tz
6) tcp congestion control: cubic
7) io scheduler:
internal memory: noop deadline row [sio] fiops
external sdcard: noop deadline row [sio] fiops
8) mmc crc: disabled
9) supersu install method: system
I recommend the app Kernel Adiutor for control over idleKernel if you are inexperienced in terminal usage, it's very well written and easy to use.
If you want to use the FauxSound controls, please consider buying FauxSound from the Play Store. It's the same developer that wrote the kernel side components to it.
If you want to use KCAL advanced color control, you will need to download the Color Control app from here.
USB 3.0 & MASS STORAGE
idleKernel 6.6.2+ comes with a terminal command called usb, with shortcuts mtp, ptp, and ums.
These commands don't work from adb as running them usually closes the adb session cancelling the command part way through.
They are meant to be run from Terminal Emulator as superuser. If it shows not found, go into Terminal Emulator options and uncheck "Verify PATH entries". There is a bug in Terminal Emulator that causes /sbin to be removed from path sometimes when using su. You could also prefix the commands with /sbin/.
Code:
[email protected]:/ # usb
Usage: usb [mtp|ptp|ums|status] [on|off]
Enables or disables MTP, PTP, and UMS USB modes.
mtp on/off turns on/off MTP mode
ptp on/off turns on/off PTP mode
ums on/off turns on/off UMS mode
default sets USB mode to default
-3, 3 activates USB 3.0, use with on
-i, info, status displays active USB mode
-h, help displays this information
-v, version displays version info
For more help & to report bugs contact <[email protected]>
[email protected]:/ # ums on 3
Disabling USB transfer protocols...
Unmounting SDcard from /storage/extSdCard...
SDcard unmounted successfully.
Activating USB 3.0 SuperSpeed mode...
Setting up dwc3 storage gadget lun...
Mounting /dev/block/mmcblk1 to lun...
Activating USB Mass Storage transfer mode...
Done. PLEASE USE EJECT MEDIA ON PC BEFORE TURNING OFF UMS!
[email protected]:/ # mtp on 3
Disabling dwc3 storage gadget lun...
Disabling USB transfer protocols...
Mount SDcard in Android? (y/n): y
Mounting SDcard to /storage/extSdCard...
Waiting for SDcard to be ready....
SDcard mounted successfully.
Activating MTP USB transfer mode...
Done.
[email protected]:/ # usb default
Disabling USB transfer protocols...
Deactivating USB 3.0 SuperSpeed mode...
Setting USB mode to default...
Done.
TEAM WIN RECOVERY PROJECT
You will probably notice that in the downloads area there is also a TWRP 2.8.7.0 download option.
It uses idleKernel instead of the kernel prebuilts from Omni.
MTP and USB Mass Storage R/W now works in recovery mode, allowing you to plug phone in and easily transfer zips and backups/restores to and from your phone and sdcard. It also fixes some file system bugs that caused ext4 broken backups that couldn't restore to f2fs partitions, and other small bugs like brightness adjustment not working.
On top of that it allows me to support TWRP for variants that aren't officially supported, such as the Japanese and Korean variants.
You can also use ikconfig in TWRP from adb, allowing you to fix settings like unstable CPU overclocks from recovery.
It also has a really cool boot splash and gold theme, that's cool too right?
GOING TO F2FS FILE SYSTEM
See step-by-step guide here:
http://forum.xda-developers.com/gal...ekernel-leankernel-fork-t3241582/post64014959
KNOWN ISSUES
Screen sometimes turns on while charging from PC. (wake event sent from PC?)
Some ROMs refuse to flash in TWRP idleKernel edition. (tell ROM maintainer to fix flash model assert or remove assert yourself)
Streaming audio may occasionally stutter when screen is off. (increase screen off max frequency using ikconfig)
exFAT and f2fs formatted SDcards don't work in CM13. (not a kernel issue, wait for CM team to fix it)
Aroma Installer doesn't work in TWRP idleKernel edition. (it's not compiled with LP driver support? flash original TWRP to use Aroma)
If you are affected by a new issue, please follow ALL of the instructions above and post in the thread or pm it to me.
ROM DEVELOPERS
You have my permission to include idleKernel in your ROM. By doing so, I recommend that you give me the permission to try to work with users on your ROM thread to fix bugs that may possibly be kernel related. On important idleKernel updates, I may visit your thread and notify users of the changes and give them a link back to this thread.
You may also recompile idleKernel with your own changes, and give it a different name if desired. Credit to me is not necessary, but you must keep a branch with the complete source code on a publicly visible site like GitHub, and link to that from your thread. I have a guide in the post underneath this on how to do that.
If you wish to change the default settings of ikconfig when distributing the kernel in your ROM, the easiest way would be to mount /data in your recovery flash script, check for existence of /data/data/idlekernel, if it doesn't exist, create it and write values to a file for every setting you wish to change. Valid files are:
Code:
/data/data/idlekernel/paneltemp - values: -60 to 0 (default 0)
/data/data/idlekernel/panelcolor - values: 0 to 4 (default 2)
/data/data/idlekernel/scaling_max_freq - values in Hz: 652800, 883200, 1267200, 1574400, 2265600 (default), 2496000, 2726400
/data/data/idlekernel/screen_off_maxfreq - values in Hz: 652800, 883200, 1267200 (default), 1574400, 2265600
/data/data/idlekernel/cpu_governor - values: ondemand, interactive (default), performance
/data/data/idlekernel/gpu_governor - values: msm-adreno-tz (default), powersave, performance, simple_ondemand
/data/data/idlekernel/tcp_congestion_control - values: cubic (default), westwood, reno
/data/data/idlekernel/io_scheduler_internal - values: noop, deadline, row, sio (default), fiops
/data/data/idlekernel/io_scheduler_external - values: noop, deadline, row, sio (default), fiops
/data/data/idlekernel/use_spi_crc - values: Y, N (default)
/data/data/idlekernel/supersu - values: SYSTEMLESS=detect/true/false (default)
XDA:DevDB Information
idleKernel, Kernel for the T-Mobile Samsung Galaxy Note 3
Contributors
jcadduono, Imoseyon, arter97, faux123
Source Code: https://github.com/jcadduono/idleKernel-note3
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 7.1.0
Stable Release Date: 2016-03-27
Created 2015-11-05
Last Updated 2018-07-12
Reserved
EVER WANTED TO MAKE YOUR OWN KERNEL FORK?
jcadduono's GitHub forking crash course
1. Make an account on GitHub!
2. Use the fork button @ https://github.com/jcadduono/idleKernel-note3 or any other repository
3. In your terminal emulator, cd to the location you want your repository.
4. git clone https://github.com/YOUR_USERNAME/idleKernel-note3.git
(optionally add folder name after that command to change it to something other than idleKernel-note3)
5. cd idleKernel-note3
6. git remote add jc https://github.com/jcadduono/idleKernel-note3.git
(this will allow you to send commits to me, cherry-pick commits from me, or pull new commits from me!)
7. git fetch jc
(do this whenever you want updated commits from me to be available to you for cherry-picking or merging)
8. Be sure to set your git author information too, for proper commit info!
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
git config --global push.default simple
(that last one just removes a warning message whenever you push commits to github)
9. Whenever you want to pull all the latest and greatest commits from me all at once, run:
git fetch jc
git merge jc
I don't recommend doing that though, because if our branches diverge too much our commits might become incompatible or you might not want some of my changes.
The best way to do it would be to:
git fetch jc
git log jc/X
Replace X with ik-touchwiz/ik-cm12.1/ik-slim5.1, that will show you all of my commits.
For every new commit you want, cherry-pick one at a time to make sure each goes successfully.
git cherry-pick <hash from git log jc/X>
10. Now whenever you make changes to your fork, and you are satisfied with them, you can do:
git add .
(that adds every changed file to the next git commit)
or
git add <file>
then
git diff HEAD
(this is optional, but I recommend looking over everything you changed to make sure it makes sense and you can find extra whitespace or typos!)
11. Once you are satisfied with the changes you've made, you can commit them to the branch history.
git commit -m "made some great change that you detail here"
12. To put your new commits up on GitHub, all you have to do is:
git push
13. If you want to send that commit to me as well, you can do:
git push jc
TIPS
Made a mistake and committed it already? You can time travel through git history using the rebase command!
git rebase -i HEAD~X
Replace X with how far back in commit history you want to edit, trust me time travel is a bad idea.
Just change pick to drop and Ctrl+X Y enter, git will make that commit disappear forever like it never happened.
You can also use various other words like reword to change the message of a commit, etc.
In order for GitHub to accept rebases, you have to add -f to git push, but only if you are changing history you've already pushed to GitHub.
If you've already pushed a commit to GitHub and want to undo it, you can do:
git log
git revert xxxxxx
Replace xxxxxx with the hash of the commit you want undone.
If you haven't pushed to GitHub yet, using git rebase is fine for undoing or rewording commits.
Any time you want to see all the changes from one of my commits, you can use
git show xxxxxxxx
Replace xxxxxxxx with the hash from git log jc/X or even your own git log.
It pipes a nice scrollable colored diff through `less`
If you want to stop it from asking for your GitHub username when you push, in idleKernel-note3 directory do:
nano .git/config
Find a line that looks like:
url = https://github.com/......
Add before github.com so it looks like this:
url = https://[email protected]/...
Now press Ctrl+X Y enter to save.
Nice to see the new thread. I tried 6.5.0 on CM12.1, and it ran great on an N900T. Seems very fast and stable. No problems other than the 100% brightness bug mentioned in the first post.
Battery life was really good. Woke up to 99% battery (about 0.1% drain per hour) over around 6.5 hours, and I had a call during that time, so the notification light was running for a while. Stock CM12.1 battery drain was about 0.2% per hour for me (after my fixes).
Ran antutu benchmark, and the results were good (around 46.3k without overclocking), which is very similar to what I got with the stock CM kernel (46.2k). The newest leankernel 5.2 that just came out got about 44.9k. Spreadsheet with detailed results is attached.
frequentc said:
Nice to see the new thread. I tried 6.5.0 on CM12.1, and it ran great on an N900T. Seems very fast and stable.
No problems other than the 100% brightness bug mentioned in the first post, which I just double checked isn't in the stock CM kernel. Do you know if it's in the latest leankernel? I just installed it, but I don't remember noticing if it had that problem or not.
Battery life was really good. Woke up to 99% battery (about 0.1% drain per hour) over around 6.5 hours, and I had a call during that time, so the notification light was running for a while. Stock CM12.1 battery drain was about 0.2% per hour for me (after my fixes).
Ran antutu benchmark, and the results were good (around 46.3k without overclocking), which is very similar to what I got with the stock CM kernel (46.2k). The newest leankernel 5.2 that just came out got about 44.9k. Spreadsheet with detailed results is attached.
Click to expand...
Click to collapse
Interesting, some improvements could be from the -O2 flag used, or even the version of gcc used to compile. I see Linaro released a GCC 5.1 compiler now and I'm currently compiling with Christopher83's 4.9 toolchain. May or may not see a small improvement moving to GCC 5.1. I'm not too interested in trying to get a toolchain build environment going, so I'll just hope Christopher83 can make some time to release new toolchains soon.
Also, storage IO results, mmm, reason I went with SIO as the main scheduler was it seemed to be great with many storage IO threads while still being minimal and battery friendly. Looks like it's succeeding there.
In any case, all results are pretty close and probably can't be tested in real life scenarios, and are bound to vary between bench so I can't say for sure how much more performance you could possibly get out of idleKernel.
jcadduono said:
Interesting, some improvements could be from the -O2 flag used, or even the version of gcc used to compile. I see Linaro released a GCC 5.1 compiler now and I'm currently compiling with Christopher83's 4.9 toolchain. May or may not see a small improvement moving to GCC 5.1. I'm not too interested in trying to get a toolchain build environment going, so I'll just hope Christopher83 can make some time to release new toolchains soon.
Also, storage IO results, mmm, reason I went with SIO as the main scheduler was it seemed to be great with many storage IO threads while still being minimal and battery friendly. Looks like it's succeeding there.
In any case, all results are pretty close and probably can't be tested in real life scenarios, and are bound to vary between bench so I can't say for sure how much more performance you could possibly get out of idleKernel.
Click to expand...
Click to collapse
Using This baby on Darklord 5.1.1....So far, video flickering...Darkera fix that with some advice from Carlos(shinto kernel creator).My device is N900W8 on Darklord Rom.I download the hlt-can 6.5.1.I will like to send you the logcat,but dont know how...
alek889 said:
Using This baby on Darklord 5.1.1....So far, video flickering...Darkera fix that with some advice from Carlos(shinto kernel creator).My device is N900W8 on Darklord Rom.I download the hlt-can 6.5.1.I will like to send you the logcat,but dont know how...
Click to expand...
Click to collapse
upload them to Mega and post back the link
I'm getting very minimal deep sleep (less than 5% deep sleep even when screen off). Details:
Variant: N900W8
Kernel: idleKernel-hlte-can-6.5.2-cm12.1.zip and idleKernel-hlte-can-6.5.1-cm12.1.zip
Rom: https://plus.google.com/communities/106599804742834944713 (CM12.1 based)
Wakelock: NfcService:mRoutingWakeLock (keeps device awake 80% of the time, doesn't happen on the stock rom. NFC is not toggleable in settings, on stock rom as well as ik).
I'll try with another CM12 variant tomorrow, probably temasek, to confirm if this is a CM issue or one specific to the ROM that I'm using, or perhaps with n900w8. Let me know if there's anything else I can do to help. In actual usage, this kernel is excellent. Great on battery, and very smooth. Would be nice to fix the wakelock issue.
Edit: It seems like on the stock kernel (temasek kernel), nfc switches to off in setting s if i try to toggle it, but in ik, it never switches to off (and maybe keeps trying to toggle it on?).
ammarr said:
I'm getting very minimal deep sleep (less than 5% deep sleep even when screen off). Details:
Variant: N900W8
Kernel: idleKernel-hlte-can-6.5.2-cm12.1.zip and idleKernel-hlte-can-6.5.1-cm12.1.zip
Rom: https://plus.google.com/communities/106599804742834944713 (CM12.1 based)
Wakelock: NfcService:mRoutingWakeLock (keeps device awake 80% of the time, doesn't happen on the stock rom. NFC is not toggleable in settings, on stock rom as well as ik).
I'll try with another CM12 variant tomorrow, probably temasek, to confirm if this is a CM issue or one specific to the ROM that I'm using, or perhaps with n900w8. Let me know if there's anything else I can do to help. In actual usage, this kernel is excellent. Great on battery, and very smooth. Would be nice to fix the wakelock issue.
Edit: It seems like on the stock kernel (temasek kernel), nfc switches to off in setting s if i try to toggle it, but in ik, it never switches to off (and maybe keeps trying to toggle it on?).
Click to expand...
Click to collapse
:/ weird, I can try compiling kernel without any nfc support. I don't have this issue and the N900W8 is my device as well. I did have to turn off google wifi scanning though because that also gave me 80% awake time.
I see nfc in cm settings menu, and when I try to turn it on, it just greys it out and disables the option at off. I never have NfcService running either.
@ammarr I was having the same problem with the stock CM kernel. Removing the /system/app/NfcNci folder fixed the problem for me. You'll no longer see NFC as an option under settings. My system now enters deep sleep like 99% of the time.
frequentc said:
@ammarr I was having the same problem with the stock CM kernel. Removing the /system/app/NfcNci folder fixed the problem for me. You'll no longer see NFC as an option under settings. My system now enters deep sleep like 99% of the time.
Click to expand...
Click to collapse
Seems to have fixed the issue for me. Thanks for the suggestion!
ammarr said:
Seems to have fixed the issue for me. Thanks for the suggestion!
Click to expand...
Click to collapse
@jcadduono - thanks for a new kernel for us to play with! So far it runs great for me (2nd day). Just wanted to mention two little things: I tried terminal emulator but it does not have all the options to control the kernel, tried kernel auditor but it does not keep my settings after reboot, so far faux kernel control app seems to work the best for me. Otherwise so far it seems running great, thank you!
Hey guys, i havr a n900w8 on temasek 5.1.1 cm12.1. The 6.4.7 version works flawlessly.. But when I flash 6.5.3... I get stuck on starting apps screen and the phone never actually boots... Please help
Sent from my SM-N900W8 using XDA Free mobile app
flint777 said:
Hey guys, i havr a n900w8 on temasek 5.1.1 cm12.1. The 6.4.7 version works flawlessly.. But when I flash 6.5.3... I get stuck on starting apps screen and the phone never actually boots... Please help
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
are you using version from selinux_permissive folder, and have you tried rebooting to see if 3 boots or so gets past it
jcadduono said:
are you using version from selinux_permissive folder
Click to expand...
Click to collapse
Yup! permissive
Sent from my SM-N900W8 using XDA Free mobile app
---------- Post added at 06:51 PM ---------- Previous post was at 06:48 PM ----------
jcadduono said:
are you using version from selinux_permissive folder, and have you tried rebooting to see if 3 boots or so gets past it
Click to expand...
Click to collapse
https://idlekernel.com/cm12.1/
Sent from my SM-N900W8 using XDA Free mobile app
flint777 said:
Yup! permissive
Sent from my SM-N900W8 using XDA Free mobile app
---------- Post added at 06:51 PM ---------- Previous post was at 06:48 PM ----------
https://idlekernel.com/cm12.1/
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, lucky for you I also have an N900W8 so I will try out https://idlekernel.com/cm12.1/selin...1_11/idleKernel-hlte-can-6.5.3-cm12.1.tar.md5 with temasek's cm12.1 and see if I can find the issue later today. I need to get some chair hunting done.
jcadduono said:
Ok, lucky for you I also have an N900W8 so I will try out https://idlekernel.com/cm12.1/selin...1_11/idleKernel-hlte-can-6.5.3-cm12.1.tar.md5 with temasek's cm12.1 and see if I can find the issue later today. I need to get some chair hunting done.
Click to expand...
Click to collapse
Alright! Good lookin out bro
Sent from my SM-N900W8 using XDA Free mobile app
Where is the download link for 6.5.4?
Sent from my SM-N920C using Tapatalk
denny02ng said:
Where is the download link for 6.5.4?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I found it in the op
denny02ng said:
Where is the download link for 6.5.4?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
The download links are in the first post. Please read.
cuezaireekaa said:
The download links are in the first post. Please read.
Click to expand...
Click to collapse
Did you even read my question? Off course I read the op, but if you click on the note 5 ports link the latest 6.5.4 is not listed in the download links.
Sent from my SM-N920C using Tapatalk
Related
Hi
IMPORTANT: Before you continue reading!
At the moment this kernel is only for PrimoU devices
and NOT for PrimoC (CDMA) devices
IMPORTANT for CM users
If you want to use CM or a CM based ROM choose the correct kernel!
CM9 needs a different ramdisk.
With the permission from Adi_Pat I would like to announce my kernel build
All credits to this should go to Adi_Pat cause he did the hard work for
providing me with all I need. Therefore also the name has been
choosen to make this clearly visible.
This is just a first announcement.
I will upload the first image tonight
Principle #1:
Provide a kernel that is as close to stock as possible but provides
additional features that will improve functionality and/or performance
Some Q&A you might have
Q: what stands KISS for?
A: Keep It Simple, Stupid!
My aim is to provide a kernel that is 99.99% stock with just additional features
In the first build you will see
-OC (max 1.5)
-UV
-2 new goveners (lionheart, smartassV2)
-1 new scheduler (sio)
Q:will you provide a kernel with 2.0GHz?
A:No - since I want to provide a stable kernel and
my experiences showed that only using up to 1.5 is reliable
If you like to have higher frequencies you can
1) use Adi_Pats kernel
2) build your own kernel based on my changes and enable higher frequencies
Q:can I build my own kernel based on your changes?
A:sure. I will provide a patch file that can be applied on the original
sources provided from HTC
Q:how "close" is your kernel to stock?
A:actually if you dont use OC, UV and use govener=ondemand and
scheduler=deadline this IS stock kernel
Q:can you include feature "xy" in your build?
A:I will check and if it is not "against" principle #1 -Yes
Q:will you test your kernel builds?
A:yes. I will only provide images that have been tested to
1) boot without problems
2) have run through a basic test trying to include all important features
3) run some benchmarks to confirm that changes are not decreasing basic performance values
Q:how to install your kernel?
A:like titanium kernel
fastboot flash boot
regards
max
I provide a complete folder with all downloads
please look at the following "naming conventions" for selecting
the correct image for your ROM!
Images containing "OC-UV" will have presets
Images containing "CM9" are for CM9
Images containing "CM10" are for CM10
All others are for stock (sense) ROMs
Download:
http://www.mediafire.com/?e1chs7tzcsstc
github:
https://github.com/maxwen/primou-kernel-KISS
Build 201305210014
Changelog:
-reverted to BFQ v5.1 - v6 causes problems
-smartmax update
Build 201305141244
Changelog:
-upgrade to BFQ v6
-added smartmax CPU governor
Build 201305062354
Changelog:
-enabled fauxsound support
-added double tap to wake
allows waking up the device by double tapping on the lower part of the screen - disabled by default
sysfs interface:
Code:
/sys/android_touch/s2w_allow_double_tap
1 -enable 0 - disable
Code:
/sys/android_touch/s2w_double_tap_barrier_y
default 1300 - y-barrier below that taps will be recognized
Code:
/sys/android_touch/s2w_double_tap_duration
default 150 - time in ms for minimal duration between the two taps
Code:
/sys/android_touch/s2w_double_tap_threshold
default 150 - threshold how much longer the duration can be then duration
Build 201302150054
Changelog:
-added fast charge
to enable run
Code:
echo 1 > /sys/class/power_supply/battery/fast_charge
------------------------------------------------------------------------------------
Build 201212251804
Changelog:
-multi touch fix - thanks to d-panja3 for pointing me at this
------------------------------------------------------------------------------------
Build 201212180251
ChangeLog:
-added KSM support - see here how to use it
------------------------------------------------------------------------------------
Build 201212152225
ChangeLog:
-completely new S2W based on the work of nik3r and myself for the HOX+
------------------------------------------------------------------------------------
Build 201212021155
Changelog:
-switched to linaro 4.7 toolchain
-overhaul of compile flags
-improved lowmemorykiller
-added some arm specific fixes and enhancements
------------------------------------------------------------------------------------
Build 201211140025
KISS kernels will from now on only for sense ROMS
CM users use HELLBOY kernel http://forum.xda-developers.com/showthread.php?t=1954967
Changelog:
-added BFQ scheduler
------------------------------------------------------------------------------------
Chanelog Summary for all builds:
-new optimized ARM toolchain used
-some tweaks and fixes in vm
-added Proportional Rate Reduction for TCP - by Google http://research.google.com/pubs/pub37486.html
-added USB host support.
-added two-way call recording - Please consider local laws that prohibit using call recording!
based on patch found here http://forum.xda-developers.com/showthread.php?t=1048182
-added conservative govener
-switched RCU to CONFIG_TINY_PREEMPT_RCU - reduced memory usage
-enabled SFB net scheduler CONFIG_NET_SCH_SFB http://lwn.net/Articles/429449/
-applied patch for optimized sha1 algo https://patchwork.kernel.org/patch/1040902/
-applied patch for arm specific rwsem http://permalink.gmane.org/gmane.linux.ports.arm.kernel/92418
-xz compression - based on this patch http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7001/2
-OC (max 1.5GHz, boot with 1GHz)
-UV
-2 new goveners (lionheart, smartassV2)
-1 new scheduler (sio)
------------------------------------------------------------------------------------------------
The "key" e.g. 201207112231 is the build id.
Actually this is just the timestamp when the image has been created.
When you report issues with a build please also provide this id
You can also find this in
Settings -> About -> Software Information -> More -> Kernel Version
Just some notes on the govener and schedulers:
Stock kernel is using govener ondemand and scheduler deadline
To get more information about all of those see here
http://forum.xda-developers.com/showthread.php?t=1369817
You can get the stock kernel sources from here
http://www.htcdev.com/ (registration required)
Or from here http://www.mediafire.com/?o0uudb56oxawvaw
To create the KISS sources apply the patch supplied with each build
Other Downloads:
Note:
If you download save or edit those scripts on a windows host make sure that
you are not changing the line endings to be DOS "style" (CR/LF) since they will
not work on your device.
So before pushing them to the device check with e.g. notepad++ or any
other windows editor that the line endings are UNIX "style" (LF)
USB host scripts
Contains helper scripts for USB host mode
Flashable from recovery
http://www.mediafire.com/?cj1buyxvwteiyqq
Simply zip file
http://www.mediafire.com/?ao391v55e3f4h7r
getcpuinfo script
Will print current settings like OC, UV and govener
Also works with Titanium kernel
http://www.mediafire.com/?emhetf9ctcb3l0g
01vdd script
For setting UV values
Also works with Titanium kernel
http://www.mediafire.com/?yj11n461vz23l4j
02setcpu script
Will set OC max 1.5GHz and govener smartassV2
with battery "friendly" govener tweaks
Also works with Titanium kernel
http://www.mediafire.com/?i79wlhjomh9bhyf
smartassV2-tune script
Allow setting smartassV2 govener tweaks for battery or performance
Call with argument "b" or "p"
Also works with Titanium kernel
http://www.mediafire.com/?e02s5ej5acacnaj
Swap script
Will enable 130m swap partition
See here for details http://forum.xda-developers.com/showpost.php?p=31441526&postcount=17
http://www.mediafire.com/?i9xc4hnfheztgir
KISS => Keep It Simple, Stupid!
hackworks said:
KISS => Keep It Simple, Stupid!
Click to expand...
Click to collapse
Thanks
hackworks said:
KISS => Keep It Simple, Stupid!
Click to expand...
Click to collapse
LMFAO!=)
Congrats on your kernel maxwen!
I will never forget it．lol
Great, i started with kernel compiling too, recently,, keep titanium tweaker in ur ramdisk, if possible, ill update u with the ramdisk builds, will add kernel specif features if u want, pm me
Hi
Sure. Will contact you after posting the first build.
regards
max
maxwen said:
Hi
Sure. Will contact you after posting the first build.
regards
max
Click to expand...
Click to collapse
Cool
Sent from my Nexus One using xda app-developers app
I like this kernel already!
Hi
First build uploaded
regards
max
Gonna flash this now, thanks for your work=D
Sent from my HTC One V using xda app-developers app
best kernel
Hi ..
im tested this kernel on the ROM myONEv works
kernel is very fast and stable.
best benchmark!
I'll try it once I got on my lappy
Sent from my HTC One V using xda app-developers app
Thanks for a nice kernel. So far the OC/UV is working great fro me.
What is the best recommended governor for wake / sleep ?
ckpv5 said:
Thanks for a nice kernel. So far the OC/UV is working great fro me.
What is the best recommended governor for wake / sleep ?
Click to expand...
Click to collapse
Use only CPUFreq and use smartAssV2 as it has both sleep and wake freqs...UV -50 should be good!
Hi
Actually there are a lot of things that you can tweak in the goveners
using the sys interface to make them perform best under certain "preconditions"
You can read this here which I also posted in the Adi_Pat thread
http://forum.xda-developers.com/showthread.php?t=1369817
This will give you some great insights on this issue.
Also about the "decision" which govener to use a.s.o
Regarding UV:
As already writen above -50 should be safe all the time
-100 works for me if I limit it to max 1.2GHz but not higher
Then I sometimes have freezes e.g. runnung AnTuTu benchmark
I still have to play with the UV settings to find the optimal ones
Regards
max
Hi
ATTENTION!!!!
Dont use sio I/O scheduler at the moment!!!!
I just discovered some strange during testing.
Stay with deadline this is stock
Will keep you informed if sio is really the reason
If it is it will be removed in next build
regards
max
EDIT: Even intensive testing has not given me the proof that the
sio scheduler was the reason.
Running this kernel with stock rom, wil I still get FOTA updates from HTC?
Chris.nl said:
Running this kernel with stock rom, wil I still get FOTA updates from HTC?
Click to expand...
Click to collapse
AFAIK this has nothing to do with the kernel in the first place
but with rooting. Someone may correct me if I am wrong
regards
max
UNOFFICIAL CyanogenMod 12.1 for the Samsung Galaxy Nexus
Introduction
I first decided to put together this Lollipop ROM using the old graphics drivers for those of us who wished to try Lollipop, but needed full camera functionality (i.e. barcode scanner apps, or any other app that uses the camera API). At this point, it looks as if the camera has been fixed to work with the newer GPU drivers. I will continue to develop this ROM using the older drivers until all of the major kinks are worked out (both DDK and non-graphics related included) and we have a 100 percent stable release. You are welcome to try my build which does offer some unique features and will continue to be improved upon and synchronized with the CyanogenMod sources.
Please note that you can NOT use any other kernels with this ROM!! I have added a number of additional features to the kernel including custom voltage, fast charge, and color adjustment so hopefully that will satisfy enough for the time being.
I welcome any and all feedback, including bug reports and feature requests. The Galaxy Nexus is my main phone, and this ROM has been stable enough to be my daily driver since I began developing it several weeks ago.
Additional Features Specific to this ROM
F2FS support for /data and /cache. System must be ext4.
LegacyCamera app included (more stable and lots of features)
Lower screen brightness during boot sequence (/etc/init.d/96screendim)
Adjusted minfrees for better multitasking
Xposed for Lollipop compatible*
Specify maximum number of recent apps (ro.config.max_recents)
AppOps control for platform signed apps (ro.appops.show_platform)
Ability to turn off the display during the boot sequence
Support for UnifiedNlp
Volume keys can wake/boot phone from offline charger mode
Additional AppOps (read phone info/other accounts)
Less frequent notifications
Emergency Battery feature
More QS Tiles: Reboot/Recovery, Screenshot, Screen Off
Setting to disable Media Scanner on boot
Volume keys can wake/boot phone from offline charger mode
Expanded Notification Panel width in Landscape Orientation
Disable USER apps from the Applications Manager
Whitelist apps to prevent them from being killed
Recents Privacy: hide app content from appearing in recents cards*
Cell/Wifi scan AppOp
Wakelock Blocker
NEW: Alarm Blocker
NEW: Marshmallow bootanimation
CyanogenMod Features
Better AppOps, including the ability to block wakelocks and alarms.
Status bar mods (brightness control, weather, battery icon style, double-tap to sleep)
Navigation bar customizations
Button mods (volume wake, volume cursor)
Color/Gamma calibration
Battery light enable/disable
CyanogenMod DSP
Scramble for PIN layout on lockscreen
Advanced reboot menu
Charging LED ON/OFF
Theme Manager
Additional Quick Settings tiles (ADB over network, compass, profiles, NFC, hotspot, AudioFX, screen timeout)
More pattern lock sizes (3x3, 4x4, 5x5, 6x6)
and more!!!
Kernel Features
CPU frequency slots: 230-1632Mhz
CPU governors: dyninteractive, interactive, conservative, ondemand, ondemandplus, userspace, powersave, performance, ktoonservative, zzmoove
Min Screen On / Max Screen Off
I/O scheduler: row, zen, noop, deadline, cfq, sioplus
TCP congestion control: cubic, reno, bic, westwood, htcp
Fast Charge (with data transfer)
GPU Overclock (max 512MHz)
IVA Overclock
SmartReflex: Core, IVA, MPU
SmartReflex: Min calibrated voltages
Custom Voltages
Custom Regulator Voltages: VAUX3_6030, VAUX1_6030, VMMC, VANA, V2V1, VDAC, VCXIO, VUSIM, VMMC, VUSB
Color Settings (gamma offset, color multipliers)
I/O Accounting (see this post for more information).
Vibrator Intensity
Headphone Volume Boost
lowmemorykiller whitelist
Emergency Battery Reserve (see this post for details)
GPU governors (on3demand, activeidle, onoff, userspace)
Instructions
First flash:
Unlock & install a recovery
Wipe data & cache partitions
Flash CM-12.1
Install the Google Apps package
Reboot
Upgrade:
Make a backup in recovery
Flash CM-12.1
Install the Google Apps package
Reboot
If you are using F2FS, boot will hang for a bit longer on the Google Logo before animation starts.
Initial boot will take longer than it does with other 5.1 ROMS because this ROM is deodexed. My main reason for doing it this way is so that I can make modifications to individual framework files without having to flash the entire /system partition. The downside is that the initial boot after a wipe of the dalvik-cache will take marginally longer because it has to rebuild the caches for all of the system apps. If you do this while you still have a full compliment of user apps installed - i.e. after an upgrade, the boot sequence could take a REALLY long time - so be prepared for that. Personally, I feel that this is a small enough inconvenience and the benefits outweigh the drawbacks.
Downloads
Latest Build
cm-12.1-20151223-UNOFFICIAL-maguro.zip
Changelog: 12/23/2015
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
Recommended Apps
Dark Material - CM12 Theme UI (Awesome looking Dark Theme for CM12/12.1)
TouchControl (Custom wake gestures, i.e. dt2w, s2w, etc. Choose "Ponury Stock Modified" kernel module)
3C Toolbox
Trickster MOD Kernel Settings
AZ Screen Recorder - No Root
Tips / Recommendations
Bugs
Gesture typing doesn't work on stock keyboard but does work on Google Keyboard
Disclaimer
I'm not responsible for bricked devices (honestly, has anyone actually ever bricked a GNexus?), data loss, lack of rhythm and coordination. Please remember to ALWAYS make backups before you flash and if you are changing filesystems on /data, you will lose ALL DATA which includes everything on internal storage and the recovery will NOT give you any warning before it performs this highly destructive act, so just be aware! Thanks and enjoy!
Click to expand...
Click to collapse
Thanks To/Credits
Code:
[URL="http://www.cyanogenmod.org/"]CyanogenMod[/URL]
[URL="http://forum.xda-developers.com/member.php?u=3390093"]MWisBest[/URL]
[URL="http://forum.xda-developers.com/member.php?u=2633638"]Ziyan[/URL]
[URL="http://forum.xda-developers.com/member.php?u=3623306"]Dirty_Jerz[/URL]
[URL="http://forum.xda-developers.com/member.php?u=4608636"]bsmitty83[/URL]
[URL="https://github.com/Liquidsmooth"]LiquidSmooth[/URL]
[URL="https://github.com/slimroms"]SlimRoms[/URL]
[URL="https://github.com/omnirom"]omnirom[/URL]
XDA:DevDB Information
CyanogenMod 12 (UNOFFICIAL) ROM for the Samsung Galaxy Nexus, ROM for the Samsung Galaxy Nexus
Contributors
zzpianoman
Source Code: https://github.com/zzpianoman
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.0.101
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-03-23
Last Updated 2015-09-15
Reserved
Previous Builds
10/7/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347832232"]cm-12.1-20151007-UNOFFICIAL-maguro.zip[/URL]
09/14/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347816180"]cm-12.1-20150914-UNOFFICIAL-maguro.zip[/URL]
08/13/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347793158"]cm-12.1-20150813-UNOFFICIAL-maguro.zip[/URL]
07/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347782153"]cm-12.1-20150727-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B]*****UPDATE*****[/B][/SIZE]
[URL="http://forum.xda-developers.com/showpost.php?p=62160732&postcount=396"]cm-12.1-20150727-UNOFFICIAL-tuna_update1.zip[/URL]
07/18/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347776472"]cm-12.1-20150718-UNOFFICIAL-maguro.zip[/URL]
07/11/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347772069"]cm-12.1-20150711-UNOFFICIAL-maguro.zip[/URL]
06/26/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347765291"]cm-12.1-20150626-UNOFFICIAL-maguro.zip[/URL]
06/22/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347763431"]cm-12.1-20150622-UNOFFICIAL-maguro.zip[/URL]
06/12/2015
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347758931"]cm-12.1-20150612-UNOFFICIAL-maguro.zip[/URL]
06/04/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952614713"]cm-12.1-20150604-UNOFFICIAL-maguro.zip[/URL]
05/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952610816"]cm-12.1-20150527-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B]***UPDATE***[/B][/SIZE] - Flash in recovery over 5/27/2015 build
[URL="http://forum.xda-developers.com/showpost.php?p=61026999&postcount=291"]cm-12.1-20150527_UNOFFICIAL-zzpianoman_update1.zip[/URL] (Fix for Play Services FC)
05/15/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952604054"]cm-12.1-20150515-UNOFFICIAL-maguro.zip[/URL]
04/29/2015
Code:
[URL="https://www.androidfilehost.com/?fid=23991606952594303"]cm-12.1-20150429-UNOFFICIAL-maguro.zip[/URL]
[SIZE="2"][B][U]GCC 4.7 Kernel[/U][/B][/SIZE]
If your device requires a kernel that is compiled with GCC 4.7
(i.e. won't boot) then flash this kernel over the 4/29/2015 build.
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3289957&d=1430412506"]cm-12.1-zzpianoman-kernel-gcc-4.7.zip[/URL]
[SIZE="3"][B][U]UPDATE - 5/4/2015[/U][/B][/SIZE] - Flash in recovery on top of 4/29 build.
[URL="http://forum.xda-developers.com/showpost.php?p=60534106&postcount=217"]cm-12.1-20150429_UNOFFICIAL-zzpianoman_update1.zip[/URL]
04/23/2015
Code:
[URL="https://www.androidfilehost.com/?fid=96042739161892516"]cm-12.1-20150423-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]GPS FIX:[/U][/B][/SIZE] - (flash this over [B]ANY[/B] CM-12 build prior to
4/29/2015 to fix satellite GPS!!)
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3279981&d=1429903277"]cm-12-maguro_gps_fix.zip[/URL]
04/18/2015
Code:
[URL="https://www.androidfilehost.com/?fid=96039337900114737"]cm-12.1-20150418-UNOFFICIAL-maguro.zip[/URL]
[URL="http://forum.xda-developers.com/showpost.php?p=60269013&postcount=124"]Update - 4/21/2015[/URL]
04/05/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934551453"]cm-12-20150405-UNOFFICIAL-maguro.zip[/URL]
03/27/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934547216"]cm-12-20150327-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]UPDATE: 4/2/2015[/U][/B][/SIZE]
[URL="http://forum.xda-developers.com/showpost.php?p=59850356&postcount=406"]cm-12-20150327_UNOFFICIAL-update1[/URL]
03/22/2015
Code:
[URL="https://www.androidfilehost.com/?fid=95916177934545093"]cm-12-20150322-UNOFFICIAL-maguro.zip[/URL]
[SIZE="3"][B][U]UPDATE: 3/22/2015[/U][/B][/SIZE]
This update include a kernel compiled with gcc 4.7 to fix some
non-booting devices with eMMC bug. Flash this in recovery
[B]after[/B] you flash the ROM. All future builds will include this by default.
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3225706&d=1427145252"]cm-12-20150322_UNOFFICIAL-maguro_update1.zip[/URL]
Reserved
Yeah!! I was waiting for a CM12 rom based on DDK 1.8 as I wanted my camera to function properly. I'll flash it in a few hours and report back. Thanks!
Don't boot on my VYL00M Maguro :/ Stuck on Google logo and restart :/
Tolazace said:
Don't boot on my VYL00M Maguro :/ Stuck on Google logo and restart :/
Click to expand...
Click to collapse
Did you flash any other kernels? This ROM will only work with the included kernel - any other will result in bootloops.
Nope. Just clean flash this Rom + Gapps. Without Gapps still the same problem :/
Other LP roms works great (CM, FML, AOSP, Zmod, Dreams etc)
zzpianoman said:
Did you flash any other kernels? This ROM will only work with the included kernel - any other will result in bootloops.
Click to expand...
Click to collapse
I have the same problem with my kernel ... with the old chip, goes into bootloop, and perhaps the fault of GCC 4.9, I did a build with GCC 4.7 and posted on the forum a while ago, you look news ... let you know, I just news
Fenix46 said:
I have the same problem with my kernel ... with the old chip, goes into bootloop, and perhaps the fault of GCC 4.9, I did a build with GCC 4.7 and posted on the forum a while ago, you look news ... let you know, I just news
Click to expand...
Click to collapse
Ah! That must be it. I'll build the kernel with 4.7 and post a zip. Does this only affect certain maguro devices?
So when can you upload fix kernel? I would test this CM
zzpianoman said:
Ah! That must be it. I'll build the kernel with 4.7 and post a zip. Does this only affect certain maguro devices?
Click to expand...
Click to collapse
So, the problem and the GCC 4.9, go safe with GCC 4.7 a user has just confirmed that it works. This issue and on all models with the old chip "VYL00M"... with the new chip "V3U00M" the kernel can be compiled fine with GCC 4.9 no bootloop
Tolazace said:
So when can you upload fix kernel? I would test this CM
Click to expand...
Click to collapse
Shortly! I'm working on it....
Forgive me, I'm used to working on the toro variant so this eMMC bug is all new to me!
Tolazace said:
So when can you upload fix kernel? I would test this CM
Click to expand...
Click to collapse
Here is the kernel compiled with gcc 4.7. Let me know if this works!!
Working ^^ Thanks a lot I take for testing ^^
Tolazace said:
Working ^^ Thanks a lot I take for testing ^^
Click to expand...
Click to collapse
Great! I'll add it to the OP.
zzpianoman, many thanks for having ported your work to our maguro device.
I have 2 questions for you:
- does this rom have the green line at the bottom of recorded videos?
- do you plan to update LP to 5.1?
armbold said:
zzpianoman, many thanks for having ported your work to our maguro device.
I have 2 questions for you:
- does this rom have the green line at the bottom of recorded videos?
- do you plan to update LP to 5.1?
Click to expand...
Click to collapse
The rom automatically crops the section of video where green line is present. Not a solution, but a nice workaround.
The CM sources have not yet been udated to 5.1 so we'll have to wait until sources are updated to CM12.1
After one day using:
Positive:
-Rom is smooth and fast
-Green Lines "gone" (don't see it)
-Offmode Charging work
-Lot of features
-1080p don't laggy
-DoubleTap2Wake work *.*
Negative:
-Free ram is ~200mb so if you open sms/gallery/browser and listen music - music player turn off and after back to homescreen launcher is restart
-When 3G is ON - phone little laggy
-Recent stack laggy and sometimes have a bug with app name
Rom is Great and when management Ram maybe can be better this Rom be a best lollipop rom o Gnex So I can't wait for next version
(sorry for english)
@zzpianoman Bug?
ALBIEL said:
@zzpianoman Bug?
Click to expand...
Click to collapse
What am I looking at here? Mobile data issue?
WildKernel
for LG Optimus G Pro (E98x & F240x Variants)
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
Unrelated: Is your Gpro camera buggy?
This is a Linux based (3.4.0) Kernel which is maintained by me, and kept inline with the CyanogenMod Kernel so this is compatible with ALL the latest 5.x AOSP Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
So what is this mysterious zip file doing to my device?
Code:
[B]Note: Your phone must already have a booting ROM installed for WildKernel to work. If you find yourself not booting
after installing WildKernel, reinstall your ROM zip then reboot. Ensure that it boots now, then try installing WildKernel again.
If it fails a second time, yell at me below in this thread preferably with a log of some sort attached.[/B]
1. Extracts boot partition and de-lokifies it for manipulation.
2. Takes our new file and decompiles a now readable boot image to utilize its ramdisk, the one currently installed in your ROM
3. Then, it fuses my kernel image with your ROM's ramdisk to form a new boot image
4. Our new boot image is loki-fied and flashed to your boot partition
Assuming that these 4 steps were successful, you can now show your new phone off to your friends.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
E98x Build #5 Reloaded: Primary | Mirrors: #1 / #2
F240x Build #5 Reloaded #2: Primary | Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
SultanXDA
mcaserg
TeamDS
faux123
Tamcore
cretin45
showp1984
RomanBB
Mito Takatori
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
What Do I Pack?
Tame (duhh)
CM 12.1 10/2/16 & Minimal Gapps 5.1
Ondemand on 1st core @ 384-1782mhz
Performance on other cores @ 1458mhz
CFQ Scheduler
4th core disabled
Stock Voltage
GPU: 320mhz
Did you read the announcement? (page header)
XDA:DevDB Information
WildKernel for the LG Optimus G Pro (E98x & F240x Devices), Kernel for the LG Optimus G Pro
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_lge_gproj/
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Build #5
Stable Release Date: 2015-10-28
Created 2015-04-01
Last Updated 2015-11-07
Changelog:
Code:
[B]November 7, 2015 - Build #5 Reloaded #2[/B]
1. Fixed blackouts for [B]F240x[/B] (my changes weren't previously applied in last update)
[B]October 28, 2015 - Build #5 Reloaded[/B]
1. Reverted CM's color adjustment code that created the possibility for blackouts, this is a workaround. There is still a problem with mdp but this will prevent any more blackouts.
[B]September 23, 2015 - Build #5[/B]
1. Mpdecision re-enabled (recommended), intelliplug still available just disabled by default
2. Support for customizing HBLN's pattern style
3. Updates from CM Upstream
4. Misc memory patches
5. Interactive governor updated from upstream
[B]August 16, 2015 - Build #4[/B]
1. Implement DoubleTap2Wake and Sweep2Wake
2. Improve lge_touch_core logic for wake features
[B]June 21, 2015 - Build #3[/B]
1. Touch Boost updates and revamps
2. Added Governors: Adaptive, Intellidemand, Lionheart, SmartassV2 and Wheatley
3. Patch and tweak govenors
4. Added TCP Congestion controllers: Westwood and Veno
5. Made CUBIC the default TCP Congestion Controller
6. Disabled mpdecision
7. Added [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/03fd621788eb48a77e88cff990048687ca6e877d"]Intelliplug[/URL]
8. Misc patches for my drivers
[B]April 19, 2015 - Build #2 Reloaded[/B]
1. Synchronized F240x Kernel to include FauxSound (oops heh should've already been added)
2. 5.1 Bootloop issues seem to have been fixed as reported by my testers, but let me know. Thanks SultanXDA for the pointer.
[B]April 16, 2015 - Build #2[/B]
1. Support for the LG F240x Variants
2. Thermald Re-enabled, but [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/46ee361bc0023a75a47381ec0cfdc9b341ce6e7c"]limited[/URL].
3. Created the ability to [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/dc3f14b3c5a234fe8d83f93bb8a551efe21e5c45"]disable secondary CPUs[/URL], to save power.
4. Added ability to use USB Fast Charge
5. Added FauxSound Support
6. Increased regular charge current max to 1500mA for faster regular charging too
7. [STRIKE]Lollipop 5.1.x is now supported[/STRIKE]
[B]April 1, 2015 - Build #1[/B]
1. Initial Release - Official CM Kernel
2. Home Button: Added Support for Forcing Notification Pulse Intervals
3. Home Button: Added Support for Forcing Notification Pulse Blink Colors
4. Ondemand & Interactive patches
5. Input Boost Driver by SultanXDA
6. My [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/42e759fda2d4643334452ddc6866926e510f29a3"]Retain Cpufreq driver[/URL]
7. Thermald HAL disabled, [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/1dee7142d398677aa6814d454f1619ebd9244970"]here's why[/URL].
8. Disabled some unneeded debugging
9. ROW patches
10. Voltage Control Support
11. 2.1ghz support (overclock with discretion, no device is built the same)
Things You Should Know:
This kernel supports overclocking of up to 2.1ghz, however don't report instability as no 2 devices are built equal. If you feel the need to overclock, experiment with what your device can handle.
Automatically Disable HW Overlays:
As you know, our ROMs currently have graphical issues caused by our MDP drivers and need HW Overlays disabled as a workaround. Well you can add this to a Run At Boot Script in my app Tame (or your own script, ran with su) to save yourself having to manually re-enable it.
Code:
service call SurfaceFlinger 1008 i32 1
Every custom feature in this kernel can be easily configured with Tame (highly recommended), however here is how you can configure things using your favorite ADB/Terminal shell if you're feeling independent.
CPU Control:
Code:
You should be able to understand what I'm doing here. replace cpu0 with cpu[1-3] to change your secondary cores.
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1728000"> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Voltage Control:
Code:
Overvolt CPU by 25mV
echo "+25000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Undervolt CPU by 25mV
echo "-25000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Note:
Values are complimentary. so to undo voltage changes, reboot or input the opposite of what you had previously input.
Home Button Light Notification Control:
Code:
Force all notifications to pulse red (you must input a RGB value)
echo "FFFFFF" > /sys/class/leds/R/device/led_blink_rgb
Force all notifications to pulse for 300 milliseconds, every 1.5 seconds
echo "300 1500" > /sys/class/leds/R/device/led_blink_interval
Input Boost Control:
Code:
Dynamically raise minimum frequency for touch events (in 3 levels).
Enable
echo 1 > /sys/kernel/cpu_input_boost/enabled
Set the boost levels for CPU #1-3 (CPU #1 is the highest level)
echo "1134000 918000 702000" > /sys/kernel/cpu_input_boost/boost_freqs
GPU Control:
Code:
View available GPU clock frequencies
cat /sys/class/kgsl/kgsl-3d0/gpu_available_frequencies
Set max GPU Clock to 400mhz
echo 400000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk
USB Fast Charge:
Code:
This only effects non-wall chargers, wall charging is already allowed max current (1500mA)
Enable maximum speed charging (1500mA under best conditions)
echo 1 > /sys/kernel/fast_charge/force_fast_charge
Limit USB charging to 1300mA
echo 2 > /sys/kernel/fast_charge/force_fast_charge
echo 1300 > /sys/kernel/fast_charge/fast_charge_level
CPU Toggler:
Code:
I recommend disabling CPUs in greatest to least order (4-1) to avoid any possible issues, so disable your 4th core before your 3rd etc. Disabling cores can save power, but also be wary that disabling too many with to little power may slow your device down to a point of it being detrimental.
Disable 4th CPU
echo 0 > /sys/devices/system/cpu/cpu3/enabled
Disable 3rd CPU
echo 0 > /sys/devices/system/cpu/cpu2/enabled
Custom Wake Triggers:
Code:
Note: These features prevent your touchscreen from fully entering sleep, which can consume (slightly noticeable) battery
DoubleTap2Wake - Double tap the center of your screen
echo 1 > /sys/android_touch/doubletap2wake
Sweep2Wake - Sweep your finger from the left part of the screen to the right
echo 1 > /sys/android_touch/sweep2wake
TCP Control:
Code:
Note: It's a common misconception that certain protocols are the best for everyone. While this has a small truth, it ultimately depends on your connection speeds and distance. I would disregard what you may have read about reviews of various protocols, and experiment to see which one works the best for you.
See available protocols
sysctl net.ipv4.tcp_available_congestion_control
Change protocol to westwood
sysctl -w net.ipv4.tcp_congestion_control=westwood
How to make your Developer's Day
Bug Reporting:
Things marked in bold are things you should mention in a bug report to any developer, to make our lives easier.
To be clear as I'm writing this, almost all bugs you encounter are unrelated to your kernel. Most issues stem from the ROM/app/mod you're running, however on the rare occasion, I may be at fault
Well first off, let's narrow down the bug. Assuming your phone rebooted at some point, what caused your phone to reboot? Assuming you're running the latest version of my kernel, did your phone reboot when you were using it, or did you notice it reboot by itself when you weren't using.
Were you overlocking or playing a game? - IF SO stop yourself right here. This is your fault haha I win, otherwise keep going down.
Okay, can you reproduce this reboot? If so, this is a major giveaway that it is indeed an issue.
Reproducing your bug, to capture:
So now I'm gonna need 2 files off your device. Note, you need ADB drivers installed on your computer (google it), and your device plugged in.
First: Plug your device into your computer, to prepare to capture your error.
2nd: Logcat.
Once device is plugged, run:
Code:
adb logcat > logcat.txt
While this is running, reproduce your bug. If your phone doesn't reboot, this is probably not a kernel issue, but reboot yourself and keep going anyway.
Next we will retrieve your KMSG, once phone has rebooted run
Code:
adb pull /proc/last_kmsg kmsg.txt
Note: above will retrieve kernel logs right up until your phone powers off, from the LAST session. Battery pulling, or rebooting twice will overwrite this log and make it irrelevant.
You will now have 2 files logcat.txt and kmsg.txt. Attach em to a Pastebin or attach them to your post.
moe coming soon
Will there be any release in future for Korean versions?
asingha94 said:
Will there be any release in future for Korean versions?
Click to expand...
Click to collapse
most likely yes, but for now I'm sticking with my current device only through beta stages.
Emmanuel U said:
most likely yes, but for now I'm sticking with my current device only through beta stages.
Click to expand...
Click to collapse
Thanx & good luck..
Does this work with android 5.1?
warthog1997 said:
Does this work with android 5.1?
Click to expand...
Click to collapse
Wow that was quick, I didn't even notice there was a 5.1 ROM available for this device. While the kernel most likely won't require any changes on 5.1, the kernel installer will fail when trying 5.1 because it's only set to install on 5.0.x versions.
Awesome!
Nice build dude. Rock solid on ressurection remix 5.3.8 thx to @Alezzander_ . Its first OC capable kernel since android 4.3 time (that rus mcaserg was a real genius too bad he abandoned this phone)
Maybe you two can combine your intelligence and give us something unseen on g pro scene @Snepsts
Didnt checked my pvt but i need +20 mV to get 2GHz stable (on default instant reboot)
And btw faux sound would be nice Thx dev!
Links updated.
Emmanuel U said:
Links updated.
Click to expand...
Click to collapse
Awesome! Thanks for this @Emmanuel U.. I could include it in BlissPop if you wouldn't have a problem with that (with credits to you of course).. It's running so smooth on my latest version..Do you have plans for underclocking?
nerdyblonde said:
Awesome! Thanks for this @Emmanuel U.. I could include it in BlissPop if you wouldn't have a problem with that (with credits to you of course).. It's running so smooth on my latest version..Do you have plans for underclocking?
Click to expand...
Click to collapse
I used to believe that this would be beneficial for the primary core, but after gathering knowledge, now I believe that adding lower clock steps on phones like these (~384mhz) has more harm than good. If the phone is willing to idle, it'll suspend into low power otherwise we shouldnt allow it to scale to such low freqs as it won't be getting any work done at those freqs. I'm working on ideas for battery consumption (I do already get about 7.5 SOT), but I cant see myself adding lower freq steps. Feel free the lower your CPU voltage though.
Oh yea feel free to include this kernel in your ROMs, and this goes for any developer wishing to do the same
Emmanuel U said:
I used to believe that this would be beneficial for the primary core, but after gathering knowledge, now I believe that adding lower clock steps on phones like these (~384mhz) has more harm than good. If the phone is willing to idle, it'll suspend into low power otherwise we shouldnt allow it to scale to such low freqs as it won't be getting any work done at those freqs. I'm working on ideas for battery consumption (I do already get about 7.5 SOT), but I cant see myself adding lower freq steps. Feel free the lower your CPU voltage though.
Click to expand...
Click to collapse
Wow... Is that with a stock battery or the big Zero Lemon batteries?
nerdyblonde said:
Wow... Is that with a stock battery or the big Zero Lemon batteries?
Click to expand...
Click to collapse
Stock, but my phone in general heavily modified though because coming from a kid who's had dual cores all his life, you grow accustomed to cutting down on performance.
Emmanuel U said:
Stock, but my phone in general heavily modified though because coming from a kid who's had dual cores all his life, you grow accustomed to cutting down on performance.
Click to expand...
Click to collapse
Hi. What about quick charge and gpu overclocking?
Sent from my LG-E980 using XDA Free mobile app
please have mercy on the F240k/L users . we barely see any kernel for us
Alezzander_ said:
Hi. What about quick charge and gpu overclocking?
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
Most likely, just give it time.
ecrum said:
please have mercy on the F240k/L users . we barely see any kernel for us
Click to expand...
Click to collapse
Emmanuel U said:
most likely yes, but for now I'm sticking with my current device only through beta stages.
Click to expand...
Click to collapse
^^
Emmanuel U said:
Most likely, just give it time.
^^
Click to expand...
Click to collapse
can i flash this on stock kitkat rom?
[email protected] said:
can i flash this on stock kitkat rom?
Click to expand...
Click to collapse
No, it's a CM kernel
nerdyblonde said:
No, it's a CM kernel
Click to expand...
Click to collapse
for lollipop only?
[KERNEL] [ROOT] [SM-G928P] Exynos 7420 | SkyHigh Kernel [ v6.8.0-EOL ] | Synapse | Aroma | F2FS | UBERTC 6.2.1 20161012
The BEST & FULLY FEATURED EXYNOS 7420 KERNEL IS REBORN . . . . .
Many select patches for better security, performance and efficiency (not all listed). THERE IS "NO NEED" to tweak anything -- Just FLASH it !! But, if you desire, can further tweak many settings and available features with Synapse to suit your own habits and device capability. That is for you to find out
SUPPORTED DEVICES:
SM-G928P
RAMDISK BASE:
G928P : G928PVPS3BPJ2
FEATURES:
Modified from the LATEST device specific official Samsung source(s): Samsung OSRC
AUTO-ROOT SYSTEM-LESS SR3-SuperSU-v2.78 (on flash)
KNOX WARRANTY VOID: 1
SELinux PERMISSIVE (default) or ENFORCING
DEEP SLEEP FIX
UX ROM (BOOT support only)
AROMA Installer (set your own defaults)
Auto-Install busybox v1.24.1-Dorimanx & Sqlite3 to /system/xbin (on flash)
Compiled with UBERTC 6.2.1 20161012 + Graphite optimizations
Linux 3.10.104
init.d script support (drop in script & set permissions to 755 or 777 and reboot)
adb insecure
stock dt.img
Secure storage = false (should prevent WIFI settings & passwords wiping on reboots)
Reduced logging
F2FS experimental support (Much faster I/O - write speeds).
exFAT FS support
NTFS R/W support with app
CIFS support (not tested)
ISO 9660 CDROM & UDF FS support
Frandom
mount all partitions NOATIME (better performance & efficiency)
mount EXT4 /data & /cache partitions LAZYTIME (better performance & efficiency)
A53 LITTLE cores increased boot frequency (faster boot)
LZO ramdisk de/compression algorithm (faster boot)
CLEANCACHE & ZCACHE
Microsoft X-BOX gamepad controller module (updated)
Slub tweaked
Invisible CPUSETs (better efficiency)
A tonne of select patches for features, better performance & efficiency
Synapse app support for many kernel configurations + much much more !!
SYNAPSE FEATURES:
Too many too list . . . Have a look through Synapse yourself. If you don't know, then read and research or leave it DEFAULT !!
About
A57 CPU frequency scaling
A57 voltage control
A53 CPU frequency scaling
A53 voltage control
CPU governor
A57 governor tunables
A53 governor tunables
Multicore
CPU stats
Boost
GPU frequency scaling
GPU voltage control
Thermal
BUS
IO
Memory
Advanced
Power Suspend
Doze
Wakelocks
Audio
Battery
LED
Screen
Network
Security
FS (file system)
CortexBrain
Crontab
USB mode
Modules
Backup & Restore profiles + EFS (auto on boot to /sdcard/SkyHigh/EFS)
Logs
Reboot
Info
CREDITS:
My family !!
Chainfire - root & SuperSU app
AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
halaszk88 - patches and some Synapse code I adapted to many of my kernels
dorimanx - BusyBox and various ramdisk tweaks/ideas
apb_axel - I adapted and used many of the Synapse controls to suit my kernels
arter97 - various source fixes/patches
ktoonsez - ktoonservative hotplug governor
YashdSaraf - BusyBox-Cleaner script
Android File Host
Linus Torvalds & Linux Foundation
Google & Samsung OSRC
and many others!
All those in my select private group that have provided constructive feedback, help, and support.
IF I'VE FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SkyHigh Kernel for G928P devices, Kernel for the Sprint Samsung Galaxy S6 Edge+
Contributors
UpInTheAir
Source Code: https://www.androidfilehost.com/?w=files&flid=125583
Kernel Special Features: Aroma - Synapse ++ almost everything !!
Version Information
Status: Stable
Current Stable Version: 6.8.0-EOL
Stable Release Date: 2016-11-19
Created 2016-08-15
Last Updated 2016-11-19
License - requirements - installation - download - source
DON'T POST LAME QUESTIONS THAT YOU CAN FIND THE ANSWER TO BY A LITTLE SEARCHING.
I AM NOT GOOGLE & NEVER PRETEND TO KNOW EVERYTHING, SO A LITTLE HELP FROM YOURSELF WILL GO A LONG WAY. . .
THANKS & ENJOY !!
** LICENSE & DISCLAIMER **
/*
© Copyright (c) 2015-2016 UpInTheAir <[email protected]>
All rights reserved. The alterations from OEM, associated script files and coding packed within this ramdisk & installation package (the "Software"), may not be reproduced, displayed, modified or distributed without the express prior written permission of the copyright holder. For permission, contact [email protected].
The above copyright notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF , FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/
In plain language
DO NOT STEAL MY SH*T !!
UpInTheAir is NOT responsible, the person you see in the mirror is !!
REQUIREMENTS:
Supported variant only !!
Touch Wiz Android M 6.0.1 ROM or UX leaked firmware (beta support)
Appropriate custom recovery (i.e..TWRP for your variant)
INSTALLATION & UPDATE:
If you have Synapse installed = = you must clear Synapse app data before flash !!
Device Settings: Enable Developer Options > OEM UNLOCK is ENABLED
Boot into custom recovery (volume UP + home + power)
DO NOTHING but flash SkyHigh kernel.zip (ALWAYS flash again AFTER any custom ROM installation, system or data wipe)
After flash == DO NOTHING but REBOOT IMMEDIATELY from TWRP or you will have to re-flash !!
CONVERT EXT4 TO F2FS FS:
If not already, install the latest TWRP for your device variant (ie. 3.0.2-2). This must support F2FS.
Boot into TWRP.
Insert USB-OTG
** ALL DATA WILL BE WIPED FROM INTERNAL STORAGE (restored later)
Backup (copy) all important files (incl. your NANDROID) off device (ie. from internal storage > USB STORAGE). This can take a while. Advanced > File Manager > .....
Home > Backup > Select Storage > USB Storage > OK > "Swipe to Backup" (Only need DATA, but recommend to backup all partitions).
Install > Select Storage > USB Storage > OK.
Select f2fs.zip > "Swipe to confirm flash" (This will WIPE ALL DATA !! & convert DATA & CACHE to F2FS. System is not supported by kernel).
Check the box to remember setting and “Swipe to allow Modifications”.
If you do not have Step #8, then Data was not converted to F2FS.
Mounts > unchecked both Cache & Data. Repeat Step #7 & 8.
Restore > Select Storage > USB Storage > OK > Select TWRP Backup folder > DATA ONLY !! > "Swipe to Restore" (ignore warning about EXT4).
Home > Install > Select Skyhigh_kernel.zip > "Swipe to confirm Flash".
Home > Mount > USB STORAGE > uncheck/unmount (then remove USB-OTG).
Home > Reboot > SYSTEM.
Wait ~2-5 mins for boot.
Once booted, let stabilize for ~5 mins.
You can check Data & Cache F2FS FS status in either /proc/mounts or Synapse app (FS section).
Use a root type explorer (su permission) & navigate to /sdcard, and delete the "0" folder.
Move (copy) your backed up files from Step #4 to internal storage (/sdcard). This can take a while. Maybe one folder at a time is better?
ISSUES ?
If using TWRP MTP mode, deleting some folders/files may crash TWRP and cause corruption. Instead, use a root type file explorer to delete from device.
If you need to wipe data, then use the ext4 or f2fs.zip, otherwise this is not possible with this TWRP !!
Not tested any method with customized ROMs. The ROM installer script may re-format partitions back to EXT4 or not mount correctly causing TWRP crash or corruption. I can only suggest to Flash ROM with EXT4 FS > make a NANDROID on USB-OTG and then follow the F2FS steps above.
CONVERT F2FS TO EXT4 FS:
The Same steps as above, but use the ext4.zip !!
OPTIONAL SYNAPSE INSTALLATION:
After boot:
Wait at least 120 secs to stabilize
Install Synapse app from Google Play and rate it ☆☆☆☆☆ !!
Open Synapse
Tap "Understood"
So changes stick every time you start Synapse == Make any change & 'apply'.
Recommend: Disable KNOX with Synapse
DOWNLOADS:
Mod Edit: Link removed.
BUGS:
Aroma Installer: 10% of installation will encounter Aroma installer "freeze". It's only the display that freeze, the script still execute in the background. Just wait a minute, then press slightly to the top right 'home' key / top left of the 'back' key . . .
UX BETA firmware - blue light filter
UX BETA firmware - torch light (some ROMs)
HD voice ? - Speakerphone: other party cannot hear voice
SOURCE - ALL SkyHigh VARIANT:
Available upon request..
v6.6.1 AFH
v6.8.0 uploaded soon. . . . .
.
FAQ & HELP
TROUBLESHOOTING GUIDE:
I might not have your device variant and or able to reproduce your "issue".
Please provide as much information as possible.
Without resetting your device to a stable unmodified baseline, any potential troubleshooting or logs could be meaningless.
So please follow the guidelines set out below. Users can't "read minds".
Without providing important information, we are unable to help YOU.
Search thread, XDA and Google before posting
Provide as much information as possible.
- Device model
- Firmware version
- ROM name / version
- Kernel version
- Modem version
- Bootloader version
- Synapse settings (try default)
- Installed tweaks and apps etc (Xposed ?)
- The exact steps you've taken to try resolve the issue yourself.
Exact steps to reproduce the issue. Provide screenshots if able.
Does it work with older / other versions etc
Reset your device to a stable baseline (ie. stock) with only custom TWRP recovery and kernel (FULL WIPE: system, cache, dalvik-ART)
Possible logs
FAQ & HELP:
CAN I BUILD A KERNEL FOR YOUR __XX DEVICE ?
Sorry. I don't have the spare time for any more variant support.
Additionally, I do not build for any device that I can not compile using SAME source, personally test method or debug. Some device variants can compile with same source.
CAN I INCLUDE SkyHigh KERNEL IN MY ROM
NO == My ramdisk modifications are COPYRIGHT (refer LICENSE in Post #2), and distribution without MY (UpInTheAir) prior written consent is not only in a breach of that license, but also XDA Rule #12)
Although I do appreciate your contribution, if you could please do not include my kernel in any ROM package etc. This policy goes for anyone.
Having my kernel distributed outside my development thread just removes a lot of credit and more importantly, constructive user feedback that could be helpful to my development or user issue.
ALWAYS on DISPLAY (AoD)
I have spent some time to attempt port S7 display drivers to our kernel, but haven't had success as yet with too many errors.
TBH, it's a lot of work for something I'm not really interested in or would use. . . so I don't wish to spend any more of my own time on it, sorry. If someone else does it, GREAT
DO I "NEED" SYNAPSE
THERE IS NO "NEED" !!
It is "recommended", which is OPTIONAL, and not "needed".
It is for ADVANCED or adventurous users who wish more control of their device or use various features I've added.
Using any other optional tweaking or control app may conflict & many features and options won't be available.
WHY WAIT 120 SECS
The kernel and Synapse scripts need time to boot up properly and allow SU permission.
There are scripts / code that have a deliberate delay and must run after Synapse. These are not user optional.
Synapse has a stability check on boot. You may get "synapse boot cancelled".
Thermal throttling will be trying to limit many things, let the device settle
OTHER PARTY CAN NOT HEAR VOICE ON SPEAKER PHONE
It could be a conflict in the system/etc/mixer_*.xml. I don't know for sure, but if I exclude the sound mod, then this "fixes" the problem.
As I cannot reproduce the issue (and the majority), then the audio mod stays.
Unfortunately, making it optional would require to build kernels without and create much more work for many device I don't actually use.
Either live with it, or use another kernel. Sorry.
"NO UCI SUPPORT"
It's a ROM busybox compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP / RESTORE ISSUES
It's a ROM busybox or sqlite3 compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP & RESTORE
DO NOT restore profiles from different kernel version
Refer to THIS post for "how-to" screen-shots
Refer to THIS post for a "how-to" video
LOADABLE MODULES AREN'T WORKING
Check your /system/lib/modules directory. Are any ____.ko present?
Did you flash a ROM or wipe the system partition at any point? Doing this will remove them !
Re-flash the kernel will install the modules.
If modules aren't installed after flash, then re-flash and manually mount system in recovery first.
You can check running modules in terminal with:
lsmod
KTOONSERVATIVE GOVERNOR
Some info from the author HERE
DT2W & COLOUR CONTROL
No, I cannot make it work properly with single source for all supported variants
CPU POWER CONSUMPTION
The Samsung Exynos 7420 Deep Dive - Inside A Modern 14nm SoC (by ANANDTECH - Andrei)
F2FS SUPPORT
It's not needed. You wouldn't see any difference or measure much, if anything. Not worth the potential trade-off. This is not eMMC anymore
Storage Benchmarks
STUCK ON SAMSUNG BOOT LOGO AFTER FLASH
Ensure you flashed the correct kernel for your device model
Ensure your download is not corrupted. Check MD5 hash or re-download
Your current base firmware (ROM, boot-loader version etc.) may be incompatible - UPDATE to latest with Odin and try again.
CM SUPPORT
Read THIS
BATTERY TIPS (require updating !! )
Try some (or combination) of the CPU MULTICORE features in Synapse:
HMP profile = Default (values are battery orientated)
Power Aware Scheduling (slight performance cost) = Enabled
HMP LITTLE Packing (slight performance cost) = Enabled
PEWQ (power-efficient workqueue) (slight performance cost) = Enabled
Set A57 & A53 Interactive governor profile = Battery
Set Input-Booster for key/touchkey profile = Battery
Multi-tasking: enable UKSM & "low" or "quiet" profile (slight performance/battery cost)
PERFORMANCE TIPS (requires updating !! )
Set A57 & A53 Interactive governor profile = Performance
Set A57 & A53 Interactive governor = Turbo Mode (battery cost)
Set HMP threshold profiles = Stock or Performance
Once in a while:
Optimize Databases
FSTrim
RANDOM REBOOT
Don't UV or UC CPU or GPU
Use SkyHigh defaults
Use a stock UNMODIFIED ROM for your device variant
No tweaks, Xposed or other CPU control apps installed
Follow the TROUBLESHOOTING GUIDE
ASV_GROUP (ALL DEVICES ARE NOT CREATED EQUAL)
THIS is an example from my Exynos5420 source. Similar idea for Exynos4
DOWNLOAD LINK NOT WORKING
I want to keep this project all in one place - ☆☆ NO MIRRORS ☆☆
Please try again in a few minutes
POOR CPU/GPU BENCHMARK or GRAPHICS PERFORMANCE
Disable any CPU MULTICORE options in Synapse
Disable any Battery profiles in Synapse. Set to default or Performance.
Allow the device to cool. Repetitive testing will heat the device hardware and invoke thermal throttling and lead to decreased benchmark.
HIGH CPU/GPU OC == excessive heat == thermal throttling == reduced clock frequency == DECREASE PERFORMANCE
DYNAMIC MANAGEMENT OF DIRTY PAGE WRITEBACKS
by Christopher83
This feature allows to have two different intervals for dirty page writebacks and to dynamically manage them when the system has been resumed (it's active) or when has been suspended.
Three new procfs parameters are exposed inside /proc/sys/vm path:
dynamic_dirty_writeback is the activation status of this feature, set 1 to enable it, set 0 to disable it and use the standard behaviour
dirty_writeback_active_centisecs is the interval for the dirty page writebacks when the system is active (screen on)
dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off)
This feature is in part inspired on Francisco Franco's PATCH
TCP/IP NETWORK SECURITY
Thanks to zeppelinrox & V6SuperCharger
Hardening the TCP/IP stack to SYN attack
Bump up tw_buckets in case we get DoS'd
Ignore pings
Don't cache connection metrics from previous connection
Don't pass traffic between networks or act as a router
Enable spoofing protection (turn on reverse packet filtering)
Don't accept source routing
Don't accept redirects
Further reading:
http://www.cyberciti.biz/faq/linux-kernel-etcsysctl-conf-security-hardening
http://www.symantec.com/connect/articles/hardening-tcpip-stack-syn-attacks
CHROMECAST - STREAMING PROBLEMS
Lock screen MUST be enabled (simple screen lock swipe) I don't know why but it breaks the chromecast app's ability to resume smoothly if switched off
Synapse > Network > DTIM (both screen ON & OFF) = 1
Synapse > Network > WIFI Power Mode (screen OFF) = FAST
v5.8 released
SkyHigh KERNEL REBORN - v5.8 released !!
Hi fellow members.
Please find my latest release for SkyHigh kernel. There are many many changes, both visually (more / improved features) and a upgraded engine (better performance & efficiency) since I last publicly released. Far too many to talk about. . . .
Please note that although I have taken as much care in building and testing by my friends and I, the kernel may still not perform as hoped for you. Could be due to various factors including (but limited to):
hardware quality
firmware installed (incompatibility)
user habit (how you use the device)
apps & mods installed, customization's (conflicts)
user kernel settings (read them carefully - if in doubt == defaults)
As noted in Post #3, I may not have your device variant and not be always able to help either. In the end, sometimes SkyHigh is just not meant for you . . . .
If you have issues = = READ & FOLLOW ALL Posts #1-3
READ & FOLLOW THE INSTALLATION INSTALLATIONS EXACTLY (or else device will not boot)
Also please note (as per OP) the support for UX based ROMS is still in beta. I have personally tested very briefly, and also some of my friends (not all variant). I don't believe this kernel will fix the no call audio issue for those UX ROMs. It is ROM related !!
Enjoy
UITA
.
Thanks the "Ps" appreciate your time and efforts.
I know I do appreciate your time. Thank you
Sent from my SM-G928P using Tapatalk
Thank you, Sir. This is wondrous news! Much appreciation.
v5.8.1
v5.8.1 Minor update for all supported Galaxy S6 Edge Plus variants.
Enjoy
Heavy usage all day yesterday
Better battery
No lag what so ever
1 random reboot in the middle of the night while charging and not using
MonkeyAround said:
Heavy usage all day yesterday
Better battery
No lag what so ever
1 random reboot in the middle of the night while charging and not using
Click to expand...
Click to collapse
I suppose it occurred at the time battery was either full or 100% ? I've 2 of those on my N920C whilst on data and standard mains AC charging since v5.6. Battery was either full and or indicating 100%. Only happened (for me) since later kernel source merges. I thought I fixed it 5.6 - 5.8, but maybe not entirely. Could be firmware variant inconsistencies and or stock dt.img.
Unfortunately it's rare (meaning difficult to reproduce the bug so a solution can be found), and I just don't have time to look into things for a long time.
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C
This might be a newby question, but, would a Rooted Stock be able to use this Kernel? I'm guessing you must have a Rom?
SprintBama said:
This might be a newby question, but, would a Rooted Stock be able to use this Kernel? I'm guessing you must have a Rom?
Click to expand...
Click to collapse
If your device meets the requirements in Post #2
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C
Is something wrong with Android File Host? Cannot download...
N920P Tester needed
If you are capable and willing to test G928P SkyHigh kernel pre-release on full stock firmware G928PVPU2BPG1 ??
Just require ONE (THE FIRST TO REPLY) that can work around flashing and recovery WITHOUT anyone holding your hand.
Without proper testing and decent informed feedback, there will be no official release for you. I've spent a lot of time on this for just a few users here. There aren't many appreciative, since I don't even have device.....
Cheers
UITA
UN-recognized Developer of my SkyHigh Kernel v6.x.x powered SM-N920C
I'll do it. I'm always appreciative for any work to our device.
Sent from my SM-G928P using Tapatalk
nowerlater said:
I'll do it. I'm always appreciative for any work to our device.
Sent from my SM-G928P using Tapatalk
Click to expand...
Click to collapse
Okay.
All I require to finish this test build is the stock G928PVPU2BPG1 boot.img. If you don't have it, then it can be extracted from the full firmware package http://www.sammobile.com/firmwares/download/84809/G928PVPU2BPG1_G928PSPT2BPG1_SPR/ . I need it unmodified.
I can't guarantee much on this, full fresh build on top of your device specific source. A few changes along the way, which could affect stability or boot. etc. No idea.
I'll get it to you ASAP
Sent from my SM-G928P using Tapatalk
UpInTheAir said:
Okay.
All I require to finish this test build is the stock G928PVPU2BPG1 boot.img. If you don't have it, then it can be extracted from the full firmware package http://www.sammobile.com/firmwares/download/84809/G928PVPU2BPG1_G928PSPT2BPG1_SPR/ . I need it unmodified.
I can't guarantee much on this, full fresh build on top of your device specific source. A few changes along the way, which could affect stability or boot. etc. No idea.
Click to expand...
Click to collapse
https://www.dropbox.com/s/qts6z1f89sqv6e9/boot.img?dl=0
Sent from my SM-G928P using Tapatalk
nowerlater said:
https://www.dropbox.com/s/qts6z1f89sqv6e9/boot.img?dl=0
Sent from my SM-G928P using Tapatalk
Click to expand...
Click to collapse
I'm out getting the car brakes repaired. Will build as send to you for test later. Please make sure your device is prepared with full stock (Same as boot.img) and TWRP. NO other mods, tweaks, xposed or crap. We need to test the "kernel" [emoji3]
UN-recognized Developer of my SkyHigh Kernel v6.x.x powered SM-N920C
I can also test if you need me to, I'm currently running G928PVPU2BPG1 with the kernel from the OP with otherwise stock firmware and all is working fine.
Introduction
Based on samsung sources and android common tree. Supported devices: G970F/N, G973F/N, G975F/N G977B/N, N970F, N975F, N971N, N976B/N. All sources are open on GitHub.
Continuous integration with GitHub Actions set up. This means you can customize the kernel from browser and build the version suitable for you without leaving the browser (see сustomization section).
Features
Customizable build with config presets
Only part of samsung security features disabled (DEFEX, Process Authentification, root restrictions)
Switchable SELinux (by default it's locked in "always enforcing" mode in samsung sources)
Built-in in Magisk v21.1
Various toolchains (cruel,arm,samsung,proton,arter97...) supported
Wireguard for VPN
CIFS for SMB
Iptables TTL and HL editing modules for bypassing tethering restrictions
NTFS module for OTG usb drives
Moro sound module
Boeffla WakeLock Blocker
sdfat driver for vfat and exfat filesystems
reiser4 filesystem added. reiser4progs (https://github.com/CruelKernel/reiser4progs/releases)
DEX cable vendor lock for WQHD resolution removed
ZIP installer with XZ compression
ZIP installer with automatic os_patch_level patching
Build commands (configuration presets) used for V3.9 kernel:
Code:
$ ./cruelbuild pack model=<MODEL> name=CRUEL-V3.9 +magisk +nohardening +force_dex_wqhd +ttl +cifs +ntfs +sdfat +nodebug +noaudit +noksm +nomodules +wireguard +usb_serial +sched_powersave +sched_performance +morosound +boeffla_wl_blocker +fake_config +dtb
Where model can be one of G970F/N, G973F/N, G975F/N G977B/N, N970F, N975F, N971N, N976B/N.
Installation Instructions
First of all, TWRP Recovery + multidisabler should be installed in all cases. This is a preliminary step. Backup your existing kernel. You will be able to restore it in TWRP Recovery in case of any problems. Download an *.zip file. Reboot to TWRP. Install > Install ZIP > Flash CruelKernel.zip. Reboot to system.
ChangeLog
V3 - Support for G970F, G975F, G977B, N970F, N975F, N976B models.
V3.1 - Boeffla wl blocker, BTB5 sources for N10 models.
V3.2 - Magisk update v20.4, wireguard update, sdfat for VFAT, exFAT, ntfs module.
V3.3 - CTC9 sources. The camera will work only on CTC9 based firmwares.
V3.4 - CTE9/CTF1 sources. Small fixes, overall improvements, more customization configs for building on github.
V3.7 - Various toolchains added (arm, arter97, samsung, proton, system, default)
V3.8 - DTI1 sources added for N971N, N976N.
DTH7 sources added for G977N model.
Some debugging flags disabled. performance config fixed (-O3).
Cruel toolchain added (gcc 10.2 with PGO/LTO and inlining params from gcc 9 branch)
simple_lmk added (github.com/kerneltoast/simple_lmk)
V3.9 - G977N, G973N models added.
G970F/N, G975F/N, G973F/N updated to DTJA.
N976B, N970F, N975F updated to DTJ4.
Magisk updated to v21.1 version.
Vendor lock for dp cable for DEX removed (thanks, fart1-git).
Zip installer implemented.
Automted os_patch_level level patching in installer (https://github.com/CruelKernel/clone_header).
Downloads
OS Patch Level: 2020-11
V3.9 Download folder
Sources
If you like the work and want to help me with hosting: https://www.paypal.me/evdenis Hitting star button on GitHub and thanks button on XDA really helps to stay motivated.
Instructions here could be outdated a bit, one can find the latest version in project's readme at github.
How to customize the kernel build
It's possible to customize the kernel and build it from the browser. First of all, create and account on GitHub. Next, fork this repository. Switch to the "Actions" tab and activate GitHub Actions. At this step you've got your own copy of the sources and you can build it with GitHub Actions. You need to open github actions configuration file (.github/workflows/main.yml) and edit it from the browser. For example, to alter the kernel configuration you need to edit lines:
Code:
- name: Kernel Configure
run: |
./build config
model=G973F
name="CRUEL-V3.3"
+magisk
+nohardening
+ttl
+wireguard
+cifs
+sdfat
+ntfs
+tcp_cibuc
+morosound
+boeffla_wl_blocker
First of all, you need to change G973F model to the model of your phone. Supported models: G970F/N, G973F/N, G975F/N G977B/N, N970F, N975F, N971N, N976B/N.
You can change the name of the kernel by replacing name="CRUEL-V3" with, for example, name="my_own_kernel". You can remove wireguard from the kernel if you don't need it by changing "+" to "-" or by removing the "+wireguard" line and "" on the previous line. OS patch date can be changed with os_patch_level=2020-02 argument, the default current date is in build.mkbootimg.G973F file.
Available configuration presets can be found at kernel/configs folder. Only the *.conf files prefixed with "cruel" are meaningful. For example:
+magisk - integrates magisk into the kernel. This allows to have root without booting from recovery. Enabled by default.
magisk+canary - integrates canary magisk into the kernel.
bfq - enable bfq I/O scheduler in the kernel.
sched_... - enable various (conservative, ondemand, powersave, userspace, performance) CPU schedulers in the kernel.
ttl - adds iptables filters for altering ttl values of network packets. This helps to bypass tethering blocking in mobile networks.
wireguard - adds wireguard VPN module to the kernel.
cifs - adds CIFS (SMB) support.
tcp_cubic - use CUBIC as default TCP congestion control.
tcp_westwood - use WestWood as default TCP congestion control.
sdfat - use sdfat for exFAT and VFAT filesystems.
ntfs - enable ntfs filesystem support (read only).
boeffla_wl_blocker - enable boeffla wakelock blocker module.
morosound - enable moro sound control module.
+nohardening - removes Samsung kernel self-protection mechanisms. Potentially can increase the kernel performance. Enabled by default. Disable this if you want to make your system more secure.
nohardening2 - removes Android kernel self-protection mechanisms. Potentially can increase the kernel performance. Don't use it if you don't know what you are doing. Almost completely disables kernel self-protection. Very insecure.
nodebug - remove debugging information from the kernel.
noksm - disable Kernel Samepage Merging (KSM).
nomodules - disable loadable modules support.
noaudit - disable kernel auditing subsystem.
300hz - increases kernel clock rate from 250hz to 300hz. Potentially can improve ui responsiveness.
1000hz - increases kernel clock rate from 250hz to 1000hz. Potentially can improve ui responsiveness.
For example, you can alter default configuration to something like:
Code:
- name: Kernel Configure
run: |
./build config
os_patch_level=2020-12
model=G975F
name="OwnKernel"
+magisk+canary
+wireguard
+nohardening
+1000hz
After editing the configuration in the browser, save it and commit. Next, you need to switch to the "Actions" tab. At this step you will find that GitHub starts to build the kernel. You need to wait about 25-30 mins while github builds the kernel. If the build is successfully finished, you will find your boot.img in the Artifacts section. Download it, unzip and flash.
To keep your version of the sources in sync with main tree, please look at one of these tutorials:
How can I keep my fork in sync without adding a separate remote?
How do I update a GitHub forked repository?
Support
This thread. Feature requests accepted.
Telegram (testing and intermediate releases).
GitHub Pull Requests if you want to contribute.
Credits
Samsung for kernel sources
fart1-git for disabling DEX cable vendor lock
corsicanu for default blocklist of wakelocks for boeffla_wl_blocker driver
Nico (@NicoMax2012) for porting moro sound module
bamsbamx for porting boeffla_wakelock_blocker
thehacker911 for general improvements and advices
ExtremeGrief for overall improvements, porting maple scheduler
geiti94 for his advices
topjohnwu for Magisk
franciscofranco for FK Kernel Manager
and testers.
I'm sorry if I missed someone, just write me and I will update the list.
XDA:DevDB Information
[KERNEL] CRUEL KERNEL S10/Note10, Kernel for the Samsung Galaxy S10
Contributors
evdenis, evdenis
Source Code: https://github.com/CruelKernel/samsung-exynos9820
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: v3.9
Stable Release Date: 2020-12-01
Created 2020-03-08
Last Updated 2020-12-01
How to build the kernel locally on your PC
This instructions assumes you are using Linux. Install mkbootimg (AIK tool) from osm0sis, heimdall (if you want to flash the kernel automatically).
Next:
Code:
# Install prerequisites
# If you use ubuntu or ubuntu based distro then you need to install these tools:
$ sudo apt-get install build-essential libncurses-dev libtinfo5 bc bison flex libssl-dev libelf-dev
# If you use Fedora:
$ sudo dnf group install "Development Tools"
$ sudo dnf install ncurses-devel ncurses-compat-libs bc bison flex elfutils-libelf-devel openssl-devel
# Install mkbootimg
$ wget https://github.com/osm0sis/mkbootimg/archive/master.zip
$ unzip master.zip
$ cd mkbootimg-master
$ sed -i -e 's/-Werror//g' Makefile
$ make
$ sudo mv mkbootimg /usr/local/bin/mkbootimg
# Get the sources
$ git clone https://github.com/CruelKernel/samsung-exynos9820
$ cd samsung-exynos9820
# List available branches
$ git branch -a | grep remotes | grep cruel | cut -d '/' -f 3
# Switch to the branch you need
$ git checkout cruel-v3
# Install compilers
$ git submodule update --init --recursive
# Compile
$ ./build mkimg name=CustomCruel model=G973F +magisk+canary +wireguard +ttl +cifs +nohardening
# You will find your kernel in boot.img file after compilation.
$ ls -lah ./boot.img
# You can automatically flash the kernel with heimdall
# if you connect your phone to the PC and execute:
$ ./build :flash
# Or in a single command (compilation with flashing)
# ./build flash name=CustomCruel model=G973F +magisk+canary +wireguard +ttl +cifs +nohardening
Pin problem
The problem is not in sources. It's due to os_patch_level mismatch with you current kernel (and/or twrp). CruelKernel uses common security patch date to be in sync with the official twrp and samsung firmwares. You can check the default os_patch_level in build.mkbootimg.* files. However, this date can be lower than other kernels use. When you flash a kernel with an earlier patch date on top of the previous one with a higher date, android activates rollback protection mechanism and you face the pin problem. It's impossible to use a "universal" os_patch_level because different users use different custom kernels and different firmwares. CruelKernel uses the common date by default in order to suite most of users.
How can you solve the problem? 5 ways:
You can restore your previous kernel and the pin problem will gone
You can check the os_patch_level date of your previous kernel here https://cruelkernel.org/tools/bootimg/ and patch cruel kernel image to the same date. If your previous kernel is nemesis, patch cruel to 2099-12 date.
You can reboot to TWRP, navigate to data/system and delete 3 files those names starts with 'lock'. Reboot. Login, set a new pin. To fix samsung account login, reinstall the app
You can rebuild cruel kernel with os_patch_level that suites you. To do it, you need to add the line os_patch_level="<your date>" to the main.yml cruel configuration. See the next section if you want to rebuild the kernel.
You can do the full wipe during cruel kernel flashing
Good job!
Thanks Dev! Does this kernel work also with LineageOS and AOSP roms?
evdenis said:
...
After that you need to add the line os_patch_level="<your date>" to the main.yml cruel configuration and rebuild it. See the customization section if you want to rebuild the kernel.
Click to expand...
Click to collapse
Did you checked it if it works for you? For me the oneliner didnt work in main.yml. I must edit the build.mkbootimg.G975F file and rebuild. Then i got no pin problems cause the OPL was now changed.
hanspampel said:
Did you checked it if it works for you? For me the oneliner didnt work in main.yml. I must edit the build.mkbootimg.G975F file and rebuild. Then i got no pin problems cause the OPL was now changed.
Click to expand...
Click to collapse
Yes, I checked that it works. Here you did't use os_patch_level setting and the date is 2020-02. Next, you updated os_patch_level and you can see the date changed if you unfold "Show information about build" section in build log. In the third commit you removed the os_patch_level and cancelled the build, so the date reverted to default one 2020-02. And in finial commit the date was changed in build.mkbootimg.G975F file. If you doubt the date changed, you can check the build settings either in "Show information about build" section in build log or in "Kernel Configuration Info" file next to the kernel image in "Artifacts". Thanks!
Valentino911 said:
Thanks Dev! Does this kernel work also with LineageOS and AOSP roms?
Click to expand...
Click to collapse
As for now, it compatible only with Samsung based firmwares. Works on native samsung firmwares, BeyondROM, on Ambasadii it's better to use Nemesis kernel (you will face pin problem if you try to install cruel). The kernel doesn't work on LOS.
Anybody want gcam for exynos.. u can see tgis video it for android Q one ui 2.0 for s10plus exynos
I have a question . The hadest rum was established, respectively the hadest kernel. I install the cruel kernel, but after the reboot the kernel of the hadest returns. Why? The first time I encounter this phenomenon, How to solve the problem?
Before rebooting the cruel core, the necessary functions work. After a reboot, the hades kernel returns.
@evdenis
I got problems with your latest sources (3.0 and 3.1). It doesnt boot to recovery with an app. This works for a few commits earlier(last week or so). Now its not working. And the OSPL in main.yml doesnt work for me too. Doesnt pass the restart pin. But thats not a problem, changed it in the other side.
Cant test your compiled versions, pin problem, i was on nemesis kernel, so i have to compile it myself.
Another problem ive saw, the device doesnt shut down. It only reboots. Compiled with 3.0 and 3.1 sources. With the older source a week ago, it works.
Edit: So tried your released v3.1 and changed the OSPL manually for PIN Fix, seems to work(recovery and shutdown). Maybe something went wrong on my side till compiling. Have no clue atm.
hanspampel said:
Another problem ive saw, the device doesnt shut down. It only reboots. Compiled with 3.0 and 3.1 sources. With the older source a week ago, it works.
Edit: So tried your released v3.1 and changed the OSPL manually for PIN Fix, seems to work(recovery and shutdown). Maybe something went wrong on my side till compiling. Have no clue atm.
Click to expand...
Click to collapse
This could be due to enabling non-default configuration presets, like +nodebug or +nohardening2.
elchinemil said:
I have a question . The hadest rum was established, respectively the hadest kernel. I install the cruel kernel, but after the reboot the kernel of the hadest returns. Why? The first time I encounter this phenomenon, How to solve the problem?
Before rebooting the cruel core, the necessary functions work. After a reboot, the hades kernel returns.
Click to expand...
Click to collapse
Hades rom uses very good kernel. Technically, I don't see any reason to change it on hades rom, unless you really want to experiment with, for example, +1000hz or +bfq scheduler.
The reason the previous kernel restores back could be again due to patch level mismatch.
I will update installation method in the next version to dynamically repack kernel during installation procedure. Hope, this will solve os_patch_level problem (pin issue) once and for all.
nice kernel
Thanks for this wonderful kernel! It is an honour for me to be able to participate in this!
G975N
Working in 975N or not
hamidru said:
Working in 975N or not
Click to expand...
Click to collapse
If it works om F/FD devices. It will work on N devices
hamidru said:
Working in 975N or not
Click to expand...
Click to collapse
If it's an exynos device ... no reason to this