Develop Bugs

Overclocked kernel (2.6.27) - STABLE - "Kanged the code"

Introduction & Performace
I compiled a Hero 2.6.27 kernel with an overclock arround 710 MHz.
It's working perfectly for me, but I don't know how your devices will perform with it.
So be careful.
I won't provide the kernel binary nor an update.zip nor a boot.img.
I will just provide the final source.
There are several guides on how to compile the Hero kernel on the internet ;-)
It's quite easy.
The speed improvement is really good, especially the keyboard on 2.1 ROMs!
Linpack before the OC: 2.3 MFlops and 3.2 MFlops after the OC!
This kernel WILL work on 2.1 ROMs but it will lack the camera.
Best use on 1.5 Cupcake ROMs!
Also it will still show 528 Mhz.
Credits:
phhusson for providing the original patch and helping me out a bit
Teknologist whose kernel source this kernel is based on.
You can find the source here:
http://github.com/maxisma/Hero-OC-kernel/tree/67f94257b5159ea09ec1ed0bbfe818381860abe8/kernel-hero

a 2.1 kernel? thats crazy i want to try it and if my phone gets ruined i will curse your name!! (joking)
but seriously hope it doesnt screw my phone up thanks

Actually it's a 1.5 kernel.
Good work mate!

So any chance you guys pick up the 2.6.29 project again? Since apparently HTC has delayed 2.1 again..
Fantastic work by the way

Yeah! Thats awesome. I must try it now
But the battery lifetime will decrease at 20% ??

You probably should mentoin that some things don't work with this kernel. Or so I read on the CDMA forum.

tristan202 said:
You probably should mentoin that some things don't work with this kernel. Or so I read on the CDMA forum.
Click to expand...
Click to collapse
I'm guessing that the problems your referring to is because of running 2.1 on a 27 kernel

OttarA said:
I'm guessing that the problems your referring to is because of running 2.1 on a 27 kernel
Click to expand...
Click to collapse
Exactly.
10char

Anyone feel like making this into a flashable file for me?
Also a couple of questions:
Can I revert to the "normal" kernel? (and if I flash a new ROM will it replace this kernel? or do I need to do that manually?)
Will overclock widget pick this up or will it still have 528 as its maximum?

You just do an update.zip over your current ROM , if you want to go back, just do a nandroid backup or flash any other ROM, the kernel is always packed with the ROM you flash so updating over it overwrites the old rom

Someone want to compile it for me? I have no idea what to do.

G8D said:
Anyone feel like making this into a flashable file for me?
Click to expand...
Click to collapse
+1 I´m a newbie :/

I'm actually too lazy to make an update.zip too.. ;-)

Re: Overclocked kernel (2.6.27)
I'm actually too lazy to make an update.zip too.. ;-)
Click to expand...
Click to collapse
awfull when thinking of what Android stands for...

It isn't hard, he did state that its easy enough to find a guide on the net. Why not do it yourself if your that fussed?

How do i download the source? The download button does not work

Top right hand corner of that page... was it really that hard

dpi295 said:
How do i download the source? The download button does not work
Click to expand...
Click to collapse
Using a UNIX OS (here: Ubuntu)
1/ Install git:
Code:
sudo apt-get update && sudo apt-get install git-core
2/ setup git a little
Code:
mkdir ./git
cd ./git
git init
3/ Download sources using git
Code:
git clone http://github.com/maxisma/Hero-OC-kernel.git
At this time I've stop here, I'll try to compile it later (hope makefile is well written, I AM NOT a dev), and sure i'll give it as update zip coz is really easy and don't not take much time to sign.

nice to see this change and hope when the official 2.1 K source is released that the same patch can be incorporated into that also.

carbonyle said:
Using a UNIX OS (here: Ubuntu)
1/ Install git:
Code:
sudo apt-get update && sudo apt-get install git-core
2/ setup git a little
Code:
mkdir ./git
cd ./git
git init
3/ Download sources using git
Code:
git clone http://github.com/maxisma/Hero-OC-kernel.git
At this time I've stop here, I'll try to compile it later (hope makefile is well written, I AM NOT a dev), and sure i'll give it as update zip coz is really easy and don't not take much time to sign.
Click to expand...
Click to collapse
haha after a day of tweaking around in ubuntu, i managed to compile it. Well, its a slight improvement i suppose. swiping through the home screens is certainly much snappier. Gonna try the kernel on a 2.1 rom later.

Extracting kernel config from I9000XXJP3

Dear all,
Did anyone succeed extracting kernel configuration from I9000XXJP3? Kernel version is 2.6.32.9, the vermagic is "2.6.32.9 mod_unload ARMv7"
extract-ikconfig doesn't work on it.
I succeeded extracting a zImage gzipped payload, but it seems not to contain any configuration in it (see attached).
/proc/config.gz doesn't exist, Samsung open source package (downloaded from Samsung open source site) contains only Android 2.1 Eclair or previous versions.
My target is to build tun.ko and, eventually, ext3/ext4 modules to make them working in Samsung Galaxy S I9000 with rooted I9000XXJP3.
Any idea?

Without froyo source code or a good Samsung Kernel (es. for himem capable) I think is impossible to play good with theses beta roms.
Ciao

Any news? I need tun.ko for jp3 too..

I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!

redsh said:
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
Click to expand...
Click to collapse
Did you use the stock linux kernel? Or the common from android.kernel.org?
I'm trying the same thing actually. Isn't there any default config for the processor that might work? I tried with the config from .29 but when loading the module it says wrong format.

try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again

Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.

bilboa1 said:
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Click to expand...
Click to collapse
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..

miki4242 said:
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
Click to expand...
Click to collapse
Yes that would be a lot of work. Maybe its better to just wait until they release the kernel from froyo. I read that they release their opensource stuff rather fast. But just for adding a module like ext4 I don't think you need those patches, because imho they didn't touch the fs of the kernel. We just need an adaquate kernel config and adding modules should be possible.

Phlogiston said:
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
Click to expand...
Click to collapse
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions

Yes i've set the subversion as well but without the patches from samsung its impossible it seems. We need to wait and hope that they release the froyo kernel sources soon....

bilboa1 said:
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Click to expand...
Click to collapse
Are you sure they set CONFIG_MODVERSIONS? It's off in the downloadable sources.
Just compare the output of `modinfo -F vermagic <yourmodule>` to `modinfo -F vermagic <modulewhichloads>` or to /proc/version .

did this get solved yet? I google'd for the tun.ko file for my i9000 using jp3 but nothing yet... if you have a proper one for the MoDaCo version here please attach it! ~

I think I saw someone's post with tun.ko for FroYo beta somewhere in these forums, I mean i9000 Android Dev. One of the guys here has found a way to compile kernel for jp* here. I am sure.

I actually found it attached somewhere in the forum and it was 1,5447 mb big I think it was... but it still didn't work for me so I presumed the kernel or something must have been wrong.

[Q] about cifs.ko and nls_utf8.ko

Is there any method to get these 2 files?
Some kernal has these 2,but some miss nls_utf8.ko.
Is it necessary if I use the command iocharset=utf8?
And how can I get nls_utf8.ko if it is necessary?

trakanon said:
Is there any method to get these 2 files?
Some kernal has these 2,but some miss nls_utf8.ko.
Is it necessary if I use the command iocharset=utf8?
And how can I get nls_utf8.ko if it is necessary?
Click to expand...
Click to collapse
Go to Settings -> About phone -> Software information and let us know your:
Kernel version
Software number
Example:
Code:
2.6.32.21-g66cfb7a
1.32.178.5
I might be able to compile these modules for you. You'll also need another module "slow-work.ko" to use cifs.ko.
Mike

Tkanks for ur help,mike
Is there any easy guide to learn about how to compile?
I usually use Apache14's Buzz oc kernal for HTC Desire HD. There is cifs.ko included in the kernal,but it seems to lack nls_utf8.ko. Without nls_utf8.ko, I cant read specific language character.

trakanon said:
I usually use Apache14's Buzz oc kernal for HTC Desire HD. There is cifs.ko included in the kernel, but it seems to lack nls_utf8.ko. Without nls_utf8.ko, I can't read specific language character.
Click to expand...
Click to collapse
I can't compile modules for you then. It would be best to ask other users running the same kernel whether they have the nls_utf8.ko module already.
trakanon said:
Is there any easy guide to learn about how to compile?
Click to expand...
Click to collapse
You would need to get the source code for the exact Buzz kernel that you are running.
You would also need to download the Android NDK http://developer.android.com/sdk/ndk/index.html
You would then edit the .config file within the kernel source directory, and set CONFIG_NLS_UTF8=m
Then run the following at the Linux command line:
export CROSS_COMPILE=arm-eabi-
export ARCH=arm
export PATH=$PATH:/path/to/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/
cd /path/to/kernel/source
make clean
make prepare
make modules
/path/to/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-strip --strip-debug /path/to/kernel/source/fs/nls/nls_utf8.ko
The nls_utf8.ko file will be inside /path/to/kernel/source/fs/nls/
Note with all of the above commands, the bold text should be adjusted to match the locations where you extracted the Android NDK and kernel source to.
As for easy guides - I wouldn't know where to look - maybe try Google.
Mike

[Q] Kernel .config for defy 2.6.32.9

The Motorola kernel source releases don't seem to include the kernel config. Anyone know if the configs are available somewhere? Or perhaps someone has already gone through the work to create an approximation config that works for building modules and could share?

Hi,
There are some Motorola specific configs in the kernel\omap3\arch\arm\configs\ext_config folder. Is this what you missing?

mapphone_defconfig
Hi quasimidi,
quasimidi said:
There are some Motorola specific configs in the kernel\omap3\arch\arm\configs\ext_config folder. Is this what you missing?
Click to expand...
Click to collapse
Thanks! Not exactly as the stuff in ext_config seem to be config fragments only, but you pointed me in just the right direction for the full configuration.
There is a mapphone_defconfig target that seems to produce a suitable config. This is what I did, perhaps this is useful to someone:
- Download kernel source from sf.net/motorola, unpack
- Get ARM cross toolchain with gcc 4.4 - I got mine from emdebian
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- mapphone_defconfig
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-
The build tree can now be used to build modules. I only did a quick test, but the module inserted cleanly and appears to be working so far.

https://github.com/CyanogenDefy/and...n/blob/gingerbread/modules/mapphone_defconfig
its the one i use for modules... its based on the one in kernel sources, but result of a build in a repo

[Guide] Building from sources [Kernel only for now]

Hello everyone.
This guide will help you in building a kernel from source for your Nexus 10
Later, when 4.2 hits AOSP, i'll add a guide for building that too
You will need a computer running Linux / OSX to build the kernel, natively, or via a VM.
This guide assumes you’re running any Linux distro.
Getting a toolchain:
You need a toolchain to build the kernel.
The preferred one is Google’s toolchain, the same they use to build AOSP.
In a terminal, type:
Code:
git clone [url]https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/[/url]
export PATH=$PATH:$(pwd)/arm-linux-androideabi-4.6/bin
export CROSS_COMPILE=arm-linux-androideabi-
TIp: paste the export statements in your ~/.bashrc to have them exported each login.
Getting the kernel source:
The kernel source for Nexus devices is available from Google’s servers.
Source : https://android.googlesource.com/kernel/exynos
Github Mirror: https://github.com/chirayudesai/android_kernel_exynos
Open the terminal, and type the below commands to get the kernel source on your computer.
Code:
mkdir -p android/kernel
cd android/kernel
For Nexus 10, we get the exynos kernel sources.
Code:
git clone [url]https://android.googlesource.com/kernel/exynos[/url]
Next, we change our directory to the newly fetched source.
Type
Code:
cd exynos
Figuring out what to build:
Now, we need to figure out which revision to build.
You need to be exactly sure about this, otherwise there are chances that the compiled kernel won’t work.
The commit to build upon can be found by a few ways.
To get the kernel sources matching the device tree, type the below in the device tree.
Code:
git log kernel
Then type the below in the kernel tree
Code:
git checkout <commit>
The commit of the version running on the current review units is 52f6ab1 (probably), which is same as branch android-exynos-manta-3.4-jb-mr1-fr .
Compiling:
Name of defconfig: manta_defconfig
cd to the directory of the kernel source, then type the below in a terminal.
Code:
export ARCH=arm
export SUBARCH=arm
Code:
make <name_of_defconfig>
make
The kernel image will be ready at arch/arm/boot/zImage
To flash it, you need to make it into a boot.img, more on that later. when we have more sources.

Nice work, it's been nice to see some instructions on building additional kernel modules too.
Sent from my GT-I9300 using Tapatalk 2

Great guide! I look forward to seeing your tutorial on compiling 4.2 from source .
Sent from my SCH-I535 using xda premium

Super awesome! I'm currently thoroughly:good: learning the rom building process with my nexus... ill get to this!

looking forward towards the development

Great! This is very helpful and useful

hey man, i got stuck at this point
Code:
git log kernel
it gives me this error
Code:
fatal: ambiguous argument 'kernel': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
didn't really get that point... thanks :good:

matt95 said:
hey man, i got stuck at this point
Code:
git log kernel
it gives me this error
Code:
fatal: ambiguous argument 'kernel': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
didn't really get that point... thanks :good:
Click to expand...
Click to collapse
It has to be typed in the device tree, which hasn't hit AOSP yet, but should soon.
Sent from my GT-P1000

cdesai said:
It has to be typed in the device tree, which hasn't hit AOSP yet, but should soon.
Sent from my GT-P1000
Click to expand...
Click to collapse
oh, now i get this :good:

i was able to make a build tonight from aosp, waiting for my device to arrive & then ill be able to test. but as far as i could tell the output sizes were pretty on compared to the factory image files i extracted http://renzy.me/aoi
...just realized i didnt extract proprietary binaries.

Hello, Cdesai.
Thanks for your guide!
I will do my best to learn it.

so you say that you need to make the zImage into a boot.img (being a noob about this...) on my SGSII, I can flash zImages and boot.img, so I'm confused, lol

jrod091 said:
so you say that you need to make the zImage into a boot.img (being a noob about this...) on my SGSII, I can flash zImages and boot.img, so I'm confused, lol
Click to expand...
Click to collapse
i think it depends on how youre flashing. with the sgsii youre prob using odin/heimdall & it might just overwrite the kernel. flashing with fastboot might require the boot.img cause it contains a ramdisk image after the kernel & is writing a partition. thats just my guess at least, someone else might have a better/more accurate answer for ya

renzyyy said:
i think it depends on how youre flashing. with the sgsii youre prob using odin/heimdall & it might just overwrite the kernel. flashing with fastboot might require the boot.img cause it contains a ramdisk image after the kernel & is writing a partition. thats just my guess at least, someone else might have a better/more accurate answer for ya
Click to expand...
Click to collapse
yeah that's true, but for instance with HTC S-OFFed devices you don't even need to flash the boot.img....

cdesai said:
... To flash it, you need to make it into a boot.img, more on that later. when we have more sources.
Click to expand...
Click to collapse
you can extract the contents from the factory image & use getramdisk.py to get the ramdisk.img out of the current boot.img (or use this ramdisk.img)
then once youve compiled the kernel successfully, use mkbootimg from android_bootimg_tools.tar.gz to repack your boot.img.
if you want to just test...
fastboot boot [new-boot.img]
and flash if satisfied...
fastboot flash boot [new-boot.img]
just tested out if anyone wants some verification... screenshot

@cdesai, shouldn't we be using arm-eabi- instead of arm-linux-androideabi- as CROSS_COMPILE
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
export PATH=$PATH:$(pwd)/arm-eabi-4.6/bin
export CROSS_COMPILE=arm-eabi-
Building with arm-linux-androideabi- causes issues with kernel modules... here's an example of such an issue https://groups.google.com/forum/?fromgroups=#!topic/android-kernel/dzEIOVuxtEo
And the most updated kernel branch is android-exynos-manta-3.4-jb-mr1 not android-exynos-manta-3.4-jb-mr1-fr

Is there any chance of this becoming an OC kernel in the future?

craigacgomez said:
@cdesai, shouldn't we be using arm-eabi- instead of arm-linux-androideabi- as CROSS_COMPILE
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
export PATH=$PATH:$(pwd)/arm-eabi-4.6/bin
export CROSS_COMPILE=arm-eabi-
Building with arm-linux-androideabi- causes issues with kernel modules... here's an example of such an issue https://groups.google.com/forum/?fromgroups=#!topic/android-kernel/dzEIOVuxtEo
And the most updated kernel branch is android-exynos-manta-3.4-jb-mr1 not android-exynos-manta-3.4-jb-mr1-fr
Click to expand...
Click to collapse
Yes, I couldn't get md4 and cifs modules to load with arm-linux-androideabi-4.6:
<3>[ 1250.492203] md4: unknown relocation: 27
<4>[ 1260.230901] cifs: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
However, with this:
git clone https://android.googlesource.com/platform/prebuilt
export PATH=$PATH:$PWD/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
export CROSS_COMPILE=arm-eabi-
The modules load okay:
[email protected]:/mnt/shell/emulated/0 # lsmod
cifs 269223 0 - Live 0x00000000
md4 3442 0 - Live 0x00000000
(Now I have to work out why neither mount nor cifsmanager are working as expected...)

sam3000 said:
Yes, I couldn't get md4 and cifs modules to load with arm-linux-androideabi-4.6:
<3>[ 1250.492203] md4: unknown relocation: 27
<4>[ 1260.230901] cifs: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
However, with this:
git clone https://android.googlesource.com/platform/prebuilt
export PATH=$PATH:$PWD/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
export CROSS_COMPILE=arm-eabi-
The modules load okay:
[email protected]:/mnt/shell/emulated/0 # lsmod
cifs 269223 0 - Live 0x00000000
md4 3442 0 - Live 0x00000000
(Now I have to work out why neither mount nor cifsmanager are working as expected...)
Click to expand...
Click to collapse
I know the reason... busybox needs to be patched... i guess it's something new in 3.4.5 kernel... I haven't done the patch yet
https://github.com/OpenELEC/OpenELEC.tv/commit/f66041febdb07d13a158dab5da901d208cf4fff9

craigacgomez said:
I know the reason... busybox needs to be patched... i guess it's something new in 3.4.5 kernel... I haven't done the patch yet
https://github.com/OpenELEC/OpenELEC.tv/commit/f66041febdb07d13a158dab5da901d208cf4fff9
Click to expand...
Click to collapse
I had actually just got to the point of realising I could make it work by explicitly setting the unc path in mount command options. The missing patch would explain it.