yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] davec1234:
It's a development site, WTF do you expect?
[Samsung Galaxy Nexus] vigan_ks:
flashed 350 but my phone crashed 3times and i have to remove battety to start it again now im back to 348
[Samsung Galaxy Nexus] whitedragonz83:
A few pages back Franco put up nightly r354 that is working so far, but if you need your device for the holiday, just stay on r348.

Went back to r348. My music began a 1 second loop and the whole phone slowed to a crawl. Had to battery pull after my reboot basically was taking 10+ minutes.
[Samsung Galaxy Nexus] haxor:
Terribly slow down and when reboot stuck at your device rebooting finally I have to pull the battery I m on r354 :(
[Samsung Galaxy Nexus] zephiK:
It's a Nightly not a milestone. Not to mention, the kernel is completely free
[Samsung Galaxy Nexus] damage98:
Something similar happened to me on my run this am. I'm on xylon maguro 14.1 with Franco 350. Streaming Google play HQ music from my online music. Def Leppard started skipping like an old record. I was able to get a reboot prompt and toaster but just hung there so battery pulled.

I doubt it is the kernel or rom. I did a bit of research and Google Debs day this can happen if you have data loss so maybe tmob let me down.

Merry Christmas all
[Samsung Galaxy Nexus] stetsonaw:
Hey man, love this kernel, but I miss one thing that less stable kernels have... any plans to implement support for the OEM desk dock?

Sent from an EpicBlueCM9/CM10 themed Liquefied GNex
[Samsung Galaxy Nexus] whitedragonz83:
My music was of my phone. Maybe I'll try r354 again later today. Need it to work for the afternoon.
[Samsung Galaxy Nexus] calinoii:
Do i need to flash the original sd binary after flashing the zip? which version is the latest stable ? which one do you recommend ?
[Samsung Galaxy Nexus] malaroth:
I had one SOD when I put the phone on charge. Left it off the charger all night, had 35% battery at midnight and at 7am I. Had 34%. Not having lag issues or anything gonna swap batteries and see but overall I think the SOD is still Google's issue not Franco. Awesome job man. Merry Christmas!

JBSourcery 4.1 + r348 Franco osm0sis UV settings FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] mrm43:
Slow downs are gone since i reflashed my ROM with full wipe then flash r350. Been running 350 now for about 2 hours. Smooth again as usual.
[Samsung Galaxy Nexus] vrehenriqu:
Ok just had an SOD. Had to remove the battery...
[Samsung Galaxy Nexus] mikeandjaimie:
Flashed 354 this morning, no slow downs, but I did have a freeze while my phone was charging and on daydream, and had to do a battery pull.. Besides that feels alot smoother than 348..just wish we could nail down the sod/slow downs
[Samsung Galaxy Nexus] osm0sis:
How is 30 degrees C a big deal? That's normal running temperature. Isn't the thermal throttle set at 70 and the auto-shutdown is at 110?

Night and day. The trinity contrast loses all of its purple tone, becoming more natural and vivid. Colors too.

Okay, officially getting tired of your ****. We can't figure out what you're saying most of the time, and I realize that's not exactly your fault considering these are English-only forums, but on top of that when we can figure it out you clearly don't know what you're talking about and are making recommendations to people that are wrong. This is a development forum section on a developers website. We are testers. This is not a new policy, this has always been the policy. If you want stability wait for the Milestone in February, otherwise get wise, read all you can, and Google everything you don't understand.

Not trying to come off angry here, just frustrated with the obvious pattern of your posts and now this unacceptable sense of entitlement. Franco gave us the gift of a new nightly with some freshly written Google patches, which don't cause problems on all devices or take hours and specific circumstances to trigger, then he has worked through the night to try and weed out whatever the mistake is, pushing 2 more test builds out to us. How can you complain about that sort of dedication?

Merry Christmas to Franco, thank you for all your efforts in the past and coming year, and thank you to everyone who helped him test overnight without complaining; you are what make XDA great.
[Samsung Galaxy Nexus] dratif:
Had 5 episodes of phone going slow and then I had to take out the battery but I didn't panic and kept rebooting the device and after that it has been working flawlessly
[Samsung Galaxy Nexus] malaroth:
Damn it Franco... we appreciate your dedication. But for one day, Christmas.... take a break. We're not entitled to anything. If 354 works or 348 or 300 it doesn't matter. For one day people can test and give solid evidence in logcat or last_kmsg or they can revert to a build that worked for them. Unless you delight in spending your holiday coding (proof you're a robot) then just tell us "my kernel. My time. My pace. Don't like it use something else"

JBSourcery 4.1 + r354 Franco osm0sis UV settings FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] peikojose:
Thanks for your kernel, it's incredible you working today!

I'm still with 348, just to be sure.

BTW I bought the FKU finally

Best regards
[Samsung Galaxy Nexus] smileyanz:
He loves it!!!!
[Samsung Galaxy Nexus] Clusterfunk:
Since upgrading to 350 I've been getting a lot of extreme slow downs and if I leave the device for more than a few minutes, the screen will not wake up and I have to pull the battery.

Downgrading to 348 for now.
[Samsung Galaxy Nexus] mpokwsths:
:lol: :lol: :lol:
[Samsung Galaxy Nexus] ChazzMatt:
"Dailies" are not always stable. THAT's what "milestones" are for.

Franco culls the dailies that don't meet his approval, which is why releases often jump a few numbers. We never see the ones he considers not good enough. But the dailies he releases are one he thinks are worth trying. We try them out and report back. Most are improvement, but some are not. That's why we help test. After several good releases, a new line is drawn in the sand and that release is declared the new "milestone".

If you don't want to participate, then stick with (safe) milestones or wait until a daily release gets really good reports before flashing. You may end up a few releases behind everyone else.

___________

Plus, consider this. Development on our Galaxy Nexus will come to an end. When? Depends on Franco. He has an LG Nexus 4 (the current Nexus) and he's clearly stated his focus is there. Our Nexus is not sold any more. At some point when the devices diverge too much, he will stop developing for the "old" Galaxy Nexus.

One more milestone? Two? Depends on Franco...
[Samsung Galaxy Nexus] allgsmnetwork:
I did not want to offend the community or kernel of franco but tiring for 3 times with 3 kernel reset everything ... and finally back to 348 at all ... in fact I can only say thanks to the kernel by franco perhaps I expressed myself so 'because is the first time it happens I apologize :(
[Samsung Galaxy Nexus] gianton:
354 working stable with no slowdowns or freezes for the last few hours. Using osm0sis UV settings.
[Samsung Galaxy Nexus] Wynnded:
I got 354 loaded up this morning after all the standard holiday mayhem and will be abusing it throughout the day as time and opportunity permits.

Sent from my Galaxy
[Samsung Galaxy Nexus] The Gingerbread Man:
354 seems stable so far here

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jcmm11:
Back on 348, will flash 354 shortly. 350 seemed fine after some initial sod's but then got slowdown. Told phone to shutdown. After a moment got vibrate signal but then screen wouldn't turn off had to pull battery.

Will try 354 for today.

Merry Christmas to all!
[Samsung Galaxy Nexus] Angelakaro:
Merry Christmas to everyone!

I have a noob question: do you think that increasing SD card cache size will bring some advantages? I read somewhere that increasing it can improve game performance but i experienced some audio artifacts when SD card cache size was too high. What do you think about it? Thanks in advance and again,merry xmas! (I'm posting here cause in previous releases SD card cache size was higher and i had also better gaming performance,just to be sure has nothing to do with franco's great work)

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] t1.8matt:
from what i've learned throughout the years, 2048 seems to be the best sd cache size to go with, but everyone's going to have different results. i personally wouldn't go above that value.
[Samsung Galaxy Nexus] vigan_ks:
i get freezed 2times while playing angry birds on kernel 354 now i backed again to 348
[Samsung Galaxy Nexus] timbck2:
Had an SOD/freeze just now with r354, while it was frozen the battery plummeted from about 65% to 11% in about 1/2 hour and the phone got very hot. No last_kmsg since I had to pull the battery. I'll stay on 354 (for now) to see if it happens again.
[Samsung Galaxy Nexus] gianton:
Just had a freeze with r354 while on charger, device rebooted itself.

Back to 348.
[Samsung Galaxy Nexus] Langduscher:
r354

Noticed a reboot whilst phone was asleep (no SoD) - had to enter pin to unlock sim, last_kmsg attached

No issues otherwise
[Samsung Galaxy Nexus] Langduscher:
Please get last_kmsg from /proc and post it here for troubleshooting :good:

---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------

You too, please get last_kmsg from /proc and post it here for troubleshooting :good:

Just posting issues is useless to Francisco :)
[Samsung Galaxy Nexus] gianton:
Here's the last_kmsg file.

I'm going to give it another test with default settings just cleared F.K.U app data.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the logs guys. All the logs that I've seen they all end with this:

[ 2644.871032] CPU1: Booted secondary processor

[ 2644.872100] CPU1 is up

[ 2644.873931] Switched to NOHz mode on CPU #1

Pretty weird.
[Samsung Galaxy Nexus] jcmm11:
On 354 got slowdown with lock up on reboot. No kmsg due to battery pull. Logcat attached.
[Samsung Galaxy Nexus] osm0sis:
Very weird. I just got my first slowdown on r350 an hour or so ago. Tried to reboot and/or power off to get a last_kmsg but, like everyone else, it just gets stuck at the spinner and eventually completely freezes. I grabbed a logcat though. Lots of crazy repeated **** in it.

For those with slowdowns, since rebooting doesn't seem to be a viable option, instead go to /proc/ and copy kmsg to your sdcard. That will give franco something to go on for kernel messages. I'll stick with r350 for now and try to do this myself the next time.
[Samsung Galaxy Nexus] franciscofranco:
I think I know what it is causing that slowdown/reboot thing. r355 coming up, finishing compilation.
[Samsung Galaxy Nexus] franciscofranco:
Grab r355, I hope the strange things since r350 are fixed!
[Samsung Galaxy Nexus] hasnol143:
testing it out now, i'll report back in a couple of hours
[Samsung Galaxy Nexus] ChosSimbaOne:
Hi Osm0sis just to make sure i understand your post correctly. The part I've marked with bold. Do you mean that I should put in the voltage i get when the 192Mhz slot crashes into the 384Mhz slot, or is it a typo and should say 192Mhz? what confuses me is that it says that i should do the exact same for the 384Mhz slot. Does it mean that i should keep lowering the 384 Mhz slot until it crashes and set the last stable voltage for 384 slot into 537Mhz slot. I'm a bit confused.

What i thought was the propper way to UV was to set min and max to same frequency and keep lowering the voltages. Then but in the last stable for all the slots. Then again set the min and max to same voltage, and stress test with game or similar. Is that entirely wrong?

Best regards ChosSimbaOne
[Samsung Galaxy Nexus] sajty:
I always thought,that master of GN kernels is someone else...Probably i was always wrong :confused:

I am not using franco right now,but i "see" franco's hard work here and i must say...wordless.Good job franco :good:
[Samsung Galaxy Nexus] derPianist:
INDEED !

via Nexus 4 from Lampukistan.
[Samsung Galaxy Nexus] osm0sis:
Good eye. Sorry I originally wrote that when 384 was the minimum. I updated it but missed that one. Thanks for bringing that to my attention. I'll fix it now. :)

And yup that's the correct method in a nutshell.
[Samsung Galaxy Nexus] Controvrsy046:
Merry Christmas Franco! Thank you for all your hard work and dedication for pushing out new nightlies on Christmas!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] malaroth:
Thank you Franco. You're amazing and I greatly appreciate all of your hard work. Soon as I can your PayPal account will show it ;) merry Christmas

JBSourcery 4.1 + r354Franco osm0sis UV settings -25mV FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] irminsul:
I just flashed r355, let's see how this goes. After another slow down on r354 I've also got two f ups while listening to music. First a total freeze with music skipping, second a 'sod' while listening to music with screen off, music kept playing but device didn't wake up. Had to pull batteries , couldn't get logs.

Gonna charge r355 overnight and lets play with it tomorrow. Goodnight Europe.
[Samsung Galaxy Nexus] dpgetz:
Flashing 355 now :)
[Samsung Galaxy Nexus] marshy73:
Franco..

I flashed 355

Experienced a slowdown and i noticed i lost Radio Signal at the same time.

I quickly tried to do a reboot to get log but the shutdown process took longer than 15mins. Yup, the circle was still very slowly turning.

After 15mins it gave up and froze. I had to batt pull.

I'll stick on to 355 to see if it happens again and try getting you some logs.

Merry Christmas and thanks for all your work.

Cheers
[Samsung Galaxy Nexus] Controvrsy046:
Is everyone leaving the governor settings on the different stock settings on r355? Or are you guys switching it back to 6/65/45/15 ?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Wynnded:
I'm only OCing but not messing with anything else.

Sent from my Galaxy
[Samsung Galaxy Nexus] KJW979:
Using r355, after being in Kindle app reading for about 5mins, phone slowed to a crawl. Apps took for ever to open, pushing any button caused considerable lag, 2mins or more to open. Had to pull battery to get going. Only change in settings is max cpu of 1536. ROM is Evolution 2.2, no other rom troubles noted.
[Samsung Galaxy Nexus] dyndragon:
R355 sod for me. Unfortunately I didn't realize that going into recovery generates a new last kmsg so no message. Sorry!
[Samsung Galaxy Nexus] marcusva79:
Just now got on the latest nightly. Haven't noticed anything yet.
[Samsung Galaxy Nexus] lesp4ul:
I thought 354 was running well for hours (no UV) but it won't woke up after 8 hours of sleep this morning, battery pull :p . Well back to 348 for now.

Kmsg

http://db.tt/T8O5x686
[Samsung Galaxy Nexus] lippol94:
To those who have problems, what Rom are you running?

As I'm finding 354/355 absolutely perfect! Incredibly great battery life, smoothness and stability. Only had slowdown in one occasion on 351. Nothing more.

I'm running Cm10.1 by fitsnuggly.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aimcr7:
I dont think its rom related cause i am on Xylon 14-1 tried with trinity and its been 12hours up time and no lag or slowdown or anything.

Usually i got the slowdown issue when typing either on twitter or tapatalk.

It just become so slow, and it happened randomly, so i dont know what causing it.
[Samsung Galaxy Nexus] ijama:
Tried r355 running stock and default setting..never get any probs so far..working well..wanna tried uv's..report then

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mikeandjaimie:
I'm running XenonHD atm when I got my issues.. I'm running 355 now and I haven't had an Sod or slowdown yet, had them on previous builds. Been using it steadily for a few hours now.. Looking good
[Samsung Galaxy Nexus] MizzouBrent:
I was running fitsnugly cm10.1 when I got slow down on 354.
[Samsung Galaxy Nexus] OtavioMalzone:
Hey francisco,

why did you stopped messing up with cores? like, I know that gives a lot of headache, but it has some benefits..

Almost all other kernel devs are now incluing it..

Oh, and 355 is smoother that some previous versions... I don't what you did, but souds good man!

tnx btw
[Samsung Galaxy Nexus] daxisalive:
Just curious. Will the sound control option ever return? Or was it removed because it was a placebo? I really loved the high quality sound option and volume boost. I :)
[Samsung Galaxy Nexus] marshy73:
Franco

It happened again.

Still on 355.

Lost Radio Signal.

Phone Slowed to a crawl.

Immediately activated a reboot.

Circle spins at a crawl for more than 10 mins then total SOD.

Had to do a Battery Pull.

Sorry couldn't get log.

Switching back to 348 for now as I need use of phone in the day.
[Samsung Galaxy Nexus] ajm786:
Just got a SOD on 350, all stock, no OC/UV. Doing nothing but browsing the internet. Device became ultra slow, then just died. Funny thing is that the LED started blinking red. Had to do a battery pull.
[Samsung Galaxy Nexus] osm0sis:
r355 is out. Give it a spin. If you have another slow down get a logcat and copy your /proc/kmsg to your sdcard.
[Samsung Galaxy Nexus] franciscofranco:
Because there's no need to mess with the cores in this OMAP4460, 0 battery gain from it and lots of headaches because this hardware doesn't like hotplug unless some circumstances are met.

****... Thanks for reporting.

I might have to roll back down the interactive patches to r348 state, I can't figure out the cause of the slowdowns what-so-ever. Most of the patches were related to load balancing and improving the boost (when we touch the screen) logic and functionality... damnit.
[Samsung Galaxy Nexus] Controvrsy046:
No problems here on r355.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] marshy73:
Since the patches were provided from Google.

Perhaps its good to update them (if possible) on this phenomenon?
[Samsung Galaxy Nexus] franciscofranco:
Its a bit hard to describe this problem since the logs are not very explicit. I can ask them whats up, but I doubt it will do much since they are not working on Tuna anymore (this patches are aimed to Manta I believe).
[Samsung Galaxy Nexus] twistedumbrella:
Is it cache buildup with the memory killer? That happened a lot with the thunderbolt. It ran awesome at first and over time got slow and starting locking. Turns out it was too much trying to run too fast.
[Samsung Galaxy Nexus] timbck2:
Same here.

EDIT: I spoke too soon. I just had my phone slow to a complete crawl again, this time with r355. No last_kmsg existed after booting back up, since I had to pull the battery.
[Samsung Galaxy Nexus] playenball:
Fastboot flashed boot.img for r355 and no problems here. Running JBSourcery v4.1

Edit: Spoke to soon. Slowed down. I tried to reboot to get the log but no such luck. Ended up having to do a battery pull.
[Samsung Galaxy Nexus] modifii:
@ franciscofranco

Can you tell me what frequency you set for GPU in r342?

On my GNex, stock rom + r342 combo works marvelously. Ultimate battery back up.
[Samsung Galaxy Nexus] franciscofranco:
512.
[Samsung Galaxy Nexus] osm0sis:
Yes, rebooting won't work with the slowdown bug; everyone needs to save a logcat (make sure aLogcat is a system app first - when your device is running normally - so that it has the correct JB permissions for accessing system logs) and then go and copy /proc/kmsg to sdcard BEFORE battery pulling. Only ways to get anything useful. :good:
[Samsung Galaxy Nexus] davec1234:
355 took a **** after about 40 minutes.

Same behavior as last time.
[Samsung Galaxy Nexus] DoesntPostAThing:
355 gave me a SoD. Reverted back to 348 for now.

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] z7nz:
I got the same problem on 355. The phone got really slow at 30% battery, then SoD right after. I pulled the battery out, restart. It dropped to 14%!
[Samsung Galaxy Nexus] Wynnded:
I haven't had the slowdown yet with 355, but I just turned the screen off to move from one room to another and it wouldn't wake.

Should I be able to look at the last.kmsg on my device?

Sent from my Galaxy
[Samsung Galaxy Nexus] jcmm11:
If you can get in via adb copy contents of /proc/kmsg

Once you pull battery you'll lose last_kmsg and until you reboot it doesn't exist (more precisely the old one exists).
[Samsung Galaxy Nexus] reaper000:
Had the slowdown with 350. Logging my first ever SOD with a Franco kernel on 355. Not worried as it was a fairly regular occurrence with Zen.

Although I've had terrific battery life with Imoseyon's Lean, still have no problem going with Franco as the daily driver on the cutting edge... Reverting to 348.
[Samsung Galaxy Nexus] Wynnded:
Thanks for that explanation, unfortunately I am entirely mobile for up to the next week so I don't know if I'll be able to contribute any sort of logs or records of what's happening on my device. All I can really post is that Franco's efforts are working or they're not. That's pretty frustrating, but I'm sure it's not nearly as frustrating as it is for Franco. Sigh.

Sent from my Galaxy
[Samsung Galaxy Nexus] calibachrome:
r350 working great thus far. Question, Google wallet saying unsupported device since Franco installation. Is this normal?
[Samsung Galaxy Nexus] dpgetz:
V355 running smoothly with my Xylon v12 rom. :thumbup: :D

Sendt from my Gnex - Xylon v12 with Franco v355 on XDA premium.

Free mirrors for devs at droid.dpg.no - pm me for more information.
[Samsung Galaxy Nexus] Wynnded:
It says that when you're rooted, it will still work though.

Sent from my Galaxy
[Samsung Galaxy Nexus] rajputrajat:
355 was running without any problem since this morning..

but just now had SOD... reverted back to 348...

Love to try new kernels though.. good or bad.. doesn't matter....
[Samsung Galaxy Nexus] calibachrome:
Thanks, and I meant to say r355 is running great on stock Rom thus far after about 6 hours.
[Samsung Galaxy Nexus] _chanstar_:
r355 is so far so smooth.

I noticed Governor Control now has 'boost' enabled and 'input_boost_frequency' not supported.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] prembox:
Finally got an SOD on R350 after one full day of use.....phew.....back to R348....ahh...whatta relief!
[Samsung Galaxy Nexus] melvie:
Flashed 355 last night and I think my phone was rebooting whole night, it was smoking hot when I just woke up.

Had to pull the battery and let it cool down. Rebooted and when I set the screen off it reboots again. And again when the screen went off reboot.

Now I am back to 348 and no issues whatsoever.

Does this last kmsg help? http://db.tt/WaeNpiSi

No uv or taskillers
[Samsung Galaxy Nexus] gianton:
Both r354 and r355 are stable with stock voltages and overclocked at 1536MHz. Will report later again.
[Samsung Galaxy Nexus] isinisterx:
Just got a SOD while charging the phone on the latest kernel version
[Samsung Galaxy Nexus] Fenvarien:
+1

SOD happened after a full day of usage here too. Thanks Franco for all the hard work you put in sorting this out :)

GNex with franco.Kernel r350 / CM10.1
[Samsung Galaxy Nexus] jcmm11:
Well I thought 355 was fine but I finally got a slowdown after about 11 hours. Grabbed kmsg and logcat before rebooting. Back on 348 for now.
[Samsung Galaxy Nexus] kecinzer:
Yesterday I flashed 350. Go sleep with 47% battery and everything off (data, WiFi). Today I wake up and phone was completly drained and turned off.

Sebe here, that builds after 348 are broken somehow :(
[Samsung Galaxy Nexus] irminsul:
My phone SOD'd when I woke up this morning. Really wanna help you tackle the problem but I'm going on a trip and need my phone to stay stable. It's safer to use r348 for now.
[Samsung Galaxy Nexus] gianton:
Just had a slowdown with r355 while using Tapatalk (stock voltages/OCed at 1536MHz), no last_kmsg as I pulled the battery.

Back to r348.
[Samsung Galaxy Nexus] Khizar:
r354 froze on me had to do a battery pull.. think i will skip r355 and go back to r348
[Samsung Galaxy Nexus] razvanultra:
Just installed 348 over stock 4.2.1 and I still have low wifi signals, it is kernel related? or i have to find other solutions...

thanks