yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] A.C.Sanchez:
@Jackie_Jagger yes the avoided poor connection is exactly the wifi behavior I'm seeing. No clue if its ROM or kernel.
[Samsung Galaxy Nexus] peikojose:
Thanks for your answer.

Let me clear the commands:

fasboot erase boot

fasboot flash boot francokernel.img

right?

Will I loose any data changing kernels? From stock to franco and from franco to stock? Should I make a nandroid before?

Does CM10 uses franco kernel?

Best regards
[Samsung Galaxy Nexus] Puzzlegirl:
Go into Settings - >Wi-Fi - Advanced and uncheck 'Avoid poor connections'.
[Samsung Galaxy Nexus] jcmm11:
No need to fastboot erase first.

No, you won't lose data flashing kernels.

Making a nandroid is never a bad idea, just in case. (Better safe than sorry since sometimes s..t happens, even though it shouldn't)

For CM you need to wait. Franco needs to modify his ramdisk to make it compatible. Should be the next release, I believe.
[Samsung Galaxy Nexus] Timmyfoxeh:
I may add that anything below 200ish washes out the colors and make the grays dull and undersaturated..

Too much bias to cyan/magenta.. Also brightness is waaay too low and saturation washed out

Pretty decent, but blues and contrast is way over the top and there's a hint of yellow/green. Trinity set to -5 and blue multiplier to -5 made it better. I might stick with this for the time being...

Too dark and too much magenta-tint

That said, anything next to my LG IPS monitor, any setting looks awful..

On another note, I found that restoring color control profiles from the latest version of the app doesn't work for me!
[Samsung Galaxy Nexus] A.C.Sanchez:
Thanks but it is unchecked. That appears to be the bug. Must be ROM related.
[Samsung Galaxy Nexus] skinniezinho:
Just "flashed" the R335 kernel, stock rom, let's see how it goes.

Franco did awesome job in LG P500 and Nexus S, so I hope to be the same or better with this device (I am kinda new to it, but I am fairly impress, even with stock roms (no stock rom last more than 1 week in my previous androids).
[Samsung Galaxy Nexus] Puzzlegirl:
Maybe, I had to turn it on and off and turn off Wi-Fi optimisation but I haven't had any problems with it since flashing MoDaCo ROM.
[Samsung Galaxy Nexus] M3drvr:
Since 328 I've been experiencing wifi dropouts all of the sudden. It'll just drop the wifi and then10 seconds later reconnect to the same wifi network. Anyone else get this? No reboots, just drops the wifi connection. And "avoid poor connections" is unchecked. Tried re flashing the kernel. Didn't seem to help. Been running same rom the whole time too. Even before the dropouts started happening I was running same rom.
[Samsung Galaxy Nexus] peikojose:
Thanks. So I can flash it over my stock 4.2.1 with no problem.

What is the fuzz about the color? does it change the color of the screen?
[Samsung Galaxy Nexus] marcocsh:
r335 is stable and lightning fast on PA 2.99-6!:thumbup:

A candidate for M7?
[Samsung Galaxy Nexus] OMFGNuts:
No way

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] peikojose:
What would happen if stock android 4.2.2 (new teoretical version comes out)..

What would happen when I flash the new version .zip from recovery? Will I install stock kernell and will I have to install franco Kernell again?

best regards.
[Samsung Galaxy Nexus] kyokeun1234:
Yes
[Samsung Galaxy Nexus] peikojose:
Well thanks for all!

I flashed the kernel and everything went as expected.

I have the boot.img from the stock rom just in case.

Where should I see benefits?

I don't see anything wrong with the screencolors btw!

Best regards.

PD: Now I see the color problem, screen seems too blue.. How can I use the settings you were discussing before?
[Samsung Galaxy Nexus] osm0sis:
Haha no, still definitely a fair amount that Google broke that Franco probably wants to fix before he's ready to go milestone. Boss man has been known to be a bit of a perfectionist when it comes to milestones.

Personally I was seeing too much weird **** with r335 so I went back to r328 and I'm finding it markedly better at the moment.
[Samsung Galaxy Nexus] joaquinf:
For me r335 has been good performance and battery wise. No weird stuff yet. The only thing is that i haven't find that sweet spot with the colors. What kind of weird *** you had with 335?
[Samsung Galaxy Nexus] osm0sis:
A couple freezes requiring battery pulls. Wifi drops that wouldn't come back. Cell signal drops. Things like that. I didn't like that the 1228MHz slot is using the same voltage as 1305MHz by mistake (no matter what you set it to), then add the color stuff on and it's just enough to make me roll back since I need a stable phone for the next couple days for work. :(

Edit: :laugh: Spoke too soon! Time to try r340. Thanks franco! ;)
[Samsung Galaxy Nexus] franciscofranco:
r340 is out:

