There are various applications to transfer files, synchronize notifications and more.
- KDE Connect (kdeconnect) – integrates your Android device with the KDE or Gnome desktop (featuring synced notifications & clipboard, multimedia control, and file/URL sharing).
- a2lnAUR – provides notification synchronization over LAN featuring authentication, encryption and more
- USB cable
- Media Transfer Protocol for modern Android devices
- USB mass storage for older devices
- Android Debug Bridge
- special USB sticks / regular USB stick with adapter
- Arch Linux software with Android counterparts
- client or server for protocols that can be used to transfer files (eg. SSH, FTP, Samba or HTTP)
- cloud synchronization clients
- sendanywhereAUR – cross-platform file sharing
- qrcpAUR – transfer files over wifi from your computer to your mobile device by scanning a QR code
The officially supported way to build Android apps is to use #Android Studio.
Android Studio is the official Android development environment based on IntelliJ IDEA. It provides integrated Android developer tools for development and debugging.
You can install it with the android-studioAUR package.
Android Studio creates a
.android directory in home directory. To reset Android Studio, this directory can be removed.
- Make sure you properly set the Java environment otherwise android-studio will not start.
- If Android Studio shows up as a blank window try exporting
_JAVA_AWT_WM_NONREPARENTING=1, see issue #57675.
The Android Studio Setup Wizard installs the required #SDK packages and places the SDK by default in
To build apps from the command-line (using e.g.
./gradlew assembleDebug) set the ANDROID_HOME environment variable to your SDK location.
Android SDK packages can be installed directly from upstream using #Android Studio's SDK Manager or the sdkmanager command line tool (part of the Android SDK Tools). Some Android SDK packages are also available as AUR packages, they generally install to
The required SDK packages are:
|Android SDK Package||SDK-style path||AUR package||AUR dummy||CLI tools|
|Command-Line Tools||tools||android-sdk-cmdline-tools-latestAUR||android-sdk-cmdline-tools-latest-dummyAUR||apkanalyzer, avdmanager, lint, retrace, screenshot2, sdkmanager|
|SDK Build-Tools||build-tools;version||android-sdk-build-toolsAUR||android-sdk-build-tools-dummyAUR||aapt, aapt2, aidl, apksigner, bcc_compat, d8, dexdump, dx, lld, llvm-rs-cc, mainDexClases, split-select, zipalign|
|SDK Platform-Tools||platform-tools||android-sdk-platform-toolsAUR||android-sdk-platform-tools-dummyAUR||adb, dmtracedump, e2fsdroid, etc1tool, #fastboot, hprof-conv, make_f2fs, make_f2fs_casefold, mke2fs, sload_f2fs, sqlite3, systrace|
|SDK Platform||platforms;android-level||android-platformAUR, older versions||android-platform-dummyAUR (unnecessary)|
The android-tools package provides adb, #fastboot,
mke2fs.android from the SDK Platform-Tools along with
- Since the Android SDK contains 32-bit binaries, you must enable the multilib repository. Otherwise you will get
error: target not found: lib32-*error messages.
- If you choose to directly install SDK packages from upstream, install the AUR packages of the AUR dummy column to pull in the required dependencies.
- If you get a
java.lang.NoClassDefFoundErrorexception when attempting to run
sdkmanager, use OpenJDK 8's JRE temporarily, by installing the package jre8-openjdk and switching the Java environment. See Failed to run sdkmanager --list with Java 9
The Android Emulator is available as the
emulator SDK package, the android-emulatorAUR package, and there is also a dummy package for it: android-emulator-dummyAUR.
To run the Android Emulator you need an Intel or ARM System Image. You can install them through the AUR, with the sdkmanager or using Android Studio's AVD Manager.
Other SDK packages in the AUR
The Android Support Library is now available online from Google's Maven repository.
You can also install it offline through the
extras;android;m2repository SDK package (also available as android-support-repositoryAUR).
Making /opt/android-sdk group-writeable
The AUR packages install the SDK in
/opt/android-sdk/. This directory has root permissions, so keep in mind to run sdk manager as root. If you intend to use it as a regular user, create the android-sdk users group, add your user.
# groupadd android-sdk # gpasswd -a <user> android-sdk
Set an access control list to let members of the newly created group write into the android-sdk folder. As running sdkmanager can also create new files, set the ACL as default ACL. the X in the default group entry means "allow execution if executable by the owner (or anyone else)"
# setfacl -R -m g:android-sdk:rwx /opt/android-sdk # setfacl -d -m g:android-sdk:rwX /opt/android-sdk
Re-login or as <user> log your terminal in to the newly created group:
$ newgrp android-sdk
Android Studio is the official Android development environment based on IntelliJ IDEA. Alternatively, you can use Netbeans with the NBAndroid-V2. All are described below.
If you prefer using Netbeans as your IDE and want to develop Android applications, use NBAndroid-V2 .
Install android-sdkAUR package and follow the instructions from the NBANDROID README.
Vim / Neovim
It is possible to write
flutter applications for Android and iOS using (Neo)vim like an IDE. Install coc using a Vim plugin manager. Also install the coc-flutter extension for autocompletion (like in Android Studio) and to load the code into an Android emulator.
To develop a mobile
flutter application using Emacs, as the the official instruction at flutter.dev suggests, install lsp-dart.
Marvin is a tool which helps beginners set up an Android development environment. Installing marvin_dscAUR helps you set up the following things: JDK, Android SDK, IDE(s), and AVD.
Please note that these instructions are based on the official AOSP build instructions. Other Android-derived systems such as LineageOS will often require extra steps.
To build AOSP 13 you need a TTF font installed (e.g. ttf-dejavu) and the dependencies of the aosp-develAUR metapackage.
Additionally, LineageOS (as well as other many Android distributions like ArrowOS,PixelExperience etc) requires the following dependencies of the lineageos-develAUR metapackage.
Java Development Kit
The required JDK version depends on the Android version you are building:
- For Android 9 (Pie) and up, Java is included with the Android source and no separate installation is needed.
- For Android 7 and 8 (Nougat and Oreo), OpenJDK 8 is required, which is available with the jdk8-openjdk package.
Set JAVA_HOME to avoid this requirement and match the Arch Linux installation path. Example:
$ export JAVA_HOME=/usr/lib/jvm/java-version-openjdkThis change will be valid only for the current terminal session.
Setting up the build environment
Create a directory to build.
$ mkdir ~/android $ cd ~/android
Downloading the source code
This will clone the repositories. You only need to do this the first time you build Android, or if you want to switch branches.
-jswitch that operates similarly to the one used with
make. Since it controls the number of simultaneous downloads, you should adjust the value depending on downstream network bandwidth.
- You will need to specify a branch (list of branches) to check out with the
-bswitch. If you leave the switch out, you will get the so-called master branch.
$ repo init -u https://android.googlesource.com/platform/manifest -b master $ repo sync -j4
-cswitch with the repo command as such:
$ repo sync -j8 -c
-c switch will only sync the branch which is specified in the manifest, which in turn is determined by the branch specified with the
-b switch, or the default branch set by the repository maintainer.
Wait a long time. Just the uncompiled source code, along with the
.git directories that are used to keep track of it, are very large. As of Android 10, at least 250 GB of free disk space is required.
$ repo sync
Building the code
This should do what you need for AOSP:
$ source build/envsetup.sh $ lunch full-eng $ make -j4
If you run lunch without arguments, it will ask what build you want to create. Use -j with a number between one and two times number of cores/threads.
The build takes a very long time.
- Make sure you have enough RAM. Android will use the
/tmpdirectory heavily. By default the size of
/tmpis half the size of your RAM. If it fills up, the build will fail. 4 GiB of RAM or more is recommended. If
/tmpis not large enough, you can increase it. Make sure you have the combined RAM and swap space to back it. Alternatively, you can get rid of the tmpfs from fstab all together.
- From the Android Building and Running guide:
- GNU make can handle parallel tasks with a
-jNargument, and it is common to use a number of tasks N that is between 1 and 2 times the number of hardware threads on the computer being used for the build. E.g. on a dual-E5520 machine (2 CPUs, 4 cores per CPU, 2 threads per core), the fastest builds are made with commands between
- GNU make can handle parallel tasks with a
Testing the build
When finished, run/test the final image(s).
Creating a flashable Image
To create an image that can be flashed it is necessary to:
make -j8 updatepackage
This will create a zip image under
out/target/product/hammerhead (hammerhead being the device name) that can be flashed.
In some cases, you want to return to the stock Android after flashing custom ROMs to your Android mobile device. For flashing instructions of your device, please use XDA forums.
Fastboot (as well as ADB) is included in the android-tools package.
- Restoring firmwares using
fastbootcan be quite tricky, but you might want to browse XDA developers forums for a stock firmware, which is mostly a
*.zipfile, but inside of it, comes with the firmware files and
flash-all.shscript. For example, Google Nexus firmwares include
flash-all.shscript or another example could be for OnePlus One - XDA thread, where you can find firmwares with included
- If you get a
no permissionserror or execution just hangs with
< waiting for any device >then you need to run
fastbootas the root user. Alternatively you can install android-udev or the AUR package android-udev-gitAUR and reconnect your device.
Samsung devices cannot be flashed using Fastboot tool. Alternatives are Heimdall and Odin (by using Windows and VirtualBox).
To download original Samsung firmware, a platform independent script, samloader can be used.
Heimdall is a cross-platform open-source tool suite used to flash firmware (also known as ROMs) onto Samsung mobile devices and is also known as an alternative to Odin. It can be installed as heimdall.
The flashing instructions can be found on Heimdall's GitHub repository or on XDA forums.
It is also possible to restore firmware (Android) on the Samsung devices using Odin, but inside the VirtualBox.
Arch Linux (host) preparation:
- Install VirtualBox together with its extension pack and guest additions.
- Install your preferred, but compatible with Odin, Windows operating system (with VirtualBox guest additions) into a virtual hard drive using VirtualBox.
- Open VirtualBox settings of your Windows operating system, navigate to USB, then tick (or make sure it is ticked) Enable USB 2.0 (EHCI) Controller.
- At VirtualBox running Windows operating system, click in the menu bar Devices > USB Devices, then click on your Samsung mobile device from the list, which is connected to your computer via USB.
Windows (guest) preparation:
- Install Samsung drivers.
- Install Odin.
- Download required Samsung firmware (Android) for your smartphone model.
Check if configuration is working:
- Turn your device into Download mode and connect to your Linux machine.
- In virtual machine toolbar, select Devices > USB > ...Samsung... device.
- Open Odin. The white box (a big one at the bottom-left side) named Message, should print a line similar to this:
which means that your device is visible to Odin & Windows operating system and is ready to be flashed.
Run Android apps on Arch Linux
There are several projects and methods which support running Android on Arch Linux (or other distributions). As listed below:
- Container-based solutions tend to be the most popular. They are the closest you can get to run Android app natively on a non-Android Linux kernel. They tend to be the best integrated with your system and have good performance. Notable ones are:
- Anbox is probably the most famous android container solution for Linux. It runs an Android 7.1 image based on Lineageos and is completely open source.
- Waydroid is a fork of Anbox, and it is gaining popularity. It is more performant, because it runs closer to the hardware. It is based on a newer Lineageos 17.1 (Android 10) based image with the option to install the Google Play Store and other Open Gapps. Beside running apps in standalone windows, it can also run a full Android UI.
- There are also a few Chromium extensions that can run android apps:
- Arc Welder was an extension by google to test how apps would run on Chrome OS, but is now discontinued.
- ARChon is an open source extension to run android apps on Chromium-based browsers.
- Of course it is also possible to run a full android emulator. One upside to this is that you can run arm apps on x86. A downside is worse performance. Examples are:
- Android studio's built-in emulator, as earlier mentioned in this article.
- Genymotion is a pay for Android emulation/testing suite.
Android Studio: Android Virtual Devices show 'failed to load'.
Make sure you have exported the variable
ANDROID_HOME as explained in #Android Studio.
Android Studio: 'failed to create the SD card'
If you try to run an AVD (Android Virtual Device) under x86_64 Arch and get the error above, install the lib32-gcc-libs package from the multilib repository.
Eclipse: During Debugging "Source not found"
Most probably the debugger wants to step into the Java code. As the source code of Android does not come with the Android SDK, this leads to an error. The best solution is to use step filters to not jump into the Java source code. Step filters are not activated by default. To activate them: Window > Preferences > Java > Debug > Step Filtering. Consider to select them all. If appropriate you can add the android.* package. See Use Step Filters.
ValueError: unsupported pickle protocol
One fix is to issue:
$ rm ~/.repopickle_.gitconfig
If that does not work, then try this:
$ find /path/to/android-root -name .repopickle_config -delete
libGL error: failed to load driver: swrast OR AVD does not load and no error message displayed
Sometimes, beginning to load an AVD will cause an error message similar to this to be displayed, or the loading process will appear to finish but no AVD will load and no error message will be displayed.
The AVD loads an incorrect version of libstdc++, you can remove the folder libstdc++ from
~/.android-sdk/emulator/lib64 (for 64-bit) or
~/.android-sdk/emulator/lib (for 32-bit) , e.g.:
$ rm -r ~/.android-sdk/emulator/lib64/libstdc++
Note that in versions before Android Studio 3.0, this directory was in a different location:
$ rm -r ~/Android/Sdk/emulator/lib64/libstdc++
Alternatively you can set and export ANDROID_EMULATOR_USE_SYSTEM_LIBS in ~/.profile as:
Reference: Android Studio user guide
Fix for the .desktop file might be achieved by using env command, prefixing the Exec line Desktop entries#Modify environment variables
sh: glxinfo: command not found
Here is the full error:
Cannot launch AVD in emulator. Output: sh: glxinfo: command not found sh: glxinfo: command not found libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 24 (X_GLXCreateNewContext) Value in failed request: 0x0 Serial number of failed request: 32 Current serial number in output stream: 33 QObject::~QObject: Timers cannot be stopped from another thread
You can try to install glxinfo (mesa-utils) but if your computer has enough power you could simply use software to render graphics. To do so, go to Tools > Android > AVD Manager, edit the AVD (click the pencil icon), then select Software - GLES 2.0 for Emulated Performance > Graphics.
Android Emulator: no keyboard input in xfwm4
In xfwm4, the vertical toolbar buttons window that is on the right of the emulator takes focus from the emulator and consumes keyboard events. (bug report)
You can use the workaround described in :
- Open the xfwm4 settings.
- Switch to the Focus tab.
- Change the Focus Model to "Focus follow mouse".
- Disable Automatically raise windows when they receive focus option below.\
Android Emulator: Window is shaking and blinking when used in WM tiled mode
When using Tiled Window Manager like dwm, Android Emulator will shake and blink. You can use the workaround described in krohnkite issue 72 (window floating is induced by
Alt+f in dwm).
Android Emulator: Segmentation fault (core dumped)
When using Nouveau drivers try to disable gpu hardware acceleration.
In some devices it can only be done by editing
Android Emulator: Not launching / qemu-system: address resolution failed
There is an issue where no emulator-window shows up after starting a virtual device in android-studio. If this applies to you, launch the emulator from the console and inspect its output:
$ emulator -avd $(emulator -list-avds)
If on any line, it says anything similar to:
qemu-system-x86_64 : address resolution failed for ::1:46189: Name or service not known
you may try disabling IPv6:
$ sysctl net.ipv6.conf.all.disable_ipv6=1
If this solves the issue and the virtual device shows up in android-studio, you may consider a permanent change:
$ echo "net.ipv6.conf.all.disable_ipv6=1" | sudo tee -a /etc/sysctl.d/99-sysctl.conf
adb: sideload connection failed: insufficient permissions for device
If you get the errors:
adb: sideload connection failed: insufficient permissions for device See [https://developer.android.com/tools/device.html] for more information
adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: insufficient permissions for device See [https://developer.android.com/tools/device.html] for more information
You might be able to solve it by restarting the adb server:
$ adb kill-server # adb start-server
Alternatively, make sure you have installed the Android udev rules. See #Fastboot.