Related
---[ UPDATED: July 26, 2011 16:30 GMT ]---
\\--[ ANNOUNCEMENT ]--//
[Added] FreeKernel-mod350-Th#28 by ThJap
//--[ ANNOUNCEMENT ]--\\
I have started this thread based on zdzihu's suggestion...
This thread is intended for Developers ONLY...
A method of booting custom kernels (using kexec) has been developed. Thanks Bin4ry, zdzihu, jerpelea, MrHassell, blagus, and all other devs who are working hard to make this stable. (i am sorry if i missed any names)
hope the devs can use this thread to discuss on custom kernel dev....
please keep this thread clean for the devs to discuss the kernel development aspects...
for general discussions please use the following thread:
http://forum.xda-developers.com/showthread.php?t=1018391
i will also keep updating this regularly with the information like relevant posts; features, limitations & links to custom kernels currently available...
*** [IMP]: before flashing custom update.zips read this: how to find the version/type of recovery on ur current ROM ***
>>> How-To for testing custom kernel <<<
>>> How to build a Linux kernel and flash it to the phone {from SE Dev Blog} <<<
Custom kernel sources released:
Custom Kernel Sources for 2.0.A.0.504 by zdzihu
FreeXperia Project | Custom Kernel Sources for FreeXperia Kernel
FreeKernel-mod350-source by tkymgr
FreeKernel-mod352-source by tkymgr
zKernel-source by zdzihu
DooMKernel-source by DooMLoRD
Current list of custom kernels:
FreeKernel-alpha1 by zdzihu
FreeKernel-alpha1-in-call volume fix by zdzihu
FreeXperia Kernel-001 by jerpelea (from CM7.0 RC4 v014 k001 PREVIEW)
FreeXperia Kernel-002 by jerpelea (from CM7.0.0 J015 k002)
TripNKernel Modified FreeKernel-03 by TripNRaVeR
FreeXperia Kernel-003 / beta3 by Bin4ry (flashable update.zip via recovery)
FreeXperia Kernel beta4 by Bin4ry
FreeXperia Kernel-005 / beta5 by jerpelea (from CM7.0.0 J016 k005)
FreeXperia Kernel-006 / beta6 by jerpelea (from CM7.0.0 J016a k006)
FreeXperia Kernel-007 / beta7 by jerpelea (from CM7.0.3 J019 k007)
FreeXperia Kernel-008 / beta8 by jerpelea (from CM7.0.3 J020 k008)
FreeXperia Kernel-009 / beta9 by jerpelea (from CM7.0.3 J020a k009)
FreeXperia Kernel-010 / beta10 by jerpelea (from CM7.0.3 J020b k010)
FreeXperia Kernel-010 / beta10 [No UV] by jerpelea (from CM7.0.3 J020c K010)
FreeXperia Kernel-011 / beta11 by jerpelea (from CM7.0.3 FINAL J021 K011 & CM7.1.0 J001 K011)
FreeXperia Kernel-012 / beta12 by jerpelea
FreeKernel-docomo21.c-spec-v346 by tkymgr
FreeKernel-docomo2x.c-spec-v347 by tkymgr
FreeKernel-docomo2x.c-spec-v349 by tkymgr
FreeKernel-docomo2x.c-spec-v350 by tkymgr
FreeKernel-mod350-fix1 by tkymgr [ only boot.img & wifi module ]
FreeKernel-mod351 by tkymgr
FreeKernel-mod352 by tkymgr
zKernel-22062011 by zdzihu
zKernel-23062011-alt by zdzihu
FreeXperia Kernel-013 / beta13 by jerpelea (from CM7.1.0 RC1 J005 k013)
FreeKernel-mod352 #2 by tkymgr
FreeKernel-mod350-Th#11 by ThJap
zKernel-05072011 by zdzihu
FreeKernel-mod360 by tkymgr
zKernel-14072011 by zdzihu
zKernel-15072011 beta by zdzihu
DooMKernel v01 by DooMLoRD
DooMKernel v02 by DooMLoRD
zKernel-20072011 by zdzihu
zKernel-20072011_failsafe by zdzihu
FreeKernel-mod350-Th#25 by ThJap
FreeKernel-mod362 by tkymgr
DooMKernel v03 by DooMLoRD
FreeKernel-mod363 by tkymgr
FreeKernel-mod350-Th#28 by ThJap
Additional Info:
the following files are required in the /system/kernel/ folder:
splboot.ko (some devs move this file to /system/lib/modules/splboot.ko)
miniloader
boot.img (this is the actual custom kernel)
for booting the OS using custom kernel some modifications are required to the /system/bin/chargemon file
also some modified/updated modules (e.g. wifi.ko) are provided for compatibility with the custom kernel
Bootloader Bypass files:
There seems to be some issues face by some users, where in using a different version of miniloader helped them sort out the issues. So I will provide all those versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [slightly older miniloader] {came with older FreeXperiaKernels}
bootloader_bypass_files_v2.zip [older miniloader] (testing only) {came with FreeKernel by zdzihu}
bootloader_bypass_files_v3.zip [older miniloader] (testing only) {came with Flashtool v0.2.9.1}
bootloader_bypass_files_v4.zip [newest miniloader] {comes with newer FreeXperiaKernels (from CM7 J022 K011 onwards)} (recommended)
[IMP] for v4 miniloader: u need to be on the baseband from the baseband package provided in CM7 J022 for the v4 miniloader to work properly... even if u already have baseband 2.0.52 please reflash using the baseband package provided in CM7 J022... even if u are on a different ROM u will need to use the baseband from the above package to get custom kernel to work properly
FreeKernel-alpha1 by zdzihu
Linux Kernel Version:
2.6.29
Kernel features:
removed 32 fps cap
implemented netfilter (Droid wall, native USB/wifi tethering etc.)
undervolted to 0.950mV to save battery
don't remember what else I did, I bet something nasty
super ugly boot logo!
Requirements:
baseband .52 + the relevant kernel
clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
working xRecovery
Known Issues:
Tested On:
Stock SE Firmware 2.0.A.0.504
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?1gesziiz4pbvcr6
MD5 hash of boot.img:
Code:
d8e98b647641bc55270ccb73729f007f
Additional file(s) provided with kernel:
wifi.ko module
FreeKernel-alpha1 in-call volume fix by zdzihu
Linux Kernel Version:
2.6.29
Kernel features:
possible in-call volume fix
removed 32 fps cap
implemented netfilter (Droid wall, native USB/wifi tethering etc.)
undervolted to 0.950mV to save battery
don't remember what else I did, I bet something nasty
super ugly boot logo!
Requirements:
baseband .52 + the relevant kernel
clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
working xRecovery
Known Issues:
Tested On:
Stock SE Firmware 2.0.A.0.504
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?jx4lbhfioquw4sk
MD5 hash of boot.img:
Code:
5de24423ad2ccce80bbd5ac9aae3079a
Additional file(s) provided with kernel:
wifi.ko module
FreeXperia Kernel-001 by jerpelea (from CM7.0 RC4 v014 k001 PREVIEW)
Linux Kernel Version:
2.6.29
Kernel features:
tun/tap
dmmod
dmcrypt
1.1 ghz frequency
undervolt
ondemand cpu scaller (default)
camera debug messages
netfilter
Requirements:
baseband 2.0.52
Known Issues:
wifi doesnt work. enabling/activating wifi causes WLOD (white LED of Death) and then reboot
Tested On:
Cyanogen CM7.0 RC4 v014 k001 PREVIEW
Wolfbreaks CM6.1.3 v53 with Baseband Patch for 4x-52
TripNMiUI
FreeX10 beta4 hotfix1
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?8uzo3nudxh89x67
MD5 hash of boot.img:
Code:
fcacdb0189ca25b7c834a4a855f1776e
Additional file(s) provided with kernel:
kernel part of custom ROM
Bootloader bypass file(s) required to test custom kernel:
There seems to be some issues face by some users, where in using an older version of miniloader helped them sort out the issues. So I will provide here both versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [newest miniloader] (recommended)
bootloader_bypass_files_v2.zip [older miniloader] (testing only)
One question for bypass-method developers: is it necessary to have stock SE's ROM for better chances of succeeding in porting splboot/miniloader to X8?
2.1update1 - base anyone can restore with SEUS, demonstrated work from this point, with the FreeX10, FreeXperia, Wolfbreak, rendeiro2005 and others without many problems. It might be a case of, which has the least issues, what are they and how do we eliminate them.
The most common baseband with development is 52. FreeXperia - CM7 GingerBread - entirely developed for 52 - there are two groups.
Original Baseband series: 48-49-50-51-52 (52 = last of first generation)
Current Baseband series: 53-54-55-56-57-58 (59 - not released)
Baseband is a multiplexer. The core C files are - vendor/qcom-proprietary-qsd8k/data/qmi/qmuxd/../src/qmi_qmux.c and is compiled for ARM with* vendor/qcom-proprietary-qsd8k/data/qmi/qmuxd/../platform/qmi_platform_qmux_io.c and the core interface to the Linux kernel - vendor/qcom-proprietary-qsd8k/data/qmi/qmuxd/../platform/linux_qmi_qmux_if_server.c requires several SO - (ELF binaries) - be present, compiled and available to the kernel and the linker - /system/bin/linker
liblog.so
libdiag.so
libc.so
libstdc++.so
libm.so
Everything working - /data/radio/qmux_connect_socket - will bind to an address path and make possible, one radio with one input signal to many data-output-lines and many input lines. Herein the core networking is established, with WiFi and Bluetooth become linked, with the famous exploits for NULL pointer dereference vulnerability which exist in Linux kernels < .30 - Which is no coincidence, why many Kernels are below this release version.
sent from neptune
Achotjan_FreeX10 by achotjan
based on FreeKernel-alpha1 by zdzihu
---[ REMOVED ON DEVS REQUEST ]---
FreeXperia Kernel-002 by jerpelea (from CM7.0.0 J015 k002)
Linux Kernel Version:
2.6.29
Kernel features:
possible in-call volume fix
gps fix
lcd backlight resume fix
tun/tap
dmmod
dmcrypt
1.1 ghz frequency
undervolt
ondemand cpu scaller (default)
camera debug messages
netfilter
Requirements:
baseband 2.0.52
Known Issues:
wifi doesnt work
Tested On:
Cyanogen CM7.0.0 J015 k002
Wolfbreaks CM6.1.3 v53 with Baseband Patch for 4x-52
TripNMiUI FINAL 1.0.3
FreeX10 beta4 hotfix1
MiXeD MIUI 002 TMR mod
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?5egorvjv1lppno2
MD5 hash of boot.img:
Code:
25cb217886b88ba1085dfd164c8a3e8d
Additional file(s) provided with kernel:
kernel part of custom ROM
Bootloader bypass file(s) required to test custom kernel:
There seems to be some issues face by some users, where in using an older version of miniloader helped them sort out the issues. So I will provide here both versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [newest miniloader] (recommended)
bootloader_bypass_files_v2.zip [older miniloader] (testing only)
TripNKernel Modified FreeKernel-03
based on zdzihu's FreeKernel
Linux Kernel Version:
2.6.29
Kernel features:
removed 32 fps cap
Requirements:
baseband 2.0.49/2.0.52
Known Issues:
GPS (not confirmed)
apps2sd not working
Tested On:
TripNMiUI FINAL 1.0.3
Wolfbreaks CM6.1.3 with Baseband Patch for 4x-52
FreeX10 beta4 hotfix1
Achotjan_Froyo_2.2.1
scamble_v01.3 CM6.1.3
Link to download boot.img (flashable via recovery):
http://www.mediafire.com/?4mscmhfbr99hdt9
MD5 hash of boot.img:
Code:
aa40c889f482731eb4324e0c2a2b5336
Additional file(s) provided with kernel:
kernel part of custom ROM
Bootloader bypass file(s) required to test custom kernel:
There seems to be some issues face by some users, where in using an older version of miniloader helped them sort out the issues. So I will provide here both versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [newest miniloader] (recommended)
bootloader_bypass_files_v2.zip [older miniloader] (testing only)
how can we flash the .img file?
AN7 OverClocker said:
how can we flash the .img file?
Click to expand...
Click to collapse
A little more info please, wich kernel are you talking about? Tripnraver's, zdzihu's..?
If it's tripnraver's kernel you try to flash, you should just flash the zip-package you downloaded
i am talking about FreeXperia Kernel-002 by j.
This kernel is only available on .img file
You should place all your kernel files in /system/kernel/ and you must make some changes to chargemon (/system/bin/chargemon). I have no idea what changes you should exactly make..
hmmm...
i will re-upload the boot.img zips as update.zips flashable via recovery...
also for general discussions please use the following thread: http://forum.xda-developers.com/showthread.php?t=1018391
in the above thread i have already posted the changes which need to be made to the /system/bin/chargemon file to boot using custom kernels
system/bin/chargemon
system/bin/charger
system/lib/modules/wifi.ko
and Kernel folder needs to be copied out from ROMs to get custom Kernel.
Wolfbreak said:
system/bin/chargemon
system/bin/charger
system/lib/modules/wifi.ko
and Kernel folder needs to be copied out from ROMs to get custom Kernel.
Click to expand...
Click to collapse
i would not recommend copying the file /system/bin/chargemon as is (because of the different recoveries available & variations that each dev/each version of flashtool introduces) rather only search for the custom kernel booting part and add that to the chargemon file if it isnt there already...
also no need to copy the whole /system/kernel/ folder... u just need the boot.img for that specific custom kernel... (though here i assume that u already have miniloader & splboot.ko in /system/kernel/)
and yes individual rewritten modules (like wifi.ko) have to be copied too... it would be great if the devs can post update.zips which contain the hotfixes/addons (including custom kernel, modified modules, etc) so that the kernel and related files can be used on other roms too, instead of downloading the whole rom...
i would like to confirm that FreeXperia Kernel-002 by jerpelea (from CM7.0.0 J015 k002) is working well on Achotjan's V010
Has anyone tested one of the available kernels on FreeX10 Beta 4 ?
[Q] Is it also possible for x10?
Hi, I just found this:
http://forum.xda-developers.com/showthread.php?t=889503
So i wanted to ask wether it is possible to implement it in the custom Kernels of X10.
fknpwned said:
Has anyone tested one of the available kernels on FreeX10 Beta 4 ?
Click to expand...
Click to collapse
+1
sent from my Z orignal and modded 2.2 powered c64
DISCLAIMER: I own Xperia X10, Xperia J, Xperia Tipo, Xperia S and Xperia V, releases of all other phones are not personally tested by me. But since the kernel is the same in FXP/KXP ROMs I presume they would not harm your device in any way
Huge props go to all TeamWIn people like Dees_Troy and bigbiff and everyone else for developing this awesome recovery and lots of thanks to FreeXperia Team (FXP, Kali-, codeworkx, bin4ry,) for maintaining device configs for Xperias
This recovery is embedded into the ramdisk of a normal AOKP 4.1.2 bootimage. The kernels are same as the latest AOKP released by KXP team. These kernels should work with FXP's CM10, and other ROM's based of it (KXP ROM, Pac-man, officialCM10 etc). These kernels will not work on stock/cm7/cm9/blah/blah/any other ROM.
INSTRUCTIONS :
1. Download the zip file for your device (twrp2.4.3-xxxxx.zip)
2. Extract the boot.img from zip on your PC, and copy the whole zip file on device's SDcard.
3. Fastboot the kernel using the terminal command
Code:
fastboot flash boot boot.img
4. To enter recovery, when LED is pink press {vol up for 2012 models} or {vol down for 2011 models}
5. Flash zip that you kept in sdcard from recovery (wifi/OTG/etc will not work without proper modules flashed).
6. Enjoy
DOWNLOADS:
Mirror1 |or| Mirror2
download according to your device name in this list
Code:
[LIST]
[*]anzu Arc/ArcS
[*]aoba ION
[*]coconut Live with WALKMAN
[*]haida Neo V
[*]hallon Neo
[*]hayabusa TX
[*]hikari Acro S
[*]jlo J
[*]iyokan Pro
[*]mango MiniPro
[*]mesona Miro
[*]mint T
[*]nozomi S/SL
[*]satsuma Active
[*]smultron Mini
[*]tapioca Tipo
[*]tsubasa V
[*]urushi Ray
[*]zeus Play
[*]zeusc Play CDMA
[/LIST]
CHANGELOG :
All official changes to TWRP is found on http://teamw.in
Code:
=============twrp 2.4.3
code updated to oficial twrp 2.4.3.0
new device J, Tipo, Miro supported
=============twrp2.4
code updated to official twrp 2.4.1.0
fixed "/boot not found" error on 2011 phones
=============twrp 2.3
official twrp 2.3 sources
first release
=======================================================================================
for advanced users/devs/modders/porters
=======================================================================================
SOURCES:
The kernels present inside the bootimages are compiled from these sources
https://github.com/KangXperiaProject/android_kernel_sony_msm7x27a (for Tipo, J, Miro)
https://github.com/KangXperiaProject/android_kernel_sony_msm8x60 (for S,Ion,AcroS, T, V, TX)
https://github.com/KangXperiaProject/android_kernel_semc_msm7x30 (for all 2011 model phones)
The device configs are found on
https://github.com/KangXperiaProject/android_device_semc_<yourdevicename> (for all 2011 model phones)
https://github.com/KangXperiaProject/android_device_sony_<yourdevicename> (for all 2012 model phones)
you can also see our merged commits to see the precise patch we applied on each repository to be able to build TWRP
http://smartdev.com.pl:8080/#/q/status:merged,n,z
BUILD FROM SOURCE
To build TWRP for your Xperia,
1. merge the patch to enable TWRP on your own device tree (for eg. http://smartdev.com.pl:8080/#/c/239/ for Xperia T)
2. replace /bootable/recovery folder with TWRP (as mentioned here http://forum.xda-developers.com/showthread.php?t=2069242)
3. If your build folder is not from CM, switch to CM's build folder (i.e the android_build repo)
4. lunch ; mka bootimage;
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
============================================================================================
BUGS AND SUPPORT
If you have any problem with this please please please post only on this thread, not on any other thread or not on PM.
Please send me the recovery log wherever possible, and also kmsg/dmesg if you can.
If you need assistance porting TWRP to your kernel, or building from source[only for Xperia phones that I have provided builds for], then also you can post here.
DISCLAIMER: I own Xperia X10, Xperia J, Xperia Tipo, Xperia S and Xperia V, releases of all other phones are not personally tested by me. But since the kernel is the same in FXP/KXP ROMs I presume they would not harm your device in any way
Huge props go to all TeamWIn people like Dees_Troy and bigbiff and everyone else for developing this awesome recovery and lots of thanks to FreeXperia Team (FXP, Kali-, codeworkx, bin4ry,) for maintaining device configs for Xperias
This recovery is embedded into the ramdisk of a normal AOKP 4.1.2 bootimage. The kernels are same as the latest AOKP released by KXP team. These kernels should work with FXP's CM10, and other ROM's based of it (KXP ROM, Pac-man, officialCM10 etc). These kernels will not work on stock/cm7/cm9/blah/blah/any other ROM.
INSTRUCTIONS :
1. Download the zip file for your device (twrp2.4.3-xxxxx.zip)
2. Extract the boot.img from zip on your PC, and copy the whole zip file on device's SDcard.
3. Fastboot the kernel using the terminal command
Code:
fastboot flash boot boot.img
4. To enter recovery, when LED is pink press {vol up for 2012 models} or {vol down for 2011 models}
5. Flash zip that you kept in sdcard from recovery (wifi/OTG/etc will not work without proper modules flashed).
6. Enjoy
DOWNLOADS:
Mirror1 |or| Mirror2
download according to your device name in this list
Code:
[LIST]
[*]anzu Arc/ArcS
[*]aoba ION
[*]coconut Live with WALKMAN
[*]haida Neo V
[*]hallon Neo
[*]hayabusa TX
[*]hikari Acro S
[*]jlo J
[*]iyokan Pro
[*]mango MiniPro
[*]mesona Miro
[*]mint T
[*]nozomi S/SL
[*]satsuma Active
[*]smultron Mini
[*]tapioca Tipo
[*]tsubasa V
[*]urushi Ray
[*]zeus Play
[*]zeusc Play CDMA
[/LIST]
CHANGELOG :
All official changes to TWRP is found on http://teamw.in
Code:
=============twrp 2.4.3
code updated to oficial twrp 2.4.3.0
new device J, Tipo, Miro supported
=============twrp2.4
code updated to official twrp 2.4.1.0
fixed "/boot not found" error on 2011 phones
=============twrp 2.3
official twrp 2.3 sources
first release
=======================================================================================
for advanced users/devs/modders/porters
=======================================================================================
SOURCES:
The kernels present inside the bootimages are compiled from these sources
https://github.com/KangXperiaProject/android_kernel_sony_msm7x27a (for Tipo, J, Miro)
https://github.com/KangXperiaProject/android_kernel_sony_msm8x60 (for S,Ion,AcroS, T, V, TX)
https://github.com/KangXperiaProject/android_kernel_semc_msm7x30 (for all 2011 model phones)
The device configs are found on
https://github.com/KangXperiaProject/android_device_semc_<yourdevicename> (for all 2011 model phones)
https://github.com/KangXperiaProject/android_device_sony_<yourdevicename> (for all 2012 model phones)
you can also see our merged commits to see the precise patch we applied on each repository to be able to build TWRP
http://smartdev.com.pl:8080/#/q/status:merged,n,z
BUILD FROM SOURCE
To build TWRP for your Xperia,
1. merge the patch to enable TWRP on your own device tree (for eg. http://smartdev.com.pl:8080/#/c/239/ for Xperia T)
2. replace /bootable/recovery folder with TWRP (as mentioned here http://forum.xda-developers.com/showthread.php?t=2069242)
3. If your build folder is not from CM, switch to CM's build folder (i.e the android_build repo)
4. lunch ; mka bootimage;
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
============================================================================================
BUGS AND SUPPORT
If you have any problem with this please please please post only on this thread, not on any other thread or not on PM.
Please send me the recovery log wherever possible, and also kmsg/dmesg if you can.
If you need assistance porting TWRP to your kernel, or building from source[only for Xperia phones that I have provided builds for], then also you can post here.
screenshots?
TDH Kernel for the Moto X Unified (CAF)
The kernel is that which manages the phone at a fundamental level. To learn more, see the "Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel."
How I Support This Work:
Donations always work
Thanks buttons also work wonders. Don't forget to hit the Thanks button for those whose work benefits you.
If I don't respond to a question, there is a very high likelihood the answer already exists in this thread -- use search as I rarely forget what's already covered.
Working Features:
AOSP
Best battery life (kernel installs init.d script to setup SmartMax governor)
Governors: SmartMax, Intelliactive, interactive, ondemand, userspace, powersave, performance (more coming if relevant -- 'marketing checkmarks' -- a.k.a. useless but stuck in just for feature count -- won't get into this kernel)
Optional IOSched: Noop, Deadline, CFQ, BFQ, FIOPS, SIO (more coming if relevant -- same comment applies as for Governors)
Optional GPU Governors= Performance, Ondemand, Simple, Interactive
User voltage control
Kexec support
Initial Kexec support
ExFAT support
KSM optimizations
Enhanced NEON support
Reduce kswapd schedule enhancement
EXT4 file system speed ehancements
Many stability and optimizations upgrades.
In progress / futures (not stable yet) ...
Overclocking/underclocking options (in progress ... sigh , coming soon)...
Optional GPU overclocking
Doubletap2wake
Logo2wake
Pocket detection
Logo2menu.
Credits go to many, but most particularly:
Linus Torvalds (for Linux itself)
Flar2
Faux123
ThickLizard
TBaldin
A lot of other kernel devs whose code I read regularly to learn
All the Moto X Community
Instructions:
READ THE DISCLAIMER.
Download the kernel
Reboot into Recovery
Nandroid backup
Flash the kernel
Enjoy
Things to Know:
The flash uses standard 'by-name' partitions, so should install correctly on most AOSP based ROMs
The flash supports the CM11 standard /data/local/userinit.d init script (99-tdhk)
That script will delay one minute after boot and force the SmartMax governor on all cores
FIOS is the default IO scheduler
No need for Trickster or Performance Settings if you want those defaults (which you should)
KERNEL SOURCE
Enjoy.
XDA:DevDB Information
TDHK, Kernel for the Moto X
Contributors
tdhite, skiwong20
Source Code: https://github.com/tdhite/android_kernel_motorola_msm8960dt-common
Kernel Special Features: Governors, schedulers, sleep/wake options, battery tweaks, performance tweaks.
Version Information
Status: Stable
Current Stable Version: KitKit: 12/21/2014;
Stable Release Date: 2015-09-20
Created 2014-07-19
Last Updated 2015-09-20
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use any of the software provided by this thread, or convey such software to
someone else, you and all subsequent conveyees are bound by the following:
# LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
# Assumption of the Risk of Use
# YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS
# PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY,
# IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY
# MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE
# ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE
# RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT
# TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
#Disclaimer of Warranty.
# THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
# LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
# OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND,
# EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
# THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
# YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND
# AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR
# EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR,
# CORRECTION OR OTHERWISE.
#Limitation of Liability.
# IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
# ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
# PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE
# RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
# ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
# LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
# BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
# PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGES.
Downloads
KERNELS (Current):
Download: TDHK-Ghost Lollipop 09-20-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost KitKat 12-21-2014
This kernel is for KitKat AOSP ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-MotoX 08-31-2014
This kernel is for ROMs *before* the unified 'ghost' model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'msm8960dt' AOSP rom -- of course read the DISCLAIMER post.
IMPORTANT:
If you wipe Dalvik Cache, let the phone boot completely once, then reboot again (long story, but AOSP roms set a property on Android that triggers your selected 'performance' settings (e.g., performance, balanced, whatever), when you clear Dalvik that property set trigger runs rather late and the init.d script delay setup by this kernel to force smartmax onto the CPU cores might already have happened, so you end up with the old governors (ick!). Reboot and all should be fine.
Another option is to open a terminal window and 'su' to root privileges, then type "set prop sys.perf.profile 99". No need to reboot if you do this.
OLD Releases:
Download: TDHK-Ghost Lollipop 09-17-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
B]Download: TDHK-Ghost Lollipop 08-07-2015[/B]
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 07-20-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 06-28-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 05-24-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 04-06-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 01-11-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.3.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 12-21-2014
This kernel is for LolliPop AOSP ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-26-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-16-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-05-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 09-20-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
KERNEL (Enhanced -- no longer needed as integrated into standard kernel):
Download: TDHK-MotoX 08-10-2014
KERNEL):
Download: TDHK-MotoX 07-28-2014
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any AOSP rom -- of course read the DISCLAIMER post.
IMPORTANT!!!
If you wipe Dalvik Cache, let the phone boot completely once, then reboot again (long story, but AOSP roms set a property on Android that triggers your selected 'performance' settings (e.g., performance, balanced, whatever), when you clear Dalvik that property set trigger runs rather late and the init.d script delay setup by this kernel to force smartmax onto the CPU cores might already have happened, so you end up with the old governors (ick!). Reboot and all should be fine.
Another option is to open a terminal window and 'su' to root privileges, then type "set prop sys.perf.profile 99". No need to reboot if you do this.
Custom Kernel 07/17/2014
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
[*]SmartMax Tweaks (better battery credit: Rad Ryan);
[*]Startup (/data/local/userinit.d/99-tdhk) handling to force SmartMax governor on all cores;
[*]Rebased onto CM-11 MSM8960 Kernel Sources as of 07/17/2014;
[*]Make Nandroid backup;
[*]Flash in recovery after flashing ROM;
Change Logs
TDHK-Ghost Lollipop 09-20-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost KItKat 12-21-2014
Synced with CM11 sources as of the date of the build.
Use this if you download a KitKat 'ghost' ROM.
TDHK-MotoX 08-31-2014
Fixes intermittent data drops for very latest ROM versions, as well is failures to load WiFi on the same.
Contains all updates to base kernel, CM11 and prior 'enhanced' version -- all as of date of build.
Use this if you download a msm8960dt based ROM.
Prior Releases
TDHK-Ghost Lollipop 09-17-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 08-07-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 07-20-2015
Fix multi-core governor (not)stickiness when cores go offline.
Synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 06-28-2015
Maintenance release.
Synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 05-24-2015
Maintenance release.
Synced with CM12.x sources as of the date of the build.
Disabled quickdraw (which was the brunt of CM12.x updates).
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 04-06-2015
Maintenance release.
Synced with CM12 sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.0 ) .
TDHK-Ghost Lollipop 01-11-2015
Intelliactive governor
Initial Kexec support
ExFAT support
KSM optimizations
Enhanced NEON support
Reduce kswapd schedule enhancement
EXT4 file system speed ehancents
Many stability and optimizations regarding buffer overruns and similar
Synced with CM12 sources as of the date of the build -- includes fix for NFC.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.0) .
TDHK-Ghost Lollipop 12-21-2014
Synced with CM12 sources as of the date of the build -- includes fix for NFC.
TDHK-Ghost 10-26-2014
Synced with CM11 sources as of the date of the build -- includes fix for NFC.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 10-16-2014
Synced with CM11 sources as of the date of the build to pick up WiFi enhancements.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 10-05-2014
Added user level CPU Voltage Control.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 09-20-2014
Based on Ghost unified sources (should work on effectively any AOSP based ROM);
Contains all updates to base kernel, CM11 and prior 'enhanced' versions -- all as of date of build.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-MotoX 08-10-2014
Contains all that is in the Stable version.
Enhancements include upstream commits bringing the kernel up to 3.4.101.
Additional thanks to @dhacker29 for much of the upstream commits -- they're just not in CM yet, maybe one day ...
TDHK-MotoX 07-28-2014
Fixed SmartMax governor bug that caused screen to stay off after some reboots.
Changed bootup and governor setting model to support Android property model (sets up /init.target.rc to import /init.tdhk.rc, the latter of which triggers to set smartmax whenever the Android property "ro.perf.profile" is set to "99".
Yay! AOSP kernel..
Booted up great!
XT 1058 running leonardoafa unofficial carbon rom!
Thanks. Downloading to test on XT1053.
Flashed great. XT1058 on Dirty Unicorns
Can i install it on stock 4.4.2? Or just 4.4.4?
Sorry, dude. Not looking backwards, I doubt less than 4.4.4 will work but you can always flash any try.
Do me a favor and turn on the CPU options in the developer's options. See that the smartmax governor is on all cores.
Want to be sure the init.d script is properly executing on that ROM (DU).
Wi-Fi and Signal lost after installing on XT1053 (Stock 4.4.3)
Im just making sure, this only works on AOSP roms and not stock, right?
Kittiesoncrack said:
Im just making sure, this only works on AOSP roms and not stock, right?
Click to expand...
Click to collapse
Yip, that's right.
kenosis said:
Wi-Fi and Signal lost after installing on XT1053 (Stock 4.4.3)
Click to expand...
Click to collapse
4.4.4, not 4.4.3. Maybe one day I'll look at building backwards to others, but while stabilizing some new features, it's 4.4.4 or up.
Works great on the Droid Maxx!! Thanks man... Much needed!
What 4.4.4 rom is everyone using?
tdhite said:
Yip, that's right.
4.4.4, not 4.4.3. Maybe one day I'll look at building backwards to others, but while stabilizing some new features, it's 4.4.4 or up.
Click to expand...
Click to collapse
Thanks. Hope to see it for 4.4.3.
tdhite said:
Do me a favor and turn on the CPU options in the developer's options. See that the smartmax governor is on all cores.
Want to be sure the init.d script is properly executing on that ROM (DU).
Click to expand...
Click to collapse
{
"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"
}
Remember to quote so I'll get the notifications
@tdhite, can you provide the sources...
Sent from my GT-I9082 using Tapatalk
awesome job tdhite. thanks for your time on this project, so happy to see a CAF kernel available. ?
##W4TCH0UT## said:
@tdhite, can you provide the sources...
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
kernel source add to OP
Sent from my AOSP on Flo using XDA Free mobile app
skiwong20 said:
awesome job tdhite. thanks for your time on this project, so happy to see a CAF kernel available. ?
https://github.com/tdhite/android_kernel_motorola_msm8960dt-common
i will tell him later to add to op
Sent from my AOSP on Flo using XDA Free mobile app
Click to expand...
Click to collapse
It's not the source. It doesn't include the commits of features he has mentioned in the op. So he hasn't uploaded the kernel source.
Sent from my GT-I9082 using Tapatalk
NEXT Kernel 1.0.0:
STOP! This kernel supports Custom KitKat Roms (e.g. OmniROM, SlimKat, CM 11.0), Custom JB 4.3.x Roms (e.g. CM 10.2) and Stock / Stockbased Roms!
It won't work on any AOSP Android 4.1.x or 4.2.x Custom Roms for now!
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY S3 MINI PROJECT!
Sources:
https://github.com/andi34/android_kernel_samsung_golden
Dual-Boot Solution by @ketut.kumajaya, well known from Samsung Galaxy Tab 2 and Samsung Galaxy Tab 3 8.0
I/O Scheduler : noop | deadline | cfq | sio | sioplus | row | zen
Governor : Abyssplug | Ondemand | Interactive | Powersave | Performance | SmartassV2 | Sakuractive
based on latest Samsung OSRC for Samsung Golden (JB_Update2)
Linux kernel 3.0.101 version
Compiled with GCC 4.7
Open source Samsung exFAT included (v. 1.2.7)
Static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. Thanks to @ketut.kumajaya
"magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
SElinux Support
Known Problems:
Bootmenu
- Reboot into Recovery from main Bootmenu does not work
- Reboot into Bootloader from main Bootmenu only reboots normal
StockRom
- USB connection not working, charging works
- Wifi-Tethering not working on Stock / Stockbased Rom
Known fully working Roms
SlimKat by Android-Andi
OmniROM by golden-guy
VanirAOSP by Unjustified Dev
enox Stockbased Rom
Stock Light
Virginity v14
Selfcompiled CM 10.2.1 (based on CM 10.2.1 Stable Source)
Novafusion CM 11 & PAC (ext4 formatted!)
Novafusion CM 10.2 & PAC
Thanks To:
ketut.kumajaya - without you this would never be possible <3
gokhanmoral, Chainfire
@LuuchoRocha
@cocafe
OliverG96
DerTeufel1980
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
I am still learning each day, i learnd most stuff from our great Developer Ketut P. Kumajaya
- i think HE deserves a Beer instead donating to me ATM. If you like you can spend Ketut a beer using PayPal
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA:DevDB Information
[golden] NEXT kernel, Kernel for the Samsung Galaxy S III Mini
Contributors
Android-Andi, ketut.kumajaya
Kernel Special Features:
Version Information
Status: Beta
Created 2014-08-12
Last Updated 2014-10-11
Downloads
All files attached
- NEXT Tool 0.2 to create a 2nd System Partition (system.img) - also included inside PhilZ Touch Blackhawk Recovery
- PhilZ Touch Blackhawk Recovery for Dual-Boot-Support
- NEXT Kernel
Since NEXT Kernel 1.5.4: download latest NEXT Kernel here
Older files for history still here attached!
Changelog
Code:
[U]11.10.2014[/U]
1.5.6 -> 1.6.0
- Utilized blkid further
- Autogenerated fstab adapted from NEXT Kernel for Samsung Galaxy Tab 3
- Initial F2FS Support (experimental)
[U]19.09.2014[/U]
Update dual boot tool 0.3
- Create 1.5 GB dynamic growth sparse image
- Ext4 formatting fix
- Free space calculation fix
1.5.5 -> 1.5.6
- fixes a warning in dmesg (sysfs: cannot create duplicate filename '/devices/virtual/switch/usb_audio')
[U]17.09.2014[/U]
1.5.4 -> 1.5.5
- get rid of DVFS limit without breaking Stock 4.1 or Android 4.3 / Android 4.4
thanks [user=5562153]@LuuchoRocha[/user] and [user=4832589]@cocafe[/user]
[U]16.09.2014[/U]
1.5.3 -> 1.5.4
- Android 4.3: added PAC Support
- Nintendo Wii Remote support (experimental, untested)
- cpufreq: turn all CPUs online when governor gets changed
[U]04.09.2014[/U]
1.5.1 -> 1.5.3
- "magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
- Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
- Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
- symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
[u]01.09.2014[/u]
1.5.0 -> 1.5.1
fix broken Dual-Boot (because missing "tmp" folder inside ramdisk? also some file permissions fixed inside ramdisk)
1.4.0 -> 1.5.0
Upstream Kernel Changes to 3.0.101 - thanks a lot to @Fred6681 for fixing some know Problems after Upstream!
Build Xpad module (not tested if it is working)
Enabled DVFS Limit to make the Kernel boot on Stock and AOSP Roms
New Charger-Animation - thanks a lot to @daywalk3r666
[u]25.08.2014[/u]
1.3.1 -> 1.4.0
Initial CM 10.2 support
[u]22.08.2014[/u]
1.3.0 -> 1.3.1
Fix 800mhz bug, thanks to @Fred6681
1.2.0 -> 1.3.0
Updated Android 4.4 ramdisk: this will fix broken Wifi on Novafusion Roms / Roms based on Novafusion source
Build exFat as module
[u]20.08.2014[/u]
1.1.0 -> 1.2.0
Added Stock / Stock based 4.1 Support
More i/o scheduler: Added sioplus | row | zen
Compiled using GCC 4.7 again for better compatibility
Update LZO compression
arm/vfp: Makefile optimization
and some more....
1.0.5 -> 1.1.0
Fixed bootmenu flickering / blackscreen :) now the bootmenu is 100% visible
(Reboot-Recovery option from bootmenu not working, ends in kernel-panic,
reboot bootloader not working, it will normal reboot)
partially restore initial cm11 ramdisk
cleanup cm11 ramdisk
[U]19.08.2014[/U]
1.0.4 -> 1.0.5
Update permissions inside init.samsunggolden.rc,
set SELinux to permissive for now,
lzma compressed ramdisk
1.0.3 -> 1.0.4
Use Linaro 4.8 Toolchain
[U]18.08.2014[/U]
1.0.2 -> 1.0.3
Use Linaro 4.7-2013-04 Toolchain
[U]12.08.2014[/U]
1.0.1 -> 1.0.2
- fix an Superuser issue, added back init.superuser.rc
1.0.0 -> 1.0.1:
- fix "com.android.phone" crashed on Vanir Rom
1.0.0:
- initial release
How-To
Flash PhilZ Touch Blackhawk Recovery
Reboot into PhilZ Touch Blackhawk
Flash NEXT Kernel
Advanced Functions -> Run Aroma Dual Boot Tool
Create a 2nd System.img (choose 1 GB)
Reboot your recovery
Choose the 2nd Bootoption (it is flickering, black screen, just press the volume down key one time and press the power button).
Now the navigation buttons inside PhilZ Touch are RED
Flash a 2nd Rom (i tested my own SlimKat and @golden-guys OmniROM because they don't use F2FS)
Flash NEXT Kernel again
Reboot
Now you will see a Bootmenu (flicckering & blackscreen), you will see it short if you press the volume key,
first option = boot 1st Rom, second option = boot 2nd Rom
USE ON YOUR OWN RISK! MAKE A BACKUP BEFORE TRYING!
Reserved
Dual Boot FAQs
Adapted from @ketut.kumajaya s Dual-Boot FAQ,
original adapted from droidphile's "Dual Boot FAQs".
1. "Why would I wanna dual-boot?"
A. You don't have to.
You need one testing system and don't want to break your daylie Rom.
You can not decide between different Roms - use both
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p24 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel.
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=54772218&postcount=2
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present AOSP, setup AOSP as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash AOSP ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
2) Present AOSP, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create a 2nd system.img and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your AOSP ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Reboot into primary recovery
viii) Flash AOSP ROM as 1st ROM
ix) Flash blackhawk's NEXT kernel again
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition
20. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool or "Run Aroma Dual Boot Tool" in Advaced Menu from PhilZ Touch Blackhawk and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
21. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
22. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
23. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
24. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
25. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
26. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p25 = /data
mmcblk0p22 = /system
mmcblk0p23 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition.
Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom.
Cache in mmcblk0p24 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p25 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- dev/block/mmcblk0p24 is mounted as /cache.
How to get important Logs
tonyp said:
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
More FAQs will be added and the list will be updated as DB is improved.
Wow!
another milestone in the S3 Mini history!
Keep it up bro :good:
Incredible!!
This will bring my two favorite ROMs on one device!! Unbelievable Till now, I thought it is possible only with linux lubuntu and ROM, like on my tab...
Thank you!
m.
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
meduza2 said:
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
Click to expand...
Click to collapse
Ah missed that part! Thanks for pointing out.
Sent from my GT-I8190/Novafusion CM11
No worries
m.
heithered said:
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Click to expand...
Click to collapse
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Android-Andi said:
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Hey, this is a big deal. It is still awesome with or without stock support! Thanks for your awesome work!
Sent from my GT-I8190/Novafusion CM11
Well, just to leave an "Amazing work" as always:good:
great work.....dual boot with slimkat and omnirom works perfect.with vanir "com.android.phone" crashed
Top Job and faster as Nova!!!!
especially for you
@Android-Andi,
because of the world first dual boot for our s3mini, we created extra an info banner for you
Please have a look: Weltpremiere bei hubo.in
meduza, bodo_1, daywalksr666, kingg
Wow, you did it! That's so cool! Thanks a lot for this! ?
Simply awesome
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
The only idea i have:
First ROM for daily use
Second ROM for testing and replacing with different ROMs...
m.
moonryder said:
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
m.
Click to expand...
Click to collapse
you can load two roms to your phone.
at start up,you can choose either of 2 roms.
may be from recovery mode I think.
this is all what I know. hope I helped.
waiting for correction if I was wrong.
thanks and great work and much appreciation to Android Andi bro
@moonryder,
you could quickly boot one of your favorite ROMs or use the second boot partition for test ROMs....
m.