This is a kernel, build from the recently released saga-ics-crc-3.0.16-62a67df source.
Compatible with all ICS (Android 4) + Sense (3.6, 4A or 4) based ROMs
OFFICIAL MIUIv4 and Stock rooted ICS users can enjoy init.d scripts support with this kernelEnjoy!BACK2BASICS EDITION
FEATURES
Interactive Aroma Installer
Completely Stock code, with only 2 additions by me:
Configurable sweep2wake.
Ported bcmdhd wireless driver from the HTC One V latest source code for better reception and no wakelocks. Still breaks WiFi tethering in ROMs based on Sense 3.6. Tethering works fine in Sense 4
Completely Stock ramdisk. The only changes are:
Unsecured boot.img (adb remount and USB debugging)
Busybox run-parts (init.d scripts) support
Some extra lines, required for the proper operation of the new WiFi driver
No OC, UV, optimizations or any other changes.
Compiled with the recommended by HTC toolchain 4.4.3
ISSUES
For all with BLUETOOTH issues: use 4EXT Recovery
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to falsemanually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
NEW USERS: before flashing install/update BusyBox in /system/xbin (with some of the apps available in the Google Play - the one by Stericsson+Smart Install worked fine for me) and check for the existence of the busybox binary and run-parts symlink in the /system/xbin folder on your device. If there is no such files install/reinstall BusyBox until you have it.
OPTIONAL: If you do not have an /system/etc/init.d folder AND you want to use additional modules you should create it manually BEFORE flashing the kernel:adb remount
adb shell
mkdir /system/etc/init.d
chmod 775 /system/etc/init.d
DOWNLOAD AND INSTALLATIONDownload: b2b_3-0-16.zip
md5sum: d5bd32bd12a0e1120b03f800eaf1beda
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with th following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.imgIMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
Boot images are:
Sense4_boot.img - for all Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa Prime, Desire XS, ViperSaga, others)
Custom_Sense36_boot.img - for ICE_DS, Stock ICS by masteross, or other custom Sense 3.6 ROM without lib partition
Stock_Sense36_boot.img - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_boot.img - for any version of official MIUIv4
NOTES:
There is no boot.img for Virtuous Infinity since it cannot operate smooth with the Stock CPU settings
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)
PATCHED KERNEL 3.0.89
Due to controversial feedback on Tweaked kernel starting from version 5.0 I have decided to take a different approach.
Patched kernel unifies the concept of both Tweaked3 and B2B kernels.
So what does this mean?
The HTC source is taken as a base and is synced completely with the upstream (the official Android kernel 3.0) where applicable. Since it is patched only up to 3.0.72 the rest of the patches are taken directly from the Linux kernel upstream.
All is done from scratch and revising every single commit (it took me 4 days to complete this only). The result is absolutely clean merge (not as in Tweaked where I took the patches from other developers without actually knowing have they screw up something in the progress). During the patching I have discovered some misses or copy-paste from 3.4 upstream (which I consider for another generation devices and probably the changes from there are not completely suitable for our device). I have cleaned and synced with the 3.0 upstream all not-updated files that I discovered during the patching.
FEATURESThe features of the kernel are the basic ones from Tweaked, but staying as close as possible to the Stock configuration (B2B concept):
Interactive Aroma Installer
Compiled with GCC 4.4.3 toolchain
Patched to Linux Kernel version 3.0.89
Synced with Android kernel 3.0 upstream
Overclockable to 1.5 GHz
Added VDD sysfs interface for userspace UV control
Stock Frequencies and Voltages
Default governor: INTERACTIVE @ 254 - 1024 MHz
Interactive governor updated from android 3.4 upstream
Default scheduler: DEADLINE
Configurable Sweep2Wake
Fixed WiFi tethering on Sense 4 based ROMs
Updated WiFi drvier from HTC One V source
Built-in CIFS support
Built-in TUN support
Built-in NTFS + NLS_UTF8 support
Optional WiFi calling
Two way call recording - both WAV and AMR
Enabled USB OTG HOST (big thanks to astro757 and engelmarkus)
Enabled SWAP support
ISSUES
If your WiFi does not work upon install check this solution /10x to toxic-hero/
Sometimes the sweep2wake does not work instantly after deep sleep period. Just swipe once more to unlock the device or press the search button.
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to false manually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
For all with BLUETOOTH issues: use 4EXT Recovery
USEFUL INFORMATION, PLEASE READOverclocking applications, reported to work:
If you are in doubt which governor and IO scheduler to use - there is a lot of useful info here (thanks to Tectas and the authors)
SetCPU
Voltage Control {settings not stick after reboot on Virtuous Infinity}
No-frills CPU Control {settings not stick after reboot on Virtuous Infinity}
Daemon Controller app + andrev_oc script
note1: there is virtuous_oc on Virtuous Infinity already, so you can use only the Daemon Controller app
note2: oc daemons are not supporting scheduler changing
undervolting can be done with a command from Terminal Emulator or adb shell:echo -X > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levelswhere X is the desired value (-25, -50, -75, -100, -125 or whatever you like). Unfortunately has to be repeated after every reboot since putting it in an init.d script is risky
Originally posted by engelmarkusHi,
I played around with the experimental branch of your kernel once more and today it works perfectly.
Keyboards, mice and USB storage devices work without any messing with the terminal. For almost-auto-mounting I used this app here: https://play.google.com/store/apps/d....shajul.usbotg
So I think you can very well enable this in your next kernel version so others can try this out, too.
DOWNLOAD AND INSTALLATIONDownload: 3089.zip
md5sum: 921dda7817b33ee1b7730afca4c57e1c
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with the following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.imgIMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
Boot images are:
Virtuous_boot.img - for any version of Virtuous Infinity
Sense4_boot.img - for other Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa, Desire XS, ViperSaga, others)
Custom_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Custom_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Stock_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
Stock_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for any version of official MIUIv4
MIUIv4_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for any version of official MIUIv4
Sense4_lib_boot.img - for recent versions of Desire XS or other Sense 4 ROM that is reodexed/with separate lib partition
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)
TWEAKED3 VERSION XI DISCONTINUED - reference only
FEATURES
Interactive Aroma Installer
Patched to Linux Kernel version 3.0.56
Added ck1 patchset by Ziggy (thx to Coolexe) - aims towards better performance
Compiled with the latest stable Linaro GCC 4.7.3-2012.11 toolchain
Overclockable to 1.5 GHz
Added VDD sysfs interface (10x to lowveld) for userspace UV control
Stock Frequencies and Voltages
Tuned ONDEMAND and INTERACTIVE governors
Tuned DEADLINE and SIO schedulers
ONDEMAND @ 254 - 1024 MHz and DEADLINE set as default
Enabled TINY_PREEMPT_RCU
Some tweaks and optimizations for better performance
Configurable Sweep2Wake
Fixed WiFi tethering on Sense 4 based ROMs (10x to m0narx)
Updated WiFi driver from the latest HTC One V source
Enabled CIFS and TUN support
Enabled NTFS + NLS_UTF8 support
Enabled PPP_ASYNC and PPP_SYNC_TTY
Two way call recording - works in AMR and WAV (10x to Andromadus) format with CallRecorder app by skvalex
CHANGELOG
16 Dec 2012: Tweaked3 XI:
Compiled with the latest stable Linaro GCC 4.7.3-2012.11 toolchain
Patched to Linux Kernel version 3.0.56
Upstream update of interactive governor change speed routine
Enabled TINY_PREEMPT_RCU - should give small-memory-footprint on uniprocessor systems (where all processing tasks share a single CPU)
23 Nov 2012: Tweaked3 10.0 (X):
Patched to Linux Kernel version 3.0.52
Removed all third party governors
Removed BFQ, VR and CFQ schedulers
Tweaked SIO for better performance on Android
All modules built-in, except the one for WiFi Calling (kineto-gan.ko - optional)
No more init.d scripts, except for sweep2wake
During installation a /system/etc/init.d folder will be created, with the right permissions on ROMs that do not have such
09 Nov 2012: Tweaked3 9.0:
Compiled with the latest Linaro Toolchain 4.7.3-2012.10
Patched to Linux Kernel version 3.0.51 (10x to oliverclaude)
Ondemand and Interactive governors synced to upstream (10x to Andromadus)
Scheduler improvements (10x to faux123)
16 Oct 2012: Tweaked3 8.6:
Patched to Linux Kernel version 3.0.46
Updated BFQ code to v5 (10x to Andromadus repo)
2WCR now makes recording in WAV format (10x to Andromadus repo)
BCMDHD wireless driver is updated to the latest HTC One V source - there are some changes related to the Country Codes, so please anyone that has such issues to try it without WiFi FIx app and report
Initialization of the wireless modules moved to ramdisk, no need of init.d script to run them anymore, so new users can skip that part and go straight to flashing!
10 Oct 2012: Tweaked3 8.5:
Patched to Linux Kernel 3.0.45
Added ck1 patchset by Ziggy (thx to Coolexe) - aims towards better performance
Removed ZRAM - it seems that the compression was the reason for the battery drain
Removed the script for changing the screencapture line in build prop from Aroma, hopefully this will solve the installation issues. You will have to change it manually if needed
01 Oct 2012: Tweaked3 8.0:
Aroma installer - one file for all. No need to do any preparations anymore (like changes of the updater-script, etc) The installer will gather the important information about your ROM and hboot and the flashing process will be done accordingly.
HTCDEV users: there are instructions in the first post which boot.img to flash. Important: if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
All governors are tuned up according to the CPU frequencies (should have done it long time ago, sorry for the delay). OndemandX (proved unstable) and Userspace (doubt that anyone even uses it) governors removed
CIFS, TUN, KINETO_GAN, NTFS+NLS_UTF8 and ZRAM moved to modules for optional install (the installer will give you a menu for selection, where the purpose of each module is explained)
Updated LZO compression/decompression method for ZRAM (it sould be at least twice faster now)
TREE_RCU and SLAB memory allocator set as default (as it was in the Stock kernel).
21 Sep 2012: Tweaked3 7.1:
Patched to Linux kernel version 3.0.43
Compiled with the latest stable Linaro GCC 4.7-2012.08 toolchain
Added VDD sysfs interface (10x to lowveld) for userspace UV control (comes with Stock Voltages by default)
Added BrazilianWax, InteractiveX and OndemandX governors
All modules except bcmdhd.ko are built-in in the kernel
Finally found the reason of the battery drain when the Screen is ON and hopefully fixed it. Now the battery life should be rock solid
Flashable zips should be fixed for good. They now will wipe dalvik-cache and cache during flash, no need to do it manually. Version 5.0 zips are backwards compatible (this means you can flash version 5 over version 7.1 without additional actions (deleting or moving files)
05 Sep 2012: Tweaked3 6.0:
Added bcmdhd WiFi driver and fix WiFi Tethering on Sense 4 ROMs (10x to m0narx)
Flashable zips are back!
Comes is two flavors - undervolted -100 and Stock voltages
02 Sep 2012: Tweaked 5.0:
Built with Linaro toolchain
Patched to Linux Kernel version 3.0.42
Reverted to Stock Voltages due to some users complaints
SLUB is the default memory allocator
Added tun.ko module (use 51-modules init.d script to load it)
Added cifs.ko module (use 51-modules init.d script to load it)
Enabled full capacity charge in non-OEM chargers (e.g. some car chargers)
Enabled NTFS + NLS_UTF8 support
Enabled PPP_ASYNC and PPP_SYNC_TTY
Enabled ZRAM - adds another 100 MB to your RAM as a SWAP partition (use 52-zram init.d script to load it)
Enabled USB-OTG (needs confirmation, since I do not have the necessary equipment) - not working
27 Aug 2012: Tweaked3 4.7:
Expanded frequency table - to give the CPU more steps until the highest frequency
Slight undervolting to save some battery life
Fixed backlight staying on when pressing only home button when s2w with backlights enabled (10x to scan6 for the heads up)
Default clock frequency is 1024 MHz for everyone that requested it
Enabled init.d support in the MIUIv4 version (now you can use the 50-sweep2wake script too)
Separate installation files and instructions for S-ON (hboot 2.00.0002) and S-OFF (hboot 0.98.2000, 2.00.2002, 7.xx) users
25 Aug 2012: Tweaked3 4.0:
Patched to Linux Kernel version 3.0.41
Added sweep2wake configuration: default Enabled with no backlight
Added lionheart, lulzactive, intellidemand, scary, lagfree, lazy and savagedzen governors
Added BFQ and VR schedulers
Added Snapdragon optimizations
23 Aug 2012: Tweaked3 3.0:
Added Lionheart and Smartass2 governors
Added Simple IO Scheduler
Enabled ARCH_POWER
Disable GENTLE_FAIR_SLEEPERS
22 Aug 2012: Tweaked3 2.0:
Patched to Linux Kernel version 3.0.30
Added support for MIUIv4 and Virtuous Infinity
Source code published @github
21 Aug 2012: Initial release
Based on the released by HTC saga-ics-crc-3.0.16-62a67df source
Added Sweep2wake functionalit
Overclocked to 1,5 GHz
ISSUES
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to falsemanually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
For all with BLUETOOTH issues: use 4EXT Recovery
USEFUL INFORMATION, PLEASE READOverclocking applications, reported to work:
If you are in doubt which governor and IO scheduler to use - there is a lot of useful info here (thanks to Tectas and the authors)
SetCPU
Voltage Control {settings not stick after reboot on Virtuous Infinity}
No-frills CPU Control {settings not stick after reboot on Virtuous Infinity}
Daemon Controller app + andrev_oc script
note1: there is virtuous_oc on Virtuous Infinity already, so you can use only the Daemon Controller app
note2: oc daemons are not supporting scheduler changing
undervolting can be done with a command from Terminal Emulator or adb shell:echo -X > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levelswhere X is the desired value (-25, -50, -75, -100, -125 or whatever you like). Unfortunately has to be repeated after every reboot since putting it in an init.d script is risky
DOWNLOAD AND INSTALLATIONDownload: Tweaked3_XI.zip
md5sum: e9bf1393d48c6f7e7e8697e34ac63e7a
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with the following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.imgIMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
Boot images are:
Virtuous_boot.img - for any version of Virtuous Infinity
Sense4_boot.img - for other Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa, Desire XS, ViperSaga, others)
Custom_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Custom_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Stock_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
Stock_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for any version of official MIUIv4
MIUIv4_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for any version of official MIUIv4
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)
Stock Sense GingerBread sweep2wake kernel
MIRROR @ DEV-HOST /all versions/:
SOURCE CODE
Tweaked3 - experimenal branch
B2B - stable branch
Patched - linux branch
CREDITSHTC for the source code
BIG thanks to m0narx for the WiFi Tethering fix!
showp1984 and his source for atmel touchscreen devices
mdeejay for some of the linux version patches
AdiPat for his repo
Coolexe for his repo
cjoliver for the sweep2wake switch and the recent upstream patches
crking for the sweep2wake init.d script
lowveld for his all great projects for HTC Desire S and the VDD sysfs
Ziggy for the ck1 patchset
Team Andromadus for their repo
astro757 and engelmarkus for the USB OTG HOST
All the great kernel developers @Xda For their great workThanks for testing and corrections:rzr09
dr.higgins
dont know
signfinder/dalexx
dmatik
TatoValverde
toxic-heroThanks for donating. Much appreciated:dont know
TatoValverde
petjoh
XDA:DevDB Information
B2B |&| Patched, Kernel for the HTC Desire S
Contributors
amidabuddha
Source Code: https://github.com/amidabuddha/saga-ics-crc-3.0.16
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: BACK2BASICS EDITION
Stable Release Date: 2012-08-21
Current Beta Version: PATCHED KERNEL 3.0.8
Beta Release Date: 2013-08-06
Created 2015-02-24
Last Updated 2015-02-24
amidabuddha said:
Features:
- Sweep2wake functionality
- Overclocked to 1,5 GHz
Download: View attachment 1273069
md5sum: 98fe244bbfb430283f194e61031e0d7f
Issues:
- due to incompatibility with s2w the native Sense screenshot function is disabled
- do not use with the official MIUI v4, since it is not mounting /system/lib on init
Installation: flash in the Recovery
Click to expand...
Click to collapse
man you are the best!!
Installed on Nik Project, any issues with buttons backlight? It seems like they are always on
Nope,it works well to me
Nik project v4.1:
1.oc ---ok
2.s2w---ok
Sent from my HTC Desire S using xda app-developers app
Nik 4.1, have 3600 in anututu =)
Will try to reinstall with really full wipe, because my buttons are always on
mizerok said:
Installed on Nik Project, any issues with buttons backlight? It seems like they are always on
Click to expand...
Click to collapse
On Fallout the backlight works as it should.
In a room without direct sunlight - off
On screen off - off
Outdoor or in a dark place - on
Try in different conditions, maybe there is too much light where you are
I wish it was usable for non Sense ROMs
Nik 4.1, Atuntu - 3527
No prob with S2W. Auto brightenss is off.
Thx Stefan.
I get 3883 on antu with fallout rom
sent from my desire s from one of lowvelds roms
docertabum said:
I wish it was usable for non Sense ROMs
Click to expand...
Click to collapse
Working on it more or less ^^
Great done amidabuddha
Gesendet von meinem GT-I9300 mit Tapatalk 2
I am not a big fan of benchmarking. But tried just out of curiosity.
Antutu: 4035 on Fallout
Sent from my HTC Desire S
It's perfect! I haven't seen so cool and fast rom as fallout with this kernel yet!
Is it not harmful for Desire S to overclock to 1.5 GHz ?
Shouldnt make any harm going to 1.5.
Now the kernel source, is https://github.com/showp1984/bricked-shooteru-ics-sense what you releasing? if no you need to release the exact kernel source you using, laws
I dont want any saga dev to have issues
Edit:
More then that, some devices comes with stock 1.5 with same processor but remember, the more you put, the less battery
Hi, is there a way to revert it to stock? Thanks.
Sent from my HTC Desire S using xda app-developers app
superkid said:
Shouldnt make any harm going to 1.5.
Now the kernel source, is https://github.com/showp1984/bricked-shooteru-ics-sense what you releasing? if no you need to release the exact kernel source you using, laws
I dont want any saga dev to have issues
Edit:
More then that, some devices comes with stock 1.5 with same processor but remember, the more you put, the less battery
Click to expand...
Click to collapse
Good point
Yes the changes for sweep2wake are the same, made by showp1984, unmodified by me
And yes, this is the stock OC, I have just enabled it for the time being.
I am pretty sure that soon there will be much more tweaked and polished kernels made by the experienced devs, but since most of them are taking summer holidays I compiled this one for playing with Sense 4 until they come back to development
Dreamtheater2003 said:
Hi, is there a way to revert it to stock? Thanks.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Yes you can always flash the original boot.img of the ROM that you are using via fastboot. Then copy the bcm4329.ko and kineto_gan.ko of your original ROM to /system/lib/modules with any root file explorer. To restore the stock screenshot feature change the value ro.htc.framework.screencapture from false to true in your build.prop
Dreamtheater2003 said:
Hi, is there a way to revert it to stock? Thanks.
Click to expand...
Click to collapse
flash the rom once again...
masterross said:
Nik 4.1, Atuntu - 3527
No prob with S2W. Auto brightenss is off.
Thx Stefan.
Click to expand...
Click to collapse
Nik Project X v4.1 with AnTuTu - 3907
sdcard: class6
wifi not working after flashed this oc file.....why?
Related
Here come our custom 32A kernel
Updated, see changelog
Sorry for the delay, I was taking some sun and some work .
http://www.mediafire.com/?mjgm5gcgmya
README:
Code:
HTC Magic Sapphire PVT32A kernel build.
This kernel build is only for 32A (HTC branded) version of the HTC magic.
It's designed to run FAST. (much more than the stock kernel).
I made some improvement in the config, removed uneeded things (all of this debuging message, hooks, ... is not needed for everyday use,
and use precious CPU cycle for nothing :).
You can use this kernel in your current ROM but you need to known what you're doing. (Boot image and ramdisk knownledge are required).
If you don't have those skills, you can wait a ROM cooker to build a ROM with this kernel for you. (It's not a subliminal message :p).
Hope you'll enjoy it.
In this archive you'll find:
README -> this file :)
CHANGELOG -> Errr... oh yes, got it! It's the changelog!
boot-gbo-v4.img -> An boot image. You can try to boot it but you'll be more lucky if you ask your ROM builder :).
zImage -> for ROM builders. You can include it in your boot.img file
config.gz -> The config used to compile the kernel.
wlan.ko -> Wlan driver for the kernel in this archive.
modules/ -> Extra modules you can include in you ROM (or not). IPV6, ReiserFS, NTFS, Tun, ...
modules/ipv6.ko -> IPv6 support
modules/xfrm6_mode_beet.ko -> Needed by IPv6 support
modules/sit.ko -> Needed by IPv6 support
modules/xfrm6_mode_transport.ko -> Needed by IPv6 support
modules/xt_TCPMSS.ko -> Needed by IPv6 support
modules/xfrm6_mode_tunnel.ko -> IPv6 over IPv4 support
modules/tun.ko -> TUN/TAP Interface support
modules/tunnel4.ko -> IPv4 Tunnel support
modules/ipip.ko -> Needed by TUN/TAP Interface support
modules/ip_gre.ko -> IP GRE security support
modules/ntfs.ko -> NTFS support
modules/reiserfs.ko -> ReiserFS support
modules/as-iosched.ko -> AS scheduler
modules/cfq-iosched.ko -> CFQ scheduler
Current version: 2.6.27-6
Features:
- See CHANGELOG
Questions, bugs, request ? -> PM Me
Creditz:
TigerTael for making a 32A compatible kernel
rayman84 which helped TigerTael with its quest :) (and making an unified patch)
Amon_RA for giving me some keys to find the wallpaper bug.
All people that make android & htc hacking possible every day
CHANGELOG:
Code:
2.6.27-gbo-6:
- Reverted to GP Timer, should fix clock issues
- Switched to SLOB allocator (default android kernel behaviour)
- Merged last change from TigerTael patch
2.6.27-gbo-5:
- Removed debug symbols from kernel
- Switched to SLUB allocator
- Added loopback device support
- Removed kernel debugging core
- Disabled verbose console message
- Added TUN/TAP module to extras
- Removed SysRq keys
2.6.27-gbo-4:
- Reverted inotify support
- Wallpaper change is now working.
- Added extra modules, see README
2.6.27-gbo-3:
- Removed profiling support from kernel.
- Reverted CPUFreq scaling to default behavior.
- Changed default CPUFreq gouvernor from 'performance' to 'ondemand'.
- Set max frequency to 528Mhz
- Added reiserfs support.
- Removed Network FS support
- Removed DebugFS
- Removed Kernel debugging
2.6.27-gbo-2:
- Added IPTables support (for tethering).
- Added EXT4 support (dev).
- CPU scaling is reduced at max 245Mhz when screen is OFF.
- CPU scaling is increased at max 528Mhz when screen is ON.
- Latest WLAN driver which will be released with Donut build.
- Removed some debug options from the kernel config.
- Removed inotify support.
Known bugs:
- Not yet...
I just cooked all of this, the real hard work was made here:
http://forum.xda-developers.com/showthread.php?t=548061
gboddina said:
Here come our custom 32A kernel
http://www.mediafire.com/download.php?wmtnwn5tbzt
README:
Code:
HTC Magic Sapphire PVT32A kernel build.
This kernel build is only for 32A (HTC branded) version of the HTC magic.
In this archive you'll find:
README -> this file :)
boot-gbo.img -> An boot image. You can try to boot it but you'll be more lucky if you ask your ROM builder :).
zImage -> for ROM builders. You can include it in your boot.img file
config.gz -> The config used to compile the kernel.
wlan.ko -> Wlan driver for the kernel in this archive.
Version: 2.6.27-2
Features:
- IPTables support (for tethering)
- EXT4 support (dev)
- CPU scaling is reduced at max 245Mhz when screen is OFF
- CPU scaling is increased at max 528Mhz when screen is ON
- Latest WLAN driver which will be released with Donut build.
Questions, bugs, requests ? -> [email protected]
Creditz:
TigerTael for making a 32A compatible kernel
rayman84 which helped TigerTael with its quest :) (and making an unified patch)
All people that make android & htc hacking possible every day
I just cooked all of this, the real hard work was made here:
http://forum.xda-developers.com/showthread.php?t=548061
Click to expand...
Click to collapse
Excellent job.
Any chance you wanna talk me through building a kernel!?
I think someone need to make a goot tutorial about this! (getting sources, applying the patch, building kernel, builder wlan module...)
I'm not a fan of making documentation but if nobody do it, I will, because the knownledge must be shared
gboddina said:
I think someone need to make a goot tutorial about this! (getting sources, applying the patch, building kernel, builder wlan module...)
I'm not a fan of making documentation but if nobody do it, I will, because the knownledge must be shared
Click to expand...
Click to collapse
Well, even if you could do something quick and basic it would be awesome
a good resource here..
http://sglnx.com/2009/08/linux-kernel-in-a-nutshell/
Works on JACxHEROski-v1.4 for 32A.
(it's a fast HERO rom btw)
Thanks a bunch! I have multi-touch now!
Instructions
For the strong hearted only!
Testing the boot.img: (gboddina's instruction from original thread)
adb push wlan.ko /system/lib/modules/wlan.ko
adb shell sync
[Shutdown device, adb rebooting can cause wifi to not work]
[Fastboot device]
fastboot boot boot-gbo.img
Click to expand...
Click to collapse
Flashing the boot.img:
[Normal Phone Mode]
adb push boot-gbo.img /sdcard
adb shell cat /dev/zero > /dev/mtd/mtd2
adb shell flash_image boot /sdcard/boot-gbo.img
[Reboot Phone]
Click to expand...
Click to collapse
It's a nice basic kernel. But just wondering, in the original thread, it's stated that LED is working. But my Rogers Magic still doesn't show red LED during charging. Any explanations?
Thanks, 2.6.29 with compcache and the common g1 kernel modules would be nice =]
Any dangers with trying to use this, or things to watch out for?
This boot.img does not work with the Rogers ROM for me It gets stuck at the Rogers logo...
hotweiss said:
This boot.img does not work with the Rogers ROM for me It gets stuck at the Rogers logo...
Click to expand...
Click to collapse
There is another bootimage with another ramdisk , it will work just gå back to the orginal thread from the first post here and look!
it works! ...., waiting for the tutorial
gboddina said:
Here come our custom 32A kernel
http://www.mediafire.com/download.php?wmtnwn5tbzt
README:
Code:
HTC Magic Sapphire PVT32A kernel build.
This kernel build is only for 32A (HTC branded) version of the HTC magic.
In this archive you'll find:
README -> this file :)
boot-gbo.img -> An boot image. You can try to boot it but you'll be more lucky if you ask your ROM builder :).
zImage -> for ROM builders. You can include it in your boot.img file
config.gz -> The config used to compile the kernel.
wlan.ko -> Wlan driver for the kernel in this archive.
Version: 2.6.27-2
Features:
- IPTables support (for tethering)
- EXT4 support (dev)
- CPU scaling is reduced at max 245Mhz when screen is OFF
- CPU scaling is increased at max 528Mhz when screen is ON
- Latest WLAN driver which will be released with Donut build.
Questions, bugs, requests ? -> [email protected]
Creditz:
TigerTael for making a 32A compatible kernel
rayman84 which helped TigerTael with its quest :) (and making an unified patch)
All people that make android & htc hacking possible every day
I just cooked all of this, the real hard work was made here:
http://forum.xda-developers.com/showthread.php?t=548061
Click to expand...
Click to collapse
Does your kernel allow changing the CPU freq? The previous one you made would not allow the CPU frequency to be set (By apps, etc)
is it permission problem... you cant write the frequencies?!
Just grabbed setcpu and it seems to halt after the intial page so it just freezes up after hiting the "always allow" page from the superuser app just after hiting "android cupcake 1.5" from the intial page of the app it self... what im trying to say that i dont think its a permission problem...
So I just unpack boot-gbo.img and put the kernel in any rom?
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
i cant find anything beyond cpu0.
TigerTael said:
Does your kernel allow changing the CPU freq? The previous one you made would not allow the CPU frequency to be set (By apps, etc)
Click to expand...
Click to collapse
Since this is active:
Code:
CONFIG_MSM_CPU_FREQ_SCREEN=y
CONFIG_MSM_CPU_FREQ_SCREEN_OFF=245760
CONFIG_MSM_CPU_FREQ_SCREEN_ON=528000
Manual cpu scaling cannot be done.
Seems that many people doesn't like this behavior. I am currently reviewing the config to made some performance improvement and will release 2.6.27-gbo-3 during this day.
Small poll so:
CONFIG_MSM_CPU_FREQ_SCREEN or CONFIG_MSM_CPU_FREQ ?
gboddina said:
Since this is active:
Code:
CONFIG_MSM_CPU_FREQ_SCREEN=y
CONFIG_MSM_CPU_FREQ_SCREEN_OFF=245760
CONFIG_MSM_CPU_FREQ_SCREEN_ON=528000
Manual cpu scaling cannot be done.
Seems that many people doesn't like this behavior. I am currently reviewing the config to made some performance improvement and will release 2.6.27-gbo-3 during this day.
Small poll so:
CONFIG_MSM_CPU_FREQ_SCREEN or CONFIG_MSM_CPU_FREQ ?
Click to expand...
Click to collapse
Well, I definitely like to set my CPU and this is pretty common in the stock kernels and other 32B kernels, so I would stick with this. Of course, this is -your- kernel, so you can do it exactly how you want to. :3
It's not "mine" . It's your kernel and my build
Better, it's a community kernel
I'll revert back to stock configuration for this part .
gboddina said:
It's not "mine" . It's your kernel and my build
Better, it's a community kernel
I'll revert back to stock configuration for this part .
Click to expand...
Click to collapse
Hey i don't wanna sound annoying lol since i already said this but any chance of compcache, squashfs, and cgroup? i'm pretty sure non of them are on the current build since there is lines in the ramdisk im using that try to use these features but it's failing and ofcourse just by looking at "mount"....
thanks for the hard work,
BCK - Bam Custom Kernel for i9003 / Galaxy SL
This Kernel is based on the Chinese GB source, released by Samsung on the 18th of November. Last changes to the source were made by Samsung on November 15th. If you still have questions after reading this post, look at the FAQs (including a list of requested features and known issues).
Kernel features:
No SOD
Bugfixes:
~ Sync bug fixed. Notifications for new mails and messages should arrive within one minute under all circumstances
~ Bluetooth problems fixed. Your phone now should play nice with bluetooth hosts, i.e. your car audio system
~ Micro stutters nearly completely gone thanks to lowered processor transition latency. It's smooooooooth
~ Home button double presses exterminated
Governors:
~ smartassV2 governor by erasmux (default)
~ interactive governor by Mike Chan
IO scheduler:
~ SIO IO scheduler by Miguel Boton (default)
~ BFQ IO scheduler by Paolo Valente and Fabio Checconi
~ deadline IO scheduler
Extended features:
~ ro.secure=0 (root acces through adb shell - to root the 'clean flavour' of BCK, please follow the instructions)
~ EXT4 support (to convert your file system, use amit.bagaria's ext4 add-on .apk) (Only in CF-Root .tar)
~ Support for init.d scripts (to use scripts, please follow the instructions) (Only in CF-Root .tar)
~ BLN support (to use BLN, please follow the instructions)
~ TUN support for VPN networks built-in (no module needed)
~ Increased SD-card read ahead of 768 kb for improved read speed
~ Available with universal CF-root ramdisk based on amit.bagaria's version, improved by loSconosciuto (Only in CF-Root .tar)
~ Available with universal CWM ramdisk (rooted) based on universal CF-root, but 'tweakless' (Only in CWM .tar)
Overclocking and Voltage:
~ Evolved sysfs interface for variable overclock or underclock (all operating points [OPPs] can be adjusted seperately)
~ Fifth OPP (1.2 GHz) available, device booting up at stock speed (1 GHz)
~ Total frequency control. The device will never run at higher speeds than defined by you, not even on WiFi.
~ sysfs interface for voltages (read only at the moment)
~ Slight undervolt (3%) on all OPPs
Flashing , settings and compatibility:
If you want to use BCK, please flash it on a clean stock ROM. If you want to go back to stock, repartition and reflash the full firmware with ODIN. This kernel will not work on CM or MIUI.
The CF-root and CWM versions (PDA_BCK_CF-root_universal_***.tar / PDA_BCK_CWM_universal_***.tar) can be flashed on any recent Gingerbread firmware. These versions are pre-rooted, which means they include Superuser.
The non-CF-root "clean" version (PDA_BCK_XXKPQ_***.tar / PDA_BCK_XXLE4_***.tar) will only work on XXKPQ / XXLE4. Do not flash this version on anything other ROM than the one indicated in the file name. This will break your WiFi. It's especially risky to flash the clean version of BCK after flashing any CF-root kernel before. Don't do it. This version does not include Superuser, but it is prepared to be rooted. Follow the instructions to do this.
After a kernel update, please wait for the device to boot up and reboot once. There is generally no need for cache cleaning or a full reset. To change the governor and IO scheduler, I use NoFrills CPU Control from the market. It's free and reliable.
I recommend to use the clean XXKPQ version. If you want / need to have root, try the CWM version. If you want the 'full package' with FuGu-Mod and more, use the CF-root. I recommend that you do not apply any further tweaks and use a stock ROM.
>>> Warning: Overclocking may damage your device. <<<
Overclocking instructions:
For overclocking, you will need a shell on your phone, or adb access. I use Android Terminal Emulator. Overclocking is currently limited to certain frequencies (see below) and all operationg points will be set with the stock voltage of the corresponding stock frequency. The frequencies you set have to be within the following ranges:
Code:
OPP1: 100 - 500 MHz, stock 300 MHz
OPP2: 501 - 700 MHz, stock 600 MHz
OPP3: 701 - 900 MHz, stock 800 MHz
OPP4: 901 - 1100 MHz, stock 1000 MHz
OPP5: 1101 - 1500 MHz, stock 1200 MHz, not used by default
Remember that your phone uses all operating points depending on the current load. Anything more than 10% higher than the highest stock frequency is likely to be unstable, but you are free to try it. To change the clocks, open Terminal Emulator (or type 'adb shell') and hack in
Code:
su
echo "1100" > /sys/power/overclock_opp4
as an example. The others are opp5, opp3, opp2 and opp1. That's it.
Settings will be lost at reboot, unless you add them to your init.d scripts. I do not recommend this, as this may cause boot loops if the settings are to high! Be advised that NoFrills CPU Control, SetCPU, or whatever app you use that may adjust clock settings interfers with this. You may wanna update their settings after this. I do not recommend using them to set anything at boot if you overclock any OPP, because they might save the wrong frequencies and crash or do worse.
Changelog:
beta 1:
Added cpufreq governors
beta 2:
Changed smartassV2 settings to fit i9003
Added EXT4 support
Smaller zImage due to .config changes
beta 3 (not released):
Experimented with overclocking (not working, yet)
beta 4:
Finetuned smartassV2 settings
Made smartassV2 governor default
Reverted: Smaller zImage due to .config changes
Switched to linaro 4.6.2 toolchain (also used for ICS)
Activated new, aggressive compiler optimizations (-O3)
Added deadline IO scheduler
Added BFQ IO scheduler (10% higher performance than CFQ in Antutu Database IO Benchmark. This does not mean, that the maximum read or write speed increase! It just means that the throughput under heavy load is higher.)
Made BFQ IO scheduler default
Updated all modules
beta 5:
Variable overclock. Loosely based on the modifications of the Nook Color sources by dalingrin and of course with help from amit.bagaria and DooMLoRD.
beta 6:
Variable overclock for all operating points
beta 7:
Switched to universal CF-Root by amit.bagaria (BCK now should run on every recent GB ROM)
Added correct version information in settings menu, credits to DooMLoRD
Fixed cpufreq stats to correctly reflect frequency changes
Increased SD-card read ahead to 768 KBytes. This results in higher SD-card read speeds.
Major simplifications in overclocking code. Works more robust, now.
Added sysfs interface to show voltages. See /sys/power/overclock_vdd_oppX
Changed all voltages to the mainline Linux kernel defaults. This results in a slight 3% undervolt for each OPP, which saves about 5% power and should have no impact on stability whatsoever. Below you will find an overview of the exact voltages.
Code:
stock BCK
OPP1: 1.0250 V 1.0000 V
OPP2: 1.2000 V 1.1625 V
OPP3: 1.3300 V 1.3000 V
OPP4: 1.3875 V 1.3500 V
OPP5: not def. 1.3800 V
beta 8:
OPP5 (1.2 GHz) now enabled in _1200 version of kernel. Thanks to knzo for pointing me to the right patch.
Fixed video recording bug when running at 1.2 GHz
Fixed power management issues at 1.2 GHz
Small changes to smartassV2 and interactiveX settings
beta 9:
Added simple IO ('SIO') scheduler
Only one kernel version now, which includes OPP5 (1.2 GHz) but boots up at 1 GHz. Be advised that your device may nevertheless be running at 1.2 GHz for five to ten seconds at boot because of software limitations.
Changes in PM to always respect cpufreq policy limits. From now on, the device will never run at higher speeds than defined by you, not even on WiFi. Based on an omapzoom.org patch.
Changes to OPP switching code. May lead to less 'hickups'. Based on an omapzoom.org patch.
Bugfix for framebuffer code. Based on an omapzoom.org patch.
Reduced IVA / DSP frequency when on OPP5 to be on the safe side.
beta 9fix:
Reverted: Changes to OPP switching code. May lead to less 'hickups'. (Patch caused random freezes using WiFi.)
Reverted: Bugfix for framebuffer code. (Patch showed no noticeable benefits.)
beta 10:
Fix for sync bug applied. If you still have problems, please report.
This version is identical to beta 10rc14. No need to flash again, if you already are on that version.
beta 11:
Updated universal CF-Root by amit.bagaria to version 9 (released 1st of February 2012), but NO touch recovery
Slight increase in OPP5 voltage (1.38 V -> 1.40 V), may prevent some reported reboots on 1.2GHz
Code:
stock BCK
OPP5: not def. 1.4000 V
Changes in overclocking code to play nice with your frequency settings. If you overclock OPP5 but have restricted freqs to 300 - 1000 MHz, it won't automatically activate OPP5 anymore. The same is true for the lowest OPP.
If you overclock OPP4 above 1000 MHz and have restricted freqs to 300 - 1000 MHz, it will update the upper boundary to the new frequency of OPP4 so it doesn't get deactivated.
beta 12:
Fixed bluetooth problem with car audio systems (Based on omapzoom patches [1], [2] and [3]). Might resolve other bluetooth issues, too.
Universal CF-Root: Fixed bootanimation. Thanks to loSconosciuto.
Universal CF-Root: Fixed install procedure. It will check the actual kernel version, now. Thanks to loSconosciuto.
Universal CF-Root: Fixed fix_permissions script to work on our device. Thanks to loSconosciuto.
Switched to user_defconfig, to avoid unnecessary debug lines in dmesg.
beta 13:
Updated sources to GT-I9003_SWA_GB_Opensource_Update1 from the 30th of March. This also enables TUN support by default. You do not need any modules for this - it works "out of the box" with any VPN client.
Universal CF-Root: Backup is not failing anymore when started from CWM. Thanks to loSconosciuto.
Universal CF-Root: Some small improvements to multiple scripts.
Home button double press issue fixed. There should be no more unwanted double selections in CWM and you can now reliably long press the home button to bring up the list of previously used apps. Idea and timer function taken from a patch by Tegrak.
Fixed priority class for CONTENT_PROVIDER not being set, which may have caused apps of this class to be ignored by the autokiller, resulting in less free RAM.
Lowered OMAP processor transition latency to the value recommended by TI. Subjectively, this brought huge improvements in terms of reducing micro stutters.
Lowered CFS scheduler latency and granularity to values very close to mainline kernel defaults. This could reduce lags in some critical situations, but it doesn't do wonders.
Switched to SIO as default IO scheduler.
beta 14:
Universal CF-Root: Replaced CWMManager and TweakManager with zipaligned files. Thanks to loSconosciuto.
Universal CF-Root: The TweakManager is not replaced on install if it didn't change to preserve it's settings. Thanks to loSconosciuto.
Universal CF-Root: Corrected problems because of too little free space in /system when converting to ext4 by permanently moving InfoAlarm.apk from /system/app to /data/app. Thanks to loSconosciuto.
Universal CF-Root: Fixed the non-working WiFi on XXLE4 and prevented future problems. Instead of patching the WiFi modules, they are now replaced. Thanks to loSconosciuto.
Universal CF-Root: Fixed some small mistakes in the CF-root install procedure.
Switched the compression of ramdisk and kernel from gzip to lzma. This makes the files much smaller and allows us to include more 'stuff'.
Changed smartassV2 settings to wake up at lower frequencies. Further, it is not locked at 300 MHz anymore when the screen is off. Tests showed that free scaling is more battery friendly.
Removed InteractiveX and OndemandX governors and added the Interactive governor by Mike Chan (Source: CyanogenMod Crespo kernel). Since free scaling proved to be more battery friendly, the screen off profiles in InteractiveX and OndemandX made them superfluous.
The device will not scale above 1 GHz for some seconds when booting anymore. It's now safe to use BCK even if your device can't handle 1.2 GHz. Based on a patch by dalingrin.
Changes in PM to respect cpufreq policy limits when playing or recording video. The device should respect your wishes under all circumstances, now
Fixed the SmartReflex voltage calibration of the OMAP SoC for OPP5. This could lower power consumption as soon as OPP5 (1.2 GHz) is activated for the first time.
Slight increase in the OPP5 nominal voltage (1.40 V -> 1.42 V) to allow for some adjustment by SmartReflex (now that it's working...), if necessary. The actual voltage when the device is running will not change for most users! Based on patches by dalingrin and Sanjeev Premi.
Code:
stock BCK
OPP5: not def. 1.4200 V
beta 14 fix:
Universal CF-Root: Fixed the non-ending row of force closes after flashing the Universal flavour of BCK. The clean XXKPQ version did not show these problems and didn't need a 'fix'.
beta 15:
Universal CF-Root: Modified some permissions to bring it closer to the stock ramdisk
Universal CWM: Created a CWM ramdisk based on CF-root, without most tweaks. You now have three BCK flavours to choose from
Updated to newest UPDATE2 sources by Samsung
Sync bug fix reworked to use new Samsung method from UPDATE2. This may lead to slightly lower standby battery consumption.
Fixed accidental front camera mirroring
Editing smartassV2 settings with busybox 1.20.x and newer no longer leads to reboots. Thanks to loSconosciuto for pointing me to the patch.
Fixed complete crash of WiFi driver when activating WiFi by adapting smartassv2 thresholds
Reverted to the original Google Android toolchain using gcc 4.4.3
Because of the toolchain-switch, the compiler optimizations are now back to -O2 instead of -O3
Credits:
Credits go to the mentioned developers of the cpufreq governors, ganeshbiyer, skin1980 and amit.bagaria for the CF-Root and skin1980 for his repack script. Many thanks to DooMLoRD, amit.bagaria, knzo and loSconosciuto for their help! BCK sources are available on GitHub.
Files:
Attached files:
ODIN-flashable PDA_BCK_XXKPQ_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXKPQ ROMs.
ODIN-flashable PDA_BCK_XXLE4_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXLE4 ROMs.
ODIN-flashable PDA_BCK_CF-root_universal_***.tar with CF-root ramdisk ('Universal CF-root flavour'). For all current Gingerbread ROMs.
ODIN-flashable PDA_BCK_CWM_universal_***.tar with CWM (rooted) ramdisk ('Universal CWM flavour'). For all current Gingerbread ROMs.
Other files (not attached):
Old releases and release candidates can be found on Dev-Host. Use these with caution!
MD5 sum:
Code:
PDA_BCK_XXKPQ_beta10.tar: 83013b2d54c52dddb72deec46b5471de
PDA_BCK_CF-root_universal_beta10.tar: e1e8bcc28c878095618413141b642ec1
PDA_BCK_XXKPQ_beta11.tar: 9eaa6d080f3409c4822e38602bad8efb
PDA_BCK_CF-root_universal_beta11.tar: 93437cf26699dfe595881941b13a6a83
PDA_BCK_XXKPQ_beta12.tar: d9849ae7d9587402aa6465081b4c65a1
PDA_BCK_CF-root_universal_beta12.tar: 2107dfbf33b2838e66007f4319bee14e
PDA_BCK_XXKPQ_beta13.tar: bff3112d3249e951a569148d79643744
PDA_BCK_CF-root_universal_beta13.tar: 1fab51d641a8914e11a81781683d7d7d
PDA_BCK_XXKPQ_beta14.tar: 08cd77964c3d8b54b4c97e59500a0b96
PDA_BCK_CF-root_universal_beta14fix.tar: 6a2cda17362f5a2e6aac7e78dbe94089
PDA_BCK_XXLE4_beta15.tar: 7159e6cd5f2b71bebffcb4d86201b6cf
PDA_BCK_CF-root_universal_beta15.tar: ecfa46b8aec239f1ac246df61dc63477
PDA_BCK_CWM_universal_beta15.tar: 765a5253b0313d41399ea86822cf5f80
Nice i'll try it out ! but m not on clean kpq :\ oh well its worth the shot for thse governors and can u please provide the link to the new source ?
phone boots but the boot animation keeps on repeating ! cf root problem !clean kpq did the trick m in !
Oh!very nice
shriomman said:
Nice i'll try it out ! but m not on clean kpq :\ oh well its worth the shot for thse governors and can u please provide the link to the new source ?
phone boots but the boot animation keeps on repeating ! cf root problem !clean kpq did the trick m in ! but how to root it now ? :\
edit- rooted with soc with psnuter had to instal busybox from stricson and all working just fine
Click to expand...
Click to collapse
Thanks bro for your feedback.
Sent from my GT-I9003 using Tapatalk
over clock to ? ghz?
leongwenjun said:
over clock to ? ghz?
Click to expand...
Click to collapse
it doesnt have oc ! it has special cpu governors which are efficient and fast
tough luck for me mate....
i compile a vanilla kernel which is ~200 kb larger than stock zImage and it doesnt even boot!
also,even i want to update to 2.6.35.14,,,,,,,,,,,,,,how u did it without source?
also(2)lz open an acc. on github!
@sakindia123: Take a look here, update your sources to the new version, and get the new toolchain they use (see readme in the sources).
i followed that link before......
ok i will try with new source
what will happen if we use this ? are there any good feautures ?
it has special cpu governors which are efficient and fast
Now just wait for some days guys. Doomlord, bam, sakindia will show u real power of our device.
This is great! Just one little question, you said this is for a chinese firmware, but you mention KPQ, so it can be put in XXKPQ or not? Anyway sorry for my noob question
vishal24387 said:
Now just wait for some days guys. Doomlord, bam, sakindia will show u real power of our device.
Click to expand...
Click to collapse
U forgot To mention "fuss" dude...
Sent from my GT-I9003 using XDA Premium App
Slynightdark said:
This is great! Just one little question, you said this is for a chinese firmware, but you mention KPQ, so it can be put in XXKPQ or not? Anyway sorry for my noob question
Click to expand...
Click to collapse
It is based on the Chinese source - this includes kernel and android system source. But the kernel is universal (not language specific), and I applied all necessary settings for XXKPQ. Therefore you can flash it on KPQ.
what does a kernel do??
it is the main driving force of a phone that i know.
does it make our phone fast??
how to flash it as i would like to give it a try right away!!
can i roll back to stock kernel after this??
sorry for thr noob question as im new to all this.
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
also do we need to have CWM recovery for this????
or we can do it with the stock recovery menu??
i was just doing some testing and the kernel is stuck at "SAMSUNG" bootanimation after a FRESH FLASH...
any idea?
used on XXKPQ FW
I flash your kernel. From last 5hours no SOD ISSUE. I'm using smartass v2 let's see how will battery I will get from it.
Sent from my GT-I9003 using Tapatalk
Fresh flash of what PDA? Yours, mine, GitHub?
@manrock111: smartassv2 gives me slightly higher battery usage than stock. I want to tweak it, but have problems with my sources at the moment.
XDA_Bam said:
Fresh flash of what PDA? Yours, mine, GitHub?
@manrock111: smartassv2 gives me slightly higher battery usage than stock. I want to tweak it, but have problems with my sources at the moment.
Click to expand...
Click to collapse
sorry... did a fresh install of full XXKPQ FW and now its booting
ok now this is weird... suddenly all of my test kernels have started booting
Update 2013-04-01 (3.1.10-10.4.4.25-that6):
With a small fix for a crash when reading a file in /sys, the revolutionary pre-init system from v5, and a more complete Data2SD package:
http://forum.xda-developers.com/showpost.php?p=39822992&postcount=239
Update 2013-03-24 (3.1.10-10.4.4.25-that5):
The latest experimental kernel is here: http://forum.xda-developers.com/showpost.php?p=39528295&postcount=227
Update 2013-03-05 (3.1.10that4):
The latest kernel is up: http://forum.xda-developers.com/showpost.php?p=38797590&postcount=194
New features: User voltage control and Data2SD auto-detection.
End Update 2013-03-05
Update 2013-02-06 (3.1.10that2):
After positive feedback from testers and due to popular demand, here is my latest kernel with the experimental new "ROW" I/O scheduler. If you want to know more, read the documentation in the patch here: https://patchwork.kernel.org/patch/1862241/ . Please note that this is a rather new development and not yet merged into a mainstream kernel, so it has not been widely tested. However, all results from XDA members were neutral or positive so far.
End update 2013-02-06
Since Asus seemed to have forgotten to release the 10.4.4.25 kernel sources, I reminded them politely - and finally the sources are available for download from their support site!
This is the first kernel ever that I cross-compiled myself - be gentle.
zImage (kernel binary) features:
- Asus 10.4.4.25 base
- fsync control
- ISO 9660 + UDF support (CD/DVD filesystems)
- CIFS (for mounting Windows shares)
New in 3.1.10that2 (2013-02-06):
- ROW I/O scheduler (prioritize READ requests over WRITE requests on eMMC/SD cards) included as default
New in 3.1.10that4 (2013-03-05):
- User voltage control for undervolting
New in 3.1.10-10.4.4.25-that5 (2013-03-24):
- Penguins! (framebuffer console)
New in 3.1.10-10.4.4.25-that6 (2013-04-01):
- No more crash when reading /sys/bus/nvhost/drivers/tegradc/tegradc.0/nvdps
Ramdisk features:
- insecure adbd
- init.d support
- does not set lcd_density (dpi unlocked)
in the -data2sd versions only:
- mount points modified for the Data2SD mod (see http://forum.xda-developers.com/showthread.php?t=1962507)
New in 3.1.10that4 (2013-03-05):
- auto-detection of data2sd - if the microSD card is inserted at boot time and it contains a second partition, it is assumed to be a data2sd partition and mounted as /data. Otherwise, the system is booted with /data mounted to internal storage as usual.
New in 3.1.10-10.4.4.25-that5 (2013-03-24):
- moved auto-detection of data2sd to scripts in /system for easier customization (read the release post for details)
Credits:
- Linux kernel devs and Asus for the base
- Gentoo devs for their easy "crossdev" toolchain-generation tool
- scrosler for the original CleanROM, from where I got the ramdisk mods
- Ezekeel for the fsynccontrol patch (http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__700#entry607555)
- clemsyn, for finding the fsynccontrol patch and integrating it into his kernel
- faux123 for the user voltage control patch which clemsyn integrated into his kernel
- sbdags and buhohitr for testing
- dasunsrule32 for finding the ROW I/O scheduler and testing it with the CM kernel
- snypa for notifying me of dasunsrule32's research
- blackmambazzz for making the ROW scheduler compile with 3.1
Flashable ZIP:
This kernel (and all others in this thread) is compatible with stock-based (Asus Android 4.1.1) ROMs that set lcd_density (dpi) in build.prop - in other words, this is the preferred kernel for CleanROM Inheritance.
2013-04-01: v6: Latest version:
Get it here: http://forum.xda-developers.com/showpost.php?p=39822992&postcount=239
2013-03-24: v5:
Get it here: http://forum.xda-developers.com/showpost.php?p=38797590&postcount=227
2013-03-05: v4:
Get it here: http://forum.xda-developers.com/showpost.php?p=38797590&postcount=194
2013-02-06: (3.1.10that2):
View attachment that-kernel-10.4.4.25-2.zip
View attachment that-kernel-10.4.4.25-2-data2sd.zip (for Data2SD users only)
2013-01-30: Original version (3.1.10that1) without ROW:
View attachment that-kernel-10.4.4.25-1.zip
A version for data2sd users is here -> http://forum.xda-developers.com/showpost.php?p=37392834&postcount=5
Sources:
zImage compiled from stock Asus 10.4.4.25 base with following config and patches:
View attachment config.txt
View attachment ril-include-fix.patch
View attachment fsynccontrol.patch
New in 3.1.10that2 (2013-02-06):
View attachment v4-1-2-block-Adding-ROW-scheduling-algorithm-for-3.1.patch
Boot image repackaged as described here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
(You might now ask "where is the overclocked version"? I decided to start with a known stable base for my first release - if this one turns out to work fine, the oc build comes next.) - for overclocked version, read next post!
Overclocked!
This is 3.1.10that1-oc - the version with clemsyn's overclocking patches. Please note that I only extracted and then applied his patches to the current kernel and typed "make" - I don't understand all the scary frequency and voltage tables, and I don't know how it works in detail. However I got up to 7130 points in this benchmark thingy, and system tuner shows 1.8 GHz, so it appears to do something.
Please note that this is only the kernel, and it does not contain clemsyn's changes for the Asus performance modes. As you may know, the 3 Asus performance modes are activated by running shell scripts in /system/etc named cpu1.sh to cpu3.sh. Clemsyn's kernels replace balanced mode with performance mode, and performance mode with the new overclocked mode. This kernel does not do that, it leaves your modes as they were!
Depending which kernel you were using before, the following will happen:
- Coming from a stock kernel, you keep balanced and performance modes, and the extra overclocking mode can only be activated by executing /system/etc/cpu4.sh. If you want, you can rename cpu2.sh to cpu2_original.sh, cpu3.sh to cpu2.sh and cpu4.sh to cpu3.sh, then you have performance mode as default instead of balanced, and overclocking mode if you activate "performance mode" - same as clemsyn's. If this is too complicated for you, you can either flash clemsyn's kernel directly before this one, or wait until someone repackages this kernel.
- Coming from clemsyn's kernel, performance modes should work as before. Please don't ask me which specific variant of clemsyn's kernels this one is comparable with - he released only one source package, which I used, but many different kernel binaries. I can't recreate other versions without clemsyn releasing sources for those specific versions.
zImage (kernel binary) features:
- all of the above
- Overclocking and voltage control
Ramdisk features:
- same as non-overclocked version
Additional credits:
- clemsyn, for his amazing overclocking kernel
Flashable ZIP:
3.1.10that2-oc with ROW scheduler (2013-02-06):
Internal storage: View attachment 1703857
For Data2SD: View attachment 1704016
3.1.10that1-oc (2013-01-31):
Internal storage: View attachment that-kernel-10.4.4.25-1-oc.zip
For Data2SD: View attachment that-kernel-10.4.4.25-1-oc-data2sd.zip
Sources:
same as non-overclocked version plus this patch extracted from clemsyn's "tfcombofinal" source:
View attachment clemsyn-tfcombofinal-oc.patch
Config: View attachment config.txt
Have fun, and don't fry your tablets!
Excellent work my friend! Will test it out later. :cyclops:
Excellent work my friend...dream comes true. BTW, currently I'm on data2sd, is it possible to make one for data2sd? Thanks.
buhohitr said:
Excellent work my friend...dream comes true. BTW, currently I'm on data2sd, is it possible to make one for data2sd? Thanks.
Click to expand...
Click to collapse
Good idea.
View attachment that-kernel-10.4.4.25-1-data2sd.zip
(Note: This is 100% untested - if you tell me that it works, I'll add it to the OP. ) Now tested by buhohitr, thanks. :good:
Same zImage with the ramdisk from the previous data2sd kernel.
Note: this is not a data2sd installer, it's only a new kernel to drop into an existing data2sd installation.
Working well so far! :good:
_that said:
Good idea.
View attachment 1690048
Note: This is 100% untested - if you tell me that it works, I'll add it to the OP. Same zImage with the ramdisk from the previous data2sd kernel.
Click to expand...
Click to collapse
Great news! Your new data2sd kernel is working very well. All data mountings are correct and fsync is woring wonder! Great job!
1. When PC hook up to device, on PC I see:
a. Internal - ext4 parition on microsdcard
b. Micro - Fat32 partition on microsdcard
c.-SD - Dock SDcard.
2. Disabled fysnc - working wonder, gain 600+ on Quadrant.
I have been using Sandisk Extreme Pro class 10 (95mb/s) and it's very stable (Did not work before with Clemsyn Kernel). With fsync disabled, a gain of 600 point bring Quadrant to 6639 from 5995/6005 without OC. The tablet is super smooth and fast with fsync disabled. I can see the apps are launching faster from stand still, if they already in memory, BAM it's there. Browser also faster, Gallery loaded much faster and I got over 2 thousand pictures. In summary, I'm impress and very happy....just couldn't wait for the OverClock version.. Again, great job _that!! :good::good:
Edit: I will be running this for a week to see if any issue with journaling and fsync disabled on this super fast sdcard. Will report back.
Update 1/30 @ 10:30pm est - After 4 1/2 hrs, this tablet stills running smooth and quick. Very happy with this kind of performance, probably the best to date. What I'm really exciting about is, there still more room for performance....when "_that Overclock kernel" arrived..
tried this on PA, and I get a message, upgrading apps, but then it hangs. Is this to work on all ROMS, or just stock?
gvsukids said:
tried this on PA, and I get a message, upgrading apps, but then it hangs. Is this to work on all ROMS, or just stock?
Click to expand...
Click to collapse
Should be just for stock Cleanrom.
Tried this fantastic kernel in the last 5 hours and it is smooth, had no problem at all. Epic Citadel reports a benchmark of 38.9 fps.
Can't wait to try the OC version of it. Also waiting for the SanDisk Extreme to arrive from Amazon to try out the data2sd too.
Re: [KERNEL] 3.1.10that1 ★ 10.4.4.25 + fsync + ISO9660 + CIFS
I can confirm that data2sd version is working great. Waiting for the OC version. Good job!
So how does one disable fsync?
Flash this kernel, reflash ROM with no kernel option and fsync disable checked, or?
Just flashed this kernel. I have disabled fsync and my tablet has sped up. Thanks for this kernel _that.
---------- Post added at 04:28 PM ---------- Previous post was at 03:34 PM ----------
inSaN1Ty_X said:
So how does one disable fsync?
Flash this kernel, reflash ROM with no kernel option and fsync disable checked, or?
Click to expand...
Click to collapse
1. Reflash CleanRom 3.2.1
2. Disable Fsync during the installer
3. Reboot
4. Wipe Devlink Cache/Cache
5. Flash this kernel
This should disable fsync with this kernel.
Απ: [KERNEL] 3.1.10that1 ★ 10.4.4.25 + fsync + ISO9660 + CIFS
Hello i just want to say thanks, i am using the data2sd version without any problem.
If someone is interested in the kernel changes between 10.4.4.23 and 10.4.4.25 can follow this link to my github.
Looks like Asus has made some changes in the mmc management:
Code:
/*
* SD Workaround: downgrade frequency for seldom specific sdcard
*/
https://github.com/blackmamba97/asus-kernel-tf700t/compare/10.4.4.23...10.4.4.25
@_that I hope its ok that I have used your config because I dont have Cleanrom installed atm and so I cant pull the config.gz
blackmambazzz said:
@_that I hope its ok that I have used your config because I dont have Cleanrom installed atm and so I cant pull the config.gz
Click to expand...
Click to collapse
Sure, that's the point of me publishing all the sources as detailed as I can - take whatever you can use.
By the way, there is a nice script in the kernel sources that extracts a config from a zImage, it's in scripts/extract-ikconfig and you pass a zImage to it as a parameter. Maybe that's useful for you one day.
buhohitr said:
What I'm really exciting about is, there still more room for performance....when "_that Overclock kernel" arrived..
Click to expand...
Click to collapse
myeepad said:
Can't wait to try the OC version of it.
Click to expand...
Click to collapse
ariadnejro said:
Waiting for the OC version.
Click to expand...
Click to collapse
Made for you...
http://forum.xda-developers.com/showpost.php?p=37390637&postcount=2
_that said:
This is 3.1.10that1-oc - the version with clemsyn's overclocking patches. Please note that I only extracted and then applied his patches to the current kernel and typed "make" - I don't understand all the scary frequency and voltage tables, and I don't know how it works in detail. However I got up to 5780 points in this benchmark thingy, and system tuner shows 1.8 GHz, so it appears to do something.
Please note that this is only the kernel, and it does not contain clemsyn's changes for the Asus performance modes. As you may know, the 3 Asus performance modes are activated by running shell scripts in /system/etc named cpu1.sh to cpu3.sh. Clemsyn's kernels replace balanced mode with performance mode, and performance mode with the new overclocked mode. This kernel does not do that, it leaves your modes as they were!
Depending which kernel you were using before, the following will happen:
- Coming from a stock kernel, you keep balanced and performance modes, and the extra overclocking mode can only be activated by executing /system/etc/cpu4.sh. If you want, you can rename cpu2.sh to cpu2_original.sh, cpu3.sh to cpu2.sh and cpu4.sh to cpu3.sh, then you have performance mode as default instead of balanced, and overclocking mode if you activate "performance mode" - same as clemsyn's. If this is too complicated for you, you can either flash clemsyn's kernel directly before this one, or wait until someone repackages this kernel.
- Coming from clemsyn's kernel, performance modes should work as before. Please don't ask me which specific variant of clemsyn's kernels this one is comparable with - he released only one source package, which I used, but many different kernel binaries. I can't recreate other versions without clemsyn releasing sources for those specific versions.
zImage (kernel binary) features:
- all of the above
- Overclocking and voltage control
Ramdisk features:
- same as non-overclocked version
Additional credits:
- clemsyn, for his amazing overclocking kernel
Flashable ZIP:
Internal storage: View attachment 1693162
For Data2SD: View attachment 1693164
Sources:
same as non-overclocked version plus this patch extracted from clemsyn's "tfcombofinal" source:
View attachment 1693163
Config: View attachment 1693166
Have fun, and don't fry your tablets!
Click to expand...
Click to collapse
Excellent. Note I mod Clemsyn's cpu.sh files so that balanced mode is balanced mode which theorectically means I can now make a 1.3 1.8 and a 1.5 1.8 version of this
Off to do some testing.
Looks like Kernel Installer 1.8 is in the making.
I can confirm that oc data2sd version is working great.
Thanks great job :good:
sbdags said:
Excellent. Note I mod Clemsyn's cpu.sh files so that balanced mode is balanced mode which theorectically means I can now make a 1.3 1.8 and a 1.5 1.8 version of this
Off to do some testing.
Looks like Kernel Installer 1.8 is in the making.
Click to expand...
Click to collapse
Nothing like quoting yourself. Yes it works. Now running a 1.3 1.8 GHz version of this kernel
Many thanks _that. Time to thank you with a donation. :good:
Introduction
This kernel is designed to be more stable than the stock kernel, with more features and more performance. Choose any three.
I do not include any changes that have no clear positive effect on these goals.
Features
zImage (kernel binary) features:
- Asus 10.6.1.14.10 base
- Support for Samsung's F2FS filesystem (experimental) and exFAT
- ISO 9660 + UDF support (CD/DVD filesystems)
- CIFS (for mounting Windows shares)
- BFQ I/O scheduler (http://algo.ing.unimo.it/people/paolo/disk_sched/) v7r5; ROW I/O scheduler v4 (https://patchwork.kernel.org/patch/1862241/) and "deadline" is also available
- fsync control (echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled)
- Overclocking up to 1800 MHz, based on clemsyn's patch, configurable clock frequencies for balanced and performance mode
- User voltage control for undervolting
- Crash fixes when reading various files in /sys
- mount space hack from http://forum.xda-developers.com/show...php?p=36889027 allows mounting across Android processes again (e.g. using CIFS Manager)
- NFS v3/v4 client (supports files > 2 GB)
- NFS v3/v4 server as module (untested, needs userspace tools which I haven't yet compiled)
- Framebuffer console at boot (Android penguins!)
- Keyboard dock: support for F1-F12 function keys, special key mappings for CyanogenMod and GNU/Linux (Esc, Insert, Delete, Alt, Windows)
- Support for various USB Ethernet adapters and FTDI serial port adapters
- Kexec-able and able to kexec other kernels
- SELinux is not included for compatibility with the stock ROM's proprietary NTFS and exFAT drivers
- Tethering via dock USB port (untested), see http://forum.xda-developers.com/showpost.php?p=52917184&postcount=2740
Ramdisk features:
- adbd with root access enabled in default.prop, ro.secure=0
- optimized mount options (noauto_da_alloc)
- init.d script support
- USB IDs for all Tegra 3 based Transformer models (init.xx.rc)
- does not set lcd_density (dpi unlocked), must/can be set in /system/build.prop instead
- preinit system for easy ramdisk customization without repacking or reflashing the kernel: if exists, runs a custom script "/system/boot/preinit" before Android init, e.g. for adding Data2SD detection, ROM2SD, etc.
- File-system auto-detection for use in preinit scripts
Installation/Download
Flash the zip in recovery and reboot; the bootloader will move the kernel to its final place while showing a blue progress bar.
Compatibility
This kernel is compatible with the 10.6.1.14.x bootloaders and stock-based (Asus Android 4.2.1) ROMs that set lcd_density (dpi) in build.prop - in other words, this is the preferred kernel for CleanROM Inheritance. It also works with other ROMs up to Android 4.4 (requires a preinit script to provide the corresponding ramdisk files). The kernel is derived from the original TF700T sources but is known to work also on the TF300.
MD5 sum:
You don't need an MD5 sum. Enable "Zip file signature verification" in TWRP instead - it checks the SHA1 checksum embedded in the archive, which is both more secure and more convenient.
Download the latest version here -> http://forum.xda-developers.com/showpost.php?p=55513454&postcount=484
Credits
- Linux kernel devs and Asus for the base
- Gentoo devs for their easy "crossdev" toolchain-generation tool
- scrosler for the original CleanROM
- sbdags for CleanROM Inheritance
- Ezekeel for the fsynccontrol patch (http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__700#entry607555)
- faux123 for the user voltage control patch
- clemsyn for the overclocking patch. I still use his frequency and voltage tables but rewrote the EDP handling.
- Hundsbuah for decoding the EDP limit tables and finding an f2fs patch that applies cleanly to our kernel
- cogano for improving the dock key mapping for native Linux
- wenchien for cherry-picking lots of f2fs updates from later kernels
Development Info
Guide for unpacking and repacking kernel blobs and boot images -> http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
XDA:DevDB Information
_that-kernel, Kernel for the Asus Transformer TF700
Contributors
_that
Kernel Special Features: Stock kernel with more stability, more features and more performance. Choose any three.
Version Information
Status: Stable
Current Stable Version: that11
Stable Release Date: 2014-09-17
Current Beta Version: that11
Beta Release Date: 2014-09-17
Created 2014-02-17
Last Updated 2014-10-14
Changelog/History
2014-09-17: 3.1.10-that11
New features:
- enable tethering via dock USB port (untested)
- fix for the Towelroot exploit
- lots of f2fs updates from mainline kernel, thanks to wenchien
- new BFQ (budget fair queueing) I/O scheduler
- added FTDI USB serial support
- exFAT filesystem support from Samsung
download -> http://forum.xda-developers.com/showpost.php?p=55513454&postcount=484
2014-05-14: 3.1.10-that10
New features:
- Removed the special overclocking mode (system_mode 3) - instead, clock speeds for balanced and performance modes are now user-configurable.
- More options for dock key mapping for GNU/Linux and autorepeat
- File system auto-detection in init for use in preinit script
download -> http://forum.xda-developers.com/showpost.php?p=52659251&postcount=446
2014-03-29: 3.1.10-10.6.1.14.10-that9-oc
New features:
- Dock function keys and CyanogenMod-compatible mode for dock keys
- Support for various USB Ethernet adapters
download -> http://forum.xda-developers.com/showpost.php?p=51486800&postcount=414
2014-02-17: 3.1.10-10.6.1.14.10-that8-oc
New features:
- F2FS (Flash Friendly) filesystem by Samsung (experimental, may eat your data)
- USB mass storage support (needs a computer that understands ext4 (i.e. Linux))
- Enabled dual filenames on FAT filesystems for compatibility with some devices
download -> http://forum.xda-developers.com/showpost.php?p=50408485&postcount=396
2013-11-22: 3.1.10-10.6.1.14.10-that7-oc
Security config options disabled to restore compatibility with proprietary exFAT/NTFS modules. Details and download -> http://forum.xda-developers.com/showpost.php?p=47743629&postcount=358
The Data2SD auto-detection add-on is here: http://forum.xda-developers.com/showpost.php?p=40522097&postcount=56
Or if you prefer Data2SD with internal /sdcard: http://forum.xda-developers.com/showpost.php?p=41305526&postcount=159
(these add-ons are unchanged since they were released, so if you already have them installed, you don't need to reinstall when updating the kernel)
2013-11-11: 3.1.10-10.6.1.14.10-that6-oc
Now with 100% more penguins! Get it here -> http://forum.xda-developers.com/showpost.php?p=47361802&postcount=325
2013-09-06: 3.1.10-10.6.1.14.8-that5-oc
Overclocking is back! Get the new version here -> http://forum.xda-developers.com/showpost.php?p=45332265&postcount=263
2013-07-03: 3.1.10-10.6.1.14.8-that4
The latest version is here -> http://forum.xda-developers.com/showpost.php?p=43199757&postcount=237
New kernel features since -that2
- rebased on Asus source release 10.6.1.14.8
- mount space hack from http://forum.xda-developers.com/show...php?p=36889027 allows mounting across Android processes again (e.g. using CIFS Manager)
- some more sysfs crash fixes
- "deadline" I/O scheduler added (default is still ROW)
- NFS v3/v4 client (supports files > 2 GB)
- NFS v3/v4 server as module (untested, needs userspace tools which I haven't yet compiled)
New ramdisk features since -that2
- fstab: optimized mount options (added noauto_da_alloc)
- added init.xx.rc files for other Transformer models
2013-06-25: 3.1.10-10.6.1.14.8-that3
preview release, see http://forum.xda-developers.com/showpost.php?p=42915255&postcount=201
2013-04-11: 3.1.10-10.6.1.14.4-that2
The Asus source release was surprisingly fast this time. I ported all my popular non-intrusive stock kernel improvements (http://forum.xda-developers.com/showthread.php?t=2125783) and recompiled the kernel. Special thanks to buhohitr for testing this release!
I couldn't get the framebuffer console to work, so no UltraCleanROM support for now.
(-that2 downloads deleted)
Documentation
This kernel supports a few additional parameters. As usual these can be set from a root shell or an init script - for details how to do that, read a tutorial about using the Unix/Linux command line.
fsync
To turn off fsync (warning: read this and this before):
Code:
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
To turn it on, write 1 instead of 0.
Clock speeds and overclocking
Note that the special overclocked system_mode 3 has been removed in -that10. There are now only 3 modes, as in the stock kernel (powersave, balanced, performance). To enable overclocking beyond 1700 MHz (or 1600 MHz for more than one core), you need to override the EDP limit:
Code:
echo 1 > /sys/module/cpu_tegra/parameters/override_edp
To set clock speeds for balanced and performance mode, for example:
Code:
echo 1300 > /sys/module/cpu_tegra/parameters/override_mhz_bal
echo 1800 > /sys/module/cpu_tegra/parameters/override_mhz_perf
User voltage control
works exactly like in upstream implementation - ask me to update this if you want to know more.
Keyboard dock tweaks
CyanogenMod has a slightly different mapping for some of the dock function keys. To enable compatibility with CM and CM-based ROMs:
Code:
echo 1 > /sys/module/asusdec/parameters/cm_mode
Function keys F1 to F12 can be entered using right Alt/AltGr and the keys from "Toggle WiFi" to "Next Track". This might only work in native Linux and maybe CM.
For native Linux users, I added additional parameters:
Code:
echo $flags > /sys/module/asusdec/parameters/key_flags
echo 1 > /sys/module/asusdec/parameters/key_autorepeat
where $flags is a number between 0 and 15, by combining these bit flags:
1 = inverts the meaning of Alt for function keys (F1-F12 without Alt, and special functions with Alt. Also, Mute is Insert and Lock is Delete.)
2 = Back is Esc
4 = Search is left Alt
8 = Home is left Windows (aka "Meta" aka "Super_L")
Thanks so much for the RIL patch that seems like fixed my compiling problems lets see
IM just a noob here trying to compile and learn hehe:victory:
EDIT: Yes it compiled
Now I ask myself why Asus released a bad source code lol?
maxrdlf95 said:
Thanks so much for the RIL patch that seems like fixed my compiling problems lets see
Click to expand...
Click to collapse
The RIL include fix is old news - it was already required in the 10.4.4.x kernel, and it's published in my 10.4.4.25 kernel release thread.
maxrdlf95 said:
IM just a noob here trying to compile and learn hehe
Click to expand...
Click to collapse
Learning by doing is still the best way. If you manage to get your own kernel installed and running (if not, read my blob repacking guide), then you have definitely left the "n00b" status.
maxrdlf95 said:
Now I ask myself why Asus released a bad source code lol?
Click to expand...
Click to collapse
Maybe they are using an older compiler that behaves differently.
Thanks man I already knew how to make the blob file and put the signing in, I used to help clemsyn packing its kernel when he didnt have time and well I did it tonight :good: I compile my kernel thanks now will learn how to make it with linaro
EDIT:
P.D I left the n00b status some time ago lol
To install this kernel, do I need to flash both the flash zip and the patch for sbdags' Asus stock rom . I have a US bootloader and a WW rom
lartomar2002 said:
To install this kernel, do I need to flash both the flash zip and the patch for sbdags' Asus stock rom . I have a US bootloader and a WW rom
Click to expand...
Click to collapse
Which patch for sbdags' stock ROM?
_that said:
Which patch for sbdags' stock ROM?
Click to expand...
Click to collapse
In the OP the line just brlow where the krrnel flash zip is.
lartomar2002 said:
In the OP the line just brlow where the krrnel flash zip is.
Click to expand...
Click to collapse
That patch has nothing to do with sdbags roms,that patch contains all the changes made to the original kernel and it's for development only (you can apply that patch to the original or own 4.2.1 kernel source).
Pretoriano80 said:
That patch has nothing to do with sdbags roms,that patch contains all the changes made to the original kernel and it's for development only (you can apply that patch to the original or own 4.2.1 kernel source).
Click to expand...
Click to collapse
Ok, so I only need to flash the kernel zip for 4.2?
lartomar2002 said:
Ok, so I only need to flash the kernel zip for 4.2?
Click to expand...
Click to collapse
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Pretoriano80 said:
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Click to expand...
Click to collapse
In other words: either not be old or have your reading glasses at hand?
Not here. DPI is still at 240.
Flashed kernel, UV 75mV and all looks ok. :good:
Pretoriano80 said:
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Click to expand...
Click to collapse
Snah001 said:
Not here. DPI is still at 240.
Flashed kernel, UV 75mV and all looks ok. :good:
Click to expand...
Click to collapse
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Pretoriano80 said:
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Click to expand...
Click to collapse
I had already changed the build prop file to set dpi to 213 and when I flashed this new kernel it held the setting.
Obviously if you edit the build prop file then your setting remains however if you haven't then maybe it will change to 160. This I'm not sure about since if the default set by stock ROM is 240 and this is what we edit, why would it change to 160?
Pretoriano80 said:
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Click to expand...
Click to collapse
Yes, just flashed kernel as always
Sent from my Asus Infinity TF700 with Dock
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
calvinb1 said:
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
This
abbea13a9c1f9efa46fd4235a6a2f1b9
eckka said:
Obviously if you edit the build prop file then your setting remains however if you haven't then maybe it will change to 160. This I'm not sure about since if the default set by stock ROM is 240 and this is what we edit, why would it change to 160?
Click to expand...
Click to collapse
For some unknown reason, the default build.prop on the TF700 contains the line "ro.sf.lcd_density=160" - the correct 240 dpi is set by the stock kernel's ramdisk. I removed the latter, so the setting in build.prop takes effect.
calvinb1 said:
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Click to expand...
Click to collapse
Ah, I forgot to mention this, which I now added to the OP:
You don't need an MD5 sum. Enable "Zip file signature verification" in TWRP instead - it checks the SHA1 checksum embedded in the archive, which is both more secure and more convenient.
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678873&postcount=472
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0 ROMs. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
IMPORTANT NOTES:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8.3), CM 10.1.x and CM 10.2 (since 1.8.3) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM, P31xx only: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV
brolee93 for latest P51xx Samsung stock boot image
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch blackhawk version attached, PhilZ Touch 5.08.5 attached at post #3
NEXT kernel beta release attached
NEXT tool: http://forum.xda-developers.com/showthread.php?t=2285366
exFAT support files for CM/CM based ROM: http://forum.xda-developers.com/showthread.php?t=2285366 post #2
Todo:
More features in NEXT tool
Special Thanks:
@behemot24, @shakatu, @ironmaskusa, @tetakpatak
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.4
Created 2014-09-21
Last Updated 2014-10-29
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
21/10/2013 1.8.3 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
10/08/2013 1.6.3 -> 1.8.3:
Initial upcoming Samsung 4.2.2 support
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!
Updated to upstream Linux kernel 3.0.41 (incremental patch)
The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.5 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcahe memory corruption problem fixed!
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 new busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM default zRAM size 26% RAM size. Following CM's standard, user can set zRAM value for example to 30% by typing "setprop persist.service.zram 30" over Terminal Emulator or over "adb shell setprop persist.service.zram 30". CM user can use Settings application: Performance - Memory management - zRam.
Swappiness value changed to 90
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRAM support optimized for Android, utilizing the new lzo library.
cleancache support with working zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-22/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
12/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. You must update both 1st and 2nd ROM to renew both ROM vendor binaries!
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
NEXT users, please update your kernel to 1.3 version to avoid filesystem corruption risk on Samsung stock/stock based ROM! Please read Dual Boot FAQs how to update your kernel!
01/06/2013 beta -> 1.3:
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P31xx, that's way this port version directly jump to 1.3
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz. Non OC version as an addon
Both version tested on P3100 (remember, I have no access to P51xx device). Booted, upscale graphics, touchscreen not work, wrong orientation sensor, swapped volume button, got 1280x800 screenshots :laugh:
30/05/2013: Initial beta release.
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
http://forum.xda-developers.com/showthread.php?t=2285366 post #4.
Was waiting for this :victory:
Sent from my GT-P5110 using XDA Premium HD app
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button or better my DTM button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Dual Boot FAQs #29.
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
brolee93 said:
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
Click to expand...
Click to collapse
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Running smoothly for Zap Blaster.
ironmaskusa said:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Click to expand...
Click to collapse
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:
shakatu said:
Running smoothly for Zap Blaster.
Click to expand...
Click to collapse
Really? And all your init.d scripts removed by NEXT
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
shakatu said:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.
Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK.
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
behemot24 said:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
Click to expand...
Click to collapse
For free A lot of clicks to install NEXT package but why people missed to click my Thanks button
EDIT:
This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
rap3rman said:
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Two apps I never use on my tablet, so I haven't tested them...
ketut.kumajaya said:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
Click to expand...
Click to collapse
yeah ok i see this .
can you add Stweaks support ?