* CM10.1 should work now with this kernel

* Colors **** fixed

* Re-coded the freq table from stock driver, there were some weird **** coming from that. Now 192MHz, 537MHz and anything above 1228MHz is NOT calibrated by Smartreflex

* Some fixes here and there
[Samsung Galaxy Nexus] Khizar:
agreed 328 is better than 335

Edit- just saw that r340 is out, will give it a go
[Samsung Galaxy Nexus] kyokeun1234:
Hopefully this fixes some network issues, freezing and problems here and there that I had trouble with this kernel... Love your kernels BTW ;)
[Samsung Galaxy Nexus] osm0sis:
**** yeah 192MHz hardcoded. Time for some serious battery savings for the userbase once you put in screen off min with 192MHz as the default. ;):D
[Samsung Galaxy Nexus] yellowdie:
Did you manually UV 1305 and 1420 at all or just leave them?

TOTALLY agree!!! :D
[Samsung Galaxy Nexus] momomok:
Just noticed that FKU 8.1 always download kernels to storage/emulated/0/, ignoring the custom path that I have set...

Tried clearing FKU data, doesn't help.

Anyone?
[Samsung Galaxy Nexus] whitedragonz83:
Did you disable voltage adjustments? Can't do any undervolting with your app.
[Samsung Galaxy Nexus] simacai:
same here, never mind.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
New FKU doesn't recognize r300?

View attachment 1532000

View attachment 1532001
[Samsung Galaxy Nexus] joaquinf:
First impressions of r340

Colors are back!

Everything seems to work fine

No weird bootloops or random reboots

Buttery smooth as usual

I'm exhausted so im going off to bed. See ya guys tomorrow. Thanks for the update francisco

Take care
[Samsung Galaxy Nexus] kyokeun1234:
can flashing a kernel interfier with supersu allowing apps root permission? Because after the install, I don't see the root access pop up whenever I launch the root app (Trickster for ex) and when I try to do root action, phone just reboots. Any ideas?

Edit: ignore. I've fixed it by reflashing my ROM. Go Franco!!!!
[Samsung Galaxy Nexus] era_:
same too, can't config the voltage
[Samsung Galaxy Nexus] Khizar:
just flashed r340 and keep getting random reboots..had to do a battery pull, phone was unusable
[Samsung Galaxy Nexus] osm0sis:
Yeah, something not quite working with the new voltage table and the interface. Both /sys/class/misc/customvoltage/mpu_voltages and /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table are empty. Also 192MHz still shows as 830mV in Device Monitor so I don't think it being removed from SR quite worked either.

@franco: Not sure if it's worth anything to you now but I posted up a kmsg from r335 after a random weird reboot earlier today - http://xdaforums.com/showthread.php?p=34923341#post34923341

When did it reboot? Try it again but uncheck "set voltages on boot".

New 8.2 feature request: Auto-flashing should change the setting ʺset voltages on bootʺ to off, to help avoid upgrade woes if the voltage table changes. ;)
[Samsung Galaxy Nexus] franciscofranco:
Sorry guys, re-download r340 please, I did a little typo, but I fixed it, voltages are good to go.
[Samsung Galaxy Nexus] Khizar:
no more random reboots?
[Samsung Galaxy Nexus] franciscofranco:
I never had or have random reboots. Just try it ;)
[Samsung Galaxy Nexus] Khizar:
right after boot it kept rebooting and then when i tried to go to recovery the second time the phone froze and started rebooting again.. so i did a battery pull booted into recovery and flashed r328.

---------- Post added at 09:06 AM ---------- Previous post was at 09:05 AM ----------

do you recommend clearing FKU apps data before flashing? is it possible that cuz i dont go back to default settings before flashing a new version of the kernel that can cause issues?
[Samsung Galaxy Nexus] franciscofranco:
I dont wipe anything ever lol
[Samsung Galaxy Nexus] osm0sis:
Well we just saw that the voltages can get transposed if you leave "set on boot" enabled which can cause issues if you have custom UV set and franco alters the steps of the voltage table.

I usually wipe just to see what's changed with the defaults. But it's definitely the safer way to go as well. :)

---------- Post added at 12:34 AM ---------- Previous post was at 12:21 AM ----------

Speaking of which, Franco, the new default voltage for 1.8GHz is too low. It becomes unstable for me at 1405, so I wouldn't want it lower than 1425mV to be on the safe side.

And I think you could push 192MHz down at least to 750mV safely. Most can run 725mV so 750mV should be well within the safe zone. :)

Otherwise, this build is so far so very good. The best yet, and feeling snappy as hell. :good::D
[Samsung Galaxy Nexus] momomok:
flashed the revised r340, everything is fine

voltages are adjustable again in FKU

BTW, I noticed the default "input_boose_freq" becomes 537 in both r340, is this intended?
[Samsung Galaxy Nexus] osm0sis:
Yup. Been that way since r300 I believe. ;)
[Samsung Galaxy Nexus] franciscofranco:
Yes thats correct. 192MHz goes down to 800mV, I won't lower it anymore, there might be some weird bad quality hardware GN, I don't wanna push it.

I'll upload r342 now, I had another typo as well that I had to see fixed.
[Samsung Galaxy Nexus] franciscofranco:
There r342.
[Samsung Galaxy Nexus] gummie:
Same changelog? Just fixed typo and other r340 stuffs?
[Samsung Galaxy Nexus] kyokeun1234:
Basically.
[Samsung Galaxy Nexus] franciscofranco:
This is the changelog:

r342:

* Increase voltage on >1,4GHz frequencies for stability

* Lower 192MHz a little bit

* Fix an ugly bug introduced on r340
[Samsung Galaxy Nexus] Khizar:
yeah i think i will clear the apps data and then flash r342 and see if that fixes the issue
[Samsung Galaxy Nexus] jackpham:
Pls add Vietnamese into FKU (translated by me).

Tks!
[Samsung Galaxy Nexus] osm0sis:
r342 is amazing. The couple games I was seeing lag in don't have it anymore. :D

Also my voltages (which were the same all along since like r2xx) now seem stable again where they haven't in the last few builds. :good:
[Samsung Galaxy Nexus] Khrushy:
342 flashed. Haven't had time to play with it at all (at work atm), but seems all good so far.
[Samsung Galaxy Nexus] Hungry Man:
Is there a way to view changelogs in the app? And is there a way to save voltages without applying them at boot?
[Samsung Galaxy Nexus] osm0sis:
Not yet for the changelogs, but I think it's something Franco has said he'd like to add back in.

Negatory for just saving the voltages, it overcomplicated the app too much to have both that and set on boot. All the other areas of the app revert to defaults when you turn off their set on boot functions, so it's also more consistent this way.
[Samsung Galaxy Nexus] Khizar:
if you dont mind could you post all your settings? i would like to compare them to mine, you could PM me if you dont wanna post in the thread.. Thanks
[Samsung Galaxy Nexus] osm0sis:
Sure. Happy to post my franco.Kernel settings here for anyone who wants to try them. I'll keep these up-to-date if I change them. :)

These are my f.K settings, my DirtyV settings can be found here.

The following voltages are just as a reference. DO NOT enter them; your device may not be able to handle them this low, causing freezes and reboots. They are here so that people can compare their stable voltages after following the UV guides linked below, to see how our devices compare. Every device is different, so again, DO NOT enter them.

There are some battery savings from UVing but they aren't extreme. If you do not know how UVing works and/or you can't/won't read to properly build your own voltage profile, then just stick with the defaults Franco has already UVed. If you do still want to learn to UV then, once again, everyone should build their own voltage profile for their own device. Read this, this, this, and this for starters on UV methods. You don't know how your device will do until you learn and try.

As a sidenote, if anyone else wants to share their voltages for comparison the easiest way is to copy the contents of the 3 voltage files (mpu/iva/core) in /sys/class/misc/customvoltage/ - they look (almost) exactly as the sections above.

Fsync on just in case anything ever happens I want my data protected. That said I do disable it temporarily if I ever want a bit more performance in an app or game. SR is hardcoded disabled in the latest builds.

The other thing worth noting is I set my color settings on boot with an init.d script. Doing it that way you can end up with a completely different result from the same values. The contrast, blacks and colors are much more natural. Also it's seamless which is nice; they take effect during the Google logo. Attached is my init.d script for that. Alter it to your own color settings, remove the .txt extension, push to /system/etc/init.d/ and set the correct perms; rwxr-xr-x (chmod -R 755 /system/etc/init.d in Terminal Emulator).

900colorsettings can be found with my other init.d scripts (from Franco Dev Team), here: https://s.basketbuild.com/filedl/devs?dev=osm0sis&dl=osm0sis/scripts/900colorsettings

Note: On my new replacement screen, setting the color multiplier too early in the boot (any time before the boot animation) made everything look dark, oversaturated, uncontrasted and dusky; basically the opposite of the way it used to work on my old panel. Adding sleep 2; before that line in the init.d script fixed this, so experiment if your panel is more like my new one, and the init.d as-is after you put in your settings makes it look worse.

[ New init.d script with my new colors. I need the sleep 4 because of my problem in my "Note" above, so comment it out if you don't need it, it will make it look worse. Previous download counts were 1880, 646, and 307. Thanks everyone! ]
[Samsung Galaxy Nexus] franciscofranco:
Changelogs of nightlies come in 8.1.1, just finishing it before pushing.
[Samsung Galaxy Nexus] GIKE:
still not work on cm 10.1 based roms, right?
[Samsung Galaxy Nexus] franciscofranco:
Thank you so much!
[Samsung Galaxy Nexus] franciscofranco:
It works on CM based roms since 340, its written one or two pages ago in the changelog.
[Samsung Galaxy Nexus] osm0sis:
Franco, above is my proposal for the updated Share settings. ;)
[Samsung Galaxy Nexus] franciscofranco:
Do you know why it looks different setting it up on init.d rather than from the bootservice in the app? I got not clue.
[Samsung Galaxy Nexus] franciscofranco:
Yes I'll work on that for 8.2, need a few days without coding during the next week so I can actually sleep.
[Samsung Galaxy Nexus] osm0sis:
Beats me, but I know if you set them during the Google logo it turns out great, and if you put a sleep 5 so it does them during the boot animation it makes it go crazy purple like the trinity contrast/omap gamma is jacked up. Not setting them during boot and and just doing it all from the app has it somewhere in the middle. I think that was one of the first questions I ever posted in this thread, so.. long-time mystery. ;)

Awesome. I just went back and added TCP CAA in there too. But definitely take some time off. You deserve it and the kernel's in a good place now again. r342 is very much back on track. :D
[Samsung Galaxy Nexus] J-Hop2o6:
+1. I had to edit the file to adjust to my values. But what is acl inside the file? If it's CAB, does "1" = enabled?
[Samsung Galaxy Nexus] osm0sis:
That's a big 10-4. :good::)
[Samsung Galaxy Nexus] J-Hop2o6:
Thx. Will set that to 0 to disable ;)
[Samsung Galaxy Nexus] Khizar:
tried using your setting.. got half done setting the voltages and thats when phone started rebooting now it keeps freezing and then rebooting, not sure if it the kernel or your settings.. i will got back to r328
[Samsung Galaxy Nexus] osm0sis:
It's the voltages. Your phone likely can't handle them as low as mine can. You probably had set on boot checked again too. Never set on boot until you know they're stable. Since you were surprised that a freeze could occur while setting voltages I'm going to recommend you don't UV until you've read a bit more about it. Search the thread for a post by me where I quote rogersnm (so use his name as the keyword), it explains how to UV.

Stay on r342, it's the first build from the JB4.2 branch that I feel is legitimately stable. :)
[Samsung Galaxy Nexus] Khizar:
yup the problem was your settings phone froze and started rebooting on r328 as well.. i am back on r342 with my old settings and everything feels fine so far didnt go to r340 cuz i was getting reboots on that with both stock and my custom settings
[Samsung Galaxy Nexus] osm0sis:
Yeah who knows, maybe your phone can't handle 1536 max either. Some can't, I suppose. Fairly confident it was just the voltages your device couldn't handle though, they're the obvious culprit.

The keyword search for rogersnm in posts by me didn't show it, (even though his name is clearly in there) - so here's the link to the mini UVing Guide:

http://xdaforums.com/showpost.php?p=31096831&postcount=26214

Give it a read. :) :good:
[Samsung Galaxy Nexus] Khizar:
i am pretty sure it was the voltage that caused the phone to freeze, i tired you settings again and when i tried setting voltage the froze started and then phone rebooted.. i cleared the apps data and am using stock settings right now..

btw these are the settings i use

http://xdaforums.com/showpost.php?p=34563397&postcount=1583
[Samsung Galaxy Nexus] Shadow-Nexus:
Os I just tried your settings and while setting the voltages I got a reboot but when I tried again it all worked perfectly!

By the way thanks for uploading your script
[Samsung Galaxy Nexus] osm0sis:
Yeah, though it's working you definitely have a borderline voltage. The one that froze is the one that needs to be raised... I'm going to have to go back and put a disclaimer on my settings post now since everyone's just trying them without knowing how UVing works.. :rolleyes:
[Samsung Galaxy Nexus] Khizar:
lol no luck here.. tried the settings 3 times and phone froze and then reboot all 3 times.. i guess tweaking the voltages would have worked but i ended up clearing apps data and am using stock settings atm

---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------

read the post you linked.. will give it a try later
[Samsung Galaxy Nexus] Shadow-Nexus:
I don't remember on which one it froze so I'll just wait to see if it happens again!
[Samsung Galaxy Nexus] osm0sis:
K... "disclaimer" added. :eek:;)
[Samsung Galaxy Nexus] gautam_nexus:
Anyone facing low call volumes after flashing 342?
[Samsung Galaxy Nexus] Khizar:
nope.. call volume is fine
[Samsung Galaxy Nexus] gautam_nexus:
I could hardly hear someone over the phone after flashing 342...I was using trinity a5 before...never faced such issues
[Samsung Galaxy Nexus] Khizar:
i just got off the phone like 5 mins ago and call volume was fine for me, i havent had any issues with volume on any kernels i have tried
[Samsung Galaxy Nexus] yaatzek:
Maybe some app is messing with volume?
[Samsung Galaxy Nexus] garuhhh:
I've had a reboot with r342. My phone is just sitting still, charging. BLX is at 90.

192MHz/1228MHz, stock voltages. everything else is stock.

I have attached the last_kmsg.
[Samsung Galaxy Nexus] osm0sis:
There are a bunch of these in your log right before the "warm software reset":

omap_temp_sensor_enable:get sync failed

Interesting, I wonder if that is related to all the sync errors I was seeing in the kmsg from my reboot on r335:

omapdss DISPC error: SYNC_LOST, disabling LCD

omapdss DISPC error: First SYNC_LOST.. ignoring
[Samsung Galaxy Nexus] usmankh10:
Nfs mw still lags on franco 342,this issue exists since milestone 6 ,is there any fix available ???
[Samsung Galaxy Nexus] osm0sis:
Search the thread for "nfs"; someone already posted a fix for that game's crappy coding.
[Samsung Galaxy Nexus] jorgen2009:
Working perfectly on my CM10.1 nightly. Thx for supporting this!
[Samsung Galaxy Nexus] Khrushy:
Osmosis: Are you currently UV'ing the GPU / IVA at all?
[Samsung Galaxy Nexus] osm0sis:
Nope. Haven't been cocky enough to mess with those yet since it's harder to tell when you've put it too low.
[Samsung Galaxy Nexus] clarkey1269:
Another bug, when downloading a 4.2 kernel and you rotate the photo (screen rotate) it stops downloading at FC the app
[Samsung Galaxy Nexus] tobitronics:
Been using 335 for 2 days and for 2 days in a row my phone was off when I woke up after a night of charging, resulting in my alarm not going off ..... Rest is ok.
[Samsung Galaxy Nexus] shawnaye:
R342 is hands down the best 4.2 kernel for me do far.

Thanks for all your time and effort franco!
[Samsung Galaxy Nexus] ghettojack:
Do you know how much we love you Franco? <3
[Samsung Galaxy Nexus] jackie_jagger:
Holy crap, r342 is definitely the best kernel yet.

It has gotten rid of any micro lag and I swear I'm not seeing things when I'm saying it is as smooth as 4.1.2 was.

Thanks a lot Franco :thumbup:
[Samsung Galaxy Nexus] franciscofranco:
This thread is 1 year old... damn... almost 5 million views and 40k replies... damn, thats all I can say right now :)
[Samsung Galaxy Nexus] Vangelis13:
Yours was the first kernel I flashed once the phone was rooted. Donated + bought the app as well. Things have come far & changed a lot since. You're not even on the same continent anymore..! :)

All the best over there young man, you've deserved every single thing that has come towards you. Keep up the hard work. Some day we'll be proudly saying that we were flashing your kernels when you were starting up..
[Samsung Galaxy Nexus] tetrakinitis:
Because you deserve it. Respect :thumbup:

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] garuhhh:
Had another reboot, just now. got the last_kmesg, though I think it's very similar with the previous one :(

My phone just sitting still, plugged in the PC, 192MHz/1228MHz, everything else is stock except BLX (90).

I'm seeing the same errors again before the shutdown(?):
[Samsung Galaxy Nexus] garuhhh:
the smoothness of the kernel is very good for me! haven't experienced any lag at all with normal usage. My issue are these recent reboots.

I'm still sticking with r342 though :D
[Samsung Galaxy Nexus] Khizar:
gotta agree with all these ppl r342 is the shiz.. gotta no issues with it and running it with stock settings
[Samsung Galaxy Nexus] Timmyfoxeh:
r342 is amazing!

Though restoring color profiles still doesn't do anything as of v8.1.1 of the app...
[Samsung Galaxy Nexus] malaroth:
Thanks for the thread link fixes in app Franco not to mention churning out top notch kernels. Just flashed latest nightly and will check back throughout the day...

JBSourcery 4.0 + Franco nightlies! Sourcerized to the max! Keep the magic alive.
[Samsung Galaxy Nexus] shawnaye:
Running 342. I tried to unlock my phone and the touch screen was unresponsive.

Had to do a battery pull. Anyone else faced this problem?
[Samsung Galaxy Nexus] hotnikkelz:
I have a noob question. Uhm is there a way to see the changelogs for the nightlies? Since the redesign of the franco app I am not sure where to find it. I think i used to get a pop up window before i flash, or it was in the overflow menu somewhere....sorry if this has been asked before or the answer is obvious :o
[Samsung Galaxy Nexus] indbeegee:
Also had this issue several times with 335. Are you using PGM? I was. Wakeup with swipe ok, then touchscreen unresponsible.
[Samsung Galaxy Nexus] shawnaye:
Exactly the same issue. Weird seeing that pgm is fine but not afterwards.

I never had this issue with prior kernel variations though.

Gonna try reinstalling pgm.