[KERNEL] Semaphore ICS 1.3.0

Search This thread
By:
Advanced…
dastinger

dastinger

Senior Member
Dec 2, 2010
895
307
@badworker

Search some pages back for a tutorial for Heimdall.

-----

I'm having trouble as well for some days now. Didn't say anything earlier because I wanted to make sure it was Semaphore. I did a clean flash of AOKP B32. Flashed JW4 w/ PIT using ODIN -> Hard Reset -> Flashed B32 -> Let it boot -> Restored /data from a Nandroid -> Flashed Semaphore. I always used Semaphore with AOKP with this settings:

OC: 1140
Ondemand
Simple I/O
Lock Min Scaling Frequency
Deep Idle

Voltages:

Screenshot_2012-04-18-23-37-00.png


(Apart from the 1140 frequency which I had running on 1300mV. Changed it to purely test if that was the issue)

All ran well on M4, Build 30 and 31. Since I flashed 32 that I get random reboots using these settings. I tried to disable OC, still random reboots. Disabled UV. Still random reboots. Yesterday I flashed B32 again without wiping and stayed on Glitch for a day. Used exactly the same settings regarding OC, scheduler, UV etc. It ran perfectly. About 2 hours ago I decided to have another go with Semaphore 1.0.1s and, 45 minutes later, reboot. Thing is, I'm not always doing something on the phone. I can be watching a video and it reboots, I can be browsing forums in Tapatalk, stop and, seconds later, reboot etc etc. I really love AOKP as I really love Semaphore so I want to keep this combo. I know lots of users have this combo on their phones running perfectly so it's not an incompatibility issue.

What should I do? Is there any way I can get a logcat at the time of the reboots? If so, how? I don't know anything more I can do. Help.

PS: Could anyone tell me, please, what are the default kernel voltages?
PSS: I had the same issues both on 1.0.0s and 1.0.1s.
PSSS: Ran Kernel Cleaner Script and cleared both init.d and NS Tools settings everytime I changed kernels.
 
Last edited:
yahyoh

yahyoh

Senior Member
Nov 7, 2011
4,867
1,929
Amman
badworker said:
I was listening to music with my sgs and suddently the phone starts 'clicking' (like BSOD in windows when the music is playing, if you know, the sound were like that).
Then I removed battery and put back on, the phone doesn't boot.
I can't go into recovery nor boot normally, it goes in bootloop.

There's some way to flash this kernel via odin or something similar, without loosing any data?

I don't really know if the problem is kernel-side or rom-side, I believe that's something wrong with kernel but I can't confirm.

The operation that I made today:
flashed a new modem.
installed Voltage Control (locking max freq to 800MHz when display's off).

I used this configuration since semaphore 1.0.1s and CM9 04-19 were released:
SGS with CM9 04192012 + Semaphore 1.0.1s + lock min freq to 100MHz and a little UV, I've never had any kind of problem with this configuration until this evening.

ty
Click to expand...
Click to collapse
just reflash an odin kernel or flash recovery fix from here the reflash the kernel u like the go to advanced in recovery thn reboot recovery then try to clear ns tool then clean init.d scripts then wipe cache an dalvik and see if it work
dont forget to restore init.d scripts when it work :D
 
contactfornitish

contactfornitish

Senior Member
Jul 8, 2011
137
19
New Delhi
Now this is something that is beyond horrible.

This is not the case always but as many reported, battery life is not that good as been earlier. I also understand that it might be an issue with ICSSGS ROM but can not understand that why others not facing such issue.

Sent from my GT-I9000 using XDA
 

Attachments

  • uploadfromtaptalk1334967457728.jpg
    uploadfromtaptalk1334967457728.jpg
    45 KB · Views: 712
scuba156

scuba156

Senior Member
Apr 28, 2011
575
759
Melbourne
www.codesourceproject.com
HM.Carbide said:
I can't see the SemaphoreScripts folder.

The tests folder has to be lowercase, and I am not sure about the .txt extension and the file rights.

Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse

That's within the SemaphoreScripts folder (the current directory is shown at the top of the screen).

'tests' was renamed to 'Tests' to disable the script to allow the default bt_off script. The .txt extension worked fine for me, i haven't seen any source (not sure if you use open source anyway), but it seems to ignore any file extensions for anything in there. I've never had an issue with the script. My issue was with incorrect OC/UC values, i don't have the issue now, just pointing out what happened for me.

Sent from my GT-I9000 using Tapatalk 2
 
nieohl

nieohl

Senior Member
Sep 8, 2011
790
44
Having random boot. Just got woke up and turned on my phone, as i was watching tv, after like 10mins, i heard my phone, it was the notification sound, then i checked it. It was rebooted by itself. I know it was rebooted because it has super backup, email notification on my status bar. They said it was kernel issue.. :/
I was on semaphore 1.0.0bm btw.

Sent from my GT-I9000 using xda premium
 
L

LoqOs195

Senior Member
Apr 28, 2011
174
14
I cant sync with any devices using bluethoot, the devices can not found my sgs :(

Enviado desde mi GT-I9000 usando Tapatalk
 
dchawk81

dchawk81

Senior Member
Nov 21, 2010
652
49
Is there a way to fix the screen rotation and the backwards home and back capacitive buttons on my Captivate?
 
T

the_stift

New member
Sep 12, 2007
4
0
Hamburg
I am using Rom: Slim ICS v3.3 with the semaphore kernel 1.0.0s
and I have the problem that adb v1.0.29 cant reach my phone anymore.
I got adb working over WIFI but not with usb :-/
Any ideas what I can do?
 
Last edited:
dastinger

dastinger

Senior Member
Dec 2, 2010
895
307
dastinger said:
@badworker

Search some pages back for a tutorial for Heimdall.

-----

I'm having trouble as well for some days now. Didn't say anything earlier because I wanted to make sure it was Semaphore. I did a clean flash of AOKP B32. Flashed JW4 w/ PIT using ODIN -> Hard Reset -> Flashed B32 -> Let it boot -> Restored /data from a Nandroid -> Flashed Semaphore. I always used Semaphore with AOKP with this settings:

OC: 1140
Ondemand
Simple I/O
Lock Min Scaling Frequency
Deep Idle

Voltages:

Screenshot_2012-04-18-23-37-00.png


(Apart from the 1140 frequency which I had running on 1300mV. Changed it to purely test if that was the issue)

All ran well on M4, Build 30 and 31. Since I flashed 32 that I get random reboots using these settings. I tried to disable OC, still random reboots. Disabled UV. Still random reboots. Yesterday I flashed B32 again without wiping and stayed on Glitch for a day. Used exactly the same settings regarding OC, scheduler, UV etc. It ran perfectly. About 2 hours ago I decided to have another go with Semaphore 1.0.1s and, 45 minutes later, reboot. Thing is, I'm not always doing something on the phone. I can be watching a video and it reboots, I can be browsing forums in Tapatalk, stop and, seconds later, reboot etc etc. I really love AOKP as I really love Semaphore so I want to keep this combo. I know lots of users have this combo on their phones running perfectly so it's not an incompatibility issue.

What should I do? Is there any way I can get a logcat at the time of the reboots? If so, how? I don't know anything more I can do. Help.

PS: Could anyone tell me, please, what are the default kernel voltages?
PSS: I had the same issues both on 1.0.0s and 1.0.1s.
PSSS: Ran Kernel Cleaner Script and cleared both init.d and NS Tools settings everytime I changed kernels.
Click to expand...
Click to collapse
About this:

I tried Devil XL 0.72 with the same configurations apart from Voltages. Tried both stock and the ones .:Crack:. advised on THIS post..just didn't OCed so much. Stayed with 114%. Got the same results as I do on Semaphore. Random reboots. So, right now, the only stable kernel for me is Glitch that I am running without any issues, again.

I am backing up everything atm to do a Factory Reset and flash Build 33. Will try Semaphore without restoring from a Nandroid. Will only restore user apps + data, SMS and Contacts using separate apps to do it. Will flash Semaphore 1.0.1s on that rom and see how it goes.

Btw, I don't know if this is of any help but I don't get full reboots but fast reboots. I mean, I don't get to see the i9000 screen, it jumps to boot animation when it reboots.

Will leave feedback later. Hope this clean install solves the issue. Fingers crossed.
 
nieohl

nieohl

Senior Member
Sep 8, 2011
790
44
Anyone gets random boots sometime? Because i do. They said it was kernel problem. So don't think of me wrong. :)
On slim 3.3 atm.
Sent from my GT-I9000 using xda premium
 
J

JJustin

Senior Member
Dec 16, 2010
224
30
BC (Bell)
I get random reboots / SOD sometimes. Maybe once every 3 days if I don't reboot the phone. At first I thought it was because my phone couldn't handle overclocking, but I can play play CPU and GPU intensive games and it's stable. I now just chalk it up to the random bugs of ICS.
 
ZioGTS

ZioGTS

Senior Member
Jun 11, 2011
837
427
Samsung Galaxy Tab S4
Samsung Galaxy A54 5G
JJustin said:
I get random reboots / SOD sometimes. Maybe once every 3 days if I don't reboot the phone. At first I thought it was because my phone couldn't handle overclocking, but I can play play CPU and GPU intensive games and it's stable. I now just chalk it up to the random bugs of ICS.
Click to expand...
Click to collapse

I don't think ICS has any "random bug" dude... My SGS is perfectly stable, never had a single reboot, even with 20% LiveOC (that I stopped using when I understood everything's smooth even without OC, and battery lasts way more). I guess your problems are related to your config, not to ICS itself.
 
  • Like
Reactions: doc_2nas, habylab and stratosk
oci.05

oci.05

Member
Dec 8, 2010
36
2
Hey Guys Help please...

Hello guys i'm running ICSSGS RC4.2 ROM for ics. i flashed semaphore ICS 0.9.1 and i'm loving it so far. but i see their is a new V1.0.1... is this one kernel better??? for the ROM... and by the way how can i remove the Semaphore Boot load :D i want it just the Goggle log back...

Thanks in Advance
 
brfsa

brfsa

Senior Member
Dec 1, 2008
266
35
Bangkok
Slim 3.3

I was getting few random reboots, locked phone and nstools settings not sticking.
I think it was because some settings was messed up with nstools and semaphore. when I rebooted NStools would LiveOC to 120% even thou I choose 110%.

what I did was:
1. Recovery mode -> Advanced menu
2. Clean NSTOOLS settings
3. Clean init.d scripts
4. Reflash Semaphone 1.0.1s
5. reboot

Now it's working perfectly, no more reboots or crashes, here are my settings:

110% liveOC
Min: 110MHz
Max: 1100MHz

Voltage
1275 -> 1250 (-25)
1200 -> 1175 (-25)
1050 -> 1025 (-25)
950 -> 925 (-25)
950 -> 900 (-50)

I used 115% with above voltages I did not get reboots, but I dont like to force the cpu too much.

What I noticed too is that Min CPU keeps going back to 220MHz, even I set Lock GPU to 100Mhz in Semaphore application.

[Slim 3.3]
 

Attachments

  • Screenshot_2012-04-22-16-54-12.jpg
    Screenshot_2012-04-22-16-54-12.jpg
    24.9 KB · Views: 484
  • Screenshot_2012-04-22-16-55-42.jpg
    Screenshot_2012-04-22-16-55-42.jpg
    20 KB · Views: 481
  • Screenshot_2012-04-22-16-55-55.jpg
    Screenshot_2012-04-22-16-55-55.jpg
    21.4 KB · Views: 473
  • Screenshot_2012-04-22-16-54-31.jpg
    Screenshot_2012-04-22-16-54-31.jpg
    30.6 KB · Views: 456
stratosk

stratosk

Recognized Developer
Mar 3, 2011
6,224
31,853
Thessaloniki
www.semaphore.gr
Leonardus97 said:
Does this kernel support swap? If not it should! :D
Click to expand...
Click to collapse

No, and It will not.


brfsa said:
I was getting few random reboots, locked phone and nstools settings not sticking.
I think it was because some settings was messed up with nstools and semaphore. when I rebooted NStools would LiveOC to 120% even thou I choose 110%.

what I did was:
1. Recovery mode -> Advanced menu
2. Clean NSTOOLS settings
3. Clean init.d scripts
4. Reflash Semaphone 1.0.1s
5. reboot

Now it's working perfectly, no more reboots or crashes, here are my settings:

110% liveOC
Min: 110MHz
Max: 1100MHz

Voltage
1275 -> 1250 (-25)
1200 -> 1175 (-25)
1050 -> 1025 (-25)
950 -> 925 (-25)
950 -> 900 (-50)

I used 115% with above voltages I did not get reboots, but I dont like to force the cpu too much.

What I noticed too is that Min CPU keeps going back to 220MHz, even I set Lock GPU to 100Mhz in Semaphore application.

[Slim 3.3]
Click to expand...
Click to collapse

The cpu will go to 200 (or 220 if you OC) when GPU is active. Nstools display the min scaling frequency when it loads. Then the cpu (because of GPU inactivity) goes down to 100. You may check it from a terminal emulator or from adb shell:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

The option in Semaphore app does work.

About reboots. Try to uninstall NStools and select your options from Semaphore app.
 
You must log in or register to reply here.

Similar threads

cantIntoCode
  • Locked
[ROM][ICS][I9000] Team ICSSGS RC4.2
Replies
13K
Views
5M
cantIntoCode
cantIntoCode
stratosk
[KERNEL] Semaphore JB 3.3.0 / KK 3.4.3
Replies
8K
Views
2M
F
fathi48
stratosk
[KERNEL] Semaphore 2.7.4 (CF-Root + Voodoo Snd v10 + OC/UV + BLN)
Replies
8K
Views
2M
P
Patryk2003
P
  • Locked
[ROM][ICS][IML74K] teamhacksung's CM9 ALPHA for Galaxy S (BUILD 17) BUG REPORTS ONLY
Replies
15K
Views
6M
P
pawitp
O
  • Locked
[DEV] ICS port for I9000/I9000B - BETA (ICS sources) - work in progress
Replies
5K
Views
2M
Whiskey103
Whiskey103

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 597
    stratosk
    stratosk
    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
    View
    100
    stratosk
    stratosk
    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.
    View
    92
    stratosk
    stratosk
    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.
    View
    68
    stratosk
    stratosk
    Please accept my apologies

    stratosk said:
    I'm sorry for your issues.

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

    @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!
    View
    67
    stratosk
    stratosk
    Thank you all of you! Your help and your support is awesome!
    View

New posts