[Nexus 5 Original Android Development] show-p1984:
The new s2w and dt2w versions I recoded for the n5 are the easiest to port yet.

It should be no problem for any dev to add it to a kernel.

No. Stable = the features are not cause issues when turned on.

Due to the N5's hardware layout and the fact that we don't have any documentation about the chips used that battery drain is not an issue, but rather expected.

There is no need to wait. If it's on my website it's released.

No.

Turning on one of them will automagically prevent touch screen hw from sleeping. Turning the other on/off won't change that.

Absolutely wrong. Look above.

The only way to fix this would be to incorporate the proximity sensor into the touchscreen sleep prevention. But that would mean additional drain.

Also: This is not a kernel bug, it's actually an android bug. Android should disable the touchscreen inputs on it's own, they are just not doing it (anymore, it was done prior to android 4.1 iirc) because usually the touchscreen will be disabled.

No. There will be an option to do that soon(tm)

Look above.

No. KControl doesn't use an init.d script to set the settings. KControl uses Android's bootup callback to know when to re-apply your settings.

This option is safer, since Android won't issue these calls in safe mode and we ensure that the settings are only being applied after the system has finished booting up.

That's why both are disabled as default. If you can't live with the trade off, don't use those two features.

I am still asking: Version? Log? Send the crash report? Google tells me that no crashes are reported for 1.8 or 1.8.1.

That's bs.

Enabling one or both will make no difference in battery usage.

That's why those features are disabled by default... Wait a second, I wrote that already at least 4 times. STFT.

That explains one crash log I got from a user running KControl 1.7.2. It was crashing on a suddenly closed root shell, which I now see why this could have happened.

for GPU Memory to be available KControl checks if "/sys/kernel/debug/kgsl/kgsl-3d0/memfree_history" is existing.

The exact command used is: "ls /sys/kernel/debug/kgsl/kgsl-3d0/memfree_history"

If that doesn't return an error, an empty string or no string at all the condition will be true and KControl will show "pass", otherwise it will be "fail".

My kernel has recommended settings, however those might not be your preferred settings, so set it to whatever you want.

I can give you a few, quick hints: (some may already have been set as default and some may not be supported by your device. Like vdd, freqs, etc...)

CPU->Frequency->Min: 96Mhz on all

CPU->Voltage->-50mV

Thermal->+5°C for performance, -10°C for a cooler phone (on all, except shutdown)

MPDEC->Simple-> Hotplug cores Fast for performance, unplug cores fast and hotplug cores slow for battery.

MPDEC->Simple->Disable boost for battery, this might cause the typical <Android4.1 microlagging while scrolling.

Scheduler->Autogroup [X]

Scheduler->Childfirst [X]

Scheduler->CFQ on all

Scheduler->CFQ Settings->group_idle to 1 for all

Vibration->80 (slightly stronger, more like n4)

Ondemand already has everything set to optimized values.

Benchmark scores are subject to throttling which occurs earlier on lower PVS id SOCs. Check your PVS id and if it's below 3 you know why.

Why are lower binned SOCs earlier throttled? Because they need more power to run stable which equals more heat.

If you show me a repo where it is actually being developed and tuned for the n5 I will. Otherwise adding 1 million governors that are not tuned for this device just makes no sense, at all.