Originally Posted by travisross69

What is the difference of installing this kernel or using Rom Toolbox and simply over locking?

Rom Toolbox/SetCPU/or any other do that while booting, at every boot it set frequency to desired one(one you selected). But with this kernel its preset inside kernel.

Updated new kernel 3.0.8 in my mediafire folder.
It is not compiled by me, so is set to normal frequency, not over-clocked.

Kernel 3.0 did not work for me with 3-15 nightly. Cleared all cache then after installing kernel it stayed on android is updating and never loaded. Forced a reboot and it stayed on boot animation running and never loaded.

Originally Posted by kingtuk1

Kernel 3.0 did not work for me with 3-15 nightly. Cleared all cache then after installing kernel it stayed on android is updating and never loaded. Forced a reboot and it stayed on boot animation running and never loaded.

Logcats of boot help more then just saying it bootloops.

Edit: http://pastebin.com/FXmwzY0B

That seems like your touchpad booted up fine for first time, as it came to "Android is Updating" screen, so kernel is loading up, need to test it more, and solve problems.

I/ServiceManager( 190): Waiting for service media.player...
I/ServiceManager( 190): Waiting for service media.audio_policy...
I/ServiceManager( 190): Waiting for service media.player...
I/ServiceManager( 190): Waiting for service media.audio_policy...
W/IMediaDeathNotifier( 190): Media player service not published, waiting...
I/ServiceManager( 190): Waiting for service media.audio_policy...
I/ServiceManager( 190): Waiting for service media.player...

seems like needs additional commits in main rom to get it working, or need modules to be added for audio

I applied update to "[ROM][MAR14][RC1] CM9 with Cornerstone" Nightly 3-14 build and it wouldn't boot after the kernel was selected. Told me to hit menu to continue.

I wiped all partitions over and over and reinstalled just the ROM, not sure if he includes the kernel in there (dont want to open the install file and check).

In Moboot I've selected CyanogenMod to boot because yours doesn't load. Downloaded the latest 3.0.8 kernel from your MediaFire as well. I'll try it again and see.

"Checking uImage.. Invalid Size"
"BOOT FAILED!"

I'm at work right now so I can't run ADB and get logcats until later.

People sorry for not working kernel. Image invalid size comes due to having 2 kernel in your touchpad, you need to boot up into WebOS and delete one, if you are coming from other roms, it supports only CM9 and nightlies/kangs of it.

Please use normal kernel, I am removing 3.0.8 until I fix it up.

Originally Posted by bhanvadia

People sorry for not working kernel. Image invalid size comes due to having 2 kernel in your touchpad, you need to boot up into WebOS and delete one, if you are coming from other roms, it supports only CM9 and nightlies/kangs of it.

Please use normal kernel, I am removing 3.0.8 until I fix it up.

I haven't gone in to WebOS since it was 3.0.4 lol there's no easy way to delete it through adb?
Sent from my SAMSUNG-SGH-I727 using XDA

Originally Posted by LinuxNewb

I haven't gone in to WebOS since it was 3.0.4 lol there's no easy way to delete it through adb?
Sent from my SAMSUNG-SGH-I727 using XDA

Would have to mount /boot in CWM, then use it to delete whatever uImage you do not need then flash the older kernel in this thread.

Originally Posted by Nburnes

Would have to mount /boot in CWM, then use it to delete whatever uImage you do not need then flash the older kernel in this thread.

The 2nd half of NMSU vs Indiana just started. I went to UNM so I want NMSU to lose After pizza and basketball ill tweak the boot.

So how did you gather your logcats? I tried doing it through adb on my Linux machine and CWM recovery since I couldn't boot to the OS. I got an /sh/command error. I also couldn't do su


Sent from my SAMSUNG-SGH-I727 using XDA

Originally Posted by LinuxNewb

The 2nd half of NMSU vs Indiana just started. I went to UNM so I want NMSU to lose After pizza and basketball ill tweak the boot.

So how did you gather your logcats? I tried doing it through adb on my Linux machine and CWM recovery since I couldn't boot to the OS. I got an /sh/command error. I also couldn't do su


Sent from my SAMSUNG-SGH-I727 using XDA

I had no issue. Just ran adb logcat on 3.0.8 kernel and newest nightly.