yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] raubkatze:
I was wrong...

I stayed about two minutes on calibrated voltages tab and vualya... the jumps here. Not often but happens.

But I love r111(384) with hotplug governor )
[Samsung Galaxy Nexus] Treatcon:
Just a suggestion, but maybe you should name your kernels like Faux does... S for standard and U for ultimate, or something along those lines. It's hard to tell when I download them which is which. Thanks for your work, it's awesome!!
[Samsung Galaxy Nexus] rafi300:
Hmmm... so is there any specific reason for the jumps we are experiencing in core voltage with hotplugmod on ?is it bad ? Any fix or is this normal behaviour?

Sent from a gNexus using a swyping thumb!
[Samsung Galaxy Nexus] raubkatze:
Hotplug Mod removed in r111. There is hotplug governor in this kernel.

I don't think it is bad. Maybe these jumps happen as hotplug governor uses cores dinamically.
[Samsung Galaxy Nexus] detritu5:
Which governor is more conservative? hotplug or conservative?

ANd which one is better if I have a screen off profile in setcpu?
[Samsung Galaxy Nexus] Vangelis13:
- probably hotplug

- No need for screen off profiles, android handles it on its own nowadays. Plus, I'm fairly sure a combination of hotplug + screen off profile would just stir trouble.
[Samsung Galaxy Nexus] joelteixeira:
*sorry, answer found*

Tapatalked from my Nexus Prime
[Samsung Galaxy Nexus] raubkatze:
Download latest nightly kernel > Auto-flash or Download .zip > and choose
[Samsung Galaxy Nexus] joelteixeira:
Thanks man, I flashed r111 before the release of the new app and spent some time looking for a checkbox/dropdown menu or something like this. :-)

Tapatalked from my Nexus Prime
[Samsung Galaxy Nexus] cyanoviper:
so i just flashed r111, but apparently the popping speaker fix doesnt work for me. can i provide anything that will help to find the issue?
[Samsung Galaxy Nexus] raubkatze:
I have installed 3.8.5 and then flashed r111 )
[Samsung Galaxy Nexus] raubkatze:
But are you sure it is not cell issue?
[Samsung Galaxy Nexus] Mrc527:
CIFS Support

I've recompiled the 111 version, with CIFS support too!

Look at here:

http://www.kernel-xp.net/index.php/en/progetti/20-galaxy-nexus-kernel

I hope it helps.

Bye!
[Samsung Galaxy Nexus] cyanoviper:
i am not. i have yet to find an answer to wether it is a soft- or hardware issue. and if there is a fix that is build into kernels, its probably a softwareissue at least for some people.
[Samsung Galaxy Nexus] joelteixeira:
Francisco,

Just a quick suggestions for a future release, since most of the users stick with one gpu speed (384 or 512) we could maybe have this set on the application and the auto-flash button would check this and download the one set instead of asking everytime.

It's not a big deal, I personally don't mind hitting 512 but would be even better.

r111 ondemand is smooth addicted as this phone should be stock. No donuts for Google/Sammy. :-P

Tapatalked from my Nexus Prime
[Samsung Galaxy Nexus] raubkatze:
I had the same issue on r96 but I have never had it again since kernel update.

But periodically there are "strange sounds" during the call on gnex as well as on blackberry. As it happens in the same places I don't doubt it's the cell problem.
[Samsung Galaxy Nexus] cyanoviper:
oh i thought you meant if its an issue of the cellphone itself.

I am talking about the issue that the speaker of the phone "pops" after a sound was played, the speaker on the lower end, that is. not the one used for regular calls.
[Samsung Galaxy Nexus] Mondfahrer:
r110 running quite nice on my GN (conservative with hotplug). I lost only 9% over the night with wifi on. Usually I lose like 15-17% with M1 and also M2.

I will try r110 some day's before changing to r111.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] raubkatze:
Hmm... As Franco wrote Hotplug Mod was removed from r111(384&512). There is Hotplug Mod in the settings but it doesn't work with these builds.
[Samsung Galaxy Nexus] franciscofranco:
That will give me another problem: people tick the checkbox, then forgot they ticked it and then nuke my email with questions "WHERE IS THE GPU CLOCK CHOICE MENU?!? FIX PLIX UNTIL THEN 1 STAR RATING FOR YOU".
[Samsung Galaxy Nexus] raubkatze:
I really understand what you mean. But there were pops sound issues after (or during) call using speakerphone as well as issues that you wrote above.
[Samsung Galaxy Nexus] xTee:
How is better? with Automatic voltage calibration toggle enabled or disabled?
[Samsung Galaxy Nexus] Jiia:
Even 9% sounds like a lot. I'm on M2 and I usually lose 5% or less over 8 hours with wifi.
[Samsung Galaxy Nexus] franciscofranco:
There is no better in Android. Personal preference > everything else.
[Samsung Galaxy Nexus] hawkye:
I unticked the Hotplug Mod last night, downloaded r111, installed r111, and selected 384/1228 Hotplug gov. Everything was working great before I went to bed. I put it on the charger and woke up to SoD.
[Samsung Galaxy Nexus] franciscofranco:
Maybe your device doesn't like Hotplug ;)
[Samsung Galaxy Nexus] raubkatze:
Heh. I remember that replied you in aokp thread... Mine no undervolted and SR is enabled. But someone using undervolted.

Disabling SR makes sense if you want to use your undervolted values.

What is better? I think you can decide only on yours expirience.

---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------

I'm using r111 ((384) 384-1228 hotplug governor) 9+ hours. Works great and no SoDs.
[Samsung Galaxy Nexus] joelteixeira:
Understandable, keep up the great work. :thumbup:

Tapatalked from my Nexus Prime
[Samsung Galaxy Nexus] spaceman860:
Sorry for the noob Q but what is SOD

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] bigeyes0x0:
@spaceman: Here you are http://goo.gl/zcQnu
[Samsung Galaxy Nexus] jornbjorn:
SOD = Software On Drugs
[Samsung Galaxy Nexus] nodstuff:
What it really means is sleep of death. Search for it and you'll get better info on it.
[Samsung Galaxy Nexus] Tommebaas:
Can anybody tell me if peggle is working with this kernel? I don't care about the battery life or performance, I just want to play peggle.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] vomer:
franco: any comments on the voltage jumping problem in hotplug governer on r111? Is it normal?
[Samsung Galaxy Nexus] franciscofranco:
Two things happen on that screen:

- Two threads running, one for the UI and another that is reading from the voltages files. The reading thread is fetching the files while the UI thread is receiving the values and updating the UI. That creates a little overhead and possibly makes the CPU jump frequencies a little;

- Hotplug governor is constantly polling the system for load changes so that creates a small overhead as well.

Those two things happening at the same time makes it seem that the device is always jumping around, but that doesn't happen during normal device usage since we don't always have a thread fetching files to update a UI screen.

TL : DR -> Don't worry about it.
[Samsung Galaxy Nexus] GibMcFragger:
Hahaha brilliant! I can't believe I hadn't seen that until now lol.

Swyped from my GNex using XDA Premium.
[Samsung Galaxy Nexus] hawkye:
It definitely doesn't like it LOL! I just used it for about 2hrs this morning and another SoD. Going back to OnDemand. ;)
[Samsung Galaxy Nexus] vomer:
Thank you! That makes sense :D
[Samsung Galaxy Nexus] Stretlow:
Franco

Would you mind posting your exact setup with r111 (Govenor rom sync etc) I am getting better battery than any other version but no where near what you posted yesterday.

Thanks in advance
[Samsung Galaxy Nexus] tcchuin:
It seems that I have better battery with r110. Mefiaserver wakelocks are higher for me on r111
[Samsung Galaxy Nexus] nodstuff:
Its media scanner not mediaserver, mediaserver holds a wakelock when you listen to music etc.

Media scanner is self explanatory.
[Samsung Galaxy Nexus] Bram77:
Just wanted to say that r110/r111 are the best kernels I've useb on my gNex so far. Very smooth, stable and battery friendly. I'm amazed how you can keep making it better and better. Realy impressive!
[Samsung Galaxy Nexus] stupidslow02gt:
My GF and I just had a SOD within five minutes of each other :(

She is using r98 and I'm on r110. I'm using hot plug governor and she ondemand. We are both at 384/1344. If it happens again I'm switching to ondemand. And again after that I'm going to r111 with stock GPU clocks.
[Samsung Galaxy Nexus] asb123:
Are you considering changing the colour control to a system that works with the settings in AKOP?
[Samsung Galaxy Nexus] joelteixeira:
You're spending to much time on this forum and your GF sabotaged your phone.

Try to set your minimum CPU to 729, you probably won't notice any battery drain cause your phone will switch to 1344 less often. And it's so moooore smooth.

Tapatalked from my Nexus Prime
[Samsung Galaxy Nexus] stupidslow02gt:
I switched to r111 with ondemand. Some strange **** started to happen so I'm sticking with ondemand until the hotplug governor is tried and true. Also r110 seemed to have significantly worse battery than r98 so I'm thinking it was that media wake lock. Hopefully r111 gets me back to how things were going on r98.
[Samsung Galaxy Nexus] QUEDRO:
Pic below is on Milestone 2

Just flashed r111.....
[Samsung Galaxy Nexus] mazubo:
LMFAO :D:D:D
[Samsung Galaxy Nexus] ragnarokx:
I just flashed the new 4.0.4. I know this kernel is compatible with the Toro 4.0.4 leak, so it should work with the Maguro 4.0.4 right?
[Samsung Galaxy Nexus] raubkatze:
From rootzwiki:
[Samsung Galaxy Nexus] franciscofranco:
Thats untrue. The new 4.0.4 with the new binaries **** up the kernel compatibility since we need the new DDK kernel drivers (GPU drivers). Until we have the new OMAP kernel source out theres nothing we can do about it. In fact I think theres a possibility to get those DDK drivers. Let's see what I can do.
[Samsung Galaxy Nexus] raubkatze:
Thanks! I was almost going to flash...
[Samsung Galaxy Nexus] SirOcelot:
Please correct me if need be, but I seem to notice that the GSM users are the ones that are getting the SoDs. I personally have the LTE variant and have yet to experience SoD, screen tearing or any of the other aforementioned problems that plague this forum.
[Samsung Galaxy Nexus] GibMcFragger:
Not sure. I have the GSM version and have yet to experience a SOD. I have tried every ROM and kernel combination possible too. I have settled on BAMF and this kernel. They make for a butter smooth experience on my GSM GNex. I can't wait till we get some 4.0.4 lovin (I know we need the kernel source as stated above).
[Samsung Galaxy Nexus] dcoy82:
I'm on the LTE Verizon and got SOD on 110. Have not had a single since reverting back to 98 and have not tried 111 yet.
[Samsung Galaxy Nexus] zgmf-x322a:
will there be an update for gnex milestone 4 rom?

thanks
[Samsung Galaxy Nexus] johno168:
Wrong thread i think?
[Samsung Galaxy Nexus] franciscofranco:
I have to wait for the newer sources. Me and Imoseyon have been trying to boot our devices with 4.0.4 and merging android-omap-3.0 to our kernels but its stuck on a bootloop.

Just in time for a new nightly to fix those damn SoD's ;)
[Samsung Galaxy Nexus] johno168:
so will your kernel at the moment work with 4.0.4 rom's?
[Samsung Galaxy Nexus] franciscofranco:
No.

r112:

* Sleep of death fix attempt
[Samsung Galaxy Nexus] GibMcFragger:
Not unless you like bootloops...

Swyped from my GNex using XDA Premium.
[Samsung Galaxy Nexus] johno168:
Thanks for the replies! I appreciate it! In the mean time n112 (512mhz + 700/1200 ondemand) + AOKP 28 should be just fine!

thank you so much franco!
[Samsung Galaxy Nexus] GibMcFragger:
Lol give it time. The 4.0.4 based ROM updates and kernels will be out soon enough. I can't wait either.

Swyped from my GNex using XDA Premium.
[Samsung Galaxy Nexus] Gahh Its Lee:
On r112 running fine never had a sod but I figured why not update. I was happy to see on rootz people were sent to xda earlier today. Makes me feel maybe we won't die over here.
[Samsung Galaxy Nexus] resynx:
So how does one get out of the SOD when it occurs? A battery pull?
[Samsung Galaxy Nexus] heo_con184:
Yep, pull out the battery, plug it in and power on.
[Samsung Galaxy Nexus] nbeebe24:
Franco, I for one would like to thank you for all of your hard/brilliant work. I have been running your kernels since the first release and have never had any issues with any of them. Keep up the great work, its much appreciated!
[Samsung Galaxy Nexus] EspadaKiller:
Guys, 700/1200 or 300/1200 saves more battery life? I guess 300? And what is the difference in terms of performance?
[Samsung Galaxy Nexus] johno168:
In theory yes. But i use 700/1200. It seems to go in deep sleep quicker also most of the time your cpu is at 700 anyways. That could also just be me. Performance wise, less stutter than 300.
[Samsung Galaxy Nexus] SirOcelot:
To be honest, I run mine at 1228/729 and have noticed a very negligible drain especially so after I switched to the hotplug governor.
[Samsung Galaxy Nexus] EspadaKiller:
Alright thanks guys, guess I will try 1228/729 option! :D
[Samsung Galaxy Nexus] ArmanUV:
you might wanna consider 729/1350. Due to the small voltage difference between 1200 and 1350, the battery hit is minimal.
[Samsung Galaxy Nexus] nailbomb3:
Franco, thought I'd let you know on n112, I had had a mediascanner wakelock that lasted well over an hour. First time I've ever had one actually.

So it would seem rather than fixing it, it caused it.

Thanks for your hard work!
[Samsung Galaxy Nexus] GibMcFragger:
Ok. I need to change my earlier answer. The latest nightly works fine with the 4.0.4 that birdman just put up. I am running the combo now and it works great. So yea, this kernel seems to run fine with 4.0.4

Swyped from my GNex using XDA Premium.
[Samsung Galaxy Nexus] drewlim:
How do u like 4.0.4 so far?
[Samsung Galaxy Nexus] EspadaKiller:
Okay will give it a try. Thanks :D
[Samsung Galaxy Nexus] Mrc527:
CIFS Support

I've recompiled the 112 version, with CIFS support too! :D

Look at here:

http://www.kernel-xp.net/index.php/en/progetti/20-galaxy-nexus-kernel

I hope it helps.

Bye!
[Samsung Galaxy Nexus] MacDaddyTMT:
Preliminarily, I think your attempted SoD fix has succeeded. I've been running 112 with hotplug governor for several hours now without issue.
[Samsung Galaxy Nexus] lukasb9000:
Running 112 @ 729/1344 with hotplug and 512 gpu without any problems here too...no SoD or whatsoever

Just a small question: the hotplug governor acts like the hotplug option on former versions right? so it disables one core just when screen is off? or also when it's not needed while running some apps or something?

And the cpu scaling, the threshold when it jumps to a higher clockspeed...which governor is it most comparable to? interactive, ondemand or conservative?
[Samsung Galaxy Nexus] raubkatze:
Hotplug Mod disables one core when screen is off but it was removed from kernel since r111.

Hotplug governor disables one core when it's not needed. As Franco wrote, hotplug governor is basically ondemand + dynamic hotplug.

I'm using hotplug governor - works fine.
[Samsung Galaxy Nexus] samizad:
I've got the 4.0.4 running with franco's kernel and it performs more or less the same as before (comparable to AOKP M4).

I miss the ROM options and Nitroz's Black Exodus theme though. I'll give it a few days and I'm sure there'll be loads of ROMs coming out based on 4.0.4.
[Samsung Galaxy Nexus] Unlawful:
That's very impressive for stock, though it seems Google is always playing catch up with dedicated devs these days (after they and hardware vendors release their sources anyway). But still Google-Love.
[Samsung Galaxy Nexus] raubkatze:
Kernel works as well as possible. For me r112 looks like M3 ;)
[Samsung Galaxy Nexus] Antob125:
So Roman just released AOKP b29 on 4.0.4. So currently this kernel will or will not work on 4.0.4? I know OP says it's compatible but just making sure.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] raubkatze:
Downloading now. I'll write as soon as flash it.

---------- Post added at 05:04 PM ---------- Previous post was at 04:39 PM ----------

Flashed b29 and r112 (384). On my mind works fine. Will be watch...
[Samsung Galaxy Nexus] schizophrenia:
did you fully wipe? or just flashed on top of b28?

thanks
[Samsung Galaxy Nexus] raubkatze:
Dirty flash. Over b28 without wiping.
[Samsung Galaxy Nexus] vomer:
dude you should probably do a wipe to avoid problems.
[Samsung Galaxy Nexus] raubkatze:
Why? I had no problems till now. And I always able to reflash rom with full wipe if problems will appear.
[Samsung Galaxy Nexus] sotoskawasaki:
Roman in his OP specifically says to wipe wipe wipe wipe. :)

Now back on topic!
[Samsung Galaxy Nexus] stellaryt:
Just flashed AOKP B29 (4.0.4) couple of hours with franco's kernel.Work fine till now except the rom's known issue.
[Samsung Galaxy Nexus] kecinzer:
What is rom's known issue?
[Samsung Galaxy Nexus] GibMcFragger:
To be honest, it's performing exactly the same as AOKP b28 and Franco's nightly was for me. The only thing that has changed is the lack of customizations. It's maybe a tad smoother/faster, but that could be placebo.

Swyped from my GNex using XDA Premium.
[Samsung Galaxy Nexus] raubkatze:
eg FC on lockscreen wall
[Samsung Galaxy Nexus] monkey hung:
I've noticed that forcing GPU acceleration in developer options actually makes things less smooth on the latest kernel and aokp build 29. First time I ever disabled it. I guess we don't need it anymore!
[Samsung Galaxy Nexus] TheInVisibleGoD:
True... but that does not mean that everyone who don't do a fresh install will have issues! Just do a backup before upgrading to be safe, I did and until now, zero issues.
[Samsung Galaxy Nexus] raubkatze:
I agree and I have not any issues except known.
[Samsung Galaxy Nexus] vomer:
You guys think 112 is m3? Haven't seen any issues personally but maybe franco has something up his sleeve for 4.0.4 :D
[Samsung Galaxy Nexus] cyanoviper:
i seem to be getting that mediascanner issue with 112 on aokp #29, so i reverted to the aokp stock kernel for the moment

edit: nvm it seems it was a one time issue, was gone after i flashed again
[Samsung Galaxy Nexus] franciscofranco:
Now that 4.0.4 is out I'm gonna hold on until we have full kernel sources available, then we'll see.
[Samsung Galaxy Nexus] SpOuK-3-:
I'm running my own AOSP build with r112... looks perfect to me... no issue since yesterday...
[Samsung Galaxy Nexus] ProficienTICS:
Just came back to Franco and wondering what best under volt values are? For 112
[Samsung Galaxy Nexus] vomer:
Nice! I am planning on holding off on 4.0.4 just to let the bugs iron out... so this works perfectly :)
[Samsung Galaxy Nexus] kashix:
On AOKP b29 with r112! Smooth!
[Samsung Galaxy Nexus] eRajesh:
How do you guys OC the GPU? Cannot I manually control the GPU clocks, like I do for the CPU?
[Samsung Galaxy Nexus] kashix:
gpu cannot be oc cause franco removed the live gpu oc. you can only select the gpu clock from the nightly manually.
[Samsung Galaxy Nexus] Remoteconcern:
There isn't really any need to undervolt on this phone, because of smart reflex.

If you want some good starting points though, check out the James bond kernel thread.
[Samsung Galaxy Nexus] nikulogical:
So is 112 working with aokp b29?
[Samsung Galaxy Nexus] CommanderDuplex:
Had realy good Ram-space with the nightly r112 and CM9 (4.0.4) , arround 400MB ! (402-405mb) of FREE RAM !!

Nice work Franco :D!!
[Samsung Galaxy Nexus] kashix:
yeah and it's blazing fast. Faster than any of the build I've used before.
[Samsung Galaxy Nexus] raubkatze:
Works great!)
[Samsung Galaxy Nexus] kecinzer:
Starting with Kernel nightly 100+ I experiencing twice or triple more battery drain in stand by with data and sync on. When I turn off data battery drain is same as usual.

I have other confirmation about this battery drain from czech android forum.

