yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Right now SR is hardcoded disabled, but the UV interface works (so the voltages aren't hardcoded). Franco's likely seeing if anyone cares. :p

There's also a dev thread about improving on the (many) failings of SR on tuna as it is, so maybe Franco's disabling it until we have something better.
[Samsung Galaxy Nexus] bunnahabhain:
AW: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks guys. Just messed some time with lean, trinity and ak kernel.

Lean can't handle my colorcontrol settings. Trinity won't boot and AK gave me 3 times a Black screen after google Logo that leaves the phone unusable. I hope Francos Kernel will do the trick.

Just wanted to check the thing with smart reflex, since i used Francos kernel for ages and reminded that smart Reflex was enabled ever since. Now i know. :thumbup:

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

r366? Got to go flash...
[Samsung Galaxy Nexus] franciscofranco:
Just pushed r366:

r366:

* Merge upstream version to 3.0.66

* Merge a bunch of patches from my Mako kernel which include a memory leak fix, two fixes for semaphores, a new hashtable implementation (google Hashtable if you don't know what it is), and some other patches - take note all these patches come from Linux Kernel developers, I did nothing besides reading the patches, reading the code and merging them.

* r366 version number and .66 upstream number… see what I did there?
[Samsung Galaxy Nexus] AndyGnex:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

All hail the king of kernels
[Samsung Galaxy Nexus] creeve4:
above_hispeed_delay and timer_rate: franco's defaults (30k) or 15k? I thought the settings we found to be optimum are 15k. Why is 30k still the default?

For deadline, front_merges and fifo_batch have both been set to 0 in 366, what is the logic behind this? I get that a value of 1 for fifo yields first-come first-served behavior, but what does a value of 0 do?
[Samsung Galaxy Nexus] shawnaye:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Franco did post some time back that he did prefer 30k and still found 30k better.

The man has his reasons.

If you find 15k better, go ahead and use it. No one's stopping ya :D
[Samsung Galaxy Nexus] franciscofranco:
The IO tunables are the ones from malaroth, unless I'm missing something.
[Samsung Galaxy Nexus] osm0sis:
Those two tweaks go with two other new tweaks:

echo 2 > /sys/block/mmcblk0/queue/nomerges;

echo 2 > /sys/block/mmcblk0/queue/rq_affinity;

Both of the above are default in r366. :D The GN still doesn't accept 2 for rq_affinity, it only goes to 1, but all 4 of those combined improve deadline to malaroth's/our latest and greatest testing.

read_ahead_kb is still 1024 on r366, franco must have forgot that, so if you want to experience them properly:

echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb;

:good: Thanks Francisco! And happy belated birthday! :)
[Samsung Galaxy Nexus] creeve4:
Should fifo be 1 or 0? Malaroth has 1 in his deadline script. Does 0 just disable fifo?
[Samsung Galaxy Nexus] Blackcrx:
Any chance the 4.2.1 kernel getting updated or having an universal kernel for 4.2.1 and 4.2.2?
[Samsung Galaxy Nexus] shreddintyres:
4.2.1 and 4.2.2 use different binaries i doubt its possible/feasible to make a universal kernel
[Samsung Galaxy Nexus] Blackcrx:
Actually Lean and Air (possibly other kernels too) have universal kernels for 4.2.1 and 4.2.2
[Samsung Galaxy Nexus] AutomaticFailure27:
PGM doesn't boot, probably something to do with PGM's code again?
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yes. Report it on the app thread.
[Samsung Galaxy Nexus] haxor:
Need Help :( I was updating my apps from playstore suddenly my phone restart it self after to it my phone goes restart it self after google logo not able to boot what should i do :confused: i am on franco #365 what it cause and how to get rid of it ?
[Samsung Galaxy Nexus] alfiemenace:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

@osm0sis

If i echo 512 to /sys/devices/virtual/bdi/179:0/read_ahead_kb is it the same? Just asking because I know that this path is also existing.

Stock ROM, custom user.
[Samsung Galaxy Nexus] reysonance:
It works, mmcblk0 is just a symlink.
[Samsung Galaxy Nexus] SamOliver:
Any advice for preventing random reboots? This kernel is super fast, but I get 1 or 2 random reboots a day. It's not a SOD issue because the screen doesn't freeze, it just reboots. What are some of the most common reasons?
[Samsung Galaxy Nexus] shreddintyres:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

There are about a hundred things that could be causing it from bad rom installation to poorly written apps to user error hard to say what is causing your random reboots with out knowing more about your setup
[Samsung Galaxy Nexus] MountainX:
Did you even read my post?

usbserial driver <-- very important

Where's information about that in the thread title? Or about zram or nfs?
[Samsung Galaxy Nexus] BLL00:
-NOOB ALERT-

How do I install this, and is it reversible ?
[Samsung Galaxy Nexus] franciscofranco:
I don't know what is that usb serial. ZRAM no, don't bother asking for it as I'm not including it, it's useless. NFS not yet, keep forgetting to enable that.
[Samsung Galaxy Nexus] wayneb02:
Go into cwm

wipe cache/davlik cache

Install from sd card
[Samsung Galaxy Nexus] nic85:
How did you set screen brightness?

Lol i Read now with auto, but more or less was like 50%?

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] grinch247:
I may not know alot...however..I have used francos kernel with every rom I have used thus far....and I can say "without a doubt" his work/efforts to improve the "Gnex" experience he has not only impressed me but several of my friends..(whom have had a tbolt,rezound,bionic) and have since switched because of his efforts....this is'nt an ass kissing session/post...just a straight up KUDOS!

FRANCO..........YOU ****ING ROCK!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Samsung Galaxy Nexus] dyndragon:
Oh, NFS isn't enabled in this kernel? No wonder! Up until now I was wondering why apps like NFC Info weren't reading my RFID tags! I thought I just had incompatible or encrypted tags...

