Originally Posted by Muntey
Wow, how are you cooling that? It must get pretty damn hot! My Milestone gets hot at stock clocks.
It stays relatively cool under load. It helps that most of the casing is aluminum. Should i be lapping my battery cover and applying thermal paste/pad? Nah, but that would be funny. Strange thing is that 2016 is unstable, even with an additional 25mv bump in vcore. I only clock that high when i can make use of it. I disable scaling becauase the switch time of the vdd and clk is not specific to upclocking or down clocking. So, when you drop down to 245mhz from 1996mhz, the vdd drops first, couple microseconds after, the clk follows.. see the problem there? This scenario is fine for upclocking, as it gives the vdd time to stabilize before cranking up the clock. But reaching the vcore of 245mhz before switching the clock from 1996 is a guarenteed lock up.
So yeah, need upclock/downclock specific values for vdd_switch_time and acpu_switch_time.
I'm happy with having a big boost in perf when i need to tar xjf *backups. Doesn't seem to do **** for the awful io perf (relatively speaking, its great.. for a phone). It just frustrates me that my disk speed is the bottleneck when downloading something (C6 SDcard too). Turning the wifi PM off seems to help with large cifs transfers (iwconfig eth0 power off). The same holds true for broadcoms desktop linux driver. But I digress. Yep. 806->1996.8 .. that beats my old opty 165..