[KERNEL] Semaphore ICS 1.3.0

Search This thread

stratosk

Recognized Developer
Mar 3, 2011
6,224
31,853
Thessaloniki
www.semaphore.gr
Stratosk, are you going to implement smooth_ui in the regular 1.1.0 kernel too?

... tapatalked

Yes, of course. It was not in my plans for 1.1.0 version.
It just was a last-night-before-fell-asleep-tiny-idea and I implemented few hours ago to test if it will improve smoothness.
Actually the GPU accelerated UI is already smooth enough and maybe the smooth_ui tuner is odd, but you never know.
 

cr4zy.b0y

Senior Member
Feb 7, 2010
557
72
Bucharest RO / Wels AT
Thank you for your understanding.

Forgive me. I'm not quite sure I understand what are these incompatibilities. Can you please clarify this?

dont know how to explain ... with voltage control and other tools (advanced slim settings ASS - at performance section) there are 2 governors: ondemand and performance; nstools statistics shows that my phone doesnt use deep idle; cpu spy shows that deep idle works (i believe it works because battery drain during the night -deep sleep- is about 2-3%) ... dont know if it's the right word "incompatibilities" :confused:... srry if i said something silly or false, i'm not a developer or programmer - i just flash and enjoy :)
 

stratosk

Recognized Developer
Mar 3, 2011
6,224
31,853
Thessaloniki
www.semaphore.gr
This made me think. I'm using Ondemand Smoot UI right now and Voltage Control only has Ondemand and Performance just like cr4zy.b0y said. Voltage Control applies settings a few seconds after boot. Which one will stand? The one chosen on Semaphore app or Voltage Control?

Voltage control uses an init.d script S71voltctrl or a startup service. Both are running after the S10xxxxx Semaphore init.d scipt for governor selection. So, Voltage control will override your governor settings.

Also, Voltage Control display only Ondemand and Performance because conservative and smartass are built as modules in Semaphore. You have to load the modules to have them available.
 

cr4zy.b0y

Senior Member
Feb 7, 2010
557
72
Bucharest RO / Wels AT
This made me think. I'm using Ondemand Smoot UI right now and Voltage Control only has Ondemand and Performance just like cr4zy.b0y said. Voltage Control applies settings a few seconds after boot. Which one will stand? The one chosen on Semaphore app or Voltage Control?

semaphore app control, ofcourse :p!!! it comes along with the kernel, right? just like mnics kernel with its app "midnight control" ( i'm not sure about app name, but is something like this:confused: )
 

stratosk

Recognized Developer
Mar 3, 2011
6,224
31,853
Thessaloniki
www.semaphore.gr
dont know how to explain ... with voltage control and other tools (advanced slim settings ASS - at performance section) there are 2 governors: ondemand and performance; nstools statistics shows that my phone doesnt use deep idle; cpu spy shows that deep idle works (i believe it works because battery drain during the night -deep sleep- is about 2-3%) ... dont know if it's the right word "incompatibilities" :confused:... srry if i said something silly or false, i'm not a developer or programmer - i just flash and enjoy :)

Of course my friend. :) I didn't mean that you said something silly. I am just trying to understand what the issue. About the 2 governors please read my previous post.

About the deep idle: NSTools and cpu spy display 2 different things.
NSTools displays deep idle and cpu spy displays deep sleep. These are 2 different CPU states. You may find more details in my Deep Idle Guide (the link in first post).

If NSTools does not display anything (0 values) you have to enable Deep Idle statistics in Semaphore application.


Edit: Yes, Semaphore Script Manager application, thanks to HM.Carbide. You may control Semaphore's features from there.
 
Last edited:

Fenvarien

Senior Member
Dec 22, 2010
963
598
Yes, of course. It was not in my plans for 1.1.0 version.
It just was a last-night-before-fell-asleep-tiny-idea and I implemented few hours ago to test if it will improve smoothness.
Actually the GPU accelerated UI is already smooth enough and maybe the smooth_ui tuner is odd, but you never know.

Great :) The test version works very stable and fast with the latest CM9 nightly.

... tapatalked
 

misterpro

Senior Member
Dec 30, 2007
85
29
Tried 1.1.0 test version, but there's something wrong for me... (I'm on ICSSGS RC4.2, with the 720p Slim kernel support patch)

Everything is working as it should, untill I try to manually reboot. Semaphore Logo comes up and nothing else happens. Only way to get it to boot is by clearing init.d Then the phone starts up fine, but the first manual reboot after that it's stuck on the Semaphore logo again. (I tried to wait 15 minutes to make sure it's not just being slow)

So long story short... 1.1.0 doesn't work for me because it ONLY starts up the very first time. After choosing my governor etc it can't startup fully. (launch cwm recovery works fine, just normal startup to OS fails)

I tried both

SmartassV2, semaphore autobrightness Normal, Low Memory Killer 60MB supercharge
Ondemand, semaphore autobrightness Normal, Low Memory Killer 60MB supercharge

both failed to startup fully after the first time.

Back to 1.0.1s for now.

Anybody on 1.1.0, could you try to reboot your phone to check if you have the same problem?

Excuse me for quoteing myself, but...

I just tried 1.1.0s and it does the exact same thing in combination with ICSSGS RC4.2 (huge ram patched). First startup all fine. Working perfectly. Reboot phone and it fails to startup (only clearing init.d gets it to start up) and then the next reboot will fail again.

Some change between 1.0.1s and 1.1.0(s) seems to make this kernel incompatible with ICSSGS rom (at least if you want to be able to reboot your phone after the very first startup).

Weird. Back to 1.0.1s again for now.
 
Last edited:

cr4zy.b0y

Senior Member
Feb 7, 2010
557
72
Bucharest RO / Wels AT
Voltage control uses an init.d script S71voltctrl or a startup service. Both are running after the S10xxxxx Semaphore init.d scipt for governor selection. So, Voltage control will override your governor settings.

Also, Voltage Control display only Ondemand and Performance because conservative and smartass are built as modules in Semaphore. You have to load the modules to have them available.

noob Q: how to load them, from app or via CWM? i read in semaphore's app thread that the .zip files with addons are for GB :confused:
 

dastinger

Senior Member
Dec 2, 2010
895
307
Voltage control uses an init.d script S71voltctrl or a startup service. Both are running after the S10xxxxx Semaphore init.d scipt for governor selection. So, Voltage control will override your governor settings.

Also, Voltage Control display only Ondemand and Performance because conservative and smartass are built as modules in Semaphore. You have to load the modules to have them available.
Thanks! So, from what I understand, I'm not using Ondemand Smooth UI right now because Ondemand is chosen on Voltage Control. Is there any Voltage app that doesn't change the governor I want to use?
 
Last edited:

stratosk

Recognized Developer
Mar 3, 2011
6,224
31,853
Thessaloniki
www.semaphore.gr
Thanks! So, from what I understand, I'm not using Ondemand Smooth UI right now because Ondemand is chosen on Voltage Control. Is there any Voltage app that doesn't change the governor I want to use?

I was talking generally. If you select ondemand smoothui in Semaphore, most probably Voltage Control has nothing to change. So, your selection will remain. But if you select conservative (for example) in Semaphore app then voltage control will override this.

Selecting your governor in Semaphore application is enough. You don't need any other application.
 

dastinger

Senior Member
Dec 2, 2010
895
307
I was talking generally. If you select ondemand smoothui in Semaphore, most probably Voltage Control has nothing to change. So, your selection will remain. But if you select conservative (for example) in Semaphore app then voltage control will override this.

Selecting your governor in Semaphore application is enough. You don't need any other application.
I thought that Ondemand Smooth UI would be changed to regular Ondemand by Voltage Control once the Startup service was loaded that's why I asked.

I know I don't need another app to select governors..was just wondering if there was any voltage control application that doesn't override options regarding Governor/Scheduler etc ;)

Thanks for the answers and the continued support :)
 

stratosk

Recognized Developer
Mar 3, 2011
6,224
31,853
Thessaloniki
www.semaphore.gr
I thought that Ondemand Smooth UI would be changed to regular Ondemand by Voltage Control once the Startup service was loaded that's why I asked.

I know I don't need another app to select governors..was just wondering if there was any voltage control application that doesn't override options regarding Governor/Scheduler etc ;)

Thanks for the answers and the continued support :)

Every similar application use a mechanism to persist the user selections. When 2 applications try to set the same thing there will be a race condition. The application which will set last it's settings will be the winner.

But, I don't recommend use multiple apps for these, except if you know what exactly you are doing.
 

Fenvarien

Senior Member
Dec 22, 2010
963
598
I thought that Ondemand Smooth UI would be changed to regular Ondemand by Voltage Control once the Startup service was loaded that's why I asked.

I know I don't need another app to select governors..was just wondering if there was any voltage control application that doesn't override options regarding Governor/Scheduler etc ;)

Thanks for the answers and the continued support :)

My solution is to create the S91voltctrl script with Voltage Control (don't use the service), in the script I just remove those few lines regarding Scheduler and Governor. So just scaling and UV are applied and nothing interferes with Semaphore. :)

Just my example:

#!/system/bin/sh
##################################################
## Voltage Control boot script by xan and nitr8 ##
##################################################
LOG_FILE=/data/volt_scheduler.log
rm -Rf $LOG_FILE

echo "Starting Insanity Volt Scheduler $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;
echo "Sleeping for 20 seconds to workaround oc not setting properly on stock derivatve roms..."
sleep 20
echo "Ok lets start working"
echo "Set MIN Scaling Frequency" | tee -a $LOG_FILE;
echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo ""
echo "---------------"

echo "Set MAX Scaling Frequency" | tee -a $LOG_FILE;
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo ""
echo "---------------"

#UV_BEGIN#

echo "Set UV" | tee -a $LOG_FILE;
echo "1250 1150 975 825 800 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo ""
echo "---------------"

#UV_END#




echo "Insanity Volt Scheduler finished at $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;

... tapatalked
 
Last edited:
  • Like
Reactions: dastinger

PatcheZ

Senior Member
May 6, 2008
320
21
was waiting for you kernel before finally switching over to the 'newer' cm9 nightlies. so far so good on cm9 nightly (0425) with 1.10.

Many thanks, Stratosk
 

dastinger

Senior Member
Dec 2, 2010
895
307
Report:

After using Semaphore 1.1.0s with Smooth UI for 4h~ I say that it really looks smoother/faster. Mainly navigating through app drawer and homescreens and opening apps. I cleaned Dalvik before flashing the kernel so it might be feeling smoother because of that as well. These are only first impressions. Will report back on the next few days about this.

PS: Since I have no idea of what this does, I'll just report about things that I feel that are smoother than before. Only clue is the governor's name :D
PSS: On Slim 3.4 btw.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 597
    This is a kernel based on the pawitp's one and it works for Android 4.0.x ICS ROMs.


    Features

    - LiveOC
    - Custom Voltage
    - Voodoo Sound
    - BLN
    - 373.5MB - 398.7MB available RAM
    - Compiled with Linaro 4.7.2
    - O3 optimization
    - Semaphore Script Manager 0.75
    - Auto brightness driver
    - Touch Wake
    - Vibration intensity
    - Deep Idle
    - USB host driver
    - Governor ondemand (default)
    - ondemand: sampling_down_factor tunable by momentum, smooth_ui
    - Governor conservative (module, smooth_ui)
    - Governor smartassV2 (module, smooth_ui)
    - Noop I/O scheduler (default)
    - Deadline I/O Scheduler (module)
    - Simple I/O Scheduler (module)
    - CFQ I/O Scheduler (module)
    - Netfilter (iptables) as modules
    - CIFS as module
    - TUN as module
    - Logcat disabled (as module only)
    - Standard network packet scheduler
    - Kernel log buffer size 4KB (from 128KB)
    - Reduced debug info
    - TinyRCU
    - Fast Charge support
    - WiFi PM_MAX when suspend
    - CWM 6.0.1.0
    - /system/etc/init.d directory creation if not exist

    In order to load various modules of the kernel and enable or disable features use HM.Carbide's Semaphore Script Manager application. It automatically copies and runs the respective scripts from /res/scripts to /system/etc/init.d directory. The scripts:

    - S05enable_oc_0800 (disable overclocking - caps max freq to 800Mhz)
    - S05enable_oc_1000_default (disable overclocking)
    - S05enable_oc_1100 (enable overclocking - max freq 1100MHz)
    - S05enable_oc_1140 (enable overclocking - max freq 1140MHz)
    - S05enable_oc_1200 (enable overclocking - max freq 1200MHz)
    - S10enable_gov_conservative (load and enable conservative governor module)
    - S10enable_gov_ondemand_default (enable ondemand governor)
    - S10enable_gov_smartassV2 (load and enable conservative smartassV2 module)
    - S15enable_sched_deadline (load and enable the deadline I/O scheduler module)
    - S15enable_sched_noop_default (enable noop scheduler)
    - S15enable_sched_sio (enable and load SIO scheduler module)
    - S20enable_netfilter (load netfilter modules for firewall or WiFi, USB tethering)
    - S30enable_logger (enable logging)
    - S35enable_tun (load tun module)
    - S40enable_cifs (load cifs module)

    Custom Voltage may be configured with Voltage control or similar applications.

    For more information check the semaphore kernel website: www.semaphore.gr

    For questions or issues about Semaphore Script Manager please visit HM.Carbide thread

    Thanks to Superuser, you may download a wonderful custom bootanimation for CM9 from http://www.semaphore.gr/downloads/boot-animations


    Thanks to

    pawitp for his kernel.
    zacharias.maladroit for his useful information about CM's initramfs
    HM.Carbide for his Semaphore Script Manager application.
    Ezekeel for LiveOC, Custom Voltage
    sztupy for USB host driver
    koush for CWM
    xcaliburinhand for his work about dock support
    mialwe for his vibrator intensity and other fixes
    ShadowInkDesigns for Android logo
    trailblazerz11 for his help with Linaro and other changes
    DerTeufel1980 for various hints

    All people who support this kernel by testing, reporting issues, donating or simply using it.


    Change log

    1.3.0 (30/07/2012)
    - added CFQ scheduler as module
    - in call volume settings (thanks to DerTeufel for his hint)
    - fix charging display for car dock (thanks to pawitp)
    - CWM 6.0.1.0 (thanks to koush) *
    - CWM: added AROMA Filemanager (thanks to amarullz)
    - compiled with Linaro 4.7.2 201207

    Normal versions (for CM9 or ROMs without hugemem configuration)
    1.3.0
    - 373.5MB - 385.7MB

    For Slim ROM or patched ROMs with hugemem configuration
    1.3.0s
    - 386.5MB - 398.7MB

    * Nandroid backups with CWM 6 are not compatible with previous versions.



    1.2.6 (07/07/2012)
    - USB mass storage disable write speed cache support (thanks kasper_h, DerTeufel1980 for the hint)
    - CWM: Allow key to repeat on hold (thanks to FaultException, koush). Works for volume up, down and touch key menu (as down)
    - CWM: fix selection bar color when battery < 21%
    - CWM: upstream sync (thanks to koush) *
    - initramfs sync some changes with CM9 (adb works in root by default in recovery)
    - compiled with linaro 4.7.1 201206

    Normal versions (for CM9 or ROMs without hugemem configuration)
    1.2.6
    - 373.5MB - 385.7MB

    For Slim ROM or patched ROMs with hugemem configuration
    1.2.6s
    - 386.5MB - 398.7MB

    * Please note that due to changes in nandroid backup/restore, previous versions of Semaphore can't restore backups from version >= 1.2.6. To be on the safe side, please renew your backups.


    1.2.5 (19/06/2012)
    - rebased to 3.0.17 (thanks to trailblazerz11 and eugene373 for their github)
    - compiled with Linaro 4.7.1 toolchain (thanks to trailblazerz11 for his help)
    - O3 optimization flag
    - upstream sync (fixes for cdma in-call volume and mic gain included, thanks to pawitp, efpophis)
    - WiFi PM_MAX when suspended
    - fixed 800MHz underclocking
    - changed boot splash screen

    Normal versions (for CM9 or ROMs without hugemem configuration)
    1.2.5
    - 373.5MB - 385.7MB

    For Slim ROM or patched ROMs with hugemem configuration
    1.2.5s
    - 386.5MB - 398.7MB


    1.2.2 (01/06/2012)
    - Bootloop detection (if no normal boot is detected the phone will be forced to recovery in next boot) *
    - bugfix: enabling Wi-Fi hotspot twice (copy the new netfilter script in order this to work by disabling and then enabling again netfilter in Semaphore app)
    - creation of /system/lib/modules if does not exist
    - removed LMK scripts
    - fix some typos in scripts description (thanks to cdmackay, HiKsFiles)

    * It doesn't mean that this will necessarily resolve the known bootloop issue, but it may help on bootloops because of bad OC/UV etc.



    Full changelog: http://www.semaphore.gr/changelog/ics-version
    Deep Idle Guide and FAQ


    Sources

    The Linux Kernel
    Samsung Kernel sources
    Semaphore kernel sources


    Please use it at your own risk!

    The attachment zip files are for flashing from CWM recovery.
    The attachment tar files are for flashing through Heimdall/ODIN.

    Attachment files md5sum:

    4a963c5183993b256c5a0d52f88bc2c7 Semaphore_ICS_1.2.6.zip
    408178563587859c31a4c5a90b394166 Semaphore_ICS_1.2.6s.zip
    3a0ca16342f811dfd9666ce3633a20b6 Semaphore_ICS_1.2.6.tar
    c53114e74530e68c3b5cddb424343e8b Semaphore_ICS_1.2.6s.tar
    753748fba3b590babcbfb76857bf609d Semaphore_ICS_1.3.0.zip
    a6f0d7c9d2254d9a178248d48cf3de45 Semaphore_ICS_1.3.0s.zip
    1e71744541d74fdd60d6b43c2dc767c7 Semaphore_ICS_1.3.0.tar
    09e1e9806dc84c9c2e2341e38ebd51b0 Semaphore_ICS_1.3.0s.tar


    Alternative download from http://www.semaphore.gr/downloads/gt-i9000-ics

    1.2.5e Euro 2012 - Spain Special Edition
    100
    Deep Idle Guide and FAQ

    This was really unexpected. Unfortunately I can't answer all these questions and comments. So I tried to write a guide and a FAQ for deep idle. Feel free for suggestions and corrections. Source: Samsung's SPV210 RISC Microprocessor User's Manual. Hope it clarifies some things.


    Deep Idle Guide and FAQ

    When the phone has no actions to perform, because you leave it alone or for example contacts are not synchronizing or gmail application is not fetching a new mail e.t.c., then the best thing that the phone has to do is to go to... sleep (suspend). In this state the phone consumes very little power.

    There are also 5 other power schemes that the processor s5pv210 can use to reduce power consumption: Normal, Idle, Deep Idle, Stop and Deep Stop. We are interested in the first three states Normal, Idle and Deep Idle.

    In Normal state the CPU is running, that is, some software is running.
    In Idle state the CPU core is idle, that is, the CPU core clock is disabled but the remaining parts of s5pv210 are running.
    In Deep Idle state the CPU core power is supplied but is powered off by the internal power switch. The remaining parts of processor may become power gated except the Audio power domain for low power MP3 playback.
    Samsung in gingerbread kernels used only the Idle scheme. Deep Idle was implemented in the kernel but it was disabled by default. All known GB custom kernels have enabled Deep Idle state.

    With stock kernels only Normal, Idle and Sleep states are used. Examples of these states use:

    Normal state: User uses browser, or reading emails, watching video etc
    Idle state: User listen to music and screen is off, no other software is running.
    Sleep state: No user activity, screen is off, no activity of background services and processes.

    Kernel checks many times per second different factors and decides which power state to use.
    Deep Idle can be used as a better alternative of Idle state and the major benefit is when user listen to music. Then IF and only if all other conditions (factors) are satisfied the kernel decides to go to Deep Idle. That is, as we mentioned, CPU powered off, TOP powered off and L2 cache is powered off. Only Audio is on and that's why we have a major benefit. Another option of Deep Idle is the TOP=ON which means that the TOP module is still powered. This is used when bluetooth is enabled (powered).

    Regarding power consumption, Sleep is always the desired state. Below the states ordered by the power they consumes (Normal consumes more power):

    Normal -> Idle -> Deep Idle (TOP=ON) -> Deep Idle (TOP=OFF) -> Sleep


    FAQ

    How to enable Deep Idle?
    a) Simply check the Deep Idle option in Semaphore Script Manager or b) use this command on a terminal emulator or adb shell:
    echo 1 > /sys/devices/virtual/misc/deepidle/enabled

    How to enable Deep Idle Statistics?
    a) Simply check the Deep Idle Statistics option in Semaphore Script Manager or b) use this command on a terminal emulator or adb shell:
    echo 1 > /sys/devices/virtual/misc/deepidle/stats_enabled

    Why statistics are not enabled by default?
    Simply for saving CPU cycles. Kernel checks for entering Deep Idle (or Idle) many thousand times per minute. So, disabling statistics we have less overhead in CPU. What is the difference? Not to much, but better little than nothing.

    What is TOP?
    S5PV210 internal modules are grouped into 11 power domains based on their functions. One of these domain is the TOP and it includes these modules: Clock Management Unit (CMU), GPIO(OFF), Bus components, VIC, TZIC, Internal memory (IROM and IRAM), NAND controller, OneNAND controller, CF controller, SRAM controller, Peripheral DMA, Memory DMA, CoreSight, JTAG, Modem interface, Security sub-system, TSI, HSMMC, USB HOST, USB OTG, DRAM controller, CHIPID, IEM_IEC, Security key, SPDIF, PCM, SPI, KEYIF, TSADC, I2C, I2S channel 1 and 2, AC97, PCM, System timer, Watchdog timer, UART.
    So, Deep Idle with TOP=OFF power gates all the above modules.

    How to check if Deep Idle works?
    Enable Deep Idle and Deep Idle statistics then run music player and select your favorite music (it must be your favorite song in order to deep idle work properly). Switch the screen off and wait few seconds (or wait until your favorite song is finished). Check with this command in a terminal emulator or adb shell deep idle statistics:
    cat /sys/devices/virtual/misc/deepidle/idle_stats

    Alternatively you may just open the idle_stats file in the above directory using a root explorer like application.

    I only get TOP=ON statistics
    Bluetooth or GPS or Vibrator is running

    How to power down Bluetooth?
    Use this command:
    echo 1 > /sys/devices/platform/bt_rfkill/rfkill/rfkill0/soft
    Unfortunately I didn't manage to find a way to enable it again. I tried an rfkil script but it doesn't work for me. If you find a way, please let me know.

    I only get Idle statistics (neither TOP=ON nor TOP=OFF)
    Something is preventing kernel to enter in deep idle state. This maybe normal. For example:
    LCD controller is enabled
    USB is connected
    TV encoder is working
    G3D (GPU) is active
    MFC (multi format codec) is active
    SDMMC controller is active
    etc.

    How can I find what is preventing deep idle?
    That's why I implemented dflags in deep idle. Kernel check many factors to decide if it can enter deep idle. All these check are encoded in dflags. dflags is an integer number. If you read this number and decode it in binary you will get the results of the last check. Each check is a bit set in binary format. For example:
    dflag = 3 binary = 11. This means that LCD controller and camera are active. (Please note that I disabled camera check for preventing kernel entering deep idle). The flags in dflags (most of the are self explanatory):
    0 S5PV210_PD_LCD
    1 S5PV210_PD_CAM
    2 S5PV210_PD_TV
    3 S5PV210_PD_MFC
    4 S5PV210_PD_G3D
    5 SND_S5P_RP
    6 S5P_CLKGATE_IP0
    7 S5P_CLKGATE_IP1
    8 S5P_CLKGATE_IP3
    9 loop_sdmmc_check
    10 check_usbotg_op
    11 check_rtcint
    12 check_idmapos

    You may enable debugging with
    echo 1 > /sys/devices/virtual/misc/deepidle/ddebug_enabled

    The you may use this script to get the value of dflags every second.

    Code:
    #!/system/xbin/busybox sh
    
    while true; do
            cat /sys/devices/virtual/misc/deepidle/dflags
    
            sleep 1
    done

    Leave it to run and try to enter your phone in deep idle. The switch on the screen and read the last values and convert the to binary. Values 0 or 1 lead to deep idle. Other values lead to Idle.
    92
    How to build Semaphore kernel

    Prerequisites
    Basic knowledge of Linux is required to be able to build the kernel. We will also need a modern Linux box (preferably).

    Basic Setup
    First, we need to setup a directory in which we will clone the kernel and initramfs repositories. In this guide, we will setup them in /tmp but you can do it in any directory you want.

    In a terminal we run:

    Code:
    mkdir /tmp/semaphore
    cd /tmp/semaphore

    Then we clone the basic kernel repository:
    Code:
    git clone https://github.com/stratosk/samsung-kernel-aries

    Finally we clone the initramfs repository:
    Code:
    git clone https://github.com/stratosk/ics-ramdisk

    OK, first step done. We got the code. Now we have to do some preparation and compile it.

    Configuration
    I prefer to use a mini ugly script to compile the kernel and pack it. It's located in the root of the kernel tree (/tmp/semaphore/samsung-kernel-aries/sbuild.sh)

    We open this file with an editor of our choice (I prefer vi) and edit:
    1) The two lines with the 'make' command, changing the CROSS_COMPILE= option. We need to set the path from the cross compiler toolchain. I use the one that it's included in CM9 repository.
    2) The line starting with the 'find' command, changing the kernel source directory and destination directory of the modules location. This is into the initramfs directory. In our example it's /tmp/semaphore/ics-ramdisk/ics_combo/files/modules

    The Semaphore's kernel configuration is located in the file config_sema in the root kernel directory. So, we need to copy this file as .config:

    Code:
    cp config_sema .config

    Then we run this command to start the Linux kernel configuration utility (again change the CROSS_COMPILE according to your toolchain directory):
    Code:
    make CROSS_COMPILE=/kernels/semaphore_cap/android/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- ARCH=arm menuconfig

    We go to 'General Setup' section and we change the 'Initramfs source files' option to /tmp/semaphore/ics-ramdisk/ics_combo/
    We also need to change the next 2 options User ID and Group ID to whatever uid and gid we are logged in in the Linux box. In my case is 500,500. We exit and save the configuration.

    Compiling
    Now we are ready to build the kernel!

    We just run:
    Code:
    ./sbuild.sh

    We wait few minutes (time depends on the machine) and hopefully the compilation will end.

    The script will produce 2 files.
    1) /tmp/semaphore/samsung-kernel-aries/arch/arm/boot/zImage
    2) /tmp/semaphore/ics-ramdisk/cwm/Semaphore_ICS_1.2.0s.zip

    These are the 2 known files that we can flash via Heimdal or CWM respectively.
    68
    Please accept my apologies

    I'm sorry for your issues.

    And I have no more desire to build new versions. At least for now.

    @all

    Please accept my apologies about this comment.

    I guess I was very tired trying to prepare the new version, and hearing about these problems and almost no comments about the new stuff make me decide to stop this project.

    But, during the day and after reading all these beatiful comments from all of you, I realized that Semaphore is part of my life. It sounds a little bit exceeding saying this but it's true.
    For almost a year this project and most of all the communication with all of you is an important part of my life.

    And it would be unfair for all of you and for me to kill Semaphore.

    @Znida
    I'm sorry. My commect was general and I didn't mean to blame you for anything.

    @mialwe
    Thanks about your comment my friend. It's good to hear that from a person like you.

    @bennybaz
    Thanks so much trying to help. Beers it's not the issue. As I said I work on Semaphore for year and the $600 is not the reason I still working for this.
    Of course it's a huge help for me and many thanks to everybody who donate to me.

    @greasyguy
    Thanks mate, really appreciated.


    @all
    Thanks again for your nice comments. You gave me the motivation to start working again. THANK YOU!
    67
    Thank you all of you! Your help and your support is awesome!