November 13th, 2008, 10:54 AM
Thread Author (OP)
Join Date: Nov 2008
Device(s): S4, iPad Air, Note 2014 10.1, Dell V11 5130, Nvidia Shield. Yes- too many devices.
Thanked 1,381 Times in 970 Posts
Emulators may be a while
There has been discussion on other boards, but emulators and game ports may take a while and depend on if Android is opened for some native code access.
The author of my favorite WM emulator, Smartgear (great multi system emu for NES, GBC and Turbografx and Sega) has told me that the "Java" layer is required, so not only do you have to emulate the game systems, you have to also interpret the "Java" layer and this results in slow emulation even on the G1.
He wants to release a port of his emu to Android, but says it will not happen until Android has native code access.
Coreplayer is another program that is having issues due to Java on Android. They want to port the their media app but state that there is currently too much cpu overhead because any codec not native to the OS ALSO has to go through the "Java" layer.
If all things stay constant, this does not mean there will not be emulators, but it does likely mean that even a Gamboy emu will be slow on the G1 or any other Android device.
I put quotes around Java, because the container in the OS is more a hybrid of Java, but the cpu overhead is still the same.
We will probably not see Doom, Quake, MAME or any full speed emulator with sound until Google opens the OS up to some native code access.
Google demoed Quake, but it apparently did not go through the Java layer restriction. I would like to know if they used the SDK or used code native to the cpu.
I tend to believe others that the OS will be opened up more by Google, but how long will this take?
Last edited by rushmore; November 13th, 2008 at 10:59 AM.