• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[KERNEL][SINGLE/DUAL BOOT][JB/KK][STOCK/CM]blackhawk's NEXT kernel 2.4

Search This thread

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
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:

Todo:
  • More features in NEXT tool

Special Thanks:

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
 

Attachments

  • philz_touch_5.05.0-p5100-blackhawk.zip
    8 MB · Views: 4,037
  • philz_touch_5.05.0-p5110-blackhawk.zip
    8 MB · Views: 2,385
  • blackhawk-next-kernel-beta-p51xx.zip
    9.4 MB · Views: 915
  • blackhawk-next-kernel-1.3-p51xx.zip
    9.4 MB · Views: 621
  • blackhawk-next-kernel-1.3-addon-nooc-p51xx.zip
    6.7 MB · Views: 175
  • blackhawk-next-kernel-1.4-p51xx.zip
    8.3 MB · Views: 461
  • blackhawk-next-kernel-1.4-nooc-p51xx.zip
    8.3 MB · Views: 195
  • blackhawk-next-kernel-1.4.1-p51xx.zip
    8.3 MB · Views: 558
  • blackhawk-next-kernel-1.4.1-nooc-p51xx.zip
    8.3 MB · Views: 274
  • blackhawk-next-kernel-1.5-p51xx.zip
    8.3 MB · Views: 350
  • blackhawk-next-kernel-1.5-nooc-p51xx.zip
    8.3 MB · Views: 273
  • blackhawk-next-kernel-1.6.3-p51xx.zip
    8.5 MB · Views: 759
  • blackhawk-next-kernel-1.6.3-nooc-p51xx.zip
    8.5 MB · Views: 286
  • blackhawk-next-kernel-1.8.3-p51xx.zip
    8.5 MB · Views: 3,468
  • blackhawk-next-kernel-1.8.3-nooc-p51xx.zip
    8.5 MB · Views: 1,271
  • blackhawk-next-kernel-2.1.3-p51xx.zip
    7.9 MB · Views: 570
  • blackhawk-next-kernel-2.1.4-p51xx.zip
    7.9 MB · Views: 389
  • blackhawk-next-kernel-2.1.5-p51xx.zip
    6.8 MB · Views: 3,813
  • blackhawk-next-kernel-2.2-p51xx.zip
    7.5 MB · Views: 6,086
Last edited:

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
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:

28/10/2013 2.1.4 -> 2.1.5:

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:

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.
 
Last edited:

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
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.
 

Attachments

  • philz_touch_5.06.1-p5100-blackhawk.zip
    7.9 MB · Views: 5,352
  • philz_touch_5.06.1-p5110-blackhawk.zip
    7.9 MB · Views: 1,466
  • philz_touch_5.08.5-p5100-blackhawk.zip
    7.9 MB · Views: 1,840
  • philz_touch_5.08.5-p5110-blackhawk.zip
    7.9 MB · Views: 2,647
  • philz_touch_5.15.0-p5100-blackhawk.zip
    7.6 MB · Views: 1,832
  • philz_touch_5.15.0-p5110-blackhawk.zip
    7.6 MB · Views: 3,939
Last edited:

ironmaskusa

Senior Member
Jul 25, 2011
525
118
USA
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!:D

Sent from my GT-P5113 using Tapatalk HD
 
  • Like
Reactions: ketut.kumajaya

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
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!:D

Sent from my GT-P5113 using Tapatalk HD
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:

Running smoothly for Zap Blaster. ;)
Really? And all your init.d scripts removed by NEXT ;)
 
  • Like
Reactions: brolee93 and joiN85

shakatu

Senior Member
May 31, 2012
1,168
1,137
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
 
Last edited:

ironmaskusa

Senior Member
Jul 25, 2011
525
118
USA
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

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. ;)
 
  • Like
Reactions: ketut.kumajaya

behemot24

Senior Member
Oct 3, 2010
410
102
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 :cowboy:
 
  • Like
Reactions: ketut.kumajaya

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
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 :cowboy:
For free ;) A lot of clicks to install NEXT package but why people missed to click my Thanks button :p

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 :D
 
Last edited:

Rahul721

Senior Member
Feb 10, 2013
267
110
23
When i install this kernel on ZapBlaster the Video Player and Camera stops working :(

Sent from my GT-P5113 using xda premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 69
    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:

    Todo:
    • More features in NEXT tool

    Special Thanks:

    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
    25
    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:

    28/10/2013 2.1.4 -> 2.1.5:

    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:

    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.
    20
    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.
    14
    *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
    NEXT Kernel 2.1.6.2
    *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-


    STOP! This kernel supports ONLY
    • Samsung Stock / Stock-based Jelly Bean 4.1.x Roms
    • Samsung Stock / Stock-based Jelly Bean 4.2.2 Roms
    • Different Custom:
      • Android 4.2.2 Roms (e.g. CM 10.1)
      • Android 4.3.x Roms (e.g. CM 10.2, SlimBean)
      • Android 4.4.x Roms (e.g. SlimKat, OmniRom, CM 11, MoKee, PAC-Man-Rom)
    • It won't work on ICS, CM 9, CM 10!!!


    IMPORTANT NOTES
    • For Stock Android 4.1.x Roms flash "proprietary-vendor-samsung-4.1.x.zip" DIRECTLY after NEXT 2.1.6 Kernel!
    • For all other Roms flash "proprietary-vendor-samsung.zip" DIRECTLY after NEXT 2.1.6 Kernel!
    • (maybe no need on latest Android 4.4.2 Roms, since they have updated vendor-blobs)
    Without that you´ll get bootloop or not working cameras!
    Found those files attached here: http://forum.xda-developers.com/showpost.php?p=41583854&postcount=2


    Dual-Boot
    To get Dual-Boot support you need a Special PhilZ Touch Blackhawk Repack! Files attached!
    You also need latest NEXT-Tool: blackhawk-next-tool-0.1.zip

    How to setup Dual-Boot?
    Read FAQ: http://forum.xda-developers.com/showpost.php?p=41583865&postcount=3


    Special-Credits:
    Thanks @ketut.kumajaya for supporting and helping me and also for permissions to repack NEXT Kernel to get Android 4.4.X Dual-Boot-Support (also great Kernel on Sinlge-Boot) - i know i am not easy all the time, but we got it work :D :)
    Thanks @Phil3759 for his great PhilZ Touch Recovery
    Thanks @tetakpatak for testing NEXT 2.1.6 and PhilZ Touch Repack for me - hard work, lot hours of testing and flashing - and now your Tab is "18" again ;) (flash-counter)
    Thanks @freinet for testing too
    Thanks @ everyone i forgot ... i am tired right now :D


    About:
    NEXT Kernel 2.1.6 : Modified NEXT 2.1.5 Kernel, added Android 4.4.X support
    PhilZ Touch 6.12.8-Blackhawk-Repack: Modified PhilZ Touch Recovery from @Phil3759, using recovery-kernel from "philz_touch_5.15.0-p51XX-blackhawk.zip" and modified to add dual-boot support


    Great news:
    Ketut • 23. Feb. 04:28
    You got my permission and "officially" supported by me

    Changes:
    2.1.6 --> 2.1.6.2
    Updated CM 11 Support (it was broken on 03.03.2014 CM nightly)
    Added PAC-Man-ROM Android 4.4.2 Support

    2.1.5 --> 2.1.6
    Added Android 4.4.x Support



    Disclaimer
    I don´t own a P51XX and can not test myself (sometimes flashing P51XX things on my P3110 but screen messed up and touch not working - lol :D ) - Use on your own risk! I am not responsible for bricked devices or dead SD cards!
    13
    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 :cowboy:
    For free ;) A lot of clicks to install NEXT package but why people missed to click my Thanks button :p

    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 :D