Ensure app stays alive in Lockdown

I have an app which is being used on a number of devices which are in Lockdown via Soti Mobicontrol. I've noticed that when left unattended for some time (probably 20 minutes or so), my app that was previously in the foreground will be shut down and the Lockdown screen will be brought to the foreground. This wouldn't be that much of an issue if I wasn't relying on my app running also when noone is using the handheld, as the app will perform routine background tasks at certain time of the day.

Is there a way to ensure that if my app is active, that the Lockdown screen won't take over?

12 days ago
SOTI MobiControl
ANSWERS
RS
Robert Schäfer Bronze Contributor
11 days ago

To start with, if it's the only app in the kiosk and you want to be certain it keeps running its tasks, you should use single app mode to ensure the app is always open or alternatively use a script periodically in a task scheduler to check if the app is in the foreground and if not start (this can be done using JavaScript)

As for the kiosk screen being forced to the foreground periodically, that's unusual. It sounds like your reinstalling the kiosk periodically. It's also possible that it's not the kiosk being pushed to the foreground but Android pushing your app to the background.

There's also some inefficiencies in the way the app runs that I would suggest you look at if it's your app, or check with the app developer. Apps can run tasks even if they arnt open (fully closed) if they are designed to do so.

DS

Thank you for the answer. I cannot be certain that my app will definitely be the only app that will be used.

Regarding the ability for apps to run tasks even if they are closed, I have not done anything like that and most certainly would need to investigate that better. We are using the RhoMobile framework for our apps, and I honestly don't know if that framework has support for that functionality.

RC
Raymond Chan Diamond Contributor
11 days ago (edited 11 days ago)

Is it possible that your device has some aggressive power-saving mode enabled such that idle programs are killed/moved to the background after some time threshold or other criteria are met? If so, simply disabling such mode may leave your app in the foreground and get the problem solved.

 

Also, Android architecture have been supporting for over 10 years  "background service" software modules that get loaded, and be called called any time to serve other normal "activity" software modules from the same or different app(s).  Your software might need to be modified/rearchitetcted to take advantage of this module type partitioning to solve your current problem.

  

K
KJMOD@soti.net
10 days ago

Hi Daniel,

Thanks for posting on SOTI Pulse, Thanks Robert and Raymond for responding to the post, your expertise and willingness to help are greatly appreciated!

Kindly let us know if you tried disabling power saving mode as mentioned.

Thank you for choosing SOTI.

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net