yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sert00:
it's a features introduced from ezekieel,author of "glados" kernel.then also franco introduced that in his kernel.the sound mod convert the internal audio chip in "high performance" mode,and it boost a little the volume of the music playback on earphone only.for me it's a very usefull features...a must from a month when i choose to stick with a kernel..for more info,contact ezekieel or franco...and google to know exactly the high perf. mode of our gnex audio chip.

trying now this kernel...but too early to say nothin because of a screwed system...need to wipe all and reflash rom first!;)
[Samsung Galaxy Nexus] arvylas:
https://github.com/Ezekeel/GLaDOS-nexus-prime/commit/97e1d920bc51449d077ae7540aa6918bbe453948
[Samsung Galaxy Nexus] ch33kybutt:
Looks useful. Will test to decide whether to include in next build.
[Samsung Galaxy Nexus] chubb16:
GREAT JOB.

took all the lag out of the latest aokp build, like night and day.
[Samsung Galaxy Nexus] nexus.prime:
Ezekeel's "Touch Wake" very useful! Please consider it :)

and "wheatley" governor / "sio" scheduler

and FSync Control
[Samsung Galaxy Nexus] kashix:
Well done ch33kybutt! I've read through all 4 pages, any idea what's the recommended speed to be setting at for optimal battery:performance. other than oc to 1420! recommended governor and your personal setting? :) thanks!
[Samsung Galaxy Nexus] nexus.prime:
Very Nice Color!!! Thanks :)
[Samsung Galaxy Nexus] kashix:
just flashed this from franco's kernel, overnight drain is very little. 3% over 5-6 hours idle. very little wakelocks as well. was just wondering would it be better to use 300 or 700 for min? default governor is ondemand I guess?

well done ch33ky!

my setting

1420/350

ondemand
[Samsung Galaxy Nexus] sruel3216:
that would be great!

Yes with headphones/aux. and correct, when listening with screen off it would lock at 200mhz. but then when i turn the screen on the min would be locked at a set freq, ex. mine would be locked at 700min when i turn it on.

thanks
[Samsung Galaxy Nexus] ArmanUV:
Wouldn't this cause streaming apps like google music/spotify/rdio to jump up to higher frequencies and eventually consume more battery life?

One question: what is the difference between 0 and 5? They look the same to me.

Another question: does PM_FAST significantly affect battery life in your experience? I noticed the it's the default.
[Samsung Galaxy Nexus] loveact:
what is BT low power in better battery stats?
[Samsung Galaxy Nexus] nklenchik:
Gonna try this out again today. I like how the colors seem a lot better than they last time I used it haha
[Samsung Galaxy Nexus] ch33kybutt:
Now testing a script which can set both Min & Max freqs when screen-off & headset inserted.

Yes, it would. So I'll make it a user-selectable option in cmplus.conf, and you'll be able to set both Min & Max freqs.

No difference, I guess. Valid gamma presets are actually from 1 to 10. 0 disables.

Good point. That's actually the default in CM9 kernel. Don't use wifi much myself, but I'll set default to PM_MAX in next build.

No idea. But this might help you: http://xdaforums.com/showthread.php?t=1387243&page=56
[Samsung Galaxy Nexus] nklenchik:
Man I would easily support you if you had an app for this thing :p
[Samsung Galaxy Nexus] sruel3216:
Thanks for the screen off script! Can't wait to test it!

+1 on an app ;-)
[Samsung Galaxy Nexus] ch33kybutt:
3.0.31-CMPlus-Tuna-120509

Changelog

* Updated to Linux 3.0.31

* Another attempt to lower VDDMIN to 800000 for "possible" further power savings (might be unstable for some)

* Misc patches from Omapzoom to help with stability on high frequencies

* Fixed voltage control issues for 528MHz MPU frequency by using FUSE_CORE_OPP100 instead

* Removed Lulzactive cpufreq governor (did not scale new frequencies as expected)

* Set PM_MAX as default wifi sleep mode

* Updated cmplus script to include screenstate optimizations

---- Screen-ON mode settings for CPU Scheduler & VM to improve responsiveness

---- Screen-OFF mode settings for CPU scheduler & VM for battery savings

---- Hotplug mode to enable/disable CPU1 based on screenstate

---- Music mode to set min & max CPU frequencies when screen-off and headset inserted

Made some changes to cmplus script to make my device run exactly how I want it to: responsive and lagfree when I'm using it, and real savings on battery when screen is off. Cmplus script now includes a screenstate mode that auto tunes CPU scheduler & VM tunables depending on whether is screen on or off. Also added a Music mode for power savings when listening to music with screen off. And yes, I did say a few posts ago that any type of hotplug would only interfere with the built-int MPU Sub System function, but it's user selectable in cmplus.conf, so you can choose to enable or disable. Enjoy.

Additions to /etc/cmplus.conf

# Enables/disables Hotplug Mode (affects CPU1)
# 0 or blank =disabled (default)
# 1 = enabled
CPU_HOTPLUG=

# Specifies minimum & maximum CPU frequency when screen-off and headset inserted
# 0 or blank = disabled (default)
# 1 = 200MHz
# 2 = 350MHz
# 3 = 528MHz
# 4 = 700MHz
# 5 = 920MHz
# 6 = 1072MHz
# 7 = 1200MHz
# 8 = 1350MHz
# 9 = 1420MHz
MUSIC_MIN_FREQ=
MUSIC_MAX_FREQ=

Modify /etc/cmplus.conf then reboot and check logcat to confirm whether it all works. Should look like something below:

I/ch33ky ( 245): [CMPlus] Loading settings from /etc/cmplus.conf
I/ch33ky ( 248): [CMPlus] Touchwake Control == 1 [0:disabled, 1:enabled]
I/ch33ky ( 249): [CMPlus] Wake delay == 30000 ms
I/ch33ky ( 250): [CMPlus] Fsync (filesystem sync) == 0 [0:disabled, 1:enabled]
I/ch33ky ( 251): [CMPlus] GAMMA Preset == 7
I/ch33ky ( 265): [CMPlus] Screen-ON: Music mode OFF - Reset MIN CPU freq to 350000
I/ch33ky ( 266): [CMPlus] Screen-ON: Music mode OFF - Reset MAX CPU freq to 1200000
I/ch33ky ( 267): [CMPlus] Screen-ON: Performance settings for CPU Scheduler
I/ch33ky ( 279): [CMPlus] Screen-ON: Performance settings for Virtual Memory
I/ch33ky ( 2292): [CMPlus] Screen-OFF: Economy settings for Virtual Memory
I/ch33ky ( 2295): [CMPlus] Screen-OFF: Economy settings for CPU scheduler
I/ch33ky ( 2297): [CMPlus] Screen-OFF: Music mode ON - Set MIN CPU freq to 200000
I/ch33ky ( 2299): [CMPlus] Screen-OFF: Music mode ON - Set MAX CPU freq to 528000
I/ch33ky ( 2303): [CMPlus] Screen-OFF: Hotplug mode - CPU1 OFFLINE
[Samsung Galaxy Nexus] mihkohuy:
Thanks but just had a try on PARANOID ANDROID rom, discovered that remain BLACK SCREEN after the Google Logo is out. Reflashed 6 MAY version and i can boot successful now
[Samsung Galaxy Nexus] muck:
Exactly the same situation for me also
[Samsung Galaxy Nexus] kevinngck1:
Just upgraded to 0905version. Signal drops problem is back:( im on aokp m5 with 1420/350. Never had that on previous version with the same cpu clock
[Samsung Galaxy Nexus] ch33kybutt:
Kinda anticipated problems due to decreased VDDMIN. Not all devices can handle. I'll upload a fixed build when I reach home later.
[Samsung Galaxy Nexus] nexus.prime:
Thanks for those settings!

How to set via init.d script?
[Samsung Galaxy Nexus] bigeyes0x0:
@ch33ky: I checked your cmplus script as it has some very interesting stuffs, but it seems like there's something wrong in it with the while loop to set screen on and off settings. Anyway as I'm also writing another init.d script for myself I ported your code over and fixed some problems:

(BGPNAME=`basename $0`
BGPID=`pidof $BGPNAME | awk '{print $1}'`;
echo -1000 > /proc/$BGPID/oom_score_adj;
while
do
cat /sys/power/wait_for_fb_wake > /dev/null
# Set screen on stuffs

cat /sys/power/wait_for_fb_sleep > /dev/null
# Set screen off stuffs
done) &

Hope it helps. Also can I use your codes/ideas in my script? I will release it sometime later with Trickster ROM.
[Samsung Galaxy Nexus] fleischbanane:
Here too.
[Samsung Galaxy Nexus] gamation:
+1
[Samsung Galaxy Nexus] ch33kybutt:
Thanks for the tip. Good ole /dev/null. But it'll still work with or without it, just better to redirect output to where it won't cause any harm.

And since Android & XDA is all about open source and sharing, do please go ahead and use all or part of it anywhere you want to. Don't worry, I won't pull an "Oracle" on you ;)
[Samsung Galaxy Nexus] nexus.prime:
temporarily, flash this in CWM recovery

delete("/system/bin/cmplus");

delete("/system/bin/list");

delete("/system/etc/init.d/98cmplus");

delete("/system/etc/cmplus.conf");
[Samsung Galaxy Nexus] Sveke:
I'll buy it 3 times
[Samsung Galaxy Nexus] ch33kybutt:
3.0.31-CMPlus-Tuna-120509-A

Changelog

* Reverted VDDMIN to previous limit of 840000

* Removed accidental inclusion of swap, cleancache, zcache & zram that I was testing

* Updated cmplus script - added /dev/null to screenstate while loop (recommended by bigeyes0x0)

Bugfix version uploaded. Original VDDMIN limit should allow kernel to run on all devices now. Also, seems I added some memory functions in the earlier build that I was testing, so duly removed them as well. Enjoy.
[Samsung Galaxy Nexus] gnexdude:
Ok bet! I'll get you a shot lol
[Samsung Galaxy Nexus] muck:
Still having the same problem, black screen on boot after the logo.
[Samsung Galaxy Nexus] bigeyes0x0:
Um, You were right that it still works but it might not work correctly:

# Exclude background process from OOM killer
bgpid=`pidof $0 | awk '{print $(NF)}'`;
echo -1000 > /proc/$bgpid/oom_score_adj;

$0 will returns /system/bin/cmplus and thus pidof command will fail, at least on my ROM, which uses original mksh and busybox from Stericson. That's why I use basename command. Fixed that and tested again revealed pidof actually does not returns the correct bgpid if I put this code snippet outside the parentheses. Thus I changed this code snippet a little, put it inside ( ) and move the & symbol after ) to run all of them in another sh process. Lastly, you use awk to get the last pid, on my ROM it's actually the first :confused:.

All of this might be because we're on different ROMs, IDK for sure, but well you might wanna check again.
[Samsung Galaxy Nexus] !crazy:
I see a typo, echo -1000 should probable be echo -n1000?
[Samsung Galaxy Nexus] gnexdude:
Thanks bro! Your kernels always kick a$$
[Samsung Galaxy Nexus] ch33kybutt:
Thanks for pointing it out. I'll check again.

No typo.
[Samsung Galaxy Nexus] nexus.prime:
Indeed...

Edit : Deleting settings files OK

http://xdaforums.com/showthread.php?p=25868271#post25868271
[Samsung Galaxy Nexus] Stefano T.:
Same problem here ;)
[Samsung Galaxy Nexus] cubsfan187:
Absolutely love this kernel!! Tried to install the newest one on a rom thru boot manager and it said there was no boot img to install. Very strange.
[Samsung Galaxy Nexus] nexus.prime:
This kernel not boot.img format but any kernel format (zImage)

1st post
[Samsung Galaxy Nexus] ch33kybutt:
Those who have problems booting, what ROM are you using?
[Samsung Galaxy Nexus] nklenchik:
No problems here with liquid 1.4
[Samsung Galaxy Nexus] nexus.prime:
CM9 nightlies 08 May

Edit : How about releasing kernel and setting separately?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jsen:
do i still need to use the cmplus.conf if i bump my speed up using setcpu?
[Samsung Galaxy Nexus] Stefano T.:
CM9 Nightly Kangs - 9 may

No problems with 6 may kernel ;)
[Samsung Galaxy Nexus] nexus.prime:
CM bah!! kernel compatibility was limited :(

ch33kybutt'd better change the kernel name :)

already not CM + alpha :D

I'll switch to the othe ROM :)
[Samsung Galaxy Nexus] KL4V1CL3:
May 9 Euroskank CM9 Kang
[Samsung Galaxy Nexus] nexus.prime:
Just now rstored IMM76I Stock from nandroid and flashed 3.0.31-CMPlus-Tuna-120509-A.zip.

Booted well! :)

Again, CM Bah!! :p
[Samsung Galaxy Nexus] ch33kybutt:
Found out that CM9's init process (run-parts) can't handle the screenstate child process, which is necessary to monitor status of screen on or off. So instead of forking a child process, the cmplus script is just left "hanging", that's why CM9 users see only a black screen after Google logo.

Guess I'll have to figure out a way around it, or maybe just wait until CM9 team implements a forkable init process, which I remember was present in CM7. But it's late now and I have a long day of work tomorrow, so guess CM-Plus will have to temporarily be CM-Minus for a while ...
[Samsung Galaxy Nexus] gamation:
Hi all,

i'm using PARANOIDANDROID Rom. Delete_cmplus.conf did the trick with version 9 - i was able to boot. But then i installed version 9_A and the black screen was back.

So i've installed version 6 - wich for works best. With this version i get beautiful rich colours and that doesn't happen with version 9. Can you tell me why?

Thank you for your great effort to develop great apps for our gnex

PG
[Samsung Galaxy Nexus] nexus.prime:
Cuz your ROM based on CM9

Edit : CM users, Flash cmplus.conf_06-MAY.zip in CWM recovery

(deleting 09-MAY settings files and installing 06-MAY's)
[Samsung Galaxy Nexus] gamation:
Ok ok thanks! And what about the differences between colour temperature?
[Samsung Galaxy Nexus] nexus.prime:
the same with 06-MAY, AFAIK :)

09-MAY's changelog does not have color-related
[Samsung Galaxy Nexus] gamation:
humm... i've justo installed 9_A and it seems like this version has the screen colours right.. maybe it was just my impression...

Thank you!

PG

---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------

Issue solved then!

:)
[Samsung Galaxy Nexus] Grillrd:
Flashed 09 then flashed this fix...works :)

Thanks
[Samsung Galaxy Nexus] sruel3216:
Cheeky, this on/off screen with music seems to be working great. awesome job with this!

edit: one bug i found with the script. i have my screen on min set to 700mhz in set cpu and in your script i have screen of min and max set to 200mhz. screen off works fine with music but when i unplug my headphones my screen on doesnt stay at 700mhz, it starts using 200mhz as my min screen on
[Samsung Galaxy Nexus] nklenchik:
Is https://github.com/downloads/ch33kybutt/kernel_cmplus_tuna/3.0.31-CMPlus-Tuna-120509-A.zip

Is this the most recent fix? I'm on my phone and can't see when it was uploaded
[Samsung Galaxy Nexus] sruel3216:
yeee
[Samsung Galaxy Nexus] nklenchik:
I got a sod earlier on the new release. Running what's in my sig, except for this kernel of course lol

Ondemand 1200/200
[Samsung Galaxy Nexus] Angelakaro:
This kernel is very good (i'm using aokp rom) just a question: color saturation and contrast are too high. How can i adjust them?
[Samsung Galaxy Nexus] ahmad.afef:
i installed this one: 3.0.31-CMPlus-Tuna-120509-A

and set cpu max:1420 and min:200 and governor: interactive

when the device go to deepsleep and i unlock it it will reboot and stuck on the boot animation

and it will get very hot

i'm sorry i can't get last_kmsg coz i restored the last nandroid to mak it boot again

i'm using bamf 1.25
[Samsung Galaxy Nexus] M3drvr:
Try it at CPU Max 1200 and see if problem replicates. Phone may not be able to handle 1420. Hense why it got so hot. Especially if its set to 1420 on boot.
[Samsung Galaxy Nexus] ahmad.afef:
it's fine with 1200 and 1350 :D just not good with 1420

now start using aokp ans it seems fine with 1420 :D

EDIT:

nop still the same

i'll just use 1350
[Samsung Galaxy Nexus] Sveke:
Try to up the voltage in the 200 slot. Your phone may not like the lower voltage.
[Samsung Galaxy Nexus] sruel3216:
so i did some more testing with the new screen on/off with music and values dont stick when i unplug headphones. maybe i explained it bad the last time so il try again:

using setcpu or franco app i set my max 1200 and min 700

with cmplus script i set it to max 350 min 200 screen OFF

So i use cpuspy while playing music and the script works...it reads im in the 200-350 range. However, when my screen is on now i believe your script overwrites what i have set in setcpu and franco because it scales down lower then the 700 slot i set that i want for screen on.

Also, if i shut the screen off, unplug the headphones and turn the screen back on, the script still overwrites my values in setcpu and changes my min to 200, instead of 700

hope this helps and isnt confusing lol. thanks again!
[Samsung Galaxy Nexus] sruel3216:
I was messing around with the interactive boost. I set it to 1 and my phone on screen stays at 920mhz I believe. So I set my min to 200mhz in setcpu to see if it would idle at 200mhz while screen is off playing music. That didn't work. However I think if u can deactivate boost while screen is off allowing it to lower to 200mhz, then at least for me I wouldn't need that script. This would keep my screen on at 920 lag free but save a lot of batter when screen is off.

I'm no dev but just a thought
[Samsung Galaxy Nexus] nklenchik:
I've been at the gym pretty much the whole time listening to music and browsing the web for 5-10 Mins. This doesn't seem right does it? I'm on the newer kernel (a) using ondemand
[Samsung Galaxy Nexus] sruel3216:
Try interactive. It uses the lower freq a lot more with music.
[Samsung Galaxy Nexus] nklenchik:
Thanks for the suggestion :P
[Samsung Galaxy Nexus] ch33kybutt:
Good feedback received. Some unforeseen issues happening. Will have to disable screenstate mode in next build while I check.
[Samsung Galaxy Nexus] nklenchik:
Screen state mode is that script you were talking about?
[Samsung Galaxy Nexus] ch33kybutt:
Yes. I'll disable it by default as it doesn't work in CM9-based ROMs. Non-CM9 users will have to modify /etc/cmplus.conf to enable it.
[Samsung Galaxy Nexus] superstargoddess:
This is the best kernel that I have tried so far. Using it at 1420 with Wheatley since I agree with the person who said that lulzactive stutters.

Unfortunately I don't know much about voltage and the other little things, so I can't customize it beyond the simple things I tweak with the Glados app, like touchwake, audio options, etc etc.

Is there a tutorial anywhere about voltages or could someone give me some optimal settings?
[Samsung Galaxy Nexus] sruel3216:
honestly i dont do any custom voltages anymore since smart reflex does it auto. i find that smart reflex has much lower voltages then i usually have when i custom uv; and its stable

---------- Post added at 09:13 PM ---------- Previous post was at 08:56 PM ----------

just had a lockscreen freeze. max 1200 min 528 interactive SR on. i was tethering and charging
[Samsung Galaxy Nexus] ch33kybutt:
This was with Screenstate mode enabled? Any last_kmsg or logcat to help shed some light?
[Samsung Galaxy Nexus] ch33kybutt:
3.0.31-CMPlus-Tuna-120510

Changelog

* Attempt again to lower VDDMIN to 800000 for "possible" further power savings

* Updated cmplus script to disable Screenstate mode by default

* Fixed some errors in /system/bin/cmplus

---- Line 137: Fixed incorrect checking of MUSIC_MIN_FREQ when should be checking MUSIC_MAX_FREQ instead

---- Line 294: Fixed awk parameter to correctly exclude child process from OOM killer

Unfortunately, users of CM9-based ROMs (Skankwich, ParanoidAndroid) will not be able to enable Screenstate mode. This is because the run-parts (init process) in CM9 does not allow forking of child processes, which is necessary in my script to sense whether screen is ON or OFF. So Screenstate mode is disabled by default (see below)

# Enables/disables Screenstate modes
# 0 = disabled
# 1 = enabled (DO NOT ENABLE IF USING CM9-based ROM!!!)
SCREENSTATE=0

Those using other ROMs (stock & AOSP based) have to modify the above line to enable Screenstate mode. Hotplug and Music mode are dependent on Screenstate mode, so ensure that Screenstate mode is enabled when you enable Hotplug or Music mode.
[Samsung Galaxy Nexus] nexus.prime:
Yeap, booted well on CM9 now :)

(CM9 nightly 08 MAY)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] avyonix:
I find that the versions after the 120506 build, my phone does not stay in deep sleep for longer periods...seems like some kind of wakelock taking place? To confirm this i reflashed the 120506 and it reverts back to staying in deep sleep for longer periods. The settings i edited in the cmplus script were the same in both 120506 and later versions. I will try get a logcat when i get back home and when i figure out how to:o
[Samsung Galaxy Nexus] gknnn':
With 3.0.31-CMPlus-Tuna-120510 i lose Signal sometimes at deep sleep.

