yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ro_explorer:
About this gamma stuff.

Someone posted earlier that whites are not affected and I think he's right. The gamma correction is affecting everything in between black and white but not the white itself. That would be the "hue" settings.

And my screenshots posted 2 days ago with two phones side by side, I did it again today and it seems that the slight color difference s is coming from the screen itself, no matter what values I choose for gamma.

And back to the ideal gamma settings: is all a matter of taste.

Me for example, I have the PC monitor at work and also at home, as well as my lcd tv, with a natural warm image. This is making me to want this warm color feeling on my phone as well. An I'm achieving this by slightly increasing the red and dimming the blue ... therefore 2 0 -5 I was proposing before (currently 2 0 -4).

For the people who like the cool temp on their images, then the default Franco's settings might look nicer (-4 0 5).

However, giving the fact that the screens themselves have a more red/blue tint, the ideal settings for each one of you might be different .. therefore, only by trial and error you will achieve that nice looking display :) ...
[Samsung Galaxy Nexus] Shetlander:
Franco

Is it possible for you to add in to the overclock setting the ability to change the I/O scheduler. Then I would be able to get rid of another program. If not is there another way to change it manually so it sticks on a reboot.
[Samsung Galaxy Nexus] afilopou:
Franco regarding ntfs support, i can only see the files in my external ntfs flash disk.I have error when trying to play them.Any workaround for this?

Thanks and congrats for your work
[Samsung Galaxy Nexus] franciscofranco:
No idea I dont have an external drive to test that.
[Samsung Galaxy Nexus] ChongoDroid:
Franco.. I am thoroughly, enjoying this kernel lol.

I find the power used when the screen is on is less too. My phone runs cool even in navigation mode... it feels like a new phone buddy.

Bixie+franco12 on a fresh install is a buttery bacon lathered googletron
[Samsung Galaxy Nexus] clefster:
You should be able to use a simple USB flash drive. Do you lack the required cable? They can be had on ebay for a couple of dollars, FYI.
[Samsung Galaxy Nexus] franciscofranco:
Already ordered, still waiting for delivery.
[Samsung Galaxy Nexus] afilopou:
If you need the logcats when mounting and unmounting the ntfs disk let me know.

ps i have same issues with faux123 kernel
[Samsung Galaxy Nexus] gokpog:
I'm tethering my phone to my tablet via BT DUN quite regularly and I'm experiencing very slow, almost unusable slow tethering speeds when the display of the phone goes off with nightly #12. When I switch the display back on, the speeds resume to normal. Any way around that behaviour other than leaving the phones screen on?
[Samsung Galaxy Nexus] franciscofranco:
No, that is caused by the power management policies of the Wi-Fi. Plug it in and leave the screen on.
[Samsung Galaxy Nexus] gokpog:
Thanks, so that shouldn't be a problem with tethering my 3G connection to the tablet via bluetooth? That would minimize the issue.

I have to confess that I changed to your kernel only recently and have so far only tethered my wifi connection as a test.
[Samsung Galaxy Nexus] bradm23:
Just curious, why would you tether your wifi when your tablet could just pick up the original wifi signal?
[Samsung Galaxy Nexus] gokpog:
"so far only tethered my wifi connection as a test." ;)

What I meant was, I tethered my wifi connection to test bt tethering. You are right, what I really need to work is 3G tethering via bt. If that works without slow down than I'm happy.
[Samsung Galaxy Nexus] to_panki:
The best kernel

Enviado desde mi Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
Yes I wouldn't be surprised if it was a voltage issue to be honest, I really don't know, everything runs fine with my device, I haven't done any whacky stuff since r318 thats why I'm so surprised. Stock kernel is a bit plagued with ****, so I wouldn't be surprised if some of this crap was caused by it as well.

And if anyone is getting random reboots, please, PLEASE I need last_kmsg logs, otherwise theres nothing I can do as I can't seem to find a culprit.
[Samsung Galaxy Nexus] osm0sis:
Also are people with the issues all running Xylon or perhaps PA? I'm on stock with no issues since r327.
[Samsung Galaxy Nexus] Hungry Man:
Running the latest Eclipse and the latest Franco. No issues so far.
[Samsung Galaxy Nexus] wolf911:
yes, my bad and fixed
[Samsung Galaxy Nexus] jcmm11:
It was a SOD. Booted, got to login screen. Screen went black. Needed to pull battery. Rebooted. Boot loop. Gets to login screen, then reboots. Pulled battery again. Booted into recovery.
[Samsung Galaxy Nexus] Khizar:
if xylon is the cause that would be weird.. i have been using franco with xylon ever since it was released and never had issues.. btw on the phone right now so cant test your fix but will try soon
[Samsung Galaxy Nexus] osm0sis:
Any chance in migrating from a build with a 1228MHz step to a build without one that the "Set voltages on boot" in the app would transpose lower voltages onto the higher frequencies? That would be an instant issue for the weaker siliconed among us, and would present like what we're seeing here.

I agree. JB 4.2 in general was a major mistake. Google really **** the bed with bugs, breaking features, and not following their own design guidelines for system apps. I wouldn't be surprised if their kernel source is also riddled with bugs.

---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------

Try this please: :)
[Samsung Galaxy Nexus] Khrushy:
Xylon here, but other than one SOD overnight on 325 I've had no issues when testing 326/7/8.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jcmm11:
I'll try playing with 328 again tomorrow sometime. And I'll try getting a log. Think I figured out how I can do it.
[Samsung Galaxy Nexus] b1337:
um no
[Samsung Galaxy Nexus] rodnar77:
328... Running for 3 hours. Stock 4.2... Didn't touch stock except I'm on Westwood and deadline. But I haven't change that since pre 4.2
[Samsung Galaxy Nexus] franciscofranco:
Hmm... I wouldn't be surprised if thats what's happening, but theres nothing I can do about it.
[Samsung Galaxy Nexus] Edrill:
Just did that and r328 hasn't rebooted so far! Even received a call without any problem! I was on r327. Cleared the fKU app data, rebooted into fastboot and flashed r328 and so far so good!
[Samsung Galaxy Nexus] differentstyles:
After stuck on boot screen I've made a complete fresh install of the xeylon rom and it is working now.
[Samsung Galaxy Nexus] osm0sis:
Right on.. :good: So maybe a little bit of Column A, and a little bit of Column B for what was going on for everyone. Some have f.Ku app settings carrying over they need to clear, and others just have a ROM conflict and need to reflash it. :cool:

Can anyone else who was having issues reproduce stability with one or both of these possible fixes?
[Samsung Galaxy Nexus] EnricoTFYKD:
Don't know if this can help, I'm on r300, stock 4.1.2, but I have experienced most of the weird stuff described in the last pages (and related to 32x) after that I tried to undervolt further my CPU. Voltages that were stable when I set them manually after boot, were causing constant freezes and bootloops if I let fku set them on boot (bootanimation ok, then PIN enter screen, then when fku set voltages, bam - stuck). Right now, I've raised them a little and moved to SetCPU to Set Voltages on boot [so that I can always flash the CPU safemode .zip if I get stuck again], and I'm fine. SR disabled, fsync ON.

[BTW, this happened after the last fku update, but I really think this should be unrelated.]
[Samsung Galaxy Nexus] skinnypupp:
I am using the latest Kernel Updater from the Play store, and it is only showing nightlies up to version 196

Is there a special version for the 4.2 kernels?
[Samsung Galaxy Nexus] osm0sis:
Sometimes certain voltages are stable for an idle system but once a bit of load gets put on it they crap out. In your case that would be boot. Best way to test is to set performance governor then change the max freq to the one you want to test. Lower its voltage 25mV at a time until it instantly freezes/crashes then use the last one that didn't freeze, then do something load intensive like running a game. If it's still stable then you should be good to go.

After that and you switch back from performance there can still be some instability just based on it switching from one frequency to another. You may have to lower your max until the instability goes away to try and narrow down which is at fault.

Also never set them on boot until you know they're stable.
[Samsung Galaxy Nexus] EnricoTFYKD:
I've had those voltages run perfectly stable for three days before deciding to set them on boot. :D And I had run Stability test, Games, music with screen off, benchmarks, phone calls, videos, browsing, texting, everything. Probably some crap in the app or in something else. BTW, I'm just waiting Google to fix all the weird bugs they stuffed into 4.2 and then I'll do a clean install (with Franco.kernel, of course).
[Samsung Galaxy Nexus] shawnaye:
Wow, i flashed the zip of r328 at like 12pm, my phone kept on rebooting non-stop.

reboot only occurred AFTER franco.kernel app was granted SuperSU permissions.

so i didn't have a computer, all the way till now.

i'm running app version 8.07 btw.

now i gotta do a clean flash of rasbean again. cause somehow everything got deleted.

and i tried clearing app data and stuff, but to no avail.

reboots still occurred.

and i can't grab any log files, phone is practically dead now.
[Samsung Galaxy Nexus] anonymous2183:
Hi, Franco

May I ask the major difference between r318 and r328, the PGM aka slide2wake for Nexus works with r318, but with r328 got reboot immediately.
[Samsung Galaxy Nexus] safendi:
wich setting do you use in governor control for better perfomance? input_boost_freq is better to 527, 1036 or 1305?
[Samsung Galaxy Nexus] gianton:
PGM works fine on r328 for me.
[Samsung Galaxy Nexus] mulerokeh:
lucky me, i don't have any reboot or SOD since 318.. :)

great kernel!!

xylon 006..

Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
flashed r328 again and its working good so far, hope it doesnt start acting up again :good:
[Samsung Galaxy Nexus] waallen:
Just reporting in, I've jumped on the fk boat on the 325 release and never had a sod. Currently running 328.
[Samsung Galaxy Nexus] Controvrsy046:
Running r328 on stock 4.2 image and its insanely smooth even with widgets and 30 apps installed. The settings scrolls perfectly, much much smoother than the previous kernels.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] duduzinho15:
R328 is good for me no issues!
[Samsung Galaxy Nexus] safendi:
why when install the franco kernle updater i have reebot when applied the color setting during the start?

I have This problem with all your kernel
[Samsung Galaxy Nexus] Craxx:
After flashing 328 i get rebooted every time after system is up... so i recovered a backup with 318 and now it is ok. So i stay with 318 until the bug is fixed :(

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] tobitronics:
Are francos 4.2 kernels any good?
[Samsung Galaxy Nexus] mrfleetwood:
Flashed R238 and got never ending boot loop, reverted back to stock, wiped cache & dalvik, installed R238 and everything works fine.
[Samsung Galaxy Nexus] garuhhh:
I got a reboot while my phone is charging, sitting still. I got the last_kmesg.

running on r328, didn't do any changes with the voltages.

Here are the last few lines:

I could not attach the whole last_kmesg, so here's a dropbox link if ever you'll need it:

link

I will try clearing the cache of fkU. I flashed the kernel using fastboot.

EDIT: i just noticed my phone rebooted while near the 90% battery mark, I have always set my phone to stop charging at 90% in BLX. I'm not sure if that's even remotely related, but just reporting.
[Samsung Galaxy Nexus] kecinzer:
Latest AOKP, #328 no problems so far.
[Samsung Galaxy Nexus] stark_br:
Dont think so.

I'm on PA with 325 and had no issues at all.

Maybe when someone report a problem ( sod, freeze, reboot...) tell Franco what rom is up. Dont know if this helps, but its a start.
[Samsung Galaxy Nexus] Khizar:
read the thread or try it and you will find out
[Samsung Galaxy Nexus] lparcshinoda:
Flashed 328, got stuck at bootloops (hard reboot after bootanimation completion).
[Samsung Galaxy Nexus] osm0sis:
Try this:

Or this:
[Samsung Galaxy Nexus] kunalwanvari:
318 was sooooooooooooooooooooo perfect franco !!!!

325 327 gave me horrendous sods .. to the extent that i had to clear data and reflash roms !

and 328 reboooooots !

318 was perfect :)
[Samsung Galaxy Nexus] gianton:
Getting there... r328 is very smooth and no SODs/freezes so far!
[Samsung Galaxy Nexus] skinnypupp:
I am using 325 and tetherting and wifi hotspot do not work. Was this fixed in later versions, or should I see about helping troubleshoot the issue?
[Samsung Galaxy Nexus] shawnaye:
finally restored all my stuff back.

afraid to flash r328 though.

esp with some users still having feedbacks about reboots.
[Samsung Galaxy Nexus] mrfleetwood:
I just checked my kernel settings using the app and noticed that there are no dyninteractive governor anymore. Could that be the cause for these bootloops, app tried to use dyninteractive governor which is not there anymore?
[Samsung Galaxy Nexus] syncopy:
Not yet.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrisgtl:
#328 on Rasbeanjelly 23/11/12.

No problems to report, no SOD, no bootloop.

Thanks Franco.
[Samsung Galaxy Nexus] momomok:
Audio playback through headphone port on r328 is much flatter comparing to r325

Franco have you tweaked that?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] funkyblue04:
I'm finding Franco slow since 4.2. Phones can take a while to wake up and often. Becomes frustratingly slow and laggy.
[Samsung Galaxy Nexus] eng.stk:
First reboot problem ever with franco kernel, I'm on r328 :eek:

I tried 3 different AOSP builds, same problem: boots ok, enter PIN and unlock pattern, immediate reboot.

Reverted to r327 to have smooth sailing. Had no problems with r325 and r326 also.

Edit: cleared cache and dalvik as always
[Samsung Galaxy Nexus] kecinzer:
Try to disable PIN. I experienced many reboot issues was caused by PIN (on SIM card).
[Samsung Galaxy Nexus] Khizar:
been using r328 for the past 3 hours and no problems this time..
[Samsung Galaxy Nexus] sago62:
is normal that hotspot not work in r328? i'm on fnv 06....
[Samsung Galaxy Nexus] shawnaye:
yes. hotspot is broken for now.
[Samsung Galaxy Nexus] stark_br:
I'm on PA 2.99.3 and Franco's r328.

Its charging on usb and I fell its skipping some touches. And its not so smooth as r325.
[Samsung Galaxy Nexus] Edrill:
No problems for over five hours now on r328 after clearing the f.KU app data and cache before flashing r328. Running Xylon 006.
[Samsung Galaxy Nexus] Khrushy:
I've had 328 running for ~8 hours now without a hiccup. Very smooth, great WiFi strength, I'm a happy camper!
[Samsung Galaxy Nexus] simacai:
Almost tried everything to flash r328. Even flash and boot without fku installed. But none of them helped.

Now I'm a little jealous of you guys using r328 :rolleyes:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kizakiyuria:
get random reboot here,using r327 on aokp...little bit lag with default setting...:confused:
[Samsung Galaxy Nexus] Icecoldmeat:
Why did you delete the 1200 mhz step sir?
[Samsung Galaxy Nexus] shawnaye:
because 1300mhz and 1200mhz uses the same voltages :D
[Samsung Galaxy Nexus] Raijin:
The application has received a translation for my language, but I prefer to use it in English, the original language. Is there any way?
[Samsung Galaxy Nexus] Fenvarien:
+1

Although I'm thankful for the translation work, I would like to have an option to stay with the original language too.

GNex with franco.Kernel / MiNCO ROM v5
[Samsung Galaxy Nexus] Khizar:
you got the random reboot on r327?
[Samsung Galaxy Nexus] yellowdie:
Well sounds like y'all are havin' a blast. :)

I am running r328 and I haven't had any reboots or SODs with any of the >300 kernels. There are too many variables here that differ on everyone's phones. Some have SODs (phone doesn't turn on, just stays at black screen), some get bootloops and can't get in, some get reboots. Some are undervolting with FK.U, some are UVing with SetCPU, some are running stock settings. So to help paint a better picture (seeing as most of the people with issues aren't pulling logs), I made a GoogleDoc comparison sheet so we can all add our own setup and findings. Everyone go

HERE

and fill in your info. This may be able to help narrow down what's actually jacking things up. It's probably a local phone issue--my phone is running flawlessly and I've had every single version installed running stock settings. Feel free to add columns to the sheet with things that you think are different with your setup.
[Samsung Galaxy Nexus] osm0sis:
r328 slept overnight the best I've seen on f.K since the move to JB 4.2. 98% deep sleep, and 0.2%/h idle drain. No sleep of death, no hangs or reboots. Everyone make sure you clear f.Ku app data+cache before flashing r328. I've had zero problems since r327. A cache and dalvik wipe in recovery never hurt either. Keep up the good work Franco!

Edit: Great idea, yellow. :good:
[Samsung Galaxy Nexus] tuemdeluxe:
R328 also gives me a hard reboot right after start, sometimes even before I confirmed the pin. Mostly when Tasker is loading but it could also be something else in the background.

Clearing cache and data of fku doesn't help as well as flashing Rom again before the kernel flash...The download is fine, tried 3 different downloads of R328 but always the same problem. Weird that only some users face this issue. Maybe we have to wait for 329 :D
[Samsung Galaxy Nexus] 5nickers:
When will we be able to update our kernel for 4.2 direktly over the app? downloading it from the website and then flash it sucks a bit ;)

It would be great if its possible very soon :)
[Samsung Galaxy Nexus] kizakiyuria:
yeah,dunno where is my fault,using default setting and 5 apps in recent app, just changed color .:confused:
[Samsung Galaxy Nexus] :
Just figured I'd leave this bit of info here

I tried out the new jellybro cm10.1 build, and it runs great with stock kernel, but the instant I install FK r328 I get constant force closes and have to reflash the original kernel. Mostly its FCs related to NFC and phone? Anyway back on 4.1.2 with r300 till w.e issues there are between the two get fixed, this is just a heads up to stear clear of the cm10.1/FK combo for now and use a diff 4.2 ROM :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Can you add a column for flashing method please? Can't seem to do it off chrome on my phone

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Looks like someone did it. :good:
[Samsung Galaxy Nexus] yellowdie:
Done. Good thought. :)

EDIT:

:)
[Samsung Galaxy Nexus] G-DannY:
Please Franco give back dynteractive. It was the most lag-free governor for me.
[Samsung Galaxy Nexus] spupuz:
i also used it usually, why has been removed?
[Samsung Galaxy Nexus] RayGarden:
Due SOD's on # 326, i flashed #328 but, this one gave me constant reboots so i went back to stock Kernel for the moment
[Samsung Galaxy Nexus] yellowdie:
Guys with issues, again please go

HERE

and update it with your info. The part I'm most curious about is the second to last column about whether or not you have "Disable CAB" checked or unchecked in the color settings.

On another note, I just got back to work and this is where I really see the wifi strenght difference. Hooooollllllyyyyy cow! I normally get 1-2 bars (-65 dBm) at my desk, and these 3.4 wifi drivers are rockin' 4-5 bars (-45 dBm)! LOVE IT!

:):D:laugh::good:
[Samsung Galaxy Nexus] :
Getting the message when starting up the phone the system ui has stopped responding. This is on both r237 and r238. Flashed it via the zip file in cwr. Dalvik cache was wiped during both. I am currently on AOKP 4.2 preview for maguro 11\25 build. No random reboots so far anyways.

Thanks.
[Samsung Galaxy Nexus] gianton:
Wrong thread, you should've posted this at AOKP. Flash 1126 build it's fixed.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
That form is cool :D I was looking at it while someone else was inputting data...wild! LOL. Someone almost overwrote the column titles though :D

My WiFi is working awesome on r318, especially IMAP Idle...I'm scared to update :D

RF
[Samsung Galaxy Nexus] allbass:
Here it's ok on stock 4.2 rom
[Samsung Galaxy Nexus] ÜBER™:
I haven't been following this thread. :o Does the latest work with cm?

Sent from my Nexus 7
[Samsung Galaxy Nexus] aR_ChRiS:
All good in unofficial AOKP too.
[Samsung Galaxy Nexus] yellowdie:
Yeppers. Should work with any ROM, but r300 and below is 4.1 and above r300 is 4.2. :highfive:
[Samsung Galaxy Nexus] differentstyles:
Since this morning absolutely no problems with 328. Using xeylon rom and Francos default settings except max. 1036. I'll wait some days but battery seems to be extreme good for me.
[Samsung Galaxy Nexus] osm0sis:
Maybe.. maybe not..
[Samsung Galaxy Nexus] ÜBER™:
Thanks I tried the r313 and wouldn't boot. Will try the latest.

Sent from my Nexus 7
[Samsung Galaxy Nexus] rz32:
Anyone could help me configurating this kernel via franco kernel updater app? Or maybe there are any guide? Thank you in advance.
[Samsung Galaxy Nexus] ttabbal:
Reboot loop on 328 for me. Bigxie stock 4.2.

last_kmsg: http://pastebin.com/wvc3rjrx

The phone boots to the launcher fine, but reboots shortly after without any user input. adb pull was able to grab the kmsg before the reboot was forced.

I cleared data for the FK app before installing. Installed via FK app restore and reboot option.

318 runs great... No other changes made to the device.

------

Doing a cache/dalvik wipe in recovery gets me the expected "Android is upgrading" screen we all know and love. No forced reboots here yet...

Argh... checked logcat, it was PGM. I thought I disabled that before installing.

If anyone else gets stuck because of it, here's a quick fix if you're at a computer...

adb shell rm /data/data/net.ponury.pgm2free/files/ponury.ko

That will nuke the kernel module before the app has a chance to try to load it and panic the kernel. pffttttt.

Leaving the above to demonstrate troubleshooting for others. :p

Please give info people, the devs can't find things without that info.
[Samsung Galaxy Nexus] yellowdie:
Guys, that chart is looking great--keep it up. I think I may have something for you guys to test.

I get reboots if I don't unlock my phone in the first min after booting up and I've been testing this for over a month now and have been trying to fully lock down the issue. It has happened for me on multiple ROMs, multiple kernel versions, multiple FK.U versions. And I think I've narrowed it down to the CAB (Content Adaptive Brightness). From the chart, I see that everyone that has reboots after the phone powers up, has "Disable CAB" checked.

So let's do this. Everyone with reboots (the phone loads up, not bootloops) and anyone else who wants to test this: clear FK.U app data and reboot, and as soon as you hit the reboot button, don't touch your phone AT ALL for a few mins--it should power on the screen fine after a few mins. Then go into FK.U and JUST make this one change: open the Color Controls and check the box next to "Disable Content Adaptive Brightness" then reboot your phone and again don't touch it AT ALL. See if it reboots after a min or two if you don't touch it. Report back here the findings. I can replicate this exact scenario at any point without fail.
[Samsung Galaxy Nexus] cosmic76:
Hello everyone, I unfortunately with xylon and franco kernel r328 not modified i have reboots ... damn
[Samsung Galaxy Nexus] Puzzlegirl:
I can't reproduce this and I left it for 10 minutes before someone gtalked me and woke it up with everything working perfectly.
[Samsung Galaxy Nexus] yellowdie:
Cool thanks. You aren't having any issues at all, right? According to the chart, you look good to go.