yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] reaper000:
Jeez, Boss... You can take a break on Christmas eve!

I think I speak for pretty much everyone here when I say that even if people are posting their bugs/issues with the kernel through Christmas, there aren't any expectations. Enjoy the holiday!

Your work here is much appreciated, and I hope you have a Merry Christmas
[Samsung Galaxy Nexus] franciscofranco:
My christmas eve is over, back to enjoying Android :)
[Samsung Galaxy Nexus] shawnaye:
:cool::cool::cool:
[Samsung Galaxy Nexus] aimcr7:
Just tried it, and after several minutes after initial boot that weird slowdown happen, dont know whats wrong. But i have to pull my battery out to stop it. Cant get last kmsg :confused:
[Samsung Galaxy Nexus] franciscofranco:
What do you mean by slowdown? I don't have such thing.
[Samsung Galaxy Nexus] copi:
me too experience slow down,, its like when u having ram is full and its sluggish everywhere then have to battery pull..

edit : i'm at r350 btw
[Samsung Galaxy Nexus] Wynnded:
I've loaded up 351 too and I'll post if I have issues again. Thanks for putting that together for us on this holiday.

Sent from my Galaxy
[Samsung Galaxy Nexus] franciscofranco:
I just went through all the patches and I didn't see what could be causing that. How do I reproduce it?
[Samsung Galaxy Nexus] osm0sis:
Since you seem to be able to reproduce it pretty readily with r350, try rebooting while it's still sluggish (but before it freezes). Then upload your /proc/last_kmsg. :good:

Same goes for anyone who's able to reliably reproduce it. Only way to get a good last_kmsg is to catch it and reboot just before a battery pull is required. A logcat while it's severely sluggish would be nice too.

THEN try r351. :)
[Samsung Galaxy Nexus] franciscofranco:
Try r351 please.
[Samsung Galaxy Nexus] franciscofranco:
Whats your experience with r350? I can't seem to reproduce any problem (as usual) :(
[Samsung Galaxy Nexus] galakanokis:
The slow down I experienced on the initial flash of 350 saw the phone just reacting very slowly to commands. It could take 30 seconds to a minute for the launcher to turn a page. A reboot took almost 5 minutes to close down the screen. I did only get that once right after the first boot. I did however get a number of SOD's on 350.

Just flashed the test kernel and will report any findings. I will say that 350 felt very nice when it was running.
[Samsung Galaxy Nexus] osm0sis:
Honestly no problems yet. :fingers-crossed::confused:

Hopefully people can provide some useful logs.
[Samsung Galaxy Nexus] Wynnded:
When it happened to me, I was trying to open an app and that was it. Since then I've been trying to get it to happen again by using the crap out of it while letting it sleep for short periods in between. It'll get sorted at some point, we just need to be patient.

Sent from my Galaxy
[Samsung Galaxy Nexus] anshulajain:
Just an update- I did a full wipe and re-installed rasbeanjelly (latest) and then flashed franco's 350 kernel. Haven't faced a problem again...will test Google Maps Navigation to try and reproduce the error.
[Samsung Galaxy Nexus] The Gingerbread Man:
So flashed 350 last night all was OK through out the night, charged up as normal over night, no sod. I did how ever after reading tapatalk experience that extreme lag being mentioned, the phone is basicly unusable and I want able to reboot it it just had frozen up completely. The launcher took ages to turn page, my wall paper kept disappearing and just turning 100% black. If it happens again I'll try adb reboot and grab lastkmsg. Gonna try 351 now.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] marshy73:
Flashed 351 and on Minco 6.

Was using the phone as per normal and after 15 mins, suddenly phone slowed down terribly as mentioned by others. Scrolling is like 3 secs to turn a page. Quickly tried to do a reboot to get good logs but SOD the moment i activated reboot. In the end had to pull batt. Will try stay on 351 to try to get log again for Franco.

Edit Addon:

Encountered an autoboot.

No slowdown prior to auto boot.

Here's the log.

Please remove the .txt extension.
[Samsung Galaxy Nexus] _chanstar_:
All is good here. Stupid fast and smooth!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gianton:
r350 is working great on AOKP 1223 Roman build, no SODs or freezes. I noticed stronger WiFi signal with r350, are the drivers updated?

Thanks Franco!

Merry Christmas everyone!!

N4 order placed, it'll be my New Year's present, lol!
[Samsung Galaxy Nexus] llevo3:
no problems with r350, 384/1305, no UV, interactive/deadline/westwood, max screen off 537, hf 1036/ibf 729
[Samsung Galaxy Nexus] lesp4ul:
I noticed prob with v350 if you applied 348 UV settings, prob like super sudden sluggish, freezes when you applied it. Now i test 350 192/1036, max off 384, interactive, bfq with no UV for 5 hours. No freeze and a slight lag only.
[Samsung Galaxy Nexus] gianton:
On r350 while using Tapatalk the device became very laggy and finally had to pull the battery out. I was using osm0sis UV settings.

Will try r350 with default settings now.
[Samsung Galaxy Nexus] mrm43:
I too had this slow down. Everything just crawls. Unresponsive. Had to do battery pull.
[Samsung Galaxy Nexus] gencka:
Also I same. +1
[Samsung Galaxy Nexus] mrm43:
Tried to reboot while slow down is happening. Even the reboot process suffers slow down. I waited almost 30 minutes for the "please wait rebooting..." process but it just sits there. Had to do battery pull.

Will wait for feedbacks for 351 before I flash it. Thanks.
[Samsung Galaxy Nexus] Wynnded:
This was my experience with 351 as well. What I'm going to try this time is the next time it slows, I'm just going to let it sit and see if it will recover on its own.

Sent from my Galaxy
[Samsung Galaxy Nexus] aimcr7:
Had exactly the same as you describe with 350 and 351, now i am back to 348
[Samsung Galaxy Nexus] Langduscher:
Just flashed r351: 3 random freezes/ reboots just after booting up. Now it seems fine.

/proc/last_kmsg attached

edit: how do I upload /proc/last_kmsg.txt from phone when on stock browser? Can't seem to attach files there...
[Samsung Galaxy Nexus] irminsul:
So after the good start I've also got those strange slow downs on r351. As stated above you can wait minutes and minutes for the phone to reboot but it won't so no logs

I've used R350 only this night when I was asleep.

I'm using 384/1536 with stock voltages and the interactive governor.
[Samsung Galaxy Nexus] smileyanz:
I've been fine on 350 nothing what so ever , mind you I've only browsed and played a few games etc..and messed around with colours, max1305, min384, on unofficial
[Samsung Galaxy Nexus] jcoleridge:
Now trying 351, thanks! Just a question: is it just me or the option for input_boost_freq in interactive governor control is not present in 351?
[Samsung Galaxy Nexus] allgsmnetwork:
My experience with 350 negative at 192/1536...348 good :( blocked device and not restart manually...seem voltage 348...
[Samsung Galaxy Nexus] Khizar:
when settings voltages on r351 the phone frooze and rebooted, i also heard a pop before the reboot.. after the reboot i set the same voltages and this time no reboot,and everything seems fine
[Samsung Galaxy Nexus] gianton:
R352 (351.zip) with default voltages at 384/1536MHz seem stable so far.
[Samsung Galaxy Nexus] franciscofranco:
Ok few things that are kinda fishy for me. People that are having the so called slowness answer this:

1 - are you undervolting?

2 - are you using a task killer?
[Samsung Galaxy Nexus] anshulajain:
Nope...no task killers or under volting here.
[Samsung Galaxy Nexus] Stretlow:
Makes perfect sense

---------- Post added at 08:41 AM ---------- Previous post was at 08:38 AM ----------

Because some people need to get longer between charges, mine has been doing it. What I'll do is stick it on max and use it as i normally would at work.

Pretty sure it won't last until i get home tonight, will report back
[Samsung Galaxy Nexus] marc.tulley:
Hey Franco,

Just more positive feedback from me again. While trying to solve my faulty proximity sensor I flashed back to stock to see if it was anything to do with rom / kernel. I never noticed because I've been with your kernel since pre-knightly 1 but it is phenomenal how much quicker and responsive everything has become!

Thanks again mate.

PS still bug less for me and don't notice any wake lag worth worrying about.

PPS bring on v.13!
[Samsung Galaxy Nexus] goan0900:
What App do you mean? Is it your Kernel Updater or a different App? Is it possible to get your Updater also to androidpit?

Thanks
[Samsung Galaxy Nexus] MarcLandis:
The next Kernel Updater App will be available on AndroidPit.
[Samsung Galaxy Nexus] cjones1348:
Wow, you sir are a scholar and a gentleman......
[Samsung Galaxy Nexus] Stretlow:
Mid day update with the newly found lag problem, every single bit of lag (mostly waking and unlocking) has disapeared as a result of turning the autobrightness off.

The lagging problem is 100% due to the autobrightness....

Trialing it on max as per Franco.. Not doing too bad but no way I could have it on all the time

5 hours on the battery, 1hour 18 minutes on screen 51% remaining.

Stret
[Samsung Galaxy Nexus] franciscofranco:
Nightly's #13 and app update are up. Big changes around, need a lot of feedback.
[Samsung Galaxy Nexus] madmak:
Was waiting eagerly for this. Bought your app as a small token of appreciation. keep up the good work
[Samsung Galaxy Nexus] GchildT:
Sweet!

10char
[Samsung Galaxy Nexus] OneOfaKindDPC:
is 13 still based off of 3.0.16?

thanks for doing what you do!
[Samsung Galaxy Nexus] Felixpau86:
Franco what are your previous voltage or recommended settings?
[Samsung Galaxy Nexus] superbobup:
Hi Franco

Any chance of your app supporting non-standard DPI value :)? I always need to change from 241 to 320 if I ever want to update it via market
[Samsung Galaxy Nexus] Nebucatnetzer:
Did you add a limit for undervolting? Or can we go as far as our phone is capable.
[Samsung Galaxy Nexus] jan-willem3:
First stuff I noticed better data and wifi speeds and smoother animations.
[Samsung Galaxy Nexus] darrendm:
Tried lots of kernels but keep coming back to this one!

Finally will settle down with kernel now and have just bought your app to show some support!

Thanks for all the hard work you spend doing these bro
[Samsung Galaxy Nexus] franciscofranco:
There is a limit that is imposed in the kernel source via dependencies. This is to prevent collateral damage.

Quoting myself from Google+ to prevent repetition in the next pages:
[Samsung Galaxy Nexus] zephiK:
Has nothing to do with his app. This is a known bug with DPI switching. You have to pay $0.99 for his LCD Density app or do the market fix (find it on XDA).
[Samsung Galaxy Nexus] franciscofranco:
Yes, nothing new from 3.0.17, no need to update.

My recommended values for stability are what it is set by default.
[Samsung Galaxy Nexus] DJTaurus:
Wow i love cold colours in build 13.... yellowish effect has gone for sure... no need for brightness fix.

Sent from my blazing fast Galaxy Nexus!
[Samsung Galaxy Nexus] Vangelis13:
Default governor is performance..? That's what the app started on after updating.
[Samsung Galaxy Nexus] johno168:
Nope. Nothing like that. It was twice for me. Just randomly.
[Samsung Galaxy Nexus] Wynnded:
In my case, neither as I know that would just muddy things. No changes to the kernel, just running it as flashed.

I'm using a ROM called "Shiny" over on RootzWiki. It's very untainted and stable.

Sent from my Galaxy
[Samsung Galaxy Nexus] allgsmnetwork:
Yes i using application assistant 18 functions and setting UV...
[Samsung Galaxy Nexus] aimcr7:
1. Yes, but the same settings as 348 which is pretty stable for me. No single reboot on 348.

2. No.
[Samsung Galaxy Nexus] marshy73:
I was on 348 but I disabled voltages on boot prior to flashing 351.

No task killers.
[Samsung Galaxy Nexus] franciscofranco:
I just managed to reproduce it and it spams dmesg with this

<3>[ 8275.967376] [MIPI-HSI] ch=0, hsi_write_done timeout : 4

<7>[ 8275.967559] [HSI]00000000: 41 54 41 54 ATAT

<3>[ 8275.967864] omap_hsi omap_hsi.0: hsi_write_cancel ch 0

<3>[ 8275.968048] omap_hsi omap_hsi.0: __hsi_write_cancel : 0

<3>[ 8275.968322] [MIPI-HSI] write fail : -110

<6>[ 8275.968597] [MODEM_IF] misc_release : umts_boot0

<3>[ 8275.968780] omap_hsi omap_hsi.0: hsi_write_cancel ch 0

<3>[ 8275.968933] omap_hsi omap_hsi.0: __hsi_write_cancel : -61

<3>[ 8275.969116] omap_hsi omap_hsi.0: hsi_read_cancel ch 0

<3>[ 8275.969390] omap_hsi omap_hsi.0: __hsi_read_cancel : -125

<3>[ 8275.969573] omap_hsi omap_hsi.0: __hsi_write_cancel : -61

<3>[ 8275.969848] omap_hsi omap_hsi.0: __hsi_read_cancel : -61

I have no idea what that is, but I'm looking.

EDIT: logcat is also spammed with **** about RILD... the **** is happening...
[Samsung Galaxy Nexus] Langduscher:
Just had a major slowdown on r351 after half an hour of use. No taskmanarer/ -killer nor UV here. Rebooting to get you /last_ksmg but phone has been trying to reboot for 20 minutes now :D
[Samsung Galaxy Nexus] Controvrsy046:
R350 has frozen 3 times on me and one time slowed down literally into slow motion where key presses got backed up and the phone implemented the screen touches one by one over a period of 45 seconds. It was a trip to say the least.

When it is running it runs very smooth though.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tobitronics:
Reading all these stories I understand that I should stay with 348 for now?
[Samsung Galaxy Nexus] Wynnded:
Finally, now I can go to bed.

Thanks huge for staying up so late to look into this for us Franco, major props man.

Sent from my Galaxy
[Samsung Galaxy Nexus] GrijzeGeest:
No not undervolting, default setting

Yes using go-taskmanager

Further:

- set tcp congestion to westwood

- using Antutu CPU master pro for CPU settings
[Samsung Galaxy Nexus] franciscofranco:
Users with problems, please test this one:

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/tests/franco.Kernel-nightly-test-r354.zip

Feedback appreciated before I go to sleep.
[Samsung Galaxy Nexus] prembox:
Honestly, it's been 5hrs20 mins since I've flashed R350....seen no lag or slowness or experienced SODs at all....dunno wtf is goin on.....got at least 20 whatsapp msgs...lots of gtalk....played Angry Birds 7 sub-levels within a level....Exchange synch at Auto(Push)....posted 2 pics on FB... and yeah....received 2 and made 4 calls.....nothing funny happened ....phone a lil more smoother IMHO from R348....and I don't mess with Voltages etc....except that it is OC'd at 1536 with min @ 384Mhz

Edit: Looks like I just got plain lucky today....just read Franco's post...
[Samsung Galaxy Nexus] The Gingerbread Man:
Only 192 slot at 750 and no

On 351 I had the same freezes. Try reproduce it with camera, I was taking some Xmas pics and had it. Seems to be with CPU intensive tasks. Enjoy your Xmas day and have a days break :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] smileyanz:
Gingerbread this is to me as good as I've had from Franco, am well chuffed. Happy Christmas to all and of cause FRANKO.
[Samsung Galaxy Nexus] bunnahabhain:
I dont know if it was discussed earlier, but any chances to incorporate the latest interactive patches in r300?
[Samsung Galaxy Nexus] Langduscher:
Testing r354 now :good:
[Samsung Galaxy Nexus] AndyGnex:
Hmm..not doing any UVs or using task manager (why would ppl use it on android i dont even understand wtfffffff)

Im on 250, first i had a slowdown that everyone mentions..it doesnt freeze, just SLOW, REALLY SLOW..

I rebooted,cleared fku data, and everything was smooth for 2hrs, then suddenly...wait for it.... SoD...

Back on 248 and gonna wait for concrete feedback before going on the next nightly..i promise i wont use any other kernel in the mean time..my phone only likes francos kernel..every other kernel stutters like a retard.

delivered by FedEx
[Samsung Galaxy Nexus] lesp4ul:
1. yes at first, using my previous 348 UV setup and the phone became crazy. Tried with192/1036 max off 348, interactive, bfq, no UV, no freeze and only a slight sluggishness for 5 hours.

2.No
[Samsung Galaxy Nexus] Langduscher:
Don't think so. Upgrade to 4.2.x allright :good:
[Samsung Galaxy Nexus] prembox:
+10 on that!!
[Samsung Galaxy Nexus] aimcr7:
Will test this mate, thanks for your hard work. :)

