Announcement: EMDK issue with Android Studio 1.3 New Project Wizard

An issue has been found with the EMDK when using a recent release of Android Studio ( v 1.3 )

When using the New Project Wizard in this version of Android studio, you will not find the EMDK listed as an option for the Minimum SDK. Even if they are listed as installed in the Android SDK manager.


A resolution to this issue is currently being worked on, but in the meantime the following instructions will walk you through manually configuring a new project where  Android API 16 or 19 was selected as the Minimum SDK


Configure New Project:

1. Create a new project, and set the Minimum SDK as API 16 or 19

2. Go to File > Project Structure

3. Select app in the left-pane and Properties tab.

4. Manually enter one of the following add-on names in the “Compile Sdk Version” depending on the API version (see below):

SDK add-on (API 16) name: Symbol Technologies, Inc.:EMDK 3.1 (API 16):16
SDK add-on (API-19) name: Symbol Technologies, Inc.:EMDK 3.1 (API 19):19






5. Click OK then Select Yes in the resulting dialog.


Your project is now ready for EMDK development (see EMDK Help for more information on creating an EMDK app).


Attached Images: 


Hi Wolfram,

of course is possible, just don't compile the com.symbol.emdk.jar library in your application but specify it as a "provided library". Then you can compile with one of the latest sdk and include the support library.

Take a look at this discussion:


Hi all,

this work-around works only, if you don't use any compatibility libraries. If you create a new project however, the so called "Blank Activity" extends AppCompatActivity. When comiling this with Compile Sdk Version: Symbol Technologies Inc.:EMDK 3.1 (API 16):16, there is a huge number of errors. The only way to get rid of these errors, is to remove every usage of the compatibility library (MainActivity extends Activity, remove from app Dependencies in Project Structure etc.). Then you will be able to create an app that uses the Zebra EMDK features (barcode scanning, etc.).

If you don't need the EMDK, you can create apps that use the compatibility library and run on the TC55 device. But that's not what you want when using a TC55 device.

I tried to include the EMDK as a library of the project. This compiles with no errors, but crashes on the device.

Does anyone know, how I can use both: the EMDK AND the compatibility library?


Hi Wolfgand,

If you installed the GMS version of Android v4.1 on our TC55 (the one with Google Play, Google Maps, etc), then you need to install the enterprise enabler that is available on our support site before installing the EMDK runtime.


Hi Pietro,

finally, I got it working by installing the non-GMS version of the OS and then installing the EMDK runtime.

KInd regards,


Hi Pietro,

thank you for guiding me to the discussion. I followed the tips and got it running successfully! After that, however, I "made the mistake" to install the "Image v1.74.99.17 Android Jelly Bean" on the TC55 device. Now I receive the following error message, when trying to deploy my app: "Installation failed with message INSTALL_FAILED_MISSING_SHARED_LIBRARY." The DWDemo App is still working, so there is no problem with the device itself. I did not change my application. Do you have any idea, what I can do to get it working again?


Hi Pietro,

I did in fact install the enterprise enabler before installing the EMDK runtime. Please see my last post to MC67NA.  Installation error: INSTALL_FAILED_MISSING_SHARED_LIBRARY for details. I have also updated to "Update Image v01.77G for TC55AH and TC55BH Android JellyBean" and then again installed enterprise enabler and EMDK runtime. But I still see the problem.

Kind regards,