I just pushed out an update for psx4droid, now at 3.0.5.

The save state bug is now fixed. It affected people on stock Android ROMs.

Through various bug fixes this release should allow more hardware on various Android ROMs to run psx4droid. I’m interested if this build fixes the following hardware to allow games to be played:

• Google Nexus S
• SE Xperia PLAY
• LG Optimus 2x
• Xoom / Honeycomb
• Dell Streak

You can download the latest psx4droid.apk install file here:

http://www.zodttd.com/downloads/psx4droid.apk

I’d also like to thank those few who have used the Donate page to send me donations. It is very much appreciated and helps me know my work on this is also appreciated on this project.

Thanks,

ZodTTD

Updated April 11th 9:19pm EST:

psx4droid is now at version 3.0.4. The changelog is below.

I encourage all users of psx4droid to upgrade to 3.0.4, especially if you’re using 3.0.1 or earlier, as it will help me pin down bugs and make fixing them easier.

Download the latest version as always right here:

http://zodttd.com/downloads/psx4droid.apk

Here’s the changelog:

3.0.4 since 3.0.3:

- Fixed the hardware key mappings and they are now fully functional. Settings stick as well.
- Fixed a bug causing various phones to crash due to a multitouch related issue. One phone affected is the Xperia Play. This fix may give multitouch issues in virtual keypad mode, so if this is the case, let me know.
- Removed a legacy call to set the surface type of a view. Determining if this affects performance any, though it shouldn’t.

3.0.3 since 3.0.2:

- Fixed Key Mapping settings.
- Fixed a bug causing MotionEvent crashes due to multitouch implementation in some hardware.
- Tweaked the silent crash report logging. Should help me debug better.

3.0.2 since 3.0.1:

- Fixed a bug causing settings not to save and crashes in the settings panel. Virtual Keypad settings should work now.
- Fixed a bug causing crashes when a screenshot is made twice in a row or more.
- Fixed a bug in a temporary fashion to stop crashes when virtual keyboard control bitmap sizes could not be determined with getWidth() in some firmwares.
- Removed localization until a proper localized text can be made.
- Reset the quick load on start feature to default to off.
- Added debugging tools to help track crashes and supply crash reports.

Thanks,

ZodTTD

Just a quick note that I have updated psx4droid to 3.0.1. Now you can always find the latest version of psx4droid to download at this link:

http://www.zodttd.com/downloads/psx4droid.apk

What’s new?

I fixed a bunch of bugs in the settings screen causing force closes as well as settings not saving. I also added the option to show the current framerate.

However, I’m still looking into the incompatibility of psx4droid on the LG Optimus / Honeycomb / Xoom devices. Since I do not have any of these devices, it will take a good amount of time debugging.

Of note, I found out the source code psx4droid is based on, uses  source code by smf to emulate the GTE. I am crediting him here in addition to the readme.

Thanks,

ZodTTD

In the meantime, I’m exploring 3rd party markets and I have decided to make psx4droid free, based it on the open source software PCSX-ReARMed by Notaz, and made it compliant.

You can download the psx4droid 3.0.0 APK installer package right here:

http://www.zodttd.com/downloads/psx4droid_v3.0.0.apk

Developers interested in seeing the source that drives psx4droid, libpsx, can be found here:

http://github.com/zodttd/libpsx

What’s new in psx4droid 3.0.0? Well it’s based on a different emulator, PCSX-ReARMed. It has a better dynarec (cpu emulation technique) and lands up being much faster in general. It’s using a software GPU for graphics rendering, though I have an OpenGL ES 1.1 GPU made. OpenGL ES 1.1 is hit or miss for this type of rendering on Android devices. Many of these high end devices have slow Adreno 100 GPUs. So soft GPU is the way to go for now, especially with some improvements to come.

psx4droid 3.0.0 should have great compatibility, better performance, though it may be a lil rough around the edges when it comes to the settings panel. If you notice a force close in it, it’s bound to be fixed coming up.

Note that all save states previous to 3.0.0 are no longer compatible. If you have quick saves, be sure to turn OFF quick load before running games in 3.0.0. You should save over the quick saves or delete them before turning back on quick load.

Wish I could put this up on Android Market. This will just have to due for now.

Thanks,

ZodTTD