yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] slg60:
Perhaps noob question, but why Phone is waiting more than 60 seconds with Google logo before booting?

Is there a sense behind?

Can I adapt it into the init.d?

There's something from 60 seconds sleep mentioned!?

Nice work, kernel is performing quiet well!
[Samsung Galaxy Nexus] barrist:
Thanks. Although perhaps I'm not looking at the right file but it seems to be enabled by default along with volume boost to 3?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nexus.prime:
I deleted /system/etc/cmplus.conf and /system/etc/init.d/98cmplus, using the following script

#!/system/bin/sh

#########
#Voltage#
#########

echo "1350 1350 1330 1267 1153 975" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

##############
#CPU settings#
##############

#Maximum Frequency
echo "1200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
#Minimum Frequency
echo "350000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

#Scaling Governor
echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

#I/O Scheduler
echo "sio" > /sys/block/mmcblk0/queue/scheduler
echo "sio" > /sys/block/mmcblk0boot0/queue/scheduler
echo "sio" > /sys/block/mmcblk0boot1/queue/scheduler
echo "sio" > /sys/block/mtdblock0/queue/scheduler

########
#Tweaks#
########

#BLX
echo "96" > /sys/class/misc/batterylifeextender/charging_limit

##Color Control

#V1 Gamma Offsets
echo "55" > /sys/class/misc/samoled_color/red_v1_offset
echo "56" > /sys/class/misc/samoled_color/green_v1_offset
echo "54" > /sys/class/misc/samoled_color/blue_v1_offset
#default 60 60 60

#Color Multipliers
echo "1420000000" > /sys/class/misc/samoled_color/red_multiplier
echo "1780000000" > /sys/class/misc/samoled_color/green_multiplier
echo "2100000000" > /sys/class/misc/samoled_color/blue_multiplier
#default 2004318071 2004318071 2004318071

##Sound Control

#Headset Volume Boost
echo "0" > /sys/class/misc/soundcontrol/volume_boost

#High Performance Audio
echo "0" > /sys/class/misc/soundcontrol/highperf_enabled

##USB Fast Charge
echo "0" > /sys/kernel/fast_charge/force_fast_charge
[Samsung Galaxy Nexus] ch33kybutt:
Erm, then maybe you shouldn't do that. Does it also hurt when you poke yourself in the eye? But seriously, I don't use whatsapp much so can't relate. Try with different governors to see which works best for you. Might also be related to some so-called virtual memory tweaks that you may already have running. Point being, it's all conjecture until more info is provided.

I'm using BlackIce ROM, which is based on AOKP, and ROM control settings take effect around 40 secs or so after boot. So the "sleep 50" seconds command enables my settings over ROM settings. But you shouldn't really be waiting the full 50 seconds, as the init process should be multi-threaded, as in AOKP, and should continue to boot despite the sleep command. What ROM are you using? Feel free to remove that line.

Default refers to kernel setting without startup script. The startup script is customized to MY personal preference, so you have to either disable it or modify it to your own liking.

Yep. More than 1 way to skin a cat.
[Samsung Galaxy Nexus] adamski.ufo:
This kernel great! :)

KalimochoAz's strong basis + ch33kybutt's additions "as it should be"

Thank you very much, sir :D
[Samsung Galaxy Nexus] slg60:
Using CM latest Nightly!
[Samsung Galaxy Nexus] raubkatze:
ch33kybutt, thanks for new kernel!

Flashed on my second GNex )
[Samsung Galaxy Nexus] kashix:
Regardless, still loving every bits of this kernel! Great work!
[Samsung Galaxy Nexus] Gingernut78:
Lovely clean kernel and some great well thought out additions to the latest update.

P.S I finally got the kernel to build.

Thanks
[Samsung Galaxy Nexus] bigeyes0x0:
Just tried your kernel for a few hours, amazingly smooth.

BTW Ezekeel's just added fsync control to his kernel, can you add this to your kernel too? I find with fsync disable a lot of games that has less stuttering due to database access.

EDIT: With default settings, the kernel is sometimes slow to ramp up after idle making the lockscreen choppy. Can you do something about it?
[Samsung Galaxy Nexus] kashix:
was reading through, your kernel supports BLX, wondering what's the limit you've set for full charge? 96%? seen your commit. can't wait for more goodies!
[Samsung Galaxy Nexus] ch33kybutt:
Good for you! Care to share? And maybe you can be the one to write up a kernel building tutorial...

