yashsingh1/xdaforums huggingface dataset:
[Android General] The Gingerbread Man:
As the other guys said, and as I said in the 1st post the best settings will always be default settings. Franco not only knows how to create a very good kernel but also pretty much optimise it. If you find you manage to make a part more efficient or better or faster and can prove it you might well find he takes your suggestions on board and changes his code with improvements.

Anywho, to set on boot please refer to the op if your on an old version of the all if not then press the book mark to the right of the setting.

With any force close you should send the report to the dev through play store. If you can't use log cat and provide your exact reason
[Android General] The Gingerbread Man:
http://xdaforums.com/showthread.php?t=1369817 is a very good guide I have come across to help people learn above various governors and tweaking them.
[Android General] EarlZ:
I gonna get my phone in a few hours later, Just wondering if this kernel has some sort of color calibration or color temperature control?
[Android General] The Gingerbread Man:
There's an app you can use to change the settings for colours but its not the most user friendly experience ever. I put a link in the OP if you read through nexus 5 specific section
[Android General] Nbsss:
I think that for normal up/down scrolling, 1ghz is enough. More intensive touch interactions like pulling down the notification drawer or tapping recents needs more juice though.

So i tried to apply this theory with the second lot of settings i tried out, input_boost was @ 1ghz, and hispeed_freq @ 1.5ghz, however the threshold for hi_freqspeed was much much lower so it kicks in when it needs to.

Within the system monitor app, simply touching the screen and swiping up/down ramps to 1ghz, tapping recents/notifcation shade ramps to 1.5ghz as i wanted.

The final CPU stats frequencies below show a roughly double the distribution of 1ghz compared to 1.5ghz - would be interesting to see what this distribution is like on fully stock settings, which is what i'll test out next.

And i personally believe no mobile or application deserves/needs more than four cores running at 1.7ghz, so i like to cap it at that.

That's my theory anyway, i need to properly test it all of course, so huge grain of salt lol :)

[MENTION=4267798]JNewms[/MENTION]
[Android General] shengovind:
Yo gingerbreadman... There's no difference in battery saved by under clocking GPU to 350mhz..

It's the same.. Instead keep it at max itself

Just a opinion..
[Android General] The Gingerbread Man:
Well, in theory there would, not just in the fact there's less cycles per minute / second but the voltage difference in terms of the speeds. Granted it would be small. Ignore my settings for now, I'm busy working out undervolt table for myself and then I'll have a look at improving tunables later. Iv been working all day, then straight back out to parents house for sunday dinner. Book mark the post and check back every so often :)
[Android General] peeweew:
Hi franco, if its okay to suggest adding a sweep2wake/dt2wake enabler in FKU just in case so it may be an option. Just ignore if not okay. Thanks!
[Android General] The Gingerbread Man:
There's 2 unofficial builds with that already in. Check n5 specific bit in the OP
[Android General] EarlZ:
Thanks, I am not sure if I understood it correctly but starting r15 there is already some sort of change in the color temperature built into the kernel? I Just want to get rid of the warm whites.
[Android General] The Gingerbread Man:
There was but it got reverted because the setting that was changed was somehow related to some kind of timer or something, no one knee the full implications of the changes so until more is understood it was changed back to normal. Don't feel dumb though trying to use that app in the nicest possible way its not really ideal for most people but some guys are working on it and hopefully faux123 can come up with a more user friendly UI when people understand more.
[Android General] peeweew:
Do they update everytime the official build release?
[Android General] gasgallo:
Yes man!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android General] The Gingerbread Man:
I don't know I don't follow those threads but I have linked to them for you to find them easily
[Android General] The Gingerbread Man:
Updated my settings post with 'beta' undervolt settings. Please read the warnings, reference only guys.
[Android General] EarlZ:
I guess I just have to wait till then, on the Galaxy Note 2 I used something like +14 to blue on white to remove the yellow tint, Hopefully something similar comes to the Nexus 5. The N4 has a good whites but more on the blue side.
[Android General] The Gingerbread Man:
Tbh I think everyone is just waiting on more user friendly interface. There's about 24 settings for blue, green and red each requiring positive and negative inputs. Then you have white point. I really appreciate the efforts going into it but its just not 'user friendly' hopefully it will improve in the future
[Android General] Nbsss:
Nice, i have the same PVS and 300mhz limit so thats handy! :)

I think its probably wise to only UV the specific frequencies that you're phone is using the most.

If you check system monitor there's only 4 or 5 CPU frequencies that are listed, no point UV frequencies that won't be used for more than a few minutes if at all :)

The most valuable frequencies to UV in order of benefit would be the:

1) min (300mhz)

2) input_boost_freq (1.6ghz)

3) sync_freq (960mhz)

4) hispeed_freq (1.49ghz)

---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------

Battery Results on r24

Interesting to see that r24 has basically the same battery life as r23 (with the second lot of tunables) - could be due to either the UV [MENTION=409989]300[/MENTION] or the new gov settings, or a combination

r24: SOT/hour

100-90%: 63min

90-80%: 35min

80-70%: 36min

70-60%-50%: 66min so 33min ave (forgot to screenshot)

50-40%: 25min

40-30%: 34min

So at 30% r24 is at 4:20hrs vs custom r23 at 4:30hrs

About 32.6min/10% (excluding the 100-90 range) on stock r24 with undervolt of 625mV [MENTION=1785406]300m[/MENTION]hz,

compared to 33.1min/10% (excluding the 100-90 range) on custom r23 with undervolt to 700mV [MENTION=1785406]300m[/MENTION]hz

Yeah there's nothing in it lol

System Monitor shows 1.5ghz+ frequencies being used 4x as much as 960MHz - which is the speed I find smooth for initial scrolling/touch interaction.

Also, 960mhz is being used a third as much as 1.6ghz (the input boost)

So for my next test, i want to see how much a difference it would make by swapping the relative usage of those two frequencies (and UV to 625mV), as i think 1.6ghz can be used a bit less without compromising performance, i'll raise the boostpulse duration to 1sec as it doesn't matter since the 960 will drain less anyway.

I'll see if i can make a hybrid of sorts, using the tunables we've gotten so far and r24 stock values
[Android General] The Gingerbread Man:
About the first part I agree to a certain degree but if your going to undervolt you may as well go the whole hog although yes the ones you singled out are probably the most important but I tested all as a guide of reference to others.

The second part I agree with, I was using 960mhz touch boost on r23 and had higher hi speed freq set. If you think about it you want lower touch boost as typing in theory it wastes your battery, I still found scrolling smooth and cpu can ramp up if required. If you were to boost the touch boost duration I'd suggest half a second, 1 second is too much imo.
[Android General] Nbsss:
This is a work in progress, don't use yet please
[Android General] Lowresolution:
Hi,

Was just about to buy the kernal app , however i have a question .

1-) is it safe to apply the kernel on the stock 4.4.2 ?

2-) i am a normal user , who is just looking for better battery timings , without tinkering with the kernel settings. Means are the stock settings for the kernel good enough for me ?
[Android General] shengovind:
1 yes

2 yes
[Android General] 530farm:
FKU Settings Explained

Does anyone have a link to where I can find all the FKU settings explained, really looking for a comprehensive list of the "governor control" settings explanations.

Thank you.
[Android General] bigbear6708:
Thanks! You guys are awesome! Love the Franco community! To be sure.. On cataclysm... If I have problems with this kernel I can just dirty flash rom and kernel will over write?
[Android General] Empty Hand:
Correct.
[Android General] The Gingerbread Man:
Updated settings post on page 23. Several changes to voltages, and a few other things I have changed mainly involving CPU speeds.
[Android General] Enddo:
I just wanted to pop in and give my battery report with your nexus 5 settings and a couple tweaks of my own, but mostly yours that you had listed(the ones you had yesterday before you changed them to blanks)

I fell asleep shortly after the 30% mark, so I didn't think it was smart to keep the stats going, but I will get a screenshot of the battery stats page with screen on time.

I'm at 12% left with 13 hours screen on time so far. i usually get 12 to 12 and a half hours. but that was on ART. now im on Davik again with the davik optimizations pulled from the moto g and the cataclysm rom. im highly impressed with this setup so far.

edited to add screenshots
[Android General] Caebron:
I'm having a weird issue where the stock camera app stops working when running ART. Every time I try to open up the camera app I get a message saying unable to connect to camera. The moment I switch back to Dalvik it works just fine. Could this have something to do with the kernel? I wanted to poke around a bit first before I dedicate a thread to the issue.

