SOTI Pulse Logo

App not starting lockdown, but starts without problem after lockdown exits

IM
Ian Muirhead

Hi, We have some Unitech HT730 mobile android barcode scanners, they are running Android 10, and are registered as Android Enterprise.   We are running a native lockdown but for some reason in lockdown mode the barcose scanner system service doesn't start, we have to go into admin mode and then start it, then back into user mode.  We could not run the scanner service directly as its not designed to be run directly.

Our supplier has supplied an app called Unitech USS launcher, which if run in admin mode works fine and starts the scanner service, but if run using the package id in lockdown mode does nothing.

I have confirmed we are using the correct package ID as if I run a script containing start com.unitech.usslauncher it opens, but if in lockdown mode it doesn't.

What am I missing please?

lockdown unitech Android 10
3 years ago
Android
ANSWERS
IM
Ian Muirhead
3 years ago

I've actually thought of another way around this, since it doesn't want to start in usermode, I have a quick script as a menu option that enters admin mode, starts the scanner service, then goes back into user mode, this can also run and startup and does get around the problem. 

Not particularly elegant, but does save me having to fix scanners 20 times a day

RC
Raymond Chan Diamond Contributor
3 years ago

If you want to avoid the need to start the scanner service in device administrator mode, you have to find ALL the software modules that have to be run/launched during the process, and have ALL of them whitelisted one way or the other in lockdown/kiosk mode.    As I do not have a similar hardware model and your scanner service app on hand, you have to find the full list and whitelist them yourself.   

MB
Marcus Breitenthaler
3 years ago

Hi Ian,

what Device Agent Are you using?

in Prevously Agent Version was a but that in Lockdown Mode the App was not able to open.

You can test it when it is able to pen then us use "Activity Suppresion" instead of Native Kisok then it is an OS Relase Problem or the Soti Agent has a problem.

Similar Discussions