Replicant

h1. SDK

The [[ReplicantSDK]] page holds a list of the released Replicant SDK builds.

h2. Rationale

Up till version 4.2, Replicant provided its own SDK, built from source, since the Android SDK as released by Google is distributed under a non-free license and suggests installing non-free plug-ins such as the Google APIs.

The Replicant SDK contains only free software and will not check for plug-ins or updates from Google.

From Replicant 6.0 onward "there was no longer the need to provide a Replicant SDK":https://blog.replicant.us/2017/04/there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better/ because some fully-free GNU/Linux distributions already provide packages for the Android SDK.

| Distribution         | Status                                                                                          | Gradle version  | Android versions   |

| Debian  9 (stretch)  | Has android-sdk packages, probably complete[2]                                                  |                 |                    |

| Debian 10 (buster)   | Has android-sdk packages, probably complete[3]                                                  |                 |                    |

| Debian 11 (bullseye) | Has android-sdk packages, probably complete[4]                                                  |                 |                    |

| Parabola             | "Work in progress":https://www.parabola.nu/packages/?q=android-sdk [1] that has stalled in 2018 |                 |                    |

| Trisquel 7 (belenos) | Has android-sdk packages, probably complete[1]                                                  |                 |                    |

| Trisquel 8 (flidas)  | Has android-sdk packages, probably complete[1]                                                  |                 |                    |

| Trisquel 9 (etiona)  | Has android-sdk packages, probably complete[1]                                                  |                 |                    |

| Trisquel 10 (nabia)  | Has android-sdk packages, probably complete[1]                                                  | 4.4.1           | 6.0 (API Level 23) |

There is also the "Android Rebuilds":https://android-rebuilds.beuc.net/ project that provides a free Android SDK, built from the Android source code. So it probably works on most of the the GNU/Linux distributions that exist, however, at the time of writing, it is still relied on Google's prebuit toolchain (which is free software) to build the SDK.

fn1. The packages are based based on "android-sdk-meta":https://salsa.debian.org/android-tools-team/android-sdk-meta by the Debian project.

fn2. https://packages.debian.org/stretch/android-sdk

fn3. https://packages.debian.org/buster/android-sdk

fn4. https://packages.debian.org/bullseye/android-sdk

h2. Installation of the Replicant SDK

After downloading the Replicant SDK from the [[ReplicantSDK]] page, it should work the same as the Android SDK as provided by Google except that the Replicant SDK already contains a built and ready to use emulator image. 

Please refer to: http://developer.android.com/sdk/installing/index.html for further assistance. 

h3. Dependencies

h4. Required Packages

The Replicant SDK requires the following packages:

* SDL

* OpenJDK 6

* Ant

In some unlikely cases, creating a "JAVA_HOME" environment variable and pointing it to your JDK's true install location (not the "bin" directory but one level upward) may prove necessary.

h5. Additional requirements for amd64

Note that the Replicant SDK is built for x86 platforms and you may need compatibility libraries such as @ia32-libs@.

h4. Command line installation

h5. Trisquel/Ubuntu/Debian

Required packages:

<pre>

apt-get install libsdl1.2debian openjdk-6-jdk ant

</pre>

Additional requirements for amd64:

<pre>

apt-get install ia32-libs

</pre>

h2. Rebuilding the SDK from sources

See [[SDKBuild]].

h2. Usage guides

h3. Using Eclipse

You may want to install Eclipse to work on Android Java applications. Note that this is not strictly necessary as all the required tools are already present on the SDK package. 

h4.  Installing the "Android Development Tools" plugin for Eclipse

The following instructions work with Eclipse 3.7.2 (Indigo) as installed via Apt under Trisquel Toutatis GNU/Linux.

<pre>

sudo aptitude install eclipse

</pre>

Once you have Eclipse installed and running properly, you may want to install the Android Development Tools plugin.

* The Replicant 4.0 SDK requires ADT version 16 while the Replicant 4.2 SDK requires ADT version 20. You will need to download it from Google's archives and then manually install it in Eclipse:

http://dl.google.com/android/ADT-16.0.0.zip

http://dl.google.com/android/ADT-20.0.0.zip

* in Eclipse 3.7

- select "Window" > "Preferences" > "Install/Update" > "Available Software Sites"

- click the "Add" button

- name your software site something recognizable, e.g. "ADT"

- click "Archive" and select the ADT zip file

* in Eclipse 3.7

- select "Help" > "Install New Software"

- select the "ADT"/ software site from the dropdown menu

- select the "Developer Tools" software package

- verify that the "Android DDMS" and "Android Development Tools" sub-packages were selected

- click the "Next" to install Android Developer Tools

* restart Eclipse

h4. Pointing "Android Development Tools" to the SDK directory

When you have installed ADT and restarted Eclipse, select the "Window" menu. You should see a menu entry named "Android SDK and AVD Manager". Then select "Preferences" from the "Window" menu. A menu item named "Android" should be available on the left panel.

Once the "Android" menu item is available in the "Window" > "Preferences" dialog, select it. In the main panel, click the "Browse" button for the "SDK Location" field, and point it to the directory where you unzipped your Replicant 4.2 SDK. Then click "Apply" or "OK".

Next time you enter this dialog, a line saying "Android 4.2.2 / Android Open Source Project / Platform: 4.2.2 / API level: 17" should be present in the list of SDK targets.

h3. Writing a "Hello World" app in Eclipse

h4. Creating an Android Virtual Device

To run your app in an emulator, you need to create an Android Virtual Device. In Eclipse, choose "Window" > "Android SDK and AVD Manager" > "Virtual Devices" > "New" and fill in the properties of the virtual device as follows:

- Name: something descriptive like "AVD_for_Nexus_S"

- Screen resolution of your physical device, e.g. "WVGA800" for Nexus S

- Target: choose "Android 4.2.2 - API level 17" from the dropdown menu

- SD Card: specify the size of an emulated SD card, alternatively browse for an existing SD card image

- leave other values at defaults and click "Create AVD"

- if your disk is slow and you specified a large SD card image for creation, it may take a few seconds to complete

h4. Creating a project

In Eclipse, choose "File" > "New" > "Project". In the tree of possible project types, a branch named "Android" should exist. Open it, select the project type "Android Application Project" and click "Next".

Enter a friendly name for your application, e.g. "Hello World", then a name for your project, e.g. "hello". Enter its package name, which can be either public (e.g. "com.example.hello") or private (e.g. "hello.test").

For "Configure", select "Create project in workspace" and use default location. The project will be created in your local Eclipse workspace directory, in a subdirectory corresponding to the project name. Leave the minimum SDK version as-is.

If you want the first piece of your application's user interface to be auto-created, leave the "Create Activity" checkbox checked and enter someting like "MainActivity" for the name of the "Activity" class to create.

Finally click "Finish" and your project should appear in Eclipse's left-hand projects tree.

h4. Adding some code and resources into a project

To have your application's MainActivity class do something, consider adding some code. For example, you might want your application to have a button which closes it. In this sample, we specify the design of user interface elements in a separate XML resource file, so don't be surprised when you don't see anything related to their design here:

<pre>package hello.test;

import android.app.Activity;

import android.os.Bundle;

import android.view.View;

import android.widget.Button;

public class MainActivity extends Activity {

    @Override

    public void onCreate(Bundle savedInstanceState) {

        super.onCreate(savedInstanceState);

        setContentView(R.layout.main);

        Button buttonFinish = (Button) findViewById(R.id.buttonFinish);

        buttonFinish.setOnClickListener(new View.OnClickListener() {

			@Override

			public void onClick(View v) {

				finish();

			}

		});

    }

}</pre>

You may notice how the constructor of MainActivity calls @setContentView(R.layout.main)@. In this statement, @R@ is a special resource class, pointing to resources hosted in the @res@ directory of your project. The @layout@ class limits the choice to layout resources hosted under the @res/layout@ while @main@ is the name of a layout resource file @main.xml@ located there.

We need to create this resource file now. I would recommend having it be like this:

<pre><?xml version="1.0" encoding="utf-8"?>

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"

    android:orientation="vertical"

    android:layout_width="fill_parent"

    android:layout_height="fill_parent"

    >

<TextView

    android:id="@+id/textInfo"

    android:layout_width="fill_parent" 

    android:layout_height="wrap_content" 

    android:text="Click button to close app."

    />

<Button android:id="@+id/buttonFinish"

    android:layout_width="wrap_content"

    android:layout_height="wrap_content"

    android:text="Close" />

</LinearLayout>

</pre>

Together, it makes sense. The "LinearLayout" element directs the application to fill the screen with its window ("fill_parent" for width and height). The "TextView" element displays a text field expanding to cover window width, but limits itself to content height ("wrap_content"). The "Button" element is a button named "buttonFinish", big enough to accommodate its content. Code obtains a handle to it by calling "Button buttonFinish = (Button) findViewById(R.id.buttonFinish);"), and creates an event listener for its OnClick event. This event listener calls "finish()" to close the app.

h4. Running the app on an Android Virtual Device

Once you've coded your app, choose "Run" > "Run" in Eclipse. A dialog named "Android Device Chooser" will open, asking you to choose a device for it. Select the "Launch a new Android Virtual Device" checkbox and the virtual device you previously made, should become available for selection (select it and click "OK"). The virtual device will start booting up and will eventually run your app. Beware, on slow computers (e.g. an old model of Asus EEE PC) this can take minutes.

h4. Running the app on a real Replicant device

1. Declare your app as debuggable. In the left-hand sidebar of Eclipse, your project's resource tree should contain a file resource named "AndroidManifest.xml". Right-click it and choose "Open With". Proceed by choosing either "Android Manifest Editor" or "Text Editor". If you preferred the manifest editor GUI, select the tab "Application" at its bottom. On the "Application" tab, set the field "Debuggable" to "true". If you preferred the text editor, append the property "android:debuggable="true" to the "<application>" element.

2. Enable USB debugging on your device, for example by choosing "Menu" > "Settings" > "Applications" > "Development" and checking the "USB Debugging" checkbox.

3. Set up [[ADB]] on your PC.

Do the verification by issuing "adb devices" on command line. Make your your ADB (Android Debug Bridge) is included in your @$PATH@ variable. If it lists your device and its numeric ID, all should be fine. If it lists @?????????@ for the ID and says @No permissions@, you might need to restart the ADB server (issue @adb kill-server; adb start-server@).

4. Run the app. Without a customized run configuration, Eclipse should display the "Android Device Chooser" dialog, letting you choose. 

5. Optionally, configure automatic deployment: if you want to automatically deploy to devices when they're attached, create a run configuration for your app, proceeding to select "Deployment Target Selection Mode: Automatic" in the "Target" tab.