[4-22] nueClockControl 1.1 - underclock your touch pro/diamond/titan/etc.

[slypher]

OMG, this came completely outta left field. Glad to see the new app, will be installing today and reporting results after trying it out. Thanks Nochem!!

-s

[vernonlbrown]

Originally Posted by gsvnet

Well, I'm using 384 right now, and it doesn't seem much slower at all.

I'm using 256 and my Tp doesn't drag.

[toolz]

i have been having wicked overheating problems while tethering which i solved with a Xbox cooling fan pad but if this could fix it that would be awesome.

I'm currently testing tethering with no2chems overcharge and clock program set to 128. will post later if it helps heat. it wasn't taking long to stop charging

[toolz]

set at 128 with the keyboard open and tethered the phone got hot enough to quit charging, gonna let it cool and try the 64 setting or whatever the step above 19 is

[no2chem]

Originally Posted by toolz

set at 128 with the keyboard open and tethered the phone got hot enough to quit charging, gonna let it cool and try the 64 setting or whatever the step above 19 is

I think the heat coming from the charging..is well, from the battery itself.. not from the processor =p I think there might be a way to override the temperature check, but I haven't looked into that yet.

although, maybe just enough heat is coming from the processor the kill the charger, who knows. and maybe you can try 19 too, havox22 had it work for talk without ill effects...

[noobified]

This would be awesome if it solves the tethering heat issue! Can't wait to hear your updates!

[chronster]

OK, please correct me if I'm wrong, but underlocking the cpu can only draw less energy to a point. I mean, the difference between 19mhz and 200mhz would be the same because the device is still sending the same voltage to the cpu right? Unless the device automatically determines what the cpu needs to function correct (which I highly doubt) you'll need to tweak the voltage somehow also.

Think of it this way: I've got a cpu in a computer running at 4ghz at 1.5v. If I underclock the cpu to 2ghz, the vcore setting is still 1.5v so the same amount of energy is still being sent, just not being used, right?

As far as heat goes, it's the same. If you're pushing the limit at which a certain amount of voltage achieves a certain clock cycle, then there's going to be some resistance which causes slightly more heat than if you're simply over volting your cpu, but it doesn't matter if you're running 10mhz or 200mhz, the voltage is what's causing heat. Too much voltage causes heat, and too much resistance causes heat. Finding that sweet spot is the key.

[toolz]

Originally Posted by no2chem

I think the heat coming from the charging..is well, from the battery itself.. not from the processor =p I think there might be a way to override the temperature check, but I haven't looked into that yet.

although, maybe just enough heat is coming from the processor the kill the charger, who knows.

yeah i know my heat problem is coming from a combo of charging, tethering and low signal strength. I was hoping that taking as many heat factors out of the equation as possible would allow me to tether and maintain charge. I don't think the CPU contributes enough heat for under clocking it to help this.

overriding the temp check would be scary but useful if the proper precautions were taken

[toolz]

Originally Posted by chronster

OK, please correct me if I'm wrong, but underlocking the cpu can only draw less energy to a point. I mean, the difference between 19mhz and 200mhz would be the same because the device is still sending the same voltage to the cpu right? Unless the device automatically determines what the cpu needs to function correct (which I highly doubt) you'll need to tweak the voltage somehow also.

Think of it this way: I've got a cpu in a computer running at 4ghz at 1.5v. If I underclock the cpu to 2ghz, the vcore setting is still 1.5v so the same amount of energy is still being sent, just not being used, right?

As far as heat goes, it's the same. If you're pushing the limit at which a certain amount of voltage achieves a certain clock cycle, then there's going to be resistance. But if you're over volting your cpu, it doesn't matter if you're running 10mhz or 200mhz, the voltage is what's causing heat. Too much voltage causes heat, and too much resistance causes heat. Finding that sweet spot is the key.

that's true if the ARM processors work this way, im not sure if their voltage scales with clock speed but im sure someone out there knows

[toolz]

Ok I took it down to 61 and it still heated enough to stop charging. Don't know if im gonna try 19 right now 61 was really slow, so slow it took pdanet like 5 times as long to connect