Try with interactive governor. And I may reduce idle exit timing a little in next build.

default is 100. Use script to change.
[Samsung Galaxy Nexus] 8723045587230455:
Got it!
[Samsung Galaxy Nexus] meminiau:
My Nexus is loving your Kernel! Thanks mate!

I am downloaded your latest version now.

I've also done a little reading of the thread and noticed some instructions on how to optimise your Kernel... Is there an app that could do the same? I have used Franko's kernel in the past so I have his updater app that allowed for some customisation, is that something that I could use to make adjustments?
[Samsung Galaxy Nexus] avyonix:
Yeah, I experienced data drops too, on one occasion, but that was with 200Mhz set as minimum freq, after I set it to 350Mhz minimum, it was ok....not sure whether it was related to that though.
[Samsung Galaxy Nexus] ch33kybutt:
Good morning everyone!

Set SCREENSTATE=0 in /etc/cmplus.conf then reboot. Should solve your problem immediately.

To enable CFS tunables in /proc/sys/kernel/. Smaller time-slices when screen-on result in more efficient multitasking and thus better UI response. Larger time-slices when screen-off save a little more battery.

# SCREEN-ON
echo 0 > /proc/sys/kernel/sched_child_runs_first;
echo 1000000 > /proc/sys/kernel/sched_latency_ns;
echo 100000 > /proc/sys/kernel/sched_min_granularity_ns;
echo -1 > /proc/sys/kernel/sched_rt_runtime_us;
echo 100000 > /proc/sys/kernel/sched_rt_period_us;
echo 95000 > /proc/sys/kernel/sched_rt_runtime_us;
echo 25000 > /proc/sys/kernel/sched_wakeup_granularity_ns;
log -p i -t ch33ky "[CMPlus] Screen-ON: Performance settings for CPU Scheduler";

# SCREEN-OFF
echo 1 > /proc/sys/kernel/sched_child_runs_first;
echo 10000000 > /proc/sys/kernel/sched_latency_ns;
echo 1500000 > /proc/sys/kernel/sched_min_granularity_ns;
echo -1 > /proc/sys/kernel/sched_rt_runtime_us;
echo 1000000 > /proc/sys/kernel/sched_rt_period_us;
echo 950000 > /proc/sys/kernel/sched_rt_runtime_us;
echo 2000000 > /proc/sys/kernel/sched_wakeup_granularity_ns;
log -p i -t ch33ky "[CMPlus] Screen-OFF: Economy settings for CPU scheduler";
[Samsung Galaxy Nexus] franciscofranco:
I didn't know sched_debug did that, thanks :)
[Samsung Galaxy Nexus] laureanop:
How awesome are the both of you !

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] ceejay83:
Is blx broken? Set it to 96, but my phone was able to charge beyond that
[Samsung Galaxy Nexus] zeuswsu:
Holy boner kernal is working great for me! The battery life really shines when it comes to making phone calls, awesome job!
[Samsung Galaxy Nexus] droidholic:
Will try this. Thank you!
[Samsung Galaxy Nexus] Stricly:
I also had problems when my GNEX were in deep sleep it was unable to get out of it. Had to pull the battery. Had the min. freq. set on 200MHz when this happend.

Others got the same problems??
[Samsung Galaxy Nexus] ch33kybutt:
Not all devices run well below 350 or above 1200, which are the stock frequency limits for standard OMAP4460.
[Samsung Galaxy Nexus] bigeyes0x0:
Accidentally pressed on thanks button instead of quick replay for you ch33ky, still you deserve them anyway :D. On to the real issue, here are some mistakes you made in cmplus script:

- kernel.sched_rt_period_us can't be smaller than 950000 so setting it to 100000 does nothing

- kernel.sched_rt_runtime_us can't be smaller than 902500 so setting it to 95000 yields nothing

- vm.drop_caches does not have value 0. Look here http://www.linuxinsight.com/proc_sys_vm_drop_caches.html . And I don't think setting it to 3 to clear these caches every time users turn off their display is not a good idea, considering that the cache might have some useful data. I run this on my some linux servers I admin once a week only, and tbh I find the effect to be more peace of mind than actual effect.

Relevant part of my code that uses your idea

if [ $SCREENSTATE -eq 1 ] && [ ! -z $1 ]; then
$LOG "[Trickster] Apply SCREENSTATE=$SCREENSTATE"
(while
do
cat /sys/power/wait_for_fb_wake > /dev/null
if [ $KER_SS -eq 1 ] && [ -f /proc/sched_debug ]; then
sysctl -e -w kernel.sched_child_runs_first=0 \
kernel.sched_latency_ns=1000000 \
kernel.sched_min_granularity_ns=100000 \
kernel.sched_wakeup_granularity_ns=25000 &> /dev/null
$LOG "[Trickster] Screen-ON: CPU scheduler performance settings"
fi
if [ $VM_SS -eq 1 ]; then
sysctl -e -w vm.swappiness=60 \
vm.dirty_expire_centisecs=3000 \
vm.dirty_writeback_centisecs=1000 \
vm.dirty_background_ratio=10 \
vm.dirty_ratio=40 \
vm.laptop_mode=0 \
vm.min_free_kbytes=4096 \
vm.oom_kill_allocating_task=0 \
vm.page-cluster=0 \
vm.vfs_cache_pressure=300 &> /dev/null
(echo 1 > /sys/kernel/mm/ksm/run) &> /dev/null
$LOG "[Trickster] Screen-ON: Virtual Memory performance settings"
fi

cat /sys/power/wait_for_fb_sleep > /dev/null
if [ $KER_SS -eq 1 ]; then
sysctl -e -w kernel.sched_child_runs_first=1 \
kernel.sched_latency_ns=10000000 \
kernel.sched_min_granularity_ns=1500000 \
kernel.sched_wakeup_granularity_ns=2000000 &> /dev/null
$LOG "[Trickster] Screen-OFF: CPU scheduler economy settings"
fi
if [ $VM_SS -eq 1 ] && [ -f /proc/sched_debug ]; then
sysctl -e -w vm.swappiness=0 \
vm.dirty_expire_centisecs=0 \
vm.dirty_writeback_centisecs=0 \
vm.dirty_background_ratio=60 \
vm.dirty_ratio=95 \
vm.laptop_mode=5 \
vm.min_free_kbytes=1024 \
vm.oom_kill_allocating_task=1 \
vm.page-cluster=3 \
vm.vfs_cache_pressure=10 &> /dev/null
(echo 0 > /sys/kernel/mm/ksm/run) &> /dev/null
$LOG "[Trickster] Screen-OFF: Virtual Memory economy settings"
fi
done) &
echo -1000 > /proc/$!/oom_score_adj;
fi

EDIT: Might wanna read this http://doc.opensuse.org/documentation/html/openSUSE/opensuse-tuning/cha.tuning.taskscheduler.html
[Samsung Galaxy Nexus] ch33kybutt:
vm.drop_caches - agreed that there is no 0 (typo error) and that clearing caches every screen-off is not a good idea. I've already reverted it earlier today for my testing after a user reported issues with VoIP app. Results are pleasing.

Thanks for pointing that out. Now it's my turn *cracks knuckles* :p ...

sched_rt_period_us - exactly where is your source that specifies a low limit of 950000 for this? I get my info directly from Linux documentation:

"Time is specified in us because the interface is s32. This gives an operating range from 1us to about 35 minutes. "

See below for reference link.

sched_rt_runtime_us - it is highly recommended to use the default setting of 95% of sched_rt_period_us. Thus if sched_rt_period_us is set to 1000000, then sched_rt_runtime_us should be 950000. If sched_rt_period_us is 100000, then sched_rt_runtime_us should be 95000. And so on.

Note that sched_rt_period_us & sched_rt_runtime_us cannot be changed on the fly, and the old behaviour of runtime = period must first be specified, (echo -1 > /proc/sys/kernel/sched_rt_runtime_us). Only after can new values be entered.

So I stand by my earlier statement of smaller time-slices for more effective multitasking.

And you might wanna read this http://www.kernel.org/doc/Documentation/scheduler/sched-rt-group.txt

I do so love a challenge. Hope you had fun too. ;)

EDIT: thanked you back.
[Samsung Galaxy Nexus] bigeyes0x0:
I stand corrected, this is the magic and here I thought you were not sober writing that :p. Thanks. Now it works in my script hehe :D.

