How to Install Android Studio on Manjaro Linux
If you’re trying to get Android development up and running on Manjaro, the process is surprisingly painless once you know where to look. In this guide I’ll walk through installing Android Studio from the official repository, setting up the SDK, and fixing a common “SDK manager can’t find updates” glitch that tripped me up after a recent kernel upgrade.
Why the Arch‑Based Build Works Best on Manjaro
Manjaro ships with the latest system libraries out of the box, which means the Android Studio package from the AUR or the official JetBrains repo is already compiled for your environment. You won’t need to juggle multiple JREs like you would on a Debian‑based distro.
Step 1: Install Java – It’s the Foundation
sudo pacman -S jdk-openjdk
Android Studio requires at least Java 11. Installing it via pacman guarantees that the runtime matches what Android expects, so you won’t hit “Unsupported JVM” errors later.
Step 2: Pull the Latest Studio Build
sudo pacman -S android-studio
The android-studio package pulls a pre‑built binary from JetBrains. Using the official repo keeps everything in sync with updates, and you avoid the hassle of manually unpacking ZIPs.
Step 3: Launch and Create a Default SDK
1. Start Android Studio (android-studio from terminal or from your app launcher).
2. Accept the default settings.
3. When the “Android SDK” screen appears, click Next to let the installer download the latest platform‑tools and build‑tools.
Why this matters: The installer configures environment variables for you, so when you run adb from a terminal it works immediately.
Step 4: Add Android Tools to Your Path (Optional but Handy)
If you prefer using adb and fastboot from any shell without typing the full path:
echo 'export PATH=$PATH:/opt/android-studio/bin' >> ~/.bashrc source ~/.bashrc
This makes it a one‑liner, no more hunting for binaries in /opt.
Step 5: Fix “SDK Manager Cannot Find Updates” After Kernel Upgrade
After I upgraded from Manjaro 22.0 to 23.0, the SDK manager stopped finding updates and kept throwing “Unable to download from https://dl.google.com/android/repository/...”. The fix is simple:
1. Open a terminal and run:
sudo pacman -Syu --asdeps lib32-glibc
2. Then restart Android Studio.
The 32‑bit glibc dependency is needed by the SDK tools’ native binaries; without it, HTTPS requests silently fail.
Step 6: Verify Everything Works
adb devices
If you see “list of devices attached” even when no device is connected, that’s a good sign. Then try creating a new project and hit Run on an emulator or physical device—if it launches without hiccups, you’re all set.
That’s the whole recipe in under ten minutes. If you run into hiccups, drop a comment; I’ve been there with stubborn drivers and missing SDK components.