yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] ryanbmw51:
Just gotta say real quick without reading the last 10 pages. This kernel is epic and if you're not using flashify you're missing out on some great innovation as well. Thanks FF love the kernels and the updater app.

I know where THANKS button is. Sent from the Nexus5.
[Nexus 5 Original Android Development] vomer:
$hit just got real! :good: :D

Move away google... franco is now in da house lol!

Btw [MENTION=3292224]franciscofranco[/MENTION] try DPI of 400 - it makes the device perfect!
[Nexus 5 Original Android Development] Shano56:
Forum rules linking to other forum rules? O.O man what has xda come to.
[Nexus 5 Original Android Development] xdviper:
Ohhhh mannnn, Franco got his phone. Enjoy. I can't wait for your magic man.
[Nexus 5 Original Android Development] brittonberkan:
Yup. Don't waste time trying out the stock kernel, your own is way better ;) thrilled to see what you'll get out of the devixe

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] zephiK:
440 is another great choice too.

Awesome. Will flash r9 when it's out :D time to make my self at home.
[Nexus 5 Original Android Development] Revthejedi:
It's happening!
[Nexus 5 Original Android Development] ChazzMatt:
It's long been an unspoken rule in many development forums, shouldn't need to be spelled out. For one, devs do NOT know when the work will be finished. They have their "regular" lives and work to do also. Franco can't say, "Color Control will be ready by Friday, November 15 @ 5am GMT."

If someone asks for an ETA and one is given, then what happens if that deadline passes? It's ready when it's ready.

So, YES it's a rule.
[Nexus 5 Original Android Development] sluflyer06:
Literally takes seconds to flash with fastboot sitting at my desk at work, is there something else flashify does besides flash that makes it innovative?
[Nexus 5 Original Android Development] dmmarck:
Well, avoiding using the USB port, especially one as apparently fragile as this (the plastic around it), is always a plus in my book.
[Nexus 5 Original Android Development] ryanbmw51:
Well since you are clearly smart enough to do it that way you surely must be smart enough to realize the benefits of the flashify process. You can do it on the go bro. We don't all have access to desktop setups all the time. Not like you do. Its new. Its different. It enabled me to do certain things in a way that was more convenient for MY lifestyle. I'll go out on a limb and say I'm probably in the majority on this one.

Thanks again Franco. Love the dev work as always.

I know where THANKS button is. Sent from the Nexus5.
[Nexus 5 Original Android Development] zephiK:
I don't think the USB port is fragile at all. My Nexus 4 never had that problem.

Flashify is cool but I think that person over exaggerated. It's just convenient to flash images without being at a computer. That's all.
[Nexus 5 Original Android Development] dmmarck:
I'm talking specifically the plastic around it. I posted a picture of a review unit with decent wear, with the wear circled in yellow. Metal wins against plastic.
[Nexus 5 Original Android Development] panart:
Agree 100%. No need for flashify when we are at a pc/laptop. Personally i only used it once and that was because i wasn't near my laptop.
[Nexus 5 Original Android Development] Bobtehblob:
Why all the fuss over this flashify business...? As far as I know, the latest pringles allows you to flash new kernels in img format via the backup and restore section. Just put the img in the Franco kernel backup folder and restore it via the app, simple :) I wouldn't be surprised if this uses a similar method to flashify it self!

Sent from my Nexus 7 (2013)
[Nexus 5 Original Android Development] franciscofranco:
Not even needed to do that, you can flash it from any directory in your /sdcard using the File Manager.
[Nexus 5 Original Android Development] Bobtehblob:
Didn't even know you could do that! Was so used to doing it via backup on the n4 :D

Sent from my Nexus 7 (2013)
[Nexus 5 Original Android Development] aLNG:
Can you share anything for me to get like that?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Artood2s:
Like this.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Langduscher:
I don't use it, but have read that is uses more juice than it saves.

I've read better things about the Qualcomm Dalvik & Bionik optimizations.
[Nexus 5 Original Android Development] shinesthru:
Sorry dude, you're not going to get support for that app in this thread. This thread is specifically for development of this kernel. Good luck.
[Nexus 5 Original Android Development] Bill Gamble:
http://xdaforums.com/showpost.php?p=49311209&postcount=4793
[Nexus 5 Original Android Development] droid@xda:
I was just reading that gamma app thread. I don't understand the fuss around it! Just flash back r31 for a time being if you really want it badly. That app has never worked for me reliably and never gave as amazing results as r14 of fk. I just wish franco enable color calibration with multiple presets in his own fku app as soon as possible. If I have missed anything regarding this, kindly enlighten. Its hard to keep up with this thread!
[Nexus 5 Original Android Development] bigknowz:
music stutter

Do you mean on the tube/subway? If that's the case, you should go into airplane mode underground. Can you try adjusting RAB?

echo 1024 > /sys/block/mmcblk0/queue/read_ahead_kb

I made a script to switch between default and 1024 if you prefer: http://xdaforums.com/showthread.php?p=49318696#post49318696
[Nexus 5 Original Android Development] franciscofranco:
Working on it, beta FKU should be out today with it enabled and working, also if I'm confident enough the display app will be pushed today with it as well. No promises though.
[Nexus 5 Original Android Development] Jeremy:
franco, are you still working with PA team?
[Nexus 5 Original Android Development] franciscofranco:
Yes - not pushing any userspace code though, I have no time.
[Nexus 5 Original Android Development] franciscofranco:
Thermal throttle code was made better for the next release, I trust that won't happen anymore.
[Nexus 5 Original Android Development] v12xke:
I've been running the 4.0 "christmas" beta of PA with FK for several weeks now. I own the FKU app, so have been updating as soon as a new kernel is available. Last night I installed the unofficial January 9th build found here and then flashed r32 from recovery.

http://xdaforums.com/showpost.php?p=49276055&postcount=35

Everything works great with no issues. Odd thing is that now when I check for a kernel update, FKU reports there is no kernel available for my device / ROM combination. I know I can d/l the kernel files and flash manually, but that defeats the main point of FKU. Is this due to recent change made to PA? Of all the custom ROMS out there, I thought for sure PA would be most compatible.
[Nexus 5 Original Android Development] franciscofranco:
Hmm that's odd. Can you show me a screenshot of your About Phone please.
[Nexus 5 Original Android Development] Chris123NT:
Last day or so I've been getting a lot or reboots on r32. Here's my most recent last_kmsg.

http://pastebin.com/kGbiz74a
[Nexus 5 Original Android Development] v12xke:
Thanks, here they are. Note I flashed r31 after the ROM, and FKU will not update to r32.
[Nexus 5 Original Android Development] Curtis7990:
Awesome experience on r32. I have your last kernel and ART. Incredible speed and battery life is amazing!
[Nexus 5 Original Android Development] P.Mobile:
r32 is running great but still cant wait for r33!!:good: your a great dev franco.. thanks for all that u do for us
[Nexus 5 Original Android Development] rajendra82:
OT, but the mag01 settings using the app, the result in a near perfect gamma of 2.2 for my display. It takes a while to enter all of them, but they work. I don't know what is more amazing than an accurately calibrated display setting. Everything will look exactly as it was intended by the person that published it. I am hooked on calibrated display settings, and will try to get everything I use to a setting just like what mag01 gets.
[Nexus 5 Original Android Development] javacody:
It's awful. Really crappy. Tried it in N4 and N5.

Just take control of syncing yourself.

I use syncer and tasker. Set up my Google account to sync every four hours, but only on WiFi.

If you don't have the new Google Play Services yet, go get it from Android Police. Supposed to be better battery life fixes in it.
[Nexus 5 Original Android Development] droid@xda:
Use r14 or any kernel with franco's color tweak and check gamma values. They will still remain to their original i.e. 1.8 to 2.0. But in reality, there's night and sky difference these between color profiles. Reason is display can be calibrated or tweaked by different ways which may and may not change gamma values. Take HTC's SLCD and Samsung's SAMOLED. Adjust gamma to same levels on both the devices. You will still notice huge difference in color reproduction itself. I am not talking about contrast and black level differences as they are bound to persist upto certain degree. My point is gamma values of 2.2 do not always imply that display is perfect.
[Nexus 5 Original Android Development] cobyman7035:
is there a gamma app for nex5? thats easy to use lol

ie nexus 4 control display
[Nexus 5 Original Android Development] zephiK:
http://xdaforums.com/showpost.php?p=49361206&postcount=12401 search before you post ;)
[Nexus 5 Original Android Development] aavvaallooss:
My underclock/undervolt settings

Stock, TWRP, SuperSU, Dalvik/Bionic, Franco, Viper, Xposed.

PVS 2.

Stability Test (Classic stability test + CPU+GPU stability test)

Antutu X Benchmark (Custom test + Stability test)

Franco Kernel Updater.

-UnderClock: 1 step down

CPU Max Freq: 1958 MHz

GPU Max Freq: 389 MHz

-UnderVolt: 3 steps down

-75 mV global (Instant reboot trying -100)
[Nexus 5 Original Android Development] federikk90:
I'm just fine running everything stock on r32. It's great.
[Nexus 5 Original Android Development] franciscofranco:
Gamma part of FKU is mostly done, closer to BETA status in 6-8 hours or something. Now, time for coffee with cgollner, need a pause.
[Nexus 5 Original Android Development] pidocchio:
great :good:

now go enjoy that coffee :)
[Nexus 5 Original Android Development] Stylez Ray.:
Could someone pls tell me what the default setting for "Multicore Power Saving" in trickster mod is for r32? Thanks
[Nexus 5 Original Android Development] Notechis:
2

VIVAN las Tapas
[Nexus 5 Original Android Development] pkelly517:
[MENTION=3292224]franciscofranco[/MENTION] Any chance that the Download directory in FKU settings can pull up the file manager? Try typing in a directory or two deeper than /sdcard. My fingers are way too fat to get it right.

I promise it's the last time I'll mention it.
[Nexus 5 Original Android Development] franciscofranco:
Sure :) thanks for the reminder
[Nexus 5 Original Android Development] alcurtis93:
That would be great! About the file manager :)
[Nexus 5 Original Android Development] droid@xda:
What can be a direct or indirect affect on performance (maybe in long run) of lowering input boost frequency by around ~200mhz? I tried it using FKU for few hours and didn't notice any immediate effect.
[Nexus 5 Original Android Development] Enddo:
I run input boost at 652,800 and it's fine for me. but i dont run games or anything resource intensive other than like texting, browsing, youtube. the little stuff
[Nexus 5 Original Android Development] droid@xda:
So there's no effect on performance for non gaming tasks for you? And any effect on battery backup?
[Nexus 5 Original Android Development] swarm871:
Good work franco..... Always the best!

Stock+xposed

No games

Location and Google now off

Greenify

50%wifi 50% 3g

Stock settings

Spoiler content hidden.

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] droid@xda:
I am just trying to think logical that it will be better to lower input boost frequency than stressing too much on UV to save bit of juice out of battery. Because I can see that phone spends considerably higher time on input boost frequency than others in normal usages.
[Nexus 5 Original Android Development] Enddo:
UVing can help a tiny tiny TINY amount of battery. but that's not why people do it. it's to reduce heat
[Nexus 5 Original Android Development] droid@xda:
Reduced heat will result in battery saving too.
[Nexus 5 Original Android Development] nexusmaniac:
Nice! Looking forward to it :)
[Nexus 5 Original Android Development] Triversity:
Heat alone will in fact benefit battery life, because it throttles more -> lower frequencies used.

Yes if the CPU uses less power, it saves battery and therefore runs cooler, but the way you said it is just not right.
[Nexus 5 Original Android Development] droid@xda:
You are only taking the case of thermal throttling. What if my CPU runs at 45° instead of 50° due to tweaks like UV. It is a case of lower heat. So now, won't it consume less battery? It will. Basic principle of energy conservation which I learned in school days.
[Nexus 5 Original Android Development] Enddo:
the unnecessary heat will reduce the lifespan of the battery though. so instead of yoru battery lasting 2-3 years, it could last 2.5-3.5 years or however much heat affects the battery
[Nexus 5 Original Android Development] droid@xda:
Wrong.

If CPU uses less power, runs cooler and therefore saves battery.

