yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] spinkick:
1. Install the latest nightly in the franco.kernel download tab. Pick "download latest nightly kernel"

2.In the OC/UV section make max cpu 1228 and min 384 mhz. Pick interactive for scaling governer. Click set at boot. You can pick a higher overclock if you want but its negligible performance increase and a bigger battery hit.

3. In settings leave generic hotplug off. check sqlite, turn logger off, enable usb quick charge to on, Leave wifi power management off.

That should do it. When you flash the nightly you can try the 512 mhz over clock version but if you get weird screen corruption flash the 384 version.
[Samsung Galaxy Nexus] jaenizzo:
Thanks Spinkick I appreciate it
[Samsung Galaxy Nexus] spinkick:
No problem, glad to help!
[Samsung Galaxy Nexus] gnexdude:
Just flashed 135 on 512...going to try see if it makes a noticeable difference and the phone can take it....
[Samsung Galaxy Nexus] Gahh Its Lee:
My phone can almost handle it. Its usable but really freaks out at times. 384 for me
[Samsung Galaxy Nexus] axne1:
Franco you might have Busted the Mold!

Gpu 512 /r135/Aokp B31 :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] axne1:
Yeah it's pretty weak right now.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ibe2fly:
Trying my first 512 v (r135) all is well and smooth haven't noticed any issues seems smooth ill update after more use .. Still have some lag when speeding through phone and trying to hit recent apps button but not sure if ROM, launcher or kernel issue ... Ill flash back to 384 v later just wanted to see if this issue would be fixed and if my phone could handle it

Sent from my Gummy 1.0 Nexus
[Samsung Galaxy Nexus] dadsterflip:
Battery extender on your app. I see 96 is default. Default with the phone or yours?

I'm guessing the way that works is set it up to 96 and it just charges to that.is that correct?
[Samsung Galaxy Nexus] axne1:
I put my setting back to 100% I'll buy a new battery if it blows in a year. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Same here. You never really know how much you miss 4% until it's gone.
[Samsung Galaxy Nexus] dadsterflip:
OK I feel the same way lmao . Just making sure. Wish we could put 200% hahahah. Joking by the way.
[Samsung Galaxy Nexus] axne1:
512 gpuTakes more juice for sure!...

but everything is Soooo smooth and fast!

I'm going to run this r135 for a few days if I can.

the last nightly I was able to run for 3days until I noticed the artifacts using the browser.

r135/512/OD/1300/700

Aokp B31

Wi-Fi,/sync/GPS/Data all going

Will report soon! :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aliensquale:
About to run the AOKP rom... From what i understand that includes it's own kernal.

Just wondering.. If I ran this kernel with that rom is it a faster, more stable phone?
[Samsung Galaxy Nexus] axne1:
Yes

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aliensquale:
Sounds good.. Any reason why the AOKP rom includes the stock kernel and not this kernel?

Do i install the rom first and then this kernel?
[Samsung Galaxy Nexus] axne1:
I thought they used faux kernel. But Idk

Franco has the best kernel period! :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kjwalker:
Rom then kernel. The rom contains its own kernel so it would overwrite Franco's.
[Samsung Galaxy Nexus] spinkick:
Does 512 really take more? My core runs at the same voltage for both. Is it a multiplier thing?
[Samsung Galaxy Nexus] aliensquale:
I want to set up my new nexus just like yours.. Stupid question probably..but what is 513 gpu and od mean?
[Samsung Galaxy Nexus] japaneezy:
513 gpu is the overclocked kernel. You are given the choice to use it or the stock gpu when you download the kernel from Franco's app. OD is the ondemand governor, also a choice within the app.
[Samsung Galaxy Nexus] aliensquale:
Franco stock is probably better right?
[Samsung Galaxy Nexus] axne1:
Yes for most

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Just wanted to update. I switched the Battery from 96 to 100 and it only charges to 98. Was curious to see what others are getting.
[Samsung Galaxy Nexus] axne1:
100% here

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Cool. Thanks man. I'll keep tinkering.
[Samsung Galaxy Nexus] jcmm11:
Just to make a correction here - the nightlies ALL have overclocked gpu. It's either 512 or 384. The milestones are stock, which is 307
[Samsung Galaxy Nexus] axne1:
Truth :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] axne1:
So I ran r135 512, it still leaves me with 1hr less screen time than M2. But SUPER Smooth and FAST!! Trying r135/384 now. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gnexdude:
Just want to report, I've been running 315 with the 512 and so far no problems..also I don't see a significant difference in battery ran it yesterday for like 17 hours 2:30 plus screen time and still had like 36% left!!!! Awesome nightly pretty solid IMO.
[Samsung Galaxy Nexus] axne1:
Awesome I wish I had those results. M2 I get 4hrs screen time. With 135/512 ran Great but at a cost. Still trying R135 with 384gpu. Hoping its better :o

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Flip35:
Hey guys I'm just trying to get some feedback, I've been running nightly116 for a while now I guess maybe I should update so how is nightly 135? I was getting awesome batt and performance was good so I'm scare to update, thanx
[Samsung Galaxy Nexus] franciscofranco:
#4.1

* Added a home screen widget with the same information as in the CalibratedVoltages panel - the information is updated automatically every 30m or every time you tap the widget

* Added ºF temperature value

* Changed max CORE text to show that it's the same OPP for 384 and 512 mhz GPU slot
[Samsung Galaxy Nexus] cc16177:
I've noticed a few people mention turning hot plug off in the settings. Am I missing something here? I know there can be instabilities with certain hot plug govs but I thought the hot plug option in settings was purely beneficial.

Also, what gov have you guys been using lately? I see a lot of on demand or interactive...
[Samsung Galaxy Nexus] patmw123:
Does anyone have a working link to Franco's #84 kernel? If I'm not mistaken, that was the kernel that pushed the final clock speed spot to 1.5ghz. I'm not an overclocker by any means, but my phone was perfect at 1.5ghz and while I wouldn't use it all the time, its a nice option to have.
[Samsung Galaxy Nexus] Gahh Its Lee:
You can go to 1.6 with some of those older ones. I had them all but I lost them about an hour ago
[Samsung Galaxy Nexus] sing1gnis:
Some have said that if you are turning your screen on and off a lot, hotplug actually hurts battery life. I turn my screen on in spurts so I leave it enabled.

Also, for my phone, interactive runs best.
[Samsung Galaxy Nexus] upther:
The only times I have gotten the dreaded SOD is with the hotplug option enabled. Plus for someone like me who turns his screen on and off quite a bit, the hotplug isn't good for the phone or my battery.

I've had the best luck using the Ondemand governor.
[Samsung Galaxy Nexus] tacosrdelicioso:
Latest nightly...I've had my nexus since last night. 1228mhz at 1125mv, 1036mhz at 1100mv, 729mhz at 875mv, and 384mhz at 750mv..seems super low? Compared to what it was
[Samsung Galaxy Nexus] Frozinite:
Interesting new widget Franco. Unfortunately it's called 'Example Widget'. Forgot to update the name I guess?
[Samsung Galaxy Nexus] franciscofranco:
Ups xD
[Samsung Galaxy Nexus] GinoSylum:
MMS stopped working for me with 135. Could not send or receive... Flashed back to M2 and everything works again. Has anyone else seen this?
[Samsung Galaxy Nexus] axne1:
no not yet??
[Samsung Galaxy Nexus] Gwanatu:
Is anyone still having issues with 4.0.4 and the latest nightlies and data not working while the screen is off? It seems to be worse when using Wifi instead of Cell Data, but I still have the issue regardless of the connection I'm using. This didn't seem to happen with nightly 121 but past that it seems to happen all the time. I flashed AOKP build 32 yesterday and it didn't seem to help anything.
[Samsung Galaxy Nexus] spinkick:
Try running minimum cpu at 729 and see if it improves
[Samsung Galaxy Nexus] sway40:
Honestly I still can't flash a fresh install of aokp above 29, which is the start of 4.0.4. My camera freezes my phone no matter what I do. I have to flash over 28 to keep this from happening. I've tried everything from different kernels to wiping m multiple times and nothing works, which leads to be either aokp new **** or 4.0.4 itself.
[Samsung Galaxy Nexus] spinkick:
Is it recommended to run 729 or 384 on this kernel?
[Samsung Galaxy Nexus] axne1:
I'll keep my eye on this one
[Samsung Galaxy Nexus] hotrock11:
Bought this

