For our Honeywell CT60s we control the screen timeout using Honeywell's UEMConfig (previously known as OEMConfig).

https://support.honeywellaidc.com/s/article/Honeywell-OEMConfig-for-MDM-EMM-UEM-solutions

-and a direct link to the app, which is linked in that article-

https://play.google.com/store/apps/details?id=com.honeywell.oemconfig&hl=en

You would need to install the app on your devices using an app policy, and set the timeout in the managed app config, as per the screenshot below:

Please clarify if you have failed to set the screen timeout to 3 minutes on your "on-line" test device by using send-script device-action to send the script  

  writesecuresetting –sys screen_off_timeout 180000

This script should work for most Android-Enterprise device enrolled in work-managed (device-owner) mode.  You can check the mode of any device by looking into the active MDM API's reported in configuration tab of the device agent or in the web-console.

If the script works and you just have to handle the problem that some of the devices can be offline while you initiate this device-action to a whole group or groups of devices, then putting the script as a pre-script of the file-sync rule is one simple and efficient way of doing it.

Hi Grabriel,

I don't have any  CK65 to perform any test myself.  However, I can share some experience on my tests with various Samsung device models, in which there are only limited number of timeout selections (e.g. 1 min, 2 min, 5 min, 10 min, 30 min, never).  When I used MC script command to change the timeout to 3 minutes or any other values not in the list of selection), the configuration was actually successful but the corresponding entry in the device's Settings still showed some old settings. I just waited 3 minutes and made sure the new timeout was effective, irrespective of what was shown in Settings app on the device.   I am not sure if it is the same for CK65.  So, maybe you need to redo your test to see if the script is actually working fine in all cases.

Regarding OEMConfig app that supports timeout parameter, if there is such an app already released by the OEM device vendor, it is OK to use it.  However, being able to use MobiControl script command still has an advantage - it can be used in scheduled task profile, lockdown menu item, speed kiosk, pcg package script, alert rule action, ... etc  to support some advanced use cases based on device status/events, whereas the managed configuration via OEMConfig is limited to relative static per-device/group configuration or at most in cases involving device-group relocation.

Hi Gabriel,

Thank you for posting on SOTI Pulse!

Thank you for marking the specific post as solution that resolved the issue.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net l Discussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter