yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Enddo:
Because you don't think it will save battery or because it could have a negative impact on the hardware?
[Nexus 5 Original Android Development] matesc:
Yeah- new test IMG! Changelog? Thank you Franco! :)
[Nexus 5 Original Android Development] franciscofranco:
Pushed r56!

Why would it impact hardware?... because I don't think it will help saving battery.
[Nexus 5 Original Android Development] K Rich:
Removed the "gamma auto brightness" correct?
[Nexus 5 Original Android Development] simonarturo:
Gonna download it. Did Yorici's brightness fix make it to r56?

It actually works pretty good with my configuration (lux + the brightness patch)
[Nexus 5 Original Android Development] odavans:
Brightness patch?
[Nexus 5 Original Android Development] simonarturo:
patch, fix, "Gamma-corrected brightness scaling"

Call it however you like
[Nexus 5 Original Android Development] Red5:
I think what hes asking is, did it make it in the latest version? Its not listed.
[Nexus 5 Original Android Development] simonarturo:
I know you said you didn't like it at all but if you ever have free time and is doable without taking too much time, you should add a toggle for the brightness scaling. I know I don't speak for the majority, but some of us actually liked it. :)

[MENTION=4782328]Red5[/MENTION]: franco asnwered that one a couple of posts above. It's not in the final R56 vversion
[Nexus 5 Original Android Development] aavvaallooss:
r56 not compatible with my previous undervolt settings (Freeze and reboot). Reverting to stock values fix the problem.

Or maybe last FKU fault?
[Nexus 5 Original Android Development] Jamith:
Thanks Franco, I'm having great battery life with the R55 without problems.
[Nexus 5 Original Android Development] Bobtehblob:
Heads up to those undervolting. r56 changes voltage tolerances. My r55 values were unstable, +25mv globally did the trick :)
[Nexus 5 Original Android Development] Lapiduss:
r56 not compatible with my previous undervolt settings (Freeze and reboot). Reverting to stock values fix the problem.

Or maybe last FKU fault?

+1
[Nexus 5 Original Android Development] simonarturo:
See the replies before yours

R56 behaves differently to undervolt that previous versions. Revert to stock voltages and then try lowering it bit by bit. -50mV work fine for me
[Nexus 5 Original Android Development] doubleho:
i tried it on other kernel,itz a drainer,drained 20% last night for 8 hrs when i was in bed
[Nexus 5 Original Android Development] lkthomas:
Wow! that bad?! better not use it!

Just wondering how does Blackberry Z10 do it without drain battery. Maybe there is a special chip to sense the on screen?
[Nexus 5 Original Android Development] doubleho:
my nexus 7 2013 4.3 s2w didnt drain much at all.....
[Nexus 5 Original Android Development] Batfink33:
This,

Waste of battery.

Sent From My Nexus 5 Powered By Franco Kernel
[Nexus 5 Original Android Development] lkthomas:
Battery on N7 have huge capacity compare with N5, so it make sense.
[Nexus 5 Original Android Development] sordna:
I switched to apps that use the proximity sensor to wake my phone without using the power button.

It's a great solution. Try Automaton Locker, or Simple Cover Lock, battery drain is minimal.
[Nexus 5 Original Android Development] Moh_Jay:
Benchmarks for any phone is flawed in general. Htc, Samsung over clock in benchmark apps to "show" that their phone is better. If someone thinks high numbers are the only way the phone is good then just get off nexus. This phone compares to top flagship devices with its scrolling and swiping along with running games smoothly. Personally its annoying me that people still want a fix for antutu and slow development while Franco tries and fixes an already flawed test. Sorry for the rant and off topic from development.
[Nexus 5 Original Android Development] Nocturnal86:
Your nexus 7 isnt in your pockets most of the time and getting "false" taps to the screen in the pocket.
[Nexus 5 Original Android Development] omvir:
Nope, local music, using power amp. (The sound is as if its a really messed up tape being played in a tape player, if that makes sense)
[Nexus 5 Original Android Development] zephiK:
I had the same effect today, didnt have it two days ago. Could it have something to do with Poweramp? I was playing around with the settings to see if that was causing it.
[Nexus 5 Original Android Development] omvir:
It could be, I'll try stock player tomorrow morning.
[Nexus 5 Original Android Development] The-Nazgul:
Stutter problem while playing Spotify with screen off still exists but is much better now. Happens around every 1-2 minutes.
[Nexus 5 Original Android Development] Wenzo2:
[MENTION=3292224]franciscofranco[/MENTION]

Really interesting feature for me it's set the brightness for all steps.

for example:

200 lux = 10

300 lux = 15

the stock brightness is too high.
[Nexus 5 Original Android Development] jphilippon:
Amazing work. Down to 3%, 12 hrs total.

Heavy usage. Games took up about 3 hours. If not more.

Specifically a game with a blue tooth multi-player connection was 2 of the 3 hours.

Very impressed. (been sitting on the charger while at home w/no usage. no false screen time. :P)

sent from my Nexus 5
[Nexus 5 Original Android Development] ChriKn:
[MENTION=3292224]franciscofranco[/MENTION] on my end soundstutters became really worse. It is now constant with slow downs and this "tape sounds" and even during screen on... Back on r13 and nothing so far. Before on r 13 it was once every 10 minutes or so... Only listening to local content using poweramp. Everything stock in kernel settings :(

Let me know if I can help by playing guinea pig !
[Nexus 5 Original Android Development] beaver2233:
Try using a different music player app?
[Nexus 5 Original Android Development] ChriKn:
Now that is interesting. Back on r14 and it is much better. Only difference si that now I have perfect coverage and wifi in the city, when before I was on the germain border with crappy to no signal ... May it be linked ?
[Nexus 5 Original Android Development] atz6975:
Massive bug, cancel Paris trip!

This morning I tried to autoflash r14. My N5 rebooted and my N7 2013 fully stock but running FKU aswell prompted me to update kitkat....

Log enclosed
[Nexus 5 Original Android Development] Moh_Jay:
Well if you are streaming then yes bad connection plays a big part in music...
[Nexus 5 Original Android Development] mythenmetz:
Don't get any mobile network with r56 on carbon. I enter the pin when it boots, but then I don't get my mobile network. Reflashed r55 and it works fine. Any suggestions?
[Nexus 5 Original Android Development] franciscofranco:
Then don't UV, I don't care if you crash your device due to extreme undervolt. Its obviously not FKUs fault, its like saying my morning vanilla machiato double shot is responsible for Britney Spears horrible voice without auto-tune.

Coincidence, not related.
[Nexus 5 Original Android Development] Tylog:
Sarcasm on

Wtf. The 'Holly Mother ' UV doesn't work as before, fix it !!!

Sarcasm ?

Unbelievable...

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] darksora145:
I don't understand why there is a need to Uv anyway. It's not good for your phone and it doesn't save battery life and it makes a unstable so what is the real benefit of undervolting?
[Nexus 5 Original Android Development] BRiANj64:
UV is nothing franco would ever care about rather then actually allowing you to do it. I don't think franco would even bother adding UV if not for the community.
[Nexus 5 Original Android Development] Tylog:
Ähm yes, that's exactly what my sarcasm mean... People UV, thinking it makes BIG differences , having issues and start crying, that's in all kernel threads the same :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] augoza:
Is carbon rom cm based? Because I'm using franco 55 as of 4 hours ago and its good so far
[Nexus 5 Original Android Development] Hopper8:
This is a post containing information by a professional chip designer on the subject of UV. Since reading it I no longer UV. Worth a read: http://xdaforums.com/showpost.php?p=34153152&nocache=1&z=352972205728292

Sent from my Nexu5
[Nexus 5 Original Android Development] TheHighlightGuy:
It's happened to me before where, for some unknown reason, Bluetooth Share will stay running in the background and just destroy the battery. If you check BBS (GSam Battery Monitor) and check under Apps, it should list it there. I had it set up where the car would auto sync the contacts from my phone, and I guessed that the process would simply get "stuck" and that's what was killing it.

Simple fix: once I noticed the phone was getting really warm out of nowhere and saw that Bluetooth was the problem, I simply toggled it and voila, it was fine after that.
[Nexus 5 Original Android Development] Arstoien:
That's a nice post and probably all correct but I (and I would think many others) undervolt not to gain battery life but to lower the phone's (cpu) temperature. I won't go into the benefits of running at lower temperature but sensible undervolting does that, no question. And of course once you go too far, your device will be unstable. And since this "too far" is so different from device to device, you loose kernel/rom dev support, if you uv.

In other words undervolt is not useless, it is quite useful for some. Not for all. As are so many other things...
[Nexus 5 Original Android Development] Tzfardaya:
It's one of those questions that should never have to be asked, but has to be everythime, because the answer is usually "yes" (much like in the pc world, the question when the computer won't turn on is "Is it plugged in?" (answer is almost always, no... go figure..)

Yes, the configuration app, that only sets kernel values is causing the kernel to crash on certain values... Right... It's like saying your car won't start because you changed the colour of the radio's led display....

People think it reduces heat... so their phone run's cooler and avoids thermal throttling... or at least that's the latest claim..

There's a couple of us in the community asking for UV to be removed... we thought he had intentionally removed the "set on boot:" toggle for UV on purpose... we celebrated... too soon it seems...
[Nexus 5 Original Android Development] occtec:
[MENTION=3292224]franciscofranco[/MENTION] just reporting on latest fku update, when setting temp from Fahrenheit to Celsius temp stats still only showing Fahrenheit.

EDIT: ALL GOOD! Clearing app data, fixed the problem.

Cheers [emoji106]
[Nexus 5 Original Android Development] schizophrenia:
[MENTION=3292224]franciscofranco[/MENTION] ..phone keeps rebooting once finished home screen after flashing r56

Log here http://pastebin.com/HYr1cbmk

Thanks

EDIT: cleared FKU data and ok now for 4 hours already
[Nexus 5 Original Android Development] brenopapito:
r56 have some issues related with uv... Just clean fku app data and enjoy !
[Nexus 5 Original Android Development] jawz101:
If I was a chip designer I'd say the same thing. But I'm not a chip designer.

It's analagous to tuning a car. An engine designer comes up with an engine design. Before it is put into production they have to test many to failure. For each engine they record spark timings, oxygen and fuel mixtures, rpm's, gearing at point of failure for each engine. Then come up with the values that average out to all engines that result in an acceptable, low failure rate. And then they put a buffer on those values as well for comfort.

Let's say my 2004 Mercury Marauder was tuned for 3:55 gears, stock intake, copper spark plugs and 180 degree thermostat. They tested 100 engine blocks prior to production to run 2 million miles at 3000 RPMs- only needing new oil and fuel as needed. 10 failed at x number of miles. Well, is 10% failure an acceptable rate? No. Let's adjust the programming for fuel/o2 mix or whatever the cause for failure was and try again. Until all 100 do well keep testing and say those tunes work- then make the production tuning a little more conservative than those since there grandmas and teenagers abuse their cars differently.

Well, I added 4:10 gears for a 1/4 mile, PHP cold air intake, Denso Iridium spark plugs, and a 160 degree thermostat. Let's call this Franco's Kernel.

Would I tune my car to the absolute custom thresholds of my car? Probably not unless I was getting paid to. Franco already does that anyway. I would, however, remove that 10% safety buffer on the fuel mixture(voltage) he doesn't mess with because I assume that stock setting for voltage is designed for the poorest performing machine to still have a safety buffer.

I personally go back and forth on undervolting but if I do undervolt I may bump the values down -25 just because.

Aside from that, the only other fancy thing I can think of in regards to undervolting is dynamic voltage scaling. I don't know if that's exposed in the kernel but, if so, it's more interesting than governors to me because there's already a bunch of governors available to handle frequency junk. I personally think there's no reason to adjust the frequency/clock speed because the kernel/governor already inherently handles those adjustments. Voltage seems like it -could- be tweaked but it may be already designed in the actual chip itself if chips have a controller on them but I dunno.

I don't know much except for day dreaming.
[Nexus 5 Original Android Development] Juzman:
Runs fine with -100mV @ 300MHz and -50mV for the rest.
[Nexus 5 Original Android Development] Hopper8:
Yes I understand that many do it for temperature control. I guess you pick the lesser of two evils... Higher temps and voltage the way the chip was designed, or lower temps and voltages how they weren't intended.

Yes I see what you're saying. But the internals of a phone are delicate electronics. I'm just some amateur who likes to mess with my phone. But I let the guys who understand the delicate electronics, take care of the delicate electronics.

That post was actually written for a 3 year old galaxy S2. In the three years since that phone, these Nexuses (Nexii? :p) have come a long way. The chip on an S2 runs between 900-1250mV for 200-1200MHz, in steps of around 50mV between frequencies of 100MHz. A nexus has maybe as little as 10mV between frequency steps, and its 2265MHz uses less voltage than the 1200MHz of the S2. As you can see, the hardware has become more delicate than in the context of the post I linked.

