Julian Jeremiah wrote:That's beyond the point. Just giving feedback what I've encountered and just confirmed it again. I went to test it because of what jdidtht have said on the above posts.
From a1 to a4 GPU will stick accordingly to users preferences, however, on a5 and a6 (which I've just tested again), GPU will be set at max 320MHz irregardless whether you're trying to set it at 389MHz or 450MHz; we can set lower than 320MHz (200MHz) but not higher than this value. Well, unless all of a sudden Fauxclock has certain bugs which clearly show otherwise.yank555 wrote:Julian Jeremiah wrote:Do you mean do not change GPU msm-adreno?
Yes just realized now that GPU doesn't clock above 320MHz even when I set it at 389MHz, it'll shows at 320MHz. I think it started from a5 onwards
GPU cannot have changed prior to a6, as the code is untouched between a1 and a5. If you don't like the behaviour in a6, just look into init.d, change the script to echo 0 instead of 1 (or just delete it), you're back to full stock Update 7 code.Julian Jeremiah wrote:a6 seems to drain battery quickier than all other versions with exact same settings
Except for the GPU change it's 100% the same code
JP.
Send from my 'proudly eFused' Note 3 (n9005) running Temasek v85 on Yank555.lu htle v1.0b-beta3 (3.4.91) kernel.
a5 is just not possible
0 code change, 0 lines...
Look at the changelog.
Btw it will only scale up if under video load, which you cannot generate while looking atnit in fauxclock.
Only way to check would be through sysfs reading in adb while running a video intensive app (like a video benchmark).
JP.
Send from my 'proudly eFused' Note 3 (n9005) running Temasek v85 on Yank555.lu htle v1.0b-beta3 (3.4.91) kernel.
Edit : We are talking GPU, not CPU ?