If you install and run the SetCPU app as listed in the wiki, the CPU is underclocked to a max clock of 600mhz from the default 660mhz. You will see the CPU scale between 36 and 600mhz on the screen. SetCPU Long benchmark test score: 1806 ms (lower is better)
However after much fiddling and by accident, I've discovered that if you edit setcpu.txt with the max clock of 660000 (vs. 600000 as shown in the wiki file) then set the system to sleep and wake it up, you'll notice that the CPU now scales between 36mhz and 660mhz despite the green text saying "600 max 36 min" . SetCPU Long benchmark test score: 1593 ms (lower is better)
This has been the only way I've gotten the unit to use SetCPU's cpu scaling on demand feature while getting full speed from the cpu when i need it. [Boot up the GT, put it to sleep then wake it up]
I assume running without SetCPU lets the unit run at 660mhz all the time.
For reference: I have a GT with a unique MAC address and it came preloaded with the Aug. 4 update, now running Lincs update with Patch V3
However after much fiddling and by accident, I've discovered that if you edit setcpu.txt with the max clock of 660000 (vs. 600000 as shown in the wiki file) then set the system to sleep and wake it up, you'll notice that the CPU now scales between 36mhz and 660mhz despite the green text saying "600 max 36 min" . SetCPU Long benchmark test score: 1593 ms (lower is better)
This has been the only way I've gotten the unit to use SetCPU's cpu scaling on demand feature while getting full speed from the cpu when i need it. [Boot up the GT, put it to sleep then wake it up]
I assume running without SetCPU lets the unit run at 660mhz all the time.
For reference: I have a GT with a unique MAC address and it came preloaded with the Aug. 4 update, now running Lincs update with Patch V3
Last edited: