Device Runtime Deployment for new EMDK 4.2 does not recognize connected device

When I start "Device Runtime Deployment" to deploy the new MX runtime binaries coming with the new EMDK release 4.2, I always get an error message indicating that there is no device connected although a device is actually connected via USB.

 

This is what I see on the screen:

 

##############################################################################

 

This utility will deploy the EMDK for Android device runtime on the connected

 

Zebra Android device. This can update only one connected device at a time.

 

 

(C) 2014-2016 Symbol Technologies LLC. All rights reserved.

 

IMPORTANT: Connect the Zebra Android device to the computer via USB before

proceeding!

 

 

##############################################################################

 

Drücken Sie eine beliebige Taste . . .

 

Starting adb server...

 

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

 

Querying the state of the connected device...

 

 

FAILED: There is no device connected. Connect a device and try again.

 

 

The EMDK for Android device runtime deployment process has terminated!

 

Drücken Sie eine beliebige Taste . . .

 

I've tried with TC75, with TC55 and TC8000. Always the same result.

 

Installing the EmdkOSUpdateApp_v4.2.3.apk manually shows no problems.

But I takes much more time to first copy the APK file to the device and then install and start it on the device.

 

How to fix this?

Anonymous (not verified)
Hi Richard,  Do the devices

Hi Richard,  Do the devices show up in the devices list when you run "adb devices" on the command line? 

Make sure to update to the latest USB driver:

https://portal.motorolasolutions.com/Support/US-EN/Search?searchType=simple&searchTerm=adb

Vote: 
Vote up!
Vote down!

Points: 1

You voted ‘up’


Richard Venderbosch
Hello Bill.Yes, the device

Hello Bill.

Yes, the device does show up, but the ADB server is restarted due to different versions (32 v. 36).

Updating to the new USB drivers did solve the problem .

Thank you very much.

Richard.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Bohan Yao
Hi Bill, I am using a macbook

Hi Bill, I am using a macbook to connect a MC36 using adb, but the ./adb devices always shows nothing after I added the vendor id and reboot it for many times. I feel I need to get a android USB driver for the device but I only found drivers for windows in the motorolasolutions support page. Any suggestions?

Thank you!

Best,

Kevin

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Pietro Francesc...
Hi Bohan,MC36 is not

Hi Bohan,

MC36 is not supported by our EMDK (see release notes) or by Zebra's USB drivers (again, is not listed in the supported devices in the release notes).

I never worked with such device as it is only distributed in China, however, to retrieve the vendor ID number you can use OS X "System Information" application. Once the device is connected through USB, you can find the information about it.

Like for example for the TC75:

Screen Shot 2016-08-12 at 10.41.54.png

Ciao

~Pietro

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


chandan kumar
Hi Bill,I am developing a

Hi Bill,

I am developing a barcode Scanner app for my customer who will be using MC40 device for Scan.I am using emdk library.Is there any way to install emdk device runtime programatically or some other way?It will become a pain for customers.Right now what i am understanding is he has to connect to computer and install it on device.

Thanks

Chandan

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Richard Venderbosch
Hi Chandan.The EMDK runtime

Hi Chandan.

The EMDK runtime install process is mainly the installation of an APK file named EMDKOSUpdateApp_v6.0.7.apk (or similar).

First the APK file has to be tranfered onto the device - for example into the public "Download" directory.

From there it can then be programmatically installed using the "AppMgr" profile manager of the MX/EMDK.

Richard.

Vote: 
Vote up!
Vote down!

Points: 1

You voted ‘up’


chandan kumar
Hi Richard,Thank you for

Hi Richard,

Thank you for quick response.I am new to android and as suggested by you i was going through AppMgr of EMDK.They say that we have to add EMDKOSUpdateApp_v6.0.7.apk in xml file like this.

<!-- Silently install apk from the /enterprise/usr/persist folder -->
<wap-provisioningdoc>
  
<characteristic version="4.2" type="AppMgr">
  
<parm name="Action" value="Install" />
  
<parm name="APK" value="/enterprise/usr/persist/EMDKOSUpdateApp_v6.0.7.apk" />
  
</characteristic>
</wap-provisioningdoc>

This is which file actually?where can i find this.

Sorry for small question.

Tanks

Chandan

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Richard Venderbosch
Hello Chandan.If you have the

Hello Chandan.

If you have the latest "Symbol EMDK for Android" version 6 on your PC, you should find the APK file in this directory

C:\Programs\Symbol EMDK for Android\v6.0\Device Runtime Deployment

Richard.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


chandan kumar
Hi Richard,I tried doing

Hi Richard,

I tried doing installation via Profile Manger.So i craeted a profile,inside that i choosed App mgr and action as install of EMDKOSUPDATE.But for calling ProcessProfile you need emdk run time already installed on device.Please let me know if i am doing some thing wrong.

Thanks

Chandan

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Richard Venderbosch
Hello Chandan.Yes. You're

Hello Chandan.

Yes. You're right. Sorry that I didn't get the core of your problem

You can install the APK with another approach.

But this will need the assistance of the user because he will be prompted to allow the APK installation.

I found this method on Stack Overflow:

Intent intent = new Intent();

   // create intent
intent.setAction(Intent.ACTION_VIEW);

intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);

intent.setDataAndType(Uri.fromFile(new File(apkPathName)),

   "application/vnd.android.package-archive");

   // start activity to install the (APK) file
startActivity(intent);

Hope this helps better ...

Richard.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Log in to post comments