Solution To Overclock In Firmware 1.4.0

[Waninkoko]

People who has 1.4.0 in his GP2X will know that you cannot overclock your GP2X because when you return to the menu the clock frequency changes.

I have developed a small application that resolves this problem.

You only have to uncompress the application anywhere and modify the script "OCit.gpe".

Script example:

#/bin/bash

./OCit "/path/to/app.gpe" MHZ

Download: Link

Greetings.

 

[TelcoLou]

Cool! I'm learning about these script things ... very neat, they are

Thanks

 

[Mr Doctor]

When I can be bothered I'm going to stick all the shortcuts on nand so I dont have to see the messy SD when loading things up

 

[DARKGATE]

But this firmware resolve the problems of batteries?
Is the most important problem, =| if i don't see better for batteries i use always my old 1.0.1 ^_^.
Ah the videos work very well, also to 160 mhz ^_^ without problems.

 

[sand_man]

When I can be bothered I'm going to stick all the shortcuts on nand so I dont have to see the messy SD when loading things up

​

You would risk the life of your NAND? I'll keep mine as it is because I'm paranoid

btw: Hasn't battery life increased since FW 1.0.1?

 

[PSyMastR]

When I can be bothered I'm going to stick all the shortcuts on nand so I dont have to see the messy SD when loading things up

​

You would risk the life of your NAND? I'll keep mine as it is because I'm paranoid

btw: Hasn't battery life increased since FW 1.0.1?

​

Ya, like tenfold. 1.0.1 gave me around 1.5 hours 1.4 gives me about 4-5 hours.

 

[daclassicgamingmaster]

kewl, im gonna give this a try now. Thanks man!

 

[Hochler]

When was the 1.4.0 firmware released!?

 

[PSyMastR]

Its not. Its a beta.
Edit: See my sig.

 

[Greenchili]

1.4.0 WAS NOT RELEASED YET, ITS A BETA, AND HAS ITS PROBLEMS. DONT WORRY ABOUT IT, AND STOP ASKING FOR IT.

Maybe you should also add "and stop bragging if you have it."

:rolleyes:

 

[Hochler]

Its not. Its a beta.
Edit: See my sig.

​

Ah, cool. Thanks.

 

[thelamer]

1.4.0 WAS NOT RELEASED YET, ITS A BETA, AND HAS ITS PROBLEMS. DONT WORRY ABOUT IT, AND STOP ASKING FOR IT.

Maybe you should also add "and stop bragging if you have it."

:rolleyes:

​

LOL :lol:

 

[reallynotnick]

When I can be bothered I'm going to stick all the shortcuts on nand so I dont have to see the messy SD when loading things up

​

You would risk the life of your NAND? I'll keep mine as it is because I'm paranoid

btw: Hasn't battery life increased since FW 1.0.1?

​

Ya, like tenfold. 1.0.1 gave me around 1.5 hours 1.4 gives me about 4-5 hours.

​

Wow really and is that when playing games? Like Genesis and does it run at the standard 200mhz when doing it too?

If so I can't wait for the office 1.4 to come out or 1.5 whatever I want to get rid of 1.2

 

[PSyMastR]

Im testing a modified version of this script (I just changed the paths) for squidgeSNES. Lets see if this works (Im OCing to 279, which worked before the 1.4 update)

EDIT: Black screen of death.

Here is my code:

#/bin/bash

/mnt/sd/OCit "/mnt/sd/Games/Emulators/SNES/SquidgeSNES.gpe" 279
sync
cd /usr/gp2x
exec /usr/gp2x/gp2xmenu

Where OCit is in the root, and SquidgeSnes.gpe is in the respecive folder listed. Hm...

 

[TelcoLou]

I'm having issues with 1.4 once again :lol:

I went script-crazy (Thanks to everyone who helped me so much lastnight, especially god_at_hell), and made one for each executeable.

It seems like the FW doesn't like when I go back and forth between different clock speeds (i.e. I have DrMDx at 200mhz and MAME at 266) I got some very ugly skipping around the games menu and after I selected Atari800, the screen was flickering between the game screen (archon) and the A800 menu (!)

So I downgraded (once again) to 1.2.0 and have been testing for ~20 minutes now with no ill effects. And yes, I was using very fresh batteries. I don't have a clue about Waninkoko's app or how to use it ... but I think I'll leave 1.4 alone for awhile :lol:

 

[Shikaku]

I'm having issues with 1.4 once again :lol:

I went script-crazy (Thanks to everyone who helped me so much lastnight, especially god_at_hell), and made one for each executeable.

It seems like the FW doesn't like when I go back and forth between different clock speeds (i.e. I have DrMDx at 200mhz and MAME at 266) I got some very ugly skipping around the games menu and after I selected Atari800, the screen was flickering between the game screen (archon) and the A800 menu (!)

So I downgraded (once again) to 1.2.0 and have been testing for ~20 minutes now with no ill effects. And yes, I was using very fresh batteries. I don't have a clue about Waninkoko's app or how to use it ... but I think I'll leave 1.4 alone for awhile :lol:

​

Maybe it's just a bug with the GP2X: the GP2X changed clock speed a lot, both occurences and space in speed, which would not happen in any other setting? Just curious if that's the case...

 

[TelcoLou]

Maybe it's just a bug with the GP2X: the GP2X changed clock speed a lot, both occurences and space in speed, which would not happen in any other setting? Just curious if that's the case...

Ummm ... :blink: what??!

 

[kounch]

You can also use Selector to do this task, using an intermediate script. Here you have an example:

1. Copy cpu_speed to the root of a SD Card.
2. Copy the files in the zip file of this post (selector along with cpu.sh, fondo.png, launch_config, Launch.gpe and Launch.png) to any place in the same SD card.
3. Select Launch.gpe in the GP2X Game menu.
4. Use A,Y buttons to choose a CPU speed (66,100,150,200 or 250).
5. Use the stick and buttons L,R to select a .gpe or .gpu file in the SD.
6. Launch the file with the selected speed using B button or X button.

 

[jmetal88]

You can also use Selector to do this task, using an intermediate script. Here you have an example:

1. Use A,Y buttons to choose a CPU speed (66,100,150,200 or 250).
   

​

But I like playing GP2PSX @ 295 mhz.... at least until it crashes 10 minutes later.

 

[kounch]

You can also use Selector to do this task, using an intermediate script. Here you have an example:

1. Use A,Y buttons to choose a CPU speed (66,100,150,200 or 250).
   
   

​

But I like playing GP2PSX @ 295 mhz.... at least until it crashes 10 minutes later.

​

Then edit the file launch_config and add another line like this

cmdLine=./cpu.sh 295

If you want more speed options, keep adding lines in the same format