EDIT: looks like r354 more stable, no reboots so far, tried using some apps, like twitter, tapatalk, light gaming. No freeze so far. Just one on initial boot as usual, but no problem after that. Will let you know if i had reboots or that weird slowdown.
[Samsung Galaxy Nexus] mrm43:
All stock settings. I use ram booster.
[Samsung Galaxy Nexus] AndyGnex:
Maybe google derped something--again-- in those patches

delivered by FedEx
[Samsung Galaxy Nexus] mrm43:
Testing 354 now. Feedback in a while. Thanks.
[Samsung Galaxy Nexus] anshulajain:
Tested 354, the bootup was slow. It got stuck in "Optimizing Apps" just after boot and the animations were very very slow. After it was completed...it rebooted again all by itself.
[Samsung Galaxy Nexus] Langduscher:
r354 doing well here, no signs of slowing down yet :good:

VERY smooth actually!
[Samsung Galaxy Nexus] allgsmnetwork:
test again in 354 ... FKU governor in boost 0? go_hispeed_load 50? above_hispeed_delay and 100.000? exact parameters?
[Samsung Galaxy Nexus] mrm43:
after flashing 354,it rebooted fine. But after using flipboard in a couple of minutes, it slowed down again. As I am writing this on my computer

i am waiting for it to finished the rebooting process. It is still in the "your device is rebooting..." stage for about 5 minutes now. Will send my

last_Kmsg if I will be able to reboot it without battery pull.

Update: after 10 minutes of waiting for the reboot process it froze. I am going back to 348. Anyway thanks. I know this will be fix later on.
[Samsung Galaxy Nexus] Fenvarien:
Using r350 since it's release with no sods, reboots or slowdowns. CM10.1 latest nightly, 192/1420, 537 max screen off, interactive/deadline, UVed (192-720, 384-760). Perfectly stable here :confused:

Thank you Franco for this Xmas present! Merry Christmas to everyone :)

GNex with franco.Kernel r350 / CM10.1
[Samsung Galaxy Nexus] ijama:
Using R354 stock rom..my Gnex flying smooth..not seeing down..at least..good work mate..thanks alot..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aimcr7:
@franco Just noticed on 354 no input_boost_freq. Is it intended or not?
[Samsung Galaxy Nexus] Langduscher:
I hope you manage to pull it off to get the log - I was waiting forever :eek:
[Samsung Galaxy Nexus] Khizar:
been using r354 with xylon v14-1 and so far dont have any issues... everything seems to be working good, just hope it stays this way :fingers-crossed:
[Samsung Galaxy Nexus] mrm43:
Sorry mine froze after 10 minutes. Had to do a battery pull. I was planning on waiting longer so I could send my last_kmsg.
[Samsung Galaxy Nexus] iammagicboy:
Hi,I just want to ask,

What's the recommended color setting in r350?
[Samsung Galaxy Nexus] ledionkoci:
For me its fine r354.no reboots or anything else.
[Samsung Galaxy Nexus] allgsmnetwork:
incredible with the screen switched off for 10 minutes at 384 mhz 30 ° celsius a stove...
[Samsung Galaxy Nexus] vrehenriqu:
Using r350 on Slim branco 4.2.1 beta 1 and no issues so far.

Merry Christmas!
[Samsung Galaxy Nexus] Khizar:
there are no "recommended" color settings, everyone use settings that they prefer.. i personally use these settings.. contrast is -15 the rest are in the screenshot
[Samsung Galaxy Nexus] Langduscher:
I use an init.d script, see attachment (remove .txt)

push to /system/etc/init.d - permissions are chmod 755 (rwx-rx-rx), then reboot

I like these colors, they look fine on my device :good:
[Samsung Galaxy Nexus] franciscofranco:
Yes, for now, but thats not what I'm testing, that change just came with the package. Just trying to make sure I understand which patch made that strange slowdown.
[Samsung Galaxy Nexus] Langduscher:
No issues here mate :confused:

Try a clean install of your ROM, then flash r354 and report back.
[Samsung Galaxy Nexus] Khizar:
my phone is fine.. no heating issues, maybe the issue is with the settings you are using?
[Samsung Galaxy Nexus] aimcr7:
Fortunately, no more slowdown for me.

Looks like mpu smartreflex causing some reboots for me, deactivating it and using my custom uV fixed some reboots i got. :rolleyes:
[Samsung Galaxy Nexus] haxor:
This Christmas day gonna be history on same day Franco released 3 nightly :D
[Samsung Galaxy Nexus] aimcr7:
Its not a nightly, its a testbuild :p

But it was still a history, because he released 3 kernel in one day. :cool:
[Samsung Galaxy Nexus] haxor:
Its your own setting or its osmosis setting which he had posted ?
[Samsung Galaxy Nexus] Langduscher:
This my own color setting. If it was 0sm0sis' I'd have credited him :good:
[Samsung Galaxy Nexus] iammagicboy:
---------------------------------
[Samsung Galaxy Nexus] haxor:
r354 still smooth so far hope will keep it up :thumbup:
[Samsung Galaxy Nexus] kingmaliQue:
ZOMG r350++ suxxx fix plox!!!!!

lol jk merry christmas evry1 and thanx franco for all ur hardwork...really2 appreciate it :)
[Samsung Galaxy Nexus] marshy73:
354 so far so good.
[Samsung Galaxy Nexus] jcoleridge:
351 gave me slowdowns and reboots. Reflashed 350 and applied my settings (192-1536, input_boost at 1036, hispeed_freq at 1228, undervolted with osmosis' values +25 mV), testing from 3 hours and everything is fine, for now. Definitely smoother than 348 and 351.
[Samsung Galaxy Nexus] gianton:
None in both, r350 and r351 gave slowness. Back to 348.
[Samsung Galaxy Nexus] Khizar:
try r354 it works great for me with osm0sis settings... smoother than r348 and no freezes or SODs

does using a init.d script really make that big of a difference?
[Samsung Galaxy Nexus] allgsmnetwork:
I went back to 348 :good:

P.S. We users are alpha tester?? I do not like this new policy...
[Samsung Galaxy Nexus] gianton:
Just flashed 354, it does feel smoother than 350 and 351. Will test it with osm0sis settings.

Thanks
[Samsung Galaxy Nexus] Khizar:
then dont flash.. nobody is forcing you

---------- Post added at 06:26 PM ---------- Previous post was at 06:25 PM ----------

np bro :good:
[Samsung Galaxy Nexus] Langduscher:
Not nite & day - but yea, colors look better when using init.d as opposed to setting them through the app.

Might be me tho :cyclops: so try for yourself and let us know your opinion :good:
[Samsung Galaxy Nexus] gianton:
+1
[Samsung Galaxy Nexus] dyndragon:
Still getting SoD overnight on r350. Just reporting.
[Samsung Galaxy Nexus] haxor:
on r354 during charging using 3G for suffering the net my phone temperature reach at 46°c :eek:
[Samsung Galaxy Nexus] thegtfusion:
Me too. Thats why I cant use franco anymore :(. Franco uses higher voltages compared to trinity ( on the same freqs.)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] ledionkoci:
Me too.while charging the phone,it became tooo hott 56°c.and i have had 1 reboot 1 minute ago, i was just using xda app,nothing else.

Ps;i have r354
[Samsung Galaxy Nexus] markop90:
Flashed r350 and today I had my first sod with this phone... Reverted to r348, it was rock solid for me
[Samsung Galaxy Nexus] haxor:
As far as I know being too hot of phone can damage the phone too !
[Samsung Galaxy Nexus] --__LoRiS__--:
With my undervolt settings i have no problem on R348, on 350 and 354 i had freezes and i had to pull battery...now i'm back on 348... Maybe the problem is that on new alpha build the voltages are too low. Thanks franco for your Christmas gift XD merry Christmas to all! :D
[Samsung Galaxy Nexus] aimcr7:
Just got a crazy slowdown on 354 when typing on LINE, just like on 350 and 351.

Went back to 348. :)
[Samsung Galaxy Nexus] threev:
350 came to a weird slowdown within 10 minutes as others are reporting. 348 worked perfectly before. 354 is going well for more than an hour. Seems good to go. Using Xylon 14. Stock with overclock to 1305.
[Samsung Galaxy Nexus] sergini:
Such a ridiculous post. Go buy an iphone and dont flash/test anything if u dont like it.

On topic, just saw that there's a 354, I went to 348 after a sod on 350. U're working fast Francisco!
[Samsung Galaxy Nexus] marshy73:
354 just had a SOD. Had to pull batt.