The Wi-Fi Performance Company

Android Deployment

Obtaining the Mobile Eye app through Google Play is preferred because it facilitates deployment when using an Android Enterprise MDM/EMM solution.

Grant Permissions

Mobile Eye requires the following Android permissions:

Generally speaking, most MDM/EMM solutions that you procure through Google Play allow you to accept the app and it’s permissions before deployment.

If you use VMWare’s Workspace ONE, then when you add a public application through Google Play, you can accept the permissions the app requires on behalf of your organization, as shown below.

Below is a list of all the permissions in the app’s manifest.

[{“packageName”:”com.sevensignal.MobileEyeEnt”,”permissions”:[{“name”:”android.permission.INTERNET”,”value”:”1″},{“name”:”android.permission.GET_ACCOUNTS”,”value”:”1″},{“name”:”android.permission.ACCESS_NETWORK_STATE”,”value”:”1″},{“name”:”android.permission.READ_PHONE_STATE”,”value”:”1″},{“name”:”android.permission.READ_EXTERNAL_STORAGE”,”value”:”1″},{“name”:”android.permission.FOREGROUND_SERVICE”,”value”:1″},{“name”:”android.permission.ACCESS_FINE_LOCATION”,”value”:”1″},{“name”:”android.permission.ACCESS_WIFI_STATE”,”value”:”1″},{“name”:”android.permission.CHANGE_WIFI_STATE”,”value”:”1″},{“name”:”android.permission.WAKE_LOCK”,”value”:”1″},{“name”:”android.permission.RECEIVE_BOOT_COMPLETED”,”value”:”1″}]}]

Configure The Organization ID

Using your MDM/EMM solution, you should be able to add your 7SIGNAL Organization ID to the device profile so that your data is sent to the appropriate database in the cloud. The process will vary depending on whether your MDM/EMM solution is set as Android Enterprise.

If you register Mobile Eye as an internal or private app, then you’ll likely need to add some custom XML to your device profile, like in the example below.

<characteristic type=”com.airwatch.android.androidwork.app:com.sevensignal.MobileEyeEnt” uuid=”568bc89d-1df8-4ce9-a041-e5a24acdb7ec”><parm name=”organization” value=”globalcorp123″ type=”String”/></characteristic>

If you obtain Mobile Eye from Google Play, then most MDM/EMM solutions will allow you to pre-configure a key-value pair and push it down to the device.

For example, with Workspace ONE you may use the ‘Application Configuration’ option to On the application you can add an ‘Assignment’ where you can modify the following settings:

Restrictions → Managed Access

Distribution → App Delivery Method → Auto

Application Configuration  → 

In other instances you may need to load a configuration file on to the device at the time of deployment. This is a JSON file that should be named mobile_eye_config.json and contains the following:

{“organization”:”globalcorp123″}

You can obtain a copy of this file from 7SIGNAL. You’ll place the file in the ‘Downloads’ directory of the device. The location of the directory depends on the type of device, for example:

sdcard\download

storage\emulated\0\download\

Run App After Install

There are some MDM/EMM solutions that allow you to automatically launch the application after it’s been pushed to the device. In some cases, its a simple checkbox. If not, then add this custom XML to the device profile or manifest, such as below.

{mode=explicit,broadcast=false,action=android.intent.action.MAIN,package=com.sevensignal.MobileEyeEnt,class=com.sevensignal.MobileEyeEnt.View.MainActivity}

This command should initialize the app and run it as a background service. A 7SIGNAL icon will appear on the notification bar.

Depending on your MDM/EMM solution and whether it is connected to Google Play, you may not be able to perform all three tasks listed above, therefore, requiring some user intervention. Check with your solution vendor for more information.