yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] markop90:
Thank you franco for your kernel!

I have a request, a critical bugfix for the latest GNeuxes...

Why? These GNexuses (like mine) mount a new kind of eMMc (model V3U00M, production date 08/12 - 09/12) that suffers of the same problem N7 suffered before: when free space goes under 3gb, phone will lag horribly. Only flashing google factory images lag goes away.

The issue is described here: http://code.google.com/p/android/issues/detail?id=39154

A great dev, atlantis, has made a kernel with a functional workaround (see here http://xdaforums.com/showpost.php?p=35909877), i guess he added the discard option in the data and cache mount; could you add this mount option in your kernel too? I love the features of your rom!

Thank you in advance!
[Samsung Galaxy Nexus] marcusva79:
I flashed 356 and i got not cell service. In going to redownload it and see if it was a bad flash. Using AOKP on toro+

Edit. Bad download. Everything working good now
[Samsung Galaxy Nexus] allcity187:
Install 356 audio on Pandora and my music player would stop working. I have Misledz if that helps, went back to 348 everything is back to normal.
[Samsung Galaxy Nexus] The Gingerbread Man:
It might be because of the other mod, it works fine here using Google play music on minco v6 and #356. Tbh you really don't need extra audio mods just it without by rehashing your rom and latest kernel and report then. 0 issues here and been listening to my music for 2 hours or so in total

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] _chanstar_:
I'd have to agree with you here on r355. It was stupidly smooth and fast!!

On r356 and its smooth (minus the stupidly) but not as smooth as r355......
[Samsung Galaxy Nexus] malaroth:
It's always that one time you DON'T backup... didn't realize I mistyped my 384 voltage and sent me into irrecoverable reboot... see? Don't UV and complain about it. I see what you mean though osm0sis about voltages being borderline. Had a problem with my 1036 too but I'd been able to get it down to 1025 mV stable. Went back to 1050 and all :good: (note::; NONE of this is in any way shape or form ANYONE but my fault)

JBSourcery 4.1 Franco 356 + osm0sis UV settings FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] ajm786:
I completely understand where you're coming from.....but in my case, I do NOT UV/OC AT ALL; I run everything stock. For the first time in my history of using franco kernel when I got the SOD is when I used anything 348+.

I am running 345 now, and it's perfect. I do have to say, though, I do notice a difference between anything higher than 345; they are much smoother.
[Samsung Galaxy Nexus] Tito2007:
Back when you had the option to increase music volume (0,1,2,3) if I ever selected 3 my music would stop playing ..like if the audio out portion was too much ..so it would stop the currently playing music ...that's what happens when I use r356 my music cuts off for no reason if I lower the volume the music stays on,once I higher it ..shuts off.

Bixies 4.2.1deoexed ROM

No mods

192-320 (kbps)

Google play music

Edit: Like I said earlier r355 works flawlessly for me ..just like r348 did
[Samsung Galaxy Nexus] osm0sis:
If the 10 seconds before f.Ku sets the voltages after boot isn't enough time for you to get in and disable them, that's what my franco.Kernel Emergency Reset zip is for. No backup/restore required. Check my sig. :)
[Samsung Galaxy Nexus] obsanity:
Hey guys. Just an observation here.

For any of you running Trickster app uncheck the set on boot enable option to stop SOD.

I was able to repeat it a few times now. Reboot your phone and let it boot all the way. Don't touch it and let the screen time out. Within a minute it will reboot by itself.

Now boot back in and uncheck that option in Trickster app. Repeat and this time it will boot and not self reboot again.
[Samsung Galaxy Nexus] maverick_hunter:
Flashed r356 a few hours ago, no problems to report.
[Samsung Galaxy Nexus] malaroth:
Thanks man... that's one thing tapatalk doesn't do is show sigs and I'd forgotten you had that. Good lookin out
[Samsung Galaxy Nexus] moomingstarz:
I flashed r356, and am experiencing huge battery drains (20% in less than 2 hours) and my keyboard (stock) is also consuming 10%. Is anyone else having this problem?
[Samsung Galaxy Nexus] ahse0w:
i had a reboot when watching youtube video in HQ mode.

i turned the headphone jack a little while it was inside the hole and it rebooted.
[Samsung Galaxy Nexus] osm0sis:
Not a SOD. Spontaneous reboot. Cool info though. Wonder what the issue is.
[Samsung Galaxy Nexus] allgsmnetwork:
The problem is not UV but do not use very hot or when the battery chip, the battery is discharged at once, I use it in everything, wifi or 3g + active data, Tapatalk, google+, facebook, web, phone calls, etc. exceeds the 50° FKU there is a limit of 50 ° of temperature and UV are not forced to stop using the device so it seems clear that without UV is impossible to do everything because the battery also gets to 49° FKU because otherwise the control ?

Is not a criticism but have 512 MHz GPU often unstable made ​​some members have written that the lags in games while with the stock kernel at 307 mhz no how is it possible? Would not be better to have stable GPU to 384 or 512 unstable? according to my humble opinion it would be better to make two versions as in previous versions so 'you could choose?

Remember that it's a very thorough with GPU kernel at 512 mhz and overclock CPU.
[Samsung Galaxy Nexus] Savant:
Don't have that problem with trickster mod and its funny what problems everyone is having with 4.2+.
[Samsung Galaxy Nexus] joaquinf:
Jesus man
[Samsung Galaxy Nexus] D3VI0US:
anybody getting lags and freezes when using chrome or stock browser with r356?
[Samsung Galaxy Nexus] timbck2:
I have had some serious lag with Chrome, also with the stock camera app. A reboot "fixed" it. last_kmsg file link from after the last time it happened is attached if it will help at all.

http://db.tt/5EFHCtKA
[Samsung Galaxy Nexus] Redneck Trash:
I have no issues with Chrome and r356.

Set from my toroplus
[Samsung Galaxy Nexus] osm0sis:
Chrome is known for serious lag. Go to App Info for it and clear cache only, tends to fix it's ridiculousness again for awhile.
[Samsung Galaxy Nexus] happymonk:
Been using franco.Kernel-r356 with osm0sis UV plus another -25mv further UV for awhile. No experience of slowdown, reboot, freeze or SOD. Running Xylon 14.1 beta.
[Samsung Galaxy Nexus] osm0sis:
I'm going to take my voltages down if you people don't wise up and start following directions. DO NOT UV THE SAME ACROSS THE BOARD. Different frequencies can take different levels of UVing, so adding or subtracting 25 could work for one or two but be unnecessary or unstable for others, even if you're using mine as a base. That's why EVERY instruction post for UV has you do it for ONE frequency AT A TIME.
[Samsung Galaxy Nexus] Ridho1:
I am on r356. I undervolt a bit more than osmosi's setting. No issues here. No reboot, no SOD.
[Samsung Galaxy Nexus] allgsmnetwork:
;) hi friend
[Samsung Galaxy Nexus] dandyqb:
no any issue encountered in r356, all in default settings no UV or whatsoever :cowboy:

Merry Xmas to all :)
[Samsung Galaxy Nexus] Craxx:
... Until franco include this in kernel you can use a init.d script for that. Since I use the script all is working fine :)

http://xdaforums.com/showthread.php?p=35870040

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] slayr76:
Since Franco r350 an then again with r355 an r356 I can no longer stop my gnex from freezing up an getting sods all day long, gone back to stock kernel with no problems yet.
[Samsung Galaxy Nexus] ryanytchan:
anyone able to run 1.8ghz? What voltages are you using?

I can get 1.7 stable but am struggling with 1.8
[Samsung Galaxy Nexus] franciscofranco:
Let me guess, you undervolt?
[Samsung Galaxy Nexus] franciscofranco:
I've been following Android's gerrit and they just merged a change that enables automatic Multi Parallelism of C/C++ code using GCC 4.6.3 and GCC 4.7.2 (core Android libraries are coded in Native. Native = C/C++). The protocol is named OpenMP. I might be wrong here, but if my suspicious are true we'll probably feel a slight performance boost in the next iteration of Android (if the changes are pushed into the next iteration of course... they have their own agenda).
[Samsung Galaxy Nexus] markop90:
I have it already, but a direct kernel fix is better, since the problem of 3 gb is still present! Thank you! :)
[Samsung Galaxy Nexus] franciscofranco:
The mount option is actually done either on the ramdisk (which I can do), or via a script, but not in the kernel directly.
[Samsung Galaxy Nexus] RevengeFNF:
Hey Franco,

Im using r348 at this time.

I've done a little of undervolt, not too aggressive, using your app. My phone does not freeze and i do not have any kind of sod's. My battery last longer with the undervolt, its noticeably.

With r356, the same undervolt will cause sods and freezes?
[Samsung Galaxy Nexus] allgsmnetwork:
When will start the new update?
[Samsung Galaxy Nexus] markop90:
Yes I mean the ramdisk, in fstab.tuna right? With kernel i wrongly mean kernel+ramdisk, I know :)
[Samsung Galaxy Nexus] franciscofranco:
Well it really depends on each device's hardware, unfortunantly thats something I can't predict :)

Should be in January/February.

Yep exactly there!
[Samsung Galaxy Nexus] slayr76:
Hav'nt changed a thing running everything as default Franco settings on CM10.1 official nightly 20121226 build.
[Samsung Galaxy Nexus] kecinzer:
Just installed 356, and after few minutes my phone freeze during reply to sms.

Cfq scheduler, 192 - 1305. This setting worked on 348 like a charm.
[Samsung Galaxy Nexus] neo-X:
Getting great battery life with 192-1536 on latest kernel. Thanks Franco!!!

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] franciscofranco:
Weird. Try to use 384MHz as min and see if it happens again.
[Samsung Galaxy Nexus] gianton:
R356 working rock stable at 384/1536MHz with osm0sis UV (1036MHz at 1075mv). ROM is AOKP Roman 1223 build.
[Samsung Galaxy Nexus] obsanity:
Its actually SOD but that is just a way of testing it. If I were to try pushing the power to turn the screen on it won't wake up but will eventually reboot on it's own.

I seriously think it has to be something they pushed into CM lately or one of the apps we all have in common. I've tried it with several kernels and nothing but CM stock works.
[Samsung Galaxy Nexus] Angelakaro:
Let's hope it! However,g nexus is almost perfect thanks to jelly bean and,of course,to your kernel! The only thing i wanted better is gaming performance,which is not your fault but google should do something. (I'm so annoying about gaming cause my friends got sgs2 and we play modern combat in wlan: the difference beetween our phones is huge! Lol)

r356: rock stable and faster than r348,however in r350 i had better smoothness sensation

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 11:33 AM ---------- Previous post was at 11:30 AM ----------

The only game which lags more than with stock kernel is most wanted,which thinks that our phone is high-end (isn't it? :P) due to the overclock slots. Me too thought that GPU at 512 MHz was unstable,but now i'm not thinking this anymore because franco make it stable and fast. If you want best game performance with overclock,just disable thermal throttle

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] whitedragonz83:
For me SR under volts this to 1100. Just saying... Try SR only and set the Max CPU to various settings with performance, view the voltage in the device manager.
[Samsung Galaxy Nexus] gianton:
Yes I know that, however at lower speeds 192 and 384MHz UV does give me better standby battery life.
[Samsung Galaxy Nexus] malaroth:
:( when I had that in my sig it was because I had tried every one individually without problems. Then I got over confident and played a lil more. I'd left some -25 and actually had some that were capable of handling -75 or 100 and I thought it ridiculous to be using the voltage when my silicon could run stable. I'm better prepared now and just posted my experience as a warning of exactly what you're saying. That not testing one at a time is gonna **** up your day so be forewarned or don't do it at all

JBSourcery 4.1 Franco 356 + osm0sis UV settings FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] drnejo:
I jump from r348 to r356 and i have no SoD or freezers over r356 (192-1228 with cfq governor)

I use osm0sis settings +25mV for stability. My ROM is AOSP r8

Merry Christmas Francisco and keep the great work!
[Samsung Galaxy Nexus] Syfer_Fever:
guys can anyone provide me UV setting by sir osm0sis? and maybe some guide how to set UV setting by sir osm0sis. thanks :)
[Samsung Galaxy Nexus] aimcr7:
Look at his signature mate, it is there
[Samsung Galaxy Nexus] logi43:
Installed R356 with uv at -50 and had a reboot and freezing, voltage back to -25 and behaves stable after an hour, much faster and smoother kernel more than R348

thanks to Francisco for his work and all users that help enhance this kernel

Xylon 013 stable

F.F r356

I apologize for my poor English

Happy New Year
[Samsung Galaxy Nexus] dono89:
I'm apologize too see that the game lag yet..... I don't understand.....

With anarkia, trinity, leankernel, every game working good, but with this kernel isn't possibile play with anything that is write for 3d...there some problem with driver?
[Samsung Galaxy Nexus] logi43:
Read this post do not have any complications UV but these voltages may not work well on all phones.

http://xdaforums.com/showthread.php?p=35370188
[Samsung Galaxy Nexus] neo-X:
Amazing battery!! Can't thank you enough Franco

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] llevo3:
r356 stable with 384/1305 interactive/cfq/westwood hf1036/ibf729, no UV @ AOKP 27.12 by romanb
[Samsung Galaxy Nexus] RevengeFNF:
There is a problem that games think we have a more powerful phone.

For example, in nfs most wanted, with our kernel at 512Mhz GPU, the game runs very slow. Thats because the game puts the graphic settings to the maximum.

With lean kernel, with gpu set to 307Mhz, the game runs very smooth. Thats a little wierd, that a kernel with 307Mhz runs better 3D Games than a kernel with 512Mhz gpu.
[Samsung Galaxy Nexus] dyndragon:
R356 still sod overnight on charger. No last kmsg was generated unfortunately.
[Samsung Galaxy Nexus] calinoii:
Can someone help me with a specific issue ? Everytime my phone heats up it starts freezing,many many little freezes every second,even when scrolling or switching between drawer pages or home screens...i set Termal Throttle off and and those are my settings : 384/1536 MHz ,interactive/deadline/westwood hf 1036 / ibf 729,no undervolting. Tried with stock images from google(100% stock) 4.1.2 and 4.2.1 images. Tried milestone 6 kernel,r300 for the 4.1.2 and r348 for the 4.2.1 and a bounch of custom roms like AOKP (both 4.1 and 4.2) CNA,Xylon,Android Revolution,Overdrive,Cataclysm and I still have this issue. I noticed that if I use Faux's kernel I don't have the problem. I really do want to use franco's kernel,so please help me :(
[Samsung Galaxy Nexus] RayGarden:
Finally....

#356 gave me no SOD's so far. Very smooth with CM 10.1

(edit) Great Battery too:

26hrs on Battery

3hr 2min Screen-On

5% left

Wifi on, all the time

Thanks Franco :good:
[Samsung Galaxy Nexus] whitedragonz83:
Stock r356 full sync apps and other ****. Hitting my normal 24hrs with 3+ hours screen on time.
[Samsung Galaxy Nexus] yellowdie:
I love how Franco clearly comes out and says "Don't undervolt." And then the next five pages are people talking about UVing at -25 or -50 across the board and getting reboots...

The sheer lack of retardation and disrespect amazes me.

Osm0sis knows how to undervolt properly. He and I have worked on stuff on the side and I know that he knows what he's talking about. 90% of the rest of you here have no flippin' idea what you are doing. Just because Os' settings are stable on his phone does not mean they will always be stable on your phone. Every device is different. So when you say "oh, I'll just use Os' stuff and my phone will be super awesome and perfect and never have an issue again" you are creating more problems for everyone. Don't assume that his stable will work on your end. And don't just flippin' add or subtract numbers from it!!!

For crying out loud

.

I feel SOOOO freakin' bad for Franco having to put up with the crap here. Yes, there are some people with legit SODs and reboots (mostly due to 4.2 probably), but there is a ton of crap that you UVers are causing to yourself and then either blaming the kernel or blaming your UV but still adding confusion and mayhem to this thread. Franco has to wade through layers and layer of your crap just to find out what your problem is before he can even start to fix the issue. So you UVers are causing WAY, WAY more work for my friend and he definitely has better things to be doing. Seriously people. Seriously.

Os is right about SR not having good control over the extreme freqs, but most of the stuff is handled well (maybe not AS aggressive as would be desired, but still pretty good). Those of you who UV (with or without knowing what you're doing): how much do you actually gain from it? I run completely stock settings and I get between 3 and 4 hours of screen on time depending on what I do (gaming or not) with stock battery and wifi/3G/sync on all the time. Is dealing with potential SODs/reboots/freezes/whatever worth an extra 15 minutes of battery in a day? Honestly? *sigh*

On another note. @allgsmnetwork, just stop. Please.
[Samsung Galaxy Nexus] punkeroso:
Franco, this is my kmsg right after experiencing a slowdown with r355: http://db.tt/guJItFfG

Hope it helps.

As always, thanks for your great work!
[Samsung Galaxy Nexus] peikojose:
r356?

I'm still using r348.
[Samsung Galaxy Nexus] Khrushy:
Wooo! Stick my head back in after a few days and this place looks like a madhouse.

Testing 356 now. Initial reaction is that it's very snappy indeed. I'm impressed.

I still owe a last kmsg and logcat to do with my weird ability to set 1mv with SR turned off, but it seems like a reasonably low priority issue, and I'll be on the road for another week anyway, so it can wait till then.

Thanks again for all your hard work Franco, it's appreciated.
[Samsung Galaxy Nexus] punkeroso:
No, r355. Thanks for the advice!
[Samsung Galaxy Nexus] peikojose:
You are welcome, try 356
[Samsung Galaxy Nexus] moomingstarz:
Does anyone have battery stats on r356 with 4g/h+ on at all times? :o
[Samsung Galaxy Nexus] punkeroso:
Already done :good:!!
[Samsung Galaxy Nexus] ciairo:
GPS performance

I might be silly, but it seems to me that with the latest versions of Franco kernel the GPS performance is not good.

I know that GPS is mostly a matter related to radio and RILs than to the kernel, but I did so many tests and basically while the "stock" kernel (what is that, a LeanKernel?) installed by default in roman's last nightly AOKP gets a fix in seconds, with Franco's or the latest LeanKernel nightlies I always get a poorer performance (many satellites are viewed but the fix takes ~1-2 mis).

I tried to be sure as much as I could, therefore I always repeated my tests in the same place, same time, and changing only the kernel and nothing else. I also played with the gps.conf optimizations but ended up to the conlusion that the stock one is as good as we need. I also ensured to have the AGPS data updated etc., i.e. I tried to create a clean and meaningful test bed.

"Stock" kernel good, Franco nightly and LeanKernel nightly bad in that respect. Which is bad as they are so cool for all the rest of features :)

