trent

Combat!

1) Poorly documented but this will work in "advanced mode" - leave the OS and file fields blank and start the emulator. In that mode you can configure via the native menu system. Setting the OS and file fields on the home screen will override this (those are there to quickly load games), but if you clear them it will go back to using the regular atari800 config file. 2) Known issue that I just haven't gotten around to looking into. Will add it to the todo list. 3) Not run well in what sense? Without specifics it is hard to know if this is an Atari800 issue or something with the Android port. Happy to respond to answer questions here but I do also maintain a googlecode site for this project (droid800.googlecode.com). Also the source is maintained here: http://code.google.com/p/droid2600/source/browse/ if you are so inclined.

My kit: Samsung i5700 (Android 2.2) CyanogenMod-6.1.1-Spica-alpha8.3 (rooted) locale: ukrainian (tried to change locale to english but same problem) I can slide down and see point menu "Show Speed", but when try slide more down i receive "Force Close" Same problem with 7.2 This is what makes Android development so much fun :-) I cannot replicate the issue with my devices (Moto Droid / Google dev phone 1) or in emulation. I suspect I know what it is since it started after I added dynamic summaries in the preferences dialog, I'll post a build with that removed later today. Hopefully this fixes it: http://code.google.com/p/droid800/downloads/detail?name=Droid800-7.5.apk

iPhone Explorer - http://www.macroplant.com/iphoneexplorer/ will let you add files to an app's internal Documents directory (side loading with no jailbreaking). So, the sample games are for demo purposes. My emulator would check the Documents directory to see if any ROMS were added and load them. This end arounds Apple's restriction since the app never downloads external code. You add the ROMs by hand. Like I said, I'm a really good iPhone programmer but a poor 2600 programmer. I'd love to see someone get a good 2600 emulator on IOS, why not find a good homebrew developer to partner up with and split the profits? Keep in mind a good homebrew took much longer to craft than your IOS port of Stella, so don't expect to be the majority owner

My kit: Samsung i5700 (Android 2.2) CyanogenMod-6.1.1-Spica-alpha8.3 (rooted) locale: ukrainian (tried to change locale to english but same problem) I can slide down and see point menu "Show Speed", but when try slide more down i receive "Force Close" Same problem with 7.2 This is what makes Android development so much fun :-) I cannot replicate the issue with my devices (Moto Droid / Google dev phone 1) or in emulation. I suspect I know what it is since it started after I added dynamic summaries in the preferences dialog, I'll post a build with that removed later today.

Tried, but without success. I'll have some time tonight to look into it. This is with Droid800 v7? Anything else I should know about your kit? Rooted? Locale? Your phone doesn't seem to like a blank "summary" attribute in a list item. Try this: http://code.google.com/p/droid800/downloads/detail?name=Droid800-7.2.apk

Tried, but without success. I'll have some time tonight to look into it. This is with Droid800 v7? Anything else I should know about your kit? Rooted? Locale?

Well if it's from the OpenPandora guys I would give them 2.5 years lead time to produce it :-) Kidding aside - I will be adding support for bluetooth controllers in the near future and if this becomes reality I'd support it.

I assume you've upgraded from an older version. Try resetting preferences to their default values (press menu from the home screen).

No not really, I keep a small list of games I use for testing here: http://code.google.com/p/droid800/wiki/TestFiles The quarter circles in the top left and right are buttons for opening the on screen keyboard and control buttons. The trigger is activated whenever you press the half of the screen that doesn't contain the dpad graphic. See the manual: The manual is here: http://code.google.com/p/droid800/wiki/Manual The bits on top and bottom are part of the Emulator screen, which is a bit larger than the typical viewable area on the A8.

My personal favorite

Oh no - did you get caught up in that $hit-storm of a thread? It took my several weeks but I did get the stubborn fool to admit paddles are good for Breakout Nice work on the emulators BTW. Oh man I thought I deleted that sentence before I posted - guess not :-)

I would consider calling a person's integrity into question on a public forum worse than anything this guy has allegedly done. I assume what the OP has quoted here is either neutral or paints the guy in the worst possible light - either way there is no smoking gun. He's an elderly guy who buys up systems, repackages and sells them. Re-read the original post. The guy's tone and apparent bewilderment toward the OPer is entirely appropriate. If the OP wants to encourage people to participate in trying to offset this guy's influence on pricing it can be done without demonizing him. Just an opinion of a guy with no skin in the game.

I am the guy who ported Droid800 and Droid2600 to Android. I have to agree, to a certain extent, that the experience isn't all that great. There's just not a lot you can do to make a touchscreen feel like the real deal - although I've recently tweaked paddle emulation on Droid2600 emulation so that movement follows your finger on the screen. Makes Kaboom pretty fun in IMO :-). If you try it out just remember to switch to "paddle" mode in the control panel. Anyone mention paddles to atariski btw? On the other hand - I did these ports because I thought having an Atari in my pocket would be a fun novelty and (at the time) no one had done it yet.

Skiing, Laser Blast, Kaboom.

Even better! I'll PM you the Duck Attack! ROM pack once I'm done adding to it (I keep thinking of new things to add, like a game world map.) The AA store would be the perfect place for this sort of thing. --Will I'd like to see AA sponsor homebrew games in the Android market (or any other mobile marketplace that makes sense). Sold in packs or alone - whichever. Homebrewers could do this individually but I'd be more keen to lay down some market bucks on something published by a name I know. Games don't need to be packaged with an emulator - just pack them with a light AA branded front end that invokes your emulator of choice.

I've released a version with a virtual keyboard and some other enhancements. I'll probably make a couple tweaks to the keyboard before the next release but right now I'm distracted with improving sound support...

I would be happy to try and fix your problem in exchange for using your Galaxy S as a test mule :-) For starters I'll need to get some log output: 1) There is a free application in the market called aLogcat, grab it. 2) Start Droid800 with sound enabled and let it fail as you described in a previous post. 3) Fire up aLocat, and touch menu->send 4) Send the log to diggerbonk at gmail dot com If there's not enough info in that log file to see what is going on I'll post a debug build that you can run in a similar way. Trent.

http://droid2600.googlecode.com/files/Droid800-r1-1.apk Not sure how well it will run on that phone though - mind providing feedback after you've tried it?

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.

http://code.google.com/p/droid2600/downloads/list. There aren't many changes to the Stella code other than to initialize SDL and make things compile correctly (Android NDK doesn't support C++ exceptions, for example).

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.