42 replies to this topic

[Pleng]

To add some CPU speed presets to your menu, download this PND to the pandora/menu folder on one of your SD cards.

Presets are 500, 600, 700, 750, 800, 870



unpack the attached archive to the menu folder of one of your SD cards.This will add some shortcuts to your 'system' menu, however they won't actually function yet. To give these scripts the authority to access the CPU speed, you need to open up a terminal and type the following:

sudo chmod a+w /proc/pandora/cpu_mhz_max

Now you can test the scripts. Run one of them from the menu, and then launch the normal CPU Speed utility. It should now show the CPU speed you selected from the menu.

Edited by Pleng, 23 June 2010 - 09:44 AM.

[SomeGuy99]

Oh nice, thanks. I did this one myself a few weeks back.

You can do the same for brightness settings too. These days I just use the CPU scaler mapped to ctrl-alt-c.

[skeezix]

Why not make a pnd installer for these little hacks?

Ie: g sudo it to popup he sudo prompt as needed whilecopyng in bits or chmodding; the pnd would jut be a runs riot with a few files to copy so not hard to make?

I like the idea .. Probably can't build them into the firmware for legal sake, but common desire I bet to jump to 600, 700, 800 etc.

Hmm, we really just need an easy .ovr generator so people can flag pnds to run at desired speeds, perhaps? Whose up to it .. Pygtk awaits

Jeffphone

[Pleng]

Why not make a pnd installer for these little hacks?

because I don't know how..?

Ie: g sudo it to popup he sudo prompt as needed whilecopyng in bits or chmodding; the pnd would jut be a runs riot with a few files to copy so not hard to make?

If somebody else wants to do that the can by all means go ahead. It's just something I wanted to do for myself but thought the least I could do was share it. Packing it up as a PND with an installer breaks the 'least I can do' threshold so I'm quite happy to NOT do it

edit: besides which it gets a little more complicated than that... either your gonna have a PND which includes an installer script AND the CPU scripts, with no way to remove the installer from the menu once it's been done, or you're going to have to include the installer in each individual script in an if statement, using appdata to somehow store if the chmod has been successfully completed

I like the idea .. Probably can't build them into the firmware for legal sake, but common desire I bet to jump to 600, 700, 800 etc.

Hmm to be honest I tend to switch my unit to 750 at startup and be done with it. Doesn't seem to have any negative impact on my battery life.

Edited by Pleng, 21 June 2010 - 08:40 AM.

[Pleng]

hmm /proc/pandora/cpu_mhz_max appears to loose it's new privileges after a reset. I guess some script running as root is setting it on boot? Does anybody know how to fix this?

[skeezix]

/process is populated at runtime I imagine so your changes gt lost. Have to set the perms different internally or during a bootscript

but fair enough on your 'least' principle

jeffphone

[notaz]

You should better just run op_cpuspeed.sh from your scripts:

sudo /usr/pandora/scripts/op_cpuspeed.sh 500

this way you won't need to chmod or enter the password.

[Alerino]

any good effect on battery life? how low can it goes?

[SomeGuy99]

You should better just run op_cpuspeed.sh from your scripts:

sudo /usr/pandora/scripts/op_cpuspeed.sh 500

this way you won't need to chmod or enter the password.

What I wanted to know. Thank you

Should have read the script more carefully.

[Pleng]

You should better just run op_cpuspeed.sh from your scripts:

 sudo /usr/pandora/scripts/op_cpuspeed.sh 500

this way you won't need to chmod or enter the password.

Thanks, have updated and made a PND (see first post)

Noted a tiiiiny error with op_cpuspeed.sh script. If you set your CPU speed to 600 it gives you a warning that the speed is greater than 600.

[SomeGuy99]

You should better just run op_cpuspeed.sh from your scripts:

 sudo /usr/pandora/scripts/op_cpuspeed.sh 500

this way you won't need to chmod or enter the password.

Thanks, have updated and made a PND (see first post)

Noted a tiiiiny error with op_cpuspeed.sh script. If you set your CPU speed to 600 it gives you a warning that the speed is greater than 600.

You can edit out the Zenity popup from the script.

[Pleng]

I know I can. I was just giving feedback. It should really be fixed in one of the hotfixes. It's a nice easy fix too

[WizardStan]

I know I can. I was just giving feedback. It should really be fixed in one of the hotfixes. It's a nice easy fix too

did you file a bug report?

[jonlad1]

Works great! Good job!

[Pleng]

I know I can. I was just giving feedback. It should really be fixed in one of the hotfixes. It's a nice easy fix too

did you file a bug report?

not yet. will get around to it...