Best Practice for Low Spec Devices (Soti Agent is getting killed by android)
Thank you for posting your question.
I would recommend you to try Checking "Disable Doze Mode" Feature control. If you have MobiControl older than 14.2, Please try using the script:
writeprivateprofstring DeviceFeature DisableDozeMode 0
This will help the Device Agent to stay online all the times. Please try this out and see if this works for you use case.
Technical Support | SOTI Inc. |1.905.624.9828 | firstname.lastname@example.org | www.soti.net |
While there is some limited control to request kernel not to swap an app out due to power management considereations, there is little one can do to stop an app from being swapped due to low memory. In pinciple, the device agent should be restarted automatically after a while.
To solve your problem, the best approach is to totally disable certain memory-hungry or redundant apps/services (especially those that are freely bundled with the device) via App Manager in device's Settings.
Thanks Raymond and SCMOD,
dozemode isnt exactly helping here, since the device(agent) isnt losing connection to mobicontrol.
The whole Agent is getting killed by android and is then automaticly started again, though maybe as "security feature" when the agent combined with the lockdown is loaded, it closes all previously or still opened apps.
So when the main app uses to much ram, soti agent is killed by android then automaticly restarts and lockdown then completly closes our app.
An option to not have kiosk closing previously opened apps would be useful in this case although its kind of a security risk.
I will try to further strip down the device with unneeded apps.
Kind Regards John
So apparently i missed something and you can somehow leverage foregroundmode via scripts:
Although i cant get it to work with DA and Agent 184.108.40.2069
Foregroundmode enable doesnt work
the example foreground enable doesnt work either
Kind Regards John
'foregroundmode enable' works for me in DA mode with agent version 220.127.116.119. An icon appears in the notification area:
(It doesn't appear to work in AEDO mode)