I'm on AOKP (AOSP ROM) M5 and enable Screenstate mode because using hotplug.

Someone got this problem too?
[Samsung Galaxy Nexus] nklenchik:
Sorry if I missed it but how exactly are we enabling screenstate in the new kernel, is it in terminal?
[Samsung Galaxy Nexus] gknnn':
Think the rest you should know how to edit on the file.
[Samsung Galaxy Nexus] nexus.prime:
http://xdaforums.com/showthread.php?p=25907174#post25907174

Edit /system/etc/cmplus.conf with Root Explorer or ES File Explorer etc

...

# Enables/disables Screenstate modes with RootExplorer or ES File Explorer etc
# 0 = disabled
# 1 = enabled (DO NOT ENABLE IF USING CM9-based ROM!!!)
SCREENSTATE=[B][COLOR="Red"]1[/COLOR][/B]

...

---------- Post added at 08:44 PM ---------- Previous post was at 08:18 PM ----------

06-MAY

10-MAY Screenstate mode disabled

10-MAY Screenstate mode enabled
[Samsung Galaxy Nexus] ch33kybutt:
Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nexus.prime:
"deep sleep for longer periods"

10-MAY Screenstate mode enabled

Excellent Kernel! :)
[Samsung Galaxy Nexus] nklenchik:
Am I in the right direction here? :D
[Samsung Galaxy Nexus] ch33kybutt:
Where do you want to go ... today?
[Samsung Galaxy Nexus] nklenchik:
Hahaha oh just the little lake house. I just had to enable 1 for both of those correct?
[Samsung Galaxy Nexus] avyonix:
Thanks so much.
[Samsung Galaxy Nexus] ahmad.afef:
this kernel is the best

but it seems like it don't work for me @ 1420MHz :(
[Samsung Galaxy Nexus] mariotme:
Hey Cheeky

sorry for the OT but u just wanted to ask you if you will ever consider developing an app for your kernel features?
[Samsung Galaxy Nexus] Treatcon:
What app are you using to monitor temp and CPU, top left of notification bar?
[Samsung Galaxy Nexus] sruel3216:
hey cheeky,

i dont thing the screen off work exactly right still. once i turn my screen on it still uses the screen off freq rather then the freq i use in setcpu
[Samsung Galaxy Nexus] !crazy:
Screen of works only in combination with headset or what? I don't see an option for min-max screenof frequencies besides MUSIC_(MIN|MAX)_FREQ...
[Samsung Galaxy Nexus] sruel3216:
Yes that's what I am referring to. Screen off with headset
[Samsung Galaxy Nexus] wisefreakz:
What about this guys.... acceptable?
[Samsung Galaxy Nexus] pats4life100:
So I just instal kernel And that's it
[Samsung Galaxy Nexus] ch33kybutt:
Maybe

System Tuner

Works fine on mine. Tried using Setcpu, Nstools, ROM control and even setting manually using adb. Couldn't get it to bork no matter what I did.

Yes.
[Samsung Galaxy Nexus] M3drvr:
Love the tweaks in this app. Thanks for the share!
[Samsung Galaxy Nexus] ArmanUV:
Hi ch33kybutt, Can you add a tun and cifs module mount to the script? I hate having to redo my init.d scripts everytime I flash CM9 nightlies.

Speaking of CM9, do you think they'll fix the run parts issue soon?
[Samsung Galaxy Nexus] ch33kybutt:
tun & cifs are built-in to the kernel, same as stock CM9 kernel. I don't use either myself, so guess you'll have to figure out how to use them with the respective app.

Also, I've managed to workaround CM9's run-parts "no forking" problem. Basically just added a stupidly simple fix to /system/bin/sysinit, so will be releasing a new build soon.
[Samsung Galaxy Nexus] nexus.prime:
the problem with the following?

CM9's init.rc to support init.d

# Run sysinit
exec /system/bin/sysinit

class_start core
class_start main

and /system/bin/sysinit

#!/system/bin/sh

export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper /system/xbin/run-parts /system/etc/init.d

general init.rc supporting init.d

service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
class late_start
user root
group root
[Samsung Galaxy Nexus] ch33kybutt:
Yes. It really is a stupidly simple fix ... just place an "&" at the last line of /system/bin/sysinit so that init process can continue.

I'm now testing a couple of multicore and multithread optimizations in the kernel, so will release new build only after my tests.

Sent from my Galaxy Nexus