1 Introduction into Android Development {#tutorial_android_dev_intro}
2 =====================================
4 This guide was designed to help you in learning Android development basics and setting up your
5 working environment quickly. It was written with Windows 7 in mind, though it would work with Linux
6 (Ubuntu), Mac OS X and any other OS supported by Android SDK.
8 If you encounter any error after thoroughly following these steps, feel free to contact us via
9 [OpenCV4Android](https://groups.google.com/group/android-opencv/) discussion group or OpenCV [Q&A
10 forum](http://answers.opencv.org). We'll do our best to help you out.
15 Android is a Linux-based, open source mobile operating system developed by Open Handset Alliance led
16 by Google. See the [Android home site](http://www.android.com/about/) for general details.
18 Development for Android significantly differs from development for other platforms. So before
19 starting programming for Android we recommend you make sure that you are familiar with the following
22 -# [Java](http://en.wikipedia.org/wiki/Java_(programming_language)) programming language that is
23 the primary development technology for Android OS. Also, you can find [Oracle docs on
24 Java](http://docs.oracle.com/javase/) useful.
25 -# [Java Native Interface (JNI)](http://en.wikipedia.org/wiki/Java_Native_Interface) that is a
26 technology of running native code in Java virtual machine. Also, you can find [Oracle docs on
27 JNI](http://docs.oracle.com/javase/7/docs/technotes/guides/jni/) useful.
29 Activity](http://developer.android.com/training/basics/activity-lifecycle/starting.html) and its
30 lifecycle, that is an essential Android API class.
31 -# OpenCV development will certainly require some knowledge of the [Android
32 Camera](http://developer.android.com/guide/topics/media/camera.html) specifics.
34 Manual environment setup for Android development
35 ------------------------------------------------
37 ### Development in Java
39 You need the following software to be installed in order to develop for Android in Java:
41 -# **Sun JDK 6** (Sun JDK 7 is also possible)
43 Visit [Java SE Downloads page](http://www.oracle.com/technetwork/java/javase/downloads/) and
44 download an installer for your OS.
46 Here is a detailed JDK (Java Development Kit) [installation
47 guide](http://source.android.com/source/initializing.html#installing-the-jdk) for Ubuntu and Mac
48 OS (only JDK sections are applicable for OpenCV)
50 @note OpenJDK is not suitable for Android development, since Android SDK supports only Sun JDK. If you use Ubuntu, after installation of Sun JDK you should run the following command to set Sun java environment:
52 sudo update-java-alternatives --set java-6-sun
57 Get the latest Android SDK from <http://developer.android.com/sdk/index.html>
59 Here is Google's [install guide](http://developer.android.com/sdk/installing.html) for the SDK.
61 @note You can choose downloading **ADT Bundle package** that in addition to Android SDK Tools
62 includes Eclipse + ADT + NDK/CDT plugins, Android Platform-tools, the latest Android platform and
63 the latest Android system image for the emulator - this is the best choice for those who is setting
64 up Android development environment the first time!
66 @note If you are running x64 version of Ubuntu Linux, then you need ia32 shared libraries for use on amd64 and ia64 systems to be installed. You can install them with the following command:
68 sudo apt-get install ia32-libs
70 For Red Hat based systems the following command might be helpful:
72 sudo yum install libXtst.i386
75 -# **Android SDK components**
77 You need the following SDK components to be installed:
79 - *Android SDK Tools, revision 20* or newer.
81 Older revisions should also work, but they are not recommended.
83 - *SDK Platform Android 3.0* (API 11).
85 The minimal platform supported by OpenCV Java API is **Android 2.2** (API 8). This is also
86 the minimum API Level required for the provided samples to run. See the
87 \<uses-sdk android:minSdkVersion="8"/\> tag in their **AndroidManifest.xml** files. But for
88 successful compilation the **target** platform should be set to Android 3.0 (API 11) or
89 higher. It will not prevent them from running on Android 2.2.
91 ![](images/android_sdk_and_avd_manager.png)
93 See [Adding Platforms and
94 Packages](http://developer.android.com/sdk/installing/adding-packages.html) for help with
95 installing/updating SDK components.
99 Check the [Android SDK System Requirements](http://developer.android.com/sdk/requirements.html)
100 document for a list of Eclipse versions that are compatible with the Android SDK. For OpenCV
101 2.4.x we recommend **Eclipse 3.7 (Indigo)** or **Eclipse 4.2 (Juno)**. They work well for OpenCV
102 under both Windows and Linux.
104 If you have no Eclipse installed, you can get it from the [official
105 site](http://www.eclipse.org/downloads/).
107 -# **ADT plugin for Eclipse**
109 These instructions are copied from [Android Developers
110 site](http://developer.android.com/sdk/installing/installing-adt.html), check it out in case of
111 any ADT-related problem.
113 Assuming that you have Eclipse IDE installed, as described above, follow these steps to download
114 and install the ADT plugin:
116 -# Start Eclipse, then select Help --\> Install New Software...
117 -# Click Add (in the top-right corner).
118 -# In the Add Repository dialog that appears, enter "ADT Plugin" for the Name and the following
119 URL for the Location: <https://dl-ssl.google.com/android/eclipse/>
123 @note If you have trouble acquiring the plugin, try using "http" in the Location URL, instead of "https" (https is preferred for security reasons).
125 -# In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
127 -# In the next window, you'll see a list of the tools to be downloaded. Click Next.
129 @note If you also plan to develop native C++ code with Android NDK don't forget to enable NDK Plugins installations as well.
131 ![](images/eclipse_inst_adt.png)
133 -# Read and accept the license agreements, then click Finish.
135 @note If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
137 -# When the installation completes, restart Eclipse.
139 ### Native development in C++
141 You need the following software to be installed in order to develop for Android in C++:
145 To compile C++ code for Android platform you need Android Native Development Kit (*NDK*).
147 You can get the latest version of NDK from the [download
148 page](http://developer.android.com/tools/sdk/ndk/index.html). To install Android NDK just
149 extract the archive to some folder on your computer. Here are [installation
150 instructions](http://developer.android.com/tools/sdk/ndk/index.html#Installing).
152 @note Before start you can read official Android NDK documentation which is in the Android NDK
153 archive, in the folder `docs/`. The main article about using Android NDK build system is in the
154 `ANDROID-MK.html` file. Some additional information you can find in the `APPLICATION-MK.html`,
155 `NDK-BUILD.html` files, and `CPU-ARM-NEON.html`, `CPLUSPLUS-SUPPORT.html`, `PREBUILTS.html`.
157 -# **CDT plugin for Eclipse**
159 If you selected for installation the NDK plugins component of Eclipse ADT plugin (see the picture
160 above) your Eclipse IDE should already have CDT plugin (that means C/C++ Development Tooling).
161 There are several possible ways to integrate compilation of C++ code by Android NDK into Eclipse
162 compilation process. We recommend the approach based on Eclipse CDT(C/C++ Development Tooling)
165 Android application structure
166 -----------------------------
168 Usually source code of an Android application has the following structure:
170 - `root folder of the project/`
175 - `AndroidManifest.xml`
176 - `project.properties`
177 - `... other files ...`
181 - the `src` folder contains Java code of the application,
182 - the `res` folder contains resources of the application (images, xml files describing UI layout,
184 - the `libs` folder will contain native libraries after a successful build,
185 - and the `jni` folder contains C/C++ application source code and NDK's build scripts `Android.mk`
186 and `Application.mk` producing the native libraries,
187 - `AndroidManifest.xml` file presents essential information about application to the Android
188 system (name of the Application, name of main application's package, components of the
189 application, required permissions, etc).
191 It can be created using Eclipse wizard or android tool from Android SDK.
193 - `project.properties` is a text file containing information about target Android platform and
194 other build details. This file is generated by Eclipse or can be created with android tool
195 included in Android SDK.
197 @note Both `AndroidManifest.xml` and `project.properties` files are required to compile the C++ part
198 of the application, since Android NDK build system relies on them. If any of these files does not
199 exist, compile the Java part of the project before the C++ part.
201 `Android.mk` and `Application.mk` scripts
202 -----------------------------------------
204 The script `Android.mk` usually has the following structure:
206 LOCAL_PATH := \f$(call my-dir)
208 include \f$(CLEAR_VARS)
209 LOCAL_MODULE := <module_name>
210 LOCAL_SRC_FILES := <list of .c and .cpp project files>
211 <some variable name> := <some variable value>
213 <some variable name> := <some variable value>
215 include \f$(BUILD_SHARED_LIBRARY)
217 This is the minimal file `Android.mk`, which builds C++ source code of an Android application. Note
218 that the first two lines and the last line are mandatory for any `Android.mk`.
220 Usually the file `Application.mk` is optional, but in case of project using OpenCV, when STL and
221 exceptions are used in C++, it also should be created. Example of the file `Application.mk`:
223 APP_STL := gnustl_static
224 APP_CPPFLAGS := -frtti -fexceptions
228 @note We recommend setting APP_ABI := all for all targets. If you want to specify the target
229 explicitly, use armeabi for ARMv5/ARMv6, armeabi-v7a for ARMv7, x86 for Intel Atom or mips for MIPS.
231 @anchor tutorial_android_dev_intro_ndk
232 Building application native part from command line
233 --------------------------------------------------
235 Here is the standard way to compile C++ part of an Android application:
239 We strongly recommend using cmd.exe (standard Windows console) instead of Cygwin on
240 **Windows**. Use the latter if only you're absolutely sure about, what you're doing. Cygwin is
241 not really supported and we are unlikely to help you in case you encounter some problems with
242 it. So, use it only if you're capable of handling the consequences yourself.
244 -# Open console and go to the root folder of an Android application
246 cd <root folder of the project>/
248 -# Run the following command
250 <path_where_NDK_is_placed>/ndk-build
252 @note On Windows we recommend to use ndk-build.cmd in standard Windows console (cmd.exe) rather than the similar bash script in Cygwin shell.
253 ![](images/ndk_build.png)
255 -# After executing this command the C++ part of the source code is compiled.
257 After that the Java part of the application can be (re)compiled (using either *Eclipse* or *Ant*
260 @note Some parameters can be set for the ndk-build:
261 **Example 1**: Verbose compilation
263 <path_where_NDK_is_placed>/ndk-build V=1
265 **Example 2**: Rebuild all
267 <path_where_NDK_is_placed>/ndk-build -B
270 @anchor tutorial_android_dev_intro_eclipse
271 Building application native part from *Eclipse* (CDT Builder)
272 -------------------------------------------------------------
274 There are several possible ways to integrate compilation of native C++ code by Android NDK into
275 Eclipse build process. We recommend the approach based on Eclipse CDT(C/C++ Development Tooling)
280 OpenCV for Android package since version 2.4.2 contains sample projects
281 pre-configured CDT Builders. For your own projects follow the steps below.
283 -# Define the NDKROOT environment variable containing the path to Android NDK in your system (e.g.
284 "X:\\Apps\\android-ndk-r8" or "/opt/android-ndk-r8").
286 **On Windows** an environment variable can be set via
287 My Computer -\> Properties -\> Advanced -\> Environment variables. On Windows 7 it's also
288 possible to use [setx](http://ss64.com/nt/setx.html) command in a console session.
290 **On Linux** and **MacOS** an environment variable can be set via appending a
291 "export VAR_NAME=VAR_VALUE" line to the `"~/.bashrc"` file and logging off and then on.
293 @note It's also possible to define the NDKROOT environment variable within Eclipse IDE, but it
294 should be done for every new workspace you create. If you prefer this option better than setting
295 system environment variable, open Eclipse menu
296 Window -\> Preferences -\> C/C++ -\> Build -\> Environment, press the Add... button and set variable
297 name to NDKROOT and value to local Android NDK path. \#. After that you need to **restart Eclipse**
298 to apply the changes.
300 -# Open Eclipse and load the Android app project to configure.
302 -# Add C/C++ Nature to the project via Eclipse menu
303 New -\> Other -\> C/C++ -\> Convert to a C/C++ Project.
304 ![](images/eclipse_cdt_cfg1.png)
306 ![](images/eclipse_cdt_cfg2.png)
308 -# Select the project(s) to convert. Specify "Project type" = Makefile project, "Toolchains" =
310 ![](images/eclipse_cdt_cfg3.png)
312 -# Open Project Properties -\> C/C++ Build, uncheck Use default build command, replace "Build
313 command" text from "make" to
315 "${NDKROOT}/ndk-build.cmd" on Windows,
317 "${NDKROOT}/ndk-build" on Linux and MacOS.
319 ![](images/eclipse_cdt_cfg4.png)
321 -# Go to Behaviour tab and change "Workbench build type" section like shown below:
323 ![](images/eclipse_cdt_cfg5.png)
325 -# Press OK and make sure the ndk-build is successfully invoked when building the project.
327 ![](images/eclipse_cdt_cfg6.png)
329 -# If you open your C++ source file in Eclipse editor, you'll see syntax error notifications. They
330 are not real errors, but additional CDT configuring is required.
332 ![](images/eclipse_cdt_cfg7.png)
334 -# Open Project Properties -\> C/C++ General -\> Paths and Symbols and add the following
335 **Include** paths for **C++**:
337 # for NDK r8 and prior:
338 ${NDKROOT}/platforms/android-9/arch-arm/usr/include
339 ${NDKROOT}/sources/cxx-stl/gnu-libstdc++/include
340 ${NDKROOT}/sources/cxx-stl/gnu-libstdc++/libs/armeabi-v7a/include
341 ${ProjDirPath}/../../sdk/native/jni/include
343 # for NDK r8b and later:
344 ${NDKROOT}/platforms/android-9/arch-arm/usr/include
345 ${NDKROOT}/sources/cxx-stl/gnu-libstdc++/4.6/include
346 ${NDKROOT}/sources/cxx-stl/gnu-libstdc++/4.6/libs/armeabi-v7a/include
347 ${ProjDirPath}/../../sdk/native/jni/include
349 The last path should be changed to the correct absolute or relative path to OpenCV4Android SDK
352 This should clear the syntax error notifications in Eclipse C++ editor.
354 ![](images/eclipse_cdt_cfg8.png)
356 Debugging and Testing
357 ---------------------
359 In this section we will give you some easy-to-follow instructions on how to set up an emulator or
360 hardware device for testing and debugging an Android project.
364 AVD (*Android Virtual Device*) is not probably the most convenient way to test an OpenCV-dependent
365 application, but sure the most uncomplicated one to configure.
367 -# Assuming you already have *Android SDK* and *Eclipse IDE* installed, in Eclipse go
368 Window -\> AVD Manager.
369 -# Press the New button in AVD Manager window.
370 -# Create new Android Virtual Device window will let you select some properties for your new
371 device, like target API level, size of SD-card and other.
373 ![](images/AVD_create.png)
375 -# When you click the Create AVD button, your new AVD will be available in AVD Manager.
376 -# Press Start to launch the device. Be aware that any AVD (a.k.a. Emulator) is usually much slower
377 than a hardware Android device, so it may take up to several minutes to start.
378 -# Go Run -\> Run/Debug in Eclipse IDE to run your application in regular or debugging mode.
379 Device Chooser will let you choose among the running devices or to start a new one.
383 If you have an Android device, you can use it to test and debug your applications. This way is more
384 authentic, though a little bit harder to set up. You need to make some actions for Windows and Linux
385 operating systems to be able to work with Android devices. No extra actions are required for Mac OS.
386 See detailed information on configuring hardware devices in subsections below.
388 You may also consult the official [Android Developers site
389 instructions](http://developer.android.com/tools/device.html) for more information.
391 #### Windows host computer
393 -# Enable USB debugging on the Android device (via Settings menu).
394 -# Attach the Android device to your PC with a USB cable.
395 -# Go to Start Menu and **right-click** on Computer. Select Manage in the context menu. You may be
396 asked for Administrative permissions.
397 -# Select Device Manager in the left pane and find an unknown device in the list. You may try
398 unplugging it and then plugging back in order to check whether it's your exact equipment appears
401 ![](images/usb_device_connect_01.png)
403 -# Try your luck installing Google USB drivers without any modifications: **right-click** on the
404 unknown device, select Properties menu item --\> Details tab --\> Update Driver button.
406 ![](images/usb_device_connect_05.png)
408 -# Select Browse computer for driver software.
410 ![](images/usb_device_connect_06.png)
412 -# Specify the path to `<Android SDK folder>/extras/google/usb_driver/` folder.
414 ![](images/usb_device_connect_07.png)
416 -# If you get the prompt to install unverified drivers and report about success - you've finished
417 with USB driver installation.
419 ![](images/usb_device_connect_08.png)
421 ![](images/usb_device_connect_09.png)
423 -# Otherwise (getting the failure like shown below) follow the next steps.
425 ![](images/usb_device_connect_12.png)
427 -# Again **right-click** on the unknown device, select Properties --\> Details --\> Hardware Ids
428 and copy the line like `USB\VID_XXXX&PID_XXXX&MI_XX`.
430 ![](images/usb_device_connect_02.png)
432 -# Now open file `<Android SDK folder>/extras/google/usb_driver/android_winusb.inf`. Select either
433 Google.NTx86 or Google.NTamd64 section depending on your host system architecture.
435 ![](images/usb_device_connect_03.png)
437 -# There should be a record like existing ones for your device and you need to add one manually.
439 ![](images/usb_device_connect_04.png)
441 -# Save the `android_winusb.inf` file and try to install the USB driver again.
443 ![](images/usb_device_connect_05.png)
445 ![](images/usb_device_connect_06.png)
447 ![](images/usb_device_connect_07.png)
449 -# This time installation should go successfully.
451 ![](images/usb_device_connect_08.png)
453 ![](images/usb_device_connect_09.png)
455 -# And an unknown device is now recognized as an Android phone.
457 ![](images/usb_device_connect_10.png)
459 -# Successful device USB connection can be verified in console via adb devices command.
461 ![](images/usb_device_connect_11.png)
463 -# Now, in Eclipse go Run -\> Run/Debug to run your application in regular or debugging mode.
464 Device Chooser will let you choose among the devices.
466 #### Linux host computer
468 By default Linux doesn't recognize Android devices, but it's easy to fix this issue. On Ubuntu Linux
469 you have to create a new **/etc/udev/rules.d/51-android.rules** configuration file that contains
470 information about your Android device. You may find some Vendor ID's
471 [here](http://developer.android.com/tools/device.html#VendorIds) or execute lsusb command to view
472 VendorID of plugged Android device. Here is an example of such file for LG device:
474 SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
476 Then restart your adb server (even better to restart the system), plug in your Android device and
477 execute adb devices command. You will see the list of attached devices:
479 ![](images/usb_device_connect_ubuntu.png)
481 #### Mac OS host computer
483 No actions are required, just connect your device via USB and run adb devices to check connection.
488 Now, when you have your development environment set up and configured, you may want to proceed to
489 installing OpenCV4Android SDK. You can learn how to do that in a separate @ref tutorial_O4A_SDK tutorial.