Downloading android source code

Get Android Source Code

This document describes how to set up your local work environment, how to use Repo to get the Android files, and how to build the files on your machine.

Related reading:

• For an overview of the entire code-review and code-update process, see Life of a Patch.
• For reference details about Repo, see Using Repo and Git.

What’s in the source?

To see snapshots and histories of the files available in the public Android repositories, visit the GitWeb web interface.

The source is approximately 2.6GB in size. You will need 6GB free to complete the build.

Setting up your machine

To build the Android source files, you will need to use Linux or Mac OS. Building under Windows is not currently supported.

Linux

The Android build is routinely tested in house on recent versions of Ubuntu (10.04 and later), but most distributions should have the required build tools available. Reports of successes or failures on other distributions are welcome.

In general you will need:

• Python 2.4, which you can download from python.org.
• JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older. You can download either from java.sun.com.
• Git 1.5.4 or newer. You can find it at http://git.or.cz/.

Ubuntu Linux (64-bit)

The Sun JDK is no longer in Ubuntu’s main package repository. In order to download it, you need to add the appropriate repository and indicate to the system which JDK should be used.

Java 6: for Gingerbread and newer

Java 5: for Froyo and older

To set up your development environment, install the following required packages:

You might also want Valgrind, a tool that will help you find memory leaks, stack corruption, array bounds overflows, etc.

Running Linux in a virtual machine

Mac OS X

To build the Android files in a Mac OS environment, you need an Intel/x86 machine running MacOS 10.4 (Tiger), 10.5 (Leopard), or 10.6 (Snow Leopard). The Android build system and tools do not support the obsolete PowerPC architecture.

Android must be built on a case-sensitive file system because the sources contain files that differ only in case. We recommend that you build Android on a partition that has been formatted with the journaled file system HFS+. HFS+ is required to successfully build Mac OS applications such as the Android Emulator for OS X.

Creating a case sensitive disk image

If you want to avoid partitioning/formatting your hard drive, you can use a case-sensitive disk image instead. To create the image, launch Disk Utility and select «New Image». A size of 8 GB is sufficient, or more if you prefer. Be sure to select «case sensitive, journaled» as the volume format.

This will create a .dmg file which, once mounted, acts as a drive with the required formatting for Android development. For a disk image named «android.dmg» stored in your home directory, you can add the following to your

/.bash_profile to mount the image when you execute «mountAndroid»:

To set up your Mac OS development environment, follow these steps:

1. Install XCode from http://developer.apple.com. We recommend version 3.0 or newer. If you are not already registered as an Apple developer, you will have to create an Apple ID in order to download.
2. Install MacPorts from http://www.macports.org/.
3. Make sure that /opt/local/bin appears in your path BEFORE /usr/bin. If not, add

/.bash_profile.
Get make, git, and GPG packages from port:

Edit /opt/local/etc/macports/sources.conf and a line that says

Installing Repo

Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see Using Repo and Git.

To install, initialize, and configure Repo, follow these steps:

Make sure you have a bin/ directory in your home directory, and that it is included in your path:

/bin/repo
$ chmod a+x

Initializing a Repo client

After installing Repo, set up your client to access the android source repository:

Create an empty directory to hold your working files:

Getting the files

To pull down files to your working directory from the repositories as specified in the default manifest, run

The Android source files will be located in your working directory under their project names.

Verifying Git Tags

Load the following public key into your GnuPG key database. The key is used to sign annotated tags that represent releases.

——BEGIN PGP PUBLIC KEY BLOCK——
Version: GnuPG v1.4.2.2 (GNU/Linux)

mQGiBEnnWD4RBACt9/h4v9xnnGDou13y3dvOx6/t43LPPIxeJ8eX9WB+8LLuROSV
lFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw7
8tR1cXb197Ob8kOfQB3A9yk2XZ4ei4ZC3i6wVdqHLRxABdncwu5hOF9KXwCgkxMD
u4PVgChaAJzTYJ1EG+UYBIUEAJmfearb0qRAN7dEoff0FeXsEaUA6U90sEoVks0Z
wNj96SA8BL+a1OoEUUfpMhiHyLuQSftxisJxTh+2QclzDviDyaTrkANjdYY7p2cq
/HMdOY7LJlHaqtXmZxXjjtw5Uc2QG8UY8aziU3IE9nTjSwCXeJnuyvoizl9/I1S5
jU5SA/9WwIps4SC84ielIXiGWEqq6i6/sk4I9q1YemZF2XVVKnmI1F4iCMtNKsR4
MGSa1gA8s4iQbsKNWPgp7M3a51JCVCu6l/8zTpA+uUGapw4tWCp4o0dpIvDPBEa9
b/aF/ygcR8mh5hgUfpF9IpXdknOsbKCvM9lSSfRciETykZc4wrRCVGhlIEFuZHJv
aWQgT3BlbiBTb3VyY2UgUHJvamVjdCA8aW5pdGlhbC1jb250cmlidXRpb25AYW5k
cm9pZC5jb20+iGAEExECACAFAknnWD4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIX
gAAKCRDorT+BmrEOeNr+AJ42Xy6tEW7r3KzrJxnRX8mij9z8tgCdFfQYiHpYngkI
2t09Ed+9Bm4gmEO5Ag0ESedYRBAIAKVW1JcMBWvV/0Bo9WiByJ9WJ5swMN36/vAl
QN4mWRhfzDOk/Rosdb0csAO/l8Kz0gKQPOfObtyYjvI8JMC3rmi+LIvSUT9806Up
hisyEmmHv6U8gUb/xHLIanXGxwhYzjgeuAXVCsv+EvoPIHbY4L/KvP5x+oCJIDbk
C2b1TvVk9PryzmE4BPIQL/NtgR1oLWm/uWR9zRUFtBnE411aMAN3qnAHBBMZzKMX
LWBGWE0znfRrnczI5p49i2YZJAjyX1P2WzmScK49CV82dzLo71MnrF6fj+Udtb5+
OgTg7Cow+8PRaTkJEW5Y2JIZpnRUq0CYxAmHYX79EMKHDSThf/8AAwUIAJPWsB/M
pK+KMs/s3r6nJrnYLTfdZhtmQXimpoDMJg1zxmL8UfNUKiQZ6esoAWtDgpqt7Y7s
KZ8laHRARonte394hidZzM5nb6hQvpPjt2OlPRsyqVxw4c/KsjADtAuKW9/d8phb
N8bTyOJo856qg4oOEzKG9eeF7oaZTYBy33BTL0408sEBxiMior6b8LrZrAhkqDjA
vUXRwm/fFKgpsOysxC6xi553CxBUCH2omNV6Ka1LNMwzSp9ILz8jEGqmUtkBszwo
G1S8fXgE0Lq3cdDM/GJ4QXP/p6LiwNF99faDMTV3+2SAOGvytOX6KjKVzKOSsfJQ
hN0DlsIw8hqJc0WISQQYEQIACQUCSedYRAIbDAAKCRDorT+BmrEOeCUOAJ9qmR0l
EXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM=
=Wi5D
——END PGP PUBLIC KEY BLOCK——

Building the code

To build the files, run envsetup, lunch, and make from within your working directory:

/directory
$ source build/envsetup.sh
$ lunch
$ make

What’s next?

See Using Eclipse for instructions on how to use an IDE for Android platform development. To learn about reporting an issue and searching previously reported issues, see Report bugs. For information about editing the files and uploading changes to the code-review server, see Contribute.

Источник

Android
Open Source Project

Android unites the world. Use the open source Android operating system to power your device.

Interfaces and architecture

Android security is essential

Design compatible devices

About the Android Open Source Project

Android is an open source operating system for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android OS, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.

As an open source project, Android’s goal is to avoid any central point of failure in which one industry player can restrict or control the innovations of any other player. To that end, Android is a full, production-quality operating system for consumer products, complete with customizable source code that can be ported to nearly any device and public documentation that is available to everyone (in English at source.android.com and in Simplified Chinese at source.android.google.cn).

Just as you can contribute code to AOSP, you can also contribute to AOSP documentation—and we want your input! Android’s flexibility and ever-changing codebase means this site needs your feedback to keep content fresh, accurate, and relevant to Android implementors. We encourage you to check the changelog for details on recent AOSP updates and to report bugs or offer suggestions using the Site Feedback at the bottom of every page (or by visiting g.co/androidsourceissue).

Security and Update Bulletins

Every month, we publish the Android Security Bulletin along with the Android Automotive Bulletin and Pixel Update Bulletin.

Go to any of the following Android and Pixel Bulletins to see links to the fixes and new build numbers associated with the latest security release.

Источник

Guides

Download an Android project with source code and start using Back4App

Introduction

In this guide, you will learn how to get started with an Android application written in Java or Kotlin and connect it to Back4App.

