Changing Android device settings unavailable in SOTI native GUI

With most MDM/EMM solutions you are limited to whatever options are available in the GUI (I’m looking at you, AirWatch). SOTI in this regard looks weird, since the number of settings is not particularly rich, which makes it seem limited. However, SOTI has the super-awesome SOTIscript, and SOTIscript has a number of super-awesome  (but barely documented) script commands.

Today, we will take a look at how to use those commands to change (virtually) any Android OS setting available on your device via SOTI MDM.



Calling Android Settings pages programmatically during Staging

In quite a few situations we need the user to input specific data during device Staging. For instance, I have been doing a job for a customer, requiring a PIN code pre-set on the device, when it comes back from repairs. This PIN code can only be set programmatically by Device Administrator class app (or MDM agent, which usually registers as one). Given the circumstances, this was not an option.

Normally, this means that you’d have to provide instruction containing lots of “tap this” and “skip that” as well as lots of screenshots to ensure that there is no way the user will be lost. However, this approach is error prone and time consuming. And for repair loop operations this means $$$. Wouldn’t it be better to just scan a barcode? But how?

Each page of the Settings app in an Activity. Thus, we can write an intent to pop it up. StageNow (via MX) allows us to run intents. The question is, how do we find, which data to populate the intent with? Let’s find out!