Android OS Forum banner
1 - 16 of 16 Posts

· Premium Member
229 Posts
The Launchpad kernel works on both 3G/4G and Wifi Only Xooms​

***This Kernel is for 3.1 and 3.2 Xooms***

***Forked from AOSP***​

With added overclock, microSD, and other features made possible from the hard work of Bigrushdog, Coolbho3000, Solarnz, Kcrudup, and Cybertronic​

-Launchpad 1.3.0-

***1.3.0 Plays Nice With 3.1, 3.2, Tiamat 1.1, and Tiamat 2.0***​

Please see below posts for Special Instructions!!!

As a reminder you must be unlocked and rooted!

Install Instructions:

There are a few different ways to do this, this is what I do-

1) Download ROM Manager (Free or Paid)
2) Download the zip from the link below
3) Move zip to your external SD card
A- Using a file explorer ( ex. Root Explorer), copy and paste the .zip file to your external sdcard (/sdcard/external)
B- Put the zip on your SD card using your PC
4) Open Rom manager
5) Press the second button (Reboot Recovery)
Xoom will boot into recovery
6) Use volume rocker to select install zip from sdcard (Press power button to confirm)
7) Use volume rocker to select choose zip from sdcard
8) Select the zip file placed on the sdcard
9) Select yes
Xoom will flash file and put you back onto recovery screen
10) Select Reboot
11) Sit back and bask in the glory



Launchpad 1.3.0 Gemini-


Launchpad 1.3.0 N Gemini (Stock clocks for GPU and some other core clocks (sclk, hclk, vde)-

Add On's-

Flash any of these after the kernel



Big thanks to TDR for all the hard work!!!​

+Source can be found on Github-

Follow me on Twitter or Google+ @SteadyHawkin for breaking kernel news, and other Xoom goodness!!!

Link to my OP can be found here-

· Premium Member
229 Posts
-Special Instructions-

This version of Launchpad comes packed with a maximum CPU frequency of 1.7GHz and user adjustable voltages for each frequency. Use these features responsibly! Do not select "Set on boot" unless you are confident the settings you chose are stable! Always make backups!

How to use the voltage control:

The stock frequencies and voltages in a kernel are not optimal for everyone. Userspace voltage control lets you either 'undervolt' (to save power) or 'overvolt' (to try and stabilize) any given CPU frequency to meet your needs.


The easiest way to adjust these voltages is by using the app "Pimp my Cpu", available either from the Market or xda ([APP] 24 June 2011 : Pimp My Cpu 3.0 (OC/UV kernel control tool) - xda-developers). This app will let you to set an undervolt amount for each possible frequency, as well as fill some of the basic overclocking roles of a tool like SetCPU or Droid Overclock.
Note: at this moment, the app "Voltage Control" is not compatible with Launchpad 1.2.0.


Unfortunately, Pimp my Cpu does not do overvolting, so you need to execute a shell command to set an overvolt amount.
Say for example 1600MHz isn't quite stable, and you want to give it a little help. From either adb shell or Terminal Emulator, execute the following commands:

echo "0 -25 0 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

The second line has a series of 13 numbers, mostly zeros. They represent the number of millivolts to subtract from the default voltage of each possible frequency, starting from the higest (1700MHz) to lowest (216MHz). So in the above example, we apply a negative 25 millivolt undervolt ( which transleted to a 25 millivolt overvolt) to the second fastest CPU frequency (1600MHz). Note that the minimum voltage is 770 millivolts and the maximum voltage is 1400 millivolts. If your new voltage exceeds these limits, it will not work.

Here is an example of bumping up 1500, just so you get how its done:

echo "0 0 -25 0 0 0 0 0 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

In Pimp my CPU, you will see the following as a result of the first command


· Premium Member
229 Posts
-Partial Changelog-

1.3.0 'Gemini' rc6 (Official Release)
-Fixed many installer bugs for 3.1 and 3.1-international
-Fixed FC in Storage settings under Tiamat ROM 2.0

1.3.0 'Gemini' rc5 (Test)
-Revamped installer again
-Improved (but still not tested) support for international Xooms
-Improved support for Tiamat ROM 1.x and 2.x
-Packages are now signed properly

1.3.0N 'Gemini' rc4 (Test)
-3.1: Fixed small error in dvfs; problem only in the N kernel for Android 3.1 - all others remain unchanged

1.3.0/N 'Gemini' rc3 (Test)
-Minor fixes for vold (USB OTG mounting works)
*3.2: USB drives mount at /mnt/usbdisk, symlink at /usbdisk
*3.2: Micro SD card symlinked at /sdcard2
*Updated tun and usbwwan add-ons
**Reminder: These add-ons will install drivers, but won't load them automatically. It's up to you to know how to use them

-All new "universal" charging LED disabler, for people who hate that light. v3 now extracts and edits the current ramdisk image in recovery.

1.3.0 'Gemini' rc2 (Test)
-Revamped installation script
**Removed unnecessary feature code (OV) from build string
-(Experimental!) Support for non-US 3.1 Xooms with SD support (e.g. Australian 3G Xooms)
**Requires stock boot and vold. If a US kernel has been flashed (causing FCs in Storage settings), flash stock boot.img and system.img, update again to 3.1 if necessary, then flash this kernel (otherwise it will not work!)

1.3.0 'Gemini' beta10a (Test)
-Now compatible with Android 3.2
-Improvements to installation script
-Upstream patches from android-tegra-2.6.36
-Includes updated kernel for Android 3.1 (without the upstream patches)
*Fixed compatibility (again) with current version of SetCPU
-Added sysfs switch to reverse frequency & voltage tables if needed (set /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table_bigendian to 0)
**Removed unnecessary source tree label (athm1) from build string

1.2.3/N-rev2 (Official Release, minor)
-busybox is back
**Kernel is the same as Launchpad 1.2.3, no need to update if 1.2.3 is working

1.2.3/N-rc3 (Official Release)
-Cleanup after older beta

1.2.3/N-rc2 (Test)
-Fixed broken installer in beta10a
-Fixed incorrect nominal voltage values leading to instability

1.2.3/N-beta10a (Test)
-Yet more alterations to dvfs

1.2.3/N-beta9a (Test)
-Small correction in detectrom script, init.stingray.rc

1.2.3/N-beta9 (Test)
-Now compatible with both stock ROM and Tiamat ROM 1.1

1.2.3/N/T-rc1 (Test)
-Tweaked updater script
-Updated addons

1.2.3/N-beta6 (Test)
-Changed CPU voltage interface to be compatible with SetCPU and Voltage Control (in line with the FakeShmoo Tegra 2 kernels)
**The voltage table is now reversed (Low frequencies first)! The installer will try to remove any saved voltage scripts, but it is recommended to remove any voltage tweaks first and reapply them after installation

1.2.3N-beta5 (Test)
-Stock clocks for GPU and some other core clocks (sclk, hclk, vde)
**Use this if you experience graphical corruption, instability, lockups, heat problems or just want to save some battery

1.2.3-beta5 (Test)
-Added interface to see CPU voltage constraints
-Improved handling of init.d scripts and added support for init.local.rc (thanks to bigrushdog, solarnz, CyanogenMod team)
-Cleaned up dvfs with respect to nvidia's implementation

1.3.0-beta8 (Test)
-Removed NTFS support from kernel (a module will probably be brought back later)
-Added an interface to adjust sclk frequency
*Location: /sys/devices/system/cpu/cpu0/cpufreq/sclk_max_frequency_offset
**For the moment, it will default down to the stock (240MHz, -60 from the overclocked 300MHz).
***This is a temporary interface, subject to change

1.2.2-rc0 (Test)
*Fixed installer to work with Tiamat ROM 1.0
-Upstream patches for Apple Magic Trackpad, mmc power management
*Small tweak to interactive gov
*Updated add-ons
-New add-on: request for alternative micro SD card mount-point at /data/media/DCIM (so camera photos/videos go on the micro SD card)

1.2.1-rc1 (Official Release)
-USB Mass Storage mode (thanks kcrudup)*
*Requires dinomight's USB Mass Storage Tool from the Market-
-Some code cleanup
-Updated add-ons

1.2.0-rc1 (Official Release)
-Configured for USB tethering support (thanks solarnz)
*Updated add-ons

1.2.0-rc0 (Test)
-Cleaned up voltage control a little, added some protections
-Debug spam
*New method of disabling the charging LED

1.2.0-beta5 (Test)
-Initial, hacky implementation of user controlled voltage
*This kernel has a lot of debug code, performance may suffer

1.2.0-beta4 (Test)
-Added 1.7GHz CPU step, working this time
-Tweaked dvfs, frequency tables a bit

1.1.0- (Official Release)
-Switched to more stable major.minor.revision-extra versioning system
-Re-enabled HIGHMEM, GPU seems faster this way (at the expense of a little RAM)
-Updated add-on files

1.0.4 (Test)
-Built with updated version of compiler
-Fix for incorrect BogoMIPS value on second CPU core
-Hack for loops_per_jiffy value when overclocked

1.0.3 (Test)
-More adjustments to CFS CPU scheduler, experimenting with different values

1.0.2 (Test)
-Minor tweaks to interactive governor and CFS CPU scheduler

1.0.1 (Test)
-Added support for executing shell scripts on startup from /system/etc/init.d/ (Allows for important changes to be applied at boot e.g. the charging LED can be disabled with a small patch)
-Installer now also includes a compatible version of busybox

1.0 (Official Release)
-New Kernel drops under name
-Fixed installer to correctly clean up old kernel modules from /system/lib/modules before installing new ones
-Fixed issue with selected CPU frequency getting reset to max**
-Extended frequency table to add 1.6GHz CPU
-Fixed lockup/reboot on wake (caused by bad CONFIG_HZ)
-Fixed broken 3G (caused by missing drivers)+

TDR (First 3.1 Kernel)
-Initial un-named release

**When the Xoom goes to sleep, it shuts off the second of its two CPU cores to save power. When it wakes up again, it reloads the previous configuration but the selected frequency gets reset. TDR has patched it to use the same frequency as the first core (which should always be awake).

+If your 3G isn't working before you flash this kernel, please flash another kernel that does have working 3G (or flash BRD's 3G boot image for Tiamat 1.4.2) before flashing this one.
1 - 16 of 16 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.