Could you walk me through creating an arm64 virtual device? with images?
**How to create an ARM 64 virtual device on Genymotion SaaS (cloud)**
*(See screenshots in the official blog post: “Genymotion’s ARM64 virtual devices are now officially live!” – July 23 2025)*
---
### 1️⃣ Sign in to the Genymotion Cloud dashboard
1. Open
2. Select **Genymotion SaaS** (the cloud platform).
---
### 2️⃣ Add a new virtual device
1. In the left‑hand menu, click **Virtual Devices** → **+ Create**.
2. The “Create Virtual Device” wizard appears.
---
### 3️⃣ Pick an ARM‑64 image
| Step | What to choose | Why it matters |
|------|----------------|----------------|
| **OS** | **Android** | We’re creating an Android VM. |
| **Architecture** | **ARM64** (arm64‑v8a) | Eliminates the x86 → ARM translation layer, giving you a true‑ARM testing environment. |
| **Android version** | Choose the latest (e.g., Android 15 or Android 16 when available). | ARM64 support is available for all current Android releases. |
| **Device model** | Pick the phone/tablet that matches your target audience (e.g., Pixel 7a, Galaxy S24, etc.). | Keeps your test environment close to the real device. |
> *Tip:* The preview thumbnail will show a “64‑bit” badge.
---
### 4️⃣ Configure device settings
- **Name** – e.g., `My_ARM64_Test_Dev`.
- **Resolution** – e.g., 1080 × 2400 for a standard phone.
- **RAM & CPU** – Default is fine; bump RAM if you run heavy tests.
- **Storage** – 64 GB is typical.
- **Advanced** – Enable **GPU acceleration** if you’ll test graphics‑heavy apps.
---
### 5️⃣ Launch the device
1. Click **Create**.
2. The new VM appears in your list.
3. Hit the **Start** button.
When the device boots:
- Open **Settings → About phone** → check **CPU/ABI** → should say `arm64‑v8a`.
- Or run in a terminal:
```bash
adb shell getprop ro.product.cpu.abi
# → arm64-v8a
```
---
### 6️⃣ (Optional) Use the CLI for CI/CD
If you’re automating tests, the **gmsaas** CLI can spin up ARM64 VMs on the fly:
```bash
gmsaas start \
--arch arm64 \
--android-version 15 \
--name My_ARM64_Test_Dev
```
Then point your test framework (Appium, Espresso, etc.) to the returned public IP or internal DNS.
---
### 7️⃣ Tips & Gotchas
| Issue | Fix |
|-------|-----|
| **Boot takes longer** | ARM64 images use native ARM servers; expect ~70 % faster boot than x86. |
| **App crashes on startup** | Verify your app is compiled for `arm64‑v8a`. |
| **ADB not connecting** | Ensure the device’s port is forwarded in the dashboard or CLI. |
| **GPU‑heavy app lagging** | Enable GPU‑acceleration in the device settings. |
---
### 📚 Further Resources
- **Blog post**: “Genymotion’s ARM64 virtual devices are now officially live!” – July 23 2025 (includes screenshots).
- **Docs**: `genymotion.com/docs/arm64` – detailed API & CLI usage.
- **Support**: Chat widget or ticket if you hit a roadblock.
Happy testing! 🚀
---
**Quick follow‑up:** Which Android version are you targeting for your next project? This will help us suggest the best ARM64 device for your needs.