I understood from Alex that the crash when bringing up the console is a known issue.
That remapping is with the SDL Device setup screen?
Anyway, need Alex to really comment on this one.
@Meits: thanks for the zip from the sd-card. I've downloaded it to my PC and will analyze it Saturday to understand what is going wrong.
@teroper: First of all, thanks for the nice words about the android port. I'm happy to have made a dream come true together with the entire openMSX team who have laid all the ground work for running openMSX on handheld devices and who have been helping me a lot with the Android port.
I confirm that, like Manuel said, the console is currently broken in the Android version.
Furthermore, I will investigate the issues with the SELECT and STOP keys that you reported coming weekend. I'm also investigating the root cause for the console crash. I hope I can fix all the issues in the weekend and then make a new build.
@mighty.m: can you please let me know which link that you followed to download openMSX? The download link on the MSX Plaza normally points to an APK file.
Can you please also let me know which android device that you used to click the download link (brand, model and Android version). Maybe it mistakes the APK file for a ZIP file. They are technically the same format. The only difference between a ZIP and an APK file is in the extension. It might be that I need to configure the web-server to set the appropriate mime-type when serving APK files.
@Alex: Last night i kept trying little more things and suddenly i got an idea...
I opened settings.xml file in mnt/sdcard/openMSX/share folder and added line: <
setting id="kbd_mapping_mode">
KEY<
/setting>
. Then remapped keys once again, and it worked Console still leads to emulator crash, but now i can use SELECT, STOP and SHIFT keys normally. openMSX port for android has now officially become my favorite program in my phone.
And also, i like to thank whole openMSX team for their great job. Thanks to you, MSX lives forever
@teroper: thanks for reporting the finding on the kbd_mapping_mode. It has put me on the right track for the investigation. It turns out that the SDL Android port has different behaviour for the SDL KEY events.
For example, when I press F8 key on the PC, I get the scancode (for F8 key) but the unicode value is set to 0 because a function key does not have a unicode (it is not a character).
On Android, I also get the correct scancode but on top of it, I get a non-zero unicode value, as if a character was pressed. As such, openMSX then believes that a character was pressed and not a function key (when in character mode).
I'll further investigate the keyboard driver in the SDL Android port and work together with the SDL Android port developer on fixing it. Though, it may take a while. Keyboard driver and mapping is non-trivial code.
@mighty.m: I have updated my website to indicate the correct mime-type in the HTTP-headers when serving the APK file. Can you try if it solves the problem for you?
It works now, but this occured when trying to download the file from my desktop pc (IE6). Then I tried accessing it through my smartphone and this worked. Installed flawlesly and works fine :-)
Sony Xperia U - android v2.3.7
Thanks for this great app :-)
IE6 ???
Switch to Firefox and many problems will disappear !
Sorry, I obviously meant IE9 :-)