EDIT: Just running the kernel btw (r24), not the FKU.
[Android General] prasannathani:
Why bother even having a smartphone when its idling for 99% of the time? Lets just stick to realistic test results.
[Android General] Enddo:
its a computer in your pocket. are you suggesting i play horrible mobile games when i could turn on my desktop and play games on steam. are you suggesting i watch videos on it when i have a 30 inch monitor or my 55 inch tv to watch what i need to watch

i wasn't being deceitful, im not lying about how i use 3G or LTE for 10+ hours on one battery. so how about you back up and use your 'smartphone' how you use it, and ill use mine how i want.

in any case. i bet my test results are more useful than 4 hour screen time tests that have so many variables that who knows what benefits you're getting out of kernel updates or UV/UC changes.
[Android General] prasannathani:
I'm not suggesting your results are deceitful, I'm suggesting there should be context provided (i.e. I left my screen on and walked away). Your screenshots clearly state that no activity occurred (other than the 4% used by whatsapp). Simply leaving your screen on and letting it idle for 14 hrs isn't really providing much.

But like you said, if there are users who would like to know how long one could leave their screen on without little to no activity... then you're right -your post would be helpful to them lol :victory:
[Android General] Enddo:
i gave you context. i specifically said that the longest i left the device alone with the screen on, was when i went to take a shower for 20 minutes. believe what you want kid
[Android General] prasannathani:
You do know how to read the battery stats right? Take a look at your second screenshot... Your device has been reported to be on for 19.5 hrs with a total screen on time of 72% - this give you your +14 hrs. You notice that the next battery draining task is wifi and android system? both of which require no input activity from you. The only other thing is whatsapp which used about 4% of the 19.5hrs of battery - this translates to 0.78hrs. There may have been other things you did on your device, ie. opened the browser to only close it again 2 seconds later, but majority of your "testing" was done in idle with the screen left on.

P.s. Will completely overlook your "kid" remark this time.
[Android General] Enddo:
i dunno where you get your math from. you're gonna pretend that i had whatsapp open for .78 hours? an app that i use to talk to my girlfriend while im deployed overseas, an app that i kept open and active for at least 13 of those hours. sending over 1000 texts/pictures/voice notes to her, and receiving over 1200 texts/pictures/voice notes from her during yesterday alone

look. you can pretend to know what you're talking about, but you dont. and that's why i called you a kid. dont overlook it, acknowledge that you're acting like a child and you got called out on it
[Android General] bradputt:
actually both of you guys are right, SOT is never a good way to measure the battery life.

if you leave the phone with screen on only without doing anything you pretty much will have a good SOT.

i bet you if you actually do something on your phone i.e browsing, playing games and reading something and making phone calls, the batt vs SOT will not even hit 4 hrs.

another thing is your 3G/LTE reception or if you are on WIFi or not. 3G/LTE will definitely drain your power faster.

so there's too many factors that will affect your so called "SOT", don't take things on the surface only.

everyone got their own way of testing their "SOT"
[Android General] tjtj4444:
Please understand that 72% above means that the display have used 72% of the used power. It does not translate to 14 hours of screen on time.
[Android General] Enddo:
thank you :)

:highfive:
[Android General] The Gingerbread Man:
That usually happens when the LED is on if your using it for a torch. I don't what the issue is but art is experimental try dalvik if it works better for ypu
[Android General] Nbsss:
I've been stable with the same pvs for the following frequencies:

835mV [MENTION=2782247]148[/MENTION]7mhz

750mV @960mhz

Does yours reboot?
[Android General] prasannathani:
[MENTION=2662403]bradputt[/MENTION] That was my point, just didn't say it as nicely as you have put it. Thanks!

---------- Post added at 05:04 PM ---------- Previous post was at 04:42 PM ----------

No you're right its not a fair translation, but the app essentially tracks how much power has been used by the screen (with the brightness and SOT being the main factors). However my point was that since he says he has the brightness down to 2% for 99% of the time, some context should be given to the +14hrs SOT.

[MENTION=5518280]Enddo[/MENTION] [MENTION=4901494]abbz123[/MENTION] think you misunderstood, there's no "hating" going on. We all share the same device and can easily achieve similar results if we all used the device the same way (ie. 2% brightness, airplane mode, idling, etc). My point is, if you're going to post your results, provide some context within the post. Your comment about leaving it on for no more than 20 min, 2% brightness for 99% of the time all wasn't mentioned in your post. Therefore to a normal user, they see your +14hrs and think that it was achieved under "average" use - which even as you stated, is not the case.

Rant done. Just wanted throw caution in the wind to those who were going to try and reproduce your results under normal use.

Now let's get back to what this thread was created for.
[Android General] The Gingerbread Man:
I keep getting reboots every so often mostly on lock screen where the camera launches (I use face unlock) so I've been changing my MV posted. I just can't quite trace exactly which on is triggering the reboots, once I find it I can probably drop the others off a little
[Android General] The Gingerbread Man:
[MENTION=4788174]Nbsss[/MENTION] I think I've finally got rid of my random boots. Took 25mv more on the lower speeds
[Android General] Nbsss:
nice, what caused the problem?
[Android General] The Gingerbread Man:
Either 625 @ 300mhz or 650 @ 422 not sure which but its stopped since I changed both together
[Android General] cobyman7035:
help please, whats the easiest way for me to get on 4.4.2 and keep my franco kernel/ apps and data all intact , thanks

im on r24 with kk 4.4 only , stock rom i think not sure but its modded and using ART mode

so im thinking i need to flash the system.img and boot.img of the stock 4.4 google factory image and then do the OTA, then root, then flash r24 again?

thanks
[Android General] gtanner00:
Or try a flashable stock rooted ROM. It's not exactly the factory image (meaning it won't get ota updates) but it is identical to stock 4.4.2 and can be flashed the same way as any other ROM. You will need to reflash Franco kernel but if you back up the kernel and settings in F.KU app then you should be fine. There should be no need to wipe data in recovery since you are essentially staying on stock rom.
[Android General] Enddo:
im unable to use 300mhz at 625 either. but reboots are instant on my PVS3

edit - maybe not. maybe it was just the jolt of voltage reduction that forced the reboot at first. from stock everything i put it at 625 and have been able to do multiple stability tests in antutu without crashing. seems stable in my every day usage too. but i will be testing this more as the day goes on
[Android General] JamieFL:
I've been trying to get through this entire thread before asking my question, but after several hours and only getting half way, here it is...

Does FC work on ART?
[Android General] Caebron:
Yes. I've been running ART on FC for a couple days now. The first time I switched I was having problems with the stock camera app now wanting to start up, but after I switched back to Dalvik and then back to ART again, it worked fine. Haven't had any issues since.
[Android General] The Gingerbread Man:
What do you mean FC work on art? What do you mean by FC?
[Android General] JamieFL:
FC =Franco Kernel. Sorry. Had to fix that a couple of times because of auto correct and still got it wrong.
[Android General] OGroteKoning:
I posted this on the other thread, but the guys there are too busy discussing their SoT to notice my query. So perhaps someone here can help me.

Please help me understand. As far as I know the stock speaker setting on 4.4.2 for the Nexus 5 is 88. Before using this great kernel, I edited the mixer_paths file and set it to 93. After flashing Franco, I set it back to 88.

In the FKU app, the gain can be set from -20 to 20. If I set speaker gain to +5, does it mean that it increases the gain from 88 to 93, or is the -20 to 20 "random" settings? I would also like to know the same for headphones, headset and mic.
[Android General] The Gingerbread Man:
Jamiefl yes the kernel works with art I'm using it, but you can't use art and xposed modules

Ogrotekoning sorry I don't know the answer. If I were you I'd fastboot system image to revert your own changes and use the kernel interface if your having issues
[Android General] Nbsss:
[MENTION=2918197]The Gingerbread Man[/MENTION]

Hey man, from my testing the extra drain from a higher input_boost didn't matter as much if the min_sample_time and boostpulse_duration were reduced, as it spends much less time at that higher freqency, so i think we can get away with a higher clocked input_boost.

As an example, let's say we configure it to spend half the time on 1.6ghz (as it ramps down faster):

Then 5min on 1.6ghz + 5min on 300mhz, would drain far less than 10min on 960mhz.

I've also been using 960mhz as my input boost for the last 3 days or so and its been smooth over 95% of the time, its just those 1 or 2 moments that you can notice its struggling when it can't clock higher soon enough, so this would help with that.