About the limit that you thought I pulled out of my hat. Those values actually can be changed but only in a small range around the current value if you didn't reset it with the magic. After removing the magic in ignorant, and setting these values didn't work I use manual binary search to find them lol.
[Samsung Galaxy Nexus] nklenchik:
ch33ky,

Is there a way to manually edit the script to change the gpu clock speed?
[Samsung Galaxy Nexus] bigeyes0x0:
There's no sysfs file to change GPU speed on ch33ky's kernel.
[Samsung Galaxy Nexus] nklenchik:
Oh okay but that would be sweet to include for the users whose phones could handle the increase.

Also, Idk if this is liquid 1.4 or the newer 5/18 kernel but I'm not getting deep sleep while charging.
[Samsung Galaxy Nexus] bigeyes0x0:
Here's your answer regarding GPU OC sysfs http://xdaforums.com/showthread.php?p=25528377#post25528377
[Samsung Galaxy Nexus] franciscofranco:
I dont know how many times we've answered this but no device sleeps while charging, it needs to hold a wakelock to do so.

Ch33ky Ive been testing your sched values and its noticeable smoother, thanks for taking the time to research it.
[Samsung Galaxy Nexus] ch33kybutt:
Yeah, UI is noticeably more responsive now. Especially noticeable during a toast notification pop-up. Simple test to confirm, run any cpu-intensive game, e.g. temple run, and adjust volume while playing. Any lag?
[Samsung Galaxy Nexus] bigeyes0x0:
There's still some lag, but very little compared to previously.
[Samsung Galaxy Nexus] CMNein:
I find that CPUSpy/BBS report wakelocks when charging by USB (have never fast charged), but not on AC. Seems counter intuitive to me as well, ICS + Apps not reporting properly?
[Samsung Galaxy Nexus] franciscofranco:
I will be honest Im not entirely sure we need a wakelock to charge via AC. My intuition says that its fairly obvious that theres a need to hold a wakelock or the device would just be powered down - power collapsed without receiving power. But I can be wrong, I havent looked at those drivers with much attention.

For USB charging a wakelock hold is needed to power up the USB interface and make it ready to pull/push data.

Just my two cents here. Sorry for off-topicying ch33ky.
[Samsung Galaxy Nexus] ch33kybutt:
AC charging - no wakelock, able to deep-sleep.

USB charging - wakelock, no deep-sleep.

And it's kernel related, so pretty much on-topic.
[Samsung Galaxy Nexus] Bosio91:
Hello c33ky,

First of all, thank you for your great work! Could you please indicate in what file I must change the code to the one you posted above?

Thank you again!
[Samsung Galaxy Nexus] !crazy:
I think SCREEN_ON part is implemented in the function with same name in /system/bin/cmplus. I am not sure if the values are 100% same, didn't check carefully, but you probably already have what you are looking for. Regarding this kernel at least : ).
[Samsung Galaxy Nexus] Bosio91:
Yes I checked the file and the values are the same.

Thanks anyways!
[Samsung Galaxy Nexus] nolsen311:
Just tried this out yesterday and I have to say I'm pretty impressed overall. Lots of features, reasonably stable. Although I seemed to get lockups when using the 200 MHz low setting.

Charging via the desktop dock does not seem to work well. Slow charging, maybe? I woke up this morning and the phone was only at 40%.
[Samsung Galaxy Nexus] kashix:
Great update again ch33ky! Trying out screenstate!
[Samsung Galaxy Nexus] jesusice:
Thank you for this! I've always preferred the CM9 kernel just wished it included things like high performance audio and touchwake. Now my life is complete :)
[Samsung Galaxy Nexus] jerrycycle:
This kernel does offer those and more options.
[Samsung Galaxy Nexus] BigBake88:
What screen on time battery life have you guys been getting?
[Samsung Galaxy Nexus] jesusice:
I know, hence the thanks ;)
[Samsung Galaxy Nexus] M3drvr:
Managed 4:21 yesterday. Good enough for me. That was on Wi-Fi 90% of the time though.
[Samsung Galaxy Nexus] BigBake88:
Stock battery?
[Samsung Galaxy Nexus] M3drvr:
Yes that would be correct.
[Samsung Galaxy Nexus] hitman818:
If by chance is there a way to add voodoo sound to this kernel? It would be great if you can.
[Samsung Galaxy Nexus] nklenchik:
Voodoo sound = SGS devices

