I read about other applications and ways to integrate app with android to have more control over device which is non-rooted (remote reboot, remote update of apk).
I found that maybe there is the way to use such command via ADB:
bash
adb shell appops set --uid uk.org.xibo.client PROJECT_MEDIA allow
adb shell appops set --uid uk.org.xibo.client WRITE_SETTINGS allow
adb shell appops set --uid uk.org.xibo.client READ_DEVICE_IDENTIFIERS allow
adb shell appops set --uid uk.org.xibo.client SYSTEM_ALERT_WINDOW allow
adb shell pm grant uk.org.xibo.client android.permission.WRITE_SECURE_SETTINGS
adb shell dpm set-device-owner uk.org.xibo.client/.AdminReceiver
I’ve tried such way but setting the device owner was impossible.
Maybe Xibo support can drive this functions into Xibo development.
The Xibo APK is “device owner” ready and has all the bits required to support it. Being the device owner enables various further device control, again, already included.
However our experience is that the device owner must be set in the firmware by the device manufacturer and cannot be set via ADB unless the security on the device is bad (in which case we do not recommend using it).
I tested this feature in a competing solution and tried it on a regular Samsung phone — it worked without any issues. Therefore, it’s hard to agree with the claim that the solution must be supported by the manufacturer.
Nevertheless, I believe Xibo could share instructions that would allow users — without requiring root access on the device (which I consider extremely unsafe) — to enable software updates for Xibo, use the reboot function, and control the HDMI output (off/on).
Device Admin is available without manufacturer support, Device Owner is not. The Xibo Application should be listed as an available option in the Device Administrators section in settings where you can then activate it.