[HTC One X] HebeGuess:
Rich, last time I posted this and you snapped up..

Hopefully not this time.. Don't click spoiler button before you back from rest.. :D

==============================================

Broken CPU Max Frequency Capping:

View attachment 1842556

First, I am not even a kernel guy but wishes to sorting out why CPU capping isn't actually working in Venom Tweaks.

Seems like issue was caused by a series of Power Management QoS from nVidia patched during Jan 2012, which resulted in linux either 3.0 or 3.1.

Thus, the patches take effects on HOX since JellyBean update with new linux 3.1 kernel.

Some extra findings during my researhes, they are lot of mainline app also under the NOT working list.

References:-

http://lists.linux-foundation.org/pipermail/linux-pm/2012-January/033463.html

http://comments.gmane.org/gmane.linux.power-management.general/26522

https://android.googlesource.com/kernel/tegra/+/4d8c37b3d77830ac223dde3d6f644f2415ca70a6

SU access logs of Venom Tweaks changing CPU Frequency Limit:

echo 4 > /sys/power/pnpmgr/hotplug/min_on_cpus;
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo 1400000 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo 0 > /sys/power/pnpmgr/hotplug/min_on_cpus;
exit

The scaling_max_freq will be ignore by the kernel while Power Management QoS in effects.

Echo the desired maximum frequency to /sys/module/cpu_tegra/parameters/cpu_user_cap should solved it.

It's better to consult kernel expert for more thorough understanding and see if any better ways to do it.

And also according to su log, changing screen off max frequency didn't commit anything related.

echo 4 > /sys/power/pnpmgr/hotplug/min_on_cpus;
echo 0 > /sys/power/pnpmgr/hotplug/min_on_cpus;

Since, there are already notification+drawer animations now.. This would be neat too..

AOSP Statusbar Pulldown Dimming Effect:

[YOUTUBE]MTaPPdq3394[/YOUTUBE]

I have been digging into related sources code for last few days.. It looks like I finnaly got it figure out..

HTC didn't breaks it but removing few lines of codes that makes it happened..

Corresponding sources : [SystemUI.apk] com\android\systemui\statusbar\phone\PhoneStatusBar.java

// Sense 4+ (JB 4.1.1: One X) / Sense 5 (JB 4.1.2: HTC One)
protected void updateExpandedViewPos(int i) {
...
saturate((float)(l - i1) / (float)(j - i1));
...
}

// AOSP JellyBean 4.1 (from decompile version)
// References: https://github.com/android/platform_frameworks_base/blob/jb-release/packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
if(l != mTrackingPosition)
{
...
float f = saturate((float)(l - i1) / (float)(j - i1));
if(ActivityManager.isHighEndGfx(mDisplay))
{
int j1 = (int)(176F * (float)(1.0D - 0.5D * (1.0D - Math.cos(3.1415901184082031D * Math.pow(1.0F - f, 2.2000000476837158D))))) << 24;
mStatusBarWindow.setBackgroundColor(j1);
}
...
}

For future refencences: Since Android 4.2 added Quick Settings google dicided to migrate the code to the referenced class PhoneStatusBarView's new function panelExpansionChanged() with more furnished codes too.

References: https://github.com/android/platform...temui/statusbar/phone/PhoneStatusBarView.java