[ Lulz Kernel ]
Features
*prevents unintended home-key double click
- https://github.com/tegrak/lulz-kernel_gt-i9100/commit/070955b710c945bcdd3017bc80d93e087d39f4e3
*supports Voodoo Louder
- https://market.android.com/details?id=org.projectvoodoo.louder
*supports Lulzactive governor v2 (default)
- http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html
*supports 2nd Core
- http://tegrak2x.blogspot.com/2011/11/2nd-core.html
*SLAB allocator
*supports advanced touch tune driver
- thanks to vitalij Link
- the control app "Touch Move" from Web, from Mobile
- driver patch file download
*supports BLN
- thanks to creams and neldar.
- get the source from creams' blog http://creamsnexus.blogspot.com/
*supports clockworkmod recovery 4.0.1.5 Link
- Thanks to codeworkx
*supports BFQ v3-r1 scheduler (default) Link
*CPU scaling level is changed from 5 to 7 (1204/1152/1100/1000/800/500/200MHz)
*includes Tegrak Kernel functions
*based on GT-I9100 gingerbread_update3 source
*supports Interactive governor Link
*supports CIFS
*jhash3
Lulz Kernel Build 3 Changelog
*built from the latest kernel source. (SHW-M250S EE31)
*added BFQ IO scheduler.
Lulz Kernel Build 4 Changelog
*added Lulzactive governor.
- http://tegrak2x.blogspot.com/2011/07/lulzactive-governor.html
*kernel uses additional frequencies more efficiently
Lulz Kernel Build 5 Changelog
*fixed a wakeup issue of lulzactive governor!
- now online!
*fixed failures when kernel loads drivers.
- WIFI issue is from it. it's fixed!
Lulz Kernel Build 6 Changelog
*Set BFQ scheduler as default
*Fixed a bug about a locked frequency by touch screen
- cpu driver changes min frequency to 500MHz when touch screen works.
- before build 6, it set 1000MHz because of additional frequency steps.
*Fixed a interactive governor issue
- the issue is phone couldn't wake up after suspending.
Lulz Kernel Build 7 Changelog
*Fixed a lulzactive governor bug
- CPU used 1.0GHz instead of 200MHz(min freq) while suspend mode.
*Change CPU driver
- set min freq when kernel completes to enter suspend mode. (original driver set 1.0GHz)
Lulz Kernel Build 8 Changelog
*supports clockworkmod recovery 4.0.0.2
- you can choose one of recovery <3e> and clockworkmod.
- thanks to koush. http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
*uses XXKG1 initramfs.
Lulz Kernel Build 11 Changelog
*supports clockworkmod recovery 4.0.1.4
- thanks to codeworkx. http://forum.xda-developers.com/showthread.php?t=1118693
*upgraded BFQ to v2-r1
*set lulzactive governor as default.
- I decided it to make a sure difference from the stock kernel.
*removed additional file system support
- NILFS2, BTRFS and etc
*uses GT-I9100 gingerbread_update1 source code
- applied new source code for 2.3.4
Lulz Kernel Build 12 Changelog
*supports BLN
- thanks to creams and neldar.
- get the source from creams' blog http://creamsnexus.blogspot.com/
- how to enable BLN http://forum.xda-developers.com/showpost.php?p=16283045&postcount=696
Lulz Kernel Build 13 Changelog
*built from the latest kernel source. (SHW-M250S EG14)
Lulz Kernel Build 14 Changelog
*built from the latest kernel source. (GT-I9100 Update2)
*supports advanced touch tune driver.
- Download Touch Move!
- https://market.android.com/details?id=com.tegrak.touchmove
- market://details?id=com.tegrak.touchmove
Lulz Kernel Build 15 Changelog
*supports 2nd Core for multi-core control.
- http://tegrak2x.blogspot.com/2011/11/2nd-core.html
*built from the latest kernel source. (GT-I9100 Update3)
*supports clockworkmod recovery 4.0.1.5
- this is the latest stable version.
*changed SLAB allocator from SLOB to SLAB
Lulz Kernel Build 16 Changelog
*Lulzactive governor v2
- added detail options
- provides an app to control detail options
- screen off maximum freq is 500MHz (before this, used 200MHz)
- http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html
*BFQ update
- BFQ-v3-r1 is applied.
*-O3 optimization
*jhash3
*disabled "MMC discard debugging" option
Lulz Kernel Build 17 Changelog
*prevents unintended home-key double click
- we are free from home-key stress!
- https://github.com/tegrak/lulz-kernel_gt-i9100/commit/070955b710c945bcdd3017bc80d93e087d39f4e3
*supports clockworkmod recovery 5.0.2.3
(and please read Tegrak Kernel Build 30 update details)
Lulz Kernel Build 18 Changelog
*supports Voodoo Louder
- https://market.android.com/details?id=org.projectvoodoo.louder
Download
Source https://github.com/tegrak/lulz-kernel_gt-i9100
Lulz-Kernel-Build-3-for-I9100-ZSKF4.tar
*includes Tegrak Kernel Build 25
*includes ZSKF4 initramfs
Lulz-Kernel-Build-5-for-I9100-ZSKF4.tar
*includes Tegrak Kernel Build 25
*includes ZSKF4 initramfs
Lulz-Kernel-Build-6-for-I9100-ZSKF4.tar
*includes Tegrak Kernel Build 25
*includes ZSKF4 initramfs
Lulz-Kernel-Build-7-for-I9100-ZSKF4.tar
*includes Tegrak Kernel Build 25
*includes ZSKF4 initramfs
Lulz-Kernel-Build-8-for-I9100-XXKG1.tar
*includes Tegrak Kernel Build 25
*includes XXKG1 initramfs
*REMOVED. too many problems with 2.3.4 ROM
Lulz-Kernel-Build-11-for-I9100-XXKG2.tar
*includes Tegrak Kernel Build 25
*includes XXKG2 initramfs
Lulz-Kernel-Build-11-for-I9100-XXKG3.tar
*includes Tegrak Kernel Build 25
*includes XXKG3 initramfs
Lulz-Kernel-Build-11-for-I9100-XXKG6.tar
*includes Tegrak Kernel Build 25
*includes XXKG6 initramfs
Lulz-Kernel-Build-12-for-I9100-XXKG6.tar
*includes Tegrak Kernel Build 25
*includes XXKG6 initramfs
Lulz-Kernel-Build-13-for-I9100-XXKH3.tar
*includes Tegrak Kernel Build 26
*includes XXKH3 initramfs
Lulz-Kernel-Build-14-for-I9100-XWKI8.tar
*includes Tegrak Kernel Build 26
*includes XWKI8 initramfs
Lulz-Kernel-Build-15-for-I9100-XWKJ2.tar
*includes Tegrak Kernel Build 29
*includes XWKJ2 initramfs
*not fully tested. welcome to report any bugs.
Lulz-Kernel-Build-15-for-I9100-XWKJ3.tar
*includes Tegrak Kernel Build 29
*includes XWKJ3 initramfs
Lulz-Kernel-Build-16-for-I9100-XWKK2.tar
*includes Tegrak Kernel Build 29
*includes XWKK2 initramfs
Lulz-Kernel-Build-16-for-I9100-XWKK5.tar
*includes Tegrak Kernel Build 29
*includes XWKK5 initramfs
Lulz-Kernel-Build-17-for-I9100-XWKL1.tar
*includes Tegrak Kernel Build 31
*includes XWKL1 initramfs
Lulz-Kernel-Build-18-for-I9100-XWKL1.tar
*includes Tegrak Kernel Build 31
*includes XWKL1 initramfs
-----------------------------------------------------------------------
[ Tegrak Kernel ]
KERNELS IN HERE DO NOT SUPPORT CWM RECOVERY.
You need to know this before flashing!
This is a custom kernel based on the stock kernel.
NOT built from the source, only repacked initramfs of the stock kernel.
So this doesn't affect your battery time or performance. Just same as stock kernel.
It's only for providing useful functions. (but provide lagfix options on Galaxy S)
Supports I9100, I9000, M250S, M250K, M250L, M110S, M130K, M130L, M180S, M180L, YP-GB1 (Korea Galaxy S II, Galaxy S, Galaxy Tab, Galaxy Player models)
Tegrak Kernel application has been downloaded over 200,000.
Tegrak Kernel for Galaxy S can be found in here. http://forum.xda-developers.com/showthread.php?t=920711
TEGRAK KERNEL GUIDE
made by Cypher_X and marcedli
It's written for GT-I9000 Galaxy S, but kernel has same recovery mode.
2. Tegrak Recovery Guide
Download
http://tegrak2x.blogspot.com/2011/12/tegrak-kernel-downloads.html
Features
*one click rooting and unrooting by app. need no reboot.
*reboot, reboot download mode, reboot recovery mode commands without rooting
*provide a custom recovery mode named "Tegrak recovery". (see below for details)
*always root permission on adb shell. (also adb is enabled in 3e recovery mode)
UPDATE in build 31 2011-12-30 KST
*fixed a restoring bug.
- symbolic link files weren't restored on build 30.
UPDATE in build 30 2011-12-30 KST
*fixed a rooting problem
- after "Disable rooting", some banking apps still said "rooted phone".
*mount option
- applied noatime, nodiratime on all partitions.
*update tegrak recovery mode
- changed UI.
- fixed blinking screen while moving items in menu.
- scroll screen up when there are too many text outputs.
- add a selection key. now you use Home and Power key to select a menu.
- you can navigate your sdcard at "update from zip package" menu
- prevent unintended selection key double-clicking.
*improved backup/restoring
- backups are changed from .bak to .tar.
- you can see contents in backups via archive managers on PC.
- (caution) if you modify backup tar file, you can't use that for restoring.
- show progressbar status while backup and restoring.
UPDATE in build 29 2011-10-28 KST
fixed bugs when do rooting and un-rooting
minor bug fixes
UPDATE in build 27 2011-10-24 KST
changing su and Superuser app is available.
just put latest su and Superuser.apk into the /sdcard/tegrak/rooting folder.
(file names must be matched. case-sensitive.)
UPDATE in build 26 2011-08-20 KST
based on XXKH3 kernel
fixed enabling & disabling rooting problems.
fixed a restoring bug.
UPDATE in Build 25 2011-07-03 22:40 KST
based on ZSKF4, JPKG2, XXKG1, XXKG2, XXKG3 kernel
fixed the endless custom boot animation again.
UPDATE in Build 24 2011-06-21 15:13 KST
based on ZSKF4 kernel
fixed the endless custom boot animation!
adb shell enabled on Tegrak Updater Mode
fixed a "getprop" method problem at updater-script. it works now.
Tegrak Kernel boot on Galaxy S (SHW-M110S)
Installation Instructions
1. Turn off your phone.
2. Enter download mode (Volume Down + Home + Power)
3. Flashing Tegrak-Kernel-Build-xx-for-GTI9100.tar file by using Odin PDA. You must install latest stock firmware before.
4. Install "Tegrak Kernel" application from Android Market.
Web link: https://market.android.com/details?id=com.tegrak.lagfix
Mobile link: market://details?id=com.tegrak.lagfix
Kernel
*supports a custom boot animation.
- put the animation zip file to /system/media/sanim.zip
- if you delete sanim.zip, kernel shows the default boot animation.
- here is a sample. LG Optimus 2X boot animation install zip. try to apply this at Tegrak recovery mode > UPDATE: from zip package.
- Get more animation from here by xtrememorph
*supports init.d
- run all binary and shell script files in the /system/etc/init.d folder on boot time.
Tegrak Kernel app
Web link: https://market.android.com/details?id=com.tegrak.lagfix
Mobile link: market://details?id=com.tegrak.lagfix
*Enable rooting
- install su and Superuser.apk in the system folder.
- need no reboot. Rooting takes 0.5 second.
*Disable rooting
- unrooting.
- also need no reboot. Unrooting takes 0.5 second.
*Reboot
- run reboot command without rooting.
*Reboot download mode
- enter download mode without rooting.
*Reboot recovery mode
- enter 3e recovery mode without rooting.
*Power off
- shutdown the system.
Tegrak Recovery Mode
To enter this mode, you have to press home key on boot. You can see the message on the screen.
*EXIT: exit recovery
- continue boot
*UPDATE: from zip package
- install update.zip files. (not using clockworkmod)
- put the zip packages in /sdcard/tegrak/update folder.
- you can choose one of zips by using volume keys.
*UPDATE: from internal sdcard
- copy files from your internal sdcard.
- /sdcard/tegrak/update/00 ~ 05
- if you put framework-res.apk to /sdcard/tegrak/update/00/system/framework/ folder and run 00 folder, it overwrites your frameworks-res.apk.
*UPDATE: from external sdcard
- copy files from your external sdcard.
- /sdcard/external_sd/tegrak/update/00 ~ 05
*RESTORE: /system
- restore your system folder with a backup-ed file.
*BACKUP: /system
- create a backup file (whole system folder) in /sdcard/tegrak/backup/system.bak
*RESTORE: /data
- restore your data folder with a backup-ed file.
- data folder has all of your apps and apps' data. (account.. bookmarks.. etc)
*BACKUP: /data
- create a backup file (whole data folder) in /sdcard/tegrak/backup/data.bak
*RECOVERY: reboot recovery
- enter 3e recovery mode.
*DOWNLOAD: reboot download mode
- enter download mode for flahsing via Odin.
*wipe cache
- delete files in /cache
*wipe dalvik-cache
- clear /data/dalvik-cache folder.
*wipe init.d
- clear /system/etc/init.d. It's useful when you put a wrong script in there.
Do you have any question or opinion?
Leave a comment.
Contact me [email protected]
Follow me http://twitter.com/tegrak
Yes. Nice.
Tegraks no 1 fan here
Sent from my GT-I9100 using Tapatalk
Tricky103 said:
Yes. Nice.
Tegraks no 1 fan here
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Laila's no 1 fan here.
We have to stop this playing.. there will be someone who doesn't like us..
That was sudden!!!
I like it tegrak!
I like it a lot!!!
@tegrak
I bought your tool and previously used with the CF.
now after this kernel I use here to test, I find an option "tweaks ".... but I do not know what the settings mean there.
You can read this somewhere or could you describe it briefly?
finally .. backup of /data .. tegark you are my hero
Hey,
I tried to buy Overclock ultimate but android market says error try again? I have two credit cards working. Can you provide another way to buy it and put a guide for OC and recommended frequencies and voltages?
Sent from my GT-I9100 using XDA App
tegrak said:
This is a custom kernel based on the stock kernel.
NOT built from the source, only repacked initramfs of the stock kernel.
So this doesn't affect your battery time or performance. Just same as stock kernel.
It's only for providing useful functions. (but provide lagfix options on Galaxy S)
Supports I9100, I9000, M250S, M250K, M250L, M110S, M130K, M130L, M180S, M180L, YP-GB1 (Korea Galaxy S II, Galaxy S, Galaxy Tab, Galaxy Player models)
Tegrak Kernel application has been downloaded over 200,000.
Tegrak Kernel for Galaxy S can be found in here. http://forum.xda-developers.com/showthread.php?t=920711
Download
Tegrak-Kernel-Build-23-for-I9100-XWKE7.tar - STABLE!
Features
*one click rooting and unrooting by app. need no reboot.
*reboot, reboot download mode, reboot recovery mode commands without rooting
*provide a custom recovery mode named "Tegrak recovery". (see below for details)
*always root permission on adb shell. (also adb is enabled in 3e recovery mode)
Tegrak Kernel boot on Galaxy S (SHW-M110S)
How to Install
1. Turn off your phone.
2. Enter download mode (Volume Down + Home + Power)
3. Flashing Tegrak-Kernel-Build-xx-for-GTI9100.tar file by using Odin PDA. You must install latest stock firmware before.
4. Install "Tegrak Kernel" application from Android Market.
Web link: https://market.android.com/details?id=com.tegrak.lagfix
Mobile link: market://details?id=com.tegrak.lagfix
Kernel
*support a custom boot animation.
- put the animation zip file to /system/media/sanim.zip
- if you delete sanim.zip, kernel shows the default boot animation.
- here is a sample. LG Optimus 2X boot animation install zip. try to apply this at Tegrak recovery mode > UPDATE: from zip package.
*support init.d
- run all binary and shell script files in the /system/etc/init.d folder on boot time.
Tegrak Kernel app
Web link: https://market.android.com/details?id=com.tegrak.lagfix
Mobile link: market://details?id=com.tegrak.lagfix
*Enable rooting
- install su and Superuser.apk in the system folder.
- need no reboot. finish in 1 second.
*Disable rooting
- unrooting.
- also need no reboot. finish in 1 second.
*Overclock
- run Tegrak overclock app.
*Reboot
- run reboot command without rooting.
*Reboot download mode
- enter download mode without rooting.
*Reboot recovery mode
- enter 3e recovery mode without rooting.
*Power off
- shutdown the system.
Tegrak Recovery Mode
To enter this mode, you have to press home key on boot. You can see the message on the screen.
*EXIT: exit recovery
- continue boot
*UPDATE: from zip package
- install update.zip files. (not using clockworkmod)
- put the zip packages in /sdcard/tegrak/update folder.
- you can choose one of zips by using volume keys.
*UPDATE: from internal sdcard
- copy files from your internal sdcard.
- /sdcard/tegrak/update/00 ~ 05
- if you put framework-res.apk to /sdcard/tegrak/update/00/system/framework/ folder and run 00 folder, it overwrites your frameworks-res.apk.
*UPDATE: from external sdcard
- copy files from your external sdcard.
- /sdcard/tegrak/external_sd/update/00 ~ 05
*RESTORE: /system
- restore your system folder with a backup-ed file.
*BACKUP: /system
- create a backup file (whole system folder) in /sdcard/tegrak/backup/system.bak
*RESTORE: /data
- restore your data folder with a backup-ed file.
- data folder has all of your apps and apps' data. (account.. bookmarks.. etc)
*BACKUP: /data
- create a backup file (whole data folder) in /sdcard/tegrak/backup/data.bak
*RECOVERY: reboot recovery
- enter 3e recovery mode.
*DOWNLOAD: reboot download mode
- enter download mode for flahsing via Odin.
*wipe cache
- delete files in /cache
*wipe dalvik-cache
- clear /data/dalvik-cache folder.
*wipe init.d
- clear /system/etc/init.d. It's useful when you put a wrong script in there.
Do you have any question or opinion?
Leave a comment.
Contact me [email protected]
Follow me http://twitter.com/tegrak
Click to expand...
Click to collapse
Thanks for the kernel.
After I flash your kernel, my titanium backup is saying that I don't have ROOT access. It say "Sorry, I could not acquire root privileges.." Pls help..
add info:
Before I flash your kernel, I was using [CF-Root v3.7] KE2/7/8 - su+bb+CWM3 from chainfire. My titanium backup apps was fine.
@araf
had also before the cf and all is working... so, look if superuser is installed.
I am using ZSKE7 (HK and Taiwan version). Does it work for ZSKE7??
Finally, thanks @tegrak !
@diddsen, SkilletDesire
Hey this is kernel thread.. am I wrong?
@eatingking
Hmm.. I don't know that works or not. already tried?
Sent from my SHW-M250S using XDA App
I flashed the Tegrak-Kernel-Build-xx-for-GTI9100.tar file by using Odin PDA and installed "Tegrak Kernel" application. How to lagfix and run Tegrak overclock app same with I9000? No Enable tegrak lagifx (all) display in Tegrak Kernel" application.
Moreover, how to use the CWM ?
Thanks~~
I have try this kernel over angelom 1.7 rom, and it is very good kernel!
Thank's Tegrak
Does this Kernel have the yellow warning at boot?
@eatingking
there is no lagfix for s2.. and this kernel is cwm independent. I do not know how to use it.
@KillerBee
Yellow text is not warning. What is the text??????
@Lio78
Thank you~
Sent from my SHW-M250S using XDA App
After flashing this with ke7 Stock and im getting a yellow warning triangle on boot. Is this normal?
Lio78 said:
I have try this kernel over angelom 1.7 rom, and it is very good kernel!
Thank's Tegrak
Click to expand...
Click to collapse
If I'm using angelom 1.7 rom with Tegrak overclock, is there any point to installing the Tegrak kernel?
jorelleperds said:
After flashing this with ke7 Stock and im getting a yellow warning triangle on boot. Is this normal?
Click to expand...
Click to collapse
You meant that triangle? yes it's absolutely normal..
The triangle icon means you are using a custom kernel.
You can remove it by JIG. search thread~ JIG
I was referring to the yellow triangle, but you've already answered it. Thanks.
Related
_motley kernel for the Prime
Disclaimer: You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!
New version released for testing on 4.2.2 ROMs I see popping up since this is likely our future unless Asus releases something. I have been dev'ing for the N4 and N7 lately, so I haven't had a lot of time to keep up with the Prime. However, I wanted to stop by to share the kernel I built over the course of the last two nights for my own device.
Features:
Forked from namidairo (thanks!)
OC to 1.7GHz
GPU OC to 600MHz - configurable from 520-650MHz (see below)
Voltage Control (use Trickster or System Tuner)
Removed system_mode from Asus - boots to 1.4GHz - control with standard apps (use Trickster or System Tuner)
FSYNC - 3 modes (see below) (use Trickster)
Linaro built with optimizations
Kernel log spam reduced - important for our crappy eMMC
optimized ARM RWSEM algorithm
Other misc tweaks (see github)
Build 24 (beta)
Initial release for 4.2.2
AnyKernel install works on 32GB Primes only
Added blob based installs for CM 10.1 and PA. Read notes carefully below when choosing an install zip.
View attachment motley_anykernel_tf201_build_24.zip - 32 GB Primes ONLY (any 4.2.2 custom ROM)
View attachment motley_b24_CM.zip.zip - CM10.1 based ROMs only (blob based install for 32/64GB Primes)
View attachment motley_b24_AOSP_PA.zip - PA/AOSP 4.2.2 ROMs only (blob based install for 32/64GB Primes) (only tested on PA thus far! Using PA ramdisk as donor.)
Git repo:
https://github.com/motley-git/android_kernel_asus_tf201
GPU OC
Examples:
Code:
echo 520 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Code:
echo 650 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
FSYNC Control
Notes: I thought about combining these options, but many kernel apps already support these two options. So, I have them both and they can be controlled in combination to give us the 3 modes. If you set fsync_enabled = 0 it will be OFF regardless of how Dyn_fsync_active is set.
3 Modes:
Dynamic (default in b35 and higher)- fsync is asynchronous when screen is on, when screen is off it is committed synchronously
dynamic fsync ON
fsync ON
Code:
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
Off (best performance, less safe) - fsync is always asynchronous (b32 and prior builds)
dynamic fsync OFF
fsync OFF
Code:
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
Stock (safest) - fsync is always committed synchronously
dynamic fsync OFF
fsync ON
Code:
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
There is a lot of info out there on fsync, that will not be discussed here. I have run fsync off on several devices for awhile now and haven't experienced any issues. If you are using a device that is not stable and crashes alot, I recommend enabling it via init.d or script manager on boot.
See all my old tf201 kernel versions for ICS here:
Requirements (please read carefully!)
alpha version is stable for most, but changes often until we hit a good stable version. Let me know how it works!
Do a CWM backup so you can restore your boot.img and ROM if necessary!
64GB tabs please use blob based install with ramdisk. Anykernel method may not work on 64GB tablets
Recommend 1.6 or 1.7GHz. I have scored 14300+ on Antutu with 1.7GHz. 1.8 is just not necessary IMO and generates too much heat.
ICS ROMs only
You must be rooted with busybox. Busybox is used for init.d support.
You must be unlocked (Asus Unlock Tool provided on their web site)
Official CWM with latest update (see http://forum.xda-developers.com/showthread.php?t=1533697)
You should have your current full and a stock ROM including kernel on your sdcard (just in case). This is always a good idea anyhow.
Beware of third party tweaks that may conflict. If you have installed another app that will load conflicting kernel modules or provide overclocking capability for the stock kernel, please uninstall or disable this on boot before you install this kernel. For example, if you are using ATP Tweaks and are loading the CFQ or SIO schedulerd at boot, it can cause a crash as soon as the conflicting kernel module loads into memory. This kernel now includes the many features that folks were previously using kernel modules for. Since this kernel supports these features natively, you know longer need to load a kernel module manually or via a third party application unless the feature is not listed above. For example, if you use CIFS Manager, you should remove the requirement to load the CIFS kernel module in the settings as it is no longer needed with this kernel.
Stock/AOKP versions
Still using stock broadcom WiFi drivers (module built by me match stock modules)
Still use same scaling scripts from before (cpu3.sh etc.) or installed 2.6.11 first and then flash this kernel to be sure you have them right.
Same system modes apply as before (system_mode=3 for 1.6GHz, system_mode=4 for 1.7GHz, system_mode=5 for 1.8GHz etc.)
Generic kernel versions
Supports Gummy, Team EOS, and CM9 since they have the same WiFi driver implemented in their device trees.
No need to use an OC app (SetCPU, No-frills etc.) to set the clock.
WiFi driver is built-in (no kernel modules) using opensource broadcom drivers (nl80211)
KSM=y (ROM needs to enable KSM in dalvik and set scan in the init file like in CM9)
Overclock - needs init.d to be functional to run a init.d script on boot (see sample script below).
Same system modes apply as before (system_mode=3 for 1.6GHz, system_mode=4 for 1.7GHz, system_mode=5 for 1.8GHz etc.)
If you don't get deep sleep, make sure you have implemented the init.d script properly. "echo N > /sys/module/cpu_tegra3/parameters/no_lp" seems to be necessary on generic ROMs to get the proper deep sleep.
"Lite" kernel
This kernel version has been kept very close to stock form, except for OC and some basic features. The kernel won't be updated often, only when Asus releases new versions or an important fixable bug is discovered.
"Lite" Features
Based on stock Asus v9.4.2.28 base
Simple I/O scheduler as the default
OC from 1.5 to 1.7GHz (system_mode 3 = 1.5GHz, 4 = 1.6GHz, 5 = 1.7GHz)
Compiler optimizations (-o2), ARM toolchain - Code Sourcery Lite 2010.09-51
initramfs changes from stock - init.d support (your ROM must have the /system/etc/init.d folder and busybox) and the default.prop has been updated with ro.secure=0 (for "adb remount")
CIFS support (built-in, no need for kernel module)
NTFS/exFAT modules are provided in stock ramdisk - uses stock Tuxera modules. See http://www.tuxera.com/) - modules are loaded during init automatically with included initramfs.
Kernel compression mode LZMA
Input devices - PS3 (stock), XBox (CONFIG_INPUT_FF_MEMLESS and CONFIG_JOYSTICK_XPAD_FF), Other input device support (CONFIG_HID_APPLE, CONFIG_INPUT_MOUSEDEV, CONFIG_HID_LOGITECH)
Networking/VPN - in addition to stock: CONFIG_L2TP, CONFIG_IP_ADVANCED_ROUTER, CONFIG_NET_IPIP, CONFIG_NET_IPGRE, CONFIG_IP_MULTIPLE_TABLES, CONFIG_INET_AH, CONFIG_INET_IPCOMP, CONFIG_INET_XFRM_TUNNEL, CONFIG_INET_XFRM_MODE_TUNNEL, CONFIG_INET_XFRM_MODE_BEET, CONFIG_L2TP_DEBUGFS, CONFIG_L2TP_V3, CONFIG_L2TP_IP, CONFIG_L2TP_ETH, CONFIG_PPP_MULTILINK, CONFIG_PPPOE
v1.0.0
Stock ROM with ramdisk and 1.7GHz heat script (init.d added, unsecured ramdisk)
CWM flashable: View attachment motley_lite_stock_full_kernel_and_ramdisk_1.0.0_build_1.zip
(Stock and stock-based ROMs only - 32GB and 64GB primes)
Anykernel for Stock or AOKP (won't touch your ramdisk, heat, or init.d scripts)
CWM flashable: View attachment motley_lite_anykernel_stock_and_AOKP_1.0.0_build_1.zip
(32GB stock-based ROMs or AOKP primes only!)
AOKP MS 6.1 with full ramdisk and 1.7 init.d OC script
CWM flashable: View attachment motley_lite_v1.0.0b_build_1_for_AOKP_MS_6.1.zip (updated zip 7/16/2012 10:40pm - will OC to 1.7 on boot, WiFi is working for me)
(AOKP only - 32GB and 64GB primes)
Generic Anykernel for EOS, Gummy, CM9 (won't touch your ramdisk or init.d scripts)
CWM flashable: View attachment motley_lite_generic_anykernel_v1.0.0_build_2.zip
(32GB EOS, Gummy, CM9 primes only!)
Alpha 3.x kernel
A more experimental kernel, with stable versions along the way.
View attachment 986646
Features - includes alpha
Asus v9.4.2.28 base with Asus keyboard dock support
Overclocking options: 1.6, 1.7, or 1.8GHz performance mode (choice of Asus modes)
Compiler optimizations (-o2)
I/O schedulers - CFQ (default), SIO, NOOP, and deadline
ZRAM (must be enabled by a script...see example below)
MMC drivers back-ported from Nvidia 3.1 kernel
Governors - optimized Interactive (default), Performance, On Demand, Power Saver
initramfs changes from stock - init.d support (your ROM must have the /system/etc/init.d folder and busybox) and the default.prop has been updated with ro.secure=0 (for "adb remount")
CIFS support (built-in, no need for kernel module)
NTFS/exFAT modules are provided in stock ramdisk - uses stock Tuxera modules. See http://www.tuxera.com/) - modules are loaded during init automatically with included initramfs.
Kernel compression mode LZMA
Userspace voltage control/undervolting (UV)- experimental, don't set on boot until you test your settings (use SetCPU or other voltage tweaking tool) (thanks richardtrip)
Input devices - PS3 (stock), XBox (CONFIG_INPUT_FF_MEMLESS and CONFIG_JOYSTICK_XPAD_FF), Other input device support (CONFIG_HID_APPLE, CONFIG_INPUT_MOUSEDEV, CONFIG_HID_LOGITECH)
Networking/VPN - in addition to stock: CONFIG_L2TP, CONFIG_IP_ADVANCED_ROUTER, CONFIG_NET_IPIP, CONFIG_NET_IPGRE, CONFIG_IP_MULTIPLE_TABLES, CONFIG_INET_AH, CONFIG_INET_IPCOMP, CONFIG_INET_XFRM_TUNNEL, CONFIG_INET_XFRM_MODE_TUNNEL, CONFIG_INET_XFRM_MODE_BEET, CONFIG_L2TP_DEBUGFS, CONFIG_L2TP_V3, CONFIG_L2TP_IP, CONFIG_L2TP_ETH, CONFIG_PPP_MULTILINK, CONFIG_PPPOE
MMC - CONFIG_ZIMMER by HTC Studio Engineering (reference OneX kernel) - Experimental - can't find the source of this hack, so it may be an HTC original or a variant of another hack upstream. It increases vm swappiness to 100 by default to force swapping of dead RAM. The theory is to clear out the stale RAM and open up the RAM for something more useful. While this may be counter-intuitive to I/O performance since swapping equates to more disk i/o, the code changes also implement some changes to the block, fs, and mm portions of the kernel. Essentially, from what I can tell, it flags and handles disk operations (aka "bios") differently if they are involved in swap operations (going to or coming from swap). A "bio" is essentially a manifest of an ongoing I/O block device operation, what sectors and memory locations it contains etc. Once the RAM is freed up, I have also been increasing the Dalvik vm RAM settings in the build.prop (see Demandarin's build.prop post) to allow for more RAM consumption.
Turned off GENTLE_FAIR_SLEEPERS - Theoretically should improve UI performance on Android.
ARM toolchain - Code Sourcery Lite 2010.09-51
Many other performance tweaks and many Nvidia patches/bug fixes applied beyond the stock version. See the release notes or github for details.
alpha v3.0.7.0 - fix deep sleep issue
Stock ROM with ramdisk and 1.7GHz heat script (init.d added, unsecured ramdisk)
CWM flashable: View attachment motley_stock_full_kernel_and_ramdisk_3.0.7.0_b302.zip(build 302)
(Stock and stock-based ROMs only - 32GB and 64GB primes)
AOKP build 40 with full ramdisk and 1.7 init.d OC script
CWM flashable: View attachment z_motley_tfp_v3.0.7.0_b302_for_AOKP_build_40_1.7GHz.zip(build 302)
(AOKP only - 32GB and 64GB primes)
Anykernel for Stock or AOKP (won't touch your ramdisk, heat, or init.d scripts)
CWM flashable: View attachment z_motley_anykernel_stock_and_AOKP_3.0.7.0_b302.zip (build 302)
(32GB stock-based ROMs or AOKP primes only!)
Generic Anykernel for EOS, Gummy, CM9 (won't touch your ramdisk or init.d scripts)
CWM flashable: View attachment motley_tfp_anykernel_generic_3.0.7.0_b303.zip (build 303)
(32GB EOS, Gummy, CM9 primes only!)
alpha v3.0.6.10 - fixed wifi issues in 3.0.6.9
Stock ROM with ramdisk and 1.7GHz heat script (init.d added, unsecured ramdisk)
CWM flashable: View attachment motley_stock_full_kernel_and_ramdisk_3.0.6.10.zip (build 247)
(Stock and stock-based ROMs only - 32GB and 64GB primes)
AOKP build 40 with full ramdisk and 1.7 init.d OC script
CWM flashable: View attachment z_motley_tfp_v3.0.6.10_for_AOKP_build_40_1.7GHz.zip (build 247)
(AOKP only - 32GB and 64GB primes)
Anykernel for Stock or AOKP (won't touch your ramdisk, heat, or init.d scripts)
CWM flashable:View attachment z_motley_anykernel_stock_and_AOKP_3.0.6.10.zip (build 247)
(32GB stock-based ROMs or AOKP primes only!)
Generic Anykernel for EOS, Gummy, CM9 (won't touch your ramdisk or init.d scripts)
CWM flashable: View attachment motley_tfp_anykernel_generic_3.0.6.10.zip (build 250)
(32GB EOS, Gummy, CM9 primes only!)
Older alpha 3.0.x versions can be found in post 803
Many are stable on v3.0.5 if the above versions don't work for you.
v2.6.11 build 100 2012-04-22
Asus stock-based ROMs (aroma installer): View attachment motley_tfp_2.6.11_Turge_installer.zip
Flash with CWM to run the installer and pick your heat!
Other ROMs: see alpha version 3.0.x above as previous generic kernels discontinued due to wifi incompatibility other than AOKP.
Installation
1. Backup stock boot.img (just do a full backup with the latest CWM)
See http://forum.xda-developers.com/showthread.php?t=1533697
2. Flash the proper zip with CWM
--------------------------------------------------------------------------------------------------------------------------------------
If you want to set your modes and play with the scripts manually as before see this post:
http://forum.xda-developers.com/showpost.php?p=24565491&postcount=278)
Don't set your core_cap_level higher than 1400mV as it is the highest core voltage available.
system_mode numbers (3=1.6GHz, 4=1.7GHz, 5=1.8GHz)
--------------------------------------------------------------------------------------------------------------------------------------
Going back to stock:
If you want to revert to stock boot image including stock kernel from your backup
Use your CWM backup. You can do a selective restore and just restore your boot.img
If you want to revert back to your Asus scaling scripts
Flash the stock scaling script: View attachment Stock_scripts_1_to_5.zip
--------------------------------------------------------------------------------------------------------------------------------------
Github rep: https://github.com/motley-git/TF201-Kernel
--------------------------------------------------------------------------------------------------------------------------------------
Past versions
v2.5.8 build 71 (GPU Love) 2012-04-14
CWM flashable zip: v2.5.8
Aroma installer with heat scripts: View attachment motley_tfp_2.5.8_Turge_installer.zip
v2.4 build 34 (Neon glitter) 2012-04-06
CWM flashable zip: View attachment 986645
v2.3 build 25 (Need for speed)
CWM flashable zip: View attachment 978413
v2.2 build 23 (No fools, more Asus Tweaks)
CWM flashable zip: View attachment 976821
Thanks to:
Asus for the awesome machine and kernel source
viperboy, jermaine151, MasterZen88, di11igaf, Diamondback and shaky156 for sharing their knowledge and tools
raman84 (RaYmAn) and others for the blob tools that work on transformer
Turge - awesome Aroma installer base creation for us!
amarullz - Aroma Installer
Doktaphex - touch recovery thread used by Turge for the touchscreen components.
AnyKernel - Koush and TeamDRH (and Jermaine for bringing it to the Prime)
All of those that have helped with testing! Special thanks to CekMTL for his troubleshooting skills and Deathmo for really going above and beyond to help out.
Sample overclock init.d script example (needed for AOKP or generic roms). AOKP uses /system/etc/init.d/cpu_overclock, so I recommend you edit that file for AOKP since it is already working.
Code:
#!/system/bin/sh
echo 4 > /sys/module/cpu_tegra/parameters/system_mode
echo 1350 > /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0
echo 1700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo N > /sys/module/cpu_tegra3/parameters/no_lp
Sample ZRAM init script (thanks show-p1984) (needs to be run as "su" using script manager):
Code:
#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984
echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";
if [ ! -e /sys/block/zram0/disksize ] ; then
echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
echo "[90ZRAM]: Is this a ZRAM kernel?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
#find busybox in /system
bblocation=$(find /system/ -name 'busybox')
if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
echo "[90ZRAM]: busybox found in:" $bblocation;
echo "[90ZRAM]: Setting ZRAM disksize.";
echo $((100*1024*1024)) > /sys/block/zram0/disksize
echo "[90ZRAM]: Starting ZRAM...";
bblocation=${bblocation%/*}
cd $bblocation
./busybox mkswap /dev/block/zram0
./busybox swapon /dev/block/zram0
echo "[90ZRAM]: ZRAM activated.";
else
echo "[90ZRAM]: ERROR! busybox not found!";
echo "[90ZRAM]: Is busybox installed? Symlinks set?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
fi
fi
nice work man, i was getting ready to implement this myself. they made that pretty easy right.. at first i thought it was gonna be a pita until i looked a little deeper and saw most of what we need is already there.
di11igaf said:
nice work man, i was getting ready to implement this myself. they made that pretty easy right.. at first i thought it was gonna be a pita until i looked a little deeper and saw most of what we need is already there.
Click to expand...
Click to collapse
Thanks, yeah not too bad. There is a lot more "nanny" code in tegra 3 than in tegra 2. Tempted to tweak some of it, but decided it was best to take baby steps! Kind of hoping we can get a community version going once some of us do some study and get our feet wet.
Cheers
is it possible to convert this into an apk form like EZOverclock? where there is no need for unlocking and CWM. all needed is rooted device and installing the app. just curious
great work though. plus u mentioning 1.8Ghz might be the final straw needed to push me over the edge to unlock..lol cant wait to see it implemented. I'm holding back so badly with all this new developement coming out for prime. its really starting to blow up in here and temptation to unlock is eating me up
So like a retard I flashed boot.img.zip instead of extracting the boot.img out first
-_-
It is entirely my fault but any help would be appreciated
My TP hangs at he Eee Pad logo
Any hopes of holding vol down + power button sends me straight to wipe data or fastboot menu (I CANT ACCESS THE RECOVERY TRIED 99999 TIMES TO DO IT WITH VOL DOWN + POWER)
Tried doing the following:
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 flash boot boot.img (original stock boot.img found here http://forum.xda-developers.com/showthread.php?t=1514088
Still it hangs at Eee Pad logo if I don't do anything. If I tried the Volume down + power goes straight back to wipe data or fastboot.
ANY thoughts?
tHANKS
tassadar898 said:
So like a retard I flashed boot.img.zip instead of extracting the boot.img out first
-_-
It is entirely my fault but any help would be appreciated
My TP hangs at he Eee Pad logo
Any hopes of holding vol down + power button sends me straight to wipe data or fastboot menu (I CANT ACCESS THE RECOVERY TRIED 99999 TIMES TO DO IT WITH VOL DOWN + POWER)
Tried doing the following:
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 flash boot boot.img (original stock boot.img found here http://forum.xda-developers.com/showthread.php?t=1514088
Still it hangs at Eee Pad logo if I don't do anything. If I tried the Volume down + power goes straight back to wipe data or fastboot.
ANY thoughts?
tHANKS
Click to expand...
Click to collapse
Try using the following commands in APX mode. To access APX mode:
1. Undock transformer prime
2. Hold power+ up key.
3. Install naked drivers (http://forum.xda-developers.com/showthread.php?t=1514942)
4. Screen will be black but once connected to a pc you should see it in device manager.
Nice stuff! Flashed and all is well but 1.7ghz plus antutu. Equals sad prime. 2 reboots and one crash to homescreen (it didn't force close though)
Balanced works fine.
Edit: anything that is cpu intensive makes my prime sad reboot time lol. Meh I probably need more volts.
Sent from my Transformer Prime TF201 using Tapatalk
Good job motley!!
tassadar898 said:
So like a retard I flashed boot.img.zip instead of extracting the boot.img out first
-_-
It is entirely my fault but any help would be appreciated
My TP hangs at he Eee Pad logo
Any hopes of holding vol down + power button sends me straight to wipe data or fastboot menu (I CANT ACCESS THE RECOVERY TRIED 99999 TIMES TO DO IT WITH VOL DOWN + POWER)
Tried doing the following:
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 flash boot boot.img (original stock boot.img found here http://forum.xda-developers.com/showthread.php?t=1514088
Still it hangs at Eee Pad logo if I don't do anything. If I tried the Volume down + power goes straight back to wipe data or fastboot.
ANY thoughts?
tHANKS
Click to expand...
Click to collapse
You need to repack the correct boot.img as a blob file. Fastboot doesnot work the way you use it.
Fastboot can't flash raw imgs, you need to repack them before as a blob file.
Search goolge for blobtools, there is a thread on xda with both linux and a windows version.
And now @OP
I guess the kernel itself is based on the outdated ASUS source?
And for the next build, maybe make a verion where you overclock the 1.6GHz mode instead of the Performance mode?
Most (if not all) who would use such a kernel, use some kind of tool/app/rom which can access the 1.6 Ghz mode anyway, so you are better of tweaking the 1.6Ghz mode
looks promising. will wait till for the updated version before i start playing with the kernel.
but always appreciate the work bruh thanks.
Diamondback said:
And now @OP
I guess the kernel itself is based on the outdated ASUS source?
And for the next build, maybe make a verion where you overclock the 1.6GHz mode instead of the Performance mode?
Most (if not all) who would use such a kernel, use some kind of tool/app/rom which can access the 1.6 Ghz mode anyway, so you are better of tweaking the 1.6Ghz mode
Click to expand...
Click to collapse
the2rrell said:
looks promising. will wait till for the updated version before i start playing with the kernel.
but always appreciate the work bruh thanks.
Click to expand...
Click to collapse
Correct me if I'm wrong, but the kernel versions are identical and the only things that changed were the host that the new kernel was compiled on and the appended string on the end. It sounds to me like they just built the same source with a different config.
Am I missing something???
jermaine151 said:
Guys, why does everyone think that there's a new kernel version and that they will wait for the source to drop? Correct me if I'm wrong, but the kernel versions are identical and the only things that changed were the host that the new kernel was compiled on and the appended string on the end. It sounds to me like they just built the same source with a different config.
Am I missing something???
Click to expand...
Click to collapse
First: I have no idea about kernels or building them from source
I only see that we got several kernel upgrades without getting new kernel source from ASUS.
So I guessed that they have newer source, correct me if I am wrong here
Diamondback said:
First: I have no idea about kernels or building them from source
I only see that we got several kernel upgrades without getting new kernel source from ASUS.
So I guessed that they have newer source, correct me if I am wrong here
Click to expand...
Click to collapse
I think we'll only get a new release if they use a different source version. The kernel version hasn't changed on their ICS kernels yet, so I "believe" that the source they have posted is the latest and is what they built the mercury kernel from.
jermaine151 said:
I think we'll only get a new release if they use a different source version. The kernel version hasn't changed on their ICS kernels yet, so I "believe" that the source they have posted is the latest and is what they built the mercury kernel from.
Click to expand...
Click to collapse
Oh okay, good to know
Diamondback said:
You need to repack the correct boot.img as a blob file. Fastboot doesnot work the way you use it.
Fastboot can't flash raw imgs, you need to repack them before as a blob file.
Search goolge for blobtools, there is a thread on xda with both linux and a windows version.
Click to expand...
Click to collapse
I tried my best for the past 10 hours and couldnt get the boot.img repacked. Is there a way someone can help me do it?
tassadar898 said:
I tried my best for the past 10 hours and couldnt get the boot.img repacked. Is there a way someone can help me do it?
Click to expand...
Click to collapse
I attached a pretty much stock kernel blob (Dr Wowe's kernel) to this post:
http://forum.xda-developers.com/showpost.php?p=23182705&postcount=13
You need to grab it out of the zip file. Maybe that will help you get up and running again.
This is great! Can't wait till this kernel is included in one of the stock roms
If was this kernel make it like app can i get overclock without unlockbootloader???
Sent from my HTC Desire HD A9191 using XDA
EDIT: Thanks to demandarin for testing this. It looks like this will NOT be able to be flashed on a Prime with a locked bootloader. It was worth a shot. I'll leave the attachment in case anyone needs this kernel in a signed blob format.
White Beam Kernel for Galaxy Player 4.0 YP-GB1(KOR) and YP-G1(INTL)
Hello there, I'm glad to Release latest version of my kernel
it can be have less features then other kernel in this SGP 4.0 and 5.0 forum
if you have any problems while you using this kernel OR want to send me feedback,
send them via email, fascbook, google+, twitter, my blog and etc.
Latest Version of this Kernel : #23 (2012/08/01)
This kernel woks on Galaxy Player 4.0 YP-GB1(KOR) and YP-G1 (INTL), May not or never works on other version of Galaxy Player
If you are using other version of Galaxy Player DO NOT flash this kernel.(except when you are brave)
Features
Based on YP-GB1 2.6.35.7 Gingerbread kernel source
-LiveOC (You can set OverClock value in percent(%) → to set overclock value in percent, install NSTools from play store
-Voodoo Sound driver v10
-init.d support
-Scheduler : CFQ, Deadline, Noop, SIO(default), VR, BFQ(v1r1)
-Read ahead tweak
-Max touch point limit : 10points
-Custom bootlogo
-CWM Recovery (Added from SteveS' kernel source)
-Standard bootanimation support
-CPU Governors : conservative, userspace, powersave, ondemand, performance, SmartassV2(default), lulzactive
-Tiny RCU
-jhash3
-Kernel compression : LZMA
Changlogs
20120801(#23):
Updated jhash2 to jhash3
Enabled Tiny RCU
Using LZMA compression
20120731(#21):
Added lulzactive CPU governor, set smartassV2 as default
*My Kernel(WhiteBeam Kernel) was verified that works on YP G1(INTL)
thanks to S_m_O_k for test it on YP-G1 INTL
20120730(#20):
Added BFQ i/o scheduler (v1r1)
20120729(#19):
from this version, this kernel is compiled with KRKPG initramfs
20120727(#16):
Added SmartassV2 CPU Governor
20120726:
Added Standard bootanimation support
20120725:
Fixed T-DMB problem
20120724:
Added CWM recovery from SteveS' kernel source
20120723:
First release on here
How to install(with Odin3)
-Download Kernel from dowmload URL.
-turn off your device first, then get it in Download mode.
-Open Odin3
-Select the Kernel file in 'PDA' section
※DO NOT touch any option in Odin (Make sure Re-Partition, Flash lock, Phone EFS clear, and Phone bootloader aren't checked)
-Click 'Start' to flash kernel
How to uninstall(with Odin3)
-Download stock KRKPC kernel from here
(OR Download stock KRKPG kernel from here if your using KRKPG firmware)
-turn off your device first, then get it in Download mode.
-Open Odin3
-Select the Kernel file in 'PDA' section
※DO NOT touch any option in Odin (Make sure Re-Partition, Flash lock, Phone EFS clear, and Phone bootloader aren't checked)
-Click 'Start' to flash kernel
Download:
WBK_YP-GB1_YP-G1-INTL_GB_20120801(Latest Version)
WBK_YP-GB1_GB_20120731
WBK_YP-GB1_GB_20120730
WBK_YP-GB1_GB_20120729B
WBK_YP-GB1_GB_20120727
WBK_YP-GB1_GB_20120726
WBK_YP-GB1_GB_20120725
WBK_YP-GB1_GB_20120724
WBK_YP-GB1_GB_20120723
Source codes
Kernel | initramfs(KRKPC) | initramfs(KRKPG)
CREDITS
SteveS, Superqurio, Ezekeel, morfic
Do it at your own risk, i have no responsible if your device damaged after flash kernel
It looks nice but don't make a thread on each new version.
zaclimon said:
It looks nice but don't make a thread on each new version.
Click to expand...
Click to collapse
^^ this.
Sent from my One S
zaclimon said:
It looks nice but don't make a thread on each new version.
Click to expand...
Click to collapse
sorry, i will be careful next time when i submit new thread
썩소님
쓰레드 매번 새로 올리시지 마시고 에딧/딜릿 눌러서 수정하시면 되겠슴당 고객님.ㅎㅎ
xda에 용감한 한국어 등장!
neodymium said:
쓰레드 매번 새로 올리시지 마시고 에딧/딜릿 눌러서 수정하시면 되겠슴당 고객님.ㅎㅎ
xda에 용감한 한국어 등장!
Click to expand...
Click to collapse
이미 아까 #23 릴리즈부터 그렇게 하고 있지요 허허허허
그리고 이미 zaclimon 님께서 새 버전 올릴때 쓰레드 새로 만들지 말라고 예기 해주셨어요 허허허허
근대 갑자기 한글이라니 ㅋㅋㅋ
Branch 4.x only for Sammy ROMS 4.1.2 (CWM and TWRP)
Branch 5.x only for AOSP 4.2.2 (CWM & TWRP)
Branch 6.x only for AOSP 4.3.x (TWRP)
Branch 7.x only for AOSP 4.4.x (TWRP)
Branch 8.x only for AOSP 5..x (TWRP)
DEVELOPMENT STOPPED . APOLO WON'T WORK IN LATEST LP ROMS . MORE INFO
Apolo Configurator -> will be available in Google Play THIS
Apolo 8.0 Beta9
Beta 9
-initramfs updates
-zRam disabled
Beta 8:
- initramfs updated
- TWRP 2.8.5.0
Beta 7/7b:
- zRam enabled
- initramfs updated
Beta6:
- App2SD Fixed
- Wifi Toggle issues fixed
- Network issues fixed
Beta5:
- CM wifi issue fixed
- same initramfs for cm and omni (same kernel for all roms)
- charging animation fixed
- zzmoove updated to 1.0beta5
Beta4:
- Recovery TWRP updated to 2.8.5.0
- Updated initramfs to latest CM & OMNI
Beta3:
- Recovery TWRP updated to 2.8.3.0
- Governor zzmoove updated to 1.0 Beta4
- Fuse bug fix by @zeitferne (thanks to @Lanchon too)
- Charging Animation fixed (thanks to @Lysergic Acid)
Download Link
MIRROR
Apolo 7.3 (final version for kitkat)
- Governor zzmoove updated 1.0 Beta5 (thanks ZaneZam)
- TWRP Recovery 2.8.6.0 ("Reboot Bootloader" button fixed)
- SPEEDUP KEYRESUME (Faster wake up at power button and incoming call)
- Fixed fuse bug (thanks to @Lanchon)
Apolo 4.15b for SAMMY JB ROMS (Removed vibration interface compared with 4.15)
- Governor zzmoove updated to 1.0 beta 4
- Speedup keyresume (faster wake up)
- Governor Neox has come back (not included in beta )
- FPBug fix by @zeitferne & @Lanchon)
Download links in the usual section in this OPChangelog old Versions in Post #2
Features:
This kernel is mainly based in hardcore work (thank you to Hardcore :victory: for his great contributions). I have added undervolting (kind of phenomenal) and some additional features.
- CWM and TWRP recovery in Samsung. In AOSP I will use only TWRP in the future.
- No logs, no extra debugging
- install su, supersu in samsung. Support init.d and cifs
- Ondemand Tweaked by Hardcore
- Added some governors (specially tweaked slp and zzmoove)
- Scheduler changing enabled
- BLN enable (Since Apolo 4.5 BLNWW too)
- CRT-OFF enable
- Effective Underclock (max frequency limited)
- UV Interface for ARM (you can change voltages in ARM with external aplications)
- Kernel Includes frandom for using with CrossBreeder (I really recomend it, Thx idcrisis)
- No Overclock and no different CPU-GPU steps from stock (please don't ask me more about that, I won't add it)
Update Supersu (only sammy kernel, AOSP doesn't have supersu)
Choose normal update (not the other with CWM/TWRP). In case you chose the wrong option, you'll have a bootloop. Read the bootloop section in this OP to recover your system.
Undervolting
UV cannot damage your mobile phone, but it can make your device unsteady. It is important that you choose the right version for your mobile.
There are some Apolo versions depending on the UV used:
- Light (stock voltages)
- Regular (-50mV in ARM, internals)
- Extreme (3 versions, you can try to see what versión is better for your battery life): in JB system chooses among the different steps available inside the kernel (in internal and ARM), so depending what step is chosen, final voltages applied are different.
Regular and extreme has -50mv UV in GPU (others UV like bus, memory, video controller too). Light has stock voltages in GPU
I recommend you try regular version first. If there are no problems in two days (reboots or frozen screens) you can try extreme V0.
System changes voltages in some devices (new in JB). Android chooses among voltages included in kernel (8 steps in every frequency). I recommend not to change them in extrem versions.
More information and Voltages values:
Depending on the device, system changes voltages (in JB), choosing among voltages defined in the kernel source. It seems, system tries to choose the ideal ones for every device (taking into consideration internal and ARM voltages).
For each frequency, there are 8 posible voltages in the code (I call them steps). In ICS, system always chose 4th step for every frequency, but in JB it doesn't sometimes.
It happends with ARM voltages (you can see them in the configurator) and with internal voltages, so there are many possibilities
You can see ARM and Internal voltages in this pdf (it is in Spanish but I think you can understand it) :
VOLTAGES
So, it is not strange that configurator shows different values in two different devices with the same Apolo version. It simple, system has chosen different voltages steps. I recommend you don't pay too much attention to this, it is not important, indeed system try to be stable choosing different values.
Tips
- TWRP and CWM Backups are not compatibles between them, so you need the suitable version to restore your backups.
- I recommend OBackup. Great application for making backups in Android itself (it supports TWRP and CWM).
- Not always less voltages means better battery life, it depends on your device. The only way is testing every version and please start with Regular or Light version
- Deep Sleep problems sometimes is caused by undervolting. If your system doesn't enter in deep sleep and it is not because of any application , install regular or light version.
- It is not the same, lower ARM voltages with an external APP (for example Apolo Configurator) and change Apolo version (V2,V1,V0 or regular) because there are more voltajes involved (not only ARM)
- If you want to turn off the leds always (when you touch tactile buttons), you have to use Apolo Configurator, otherwise (if you use only Samsung settings) your leds will turn on when you turn on the screen.
- If your system doesn't boot due to wrong Voltages, flash this in recovery : download zip
- Acess to internal sd in TWRP recovery :
(Up a level )
then go to
"emmc"
that's your internal sd
- Recommended wipe Cache and Dalvik after changing any kernel (it is not mandatory but it is a good custom)
- To increase sound volume use mods like Viper or appications like Alsa Mixer or Vodoo louder in play store
Enable logs in TWRP and v7 : Create a file in "/data" named ".enable_logs" and reboot.
¿In kit kat, should I use CM version or Omni version?
Just see if your ROM has superuser included (I mean if you can gain root just enabling it in developer options). In that case you should use CM version. If your ROM needs supersu to manage the root, install omni version.
Bugs
- Battery Animation doesn't work when phoes is off
There is a workaround. Thanks to @It_ler : http://forum.xda-developers.com/showpost.php?p=43244090&postcount=1250
- S2W doesn't work after rebooting.
It's because this S2W bug: "When the phone is booting, if the screen is off in the exactly moment the script is changing the S2W setting, the screen will not respond any longer and you have to reboot."
To avoid it, increase the screen timeout. Another solution is to keep the screen on, while the phone is starting until android had started completely and you can be sure that the script has been applied (more than a minute because the script has 60 seconds of delay).
- If BLN y/o WIFI doesn't work in kit kat ROMS (maybe it can help in other bases too)
If test button works in Apolo Configurator check if in your Android Settings- Display there's something related to notifications led or Notifications light
or review
Rom settings (name depends on the ROM) - Active display must be disabled, otherwise BLN won´t work
If BLN test or wifi doesn't work, try this:
- Remove Apolo folder in /system (if folder exists)
- Go to Recovery
- Wipe Cache
- Flash Apolo
- Wipe cache again
- Reboot
- Avast doesn't work with Apolo, if you can't live without it, use other kernel, sorry
- Bootloops: it doesn't happend very often but it can happend in JB if there is something corrupt in partitions. Posible solutions:
1) Try to enter to recovery. Press vol up, Home button and Power button at the same time until the device enters into recovery (system can restart 2 or 3 times, but don't release buttons). Then wipe cache and dalvik and reboot.
2a) if 1) didn't work, enter into download mode and flash light TWRP version if you had CWM. Wipe cache and Dalvik and reinstall CWM if you wish.
2b) if TWRP didn't work or you had TWRP version already, flash last PhilZ kernel (thx to Phil3759), enter into Philz recovery and wipe cache and Dalvik. Then reinstall Apolo.
3) if nothing worked, try to reinstall your ROM without wipe data and wipe cache and Dalvik
4) wipe data (you will loose all your application and configurations)
5) reinstall with odin stock ROM WITH repartition (pit file). Then install Apolo and reinstall your custom ROM.
- Sometimes when you reboot your device, your battery seems to drop a lot (it is not real).
To recover your old battery percentage, plug in your device and reboot into recovery. Check your battery level in the recovery, if it is correct, reboot (solved).
If it is not, reboot into recovery again (in CWM advanced - reboot into recovery, in TWRP reboot - recovery). It should be solved.
This issue never happens if you reboot your device while is charging, so I recommend you plug in your device before rebooting (if you can do it)
If you can't plug in your device, don't reboot if you can avoid it
- AOSP: Recommended installation procedure for 4.3 ROMS (stuck in the second boot) Read post 3
- AOSP: Restoring backups changing ROM base (stuck in the second reboot), Read post 3
Download Kernel
Mirror
Installation (you can install Apolo through CWM or TWRP recovery, it doesn't matter)
- Use a kernel cleaning script before installing (for instance Gs2KernelWipe thanks to hawkerpaul, but you can use other)
- .zip : install in custom recovery
- .tar : install in PC with odin (windows) or heimdall (linux)
Apolo Configurator (Available in Google Play again HERE)
I've developed a multilanguage application (Spanish, English, Italian, Catalan, Gallego, Russian and Turkish).You can change governor and scheduler, set ARM undervolting, configure BLN, BLNWW and S2W and set brightness curve:
I extremely recommend you read the Apolo Configurator Manual : Apolo Configurator Manual
My recommendation about scheduler/governor (it's only my opinion, maybe yours can be different)
- You can find 3 defined profiles in Apolo Configurator (performance, balanced and battery saving) based in noop/slp. I have changed parameters to achive the profile goals.
- Another good combination is noop/zzmoove
THANKS
- Hardcore for his fabulous kernel speedmod
- Thx to great :goodhil3759 (he helped me to build the CWM recovery and let me use his recovery in the new Apolo versions) Please, visit his great job here
- Thx to jeboo for his great kernel and for let me use his TWRP recovery :good:
- Thx gokhanmoral , great master. Most advanced features come from him
- Thx dorimanx for his great kernel and sources
- fenomeno83 for his idea and help when I started
- Thx mialwe for his great "smoove" governor (base of zzmoove) and ZaneZam for keeping it alive with the zzmoove.
- Chainfire for CF-Root, CWM Manager, etc, etc
- Thx sk8erwitskil, myfluxi, Talustus for recovery sources
- Thx to Devil_1210 for his help building the ICS kernel
- Thx to my betas for their help and ideas and much more: Broquen, Garrapatero123, Palleiro, Doomper, partisano, 666roi666 , Gordon320, nrg86
- Many thanks to @daga69 for giving me a S2 and keep this kernel alive
- Thanks to @rrgrrg for the Configurator icon.
(for sure I forgot more people, I hope they forgive me)
Donors: :laugh:
Axel 11, manuelmagix, K-a-M-u-Z-u, elbanzai,Zytrel, bkraptor,Shadowrun1,rogers11,LarsX,Andreas75k,espirito-livre, dsp26, gumsle, karpfenhai,
Andreas75k (Yes again ), metalgearhathaway
Thanksssss a lot ¡¡ :highfive::victory::good:
If you see something that you cannot understand or it is not correct (my English is far away from perfect ) please let me know
If you want to translate the Apolo Configurator to other lenguages, please tell me
Thanks to @lejarton, @Maxximo88, @stelistcristi,@Gordon320, @nrg86, @Palleiro, @Partisano, @Broquen and @nhmanasfor their translations
Enjoy ¡¡
Apolo source code
CHANGELOG OLD VERSIONS
Apolo 7.1 (for kitkat ROMS, 4.4.x)
- Recovery TWRP updated to 2.7.1.0
- Mali drivers updated
- zzmoove updated to 0.9beta3 (thanks to ZaneZam)
- rebuilt cypress (maybe helps with BLN errors in some devices)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 7.0b for kit kat, 6.3 for 4.3.x ROMS (TWRP recoverys) and Apolo 4.14 for stock ROMS (CWM & TWRP recoverys)
Changelog All bases (7.0b & 4.14 & 6.3):
- New zzmoove 0.8 (thx ZaneZam Link )
For kitkat (Apolo 7.0b & 6.3 TWRP):
- Fixed second core bug that affected some governors
- Pac-Rom support
- TWRP updated to 2.7.0.0 (it doesn't work fine in stock roms 4.1.2 (bootloops issue), so if you want to go back to sammy roms from kitkat, install first 4.14 and reboot in recovery and install from Apolo 4.14 recovery)
Remember that 6.3 comes with new mali drivers. If you see your screen off when you start your system, you must flash this through recovery.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 4.13 (SAMMY) & 6.2b (AOSP 4.3.1)
Both (SAMMY and AOSP):
- Linux updated to 3.0.101
- Updated row scheduler
- Added bfq scheduler
- Removed MDNIE Sharpness by Hardcore (no mor problems with mdnie scenarios)
- Initramfs improved
6.2b ONLY:
- GPU an Screen drivers updated (r3p2+s3cfb)
- Wifi drivers updated to 1.61.58
WARNING: 6.2b version only with mali r3p2+s3cfb.
If your ROM is mali v2 (old drivers) you have to update some libs (otherwise, black screen). You can do it with this zip (flash in recovery):
https://copy.com/reo37Z4KqLVhU1S2
The zip will change some libs in ROM, so if you want to go back, you'll have to flash the ROM again without wipes
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo beta kitkat (Android 4.4 CM and OMNI-SlimKat)
- Beta 3 ONLY for OMNI ROMs: Solves the issue installing some application in latest nightlies
- Beta 2/2b for CM ROMs:
Only with mali v3. Works with new CM bases (4.4.2) .Thanks Karpfenhai for your help testing it
- Fixed battery settings
- CWM stock recovery (restores fine)
- Last changes (like 6.2)
If you suffer issues with the battery indicator, please change to beta2 or beta2b (depending on what kernel had the issue)
- For Omni ROMS there is a beta2 (same changelog) with TWRP recovery
For SLIMKAT 4.4.2 ROMs you should use Apolo beta2b for CM.
If you use omni version in CM ROMS (don't recommended because you will loose root) don't forget to download supersu and update binary BEFORE flashing Apolo kernel (otherwise you'll have a bootloop).Thanks to @Shahan_mik3 and @EricCartmanez for the information.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo Beta 3 FOR CM KITKAT (4.4.2) ROMS
- Solves the issue in (FC in phone) in latests nightlies
- Fix the bug moving big files to external sd (CREDITS TO GUSTAVO)
It was a lot of work, headaches, and semibricksssss so ENJOY IT¡¡
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo versions 4.12, 5.1, 6.1
For all bases:
- Reverted the stupid android_secure change I did in last kernel
- Added new governor Neox
- Added MyFluxi sound interface (to control it you'll need to use the new Apolo configurator 5.0)
- Fixed mdnie in the camera with mdnie sharpness disabled
Only For 5.1:
- Fixed vibration control
Only For 6.1:
- Added support for framework-2.jar
- Fixed com.android.phone FC in latest releases
---------------------------------------------------------------------------------------------------------------------------------------------
Apolo 5.0 & 6.0 (AOSP ROMS)
5.0 (AOSP ROMS 4.2.2):
- TWRP version fixed (bluetooth) and updated to 2.6.3
6.0 (AOSP ROMS 4.3 and 4.3.1):
- Initramfs improved
- Fixed booting for latest Pacman ROMS (4.3.1)
- TWRP version fixed (bluetooth) and updated to 2.6.3
- Vibration Control enabled
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Apolo 4.11 (Sammy only)
- zzmoove updated to 0.7d
- Backup and restore Android_secure fixed
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 5.0 & 6.0 (AOSPs Version)
- Base: smdk4412 by cyanogenmod
- Same tweaks as Apolo JB 4.x
- zzmoove updated to 0.7d
- Backup and Restore of Android_secure solved (thx dorimanx)
- Fully compatible with Apolo Configurator
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 4.10 (Sammy ROMS)
- Added brightness curve interface (credits to gokhanmoral) It will be necessary to use new Apolo Configurator 4.0 to configure the brightness curve (available in Google Play).
- Exfat support in kernel and recoverys (CWM and TWRP)
- TWRP recovery updated to 2.6.1 (thx to the TWRP team)
- zzmoove updated to version 0.7c.(thx ZaneZam)
- su and supersu updated (thx chainfire)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.9
- Slightly change in brightness levels (automatic brightness higher than 4.8)
- Wifi drivers updated (latest S4) thx dorimanx
- Pegasusq , sampling time set to 50000, instead 100000 (improvement listening music with bluetooth)
- Try to solve issue of charging animation with phone off (will see if it works)
- zzmoove updated to 0.6 and tweaked thx ZaneZam
- sio scheduler updated
- su, supersu updated
- Revert USB charging values to 450 mA by default (safety measure). Added charging interface, so since Apolo configurator 3.8b you will be able to change it.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.8
- Bilingual CWM recovery(Spanish-English). Default: English (you can change language in Extras Apolo)
- Fixed toggle ctr-off in CWM recovery
- Default backup format set to tar in CWM
- Updated TWRP recovery to version 2.5 (Thx Jeboo for sources). Added Preload support.
- Two new minimum brightness levels in manual mode (lower than stock)
- Fixed init.d. Now kernel considers all scripts in /system/etc/init.d
- Fixed BLN test in Configurator
- Current for USB charging to 650 mA (same as wall charger)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.7
- New Wifi Drivers from S4 (Thx dorimanx and codeworks)
- Added I/O Scheduler row (Thx Jeboo)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.6
- Revert Linaro toolchain compiler to GCC 4.6.3
- New governor interactivex (thx dorimanx)
- New governor zzmoove tweaked by pedestre (I recommend this governor, it's great)
- Fixed bug flashing from recovery updates with Assert instruction (for instance modem zips)
- Updated su and supersu
- Fix Touchscreen Choppy using MXT224E chip(thx kgp700)
- New Apolo Configurator 3.2 (useful for activating and scheduling BLN and BLNWW, selecting governors and schedulers and much more ...). You can find it free in Google Play
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.5
- New interface with BLNWW, leds timeout and brightness and Slide to Wake (All the credits for gokhanmoral)
- New governor Intellidemand (thx dorimanx)
- New Apolo Configurator 3.0 (useful for activating BLN and BLNWW and much more ...). You can find it in Google Play free
INSTALLATION PROCEDURE FOR 4.3 / WIPING DATA ( if you are going to wipe data, skip 4,5 and 6)
In 4.4 is not necessary if you are using beta2,beta2b or beta3 (Omni or CM)
I don't know what the problem is (update: the problem is recovery) but if you follow this procedure (fresh install) you won't have any problem. If you install the rom right with Apolo, you may be stuck in the second reboot ?¿?¿
1- Install CM recovery (it is better install ROM with CM recovery). You can download it here
2- Advanced - Reboot in recovery (you will reboot in CM recovery , it is no a touch recovery, sorry)
3- Wipe data (and format system if you are going to install a new ROM)
4- Install ROM
5- Install gapps
6- Wipe data again
7- Boot system
7- Do the initial guided setup (wifi, gmail, etc) and install a couple of your apps
8- Reboot (it takes to boot a little longer than usual, even a couple of minutes)
9- After a successful second reboot, you can change the kernel to Apolo and you won't have any issue. It will always boot normally.
RESTORE ROMS IN AOSP ROMS (moving from 4.3 to 4.4 or from 4.4 to 4.3)
This issue only happends (AFAIK) when you change your base restoring the backup, for instance if you are in 4.4 and restoring a 4.3.1 backup. In my experience if you are in the same base, it works right.
You won't have any issue restoring roms in firs reboot, but you may be suffered the same issue (stuck in samsung logo) in second reboot, after restoring your backup. You can do your backups with Apolo, the issue is restoring, but I recommend you do your backups with OBackup App, because you don't need to reboot in recovery (you can do it in Android without rebooting)
If you want to restore your backups successfully I recommend you first change the kernel to CM kernel and then restore your backup:
SAFE PROCEDURE TO RESTORE BACKUPS
1- Reboot in recovery
2- Install CM recovery download
3- Advanced- Reboot in recovery
4- In CM recovery : Restore your backup
5- Reboot and everything will be fine
And more
Greetings!!!
YES! Finally Apolo by Pedestre here!!!
WELCOME :victory:
Kernel rocks
And CWM in english now?
Ooooh goood
I follow your kernel on an Italian forum, and it's quite popular.. just because your kernel is waaaaay good :thumbup:
Welcome to Xda mate! I hope a lot of people will enjoy your work
WarcoLLapsE said:
YES! Finally Apolo by Pedestre here!!!
WELCOME :victory:
Kernel rocks
And CWM in english now?
Click to expand...
Click to collapse
Thanks ¡¡
No plans , too much work translating and maintaining two CWM recoverys, but I wouldn't mind to include any English CWM recovery if somebody let me use it (as I did with TWRP from Jeboo)
finally on xda!!
Thank you for having implemented the zzmoove:thumbup:
my results with this amazing kernel .....
only wifi - no games/no 3G/no BLN/no Slide2wake, Tapatalk, internet browser, youtube + 2h to music on headphones....
Spoiler
{
"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"
}
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel:Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:
Thank you very much for your work Pedestre. Glad to see you here too. Good Luck. Regards
Enviado desde mi GT-I9100 usando Tapatalk 2
vitalianoleone said:
finally on xda!!
Click to expand...
Click to collapse
+1
Just added this kernel thread to my kernels-to-test list of my kernel test thread.
Hope that latest light version will run stable on my phone, as I had some FCs and SODs on previous regular version.
Thanks pedestre! Great kernel and best person. :thumbup:
It_ler said:
+1
Just added this kernel thread to my kernels-to-test list of my kernel test thread.
Hope that latest light version will run stable on my phone, as I had some FCs and SODs on previous regular version.
Click to expand...
Click to collapse
FCs and SODs are tipical undervolting issues. Light version has stock voltages, I hope you don't have any problem
Your mobile must be delicate with undervolting; most devices don't experience any issue with regular version.
Thanks for added Apolo to your kernel list. Great job testing ¡¡
My results
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel: Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:
Thanks !!
Let's try 4.6
Nice to see you here pedestre, tnx a lot for your work!
What a tremendous job man!! Works great with AllianceROM!! Thx
Welcome master. Great job. Best kernel ever.
Yeah! Finally on xda! I'm sure that philz will let you use his recovery!
Inviato dal mio GT-I9100 con Tapatalk 2
Glad to see you around here
I will help you as much as I can
NEXT Kernel 1.0.0:
STOP! This kernel supports Custom KitKat Roms (e.g. OmniROM, SlimKat, CM 11.0), Custom JB 4.3.x Roms (e.g. CM 10.2) and Stock / Stockbased Roms!
It won't work on any AOSP Android 4.1.x or 4.2.x Custom Roms for now!
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY S3 MINI PROJECT!
Sources:
https://github.com/andi34/android_kernel_samsung_golden
Dual-Boot Solution by @ketut.kumajaya, well known from Samsung Galaxy Tab 2 and Samsung Galaxy Tab 3 8.0
I/O Scheduler : noop | deadline | cfq | sio | sioplus | row | zen
Governor : Abyssplug | Ondemand | Interactive | Powersave | Performance | SmartassV2 | Sakuractive
based on latest Samsung OSRC for Samsung Golden (JB_Update2)
Linux kernel 3.0.101 version
Compiled with GCC 4.7
Open source Samsung exFAT included (v. 1.2.7)
Static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. Thanks to @ketut.kumajaya
"magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
SElinux Support
Known Problems:
Bootmenu
- Reboot into Recovery from main Bootmenu does not work
- Reboot into Bootloader from main Bootmenu only reboots normal
StockRom
- USB connection not working, charging works
- Wifi-Tethering not working on Stock / Stockbased Rom
Known fully working Roms
SlimKat by Android-Andi
OmniROM by golden-guy
VanirAOSP by Unjustified Dev
enox Stockbased Rom
Stock Light
Virginity v14
Selfcompiled CM 10.2.1 (based on CM 10.2.1 Stable Source)
Novafusion CM 11 & PAC (ext4 formatted!)
Novafusion CM 10.2 & PAC
Thanks To:
ketut.kumajaya - without you this would never be possible <3
gokhanmoral, Chainfire
@LuuchoRocha
@cocafe
OliverG96
DerTeufel1980
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
I am still learning each day, i learnd most stuff from our great Developer Ketut P. Kumajaya
- i think HE deserves a Beer instead donating to me ATM. If you like you can spend Ketut a beer using PayPal
Screenshots
{
"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"
}
XDA:DevDB Information
[golden] NEXT kernel, Kernel for the Samsung Galaxy S III Mini
Contributors
Android-Andi, ketut.kumajaya
Kernel Special Features:
Version Information
Status: Beta
Created 2014-08-12
Last Updated 2014-10-11
Downloads
All files attached
- NEXT Tool 0.2 to create a 2nd System Partition (system.img) - also included inside PhilZ Touch Blackhawk Recovery
- PhilZ Touch Blackhawk Recovery for Dual-Boot-Support
- NEXT Kernel
Since NEXT Kernel 1.5.4: download latest NEXT Kernel here
Older files for history still here attached!
Changelog
Code:
[U]11.10.2014[/U]
1.5.6 -> 1.6.0
- Utilized blkid further
- Autogenerated fstab adapted from NEXT Kernel for Samsung Galaxy Tab 3
- Initial F2FS Support (experimental)
[U]19.09.2014[/U]
Update dual boot tool 0.3
- Create 1.5 GB dynamic growth sparse image
- Ext4 formatting fix
- Free space calculation fix
1.5.5 -> 1.5.6
- fixes a warning in dmesg (sysfs: cannot create duplicate filename '/devices/virtual/switch/usb_audio')
[U]17.09.2014[/U]
1.5.4 -> 1.5.5
- get rid of DVFS limit without breaking Stock 4.1 or Android 4.3 / Android 4.4
thanks [user=5562153]@LuuchoRocha[/user] and [user=4832589]@cocafe[/user]
[U]16.09.2014[/U]
1.5.3 -> 1.5.4
- Android 4.3: added PAC Support
- Nintendo Wii Remote support (experimental, untested)
- cpufreq: turn all CPUs online when governor gets changed
[U]04.09.2014[/U]
1.5.1 -> 1.5.3
- "magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
- Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
- Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
- symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
[u]01.09.2014[/u]
1.5.0 -> 1.5.1
fix broken Dual-Boot (because missing "tmp" folder inside ramdisk? also some file permissions fixed inside ramdisk)
1.4.0 -> 1.5.0
Upstream Kernel Changes to 3.0.101 - thanks a lot to @Fred6681 for fixing some know Problems after Upstream!
Build Xpad module (not tested if it is working)
Enabled DVFS Limit to make the Kernel boot on Stock and AOSP Roms
New Charger-Animation - thanks a lot to @daywalk3r666
[u]25.08.2014[/u]
1.3.1 -> 1.4.0
Initial CM 10.2 support
[u]22.08.2014[/u]
1.3.0 -> 1.3.1
Fix 800mhz bug, thanks to @Fred6681
1.2.0 -> 1.3.0
Updated Android 4.4 ramdisk: this will fix broken Wifi on Novafusion Roms / Roms based on Novafusion source
Build exFat as module
[u]20.08.2014[/u]
1.1.0 -> 1.2.0
Added Stock / Stock based 4.1 Support
More i/o scheduler: Added sioplus | row | zen
Compiled using GCC 4.7 again for better compatibility
Update LZO compression
arm/vfp: Makefile optimization
and some more....
1.0.5 -> 1.1.0
Fixed bootmenu flickering / blackscreen :) now the bootmenu is 100% visible
(Reboot-Recovery option from bootmenu not working, ends in kernel-panic,
reboot bootloader not working, it will normal reboot)
partially restore initial cm11 ramdisk
cleanup cm11 ramdisk
[U]19.08.2014[/U]
1.0.4 -> 1.0.5
Update permissions inside init.samsunggolden.rc,
set SELinux to permissive for now,
lzma compressed ramdisk
1.0.3 -> 1.0.4
Use Linaro 4.8 Toolchain
[U]18.08.2014[/U]
1.0.2 -> 1.0.3
Use Linaro 4.7-2013-04 Toolchain
[U]12.08.2014[/U]
1.0.1 -> 1.0.2
- fix an Superuser issue, added back init.superuser.rc
1.0.0 -> 1.0.1:
- fix "com.android.phone" crashed on Vanir Rom
1.0.0:
- initial release
How-To
Flash PhilZ Touch Blackhawk Recovery
Reboot into PhilZ Touch Blackhawk
Flash NEXT Kernel
Advanced Functions -> Run Aroma Dual Boot Tool
Create a 2nd System.img (choose 1 GB)
Reboot your recovery
Choose the 2nd Bootoption (it is flickering, black screen, just press the volume down key one time and press the power button).
Now the navigation buttons inside PhilZ Touch are RED
Flash a 2nd Rom (i tested my own SlimKat and @golden-guys OmniROM because they don't use F2FS)
Flash NEXT Kernel again
Reboot
Now you will see a Bootmenu (flicckering & blackscreen), you will see it short if you press the volume key,
first option = boot 1st Rom, second option = boot 2nd Rom
USE ON YOUR OWN RISK! MAKE A BACKUP BEFORE TRYING!
Reserved
Dual Boot FAQs
Adapted from @ketut.kumajaya s Dual-Boot FAQ,
original adapted from droidphile's "Dual Boot FAQs".
1. "Why would I wanna dual-boot?"
A. You don't have to.
You need one testing system and don't want to break your daylie Rom.
You can not decide between different Roms - use both
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p24 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel.
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=54772218&postcount=2
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present AOSP, setup AOSP as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash AOSP ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
2) Present AOSP, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create a 2nd system.img and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your AOSP ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Reboot into primary recovery
viii) Flash AOSP ROM as 1st ROM
ix) Flash blackhawk's NEXT kernel again
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition
20. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool or "Run Aroma Dual Boot Tool" in Advaced Menu from PhilZ Touch Blackhawk and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
21. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
22. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
23. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
24. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
25. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
26. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p25 = /data
mmcblk0p22 = /system
mmcblk0p23 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition.
Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom.
Cache in mmcblk0p24 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p25 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- dev/block/mmcblk0p24 is mounted as /cache.
How to get important Logs
tonyp said:
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
More FAQs will be added and the list will be updated as DB is improved.
Wow!
another milestone in the S3 Mini history!
Keep it up bro :good:
Incredible!!
This will bring my two favorite ROMs on one device!! Unbelievable Till now, I thought it is possible only with linux lubuntu and ROM, like on my tab...
Thank you!
m.
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
meduza2 said:
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
Click to expand...
Click to collapse
Ah missed that part! Thanks for pointing out.
Sent from my GT-I8190/Novafusion CM11
No worries
m.
heithered said:
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Click to expand...
Click to collapse
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Android-Andi said:
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Hey, this is a big deal. It is still awesome with or without stock support! Thanks for your awesome work!
Sent from my GT-I8190/Novafusion CM11
Well, just to leave an "Amazing work" as always:good:
great work.....dual boot with slimkat and omnirom works perfect.with vanir "com.android.phone" crashed
Top Job and faster as Nova!!!!
especially for you
@Android-Andi,
because of the world first dual boot for our s3mini, we created extra an info banner for you
Please have a look: Weltpremiere bei hubo.in
meduza, bodo_1, daywalksr666, kingg
Wow, you did it! That's so cool! Thanks a lot for this! ?
Simply awesome
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
The only idea i have:
First ROM for daily use
Second ROM for testing and replacing with different ROMs...
m.
moonryder said:
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
m.
Click to expand...
Click to collapse
you can load two roms to your phone.
at start up,you can choose either of 2 roms.
may be from recovery mode I think.
this is all what I know. hope I helped.
waiting for correction if I was wrong.
thanks and great work and much appreciation to Android Andi bro
@moonryder,
you could quickly boot one of your favorite ROMs or use the second boot partition for test ROMs....
m.
Hi all,
It's ME again, being inactive for a few years due to my health conditions since Android Marshmallow! Today I would like to present you something I wanted for so long... an updated kernel for One UI 2.5! To be honest, I knew there were a lot of changes since MM, but not until these days I realized how troublesome they are, including rooting a device these days!! ( just rooted my N960F/DS running stock pie for more than a year )
OK, here we go!!
This is an update to the BeastMode Kernel vR154 originally developed by @freeza and patched with latest Samsung One UI 2.5 kernel sources.
Some of the features from R154 include:
- enforcing kernel (switchable between enforcing/permissive)
- cpu/gpu oc
- dt2w (double tap to wake)
- wireguard support
However, due to my health conditions, I cannot spend too much time to update this kernel everyday although I am jobless, nor to have frequent updates as what @freeza did to his BeastMode Kernel. So please don't expect things will come very often. Thank you
Special notes for BeastMode Kernel v2 initial release:
- in the initial release (v2.02) there is no fix nor new feature added to the BeastMode Kernel vR154, as it servers as an update for new One UI 2.5 ROMs released by Samsung only
- for existing features, problems or solutions, please visit the original BeastMode Kernel thread by @freeza
- new features will be added in later releases
BeastMode Kernel v2:
- built with EVA GCC 12 and Proton Clang 13.0.0
- for cts profile/safetynet fix, please install the Universal SafetyNet Fix by @kdrag0n
Planned features:
- more IO schedulers
- more governors
- OC/UV (partially done)
- f2fs (DONE!)
If you like this, please consider donating a loaf of bread or something to support my living or buy some treats for my old dog @ https://paypal.me/ykkfive ( I don't need coffee or beer ). Thanks!
Important Notes:
if you are using a kernel manger, please go to here and see if you are affected
Downloads:
Changelog and downloads in post #2
Credits:
Big thanks to @freeza for allowing me to use his work and publish this update
Samsung open source
@evdenis
@yarpiin
@Da-BOSS
@flar2
@faux123
xxmustafacooTR
Source code:
github
NOTE: I am not responsible for bricked devices, loss of data, etc. Flash it with your OWN RISKS and ALWAYS DO A FULL BACKUP first
NOTICE:
20020526 - many of the links below were blocked by bit.ly for unknown reasons. up to now the latest 2.17k2 links are not affected. i have reported to them already
Changelog and Download (NO mirror please):
*** TWRP 3.3.1.0 is recommended
20230223 - v2.18f1a3 [Links Fixed]
- patched with latest N960FXXU9FVH1 source
- upstreamed to linux 4.9.304
- added battery charge control for max charging (default: disabled, max=85, min=40) [Do a EFS Backup first]
- fixed breathing/fading led
- misc updates and changes
- IMPORTANT: please set the io scheduler to noop (by default) as to increase the ext4 performance
Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
FUF5
BM-Kernel-v2.18f1a3-FUF5-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUH1
BM-Kernel-v2.18f1a3-FUH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUJ2/FUK1
BM-Kernel-v2.18f1a3-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FVC2
BM-Kernel-v2.18f1a3-FVC2-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FVH1
BM-Kernel-v2.18f1a3-FVH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
Previous releases:
20220522 - v2.17k2
- NOT compatible with alex 3.3 with may updates, screenlock and samsung account problems may occur
- patched with latest N960FXXU9FVC2 source
- fixed gpu table max freq and other related stuff
- all gpu frequencies shown
- big cores single 2886000, big cores triple/quad 2314000 (Tip: overclock may damage your phone, you have been warned)
- IMPORTANT: please set the io scheduler to noop (by default) as to increase the ext4 performance
Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
FUF5
BM-Kernel-v2.17k2-FUF5-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUH1
BM-Kernel-v2.17k2-FUH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUJ2/FUK1
BM-Kernel-v2.17k2-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FVC2
BM-Kernel-v2.17k2-FVC2-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
20220122 - v2.17i
- cpu oc big cores quad to 2002000
- cpu oc little cores to 2002000
- preset cpu uv for frequency < 2000kMhz
- preset gpu uv for frequency < 500kMhz
- added dynamic fsync: performs fsync only when screen is off for maintaining data integrity (make sure to enable both fsync and dynamic fsync options)
- raised some internal values:
-- little cores will go to 2002000 instead of staying at 1950000
-- big cores will go back to higer frequencies after throltted when temperature drops
- added frandom
- some more tweaks i cant remember
- IMPORTANT: please set the io scheduler to noop (by default) as to increase the ext4 performance
Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
FUF5
BM-Kernel-v2.17i-FUF5-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUH1
BM-Kernel-v2.17i-FUH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUJ2/FUK1
BM-Kernel-v2.17i-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
20211130 - v2.15a
- patched with latest FUJ2 sources
- some more tweaks
- IMPORTANT: please set the io scheduler to noop (by default) as to increase the ext4 performance
Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
FUF5
BM-Kernel-v2.15a-FUF5-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root) - RE-UPLOADED
FUH1
BM-Kernel-v2.15a-FUH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root) - RE-UPLOADED
FUJ2
BM-Kernel-v2.15a-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root) - RE-UPLOADED
20211121 - v2.14b2-FIXED
- FIXED no sound ocasionally after reboot (tested for more than 10 reboots)
- added PELT
- undervolt including memory/bus, etc
- gpu oc to 598 again
- many other performance and battery saving tweaks, as well as other that I could not remember
- swithed back to 250 HZ due to the no sound bug
- IMPORTANT: please set the io scheduler to noop as to increase the ext4 performance
Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
FUF5
BM-Kernel-v2.14b2-FIXED-FUF5-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUH1
BM-Kernel-v2.14b2-FIXED-FUH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUJ2
BM-Kernel-v2.14b2-FIXED-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
20211120 - v2.14b2
- REMOVED due to an old minor bug was re-introdecued which occasionally produce no sound after a reboot
- pls download the v2.14b2-FIXED above
20211024 - v2.12
- for FUF5/FUH1 (NOTE: 2 different versions)
- updated to latest samsung FUH1 sources
- fixes for slow ext4 performance due to bugs introduced by ext4 and kernel updates
- IMPORTANT: please set the io scheduler to noop as to increase the ext4 performance
Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
FUF5
BM-Kernel-v2.12-FUF5-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUH1
BM-Kernel-v2.12-FUH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
20210920 - v2.11c6
- for FUF5/FUH1 (NOTE: 2 different versions)
- updated to latest ext4 and f2fs
- full f2fs support (cache and data partitions tested, system not yet tested) ** MAKE SURE you know how to go f2fs first
- linux upstream to 4.9.280
- some other tweaks and patches
Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
FUF5
BM-Kernel-v2.11c6-FUF5-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
FUH1
BM-Kernel-v2.11c6-FUH1-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
20210818 - v2.10
- revised from the beginning with updates to FUF5
- cpu oc/uv
- gpu overclock/under voltage removed (awaiting fixes)
- some changes reverted
- Wake Gestures and Boeffla wakelocks included
- bring back the performance from initial release (up to 23% or more with multi cores, and nearly 3x memory performance when compared with v2.04) ** thanks for reporting this issue
Downloads (mediafire):
BM-Kernel-v2.10-magisk_patched.zip (patched with Magisk 23.0)
boot.img (no root)
Known Issues:
20210730:
(I) for version up to v2.05, the following features do not work as expected due to my mistakes
- Wake Gestures including double tap to wake (dt2w), swipe to wake (s2w), etc
- Boeffla wakelocks
- These problems will be fixed in the next version soon.
FIXED. Please accept my sincere apology
(II) in v2.05 default gpu voltage may incorrectly show the modified values as default values in kernel manager
(III) since v2.04m the performance is not as good as v2.03 due to the introduction of some kernel changes
20210730 - v2.05a
- Wake Gestures and Boeffla wakelocks problems fixed
- no other changes, bugs fixing release of v2.05
20210729 - v2.05
- updated with Samsung FUF5 sources just released
- no other changes
- REMOVED, superseded by v2.05a
20210726 - v2.04m
- compatible with FUF5 (** may have problems if you use lockscreen or samsung account with possible fix here. ALWAYS do a full backup first)
- overclocked: cpu little to 2002000Mhz, gpu to 598000Mhz
- undervoltaged: cpu/memory
- gpu undervoltage support awaiting a fix
- linux upstreamed to 4.9.250
- cherry picked some kernel tweaks
- for undervolting the gpu, you may go and read my settings here awaiting a fix
More Previous releases:
20210628 - v2.03
- added "magisk detected" BASIC fix to prevent apps trying to detect if magisk is installed (only some of the detections are prevented)
- you can see the difference by installing an app from google play store called "Дія" issued by Ministry of Digital Transformation of Ukraine
{
"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"
}
- for more info, please read:
https://darvincitech.wordpress.com/2019/11/04/detecting-magisk-hide/
- for a comprehensive solution (NOT TO BE SUPPORTED/DISCUSSED HERE):
https://forum.xda-developers.com/t/magisk-detected-on-bankapp-solved.4258245/
IMHO, if there's nothing bothering you, you can ignore this comprehensive solution atm. but of coz it's up to you
20210621 - v2.02 (init release)
*** Special announcement for Dr.Ketan ROM Q16 - 20210623 ***
it seems there are some compatibility issues with Dr.Ketan ROM Q16 and this kernel, due to the fact that Q16 is based on N960FXXU8FUE1 while this kernel is N960FXXS8FUE5. As a result you may not be able to login to Samsung Account, or have cts profile/safetynet issue. So please MAKE A FULL BACKUP before proceed.
- updated with N960FXXS8FUE5 sources
- tested with stock rom UE5, Dr Ketan Q16 with some patches
- working properly with DevBase 7.4 and Alexis ROM 2.8 from users feedbacks
*** make sure you have flashed N960FXXS8FUE5 AP, BL, modem etc
.
reserved #2
reserved #3
Life battery? Sot?
Tested with Dr.Ketan Q16 ROM
Detonatte said:
Life battery? Sot?
Tested with Dr.Ketan Q16 ROM
Click to expand...
Click to collapse
need more time to test, just finished the release last nite
it should be the same with r154 however, unless samsung made some mistakes in the latest versions
from my 3 or 4 days experience, it's about 2-3% per nite in flight mode for around 17 to 20 hours
edit: on stock rom
were you on dr ketan q16 before? do you notice any difference?
Works perfectly on ALEXNDR/DevBase v7.4, No Issues/Bug yet. So far so Good, I tried Gaming on it and it's Very Smooth on Stock Clocks, No unnecesarry Overheat and Drain, and even though I turned off Fast Charging it still Charge Fast. Great Work Dev!
JC1126 said:
Works perfectly on ALEXNDR/DevBase v7.4, No Issues/Bug yet. So far so Good, I tried Gaming on it and it's Very Smooth on Stock Clocks, No unnecesarry Overheat and Drain, and even though I turned off Fast Charging it still Charge Fast. Great Work Dev!View attachment 5343821
Click to expand...
Click to collapse
credits to @freeza ( golden freeza? )
i only updated it to one ui 2.5, that's all for this initial release. perhaps the newer toolchains help too performance-wise
With Dr.Ketan Q16 SOT 4 hours
Detonatte said:
With Dr.Ketan Q16 SOT 4 hours
Click to expand...
Click to collapse
pls wait, i just installed q16 and i am facing some problems. now reinstalling
btw, do you find it a bit lag sometimes after installing q16?
No, no exist lag. Q16 rom is perfect custom rom. Q16 is very stabil rom.
Detonatte said:
No, no exist lag. Q16 rom is perfect custom rom. Q16 is very stabil rom.
Click to expand...
Click to collapse
can you tell me more about how did you do the update in more details pls?
for example, were you on Q16 already? then you install my kernel and that's all? what about your cts profile/safetynet status? etc
Detonatte said:
No, no exist lag. Q16 rom is perfect custom rom. Q16 is very stabil rom.
Click to expand...
Click to collapse
i mean, did you notice any jitter or lag after installing this kernel with Q16?
01. Open phone in TWRP
02. Wipe
03. Advanced Wipe
04. Mark:
- Dalvik ART/Cache
- Cache
05. Swipe to Wipe
06. Back
07. Back
08. Back home
09. Install
10. Select Storage
11. Micro SD card
12. OK
13. Choose
- BM-Kernel-v2.02-magisk_patched.zip
14. Swipe to confirm Flash
15. Wait to flash
16. Finish
17. No Reboot System !!!!
18. Back home
19. Install
20. Select Storage
21. Micro SD card
22. OK
23. Chose:
N960_F_DS_N_DrKetan_custom_ROM_Q16.zip
24. Swipe to confirm Flash
25. Next
26. Mark:
- I Agree with this Terms Of Use...
27. Next
28. Next
29. Next
30. Chose:
- Proceed with ROM flasher and MultiTool
31. Mark:
- Do Not Change
32. Next
33. Mark:
- Patch for OEM issue
34. Next
35. Mark: (CSC Flasher)
- Do Not Change
36. Next
37. Mark:
- Keep Existing Kernel
38. Next
39. Mod features
40. Mark:
- Fix For Custom Kernel
41. Next
42. Run Now
43. Wait to flash
44. Next
45. Finish
46. Wipe Cache/Dalvik
47. Swipe to Wipe
48. Reboot System
Detonatte said:
01. Open phone in TWRP
02. Wipe
03. Advanced Wipe
04. Mark:
- Dalvik ART/Cache
- Cache
05. Swipe to Wipe
06. Back
07. Back
08. Back home
09. Install
10. Select Storage
11. Micro SD card
12. OK
13. Choose
- BM-Kernel-v2.02-magisk_patched.zip
14. Swipe to confirm Flash
15. Wait to flash
16. Finish
17. No Reboot System !!!!
18. Back home
19. Install
20. Select Storage
21. Micro SD card
22. OK
23. Chose:
N960_F_DS_N_DrKetan_custom_ROM_Q16.zip
24. Swipe to confirm Flash
25. Next
26. Mark:
- I Agree with this Terms Of Use...
27. Next
28. Next
29. Next
30. Chose:
- Proceed with ROM flasher and MultiTool
31. Mark:
- Do Not Change
32. Next
33. Mark:
- Patch for OEM issue
34. Next
35. Mark: (CSC Flasher)
- Do Not Change
36. Next
37. Mark:
- Keep Existing Kernel
38. Next
39. Mod features
40. Mark:
- Fix For Custom Kernel
41. Next
42. Run Now
43. Wait to flash
44. Next
45. Finish
46. Wipe Cache/Dalvik
47. Swipe to Wipe
48. Reboot System
Click to expand...
Click to collapse
very detailed, thanks
it looks like the step are similar to mine, except that i didnt chose the fix for custom kernel. i will post my battery consumption later today
Detonatte said:
With Dr.Ketan Q16 SOT 4 hours
Click to expand...
Click to collapse
here's mine today, with Q16 compatibility fixes
1st image: screen on for 2h17m for surfing the internet, and started google map for a minute (but it still consuming battery in the background and triggered an alarm)
2nd image: more than 10 hrs in flight mode
Detonatte said:
01. Open phone in TWRP
02. Wipe
03. Advanced Wipe
04. Mark:
- Dalvik ART/Cache
- Cache
05. Swipe to Wipe
06. Back
07. Back
08. Back home
09. Install
10. Select Storage
11. Micro SD card
12. OK
13. Choose
- BM-Kernel-v2.02-magisk_patched.zip
14. Swipe to confirm Flash
15. Wait to flash
16. Finish
17. No Reboot System !!!!
18. Back home
19. Install
20. Select Storage
21. Micro SD card
22. OK
23. Chose:
N960_F_DS_N_DrKetan_custom_ROM_Q16.zip
24. Swipe to confirm Flash
25. Next
26. Mark:
- I Agree with this Terms Of Use...
27. Next
28. Next
29. Next
30. Chose:
- Proceed with ROM flasher and MultiTool
31. Mark:
- Do Not Change
32. Next
33. Mark:
- Patch for OEM issue
34. Next
35. Mark: (CSC Flasher)
- Do Not Change
36. Next
37. Mark:
- Keep Existing Kernel
38. Next
39. Mod features
40. Mark:
- Fix For Custom Kernel
41. Next
42. Run Now
43. Wait to flash
44. Next
45. Finish
46. Wipe Cache/Dalvik
47. Swipe to Wipe
48. Reboot System
Click to expand...
Click to collapse
could you try to apply netflix HD patch then try to watch a movie on it? I tried to watch but it takes too much time to load. Sorry for off-topic
SOT no good!!! Flight mod not use!!!
Detonatte said:
SOT no good!!! Flight mod not use!!!
Click to expand...
Click to collapse
there must be something wrong, what's the sot before?
CyderXDA said:
could you try to apply netflix HD patch then try to watch a movie on it? I tried to watch but it takes too much time to load. Sorry for off-topic
Click to expand...
Click to collapse
i think it should be done in rom