Android 11+ Migration

Android Platform Transition

PAGE UPDATED: Apr. 4, 2024

Overview

In accordance with Google-mandated enhancements to Android device security and data privacy, the Zebra device architecture is undergoing a major change. Zebra is working hard to make many of the changes transparent, but actions are required for most customer and partner apps either now or in the near future, particularly for data persistence and for apps that share and/or use shared data. Beyond Google mandates, Zebra is taking the opportunity to transition away from proprietary frameworks in favor of public specifications, and to build new solutions to help simplify app deployment across an enterprise. This evolution of the Zebra Android-device platform will help shorten development times.

At the forefront of Zebra's transition is its enhanced XML (eXML), an all-new framework that initializes instantaneously, processes commands more quickly and occupies less device storage space, leaving more room for customer apps and data. Zebra will continue to support and advance its traditional XML-based configuration system well into the foreseeable future.

Re-engineering MX

On Zebra devices running Android 11 and later, the feature set implemented historically by the MX service will be delivered by Zebra Device Manager (ZDM), a more extensible service that's easier to maintain and that provides a modern foundation for the delivery of new features and capabilities in the future. The familiar MX feature set remains and is still referred to under the MX brand name, with new features delivered under version numbers corresponding to those of Android.

As Zebra moves into the future, MX features will be exposed by ZDM, which hosts a new, more modern programmatic interface that conforms to public specifications and standards. While everything has changed for MX under the covers, Zebra is modifying its tools and utilities for use with ZDM to provide as transparent a transitional experience as possible for customers and partners. In addition to its new capabilities, ZDM also will perform the following:

  • Configuration of Zebra devices running Android 11 and later
  • Secure barcode processing for device configuration
  • Managed Configuration processing for Zebra app administration
  • Communications with all APIs, including those of the Android system, Zebra apps, and DPC and privileged-device APIs

MX Enhancements

In addition to implementing current MX features, the enhanced version also can do the following:

  • Work programmatically with apps and other services on the device through a publicly specified content provider interface and the new Zebra Secure Storage Manager (SSM) tool
  • Leverage SSM to make persistence more secure by encrypting persisted data
  • Store access permissions (i.e. "whitelists") for apps and manage inter-app file and data sharing
  • Receive updates independent of the underlying OS image, for faster delivery of features and fixes

Other Major Benefits

  • Faster delivery of Zebra value-added features thanks to decoupling from proprietary system underpinnings
  • Many new features and fixes available without a system update
  • Android Content Provider model employs public Android APIs, improves security, provides consistent sharing method for all apps
  • Security is improved for persistent data, including for EMM device enrollment, device configuration and enterprise apps
  • Supplements proprietary XML with an enhanced version of XML (eXML) with extensible specifications
  • Secure Storage Manager encrypts all data stored on the device, including persistent and transient data
  • All Zebra apps to support Managed Configurations for feature configuration and settings-file deployment
  • Simplified Device Owner enrollment from device Set-up Wizard for GMS and non-GMS devices
  • EMDK and StageNow solutions will continue to support device configuration using new methods

MX Deprecation

Some of the features in MX will not be implemented as Managed Configurations, either because they are not being used or offer little or no value. These features will be deprecated over time and eventually dropped from MX.

Learn more about the Android 11 Transition.

MX Feature Disposition

  • The MX Feature Matrix adds a "Status" column with icons to indicate disposition of each configurable parameter.
  • Hover over an icon to display its description.
  • Click an icon to display the icon key.

New Services, Tool Versions

The following architectural changes are available now:

  • Secure Storage Manager (SSM) employs Android Content Provider model for secure persistence, data storage and data sharing. Use of the /enterprise partition remains in effect, but Zebra strongly recommends switching to SSM as soon as possible. SSM is available now on devices running Android 11 and later.
  • Data Encryption Tool (DET) provides end-to-end encryption for on-device data storage and retrieval.
  • StageNow desktop and client supports traditional and eXML barcodes for staging all Zebra devices and Amdroid versions.

Note to Developers, EMMs

The use of XML for configuring Zebra devices and app settings is being enhanced, and Zebra has selected Android 11 as the "transitional" OS version. Zebra devices running Android 11 will accept either XML or eXML for device configuration. This is intended to allow organizations to continue using current methods for staging, persistence, and data and file sharing while gradually converting to the new version being introduced.

Important Changes

  • For barcode staging on Zebra devices running Android 13 and later: ONLY eXML barcodes are supported.
  • For XML staging from an EMM: Only legacy XML is supported, regardless of the target Android version.
  • For configuring devices from an EMDK app: Only legacy XML is supported, regardless of the target Android version.

Why is Zebra Doing This?

Zebra's "Mobility Extensions" (MX) framework was introduced in 2015, and has served reliably to control and configure Zebra's Android devices while helping Zebra customers and partners to avoid the complexities of platform signing. A proprietary system was required then because early versions of Android lacked the ability to interface with many Zebra-device features and peripherals, and very few centralized management systems existed to aid in device deployment across an enterprise.

Since 2015, Android has advanced tremendously. Most of the interfaces Zebra first built are now part of the platform, accessible through public, non-proprietary methods such as Android Managed Configurations. This has allowed Zebra to shift its focus to platform innovation, value-added features and faster times to market. One such innovation was to decouple the application layer from multiple underlying proprietary frameworks, allowing Zebra to develop its value-added solutions more reliably, in less time, and with fewer inter-dependencies.

What Do I Have to Change?

In the chart below, the two left-hand columns list the Zebra Mobility DNA components and how their major activities are achieved under Android 10 and older. The two right-hand columns show how the same activities are achieved on devices running Android 11 (the "transitional" OS), Android 13 and beyond.