I never buy stuff....
[Samsung Galaxy Nexus] Gwanatu:
I haven't tried that since AOKP 32/Nightly 135 but I'll do that again. It worked in the past with nightly 121 and AOKP 30 so it's certainly worth a shot, I just forgot about it! Thanks!

EDIT: so far so good, it's been a while now and I've tried on both cell data and wifi and it seems to be holding the signal when the screen is off. I also turned off hotplug and turned on wifi booster just to be sure.
[Samsung Galaxy Nexus] cchhat01:
I am planning on switching from using the franco.Kernel on AOKP to CM9 nightlies.

I plan on performing a clean install.

Do i need to worry about any Ramdisk issues. Will i need to flash faux's ramdisk reset kernel before flashing franco.Kernel.

Also, I plan on UVing. So is this the proper way to disable smartreflex?

echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp

Thanks
[Samsung Galaxy Nexus] spinkick:
Awesome!
[Samsung Galaxy Nexus] mark manning:
Someone correct me if I am wrong but I don't think you will need to use the reset kernel. Cm uses the stock kernel so I doubt there are any ram disk tweaks.
[Samsung Galaxy Nexus] aliensquale:
Francisco,

I'm running your M2 kernal on my phone with the AOKP latest build.. WOW... it flies.. thanks so much!

I also went ahead and purchased your kernal app last night!!!
[Samsung Galaxy Nexus] Jeremiah_1988:
Son its fast for sure, running great so far on axiom pz m1!!
[Samsung Galaxy Nexus] mrwebb:
138 too damn fast...lol
[Samsung Galaxy Nexus] Aerocaptain:
WOW, Franco, you have outdone yourself. You have managed to create lightning with 138. Bad ASS. Thank you.

Sent from CDMA V6 SC GNexus w/Liquid & Franco's BAD ASS 138.kernel aka Lightning
[Samsung Galaxy Nexus] masri1987:
francoturtle?
[Samsung Galaxy Nexus] Aerocaptain:
To hell with francoturtle. We's got francolightning!!!!!!

Sent from CDMA V6 SC GNexus w/Liquid & Franco's BAD ASS 138.kernel aka Lightning
[Samsung Galaxy Nexus] vtmike:
On 138 I've had some graphics artifacts while running more demanding games. Screen froze up while using the browser too.
[Samsung Galaxy Nexus] azsl1326:
Sounds like your phone can't handle the 512 gpu. Maybe try the 384?
[Samsung Galaxy Nexus] vtmike:
512 gpu works on the previous nightly for me.

Switching to 384mhz does correct the problem though.
[Samsung Galaxy Nexus] djkurruption:
This kernel flies, have not used it long enough to report battery savings though. Thank you!!
[Samsung Galaxy Nexus] ghost_o:
I have the GSM version - did I post this in the wrong thread? Sorry! I probably only watched 30 minutes of video and took 10 calls during that 3 days, but I never turned anything off. I was in HSDPA+ coverage the whole time, and was getting push email for 2 separate accounts as well.

I was amazed as well. I have never had any android phone (N1, HTC Desire (same phone really), Atrix ) ever even come close to 2 days.
[Samsung Galaxy Nexus] unw1red:
The camera workaround seemed to have fixed the drain. I will post the battery stats from a non-workaround and a workaround later. Can this be fixed through software?

