How to skip battery optimisation & usage steps on Zebra devices

The page describes how to automate the disablement of the battery optimisation for the companion app, as well as granting access to the usage data, during the enrollment process.

In the profile configuration tab, when the admin enables the following option:

He’s prompted to explicitly grant access to the usage data during the device enrollment, which adds steps to the whole process.

Same for the following option:

When enabled, the process is even more complicated: the user has to look for the companion app in the list of apps, then select it to disable the battery optimisation.

Fortunately, these both steps can be automated thanks to the Zebra OEMConfig app.

 Instructions

Please follow these steps to make the enrollment process much smoother, without losing access to the usage and advance status update features.

Create an enrollment profile

In the WizyEMM console, create a dedicated profile which will be used to enroll your devices. In this profile, make sure to disable both options:

Then, open the Zebra tab, and create a first step named Disable battery optimization for the companion app. Then, in this step, value the following items:

• Power Configuration > Battery Optimization Action: select Remove

• Power Configuration > Remove Package Names: type app.wizyemm.eu.companion

This should look like this:

Then, create a second step named Grant access to usage to the companion app, and value the following items:

• Permission Access Configuration > Permission Access Action: select Grant

• Permission Access Configuration > Grant Permission: select Package Usage Stats

• Permission Access Configuration > Grant Application Package: type app.wizyemm.eu.companion

• Permission Access Configuration > Grant Application Signature: type the following text:

MIIDlzCCAn+gAwIBAgIETvxF3zANBgkqhkiG9w0BAQsFADB8MQswCQYDVQQGEwJGUjEZMBcGA1UECBMQUGF5cyBkZSBsYSBMb2lyZTEPMA0GA1UEBxMGQW5nZXJzMRAwDgYDVQQKEwdXaXp5RU1NMRYwFAYDVQQLEw1Tb2Z0d2FyZSBUZWFtMRcwFQYDVQQDEw5GbG9yaWFuIFBPTlJPWTAeFw0xOTA3MjkxNDAxNDRaFw00OTA3MjExNDAxNDRaMHwxCzAJBgNVBAYTAkZSMRkwFwYDVQQIExBQYXlzIGRlIGxhIExvaXJlMQ8wDQYDVQQHEwZBbmdlcnMxEDAOBgNVBAoTB1dpenlFTU0xFjAUBgNVBAsTDVNvZnR3YXJlIFRlYW0xFzAVBgNVBAMTDkZsb3JpYW4gUE9OUk9ZMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwEjr5kCtO6jCbHyrClx/C7mlkBG4yPeSHWHScz4v6V76Tg/EtRbRqYMmkjPj3hMPsQVVuykO3tivSwRfMLoKDZijR2a5eP3a5sUoNBYJKQXf8B1uOU0WoSIriZurloEPlE0CZaShWsDXIDuEksrgLdprCMqdJ/Ch+HBkNJe2zRJTKaeAn3cRYMJy496n8AQzt1P+XL3a2AJDty2zUM53xF9IvZipQ7Ouz905p83trn8yakYtPBfYtrDSIjXCnG7M3akQiV4Hf8K+JIRoHAA+3ugwXYx5kXIR0pG3/oOUPU7L7wkLzs17/W+e1zdbceQUvedaKjcAbEhSkh3hGaBmawIDAQABoyEwHzAdBgNVHQ4EFgQUQU124Zst6MqMkNFldiwqL4qyPqYwDQYJKoZIhvcNAQELBQADggEBADeQwSFB6nLqsbR6sva6UWbQNVByArMIJo5plSTf4gRvPeLDual8dNnTjPcByYBDkeGf0UXSc139Gt1jLgRl5BXZ4TXgYoNvhI6Oof5RuCAZDJeRU+9/gjjDlXwR+JIiyZYQnUtqvmmE/XQbZ68Lt2I9FDnb28yxDAAsew3ZYRFpxWwXHU4D5glu5GZzH6cZsFVnS28CfRbWGe03LXUyI5G37+DzDvKKpd7cGSdDRmb4lbnIe+C9lZp1JOoCMHJMhnEL2Xt4ohf9lKZ82ZleomLECZswVY7vTf4RIVLBPvi4igNzd6bUkfsB2C6W3nzv9nvbN8mBE5EjTKS3Mx9DTCs=

This should look like this:

 

Create a runtime profile

Duplicate the enrollment profile created in the step before, then enable the two options:

 

Device enrollment

Enroll the device with the first profile.

Then, when the device is enrolled and fully functional, apply the second profile.

Finally, make sure that the configuration was properly applied by checking the device application logs:

 

The companion app should report that the usage access has been properly allowed by the user, and that the report service is enabled.