yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cordell12:
Dang! I thought for sure this was gonna do it. Did the code as posted, when it installed and I opened it did the same, black screen then goes back to launcher :( Do I need to do anything to "undo" the code (gain my 1 GB back).

edit...i see i didnt create any partition or anything so I should be OK when I uninstall GTA3.

Thanks for the help.
[Samsung Galaxy Nexus] simms22:
its not that hey have to go in 25mV increments, its that the apps set it that way. some apps use less than 25mV increments to adjust voltage.
[Samsung Galaxy Nexus] darrendm:
Reboot at 1.5GHz (1400mV) while browsing (low usage).

Great otherwise :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
Coolio, so if I set the voltages manually I can set them in whatever increments I want??
[Samsung Galaxy Nexus] simms22:
if the kernel allows for it, yes. you can set 1mv voltages via the terminal/adb or depending on the app used.
[Samsung Galaxy Nexus] dpaine88:
So far on wheatly I'm getting a 1:1 ratio of Max to min speed. Running 700-1500

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ivan08v:
Reboot also on 1.5ghz 1400mv on low usage..seems not a voltage problem..

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] fatappel:
Running r180 with b38 and have no issues what so ever. This is a long shot but if you have the franco app, maybe one of your settings does not play well with r180. For instance, i know hot plug was removed and maybe if you have it enabled from a previous kernel release, it won't boot now with 180. Try clearing the data on the kernel app to wipe your left over settings and attempt to flash again. Again, just a guess.
[Samsung Galaxy Nexus] morfic:
Have you tried turning off SR on MPU?

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] ivan08v:
Let's try it. I was thinking that franco said freqs over 1350 won't be mnaged by SR..

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] psyren:
Are you sure? I thought it was just the GPU that was underclocked, not the CPU.
[Samsung Galaxy Nexus] dpaine88:
I thought the same

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
The CPU is underclocked too, its 1.5ghz out of the factory.
[Samsung Galaxy Nexus] yyz71:
No reboots or problems to report :) I actually think my phones loves to be overclocked!!
[Samsung Galaxy Nexus] Ownatik:
Exactly the same here.
[Samsung Galaxy Nexus] andrew53517:
I believe he said that was impremented for 1.5 ghz. That's why when we adjust the frequencies SR doesn't get involved :)

But I could be wrong too :p

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] do0b:
default value for OMAP4 is 1.0 yea?
[Samsung Galaxy Nexus] sotoskawasaki:
Wow Franco, these are a lot of changes and additions. That's amazing. Should we expect more improvements from linaro?
[Samsung Galaxy Nexus] ivan08v:
I have got another look and it says that "voltages" over 1350mv won't be managed by SR..but the situation of the reboots its like when the phone is softly used it gets undervolted too much for the freq..I'm testing with SR turned off

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] upstandingcitizen:
Constant reboots, 5 per hour.

Imo's exp builds running at 1650 gave me no issues, so I assume it's a bug in the kernel.

Good luck Franco.

BOOM.
[Samsung Galaxy Nexus] galakanokis:
Son. Of. A. Betch! This is fan....ingtastic!

Running like a dream right now. Ran benchmark and temple run for 20 minutes, only hit 59 degrees for a temp on 1500 with 1375 for voltage settings. Everything else is flying. No comment on battery right now as I am far from normal usage.

Much thanks Franco, this is awesome and greatly appreciated.
[Samsung Galaxy Nexus] SupWiz17:
Only have had r180 flashed for a few hours and it's been running great. It's very fast on black ice ROM at 1.5ghz and I have had no reboots yet. The Franco widget doesn't seem to be working but that could be an issue with the ROM. I'm gonna flash cm9 tomorrow and will probably have the fastest phone ever lol.
[Samsung Galaxy Nexus] metalspring:
Liquid is probably the fastest rom out there...at least of all the ones I've run and they might have a new update coming out soon
[Samsung Galaxy Nexus] x-ravin:
1.5ghz messed me up to the point that I'll have to wipe and reflash to get most of my apps working again. I should note my phone hasn't taken well to overclocking beyond 1.3 so this isn't the fault of the kernel. Just warning anyone else who may have a finicky device.
[Samsung Galaxy Nexus] superbobup:
Did a very unscientific, basic test for music with wheatley.

After 30mins of STREAMING music via Google Music over H+ I lost ~3%, with sync on and about 30s screen time at Max brightness

I'll try to post on this as I do more listens at shorter and longer intervals
[Samsung Galaxy Nexus] franciscofranco:
SR skips calibration for the 1.536Ghz step so might've been some weird issue. The reboot dmesg log (which no one provided by the way) gave me a MPU watchdog reset.
[Samsung Galaxy Nexus] jameslfc5:
Sorry to be lazy but if I flash 7.1 is the GTA game working yet?

Cheers
[Samsung Galaxy Nexus] zephiK:
Yes it'll work read #7 change logs.
[Samsung Galaxy Nexus] jameslfc5:
Cheers! Didn't think to read all them sorry! :D

ps, how do you find the battery?
[Samsung Galaxy Nexus] fiftyclick:
Read the last 4 pages -- it is great. lol
[Samsung Galaxy Nexus] zephiK:
Er I meant nightly #6 but you get the point :p
[Samsung Galaxy Nexus] dario3040:
happy new year!!!!!!!!

2012
[Samsung Galaxy Nexus] belair56:
Yes, runs super. All stk settings.
[Samsung Galaxy Nexus] franciscofranco:
Happy new year everyone. Tomorrow the source code is updated and a new release is also out with a few fixes and polishes.
[Samsung Galaxy Nexus] yyz71:
Happy new year y'all :)
[Samsung Galaxy Nexus] Vangelis13:
Happy New Year Francisco! Good health & happiness. Thank you for all the hard work that you do for us, much appreciated!!
[Samsung Galaxy Nexus] Redflea:
Start the new year off right!

Thanks, and happy new year.
[Samsung Galaxy Nexus] yeeson:
happy new year！！
[Samsung Galaxy Nexus] mohitrocks:
This kernel + AOKP = Pure awesomeness. :D

Pretty much the best performance I've ever had on any device as of yet.

Thanks so much for your continued effort :)

Happy new year everyone!
[Samsung Galaxy Nexus] yohinomura:
Happy new year
[Samsung Galaxy Nexus] sishgupta:
I've been running AOKP with Franco's 7.1 and its amazing.

Thank you for your hard work.
[Samsung Galaxy Nexus] jknisley:
I'm really curious what settings you're using for set_cpu. I'm getting great performance, but all of those incredible battery life that everyone has makes me feel left out. At least 4%/hour, and that's after killing my over-alarmed clock widget. That's an enormous improvement from the 25%/3hrs and no deep sleep I was getting before this kernel and a few changes I made.

Then again, I'm on the LTE phone and I hear that it gets laughably worse battery life.
[Samsung Galaxy Nexus] Trongable:
First off, thanks Francisco for the awesome kernel!

Secondly, has anyone been running this kernel exclusively on the Interactive governor? How's the battery life on that gov? Is it a noticeable difference from ondemand?

The reason I ask is that the ondemand governor can be a little slow to ramp up for me sometimes. Thanks.
[Samsung Galaxy Nexus] PanBongo:
First of all I would like to thanks franco for his effort to bring this phone to holy perfection. Second I would like to know how could you be possible, some of you, to get 5% battery per night, that was with data off, airplane mode or what? :D Coz I got 25% down for 8 hours at night, wifi and gmail sync online.. In battery report the second after display was "standby". I noticed that Gmail notification may be preventing phone from deep sleep, coz I had some new emails when woke up. So what possibly could I have done wrong?

ps: wish all of you successful year 2012 ;)
[Samsung Galaxy Nexus] raimondomartire:
Also in 7.1 I must delete /system/lib/egl/libGLES_android.so ?
[Samsung Galaxy Nexus] skdubg:
no its not needed again
[Samsung Galaxy Nexus] Lambetts:
Thanks for your reply man.

Ok, well, I've experimented with it off and on and I could be wrong here but I don't see a massive increase in performance. Having the option to change it would be great. Just IMO....

Seen a few users now that have mentioned this also.

Thanks guys.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
So you want a dmesg log of a reboot from running 1.5 GHz? Would the last kmesg work too?

I'm still not entirely sure what exactly the kmesg is, I'm used to my old Droid 1 where all there was were logcat and dmesg
[Samsung Galaxy Nexus] ivan08v:
On my "SR off test" I had two reboots under 1350mv, and 1375mv. Listening music and using tapatalk. I keep believing is other than the voltages :)

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
/proc/last_kmsg is dmesg.
[Samsung Galaxy Nexus] nodstuff:
Tested with SR on at 1420mv and had a reboot

Testing now with SR off at same voltages and no reboot yet.

Antutu benchmarks, video, 5 races on different tracks in Riptide and browsing the internet.

Still no reboots.

With SR on before when I loaded a new track on riptide it would freeze.

Maybe its just luck but maybe its worth looking at.

Edit: bumped it down to 1400mv with SR off and still no reboot.
[Samsung Galaxy Nexus] morfic:
What's the lowest you tried, and what is the core voltage at?

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] Gahh Its Lee:
At 1450 I can run 1.5 with no issues zero reboots no heat issues. Seems golden so far.
[Samsung Galaxy Nexus] ivan08v:
The lowest I tried is 1350mv and core voltage is at 1250mv for 384/512 mhz

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] mert2go:
Thank you so much Franco! Nightly 180 is a beast never seen my Nexus so fast! 1.5GHz runs perfect without any issues. Thank you again!

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
SR off at 1400mv reboot, I was browsing XDA.

Here is the dmesg.

http://db.tt/zyYYx5ST
[Samsung Galaxy Nexus] morfic:
After the next reboot type the following in terminal and email it to Franco:

cp /proc/last_kmsg /sdcard/last_kmsg.txt

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] neverhappy:
r180: had 3 SOD's in about 2 hrs after I initial adjusted to 729 min and 1536max. Adjusted all voltages +25mv and no SOD's or reboots for about 3 hrs now. will monitor. GNEX LTE CMPLX BLACK ADV4, 729 min 1536 max, GPU 512.
[Samsung Galaxy Nexus] jnr21:
Wheatley and 1,5ghz@1400mv running great on my gnex, no reboots while playing/running stability tests. Now i'm going to test battery life, i will report more later.

Thanks franco, i really appreciate your work!
[Samsung Galaxy Nexus] arzbhatia:
r180 - @1536/384 Mhz - Ondemand - Custom undervolt values - No reboots, no heatups, perfect battery life.

Nice work francs.
[Samsung Galaxy Nexus] Diger36:
Experienced no more freezes or reeboots after setting the 1536 Mhz slot at 1425mV. Now solid as a rock. Getting warm sometimes but not too hot :D

Looking good for now!
[Samsung Galaxy Nexus] 15israellai:
Decided to jump on the nightly bandwagon, and now 1536MHz + 512MHz is running smooth as hell! Wow I never knew my CPU could stand that. thanks, Franco!

Next off, I'll probably try UV.

Blazing on my Nexus Prime using xda premium
[Samsung Galaxy Nexus] metalspring:
I'm thinking one of these patches or something in the Wheatley governor is causing the random reboots or a combination of these...

I just switched back to interactive and lowered the 1.5 slot back down to 1400mv and no reboots

With Wheatley I had 1450 mv for 1.5GHz and still got the occasional reboot when using light resources (tapatalk app or friendcaster app)
[Samsung Galaxy Nexus] digweed4me:
Nightly 180 is the best man super fast faster than my Samsung epic touch running 1536 /729 and default voltage.thanks a lot Franco u are just amazing.

Here is the quadrant
[Samsung Galaxy Nexus] metalspring:
All galaxy nexus's should be able to handle 1.5 GHz, all that might have to change would be the voltage (complete stock voltage for whatever they would have had for 1.5 at worst case)

The stock CPU speed is actually 1.5GHz, it was just underclocked by Samsung/Google

Same with gpu, 384 is the real stock speed but was underclocked to 308 by Samsung/Google
[Samsung Galaxy Nexus] brockmo:
I thought this was a very good educated guess. Just tried it and no dice. So odd. At least there are others with this issue. With all the updates I was looking forward to this one too. So strange... completely at a loss for what else I can try.
[Samsung Galaxy Nexus] icbt:
I have just got a strange issue on my phone

After I used the updater to auto flash r180 from r175

My screen turn very dark

Eventually, I found out that my color multipliers turned the rgb values all into 431!!

I fixed it when I was changing it back to normal.

I haven't change my rom or kernel for a long time

I thought that it might be a bug in kernel or the updater.

Hope the post would help u Franco :)

PS: I am using the LS 1.4

and have read recent 20 pages of this topic and never seen such issue
[Samsung Galaxy Nexus] johno168:
Well maybe you should read again, cause it has been discussed, franco has also updated his app twice adressing this bug. If the problem still persists re-install the app again
[Samsung Galaxy Nexus] zammbi:
Sent off a couple of crash reports. Seems the kernel updater is getting null pointer crashes when trying to download.
[Samsung Galaxy Nexus] The Gingerbread Man:
Well thats 4 of us so far, 2 cm9 nightly, 1 akop and 1 stock sprint rom.

I tried this thanks for your advice unfortunately didn't work. I fully backed up all my apps with titanium backup and reported to recovery and did a nandroid, rebooted, went to titanium wiped the Franco kernel app data then went to settings/apps/downloads/Franco kernel app and force stopped and made sure there was no data or cache. Reboot to recovery and flash 180 and hung at Google screen.

I then pulled battery boot to recovery, advance restore m4 from my nandroid and all is good again.

Sent with a shake
[Samsung Galaxy Nexus] jnr21:
Quadtrant score doesn't mean nothing. I have 729-1536 freqs, wheatley gov, 512mhz gpu, guadrant gives under 2000 points but my gnex is still super smooth on games and ui.
[Samsung Galaxy Nexus] SrTapir:
When I install a new version of the kernel I always wipe the previous kelrnel data via the "Preparation for installing kernels" script of Ezekeel, it saved me of some problems I used to have after several updates and installs.

http://xdaforums.com/showthread.php?t=1437633
[Samsung Galaxy Nexus] schizophrenia:
that's strange.

i had 192-1536 wheatley gov 512mhz gpu and AOKP and quadrant gave me 3.7k

it went up to 3.9k when I switched to interactive
[Samsung Galaxy Nexus] ado7980:
Hi, I using v180 on MIUI Rom 2.6.1 and have a one problem. In 3D games always freezing pictures with random cubics default. Its problem of 512GPU? Because with other kernel with stock 384GPU a havent this problem. With Milestone4 is all super but missing 1536Mhz slot :) Can you make version 180 with stock 384GPU please? Sorry for my english :)
[Samsung Galaxy Nexus] metalspring:
You probably don't have force gpu rendering checked under developer options...it adds A LOT to benchmark scores, especially quadrant... Make sure it's checked and try again and you should get at least 3500 or around there
[Samsung Galaxy Nexus] metalspring:
There is a 384 gpu one...
[Samsung Galaxy Nexus] rogersnm:
180 is available with 384GPU, either via the app or here: http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/gpu_384mhz/franco.Kernel-r180.zip
[Samsung Galaxy Nexus] ado7980:
About Phone-Kernel version: 3.0.8francoKernel-nightly-512GPU....

What is this??? 512GPU or 384GPU
[Samsung Galaxy Nexus] jnr21:
Yes, it's strange but i don't need to worry as long as everything is smooth and fast.
[Samsung Galaxy Nexus] joeyfong:
Who care about benchmark
[Samsung Galaxy Nexus] The Gingerbread Man:
Didn't work either. I'm just gonna wait till next one and try again. Thanks for help guys

Sent with a shake
[Samsung Galaxy Nexus] The Gingerbread Man:
You installed the 512 gpu version

Sent with a shake
[Samsung Galaxy Nexus] despard:
just had a reboot using 1536mHz slot.

http://db.tt/O0hJIpM0

Hope you've got some time to look at it:)

Thx Franco
[Samsung Galaxy Nexus] jnr21:
I agree.
[Samsung Galaxy Nexus] rogersnm:
192-1536 MHz with 1375 mV max voltage seems to be stable with the interactive governor (10 Antutus and 5 Quadrants + 1 hour idle home screen). Looks like there is a bug with the wheatley governor that causes the system reset.
[Samsung Galaxy Nexus] Benji1983:
is this question really serious from you ???

^^

greetz benji
[Samsung Galaxy Nexus] gnlcp:
Guys, I still have problems with Franco Kernel Uptader app... It doesn't save my settings of governor and clock on every reboot.. Is it a common problem? Is there any fix for it?
[Samsung Galaxy Nexus] The Gingerbread Man:
If your using cm9 I don't think it works, you need to use set on boot in settings/performance/processor/set on boot after setting up what ever you wanted to use

Sent with a shake
[Samsung Galaxy Nexus] provolinoo:
Anyone tested latest kernel nightly 180 with cm9 nightly 20120605? Does it work?
[Samsung Galaxy Nexus] Reviz:
just for report

SlimICS 3.9 + franco r180

no issues
[Samsung Galaxy Nexus] Meannekes:
So close.. 1344cpu 384gpu
[Samsung Galaxy Nexus] jnr21:
Cm9 issue. Set on boot via cm9 performance settings.
[Samsung Galaxy Nexus] gnlcp:
I'm using latest AOKP.. so I'll do what u suggested me to do.. really thank u man
[Samsung Galaxy Nexus] jnr21:
Battery life looks good with r180 (weathley, 729mhz-1,5ghz). 3h 20min screen on and 44% left.
[Samsung Galaxy Nexus] rogersnm:
Franco, could you increase the thermal throttle from 64C to something like 75C? My phone hits 64C with just slow web browsing.
[Samsung Galaxy Nexus] Diger36:
Just had a spontanious reboot.

Logcat : http://dl.dropbox.com/u/10712738/logcat.txt

last_kmsg : http://dl.dropbox.com/u/10712738/last_kmsg

r180 192 Mhz-1536 Mhz (the last at 1425mV) Wheatly

Going to try 1450mV now.
[Samsung Galaxy Nexus] rogersnm:
You've got the same error message as everyone else:

Last reset was MPU Watchdog Timer reset (PRM_RSTST=0x8)

You'd be better off trying another governor at a lower voltage.
[Samsung Galaxy Nexus] dracon6ai:
Well after my last post yesterday my phone rebooted after I turned the screen off (700-1500 wheatly 1425mv). I got stuck in a never ending boot loop. Had to wipe and reload. After I got everything loaded I set it to 700-1500 wheatly 1450 and it rebooted while I was adjusting some ringtones back. Got stuck again in a boot loop. Rewiped and reloaded everything again and chilling at 700-1300 wheatly for now. That Fsync file corrupt issue doesn't like me today.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] Diger36:
I understand that but isn't the purpose of those nightlies to test and to gather data so Francisco can optimse them? My phone ran good for 16 hrs on these settings so I'll give it another shot. I don't mind an occasional reboot if on the horizon is more awesomeness waiting for us ;):D
[Samsung Galaxy Nexus] L-ViZ:
nightly 180 working well? wanna try it with clean install of aokp b38.
[Samsung Galaxy Nexus] rogersnm:
Everyone seems to be testing the new 1.5 GHz frequency with the wheatley governor however far fewer appear to be testing it with another governor. Given that many have reported reboots with a variety of voltages on the wheatley governor it would be useful for people to test either lower freqs on that governor or the same frequencies on different governors so that the problem can be narrowed down.
[Samsung Galaxy Nexus] bongostl:
Hey all...2qs

1. What kind of mpu tennis are you sering at 1500? I'm hitting the low 70s...

