MobiControl - Lockdown - Fatal Crash

MH
Mark Henke
TFORCE INTEGRATED SOLUTIONS

Our developments team is recently converting some mobile apps to Android (Xamarin Forms).

We have an existing SOTI server version 13.2.0.3123 for Windows CE devices.

Android device is Panasonic Toughpad FZ-N1 OS: 6.0.1

We have been successful Registering Android+ devices in SOTI and have managed to create a Profile that adds a local WiFi connection and deploys several packages to the device once the Profile is assigned and everything is as expected the apps function accordingly.

However when Lockdown feature is enabled in the Profile the device arbitrarily crashes and reboots itself.

I did run AppCat on the device and notice there was a fatal exception that happened close to the time a reboot occurred but the log does not display the exception details,  only a pointer to a subsequent log file that I cannot seem to access on the device. I am not certain if the device has to be routed to gain access to those debug files.

I am under the suspicion that Android 6 is not really supported with server version 13 or the agent is not fully compatible with Android 6.0.1.

I have read a similar post on this forum where it stated that the Lockdown is too aggressive and blocks access to system services that get called once the app is running by the OS and a fatal error is raised so the system reboots.

Any insight would be appreciated before we make a call for SOTI support otherwise

Regards 

7 years ago
Android
ANSWERS
DP
Dean P
7 years ago

Which device agent and version are you using? 

You could try a higher version of the v13 agent as an experiment from: https://docs.soti.net/mobicontrolagentdownloads

EG
Edgar Gomez
7 years ago

Hello

You may try to have Launch://com.android.settings in the lockdown. You may have it hiden, not showing it in the template.

For us, this has solved many issues similar to that you describe.

MH
Mark Henke
7 years ago

Thanks for your reply...

We have 13.0 from our 13.2 server... will try manually version 13.5,13.6 from the OEM SOTI downloads and see from there.

Regards

TP
Tu Pham
7 years ago (edited 7 years ago)

hey edgar-gomez-1 

Did you define the command "Launch://com.android.settings" in the GUI og your Lockdown profile or did you embed it into the HTML code of your template directly?

MH
Mark Henke
7 years ago

FOr us the SOTI MobilCOntrol Agent v13.5.1 was the answer downloaded from the OEM specific section on soti.net/oem

EG
Edgar Gomez
7 years ago

Hello, sorry for the late answer.

We add the item in the lockdown configuration screen in Mobicontrol.