Ok, it can be just me or my phone, therefore I ask here. I'd like to know how many of you guys think that GPS performance is not good, and if so, if there is any clue on the reason and possible solution.
[Samsung Galaxy Nexus] Angelakaro:
FOR WHO IS INTERESTED IN UNDERVOLTING:

I founded a nice guide searching on google,maybe will be useful for people interested

http://bigfatreality.blogspot.it/2012/04/complete-android-undervolting-guide.html?m=1

However,i do not want to undervolt even if my battery life sucks to avoid dangers and who wants to avoid dangers just like me must avoid undervolt by himself,cause it may be only a waste of time and a couple of problems for his device.

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] Angelakaro:
Here is another guide for undervolt,just to stay at home ;)

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

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] Paragon_X:
Thought I'd give me impressions on r356. My setup is AOKP 12/23 with stock settings from Franco Kernel. The sound booster is noticeable, minimal if no skip with music. However battery is less, airplane mode overnight usual drop is around 1-2% I got pretty much 4-5%, on screen time roughly over 2hrs. I find r354 the rest model was the best for my so I just may revert back but I quite enjoyed the sound boost performance here.
[Samsung Galaxy Nexus] gianton:
Idle drain on r356 is equal to r348, I lost 1% in 8h all disabled with AOKP Roman 1223 build.
[Samsung Galaxy Nexus] yellowdie:
For the record

: Undervolting is not necessarily a bad thing--I used to be a huge fan of UVing pretty extremely on my Epic 4G. But the GNex comes with Smart Reflex and it does a really, really good job of handling the UV for your specific device (again, not for the extreme frequencies). That's why I think UV (at least on this phone) is not worth the trouble because you aren't running "stock" voltages per se, you're running Smart Reflex Calibrated voltages. And UVing manually does not gain much in the long run when compared to the negative side affects that may (or may not) arise. I'm just sayin'...

:):D:laugh::good:
[Samsung Galaxy Nexus] gianton:
GPS on r356 is awesome, I got lock of 7/7 sats in a few secs, running AOKP Roman 1223 build. Tested this morning for about an hour with iGO Primo.
[Samsung Galaxy Nexus] whitedragonz83:
Yep. 50-75 mV savings is near meaningless basically for screen on time since the screen uses so much more. Maybe the lowest frequency undervolted as low as possible would benefit a little for idle time when there is a wake from deep sleep. As then the CPU starts to be a higher percentage battery drain.
[Samsung Galaxy Nexus] yellowdie:
Exactly. When we were first testing 192MHz, I was very much in favor of super UVing that freq because it was designed to be a low-batt consumption idea. But when we finally concluded that it wasn't worth the occasional lag and 384MHz was just fine, then I stopped UVing it manually. Because I know that 384MHz can definitely go below SR's bottom level of 830mV, I would be okay with manually pushing it lower; but I still don't. Again, you're gonna gain maybe 10 mins. Yippee! It's just not worth it to me to have people complaining (I almost used the B word, but I don't swear) about kernel issues that are CLEARLY THEIR fault. That's my point. People need to stop breaking stuff and then giving Franco a hard time about it. If you're UVing, I don't give a crap if you get a SOD/reboot/freeze. It's your own fault! lol. Okay, I'm done with my rant now. </rant>
[Samsung Galaxy Nexus] llevo3:
OK, here is what I got with r356: 384/130,5 interactive/cfq/westwood, hf1036/ibf729, osm0sis UV (1036@1075)

I run Classic Stability Test for 30min, everything's :good:

but in Scaling Stability Test I got reboot at 1728, since I don't use those frequencies, I'm pretty satisfy with 356

no SODs so far, I'll see about battery life, but I assume it'll be OK.