AYN Thor Setup Guide: 13 Steps, 90 Minutes [2026]

What the AYN Thor Actually Is, and Why Setup Takes Longer Than Expected

AYN’s Thor is a clamshell Android handheld built around two AMOLED panels: a 6-inch, 1920×1080 top display that runs up to 120Hz, and a 3.92-inch, 1240×1080 touchscreen on the bottom running at 60Hz. It ships in four configurations. The Lite uses a Snapdragon 865 with an Adreno 650 GPU, 8GB of LPDDR4X RAM, and 128GB of UFS 3.1 storage. The Base, Pro, and Max all move to a Snapdragon 8 Gen 2 with an Adreno 740 GPU, scaling RAM from 8GB to 16GB of LPDDR5X and storage from 128GB up to 1TB. Every tier runs a 6,000mAh battery with 27W charging, and the higher three tiers add Wi-Fi 7 and Bluetooth 5.3 over the Lite’s Wi-Fi 6 and Bluetooth 5.1. Dimensions land at roughly 150 x 94 x 25.6mm and 380g.

According to trend-tracking data published by RisingTrends, “Android Handheld” search volume sits near 9,900 monthly queries with 22% year-over-year growth, while the AYN Thor itself is driving a steep spike in handheld-specific search traffic as reviews land through late 2026. That spike correlates with a second trend: this is not a plug-and-play console. The Thor arrives with no bundled games, no preinstalled emulator, and no third-party launcher. AYN wraps the dual screens in its own AOSP launcher, but everything beyond stock Android app behavior, including RetroArch, Winlator, and streaming clients, is something the owner installs manually. That is the gap this AYN Thor setup guide closes.

Prerequisites: What You Need Before You Start

– An AYN Thor unit (Lite, Base, Pro, or Max) with at least 40% battery
– USB-C to USB-C cable (the one in the box works, but a 3A-rated cable speeds up charging)
– A microSD card, UHS-I or UHS-II, 64GB to 2TB, formatted exFAT or ready to format on-device
– A Windows, macOS, or Linux PC with a free USB port for ADB-based sideloading
– Android Platform Tools (ADB and Fastboot) version 36.0 or newer, downloaded from Google’s official SDK platform-tools page
– A Google account, or a plan to skip one during first boot
– Wi-Fi network access, ideally 5GHz or Wi-Fi 6/7, for firmware downloads and app installs
– RetroArch for Android, version 1.21 or newer, downloaded as an APK or through the Play Store
– Winlator, version 10.0 or newer, for Windows game emulation on the Snapdragon 8 Gen 2 models (Base, Pro, Max)
– Moonlight for Android, latest stable build, if cloud/PC game streaming is part of the plan
– Your own ROM files or legally owned game backups; this guide does not provide or link to pirated content

One hardware note matters before the first boot: internal UFS 3.1 storage on the Thor is rated up to roughly 2,100MB/s sequential read and 1,200MB/s sequential write. Even premium UHS-II microSD cards rarely clear a few hundred MB/s, so treat the SD slot as bulk storage for ROMs and large game files, not as a drive for anything performance-sensitive like active emulator save states or Winlator containers.

Step 1: Unbox and Inspect Your AYN Thor Model

Before powering on, confirm which configuration arrived. The box and the rear label both list the chip and storage tier, but it is worth double-checking against the order confirmation, since AYN has shipped four distinct SKUs with meaningfully different performance ceilings. A Lite unit with a Snapdragon 865 will struggle with anything beyond PS2-era emulation and light Android titles, while a Base, Pro, or Max unit with the Snapdragon 8 Gen 2 can realistically handle GameCube, Wii, early Switch titles, and Windows games through Winlator’s translation layer.

Inspect the hinge for smooth, consistent resistance across its full range of motion, check both screens for dead pixels under a solid gray background, and test every button and both Hall-effect joysticks for drift or sticking before the warranty window starts counting down. The Thor’s shell is a clamshell with front-facing speakers along the lower edge; several hands-on reviews have flagged this speaker placement as something that is easy to accidentally cover with a hand grip, so get a feel for where fingers naturally rest during the inspection pass.

