5,815,133 Members 38,878 Now Online
XDA Developers Android and Mobile Development Forum

[KERNEL][SM-T31x][SINGLE/DUAL][STOCK/CM] blackhawk's NEXT kernel 2.4

Tip us?
 
ketut.kumajaya
Old
(Last edited by ketut.kumajaya; 11th July 2014 at 10:17 AM.)
#1  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
Default [KERNEL][SM-T31x][SINGLE/DUAL][STOCK/CM] blackhawk's NEXT kernel 2.4

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_...2/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_...ommits/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/devd...5210#downloads

Todo:
  • Dual boot

Special Thanks:
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
Attached Files
File Type: zip mali-400-r3p1-01rel1-blobs-t31x.zip - [Click for QR Code] (762.0 KB, 163 views)
File Type: zip mali-400-r3p2-01rel3-blobs-t31x.zip - [Click for QR Code] (798.4 KB, 824 views)
File Type: zip blackhawk-next-kernel-1.3-t311.zip - [Click for QR Code] (6.72 MB, 335 views)
File Type: zip blackhawk-next-kernel-1.3-t310.zip - [Click for QR Code] (6.68 MB, 295 views)
File Type: zip blackhawk-next-kernel-1.3-t315.zip - [Click for QR Code] (6.77 MB, 70 views)
File Type: zip blackhawk-next-kernel-1.4-t310.zip - [Click for QR Code] (6.68 MB, 848 views)
File Type: zip blackhawk-next-kernel-1.4-t311.zip - [Click for QR Code] (6.72 MB, 481 views)
File Type: zip blackhawk-next-kernel-1.4-t315.zip - [Click for QR Code] (6.76 MB, 145 views)
File Type: zip blackhawk-next-kernel-1.5-t311.zip - [Click for QR Code] (6.84 MB, 83 views)
File Type: zip blackhawk-next-kernel-1.5-t310.zip - [Click for QR Code] (6.80 MB, 120 views)
File Type: zip blackhawk-next-kernel-1.5-t315.zip - [Click for QR Code] (6.90 MB, 24 views)
File Type: zip mali-400-r3p1-01rel1-repack-t31x.zip - [Click for QR Code] (769.0 KB, 38 views)
File Type: zip mali-400-r3p2-01rel3-repack-t31x.zip - [Click for QR Code] (805.4 KB, 248 views)
File Type: zip blackhawk-next-kernel-1.6-t310.zip - [Click for QR Code] (6.83 MB, 167 views)
File Type: zip blackhawk-next-kernel-1.6-t311.zip - [Click for QR Code] (6.87 MB, 144 views)
File Type: zip blackhawk-next-kernel-1.6-t315.zip - [Click for QR Code] (6.92 MB, 74 views)
File Type: zip blackhawk-next-kernel-1.7-t310.zip - [Click for QR Code] (6.88 MB, 324 views)
File Type: zip blackhawk-next-kernel-1.7-t311.zip - [Click for QR Code] (6.92 MB, 325 views)
File Type: zip blackhawk-next-kernel-1.7-t315.zip - [Click for QR Code] (6.98 MB, 146 views)
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating
The Following 44 Users Say Thank You to ketut.kumajaya For This Useful Post: [ Click to Expand ]
 
ketut.kumajaya
Old
(Last edited by ketut.kumajaya; 27th August 2014 at 06:10 PM.)
#2  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
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_...ommits/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_...ommits/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:
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!
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating
The Following 19 Users Say Thank You to ketut.kumajaya For This Useful Post: [ Click to Expand ]
 
ketut.kumajaya
Old
(Last edited by ketut.kumajaya; 3rd April 2014 at 10:16 AM.)
#3  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
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/show...7&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.
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating
The Following 10 Users Say Thank You to ketut.kumajaya For This Useful Post: [ Click to Expand ]
 
ketut.kumajaya
Old
(Last edited by ketut.kumajaya; 25th November 2013 at 08:56 AM.)
#4  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
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/recept...chValue=sm-t31
Samsung OSRC exFAT source: http://opensource.samsung.com/recept...rchValue=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
  1. Clone kernel source repo:
    Code:
    $ cd /home/android/
    $ git clone git://github.com/kumajaya/android_kernel_samsung_lt01.git
  2. 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
  3. 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
  4. 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/

Attached Thumbnails
Click image for larger version

Name:	Screenshot_2013-11-12-07-13-21.png
Views:	27670
Size:	151.7 KB
ID:	2386782  
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating
The Following 4 Users Say Thank You to ketut.kumajaya For This Useful Post: [ Click to Expand ]
 
ketut.kumajaya
Old
(Last edited by ketut.kumajaya; 11th November 2013 at 10:25 AM.)
#5  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
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

Attached Thumbnails
Click image for larger version

Name:	fbdump.png
Views:	27472
Size:	250.4 KB
ID:	2385344  
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating
The Following 4 Users Say Thank You to ketut.kumajaya For This Useful Post: [ Click to Expand ]
 
ketut.kumajaya
Old
#6  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
Samsung Galaxy Tab 3 8.0 original boot logo:

Attached Thumbnails
Click image for larger version

Name:	logo.jpg
Views:	27206
Size:	53.9 KB
ID:	2386977  
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating
The Following User Says Thank You to ketut.kumajaya For This Useful Post: [ Click to Expand ]
 
rothshek
Old
#7  
Member
Thanks Meter 2
Posts: 44
Join Date: Mar 2011
oc kernel ?? thanks.
 
adrian13th
Old
#8  
adrian13th's Avatar
Senior Member
Thanks Meter 266
Posts: 236
Join Date: Oct 2012
Location: West Sumatra
Finally a developer with GTab 3 8inch
Can't wait to see a flashable zip and try on my tab
 
ketut.kumajaya
Old
#9  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
Just got a black screen of death when trying to replace Samsung boot logo Solved: reflash my own param.bin Odin flashable tar.md5
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating
 
ketut.kumajaya
Old
#10  
Recognized Developer - OP
Thanks Meter 9,241
Posts: 3,477
Join Date: Apr 2011
Location: Bekasi

 
DONATE TO ME
Quote:
Originally Posted by rothshek View Post
oc kernel ?? thanks.
There's no OC commit: https://github.com/kumajaya/android_...commits/master
 
A proud owner
P31xx kernel | P51xx kernel | T31x kernel
for stock/stock based ROM
for CM/CM based ROM
for DUAL BOOT
If you like my work, please consider donating

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes