Linphone is an open source softphone for voice and video over IP calling and instant messaging.
It is fully SIP-based, for all calling, presence and IM features.
General description is available from linphone web site.
How to get it
You can also download APKs signed with our key from our website.
Copyright © Belledonne Communications
Linphone is dual licensed, and is available either :
under a GNU/GPLv3 license, for free (open source). Please make sure that you understand and agree with the terms of this license before using it (see LICENSE file for details).
under a proprietary license, for a fee, to be used in closed source applications. Contact Belledonne Communications for any question about costs and services.
Supported features and RFCs : https://www.linphone.org/technical-corner/linphone/features
Linphone public wiki : https://wiki.linphone.org/xwiki/wiki/public/view/Linphone/
App has been totally rewritten in Kotlin using modern components such as Navigation, Data Binding, View Models, coroutines, etc...
Check the CHANGELOG file for a more detailed list. The first linphone-android release that will be based on this will be 4.5.0, using 5.0.0 SDK.
We're also taking a fresh start regarding translations so less languages will be available for a while.
If you want to contribute, you are welcome to do so, check the Translations section below.
org.linphone.legacy flavor (old java wrapper if you didn't migrate your app code to the new one yet) is no longer supported starting 5.0.0 SDK.
The sample project has been removed, we now recommend you to take a look at our tutorials.
Building the app
If you have Android Studio, simply open the project, wait for the gradle synchronization and then build/install the app.
It will download the linphone library from our Maven repository as an AAR file so you don't have to build anything yourself.
If you don't have Android Studio, you can build and install the app using gradle:
will compile the APK file (assembleRelease to instead if you want to build a release package), and then
to install the generated APK in the previous step (use installRelease instead if you built a release package).
APK files are stored within
When building a release AppBundle, use releaseAppBundle target instead of release.
Also make sure you have a NDK installed and that you have an environment variable named
ANDROID_NDK_HOME that contains the path to the NDK.
This is to be able to include native libraries symbols into app bundle for the Play Store.
Building a local SDK
- Clone the linphone-sdk repository from out gitlab:
git clone https://gitlab.linphone.org/BC/public/linphone-sdk.git --recursive
Follow the instructions in the linphone-sdk/README file to build the SDK.
Create or edit the gradle.properties file in $GRADLE_USER_HOME (usually ~/.gradle/) and add the absolute path to your linphone-sdk build directory, for example:
- Rebuild the app in Android Studio.
Install LLDB from SDK Tools in Android-studio.
In Android-studio go to Run->Edit Configurations->Debugger.
Select 'Dual' or 'Native' and add the path to linphone-sdk debug libraries (build/libs-debug/ for example).
Open native file and put your breakpoint on it.
Make sure you are using the debug AAR in the app/build.gradle script and not the release one (to have faster builds by default the release AAR is used even for debug APK flavor).
If you encounter the
couldn't find "libc++_shared.so"crash when the app starts, simply clean the project in Android Studio (under Build menu) and build again. Also check you have built the SDK for the right CPU architecture using the
Push notification might not work when app has been started by Android Studio consecutively to an install. Remove the app from the recent activity view and start it again using the launcher icon to resolve this.
When submitting an issue on our Github repository, please follow the template and attach the matching library logs:
To enable them, go to Settings -> Advanced and toggle
Debug Mode. If they are already enabled, clear them first using the
Reset logsbutton on the About page.
Then restart the app, reproduce the issue and upload the logs using the
Send logsbutton on the advanced settings page.
Finally paste the link to the uploaded logs (link is already in the clipboard after a successful upload).
First of all, to be able to get a symbolized stack trace, you need the debug version of our libraries.
If you haven't built the SDK locally (see building a local SDK), here's how to get them:
Go to our maven repository, in the linphone-android-debug directory.
Download the AAR file with the exact same version as the AAR that was used to generate the crash's stacktrace.
Extract the AAR somewhere on your computer (it's a simple ZIP file even it's doesn't have the extension). Libraries are stored inside the
jnifolder (a directory for each architectured built, usually
arm64-v8a, armeabi-v7a, x86_64 and x86).
To get consistent with locally built SDK, rename the
Now you need the
ndk-stack tool and possibly
If your computer isn't used for Android development, you can download those tools from Google website, in the
Command line tools only section.
Once you have the debug libraries and the proper tools installed, you can use the
ndk-stack tool to symbolize your stacktrace. Note that you also need to know the architecture (armv7, arm64, x86, etc...) of the libraries that were used.
If you know the CPU architecture of your device (most probably arm64 if it's a recent device) you can use the following to get the stacktrace from a device plugged to a computer:
adb logcat -d | ndk-stack -sym ./libs-debug/arm64-v8a/
If you don't know the CPU architecture, use the following instead:
adb logcat -d | ndk-stack -sym ./libs-debug/`adb shell getprop ro.product.cpu.abi | tr -d '\r'`
Warning: This command won't print anything until you reproduce the crash!
Create an APK with a different package name
Simply edit the app/build.gradle file and change the value of the
The next build will automatically use this value everywhere thanks to
manifestPlaceholders feature of gradle and Android.
You may have already noticed that the app installed by Android Studio has
org.linphone.debug package name.
If you build the app as release, the package name will be
If you encounter
Execution failed for task ':app:processDebugGoogleServices'.
> No matching client found for package name 'your package name'
error when building, make sure you have replaced
app/google-services.json file by yours (containing your package name).
If you don't have such file, remove ours.
Firebase push notifications
Now that Google Cloud Messaging has been deprecated and will be completely removed on April 11th 2019, the only official way of using push notifications is through Firebase.
However to make Firebase push notifications work, the project needs to have a
app/google-services.json file that contains the configuration.
We have archived our own, so you can build your linphone-android application and still receive push notifications from our free SIP service (sip.linphone.org). If you delete it, you won't receive any push notification.
If you have your own push server, replace this file by yours.
We no longer use transifex for the translation process, instead we have deployed our own instance of Weblate.
Due to the full app rewrite we can't re-use previous translations, so we'll be very happy if you want to contribute.
In order to submit a patch for inclusion in linphone's source code:
- First make sure your patch applies to latest git sources before submitting: patches made to old versions can't and won't be merged.
- Fill out and send us an email with the link of pull-request and the Contributor Agreement for your patch to be included in the git tree.
The goal of this agreement to grant us peaceful exercise of our rights on the linphone source code, while not losing your rights on your contribution.