yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Or, even easier, you could just use Franco's flashable zips from:

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/zips/

And flash from Clockwork mod.
[Samsung Galaxy Nexus] ledzpg:
Flashed it today on my gnex and it rocks.

Thank you very much, Franco. :good:
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Anyone noticed a long press on WiFi and Bluetooth quick settings tile will toggle them on/off on stock 4.2.2? Great!
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -> 4.2 | r300 -> 4.1

If nothing changes, ROW fans get ready, I might be close to finalizing the sweet spot. Ultimately the decision is Franco's. When he's ready he'll let me/us know. He's gotta be extremely busy right now though so be patient

Franco r364
[Samsung Galaxy Nexus] aeroseek:
I just want to report that I've also just experienced the phone freezing after app update in the market on r364. I'm using deadline with tweaked settings. Following the freeze and subsequent forced reboot, I changed to row, updated apps no problem, now back to deadline.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Are you setting the deadline values via init.d script? If not and if you've rebooted at all since setting them they are back at default 500/5000. The tweaked settings aren't implemented on Gnex yet

Franco r364
[Samsung Galaxy Nexus] aeroseek:
Yup, using init.d
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Hmmm... that's strange... I'll look into it

Franco r364
[Samsung Galaxy Nexus] thloe:
great kernel,

aokp stevespear aokp_maguro_PUB_Feb-05-13.zip and francos r364

thanks franco :good:

see screenshot

http://dl.xda-developers.com/attach.../2/6/6/6/6/Screenshot_2013-02-13-16-38-45.jpg
[Samsung Galaxy Nexus] aeroseek:
Some people have reported this issue a few dozen pages back on "stock" deadline i/o values which makes me doubt it has anything to do with your tuneables. Also, flashing to r361 is supposed to fix the problem. I haven't done that though.
[Samsung Galaxy Nexus] bigknowz:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Osmosis, have you set up an init.d script with an if then statement? I was thinking of trying to set one up that would prompt me to input the kernel I am running and then set values accordingly. Thanks.
[Samsung Galaxy Nexus] osm0sis:
Cool idea but there's no way to really input anything since it runs in the background and you don't have access to the terminal. A file check of some kind could work but I'm not sure where you could automatically grab what kernel you're running from.
[Samsung Galaxy Nexus] Mevordel:
if cat /proc/version | grep franco
if [ $(cat /proc/version | grep franco | cut -d " " -f 2) -e "#264" ]

First checks if franco, second a specific version. (Note: off the top of my head, so maybe not quite right.)
[Samsung Galaxy Nexus] osm0sis:
A newer member just sent me this via PM. Could work!:

Thanks ohurvitz! Welcome to XDA. Get your posts up in the Q&A section and then come join the discussion here. :)
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I've used the following successfully:

grep -i franco /proc/version > /dev/null

if [ $? = 0 ] ; then

{

command block here

}

fi
[Samsung Galaxy Nexus] osm0sis:
I just tried repackaging JDQ39 stock ramdisk with the franco.Kernel r364 zImage, but sadly it still won't boot. Must be more than just the ramdisk that's changed, keeping it from booting. :(
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Is anyone else having trouble under or over clocking since the app update to 8.6? If I change the max frequency to anything other than whatever the kernel default is, it gets set back to the default value after reboots.
[Samsung Galaxy Nexus] osm0sis:
Nope. I was running 1305 max here without a problem. Clear app data+cache on f.Ku, then reboot. Then try again. :good:
[Samsung Galaxy Nexus] 5pace:
renaud (Developer of Fugu kernel) said this:

So, I guess you know whats the problem now.
[Samsung Galaxy Nexus] ptmax13:
Can anyone help me with this..

I have stock 4.2.1 with franco kernel and stock recovery. Rooted and unlocked bootloader.

Obviously I cannot update via OTA the traditional way...

If I flash the zip of the 4.2.2 OTA update (via custom recovery), will I brick my phone?

If yes, how can I return to stock kernel, so that I can update to 4.2.2? (any links would be great!)

sorry for the noob question....
[Samsung Galaxy Nexus] joaquinf:
Your question isn't kernel related, please post in the proper thread. There is a lot of information out there regarding the OTA update, please be aware of what you are doing and read to be completely sure about you are going to do on your device.

Please help us keep the thread clean.

Thanks
[Samsung Galaxy Nexus] osm0sis:
All your questions have already been answered in the OTA thread over the last couple days, so go have a bit of a read: http://xdaforums.com/showthread.php?t=1419170

And no, you won't brick anything. Read the OTA thread OP so you'll know what you're doing and won't worry. ;)

Ah, that explains why the N7 f.K boots and the GN f.K doesn't; no PVR. Interesting.

Kernel sources dropped today so hopefully Google haven't made it too hard to merge. 4.1 -> 4.2 was a pain in the ass if I recall correctly and Francisco basically had to start from scratch.

While we wait for boss man to do his magic, I've tweaked stock kernel a bit.

Stock apparently has TCP Congestion Avoidance Algorithms now, but only cubic (Linux default) and reno. I switched it to reno for fun. Disabled Content Adaptive Brightness too since I can't do any of my other color tweaks with stock kernel.

Interactive is still the old version, so the original "magic" tunables are still fantastic. Oddly enough Google has disabled input_boost by default, I wonder why.. Anyway for those with poor memories:

60000 / 0 / 65 / 700 MHz / 1 / 45000 / 15000

Our newer tunables also work well, possibly better:

15000 / 0 / 95 / 700 MHz / 1 / 45000 / 15000

Then I switched to deadline from the Google default of cfq. Even though deadline isn't default the default tunables for it have changed. writes_starved is 2, fifo_batch is 16, and front_merges is enabled. malaroth's new values still feel smoother:

350 / 3500 / 6 / 1 / 1

Stock read_ahead_kb is 128, so I tried that at 512 again, but this felt worse. Feels like 128 or 256 is the sweet spot.

No way to set the IO Scheduler tunables on boot with f.Ku or stock (since there's no init.d), but I might try combining Franco's ramdisk with stock zImage later today to see if I can get that to work. Francenstock. ;):p

Edit:

Stock vfs_cache_pressure is 100; LMK minfree is now 8099,10132,12165,14213,16245,20295; adj 0,1,2,4,9,15. Can someone compare those to f.K r364?
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks for figuring out the new deadline figures. Once my rom updates I'll be back at it. But I really prefer to tweak Franco.kernel when he's ready, since that's my daily driver and it doesn't leave him to figure all the numbers out. He's done so much I gotta help where I can

Franco r364
[Samsung Galaxy Nexus] yellowdie:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Hey guys!! Long time, no see! Lol. Good work on the new tunables malaroth (and everyone else).

Just wanted to throw out there that I am running Xylon 4.2.2 and it comes with LeanKernel 5.8.2. So somehow Imo figured out how to get it booting! So hopefully Franco can glean what he needs from there. But dang is this slow! Lol. I am dying for some Franco love here... Lean is so much laggier. Haha. Can't wait until Boss Man has his way with Google's latest!

:) :D :laugh: :good:

EDIT: FAIL!!! I just learned that Xylon20beta is based on a 4.2.1 kernel.... grr.... Still no 4.2.2 there. :/
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Amen to that! As much as I want to try out 4.2.2 it WON'T be with lk. I'll wait. Plus I can see there's already jbsourcery 4.5.x being built and I can't do without fK

Franco r364
[Samsung Galaxy Nexus] Kurre:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

LMK values should be same and those aren't even adjustable anymore since values are hardcoded and dynamically calculated on the fly. IMHO newest lmk implementation works quite nicely :p

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] akash3656:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Osmosis, give this a try,

http://xdaforums.com/showthread.php?t=1933849

People over at Trinity/Rasbean threads usually recommend this if they need init.d support on Trinity/Rasbean combo as this combo doesn't support init.d scripts by default.
[Samsung Galaxy Nexus] osm0sis:
Nah. I already made francenstock. ;)

http://www.sendspace.com/filegroup/SEtis71UnXju7TN4ip0XFQ

It's just stock JDQ39 + franco's ramdisk to enable init.d support. I disabled the part of it that backs up and replaces power.tuna.so though. Made using my Android Image Kitchen. :D
[Samsung Galaxy Nexus] pkgnex:
Can you explain this further or link to a thread that discusses it? Searched and can't find it. I am still setting lmk values via init.d (more aggressive than franco's old values for some parameters). If this doesn't do anything anymore, I'd like to know, and understand the new implementation. Thanks!
[Samsung Galaxy Nexus] Kurre:
well you can set those values, but will it do any good..that's the question ;)

Pikachu01 made some investigation and had big "debate" with zeppelinrox at end of the last year which then turned to a "flameboywar" :D

But anyway, I made my conclusions and I'm using totally stock lmk without any tweaks and it seems to be just fine (some launcher redraws after playing some game, but that isn't really a problem). Newest implementation works imho better than earlier ones (when also franco had his own minfree values etc).

some links if you're interested to read a "little":

Summary by pika

Other post by pika (links to SuperCharger thread -> beginning of debate)

It's little hard to keep up with their conversation (since it seemed to happen in SC and TB threads simultaneously), but it's fun to read and you'll learn a lot if you want to :)

You could also try to search those thread for pika's and zep's posts.

My advice: keep it stock. I'm almost everyday surprised that some app which I have used long time (well this is relative, but anyway) ago, haven't been killed when I'll go back to it (like tapatalk, currents, sms app, browser). So I'd say that it works quite well :D
[Samsung Galaxy Nexus] pkgnex:
Much obliged. Now I've got some reading material for this evening!
[Samsung Galaxy Nexus] franciscofranco:
4.2.2 sources are out. Later when I'm off work I'll merge them and release it. 4.2.2 kernels won't work on older versions due to a new GPU driver that requires a new GPU binary.
[Samsung Galaxy Nexus] aHecticLife:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks franco for the amazing work! :) :thumbup:

Sent from Blah Blah using XDA's Blah Blah Premium App
[Samsung Galaxy Nexus] tetrakinitis:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Give us a little magic! :thumbup:

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] sotoskawasaki:
we cant wait for the magic to happen again... :)
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

New gpu driver = better performance?
[Samsung Galaxy Nexus] whitedragonz83:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Same but I am enjoying such atm except for the colors. Excited to see Franco again on my phone.
[Samsung Galaxy Nexus] lsv-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Can someone tell me please what are the default color settings on r364 (color multipliers) thank you!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] reysonance:
Osm0sis posted it in another thread a while back.
[Samsung Galaxy Nexus] franciscofranco:
Here we go: http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2.2/

boot.img for fastboot and zip for recovery. This is ONLY compatible with 4.2.2, it will bootloop on 4.2.1.

App will be updated later today for all the nexuses, its a long process so until then just download it from here.
[Samsung Galaxy Nexus] osm0sis:
Thanks Francisco! :)

Question: Are the interactive tunables you used ones you prefer to our winners of 15000 / 95 / 729MHz / 45000 / 15000 / 85?
[Samsung Galaxy Nexus] shreddintyres:
looks like they are 30/90/729/45000/30000/80

still feels good but gonna revert back to the winners
[Samsung Galaxy Nexus] franciscofranco:
Yep, I prefer the ones I set. 15ms timer_rate is too low, might jump freqs too easily.
[Samsung Galaxy Nexus] osm0sis:
Yup. Same. I also see read_ahead_kb is 1024. I think our general consensus was 512 felt the best with the optimized deadline + tunables, right?

Ah thanks. Good to know. I think the 15000 is tempered well by the 95% go_hispeed_load we use in the winners, but I understand where you're coming from.

Edit: Comparing them, our winners definitely feel snappier still. ;)
[Samsung Galaxy Nexus] pnut22r:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm relatively new here, can you send me a screen shot of your prefect tunables?

I want to try this "sweet spot" your talking about.
[Samsung Galaxy Nexus] osm0sis:
They're five posts back, and in the order of the Governor Control settings page in franco.Kernel updater (skipping boost, boostpulse_duration and target_slack because they're useless..):

above_hispeed_delay / go_hispeed_load / hispeed_freq / min_sample_time / timer_rate / target_loads

Welcome, and happy tweaking! :D

Actually just switched back to those (but with CAB disabled) myself. On my new panel the f.K defaults look almost perfect, just a tiny bit blue or yellow depending on the level of brightness.
[Samsung Galaxy Nexus] pnut22r:
Re: [KERNEL][GPL][GN] franco.Kerne r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thank you, yeah I saw the values, just didn't know the labels.

Deadline at 512?

Fsync and zram?
[Samsung Galaxy Nexus] osm0sis:
The Galaxy Nexus wouldn't benefit from zram so it isn't in f.K. fsync on if you want data integrity in case of a crash. Read ahead buffer 512.
[Samsung Galaxy Nexus] alexdemonumber3:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Installed r365 over stock unrooted 4.2.2 and wow its buttery smooth. I think I'm just gonna stick to this brilliant setup so I can actually study for once ;)

Great work Franco!
[Samsung Galaxy Nexus] osm0sis:
Hmm.. Francisco, another question: does your GN kernel have the -discard option for the mounts like you recently added on the N7? If not, can we get it? I believe the same sdcard/lag issue afflicts those with the newer GN's/brickbug emmc chips.

Edit: The native OTG mounting would be sweet too. ;)
[Samsung Galaxy Nexus] malaroth:
Still getting bootloop on 365... yes I'm running a test 4.2.2

---------- Post added at 12:57 AM ---------- Previous post was at 12:54 AM ----------

I'm crashing out. Been up 22 hours.. night y'all and thanks for working so quick Franco

---------- Post added at 01:01 AM ---------- Previous post was at 12:57 AM ----------

Last update... rom is still experimental so 4.2.1 kernel only for now. Soon after it's tested I'll flash 365
[Samsung Galaxy Nexus] str8killinya:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Working great so far. Thanks for keeping us up to date

DEVICE: Maguro

ROM: Stock 4.2.2 Rooted

KERNEL: Franco r365

LAUNCHER: Nova Launcher Prime
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

You're phone says it runs 364?

365 runs perfectly on stock 4.2.2. It's the smoothest our gnex can get I think. With all bugfixes by Google it hopefully will be the stablest too.

I thought you switched to stock?
[Samsung Galaxy Nexus] zeppelinrox:
LMKs still work.

Pika however lives in some fantasyland where it's sacrilege for the lowmemorykiller to be more aggressive than the low ass minfrees built into services.jar

Those internal minfrees, on newer devices, don't even come into play on newer devices with lots of ram and with a low hidden app limit - because apps get killed when there's still lots of free ram due to those app limits (normally it's 15 to 20 apps)

I always heard users complain in the past that their apps are still getting killed even tho they have 200mb free ram - it's due to the app limits and not the internal lowmemorykiller.

Of course with my multitasking mods such hidden app limits are removed and the lowmemorykiller now has a chance to actually do what it was made to do.

Users that want to multitask alot, can patch their services.jar to remove the app limits and control free ram with minfrees and OOM grouping fixes.

Despite what pika believes, who btw is about a year late to the party and has never patched services.jar - and therefore speaks out of ignorance, the sky has not fallen and SuperCharging makes multitasking better than ever.

You want to fix your car?

Go to a mechanic and not somebody who once read a book about it - and didn't even understand it.
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I have a feeling it was using memory killer apps and batching the entire concept that leads to conclusions that they don't work. It's like calling tweaking voltages, governor, scheduler, and frequencies overclocking when that only means changing the processor speed.
[Samsung Galaxy Nexus] spupuz:
emh where the hell is the 365 version?
[Samsung Galaxy Nexus] the.emilio:
In the OP, above the other ones, its the link for 4.2.2 :eek:
[Samsung Galaxy Nexus] zeppelinrox:
Off topic but... how the hell are ya man? long time no see lol
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Doing good. I hope all is well on your end. I saw your post and couldn't help myself lol. Memory management is the one thing that is way too variable for an on/off switch so it's good to know there's something there to handle it properly.
[Samsung Galaxy Nexus] Kurre:
Yeah can't really argue with you (I ain't competent enough for that..I just write PHP etc. and compile kernels for fun :p).

At least multitasking mod would benefit all and I should also try it once I have a time for that..Hell, maybe I'll just try SC also :)

I was a SC user for a long time (in SGS it really made a big difference, so I know what it's all about). But my usage pattern with my phone nowadays is quite light (tapatalk and currents mostly and occasionally sms's and some browsing), so I can't say that I multitask a lot. But it's always refreshing to test latest iterations on various stuff/tweaks/etc :)

But all I can say, is that stock lmk works just fine for me. No problems, no excessive killing of background apps etc. Suits for me :) But things could always change for sure.

btw. I do my car's maintenance/services/repair by myself (even the tricky ones too)..and I ain't machanic :p Just by reading a lot and understanding what it means, have always led me to a succesful service (well okay..got my first "car" about 17-18 years ago..when I was about 12-13 yo).

Ps. but now..I think I don't want to clutter Franco's thread anymore, since this isn't really kernel development related.

Pps. I never tryed to be disrespectful or anything towards you..I always try to avoid that, especially when it comes to those who have contributed a lot to this community :)
[Samsung Galaxy Nexus] ayaad:
hi guys i need your help

i flashed franco kernal r365 on paranoid rom today and it has stuck on google logo and its not booting...

any suggestions please...
[Samsung Galaxy Nexus] YamazakiRobert:
the pa is still incompatible with the new 4.2.2 kernels, the pa team need to full update to 4.2.2 build to work the new kernels.
[Samsung Galaxy Nexus] amarinos:
Was one of the first to discover the hard way that 364 on 4.2.2 wil get you stuck on boot...already downloaded 365, will give it a try later this evening ;)
[Samsung Galaxy Nexus] Icecoldmeat:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

ParanoidAndroid is still v4.2.1. R365 is 4.2.2.
[Samsung Galaxy Nexus] rossrogers:
CM 10.1 - 4.2.2 nightly 2/15/2013

CM appears to have merged 4.2.2 stuff in the most recent build, but after flashing franco r365 my gnex is stuck at the google boot logo. My guess it they merged some of 4.2.2 and changed the build to reflect 4.2.2, but that some stuff isn't fully in yet.

So FYI, CM 10.1 - 4.2.2 will not boot with franco 365. (does boot with 364, obviously)
[Samsung Galaxy Nexus] whitedragonz83:
I've been enjoying stock 4.2.2 and if after reflashing Franco's kernel to go back are both of these methods 'equivalent'? (Basically I want an easy transition in a few months to Android 5.0 if it is released and decided to only have a modded Kernel at this point.

1) fastboot flash boot boot.img (from stock factory images)

2) Save Stock Kernel via Franco app, restore it to return to stock

Thanks
[Samsung Galaxy Nexus] Zadeis:
I can confirm this is happening in my experiences also.
[Samsung Galaxy Nexus] jan-willem3:
No the GPU is not as fast as in the S2 everyone knows this. 384 mhz gpu oc doesnt really make a difference at the moment so expect for the future maybe a 20% extra performence boost by various tweaks if we are lucky. Btw this is a kernel thread not a wich phone should I buy thread ...
[Samsung Galaxy Nexus] ro_explorer:
13.1..... nothing off overnight.

// sent from my green robot //
[Samsung Galaxy Nexus] johantheolive:
What seems a little strange is that the graph on mine (uploaded it now in original post) shows two lengths of awake time but looking at betterbatterystats I can't see anything that woke the phone for that long. I was wondering if perhaps I'm undervolting too much and the phone rebooting, but I would see the uptime affected I think. I'm also using the LTE model (I know, this thread is for GSM but it gets much more attention) and my battery is 100mah greater too.

I just noticed something interesting. I was at about 85-86% and plugged in (wall not usb), rebooted and it shows fully charged. Maybe my phone just isn't reporting battery info right...
[Samsung Galaxy Nexus] Simer03:
with that Stability Test app...are u talking about a min of 3 successful RAM runs or the core runs? cuz the core runs take forever...lol!

edit: never mind!
[Samsung Galaxy Nexus] Elganja:
I've noticed the same.... but my battery life hasn't suffered during those "awake" times.
[Samsung Galaxy Nexus] ro_explorer:
If you have the google location services on, those can wake up the device looking for a rough location. It happened to me before.
[Samsung Galaxy Nexus] RyderOCZ:
I went to bed with 70% battery left and I awoke to 66% battery. 8hrs 15min of sleep for me, 1% every 2 hours.

Camera opened then closed right after the flash, as what has been reported several places.

Gtalk signed out and disabled.

DRM content disabled (from AOKP thread)

AOKP 19, Franco 13.1.

I love this phone and Franco for all his hard work :)
[Samsung Galaxy Nexus] bradm23:
Shoot me a pm if you need any testing done... I love testing experimental stuff out...
[Samsung Galaxy Nexus] Simer03:
heres my UV values with this awesome kernel! from 1200 - 350.....1125, 975, 875, 775
[Samsung Galaxy Nexus] psycho2097:
+1 me too.
[Samsung Galaxy Nexus] Sayan1987:
Ehehe great to hear this.

You going to release it public soon?
[Samsung Galaxy Nexus] franciscofranco:
Not yet. I haven't sent it to anyone yet. Trying to find where the voltage of the screen is defined at this moment.