2. What is the acceptable range for this temp? at what point is it dangerous (to the phone)?
[Samsung Galaxy Nexus] rogersnm:
#define TSHUT_THRESHOLD_TSHUT_HOT	110000	/* 110 deg C */
#define TSHUT_THRESHOLD_TSHUT_COLD	100000	/* 100 deg C */
#define BGAP_THRESHOLD_T_HOT	75000	/* 75 deg C */
#define BGAP_THRESHOLD_T_COLD	70000	/* 70 deg C */

The CPU begins to throttle back once the temp is more than 75C, but it won't shut down until it's 110C. Obviously ideally the temp should be as low as possible, however temps <100 shouldn't cause permanent damage.
[Samsung Galaxy Nexus] bongostl:
I'm now up near 80....do nothing too worry about? (thanks! )
[Samsung Galaxy Nexus] opethrocks:
Ive been using wheatley govenor at 1344mhz since last night and ive had 0 reboots since. I initially tried wheatley at 1.5ghz with voltage at 1375, 1400, 1425 and 1450 all eventually random reboot, and the reboot only happened while doing light duty tasks like texting, it did fine with benchmarking and stress tests
[Samsung Galaxy Nexus] rogersnm:
Your CPU frequency and voltage will drop as the processor tries to give itself time to cool off, but it won't cause any damage.
[Samsung Galaxy Nexus] Hanny:
everytime when you test a new (higher) cpu freq or gov, uncheck set cpu settings on boot for at least 24 hours stable uptime. that saves you the time cleaning up bootloop ****s, as it wont bootloop anymore. :)

@franco please add me into the positive results list:

no reboots for 18 hours wheatly gov 1536mhz default voltage 1400mv :cool: thanks lots. as seen in previous post i will try to monitor more on the actual battery change while wheatly uses highest freq when music is playing. maybe the theory of "using 1536 all the time but not wasting battery" is true. waiting on more opinions for that :)
[Samsung Galaxy Nexus] franciscofranco:
Device throttles at 75C, I already changed it long ago.
[Samsung Galaxy Nexus] rogersnm:
My ctrl+f let me down :(

Cheers :D

Are the values not defined in this file then: https://bitbucket.org/franciscofran.../388ae9aa9b26/drivers/misc/omap_temp_sensor.c

[lines 61-64]

Edit: Ah it's committed to a different branch
[Samsung Galaxy Nexus] Diger36:
True... Will do :-)
[Samsung Galaxy Nexus] ssglackey:
+1

I had 3rd reboot today on 1,5 wheatley during low usage.
[Samsung Galaxy Nexus] Meaple:
So far so good with the latest nightly. 1375mV for 1536MHz. Runs fine in high and low usage. No reboots as yet.
[Samsung Galaxy Nexus] xinos:
No problem whatsoever using wheatley 192-1536. Tested using a few benchmarkers and stabilitytest from market, and of course just daily usage (gaming whatsapp mail etc.)
[Samsung Galaxy Nexus] opethrocks:
Lucky. What do you guys have maximum screen off freq set at? Default 729? Because from what ive read its better to not limit screen off freq when using wheatley
[Samsung Galaxy Nexus] Meaple:
I put it to 192 for screen off. I'm just testing it out properly to see what's best. Will check battery in a few hours. If battery is being ragged then I will change to default again. I'm also going through my voltages since I've not properly been through them yet.
[Samsung Galaxy Nexus] Misledz:
Doesn't the WiFi stop working if you put it to 192? I don't know if that's been rectified but the 5 other phones I own have the issue of a deep sleep with 192. Then again milestone 5 tends to have a nice bump up in response time compared to the little jitter I used to get for tapping the multi task button.
[Samsung Galaxy Nexus] franciscofranco:
Yep I work on the exp branch.
[Samsung Galaxy Nexus] vomer:
Hey franco are you planning on implementing that cool improvement someone point out earier in the thread? I remember it was a YouTube video :p

edit: this one: http://xdaforums.com/showthread.php?p=26968509#post26968509
[Samsung Galaxy Nexus] Meaple:
WiFi is fine for me. Think it was a little jittery in previous two nightlies but r180 has been fine with WiFi. No major issues at all.
[Samsung Galaxy Nexus] franciscofranco:
Linaro improvements = userspace.

franco.Kernel = kernelspace.