There's no need for standards. I won't follow some of the proposed GP2X standards that came forth because I don't think they all make sense. For instance, on the GP2X standards website, they list START as a hotkey for exiting the program! WTF???
I will admit my first port Koules2X has a hotkey for exiting and it never asks if they want to quit. FOR SHAME! I've never released a new version but I'd never allow that on my newer ports. It's not rocket science, designing a user-friendly program. It's just a question of if the programmer cares, or not. A logo isn't going to change that. It's their prerogative (the coder) if they don't want to bother with volume controls. I think they're sillly to release it with no volume controls, but I also think it's silly to release a program that will kick you out just for pressing START! Who am I to argue with a programmer that released something for free? I have a problem though, because I can't use the logo either, even though I care a LOT about user interface and so I choose to forgo the START button exiting the program and a few of the other "standards"
A lot of these problems the standards attempt to "solve" came from one central source: overly-complicated interfaces. The way to solve that is with a context menu and a two button interface: One button to bring up the context menu, the other button to select items on said menu. That's it. Nothing more needed (save for page up/page down in long lists, and a good programmer familiar with GP2X programs will already note that L/R triggers and LEFT/RIGHT joystick are the only things that make sense there).