- Ubuntu Documentation
- Preparation and Installation
- Downloading the SDK Starter Package
- Setting up Java
- Downloading the SDK platform tools
- Post-Installation Configuration
- Modifying the PATH Environment Variable
- Preparing Hardware
- Arch Linux User Repository
- Search Criteria
- Package Details: android-sdk 26.1.1-1
- Package Actions
- Dependencies (22)
- Required by (55)
- Sources (5)
- Pinned Comments
- dreamingincode commented on 2020-03-11 07:51
- dreamingincode commented on 2017-04-18 11:40
- Latest Comments
- qualphey commented on 2020-10-23 11:35
- ulidtko commented on 2020-10-23 11:30
- qualphey commented on 2020-10-23 11:28
- relrel commented on 2020-08-23 19:19
- dreamingincode commented on 2020-06-01 18:26
- ulidtko commented on 2020-06-01 16:26
- dreamingincode commented on 2020-03-11 07:51
- Anonymous comment on 2020-03-10 17:54
- AndreVallestero commented on 2020-02-25 16:32
- AndreVallestero commented on 2020-02-25 16:28
Ubuntu Documentation
This is a general overview of what the Android SDK is, what it does, and how it can benefit you. This guide also contains instructions on how to set up the Android SDK on Ubuntu 10.04 onwards.
The Android Software Development Kit (AKA SDK) is a software suite for the Android mobile operating system that allows you to write applications for Android in the Java programming language. Most people who use the Android SDK either develop applications for the Android operating system OR they use it for other purposes, such as obtaining elevated privileges on an Android device with the help of third-party software or use it for diagnostic purposes in case of malfunctioning.
The vast majority of Android users probably won’t have to make use of the Android SDK, however, it is useful if you wish to learn more about the Android operating system and even then it’s still a handy tool to have in case something goes wrong.
This tutorial covers Ubuntu 10.04 Lucid Lynx onwards. For anything prior to Lucid, you will have to find it yourself.
Preparation and Installation
Before we set up the SDK, we have some preparation to do. Due to some major changes in the Android SDK made in the last couple of months, setting up the Android SDK is not as easy as it was two years ago, when Android was starting to take off. Setting up the SDK itself is relatively easy once the preparation has been done.
Downloading the SDK Starter Package
First things first, we have to obtain the starter package. The SDK starter package can be obtained at http://developer.android.com/sdk/index.html.
Download the one for Linux (.tgz file) and once it’s finished downloading, extract it to somewhere safe and easy to reach. For example, the home folder. To do so, open up a terminal, navigate to the directory where the SDK was downloaded and enter the following command:
$ tar -xvzf android-sdk_rXX-linux.tgz && mv android-sdk-linux
As of 12 May 2012, the Android SDK is currently up to r18, however that is set to change in the near future, and as such, replace XX with the version of your SDK.
Setting up Java
Prior to SDK r08, everything you’ll need to develop applications was included on a 100-200MB .tgz archive. However, with the release of SDK r08, the tools necessary for creating and building applications was removed and can be obtained by using the Android SDK and AVD Manager which is located in the / /tools folder.
However, you should not execute the Android SDK and AVD manager just yet, as you’ll most likely get a Parse: XML error notice. The reason for this is that after SDK r08, it’s now required to have Java installed before you set up the SDK. To do this, we’ll download the OpenJDK and the Icedtea browser plugin. In a terminal window, enter the following command:
$ sudo apt-get install openjdk-6-jre openjdk-6-jdk icedtea6-plugin
This will download and install the OpenJDK implementation of Java, which will be sufficient enough for us to download the SDK platform tools.
Downloading the SDK platform tools
This is pretty much the actual «installation» of the SDK’s platform tools. One key reason why this step is important is that it contains an important protocol called the Android Debug Bridge (ADB).
ADB comes bundled with the SDK platform tools. It is a command-line tool used to communicate with and control the device over a USB link from a computer. The tool comes bundled with the Android SDK and is commonly used for diagnosing problems with the device. Once you have ADB installed, you can use ADB to copy files to and from the device’s internal memory, install apps, run commands, see logs and more. This makes it an invaluable tool if your device is running into some trouble that might warrant a new device.
Now, in order to obtain the SDK platform tools, we’ll need to initialize the Android SDK and AVD Manager that I mentioned earlier. To do so, enter the following commands in a terminal. The first command will direct you to where the Android SDK and AVD Manager is located, and the second will execute said program.
/android-sdk-linux/tools
Once you do that, a new window will pop up, which is the actual Android SDK and AVD Manager. Click on «Available Packages» and you will be presented with two boxes. One is the Android Repository and the other is the Third-party Add-ons. Click on «Android Repository» then click on Install Selected. A confirmation window will pop up. Click on «Accept All» and then click on the Install button to install the SDK platform tools. It’s quite a bit to download so make sure you have at least 512MB to 2GB of hard drive space available. Once the download has finished, you’ll get a notice saying that the ADB daemon needs to be restarted. Click on «Yes» and everything will finish downloading.
Post-Installation Configuration
Now once the download has finished, or while you’re waiting for the download to finish, we have to configure Ubuntu a little to meet our needs. First, we have to set up the PATH variable to include ADB and other SDK tools, and we have to make sure our hardware will be detected once we initialize ADB.
Modifying the PATH Environment Variable
In the days before Android 2.2, a good number of people used to place their various projects and applications in the directories where the necessary tools they used existed. This was in itself a very flawed method because it cluttered up the directories, and while cleaning up the SDK, one might accidentally delete a crucial file, which will cause the SDK to fail and having to completely reinstall everything.
Modifying the PATH Environment Variable will help out immensely when it comes down to making use of SDK tools like ADB. Doing this will also allow you to execute certain protocols like ADB from ANY location. So if you’re operating from the Desktop, you don’t have to redirect to the SDK’s platform-tools folder to make use of ADB if you need to make use of it.
Enough chatter, let’s get busy. To modify the PATH variable of your system, you need to edit your .bashrc file. To do so, in a terminal, execute the following command:
You will now have the Nano text editor enabled on the terminal. Now, at the very top of the file, enter the following:
/android-sdk-linux/tools
/android-sdk-linux/platform-tools
Once you’re finished, press CTRL + X, Y, and then hit Enter to save your changes and exit the Nano text editor.
Preparing Hardware
Now that we have our PATH variable set up, we need to make sure our hardware will be detected once we initialize ADB. However, up until Natty, udev in Ubuntu wouldn’t allow ADB access to the Android phone via USB. This was fixed in udev version 165-0ubuntu1 — if you are running an earlier version ( apt-cache policy udev will tell you whether you are), you’ll need need to create a new udev rule file as root.
In a terminal, execute the following command that will create the rule file. This will utilize the graphical sudo command, so that we can still have control over the file if we’re not a root user.
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Copy and paste the following udev rules in the text editor that opened up which contains the new rule file we created. The rules included should work with most if not all Android devices across multiple manufacturers, such as HTC, Motorola, LGE, and so forth.
SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS SUBSYSTEM==»usb», ATTRS Once you’ve copied and pasted the udev rules in the text editor which contains your newly created rule file, save your changes and quit. Now that you’ve set your udev rules you have to reboot so that ADB will be in your path. To test your changes, open up a terminal and execute the following: $ adb devices Note: You may need to enable USB debugging mode on your phone first in order for it to be recognised. This will give you two messages: 1) It will tell you it’s initializing the ADB daemon. 2) It should show you a list of connected devices. If all went well you should see your device’s serial number under the list of connected devices. If you see a message like: List of connected devices . No permissions This means your hardware was detected, however you made a mistake in configuring Ubuntu or the udev rule for your phone’s manufacturer was not listed. AndroidSDK (последним исправлял пользователь uusijani 2012-07-28 15:47:15) The material on this wiki is available under a free license, see Copyright / License for details Источник cmdline-tools should be a different package because it’s installed at android-sdk/cmdline-tools/latest, not android-sdk/tools of this package. They show up as different packages in Android Studio SDK manager as well, and they can be installed side-by-side. I’m going to update this package to 26.0.1 (it has been long-outdated), according to https://dl.google.com/android/repository/repository2-1.xml which is used by Android Studio. Some tools have been removed by upstream in this update (namely the standalone SDK Manager’s GUI), and you may want to check against https://developer.android.com/studio/releases/sdk-tools.html for the breaking changes before this update. If you are using an AUR helper and you want to stay on the old version, consult your AUR helper’s manual. @ulidtko Ah yes, that worked. Thank you! My bad. 😛 @qualphey as you can see from pacman -Ql android-sdk , it installs its tools under /opt/android-sdk/tools/bin — so you have to ensure that dir appears on your $PATH. Does the sdkmanager get installed with this package? I get bash: sdkmanager: command not found when trying to run it? What am I missing? @ulidtko @dreamingincode After encountering the same issue, running the following worked for me: It uses Android Studio’s built-in java instead of the globally installed one. I haven’t dig to the root cause (probably java versioning issue), but I think this issue should be resolved appropriately in the sdkmanager shell wrapper. @ulidtko I would suggest selecting an older default Java version with archlinux-java . With java-11-openjdk x86_64 the tools from android-sdk fail for me, like so: $ sdkmanager —list Exception in thread «main» java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema at com.android.repository.api.SchemaModule$SchemaModuleVersion. (SchemaModule.java:156) at com.android.repository.api.SchemaModule. (SchemaModule.java:75) at com.android.sdklib.repository.AndroidSdkHandler. (AndroidSdkHandler.java:81) at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73) at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48) Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) . 5 more From half a day of research (I’m not really into java), I understand that the JAXB apis, including the package javax.xml.bind, have been deprecated in Java 9 & 10, and dropped altogether from JDK 11. Okay, that’s fine. But how to fix it. Everyone online is quick to suggest adding jakarta.xml.bind dependency to my Maven/Gradle/SBT build. But with aur/android-sdk, I don’t have such thing. My attempts to —add-modules to the systemwide java were not successful. @dreamingincode are you aware of this problem? I don’t remember making any java-related customizations on this machine; and as-is, this package seems completely broken here. cmdline-tools should be a different package because it’s installed at android-sdk/cmdline-tools/latest, not android-sdk/tools of this package. They show up as different packages in Android Studio SDK manager as well, and they can be installed side-by-side. @dreamingincode: This package could be updated to the new commandline tools. This is an alternative to the full android studio wit sdkmanager command line. I would like to do this. Please add support for aarch64. This can be simply done by adding ‘aarch64’ to the arch list and by replacing lib32 packages with their 64bit equivalents (gcc-libs, glibc). sdkmanager is intended to be used with jdk8 or lower. It can work with jdk9 and jdk10 with the following export: export JAVA_OPTS=’-XX:+IgnoreUnrecognizedVMOptions —add-modules java.se.ee’ It will NOT work with jdk11 or higher as java.se.ee is removed after jdk 10 Copyright © 2004-2021 aurweb Development Team. AUR packages are user produced content. Any use of the provided files is at your own risk. Источник
You can contribute to this wiki, see Wiki Guide for detailsArch Linux User Repository
Search Criteria
Package Details: android-sdk 26.1.1-1
Package Actions
Git Clone URL: https://aur.archlinux.org/android-sdk.git (read-only, click to copy) Package Base: android-sdk Description: Google Android SDK Upstream URL: https://developer.android.com/studio/releases/sdk-tools.html Keywords: android development Licenses: custom Submitter: None Maintainer: dreamingincode Last Packager: dreamingincode Votes: 1473 Popularity: 1.77 First Submitted: 2007-11-12 19:26 Last Updated: 2020-09-30 12:40 Dependencies (22)
Required by (55)
Sources (5)
Pinned Comments
dreamingincode commented on 2020-03-11 07:51
dreamingincode commented on 2017-04-18 11:40
Latest Comments
qualphey commented on 2020-10-23 11:35
ulidtko commented on 2020-10-23 11:30
qualphey commented on 2020-10-23 11:28
relrel commented on 2020-08-23 19:19
dreamingincode commented on 2020-06-01 18:26
ulidtko commented on 2020-06-01 16:26
dreamingincode commented on 2020-03-11 07:51
Anonymous comment on 2020-03-10 17:54
AndreVallestero commented on 2020-02-25 16:32
AndreVallestero commented on 2020-02-25 16:28
