yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nexus.prime:
Verified! :)

/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 [COLOR="Red"][B]&[/B][/COLOR]

booted well with 10-MAY, Screenstate mode enabled

(flash the attatched file, CM9_sysinit.fix.zip)
[Samsung Galaxy Nexus] avyonix:
But....phone still doesnt stay that long in deep sleep..tried on both CNA as well as Trickster ROMs. However it enters deep sleep normally when i use the 6May kernel. I use 350 min 1072 max freq.
[Samsung Galaxy Nexus] nexus.prime:
logcat on terminal emulator :)

(ROM : CM9 Nightly 10-MAY / Kernel : CMPlus 10-MAY)
[Samsung Galaxy Nexus] CMNein:
You can b/u system files with a script in addon.d: http://xdaforums.com/showthread.php?t=1617356
[Samsung Galaxy Nexus] ch33kybutt:
I'll have a look at changes made since 6 MAY for anything that might have affected race-to-idle. But my device enters deep-sleep almost as soon as screen is turned off, so I don't really expect to find anything. Most likely a wakelock preventing your device from sleeping, so go and use BetterBatteryStats to find out.
[Samsung Galaxy Nexus] sruel3216:
maybe im using it wrong...

say in setcpu i set max 1200 and min 700

in your script i set sceen off to max 350 min 200

when you unplug your headphones your min changes back to 700 on its own? mine doesnt switch back to 700. it will use the 350 and 200 slot until i switch it manually again. can anyone recreate this?
[Samsung Galaxy Nexus] ch33kybutt:
Just tried above settings. Works fine. Check logcat for CMPlus entries.
[Samsung Galaxy Nexus] ch33kybutt:
3.0.31-CMPlus-Tuna-120511

Changelog

* Enabled ARM sched_mc & sched_smt (multi-core & multi-threading) support

* Added simple workaround to CM9's run-parts "no-forking" problem

---- Screenstate mode (Screen-ON = performance, Screen-OFF = economy) now enabled by default

* Misc patches from android/kernel-common

Thanks to a simple sysinit workaround, users of CM9-based ROMs (CM9, Skankwich, ParanoidAndroid) can now enable Screenstate mode, and also Music mode & Hotplug. Also enabled support for sched_mc & sched_smt which is supposed to improve CPU scheduler's decision making when dealing with multi-core chips and multi-threading.
[Samsung Galaxy Nexus] sruel3216:
hmm ok il give it a try again
[Samsung Galaxy Nexus] nklenchik:
Do I have to edit the cmplus bin file again if I flash the new kernel over?

Edit: Sod on Liquid with today's kernel

Edit 2: I think it was a profile I had set in setcpu, you can disregard that
[Samsung Galaxy Nexus] !crazy:
Could you please guide me how to start that cpu and temp monitor in statusbar? I am looking at the app options and cannot find it...
[Samsung Galaxy Nexus] ch33kybutt:
Settings > Notification packages > Notification packages > click on Play logo left of "Installed packages" > Download your desired ST Icons packages > Go back to System Tuner and Activate packages > Exit System Tuner > Profit :)
[Samsung Galaxy Nexus] drunkboi:
Screenstate mode is ON by default for 120511 or needs to be enabled? Thanks!
[Samsung Galaxy Nexus] nexus.prime:
http://xdaforums.com/showthread.php?p=25971365#post25971365
[Samsung Galaxy Nexus] drunkboi:
I'm half asleep OR just a crack head. It's clearly stated. Thank you!
[Samsung Galaxy Nexus] ch33kybutt:
I'm aware that we sometimes need that extra boost for certain tasks (been playing some ShadowGun lately :p), so been working on getting 1.5GHz stable on our device. Finally successful in using it without having the device freeze during stress tests. Works really well with Ezekeel's wheatley governor. Will do some real-world tests for a day, and if all's well, will release in next build.

Also, in response to feedback of visible slowdowns in the past few builds. It's due to enabling the Gamma Preset (contrast control). Since it's a software-only function, it takes cpu cycles away from other processes and this results in reduced responsiveness. So next build will have only Screenstate enabled, with all other options (touchwake, fsync, gamma preset, etc) left blank. Up to you to modify cmplus.conf to your preference.
[Samsung Galaxy Nexus] drunkboi:
I wanted to say thanks for the Gamma Preset! I was very unhappy until I came across your Gamma settings. I can set them myself now since you have them in your signature, but just wanted to say for me your Gamma settings are PERFECT!
[Samsung Galaxy Nexus] nexus.prime:
Hi ch33kybutt

11-MAY, Startup script does not work

please look into that

(replacing with 10-MAY's configuration files on 11-MAY kernel, working well)
[Samsung Galaxy Nexus] ch33kybutt:
Which ROM?
[Samsung Galaxy Nexus] nexus.prime:
IMM76I stock, ROM issue?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bigeyes0x0:
Stock ROM ramdisk does not support init.d and ch33ky's kernel CWM zip does not add this feature last I checked. Maybe it's that. You can try apply this IMM76I modded ramdisk with stock kernel first.
[Samsung Galaxy Nexus] nexus.prime:
Thanks, but I edited ramdisk to support init.d so 10-MAY conf files works well

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ch33kybutt:
But he's saying it worked before. Strange. I'll check when I get home later.
[Samsung Galaxy Nexus] nexus.prime:
Thanks, solved :)

updated busybox and then works well

maybe 11-MAY conf files requires the latest busybox?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] !crazy:
I am on Black Ice 35 and I have noticed that the touch wake doesn't work and I don't know how to get rid of trinity kernel blue colors. I thought that has something to do with ram disk so I tried flashing some reset kernels before flashing CMPlus again, but that didn't help.

Anyone with a suggestion or hint what the reason could be and could I do about?

@ch33kybutt, thanks for system tuner instructions (and other stuff : )), will try them later.
[Samsung Galaxy Nexus] ch33kybutt:
Which version was it?
[Samsung Galaxy Nexus] nexus.prime:
I don't know what version is necessary

I just extracted from the latest CM9 and installed (v1.20.0-CM9)

the attatched file, flashable zip in recovery
[Samsung Galaxy Nexus] !crazy:
Strange, I got that version perinstalled with Black ICE 35 and it didn't work. I installed stericson 1.20, that doesn't work either.

I have tried to execute script with Rom Toolbox and I only get a lot of 'not found' errors, which sadly refer only to line numbers and not exact commands.
[Samsung Galaxy Nexus] !crazy:
I have reinstalled busy box and touch wake works now even if I am still getting errors in From Toolbox and trinity colors are still there..
[Samsung Galaxy Nexus] ch33kybutt:
Post the error log.
[Samsung Galaxy Nexus] nexus.prime:
install BlackICE 35 boot.img and reinstall CMPlus kernel

(the attached file flashable zip BlackICE 35 boot.img)
[Samsung Galaxy Nexus] ch33kybutt:
3.0.31-CMPlus-Tuna-120512

Changelog

* Added 1500MHz CPU frequency

* Enabled APM (Advanced Power Management)

* Enabled ARCH_POWER for ARM architecture dependent CPU power management

* Reset lower limits VDDMIN to 840000 for stability, as Smartreflex isn't all that smart

* Prevent random WiFi MAC address by hardcoding it (Imoseyon)

* Patched interactive governor with latest commits

* Misc OMAP patches from Imoseyon, Codeaurora and Omapzoom

* Added enable/disable of KSM (Kernel Samepage Merging) in Screenstate modes

* Reset all settings to default in /etc/cmplus.conf

So, after a whole day of real-world testing on 350-1500MHz on Wheatley governor, pleased to report that I did not get a single freeze/reboot. And checking dmesg logs, I was surprised to find little evidence of thermal throttling. I've had my device running over 1600MHz before, but only with Smartreflex disabled, and the thermal throttling got so bad that it ran even worse than at 920MHz. So I feel confident enough to provide 1500MHz CPU frequency for power users. Let me just repeat that 1200MHz should be high enough for most users, and I don't recommend going higher than that. So only the use the 1500MHz frequency for situations that really warrant it (for me, they're ShadowGun & Six Guns :P).

Also, some of you gave feedback that UI seems a little slower, and the culprit is the gamma preset (contrast control) which is a software-only UI mod, so it steals cpu cycles from other critical system processes, such as SystemUI. Whilst I look at a workaround to that (by increasing priority levels for certain system processes), I've decided to set all parameters in /etc/cmplus.conf to default settings, only enabling Screenstate mode. That means that ALL other features (touchwake, fsync, gamma preset, etc) will be disabled by default. So you'll just have to copy it to /sdcard/cmplus.conf and set your own preferences. Ch33rs!
[Samsung Galaxy Nexus] franciscofranco:
What were your findings with APM and ARCH_POWER enabled? I once tested ARCH_POWER enabled, but I saw no difference.
[Samsung Galaxy Nexus] ch33kybutt:
No hard evidence, but enabling both seems to help stability at high freqs. Changed too much stuff to be sure. Just a gut feeling, or it could be the curry I just had :p.
[Samsung Galaxy Nexus] pats4life100:
Wats the best governor for battery
[Samsung Galaxy Nexus] pats4life100:
How to get touch wake to work
[Samsung Galaxy Nexus] nexus.prime:
2nd post

http://xdaforums.com/showpost.php?p=24545601&postcount=2

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

...

# Enables/disables Touchwake (tap to reactivate screen after timeout)

# 0 or blank = disabled (default)

# 1 = enabled

TOUCHWAKE=1

# Sets time to keep Touchwake active after screen timeout, in milliseconds

# 0 = indefinite (default=45000)

WAKE_DELAY=

...
[Samsung Galaxy Nexus] ch33kybutt:
One man’s meat is another man's poison. And only royalty can afford to employ food tasters.
[Samsung Galaxy Nexus] nexus.prime:
Hi ch33kybutt

Thanks for the update :)

btw, setting 200 ~ 1500 MHz but my device does not use 1420 and 1500 MHz

How about you?
[Samsung Galaxy Nexus] ch33kybutt:
After one round in Stability Test - Scaling
[Samsung Galaxy Nexus] nexus.prime:
Ah! I want to learn "Stability Test"
[Samsung Galaxy Nexus] ch33kybutt:
https://play.google.com/store/apps/details?id=com.into.stability
[Samsung Galaxy Nexus] tcchuin:
ch33kybutt, please consider developing an app and sells it on play.

maybe you'll say

"I do this for masochistic tendencies fun, so won't accept donations. But if you feel the inescapable urge to part with your ill-gotten gains hard-earned savings, then why not donate to where it actually matters."

what about you take the income and donate to those party?
[Samsung Galaxy Nexus] nexus.prime:
thanks for the heads up

but my phone still does not use those frequencies :(
[Samsung Galaxy Nexus] mariotme:
Would love too see this too :)
[Samsung Galaxy Nexus] nklenchik:
Hmm links down?

Edit: nope lol https://github.com/ch33kybutt/kernel_cmplus_tuna/downloads
[Samsung Galaxy Nexus] nexus.prime:
links not down

http://github.com/ch33kybutt/kernel_cmplus_tuna/downloads

3.0.31-CMPlus-Tuna-120512.zip
[Samsung Galaxy Nexus] superstargoddess:
+1 to that. I've been using Glados app to tinker with it, would love to see it have its own app!
[Samsung Galaxy Nexus] nklenchik:
Ch33ky, anyway we can get the Lulzactive governor in the next release?
[Samsung Galaxy Nexus] ch33kybutt:
New freqs seem to have borked it. Been trying to fix but no joy so far.

Taking a break for a few days. Real life finally caught up with me. So no new builds for a while. Off to cook the best Mother's Day meal for my dearest!
[Samsung Galaxy Nexus] franciscofranco:
Nothing like a few days off Android to relax. Enjoy it.
[Samsung Galaxy Nexus] CMNein:
You've been turning out a kick ass kernel; I'm very happy with the current iteration. Very few hiccups along the way, and considering this started for your personal use, I've been pleased to see the awesome results and changes along the way.

Unless your significant other and/or mother are interested in coding on this day, or any other day, dinner is probably the best choice :cool:
[Samsung Galaxy Nexus] gnexdude:
Just want to say that the 12.05.10 release F---ing rock!!! Its giving me insane battery on 350/1072 setting. I downloaded the latest release, but this one is working just right for me. Thanks again cheeky...:)
[Samsung Galaxy Nexus] nexus.prime:
cheeky kernel

