yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ch33kybutt:
Oic. Never had that problem. Tried GetRIL to sync RIL & baseband? Heard that it only affects GSM users. If so, then I think it's caused by an unfortunate coincidence of multiple factors which occur during inter-system handover. "What is inter-system handover?", you say ... here's where all of us GSM users should educate ourselves : http://www.radio-electronics.com/info/cellulartelecomms/gsm_technical/handover-handoff.php

Knowledge is power.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] obsanity:
Great kernel. I'm running smastass2 governor with some custom settings and it flies compared to standard CM9 kernel. Also, I like it that I can limit processor on screen off way down to 350Mhz. Saves a tone of battery. Love it.
[Samsung Galaxy Nexus] albsat:
Great to hear that. I like this kernel because you can figure a lot of settings manually.

Do you mind sharing your custom config and battery life? Thnx

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bart594:
Hi ch33kybutt,

i think ezekeel has found culprit of those nasty data drops

Since upgrade to 4.0.4 i have had this issue. With his new kernel no need to turn on/off airplane mode anymore.. no single data drop!

You might take a look:

http://rootzwiki.com/topic/14685-11-may-glados-v133/page__st__1220
[Samsung Galaxy Nexus] ch33kybutt:
You mean using Westwood+ as TCP congestion protocol? Lol, CMPlus has had that as default since very first build. Check OP. Already knew long ago that it was the best choice for all types of wireless networks (wifi & mobile).
[Samsung Galaxy Nexus] renaud:
My phone does enter deep sleep while charging. using stock 4.0.4 and fugumod.
[Samsung Galaxy Nexus] ch33kybutt:
That's true for AC charging. But for USB charging, deep-sleep is not possible while charging, only AFTER FULL charge has been achieved.
[Samsung Galaxy Nexus] renaud:
Ah, OK, I didn't notice this comment was for pc connected USB charging.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
Liquid is a lot faster and months ahead with features if that's ur "thing" I love that rom (liquid 1.4)
[Samsung Galaxy Nexus] ch33kybutt:
Haven't felt a need to cook a ROM for myself like I did for my N1. GNex users are spoilt for choice when it comes to ROMs & kernels. Something for everyone, in multiple combinations, to suit any mood or situation. Yet, from reading all the forum threads, whiners from the gimme-more, gimme-now gang still abound. I just don't get it ...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] albsat:
Lol. I agree with you. I used to be on galaxy S2 forum as I had such a phone. People there were hungry for an akop port rom. Here there is such a multitude of roms and people still complain indirectly. Unbelievable.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ock:
I check your thread almost everyday, always have something new to learn from your posts :)
[Samsung Galaxy Nexus] albsat:
@ch33kybutt

Do you plan releasing a kernel with 307 gpu speed? It could make us gain more battery life. I could be a tester for such kernel. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CMNein:
People seem to get pissed off here too when all the choices aren't just ports of each other for some reason.
[Samsung Galaxy Nexus] obsanity:
Here is my setup along with Max CPU frequency set to 350 MHz in the config file.
[Samsung Galaxy Nexus] blowtorch:
Thanks ch33kybutt the community really needed your kernel! i have officially switched to this kernel after months and months of testing kernels and i dont expect to switch to anything else again. please keep up your good work!
[Samsung Galaxy Nexus] ArmanUV:
what app is that?

ch33kybutt, I have a small suggestion: Is it possible to have the install script check for /sdcard/cmplus.conf and create one if it doesn't exist?
[Samsung Galaxy Nexus] ch33kybutt:
I might bring back Imoseyon's gpu OC, since stock CM9 kernel already has it merged in.
[Samsung Galaxy Nexus] Karl:
hmm after i flash your kernel it kills my signal
[Samsung Galaxy Nexus] ch33kybutt:
hmm after i read your post it kills my patience

- ROM name and version

- RIL & baseband version (use GetRIL)

- dmesg & log at to pastebin.com
[Samsung Galaxy Nexus] ArmanUV:
man do I have bad luck with kernels: totally random freeze and reboot while I was browsing.

last_kmsg: http://d.pr/n/lTS4

cmconf: http://d.pr/n/wnyR

CM9 Smartassv2 350-1420.

I'm guessing my phone couldn't handle 1420? it's stable on leankernel.
[Samsung Galaxy Nexus] ch33kybutt:
No errors detected
Boot info:
Last reset was MPU Watchdog Timer reset (PRM_RSTST=0x8)

Not a kernel panic. Some system process just got hung which triggered the watchdog reset. Can't really tell, but most likely a random bug. If it's not persistent, then I wouldn't worry about it.
[Samsung Galaxy Nexus] ArmanUV:
ok thanks it's probabely cm9 I had just flashed a new nightly an hour before.
[Samsung Galaxy Nexus] RjsShadows:
Will hot plug be added to the kernel? I'm sorry if it's been asked before or if it's already implemented I just wanted to ask

EDIT: I'm sorry never mind I saw the post a about the script.
[Samsung Galaxy Nexus] Karl:
:eek: hmm you need more patience then

AOKP Build 37

RIL:I9250XXLA2, BASE:I9250XXLA2

http://pastebin.com/w4banxuT

http://pastebin.com/fi4QbiBM
[Samsung Galaxy Nexus] ch33kybutt:
Thanks for the logs, but 2nd one is empty, and nothing in the 1st one shows any indication of any problem.

You might want to monitor and check radio buffer logcat for suspicious errors whenever you have signal drops.

# adb shell

# logcat -b radio

or

Run aLogcat > settings > preferences > buffer > radio
[Samsung Galaxy Nexus] Ibanez33:
it is available but has to be enabled in the config script..

in cmplus.conf

find..

# Enables/disables Hotplug Mode for CPU1 (DEPENDS ON SCREENSTATE=1)

# 0 or blank = disabled (default)

# 1 = enabled (WARNING: May cause instability such as signal drops)

CPU_HOTPLUG=

and set to 1. Although as suggested in first post if your making changes to it copy it sd so allow it to survive updates :)

Edit I should have read your whole post lol *facepalm
[Samsung Galaxy Nexus] obsanity:
Nstools from the market.
[Samsung Galaxy Nexus] farmerwill:
Great kernel amazing battery life so props to the dev. One of the few kernels that has given me impressive battery life since getting the phone!
[Samsung Galaxy Nexus] ch33kybutt:
3.0.32-CMPlus-Tuna-120531

Changelog

* Reverted Wifi voltage back to stock 2.0V

* Tweaked and re-enabled Lulzactive cpufreqgovernor

* Added fix for I2C crash by Imoseyon

* Changed to Vibrator Control by Ezekeel (removed Morfic's)

* Enabled CONFIG_AIO with extra patch to reduce I/O latency

* Re-disabled ARCH_POWER in sched_features.h (no improvement)

* Misc updates from Omapzoom and Codeaurora

* Updated cmplus script

---- Removed Hotplug from Screenstate mode as it caused instability
[Samsung Galaxy Nexus] nklenchik:
Perfect chance for me to test this tomorrow. Longgg day ahead
[Samsung Galaxy Nexus] wisefreakz:
Awesomeness again
[Samsung Galaxy Nexus] hitman818:
Can anyone tell me whats the gpu clock set at?
[Samsung Galaxy Nexus] Sveke:
384
[Samsung Galaxy Nexus] hitman818:
Is there a way to set at 307 in the cmplus script? Im wondering if that will help the temple run lag thats on cm9 and aokp roms. Im using francos kernel and its set at 307.
[Samsung Galaxy Nexus] Sveke:
I Don't believe you can change it
[Samsung Galaxy Nexus] tcchuin:
Hi cheeky, since you actually let us use startup script to change settings, it it possible for you to use Ezekeel color mod instead of the cm one? =x

Just an opinion, hope you can consider it..
[Samsung Galaxy Nexus] bigeyes0x0:
@hitman818: Not yet, he said he's going to add sysfs to change GPU clock again, let the man rest a little. And I don't really think it's his problem that CM9/AOKP lags with Templerun as it's runs fine with his kernel and my ROM or rascream.
[Samsung Galaxy Nexus] ch33kybutt:
How would reducing GPU speed improve lag?
[Samsung Galaxy Nexus] albsat:
:) ehhh. It doesn't make sense. A lower gpu reduces the speed of game rendering.

By the way, do you think that a 307 mhz gpu would save us some battery lifetime?
[Samsung Galaxy Nexus] ch33kybutt:
Not really, since 307 & 384 both use the same voltage. Best guess is maybe an extra 5-10 minutes. Worth it?
[Samsung Galaxy Nexus] hitman818:
I wasnt saying it was his fault it lagged. I was just thinking that stock roms run better than cm9/aokp.
[Samsung Galaxy Nexus] obsanity:
Ummm please don't. This is CMplus not Glados plus kernel.
[Samsung Galaxy Nexus] albsat:
If you can push it up to 30 - 60 extra minutes, yes !!! ;)
[Samsung Galaxy Nexus] tcchuin:
But why? The choice of 1-200 is better than 0.01-1.00 in my opinion
[Samsung Galaxy Nexus] wisefreakz:
Cheeky... I notice after latest kernel I miss information regarding what is consuming battery.... does it happens to you?
[Samsung Galaxy Nexus] ch33kybutt:
Battery stats is fine on mine. Reboot maybe?
[Samsung Galaxy Nexus] wisefreakz:
I did... no lucky. Will try reflash....
[Samsung Galaxy Nexus] nexus.prime:
"lulzactive fixed"

Thanks, sir :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] wisefreakz:
No lucky...
[Samsung Galaxy Nexus] ch33kybutt:
Here's a test kernel just for fun (not sure if I want it in mainline yet) with framebuffer console enabled to show dmesg on boot. You should be able to see it just before the bootanimation. If you want to see only dmesg log until lockscreen, then rename /system/bin/bootanimation with a .bak extension (so you can revert easily).

Credit to Cpasjuste as I used tips from this I9000 post : http://xdaforums.com/showthread.php?t=829817
[Samsung Galaxy Nexus] Think420:
ever considered including noop, deadline, or FIOPS as alternate I/O schedulers?

personally I'm a big fan of noop
[Samsung Galaxy Nexus] nklenchik:
Can't get into the phone with the test kernel. It'll boot up and freeze before the lockscreen. Actually it froze at the bootanimation the 2nd time I tried rebooting.

Also anyone able to oc past 1350? I tried to get it to 1.5 and it's a no go with with interactive
[Samsung Galaxy Nexus] dwang:
Did you mention you were going to add configurable GPU OC sysfs?

Is that still planned?
[Samsung Galaxy Nexus] ch33kybutt:
Considered all before. Tested all before. And SIO came out tops. With Deadline and VR joint second place. In fact, Noop was the worst performer, which isn't surprising given it's not really a scheduler, but a 1st-come-1st-serve algo, which often results in agonizingly long wait times for pending I/O requests.

It's just a "for fun" build. Won't make it to mainline. Also noticed that it caused some problems waking up screen after deep sleep. Have to press power button more than once. Imho, if you really want to see scrolling log on boot, then Chainfire's live dmesg/logcat is a much better solution. Much prettier colours.

I've always taken the care to stress test all freqs on all governors using Stability Test before releasing any build. Run it for hours until battery fully discharges. Only release if there are no reboots or hangs. Without any freezer intervention, even. But do note that testing is always done with a clean install of a rooted stock ROM. So if you can recreate the problems on a cleanly installed ROM, then I can probe further.

I mentioned that I "might" bring it back again. But as Burns or Steinbeck said, "the best laid plans of mice and men, often go awry." Or was it Jethro Tull?
[Samsung Galaxy Nexus] Think420:
so what governor is everyone using and how is the performance/battery life with said governor?

I've been on wheatley 200-1072 all day and managed about 1 hr 30 minutes of screen time, but that was with a lot of 3g and poweramp usage
[Samsung Galaxy Nexus] wisefreakz:
Cheeky... the batt stats says my phone was "awake" while CPU Spy says it was in deep sleep.

How can I find out what is keeping my phone awake and stop unnecessary battery drain?
[Samsung Galaxy Nexus] ch33kybutt:
Looks like your battery stats file is acting up. Do a full charge while phone on, then turn off and bump charge till really full. Disconnect charger and boot. That should reset the battery stats. Monitor from then on.
[Samsung Galaxy Nexus] wisefreakz:
Thanks dude.... will do that and report back.
[Samsung Galaxy Nexus] kashix:
Excellent update ch33ky! The color seems better, not sure whether is the contrast control in the cmplus.conf

I think cmplus kernel and long battery life go hand in hand, its simply terrific!
[Samsung Galaxy Nexus] bioan:
Thank you for this great kernel. I tried all kernels around here, but I keep switching between this one and Franco's.

I am keeping this one because the colours are great and the sun eligibility is much better.
[Samsung Galaxy Nexus] creaky:
Just wanted to tell you that the last release blew me away. Fantastic work on this kernel; your service to the community is much appreciated!
[Samsung Galaxy Nexus] bioan:
Cheeky, I just had a radio drop. While in call I received another one. After I answered the incoming call, the radio dropped.

I haven't rebooted the phone yet, should there be any logs ?

Thank you!
[Samsung Galaxy Nexus] ch33kybutt:
Open adb shell or terminal emulator ...

# logcat -b radio > /sdcard/radio.log

wait a couple of minutes, then exit and check the log file.

Also, use GetRIL to check RIL & Baseband match.
[Samsung Galaxy Nexus] bioan:
I have checked with getril and everything is ok. They match.

Here is a log http://db.tt/WhaQoeav

Thank you !
[Samsung Galaxy Nexus] obsanity:
Is anyone able to use the 200Mhz frequency? I keep getting the sleep of death if I lower it that far so my min has to be 350Mhz. I tried increasing the voltage to same as 350Mhz and also tried using smart ass to keep ideal higher but always end up pulling the battery because it won't wake up.
[Samsung Galaxy Nexus] bioan:
Why would you use 200 mHz with the same voltage as 350 mHz? The min 350 is doing a fantastic job.
[Samsung Galaxy Nexus] albsat:
@ch33kybutt

What do you think of NsTools? I think it is allowed to adapt it, but not sure. Have you consider to use it as a gui config for your kernel?
[Samsung Galaxy Nexus] obsanity:
Ummm... because when I tried the default voltage on 200 it went into a coma so I wanted to see if voltage is going to change things. Yes the 350 is working great but he must have put 200 in the kernel for some reason. So I wanted to see if there is a setting which will work with 200. I'm not complaining, just experimenting.
[Samsung Galaxy Nexus] parkson:
The point of running at 200mhz min is obtaining minimal battery savings from running at lower voltage for that particular slot. If you have to raise the voltage to match 350mhz, then just run 350.

My phone doesn't like less than 350 either, but I believe the battery savings (if any) are negated due to the processor taking longer to complete tasks at such low freq before entering sleep/c states.

Sure, it may work well if your phone sleeps in your pocket for 2/3 of the day, but then... what's the point?
[Samsung Galaxy Nexus] ch33kybutt:
I suspect that the problem occurs when moving from coverage of one cell to another, when the REQUEST_GET_NEIGHBORING_CELL_IDS is made. For some reason, android sometimes reports that this request is not supported.

Most of the time the process should successfully complete:

D/RILJ ( 465): [1206]> REQUEST_GET_NEIGHBORING_CELL_IDS
E/RIL(s) (15662): onRequest: GET_NEIGHBORING_CELL_IDS
E/RIL(s) (15662): CreateRequest(): req(0x2a1d0), id(75), tok(0x2a308) - FUNC(0x40138345)
E/RIL(s) (15662): [EVT]:Req(1), RX(0)
E/RIL(s) (15662): defaultReqHandler()
E/RIL(s) (15662): RIL_onRequestComplete: tok(0x2a308)

But sometimes, for some reason, android responds to RIL request with a REQUEST_NOT_SUPPORTED:

D/RILJ ( 465): [1189]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED

Which results in the signal failing to handover to the the nearest cell, thus radio drop. It's not due to poor signal strength, as your logs indicate an acceptable strength of around -60 to -80 dBm.

So I really have no idea why this behaviour occurs and why android seems to randomly respond with REQUEST_NOT_SUPPORTED, as I have yet to experience this radio drop.

Which ROM, RIL & Baseband are you currently using?
[Samsung Galaxy Nexus] bioan:
XXLA2 and Latest CM9 Nightly.
[Samsung Galaxy Nexus] ch33kybutt:
Not all devices can handle frequencies beyond stock values of 350 & 1200.

NSTools works fine, especially for the cpufreq governors, as it allows tweaking of not only the stock governors, but also Lulzactive & Smartass2.
[Samsung Galaxy Nexus] ch33kybutt:
Well, If it's a one-off occurence, then probably just let it be. But if you get frequent radio drops, then suggest you try the other RIL/Baseband combinations, XXKK6 or UGLC1.
[Samsung Galaxy Nexus] bioan:
I didn't experienced stuff like this before. Only data drops on Franco kernel. Let's presume it was a network error.
[Samsung Galaxy Nexus] nexus.prime:
ch33kybutt is erudite and responsive :) the excellent and kind dev!

many thanks to you
[Samsung Galaxy Nexus] CMNein:
Typically my verbosity knows no satiety, thanks for the new word :D
[Samsung Galaxy Nexus] nexus.prime:
:D I'm non-native English speaker, just referring to a dictionary and then can write :D
[Samsung Galaxy Nexus] ch33kybutt:
Lol! Thanks, but hardly think I deserve such a fancy-shmancy compliment, as I wasn't able to solve the problem. Actually wish this radio drop would happen to my device so I could have a first hand look at it.
[Samsung Galaxy Nexus] obsanity:
Well, I didn't say I wanted to keep it that way. Like I said I was just testing to see why it wouldn't wake up.

However, just because two frequencies run at the same voltage doesn't mean they both eat up the same amount of battery. This was proven somewhere in Glados kernel discussion in the Nexus S forum. A lower frequency will always tax the battery less than a higher. That is of course if the voltage for both is even.

It's irrelevant anyway since it sounds like my phone simply can't handle 200Mhz.
[Samsung Galaxy Nexus] blowtorch:
i had a complete radio failure on the may 31st build even rebooting didnt restore gsm connectivity. i panicked and flashed a different kernel and my gsm came back. sorry i didnt get a log for you like i said i panicked lol. thought* i would report it though.

cm9 on xxla2 radio
[Samsung Galaxy Nexus] chadouming:
Honnestly, this is the firs time i see someone finding something useful about radio drop. Usually, people only say it's kernel, and kernel dev don't know what to do to get it working properly. Maybe erudite is not the perfect word for this since i don't know if you knew it or simply deducted it from what you saw, but there is surely a long list of kind words coming while thinking about you. And responsive is well suited. I saw reading you post that you take a lot of time answering most of the person asking question if not all. Thanks for this, and thanks for your hard work !
[Samsung Galaxy Nexus] chadouming:
This is also true. It's not because frequencies are at the same voltage that they will use the same amount of energy. Without entering in too much details, xxx Mhz is the amount of time million of time that the CPU start and stop per second. Let's say that stoping the cpu does not require energy, starting it 200 000 000 of times @ 850mv will take less juice than starting it 350 000 000 of times @ 850mv. Simple science fact.
[Samsung Galaxy Nexus] obsanity:
Yes, precisely. Simple math and you can figure out how much you can go up on voltage before it makes sense to run the higher frequency.

Anyway, going back to my original question. Is anyone able to run the 200Mhz and be able to wake the phone up from sleep?
[Samsung Galaxy Nexus] jerrycycle:
I ran the 200 mhz with no issue . Sleeps and wakes fine for me.
[Samsung Galaxy Nexus] Sylde:
Mine shows some difficulties to wake with 31A version, so I flashed back to 24 (which is very smooth for me)
[Samsung Galaxy Nexus] ch33kybutt:
Version 531A was a test kernel. Use 531 instead.

