I have a request that might be slightly off-topic, since Android is usually associated more with phones than with general “computers,” but I think it’s still relevant. One of the biggest weaknesses of single-board computers is the lack of well-maintained Android images especially images that are not only stable but also optimized for users, gamers, and video playback.
Recently, there has been a lot of progress in Android emulation for both Qualcomm and Mali CPUs/GPUs. The Adreno-based drivers that now work across different CPUs, along with GameSir’s interactive app for easy Steam integration and the various Winlator forks, opened an entirely new world of possibilities. I’ve discovered a lot of things that shouldn’t be overlooked, and I’d like to share them.
I understand that while some Radxa products are great, they may not deliver flagship-level native performance especially for emulation. But a lot of the potential depends on how good the Android image is.
There have also been improvements in GSI implementations. For example, at least one user managed to run Android 16 on an Orange Pi 5. And we still have dedicated developers like mo123 who continue to push Android development forward.
So my request is this:
Could you open a forum group called “Android Developments”?
This would allow all Android-related topics to be organized in one place. I could also contribute by posting guides and sharing what I’ve learned.
Some of the content might extend beyond Radxa devices, but since many things are cross-compatible on Android, I’m sure a lot of it would still be useful. It would also help with testing and collecting feedback.
Topics could include:
- Winlator and its forks
- Their dependencies
- Fex-emu
- ptitseb’s boxes
- GameHub
- GameNative
- Switch emulators
What works and what doesn’t.
Steam on Android emulators (how to share the .exe files so they don’t need to be duplicated across multiple folders, especially when testing different Winlator forks)
I think this would be valuable for many users.
@RadxaYuntian 
please.
@hipboi please.