Samsung Tab E - Set Screen Inactivity Setting

Samsung Tab E - Set Screen Inactivity Setting

Hi,

I'm attempting to come up with a solution to update a mass amount of devices to change the screen timeout setting from 30 seconds to the OS max of 10 minutes (wish I could disable completely).

I monitored setting the 10 minute setting and came up with the log and then script below.

 

Log:

Custom log (URI:content://settings/system SETTING:screen_off_timeout VALUE:600000)

 

Script sent to device:
writesecuresetting –sys screen_off_timeout 600000

 

There were no changes after the script was sent.  I waited a few minutes / rebooted the tablet but no results.  Is the command I sent via the script possibly not supported on our devices?

Device:  Samsung Tab E 8.0 (Verizon)

Model:  SM-T378V

OS:  7.1.1

 

Thanks in advance for any help on this issue.

7 Answers

Order By:   Standard | Newest | Votes
Support Staff | posted this 13 February 2018

Hi Chris, 

 

The script you are trying to run looks like it was written correctly.

 

However that being the case, some API's were depreciated in Android 7+ by Google and have since stopped working in the MobiControl console.

 

Let me look into this for you and see if there is a definitive answer for the particular script you trying to use to change the screen timeout settings.

 

Regards, 

 

 

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 1
  • 0
Chris R. | posted this 13 February 2018

Thanks much.  Would hate to think we would have to manually touch 100s of device for something simple like this.

  • 0
  • 0
Matt Dermody | posted this 13 February 2018

I just attempted this on a Zebra Android 7.1.1 TC51 and unfortunately got the same results. It appears to be deprecated with Android Nougat. 

  • 0
  • 0
Chris R. | posted this 14 February 2018

I just tried this on an older AT&T Tab E running 6.0.1 with the same results.

 

Model:  SAMSUNG-SM-T377A

OS:  6.0.1

 

I did notice this time when I turned the watchsettings to ON and manually changed the settings I saw 2 entries:

 

Custom log (URI:content://settings/system SETTING:screen_off_timeout VALUE:600000)
Custom log (URI:content://settings/system SETTING:screen_off_timeout_rollback VALUE:600000)

  • 0
  • 0
Raymond Chan | posted this 14 February 2018

Hi Chris, 

On Android Nougat devices, you can first check in your device's "Settings" to see if you can grant "Write Settings permission" option for Mobicontrol device agent.  I can do so on my Samsung S6 running Android 7.0.  After that,  sending

  writesecuresetting -sys screen_off_timeout_rollback  600000 
  writesecuresetting -sys screen_off_timeout  600000

to the device should be able to set the timeout to 10 minutes.

In fact, for many Samsung models, you can even set the timeout to values other than those available on the device's timeout Settings. E.g. sending

  writesecuresetting -sys screen_off_timeout_rollback  3000000 
  writesecuresetting -sys screen_off_timeout  3000000

set the time-out to 50 minutes.  No item on the timeout selection will be highlighted, but the timeout value works fine in our tests done years ago.  I am not sure if this trick also works for your device model. You can give it a go.  Good luck !

 

  • 1
  • 0
Chris R. | posted this 14 February 2018

That worked!!  I was able to enable the 'Modify System Settings' setting in the Apps > App Manager > MobiControl > Advanced section.  Once I did that, I sent the original scripts to the device and the timeout time updated to 10 minutes.

 

The only bad part is that I likely can't script the change I made above and every tablet we have out in the field is still going to have to be "touched" to enable that setting.  Might as well just change the display while we're in there making that change.  Is there anyway to default that setting on MobiControl install or automate it somehow?

  • 1
  • 0
Raymond Chan | posted this 15 February 2018

Hi Chris,

I still have not successfully grant such permission remotely with script commands.

However, if there are really many many devices of one device model but deployed very far away, one way to reduce the overall management cost is to consider using classical (i.e. non-html5/non-web-based) remote control session in combination with kiosk mode and macro playback to change the permission.

In summary,

1. deploy a profile to set kiosk mode with Settings as the only icon

2. start a  classical remote control session on one test device, record a macro to select the Settings icon and go to the relevant tab to grant the required permission.

3. start a classical remote control session on all the other remaining devices, and playback the recorded macro instead of doing the whole thing manually.

 

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback