Android repo for windows

Download Android Repositories for GitHub-700 + repositories PC for free at AppsPlayground. adarshgumashta published Android Repositories for GitHub-700 + repositories for Android operating system mobile devices, but it is possible to download and install Android Repositories for GitHub-700 + repositories for PC or Computer with operating systems such as Windows 7, 8, 8.1, 10 and Mac.

Let’s find out the prerequisites to install Android Repositories for GitHub-700 + repositories on Windows PC or MAC computer without much delay.

Select an Android emulator:  There are many free and paid Android emulators available for PC and MAC, few of the popular ones are Bluestacks, Andy OS, Nox, MeMu and there are more you can find from Google.

Compatibility:  Before downloading them take a look at the minimum system requirements to install the emulator on your PC.

For example,  BlueStacks requires OS: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista SP2, Windows XP SP3 (32-bit only), Mac OS Sierra(10.12), High Sierra (10.13) and Mojave(10.14), 2-4GB of RAM, 4GB of disk space for storing Android apps/games, updated graphics drivers.

Finally, download and install the emulator which will work well with your PC’s hardware/software.

How to Download and Install Android Repositories for GitHub-700 + repositories for PC or MAC:

• Open the emulator software from the start menu or desktop shortcut in your PC.
• Associate or set up your Google account with the emulator.
• You can either install the app from Google PlayStore inside the emulator or download Android Repositories for GitHub-700 + repositories APK file and open the APK file with the emulator or drag the file into the emulator window to install Android Repositories for GitHub-700 + repositories for PC.

You can follow above instructions to install Android Repositories for GitHub-700 + repositories for PC with any of the Android emulators available.

Download Android Repositories for GitHub-700 + repositories

Last Updated :
20 Jul, 2022

Git is created by Linus Torvald. Git is the most popular Version Control System in the world, used by millions of developers. It helps us to keep track of all the files in a project. Git tracks every change that are made. If we make a mistake, it can reset a file to match a previous version or we can also reset the version of all the project files at the same time. The collection of all versions of the project files is known as a Git Repository. It’s basically a folder in which we can edit our files and then run Git commands to store the changes made and pull in changes from other contributors. We can have multiple Git repositories on our computer one for each project we are working on. 

Why Git?

• Free
• Open Source
• Super Fast
• Scalable
• Cheap Branching/Merging

Android Studio

Android Studio is the official IDE (Integrated Development Environment) for Android app development. It is based on JetBrains’ IntelliJ IDEA. 

Installing Git in Android Studio

To get started we have to install Git which can be downloaded from the official website git-scm.com/downloads. 

Step 1: On the download, section select the operating system that we are working on. (As I am working on Windows so, I am going to select Windows)

Картинка с сайта: www.geeksforgeeks.org

And the download should begin automatically.

Картинка с сайта: www.geeksforgeeks.org

Step 2: Once the download is done we are going to run the executable and then hit «Yes» and then click «Next».

Картинка с сайта: www.geeksforgeeks.org

Now, setting up the path is a very important process. It is highly recommended to keep it as the default path because Android Studio can auto-detect Git.

Картинка с сайта: www.geeksforgeeks.org

Then keep on hitting next by keeping everything as default. And then finally we have to click install.

Картинка с сайта: www.geeksforgeeks.org

And then click on finish, and Git should be installed on the computer.

Картинка с сайта: www.geeksforgeeks.org

Step 3: Now let’s check on Android Studio whether it auto detects where Git was downloaded. So, to do this we are going to click on «File» and then on «Settings».

Картинка с сайта: www.geeksforgeeks.org

Now, in Settings, we are going to click on «Version Control» and then «Git», and in the top portion, it is said that «Auto Detected» is the path where the Git executable file is, and on clicking on «Test» the Git Version which is installed is shown.

Картинка с сайта: www.geeksforgeeks.org

Step 4: To install Git in Android Studio, we have to build a repository on GitHub first.

Картинка с сайта: www.geeksforgeeks.org

Step 5: Now coming back to Android Studio, click on «VCS» (Version Control Systems) and then click on «Enable Version Control Integration». 

Картинка с сайта: www.geeksforgeeks.org

Step 6: Then on selecting a version control, click «Git» and then «Ok».

Картинка с сайта: www.geeksforgeeks.org

Step 7: Now, it is shown that a Git repository is created.

Картинка с сайта: www.geeksforgeeks.org

Don’t worry if all the files turn red. It is because we haven’t uploaded those files to GitHub yet.

Step 8: In the next step, now coming over to the far left instead of having «Android» we are going to choose «Project».

Картинка с сайта: www.geeksforgeeks.org

And then we are going to right-click on the first folder coming down to Git and then we are going to add those files.

Картинка с сайта: www.geeksforgeeks.org

So, it’s going to add them all to our Version Control System.

Картинка с сайта: www.geeksforgeeks.org

And then, all of the files should turn green.

Картинка с сайта: www.geeksforgeeks.org

Step 9: Coming over to Git and then clicking on «Commit».

Картинка с сайта: www.geeksforgeeks.org

It will ask us to add a comment to it and then click on «Commit».

Картинка с сайта: www.geeksforgeeks.org

Do not worry about the warnings that are shown. Only the code should not contain any errors, and thus, Git is installed in Android Studio, and also we learned how to commit the files using Git from Android Studio. Now, if we want, then, we can «Push» the files to the GitHub

Step 10: Come over to Git and then click on «Push».

Картинка с сайта: www.geeksforgeeks.org

Now, we need to «Define remote» which is actually the repository to which we are uploading to, and then we need to copy and paste the URL of the repository and then click «Ok».

Картинка с сайта: www.geeksforgeeks.org

We are shown a list of files that were added to the repository. Now, all we have to do is click «Push».

Картинка с сайта: www.geeksforgeeks.org

Thus, we have uploaded a project to GitHub.

Картинка с сайта: www.geeksforgeeks.org

Overview

The source code for Android is available at https://android.googlesource.com.

It’s important to note that the open source project for Android consists of multiple Git repositories. While each Git repo can be cloned separately, Google provides a special repo script to help retrieve all of them. This script also helps automate the process of submitting pull request changes to the repository, so you
will need to use this tool for any code changes.

While downloading and building the entire tree requires at least 100GB and usually relies on building on
certain machines according to the official docs, you
can also build portions of the repo without needing this much disk space. One downside however is that
initially downloading the Git data from all the repos still takes at least 1-3 hours.

Building Android Tools

This walkthrough shows an example of how you can build the Android Tools repository. It is intended to show how you can contribute back to any part of the Android open source code, such as the components that work with Android Studio, the native emulator, the 9-patch viewer, etc. It also will show you how to setup with a Java IDE to be able to set breakpoints and understand the code better.

Preliminary Setup

See the instructions to make sure you have installed all the necessary libraries. You will need at least JDK 7 installed. There isn’t much setup work needed for OS X, but follow the apt-get install commands if running Ubuntu-based machines. If you are using Ubuntu 15.04 machines, you may need to run these commands at the minimum to get the Tools repository to compile:

sudo apt-get install libc6-dev-i386 lib32z1
sudo ln -s /usr/lib32/libstdc++.so.6 /usr/lib32/libstdc++.so

Download the IntelliJ IDEA Community Edition IDE. You will be able to use this IDE to compile and troubleshoot any of the Java-based tools.

Install the Repo client

The first step necessary is to download the repo client, which helps manage all the various Android repos.

Create a ~/bin directory

You will need to download and store the repo script somewhere. The official docs recommend storing the program
in a ~/bin directory accessible through the PATH environment variable.

$ mkdir ~/bin
$ PATH=~/bin:$PATH

Downloading the repo client

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Downloading the source code

Use the repo client to download the latest branch:

$ mkdir studio-1.4-dev
$ cd studio-1.4-dev
$ repo init -u https://android.googlesource.com/platform/manifest -b studio-1.4-dev
$ repo sync

When the repo init command is run, it will first download code from its own repository. It uses the manifest repository to determine what Android repositories are available. You can type repo help or check out the sub commands to see what functions are supported.

The overview page lists all the available branches to use. Most likely you should pick the current development branch. Android Studio and Gradle versions are often released at different times, so there are also separate Git tags created. For instance, if you wish to check out tagged releases for Gradle releases, you can also look through the list of tagged branches and use repo to switch to this branch by typing:

repo init -b gradle_1.3.1
repo sync

The repo sync script will refetch any changes. If you have made any changes in this repo, you may need to do the equivalent of resetting your changes across all Android repositories before attempting to run the sync command.

repo forall -vc "git reset --hard"

After running repo, you should have a tools/ directory created. There should be many subdirectories under this directory such as base, emulator, and gradle too. Many of these directories are also separate Git repositories.

Editing the build.gradle

The current tools project requires Java 1.6 and prevents you from building unless Java v1.6 is used. Assuming you have downloaded the latest branch, you can edit the tools/build.gradle in this directory and change the requiredVersion check to match the version you are running. You can obviously set an environment variable to do the same as well.

task('checkJavaVersion') << {
    def jvmVersion = System.getProperty('java.version')
    def requiredVersion = System.getenv('JAVA_FOR_TESTS') ?: '1.6'
    if (!jvmVersion.startsWith(requiredVersion)) {
        throw new RuntimeException("Tools need to be compiled with Java $requiredVersion, you are using Java $jvmVersion.")
    }
}

This pull request is intended to modify the behavior to allow any version of Java v1.6 to run.

Updating gradle.properties

You should have a tools/gradle/wrapper/gradle.properties already created as well. Currently this file assumes that
you have Gradle stored in a external/gradle directory. You can change the distributionUrl reference to point to a remote URL, which will be fetched if it doesn’t currently exist:

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-2.2.1-all.zip

If you forget this step, IntellIJ will likely complain about not having a Gradle Home setup.

Changing the output directory

Normally the Tools project will try to store all the intermediate builds inside a common build/ directory in the main repo. There is a current issue with IntelliJ v13.1 and up that prevents you from doing so.

If you see «Can’t register given path of type ‘SOURCE’ because it’s out of content root», you will need to change
the project.buildDir as shown:

subprojects { Project project ->
    // Change buildDir first so that all plugins pick up the new value.
    //  project.buildDir = project.file("$project.parent.buildDir/../$project.name/build")
    project.buildDir = project.file("build")
}

Opening with a Java IDE

You should now be able to open the tools/build.gradle file. Import the project and make sure that the Gradle wrapper option is selected. You should be able to build the project successfully.

You can find any of the tests, right click on the file, and click on the Debug option..

Experimenting with changes

Click on the Gradle icon on the right side of the screen and find the publishLocal option by going to tools->Tasks->other->publishLocal. Click on it to save it to an /out/repo directory that will be used in the next step.

You can also type the same command at the command-line:

./gradlew publishLocal

If you wish to experiment with the changes made with this new package, you can simply modify your app/build.gradle. You would add an extra maven reference to the out/repo directory created. Assuming you were experimenting on the gradle:1.4.0-beta branch, your configuration would look like the following:

buildscript {
    repositories {
        jcenter()
        maven { url '/home/johndoe/projects/android/out/repo/' }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.4.0-beta'

Submitting changes

You must first start a branch using the repo command:

repo start <branch_name> <project_name>

The project name can be determined by looking through the manifest file. For instance, the Tools project has multiple project names: platform/tools/base, platform/tools/build, platform/tools/emulator, etc.

The branch name can refer to any name you wish. It is a name that you will create locally and should refer to the set of changes for a particular improvement or feature change.

Once you’ve started a branch, you can go into the individual repositories and use Git as you normally would to add, revise, and commit changes. To create a pull request, you can type repo upload. If you revise any changes, you would use the same command too.

See the Google guide for submitting patches.

References

• https://source.android.com/source/using-repo.html
• https://source.android.com/source/developing.html
• http://tools.android.com/overview

Решил поделиться своей инструкцией как собрать AOSP (Android Open Source Project). Эта инструкция будет полезна тем кто хочет посмотреть что-же внутри Android и возможно заняться системной разработкой. В любом случаи эти знания полезны для понимания самого Android, как раз для этого и решил собрать AOSP.

Проект собираю на elementary 5.1 OS Ubuntu 18.04 LTS (bionic), пытался на MacOS собрать, но так и не удалось. Для исходников и сборки нужно 200 Гб на жестком диске (лучше SSD, на обычном производительность сильно проседает). Так же много времени, я потратил чтобы скачать и собрать около 20 часов, частично виновата «слабая» конфигурация моего компьютера. У меня установлено всего 8 Гб оперативной памяти, но увеличил размер swap-а до 16 Гб.

Загружаем AOSP

Установить требуемые пакеты для загрузки и сборки :

sudo apt-get install git-core gnupg flex bison build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev libgl1-mesa-dev libxml2-utils xsltproc unzip fontconfig

Создаем папку и качаем repo утилиту для загрузки исходного кода

mkdir aosp # имя папки можно выбрать любое
cd aosp

curl https://storage.googleapis.com/git-repo-downloads/repo > repo
chmod a+x repo

Исходники AOSP состоят из отдельных проектов с собственными git-репозиториями, repo позволяет упросить всю загрузку всех проектов и разложить по нужным папкам.

Инициализируем repo

./repo init -b android-10.0.0_r45 --depth 1 -u https://android.googlesource.com/platform/manifest

Параметры:

• -u — урл git-репозитория с манифестом
• -b — ветка (самая последняя на текущий момент)
• —depth — скачивать только одну ветку (если не использовать, то для каждого репозитория скачается весь индекс, что увеличит время загрузки и место на диске)

Выбрал самую последнюю версию Android 10. Не использую develop или master, так как там устаревший манифест и проект скорее не соберется.

Теперь можно запустить загрузку исходников AOSP

./repo sync -c  -j $(nproc) --no-tags --no-clone-bundle

Параметры:

• -c — скачивать только текущую ветку манифеста (как указал выше — android-10.0.0_r45)
• -j — количество потоков, обычно указывается столько доступно процессоров
• —no-tags — не скачивать тэги с репозитариев
• —no-clone-bundle — не пытаться качать clone.bundle (упакованная репа, которая уменьшить время на загрузку, но не у всех сервер формирует этот bundle),

—no-clone-bundle можно попробовать убрать, что в теории ускорит скачивание, но у меня заваливается с 404 ошибкой

Скачивание может занять минуты и часы, теперь с repo закончили, если нужно почитать больше то ищите в официальной документации: https://source.android.com/setup/develop/repo

Сборка

Настраиваем среду разработчика:

source build/envsetup.sh

конфигурируем сборку

lunch aosp_x86_64-eng

x86_64 — указывается под какой девайс собирать, в данном случае Generic x86_64 подходит для эмуляторов, если будете запускать на Nexus девайсах, то ищите детали в документации https://source.android.com/setup/build/building#choose-a-target

eng — тип сборки (сокращение от engineering), с максимальными логами и дополнительными утилитами для отладки. Другие тип сборки думаю не особо интересны

Для сборки java файлов увеличиваем Heap size, если этого не сделать, то сборка всего завалится с StackOverflow ошибкой:

export _JAVA_OPTIONS="-Xmx4g"

Так же можно добавить в .bashrc чтобы постоянно не повторять команду

Все, теперь готовы к сборке:

USE_CCACHE=1 CCACHE_DIR=ccache make -j $(nproc)

Можно не использовать CCACHE, что уменьшит количество занимаемого места на диске, но увеличит время повторной сборки. На моем «слабом» компьютере сборка заняла где-то 16 часов.

После окончания сборки, запускаем эмулятор:

emulator -show-kernel

-show-kernel — выводить уведомления в консоль

Если нажать Enter, то попадем в консоль эмулятора

Если эмулятор не запустился, нужно будет проверить что включена виртуализация

Картинка с сайта: habr.com

Готовим IDE для отладки

Для начала необходимо сгенериовать проект для IDE, проект генерируется для IDEA. Собираем модули для генератора:

mmm development/tools/idegen

Чтобы весь AOSP затолкать в проект, то просто запускаем генератор

development/tools/idegen/idegen.sh

Но сгенерированный IDEA проект будет очень «тяжелым». Одно открытие и индексация занимает достаточно много времени. Лучше генерировать IDEA проект для каждого отдельного проекта, например для Android фреймворка

development/tools/idegen/intellij-gen.sh frameworks/base

Весь список доступных проектов можно посмотреть в

cat .repo/project.list

Открываем сгенерированный base.iml (находится в папке frameworks/base) в IDEA. Дальше нужно настроить Java, только нужно подключать java без библиотек, так как у AOSP-а свои реализации.

Картинка с сайта: habr.com

Запускаем отладку

Для начала необходимо запустить monitor

 ~/Android/Sdk/tools/lib/monitor-x86_64/monitor

возможно потребуется дополнительно поставить jre
sudo apt install openjdk-8-jre-headless

Выбираем процесс, который будем отлаживать. В monitor-е выбираем процесс и справа от порта процесса появится /8700, это как раз порт отладчика, к нему можно подключаться через IDEA.
Все системные штуки находятся в system_process. Его мы и будем отлаживать.

monitor один самых полезных инструментов при отладке и исследования работы AOSP

Картинка с сайта: habr.com

В проекте добавляем новую Remote конфигурацию, только указываем 8700 порт. Именно к этому порту и будем подключаться

Картинка с сайта: habr.com

Запускаем Debug (Run → Debug)

Чтобы удостоверится, что все подключилось поставьте брейкпоинт в frameworks/base/services/core/java/com/android/server/wm/ActivityTaskManagerService.java файле на метод:

// line 1040
int startActivityAsUser(IApplicationThread caller, String callingPackage,
            Intent intent, String resolvedType, IBinder resultTo, String resultWho, int requestCode,
            int startFlags, ProfilerInfo profilerInfo, Bundle bOptions, int userId,
            boolean validateIncomingUser) {
//...
}

и запустить любое приложение на эмуляторе (например, Settings).

Теперь все готово для экспериментов.