Installation

Step 1: Download and verify the installer

Download the latest Orbittest-Studio-Setup-x.x.x.exe from the official GitHub releases page (linked from this site’s homepage). Before running it, verify the file hash, this confirms the download was not corrupted or tampered with:

Get-FileHash .\Orbittest-Studio-Setup-1.0.0.exe -Algorithm SHA256

PowerShell. The output must exactly match the hash published on the Installer Integrity page.

The published SHA256 for v1.0.0 and the full verification walkthrough are on the Installer Integrity page.

Step 2: Run the installer

Double-click the installer and follow the prompts. One expected speed bump: the installer is not yet Authenticode-signed, so Windows SmartScreen may show “Windows protected your PC”. Click More info, then Run anyway, this prompt is about the missing code-signing certificate, and the hash check you just did is what actually proves the file is genuine.

Step 3: Enable USB debugging on the phone

Go to Settings → About Phone.
Tap Build Number 7 times. Android unlocks Developer Options (you will see a small toast confirming it).
Go to Settings → Developer Options.
Enable USB Debugging.
Connect the phone to the PC with a USB data cable.
On the phone, tap Allow on the “Allow USB debugging?” prompt to authorize this computer.

Step 4: Install the Companion app

Open Orbittest Studio.
Your device should appear in the Devices panel (left sidebar) within a few seconds.
Select the device and click Install on the device card.
Approve the installation prompts on the phone.

If Android blocks the install, enable Developer Options → Install via USB and try again, several vendors (notably Xiaomi and some Oppo/Vivo builds) gate USB installs behind this extra switch. If a previous Companion version is on the phone, uninstall it first from the phone’s app settings.

If the device does not appear

Work through these in order; each one rules out a layer:

Run adb devices in a terminal. The device must show with the state device. If adb itself is not found, install platform-tools or point Studio at the binary.
If it shows unauthorized, unlock the phone and accept the USB debugging prompt.
If adb is not on PATH, open Studio Settings and set the ADB path manually, typically C:\Users\<you>\AppData\Local\Android\Sdk\platform-tools\adb.exe.
Still nothing: different cable, different port, then a different machine to isolate the phone vs the PC.

adb devices
# List of devices attached
# R58M12ABCDE     device      <- ready
# R58M12ABCDE     unauthorized <- accept the prompt on the phone

The two adb states you will see, and what they mean.

Frequently asked questions

Why does SmartScreen warn about the installer?

The installer is not yet signed with an Authenticode certificate, so Windows cannot attribute a publisher. The published SHA256 hash is the integrity check; verify it before running and the warning is expected noise.

Does Studio need admin rights?

The installer follows standard Windows install prompts. Day-to-day, Studio runs as a normal user app; talking to a USB device through adb needs no elevation.

Can I use Studio with an emulator?

Studio targets devices visible to adb. An emulator that appears in adb devices can work for test runs, though the mirror and Companion features are built primarily for physical devices.

Installer Integrity — Verify the Studio installer with its published SHA256 hash before running it, and follow safe download practices.
Quick Start — From new project to first passing mobile test: connect a device, write a smoke test, run it, and review the video evidence.
Troubleshooting — Fixes for unauthorized devices, missing devices, blocked Companion installs, black mirror screens, and empty log panels.
What is Studio? — Orbittest Studio explained: a Windows desktop IDE that puts device mirror, inspector, logcat, editor, and test runner in one app.