What are your thoughts?

Edit: I hope you had a better Christmas than this guy http://www.youtube.com/watch?v=FpBJih02aYU :P, my feelings go out to your race after the mass genocide of your Gingerbread people on Christmas, though i may have contributed, sorry.....
[Android General] Enddo:
what does everyone think about bionic and dalvik optimizations over art. for battery life and performance
[Android General] The Gingerbread Man:
Yeah that makes sense, iv got my touch boost to 1036mhz currently and its fine. I found reducing the timer rate back to Franco's default 30000 made things a hair smoother. You might also find if you were to try lowering your first level of hot plug level to say 65 it would be easier to get some more cores on if required. Maybe try 95 for go high speed load.

As for the genocide part I'll forgive you only as long as you bake some more of my people today :)
[Android General] OGroteKoning:
Thanks for answering. Who do you think would know the answer or where do you think I should ask?
[Android General] Nbsss:
Yep, i've been using 30,000 time_rate and 95 for the high speed load in my latest test (linked it to my sig also).

The hotplug thing is more of an experiment, but it seems to be working well, quite surprisingly, it only kicks in the quad-core beast in sustained load when its really needed eg. doing a titanium backup or screen unlock, which is probably better for battery than switching cores 3 & 4 on and off for 1-2 seconds.

For my next run i'll decrease the hispeed load to 85 and decrease the hotplug threshold, and compare it to the baseline battery i have at the moment, should be interesting!

Time to start youtubing gingebreadman recipes...
[Android General] The Gingerbread Man:
Try a Q&A thread or bump your post in the main thread.

Sounds good I look forwards to your next set of results
[Android General] The Gingerbread Man:
Made a few changes to settings post page 23
[Android General] Mynix:
Hi everyone,

Already reported this issue (if it's not from my side), in Franco Kernel thread but didn't find an awser (maybe I missed it ! :rolleyes:)

The thing is, whatever settings I change in CPU freq/governor, it doesn't actually apply if it's done from FKU..

For example, if I set min/max to 2265/2265 or 300/300, it doesn't work, performance governor doesn't neither. From Trikster MOD, no issue.. I checked the frequency with System Monitor during 'idle' and benchmarking. See here xdaforums.com/showpost.php?p=48759744&postcount=9090

Running stock, no bionic libraries, Franco Kernel r25. Tried to unistall every kernel tuner app, no changes.

Thanks for your help, if no idea why I'll try to start everything from scratch..
[Android General] Binary Droids:
Gingerbread Man, I'm trying to test UV settings by doing the same thing you did. Isolate the CPU freq & then UVing until reboot. I decided to work from the top down & got a reboot at 950mV for 2265MHz which I expected. When I did 1958MHz, though, it went all the way down to 600mV and still hasn't rebooted yet (about a half hour now). This can't be normal, right? I have PVS 2 just like you do.

EDIT: Nevermind, must've been a hiccup in the FKU app. I cleared data & tried again. Got it to reboot at 895mV.

Nexus 5 - Stock Rooted - franco.kernel
[Android General] The Gingerbread Man:
I don't know, your using the same set up as me, stock rom, art, r25 and it works fine for me sing fku. Really not sure what else to suggest other than full wipe and start again
[Android General] The Gingerbread Man:
Yeah I found that a few times but it means its not been set correctly some how. The best way to test it I found was use 300mhz as min speed, then go to voltage control and change the MV for the step you want to test and then go back to CPU manager and change your min speed to the one with the voltage you just changed. Also you may find when you get close to stable settings they don't always save unless you unset on boot and set on boot again. I'll add this to the settings post page 23
[Android General] Binary Droids:
I finished up testing and got the exact same stable values as you. Pretty much expected that since we have the same PVS, but I like to try it myself... Thanks for this thread & your contributions to the main franco.Kernel thread as well.

Nexus 5 - Stock Rooted - franco.kernel
[Android General] casperpas:
Mirror (Screencast)

I'm using Mirror screencast on my Nexus 5.

Last night I tried to record my screen but the video couldn't save property. When I'm on r25, I flashed back r23 and r24 and found that r23 works but r24 and r25 didn't. Stock kernel worked too.

Could you tell what it is? I love both Franco.Kernel and Mirror Screencast :D