Enabling data usage monitoring permission on Samsung devices
Are these devices enrolled as Android Plus or Android Enterprise Managed devices?
Even if your device is using the latest Android Enterprise agent, the newly introduced MobiControl script commands related to app permission management cannot be used to manage permission of the device agent itself. There is no similar script command for Android+.
So, your only remaining options likely are either:
(1) Get the device in hand, enter admin password (defined in authentication profile)to force the device into MobiControl administrator mode and go to Settings to grant the required permission OR
(2) Start a remote control session to do what is described in (1).
Thanks for the reply Raymond. That's a lot of devices in a lot of different places. Not feasible to do it one at a time unfortunately.
Hopefully in the near future, the new script commands for Android Enterprise app permission can be extended to cover permissions of the device agent itself, or some newer Android Enterprise agents will have all required app permissions pre-approved by default.
For Android+ devices, I personally don't think there will be any solution.
Found a solution!
adb shell pm grant net.soti.mobicontrol.elm.samsung android.permission.PACKAGE_USAGE_STATS
You can do anything if you get the device in hand and have access to the ADB port. However, In the previous posts in this thread, we are talking about solution using MobiCotnrol to "remotely" change app permission.
With ADB, it is much more powerful than rooting a device. Hence, disabling USB debugging with feature control profile is nearly a must for deployment requiring even minimum security. Actually, if you have the device with you, you can just get into MobiControl administrator mode and have the lockdown menu turned off, then go to Settings and grant any app permission required. This way, all protections on USB ADB can be left unchanged.
How do you execute the adb shell command? I would also like to know if there is a way to do this.
1) Create script file containing command
2) Create a package containing the script file
3) Use a post-install script in the package to run the script file once