Step 2: Charge Fully Before the First Boot

Plug in with the supplied USB-C cable and let the 6,000mAh battery reach 100% before doing anything else. The Thor charges at up to 27W, which brings a fully depleted battery to full in roughly two hours on a compatible PD charger. Charging fully first avoids a mid-setup shutdown during firmware flashing, which is the one failure mode that can genuinely brick a device if it happens during an OTA write.

Step 3: Complete First Boot, With or Without a Google Account

Power on and work through Android 13’s standard first-run wizard: language, Wi-Fi, and then the Google account prompt. The Thor supports skipping the Google account entirely during this step, which some privacy-conscious owners prefer since the device is going to run heavily sideloaded software anyway. Skipping it does disable Play Store access until an account is added later through Settings, so anyone planning to install RetroArch or Moonlight from the Play Store should sign in now rather than skip and come back.

As the IGN review of the device put it, “Downloading games and apps from the Play Store is as easy as it ever is, simply requiring you to log in with your account, find what you want, and click download.” That simplicity is the whole point of signing in during this step instead of after the fact.

Step 4: Update the Firmware Before Building Anything Else

This is the step most new owners skip, and it is the one that causes the most downstream problems. Early AYN Thor units have shipped with firmware that predates fixes for display flicker, Bluetooth pairing drops, and battery reporting accuracy. Go to Settings, then System, then System Update, and install every available update before installing a single app or emulator. If an update changes default display or performance settings, as several firmware revisions have, redoing app installs after the update wastes far less time than redoing them before it.

After the OTA update finishes and the device reboots, open a terminal on a connected PC and verify the installed build number over ADB before moving on, since the on-screen version string is not always the clearest indicator of which patch actually landed:

adb devices
adb shell getprop ro.build.version.incremental
adb shell getprop ro.build.date

USB debugging needs to be turned on first for this to return anything useful. That happens in Settings, About Phone, tapping Build Number seven times to unlock Developer Options, then enabling USB Debugging inside the new Developer Options menu.

Step 5: Configure the Dual-Screen Display and Refresh Rate

The top 6-inch AMOLED panel defaults to a lower refresh rate on most firmware builds, trading some motion smoothness for battery life. For fast-paced emulation or Winlator-streamed PC games, forcing the full 120Hz mode is worth the battery trade-off. Inside Developer Options, enabling “Force peak refresh rate” pushes the top panel to 120Hz across all apps, though it is also settable per-profile through ADB if a toggle-by-toggle workflow is preferred:

adb shell settings put system peak_refresh_rate 120
adb shell settings put system min_refresh_rate 60

The bottom 3.92-inch screen is fixed at 60Hz since it is primarily a touch-input and secondary-display panel rather than a main viewport, so there is nothing to configure there beyond brightness and auto-rotation, both of which live in the standard Android display settings. Several early hands-on write-ups have also flagged a visible brightness-uniformity pattern known as the mura effect on some top-panel units, most noticeable on flat gray or white backgrounds at low brightness. It is a panel-level cosmetic issue rather than a settings problem, so if it shows up, it is worth documenting with photos for a warranty claim rather than chasing a software fix.

Step 6: Set Up the microSD Card the Right Way

Insert the microSD card after the firmware update is confirmed, not before. Android formats and mounts the card during this step, and the Thor gives two choices: Portable storage, which keeps the card readable in a PC card reader, or Internal/Adoptable storage, which encrypts and ties the card to the device but lets some apps treat it as extended internal space. For a device meant to swap ROM libraries between machines, Portable mode is the better default. Go to Settings, Storage, tap the SD card entry, and choose the storage type before copying any files over.

Because UFS 3.1 internal storage dramatically outperforms even fast microSD cards, keep RetroArch’s core and state folders, Winlator’s container files, and any actively-written save data on internal storage, and reserve the SD card for the bulk ROM and ISO library itself. This single decision affects load times and emulator responsiveness more than almost any other setting in this guide.

Step 7: Install RetroArch and Point It at Your Library

With Play Store access confirmed, install RetroArch directly, or sideload the APK from RetroArch’s official site if a Play Store account was skipped in Step 3. Sideloading requires enabling “Install unknown apps” for whichever file manager or browser is doing the installing, found under Settings, Apps, then the three-dot menu for special access permissions.

From a connected PC, the fastest path is pushing the APK and launching the installer directly over ADB:

adb install ./retroarch-android.apk
adb shell am start -n com.retroarch/.browser.retroactivity.RetroActivityFuture

Once installed, open RetroArch’s Online Updater to download cores. For DS emulation, both the DeSmuME core inside RetroArch and the standalone DraStic emulator are viable, with DraStic generally running better on the Lite’s older Snapdragon 865. On the Snapdragon 8 Gen 2 tiers, cores for GameCube, Wii, and early 3DS titles are realistic additions; heavier Switch and PS3 titles need separate, purpose-built emulators rather than RetroArch cores, and performance varies heavily by title, similar to the trade-offs covered in our DuckStation vs ePSXe vs RetroArch comparison. Point RetroArch’s file browser at the microSD card’s ROM folder under Settings, Directory, System/BIOS, and Content, and the library should populate on the next scan.

Step 8: Set Up Winlator for Windows Game Emulation

This step only applies to the Base, Pro, and Max tiers, since Winlator’s Box64 and Wine translation layer needs the Snapdragon 8 Gen 2’s Adreno 740 GPU to run acceptably; the Lite’s older Adreno 650 is not a realistic target for x86 Windows emulation. Download Winlator from its official GitHub releases page, sideload the APK the same way as RetroArch, then create a new container from inside the app.

Each Winlator container is effectively an isolated Wine prefix with its own DXVK and driver configuration. For lighter 2D or older 3D Windows titles, the default DXVK/Vulkan preset is usually enough. For anything leaning on newer DirectX features, switching the container’s graphics driver preset to a Turnip-based Vulkan driver build, where available in the Winlator release, tends to produce more stable frame pacing than the stock option. Store each container’s files on internal storage, not the SD card, since container I/O is constant during gameplay and the UFS 3.1 to microSD gap shows up immediately as stutter if containers live on the card.

Step 9: Map Controls and Calibrate the Hall-Effect Sticks

The Thor’s joysticks and triggers both use Hall-effect sensors, which resist the physical drift that plagues potentiometer-based sticks over time, but they still benefit from a calibration pass after setup. Inside RetroArch, go to Settings, Input, Port 1 Controls, and run through “Set All Controls” to bind the Thor’s ABXY layout, D-pad, and both triggers to a per-core or global profile. For Winlator, controller mapping lives inside each container’s settings, where Xbox-style default bindings usually need remapping to match whatever the specific Windows game expects.

A quick drift check is worth running before relying on any saved profile: open Android’s Developer Options, enable “Pointer location,” and watch the on-screen stick position readout while both analog sticks sit at rest. Any persistent offset away from dead-center on a Hall-effect stick usually means a software recalibration inside AYN’s control panel app rather than a hardware fault, since Hall sensors drift far less than mechanical potentiometers but are not immune to firmware-side miscalibration.

Step 10: Set Up Cloud and PC Game Streaming

For games that are too demanding for on-device emulation or Winlator translation, streaming from a gaming PC or a cloud service is the more reliable path. Moonlight, paired with Sunshine or Nvidia GameStream on the host PC, is the most common setup. Install Moonlight from the Play Store, make sure the host PC and the Thor are on the same network, and pair them using the PIN code Moonlight generates on first launch:

# On the Sunshine host PC
sunshine –pair 123456

# The six-digit PIN above matches the code shown
# in the Moonlight app on the AYN Thor during pairing

The Thor’s Wi-Fi 7 radio on the Base, Pro, and Max tiers (Wi-Fi 6 on the Lite) makes a meaningful difference for streaming latency and bitrate stability compared to older handhelds still running Wi-Fi 5. Set Moonlight’s bitrate manually rather than relying on auto-detection when streaming over 5GHz or 6GHz bands, since auto-detection tends to undershoot available bandwidth on newer routers. For services like GeForce NOW or Xbox Cloud Gaming, the setup is simpler: install the respective Android app or use a Chromium-based browser shortcut, since neither service needs local pairing or a host PC, a distinction we cover in more depth in our free cloud gaming setup walkthrough.

Step 11: Optimize Battery and Thermal Behavior

The 6,000mAh cell comfortably covers several hours of emulation but drains faster under Winlator or streaming workloads, both of which keep the Snapdragon 8 Gen 2 near its thermal ceiling for extended periods. Inside Settings, Battery, switch on a custom performance profile if AYN’s firmware exposes one, and cap the top screen’s refresh rate back to 60Hz for anything that is not latency-sensitive, since 120Hz draws noticeably more power for marginal benefit in turn-based or slower-paced titles.

The Thor includes active cooling, which keeps sustained Winlator or streaming sessions from thermal throttling as aggressively as a fanless handheld would, but fan noise becomes audible under load. There is no user-exposed fan curve control on current firmware, so the practical lever for thermal management is workload: dropping Winlator’s internal resolution scale or Moonlight’s streamed bitrate reduces GPU load and, by extension, fan noise and battery draw together.

Step 12: Organize Storage, Launchers, and Backups

With emulators, Winlator containers, and streaming apps installed, the stock AYN dual-screen launcher can get cluttered fast. A dedicated gaming launcher built specifically around the Thor’s two-screen layout, distributed as an open-source project on GitHub, adds proper focus handling between the top and bottom panels, something the stock AOSP launcher does not fully account for. Installing it is optional but worth testing if the default launcher’s window focus feels inconsistent when switching between a running game on top and a control or map screen on bottom.

Before loading the device with a full game library, back up the current app and settings state. ADB’s backup command covers most sideloaded app data, though RetroArch save states and Winlator containers are large enough that a manual copy to a PC is more reliable than an ADB backup archive:

adb shell settings list system > thor_settings_backup.txt
adb pull /sdcard/Android/data/com.retroarch/files/ ./retroarch_backup/

Choosing a Launcher: Stock AOSP vs Daijisho vs ES-DE

AYN’s own dual-screen launcher handles the basics, scrolling installed apps across both panels and letting the bottom screen act as a secondary control surface, but it was not built as a game-library front end. Two community options fill that gap for anyone running a large emulator collection: Daijisho, which scrapes box art and metadata automatically and launches straight into RetroArch or standalone emulators, and ES-DE (EmulationStation Desktop Edition), a more configuration-heavy front end originally built for dedicated retro handhelds and ported to Android. Both install the same way as RetroArch, through a sideloaded APK with “Install unknown apps” enabled for the browser or file manager doing the install.

The trade-off between the three comes down to setup time versus day-to-day convenience. The Galaxus review of the device noted that “depending on how many emulators you need, the Thor can be set up in minutes,” and that holds true if the plan is to stick with the stock launcher and open RetroArch directly. Daijisho and ES-DE both add real setup time upfront, mostly around scraping metadata and organizing ROM folders into the naming structure each tool expects, but they pay that time back on every session afterward with a proper grid-view library instead of a flat app list.

For a dual-screen device specifically, ES-DE’s community builds have had more consistent handling of secondary-display behavior than Daijisho in early 2026 testing, since ES-DE’s underlying EmulationStation codebase was adapted with multi-display Android devices in mind from an earlier handheld generation. Neither tool is required to use the Thor; they are purely a convenience layer on top of everything already installed in Steps 7 and 8.

Step 13: Run a Final Full-System Pass

Before calling the setup finished, run through every input, both screens, Wi-Fi, Bluetooth, USB-C video output if planning to dock the Thor to a TV, and at least one title from each category: a RetroArch core, a Winlator container if applicable, and a Moonlight stream. The Thor outputs over USB-C with DisplayPort alt-mode support, so a USB-C to HDMI cable or dock is enough to confirm external display output works before relying on it later for a TV-connected session.

According to a long-term review published by Pocket Gamer, “The Thor does require some light tweaking and internal file editing to make it really shine,” which matches the pattern this entire guide follows: nothing about the AYN Thor setup process is broken, but almost nothing about it is automatic either.

AYN Thor Model Comparison: Lite vs Base vs Pro vs Max

Picking the