Might i suggest renaming the plugins section just to settings so really non developer users dont get confused?
I suppose that makes sense in the current basic setup. Eventually, though, the GUI is going to be focused around the skins and plug-ins, so I reserve the right to change it back in the future when it makes more sense

is some of the futures added, if it post a test 
I'll post a test soon. Just trying to bring all the pieces together (keeping track of the views is a bit more complicated than it seems at first glance). There are a few minor bugs that I mentioned as well that I want to address first (so the tests can focus on compatibility issues rather than fixing bugs I already know about). They called me in to work this afternoon, so I probably won't have this finished today like I planned.
why eould paul build in support for armv5-7 if he didn't want people with slower phones to use it?
The main reason for this is because "necessity is the mother of invention", as they say. I figure folks with slower devices will be the driving force behind optimizations and getting the emulator to run as efficiently as possible. There's really no reason 1 GHz or higher is necessary to emulate a 93.75 MHz chip. The general rule-of-thumb minimum requirement for emulating a CPU is at least 5X speed on the host hardware, which would translate to 470 MHz. Clearly there is plenty of room for improvement.
i will
any preference of game or just all of em?
Any that you had strange graphics problems (this is more out of curiosity than anything) I expect gles2rice to be a lot better than gles2n64 with regards to accuracy (I'll likely make it the default video plug-in when the slow-speed problem has been improved). Like scorpio16v said, though, it will be painfully time consuming on your device, so no worries if you don't have the time for this (I'll get around to doing more comparison tests when I move to the beta testing phase).