Yet, people UV in steps of 25mV, and some UV by even 100mV overall. What I'm saying is that a 25mv jump is relatively little for an S2 which that post was written, yet the chip designer was concerned. The 25mV UV on a Nexus is a huge jump in relative terms, especially considering a 10mV step between some frequencies. Be aware that you're messing with precision electronics, something that has been carefully designed by highly qualified people.

Sent from my Nexu5
[Nexus 5 Original Android Development] Aerowinder:
If worried about heat, reduce throttle temperature. I set mine to 55c. Never even comes close to that if you use per app modes.

Not sure why undervolting is even an option.

We know it does not improve battery. If it does improve temperature, it's negligible at best and the better way to mitigate the heat problem is stated above.
[Nexus 5 Original Android Development] Tzfardaya:
Good analogy, one flaw... You're swaping out hardware components with different tolerances on your car, all you can do on these phones by altering the voltage is change the gas type, adjust the octane... Yes, you can tune your car and gain some improvements using only the stock components, but you're either only going to get minimal improvements (unless you're talking diesel, but that a whole 'nother kettle of fish *ooh, look at me mix my metaphors* :p ) or blow out your engine...

So, lets see what happens if you change the octane in your gas (your car's owners manual calls for 92 octane... what happens when you try to be cheap and run 87)... well, depending on your engine compression, age, wear, etc... you're going to get premature fuel detonation (pinging) which, if you're very unlucky, can ruin your whole engine in a matter of minutes.. or, if you managed to luck out and get a more durable engine... it will (seem) to run fine, until one day it self destructs as well...

UV isn't as beneficial as people think... even with -100mv the device will produce almost identical amounts of heat under the same load... maybe 1 or 2 degrees cooler... if that, but given the thermal tolerances and mean time to failure with those tolerances, the recuding the heat generated by your cpu may extend it's lifetime one, maybe two days... the heat generated by charging/discharging the lipo battery is of far greater concern, that's the part that temperature is going to kill these days... (which is why, if you take the back off your n5, the "thermal guide" for the cpu/ram leads *away* from the battery...now, 1-2 degrees less heat from the cpu, will barely register on the battery...

So sure, while your phone may be tunable to work (seemingly) fine with a UC, all you're really doing is increasing the instability of the device for no real gains... 1-2% battery life over the course of a day (maybe...) and no effect on the number of charge-cycles of the battery...
[Nexus 5 Original Android Development] aaa12585:
Undervolted for the longest time without any noticeable degrading of performance. My phone had a few hiccups today with the r55-r56 kernel and i had a suspicion that the UV could be it. these posts only helped reassure me.

Keeping stock volts now and things are swimming! Thank you guys!
[Nexus 5 Original Android Development] Technecium:
I'm not yet either. I'm more interested in learning how all these parts and pieces work together.

I much rather spend an afternoon trying to figure out why something is the way it is, than playing a game.

I only post in here because I'm using your code. Hope you don't mind my ramblings here. It breaks up the day to day asked & answered.
[Nexus 5 Original Android Development] fatspirit:
Since you're able to use FK, I guess it's not.
[Nexus 5 Original Android Development] der_sascha:
Thank you for build 56

I have read that some people UV and some not

Is it right that UV not really makes battery drain better?

Or should I can UV 25 or 50 ?
[Nexus 5 Original Android Development] PetritH:
even though I don't totally understand your question im gonna answer :P, UV doesn't have any impact in battery, maybe the phone will be less heated.. so don't uv if u don't know what you're doing
[Nexus 5 Original Android Development] der_sascha:
I thought that it will help to get longer battery. But now I know that's not true. So don't UV anymore. Thank you for helping me.
[Nexus 5 Original Android Development] menting:
I won't say undervolting directly increases the instability of the chips, but it will take away voltage margin, and if enough is taken out, then it will start to affect the stability.

I worked with DRAM for ~11 years, and logic chips for ~2+ years, and I can say there's a fairly sizable benefit from undervolting if the part can handle it (depending on usage). All my colleagues (that also work on DRAM and/or logic dies) that install custom ROMs due it for the main reason of having the ability to undervolt and underlock.

The biggest tradeoff of undervolting though, is that you lose that voltage margin that was intended to provide stability.Some parts can handle losing that margin if they have more margin, while some can't. It's really a crapshoot if you don't get to pick your parts.

Usually parts are tested to +/-3% or +/-5% spec voltage to guarantee margin due to voltage droop from various reasons. If you aren't doing much with your phone, usually it's pretty safe to drop it by 3% or 5%, provided that the die packaging doesn't have much of a voltage drop from the power planes to the chip.

Power is proportional to the square of the % voltage increase/decrease, and proportional to the % frequency increase/decrease. Usually you'd be lucky to have a 10% voltage decrease, With a 10% decrease, you're looking at a ~20% power reduction, which isn't shabby at all. Of course, CPU/DRAM power usage pales in comparison to platform total power (LCD and radios use a lot more power) when the phone is being used, but for people like me who only have maybe 25 min screen on time a day, undervolting is a great benefit, since the LCD and radio portions are fairly small.
[Nexus 5 Original Android Development] PetritH:
No it wont man, so dont uv, doesn't worth it.
[Nexus 5 Original Android Development] Technecium:
I don't think this commit is correct. msm: acpuclock-8974: Modify L2 table for 8974

Current state:

1267200 66 1267200 7 1050000 617 810000 333 0
1344000 70 1344000 7 1050000 617 825000 356 0
1420800 74 1420800 7 1050000 617 835000 380 0
1497600 78 1497600 7 1050000 617 845000 404 0

Reverted:

1267200 66 1267200 7 1050000 2105 860000 333 0
1344000 70 1344000 7 1050000 2105 875000 356 0
1420800 74 1420800 7 1050000 2105 885000 380 0
1497600 78 1497600 7 1050000 2105 895000 404 0
[Nexus 5 Original Android Development] sordna:
Bottom line: every custom kernel setting, not just UV, is contrary to what google has engineered as most aporopriate. Therefore nobody should be asking to remove UV from FKU. Custom kernels are about freedom to tinker with our devices as we wish. Non tinkerers should stay stock. Some devices benefit from UV more than others. The N4 can be undervolted much more than the N5 which means the N5 is volted pretty optimally and the N4 isn't. The temperature drop in the N4 is undeniable. It gets really uncomfortable to hold under load situations without UV.
[Nexus 5 Original Android Development] aavvaallooss:
Just reporting. Nobody ask for a fix. I provided the solution by myself

My post was for people who UV. Not for Franco nor for your sarcasm
[Nexus 5 Original Android Development] chikimonke:
Has anyone tried using the Screen Casting with the updated Chromecast app? I can't seem to get screen casting to work, Play Services FCs each time I try. I wasn't thinking it was kernel related, but over in the Slim thread, someone mentioned they had the same issue on Bricked with the L commits, but reverting to Slim Kernel, or Bricked prior to the L commits, no more issue. [MENTION=3292224]franciscofranco[/MENTION] here is a log I got of the FC in case there's something there that might help. https://docs.google.com/file/d/0B7fls-m7-sKSNG5uQk84RVkzOTQ/edit?usp=docslist_api

Edit: so while that one user seems to have had success with switching kernels, I did not. Nor did it help the change between ART and Dalvik.
[Nexus 5 Original Android Development] franciscofranco:
Please keep posting :)

