Generally speaking there are 3 types of condition on android that will cause the android client to close:
- Application exception.
- An “ANR” error.
- Resources Pressure.
This is an error message raised by the application code which causes it to terminate. Every time an instance of this type of error occurs, Spring Signage are notified and take action to resolve the issue in the next version (where possible).
Application Not Responding (ANR)
This is an error caught by the Android O/S when an application is taking too much time and holding up the device. We are confident that our application doesn’t cause errors of type 2, we are constantly testing for this situation.
This is where the Android OS detects that the free RAM on the device is running low and closes the application to free up resources. This type of error is very difficult to detect and counter and is usually caused by other applications running on the device, or the device firmware itself. We have tested some devices that caused applications to close almost immediately due to RAM usage.
Solutions and Automatic Restart
Xibo protects against all 3 types of these errors using the automatic restart functionality which can be enabled in settings. This functionality checks to see if Xibo for Android is still running, and if not - requests that it be restarted.
Prevention is preferable to a cure, but unfortunately the problem is often with the device hardware / firmware or another application and not with Xibo. As a best practice all non-essential applications should be stopped or un-installed and the latest firmware available for the device should be used.
We maintain a list of devices with known issues.