New Firmware Due @ End Of Month (ish)

[Crazy Goat]

The original company/dev team will always develop a better firmware

BWAHAHAHHAHAHAHAHAHHAHAHAHAHAHAHAHHAHAHAHAHAHAHAHAHA *gasp* HAHAHAHAHAHAHHAAHHAHAAHHAHAHAHAHAHAHAHAHAHAHHAHAHAHAA

*passses out*

​

Because we all know that people in the community know more about the device than the people that created it.


I am not talking about modifying firmware - I am taking writing it from scratch.



BWHAHAHAHAHAHAHAAHHAHAHAHAAHHAHAHHAHA.


But, on rare occasion - the company hires those who cannot do what is asked of them, and create a bad product. But, I believe that it is more than likely true to say that GPH firmware releases could be better than the modifications. Mainly, because of stability (bugs not included), because those who modify firmware do not know all the adverse reactions of their change, which could brick devices.


This is much like saying that a firmware installer written by GPH would be better than a community based one. Those who work at GPH are representing a company, they cannot sink into the shadows if their product fails, like others can.

 

[FluffyPanda]

Well, we have a few people here who have studied the device in such depth that I'm sure they know at least as much as Dignsys did.

Bear in mind that you can get the OS running on the device without understanding everything about it thanks to the huge amount of OS code out there. A company as small as GPH probably didn't have the resources to study every component they used fully, which explains the stick (assorted community alternatives), the scan lines (community fix was rolled back into the official firmware - badly), the fact that the batter light still doesn't work too well (the Squidge monitor code is much better) and so on.

The community certainly can do better than the device designer.

 

[5465756e]

I hope they fix the autobrick bug.

​

art103 has already fixed that. Weeks ago!

​

How could I have missed that :blink: ? That's only for cramfs right?

 

[nickspoon]

Nope. All firmwares.

 

[deadlychicken22]

But, on rare occasion - the company hires those who cannot do what is asked of them, and create a bad product. But, I believe that it is more than likely true to say that GPH firmware releases could be better than the modifications. Mainly, because of stability (bugs not included), because those who modify firmware do not know all the adverse reactions of their change, which could brick devices.

​

Well, I haven't noticed any "adverse reactions" with theoddbots cramfs firmware, except that it boots in about 3 seconds (Art103's u-boot takes about 6, creating a total time of about 9 seconds). It also has some handy things built-in that I don't think the official firmware has. It even prevents crashes (sends you back to the main menu).

This is much like saying that a firmware installer written by GPH would be better than a community based one. Those who work at GPH are representing a company, they cannot sink into the shadows if their product fails, like others can.

​

Actually, they probably could, we don't have a very direct connection to them. And "firmware installer"? GPH's "firmware installer" is automatically started by their u-boot and is the reason for all of the bricked gp2x's. Art103's u-boot doesn't update automatically, but instead gives you the following options:
-Boot from NAND
-Boot from MMC/SD
-Serial Prompt
-Update Firmware

You can see these options by holding start when you turn your gp2x on (otherwise it will automatically boot from the NAND).
This is a much safer method than GPH's, and will eventually become the standard. The part about it that isn't safe is flashing it (using GPH's u-boot method) but once you've done that successfully you won't have to worry about automatic bricking.

You can find more info HERE

 

[ste_167]

Today, or tomorrow .. . . . . . .............. . . . .