Android Deployment

After Mobile Eye is successfully installed on any device, go to Configuration >  Licenses > Unassigned to find it. Check the box to the left, then click the Activate button. Within 5 or 10 minutes you should see your first data points for your device.

Permissions

First, location services must be turned "on" for your devices.  Then, with your MDM/EMM system, you should be able to auto-grant the required permissions below.

• Contacts – to associate results with a device’s host name
• Location (allow all the time) – to detect if there is a better access point close by
• Phone – to associate results with a device’s identifier
• Storage – to check its configuration file
• Notifications - to indicate that the service is running

Additionally, you may need to put the device in an administrator mode or revoke the lockdown screen first before pushing the install. 

SOTI MobiControl

• Create a profile configuration to contain the "high accuracy location permission" which is required by 7SIGNAL Mobile Eye to obtain SSID and BSSID information.
  • Go to Profile Configuration > Restrictions > Feature Control > Location Accuracy
  • Select the High Accuracy option, click Save, then Assign to the device group. 

Managed Configuration

7SIGNAL has enabled Android Enterprise Managed Configuration for Mobile Eye. Go to 'Create App Policy' then 'Advanced Configurations' to enable 'Managed App Config. Here, you may specify your organization ID and device name. See example below.

Package Studio (only use with Android 10 and below)

• Build a package with SOTI's Package Studio.
• From 7SIGNAL, get the current APK and a configuration file containing your organization ID. The configuration file will be written to the device's SD card (not supported with Android 11 and higher).
• When building the package, indicate that you want to start the app after it is installed.
• You may also add a 'reset' post-install script to your package.
• Load the package into a profile.
• Assign the profile to the device group.

VMWare's Workspace ONE

Instructions are only applicable for devices in Work Managed Device Mode. Additionally, Location Services must be turned on each device. Go to Devices → Profile → Launcher → Restrictions → Location Services to enable it for your devices in Workspace ONE.

Managed Configuration

7SIGNAL has enabled Android Enterprise Managed Configuration for Mobile Eye.  Here, you may specify your organization ID and device name. See example below.

Once you obtain Mobile Eye from Google Play, then with Workspace ONE use the ‘Application Configuration’ option, then add an ‘Assignment’ where you can modify the Organization ID and the device name. Go to:

Restrictions → Managed Access

Distribution → App Delivery Method → Auto

Application Configuration  

You should see two Configuration Keys, for organization and device name

The organization ID is given to you by 7SIGNAL and may be found in your welcome email.

The Value Type = string.   

For device name, you may use a variable, such as {DEVICE NAME}

Adding the Organization ID - 2nd method

Alternatively, you can add a device profile and add it to assigned device groups.

• Go to DEVICES → Profiles & Resources → Profiles
• On the General tab, give this profile the name 7SIGNAL Mobile Eye Org ID
• On the Custom Settings tab, add the following:

<characteristic type="com.airwatch.android.androidwork.app:com.sevensignal.MobileEyeEnt" uuid="568bc89d-1df8-

4ce9-a041-e5a24acdb7ec">

<parm name="organization" value="globalcorp123" type="String"/>

</characteristic>

• Click Save and Publish

Auto-Launch App - Two Step Process

• Go to DEVICES → Provisioning → Components → Files/Actions → ADD FILES/ACTIONS
• Select Android when prompted for the operating system.
• On the General tab, give it the name 7SIGNAL Mobile Eye Auto Start
• Go to the Manifest tab, the Action to Perform is Run Intent. Copy and paste the command line to run below.

mode=explicit,broadcast=false,action=android.intent.action.MAIN,package=com.sevensignal.MobileEyeEnt,class=com.sevensignal.mobileeyeent.ui.view.MainActivity

• Click Save when finished.

Now the second part where we use this newly created action to create a product. Products bundle provisioning components together in Workspace ONE and then can be assigned to groups of devices.

• Go to DEVICES → Provisioning → Product List View → ADD PRODUCT
• Select Android when prompted for the operating system.
• On the General tab, give it the name 7SIGNAL Mobile Eye Product and select the groups of devices that will use this product (called Smart Groups). 
• On the Manifest tab, click Add.
  • The Action to Perform is File/Action - Install
  • For Files/Actions, select 7SIGNAL Mobile Eye Auto Start (you just created this)

• Click Save when finished.
• If the Mobile Eye app does not start after deployment on some or all devices, then you may need to reprocess the action again.
  • Go to Go to DEVICES → Provisioning → Product List View
  • For the Mobile Eye product, click on the the number, indicating the quantity of devices that are "Compliant" or  "In Process" or "Failed".
  • When the list of devices appears, select the ones where Mobile Eye did not start. 
  • Then click the FORCE REPROCESS button.

Microsoft Endpoint Manager (Intune)

• Add Managed Google Play app, 7SIGNAL Mobile Eye Enterprise
• Create new app configuration policy with permissions, organization ID, and device name
• Assign both to your group

No Connection to Google Play

While an APK version of Mobile Eye is available through 7SIGNAL, it is not a recommended method of deployment because it does not support the Managed Configuration features.

Note on Running 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, like Workspace ONE and SOTI (when used in conjunction with Package Studio).

However, if your MDM/EMM system does not support this functionality, then you will need to launch the app manually or remotely. Once launched, Mobile Eye will run as a service in the background and should always restart itself after a device reboot. 

Full List of Permissions