[Galaxy Tab 8.9 Android Development] _motley:
DEVELOPMENT DISCONTINUED

Disclaimer:

You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!

_motley kernel:

Current version features:

OC support (overclock) - frequencies: 1.200, 1.400, 1.504, or 1.600Ghz (recommend 1.4 or 1.5GHz). Default clock speed is stock@1.0GHz

UV support (under-volting)

I/O schedulers: optimized deadline (default) and noop

Governors: optimized interactive, on demand, conservative, and performance

vfp, vfp3, vfpv3d16, thumb, thumbee, swp, fastmult, edsp, half

USB charging enabled

JRCU implemented - RCU for SMP with a single CPU garbage collector

Auto-group scheduling

Built in cifs, NTFS, Xbox controller, tun, PS3, joystick, mouse support

Encryption features CONFIG_DM_CRYPT, CONFIG_BLK_DEV_CRYPTOLOOP, and CONFIG_KEYS

Stock hardware/software is all working with no known issues (Camera, GPS, WiFi, sound, headphones, sensors, market, video/youtube etc.)

Prerequisites:

ROM must be based on the stock Galaxy Tab 8.9 with TouchWiz (stock and Overcome ROMs have been tested)

ROM must be rooted and have CWM installed.

Make sure you

backup your boot.img

so you can flash your stock kernel back. You should have a full CWM backup anyhow.

An app like SetCPU if you want to overclock(OC) or under volt (UV). I recommend only overclocking up to 1.4 or 1.5 GHz. Try 1.4 GHz first and see if it works for your tab.

Make sure you download the correct version for WiFi or 3G (3G only supported on Android 3.2).

Make sure you download the correct version for Android 3.1 or 3.2.

Android Honeycomb 3.2

Version v2d for Android HC 3.2

Add "autogroup" scheduling (for some background see: http://www.linuxfordevices.com)

Add support for LUKS and other file encryption utilities (CONFIG_BLK_DEV_CRYPTOLOOP=y and CONFIG_KEYS=y). Ext2 formatted loop devices should work now, but still no luck FAT12 8.3 volumes. Let me know how it works! (thanks ZeroPDA)

Misc merges\bug fixes from Nvidia repo (tegra\video\hdmi fixes, ext4 memory leak fix, interactive gov div\0 fix etc.)

v2d (7310 WiFi) View attachment 805516 MD5 640af1d30eff11124f17b7fcb4c6201e

v2d (7300 3G) View attachment 805517 MD5 640af1d30eff11124f17b7fcb4c6201e

Version v2c for Android HC 3.2

WiFi only feature addition - added CONFIG_IP_ADVANCED_ROUTER=y to properly support Cisco VPN (VPNC Widget). This was not required for 3G as it already has this kernel feature. Thanks to questionmark for providing the info and testing the change for us.

UV bug fix - v2a introduced a UV issue where it was no longer subtracting the UV values even though they were set properly in sysfs by SetCPU etc. Thanks to Crashdown12 for reporting.

Important - I recommend removing the option to set UV on boot before installing this new version, just in case you were down to unstable voltages.

v2c (7310 WiFi) View attachment 800779 MD5 cbfdee00b5ce514bef88e4230f7d0694

v2c (7300 3G) View attachment 800780 MD5 bce4881b2716f410b2903f96fe347271

Version v2b for Android HC 3.2

USB charging is now enabled like the GT10.1 (thanks pershoot, stefansaraev). See the following for usage: how-to (thanks dpakrr)

Performance: implemented JRCU, an RCU for SMP with a single CPU garbage collector so that each and every CPU doesn't periodically participate in RCU garbage collection. This is popular in the Android kernel space since dual CPUs have come about (thanks Joe Korty).

Performance: added optimized deadline i/o scheduler which is now the default since it is great for SSD (thanks morfic)

Added switch to turn off TouchWiz at the kernel level (not really relevant until someone tries to build a vanilla ROM)(thanks pershoot)

v2b (7310 WiFi) View attachment 797542 MD5 3446574b2024897e41bad69f7c699aca

v2b (7300 3G) View attachment 797543 MD5 d299579a1de0d1469bfcb99ed6afc1d4

Version v2a for Android HC 3.2

Same features as v1i kernel, but now works for HC 3.2

Now a version for P7300 3G

v2a (7310 WiFi) View attachment 791040 MD5 59bfb8b8f213517676e06b6d69f35080

v2a (7300 3G) View attachment 792959- MD5 b5b6ab4f3dffe29dce5a83f32dd7eba6

Android Honeycomb 3.1

Version 1.0i changes (current for Android 3.1):

Governor default changed to OnDemand, but only so we can properly set back to the preferred interactive governor on boot using SetCPU and other tools (let me know!).

I/O schedulers: NOOP now the default (minor read/write improvements), CFQ still available, Deadline removed for now.

Starting voltages increased for 1.504 GHz and above due to some instability issues reported. I recommend you UV 25mV or so if you already achieved stability as it was increased by 50mV. Higher than 1.5GHz is still experimental and not recommended. I have been able to run at 1.6GHz for the first time in this build.

v1i - View attachment 785156 - MD5 ea77e46967aa4c917e8dd8c429dca724 (current for Android 3.1)

Version 1.0h changes (beta 1):

Touchscreen lag fixed. Firmware downgrades prevented within Melfas touchscreen driver.

UV bug fix, no known issues.

Governor fixes, SetCPU seems to set properly on boot now (edit: still some issues setting on boot depending on SetCPU configuration)

Version 1.0g changes (alpha 2):

Overclock to 1.504GHz+ (only 1.5 is stable, over is experimental only)

UV (undervolt) support (experimental, still in testing)

NTFS and Xbox now built-in. No longer need to mess with loading modules.

Applied some upstream kernel patches.

Version 1.0c (alpha 1/first release):

Based on Samsung open source kernel from opensource.samsung.com

Overclock to 1.2GHz or 1.4GHz (a future version will likely be able to clock to 1.504Ghz)

Installation Instructions

Backup with CWM

Put the zip on your sdcard

Flash zip file from CWM

Install SetCPU and use to set governor to "interactive" and desired OC frequency (recommend 1.4 to start). The default governor has been set to On Demand on purpose even though it is not the recommended governor to use in SetCPU. Setting the recommended interactive governor will help SetCPU trigger the instructions to sysfs causing it to take hold. Sometimes it is finicky and a reboot can help once you have the interactive governor set with your desired frequency.

Optional: if you need or want to restore your original kernel, restore ONLY your boot.img from the CWM advanced recovery option.

Thanks go to:

pershoot for all his hard work on the 10.1 kernel. I used his kernel as a working guide and used his delivery method (Anykernel)

alterbridge86\Overcome for CWM.

Koush for the Anykernel delivery method.

Samsung for releasing the source like they should

Tiamat team, RichardTrip\roggin and NVidia for their open source git repositories.

All the testers!

Let me know if I forgot somebody!

Git repository:

https://github.com/motley-git