GPU-accelerated rendering
A Vulkan-to-Metal translation path drives the Android graphics stack directly on Apple silicon GPU hardware, with per-title compatibility fixes for engines that assume a different Vulkan implementation.
How ARAs presents Android hardware.
A grounded look at rendering, device identity, sensors, and the controls you have over each.
Rendering
Frames are presented from Android's own graphics memory through Metal on Apple silicon, not screen-captured or streamed as video.
GPU identity matched to the device profile
The reported GPU model scales with your Mac's chip tier and the active device profile, so apps that check for a specific graphics adapter see one consistent with the rest of the hardware profile.
Device profile
ARAs presents a coherent, real flagship hardware identity rather than a generic virtual-machine signature, and it's configurable per profile, not hardcoded.
Real flagship hardware identity
The default profile reports as a current-generation flagship Android phone with a top-tier chipset, Android 17, and arm64-v8a, matched end-to-end across build properties, board ID, and GPU model.
Per-profile overrides
SoC manufacturer, board, bootloader, and API level can be adjusted per profile at boot, so different profiles can present distinct hardware identities.
IMEI rotation
Generate a fresh, checksum-valid IMEI for a profile on demand from the app menu. Android restarts to apply it.
GMS or clean AOSP
Choose a Google Mobile Services build for apps that require it, or a Google-free AOSP build with no Play packages installed at all.
Sensors & input
What's actually wired to real or simulated hardware today:
GPS & location
Set a location from presets, including latitude, longitude, and timezone, with simulated position drift fed to Android's location providers rather than a single fixed point.
Camera & microphone
Passthrough to your Mac's real camera and microphone, matched to the best available capture format.
Orientation & rotation
Rotate the emulated device from the menu, a keyboard shortcut, or a two-finger trackpad gesture. Orientation stays in sync in both directions with whatever the Android app itself requests.
Gaming Mode
A dedicated mode for demanding titles, not a permanent tradeoff, since settings restore exactly when you turn it off.
Resolution & performance tiers
Cap rendering resolution and step CPU/RAM headroom between balanced, high, and max, with a matching GPU model bump at the higher tiers.
Key mapping
Map keyboard and mouse input to on-screen touch controls for games that don't natively support keyboard input.
Debugging & compliance
ADB and root access are a build-time choice, not a fixed setting, so the standard and development runtimes behave differently on purpose.
Standard runtime: locked down
The standard runtime disables Android debugging and root access at boot, so ARAs doesn't present as a rooted or debug-attached device to apps and anti-cheat systems that check for it.
Development runtime: ADB and root available
A separate development runtime enables ADB and a privileged root shell for testing and sideloading. It's bound to localhost only and never reachable from the network.
ARAs is emulation software: a tool that presents Android hardware on your Mac using the profile you choose and configure yourself. What you install and how you use any given app is between you and that app's own terms of service. ARAs does not operate, monitor, or endorse individual usage.