I had a quick look tonight at what’s involved in reviving the Android version and potentially PR’ing it into mainline at a later date. tl;dr it’s complicated and I can’t promise anything, but it’s still something I’d like to do.
I remember Wulfe and I were seeing a lot of Google Play crash reports and hardware issues relating to SDL2 on different Android OS versions, and it was a bit of a nightmare to try and fix them all since they only showed up on certain hardware/OS combos.
We made a bunch of modifications to the SDL2-2.0.5 source code to try and fix certain problems with that SDL version, but we’re still seeing a tonne of crashes in SDL code to this day with those changes.
I’ve had a dig through the SDL2 Mercurial history and it seems they’ve made quite a lot of fixes to the Android SDL2 implementation (and included java project template) in the last 12 months (they’re now at SDL2-2.0.8 stable), so it might be a good idea to try and update CDDA Android to SDL2-2.0.8 (including updating the java source code to match the changes they made) and see if things are more reliable then. While this sounds simple, my spidey senses tell me there will be a bunch of other pain-in-the-ass dependencies and complications, but it would definitely simplify things for merging back into mainline if we were just using a vanilla version of SDL2 for Android.
After that, I suppose there’d be the practical matters of submitting a PR, and setting up Jenkins to build an unsigned APK Android version (along with all its fun dependencies - java, ant, android sdk, android ndk etc.). Right now I’ve only had it building under Windows, though I believe Wulfe got it running under Linux, but he lost a bunch of his more recent changes (beyond 0.4.5) before they were pushed to GitHub, so what’s in Google Play is actually ahead of the GitHub source code, and I don’t think we’re able to recover those changes.
So yeah, it’s definitely possible, but a decent chunk of dev work.