wiki:Getting-Started/Android

Context Navigation

Version 67 (modified by ming, 8 years ago) (diff)
--

Getting Started: Building for Android

TracNav

~~Getting Started~~

Moved to: https://docs.pjsip.org/en/latest/index.html#get-started
Preparation

Build for Desktop

Build for Mobile

Build for Other
Next: Using the libraries

See Also

Requirements
Build Preparation
Building PJSIP
Video Support
Setting up the target device
Building and running pjsua2 sample application
1. Log output
Creating your own application
Pjsua application with telnet interface
Debugging native code with Eclipse
OpenSSL Support
1. Issue with using OpenSSL on Android M
Important Issue(s) when Developing Android Apps
Other Android projects

Android target is available since 2.2.

Requirements

Besides the Android SDK, you will also need the Android NDK (minimum version r8b).
Optional if you want to build and and run the sample application PJSUA:
- SWIG (minimum version 2.0.5)
- Eclipse with ADT Plugin.
- Telnet application to interact with PJSUA command line. If you are not familiar with telnet, please find a tutorial suitable for your development platform.

Build Preparation

Get the source code from repository, if you haven't already. This tutorial applies to PJSIP version 2.2 and above (or the 2.1 from SVN trunk dated 2013/04/24 or later).

Set your config_site.h to the following:

/* Activate Android specific settings in the 'config_site_sample.h' */
#define PJ_CONFIG_ANDROID 1
#include <pj/config_site_sample.h>

Building PJSIP

Just run:

$ cd /path/to/your/pjsip/dir
$ export ANDROID_NDK_ROOT=/path_to_android_ndk_dir 
$ ./configure-android
$ make dep && make clean && make

Notes:

It will build armeabi target, to build for other targets such as arm64-v8a, armeabi-v7a, x86, instead of just './configure-android', specify the target arch in TARGET_ABI and run it with --use-ndk-cflags, for example:
```
TARGET_ABI=armeabi-v7a ./configure-android --use-ndk-cflags
```
Also you should adjust Application.mk and library packaging path (see also #1803).
The ./configure-android is a wrapper that calls the standard ./configure script with settings suitable for Android target. Standard ./configure options should be applicable to this script too. Please check ./configure-android --help for more info.
Other customizations are similar to what is explained in Building with GNU page.
For some targets, there may be error like
```
error: undefined reference to '__stack_chk_fail_local'
```
this can be fixed by adding -fno-stack-protector into CFLAGS, e.g: via user.mak file.

Video Support

Features

Video on Android will be supported since PJSIP version 2.4. It has the following features:

native capture
native OpenGL ES 2.0 renderer (requires Android 2.2 (API level 8) or higher).
H.264 codec (via OpenH264 library, see below)

Requirements

OpenH264 (recommended)

Provides video codec H.264, alternatively you can use ffmpeg (together with libx264).

Follow the instructions in ticket #1758 (or ticket #1947 if you use PJSIP version 2.6 or above).

Copy all library .so files into your Android application project directory, for example:

cp /Users/me/openh264/android/*.so /Users/me/pjproject-2.0/pjsip-apps/src/swig/java/android/libs/armeabi

libyuv (recommended)

Provides format conversion and video manipulation, alternatively you can use ffmpeg. If you are using 2.5.5 or newer, libyuv should be built and enabled automatically, see ticket #1937 for more info. If you are using 2.5.1 or older:

Follow the instructions in ticket #1776

Copy all library .so files into your Android application project directory, for example:

cp /Users/me/libyuv-android/*.so /Users/me/pjproject-2.0/pjsip-apps/src/swig/java/android/libs/armeabi

ffmpeg (optional)

Provides format conversion and video manipulation as well as video codecs: H.264 (together with libx264) and H263P/H263-1998.

Follow the instructions from the web on how to build ffmpeg for android. We followed the instructions provided here and successfully built with Android NDK r10.

Copy all library .so files into your Android application project directory, for example:

cp /Users/me/src/ffmpeg-2.5/android/arm/lib/*.so /Users/me/pjproject-2.0/pjsip-apps/src/swig/java/android/libs/armeabi

Configuring

To enable video, append this into config_site.h:

#define PJMEDIA_HAS_VIDEO 1

Specify third-party video libraries when invoking ./configure-android, e.g:

$ ./configure-android --with-openh264=/Users/me/openh264/android --with-libyuv=/Users/me/libyuv-android/jni

Make sure openh264 and libyuv are detected by ./configure-android:

...
Using OpenH264 prefix... /Users/me/openh264/android
checking OpenH264 availability... ok
Using libyuv prefix... /Users/me/libyuv-android/jni
checking for I420Scale in -lyuv... yes
...

Update: since PJSIP 2.5.5, libyuv is included in the PJSIP package and configure script param --with-libyuv is removed, check ticket #1937 for more info.

Adding Video Capture Device to Your Application

Copy the java part of PJSIP Android capture device to the application's source directory:

cp pjmedia/src/pjmedia-videodev/android/PjCamera*.java [your_app]/src/org/pjsip/

Using Video API

Please check Video User's Guide.

Video capture orientation support

To send video in the proper orientation (i.e. head always up regardless of the device orientation), application needs to do the following:

Setup the application to get orientation change notification (by adding android:configChanges="orientation|keyboardHidden|screenSize" in the application manifest file and override the callback onConfigurationChanged()).
Inside the callback, call PJSUA2 API VidDevManager.setCaptureOrient() to set the video device to the correct orientation.

For sample usage, please refer to pjsua2 sample app. Ticket #1861 explains this feature in detail.

Setting up the target device

To run or debug application (such as the sample applications below), first we need to setup the target device:

using virtual device: http://developer.android.com/tools/devices/index.html
using real device: http://developer.android.com/tools/device.html

Building and running pjsua2 sample application

A sample application using pjsua2 API with SWIG Java binding, is located under pjsip-apps/src/swig/java/android. It is not built by default, and you need SWIG to build it.

Follow these steps to build pjsua2 sample application:

Make sure SWIG is in the build environment PATH.
Run make from directory $PJDIR/pjsip-apps/src/swig (note that the Android NDK root should be in the PATH), e.g:
```
$ cd /path/to/your/pjsip/dir
$ cd pjsip-apps/src/swig
$ make
```
This step should produce:
- native library libpjsua2.so in pjsip-apps/src/swig/java/android/libs/armeabi
  - note: if you are building for other target ABI, you'll need to manually move libpjsua2.so to the appropriate target ABI directory, e.g: libs/armeabi-v7a, please check here for target ABI directory names.
- pjsua2 Java interface (a lot of .java files) in pjsip-apps/src/swig/java/android/src/org/pjsip/pjsua2
Make sure any library dependencies are copied to pjsip-apps/src/swig/java/android/libs/armeabi (or the appropriate target ABI directory), e.g: libyuv.so & libopenh264.so for video support.
Create Android project from pjsua. In Eclipse:
1. From menu: File --> New --> Project
2. Select Android Project from Existing Code, press Next
3. In Root Directory, put the location of pjsua2 source code (i.e. $PJDIR/pjsip-apps/src/swig/java/android) and press Finish
You may need to select different Android SDK than what is configured in pjsua2. You can do this from the project's Properties.
Run it.

Log output

The pjsua2 sample application will write log messages to LogCat window (to show LogCat window, from Eclipse menu: Window --> Show View --> Other --> type LogCat)

Creating your own application

For developing Android application, you should use pjsua2 API whose Java interface available via SWIG Java binding.

Note that this has only been tested using Eclipse with ADT, however it might also be applicable for Android Studio.

First, build pjproject libraries as described above.
Also build pjsua2 sample application as described above, this step is required to generate the pjsua2 Java interface and the native library.
Create Android application outside the PJSIP sources for your project.
Get pjsua2 Java interface and native library from pjsua2 sample application:
1. Copy pjsua2 Java interface files from pjsip-apps/src/swig/java/android/src to your project's src folder:
```
$ cd $YOUR_PROJECT_DIR
$ cp -r $PJSIP_DIR/pjsip-apps/src/swig/java/android/src .

# Cleanup excess pjsua2 application sources.
$ rm -r src/org/pjsip/pjsua2/app
```
2. Copy native library libpjsua2.so from pjsip-apps/src/swig/java/android/libs to your project's libs folder:
```
$ cd $YOUR_PROJECT_DIR
$ cp -r $PJSIP_DIR/pjsip-apps/src/swig/java/android/libs .
```
Start writing your application, please check pjsua2 docs for reference.

Pjsua application with telnet interface

There is also the usual pjsua with telnet command line user interface, which is located under pjsip-apps/src/pjsua/android. It is not built by default and you need SWIG to build it. Application flow and user interface are handled mainly in the native level, so it doesn't use pjsua2 API with Java interface.

Follow these steps to build pjsua:

Make sure SWIG is in the build environment PATH.
- Alternatively, update SWIG path in $PJDIR/pjsip-apps/src/pjsua/android/jni/Android.mk file.
Run ndk-build from directory $PJDIR/pjsip-apps/src/pjsua/android (note that the Android NDK root should be in the PATH), e.g:
```
$ cd /path/to/your/pjsip/dir
$ cd pjsip-apps/src/pjsua/android
$ ndk-build
```
Create Android project from pjsua. In Eclipse:
1. From menu: File --> New --> Project
2. Select Android Project from Existing Code, press Next
3. In Root Directory, put the location of pjsua source code (i.e. $PJDIR/pjsip-apps/src/pjsua/android) and press Finish
You may need to select different Android SDK than what is configured in pjsua. You can do this from the project's Properties.
Run it.
You will see telnet instructions on the device's screen. Telnet to this address to operate the application. See PJSUA CLI Manual for command reference.

Debugging native code with Eclipse

Here are the steps for debugging PJSIP native code using Eclipse:

Build PJSIP with debugging enabled, e.g: insert CFLAGS += -g into user.mak in PJSIP root directory.
Make sure that the JNI part of the application is built using ndk-build. For reference, check pjsua's Android.mk build config in pjsip-apps/src/pjsua/android/jni, it contains sample of how to import PJSIP build settings (build search paths, build flags, etc) and SWIG invocation.
Enable NDK plugin for Eclipse, check this and follow the instructions.
- CDT can also be fetched from CDT download page, normally Eclipse for C/C++ will have CDT installed, just make sure that the CDT version is 7.0.2 or newer.

It is recommended to introduce delay (about 5 seconds) in the application code between loading the native code library and calling any native functions (to be debugged), e.g:

try {
	System.loadLibrary("some_native_lib.so");
} catch (UnsatisfiedLinkError e) {
	return -1;
}

// Wait for GDB init
if ((getApplicationInfo().flags & ApplicationInfo.FLAG_DEBUGGABLE) != 0) {
	try {
		Thread.sleep(5000);
        } catch (InterruptedException e) { }
}

// Start calling native functions here
// ...

Load the PJSIP project to Eclipse (if not yet), and try put breakpoint anywhere in the PJSIP code before launching the Android application debug configuration in Eclipse.

OpenSSL Support

Build OpenSSL (tested with OpenSSL 1.0.2a) for Android. The instruction provided here is specifically for arm64. For other architectures, modify accordingly. Please visit this page for reference and some examples. Note: change the NDK path below.

cd openssl-1.0.2a

export NDK=[your_android_ndk_path]/android-ndk-r10d

$NDK/build/tools/make-standalone-toolchain.sh --platform=android-21 --toolchain=aarch64-linux-android-4.9 --install-dir=`pwd`/android-toolchain-arm64
export TOOLCHAIN_PATH=`pwd`/android-toolchain-arm64/bin
export TOOL=aarch64-linux-android
export NDK_TOOLCHAIN_BASENAME=${TOOLCHAIN_PATH}/${TOOL}
export CC=$NDK_TOOLCHAIN_BASENAME-gcc
export CXX=$NDK_TOOLCHAIN_BASENAME-g++
export LINK=${CXX}
export LD=$NDK_TOOLCHAIN_BASENAME-ld
export AR=$NDK_TOOLCHAIN_BASENAME-ar
export RANLIB=$NDK_TOOLCHAIN_BASENAME-ranlib
export STRIP=$NDK_TOOLCHAIN_BASENAME-strip
export ARCH_FLAGS=
export ARCH_LINK=
export CPPFLAGS=" ${ARCH_FLAGS} -fpic -ffunction-sections -funwind-tables -fstack-protector -fno-strict-aliasing -finline-limit=64 "
export CXXFLAGS=" ${ARCH_FLAGS} -fpic -ffunction-sections -funwind-tables -fstack-protector -fno-strict-aliasing -finline-limit=64 -frtti -fexceptions "
export CFLAGS=" ${ARCH_FLAGS} -fpic -ffunction-sections -funwind-tables -fstack-protector -fno-strict-aliasing -finline-limit=64 "
export LDFLAGS=" ${ARCH_LINK} "

./Configure android
make

Then copy the libraries into lib folder:

mkdir lib
cp lib*.a lib/

Specify OpenSSL location when running configure-android, for example (with Bash): (change the openssl path folder)

TARGET_ABI=arm64-v8a ./configure-android --use-ndk-cflags --with-ssl=[your_openssl_path]/openssl-1.0.2a

And check that OpenSSL is detected by the configure script:

...
checking for OpenSSL installations..
checking openssl/ssl.h usability... yes
checking openssl/ssl.h presence... no
aconfigure: WARNING: openssl/ssl.h: accepted by the compiler, rejected by the preprocessor!
aconfigure: WARNING: openssl/ssl.h: proceeding with the compiler's result
checking for openssl/ssl.h... yes
checking for ERR_load_BIO_strings in -lcrypto... yes
checking for SSL_library_init in -lssl... yes
OpenSSL library found, SSL support enabled
...

Build the libraries:
```
make dep && make
```
If you encounter linking errors, you need to add this in user.mak:
```
export LIBS += "-ldl -lz"
```

Issue with using OpenSSL on Android M

As reported here, Google has moved from OpenSSL to BoringSSL, and hence app that links against platform libraries (such as libcrypto.so) will likely break. On Android M, you might get error like this:

java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "OPENSSL_add_all_algorithms_noconf" referenced by "/data/app/someapp/lib/arm/libMyAppApp-arm-android-eabi.so"

The solution would be to include the OpenSSL library in your project/APK.

Important Issue(s) when Developing Android Apps

Unable to Make or Receive Call (Problem with sending and receiving large (INVITE) requests over TCP)

The issue is documented in #1488. The solution is to try using port other than 5060 in *both* client and server, and/or reducing the SIP message size by following our FAQ here.

Garbage Collector May Crash Your App (Pjsua2 API)

Please check this pjsua2 book page about problems with GC.

OpenSLES audio device deadlock upon shutdown

As reported in Android NDK forum, when shutting down OpenSLES sound device backend, it may block forever:

W/libOpenSLES(6434): frameworks/wilhelm/src/itf/IBufferQueue.c:57: pthread 0x5fce71c0 (tid 6670) sees object 0x5fcd0080 was locked by pthread 0x5f3a2cb0 (tid 6497) at frameworks/wilhelm/src/itf/IObject.c:411

Currently, the only workaround is to use PJSIP's Android JNI sound device instead (one way to do this is by defining PJMEDIA_AUDIO_DEV_HAS_ANDROID_JNI to 1 and PJMEDIA_AUDIO_DEV_HAS_OPENSL to 0).

Bad audio recording quality on some devices

Reported that audio quality recorded on the microphone is bad and the speed is twice what it should be, it only happens on some devices. It could be fixed by setting audio mode via AudioManager to MODE_IN_COMMUNICATION in the application, e.g:

AudioManager am = (AudioManager) getSystemService(Context.AUDIO_SERVICE);
int original_mode = am.getMode();

/* Set audio mode before using audio device, for example before making/answering a SIP call */
am.setMode(AudioManager.MODE_IN_COMMUNICATION);
...
/* Restore back to the original mode after finished with audio device */
am.setMode(original_mode);

UnsatisfiedLinkError exception with "cannot locate 'rand'" message

This may occur when running pjsua2 sample app:

Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lorg/pjsip/pjsua2/app/MyApp;
...
java.lang.UnsatisfiedLinkError: Cannot load library: reloc_library[1285]:    37 cannot locate 'rand'...

As described here, this happens if you've built your native components with the android-21 target, but are trying to run it on a device with an older Android version, so re-run configure with APP_PLATFORM set to lower platform version, e.g:

APP_PLATFORM=android-19 ./configure-android

Error configure-android with "--use-ndk-cflags" using android-ndk-r11 or later

Starting from r11, Android NDK has removed the sample folder and changed the toolchain version, hence the configure-android with "--use-ndk-cflags" will fail with this error:

samples/hello-jni: No such file or directory.  Stop.
configure-android error: failed to run ndk-build, check ANDROID_NDK_ROOT env var

Please apply the fix in ticket #1950.

A review of Android audio output latency

For a review of Android audio output latency, please have a look at ticket #1841.

Other Android projects

Also have a look at the following PJSIP Android project:

csipsimple project, an Android port of pjsip.

Context Navigation

Getting Started: Building for Android

TracNav

Getting Started

Preparation

Build for Desktop

Build for Mobile

Symbian...

Next: Using the libraries

See Also

Requirements

Build Preparation

Building PJSIP

Video Support

Features

Requirements

OpenH264 (recommended)

libyuv (recommended)

ffmpeg (optional)

Configuring

Adding Video Capture Device to Your Application

Using Video API

Video capture orientation support

Setting up the target device

Building and running pjsua2 sample application

Log output

Creating your own application

Pjsua application with telnet interface

Debugging native code with Eclipse

OpenSSL Support

Issue with using OpenSSL on Android M

Important Issue(s) when Developing Android Apps

Unable to Make or Receive Call (Problem with sending and receiving large (INVITE) requests over TCP)

Garbage Collector May Crash Your App (Pjsua2 API)

OpenSLES audio device deadlock upon shutdown

Bad audio recording quality on some devices

UnsatisfiedLinkError exception with "cannot locate 'rand'" message

Error configure-android with "--use-ndk-cflags" using android-ndk-r11 or later

A review of Android audio output latency

Other Android projects

Download in other formats: