Difference between revisions of "Emulation:Android"
Line 68: | Line 68: | ||
{{++}} Runs using Hyper-V which is Type 1 Virtual machine and offers near bare-metal CPU performance compared to Virtualbox solution. | {{++}} Runs using Hyper-V which is Type 1 Virtual machine and offers near bare-metal CPU performance compared to Virtualbox solution. | ||
{{++}} Offer much better CPU compatibility by using latest compatibility layer called "Intel Bridge". | {{++}} Offer much better CPU compatibility by using latest compatibility layer called "Intel Bridge". | ||
− | {{++}} Based on Android | + | {{++}} Based on Android 12 (API level 31) source code since 2204 version. |
{{++}} Highest image and audio quality possible compared to Virtualbox solution. | {{++}} Highest image and audio quality possible compared to Virtualbox solution. | ||
+ | {{++}} Perfect multi touch support for devices have a touch screen like Surface series. | ||
{{ii}} WSA is in Insider testing. | {{ii}} WSA is in Insider testing. | ||
− | {{ii}} No Vulkan at the moment. | + | {{ii}} No GLES 3.1+ & Vulkan at the moment. |
{{ii}} Apps outside of Amazon Appstore have to be sideloaded. | {{ii}} Apps outside of Amazon Appstore have to be sideloaded. | ||
+ | {{--}} High audio latency (~300ms). | ||
{{--}} Only runs on Windows 11. | {{--}} Only runs on Windows 11. | ||
{{--}} No keymapper, must rely on game support to properly controlling games. | {{--}} No keymapper, must rely on game support to properly controlling games. |
Latest revision as of 02:59, 13 June 2022
Key points
- There are several x86 builds of Android, most notable being Android-x86 (Wikipedia article), which allows Android to be installed on regular PC hardware without need for emulation. However, due to most applications being done for ARM architecture, some applications and especially games, simply do not work.
General information
- Android at Emulation General Wiki
Android-x86 based emulators
These emulators are based on Android-x86 source code and mostly use Virtualbox as virtual machine.
- Use older Intel CPU compatibility layer called Intel Houdini which runs slower than Intel Bridge used in Windows Subsystem for Android™
BlueStacks
Key points
General information
MEmu
Key points
General information
LDPlayer
Key points
General information
NoxPlayer
Key points
General information
XePlayer
Key points
General information
KoPlayer
Key points
General information
Gameloop
Key points
- Enable rendering optimization can fix some graphical glitches[1]
- If having stuttering, try to enable vertical sync in the game settings[1]
General information
Non Android-x86 based emulators
These emulators are not based on Android-x86 source code, and possibly closed-source most of the core parts.
Genymotion
Key points
- Runs on Virtualbox
General information
Windows Subsystem for Android™
Key points
- Runs using Hyper-V which is Type 1 Virtual machine and offers near bare-metal CPU performance compared to Virtualbox solution.
- Offer much better CPU compatibility by using latest compatibility layer called "Intel Bridge".
- Based on Android 12 (API level 31) source code since 2204 version.
- Highest image and audio quality possible compared to Virtualbox solution.
- Perfect multi touch support for devices have a touch screen like Surface series.
- WSA is in Insider testing.
- No GLES 3.1+ & Vulkan at the moment.
- Apps outside of Amazon Appstore have to be sideloaded.
- High audio latency (~300ms).
- Only runs on Windows 11.
- No keymapper, must rely on game support to properly controlling games.
- Having several GPU rendering issues.
- Heavy RAM consumption and very slow booting speed.
- Incompatible with Google Play login and impossible to login into games that use Google Play Services.
General information
- Introducing Android™ Apps on Windows 11 to Windows Insiders
- Windows Subsystem for Android™ support page
- Store link