Hi Mark,

Thank you for posting in SOTI Central.

Try this script action: sendintent -b "intent:#Intent;action=com.symbol.selfdiagnostics/com.symbol.selfdiagnostics.SESReceiver;end"

Reference: https://www.soti.net/mc/help/v15.2/en/scriptcmds/reference/sendintent.html

If this resolves the issue please mark this post as the solution.

Regards,

I tried that script (that was one of my guesses), but doesn't work for me.
When using the adb command, a (new) file appears, that's how I check if it works.

Hi Mark,

I recommend you look into using ADB Logcat and identify what is going on within the backend of Android. You can also download additional logs via MobiControl Web Console -> View Device -> Logs -> "Download Logs" Button -> Device Agent Activity. Then you can match up the time that the script is sent to the ADB Logcat.

ADB Command Example: adb logcat -v threadtime *:V >> C:\temp\ADBLogs.txt

Reference: https://developer.android.com/studio/releases/platform-tools

Also make sure you're utilizing the latest agent, plugin, and firmware where applicable. You may need to disable Chatty if you're utilizing a System Signed agent for ADB Logcat to show everything: chattyfilter disable and then re-enable it via chattyfilter restore.

Regards,