hope the name changed in the next release :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ArmanUV:
unfortunately, I got a freeze and then a sod (while playing music with screen off) shortly after enabling the screen-state functionality (350mhz-920mhz). No last_kmsg though.
[Samsung Galaxy Nexus] ch33kybutt:
Hotplug on or off?
[Samsung Galaxy Nexus] ArmanUV:
on.
[Samsung Galaxy Nexus] ch33kybutt:
That's the reason for SOD, then. Recommend Hotplug OFF and let MPUSS handle CPU1 suspend.
[Samsung Galaxy Nexus] wisefreakz:
Here is a proof about the so claimed "satanic kernel" where we gain battery instead if losing... lol
[Samsung Galaxy Nexus] M3drvr:
I'm having issues where it won't use 1420 or 1500 if I'm set to Max 1500. Will only use frequencies up to 1350. Otherwise its a great kernel. Smooth and terrific battery life.
[Samsung Galaxy Nexus] nklenchik:
Had a strange, idk what to call it on the new kernel this morning (forced me back to Franco for now). I went to bed, phone at 99%, woke up and it was on with a dark grey screen with the led light staying on white. Couldn't do anything but a battery pull and when I rebooted it was at 62%
[Samsung Galaxy Nexus] ch33kybutt:
Lol. Think I'll blame .... unusual solar activity for that.
[Samsung Galaxy Nexus] ch33kybutt:
Which governor?
[Samsung Galaxy Nexus] nklenchik:
Hotplug off

Interactive, 1450/200

Maybe it was the 1450 thing? No idea but I'll just wait until the next release and test

