I created a repository with the source code of UAE4ARM on GitHub (https://github.com/PandTomB/uae4arm). There are all release and beta versions available and also contains new stuff for the RaspberryPi port. These changes will also become part of the Pyra port, when I get my device.
There is a new version of UAE4ARM in Repo.
The performance we lost by newer code from WinUAE was compensated by using GCC 7.2 with profiler. So the Pandora is still fast enough for this version.
Changes since last release (2016-09-24):
- Merged lot of changes from WinUAE 3.5.0
- Added panel...
Here is another beta of UAE4ARM. In this version, I merged lot of changes from WinUAE 3.5.0.
Thanks to GCC 7.2 and the profiler, we have same or better performance than latest version in Repo. So after some more testing, I will create a new release version for the Pandora.
To use controllers on Android, you have to ask the porter of uae4arm to Android to fix this. The core can handle any controller provided by the host specific code. I can´t do any changes on the Android specific code to fix your problem. Sorry.
Here is a new version with following changes:
- Fixed loading new config (now using same method like WinUAE)
- Display message instead of crash in some situations
- More cleanup of threads/pipes/mutex
In WinUAE, at each display line, several variables are checked and updated to get the first and last output of the line. With these values, center_image() in display.cpp does the centering and somewhere else is the automatic screen mode change.
Using the automatic size and center mode of WinUAE will slowdown emulation. This is the why it's not part of UAE4ARM.
I will merge the code of the raspberry-pi version and android version into this code. It's already on my list.