I don't understand why you think the commit is incorrect. The idea is to map a lower DDR frequency to those middle CPU freqs in order to save power.
[Nexus 5 Original Android Development] der_sascha:
hi i am searching for another good script for kernel settings like vomer_tweaks

are there some other which i can flash in recovery?
[Nexus 5 Original Android Development] Technecium:
The commit comment says, 800MHz to 617MHz. The commit changes BW_Mbps from 2105Mbps to 617Mbps.

I don't see any change in MHz.

If it is correct, these are the things I'm trying to get my head around.

I know you're busy and I wouldn't ask for you to explain the whole thing in detail but is there somewhere I can see the changes.

Is there another path I can cat?
[Nexus 5 Original Android Development] nrdl:
Olá [MENTION=3292224]franciscofranco[/MENTION] tudo bem ctg? ;p I got frequent reboots on latest r56 and found one other strange issue since r54 (tested after)... My alarms simply dont start.

Any ideas how to report you or how to test other options ? Im using stock clock app and running on slimkat lastest version.

Thanks!
[Nexus 5 Original Android Development] SynnyG:
XD you killed me, really, and made my day ! Thanks so much for that ^^

Return to topic: I've to report a bug concerning your app. I've seen that you've added a button to put the UV settings on boot, even if it's clicked, the settings doesn't stick on boot, at least for me ! Thanks in advance for your attention !