yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] IIMaxII:
Are you using Viper4Android or modifying the gain in mixer_paths.xml? Because I experienced the same thing, and just thought it was because of me doing stuff with the audio...but maybe not.
[Nexus 5 Original Android Development] F.B.8.:
Just downloaded FKU, bought the app just for support but I have to say it's very nice!!!

By the way I have a question, I've seen that it's possible to boost the speaker gain (red from above), what value do you think it's safe to use? I use the speaker just for ringtones/notifications/alarms (sometimes videos but rarely)
[Nexus 5 Original Android Development] Nbsss:
Weird, I feel like it's smoother ;)
[Nexus 5 Original Android Development] JNewms:
That's because Franco's CPU threading is so efficient. I believe we can squeeze more juice out of it workout sacrificing performance.
[Nexus 5 Original Android Development] assasin34:
How can i control this kernel.?

Nexus 5 cihazımdan Tapatalk kullanılarak gönderildi

---------- Post added at 01:10 AM ---------- Previous post was at 01:10 AM ----------

Nexus 5 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 5 Original Android Development] franciscofranco:
Shell scripts or apps.
[Nexus 5 Original Android Development] rayz93:
I see, so if I'm already using minimum of the extended minimum brightness with GravityBox via manual brightness slider before the the Brightness patch, with the Brightness patch the minimum brightness will be the same as GravityBox extended minimum brightness having both version manual brightness slider slide all the way down? Therefore, I can't tell the difference? Cool, thanks.

Yes, portrait work just fine. I noted that this "back button failure" only happens when the screen have both the menu bar and the content both displayed at the same time (where sliding menu bar is no longer needed). Changing back into portrait on the other hand requires you to slide the menu bar away to view the content, here, back button works without issue.

Hopefully, my explanation is clear enough xP
[Nexus 5 Original Android Development] assasin34:
İs that normal score with this kernel.was over 2500 with stock kernel..!!!

Nexus 5 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 5 Original Android Development] The Gingerbread Man:
Increasing above high speed delay to around the 50k area could also help and reduce input boost to 1497mhz (unless 1574mhz is specifically where this high ram freq thing is the lowest speed for it?). I must admit I've been wanting to spend sometime doing this stuff but have been waiting for a time when fku doesn't require inputting numbers so much and drop down menus for gov control to be introduced. I spent an extensive amount if time testing io schedulers with some other guys back on gnex and old n7. This is old data now but may interest you https://groups.google.com/forum/m/#!forum/francosdevteam
[Nexus 5 Original Android Development] franciscofranco:
You're thermal throttled - and besides stock kernel is MUCH more aggressive with the frequencies and it ramps up too much.
[Nexus 5 Original Android Development] BirchBarlow:
CPU Manager settings don't stick after reboot with FKU

I'm trying to use the franco.Kernel updater to undervolt, but it seems none of the CPU settings stick after reboot. How do I fix this? Thanks.

Update: Nevermind, I didn't realize about the set on boot parameter.
[Nexus 5 Original Android Development] JNewms:
Thanks I'll definitely give this a read tonight once I've played a little more AC multiplayer.
[Nexus 5 Original Android Development] Bhonka:
Phone was getting super hot on r22 whilst playing snes roms with supergnes.

Will try with 23.
[Nexus 5 Original Android Development] The Gingerbread Man:
Sure no worries. Like I say its old data and hasnt been updated for sometime. I have been meaning to revisit this and see if any more improvements can be made for flo and hammerhead, I just haven't had a great deal of chance with work and build up to Xmas. Perhaps at a later less busy time we could crunch some numbers for io schedulers

---------- Post added at 11:48 PM ---------- Previous post was at 11:34 PM ----------

Franco, in a file explorer where I can find the frequency table? Not sure if that's the right name... I can't remember the path before I find cpu0 cpu1 cpu2 cpu3 and the file in them which shows the freqs available. Googleing hasnt helped me on this occasion
[Nexus 5 Original Android Development] Habs69M:
first thks franco for this great rom, franco wrote something in this thread and he wrote it only once (believe me i read allot lolll) he wrote "know your phone" when asked for settings, and i figured hey he is right, so i search and read some more and now i get 0.4%, 0.5% idle drain an hour, what i did is use tasker, with some playing around i got it to greenify when screen is off (instead of waiting 3 to 5 minutes for greenify to do it) and shut-off wifi and data when screen is off, and auto-synch once each hour for 1 minute.

so on stock rom with this kernel combine with tasker and greenify will give great results, and again "know your phone"

thks again franco, love your work :)
[Nexus 5 Original Android Development] Testraindrop:
just put 30°C as thermal throttle temp... it will stay cold as ice :D

Of course it will lag as hell, but it will stay cold if thats what you are after.

Someone should invent new physics.

Franco, why haven't you invented a no-drain, no heat CPU yet? :rolleyes:

For real, just use a throttle temp that doesn't throttle your game and is not too hot, you can't have both at the same time.
[Nexus 5 Original Android Development] Nbsss:
I should probably mention i've added your values to my previous changes of:

above_hispeed_delay = 25k

hispeed_freq = input_boost_freq = 1190,000

timer_slack = 100,000

GPU max = 320

CPU max = 1728

UV = 700mV @ 300mhz

( + flashed the motox optimisations + also running 'app ops X' to tame Google Play Services Wakelocks + greenify + loc off + lux + 8 xposed modules running in the background + 7 pages of apps in my drawer)

Will charge it fully right now so i can test fairly, but initial impressions based on system monitor and smooth scrolling in the crappy tapatalk app look good...cheers!

Edit: which IO scheduler is preferred for max battery life?
[Nexus 5 Original Android Development] JNewms:
Ill add your values in with mine so we can see if both of our devices behave similarly
[Nexus 5 Original Android Development] The Gingerbread Man:
Sampling down factor maybe something to concider, iv lower mine to 60k and set system monitor CPU flying window to refresh to 0.1 seconds to see if the speeds lower to 300mhz faster.
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Is there any way to control call volume through the kernel?
[Nexus 5 Original Android Development] JNewms:
Headset and mic gain should be what you're looking for, I believe.
[Nexus 5 Original Android Development] xI mEzMeRiZe Ix:
Some WiFi networks can keep your device awake. My work does this so I need Tasker to control it.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Enddo:
that sounds like a question for the Cataclysm thread
[Nexus 5 Original Android Development] sempot:
Is this considered as good? Thank you guys.
[Nexus 5 Original Android Development] StiffyBoy:
R23 is by far the best battery life I've seen on 4.4.2 so far.

I've got 50% left and I've been running for 19 hours, with 2.30h SOT, mainly wifi, location off.

Very very happy franco!
[Nexus 5 Original Android Development] BTT8:
What are you turning off in app Ops to tame Google wake locks?
[Nexus 5 Original Android Development] theultimatev:
Could you please post your profile??? I've been looking for an answer to my university WiFi for weeks! Thanks :D
[Nexus 5 Original Android Development] SplitCold:
For USB fast charge, you change the value from 0 to 1 right? I do this but I can still access the internal storage when i connect it to my computer.
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
But doesn't that adjust ALL volumes? I'm interested in call volume only.
[Nexus 5 Original Android Development] JNewms:
Each one of those gains adjusts a certain aspect of the hardware. There isn't a way I'm aware of to make it to where it only affects in call volume.
[Nexus 5 Original Android Development] cobyman7035:
Does r23 work on kk 4.4¿?

Via my NeXus™ 7 FHD on Tapatalk⁴ Pro
[Nexus 5 Original Android Development] abbz123:
Yes.
[Nexus 5 Original Android Development] Enddo:
yes it does
[Nexus 5 Original Android Development] feedhead:
My first full charge testing franco... Impressive.
[Nexus 5 Original Android Development] Savant:
Works better on 4.4.1 because of the changes to ramdisk and other things.
[Nexus 5 Original Android Development] shreddintyres:
I had a similar issue as yours today, until i checked my BBS logs GNOW/google search has something really wonky going on with it, held a wake lock for 3hrs 45 mins while i was sleeping so i disabled gnow and my battery drain is substantially lower.

- Cheers
[Nexus 5 Original Android Development] zoltrix:
How does mic gain work?

If I set it to 20 does that mean that I can talk softer and the other person will hear me ?
[Nexus 5 Original Android Development] aNYthing24:
Do you mean 4.4.0? Or just 4.4.x in general?
[Nexus 5 Original Android Development] drawde40599:
I no u said kernel but Did u look threw the mixer_paths.xml file within the ROM ? that option may be in there ? There's a thread about that file if u haven't seen it .
[Nexus 5 Original Android Development] grumphy:
Rather look for the partial wakelocks instead

Sent from N5/stock/fkr23
[Nexus 5 Original Android Development] OptimusVDarwin:
I just had a bug report pop up on my notification bar what do I do?

Im on Stock 4.4.2 Franco r23
[Nexus 5 Original Android Development] franciscofranco:
No... 4.4.1 and 4.4.2 have the same ramdisk -.-
[Nexus 5 Original Android Development] Sydius08:
Wow that's incredible. How are you getting that kind of battery life? Flashed r23 yesterday. 14 hours on and 1h 21m of screen on time and I'm at 44% (CPU underclocked to 1.5GHz). Mostly just idle, checking Facebook/Instagram, texting, and a little bit of Google Play music streaming

What settings are you using to get that kind of battery life?
[Nexus 5 Original Android Development] Exostenza:
Forgive me for asking but where can I find the set on boot option in Fku so my undervolt sticks through reboots?
[Nexus 5 Original Android Development] :
Press and hold the setting you want to set on boot -> tick set on boot box
[Nexus 5 Original Android Development] big_adventure:
You get that, thanks to race-to-zero efficiencies, underclocking often is LESS efficient than running at full clock? Especially in your use-case.

Basically, it goes like this:

The phone ramps CPU when it needs to do work.

The phone, stock, eats 925mv at 1.57ghz. It eats 1050mv at 2.26ghz.

So, for a 12% increase in electricity, you get a 45% increase in compute power. In a load with lots of stop-starts - like using facebook and instagram, browsing, etc., it is much more efficient to let the phone ramp as fast as possible then ramp back as soon as it can - this is the "race to zero." This is, for example, why LTE is now consistently more battery efficient than HSPA - it's not that it uses less power (it doesn't, at all), it just that the power-hungry radio has to spend less time on, so it can get back to drawing less power more quickly.

If your use-case is gaming, well, that's different - since the CPU is going to mostly be pegged (depending on the game), you'd do better capping it lower to force lower voltages.

So, you are likely doing yourself a disservice by underclocking.
[Nexus 5 Original Android Development] Sydius08:
Wow. That's an incredibly detailed explanation. Thank you very much! So you're saying I should just move it back to 2.2GHz since the power saving I'm getting from underclocking is very minimal? Or what else?

Thanks again!
[Nexus 5 Original Android Development] big_adventure:
A bug report is Android saying there was an app issue. It probably has nothing to do with the kernel. You can dismiss the bug report, or let the phone send debug info to Google. It's up to you.
[Nexus 5 Original Android Development] Patozandoval17:
Works on stock ROM? 4.4.2

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Craxx:
Yep

Best regards ;)

Craxx

Send from my Nexus 5 with Tapatalk
[Nexus 5 Original Android Development] ikaola:
Great update ! :good:
[Nexus 5 Original Android Development] oediv:
Well I try both settings merged now.

Have 90 % will give some Feedback in the afternoon :)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] i860:
Hi Franco!

Just had a reboot on r23. I was on desktop after surfing on xda.

http://pastebin.com/t0BejJY5
[Nexus 5 Original Android Development] big_adventure:
There really isn't a hard and fast answer as to one choice being definitively better than another. I would try both. Spend a few days running at stock clocks, spend a few days running severely underclocked, and see which does better for you. Keep everything else the same: try for "normal" daily use, make sure that you are starting and stopping the tests at around the same times, if you are undervolting, make sure that you are using the same shifts, grab BBS info for each test to be sure that one or more aren't corrupted by something screwed up, etc. Take into account that if you spend an hour playing games one day, and 15 minutes playing games another day, it's going to completely bork the results.

I'd set up such a test like this:

Week 1: Stock clocks. Unplug phone at 7AM, take a screenshot of battery right after (to be sure it's reset). Take a screen shot of battery and take BBS logs (or at least screenshots of wakelock info) again at 7PM. Repeat daily.

Week 2: Underclocked. Same as above.

The test won't be totally empirical or objective - slight differences in signal strength, app updates, photo syncing and the like can have a pretty large effect on battery - but it'll be better than nothing.

It's a bit of effort, but you'll learn what's best for your specific use case. I personally found that UCing helped oh-so-slightly with some old phones, like a Nexus S or GalNex. But on those phones, there was something like a 30% power-penalty to shift up a couple of hundred megahertz, so avoiding the top bins made total sense for me and my usage. With Qualcomm's Snap S4 Pro, Snap 600 and, especially, Snap 800 chips, the power penalty for shifting up to max clock is so slight for such a MASSIVE compute increase that I don't really see a value to changing max clocks, with everything else consistent, and there is quite likely a penalty for many scenarios.

Your mileage may vary. Standard disclaimer, but fair: no two of us do the same things with their phones, so no two of us are going to have the same results. I see people getting 5 hours of SoT with 19 hours off charger and I'm amazed. I generally don't get near that. Of course, I often work in a location with questionable signal, I never shut wifi off when I'm out of the house, but nearly never use it, so the supplicant is just chomping away at the battery, I get lots of mails (3 synced accounts), texts, hangouts and WhatsApps, so I'm constantly locking and unlocking my phone, I don't use Greenify or Tasker, I'm in and out of signal-challenged public transit frequently, location services are on at high accuracy, I stupidly have both Dropbox and Google auto-syncing my photos, app updates run over Wifi and cell, plus, up until yesterday, I had Google Now on at all times. So I'm not exactly running thin and light here.

I generally have no issue making it through whole days with 4+ hours SoT as long as I don't play games. Games will kill my battery, though, but that's true on any phone.
[Nexus 5 Original Android Development] Mixy:
Hi guys!

Having some problems with the app, and wondering if anyone has tips for me. I've got two Google accounts, and bought the app on the first one. Now whenever there is an update, it tries to update with the new account, resulting in errors (as I havent bought the app with new acc). Whats weird is that if I change accounts i Play store, I'm still getting the error. Have to uninstall and hassle around before it will update.

I wouldnt mind buying the app again on my new account to support Franco, but Play wont let me. Whenever I'm on the new acc it says that I've purchased the app, so I cant buy it again. Same goes for if i do it from play.google.com

Any tips on how I can either get stable updates on the old account, or how I can buy it on the new account?
[Nexus 5 Original Android Development] riDDimann:
For the sake of not spamming the thread I'll keep this short: No. You increase the voltage and because you increased it the chip also leaks more current. For that reason power draw is not proportional to voltage, but behaves quadratically. How this works out exactly is very complicated. I seriously doubt that the S800 uses less energy per instruction at 2.26 vs 1.57 GHz.

Race-to-idle means something different. When the device is supposed to be sleeping, it turns out to be more energy efficient to finish the task that's keeping it awake as fast as possible, so the CPU and all other active components can be turned off again. If the phone is in use it cannot power down, because the user is still staring at the screen. If your workload means the device will be running for a long time (games, reading, ...), you want to keep the CPU in the lowest power state that gives enough throughput for smooth operation.
[Nexus 5 Original Android Development] showofdeth:
Any word from the developer or someone in the know as to when/if the colour control option in the FK Updater app (paid) will be compatible with the nexus 5?
[Nexus 5 Original Android Development] ppog:
Yeah, I saw the post you quoted and thought...no.

I don't pretend to understand it, but surely because the clock is cycling faster the battery draw will be (clockspeed*voltage) and therefore exponentially more; the difference is not linear. I remember on a kernel development thread for GNex some guy did loads of testing and said it was something like this. It was in the context of undervolting. The point was that if you test meticulously and do it right, you can achieve a significant battery saving by UV at higher frequencies.

I've done not meticulous or tested UV'ing on this ROM :) and I'm getting incredible battery. Thanks Franco
[Nexus 5 Original Android Development] :
When it is ready. You can use [Free APP] Nexus 5 gamma reverse engineering App in the meantime.
[Nexus 5 Original Android Development] showofdeth:
Have that app already installed but I find it confusing to be honest. Cheers for your clarification on this, though. Nice one.
[Nexus 5 Original Android Development] riDDimann:
Exactly. Each transistor can switch once per clock cycle and that requires energy (to move the electrons). Clock twice as fast means it consumes twice the energy. That's linear. Add the increase in voltage it needs to run stable at higher frequencies and you're in a lot of trouble power-wise.

Of course this is a very crude and simplified way of viewing this, but it works nonetheless.
[Nexus 5 Original Android Development] MaXAiRO:
I don't know if it 's a known bug or if it 's just me but set on boot option doesn't always work for me. It works for about 50% of the reboots. I have set it for Voltage Control, FSYNC, Vibration and Speaker gain. I have latest FKU paid app and r23 kernel.
[Nexus 5 Original Android Development] :
You need to wait a little bit after rebooting. It won't be set immediately as far as I understood.
[Nexus 5 Original Android Development] z3nith66:
Guys I have a big problem. Just bought the app because I want to use this kernel with CM. Now I can't even get a refund because the time's up.

Anyway, if I install both a new CM nightly and the kernel at the same time, it gets stuck at boot. If I install the kernel afterwards everything works fine, but there is no damn battery option in the settings menu.

This is either a huge bug or I've found the key to smartphone immortality. So...what the hell is happening?
[Nexus 5 Original Android Development] nexusmaniac:
It's a CM bug
[Nexus 5 Original Android Development] 75markus:
CM is borked, no problems with stock-based roms

you gotta wait for a CM update, it´s no kernel problem
[Nexus 5 Original Android Development] z3nith66:
Ok...I've been on another ROM and came back to CM. Do you know if this problem is only with the latest nightly or if I should try an older one?

If I go to the CM topic I have a feeling I'll get a 'gtfo it's a kernel problem' so...haha, what do i do...
[Nexus 5 Original Android Development] r0cafella:
Sounds good,

Please make a thread of you'd own with the results for each
[Nexus 5 Original Android Development] ShotSkydiver:
Oh... I've been using it for the past day or so, other than lengthy install times for apps, everything seems to be running super smoothly despite its unfinished nature.
[Nexus 5 Original Android Development] techmatlock:
I've been using ART for the past week and really like it. Just don't use apps coded by 12 year olds and you won't have crashes on your phone. I mean I only have about 20 apps installed on my phone and most of them are Google, so I can't speak for everyone.
[Nexus 5 Original Android Development] roguenode:
I downloaded the 7 img and was poking around in Franco's App in the file explorer, tapped on the image file in the explorer and my phone went immediately dead. Won't power up, dead also when plugged into wall to charge. Yes, I'm a dumba$$. Just wondering if anyone has any suggestions before I send this back to Google.
[Nexus 5 Original Android Development] franciscofranco:
I already stated that my app is not ready for the N5, why use potential dangerous options? Im sorry if this sounds harsh but that's on you.

I don't have any suggestion for you, no idea, I don't have the device yet.
[Nexus 5 Original Android Development] roguenode:
Franco, I fully agree. It's my responsibility and certainly did not intent to suggest otherwise. Just checking for suggestions before I go through the trouble of working with Google. Carry on...
[Nexus 5 Original Android Development] bkeaver:
Installed this today and everything seems to work great! Awesome job!
[Nexus 5 Original Android Development] Zainiak:
Not trying to be a ****, but realize that you are making Google pay for your mistake.

Im not trying to argue. Just putting it out there
[Nexus 5 Original Android Development] zephiK:
Doesnt boot into bootloader mode? (vol down + power)
[Nexus 5 Original Android Development] drdrewdown:
if it's not compatible can't you restrict access on Google Play Store?
[Nexus 5 Original Android Development] roguenode:
It would not boot into recovery at first, but left on charger and did manage to get in and restore a backup. Fwiw, I did not intend to lie to Google and get them to give me a free replacement, but just start RMA and pay to either have it fixed or replaced. I may be an idiot to doing this, but I am not a jerk. :)
[Nexus 5 Original Android Development] antabaka:
Whew glad I wasn't the only one!

You should still be able to get into bootloader *hold volume plus and minus keys with pwr* though it make take some time for it to respond.

Restore your phone to stock and all should be good flash stuff over again.

I used this guide

http://xdaforums.com/showthread.php?t=2513701
[Nexus 5 Original Android Development] franciscofranco:
Hope you manage to fix it ;)

Nope, everything basically works besides anything that involves flashing boot.imgs.
[Nexus 5 Original Android Development] m3nster:
Thats what we all mean, i think at least. I have over 180 apps on my nexus, I need to keep everything smooth, so I'll use dalvik and franco.kernell :)

When you almost have no apps than ART might be a better option :)

That's just my thought on it.
[Nexus 5 Original Android Development] Savant:
I have 138 apps and they work wonderfully with art so, try not to mislead anyone since everyone's experience varies.