Is that just a switch to flip on or is there some major work to be done there? It'd be nice to have the feature!

Thanks Franco for your work
[Samsung Galaxy Nexus] MountainX:
Thank you! OK, I'll forget about zram. NFS would be great! Here's some background on usbserial:

usbserial kernel module: https://www.kernel.org/doc/Documentation/usb/usb-serial.txt

relevance: https://code.google.com/p/usb-serial-for-android/

http://slickdevlabs.com/slick-usb-2-serial-library/ (wow - $99! - we can do it for free!)

http://www.mailinglistarchive.com/html/android-kernel@googlegroups.com/2010-07/msg00057.html

http://www.tombom.co.uk/blog/?p=124
[Samsung Galaxy Nexus] clefster:
NFS is not NFC
[Samsung Galaxy Nexus] wil2bm:
Today I flashed to the latest version along with AOKP - seemed to be a good mix till I went to make a call and realized any call I made/received dropped in a matter of 3 seconds lol...

Does that sound like a kernel issue or possibly the rom? I had enabled power saver so wasn't sure if that may have done something...
[Samsung Galaxy Nexus] Thracks:
I found that power saver in AOKP is a little unreliable in that it doesn't always want to bring data back without a reboot. I usually leave it off, now.

Not a kernel issue.
[Samsung Galaxy Nexus] birdster:
Hi Franco, for me the last two version have been causing dropouts on wifi-tethering its doesnt seem to hold a connection as well as previous versions, ive checked my ping times on the phone and speed and they all seem great but after a while the connection to my computer becomes flakey at best, im wondering if the power saving is somehow kicking in when wifi-tethering is on ??
[Samsung Galaxy Nexus] dpaine88:
Franco would you mind sharing your opinion on UVing ourselves? Do you really think it could make an impact on battery life ?

If he has answered this already, I apologize but please paraphrase what he said for me , thank you :)
[Samsung Galaxy Nexus] birdster:
HI Franco could you put wusb support in your next version please or maybe direct me to a beginers guide to how to do it myself and compile my own version based on your kernel ? I know wusb wouldnt isnt that popular but im working on a project that requires this, the hard work is already done at http://o2droid.phj.hu/trac/browser/kern_oII/include/linux/usb/wusb.h?rev=2 i would be forever in your debt if you could do this, thankyou :o
[Samsung Galaxy Nexus] Thracks:
Undervolting can substantially increase battery life. You'll be lucky to get more than -75mV on all of your steppings. Please read the thread next time.
[Samsung Galaxy Nexus] ArmedandDangerous:
True, but I will be installing this kernel into the GN should I get one, and would just like to know how much of an improvement getting the GPU to 384MHz really is in the real world :)

I love the Nexus environment, but sadly they almost never come with the best hardware. Will decide when stock is replenished at my local Samsung store :) Thanks all!
[Samsung Galaxy Nexus] dpaine88:
No need to come off as a ****, I have read tons of pages of this thread as a matter of fact, but this is a very busy thread and has 5-6 new pages daily.

I simply ask because I see two sides of the arguement and was curious what Franco thought since he is the kernel dev.

Sometimes I see people say "The kernel is already UV, there isn't a need for any more UVing because the battery gain is so minimal its not worth it and makes it less stable"

Then other times I see people such as yourself say " Yes, UV can have a significant impact on battery life."

Related to UV: I have been experimenting in SetCPU using the instructions posted about 6 pages back using the "Stability Test" app and have found voltages that pass the test for 10+ minutes but then when I reboot the phone, it stays on the boot animation forever. I try leaving battery out for 5+ minutes, wiping cache/dalvik etc but I am forced to do a restore to a prior backup or do the SetCPU safeboot thing. I made sure NOT to check "set on boot" in the voltages tab.
[Samsung Galaxy Nexus] wil2bm:
I had the same problem - Really hope they work the bugs out because that feature would help ALOT with the damn battery lol...

Had a feeling that might have screwed something up... On a CDMA phone btw posted in wrong board!
[Samsung Galaxy Nexus] tsekh501:
Regarding StabilityTest: 10+ minutes is definitely not enough. Test the desired voltage at the specific frequency, and lock at that frequency and have StabilityTest (classic) run at least an hour. After you did that for each frequency, do a scaling test. Being stable at each frequency does not guarantee stability when you allow the frequency to change. The main reason is that voltage change is not really instantaneously. For example, when your CPU jumps from 350MHz to 1200MHz, the supplied voltage may have yet jumped to the voltage you set for 1200MHz, causing instability.
[Samsung Galaxy Nexus] Nebucatnetzer:
One of the reason why I like to undervolt the phone myself is that every phone is different. As you may have seen before. One guy is able to run 350 MHz at 750 mV which doesn't work for me. It's a difference of 75mV.

I don't agree with the guy above. You don't have to run Stability Test for an hour. For me it works perfectly fine just to find out which value might work. The real testing is done when you are using your phone normally. Because real world usage differs from testing.

For your reboot thing. This shouldn't be caused by undervolting since a reboot restores your values back to stock. Did you probably set "set on boot" for the frequency?
[Samsung Galaxy Nexus] SamOliver:
Everything is default except I use wheatley and 1.3 ghz, no reboots when I use default or tiny kernel. Also, it might be noteworthy that when I enable min freq of 192 mhz I always get a reboot within minutes, so I don't enable 192 mhz anymore. I thought maybe the low frequencies were undervolted too far, because it usually reboots when it's in my pocket and I'm not using it, but I still got a reboot after increasing the 384 mhz freq voltage to 875.
[Samsung Galaxy Nexus] reysonance:
A warm reboot should produce a last_kmsg, try pulling that.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Stock voltages? UVing too far is a common cause of reboots.
[Samsung Galaxy Nexus] ajm786:
Franco, I know this is not in the kernel changelog, but did you change anything from 365 to 366 relating to the wifi driver in the kernel? I get horrible wifi performance from 366. For instance, transferring a FTP file on my local network to my Galaxy Nexus on 365, I get between 2500 and 3500 Kbps, whereas with 366, I get between 800 and 1000 Kbps.

Going back to 365, everything works beautifully.
[Samsung Galaxy Nexus] jswede:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -> 4.2.2| r364 -> 4.2 | r300 -> 4.1

Do a factory image restore, then ask yourself if you should mess around with kernels again.
[Samsung Galaxy Nexus] bat0nas:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I think I am on the same boat.

I had very often phone freezes during app installation from the Google Play. I had to remove battery to restart my phone.

Same during taking photos. If I shoot rapidly and then try to view the last photo - the phone dies. Image on the screen freezes forever. Again remo e the battery.

Same after flashing factory images and franco kernel.

So now I decided to use stock for a while. Let's see if Franco kernel was causing that or not.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
0. The r366 defaults are correct, and malaroth and francisco's latest, just not released to general public until now. We tested them in private and they're excellent. Only thing boss man missed was the read_ahead_kb buffer like I wrote before, and the GN code doesn't accept rq_affinity 2; this is on the books for a future build as well unless he changed his mind.
[Samsung Galaxy Nexus] thuanle:
Yeah, we also bought the Franco's app to support kernel development by ourselves.
[Samsung Galaxy Nexus] gaich:
If someone is interested, cured with setting read ahead to 128:)
[Samsung Galaxy Nexus] reysonance:
Were your free space was under >2GB by any chance? Digging back old thread it looks like it happen when the internal storage is almost full.
[Samsung Galaxy Nexus] sajty:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

PGM is not working for me with 366. After loading module i get hard reboot.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yes its been reported already, pass it on to the pgm dev

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
Yes, there`s still less than 1 GB space left, but now, when I`ve set 128, I do not see stutters anymore, I hope this will continue...:cowboy:
[Samsung Galaxy Nexus] sajty:
Thanks for the info,already reported to dev.
[Samsung Galaxy Nexus] Kurre:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

check this for a more information: http://xdaforums.com/showthread.php?t=1971852

in a nutshell, generally it would be good to have at least 2-3GB free. ymmv, depending on your flash chip.

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] haxor:
i just fed up bcoz i am keep try to recover my phone since morning i was on PA 20 feb build with franco #365 in morning i just update my apps from playstore don't know what went wrong :( my phone got reboot itself and after that its stuck at Google logo afterward i did factory reset wipe system/dalvik /cache to flash clean rom and i tried 15 feb to 26 feb build but still straggling to get my phone keep working :( :crying:
[Samsung Galaxy Nexus] Zadeis:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Have you tried the stock ROM at all? You can install the stock ROM using fastboot and get everything working again on stock and then try from there.
[Samsung Galaxy Nexus] haxor:
nope i didn't try stock bcoz i will tried stock then it will wipe my all data bro so don't wanna lose it stock will wipe my sd storage too
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Only if you flash userdata. Flash stock recovery, radio, system then you should be out of bootloop

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] haxor:
is there any other way to get rid of from boot loop ?
[Samsung Galaxy Nexus] Khizar:
dude stop posting in 2 different threads you will get confused plus you made a new thread in the general section lol..

if you can boot into recovery like you said in the PA thread and you made a nandroid backup restore it... if you dont have a backup use adb to push rom/gapps to your sdcard then flash them in recovery

PS- why dont you just flash stock minus the userdata to get rid of the bootloop?
[Samsung Galaxy Nexus] haxor:
bro i just fed up and i losing my passion i am trying to get back my phone in running stage thats why and don't if there some thing wrong from kernel or rom so which rom and kernel i have in my phone so it obviously thing that i will post in that kernel and rom thread !! and let me tell you i restored my nandroid but no luck there too same problem as it was and i tried factory reset and wipe system to try other rom but no luck !

and i think XDA is only place where i can get support is in it ?
[Samsung Galaxy Nexus] Fenvarien:
I had just the same problem yesterday. My Gnex froze when I updated Tapatalk in the playstore, after the usual battery pull it bootloped like there was no tomorrow... But via the still reachable recovery I flashed Leankernel 6exp1 and successfully booted. Asap I installed the just released franco.Kernel r366 and had no more issues. :) I guess I messed too much around with the scheduler tunables, did you use any tweaks, init.d scripts or "tuning" apps?

