I noticed something obvious recently, you can run your GP2X on batteries for much much longer at 50 MHz than at 200 MHz. Which made me think, why do most developers think it's fine if their game runs at 200 MHz, as it could run just as fine with a lower CPU frequency? Well it's not because the GP2X is by default clocked at 200 MHz that everything must run at 200 MHz.
I'm sure NetHack could run just fine at 25 MHz (correct me if I'm wrong but apps can run as low as 25 Mhz on the GP2X, lower makes the screen have black frames, but maybe it's just with the app I tested, so I'd need confirmation) and if so it just could run for so much longer than at 200 MHz.
So here's what I'd like you developpers to do. Take every app you have released on the GP2X, even ports, and look for the lowest CPU frequency you can use for your app, and inside your code, make your app switch the GP2X to that low CPU frequency you deem decent, and release. And while you code please remember to always optimize stuff so that you can run it at an even lower CPU frequency, don't content yourself with a "it runs at 30 FPS at 200 MHz, why bother?" thought.
Because I find it aberrating to have simple ass homebrew SDL games run at 200 MHz and drain batteries much faster and they just don't need that, and that by giving the user the same experience while making batteries last longer, it gives the user a much nice overall GP2X experience, and it probably makes the user want to play your game more if he knows it'll drain batteries less than something else.
I'm sure NetHack could run just fine at 25 MHz (correct me if I'm wrong but apps can run as low as 25 Mhz on the GP2X, lower makes the screen have black frames, but maybe it's just with the app I tested, so I'd need confirmation) and if so it just could run for so much longer than at 200 MHz.
So here's what I'd like you developpers to do. Take every app you have released on the GP2X, even ports, and look for the lowest CPU frequency you can use for your app, and inside your code, make your app switch the GP2X to that low CPU frequency you deem decent, and release. And while you code please remember to always optimize stuff so that you can run it at an even lower CPU frequency, don't content yourself with a "it runs at 30 FPS at 200 MHz, why bother?" thought.
Because I find it aberrating to have simple ass homebrew SDL games run at 200 MHz and drain batteries much faster and they just don't need that, and that by giving the user the same experience while making batteries last longer, it gives the user a much nice overall GP2X experience, and it probably makes the user want to play your game more if he knows it'll drain batteries less than something else.