Android SDK Offline
One Stop Location to Download ALL Android SDKs for Offline installation
Android SDK Tools/Manager
Android SDK Tools/SDK Manager
WARNING.
Android SDK Tools is now marked as O.B.S.O.L.E.T.E. You still can use it in your project and your project still compile.However, you will NOT receive newer SDK packages from this Android SDK Tools when you use the sdkmanager utility.
As such we recommend you to move to CMDLine Tools from now on, unless you still have projects that rely on this package especially that are paired with 3rd party frameworks/tools.
Last Time Checked
All the packages were last checked on: 2021-12-05 | 1:18:44 AM
All the packages were taken directly from the official Google’s Android host.
| No | Package Name | API | Version | OS | Size (MB) |
|---|---|---|---|---|---|
| 1 | Android SDK Tools .zip ↓ | 26 | 26.1.1 | MACOSX | 98.25 MB |
| 2 | Android SDK Tools .zip ↓ | 26 | 26.1.1 | LINUX | 147.42 MB |
| 3 | Android SDK Tools .zip ↓ | 26 | 26.1.1 | WINDOWS | 148.9 MB |
How to install offline Android SDK Tools/SDK Manager ?
This package will ALWAYS be installed on the same path regardless of the newer versions available.
It CAN NOT be installed side-by-side with other versions and it’s install path DOES NOT follow Android API numbering scheme.
Upon updates, it overrides previous installation completely.
You can install ONLY ONE VERSION for this package installation.
The offline installation is done using Bash’s unzip that is widely avaialble on Windows (with WSL), Linux and Mac.However you can use whatever unzipping/decompressing/extracting tools you like that support extracting .zip, but please pay attention carefully so that the package is installed correctly and is recognized.We use Bash’s unzip for this purpose , respectively.
- Download the latest version of the packages available above.If it has different OSes, choose one that match your development OS.
- After finished, you can DISCONNECT any internet connections.
- Locate the downloaded .zip pacakge into accessible location, as you will need that location for installation purpose.
- Open up CLI/CMD, for Windows make sure you have WSL or Bash for Windows support.
- Now follow the steps below, it mimics CMD interface to make it easier for you:
- cd $ANDROID_SDK_ROOT
First, go to the root directory of Android SDK installation. On Windows you might also type: cd %ANDROID_SDK_ROOT%
Remember! You should only proceed to the next step if only you already in the root directory of Android SDK. - Now, from rootdir of Android SDK, locate the package you’ve downloaded and then extract the package based on your OS.
Make sure to change the /path/to/ with absolute path that points to actual downloaded package file location on your local disk.- [macosx Only]
rm -rf tools && unzip path/to/ sdk-tools-darwin-4333796.zip -d .
extract the package archive as-is from the root SDK directory, to install version 26.1.1 on macosx - [linux Only]
rm -rf tools && unzip path/to/ sdk-tools-linux-4333796.zip -d .
extract the package archive as-is from the root SDK directory, to install version 26.1.1 on linux - [windows Only]
rm -rf tools && unzip path/to/ sdk-tools-windows-4333796.zip -d .
extract the package archive as-is from the root SDK directory, to install version 26.1.1 on windows
- [macosx Only]
- DONE! 😀
Источник
Android sdk offline installer
A (Brief?) Introduction
In order to understand what this tool does, I highly recommend you read the following paragraphs. Don’t worry, they get more relevant as you approach the end.
Android SDK is, at its core, a plain old folder. Actually, it can can have any name, not necessarily ‘Android SDK’, ‘AndroidSDK’, or any other variant thereof. What distinguishes an SDK folder from a non-SDK one is the folder’s directory structure and contents: a folder can be an android sdk folder if it has (at the very least) a subfolder named ‘tools’. That folder must in turn, contain certain files to in order to be distinguished as an sdk folder by programs like Android Studio, but as far as the folder structure is concerned, having a sub-folder named ‘tools’ is all an folder needs look like a (bare-bone) sdk folder.
«Installing» an android sdk component consists of downloading a compressed archive (i.e, a .zip file, or a .tgz file, etc.), and extracting it to a relevant folder under the sdk folder’s root. the most common types of android sdk components are: system image, NDK, build tool, LLDB, and documentation.
«Updating» the sdk consists of downloading a number of certain XML files containing details (i.e., checksum, size and URL, etc.) of various android sdk components, and «installing» (cf. above) those you have chosen to.
But who is the one who does all the installing/updating stuff? Good questions. It is an executable file, to be found under /tools/ , and aptly named android . (Note: replace with the name you gave your android sdk folder.)
android is a rather versatile tool whose duties range from updating/installing android sdk to managing your android projects, and beyond. I will soon describe how to actually obtain this executable. But for now, let me tell about the problem that made me create offdroid.
As stated above, android (which is the SDK manager, among other things) is in charge of finding, downloading, and installing sdk components:
- «Finding» involves retrieving the list of sdk components from google’s servers.
- «Downloading» is downloading the components you select from the aforementioned list.
- «Installing» involves extracting the downloaded components under the sdk’s root folder, and possibly editing certain configuration files along the way.
Even though the sdk manager can do all the above tasks, it could be arguably slower in downloading the components, compar’d to a dedicated download manager. Wouldn’t it be great if we could somehow download the components ourselves, and «fed» them into the sdk manager, which would then install them for us?
Savvy android users might point out using the «cache» mechanism built into the sdk manager — copy all the downloaded components under the sdk’s ‘cache’ root (in linux, it is under
/.android/cache). Unfortunately, the sdk manager only supports caching files up to 640KB in size, and even then, the files to be cached must be renamed in a certain way before being put in the cache folder.
Offdroid’s solution is rather different.
The sdk manager downloads the things it needs from the internet, possibly through an http proxy. In case the previous sentence looks like a tautology to you, please read its last part again — «possibly through an http proxy«.
That’s the solution! Creating a localhost proxy that serves the content you have on your local disk, and fooling the sdk manager to connect to the «internet» through this local proxy.
Offdroid contains all the tools to set up such a localhost server. So let’s learn how to use it, which is what the next section is for.
Setup and Usage
** Offdroid works best on unix-like operatin systems; if you are using a non-unix-like operating system, you should install cygwin first. **
Offdroid makes extensive use of node.js; you must install it before being able to use offdroid. Offdroid also uses node-expat node package; assuming you have npm, you could install node-expat like so (if you haven’t already):
To use offdroid, you must first download it 😉 my favorite way to do so is:
Another way would be downloading the zip of the master branch, and extracting it to a folder of your choice.
Setting up the environment
After obtaining offdroid, you must set OFFDROID shell variable, and tweak the existing PATH variable as follows:
I would recommend you add the above lines to your .bashrc, otherwise you have to type them in each time you use offdroid.
NOTE 1: replace path/to/offdroid with the actual path to the folder offdroid resides in.
NOTE 2: the OFFDROID shell variable is crucial for offdroid to run properly; simply appending the PATH variable with the path to offdroid’s folder will not work.
The main, and indeed the only, command Offdroid has is the offdroid command. It is an umbrella command, like git and apt-get , exposing different functionality through various subcommands it provides. Below is the list of all subcommands offdroid provides, along with a description of what they do.
- offdroid init
- initialize an offdroid workspace. An offdroid workspace is the folder you run all other offdroid commands from, and is where all offdroid commands you issue read data from or write data to.
- offdroid fetch-xmls [through
]
- fetch the xmls containing sdk component descriptors, optionally through a proxy
- offdroid list-packages
- extract certain component details from the xmls obtained through offdroid fetch-xmls ; the content server later uses the output produced by this command to resolve url addresses to local file paths.
- offdroid latest-tool
- outputs the url(s) of the latest android ‘tools’ archive, the archive containing android executable; if you have decided to manually create an sdk (as opposed to downloading a pre-bundled archive) you will have to download the file this url points to, create a new folder, and extract this file under the folder you have created; the very folder you extracted the ‘tools’ archive in will be your sdk root folder; more about it on ‘A Note About the SDK’, below.
- offdroid set-sdk [FOLDER]
- set the sdk the current offdroid workspace is going to use
- offdroid add-source-folder [FOLDER]
- adds a new source-folder to the current offdroid workspace’s list of source folders. A source folder is a folder containing the sdk components you have downloaded.
- offdroid launch-manager
- launches the local server, and then the sdk manager. This is the command all other offdroid commands labor for.
A Note About the SDK
As you know, android is traditionally used to manage the sdk folder’s contents. But what is the sdk folder? and where can android be found? as described in the very beginning of this README, the sdk folder is a plain old folder, in which a ‘tools’ archive has been extracted. A ‘tools’ archive is itself a component of android sdk, in the form of a ‘zip’ archive; this archive is where the android executable resides. You could obtain the url for the latest ‘tools’ archive as simply as below:
This might output more than one url; you should choose the one whose prefix matches the name of your operating system.
After downloading the ‘tools’ archive, you should extract in a folder — preferably, a new folder. Congratulations! The very folder you extracted the ‘tools’ archive in is now a barebones but usable android sdk folder.
If you find the above process cumbersome (I didn’t), you coul well go to https://developer.android.com, and download the pre-bundled sdk folder suiting you operating system. Its name is like so: «android-sdk_r-.tgz». The archive contains the sdk root itself; extracting gives you an sdk folder out of the box.
A Complete Example
Below is an illustartion of how offdroid is actually used; it assumes no sdk folder has been set up yet.
- creating workspace folder:
- go into this workspace, and initialize it:
- fetch sdk component descriptors; I prefer to fetch them through the tor client I have running on my machine:
- use the component descriptors downloaded above to extract the hash and url of actual sdk components:
- find the url of the lastest ‘tools’ archive:
- fetch (download) the tools archive from the url you obtained in the previous stage, and extract the archive under a preferably-new folder
Now return to your offdroid workspace (if you are not already there); then:
- tell your workspace the path to the sdk-folder you want it to use; in my case, it is located under
/my-android-sdk, but your mileage might vary:
- run android from the tools folder under the sdk root; in my case, it is located under
In the sdk manager:
- go to Tools > Options
- Under ‘Proxy Settings’, set ‘HTTP Proxy Server’ to 127.0.0.1, and ‘HTTP Proxy Port’ to 8080
- uncheck ‘Use download cache’, as we must not use the cache
- check ‘Force https://. sources to be fetched using http://. ‘;
- exit the sdk manager
select the components you want to add to your sdk. this stage launches the actual manager; you select whatever you would like to install, and then follow the installation intructions as if you are actually installing the components you have chosen. when the «installation» is finished (it will actually take a few seconds, as all the downloads will fail immediately), close the sdk manager.
the urls for packages you had selected in the sdk manager are stor’d in .selected-packages in your offdroid workspace (i.e., in the current directory.)
- download the components you like (from the urls in .selected-packages or .all-urls ); I highly recommend you create a new folder and download the components there. after you are done downloading the components, return to the offdroid workspace (if you haven’t already), and add the path to the folder you have downloaded your components into to the workspace’s source list. (I downloaded my componnents of choice under
Источник
