Repository navigation
Open Android DeX v0.3.25
Which download
| Your machine | File |
|---|---|
| Windows | ..._x64-setup.exe (installer) or ..._x64_portable.zip |
| Mac, Apple Silicon (M1–M4) | ..._aarch64.dmg |
| Mac, Intel | ..._x64.dmg |
| Linux — Ubuntu, Debian, Mint | ..._amd64.deb |
| Linux — Fedora, openSUSE | ..._x86_64.rpm |
| Any other Linux | ..._amd64.AppImage |
Not sure which Mac you have? → About This Mac, and read the "Chip" line.
Linux is 64-bit Intel/AMD only for now. It is the one machine scrcpy publishes
a ready-made build for, and shipping a version of this that could not talk to
your phone would not be worth the download.
No computer? The phone apps are here too
Both install straight onto the phone and need no PC at all.
| What you want | File |
|---|---|
| The DeX desktop on a monitor over HDMI, or in Samsung DeX | OpenAndroidDeX-Launcher-v<version>.apk |
| Just Ubuntu, on the phone | LinuxOnDroid-v<version>.apk |
The launcher APK is the same one the desktop app installs for you, so having
one does not stop you using the other. Custom titlebars are the one thing that
wants the computer — without it, your phone's own window chrome is used
instead.
Linux: installing it
Pick the file that matches what you run:
-
Ubuntu, Debian, Mint —
sudo apt install ./Open.Android.DeX_<version>_amd64.deb -
Fedora, openSUSE —
sudo dnf install ./Open.Android.DeX_<version>_x86_64.rpm -
Anything else — the AppImage. A downloaded file arrives without permission
to run, so give it that permission once and then start it:chmod +x Open.Android.DeX_<version>_amd64.AppImage ./Open.Android.DeX_<version>_amd64.AppImage
Linux: the phone appears but says it is not allowed
This is the one thing that catches nearly everyone, and it is not your phone's
fault. Linux only lets a program open a USB device when a rule says it may, and
a fresh install has no rule for a phone. Add the rules:
sudo apt install android-sdk-platform-tools-common
Then unplug the phone and plug it back in. The replug matters — the rules are
applied at the moment the phone appears, so one that was already connected keeps
the permissions it was given.
Linux: what is not there yet
Connecting, the desktop, the launcher, and Ubuntu and Docker on the phone all
work the same as everywhere else. Four smaller things are Windows-and-Mac only
for now, and none of them stop the desktop working:
- the fullscreen (⛶) button on the phone-side taskbar
- Escape to leave fullscreen
- three-finger touchpad gestures
- "Project to PC", which is a Windows feature and is hidden here
macOS: opening it the first time
Open Android DeX is not notarized — that needs a paid Apple Developer account
— so macOS will not open it until you say so once.
-
Open the
.dmgand drag the app into Applications. -
Open Terminal and run:
xattr -dr com.apple.quarantine "/Applications/Open Android DeX.app"The
-rmatters: the app shipsadbandscrcpyinside it, and those are
quarantined separately. Without it the app opens and then fails to talk to
your phone. -
Open it normally.
If you would rather not use Terminal: double-click the app, dismiss the
warning, then go to System Settings → Privacy & Security, scroll down to
Security, and press Open Anyway. (The old right-click → Open trick
stopped working in macOS 15.)
macOS: two permissions it will ask for
-
Local Network — needed to find phones over Wi-Fi. macOS asks the first
time you use a wireless connect option. Without it the Wi-Fi routes find
nothing; the USB cable is unaffected. -
Accessibility — only for the fullscreen (⛶) button on the phone-side
taskbar, which has to resize a window belonging toscrcpy. Everything else
works without it. Grant it under System Settings → Privacy & Security →
Accessibility.Because the app is signed ad-hoc rather than with a developer certificate,
macOS ties this permission to that exact build — after installing a new
version you may have to switch Open Android DeX off and on again in that
list.
Full Changelog: v0.3.24...v0.3.25