Yes, yes, a thousand times yes! I was actually thinking about this the other day and thought that it would be really cool and useful. My only question, though, is how will one acquire ROMs?

Ahh, okay. Yeah, I was thinking that the option for creating a ROM from open-source software would be neat on the phone.

Sad, no iOS version.

J/k this is awesome if this works out well. Good luck because I remember some people here requested an emu for their phone before. It can be handy when your calc is taken away or something and to test stuff at school without screwing your calc up before a test.

This is pretty cool! It'll be nice to see wabbitemu running on android.

I was planning to try a port of nspire_emu to Android by the way.

Fixed the major core bug so now all models boot. Source is up at: http://buckeyedude.zapto.org/Revsoft/Wabbitemu/Wabbitemu.tar.gz
APK is up http://buckeyedude.zapto.org/Revsoft/Wabbitemu/Wabbitemu.apk. To use it you must have your rom saved at /mnt/sdcard/ti84pse.rom. It can really be any rom, it just has to be named as such.

Juju: What needs to be done now is a couple things. First we need a way to select file. I'm sure there are file dialogs libs out there, but I havent looked yet. Probably easiest to hook one of those up and let the user select ROM or files to load. Second is optimization. The core for the 83p is pretty good on my Inspire 4G but the 84pse is still slow. I've also had to bump down the frame rate. My drawing code is current terrible. I'm guessing the core is still pretty slow, but I'm betting the drawing code is eating up my time. Profiling is a must. Third is Setup Wizard. Obviously this is huge for the dumbass user who is downloading it with no clue what a ROM is. If you can write the GUI, I can write the backend. Another minor thing is keypresses. Currently I don't handle multiple keypresses, which means fast keypresses or trying to press two keys at once fails. On the subject of keypresses, keys should be highlighted with a rectangle so its clear what the user just pressed. Not a priority but something to think about.

A long list I know. Once those things are in place, the emulator should be very usable. There's still a bug in the core dealing with FP numbers. I'm working on tracking it down. I have a good idea what it is thanks to js795. After a file selector is up we can start testing external files. I figure throwing a couple calc84, thepenguin77, and jim e programs at it will find any remaining core issues.

I can't access the apk, seems you haven't set up your permissions correctly?