Anyone else can confirm it?
[Samsung Galaxy Nexus] Elganja:
this kernel seems to have the best battery life yet for me since m2
[Samsung Galaxy Nexus] raubkatze:
Can't confirm it. It looks fine for me. 0-0,5%/h when screen off... What else needs to be happy? )
[Samsung Galaxy Nexus] GibMcFragger:
Nope, battery life has been amazing for me.

Swyped from my GNex using XDA Premium.
[Samsung Galaxy Nexus] EnIXmA:
The battry life is phenomenal on r112. I got my best on screen time today :)
[Samsung Galaxy Nexus] resynx:
My wifi turns off when my screen goes off even though its set to always be on. I think this started happening after I flashed M2 last night, is anyone else experiencing this?
[Samsung Galaxy Nexus] zephiK:
Settings -> ROM Control -> Power Saver -> Screen-off WiFi action? Is it set to untouched?

Settings -> WiFi -> Advanced -> Keep Wi-Fi on during sleep -> Always.

Check those two. Specifically the first one. Pretty sure that the problem you're having has nothing to do with the kernel.
[Samsung Galaxy Nexus] KingDavid63:
love what you done with the in app mods selecting two different gpu oc options.. nice man, keep up the great work...

gonna try this hotplug gov out, will report back with info, been running on demand with hotplug mod for the longest...
[Samsung Galaxy Nexus] nikulogical:
Why was OC'd gpu introduced again? I thought that it didn't bring much advantage but was bad for the battery?
[Samsung Galaxy Nexus] resynx:
They are both set as you said above. Hm, I wonder what could be causing this then o_O
[Samsung Galaxy Nexus] Mondfahrer:
I have the same issue with r112. In standby-mode my wifi turn off although I checked the two settings which "zephiK" mentioned.
[Samsung Galaxy Nexus] mikeandjaimie:
Are you actually loosing your wifi connection, or its going grey instead of blue, cause they are two different things. I have often found it grey (no Google connection) but never actually dropping the wifi connection totally.
[Samsung Galaxy Nexus] franciscofranco:
Yes, it's in the OP and I already posted a pic of me holding the phone some days ago...

It's not working how? It works fine to me. I need more evidence that it doesn't work, I have no problems with it.
[Samsung Galaxy Nexus] theboo7:
Idk how else to prove it..
[Samsung Galaxy Nexus] franciscofranco:
That's with this kernel? If it is so I'll remove the UV interface.
[Samsung Galaxy Nexus] theboo7:
Yeah, your latest one posted.
[Samsung Galaxy Nexus] franciscofranco:
Thanks, bye UV.
[Samsung Galaxy Nexus] theboo7:
No problem, other Devs are having problems with it as well, and some have already removed . Hopefully we can get this working
[Samsung Galaxy Nexus] RMatt1992:
Thats unfortunate, it was working in the 4.0.1 build.

We shall see!
[Samsung Galaxy Nexus] theboo7:
Word is that if you can set UV in the kernel yourself then compile and Give to us so we can have a mild UV. Safe UV for most phones are

Frequency Voltage

350Mhz ------- 0.975V

700 ----------- 1.150

920 ----------- 1.225

1200---------- 1.3

Voltages taken from Fabolous over @rootzwiki
[Samsung Galaxy Nexus] franciscofranco:
I don't want to set it directly into the source, I prefer having the stock voltages from TI to maximize stability, there was a reason they set up those values. I'll try to do something else, like a loadable module or something with some mid undervolt values. Currently I'm working on a logcat mod to make it loadable on demand. Something like: terminal -> su -> logcat_on -> Logcat enabled, reboot please. Then to turn it off -> logcat_off -> Logcat disabled, reboot please.
[Samsung Galaxy Nexus] theboo7:
Yeah, i understand, Francisco knows best lol. well can't wait for the next nightly.
[Samsung Galaxy Nexus] franciscofranco:
It's a few hours to being released, but performance wise there isn't much more that I can do, I already squeezed almost every bit available. Now I'm working on stability and adding a new modular approach to give users some choice. Battery wise my phone is with a straight line on the battery graph since it's been idle for a little, can't ask for more, obviously running with nightly 3.
[Samsung Galaxy Nexus] theboo7:
Can't wait. Can't complain about battery life on #2, every other kernel is good on Quads and benchs, but yours are way smoother and almost double the battery life.