[Nexus 4 Original Android Development] show-p1984:
There will be several choices, if you are not happy with them compile your own kernel binary from bricked source :p

It doesn't. Look below.

I am currently fine tuning ondemand to avoid this behavior.

Thank you for your report, busybox default path is xbin. (always was)

I would need source for full gamma control, or redo it myself, but why reinvent the wheel? =/

Don't mess with the thermal settings.

If you haven't touched them it is likely that your phone shut down because it simply couldn't handle the frequency, not because it was too hot.

There is something huge coming. Stay tuned.

(Yes I coded on christmas...)

The kernel is not altering the ui.

Thank you very much!

I will be very blunt:

I don't even know where to start as to how stupid that above post is.

Either you just didn't try it and tried to sell us a bunch of crap, or you are too incompetent to measure the current your phone draws from a power source. (another possibility would be that your chargers are crap)

There is virtually and practically NO DIFFERENCE in any way between an outlet charger with an usb plug or one with a directly connected cable. Apart from the obvious differences of course: It has a connector instead of a directly connected cable.

How do you think they work? Both are just throwing some power on +/- of the usb plug and grounding the shield while they ignore the data lines.

There is a security mechanism in mobile devices capable of charging over USB, it ensures that if another device is detected (like a PC, for which we obviously need the data lines), there is only 500mA of current drawn from that power source. Why? Because USB2.0 can only give you that much. (USB3.0 = 1A, but since the majority are 2.0 we are limited to 500mA)

USB fast charging does the following:

It disables that security mechanism so that you can draw more power from USB sources, plain and simple.

Now what can go wrong? - Usually nothing. Motherboards usually have a fail-safe built-in that cuts power to the usb port if too much current is drawn, or at least limit the amount. But what if your motherboard does not have such a protection? Of if it is just malfunctioning?

Well congratulations, depending on your luck and the length of the 'overcharging' you either have a broken USB on your mainboard, a broken mainboard, or a broken phone + mainboard. Worst case scenario: ~600€ down the drain because you couldn't wait 30 minutes longer.

I had that symptom a lot in my µC days. You solder a board together and don't see that slight bit of soldering tin short circuiting something. I blew my motherboard + µC before I switched to USB hubs, which are way cheaper to replace. (But tbh it never happened to me again, since I always carefully checked the boards from there on)

Conclusion: It isn't worth it for me.

In the past I have added that feature to the pyramid kernel only because a lot of people asked me to do it, but to be perfectly honest: I have never used it and didn't even add an option in Aroma for it.

They are not used for scaling, but they are still there. I could remove them from the table though, but that is something for the end of my todo list :)

Nope. Mainly because of two reasons:

1. The power supply is very unstable at those low power values which produces random errors.

2. I doubt that it even sticks. I tested 384Mhz with 400mV and 702Mhz with 600mV, which is just nonsense. 700mV on the other hand seems to work perfectly since 702Mhz freezes my phone on 700mV.

The kernel does not influence your ui.

KControl will be on the market soon with some epic stuff :) (paid and free)

Just let me get some stuff into the mako first :)

You haven't looked once at the code, right?

There are no arithmetic steps saved with your approach, we would just have one more array in the code. (about which the compiler doesn't even care)

And if people can't do this math: (2-1)*2, then they should probably fall of the chair and die immediately for the sake of evolution.

Seriously now, I won't change code because it makes stuff easier to tweak but the code harder to modify and understand.

Blame androids webkit, I have written a post about that already on the first few pages.

No. Look above.

The rest of that sentence, since posted?