With r366 the new deadline tunables work great, thanks for the research and for adding this, malaroth, Osm0sis and Franco! :good:
[Samsung Galaxy Nexus] osm0sis:
Did 256 and 512 not work either for this issue?
[Samsung Galaxy Nexus] bigknowz:
Stutter Help

Thanks for the tip. Are you using deadline or row? I'm using deadline / interactive with the settings tweaks. I have been working on this issue for almost 2 months. I find it counter intuitive that read ahead should be so low, when I go below 2048, the stutter gets crazy. I will try 128 and raise from there if necessary, maybe there is a lower sweet spot. Things got better when I changed minfree values to match bouchigo's suggestion.
[Samsung Galaxy Nexus] Sveke:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Tapatalk fing blows. The app...That's the problem. Mine rebooted too on app update running evolution and Franco.

Didn't get a boot loop but still did it.

Tapatalk is an embarrassment.
[Samsung Galaxy Nexus] ChazzMatt:
EDIT: ok THIS is strange. I downloaded 366 through the Franco app, allowed it to re-boot and auto-flash, but now the Franco app says I still have 365? So, just flashed it again.

This behavior below was with the first flash... which may have not worked correctly?

_____________

Flashed #366, and upon rebooting it immediately froze while Google Play was updating an app. Battery pull, rebooted.

Then another immediate freeze while another app was updating. :rolleyes: Battery pull. Rebooted. Seems to be working OK now.

(My apps tend to update whenever I reboot and I'm on wi-fi.)

I'm on Bigxie's stock ROM 4.2.2.

1305 MHz max

384 Mhz min

Interactive gov

EDIT: This may still be a bad flash? See note at top of post.
[Samsung Galaxy Nexus] alfiemenace:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I really don't know why it works fantastically for most of us, yet not for some.

Stock ROM, custom user.
[Samsung Galaxy Nexus] whitedragonz83:
I had 2 freeze-reboots happen during Google Play app updates and trying to do other things. After switching from Deadline (with Franco defaults) to CFQ I haven't had this problem thus far. Only had 1 update session though with the new configuration. I might not have enough information yet, but CFQ feels close enough to the smooth deadline for most stuff and if it fixes the app update issues I've been having, then good. :)
[Samsung Galaxy Nexus] dustrho:
I experienced exactly the same problem using deadline as well, and I've switched to cfq as well. I'll see how this goes.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

This is just a random shout out to Malaroth for the ROW tuneables. Finally got off my butt and added them to my init.d.

Sexy stuff thanks man.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I was having freezing issues on 365 using deadline when updating and downloading from the play store. Switched to another scheduler and no more issues.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] abalam:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Run the latest nightly now a days and no lockup. Also no problems with play. Settings: interactive, deadline max freq 1305, min freq 384 fsync: off

Mostly running 6 apps on the background

Tnx Francisco:thumbup:
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I do care about voltages being enabled... but with testing io schedulers it wouldn't do much good to set different values to those when I'm not running Franco's stock voltages.

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] The Gingerbread Man:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Holy **** we have a time lord amounst us who is running latest 366 for a few days even though its 19 hours old lol :silly: :p

On a more serious note no freeze ups or anything like that since Christmas time for me and iv used row and deadline for a fair amount of time, all running well here so far

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Damn it I cursed my luck :p had a random reboot while waking the phone when I got an sms. My screen went kind of jaggered and weird with a few horizontal lines, froze for a second then rebooted. I use face unlock and it was when the front camera was establishing a picture on the lock screen. Here is last kmsg http://db.tt/U080o1oy. 366 ,stock rom, interactive, deadline, 512 kB read ahead, 192-1228mhz

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Samhain77:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I also had some of these freezes with 365 when updating apps from play store but with no reboot... After 15-20 seconds it comes back to normal. Now I'm on 366 and no problem for the moment.

I'm on stock 4.2.2 rom.
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So with 366 + most updated fku app Are the default settings now set to the sweet spots we came up with few weeks ago? Meaning Governor Control and Scheduler Tuning?

Sent from my Galaxy Nexus