Screen Orientation set in AndroidManifest.xml is not being respected on Android 8.1.0 with MX version of 10.0

We're building a custom launcher. Through the EMDK (we're using MX 10.0) we're setting ourselves as the default launcher on the device via the "App Manager" EMDK profile.

This works as expected -- we're set as the default launcher. However, it has a side effect where our application no longer respects the screen orientation we set in the manifest or in onCreate of the activity.

Changing ethernet settings (static IP) using MX profile, invoke from Android app

We know it is possible to pass an xml file (StageNow XML format) to the mxconfig command using Soti MobiControl ( We want to know if there is a way to pass this xml file from within an Android Application in a more dynamic fashion?

Generating a Package Signature for Use by MX

By @DarrynCampbell

Zebra's MX layer exposes configuration and provisioning capabilities for Zebra devices. Some of these features can be potentially misused by harmful apps so in these cases it is required to specify the signature of the signing certificate used to create the app, this ensures that only the desired app is given the elevated privileges.

Dynamically Switching Keyboards on Zebra Android Devices

Last month I wrote about how to switch keyboard layouts on the fly using the Enterprise Keyboard and its API, the use case being that some screens in your app would require different methods of data entry. As I said in my previous post the Enterprise Keyboard is not a general-purpose replacement keyboard and the standard keyboard should be used for standard data or text entry.