About

FrameDrop is a sideloading client for Steam Frame. Drop a build on your PC and it's automatically uploaded to Steam on the headset.

What is sideloading

Sideloading is installing software on a device without going through its store. On Steam Frame, that means copying an app from your PC onto the headset and adding a Steam shortcut so you can launch it. Same as similar software for other platforms.

How FrameDrop sideloads

FrameDrop uses Valve’s SteamOS Devkit path. Pair the headset once, then drop an APK, a Linux ARM64 zip, or a Windows exe. FrameDrop detects which runtime the title needs, fills in the start command and arguments required to launch it on the headset, and registers it as a Devkit Game in Steam.

The copy uses the same tools as the SteamOS Devkit Client: pair over the Devkit service, then SSH and rsync. On other platforms that job is often ADB.

Why FrameDrop

The SteamOS Devkit Client is a solid developer tool, and it is the same pathway. Using it by hand means choosing the right runtime for each payload, then typing the start command and launch arguments yourself so Steam can find the binary on-device. That is a lot of setup for a casual install. FrameDrop reads the file, picks the runtime, and writes those commands for you.

Compatibility

Android (Lepton)

• Android version: Lepton runs Android 11, API level 30. APKs with a minSdkVersion of 30 or lower install. APKs that require 31 or higher, such as SDK 32 (Android 12L), fail with INSTALL_FAILED_OLDER_SDK.
• CPU: ARM64 only. APKs need arm64-v8a libraries, or no native libraries at all. Universal APKs that include arm64-v8a work. APKs with only armeabi-v7a (32-bit) fail with INSTALL_FAILED_NO_MATCHING_ABIS.
• Signature: an APK whose signature no longer matches its contents, usually a modified or repacked APK, fails with INSTALL_PARSE_FAILED_NO_CERTIFICATES.
• Package format: one .apk file. Split packages (.apks, .xapk, .aab) need to be merged into a single APK first.
• OBB data: an obb folder next to the APK uploads with it.
• VR and Flatscreen: Android (Lepton VR) is for OpenXR apps. Android (Lepton Flatscreen) opens 2D phone and tablet apps in a window.
• Failed installs: when Android rejects an APK, Lepton closes a few seconds after launch. The reason is in the Lepton log on the headset.

Linux

• CPU: ARM64 (aarch64) builds run natively in Steam Linux Runtime 4.0 ARM64.
• x86_64: x86_64 builds map to Steam Linux Runtime 4.0 and depend on translation on the headset. ARM64 builds are the reliable choice.
• Zips: zipped builds unpack on the PC before upload. A single wrapper folder is fine.

Windows

• Proton: .exe builds run through Proton. ARM64 Proton has to be installed on the headset.

Troubleshooting

Connecting

• “No headset found. Still looking.” The headset is asleep, on a different network, or the name is not resolving. Wake the headset, check both are on the same Wi-Fi, or enter the headset’s IP address in Settings → Connection.
• “Headset refused pairing.” On the Frame, open Settings → Developer → Pair new host, then click Pair in FrameDrop while that screen is open.
• “Paired, but the headset isn’t ready yet.” The headset is still accepting the new key. Wait a few seconds, then Connect.

Installing

• “Files went up. Steam on the Frame did not add the shortcut.” Steam was closed, asleep, or busy on the headset. Open Steam on the Frame, then Install again.
• “Upload stopped.” The connection dropped mid-copy. Keep the headset awake and on the same network, then Install again.
• “Steam could not find the launch file.” The launch file had a space in its name. Drop the file again, then Install.

Launching

• Lepton opens, then closes after a few seconds. Android rejected the APK. The usual causes are an SDK above 30, no ARM64 libraries, or a signature that no longer matches the file. The exact reason is in the headset log: switch FrameDrop to logs, then Pull log.
• A 2D Android app shows nothing in VR. Phone and tablet apps need Android (Lepton Flatscreen). Pick it in the runtime list, then Install again.
• A Linux build is listed but does not start. The build needs to be ARM64, and the launch file needs execute permission. Check the permissions in Explorer: right-click the file, then Properties.
• A Windows build is listed but does not start. ARM64 Proton has to be installed on the headset.

Windows

• “FrameDrop needs the Microsoft Edge WebView2 Runtime.” Install the WebView2 Runtime from Microsoft, then open FrameDrop again.
• Setup stops while replacing FrameDrop. FrameDrop was still running. Close it, or end it in Task Manager, then run Setup again.
• Reporting a problem. The PC log is in Settings → Logs, and on disk at %LOCALAPPDATA%\FrameDrop\framedrop.log.