We have a couple enhancements such as high quality audio and raising the volume, but that's as far as it goes. I'd just suggest an equalizer.
[Samsung Galaxy Nexus] BigBake88:
No Franco kernel for the time being? I've seen you post a lot on his thread. CMPlus been treating you good?
[Samsung Galaxy Nexus] nklenchik:
I've been going back and forth :p
[Samsung Galaxy Nexus] oned:
WTF, sorry :p

Just flashed your last kernel, and woww so smooth and fast ! :eek:

Perfect integration with CM9 nightly.

Come from the popular and great Franco's kernel (thx to him) and I don't move .....for now.

Thank u ch33kybutt for your work.

Sent from my Gnex
[Samsung Galaxy Nexus] oned:
And Excellent battery life

Loose 4% between 11pm and 7 this morning ! Wifi + 3g + all sync on.

Never had this before.

Again thx Mister ch33kybutt :D

Sent from my Gnex
[Samsung Galaxy Nexus] ch33kybutt:
You're welcome! But I'm not really focused on getting the best benchmark results, as they mainly focus on raw throughput for CPU, GPU and memory, which anyone can easily top with some questionable hacks and a freezer. Not really real-world testing, imho. No benchmark app that I know of can effectively provide test results for latencies and responsiveness (but if anyone knows any benchmark which can measure that, please let me know). Reducing latency and improving responsiveness for the best possible user experience is, and will always be, my main aim for this kernel, whilst also trying not to wreak too much havoc on battery life.
[Samsung Galaxy Nexus] oned:
Am totally agree with your philosophy, it was just a illustration with an tool know to all.

Thx
[Samsung Galaxy Nexus] wisefreakz:
Which rom? What kind of widgets you use?
[Samsung Galaxy Nexus] oned:
Last CM9 with xxla2 radio.

350/1500 interractive.

All settings set to default. News week and beautifull widgets as sync apps... of course push mail on

Hope I answered you.

Sent from my Gnex
[Samsung Galaxy Nexus] ch33kybutt:
3.0.32-CMPlus-Tuna-120524

Changelog

* Updated to Linux 3.0.32

* Reverted to TREE_PREEMPT_RCU from JRCU

* Disabled SCHED_AUTOGROUP as it had no visible performance boost

* Updated cmplus script

---- Removed modification of vm.drop_caches in Screenstate as it caused instability

---- Back to using my own personal preferences as default settings :P
[Samsung Galaxy Nexus] nexus.prime:
Thanks for the update :)

But on this version, my device does not use 1420 and 1500 MHz like the previous version :(

Edit: need to crack any restriction?
[Samsung Galaxy Nexus] marjaN_:
i still run cm9 nightly 0518 & also your kernel 0518, can i update kernel to 0524 without problems? (without changing my current rom) :)
[Samsung Galaxy Nexus] neur0tk:
Clear cache and dalvik only and you will be money

Sent from BAMF'd GneXus
[Samsung Galaxy Nexus] oned:
Thx for the uptade, my Gnex litteraly fly...

U really roX !

Sent from my Gnex
[Samsung Galaxy Nexus] franciscofranco:
What kind of **** was vm.drop_caches causing? By de description it doesn't seem to **** anything up, or am I missing something?
[Samsung Galaxy Nexus] gnexdude:
Dang Cheeky! the 5/18/12 release was just setting in nicely!!!!....

F##k it, I flash any upgrades you got lol
[Samsung Galaxy Nexus] obsanity:
Does this kernel work on the Sprint version of Galaxy Nexus?
[Samsung Galaxy Nexus] ch33kybutt:
Cleared cache when screen off, which was real bad for streaming apps and any active voip connections. Big blunder on my part :(
[Samsung Galaxy Nexus] Redneck Trash:
Yes. Running it on mine.

Sent from my Galaxy Nexus using Xparent Red Tapatalk 2
[Samsung Galaxy Nexus] ch33kybutt:
Should work on all variants: maguro, toro, toroplus.
[Samsung Galaxy Nexus] wisefreakz:
Tks m8. Do you use facebook app?
[Samsung Galaxy Nexus] franciscofranco:
Hmm. I wonder if thats correlated with some signal loss on screen off with the last 3 releases of my nightlies, I added a vm.drop_cache = 1 on the ramdisk, but I can't see how it can affect it...
[Samsung Galaxy Nexus] laureanop:
My wife has been missing lots of phone calls on 162 so there may be something to it

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] ch33kybutt:
Well, vm.drop_caches = 1 just clears the pagecache, so don't really see how it could affect RIL (radio interface layer). Probably best to look elsewhere for the root cause of signal drop. But then again, which is the real problem: signal drop or data drop? Users may be confusing the 2 and so reporting data drops as signal drops and vice versa. 2 different problems with 2 different root causes.
[Samsung Galaxy Nexus] bigeyes0x0:
The way vm.drop_caches works AFAIK is only to clear set cache when user uses sysctl to apply to it a value (or echo). I don't think setting it in the ramdisk would do anything at least after boot.
[Samsung Galaxy Nexus] obsanity:
Thanks. Runs great so far.
[Samsung Galaxy Nexus] oned:
I can't believe, loose just 1% batt this night !!! Between 0.00 and 7.

Same config as before.

Oh and i don't have a Facebook account, I know am a E.T:p maybe my Gnex so :confused:

One more times thank you mister ch33kybutt, I understand now why the famous Franco take some inspirations here...

Sent from my Gnex
[Samsung Galaxy Nexus] paratox:
had a SOD this morning with 24.5. release.
[Samsung Galaxy Nexus] ch33kybutt:
More info would help ...

Governor

Min & Max freq

Screenstate ON/OFF

Hotplug ON/OFF

and if possible ... last_kmsg and/or logcat (check 1st post).
[Samsung Galaxy Nexus] paratox:
interactive

350 - 1350

the rest is on default settings (nothing changed)

when alarm was ringing the phone was responsible again.
[Samsung Galaxy Nexus] ch33kybutt:
Thanks for the info, but not able to reproduce the problem. Runaway real-time processes which caused SoD were fixed in 120518 (18 MAY build).
[Samsung Galaxy Nexus] oned:
Plz can you share your colors settings, I just modified it, and can't go back...:( sorry

Sent from my Gnex
[Samsung Galaxy Nexus] ch33kybutt:
See my sig below ...
[Samsung Galaxy Nexus] oned:
Edit : sorry, am maybe a noob, how can i do with CM9 stock control colors, i can not reproduce your settings...

Sent from my Gnex
[Samsung Galaxy Nexus] albsat:
@ch33kybutt

I am trying this kernel and liking it a lot.

Two questions please:

Is it possible to modify voltage settings with the cmplus config file or if not do you have plans yo include this feature?

Is it possible to change gpu speed for the kernel?

Thanks for your work.

P.s I couldn't ovc this kernel to 1420 which was possible with another kernel. Hope u can give me a tip.
[Samsung Galaxy Nexus] ch33kybutt:
Just use ROM controls or SetCPU. Lots of voltage control apps out there.

Nope. GPU static 384MHz.

If it doesn't work for you with SmartReflex on, then suggest turning off SmartReflex. Note that thermal throttling may kick in and resultant performance may be even worse than 1200.
[Samsung Galaxy Nexus] albsat:
@ch33kybutt

Thanks for your explanation. If battery life would be your goal, what would your config file like?
[Samsung Galaxy Nexus] ch33kybutt:
Battery life is very much dependent on individual usage pattern. How often you have your screen on, when you use it most, what you do when using it, etc. Just too many variables. One man's meat is another man's poison. One size does not fit all. But since display is the biggest drain, best advice is to use a predominantly black theme.

And just fyi, here's my usage right now ...
[Samsung Galaxy Nexus] albsat:
Just great. Is that with your default kernel settings?

I got 3 hours and 22 minutes with 29% battery left with your excellent kernel. Then I recharged.
[Samsung Galaxy Nexus] ch33kybutt:
With settings in my signature.
[Samsung Galaxy Nexus] nexus.prime:
You switched ROMs from BlackICE to LiquidSmooth?!
[Samsung Galaxy Nexus] ch33kybutt:
Yup. Trying it out. Not bad at all. Might stay with it for a while.
[Samsung Galaxy Nexus] laureanop:
Liquid with yours or Franco's kernel simply flies.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Karl:
24may release is killing my single x above bars anyone else?
[Samsung Galaxy Nexus] Razer(x):
Faster than CM9?
[Samsung Galaxy Nexus] ch33kybutt:
Don't understand ...
[Samsung Galaxy Nexus] mariotme:
I think he's suffering from the 4.0.4 signal drops issues