Oh but while I'm here, any more governor options available? I know you said Lulzactive was a no go but what about Intellidemand?
[Samsung Galaxy Nexus] tndb:
I had trouble running my phone with 200mhz so try up it to 350 (default) and see if problem persist as i also had to do a batt pull but it went away when i upped the lowest speed to 350mhz
[Samsung Galaxy Nexus] M3drvr:
I'm using interactiv
[Samsung Galaxy Nexus] gnexdude:
Cheeky, I TOLD you so lol...your kernels need exorcism!!!
[Samsung Galaxy Nexus] wisefreakz:
Hahahahaha... agree!!!
[Samsung Galaxy Nexus] ArmanUV:
ok I disabled hotplug (in fact I'm using the default script now).

This morning, my alarm app went off and I snoozed it (as usual :p). 10 minutes later I woke up to a freezed phone and extremely high tempreture. It wasn't too hot to touch but damn it was close. I panicked and removed the battery instantly.

Hopefully there is a way to debug this (wherever the problem is, I'm using CM9 nightlies).
[Samsung Galaxy Nexus] ch33kybutt:
There is. Post /proc/last_kmsg
[Samsung Galaxy Nexus] ArmanUV:
I meant besides last_kmsg. It wasn't generated (in fact, I've never seen a last_kmsg when my phone freezes, only when it reboots)
[Samsung Galaxy Nexus] ch33kybutt:
Maybe you could provide more details, such as ROM, cpufreq governor, min & max freqs, hotplug on\off, then I could try to replicate the scenario.
[Samsung Galaxy Nexus] !crazy:
I was having that issue too, and since I set SCREENSTATE=0 it didn't happen any more.
[Samsung Galaxy Nexus] nexus.prime:
+1 here. will set SCREENSTATE=0
[Samsung Galaxy Nexus] ArmanUV:
CM9 Skankwitch, interactive 350-1350, screen state off, hotplug off, default script.

maybe it was a one time weiredness.
[Samsung Galaxy Nexus] M3drvr:
Really enjoying this kernel. Using Max 700 on interactive and everything nice n smooth for everything I do. Even web browsing is a joy. Battery life is good too.
[Samsung Galaxy Nexus] nklenchik:
When can we see some new releases? I'm having withdrawals haha
[Samsung Galaxy Nexus] ch33kybutt:
Lol, didn't I say I was taking a break? Actually testing some scheduler tweaks which improve responsiveness, and also waiting for Linux kernel 3.0.32 to drop.
[Samsung Galaxy Nexus] nklenchik:
Oh yeah I forgot about that haha no problem though, take as much time as you'd like :p
[Samsung Galaxy Nexus] ch33kybutt:
Found out the most likely reason for the above reported cases is a bug in the cmplus script for Screenstate mode, which inadvertently allocated 100% of CPU bandwidth to real-time tasks when screen-off. So what most likely happened is that a run-away real-time task managed to lock up your devices and consume all CPU bandwidth. Totally doofus move on my part, so sincerest apologies. But now that I've found it, it will be fixed in next build. Not only that, but finding that bug helped me to better tweak and allocate CPU bandwidth in Screenstate mode, and I must say that UI is really responsive with the new CPU scheduler tweaks.
[Samsung Galaxy Nexus] metroidnemesis13:
This may be considered a double post, but I can report also that I have had problems with 911.

I was robbed yesterday (my other galaxy nexus was stolen) as well as a Samsung Galaxy S II Skyrocket. I tried calling 911 but my phone would not dial out to emergency services. It said "Call Failed" with no ring and 55 seconds on the call time. I tried this about nine times before I went into a target and used their phone. My phone calls everyone else fine. I just tried again and it still does this. I was never able to get through.

My Gnex is running May 8th's nightly. Luckily I was not bleeding out or anything, but this might need to be fixed. Still love the ROM and all the developers who work on it.

Here is the original post

http://xdaforums.com/showthread.php?p=26173884
[Samsung Galaxy Nexus] ch33kybutt:
Bad luck, dude. Glad you're okay. The thing is, android kernel has nothing to do with emergency calling. What ROM and Baseband were you using?
[Samsung Galaxy Nexus] metroidnemesis13:
It probably doesn't. I was just adding onto that guy's experience that it didn't work.

Baseband: I9250XXKK6

Cyanogenmod Version:

9-20120508-NIGHTLY-maguro
[Samsung Galaxy Nexus] avyonix:
Wrong thread then..:)
[Samsung Galaxy Nexus] nklenchik:
Superb battery life today. I unplugged at 7:45am and now it's 9:51pm with 40% battery left. This is texting all day, some web browsing, and 2 hours at the gym. Awesome!
[Samsung Galaxy Nexus] spr33:
What govenor/speeds are you using?
[Samsung Galaxy Nexus] nklenchik:
Interactive 200/1350

I actually debated doing this but it works fine...

Set a profile in setcpu so screen off min is at 200 and max is at 350. It helps with the music I play and I haven't seen any problems. Mostly stays at 200 but sometimes it needs a little extra and hits 350.
[Samsung Galaxy Nexus] Ibanez33:
Have you tried having a higher max when the screen is off?

only as a test with this whole idea of race to idle that it finishes what it was doing faster so it can drop to 200 sooner.. outside of the time when you playing music of course :)
[Samsung Galaxy Nexus] nklenchik:
I probably should but then I'd have to set up a system for when I want it to be a low min and a higher one :D
[Samsung Galaxy Nexus] nexus.prime:
Hi ch33kybutt

updater-script in your installer

ui_print("No need to wipe cache or dalvik-cache");
ui_print("Just reboot");

Kernel has nothing to do with cache or dalvik-cache?
[Samsung Galaxy Nexus] wisefreakz:
This is known bug in CM roms....
[Samsung Galaxy Nexus] ch33kybutt:
Absolutely nothing.

cache

Basically used to store temp files: used by recovery to store log and temp files, used by android to store OTA updates, some Market downloads, DRM files, attachment previews, etc.

dalvik-cache

Holds data for each app, which are re-aligned, optimized & verified extracted classes from classes.dex.

So maybe wiping cache BEFORE flashing is useful to clear up some space for img files, but wiping dalvik-cache is useless when installing a kernel, but at least not harmful.
[Samsung Galaxy Nexus] nexus.prime:
Thanks for your explanation :) I should never wipe them while flashing the kernels!
[Samsung Galaxy Nexus] ch33kybutt:
3.0.31-CMPlus-Tuna-120518

Changelog

