Related
This is a kernel, build from the recently released saga-ics-crc-3.0.16-62a67df source.
Compatible with all ICS (Android 4) + Sense (3.6, 4A or 4) based ROMs
OFFICIAL MIUIv4 and Stock rooted ICS users can enjoy init.d scripts support with this kernelEnjoy!BACK2BASICS EDITION
FEATURES
Interactive Aroma Installer
Completely Stock code, with only 2 additions by me:
Configurable sweep2wake.
Ported bcmdhd wireless driver from the HTC One V latest source code for better reception and no wakelocks. Still breaks WiFi tethering in ROMs based on Sense 3.6. Tethering works fine in Sense 4
Completely Stock ramdisk. The only changes are:
Unsecured boot.img (adb remount and USB debugging)
Busybox run-parts (init.d scripts) support
Some extra lines, required for the proper operation of the new WiFi driver
No OC, UV, optimizations or any other changes.
Compiled with the recommended by HTC toolchain 4.4.3
ISSUES
For all with BLUETOOTH issues: use 4EXT Recovery
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to falsemanually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
NEW USERS: before flashing install/update BusyBox in /system/xbin (with some of the apps available in the Google Play - the one by Stericsson+Smart Install worked fine for me) and check for the existence of the busybox binary and run-parts symlink in the /system/xbin folder on your device. If there is no such files install/reinstall BusyBox until you have it.
OPTIONAL: If you do not have an /system/etc/init.d folder AND you want to use additional modules you should create it manually BEFORE flashing the kernel:adb remount
adb shell
mkdir /system/etc/init.d
chmod 775 /system/etc/init.d
DOWNLOAD AND INSTALLATIONDownload: b2b_3-0-16.zip
md5sum: d5bd32bd12a0e1120b03f800eaf1beda
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with th following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.imgIMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
Boot images are:
Sense4_boot.img - for all Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa Prime, Desire XS, ViperSaga, others)
Custom_Sense36_boot.img - for ICE_DS, Stock ICS by masteross, or other custom Sense 3.6 ROM without lib partition
Stock_Sense36_boot.img - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_boot.img - for any version of official MIUIv4
NOTES:
There is no boot.img for Virtuous Infinity since it cannot operate smooth with the Stock CPU settings
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)
PATCHED KERNEL 3.0.89
Due to controversial feedback on Tweaked kernel starting from version 5.0 I have decided to take a different approach.
Patched kernel unifies the concept of both Tweaked3 and B2B kernels.
So what does this mean?
The HTC source is taken as a base and is synced completely with the upstream (the official Android kernel 3.0) where applicable. Since it is patched only up to 3.0.72 the rest of the patches are taken directly from the Linux kernel upstream.
All is done from scratch and revising every single commit (it took me 4 days to complete this only). The result is absolutely clean merge (not as in Tweaked where I took the patches from other developers without actually knowing have they screw up something in the progress). During the patching I have discovered some misses or copy-paste from 3.4 upstream (which I consider for another generation devices and probably the changes from there are not completely suitable for our device). I have cleaned and synced with the 3.0 upstream all not-updated files that I discovered during the patching.
FEATURESThe features of the kernel are the basic ones from Tweaked, but staying as close as possible to the Stock configuration (B2B concept):
Interactive Aroma Installer
Compiled with GCC 4.4.3 toolchain
Patched to Linux Kernel version 3.0.89
Synced with Android kernel 3.0 upstream
Overclockable to 1.5 GHz
Added VDD sysfs interface for userspace UV control
Stock Frequencies and Voltages
Default governor: INTERACTIVE @ 254 - 1024 MHz
Interactive governor updated from android 3.4 upstream
Default scheduler: DEADLINE
Configurable Sweep2Wake
Fixed WiFi tethering on Sense 4 based ROMs
Updated WiFi drvier from HTC One V source
Built-in CIFS support
Built-in TUN support
Built-in NTFS + NLS_UTF8 support
Optional WiFi calling
Two way call recording - both WAV and AMR
Enabled USB OTG HOST (big thanks to astro757 and engelmarkus)
Enabled SWAP support
ISSUES
If your WiFi does not work upon install check this solution /10x to toxic-hero/
Sometimes the sweep2wake does not work instantly after deep sleep period. Just swipe once more to unlock the device or press the search button.
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to false manually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
For all with BLUETOOTH issues: use 4EXT Recovery
USEFUL INFORMATION, PLEASE READOverclocking applications, reported to work:
If you are in doubt which governor and IO scheduler to use - there is a lot of useful info here (thanks to Tectas and the authors)
SetCPU
Voltage Control {settings not stick after reboot on Virtuous Infinity}
No-frills CPU Control {settings not stick after reboot on Virtuous Infinity}
Daemon Controller app + andrev_oc script
note1: there is virtuous_oc on Virtuous Infinity already, so you can use only the Daemon Controller app
note2: oc daemons are not supporting scheduler changing
undervolting can be done with a command from Terminal Emulator or adb shell:echo -X > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levelswhere X is the desired value (-25, -50, -75, -100, -125 or whatever you like). Unfortunately has to be repeated after every reboot since putting it in an init.d script is risky
Originally posted by engelmarkusHi,
I played around with the experimental branch of your kernel once more and today it works perfectly.
Keyboards, mice and USB storage devices work without any messing with the terminal. For almost-auto-mounting I used this app here: https://play.google.com/store/apps/d....shajul.usbotg
So I think you can very well enable this in your next kernel version so others can try this out, too.
DOWNLOAD AND INSTALLATIONDownload: 3089.zip
md5sum: 921dda7817b33ee1b7730afca4c57e1c
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with the following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.imgIMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
Boot images are:
Virtuous_boot.img - for any version of Virtuous Infinity
Sense4_boot.img - for other Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa, Desire XS, ViperSaga, others)
Custom_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Custom_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Stock_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
Stock_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for any version of official MIUIv4
MIUIv4_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for any version of official MIUIv4
Sense4_lib_boot.img - for recent versions of Desire XS or other Sense 4 ROM that is reodexed/with separate lib partition
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)
TWEAKED3 VERSION XI DISCONTINUED - reference only
FEATURES
Interactive Aroma Installer
Patched to Linux Kernel version 3.0.56
Added ck1 patchset by Ziggy (thx to Coolexe) - aims towards better performance
Compiled with the latest stable Linaro GCC 4.7.3-2012.11 toolchain
Overclockable to 1.5 GHz
Added VDD sysfs interface (10x to lowveld) for userspace UV control
Stock Frequencies and Voltages
Tuned ONDEMAND and INTERACTIVE governors
Tuned DEADLINE and SIO schedulers
ONDEMAND @ 254 - 1024 MHz and DEADLINE set as default
Enabled TINY_PREEMPT_RCU
Some tweaks and optimizations for better performance
Configurable Sweep2Wake
Fixed WiFi tethering on Sense 4 based ROMs (10x to m0narx)
Updated WiFi driver from the latest HTC One V source
Enabled CIFS and TUN support
Enabled NTFS + NLS_UTF8 support
Enabled PPP_ASYNC and PPP_SYNC_TTY
Two way call recording - works in AMR and WAV (10x to Andromadus) format with CallRecorder app by skvalex
CHANGELOG
16 Dec 2012: Tweaked3 XI:
Compiled with the latest stable Linaro GCC 4.7.3-2012.11 toolchain
Patched to Linux Kernel version 3.0.56
Upstream update of interactive governor change speed routine
Enabled TINY_PREEMPT_RCU - should give small-memory-footprint on uniprocessor systems (where all processing tasks share a single CPU)
23 Nov 2012: Tweaked3 10.0 (X):
Patched to Linux Kernel version 3.0.52
Removed all third party governors
Removed BFQ, VR and CFQ schedulers
Tweaked SIO for better performance on Android
All modules built-in, except the one for WiFi Calling (kineto-gan.ko - optional)
No more init.d scripts, except for sweep2wake
During installation a /system/etc/init.d folder will be created, with the right permissions on ROMs that do not have such
09 Nov 2012: Tweaked3 9.0:
Compiled with the latest Linaro Toolchain 4.7.3-2012.10
Patched to Linux Kernel version 3.0.51 (10x to oliverclaude)
Ondemand and Interactive governors synced to upstream (10x to Andromadus)
Scheduler improvements (10x to faux123)
16 Oct 2012: Tweaked3 8.6:
Patched to Linux Kernel version 3.0.46
Updated BFQ code to v5 (10x to Andromadus repo)
2WCR now makes recording in WAV format (10x to Andromadus repo)
BCMDHD wireless driver is updated to the latest HTC One V source - there are some changes related to the Country Codes, so please anyone that has such issues to try it without WiFi FIx app and report
Initialization of the wireless modules moved to ramdisk, no need of init.d script to run them anymore, so new users can skip that part and go straight to flashing!
10 Oct 2012: Tweaked3 8.5:
Patched to Linux Kernel 3.0.45
Added ck1 patchset by Ziggy (thx to Coolexe) - aims towards better performance
Removed ZRAM - it seems that the compression was the reason for the battery drain
Removed the script for changing the screencapture line in build prop from Aroma, hopefully this will solve the installation issues. You will have to change it manually if needed
01 Oct 2012: Tweaked3 8.0:
Aroma installer - one file for all. No need to do any preparations anymore (like changes of the updater-script, etc) The installer will gather the important information about your ROM and hboot and the flashing process will be done accordingly.
HTCDEV users: there are instructions in the first post which boot.img to flash. Important: if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
All governors are tuned up according to the CPU frequencies (should have done it long time ago, sorry for the delay). OndemandX (proved unstable) and Userspace (doubt that anyone even uses it) governors removed
CIFS, TUN, KINETO_GAN, NTFS+NLS_UTF8 and ZRAM moved to modules for optional install (the installer will give you a menu for selection, where the purpose of each module is explained)
Updated LZO compression/decompression method for ZRAM (it sould be at least twice faster now)
TREE_RCU and SLAB memory allocator set as default (as it was in the Stock kernel).
21 Sep 2012: Tweaked3 7.1:
Patched to Linux kernel version 3.0.43
Compiled with the latest stable Linaro GCC 4.7-2012.08 toolchain
Added VDD sysfs interface (10x to lowveld) for userspace UV control (comes with Stock Voltages by default)
Added BrazilianWax, InteractiveX and OndemandX governors
All modules except bcmdhd.ko are built-in in the kernel
Finally found the reason of the battery drain when the Screen is ON and hopefully fixed it. Now the battery life should be rock solid
Flashable zips should be fixed for good. They now will wipe dalvik-cache and cache during flash, no need to do it manually. Version 5.0 zips are backwards compatible (this means you can flash version 5 over version 7.1 without additional actions (deleting or moving files)
05 Sep 2012: Tweaked3 6.0:
Added bcmdhd WiFi driver and fix WiFi Tethering on Sense 4 ROMs (10x to m0narx)
Flashable zips are back!
Comes is two flavors - undervolted -100 and Stock voltages
02 Sep 2012: Tweaked 5.0:
Built with Linaro toolchain
Patched to Linux Kernel version 3.0.42
Reverted to Stock Voltages due to some users complaints
SLUB is the default memory allocator
Added tun.ko module (use 51-modules init.d script to load it)
Added cifs.ko module (use 51-modules init.d script to load it)
Enabled full capacity charge in non-OEM chargers (e.g. some car chargers)
Enabled NTFS + NLS_UTF8 support
Enabled PPP_ASYNC and PPP_SYNC_TTY
Enabled ZRAM - adds another 100 MB to your RAM as a SWAP partition (use 52-zram init.d script to load it)
Enabled USB-OTG (needs confirmation, since I do not have the necessary equipment) - not working
27 Aug 2012: Tweaked3 4.7:
Expanded frequency table - to give the CPU more steps until the highest frequency
Slight undervolting to save some battery life
Fixed backlight staying on when pressing only home button when s2w with backlights enabled (10x to scan6 for the heads up)
Default clock frequency is 1024 MHz for everyone that requested it
Enabled init.d support in the MIUIv4 version (now you can use the 50-sweep2wake script too)
Separate installation files and instructions for S-ON (hboot 2.00.0002) and S-OFF (hboot 0.98.2000, 2.00.2002, 7.xx) users
25 Aug 2012: Tweaked3 4.0:
Patched to Linux Kernel version 3.0.41
Added sweep2wake configuration: default Enabled with no backlight
Added lionheart, lulzactive, intellidemand, scary, lagfree, lazy and savagedzen governors
Added BFQ and VR schedulers
Added Snapdragon optimizations
23 Aug 2012: Tweaked3 3.0:
Added Lionheart and Smartass2 governors
Added Simple IO Scheduler
Enabled ARCH_POWER
Disable GENTLE_FAIR_SLEEPERS
22 Aug 2012: Tweaked3 2.0:
Patched to Linux Kernel version 3.0.30
Added support for MIUIv4 and Virtuous Infinity
Source code published @github
21 Aug 2012: Initial release
Based on the released by HTC saga-ics-crc-3.0.16-62a67df source
Added Sweep2wake functionalit
Overclocked to 1,5 GHz
ISSUES
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to falsemanually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
For all with BLUETOOTH issues: use 4EXT Recovery
USEFUL INFORMATION, PLEASE READOverclocking applications, reported to work:
If you are in doubt which governor and IO scheduler to use - there is a lot of useful info here (thanks to Tectas and the authors)
SetCPU
Voltage Control {settings not stick after reboot on Virtuous Infinity}
No-frills CPU Control {settings not stick after reboot on Virtuous Infinity}
Daemon Controller app + andrev_oc script
note1: there is virtuous_oc on Virtuous Infinity already, so you can use only the Daemon Controller app
note2: oc daemons are not supporting scheduler changing
undervolting can be done with a command from Terminal Emulator or adb shell:echo -X > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levelswhere X is the desired value (-25, -50, -75, -100, -125 or whatever you like). Unfortunately has to be repeated after every reboot since putting it in an init.d script is risky
DOWNLOAD AND INSTALLATIONDownload: Tweaked3_XI.zip
md5sum: e9bf1393d48c6f7e7e8697e34ac63e7a
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with the following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.imgIMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
Boot images are:
Virtuous_boot.img - for any version of Virtuous Infinity
Sense4_boot.img - for other Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa, Desire XS, ViperSaga, others)
Custom_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Custom_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Stock_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
Stock_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for any version of official MIUIv4
MIUIv4_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for any version of official MIUIv4
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)
Stock Sense GingerBread sweep2wake kernel
MIRROR @ DEV-HOST /all versions/:
SOURCE CODE
Tweaked3 - experimenal branch
B2B - stable branch
Patched - linux branch
CREDITSHTC for the source code
BIG thanks to m0narx for the WiFi Tethering fix!
showp1984 and his source for atmel touchscreen devices
mdeejay for some of the linux version patches
AdiPat for his repo
Coolexe for his repo
cjoliver for the sweep2wake switch and the recent upstream patches
crking for the sweep2wake init.d script
lowveld for his all great projects for HTC Desire S and the VDD sysfs
Ziggy for the ck1 patchset
Team Andromadus for their repo
astro757 and engelmarkus for the USB OTG HOST
All the great kernel developers @Xda For their great workThanks for testing and corrections:rzr09
dr.higgins
dont know
signfinder/dalexx
dmatik
TatoValverde
toxic-heroThanks for donating. Much appreciated:dont know
TatoValverde
petjoh
XDA:DevDB Information
B2B |&| Patched, Kernel for the HTC Desire S
Contributors
amidabuddha
Source Code: https://github.com/amidabuddha/saga-ics-crc-3.0.16
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: BACK2BASICS EDITION
Stable Release Date: 2012-08-21
Current Beta Version: PATCHED KERNEL 3.0.8
Beta Release Date: 2013-08-06
Created 2015-02-24
Last Updated 2015-02-24
amidabuddha said:
Features:
- Sweep2wake functionality
- Overclocked to 1,5 GHz
Download: View attachment 1273069
md5sum: 98fe244bbfb430283f194e61031e0d7f
Issues:
- due to incompatibility with s2w the native Sense screenshot function is disabled
- do not use with the official MIUI v4, since it is not mounting /system/lib on init
Installation: flash in the Recovery
Click to expand...
Click to collapse
man you are the best!!
Installed on Nik Project, any issues with buttons backlight? It seems like they are always on
Nope,it works well to me
Nik project v4.1:
1.oc ---ok
2.s2w---ok
Sent from my HTC Desire S using xda app-developers app
Nik 4.1, have 3600 in anututu =)
Will try to reinstall with really full wipe, because my buttons are always on
mizerok said:
Installed on Nik Project, any issues with buttons backlight? It seems like they are always on
Click to expand...
Click to collapse
On Fallout the backlight works as it should.
In a room without direct sunlight - off
On screen off - off
Outdoor or in a dark place - on
Try in different conditions, maybe there is too much light where you are
I wish it was usable for non Sense ROMs
Nik 4.1, Atuntu - 3527
No prob with S2W. Auto brightenss is off.
Thx Stefan.
I get 3883 on antu with fallout rom
sent from my desire s from one of lowvelds roms
docertabum said:
I wish it was usable for non Sense ROMs
Click to expand...
Click to collapse
Working on it more or less ^^
Great done amidabuddha
Gesendet von meinem GT-I9300 mit Tapatalk 2
I am not a big fan of benchmarking. But tried just out of curiosity.
Antutu: 4035 on Fallout
Sent from my HTC Desire S
It's perfect! I haven't seen so cool and fast rom as fallout with this kernel yet!
Is it not harmful for Desire S to overclock to 1.5 GHz ?
Shouldnt make any harm going to 1.5.
Now the kernel source, is https://github.com/showp1984/bricked-shooteru-ics-sense what you releasing? if no you need to release the exact kernel source you using, laws
I dont want any saga dev to have issues
Edit:
More then that, some devices comes with stock 1.5 with same processor but remember, the more you put, the less battery
Hi, is there a way to revert it to stock? Thanks.
Sent from my HTC Desire S using xda app-developers app
superkid said:
Shouldnt make any harm going to 1.5.
Now the kernel source, is https://github.com/showp1984/bricked-shooteru-ics-sense what you releasing? if no you need to release the exact kernel source you using, laws
I dont want any saga dev to have issues
Edit:
More then that, some devices comes with stock 1.5 with same processor but remember, the more you put, the less battery
Click to expand...
Click to collapse
Good point
Yes the changes for sweep2wake are the same, made by showp1984, unmodified by me
And yes, this is the stock OC, I have just enabled it for the time being.
I am pretty sure that soon there will be much more tweaked and polished kernels made by the experienced devs, but since most of them are taking summer holidays I compiled this one for playing with Sense 4 until they come back to development
Dreamtheater2003 said:
Hi, is there a way to revert it to stock? Thanks.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Yes you can always flash the original boot.img of the ROM that you are using via fastboot. Then copy the bcm4329.ko and kineto_gan.ko of your original ROM to /system/lib/modules with any root file explorer. To restore the stock screenshot feature change the value ro.htc.framework.screencapture from false to true in your build.prop
Dreamtheater2003 said:
Hi, is there a way to revert it to stock? Thanks.
Click to expand...
Click to collapse
flash the rom once again...
masterross said:
Nik 4.1, Atuntu - 3527
No prob with S2W. Auto brightenss is off.
Thx Stefan.
Click to expand...
Click to collapse
Nik Project X v4.1 with AnTuTu - 3907
sdcard: class6
wifi not working after flashed this oc file.....why?
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678873&postcount=472
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0 ROMs. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
IMPORTANT NOTES:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8.3), CM 10.1.x and CM 10.2 (since 1.8.3) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM, P31xx only: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV
brolee93 for latest P51xx Samsung stock boot image
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...
Downloads:
PhilZ Touch blackhawk version attached, PhilZ Touch 5.08.5 attached at post #3
NEXT kernel beta release attached
NEXT tool: http://forum.xda-developers.com/showthread.php?t=2285366
exFAT support files for CM/CM based ROM: http://forum.xda-developers.com/showthread.php?t=2285366 post #2
Todo:
More features in NEXT tool
Special Thanks:
@behemot24, @shakatu, @ironmaskusa, @tetakpatak
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.4
Created 2014-09-21
Last Updated 2014-10-29
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
21/10/2013 1.8.3 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
10/08/2013 1.6.3 -> 1.8.3:
Initial upcoming Samsung 4.2.2 support
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!
Updated to upstream Linux kernel 3.0.41 (incremental patch)
The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.5 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcahe memory corruption problem fixed!
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 new busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM default zRAM size 26% RAM size. Following CM's standard, user can set zRAM value for example to 30% by typing "setprop persist.service.zram 30" over Terminal Emulator or over "adb shell setprop persist.service.zram 30". CM user can use Settings application: Performance - Memory management - zRam.
Swappiness value changed to 90
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRAM support optimized for Android, utilizing the new lzo library.
cleancache support with working zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-22/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
12/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. You must update both 1st and 2nd ROM to renew both ROM vendor binaries!
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
NEXT users, please update your kernel to 1.3 version to avoid filesystem corruption risk on Samsung stock/stock based ROM! Please read Dual Boot FAQs how to update your kernel!
01/06/2013 beta -> 1.3:
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P31xx, that's way this port version directly jump to 1.3
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz. Non OC version as an addon
Both version tested on P3100 (remember, I have no access to P51xx device). Booted, upscale graphics, touchscreen not work, wrong orientation sensor, swapped volume button, got 1280x800 screenshots :laugh:
30/05/2013: Initial beta release.
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
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 mmcblk0p11 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:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
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, flash new ducati vendor blobs again (since 1.8.x)
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, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
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. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "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.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "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
26. "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.
27. "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.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /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 mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
http://forum.xda-developers.com/showthread.php?t=2285366 post #4.
Was waiting for this :victory:
Sent from my GT-P5110 using XDA Premium HD app
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button or better my DTM button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Dual Boot FAQs #29.
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
brolee93 said:
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
Click to expand...
Click to collapse
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Running smoothly for Zap Blaster.
ironmaskusa said:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Click to expand...
Click to collapse
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:
shakatu said:
Running smoothly for Zap Blaster.
Click to expand...
Click to collapse
Really? And all your init.d scripts removed by NEXT
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
shakatu said:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.
Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK.
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
behemot24 said:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
Click to expand...
Click to collapse
For free A lot of clicks to install NEXT package but why people missed to click my Thanks button
EDIT:
This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
rap3rman said:
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Two apps I never use on my tablet, so I haven't tested them...
ketut.kumajaya said:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
Click to expand...
Click to collapse
yeah ok i see this .
can you add Stweaks support ?
BIG FAT WARNING:
NEXT kernel 1.0 - 2.0 requires mali-400-r3p2-01rel3-t31x.zip!
NEXT kernel 2.1 and later requires mali-400-r3p2-01rel3-api29-t31x.zip!
Sources:
Kernel sources at https://github.com/kumajaya/android_kernel_samsung_smdk4x12/tree/cm-11.0
Features:
Based on Samsung OSRC Note 2 N7100, Tab 3 8.0 and Note 8.0 kernel source
Single source for T310, T311, and T315 target (and Note 2 N710x, Note 8.0 N51xx). Only T311 version well tested on my device but both T310 and T315 version boot T311, not working GSM radio of course
Traceable source level changes: https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0
Open source Samsung exFAT modules included
Remove a lot of debug message from touchscreen driver, display, mmc, modem, bluetooth, etc. Now, dmesg output more useful than stock kernel
Disable a lot of kernel debugging support
Linaro GCC compiler
The ramdisk based on JB 4.2.2 AMG3 (T310 and T311) and AMH1 (T315), OTA recovery flash disabled
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Auto root, SuperSU included please download SuperSU from Google Play. Heimdall v1.4.0 work for our device. For a brand new T31x, flash your device using "sudo heimdall flash --BOOT boot.img" and you will get rooted
Self compiled static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. On stock ROM, this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Mali GPU driver r3p2-01rel3
KitKat external sdcard write access for user apps patcher
Known Problems:
Thanks To:
gokhanmoral, Chainfire
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...
Downloads:
http://forum.xda-developers.com/devdb/project/?id=5210#downloads
Todo:
Dual boot
Special Thanks:
@onemoreidiot, @kutaxov, @bout_time
XDA:DevDB Information
[KERNEL][SM-T31x][SINGLE/DUAL][STOCK/CM] blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 3
Contributors
ketut.kumajaya
Kernel Special Features: Dual boot stock and CM ROM
Version Information
Status: Stable
Current Stable Version: 1.7
Stable Release Date: 2014-07-11
Created 2014-08-01
Last Updated 2014-09-11
Changelog 24/08/2014, NEXT 2.x WIP:
Samsung KitKat support
Auto root reworked
External sdcard write access auto pacher
Mali 400 r3p2-01rel3 API version 29
Changelog 11/07/2014, NEXT 1.7:
Samsung OSRC SM-T310 KitKat NF4 kernel source:
Exynos platform update
Battery, regulator, and charger driver update
Touchscreen driver and firmware update
Flip sensor, WiFi, sound, IR LED and camera driver update
Memory and block related tuning
swap, frontswap, and zswap support, etc
LZO compression/decompression update
Recent GCC versions (e.g. GCC-4.7.2) compatibility fix
Changelog 16/06/2014, NEXT 1.6:
GCC Linaro 4.9.1-2014.05 toolchain
Nintendo Wii remote support, latest CM version needed
Changelog 12/06/2014, NEXT 1.5:
Applied Samsung OSRC N7100 KitKat ND4 update on top of MK9, and then rebase our current kernel to it
Low power mode charging bug fix applied, this kernel compatible to our current JB bootloader and upcoming KitKat bootloader
Incompatibility issue to CM's hwcomposer fixed
New WiFi driver, new exFAT filesystem, arm and exynos spesific update, a lot of updates from Samsung
More efficient method of passing vsync to userspace for CM
GCC Linaro 4.8-2014.04 toolchain
Full changelog https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0 . Linaro 4.8 patch still not available on my github, I will push it later
Changelog 21/04/2014, NEXT 1.4:
Kernel update: stop log buffer spam, extra scheduler (sio, vr, and row), interactive governor, revert f2fs quick hack, etc: https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0
Ramdisk update to upstream CM (SE Linux context, sepolicy, init and healtd binary)
Install script update for easier future maintenance
Remove workaround fix for write access to the root of ext4 or f2fs formatted SD card
Changelog 26/03/2014, NEXT 1.3:
Fix boot menu reboot to bootloader option
Insecure adb, fix compatibility issue to Omni and Slim ROM
SE Linux policy update
Workaround fix for write access to the root of ext4 or f2fs formatted SD card
Default ueventd config
Compiled AROMA from source
Compiled static busybox from CM source with patched reboot applet
Changelog 16/03/2014, NEXT 1.2:
F2FS filesystem support, completely based on @DerTeufel1980 github commits and small hack in include/linux/blk_types.h https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0, Extended PhilZ Touch recovery needed for ext4 to f2fs migration
exFAT filesystem integrated in kernel
In sync to CM 11.0 init changes, CM multi SIM support compatibility issue fixed
Changelog 22/01/2014, NEXT 0.6.4:
Updated kernel source, new Mali GPU kernel driver r3p2
SuperSu 1.91 for stock ROM
Directly flash mali-400-r3p2-01rel3-blobs-t31x.zip (on both ROM for dual boot user) is a must or your device will fail to boot!
As reported by @manup456, graphic glitch occurred in stock ROM with Mali r3p2. Workaround for this issue is "Turn off hardware overlays - Always use GPU for screen compositing" in Settings - Developer but this setting doesn't stick, so you must set it on every boot. Another solution is switch to previous version of NEXT kernel and directly flash Mali r3p1 blobs (on both ROM for dual boot user).
Changelog 16/01/2014, NEXT 0.6.3:
Reworked init script as CM playground
Changelog 09/01/2014, NEXT 0.6.2:
Compatible to the new CM lights module
Changelog 05/01/2014, NEXT 0.6.1:
Flip cover detector, work on both stock and CM ROM
Changelog 30/12/2013, NEXT 0.6:
CM 11.0 support
Changelog 10/12/2013, NEXT 0.5:
Initial T315 support
CM: Ramdisk synced to unofficial CM 10.2
Changelog 02/12/2013, NEXT 0.4:
CM: fix back camera still image capture
Changelog 28/11/2013, NEXT 0.3:
CM: fix bluetooth discovery problem
CM: fix front camera preview
Add PAC ROM support
Stock: SuperSU 1.80, thanks Chainfire
T310 support
Changelog 26/11/2013, NEXT 0.2:
Add lates CM-10.2 nightly 20131125 support
SuperSU 1.75 (for stock ROM), thanks Chainfire
Changelog 25/11/2013, NEXT 0.1 brand:
Stop more spams
Linaro gcc 4.7 compatibility fix, now use GCC Linaro 4.7 compiler
VR and SIO scheduler, SIO as default sheduler
R/W semaphores implemented using ARM atomic functions
Merge espresso10 interactive CPU governor, interactive with EARLYSUSPEND support
Initializing Android USB depending on the rom type for dual boot support
Notify userspace of vsync_time using sysfs for AOSP based ROM support
Partial netfilter update, allow tracking loopback and rate limit some of the printks
Unofficial PhilZ Touch recovery
Attached PhilZ Touch recovery repack for T310 and T311. Both version tested on my T311. Both version not well tested (i.e. backup and restore not tested since have no free space SD card) but since this version based on official P5100, everything should be work correctly. Flash this at your own risk using existing CWM/TWRP recovery or Heimdall v1.4.0 "sudo heimdall flash --RECOVERY recovery.img" command.
I am almost sure @Phil3759 will officially support our device anytime soon.
ROOT + BLACKHAWK + PHILZ TOUCH FOR YOUR BRAND NEW T31X
Single step for root and PhilZ Touch recovery using Heimdall v1.4.0:
Extract both blackhawk kernel boot.img and PhilZ Touch recovery.img
Install Heimdall for your operating system: Linux, OSX, or Windows
Boot your device into download mode, connect it to your computer, flash:
Code:
heimdall flash --BOOT boot.img --RECOVERY recovery.img
Done!
NOTE: I've deleted PhilZ Touch non SELinux version to avoid confusion, total 618 downloads for all variant!
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
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 mmcblk0p16 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:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel. BIG FAT WARNING: For stock Samsung ROM, NEXT kernel 1.0 or later requires mali-400-r3p2-01rel3-blobs-t31x.zip!
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=51364377&postcount=33
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present sammy, 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 sammy, 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 system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your sammy 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
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
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. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "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
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "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.
24. "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
25. "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.
26. "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.
27. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
28. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p21 = /data
mmcblk0p20 = /system
mmcblk0p19 = /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 mmcblk0p16 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p21 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p16 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Build kernel and kernel modules for Samsung Galaxy Tab 3 8.0 SM-T31x Exynos 4212
Ketut P. Kumajaya <ketut.kumajaya at gmail dot com>, Oct 2013
Samsung Open Source Release Center: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t31
Samsung OSRC exFAT source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
Working kernel source, compilable and tested on SM-T311: https://github.com/kumajaya/android_kernel_samsung_lt01
I assume your home directory is /home/android
Clone kernel source repo:
Code:
$ cd /home/android/
$ git clone git://github.com/kumajaya/android_kernel_samsung_lt01.git
Create an environtment text file, save it as /home/android/build.env (change CROSS_COMPILE to point to your toolchain):
Code:
export CROSS_COMPILE='/opt/toolchains/arm-eabi-4.6/bin/arm-eabi-'
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm
export ARCH=arm
Import environtment file above (dot+space+build.env), create build directory outside kernel source directory, and start the building process:
Code:
$ cd /home/android/android_kernel_samsung_lt01
$ . /home/android/build.env
$ mkdir -p /home/android/build/lt01
$ make O=/home/android/build/lt01 mrproper
$ make O=/home/android/build/lt01 tab3_3G8_01_defconfig
$ make -j8 O=/home/android/build/lt01
Copy the resulting kernel and modules to a binary directory:
Code:
$ mkdir -p /home/android/build/lt01-bin
$ cp /home/android/build/lt01/arch/arm/boot/zImage /home/android/build/lt01-bin/
$ find /home/android/build/lt01/ -type f -name *.ko -exec cp {} /home/android/build/lt01-bin/ \;
Your kernel and all kernel modules ready in /home/android/build/lt01-bin/
{
"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"
}
The resulting kernel also already tested as PhilZ Touch recovery kernel, running on SM-T311 PhilZ Touch repacked from PhilZ Touch recovery for Galaxy Tab 2 10.1 target
Samsung Galaxy Tab 3 8.0 original boot logo:
oc kernel ?? thanks.
Finally a developer with GTab 3 8inch :good: :good:
Can't wait to see a flashable zip and try on my tab
Just got a black screen of death when trying to replace Samsung boot logo Solved: reflash my own param.bin Odin flashable tar.md5
rothshek said:
oc kernel ?? thanks.
Click to expand...
Click to collapse
There's no OC commit: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
Kernel and unofficial PhilZ Touch recovery repack attached at post #1.
Kernel: almost stock, compiled using gcc linaro 4.7, a lot of kernel debugging support disabled, still leave all Samsung kernel spams, restricted root disabled
Ramdisk: self compiled busybox included, auto root, init.d support, flash recovery disabled
Open source, commit history: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
PhilZ Touch repack based on official PhilZ Touch for Tab 2 10.1, thanks @Phil3759
Still in development
Flash the kernel and/or PhilZ Touch using existing CWM/TWRP recovery
Derp!
ketut.kumajaya said:
Kernel and unofficial PhilZ Touch recovery repack attached at post #1.
Kernel: almost stock, compiled using gcc linaro 4.7, a lot of kernel debugging support disabled, still leave all Samsung kernel spams, restricted root disabled
Ramdisk: self compiled busybox included, auto root, init.d support, flash recovery disabled
Open source, commit history: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
PhilZ Touch repack based on official PhilZ Touch for Tab 2 10.1, thanks @Phil3759
Still in development
Flash the kernel and/or PhilZ Touch using existing CWM/TWRP recovery
Click to expand...
Click to collapse
PhilZ Touch runs on T-310? ExFat memory cards supported? There is support for the work of internal memory?
marincax said:
PhilZ Touch runs on T-310? ExFat memory cards supported? There is support for the work of internal memory?
Click to expand...
Click to collapse
I will upload T310 version. T311 version attached at post #1 also work on T310 but every device have a different identity (default.prop). Internal and external memory works, including exFAT support.
I've been disable so much kernel spam but still a lot left flooding the kernel message buffer, just saying
ketut.kumajaya said:
I will upload T310 version. T311 version attached at post #1 also work on T310 but every device have a different identity (default.prop). Internal and external memory works, including exFAT support.
Click to expand...
Click to collapse
Thanks a lot for your reply.:good:
Will be there be enough to replace default.prop in a version for T-311 on default.prop recovery from original T-310?
marincax said:
Thanks a lot for your reply.:good:
Will be there be enough to replace default.prop in a version for T-311 on default.prop recovery from original T-310?
Click to expand...
Click to collapse
Yes, with 2 lines modification:
Code:
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ketut.kumajaya said:
I've been disable so much kernel spam but still a lot left flooding the kernel message buffer, just saying
Click to expand...
Click to collapse
Please leave messages Logcat, kmsg and dmesg. :crying:
Yes, with 2 lines modification:
Code:
ro.debuggable=1
persist.sys.usb.config=mtp,adb
Click to expand...
Click to collapse
Thank you so will I do.
Still changed:
ro.secure=0
ro.adb.secure=0
marincax said:
Please leave messages Logcat, kmsg and dmesg. :crying:
Thank you so will I do.
Click to expand...
Click to collapse
Don't worry, disable the kernel message is really a bad idea :laugh: How about switchable logcat?
ketut.kumajaya said:
Don't worry, disable the kernel message is really a bad idea :laugh: How about switchable logcat?
Click to expand...
Click to collapse
Yes, it will be good. :good:
Hi.! welcome to Suemax kernel thread for marshmallow update
Supported Device N910C/H/U
Change log :
Pure Basic v3.2 TEST Release
1.) Added Fake Enforce option (Magisk only)
2.) SaftyNet workaround and Bypass (Magisk only)
3.) Hide- red seandroid enforcing at boot (ONLY for SuperSU systemless)
Pure Basic v3.1 Last Release
1. Updated Linux Patch to 3.10.105
2. Updated Ramdisks to latest verions
Pure Basic v3.0 Previous
1. SM-N910C_SEA_MM_Opensource_N910CXXS2DPK7
2. Linux version Patched to 3.10.104
3. Updated ramdisks to N910CXXS2DPL8 & N910UXXS2DPL1
4. I/O Schedulers: sio,sioplus,tripndroid,Vr & zen
5. Added UX (Note7) + Stock firmware Support
6. Added CPU
+ALUCARD:
+BIOSHOCK
+INTEREXTREM
+LIONHEART
+CONSERVATIVEX
+IMPULSE
-(Ondemand + Conservative Disabled)
NOTE : Rest of changes Same as v2.0
v.2.0 (new)
1. Fixed private mode (Un-tested)
2. ADB insecure (now work with Android 6)
3. Updated ramdisk script
v1.0b
Has same change log but only compiled at my work station with initial Changes :angel:
v1.0
CPU
a. ) Enabled Ondemand & Conservative governor
b. ) Added Bio-shock governor
c. ) Added Lionheart governor
d. ) Added INTEREXTRE governor
Other Cpu tweaks
a. ) Added Freq relationship C ( For more power saving )
b. ) Tweaked Interactive Cpu governor & More
File-System support
a. ) NTFS
b. ) F2FS
c. ) CIFS
Other Miscellaneous Supported drivers
a. ) MS XPAD game controller support
b. ) ISO & UDF CDROM support
Miscellaneous Support for System
a. ) CLEANCACHE & ZCACHE
Network TCP Ipv4
a. ) enable all TCP Congestion Algorithm in-built - Westwood+ default
SELUNIX : Permissive
Ramdisk-changes
a. ) Added auto-Busybox install (If not there in system xbin)
b. ) Added init.d script (Automatic enable if not in rom )
c. ) Added other tweaks for wifi password save on reboot , Screen Mirror fix and disabled security Tima and Knox
Note : Use kernel Adiutor to control kernel and setting Playstore
Read this F.A.Q
1. Kindly do not ask ETAs & Special requests if asked will be just ignored .
2. Reporting Bugs : Kindly detail your issue with Device(model) Firmware (Stock or custom rom Name) and with possible Logs e.g valid Logcat
3. Kindly Stay on kernel thread topic.!
Version Information
Status: Stable (No Snaypse support)
Current STABLE: v3.0
Android: 6.0.1 (N910CXXU2DPCB)
Kernel Source : https://github.com/djmax81/Suemax-kernel_Exynos5433_BASIC_MM
New
Pure Basic Kernel Source : https://github.com/djmax81/Suemax-kernel_Exynos5433_MM_Plus
Download :
v3.2
Download Pure Basic v3.2-N910C/H
N910U - SOON
v3.1
Download Pure Basic v3.1-N910C/H
Download Pure Basic v3.1-N910U
v3.0
Download Pure Basic v3.0-N910C/H
Download Pure Basic v3.0-N910U
Download Mirror (Android file host Mirror) Thanx @dicksteele
MIUI Support for N910C/H/U (Pure Basic )
v3.1
Download MiUi Pure Basic v3.1-N910C/H
Download MiUi Pure Basic v3.1-N910U
v3.0
Download MiUi Pure Basic v3.0-N910C/H
Download MiUi Pure Basic v3.0-N910U
v2.0
Download v2.0-N910C/H
Download v2.0-N910C/H (Android file host Mirror) Thanx @dicksteele
Download v2.0-N910U
v.1.0b
Download v1.0b-N910C/H
Updated to latest N910UXXU2DPC2 ramdisk
Download v1.0b-N910U
Link N910U Noise fix by not-i : http://forum.xda-developers.com/show....php?t=3228398
SCREENSHOT from v3.2
Reserved
Reserved
Great news. Thank you my friend!
thanks
Goodies coming
Sent from my SM-N910C using XDA Free mobile app
Nice I will test it when get MM update
Thank U!
beefx said:
Nice I will test it when get MM update
Thank U!
Click to expand...
Click to collapse
Thanx and do not forget to bug report if any and I will update thread with detail change log sooon.!!!!! :angel:
just flash via recovery. right ?? i am on mm poland...and i have root and twrp 3.0.2.0
Delfinster said:
just flash via recovery. right ?? i am on mm poland...and i have root and twrp 3.0.2.0
Click to expand...
Click to collapse
Yes .! Flash zip via any custom recovery :good:
djmax81 said:
Yes .! Flash zip via any custom recovery :good:
Click to expand...
Click to collapse
just flashed...everthing is fine for now ,,, i just lost all my wifi passwords but not that big deal
Delfinster said:
just flashed...everthing is fine for now ,,, i just lost all my wifi passwords but not that big deal
Click to expand...
Click to collapse
Reboot device again and Password will be back .!!! + do not forget to flash superSU .zip on top of kernel
That was fast :good:
djmax81 said:
Reboot device again and Password will be back .!!! + do not forget to flash superSU .zip on top of kernel
Click to expand...
Click to collapse
lol..i just see that superSu not working :d i will flash right now thanks for that info
agentdeep said:
That was fast :good:
Click to expand...
Click to collapse
Hahaha.! Yup and you know what Gonna be fast my Next Snaypse supported Version Update :angel:
Delfinster said:
lol..i just see that superSu not working :d i will flash right now thanks for that info
Click to expand...
Click to collapse
Yes .! With new superSU v2.7.1 + Its recommended to Re-Flash SuperSU .zip after any kernel update coz Now on SuperSU do changes to kernel Ramdisk
djmax81 said:
Hahaha.! Yup and you know what Gonna be fast my Next Snaypse supported Version Update :angel:
Click to expand...
Click to collapse
Will flash this and observe for few days :highfive:
Now is all okey and fine ....now testing kernel for couple of days..becose on mm battery is not that good
Downloaded and flashed. Works fine! Only thing, that microsd nightmare still exists, same as on stock kernel. I wonder why TitaniumBackup and many other apps fail to get write write access even with root permission
Sapphire999 said:
Downloaded and flashed. Works fine! Only thing, that microsd nightmare still exists, same as on stock kernel. I wonder why TitaniumBackup and many other apps fail to get write write access even with root permission
Click to expand...
Click to collapse
its know firmware related issue on Stock roms.
you need to add this line to platform.xml
<group gid="sdcard_rw" />
via root Explorer dir System>etc>permission>platform.xml (With text editor)
Reboot device after
But if you got issue with presses then upload platform.xml (i'll edit it for you and all you need to do set permission and reboot or ican make flashable zip)
cheers
WETA Kernel SM-G991U/U1/0 Snapdragon only
*** This will only work on Snapdragon devices with an unlocked bootloader..
SM-G991U/U1 - SM-G9910
Telegram thread linked at bottom
See post #2 for install steps
Changelog...
R5.03
Upstreamed to 5.4.128
Enabled all tcp cong
Westwood tcp default
Disabled unneeded platforms
R5.02
Telegram thread merged into N20.S20 group, check new links.
Upstreamed to 5.4.127
all modules now inlined, no need for magisk helper module.
added wireguard
Power usage tweaks
More
R4.04
Upstreamed to 5.4.123
R4.03
Upstreamed to 5.4.122
R4.02
Upstreamed to 5.4.121
R4.01
Upstreamed to 5.4.120
R4
Testing phase complete
Upstreamed to 5.4.119
R3
Rebased off UAG source code
R2
Upstreamed to 5.4.118
Fixed Torch/Flash
R1
built using CU8 kernel source
Upstreamed to 5.4.117
Fully permissive
KNOX disabled
Wireguard
Misc debugging disabled
Kernel Downloads
Telegram thread
--------------------->
Beer fund
XDA:DevDB Information
Kernel for the Samsung Galaxy S21 Ultra
Contributors
Mentalmuso, mentalmuso
Source Code: - Kernel Source
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R1
Created 2021-05-10
Last Updated 2020-05-10
*** Be aware, there may be a need to wipe data if you desire to go back to stock kernel, my suggestion is to backup your stock BOOT partition and DATA before flashing. This way you can return to your original setup easily. It is unknown at this stage what data is causing an issue going back to stock. If you find it, be sure to share.
* You must have bootloader unlocked and rooted your device with Magisk before flashing this kernel. Magisk is essential for camera and wacom.
* Boot times are approx 60-75sec at the moment, itll sit on the yellow triangle splash for approx 60sec and the bootanimation for 5sec.
* When flashing this kernel, an AnyKernel helper module is installed. This is a Magisk Module that is essential for the operation of Camera and Wacom. Removal of this module while running this kernel will break camera and spen.
* Kernel zip labels have either a P or E in them, P=Fully Permissive, E=Enforcing (switchable)
To install
download and flash the kernel installer zip in TWRP or any custom recovery
--->
mine2
How is it working ?
Hey, any idea if you are going to produce something similar for the exynos version (o1s)?
I have extracted the config from my exynos S21 (https://gist.github.com/wolverine2k/f647be12fbdf95ad8beec416f107772b)
What compiler you used?