Also, been trying like crazy to get a radio signal drop by changing ROMs, kernels, basebands, RILs, etc, but just can't get the drop! Frustrating ...
[Samsung Galaxy Nexus] Think420:
maybe it's their devices and not your kernel

I have not experienced any drops on any kernel or rom, although I'm not sure if the data drops have been effecting LTE users

Also I was just wondering if you might consider including the governor Sakuractive in the next build...I just like options lol :p
[Samsung Galaxy Nexus] franciscofranco:
I got some news for you. My kernel data drops surge happened just after I added your tweaked task scheduler (CFS) tweaks to the ramdisk. I wasted countless hours reverting and committing other patches, releasing test kernels, re-reading all my changelogs and in the end people would still get the drops. In an act of desperation I reverted to stock CFS tunables on the ram disk and the big surge of drops stopped to the normal drops caused by Google/Samsung derps.

This is all the feedback I can give you, I'm sorry I can't be with more detail, it's just what me and my users experienced in the last days.
[Samsung Galaxy Nexus] ch33kybutt:
Interesting ... since the main difference between our kernels is Screenstate mode. Tunables in my kernel go back to stock when screen off, which, if I read correctly, is when most drops occur.
[Samsung Galaxy Nexus] franciscofranco:
Drops occur after coming out of sleep or so I've been told.
[Samsung Galaxy Nexus] ceejay83:
or when switching from wifi to data
[Samsung Galaxy Nexus] ch33kybutt:
Thanks for the info. No time for any heavy-duty testing though, as I'm off for a week-long family vacation to an off-the-beaten path location, with no Internet access. Gonna make the kiddos rough it out to toughen them up and hopefully make them appreciate what they have at home. Unfortunately that means no Internet access for me as well :(
[Samsung Galaxy Nexus] obsanity:
No internet access? This does not compute.

I haven't had any radio drops on mine yet.
[Samsung Galaxy Nexus] creaky:
No radio drops for me but it's so cool to see two devs of your and Franco's caliber in such close, open communication.

Have a great vacation. Despite what some of us on XDA think, we'll survive a week without you!
[Samsung Galaxy Nexus] chadouming:
Is the lulzactive governor included in your kernel lulzactive or lulzactive v2 ? And, in either case, can tegrak app to customize lulzactive governor be used ? Thanks for the info ^^
[Samsung Galaxy Nexus] mariotme:
Enjoy your vacation bro :)

You need it!

When ever you have free time have a read on this kinda interesting stuff

http://www.cnx-software.com/2012/06...k-android-to-shame-on-ti-pandaboard-omap4430/
[Samsung Galaxy Nexus] CMNein:
In the handful of times I have experienced data drop it's been in moving from wifi to data, or turning off wifi, I

may

have had an instance of screen off data loss.
[Samsung Galaxy Nexus] gnexdude:
This^ enjoy some time off!
[Samsung Galaxy Nexus] cbkitt:
Yes and Yes...
[Samsung Galaxy Nexus] ceejay83:
Has anyone changed the gamma presets in the script? I've changed it numerous times to different settings and they all look the same
[Samsung Galaxy Nexus] ceejay83:
It actually seems like the settings in my cmplus.Conf don't apply. I put the file in my sdcard root. wtf?

edit: got it working again, had to factory reset. guess it had to do with my previous kernel (trinity)
[Samsung Galaxy Nexus] Think420:
ch33ky you got anything for us before you leave on your vaca?

I've said it once and i'll say it again, this is THE best kernel. great performance, battery, and features

only thing I still want is the FIOPS i/o scheduler
[Samsung Galaxy Nexus] parkson:
Why fiops?
[Samsung Galaxy Nexus] Think420:
http://www.phoronix.com/scan.php?page=news_item&px=MTAzOTU

Just seems like a good fit for the GNex, I've been using it as my go to scheduler on Faux's kernel and it's been very nice.
[Samsung Galaxy Nexus] wkh1113:
Will this kernel have 512mhz gpu version?
[Samsung Galaxy Nexus] k.janku1:
Can you make an app to change things in the cmplus.conf ?