* Reduced WiFi voltage to 1.85V

* Re-added SMP commits from Linux 3.4

* Enabled SCHED_DEBUG & SCHED_AUTOGROUP for better control of CPU scheduler

* Updated cmplus script

--- Fixed bug which resulted in runaway real-time processes when screen off

--- Added additional CPU scheduler parameters to Screenstate mode

--- Added option to control screen_off_max_freq

* Misc updates from Omapzoom & Codeaurora
[Samsung Galaxy Nexus] superstargoddess:
Oh sweet jeebus, yay!
[Samsung Galaxy Nexus] avyonix:
Super!!!!!!, deep sleep issues no longer present. Thanks ch33kybutt.
[Samsung Galaxy Nexus] droidholic:
Looks like I am back to the previous version. Tried making a phone call with my VoiP app and as soon as the screen goes dark, people cannot here and I seem to have data drops. I have disabled most of the functions in the conf file.

Never had this issue with the previous version. Not really sure how to provide a log. It seems, at least on my phone, that when the screen goes dark, apps using data notice a drop. Great kernel, otherwise.
[Samsung Galaxy Nexus] franciscofranco:
Why did you enable sched_debug?
[Samsung Galaxy Nexus] droidholic:
No idea what that is, assuming the question was directed at me.
[Samsung Galaxy Nexus] dreamhunterr:
Best kernel. Congratulations to you (and all the Samsung Galaxy Nexus developers who have their code in it) :)
[Samsung Galaxy Nexus] pats4life100:
This mite be a crazy question but how do u run script
[Samsung Galaxy Nexus] leos0000:
Thanks ;) .... cool kernel :) ... work perfect on aokp 36 abd faster
[Samsung Galaxy Nexus] resynx:
loving this kernel, works perfectly on paranoid android :)
[Samsung Galaxy Nexus] M3drvr:
I find vibration is too weak. The haptic vibration feels right but vibration for notifications is weaker. And its not in the script to change anymore?
[Samsung Galaxy Nexus] franciscofranco:
No, it's directed to ch33kybutt.
[Samsung Galaxy Nexus] nklenchik:
No problems here with it enabled. In fact to be completely honest, everything seems snappier
[Samsung Galaxy Nexus] ch33kybutt:
1420 & 1350 use the same OPP, thus the same voltage, so you must have less than optimal silicon. 1200MHz should be enough for most purposes anyway.

He's got some pretty edgy stuff there, but other that SIO, don't want to veer too much away from stock CM kernel. An experimental version maybe ...

Why in all the kernel threads does everyone keep asking "what is the recommended speed/setting"? Each of us have very different usage profiles. The proof of the pudding is in the eating, they say. Anyway, I use 350-1200 and a tweaked conservative governor, which is responsive enough for my needs. Probably the most graphics intensive game I play would have to be Temple Run and it runs lagfree at this setting.

Also, next build will include the following:

- Optimized CPUfreq governors (conservative, interactive and ondemand)

- Added V(R) and SIO I/O schedulers (SIO as default)

- Ezekeel's sound control (modified for 3.0.27 CM kernel)

- Simple init.d script to customize sound control, color control & fast charge
[Samsung Galaxy Nexus] kashix:
thanks for your great work once again! can't wait for this kernel to get any better!
[Samsung Galaxy Nexus] ch33kybutt:
3.0.27-CMPlus-Tuna-1204101623

Changelog

- Merged with stock CM kernel

- Added SIO & V(R) I/O schedulers (SIO as default)

- Optimized conservative, interactive and ondemand cpufreq governors

- Added Ezekeel's Sound Control (modified for 3.0.27 CM kernel)

- Added init.d startup script for customizing sound control, color control and fast charge settings
[Samsung Galaxy Nexus] barrist:
nice work!

is sound control high perf mode on by default?
[Samsung Galaxy Nexus] kashix:
nope, edit the initialization script. default is 0 which is off. enable it to 1 to on it!

not sure if it's kernel related. but if I open whatsapp. and I remove it from the recent apps and I try to launch it again, it takes several seconds to start it.
[Samsung Galaxy Nexus] nexus.prime:
Very Nice Job!

looking forward to "Touch Wake" :)