If you want a detailed Quickstart guide or connect Back4App to an existing project, go to our Install Parse SDK tutorial

Download an Android Template and connect it to Back4App

Prerequisites

Step 1 — Download the template

There are 2 Android templates, one written in Java and the other on Kotlin:

Choose the template that suits you, and proceed to download or import your project on Android Studio. Android Studio.

Step 1.1 — Download Directly from GitHub

Use the following commands to download and unzip your project template:

Step 1.2 — Open the project on Android Studio

After downloading the files, unzip them. Let’s open Android Studio

In the welcoming screen of Android Studio, choose ‘Open an Existing Project’ and select the project’s folder.

Choose your downloaded and unzipped folder’s location and open it.

Please wait until the finish of the Gradle Run process. Now you can see Gradle console bottom tabs in Android Studio.

Step 1.3 — Import from GitHub(Optional Path)

You can import the repository link directly to Android Studio. On Android Studio welcoming screen, choose ‘Get from Version Control’

Android Studio will ask you for the Git repository link and the desired project path. You can find repository links at the start of this section.

You can find repository links in the start of this section

After filling the URL and Directory fields, click on the Clone button. Then Android Studio will copy and open the project for you. Please wait until the finish of the Gradle Run process. Now you can see Gradle console bottom tabs in Android Studio

Android Studio will copy and open project for you

Please wait until gradle run is finished.You can see gradle console bottom tabs in Android Studio

Step 2 — Get your App Keys

In this guide we will use following files in project :

AndroidManifest.xml — We will set our Back4App credentials as and app permissions
App.java ( App.kt for kotlin) — We will modify our initialization code in here
MainActivity.java ( MainActivity.kt for kotlin) — Will contain our very first code for creating a Parse Object
strings.xml — We will store and read Back4App setup credentails from here
build.gradle — We will set our Parse Android SDK version in here

In order to connect your App project to Back4App’s server, you’ll need three primary information the server URL, the Application ID, and the Client Key.
In an Android project, strings.xml is a perfect place to set this information. It is where Parse Android SDK reads Application key values to make a connection with your Back4App App.
The server URL is already on the project. You’‘ll need now go to Back4App, copy your App keys, and update your strings.xml with those values:

Open your strings file: . /app/src/main/res/values/strings.xml

Go to your App Dashboard at Back4App Website.

Find you keys on: App Settings > Security & Keys .

Return to your strings.xml file and paste your applicationId and clientKey .

Open your build.gradle (Module:Back4AppExample.app) file in Gradle Scripts from Project Explorer

In dependencies section change the Parse-SDK-Android value with version of your choice.

After saving build.gradle run ‘Sync Now’

You can see current version of SDK in here SDK Versions.

Step 3 — Connect to Back4App

After setting up your App credentials, you are ready to connect with your Parse Server instance on Back4App.

This is the initialization code you’re going to use:

You can reach initialization code in project in App.java ( App.kt for kotlin)

We are using App.java for our initialization because we need to establish connection before app takes any other action. App.java is the first Context to be created before any other Activity and Service and last to be destoryed.

Below initilization code gets App Keys from strings.xml and try to establish a connection with our Back4App server. We put our code onCreate() method because we want to connect to our server first before taking any other action.

_{app > java > com > back4app > java > example > App.java}

_{app > java > com > back4app > java > back4appexample > App.kt}

Now it is time to add some codes for interacting with the server. Let’s open our MainActivity file.

Activity files are great for interacting with user. They are main purpose providing a User Interface.

You can choose which activity to show in launch in AndroidManifest.xml

In our project MainActivity is set to open on launch.

In this code sample we have a Parse SDK code for saving a Parse Object to server and showing objectId of saved Parse Object to user with a TextView

_{app > java > com > back4app > java > example > MainActivity.java}

_{app > java > com > back4app > kotlin > back4appexample > MainActivity.kt}

Step 4 — Test the connection

1. Build your app in a device or virtual device ( Shift + F10 ).

If you don’t have any virutal device to run app. You can create a new one from AVD Manager in Android Studio

Wait until the Hello Word! screen appears. After Hello Word! you will see Object saved. Message this message will include saved object’s id.

Login at Back4App Website.

Find your app and click on Dashboard > Database > Browser .

If everything works properly, you should find a class named FirstClass as follows:

It’s done!

You can see objectId in dashboard and your app’s screen is matches !

At this point, you have learned how to get started with Android apps.

Источник