Develop Bugs

[GUIDE] Howto compile your own Pershoot kernel for CM7 Final for Vision

Compiling Pershoot's Vision Kernel for CyanogenMod 7
Why would I do this?
1. You must enjoy punishment
2. You want to know how a kernel gets compiled for Android.
3. You want to modify your kernel somehow, such as adding the Interactive Scheduler to the default Pershoot config or switching between CFS and BFS.
4. You want to modify the overclocking frequencies or voltages.
I don't teach how to do anything but #1 and 2, the rest I might get into later, but this guide is the gateway to all that.
You will need a working Ubuntu system. 10.04, 10.10, or 11.04 should all be fine. I did it with 11.04, so bleeding edge is working 100%.
On Ubuntu 10.04 and 10.10, get the following packages:
Code:
sudo apt-get install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
On Ubuntu 11.04 get:
Code:
sudo apt-get install git-core gnupg openjdk-6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
Let's create our compilation area:
Code:
cd ~
mkdir kernel-compilation
mkdir kernel-compilation/toolchain
mkdir kernel-compilation/finals
mkdir kernel-compilation/staging
Download the following files:
http://www.mediafire.com/file/5aqhkl69fq75253/arm-eabi-4.3.1.zip - Unzip to ~/kernel-compilation/toolchain
http://www.mediafire.com/file/7lo2ctg7r56urky/staging.zip - Unzip to ~/kernel-compilation/staging
And lastly, grab the source from Pershoot's GIT, which will end up in kernel-compilation/vision-2632:
Code:
cd ~/kernel-compilation/
git clone https://github.com/pershoot/vision-2632.git -b gingerbread
Next we'll set up the compiler to use the ARM toolchain through an environment variable to make it easier later:
Code:
export CCOMPILER=~/kernel-compilation/toolchain/arm-eabi-4.3.1/bin/arm-eabi-
Next we'll use Pershoot's default configuration file as a starting point:
Code:
cd ~/kernel-compilation/vision-2632
cp arch/arm/configs/pershoot_vision_defconfig .config
If you wish to modify his configuration:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
Next we'll compile the newly configured kernel:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j4 (replace 4 with the number of physical processor cores on your system, or leave the -j option off altogether if you don't know)
And the modules:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER modules
Now we'll start installing the kernel into our staging area.
Copy the kernel image from the source area into staging:
Code:
cp arch/arm/boot/zImage ~/kernel-compilation/staging/kernel/zImage
and install the modules (and fix where it puts them):
Code:
make ARCH=arm INSTALL_MOD_PATH=~/kernel-compilation/staging/system modules_install
cp ~/kernel-compilation/staging/system/lib/modules/2.6.32.38-cyanogenmod/kernel/drivers/net/wireless/bcm4329/bcm4329.ko ~/kernel-compilation/staging/system/lib/modules/bcm4329.ko
rm -rf ~/kernel-compilation/staging/system/lib/modules/2.6.32.38-cyanogenmod
Now let's finish up by zipping it all into the finals area:
Code:
cd ~/kernel-compilation/staging
zip -r ~/kernel-compilation/finals/mykernel.zip *
Now go to your finals directory and get to flashing!
References:
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
http://forum.xda-developers.com/showthread.php?t=916198#
Thanks to Pershoot, CyanogenMod Team, and everybody on #cyanogenmod on Freenode IRC.

you da man.

jbdubbs said:
Compiling Pershoot's Vision Kernel for CyanogenMod 7
Thanks to Pershoot, CyanogenMod Team, and everybody on #cyanogenmod on Freenode IRC.
Click to expand...
Click to collapse
dude, this is one amazingly simple tutorial I have almost zero ubuntu experience, and i have literally NEVER created my own anything for my phone, much less something as seemingly complex as the base kernel, but your easy walkthrough made it one of the easiest things Ive ever done, and now I have a working kernel with all the features i was looking for but never knew how to make myself
EDIT: may have spoken too soon. The kernel compiled fine and booted fine, but when i look for my added governors (interactive and conservative) in the listings, they dont appear there. any thoughts on what I need to do?

Am I right in assuming that the CPU frequencies/voltages are in /arch/arm/mach-msm/acpuclock-7x30.c , and that modifying those values in gedit (default program that opened when I doubleclicked it) would stick once I compile the kernel?

jmwils3 said:
dude, this is one amazingly simple tutorial I have almost zero ubuntu experience, and i have literally NEVER created my own anything for my phone, much less something as seemingly complex as the base kernel, but your easy walkthrough made it one of the easiest things Ive ever done, and now I have a working kernel with all the features i was looking for but never knew how to make myself
EDIT: may have spoken too soon. The kernel compiled fine and booted fine, but when i look for my added governors (interactive and conservative) in the listings, they dont appear there. any thoughts on what I need to do?
Click to expand...
Click to collapse
I'm assuming that you did the 'make ARCH=arm menuconfig' step and didn't properly save your changes. When you exit the menu it'll ask if you'd like to save, obviously select 'yes'. Don't choose the option to save an alternate config at the bottom of the main menu, just keep hitting exit until it asks to explicitly.
Sent from my HTC Vision using XDA App

qzfive said:
Am I right in assuming that the CPU frequencies/voltages are in /arch/arm/mach-msm/acpuclock-7x30.c , and that modifying those values in gedit (default program that opened when I doubleclicked it) would stick once I compile the kernel?
Click to expand...
Click to collapse
The short answer is yes, the long answer is that while that is indeed where the frequencies and voltages are stored, its pretty greek to me. I attempted to copy the 1.9 ghz acpuclock-7x30.c from another post on this forum and it doesn't seem like it compiled it, I still only made it to 1.5.
I'm going to investigate both this and where exactly the smartass governor source is and update this guide later.
Sent from my HTC Vision using XDA App

jbdubbs said:
I'm assuming that you did the 'make ARCH=arm menuconfig' step and didn't properly save your changes. When you exit the menu it'll ask if you'd like to save, obviously select 'yes'. Don't choose the option to save an alternate config at the bottom of the main menu, just keep hitting exit until it asks to explicitly.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
-facepalms- duh, that would make sense. So is there any way to undo the mistake, or would i need to start from scratch? not that bad either way, just wondered

jmwils3 said:
-facepalms- duh, that would make sense. So is there any way to undo the mistake, or would i need to start from scratch? not that bad either way, just wondered
Click to expand...
Click to collapse
You can run 'make clean' then continue from the menuconfig step.
Sent from my HTC Vision using XDA App

jbdubbs said:
You can run 'make clean' then continue from the menuconfig step.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Im sorry for the extremely noob-ish questions (havent felt this noob-ish since my pre-root days on my FIRST G2), but do you mean to run that command on the created zip file, or elsewhere?

jmwils3 said:
Im sorry for the extremely noob-ish questions (havent felt this noob-ish since my pre-root days on my FIRST G2), but do you mean to run that command on the created zip file, or elsewhere?
Click to expand...
Click to collapse
Run that command from ~/kernel-compilation/vision-2632
Sent from my HTC Vision using XDA App

jbdubbs said:
Run that command from ~/kernel-compilation/vision-2632
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
it keeps giving me an error that the selected location is a directory.

jmwils3 said:
it keeps giving me an error that the selected location is a directory.
Click to expand...
Click to collapse
cd ~/kernel-compilation/vision-2632
make clean
make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
Sent from my HTC Vision using XDA App

lol, thanks i had found my mistake, and i just started it from after where it had me retrieve the files (which of course, i already had from before) and it got me to the right place to run the command. everything seems to have worked, but ill see once my phone boots.
EDIT: that did it! thanks again, bro

Instead of:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j4 (replace 4 with the number of physical processor cores on your system, or leave the -j option off altogether if you don't know)
You can use this:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
that will put the right value based on your processor.
Out of curiosity, why is the interactive governor & others left out of pershoot's kernel in the first place?
I'm wondering if there are compatibility issues or other optimisations with undervolting etc and you may be running the risk of causing problems/damage to your hardware.
Droid Basement said:
Note:
If you use SetCPU, please do not set any Advanced settings, and you should use the ondemand CPU governor.
Click to expand...
Click to collapse
I only ask as, in pershoot's kernel the sysfs cpufreq directory differs from what seems the norm (from what I've seen); There are two cpufreq directories in (cpu & cpu0), but we only have one processor?
Dunno, maybe I'm just being paranoid and need to download the source and investigate...

waydownsouth said:
Instead of:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j4 (replace 4 with the number of physical processor cores on your system, or leave the -j option off altogether if you don't know)
You can use this:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
Click to expand...
Click to collapse
Yeah I left that out for simplicity of the guide. Most people should know how many cores they have.
Out of curiosity, why is the interactive governor & others left out of pershoot's kernel in the first place?
I'm wondering if there are compatibility issues or other optimisations with undervolting etc and you may be running the risk of causing problems/damage to your hardware.
I only ask as, in pershoot's kernel the sysfs cpufreq directory differs from what seems the norm (from what I've seen); There are two cpufreq directories in (cpu & cpu0), but we only have one processor?
Dunno, maybe I'm just being paranoid and need to download the source and investigate...
Click to expand...
Click to collapse
I actually have some issues using BFS (his default scheduler) with the interactive governor regarding stability. I'm assuming that BFS is the culprit for leaving it out.
Sent from my HTC Vision using XDA App

jbdubbs said:
The short answer is yes, the long answer is that while that is indeed where the frequencies and voltages are stored, its pretty greek to me. I attempted to copy the 1.9 ghz acpuclock-7x30.c from another post on this forum and it doesn't seem like it compiled it, I still only made it to 1.5.
I'm going to investigate both this and where exactly the smartass governor source is and update this guide later.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Seems I was right about the CPU frequencies/voltages being there - I finally compiled a kernel that booted - I added a frequency value of 184Mhz, and SetCPU reflects this.
Thank you so much for this guide - I'm so chuffed with myself compiling a working kernel

Cannot get gMTP on Linux?

Im trying to get MTP working on Linux by following this tutorial:
http://forum.xda-developers.com/showthread.php?t=1077377
I've got as far as doing
sudo apt-get install gmtp
however I get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package gMTP
Click to expand...
Click to collapse
Anyone know how I can sort this. I thought gMTP was on the Universal list...
Im using Ubuntu 10.04 LTS Lucid Lynx

gmtp was apparently added in maverick. Time to compile from source...

gotroot801 said:
gmtp was apparently added in maverick. Time to compile from source...
Click to expand...
Click to collapse
I've been trying that with no luck :-\
Where can I get to source from? I found one but when I ran 'make' it errored out with the error code 1
Sent from my Galaxy Nexus using Tapatalk

Forgive me, I haven't used Ubuntu in a little while now. Have you tried make config?
Also, why not just add the repository with the application in it?

Evostance said:
I've been trying that with no luck :-\
Where can I get to source from? I found one but when I ran 'make' it errored out with the error code 1
Click to expand...
Click to collapse
The source is available at http://gmtp.sourceforge.net, but I'm having the same problems you are. Oh well - if I'm comfortable enough building something from source, I'm comfortable enough to use adb push to move files to my phone.
RMatt1992 said:
Also, why not just add the repository with the application in it?
Click to expand...
Click to collapse
The repository is the Ubuntu repo for a later release. I can't speak for the OP, but I'm still running 10.04 LTS because it's a long-term support version and there will still be updates for it for the next three years. As much as I enjoy crackflashing on my phone, I prefer my desktop to be somewhat stable.

So add the repo, install the program, remove the repo.

cifs.ko for N8000 (tested on XXALGA)

Hi there,
I noticed noone seems to have ever bothered building cifs.ko (the Kernel module necessary to access Windows Shares) for
the Galaxy Note 10.1
So I build one. Actually it's two modules md4.ko and cifs.ko (md4.ko has to be loaded first).
I have successfully tested the module on my EU N8000 running XXALGA with CIFSmanager. Streaming a 720p mkv with
MXPlayer just works really nice.
Here you go:
http://www.mediafire.com/?5lteys7tj45zuw7
DISCLAIMER: I am providing these kernel modules as-is. Altough they have been tested by me I take no responsibility whatsoever
if you break or damage your device while installing and/or using the modules. I am also not going to explain the steps necessary to actually
use the module. You should already know how to do it...or at least be smart enough to find out what to do
Enjoy!
maui

Sounds like a very helpful piece of code.
I really think that i could need this, but for me as a non developer... how to use this kernel modules?
Could you build a kernel including this modules for flashing via CWM so anybody can use it?
Best regards,
Gery
Sent from my GT-N8000 using xda app-developers app

It does not work for me: no such device.
I have moved the files to /mnt/sdcard/cifs. I entered " /mnt/sdcard/cifs/md4.ko;insmod /mnt/sdcard/cifs/cifs.ko" in cifs manager
I'm Running GT-N8000 DR.AKRIM_ROM N8000DDALI1_v0.31 4.1.1 12-9-2012
Is jellybean a problem?

They work on 4.0.4 (Hong Kong version - n8000zsali1)!!! Thank you.

I have an non-rooted italian N8000 running the latest stock firmware, and can access all my windows shares using the samba client built in in EsExplorer, no problem for me. What exactly is this module meant to do?
Inviato dal mio GT-N8000 con Tapatalk 2

HowHigh said:
It does not work for me: no such device.
I have moved the files to /mnt/sdcard/cifs. I entered " /mnt/sdcard/cifs/md4.ko;insmod /mnt/sdcard/cifs/cifs.ko" in cifs manager
I'm Running GT-N8000 DR.AKRIM_ROM N8000DDALI1_v0.31 4.1.1 12-9-2012
Is jellybean a problem?
Click to expand...
Click to collapse
Does not work for me as well. I'm running JellyNote beta 1 rom. Could someone please recommend custom rom which is supporting cifs or where would work this modul.
Thanks!

What's the use of this module? I don't understand... I haven't installed the module but can access flawlessly all my windows shares using the samba client of es file exlorer. I can also play any shared media file through such client, using any player installed in my note!
GT-N8000 using Tapatalk

Pls compile for 4.1.1.

Hi,
I compiled the cifs modules for the JB-Kernel. I couldn't test them out as I had no time to update, yet. But I need the cifs-modules so I started with them.
So, if anyone wants to try it out, please go ahead.
This is the first time I've build a kernel for android, just that you know :silly:
Greetings,
Maz

supermaz said:
Hi,
I compiled the cifs modules for the JB-Kernel. I couldn't test them out as I had no time to update, yet. But I need the cifs-modules so I started with them.
So, if anyone wants to try it out, please go ahead.
This is the first time I've build a kernel for android, just that you know :silly:
Greetings,
Maz
Click to expand...
Click to collapse
Compile nls_utf8.ko pls)
Can you say how to compile modules because at start I get error that file not found smc.h
Sent from my GT-N8000 using XDA Premium HD app

It seems like nls_utf8 is already build in the kernel.
If someone tests the cifs modules, it would be great to post here if they work or not.

supermaz said:
It seems like nls_utf8 is already build in the kernel.
If someone tests the cifs modules, it would be great to post here if they work or not.
Click to expand...
Click to collapse
Module works but I need nls_utf8 -no in kernel!!!
Sent from my GT-N8000 using XDA Premium HD app

I've attached the nls_utf8 kernel module. Please check if this helps.
Or do you need the NLS_KOI8_R for Russia?

supermaz said:
I've attached the nls_utf8 kernel module. Please check if this helps.
Or do you need the NLS_KOI8_R for Russia?
Click to expand...
Click to collapse
All works) Thanks)
Can you say how to compile this??

GooG2e said:
All works) Thanks)
Can you say how to compile this??
Click to expand...
Click to collapse
Then hit the Thanks button
To compile you need the android ndk prebuilt environment. I followed the this howto: http://source.android.com/source/building-kernels.html (from Downloading a prebuilt gcc downwards).
Then you need your kernel sources (look at the android dev section here). In the package is a README_Kernel where you can get the make command to build the default config. From there on you just run make menuconfig and make to compile things.
Best regards,
Maz

Please compile for 4.1.2
Sent from my GT-N8000 using XDA Premium HD app

hey man, can you please compile xpad.ko and ff-memless.ko for 4.1.1 ? You would bring a new wave of gamer to the galaxy note 10.1.
thx in regard

GooG2e said:
Please compile for 4.1.2
Sent from my GT-N8000 using XDA Premium HD app
Click to expand...
Click to collapse
+1 i have: init_module '/sdcard/cifs/md4.ko' failed (Exec format error)
Or am i doing smthg wrong?

Hi,
the cifs.ko and md4.ko given lately does not work on 4.1.2 rom.
Is there a compiled module for 4.1.2 ?

come on...
it shouldn't be hard to compile it for someone who has the setup.
If I had the storage capacity on my disk for installing a linux VM, I would do it but I really don't have a setup.

[KERNEL] [13/5] Razer LTS | Beta1.0 | NTFS | TUN | CIFS | EFS | EXFAT |

Razer LTS Kernel
Features:
Based On Samsung Update 1
Built with Stock ARM Toolchain
exFat
NTFS
TUN
CIFS
Added Conservative | Interactive | Powersave
Default I/O Sched No-op
CPU_Load_Slope Corrected
Info:This is My First Time Making a Kernel..So please Do not have any regrets in me..if you really don't like my kernel..stay away this thread..do not spam my thread
If you understand what situation I'm in
but sure i can give my fullest to this community
Bugs:
None
Downloads:
Beta 1.0
Instructions:
Backup the ROM
Wipe Dalvik cache
Flash the .zip file with Clockworkmod
Credits:
Thanks for your Contribution,Support and Teachings :good:
AndreiLux
Wanam
n3ocort3x
Github:
Anybody who would like to make changes to my git can obiviously do it
My Simple Motto:Your ROM,Your Kernel
Github Link

First, I'll check it out soon
I can't seem to download it, Google docs just opens the file rather than letting me download it. I'm using my phone not my pc...
Sent from my GT-I9500 using Tapatalk 4 Beta

Nasty_z said:
First, I'll check it out soon
I can't seem to download it, Google docs just opens the file rather than letting me download it. I'm using my phone not my pc...
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
file > Download :good:

Sorry, it didn't show up before, downloading now..
Sent from my GT-I9500 using Tapatalk 4 Beta

Purely spiritual support your endeavors to enrich i9500 forum.
Sent from my GT-I9500 using xda app-developers app

The more the merrier, practice makes perfect, I'm sure you'll make a great kernel with time.

WiFi isn't working? @razer1224, are you using Google's NDK toolchain to compile the kernel? Also, Google Docs is a bit confusing for people to download from because it's a .zip file, try http://d-h.st/ instead

android1234567 said:
WiFi isn't working? @razer1224, are you using Google's NDK toolchain to compile the kernel? Also, Google Docs is a bit confusing for people to download from because it's a .zip file, try http://d-h.st/ instead
Click to expand...
Click to collapse
Very nice to see you here, we gonna need all your help. Thanks

android1234567 said:
WiFi isn't working? @razer1224, are you using Google's NDK toolchain to compile the kernel? Also, Google Docs is a bit confusing for people to download from because it's a .zip file, try http://d-h.st/ instead
Click to expand...
Click to collapse
Google Stock Arm Eabi toolchain is not working
I will be getting Linaro 4.6 And thanks for your support
Sent from my GT-I9500 using xda app-developers app

anyways am pointing out the error occuring with stock toolchain @android1234567
/home/razer/arm-eabi-4.6/bin/arm-eabi-gcc: 1: /home/razer/arm-eabi-4.6/bin/arm-eabi-gcc: Syntax error: "(" unexpected
I might be compiling with linaro soon

razer1224 said:
Google Stock Arm Eabi toolchain is not working
I will be getting Linaro 4.6 And thanks for your support
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Use Linaro 4.7 and add the -mno-unaligned-access flag to the KBUILD_CFLAGS_KERNEL line in the Makefile in the root directory, otherwise the kernel won't boot. You can download the April release of Linaro 4.7 from here: https://releases.linaro.org/13.04/c...13.04-2-2013-04-13_12-08-43-linux-x86.tar.bz2
Also, apply this patch so your kernel builds nicely with Linaro: https://github.com/Christopher83/sa...mmit/423e4b149aa5325937f6d72b9ec5deaea4d8eed2
I don't actually own the S4 (was just browsing around here lol) but it seems pretty nice. Maybe I'll get it

android1234567 said:
Use Linaro 4.7 and add the -mno-unaligned-access flag to the KBUILD_CFLAGS_KERNEL Makefile in the root directory, otherwise the kernel won't boot. You can download the April release of Linaro 4.7 from here: https://releases.linaro.org/13.04/c...13.04-2-2013-04-13_12-08-43-linux-x86.tar.bz2
Also, apply this patch so your kernel builds nicely with Linaro: https://github.com/Christopher83/sa...mmit/423e4b149aa5325937f6d72b9ec5deaea4d8eed2
I don't actually own the S4 (was just browsing around here lol) but it seems pretty nice. Maybe I'll get it
Click to expand...
Click to collapse
Thanks for Metioning

@android1234567
arm-eabi-gcc: error: unrecognized command line option '-MNO-UNALIGNED-ACCESS'
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Hmm..You asked to add a flag but it does not recognize

razer1224 said:
@android1234567
arm-eabi-gcc: error: unrecognized command line option '-MNO-UNALIGNED-ACCESS'
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Hmm..You asked to add a flag but it does not recognize
Click to expand...
Click to collapse
That flag works in Linaro 4.7. Did you set the cross compile path to the Linaro toolchain? That error can also appear if you added the flag to HOSTCFLAGS instead of KBUILD_CFLAGS_KERNEL
Sent from my HTC Sensation 4G using xda app-developers app

android1234567 said:
That flag works in Linaro 4.7. Did you set the cross compile path to the Linaro toolchain? That error can also appear if you added the flag to HOSTCFLAGS instead of KBUILD_CFLAGS_KERNEL
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
i think 4.7 GCC's normally dont work with this kernel sources
as it ends up in some error

razer1224 said:
i think 4.7 GCC's normally dont work with this kernel sources
as it ends up in some error
Click to expand...
Click to collapse
A different error? And all sources can be changed to work with GCC 4.7
Sent from my HTC Sensation 4G using xda app-developers app

razer1224 said:
anyways am pointing out the error occuring with stock toolchain @android1234567
/home/razer/arm-eabi-4.6/bin/arm-eabi-gcc: 1: /home/razer/arm-eabi-4.6/bin/arm-eabi-gcc: Syntax error: "(" unexpected
I might be compiling with linaro soon
Click to expand...
Click to collapse
This error means you are using 64bit version of the toolchain, checkout from this commit.

wanam said:
This error means you are using 64bit version of the toolchain, checkout from this commit.
Click to expand...
Click to collapse
Yeah, My System Totally cant run 64bit properly
meaning it cant update my linux
EDIT: THANK YOU @wanam THIS IS WHAT AM SEARCHING FOR
32BIT Toolchain
Thanks YOU SO MUCH

android1234567 said:
Use Linaro 4.7 and add the -mno-unaligned-access flag to the KBUILD_CFLAGS_KERNEL line in the Makefile in the root directory, otherwise the kernel won't boot. You can download the April release of Linaro 4.7 from here: https://releases.linaro.org/13.04/c...13.04-2-2013-04-13_12-08-43-linux-x86.tar.bz2
Also, apply this patch so your kernel builds nicely with Linaro: https://github.com/Christopher83/sa...mmit/423e4b149aa5325937f6d72b9ec5deaea4d8eed2
I don't actually own the S4 (was just browsing around here lol) but it seems pretty nice. Maybe I'll get it
Click to expand...
Click to collapse
Please get the S4(I9500), imagine unleashing this beast with linaro and potential kernel tweaks beyond anything around now.

Beta 1.0
Beta 1.0:
Fixed WiFi
Exfat module added from Samsung
And Probably NTFS Will Work

[Kernel Base][3.4.55][Dev]Bare Repositories of TW/AOSP Kernel (4.3 Sammy Sources!)

Up-to-Date Bare Repositories for TW/AOSP 4.2.2 Kernel​samsung-kernel-jfltexx​
Short Info:
I've made this repository to have a central place for everyone to fork their kernel base from. The advantage of this repo is that it is always up-to-date (as in the latest linux kernel version). Imagine the difference from starting at a 3.4.0 kernel base and 3.4.52 kernel base, there are thousands of new patches in that patch range. :good:
Repository Url:
Code:
https://github.com/broodplank/samsung-kernel-jfltexx
Repository Info:
Name: samsung-kernel-jfltexx
Description: Bare repositories for jfltexx (i9505)
Branches: tw-4.2.2 and aosp-4.2.2 (aosp 4.3 coming when 4.3 kernel sources are released)
tw-4.2.2 = Stock i9505 TouchWiz Kernel from Samsung sources patched until latest linux kernel version
aosp-4.2.2 = i9505g Google Edition Kernel (for AOSP 4.2.2 Google Edition and TouchWiz 4.2.2) (for i9505)
Getting the sources:
If you want to compile the kernel directly without much changes it's advised to clone it:
Code:
git clone [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url] -b branchname
If you want to make your own kernel it's advised to fork the kernel:
- Login at github
- Go to https://github.com/broodplank/samsung-kernel-jfltexx
- Click Fork at the right top of the page
Click to expand...
Click to collapse
Usage Info:
Initializing first config:
Code:
make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
Configuration:
Easiest variant (QT based GUI, needs libqt4-dev libqt4-core and libqt4-gui)
Code:
make xconfig
Default variant:
Code:
make menuconfig
Other less popular variants:
(GTK based, doesn't need any special packages)
Code:
make gconfig
(Ncurses based, needs libncurses5, libncurses5-dev and libncursesw5)\
Code:
make nconfig
Building Kernel:
Code:
export ARCH=arm
export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
make -jx (where x is the amount of cpu cores + 1)
Toolchains:
Toolchains that are suited for building the sources are:
arm-eabi-4.6
Click to expand...
Click to collapse
Building boot.img:
Code:
./build_bootimg
(Choose the rom type you will be using and it will be created in build/output)
Flashing boot.img and modules:
Code:
./flash_bootimg
(This is a process that pushes boot.img to your phone and then to the kernel partition, after that you can choose whether to push modules or not, and finally you can choose to wipe dalvik-cache or not and it will reboot.
Updating Info:
If you have forked the repository do this to fetch the updates from this repository:
First add it to the remote:
Code:
git remote add bare [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url]
git fetch bare
Then search for the commit(s) that you want to merge
For 1 commit:
Code:
git cherry-pick [commit hash here, this is the last part of a commits url]
(for example: https://github.com/broodplank/samsung-kernel-jfltexx/commit/612bbea08b67f16dd5628cb8cd8406973f8fe821 would be: 612bbea08b67f16dd5628cb8cd8406973f8fe821)
For a range of commits:
Code:
git cherry-pick [commit a hash]^..[commit b hash]
Where commit a is the oldest commit and commit b the newest.
for example:
Code:
git cherry-pick 0bff3bdba64c58ea6100d72763f2be3acc9659db^..612bbea08b67f16dd5628cb8cd8406973f8fe821
This would patch the sources from 3.4.40 to 3.4.52

Latest Repository Changes:
3-08-2013
- Switched to real samsung 4.3 sources
29-07-2013
- Updated aosp-4.2.2 and tw-4.2.2 to 3.4.55
25-07-2013
- NEW BRANCH: AOSP-4.3
- NEW BRANCH: TW-4.3
- Added MSM8960 Headers from Google!
23-07-2013
- Update to 3.4.54
14-07-2013
- Update to 3.4.53
- Merge sensor fix from faux123
13-07-2013
- Updated defconfigs for proper building
09-07-2013
- Update to 3.4.52
- Sensor fix by ausdim
- Large update to readme
06-07-2013
- Add samsung sources
- Patch to latest version 3.4.51
- add boot.img creator
05-07-2013
- Initial commit, make repository

Thanks, I just forked it.
I'm a noob at this but am learning fast. I've modified and compiled the 3.0.31 kernel for the 9210T but I'd like to now try 3.4. Appears none of the celox changes for board_msm8x60.c source came across from 3.0 to 3.4 so I think I've got my work cut out for me.
m0tter

This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?

harise100 said:
This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?
Click to expand...
Click to collapse
InitRamfs??
Permisions of initramfs?

ausdim said:
InitRamfs??
Permisions of initramfs?
Click to expand...
Click to collapse
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks

ausdim said:
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks
Click to expand...
Click to collapse
Thank you for trying to help me... but it still doesn't work. Same result.

harise100 said:
Thank you for trying to help me... but it still doesn't work. Same result.
Click to expand...
Click to collapse
Tonight Ill do a little research on this and tell you the solution.

I remember when I started to make my first kernel, I had similar problems with the Samsung sources.
Wanam gave me his jf_defconfig file and it worked. He said that the config file by Samsung is crap. But I forgot to ask for details.
If I use my config file on your sources, it results in a bootloop, whereas they work fine with Samsung update 2 sources.
Does that make sense?
Sent from my GT-I9505 using xda app-developers app

Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2

.c0dy said:
Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
What is your problem?
Sent from my GT-I9505 using xda app-developers app

harise100 said:
What is your problem?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I hate it -.- xD
Now it worked. And I do not know why... As I am pretty new to this, as already said, - could this be the problem? :
I think I made this:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ make xconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
Click to expand...
Click to collapse
instead of:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig
Click to expand...
Click to collapse
So I used xconfig before setting ARCH and CROSS_COMPILE.
Could that be the problem?
Atm i can not paste the error. The first one had something to do with a buffersize. Could "fix" that by setting "CONFIG_FRAME_WARN=1024" higher. Because it said it was 1032.
Second error was something like "‘ret’ may be used uninitialized in this function [-Wuninitialized]".
---------- Post added at 08:08 PM ---------- Previous post was at 07:32 PM ----------
Will add a new post for this, if it's okay.
And i hope it's okay to ask in here
So, first, as wrote in my previous post the compiling worked.
Now, i did the following:
1. Changed in the config: "kernel compression mode -> LZO
2. Removed "Optimize for size"
3. And changed the flag in the makefile to O3.
kernel/workqueue.c: In function 'freeze_workqueues_begin':
kernel/workqueue.c:483:11: warning: array subscript is above array bounds [-Warray-bounds]
error, forbidden warning: workqueue.c:483
make[1]: *** [kernel/workqueue.o] Error 1
make[1]: *** Waiting for unfinished jobs....
While writing this I reset "Optimize for size" and restart compiling. Now it does seem to work.
So i guess there is a problem with the flag. Where is the right place of the flag?

If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ah okay, thanks. Will see if I can find a few more infos about that

broodplank1337 said:
Tonight Ill do a little research on this and tell you the solution.
Click to expand...
Click to collapse
Did you find anything?
I do have a working build environment and I can compile and install a kernel that is better than stock kernel.
Only these sources don't work. How is that possible?
Sent from my GT-I9505 using xda app-developers app

.c0dy said:
Ah okay, thanks. Will see if I can find a few more infos about that
Click to expand...
Click to collapse
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b

broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
It will work if you have the right toolchain, I use this one:
http://www.mediafire.com/download/i...linaro_4.7.4-2013.07-build_2013_07_12.tar.bz2
It's an optimized Linaro toolchain (http://forum.xda-developers.com/showthread.php?t=2098133)

broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
Thanks Will try that.
I already compiled a kernel, but it just booted until the samsung logo.. after that instant reboot... :/