Page 1 of 1

Over-Clocking and/or Under-Clocking the Scroll

PostPosted: April 13th, 2011, 3:30 pm
by Charlie
Has anyone tried to Over-Clock and/or Under-Clock their Scroll? As a slower CPU speed would increase battery life and a faster CPU would make the scroll a lot faster, in theory.

I have found this app 'Setcpu' which you can get from the market or from the link below (if you are a member of the xda forum)

http://forum.xda-developers.com/showthread.php?t=505419

I will give it a try out on the scroll later tonight :)

Re: Over-Clocking and/or Under-Clocking the Scroll

PostPosted: April 13th, 2011, 8:19 pm
by Kamikaze-X
i didn't have great success with SetCPU. if anything it slowed my scroll down too much, and the upper limit was much lower than the Scroll's actual top clock speed of 720mhz. i really did see a massive slow down, and the Scroll isnt the quiuckest as it is.

you might get better results, i only played round with it for an hour or so.

Re: Over-Clocking and/or Under-Clocking the Scroll

PostPosted: April 13th, 2011, 8:23 pm
by Charlie
I have used the setting from the main menu 'Samsung [ARM]'

And I can set the CPU max to 800 - the chip is a 720 speed one, but SO have over-clocked the chip to 800 already. I can not get it faster than 800 - but I can slow it down and save battery when the screen is off, which is always good.

So this app is more for under-clocking at the moment - unless we can include stuff in the custom 2.2 ROM to allow over-clocking.

Re: Over-Clocking and/or Under-Clocking the Scroll

PostPosted: April 13th, 2011, 11:13 pm
by mojo
from what i've learnt with my Desire HD, the cpu controls are handled in the kernel i think ???

my Desire HD runs the 1ghz snapdragon cpu, thanks to some modified kernels ive managed to get it upto 2ghz!!! (although this is purely for showing off, the chipset burns out after a minute or so) stable overclock seems to be 1.8ghz...although it destroys the battery in half the time it used too!

Arm processors never really had much in the way of overclocking headroom, you might get another 100mhz or so, but given the scroll's dismal battery life i can only see an overclock being even more detrimental...

more focus should be on the software, trimming down the fat and having a nice resource sipping kernel that'll compliment the scrolls basic hardware.

i do still use my scroll, but only as an mp3 player plugged into my car stereo lol! when/if 2.2/2.3 etc is released as stable then i'll consider updating it, but for now im content with it :)