Mike Slatari

I've experienced the same problems with my Galaxy S. When I turn sound off, it works fine.

Absolutely! I've made no significant modifications to the Atari800 sources so merging in changes should be pretty painless. Shoot me an email and we can figure out the best way to proceed. Trent. Great! I'd like to (publicly) let you know the differences between our two codebases. I'll email you the more technical stuff. Mine has these problems due to being incomplete: Only works with phones with a physical keyboard. No touch or accelerometer support Key mappings can't be changed and there's no documentation on built-in mappings. Takes 5 seconds to startup (due to pokey init) Back button doesn't close app. Sometimes crashes on first start, but fine after that. Features it has over current Droid800 Supports the built-in atari800 menus It is much faster (100% on G1 with refresh-rate=2) and probably uses less battery The big code difference is I didn't use SDL. I tried to use the same SDL library you did, but I found it too unstable. I didn't modify any atari800 sources (except log.h). Features I wanted to eventually add: Intents to auto-run emulator when loading Atari file types .ATR, .XEX, .ROM, etc. Intent for .zip files (in case one doesn't have a zip browser) Include a small collection of good free games Include links to known websites that supply ROMs Support emuos by default, so an OS ROM isn't a requirement Native Android support of the atari800's menus (C callbacks to Java)

Hi. I am the "author" of Droid800 and Droid2600. They are straight ports of the Atari800/Stella emulators wrapped with some Android specific UI code to work around input limitations inherent in the platform. I'm considering a few alternatives for keyboard support but haven't decided on anything yet. The Android inputs (on screen dpad, accelerometer joystick, etc) are currently all implemented in Java which are layered over the SDL surface. Both Stella and Atari800 have mature built-in menu systems that could probably be made touch-screen aware with a bit of work - my first release of Droid2600 used that approach but the non-native controls were not well received by end users. Working on getting the source cleaned up and uploaded to http://code.google.com/p/droid2600 if anyone is interested in looking under the hood. Good job, Diggerbonk. I also have written a working port of atari800. You beat me to it. Perhaps we can work together, if you're willing to take contributions. I put a lot of effort into performance which yours might benefit from on older devices. (I used a G1 for testing) I also have several ideas I was working on beyond emulation. I'd like to email you my sources after I do some cleanup. What do you think about collaborating?