Develop Bugs

[KERNEL] Semaphore ICS 1.3.0

This is a kernel based on the pawitp's one and it works for Android 4.0.x ICS ROMs.
Features
- LiveOC
- Custom Voltage
- Voodoo Sound
- BLN
- 373.5MB - 398.7MB available RAM
- Compiled with Linaro 4.7.2
- O3 optimization
- Semaphore Script Manager 0.75
- Auto brightness driver
- Touch Wake
- Vibration intensity
- Deep Idle
- USB host driver
- Governor ondemand (default)
- ondemand: sampling_down_factor tunable by momentum, smooth_ui
- Governor conservative (module, smooth_ui)
- Governor smartassV2 (module, smooth_ui)
- Noop I/O scheduler (default)
- Deadline I/O Scheduler (module)
- Simple I/O Scheduler (module)
- CFQ I/O Scheduler (module)
- Netfilter (iptables) as modules
- CIFS as module
- TUN as module
- Logcat disabled (as module only)
- Standard network packet scheduler
- Kernel log buffer size 4KB (from 128KB)
- Reduced debug info
- TinyRCU
- Fast Charge support
- WiFi PM_MAX when suspend
- CWM 6.0.1.0
- /system/etc/init.d directory creation if not exist
In order to load various modules of the kernel and enable or disable features use HM.Carbide's Semaphore Script Manager application. It automatically copies and runs the respective scripts from /res/scripts to /system/etc/init.d directory. The scripts:
- S05enable_oc_0800 (disable overclocking - caps max freq to 800Mhz)
- S05enable_oc_1000_default (disable overclocking)
- S05enable_oc_1100 (enable overclocking - max freq 1100MHz)
- S05enable_oc_1140 (enable overclocking - max freq 1140MHz)
- S05enable_oc_1200 (enable overclocking - max freq 1200MHz)
- S10enable_gov_conservative (load and enable conservative governor module)
- S10enable_gov_ondemand_default (enable ondemand governor)
- S10enable_gov_smartassV2 (load and enable conservative smartassV2 module)
- S15enable_sched_deadline (load and enable the deadline I/O scheduler module)
- S15enable_sched_noop_default (enable noop scheduler)
- S15enable_sched_sio (enable and load SIO scheduler module)
- S20enable_netfilter (load netfilter modules for firewall or WiFi, USB tethering)
- S30enable_logger (enable logging)
- S35enable_tun (load tun module)
- S40enable_cifs (load cifs module)
Custom Voltage may be configured with Voltage control or similar applications.
For more information check the semaphore kernel website: www.semaphore.gr
For questions or issues about Semaphore Script Manager please visit HM.Carbide thread
Thanks to Superuser, you may download a wonderful custom bootanimation for CM9 from http://www.semaphore.gr/downloads/boot-animations
Thanks to
pawitp for his kernel.
zacharias.maladroit for his useful information about CM's initramfs
HM.Carbide for his Semaphore Script Manager application.
Ezekeel for LiveOC, Custom Voltage
sztupy for USB host driver
koush for CWM
xcaliburinhand for his work about dock support
mialwe for his vibrator intensity and other fixes
ShadowInkDesigns for Android logo
trailblazerz11 for his help with Linaro and other changes
DerTeufel1980 for various hints
All people who support this kernel by testing, reporting issues, donating or simply using it.
Change log
1.3.0 (30/07/2012)
- added CFQ scheduler as module
- in call volume settings (thanks to DerTeufel for his hint)
- fix charging display for car dock (thanks to pawitp)
- CWM 6.0.1.0 (thanks to koush) *
- CWM: added AROMA Filemanager (thanks to amarullz)
- compiled with Linaro 4.7.2 201207
Normal versions (for CM9 or ROMs without hugemem configuration)
1.3.0
- 373.5MB - 385.7MB
For Slim ROM or patched ROMs with hugemem configuration
1.3.0s
- 386.5MB - 398.7MB
* Nandroid backups with CWM 6 are not compatible with previous versions.
1.2.6 (07/07/2012)
- USB mass storage disable write speed cache support (thanks kasper_h, DerTeufel1980 for the hint)
- CWM: Allow key to repeat on hold (thanks to FaultException, koush). Works for volume up, down and touch key menu (as down)
- CWM: fix selection bar color when battery < 21%
- CWM: upstream sync (thanks to koush) *
- initramfs sync some changes with CM9 (adb works in root by default in recovery)
- compiled with linaro 4.7.1 201206
Normal versions (for CM9 or ROMs without hugemem configuration)
1.2.6
- 373.5MB - 385.7MB
For Slim ROM or patched ROMs with hugemem configuration
1.2.6s
- 386.5MB - 398.7MB
* Please note that due to changes in nandroid backup/restore, previous versions of Semaphore can't restore backups from version >= 1.2.6. To be on the safe side, please renew your backups.
1.2.5 (19/06/2012)
- rebased to 3.0.17 (thanks to trailblazerz11 and eugene373 for their github)
- compiled with Linaro 4.7.1 toolchain (thanks to trailblazerz11 for his help)
- O3 optimization flag
- upstream sync (fixes for cdma in-call volume and mic gain included, thanks to pawitp, efpophis)
- WiFi PM_MAX when suspended
- fixed 800MHz underclocking
- changed boot splash screen
Normal versions (for CM9 or ROMs without hugemem configuration)
1.2.5
- 373.5MB - 385.7MB
For Slim ROM or patched ROMs with hugemem configuration
1.2.5s
- 386.5MB - 398.7MB
1.2.2 (01/06/2012)
- Bootloop detection (if no normal boot is detected the phone will be forced to recovery in next boot) *
- bugfix: enabling Wi-Fi hotspot twice (copy the new netfilter script in order this to work by disabling and then enabling again netfilter in Semaphore app)
- creation of /system/lib/modules if does not exist
- removed LMK scripts
- fix some typos in scripts description (thanks to cdmackay, HiKsFiles)
* It doesn't mean that this will necessarily resolve the known bootloop issue, but it may help on bootloops because of bad OC/UV etc.
Full changelog: http://www.semaphore.gr/changelog/ics-version
Deep Idle Guide and FAQ
Sources
The Linux Kernel
Samsung Kernel sources
Semaphore kernel sources
Please use it at your own risk!
The attachment zip files are for flashing from CWM recovery.
The attachment tar files are for flashing through Heimdall/ODIN.
Attachment files md5sum:
4a963c5183993b256c5a0d52f88bc2c7 Semaphore_ICS_1.2.6.zip
408178563587859c31a4c5a90b394166 Semaphore_ICS_1.2.6s.zip
3a0ca16342f811dfd9666ce3633a20b6 Semaphore_ICS_1.2.6.tar
c53114e74530e68c3b5cddb424343e8b Semaphore_ICS_1.2.6s.tar
753748fba3b590babcbfb76857bf609d Semaphore_ICS_1.3.0.zip
a6f0d7c9d2254d9a178248d48cf3de45 Semaphore_ICS_1.3.0s.zip
1e71744541d74fdd60d6b43c2dc767c7 Semaphore_ICS_1.3.0.tar
09e1e9806dc84c9c2e2341e38ebd51b0 Semaphore_ICS_1.3.0s.tar
Alternative download from http://www.semaphore.gr/downloads/gt-i9000-ics
1.2.5e Euro 2012 - Spain Special Edition

How to build Semaphore kernel
Prerequisites
Basic knowledge of Linux is required to be able to build the kernel. We will also need a modern Linux box (preferably).
Basic Setup
First, we need to setup a directory in which we will clone the kernel and initramfs repositories. In this guide, we will setup them in /tmp but you can do it in any directory you want.
In a terminal we run:
Code:
mkdir /tmp/semaphore
cd /tmp/semaphore
Then we clone the basic kernel repository:
Code:
git clone https://github.com/stratosk/samsung-kernel-aries
Finally we clone the initramfs repository:
Code:
git clone https://github.com/stratosk/ics-ramdisk
OK, first step done. We got the code. Now we have to do some preparation and compile it.
Configuration
I prefer to use a mini ugly script to compile the kernel and pack it. It's located in the root of the kernel tree (/tmp/semaphore/samsung-kernel-aries/sbuild.sh)
We open this file with an editor of our choice (I prefer vi) and edit:
1) The two lines with the 'make' command, changing the CROSS_COMPILE= option. We need to set the path from the cross compiler toolchain. I use the one that it's included in CM9 repository.
2) The line starting with the 'find' command, changing the kernel source directory and destination directory of the modules location. This is into the initramfs directory. In our example it's /tmp/semaphore/ics-ramdisk/ics_combo/files/modules
The Semaphore's kernel configuration is located in the file config_sema in the root kernel directory. So, we need to copy this file as .config:
Code:
cp config_sema .config
Then we run this command to start the Linux kernel configuration utility (again change the CROSS_COMPILE according to your toolchain directory):
Code:
make CROSS_COMPILE=/kernels/semaphore_cap/android/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- ARCH=arm menuconfig
We go to 'General Setup' section and we change the 'Initramfs source files' option to /tmp/semaphore/ics-ramdisk/ics_combo/
We also need to change the next 2 options User ID and Group ID to whatever uid and gid we are logged in in the Linux box. In my case is 500,500. We exit and save the configuration.
Compiling
Now we are ready to build the kernel!
We just run:
Code:
./sbuild.sh
We wait few minutes (time depends on the machine) and hopefully the compilation will end.
The script will produce 2 files.
1) /tmp/semaphore/samsung-kernel-aries/arch/arm/boot/zImage
2) /tmp/semaphore/ics-ramdisk/cwm/Semaphore_ICS_1.2.0s.zip
These are the 2 known files that we can flash via Heimdal or CWM respectively.

just flasshing

Nice.Finally.
Downloading.

w00t, nice job Semaphore
Now on ICS ^^

thanks for the hard work!

Simply flashtastic!!! I was missing you on ics...
Enviado de mi puño y letra

i get bootloop grgrgr someelse? or maybe some restart by script manager? idk testing..

Works ok.
Gps,wifi,compass,scripts.
Good job.Finally ics from stratosk.
Nice work

Will you be implementing Voodoo Colour as well?

F1tty said:
i get bootloop grgrgr someelse? or maybe some restart by script manager? idk testing..
Click to expand...
Click to collapse
Semaphore Script Manager application is not bundled in the kernel (not yet).
I'm on teamhacksung's CM9. I didn't test it on Onecosmic's ICS.

qureshali said:
Will you be implementing Voodoo Colour as well?
Click to expand...
Click to collapse
I really don't know. I think that the pawitp's color hacks is fine.
I just want to stabilize this first. Features from Semaphore GB version will be added one by one and if there is a need for this. Lot's of features are already included by pawitp's kernel.

Re
This is just what i was waiting for... downloading now i feel like trolling everywhere out of happiness

No prob. mate! Take your time. We all love your work & Kernel!!

I also think that it's no need for voodoo colour.
This colours looks very good.

You're the man... dude

I can flash this on onecosmic rom? ( rc3.1)

Broeser said:
I can flash this on onecosmic rom? ( rc3.1)
Click to expand...
Click to collapse
I've never tried it.
F1tty reported bootloops. I really don't know what's the differences.

Broeser said:
I can flash this on onecosmic rom? ( rc3.1)
Click to expand...
Click to collapse
we will all going to find out when i will flash it to 3.1 until then....
geia soy re strato partous ta sovraka kai sto 4.0.3

Awesome, will try on build 15 right away - loaded and everything seems ok.
first impression is: great color and contrast! it's like I have 3d on my sgs now!
wifi ok, 3g ok (switches really fast, great), calling ok, sensors ok (for dialer), gps ok, whatsapp, gmail.
thank you very much!

[Kernel]Various Experimental Kernels

Google Glass Experimental Kernel Builds​
I don't have the google glass, but making a kernel is possible for all devices so why not. I have made some experimental builds using the official google kernel source and using the regular arm-eabi-4.4.3 toolchain because other toolchains gave errors while compiling.
I didn't test these kernels but they should work fine as they are built from official sources with the right defconfig, anyways, you're fully responsible for any damage caused to your expensive sunglasses :silly:
Initial Source: https://android.googlesource.com/kernel/omap/+log/glass-omap-xrr02/
Defconfig: notle_defconfig
Toolchain: arm-eabi-4.4.3
My source:
https://github.com/broodplank/glass-omap-xrr02
Installation guide:
Download the kernel you want, place it in a directory that contains fastboot and adb and rename it to boot.img
Then enter (if unlocked):
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Or when locked:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash boot boot.img
fastboot reboot
Build #1 (stock boot.img with ro.secure 0 and modified adbd binary)
Based on stock boot.img from google
Info:
- Stock kernel
- ro.secure=0
- Modified adbd binary
Build param
unknown, probably -o2 since defconfig has -o2 default.
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=2005346&stc=1&d=1369959602
Build #2 (Custom kernel built on -O3 param)
Ramdisk Based on build 1's ramdisk
Info:
- Fully optimized
- Compiled from source
- Added governor: smartassV2 (set as default)
- ro.secure=0
- Modified adbd binary
Build param
-O3 -fmodulo-sched -fmodulo-sched-allow-regmoves -fno-tree-vectorize
Warning: I don't know what the partition size is of the boot partition, if its under 5mb do not use this one (check cat /proc/partitions)
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=2005351&stc=1&d=1369960135
Build #3 (Custom kernel built on -O2 param)
Ramdisk Based on build 1's ramdisk
Info:
- Optimized a bit
- Compiled from source
- Added governor: smartassV2 (set as default)
- ro.secure=0
- Modified adbd binary
Build param
-O2
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=2005352&stc=1&d=1369960222
Build #4 (Custom kernel built on -OS param)
Ramdisk Based on build 1's ramdisk
Info:
- Optimized for size
- Compiled from source
- Added governor: smartassV2 (set as default)
- ro.secure=0
- Modified adbd binary
Build param
-Os
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=2005361&stc=1&d=1369960340

First !!. Wonderful work brood !:good:

UpGado said:
First !!. Wonderful work brood !:good:
Click to expand...
Click to collapse
Thank you , do you own the glasses btw?

broodplank1337 said:
Thank you , do you own the glasses btw?
Click to expand...
Click to collapse
No , But I liked the idea of custom kernel for glasses

[ROM] [Guide] [Linaro] Unofficial CM 10.2 (12th August) build

I managed to build CM 10.2 using linaro toolchain. (In case you decide to install this ROM, standard CM 10.2 disclaimers apply)
Here are the steps to do it:
1. Download cm 10.2 using this link (http://wiki.cyanogenmod.org/w/Build_for_maguro)
2. Before you execute the command "source build/envsetup.sh" do the following steps:
2.1 Download linaro toolchain from here (http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-bzr)
2.2 Download linaro kernel toolchain from here (http://forum.xda-developers.com/showthread.php?t=2098133)
2.3 Extract these toolchains to any directory of your choice.
3. In file build/setenv.sh change ANDROID_EABI_TOOLCHAIN & ARM_EABI_TOOLCHAIN to point to linaro toolchain that was downloaded.
4. In file build/core/tasks/kernel.mk change toolchain from ARM_EABI_TOOLCHAIN to the linaro kernel toolchain. (If you do not do this step, the cm 10.2 kernel will not be compiled with linaro)
5. In file build/core/combo/TARGET_linux-arm.mk change TARGET_TOOLCHAIN_ROOT to the linaro toolchain
6. Continue the steps mentioned in the link of step 1 (source build/envsetup.sh, breakfast maguro, extract-files.sh, brunch maguro)
Download links:
1. ROM - http://www.mediafire.com/?m55nmvhc96xywoj
2. GAPPS - http://forum.xda-developers.com/showthread.php?t=2379296
I will keep building this ROM as and when I find time.
Shyam

[ROM][HONAMI][KK][4.4.4][LINARO/SABERMOD] SlimKat [WEEKLY BUILDS][7.4]

Z1/HONAMI/C6903 SLIMKAT LINARO/SABERMOD WEEKLY BUILDS
Weekly Build 7.4 is ONLINE
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.9.1 201407 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 201407 toolchain
-O3 optimizations
strict-aliasing rules
custom performance flags
+30 cherry-picks used
(buildbot: intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 17 "Qiana" x64 3.13.0)
DONATIONS NEEDED
if you can, please make a small donation... you'll be supporting my work and time spent on these projects, helping me to keep website and dedicated server up and running, so i can deliver the downloads, host the builds, and pay the webdev.
The remaining donations, if any, ill go to a "piggy bank", to buy new devices...
Many thanks.
infected_
Click to expand...
Click to collapse
Disclaimer:
These builds are freshly compiled/synced from SlimRoms open-source code:
https://github.com/SlimRoms
latest linaro arm-eabi-4.9.1 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.4 toolchains to compile ROM code
Special Thanks
SlimRoms Dev Team​
XDA:DevDB Information
Xperia Z1/Honami/C6903 Linaro/Sabermod SlimKat Builds, ROM for the Sony Xperia Z1
Contributors
infected_
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest CWM Recovery or TWRP
Based On: SlimRoms
Version Information
Status: Testing
Current Stable Version: 7.0
Stable Release Date: 2014-08-05
Created 2014-07-24
Last Updated 2014-08-19

Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-developers.com/showthread.php?t=2397942

F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of SlimKat for the Xperia Z1/Honami/C6903
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.9.1 14.07 (kernel code) & sabermod arm-linux-androideabi 4.8.4 14.07 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse

OMG
SLIMKAT
GOOD WORK MAN

I wonder if this build is faster than Vanir

it's super fast u must try it :good:

charging slow as turtle

Really nice man.. Slim and Linaro makes superfast
Sent from my Xperia Z1 using Tapatalk

Works well, really smooth.
Sent from my Xperia Z1 using XDA Premium HD app

Definitely a charging problem, takes a while and only reaches 98% max.
Apart from that its everything I expected
Sent from my Xperia Z1 using XDA Premium HD app

MacSeoin said:
Definitely a charging problem, takes a while and only reaches 98% max.
Apart from that its everything I expected
Sent from my Xperia Z1 using XDA Premium HD app
Click to expand...
Click to collapse
Yep everything perfect expit the charging
Sent from my Xperia Z1 using Tapatalk

weekly 6.8 is up.
regards.
ps: lots of changes to kernel ..

Is it just me or camera is flaky (freezes and doesnt work) like older builds?

Camera not work. Freeze and flashlight automatic on and off. Also charging is slow, reach 96% and slowly to 100% (2hours). Try reflash original Slimkat and not of problems happen. So must be this............

weekly 7.0 is up.
regards.

infected_ said:
weekly 7.0 is up.
regards.
Click to expand...
Click to collapse
su binary seems to be missing, so no root!
i did a clean install with the latest pa mini gapps.

steveeJ said:
su binary seems to be missing, so no root!
i did a clean install with the latest pa mini gapps.
Click to expand...
Click to collapse
Enable root on developer options...
Sent from my Xperia Z1 using Tapatalk

I see there is a slim governor, I couldnt find anything about it... Care to shed us some light about it?
And... Do you have your sources or some kind of changelog?
Builds are hella fast though, great work man!

weekly 7.2 is up.
regards.

seems there were missing some commits on Slim code, in the weekly build...
compiling 7.2.1
edit: 7.2.1 is up.

[KERNEL][2020-12-01] CRUEL KERNEL S10/Note10 V3.9

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