Home Page Forums Other Emulator Message Boards Modeler and M1 M1 Android

zedblade is working for me. zerowing is not because it looks like its looking for the wrong roms(genesis not arcade, my bad :), I'll fix that in the next update. can you post a logcat for zedblade?

I've finally gotten to set up my sdcard properly and try this out and I'm having a similar problem - no matter what game I pick, the app puts a play icon in the notify bar and then force quits. I've tried, among others, Marble Madness, Haunted Castle, Daytona, Journey, Tron, and a couple of Genesis games.

This is on an HTC EVO 4G running Gingerbread 2.3.3 (HTC/Sprint's official OTA update, no CM or rooting or anything).

I just pushed an update that should have rom loading acting a lot better. This fixes the above zerowing issue and adds basic error handling to rom loading including a toast to tell you why it failed instead of crashing horribly

Edit:
oh and I'm working on the options screen. at least then I can get it so it doesn't require stuff to live in /sdcard/m1 since this is an issue for some people.

hi again! sorry i didn't provide a logcat before; i updated to the current version on the market (i think it says 1.24).

anyways, new problem: the rom list doesn't want to load up. i have the m1.xml from early june and the lists from may. below is a logcat filtered to only show m1:



maybe there's something up w/GameListActivity?

No prob. 1.23 had the romlist issue. 1.24 should have that fixed. I know I'm running it and at least one other person that isn't having that problem anymore. I forgot I had the rompath hard coded so I fixed that but I didn't notice that m1 appends a ; to the end of it when it reads the ini so 1.23 had that issue because it wasn't finding the roms at all. I fixed that and pushed 1.24 this morning to fix it. Though it was mentioned to me that the romlist may not update properly if the service never dies(which it doesn't sometimes, I dunno why) You might want to try force quitting or going in to menu|settings|applications and kill it from there.

It should be ok as long as your ini points at your rom folder. If you dont have an ini it doesn't init at all anymore, keeps stuff from getting weird. FYI you can also filter for "I/M1Android" since I spew a few debugging messages.

This android shit is a pain If you're ever looking over the source, try not to laugh because its such a horrible hack

1.23 couldn't find any roms for me so I'll try 1.24. Thanks for keeping up on this

no worries; i myself SUCK at java :P

FYI, i was on 1.24 when i took the above logcat. right now i looked at my ini file and saw that i apparently changed the rompath from /sdcard/m1/roms to simply roms expecting it to be read as a relative path, but after changing it back m1 now takes forever to action, and STILL NO ROMS show up in the list.

and now as i type my moto droid running cyanogenmod7 just went into soft-reboot. fantastic.

is running on my moto droid OCed to 800mhz simply a non-starter?

in the meantime, deadbeef player on android is satisfying my zerowing craving via genesis vgm

I wonder how well a port to the Nokia N900 with a Ti OMAP 3430 @ 600MHz and running Nokia MAEMO Linux (with X and everything) would run...

N900 isn't a port, it's just Linux. Since those are the same-ish specs as a BeagleBoard, get one and let us know...

I was thinking about buying a Hero H2000 (froyo 2.2, 416 mhz) and I wonder if there are any chances of M1 getting DRC for the 68000? I know atm mame has no backend for ARM, but since even Windows 8 will support said architecture, I suppose it is being considered (albeit I know this might be filed under "when helll freezes over" :S ).