I have also found another bug. When you are charging your phone and then unplug from power, even though the lock screen is showing, it will not go to sleep. I am using the AOKP ROM with your latest kernel.
[Samsung Galaxy Nexus] rman18:
What ROM are you using with this Kernel?
[Samsung Galaxy Nexus] mild7intl:
Thx Franco this kernel is by far my favorite. It goes real nice with gumnynex. (I've tried a few others) and the combo rocks. Keep up the good work. :)
[Samsung Galaxy Nexus] bradm23:
Is this latest update for that was posted in the GSM thread for Lte also? Thanks!

Edit - the latest version in the GSM thread is up and running great. Only thing I noticed so far is the lock screen takes a little longer to unlock than version 8. I know some tweaks were implemented to help make it lawyer, but I think something changed and makes it a little harder to wake. Its not a big deal, but maybe a second or two slower.
[Samsung Galaxy Nexus] franciscofranco:
#9.1 is also up, forgot earlier to update this thread! Enjoy.
[Samsung Galaxy Nexus] deidein:
Purchased your app on the reputation in this thread alone. Kernel just installed with AOKP build 13 - Cheers to you, sir. If it works half as well as the people in this thread suggest, I've gotten 10 times my money's worth.
[Samsung Galaxy Nexus] vin2win:
Franco or anyone who knows...when the nightly updates come out do we just remove the old one of our phone when its connected to the computer and replace it with the new one, then just flash right away or do you have to dalvik cache wipe each time then flash?

Thanks
[Samsung Galaxy Nexus] paOol:
I always wipe davlik cache and THEN flash a new kernel.

even if it's just a newer version.
[Samsung Galaxy Nexus] sinik420:
I'd keep the old kernel until you know that the new kernel is better for you.
[Samsung Galaxy Nexus] bowsersoulstar:
Stupid question.

Are we still in need to do the 'Start Camera, then close Camera' fix? As far as I know, the battery drain fix listed on Nightly #7 log fixes that. Since the OP still has a note saying to try that, I guess I'm slightly confused.

Flashed #8 last night, charged to 100%, cleared battery stats and left it completely idle for about 5 hours and noticed quite a bit of battery drop even on Wifi.

Battery graph below shows a good amount of awake activity during those screen-off/idle times.
[Samsung Galaxy Nexus] sinik420:
Do you have auto rotate enabled?
[Samsung Galaxy Nexus] bradm23:
Franco, been loving your kernel, thanks! I was wondering if there is any kernel tricks you know about that speeds up charging? Coming from the Incredible there was a kernel that had this which was very nice. From your experience with Samsung phones, is there anything that we can do?

Thanks
[Samsung Galaxy Nexus] drtchocky:
can anyone help? market says app incompatible with device?
[Samsung Galaxy Nexus] bowsersoulstar:
Yes. that's what's causing it?
[Samsung Galaxy Nexus] sinik420:
Supposedly, try it without
[Samsung Galaxy Nexus] kjwalker:
Download BetterBatteryStats to see what is causing it to come out of Deep Sleep.

http://xdaforums.com/showthread.php?t=1179809
[Samsung Galaxy Nexus] franciscofranco:
Dunno really, this **** is already charging pretty fast, I'm not sure it's good for the battery health to give more energy per tick to fasten the charge.

It's a rom problem, contact your favorite rom dev for a fix on that!
[Samsung Galaxy Nexus] firepacket:
fantastic

this is a great kernel. I flashed gummy nex 3.8 and I liked it, but it minor stuttering and stability issues. After flashing #9.1 everything has been amazing - fast, responsive, both types of tethering works and is stable, and running well all day without any reboots. Battery life looks great as well.

I will keep this thread bookmarked for future updates.

One minor request - openvpn support?

Thanks! :)
[Samsung Galaxy Nexus] mikeacela:
Does enabling hotplug show slight slowness or unresponsiveness when going to wake or use your phone?
[Samsung Galaxy Nexus] mike216:
I've heard someone say something about toggling Bluetooth on and off and opening and closing the camera is a known thing to do
[Samsung Galaxy Nexus] mike216:
I haven't noticed any lag at all and I've had it enabled for 3 days now
[Samsung Galaxy Nexus] parkson:
Have been using #12 since release, without setcpu. Things are running smoothly.

Only noteworthy issue I am having is the occasional lock screen lag. Phone awakes fine but sliding lags and sometimes will hang after releasing slide. By that I mean it freezes on the unlock icon and doesn't enter to home screen. A screen off/on alleviates the problem, but maybe you'd want to look into something like this? I will try to wipe cache/dalvik and reflash the kernel now. Thank you for your great work Francisco Franco!
[Samsung Galaxy Nexus] Mandelbrot.Benoit:
Hoe is the color control mod accessible? Or is it passive?
[Samsung Galaxy Nexus] GirLuvsDroid:
I don't think your lag is attributable to the kernel. I'm not experiencing any lock screen lag or freezing, even with hotplug enabled and my min set at 350Mhz.

---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------

You need the franko.Kernel Updater found in the Market to access the color control mod (it's in Kernel Settings in that app).
[Samsung Galaxy Nexus] Rev1vaL:
I know what my issue was, forgot to clear dalvik before I flashed 12. Went, cleared and flashed it and it's been perfect. Also getting great battery life.
[Samsung Galaxy Nexus] dobo84:
Felt like my battery life was horrible on gummy nex with this kernel on #12 but I didn't wipe the cache , can anyone tell me what setting they were getting this great batt life from
[Samsung Galaxy Nexus] cooch:
Not convinced the Android OS bug is fixed

Running Axiom 2.4 with kernel 12. I've start and stopped the camera(even force closed it). Tried different settings within Wifi(Always on/off). This weekend I'll install some better battery monitoring apps.

Anything else I can try?

This kernel runs smooth BTW...much better than version 11 with the browser crashes/reboots.
[Samsung Galaxy Nexus] zakth:
How about a paypal option to buy the updater app?
[Samsung Galaxy Nexus] Mandelbrot.Benoit:
I tried to buy the app but it says "The seller is currently unable to accept orders". Any ideas?
[Samsung Galaxy Nexus] ndwatkins:
Same issue, just tried from the phone and the computer. Just an FYI!
[Samsung Galaxy Nexus] wallendiaz:
hi guys today l install Nightly 12 and want to know what is the best governor and setting, I am using setCPU and Eagleblood 4.0.3....thanks!!!
[Samsung Galaxy Nexus] kjwalker:
I have been using 700/1350 with interactive and hotplug enabled. Smooth as pie and great battery life. Attached screenshot is from an average day of use. Lots of texting, some music, phone calls, etc.
[Samsung Galaxy Nexus] yondercomesthetrain:
I am also having the same deal. I really want the updater app, but alas, it cannot be purchased. :( Please work this out for us Mr. Franco. LOVING #12, by the way. No problems here. Only the updater app giving me a bad time. Lol.
[Samsung Galaxy Nexus] EyeOfTruth:
I typically use the conservative Governor and have hotplug enabled.

I use setcpu with profiles, because I put my screen off all the way down to 350.

Typically I leave my phone connected to 3g/4g no wifi, several calls through out the day (I use it for biz), some texting. Today I didnt steam music for 2 hours while at the gym and my battery is at 54% and has been discharging for about 16.5 hours. I am running the extended battery.

My typical use is several phone calls, 3g/4g connection no wifi all day, and then 2 hours of media steaming while at the gym, and using my phone to track my gym stats so the phone is on for probably about 45 minutes to an hour of the gym time tracking stats. I can get 12 to 16 hours.
[Samsung Galaxy Nexus] CDuke619:
Can someone explain to me how to enable Hotplug please?
[Samsung Galaxy Nexus] ceredics:
How is battery life with this?

Sent from this GN on 4GLTE!
[Samsung Galaxy Nexus] wallendiaz:
I just did a test with the multitouch tester and this kernel #12, and for some reason I see a problem with the multitouch and this kernel, with the stock kernel eagleblood 4.0.3, I had no problems, I tried it because I like to play dead space and I began to see how the multitouch failed in the game, any suggestions????
[Samsung Galaxy Nexus] dwallersv:
There's an easy to use GUI in the latest version of Franco's app, or you can change them from the command line as stated in the OP.
[Samsung Galaxy Nexus] williamthegoat:
Running 138 with aokp 31. Seems fine so far. Ran a few benchmarks and played a game for a few. No issues yet. What is smartreflex anyways?
[Samsung Galaxy Nexus] spinkick:
its a setting that turns off the second cpu. Search the thread for more info
[Samsung Galaxy Nexus] franciscofranco:
A system to calibrate the internal voltages.
[Samsung Galaxy Nexus] kjwalker:
I can't say for sure yet, but sr3 seems FAST AS HELL.
[Samsung Galaxy Nexus] GinoSylum:
On both 135 and 138 mms does not work for me. Both times flashing back to M2 was the fix. Is this happening to others?
[Samsung Galaxy Nexus] csseale:
138=13great

Response from someone else's Samsung Google Verizon Galaxy Nexus
[Samsung Galaxy Nexus] williamthegoat:
Mine seem to be okay. Just sent and received a picture to my wife.
[Samsung Galaxy Nexus] GinoSylum:
Strange... Ok, not sure why it's not working for me... Could not send or receive on 135 or 138....
[Samsung Galaxy Nexus] Flip35:
Just flashed 138 n tried sending mms to my wifes phone n it worked for me too so all is well here
[Samsung Galaxy Nexus] aliensquale:
I'm running m2 with aokp build 32... When everybody says this latest kernal update is fast where are you seeing the increased speed? My phone is already fast as hell and I'm using the GO,Launcher... See other launchers better for speed and lower memory use?
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm using apex launcher I love it and trusted 138 destroys m2. I'd say try it for sure
[Samsung Galaxy Nexus] mike216:
138 is very fast. I was wondering if UV would now be a good thing to try on this SR 3.0
[Samsung Galaxy Nexus] laureanop:
I really don't see a difference in speed compared to 116, 131,133,135

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] mike216:
Its probably hard to tell being on Franco's kernels but I tried a few the last couple weeks and I'm noticing a very fast kernel. I'm a big battery guy so will see how this speed beast holds up. Yes I'm well aware its EXPERIMENTAL. Its all about testing and reporting real life experiences ;)
[Samsung Galaxy Nexus] mike216:
By the way Franco, not happy to see HTC 1X. Hope you don't forget about us.:D
[Samsung Galaxy Nexus] laureanop:
TBH I don't think my phone liked 138. To me 116 and m2 are the standards by which I compare all kernels.

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] mike216:
Those were good. I liked 133 a lot and yes M2 is in the A-kernel archives. What aren't you liking about 138?
[Samsung Galaxy Nexus] laureanop:
Phone was only as responsive on interactive or performance so battery was taking a hit. The other governors weren't as smooth with a noticeable ui lag on conservative even with my min at 729

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] mike216:
I charged all the way to 100 then noticed the default is 96. Did it really charge to 100 or is the extra 4% placebo?
[Samsung Galaxy Nexus] Tree of Knowledge:
138 has only been out for a bit. Shouldn't you give it a little longer to get a better idea?
[Samsung Galaxy Nexus] laureanop:
Let's give it another shot

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] mike216:
I always reboot after a kernel flash. This is essential to get rid of any lag you experience
[Samsung Galaxy Nexus] Adan.Mejia3:
Hey Franco had a few dropped calls the second I upgraded through your app from 135 to 138. Not sure if its related to your kernel but thought I would mention since you said 138 was very experimental. Anyways, back on 135 and everything seems to be fine again for me. Could just be coincidence.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] OneNutShort:
Could be my imagination, but I feel like 135 was giving snappier performance than 138.