[TOOL] guestekrnL doItYourself STOCK KERNEL BUILDER for dummies - MAKE UR OWN KERNEL!

Search This thread

Stefan Gündhör

Senior Member
Oct 24, 2011
2,368
5,748
Hinterholz 8
Well.. i'll try to digest all your explanation.. (start to have headache already.. :what:)

Anyway, great post..

Sent from my LG-P990 using XDA

It's hard to compress everything in one post, but I think I'm done now :) Just take your time, begin with only compiling the kernel without changes (and try if it boots) and then slowly change more and more stuff, don't change too many things at once, always compile&try the kernel between more changes.

Also take a look at my additional hints, using versioning is very useful for keeping overview over changes and comparing the guestekrnL sources with original stock kernel sources using a diff viewer can help understanding which kernel values/source code custom kernel DEVs change in order to make their custom kernels.
 

Stefan Gündhör

Senior Member
Oct 24, 2011
2,368
5,748
Hinterholz 8
Explaination of values in the files guestekrnl.c, guestekrnl.h and nvrm_clocks_limits.c:

guestekrnl.c
-------------------------------------
  • GUESTE_USE_FSYNC = 1; -> should fsync be used by default? values 0 or 1
  • NVRM_CPU1_ON_MIN_KHZ = 366000; -> frequency (366MHz) where second core should be turned off when it was running and cpu freq is lower than this freq for a time of 600 milliseconds (NVRM_CPU1_OFF_PENDING_MS)
  • NVRM_CPU1_OFF_MAX_KHZ = 666000; -> frequency (666MHz) where second core should be turned on when it was off and cpu freq is higher than this freq for a time of 2000 milliseconds (NVRM_CPU1_ON_PENDING_MS)
  • NVRM_CPU1_ON_PENDING_MS = 2000; // time for the things above in milliseconds
  • NVRM_CPU1_OFF_PENDING_MS = 600; // time for the things above in milliseconds
  • AUTO_SECONDCORE_LIMITS = 0; // should second core activation values be calculated intelligently by default instead of using the fixed values above? values 0 or 1
  • GUESTE_USE_SECOND_CORE = 1; // should second core be used by default? values 0 or 1
  • LED_BUTTON_BRIGHTNESS = 8; // default value for LED button brightness - values 0-100, but I fear the default is also on another place hard-coded so changes won't help
  • AUTO_BACKLIGHT_BRIGHTNESS = 6; // default step for the auto brightness intensity (this is stock default), dunno if changes here make any difference
  • MAX_SCREENOFF_CPUFREQ = 503000; // max default screenOff cpu frequency (=503 MHz)
  • MAX_CPU_SCALING_FREQ = 1000000; // default maximum cpu frequency (=1000 MHz), if you change this, remove the file Desktop/kernel_source/zipstructure/data/gueste2/oc/maxcpufreq in order to use the default kernel speed right at kernel boot (the file maxcpufreq also contains the value 1000000, this is the value GuesteOC tool will set the kernel to at boot, removing the file means GuesteOC does not change default kernel speed)
  • MIN_CPU_SCALING_FREQ = 216000; // default minimum cpu frequency (=216 MHz)
  • unsigned int STRONG_HAPTIC_VIBRATION = 0; // default value for strong vibration -- values 0 or 1
  • unsigned int STRONG_RINGING_VIBRATION = 1; // default value for incoming call vibration -- values 0 or 1

guestekrnl.h - Explainations will come soon!
-------------------------------------

// Second Core Activation Auto Limits Multiplikator
  • #define G_SECCORE_MULT (6)
// Clocking & Volting
  • #define MAX_OVERCLOCK (1300000)
  • #define MAX_VOLTAGE (1150)
  • #define GUESTE_DDR_FREQ_STATIC (325000)
  • #define GUESTE_EMC_VOLT (1200)
  • #define NVRM_AP20_LOW_CORE_MV (850)
  • #define NVRM_AP20_LOW_CPU_MV (750)
  • #define NVRM_AP20_SUSPEND_CORE_MV (900)
  • #define NVRM_AP20_DDR2_MIN_KHZ (50000)
  • #define NVRM_AP20_LPDDR2_MIN_KHZ (18000)
  • #define GUESTE_AVP_FREQ (280000)
  • #define GUESTE_EMC2_FREQ (660000)
  • #define GUESTE_GPU_FREQ (345000)
  • #define GUESTE_DDR_FREQ (325000)
// Scheduler
  • #define sysctl_sched_latency_default 10000000ULL
  • #define normalized_sysctl_sched_latency_default 10000000ULL
  • #define sysctl_sched_min_granularity_default 2000000ULL
  • #define normalized_sysctl_sched_min_granularity_default 2000000ULL
  • #define sched_nr_latency_default 5
  • #define sysctl_sched_wakeup_granularity_default 2000000UL
  • #define normalized_sysctl_sched_wakeup_granularity_default 2000000UL

Desktop/kernel_source/arch/arm/mach-tegra/nvrm/core/common/nvrm_clocks_limits.c - Explainations will come soon!
-------------------------------------

  • NvU32 FakeShmooVoltages[] = {
    755,
    770,
    800,
    850,
    900,
    1000,
    1050,
    MAX_VOLTAGE,

    };
  • NvRmScaledClkLimits FakepScaledCpuLimits = {
    101, // FakepScaledCpuLimits.HwDeviceId
    0, // FakepScaledCpuLimits.SubClockId
    32, // FakepScaledCpuLimits.MinKHz
    // Clock table
    {
    216000,
    389000,
    503000,
    655000,
    816000,
    1000000,
    1100000,
    MAX_OVERCLOCK,

    }
    };
 

spica1234

Retired Recognized Developer
Aug 1, 2010
3,081
3,362
India
Mention where guesete.c and gueste.h came from.
Mention credits to Original Author of OTF

Explaination of values in the files guestekrnl.c, guestekrnl.h and nvrm_clocks_limits.c:

guestekrnl.c
-------------------------------------
  • GUESTE_USE_FSYNC = 1; -> should fsync be used by default? values 0 or 1
  • NVRM_CPU1_ON_MIN_KHZ = 366000; -> frequency (366MHz) where second core should be turned off when it was running and cpu freq is lower than this freq for a time of 600 milliseconds (NVRM_CPU1_OFF_PENDING_MS)
  • NVRM_CPU1_OFF_MAX_KHZ = 666000; -> frequency (666MHz) where second core should be turned on when it was off and cpu freq is higher than this freq for a time of 2000 milliseconds (NVRM_CPU1_ON_PENDING_MS)
  • NVRM_CPU1_ON_PENDING_MS = 2000; // time for the things above in milliseconds
  • NVRM_CPU1_OFF_PENDING_MS = 600; // time for the things above in milliseconds
  • AUTO_SECONDCORE_LIMITS = 0; // should second core activation values be calculated intelligently by default instead of using the fixed values above? values 0 or 1
  • GUESTE_USE_SECOND_CORE = 1; // should second core be used by default? values 0 or 1
  • LED_BUTTON_BRIGHTNESS = 8; // default value for LED button brightness - values 0-100, but I fear the default is also on another place hard-coded so changes won't help
  • AUTO_BACKLIGHT_BRIGHTNESS = 6; // default step for the auto brightness intensity (this is stock default), dunno if changes here make any difference
  • MAX_SCREENOFF_CPUFREQ = 503000; // max default screenOff cpu frequency (=503 MHz)
  • MAX_CPU_SCALING_FREQ = 1000000; // default maximum cpu frequency (=1000 MHz), if you change this, remove the file Desktop/kernel_source/zipstructure/data/gueste2/oc/maxcpufreq in order to use the default kernel speed right at kernel boot (the file maxcpufreq also contains the value 1000000, this is the value GuesteOC tool will set the kernel to at boot, removing the file means GuesteOC does not change default kernel speed)
  • MIN_CPU_SCALING_FREQ = 216000; // default minimum cpu frequency (=216 MHz)
  • unsigned int STRONG_HAPTIC_VIBRATION = 0; // default value for strong vibration -- values 0 or 1
  • unsigned int STRONG_RINGING_VIBRATION = 1; // default value for incoming call vibration -- values 0 or 1

guestekrnl.h - Explainations will come soon!
-------------------------------------

// Second Core Activation Auto Limits Multiplikator
  • #define G_SECCORE_MULT (6)
// Clocking & Volting
  • #define MAX_OVERCLOCK (1300000)
  • #define MAX_VOLTAGE (1150)
  • #define GUESTE_DDR_FREQ_STATIC (325000)
  • #define GUESTE_EMC_VOLT (1200)
  • #define NVRM_AP20_LOW_CORE_MV (850)
  • #define NVRM_AP20_LOW_CPU_MV (750)
  • #define NVRM_AP20_SUSPEND_CORE_MV (900)
  • #define NVRM_AP20_DDR2_MIN_KHZ (50000)
  • #define NVRM_AP20_LPDDR2_MIN_KHZ (18000)
  • #define GUESTE_AVP_FREQ (280000)
  • #define GUESTE_EMC2_FREQ (660000)
  • #define GUESTE_GPU_FREQ (345000)
  • #define GUESTE_DDR_FREQ (325000)
// Scheduler
  • #define sysctl_sched_latency_default 10000000ULL
  • #define normalized_sysctl_sched_latency_default 10000000ULL
  • #define sysctl_sched_min_granularity_default 2000000ULL
  • #define normalized_sysctl_sched_min_granularity_default 2000000ULL
  • #define sched_nr_latency_default 5
  • #define sysctl_sched_wakeup_granularity_default 2000000UL
  • #define normalized_sysctl_sched_wakeup_granularity_default 2000000UL

Desktop/kernel_source/arch/arm/mach-tegra/nvrm/core/common/nvrm_clocks_limits.c - Explainations will come soon!
-------------------------------------

  • NvU32 FakeShmooVoltages[] = {
    755,
    770,
    800,
    850,
    900,
    1000,
    1050,
    MAX_VOLTAGE,

    };
  • NvRmScaledClkLimits FakepScaledCpuLimits = {
    101, // FakepScaledCpuLimits.HwDeviceId
    0, // FakepScaledCpuLimits.SubClockId
    32, // FakepScaledCpuLimits.MinKHz
    // Clock table
    {
    216000,
    389000,
    503000,
    655000,
    816000,
    1000000,
    1100000,
    MAX_OVERCLOCK,

    }
    };
 

Stefan Gündhör

Senior Member
Oct 24, 2011
2,368
5,748
Hinterholz 8
Mention where guesete.c and gueste.h came from.
Mention credits to Original Author of OTF

Not necessary as the credit to OTF has been already given to you during kernel development and in kernel releases multiple times. Everyone already knows you made the 20 lines code for OTF.

Apart from this the things I posted and you quoted are only containing variables and none of your OTF logic. You can't get credit for variables bro :D
 

spica1234

Retired Recognized Developer
Aug 1, 2010
3,081
3,362
India
Not necessary as the credit to OTF has been already given to you during kernel development and in kernel releases multiple times. Everyone already knows you made the 20 lines code for OTF.

Apart from this the things I posted and you quoted are only containing variables and none of your OTF logic. You can't get credit for variables bro :D
Yes this public bash you wrote http://xdaforums.com/showthread.php?p=25503366#post25503366
No offence,
Yes not 20 but 50 liines OTF that you couldnt make because lack of knwoledge of C thats why i had to write as per my C knowledge:)
Whether it's writing of 50 lines or 10 lines it requires knowledge that you dont have:) it's not "hi" "how are you" whats up" kind of 50 lines, whether it needs writing of 10-50 or 1 lines it needs knowledge of the same:) eg. to check grammer mistakes you need to have knowledge of grammer:)
and Oh my GOD i know you've no knowledsge of C that why you wrote variables. For you everything written is variables cause you know nothing except it.
Bro OTF is written with Structures, Functions, Module init , Module exit, pointers , and variables. and whole kernel codes are made of these. give credits when you use it.
you could only change variables and replace lib/spica.c with lib/gueste.c and lib/spica.h with lib/gueste.h that's it nothing productive you can do:)
Why I named OTF as HP eXtended project you know because it will be easier for PPL like you with no knowledge to change variables of line 3 and to enhance OTF:)
Credit goes for 50 lines not line no.3:) remove other 49 lines does OTF work? no:)
Let's have fun can you write only 4 lines of kernel modules which clears console? no you cant obviously admit it man, because it needs basic c knowledge that you dont have. If i will give you written codes then you'll as per your nature bash that it's no big thing only 4 lines codes :)
Whether it's 50 lines codes like OTF or 1 lines codes, you cant write means you've failed. that's it:)
By the way you bashed me by OTF by mentioning not my but someone others' work. Wanna know whose work?
http://tldp.org/LDP/lkmpg/2.6/html/lkmpg.html#AEN769 <--kernel module programming. it's nobody's work. It's tutorials that needs understanding of C. So if you want to use my sources than stop bashing me otherwise dont use it if you've any self-respect.
And stop spreading wrong information-unbiased information about my work.
 
Last edited:

Flix123

Senior Member
Jan 30, 2011
1,264
807
My first kernel

If you want maximum smoothness and responsiveness combined with all guestekrnL features, here comes my guestekrnL-FlixEdition Kernel

http://www.mediafire.com/?jlfq920eil4h1yl

Changelog:

- compiled with latest working toolchain (04-2012)
- activated cpu alignment
- other standard settings
- other name ;)
- the rest is like in latest guestekrnL

Please test it and report about stability, performance and battery!
 

Stefan Gündhör

Senior Member
Oct 24, 2011
2,368
5,748
Hinterholz 8
If you want maximum smoothness and responsiveness combined with all guestekrnL features, here comes my guestekrnL-FlixEdition Kernel

http://www.mediafire.com/?jlfq920eil4h1yl

Changelog:

- compiled with latest working toolchain (04-2012)
- activated cpu alignment
- other standard settings
- other name ;)
- the rest is like in latest guestekrnL

Please test it and report about stability, performance and battery!

Great, friend, I will have to set up a special user-editions posting collecting all user editions! Will link it in first post as soon as it is done. :) And will test your edition myself of course with cojo's latest GhostRider ROM!
 
  • Like
Reactions: Flix123

Flix123

Senior Member
Jan 30, 2011
1,264
807
Stefan,

I'll appreciate your feedback. The next days, I'll work on better build flags.
 
Last edited:

barril

Senior Member
Apr 12, 2009
195
23
If you want maximum smoothness and responsiveness combined with all guestekrnL features, here comes my guestekrnL-FlixEdition Kernel

http://www.mediafire.com/?jlfq920eil4h1yl

Changelog:

- compiled with latest working toolchain (04-2012)
- activated cpu alignment
- other standard settings
- other name ;)
- the rest is like in latest guestekrnL

Please test it and report about stability, performance and battery!

this is the capture of antut. so far all ok

503be27d-d613-af24.jpg


Enviado desde mi Optimus 2X
Rom HomeroMod Opit3D v1.4.2
 

louiscypherbr

Senior Member
Oct 12, 2010
551
222
São Paulo
If you want maximum smoothness and responsiveness combined with all guestekrnL features, here comes my guestekrnL-FlixEdition Kernel

http://www.mediafire.com/?jlfq920eil4h1yl

Changelog:

- compiled with latest working toolchain (04-2012)
- activated cpu alignment
- other standard settings
- other name ;)
- the rest is like in latest guestekrnL

Please test it and report about stability, performance and battery!

Hey, I love your and gueste's work, but can someone compile this kernel with force ac/usb patch?

Sent from my LG-P990 using XDA
 

Stefan Gündhör

Senior Member
Oct 24, 2011
2,368
5,748
Hinterholz 8
Stefan,

I'll appreciate your feedback. The next days, I'll work on better build flags.

Well I just flashed DjangoManouche Beta 16 + your kernel and I am really impressed, my phone has never been so smooth! :)
I will keep your kernel on my phone for now, at least to test battery and stability and then I will report again :).
I use different 2nd core values though, I don't like such heavy use of second core :-(
Of course I will link your and further user releases as mentioned in the kernel thread and here in first posting, as soon as I have some leisure time!
 
Last edited:
  • Like
Reactions: Flix123

Stefan Gündhör

Senior Member
Oct 24, 2011
2,368
5,748
Hinterholz 8
Boss, Stefan, post a link to this danger ROM too. Let me have some fun with all these unexpected gifts :D

( You guys are all crazy , you know that.. ? First your unpronouncable kernel name, and then a GhostRider , for gods sake..!!!! How you people come up with such names??? :D).

Here you go :) http://dl.dropbox.com/u/67281342/Ghostrider_rom.zip
Source: http://www.handy-faq.de/forum/lg_op..._optimus_speed_p990_cojos_ghostrider_rom.html

All credits to cojo! -- see source link
 
Last edited:
  • Like
Reactions: Divyan

Top Liked Posts

  • There are no posts matching your filters.
  • 33
    Ohai, everypwny!​
    Wanna impress your girlfriend without spending any money? Show her your love through compiling her your own O2X stock kernel! :D

    Requirements: A PC capable of running a virtual Linux machine -- if your PC isn't much older than 5-6 years there shouldn't be a problem. Just make sure you have enough RAM (at least 1,5 - 2 GB recommended) -- no programming - or special linux knowledge required!
    ## Info: The VMWare image has been created by Jonas Hendrickx for XDA (I just altered/modified it for my needs).

    5 simple steps to success: -- EVERYONE can do that!

    1. Download and install Vmware Player (Freeware): http://www.vmware.com/go/get-player (VirtualBox will work too if you like this app better)
    2. Download the file "guestekrnL_doItYourself_developer.rar" (http://guendhoer.com:9000/guestekrnL_doItYourself_developer.rar or https://docs.google.com/open?id=0B5HJ_FpcC9ymM3ZCS0l5RFJtZnc , 1.5GB) and unpack it (using WinRar or 7Zip or...) to any folder of your choice, and afterwards double-click the file "Android Developer.vmx" -- or alternatively open VMware Player first and then import the virtual machine located in the unpacked .rar contents
    3. Click "I copied it" and wait until virtual machine starts up, login with password "root"
    4. Open folder "kernel_source" (on Desktop), double-click file "buildkernel" and click "run in terminal"
    5. Wait until terminal window closes, and start using your new kernel located in folder Desktop/kernel_source/guestekrnL_BUILDS
    After this an exact copy of current guestekrnL "SR99R100.1PI.1337-GoodBye" has been built and packaged to a flashable CWM-Zip.


    Possible things you can easily change yourself for making your own different/improved kernel versions:

    • Use a different compilation toolchain
      • (p.ex. http://releases.linaro.org/<choose a release version>/components/android/toolchain/<choose a gcc version>/)
      • download the file "android-toolchain-eabi-linaro-..." and replace the folder "android-toolchain-eabi" on Desktop of virtual machine with the unpacked content of the downloaded file
      • There are many different builds of linaro toolchains available, resulting in different smoothness, battery life and stability of the built kernel. Important:
        [*]After toolchain change you have to edit the file "buildkernel" (rightclick -> open with gedit) and change the gcc version number
        to the one of your new toolchain (you find it here: Desktop/android-toolchain-eabi/lib/gcc/arm-eabi/<gcc version number>), save the file afterwards
      • Attention: if you switch to a toolchain newer than september 2011, you MUST change
        # CONFIG_ALLOW_CPU_ALIGNMENT is not set
        to
        CONFIG_ALLOW_CPU_ALIGNMENT=y
        in file Desktop/kernel_source/arch/arm/configs/gueste_defconfig -- otherwise kernel won't boot!
      • Only use toolchains with a number up to "4.6" in name, the newer ones ("4.7") are for ICS and not Gingerbread!
      • NOT every new toolchain will work with O2X stock kernels -> p.ex. 4.6.4 might not work while 4.6.2 works. Every toolchain older or equal to september 2011 should work BUT maybe you will have to remove some of the build flags not recognized by the older chain.
      • Always check Desktop/kernel_source/guestekrnL_BUILDS/build.log for errors after you made a new kernel build, especially at the bottom of the file. (Warnings don't matter.)
    • Use a different version-name for the built kernel
      • right-click file "buildkernel" in kernel_source folder -> open with gedit -> change kernelVersion there
    • Use a different general name for the built kernel (other than "guestekrnL")
      • double-click file "Makefile" in kernel_source folder -> click "Display" -> change kernel name there (change ".9-guestekrnL" to ".9-<yourKernelName>")
      • Attention: the Android app GuesteOC won't work if it doesn't find the String "guestekrnL" in kernel name! You then have to use the function-reduced version of the OC app by TrymHansen available for all kernels!
    • Use different build optimization flags
    • Use different basic kernel configuration values
      • open folder "kernel_source", click the search-icon, search for "gueste"
      • edit the 2 files "guestekrnl.c" and "guestekrnl.h" of the result set according to your needs
      • guestekrnl.c and guestekrnl.h contain many default voltage/speed/... values, you can change them easily there
      • if you change MAX_OVERCLOCK to a higher value, you might need to change MAX_VOLTAGE as well and have to alter the whole cpu voltage and frequency table (see next point)
      • Help & explainations here: http://xdaforums.com/showpost.php?p=26696158&postcount=25
    • Change CPU scaling voltages and speed steps
      • Edit the file Desktop/kernel_source/arch/arm/mach-tegra/nvrm/core/common/nvrm_clocks_limits.c and alter the two arrays "FakeShmooVoltages[]" and "FakepScaledCpuLimits"
      • the difference from one voltage step to another one needs to be lower or equal than 100mV;; too low voltages for a step results in freezes !!
      • the values for MAX_VOLTAGE and MAX_OVERCLOCK are located in file guestekrnL.h!
      • Help & explainations here: http://xdaforums.com/showpost.php?p=26696158&postcount=25
      • Example of creating a kernel overclockable to 1.5 GHz: http://xdaforums.com/showpost.php?p=26759653&postcount=58
    • Enable/Disable kernel features you want to use or don't want to use
      • open folder "kernel_source", click the search-icon, search for "gueste", edit the file "gueste_defconfig" according to your needs
      • "<featureName>=y" means the feature is enabled
      • "#<featureName> is not set" means the feature is disabled
      • Google for more information about what the different kernel features do, just past the kernel feature name in Google and you will find a description for most of them
    • Change the text shown to user on CWM installation of kernel
      • Edit the file Desktop/kernel_source/zipstructure/META-INF/com/google/android/updater-script according to your needs
    • If you are completely bad-ass you can also compile the compilation toolchain from the official sources yourself instead of using a prebuilt one (even if the prebuilt ones tend to be much more stable than the self-compiled ones) :D

    Useful & important additional tipps/hints: Check this out

    Info: If you ever stop the compilation progress before finishing, you have to edit the file "Makefile" in kernel folder and remove the version number from the version string (so only .9-guestekrnL should remain), otherwise you will have double version number in next kernel build.

    Start being a kernel developer for XDA right now, today!

    Advantages:
    - U can impress many users by presenting them your hard work
    - You will be acknowledged
    - You will be able to easily express your creativity to the world wide web
    - And much much more ,,, Sign up today! Oh, wait, no signup needed :D

    If you think you have created an extremely good version of guestekrnL or maybe a completely new kernel, think about posting it here in the thread (I will link the posted kernels here in first posting) or open your own thread for your new kernel, it is up to you :)

    As always I'm not responsible for any harm you might do to your system ;)

    Wanna build other stock sources than the ones of guestekrnL? Check this out
    3
    Stefan, will your tutorial works with original source (eg, V20q) and others (eg, spica HP)? and which file/folder to make our kernel support ext4?

    My idea was using stock kernel but add ext4..

    Example of building unchanged stock kernel and only add ext4 compatibility:
    • start the kernelBuilder,
    • delete all folders located in Desktop/kernel_source except the folders "guestekrnl_BUILDS" and "zipstructure"
    • delete all files located in Desktop/kernel_source except the file "buildkernel"
    • edit the file "buildkernel" (rightClick-> open with gEdit) and change line
      make ARCH=arm gueste${1}_defconfig;
      to
      make ARCH=arm star_ifx${1}_defconfig;
      if you use v20 sources or to
      make ARCH=arm star_rev_f_android${1}_defconfig;
      if you use v10 sources
    • Download the official kernel sources you want from http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP990
    • Extract the sources until you get a folder kalled "kernel"
    • copy the contents from inside "kernel" folder to Desktop/kernel_source
    • edit file Desktop/kernel_source/drivers/net/wireless/bcm4329/Makefile -> change line
      -Wall -Wstrict-prototypes -Werror \
      to
      -Wall -Wstrict-prototypes \
    • edit file Desktop/kernel_source/arch/arm/configs/star_ifx_defconfig (or star_rev_f_android_defconfig): enable ext4 through replacing ext4 config (search for it in the file) with following:
    • CONFIG_EXT4_FS=y
      CONFIG_EXT4_FS_XATTR=y
      # CONFIG_EXT4_FS_POSIX_ACL is not set
      # CONFIG_EXT4_FS_SECURITY is not set
      # CONFIG_EXT4_DEBUG is not set
      CONFIG_JBD=y
      # CONFIG_JBD_DEBUG is not set
      CONFIG_JBD2=y
      # CONFIG_JBD2_DEBUG is not set
    • run the buildkernel script, kernel will be built
    • Attention: don't use linaro/gcc toolchain newer than september 2011, otherwise kernel won't boot without additional modifications (the included default toolchain will work fine)

    For every other stock kernel sources (in order to compile & zip-package them using kernelBuilder) the procedure should work similar!
    Spica horsepower kernel however won't work that way, because spica does not upload his defconfig to his sources @GitHub (thus making rebuilding more difficult).
    And default defconfig of stock kernel won't work with spica kernel. (Without the right defconfig the kernel does not boot.)
    Older spica kernels (older than SR3) completely won't work and can't be rebuilt because spica never offered full sources @GitHub until SR3.

    So in order to get a current spica kernel source working, you have to additionally
    • install the kernel you want to rebuild first on your phone and then
    • copy the file /proc/config.gz first to your internal SD and then to your PC,
    • unpack it and then rename the file you get to "spica_defconfig" and
    • place it in Desktop/kernel_source/arch/arm/configs/
    • finally edit the buildkernel file again so you have
      make ARCH=arm spica${1}_defconfig;
      in there!

    In order to see the differences of guestekrnL compared to stock kernel, Download Meld Diff Viewer in App Store of virtual linux machine and make a folder-comparison of folder Desktop/kernel_source and a folder where you keep unchanged v10E kernel sources!
    3
    My first kernel

    If you want maximum smoothness and responsiveness combined with all guestekrnL features, here comes my guestekrnL-FlixEdition Kernel

    http://www.mediafire.com/?jlfq920eil4h1yl

    Changelog:

    - compiled with latest working toolchain (04-2012)
    - activated cpu alignment
    - other standard settings
    - other name ;)
    - the rest is like in latest guestekrnL

    Please test it and report about stability, performance and battery!
    3
    Great initiative Stefan. Download stops at ~300MB for me as well, looking forward to trying it.

    Are the guestekrnl-scripts included in the finished kernel installer? (Just wondering if GuesteOC will work out of the box.)

    Yeah I'm just uploading to a new FTP mirror, will take about 2 more hours I guess!

    And yeah, the exact zipstructure of current guestekrnL release will be built automatically, including GuesteOC v2.1.5 + Myrt UV GUI, all working out of the box!

    (In fact the most actual guestekrnL release was built exactly the way I describe it in first posting: I ran the virtual machine and double-clicked/ran the buildkernel-script. That's it.)
    2
    Yeehhaawwwww!!! This is what im searching for.. thank you very very very much..

    Edit: You need to edit your post.. looks unorganized.. quite difficult to read.. :)

    Sent from my LG-P990 using XDA