yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] LiquidSolstice:
"Improvements" don't often happen in a vaccum. There are always side-effects. You don't just ignore them because "you got a small boost in battery".

The decision on whether to spend time/trouble on it is NOT the user's, it's Franco's. If he doesn't want to support issues it has, and people refuse to take off their UV before asking for help, he can eliminate that problem by not including the ability in the first place. Then, there are no variables, and better yet, people who are incapable of or unwilling to listen will go use another kernel and will pose even less of an issue to him.

If all you're arguing is pedantic definitions, then this conversation is equally useless.
[Nexus 5 Original Android Development] LiquidSolstice:
No my argument remains, it's just now I can clearly see you're just being pedantic; you don't like the word "useless" because your definition of useless is different from everyone else's.

Hence, as this conversation doesn't contribute anything to the thread, and it's probably annoying the only person in this thread who matters (Franco), it is, in your definition, just as useless.

Good day.
[Nexus 5 Original Android Development] menting:
http://www.merriam-webster.com/dictionary/useless

"not at all useful"

I'm going off this strict definition, which is the official definition.

That means if there exists a case where the benefits outweigh the drawbacks, it can't be called useless.

It's all logic imo.

Clearly you have not worked in semiconductors before.
[Nexus 5 Original Android Development] LiquidSolstice:
http://dictionary.reference.com/browse/pedantic
[Nexus 5 Original Android Development] menting:
True story. I admit.

Always go with the spec definition, and you can't be wrong.
[Nexus 5 Original Android Development] LiquidSolstice:
;) No hard feelings.
[Nexus 5 Original Android Development] yorici:
In my signature, second post of the thread linked;)
[Nexus 5 Original Android Development] simonarturo:
I think the safest course of action would be to add a better warning in FKU so that people UVing know better than to come here and complain. Some kind of prompt when ppl go into that option that warns about stability issues and marginal gains, etc.

I know there's a small msg if you long press voltage control but it doesn't seem to convey the message effectively
[Nexus 5 Original Android Development] JNewms:
It wouldn't make a difference. They still wouldn't read, and then they'd come here and complain with no logs
[Nexus 5 Original Android Development] pkelly517:
There is the obvious effect of removing undervolting.

The Franco thread activity may slow to a crawl. We may only see questions about Dalvic cache cleaning.

And CM compatibility.
[Nexus 5 Original Android Development] galakanokis:
I think the safest course of action would be for Francisco to remove under volting and if people really wanted they can figure out how to add the code to the kernel themselves.

In the context of this kernel use under volting is useless. Unless you need to squeeze out a few more minutes of mine craft while sitting on the can.
[Nexus 5 Original Android Development] Ryrynz:
Squeeze on the can, squeeze on phone.

Keep squeezing guys. [emoji31]
[Nexus 5 Original Android Development] Tzfardaya:
You're more than welcome do to just that...

It's known that lower frequencies require less voltage, and this is worked into the design.. Undervolting and variable voltage are a little different... Yes, both alter the voltage at a frequency, but one is designed and the other may put unnecessary stress on the device..

No, the decision is francos, because of the number of people who are unable to uv properly. (takes weeks to dial in the exact level of it your phone can handle without any issues... Which can all be undone by a kernel change that alters the sensitivity...)

The safest course is to remove the ability to undervolt entirely...

Now, whether it's removed from the kernel, preventing it entirely, or just removed from fku, making it harder to uv, are separate issue especially entirely...

---------- Post added at 05:52 PM ---------- Previous post was at 05:51 PM ----------

Yeah, like in the n4 Franco thread where he explicitly States in the op that issues caused while undervolting will not receive any support... But they still show up every week complaining about sod, reboots, and myriad other glitches caused by their undervolting....
[Nexus 5 Original Android Development] scrack26:
Have this experience before. Change Charging cable.
[Nexus 5 Original Android Development] hjjiang:
Seems that the latest beta has fixed this issue :)

On a side note, how are the backup/restore images sorted? i am getting boot-rXX.img is random order

the lowest number i have is boot-r39.img but it is not at the very bottom but somewhere in the middle
[Nexus 5 Original Android Development] AutomaticFailure27:
Umm... Why are we all arguing?

Thanks Franco for the wonders you do to devices. Keep it simple. To the point. No bs with you. It just works.
[Nexus 5 Original Android Development] Tzfardaya:
Mostly because we can... And we are trying to see who has the biggest e-penis :(
[Nexus 5 Original Android Development] franciscofranco:
Pushed r57, just some code improvements.
[Nexus 5 Original Android Development] Technecium:
Picture these two when you read the posts, it's pretty damn funny.
[Nexus 5 Original Android Development] Ryrynz:
Had some troubles getting this installed at first.. Downloaded and just sat on saying it's flashing but didn't.. Rebooted and tried again and it went fine. Think I was one of the first to download it.
[Nexus 5 Original Android Development] Lodion:
Flashed without issues so far. Stock 4.4.4 with Xposed, no UV ;)
[Nexus 5 Original Android Development] Red5:
R57 undervolted my whole system by -75. Franco is such a troll.
[Nexus 5 Original Android Development] tlrsax54:
I'm still amazed at the latest changes...lowered my boost to 652mhz and 250000 boostpulse...still smooth, battery is great :)
[Nexus 5 Original Android Development] PhantomGamers:
I turned boostpulse to 0 and it feels exactly the same ;_;

Franco has hax!
[Nexus 5 Original Android Development] franciscofranco:
/trollAllTheThings
[Nexus 5 Original Android Development] SketchyStunts:
I don't post much on here anymore but I wonder... What are some of you guys doing? I haven't had any issues with any revisions of this kernel. Reading through the last 10 pages is ridiculous. If you don't know what you're doing & change settings of the kernel & have issues, don't complain.. post a log at least. Without that, your issues are pointless & just garbage posts to sift through. This kernel is rock solid on my end & the vast majority of others.
[Nexus 5 Original Android Development] Ryrynz:
Is it boostpulse_duration most are changing to 0? I have input_boost_freq at 1036800 and highspeed_freq at 1190400. Any tweaks here worth it?
[Nexus 5 Original Android Development] UpSpin:
It's sad that Franco wants to remove the UV just becuase a few people don't understand how to use it.

A lot of people also unlock their device and install a custom kernel and don't know what they're doing, they complain that something is broken and complain they can't update via OTA. They also complain that ROM a doesn't work with Kernel b. Best is Franco just stops developing his kernel so he doesn't get annoyed by those people any longer.

I could continue this list. There are always people out there who don't have a clue what they're doing, yet they still do it and complain that something is broken.

Why does Franco allow tuning some parameters in his app at all? I mean, 99% of people changing those parameters don't have the slightest clue what they're doing. Even worse, people change it, use their phone for 1 day and proudly conclude (to foster their statement they post a random battery discharge graph): improved battery life. REALLY? Kids, that's not how objective testing works. And your results are meaningless.

Still, Franco keeps those settings. Should he remove them because kids misuse it? I don't think so.

Franco could simply make the risks of undervolting more prominent in his app. For example deactivate the undervolting option by default and you have to go in the settings to enable it. Or if you applied some undervolting scheme the background of the undervolting button gets red and a small disclaimer added like 'don't report bugs as long as you undervolt!'. He could also show the stock voltages next to the newly set voltages, so one easily sees how far he undervolted his phone. Once the difference is larger than let's say 25mV make the background of this entry red, add an exclamation mark and disclaimer: Instability possible.

People who say undervolting is uselesss have no idea what they're talking about.

Some even said something like 'yes, by UV the device might not get as hot, but battery life remains unchanged'. I don't know if the people who undervolt and don't know what they're doing or the people who post such contradictory bull****, are worse

Just take a look at some datasheet of a micrcontroller and you'll see the benefit of undervolting. Just inform yourself about semiconductors and you'll see that there's a benefit.

The impact of UV might be small, because you undervolt by max. 75mV, yet it has some impact, maybe more than tuning some settings in the FKU app.

Thus I hope Franco keeps the UV option in his kernel and in his app. It's a handy and useful tool.

Btw: Thanks for fixing the scrolling bug in the Backup/Restore settings, everything works now.
[Nexus 5 Original Android Development] Clauu:
I really don;t know why you people make such a drama from this uv thing.. 'stop uving it will blowup your device; oh no franco will remove it; the end of uv is here no no whyyy' wtf?! uving won't do any damage to your chip instead oc will do at higher voltage values, less voltage = less dissipated heat = longer chip life. Franco or any other dev isn;t responsable for your device uv instability problems so go and test your uv properly before yelling here. But instead franco should warns as on any kernel thresholds/sensibility changes that are related to uv otherwise it will be a silly situation when on a prev test image uv was just fine with days of usage tests etc and on another test image there will appear instability problems due to that
[Nexus 5 Original Android Development] UpSpin:
just a small follow-up:

Instead of telling people to stop UV because it can cause instabilities better try to explain them why a previous stable UV setting became instable after a kernel update suddenly. That's what confuses them, that's the reason why there's such a huge discussion, that's the reason people say the latest kernel update is broken. Because their device worked flawlessy with the previous kernel and no one tries to explain them the reason.

The answer is simple:

There are 14 frequency states accessible for the CPU governor, each with a specific voltage setting. Yet, the governor doesn't use all of them equally. Some more, some less, some almost never. And not always are those states used on all cores! It depends on the kernel and the governor.

By changing the voltage settings in FKU with the -25mV button you reduce the voltage of all those states by the same value.

Afterwards you most probably test for stability, which means the 2265 MHz state and a few others get used while stress testing and the 300MHz and a few other states get used while idling. It's stable, so you assume everything is fine. But you haven't tested all the other states. And you haven't tested each core in all those different states for stability. You also haven't tested all possible combinations, like Core 1 at 300MHz, Core 2 at 960MHz, Core 3 off, Core 4 at 2265MHz.

It's possible the custom voltage setting for the 960MHz state is too low for Core #3, yet you'll never notice it, because this state on this specific core got never used.

Now Franco tuned his kernel and changed some minor settings, which causes previously not often or never used states to suddenly get used constantly. The probability that the too low voltage for the 960MHz setting on Core 3 cause a crash now increases significantly.

I undervolted by 75mV and it was stable. With a kernel update however, once every few weeks, especially if I played a specific game, it rebooted. The culprit? The 422MHz and 652MHz state had a too low voltage. Increasing them removed the reboots and the phone is stable again now.

So as long as you UV you're always risking instabilities because you don't have the test equipment to thoroughly verify the voltage settings for each state and each core at all possible temperature values and variations. Still, it would be a pity if Franco removes this powerful setting, especially with the motivation that people don't know how to use it. Because then he can stop working on his kernel and app altogether, because most people don't know what they're doing.
[Nexus 5 Original Android Development] fatspirit:
Sisyphean task.
[Nexus 5 Original Android Development] deepakanand:
I am facing some weird issue from some time. All of sudden, my phone just stops charging and battery starts to drain.

To fix that, I have to flash some other version (sometimes older version/ sometimes newer) of the kernel and then it starts charging. But again after few days, same issue appears.

Please let me know if any log is required to debug. Will post the same.

Thanks.
[Nexus 5 Original Android Development] ben_pyett:
try replacing charger and/or cable, I recently had significant issues with charging caused by faulty original cable
[Nexus 5 Original Android Development] haasgo:
Maybe faulty hardware? Logs wud make bug detection easier though!
[Nexus 5 Original Android Development] occtec:
Thanks [MENTION=3292224]franciscofranco[/MENTION] never had an issue with your kernel, period! Obviously some need to read, then read again before they ever consider using a custom kernel let alone a custom ROM. Thanks mate, all your hard work is always appreciated!!! Have purchased all your apps as appreciation.

Cheers Mate ?
[Nexus 5 Original Android Development] ben_pyett:
Take a break.....

Don't abuse each other or the thread. Move along.

Edit: moderator thread clean up occurred
[Nexus 5 Original Android Development] jordirpz:
[MENTION=334712]francisco[/MENTION], can you add the test.img to play games in fku?

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 5 Original Android Development] JNewms:
What do you mean by that?
[Nexus 5 Original Android Development] jordirpz:
When i flash a test.img via fku, add one more count in play games?

Here
[Nexus 5 Original Android Development] ben_pyett:
I imagine that would be difficult as you don't flash test kernels through the application so how would it know? It would also encourage people to try test kernels which aren't for the masses.
[Nexus 5 Original Android Development] JNewms:
I see what you're saying, but that won't happen, for the exact reasons that [MENTION=354700]ben_pyett[/MENTION] stated.
[Nexus 5 Original Android Development] om22:
The CPU frequency sometimes doesn´t reset to 2265mhz after thermal throtteling for meµ. Instead it stays at the throtteled value. Anyone else has got this problem?
[Nexus 5 Original Android Development] jordirpz:
ben_pyett=Francisco Franco?? Not my son ?
[Nexus 5 Original Android Development] Aerowinder:
Which kernel version are you running? r55 or r56 should be the last versions to have this problem.
[Nexus 5 Original Android Development] akaHardison:
(After updating to r57,lots of kernel panic.But how to send you the last-kmsg?Using slimkat 6.2.)

Look the previous post at the thread.Kernel panic just because I UV the chip too low before r57(600mv is very stable at r55,PVS3 chip).After increasing 25mv of the voltage,my phone seems stable now.I am going to watch it.
[Nexus 5 Original Android Development] bjoswald:
Amazing kernel, Francisco! Love the app too; purchased Pro version straight away. :good:
[Nexus 5 Original Android Development] tlrsax54:
Duration set to 0 will pretty much disable input_boost_frequency I believe. Some people have done it and noticed little to no consequences, you can always try it out and if it feels laggy then set it back.
[Nexus 5 Original Android Development] sordna:
This. Some EXCELLENT suggestions in this post. I would just add a persistent notification to FKU saying "You are undervolted, do NOT report reboots and crashes."

But we must keep UV, it's the main reason I purchased FKU for my Nexus 4.
[Nexus 5 Original Android Development] californicated:
Can anyone confirm that frequency is going back to 2,2ghz with r57?
[Nexus 5 Original Android Development] Stanlehh:
r57 not looking good, flashed and my phone boots up and reboots shortly within minutes, happened for the 4th time as I'm typing this.
[Nexus 5 Original Android Development] akash3656:
(Y) are you UV-ing? If you are then disable UV plox.
[Nexus 5 Original Android Development] JNewms:
Unless you have a log to share, it'll be assumed it's something with your setup causing it. I've been testing this, across 3 different ROMs so far, and not one issue.
[Nexus 5 Original Android Development] Stanlehh:
must be the UV that was saved previously, removed it and it seems better now.
[Nexus 5 Original Android Development] blueren:
Redownload, and reflash. (Remove any unnecessary UV set on boot)
[Nexus 5 Original Android Development] msgfromside3:
I hate franco now. I thought I finally got over with flasholic behavior with N5 and his stable kernel, and told myself I am not going to flash new kernel versions every time they come out. But I did it again and again. Flashed r55 and it was so good and thought I wouldn't need another version. Flashed r56 next day it came out, and I have been so happy with it. Flashed r57 with finding myself saying, "damn.. another one? I can't miss it!!". I feel I need to do something for rehab. Maybe I should play Mario Kart 8 more. lol

Awesome job, Franco!

PS: I have decided to contribute filling this forum with positive posts to downplay all the non-sense negative comments (I am telling you folks complaining with UV on).
[Nexus 5 Original Android Development] Lownita:
It's it possible that r56 and r57 are a bit worse performing than r55? I seem to get some scrolling and animations lag here and there.

Tapatalked from my Nexus 5
[Nexus 5 Original Android Development] GtrCraft:
Give it some days, r57 is out for about a day now. You can't say it doesn't work as good yet
[Nexus 5 Original Android Development] El Daddy:
So this morning I wake up, clean up a bunch on nonsense here and sent messages to some of you. Then, I go out to the golf course and play a nice relaxing 18 holes of golf with my Dad. I come home and what is waiting for me? A whole bunch more of the same nonsense.

Think about what you guys are arguing about.... It's--a--KERNEL!

Log off and spend some time with friends and family instead of arguing with people over the internet. It's the weekend after all.

The next time I have to come here for reasons other than my own leisure, I will be taking action. Can't we all just get along?

Thread Cleaned.

-El Daddy
[Nexus 5 Original Android Development] The Gingerbread Man:
Stop under volting and update to the latest version and be happy. Really we don't need to play with settings. To be honest out of the box this kernel is fine.

If anyone wants to save battery and reduce CPU heat under clocking is the safest way to proceed. If you want to read up on how to properly post a proc/last kmsg then info is in my sig in the learner lounge.

On a personal note, removing under volt is a good idea from Franco. Let's take a vote.....

Some say nay

Others say yay

Those who say nay then answer me this. Do you know the snapdragon 800 SOC to expert level?

Still have your hand up?

If not then stop pretending you know better than paid professionals / experts and be happy with the free kernels provided by Franco, or move on if you wish to persist in saving a little temp vs stability. Battery savings might be there but for each reboot it costs you at least 1% battery. So now is the time to choose if your happy with the paid professional opinion and Franco's voltage decisions.

I know this decision has ruffled some feathers but at the end of the day place your self in Franco's shoes. Show some empathy here guys. Imagine how you would feel people ****ting all over your thread because they are incompetent / ignorant / can't read (wonders why they use forums?) users posting bad reviews because they are for the above reasons (or not willing to search) why their phones wont work when you remove electricity from it which is bottom line what it needs to actually run and function.

To end this on a nice level, if you were to purchase the paid Franco kernel updater or stand alone per app mode apps then you get full control of which apps can use your CPU power and limit the voltage used in a safe way by placing a limiter onto your apps for how much power they are allowed to use. Personally I find a Max CPU speed of 1.7ghz plenty.

I am now removing under volt setting from my settings post.
[Nexus 5 Original Android Development] justibasa:
Thank you good sir. :)
[Nexus 5 Original Android Development] Hopper8:
I like this. I will contribute to the positive posts :)

Franco, thanks for your hard work! Purchased your FKU on the first day I had my N5... But you know what? It's almost unnecessary! Your kernel at nearly default settings is a beast :) I think I will have to find a few more of your apps to buy to say thank you :)

Sent from my Nexu5
[Nexus 5 Original Android Development] The Gingerbread Man:
Don't thank me, thank the on-ominous being known as common sense. I picture it like a little toy red air balloon. Small and fragile but takes the simplest of idiots to shoot down with an arrow (to the knee).

Fail Joke I know I never played skyrim.....
[Nexus 5 Original Android Development] sordna:
Good idea, Francisco can you do a poll on this ?

Anyway, to avoid all issues related to UV, Francisco would have to remove this setting from the Nexus 5 kernel itself.

My vote is regarding FKU: it should keep the setting because UV on other phones (Nexus 4) is useful to avoid the phone burning your hands under load. My phone really gets uncomfortable to hold under load.
[Nexus 5 Original Android Development] The Gingerbread Man:
I flashed KitKat back to my n5 and n7 2013 from L just because stock kernel wasn't enough. I missed too much from my n7 in particular which took me a week later to flash back (mostly from guilt knowing my Mrs would kick off having to download her apps and **** again) but both devices are much more responsive and less laggy with better battery life than stock.

This is why we should as users appreciate xda and the devs that provide their work here for free.
[Nexus 5 Original Android Development] combatdeity:
I have disabled inputboost, I've not noticed any real changes in smoothness,

Anyone else who has done it, have you noticed any battery improvements?

I live in an area of no/low signal so my phone is constnantly on a qi charger to stop it draining throughout the day.
[Nexus 5 Original Android Development] The Gingerbread Man:
It can be removed device specifically I believe. If I'm not mistaken the app is broken down to device specific parts depending upon which device is origally detected

But I do know all devices should have something that looks a little like
[Nexus 5 Original Android Development] ChriKn:
If you had read my first comment, (litteraly 2 posts above) you would have seen that I DO NOT stream music, I only play local content from the phone's memory...
[Nexus 5 Original Android Development] blacknet101:
Battery life has been awesome on r13, idk if I should update to r14!

Transfered a new ROM that's why u see the battery go up but other than that! Texting and Tapatalk all day and 3 45min phone calls and taking a couple pictures.
[Nexus 5 Original Android Development] Moh_Jay:
Overlooked that my bad. I used Google play music for my 10 drive screen off and music played fine from sdcard. Could possibly be the app conflicting with KitKat.