Access Serial Number and IMEI on Mobile Computers Running Android 10

By @darryncampbell

The sample application to accompany this post can be found at https://github.com/darryncampbell/EMDK-DeviceIdentifiers-Sample

Android 10 limited access to device identifiers for all apps running on the platform regardless of their target API level. As explained in the docs for Android 10 privacy changes this includes the serial number, IMEI and some other identifiable information.

Zebra mobile computers running Android 10 are able to access both the serial number and IMEI however applications need to be explicitly granted the ability to do so and use a proprietary API.

To access the serial number and IMEI file on Zebra Android devices running Android 10 or higher, first declare a new permission in your AndroidManifest.xml

<uses-permission android:name="com.zebra.provider.READ"/>

Then use the MX access manager to allow your application to call the service identifiers associated with the serial number and IMEI

The MX access manager settings to enable this are as follows:

  • Service Access Action: "AllowCaller" (or 'Allow Caller to Call Service')
  • Service Identifier: For the serial number use content://oem_info/oem.zebra.secure/build_serial. For the IMEI use content://oem_info/wan/imei. If you want to allow your app access to both, you will need to declare two different instances of the AccessManager.

  • Caller Package Name: Your package name, in the case of the sample it is com.zebra.emdk_deviceidentifiers_sample.

  • Caller Signature: The signing certificate of your application. For more information on generating this see https://developer.zebra.com/blog/generating-package-signature-use-mx.

You can apply the MX access manager settings in one of three ways:

  1. Via StageNow
  2. Via your EMM
  3. Via your application, using the EMDK Profile Manager.

For example, StageNow will look as follows to enable access to the serial number:

StageNow

You can then run this sample app and should see something like the below:

Working

Or, on a device that does not have WAN capabilities, i.e. no SIM card or data connection:

Non-WAN

Handling errors:

If you failed to correctly allow your application access to oem_info service, you will see an error stating so against each property you did not assign access to, as shown below:

no_service_access

Assign access via MX and re-run the application.