ProGlove Documentation

Android 11 redefined the following storage-related permissions: READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, and MANAGE_EXTERNAL_STORAGE (for more information, see Scoped Storage.) Currently, this prevents the user to:

If you are using an MDM (Mobile Device Management) solution with Android Enterprise support or a company-managed Google Play, you can use the Managed configurations (previously known as AppRestrictions) to configure the device using the solution below that is running on the work profile.

To make the INSIGHT Mobile app available via your managed Google Play account you need to:

When this is completed, you can use the ProGlove configuration file content (Base64 encoded) as the available key in your MDM. The string is parsed inside the app and stored as a file identically to scanning the configuration barcode. The propagation is done every time the app is started or the configuration content is updated.

Custom device name

Match with a third-party system or simply identify your devices more accurately by setting a custom device name using a managed configuration within your MDM or the Intent API key broadcast.

This can help you bypass the built-in Android 10+ limitations pertaining to sharing device details, and allows you to add custom name/value to the staging file within your MDM. The custom value, i.e. customer_custom_identifier that you define, will be visible to your workforce in the INSIGHT Mobile (Android) app, and sent along with the data to INSIGHT Analytics for reporting purposes and sharper device identification.

For more details on reporting, see export data.

Once the value is set, you can see it displayed as an additional field in the INSIGHT connectivity widget within INSIGHT Mobile, as shown in the image below. That value will also be shared with INSIGHT webportal with every event.

Example created in a test mobile MDM environment and how it is displayed in INSIGHT Mobile (Android).

Note

We recommend setting up the Intent key and value prior to starting the application and work processes.

Tip

Ensure you have the correct value (macro) for retrieving your devices' serial numbers from your third-party system as this may vary (i.e. %SERIALNUM%, {DeviceSerialNumber}, etc.).

Set a custom device name using MDM

You can change the value by broadcasting a different message, bypass (ignore) it to use alternative integration methods, or remove it when needed. Sending the IGNORE value will simply ignore the entered information and allow the integrator to set the value in a different way (using adb or other API methods). Sending REMOVE as a value will remove the entered information, as well as the customer_custom_identifier field from the INSIGHT Mobile (Android) app.

Table 19. Managed configurations

File	Key	Valid values	Supported options
ProGlove.proconfig	configuration_content_android_enterprise_key	Only valid base 64 encoded config files	SET, IGNORE, REMOVE
levelname_provisioning_package.fleet	fleet_provision_content_android_enterprise_key	Only valid base 64 encoded fleet files	SET, IGNORE
customer_custom_identifier	customer_custom_identifier_content_android_enterprise_key	Any string containing 1 - 256 characters	SET, IGNORE, REMOVE

Set a custom device name using Intent

Alternatively, in case setting the custom device name isn't possible via an MDM, you can set it by broadcasting an Intent message containing the Action and Extra values, as listed below:

• Action: com.proglove.api.SET_EVENT_TAG

• Extras:

  • com.proglove.api.EVENT_TAG_KEY = "customer_custom_identifier"

  • com.proglove.api.EVENT_TAG_VALUE = "test"

  • com.proglove.api.EVENT_TAG_PERSISTENT = "true"

adb shell am broadcast -a com.proglove.api.SET_EVENT_TAG --es com.proglove.api.EVENT_TAG_KEY "customer_custom_identifier" --es com.proglove.api.EVENT_TAG_VALUE "TEST" --es com.proglove.api.EVENT_TAG_PERSISTENT true

To learn more, see Android developer's page, Admin's perspective, and Samsung KNOX page.

When your Android devices are affected by scoped storage limitations introduced with Android 11, or when access to the internet or your MDM is restricted, you can enable sending both provisioning and configuration files directly to the INSIGHT Mobile (Android) app using Base64 string.

No mediators, no permission restrictions, no access to internet or the INSIGHT webportal? No worries - read more below.

```
    adb shell "am start -n 'de.proglove.connect/.app.main.MainActivity' -a 'com.proglove.api.FILES_DATA' -e 'com.proglove.api.extra.PROCONFIG_FILE_CONTENT' 'Your Base64 String generated step above'"
```

val intent = Intent().apply {
    component =
    ComponentName.unflattenFromString("de.proglove.connect/.app.main.MainActivity")
    action = "com.proglove.api.FILES_DATA"
    putExtra("com.proglove.api.extra.PROCONFIG_FILE_CONTENT", "Your Base64 String here")
}

try {
    startActivity(intent)
} catch (e: ActivityNotFoundException) {
    // Insight Mobile was not found
}

Enable file management of Android devices when affected by scoped storage limitations introduced with Android 11 and when the use of older SOTI MobiControl versions is required.

If storage limitations affect the INSIGHT Mobile (Android) app to receive files and be configured, instead of using more technical ways, such as ADB commands, we offer the INSIGHT Mobile File Assistant solution. Relying fully on the INSIGHT Mobile (Android) app, the File Assistant offers the simplest way for managing your Android device's storage. It takes files from the public storage and provides it to INSIGHT Mobile via Intent, where it is stored inside the app-specific folder and processed per usual.

INSIGHT Mobile File Assistant is an excellent way to avoid using scripts and install other apps. It is controlled by the INSIGHT Mobile (Android) app and requires a valid PgLicence, so INSIGHT Mobile can accept the necessary files.

To ensure the PgLicence works as intended, you need store the license (.pgkey file) in a shared folder on your device. Create the ProGlove folder (i.e. /sdcard/ProGlove) and import the license. The File Assistant will always check this folder for files that should be applied to INSIGHT Mobile.

We recommend granting the "All Files Access" permission to the File Assistant before starting the process to make it seamless. Below is the ADB command to grant all permissions and enable file management:

adb shell appops set --uid de.proglove.connect.fileassistant MANAGE_EXTERNAL_STORAGE allow

Additionally, we recommend force-stopping the INSIGHT Mobile app, in case it's running in the background. Once INSIGHT Mobile restarts, it will automatically launch the INSIGHT Mobile File Assistant and ask you to allow access to all files. Follow the prompts to enable all permissions.

Supported file types: