I wouldn't count on it coming back. Google has made it clear to the OEMs and EMM providers that they want to push people toward AE management APIs and OEM exposed APIs via OEMConfig and to move away from the secure settings. This is very unfortunate given that there is STILL feature parity from what we were previously able to accomplish, but I have at least seen OEMs like Zebra start to include more within MX. For example screen rotation was finally added to MX recently, after previously only being able to configure that via writesecuresetting. 

I would be sad if this will really happen... i have a Nokia 5.3 here and want to turn off the fingerprint settings (not for unlock) and Wifi share. But now i don't know the setting names...

Hi Rafael,

Thank you for posting in SOTI Central,

Regarding Watchsettings being ported over to AE, I've requested information internally from the Product Management team. In the meantime, a potential workaround may be to use the "identify_activity" script.

I'll update this post in due course with the response.

Regards,

With "identify_activity" i only get "com.android.settings/.SubSettings" which seam not really helpfull.

Hi Rafael,

try the following:

Connect your Device via ADB and run logcat.

Make your changes to the settings repeatedly so you dont have so search for the one specific line in the logs and you should get your desired intent.

https://support.citrix.com/article/CTX232375

Sometimes its a bit difficult to find the right intent for logged adb acitivity but then you just have to use trial and error to find something working for you.

Thanks for the tipp, i'll take a look when i have time for that.

You should keep in mind though that its possible that even though you can put your intent together in the correct form from the logs, it may not be supported by oem.

I will say +1 for this topic, as i am facing the same issue.

As Rafal is quoted:

With "identify_activity" i only get "com.android.settings/.SubSettings" which seam not really helpfull. 

I would like to get all the sub permissions set for the soti agent under special apps permissions, the only thing that is coming up is "com.android.settings/.SubSettings"...

Is this what you are referring to? These are the subsettings requested by the SOTI agent. The WRITE_SETTINGS permission does need to be granted in order for the writesecuresetting script to work, but even then you will find mixed results with Android Enterprise managed devices. 

Please note that more recent MobiControl server include corresponding permission enable options in the AE add-devices rule, though they might not work on all AE devices just like for the script command just mentioned by Matt.