That's how it is and how I meant because there's a huge difference in meaning.
[Nexus 5 Original Android Development] Nocturnal86:
Franco I just had a random reboot. I wasnt doing anything in particularly different except I was down to about 10% battery life and placed my phone down with the screen on next to me and saw the reboot happen shortly after. Here is the last kmsg http://pastie.org/8627341 it says no errors detected but idk if it gives you any info why it happened.
[Nexus 5 Original Android Development] occtec:
Let me correct you my friend before you mislead others. Heat can greatly affect a smartphones battery and reduce performance, it can also damage your battery. Not only can it damage your battery, but shorten it's life span as well as cause unexpected behaviors on your device! :eek:
[Nexus 5 Original Android Development] droid@xda:
Thermal throttling is a major of prevention. One shouldn't take it as a way to save battery. The fact that temperature it takes to kick thermal throttling in (60° or more) is alone more harmful than savings it will bring afterwards. If thermal throttling was all about battery saving, franco would have lowered it all down to minimum possible.
[Nexus 5 Original Android Development] Triversity:
Maybe i didn´t explain my point well enough. You can´t say: If it runs cooler, it must hava longer battery life. Heat depends on some other factors, for example cooling.

I never said it wouldn´t affect it. You interpret in that sentence that heat is good for a smartphone? cmon. I said 'heat

alone

'. Ofcourse you can´t just apply that statement to a smartphone, because like I said above, there are many other factors...

But let´s not spam this thread even more. I´m out.
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Agreed but we're not talking about 20 degree differences by UVing. The difference is negligible for most people. You'd get better battery savings moving somewhere cooler than UVing.
[Nexus 5 Original Android Development] thesebastian:
Edit
[Nexus 5 Original Android Development] droid@xda:
I understand. I only mean that let thermal throttling do it's job and focus on other things like UV, lowering input boost etc to achieve better battery (if one wants). Going all up into thermal throttle zone due to increased heat and then save battery out of it aren't a sides of same coin!
[Nexus 5 Original Android Development] franciscofranco:
No idea, but I know I have a small bug on r32 in one piece of my code which could cause that after turning the screen on, I reproduced it a couple times, but I believe I've fixed it on my local build.
[Nexus 5 Original Android Development] jtwlbz:
Anybody having issue with light detection? I notice sometimes it jumps from 0 to 40000 lux in low light
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Yes I have this issue. Its not specific to Franco kernel though so I'm wondering if this is something he can look at to see if he can control the light meter at all.
[Nexus 5 Original Android Development] franciscofranco:
I can definitely take a look.
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Thanks.

Specifically for me I notice that in times where the light meter is registering anywhere from 0-20 lux once in a while it will spike to 30000 and my brightness jumps to 100% in response. Doing a quick screen on and off returns it to the normal curve level (which may vary for those using custom curves) and that's about 20% or so.

I've noticed people reporting this on stock and CM so far.
[Nexus 5 Original Android Development] jtwlbz:
Exacttly same thing here. But it does not happeb all the time. I hope its not the hardware issue.
[Nexus 5 Original Android Development] whytechapel_x:
It happens to me too.
[Nexus 5 Original Android Development] jtwlbz:
Ive haf.this light problem actually a while ago I just ignored it. So franco I'm sure its not r32 problem maybe older than that if its related to kernel. I wad using slimkat and aldo noticed with pa rom
[Nexus 5 Original Android Development] franciscofranco:
Happens on 100% stock as well.
[Nexus 5 Original Android Development] sir*mez:
Same problem I've been having and reported a while ago, but wasn't acknowledged by [MENTION=3292224]franciscofranco[/MENTION] because I probably didn't explain well. I've tested on the Nexus 4 (mako) which works as its supposed to and here on the Nexus 5 (Hammerhead) which has the problem of lowering the volume when entering 10 and then when entering -10 does nothing or the volume gets higher because it goes back to 0 volume gain even though -10 was entered. It's doing the opposite, it even sounds louder if you enter -3 when it's suppose to lower the volume. It's supposed to be +positive number = higher headset volume gain, -negative number = lower headset volume gain but the outcome is the opposite. This has been driving me crazy, but didn't want to continue to bring this up because I don't like nagging. But I hope he acknowledges that there's a problem since I'm not the only one reporting this now.

Below is the conversation I had with [MENTION=3292224]franciscofranco[/MENTION]:
[Nexus 5 Original Android Development] 850T5m:
I used to get the issue using the stock Rom auto brightness...but ever since I use lux I have no problems. I have lux set to change brightness on screen on, so it doesn't periodically check the amount of light...seems to have fixed the problem for me
[Nexus 5 Original Android Development] dpvu:
Yeah, it happens when you tilt the phone at a certain angle under low lighting conditions. Something just causes it to flip out and read 30000. Happens on all kernels and all ROMS I've tried.
[Nexus 5 Original Android Development] omvir:
I get this as well ONLY in the following scenario:

If I am in a place where there's lots of light, at least 150+ lux. And I hover over the phone with my face it will show a reading of 0 lux, and suddenly if I turn it to a certain angle it will jump to 30000 and back to 0 or 1 lux. But if I am in my room where there is low light the jump to 30000 never occurs.
[Nexus 5 Original Android Development] jtwlbz:
I feel better now I am not the only one. Now what would be thr root cause? Google side? Or something that franco can do some magic about it
[Nexus 5 Original Android Development] omvir:
I think its just the sensor itself. But who knows I know nothing about it lol. Yes maybe Franco can work some magic :)
[Nexus 5 Original Android Development] rajendra82:
Display can be tweaked many different ways, but it can only be calibrated one way, to the sRGB standard gamut. This will result in an overall gamma of approximately 2.2 and a Color temperature of 6400K. That is the standard. If you are able to tune the display to this standard setting, all content will appear exactly as intended by the person that made it. This is a single calibration setting and there can be no other setting that is correct. If you set your display to a gamma of 1.8 to 2.0, you may like the way it looks to you, but it is not calibrated to the standard. Period.

SAMOLED displays have a wider natural gamut than sRGB standard, and Samsung likes to utilize this as an advantage by over saturating the colors. This appears to make the colors pop is some scenes, and look garish in other scenes. This is a great example of not displaying things as intended by the content creators. The proper thing would be not to use this extra gamut, and instead turn the saturation down to the proper gamut.
[Nexus 5 Original Android Development] Tzfardaya:
oh, thank gods someone else who understands sRGB calibration and purpose.... You must be either a photographer or graphic designer. :P

anyways, have you figured out a way to hit that calibration yet? I've been looking for a way to properly set the colour temp....
[Nexus 5 Original Android Development] neriamarillo:
Have you taken a look at this thread and tried mag01's settings? After playing around with them they got my gamma to around 2.2. http://xdaforums.com/showthread.php?p=48728991
[Nexus 5 Original Android Development] Tzfardaya:
Gamma's only part of the equation there mate.... I'm looking to check colour temp first....

if you're not sure about why I'm looking for colour temp, check the post above mine, or google sRGB
[Nexus 5 Original Android Development] Rehab4Life:
Is it normal that I only get 3:30 - 4 hours of screen time? I always have my data on, and WiFi about three fourths of the time. I use lux auto brightness and I have battery savings on locations. I'm also on r31 stock ROM. I just don't see how you guys get so much.
[Nexus 5 Original Android Development] travisjustin:
Check to see if your awake time is close to your screen on time. If your awake more than the screen on you have wakelocks keeping you out of deep sleep. This is easily the number one cause of poor battery life. Get a good battery monitor like better battery stats and pick up greenify to put battery draining apps to sleep.
[Nexus 5 Original Android Development] neriamarillo:
I know exactly what you're looking for. The post doesn't only have settings for gamma. White point also gas to do with color temps.

Sorry [MENTION=3292224]franciscofranco[/MENTION] for the OT. :)
[Nexus 5 Original Android Development] Rehab4Life:
Kernel wake locks are 38 mins of power manager, which is normal. And 48 minutes of Pandora partial wake locks, hangouts being next with just 4 minutes. And its just because today I decided to try out Pandora. But I always get this even with just 4 minutes of wake locks.
[Nexus 5 Original Android Development] aloayzab88:
Ok, I was using Faux kernel before for 3 days, good battery life but lagy (yeah... lagy, not OMG super lag, but lagy on transitions and multitasking). Now I been using Franco kernel for 3 days the first 6h I have a huge battery drain on idle , device rebooted and problem solved. After that the battery life was good, like 1% evert 1-2h with Google Now on, location on, wi-fi/3g. So with medium usage it was like 1d6hish with 4-5 SOT, the funny thing is that is almost the same with the stock kernel. I feel that I need to buy the franco app to really see a big improvement... the problem: google dont acept my stupid debit card!

Any ways, great kernel and really good job, but for now I think I will stick to stock... at least until I flash some ROM (waiting PA).
[Nexus 5 Original Android Development] droid@xda:
I fully understand what you are saying. And I was wrong because I didn't bring color temperature in equation. I notice a huge difference in colors on cooler preset of some kernels and still no change in gamma values. So it must be because of varying color temp. I just don't know how to change color temperature via app or changing system file. Is it possible?