Questions for AEDO device
What device brand/model are you working on?
What are the version and build numbers of the device agent and of the Android firmware?
Had you enabled the WRITE_SETTINGS permissions of your device agent befoe you tested the script command?
Hello Raymond, All,
Do you know if any improvement have been made regarding the writesecuresetting on AEDO?
We would like to set a screen_off_timeout but unfortunately “writesecuresetting -sys screen_off_timeout 300000” still doesn’t work.. Is there any astuce to do the trick on AE devices?
Many thanks !
I've gotten writesecuresettings but not watchsettings to work on AEDO devices somewhat ironically. I feel like being able to observe a setting change would come before being able to configure the setting change. Since I havent been able to pull any setting names or values I've just had to use other Android+ DA managed devices to reverse engineer various settings for the writesecuresettingscript.
Support for many MobiControl script commands, especially the undocumented ones, are specific to the device brand or device agent version/build numbers or firmware version/build numbers.
If there is an error message saying a script command is not supported, just retry and make sure you haven't misspelt the command or used some wrong argument syntax. There is nothing else you can do.
Please let me ask a question.
I tried to send a script 'writesecuresetting -sys screen_off_timeout 600000' to my SHARP SHV43 (Android 8.1.0, AEDO, Agent ver: 18.104.22.1684) and it worked.
Then I tried to send ‘watchsettings on’ to track the setting changes on my device, but I found a message in the device log, 'Script command is not supported by device (watchsettings)'.
watchsettings command depends on the device brand or type and I cannot use the command to my device?
Please don't have too high expectation.
Support for writesecuresetting command is currently quite limited or even non-existent for most device brands on Android Enterprise platform.
Thank you for the information.
I am going to check what the plugin can do.
Got it. Speaking generically, support for writesecuresetting is coming around to AEDO in SOTI. At present it appears that you still have to manually grant the SOTI agent permission to be able to configure those settings, but it appears we will also get the granted automatically soon through the usage of the manufacturer specific plugins. This means that support for that capability may be limited by what effort SOTI is putting behind that particular manufacturer's device under AE
I just checked and their are Lenovo AE plugins available:
Thank you for the quick reply.
The customer uses Lenovo TB-X705L, but it also uses other brands of devices with AEDO enrollment and wants to do same setting for them too, if possible.