- Xibo for Android
- Install a White Label or a different Player version on a DSCS9
- CEC Screen Power on/off with DSDevices DSCS9
- Hardware Recommendations (website?)
- Philips Signage SoC Monitors (website?
- Managing Storage on the Android Device
- Player Settings
- Players without an Internet Connection
- Remote Administration with SS Helper
- Restart Rooted Device with a Shell Command
- Rooting a Device
- Running Xibo for Android
- Resolving Common Issues
- Error shown when I try to licence my Player?
- Player not updating from the CMS?
- I can see my Licence entry but the Player appears unlicensed?
- Error message - Player is missing dependencies
- My scheduled Layouts are not working?
- Layout won't play? Splash screen plays?
- Watchdog error message
- Troubleshooting for Administrators
- Audit Trail
- Log Information
- Player Logs
- Getting the Player Status
- Can I use the Xibo name / logo?
- Can I run a Xibo Player on Raspberry Pi?
- How can I increase the upload file size limit?
- How do Players communicate with the CMS?
- How many displays can Xibo support?
- How do I reset the Xibo_admin account password?
- Power On/Off for Players
- Why do I need a Default Layout?
- Xibo for Android FAQ's
- Autoplaying Embedded Youtube Videos
- Closing to Home screen
- Displaying Images
- Embedded TV
- External SD card not listed when running Banana-Pi
- Helper Command to change Time zone
- HTML5 Video
- Memory Notifications
- Menu not accessible
- Orientation Settings for the DSDevices DSCS9 Player
- SSL Support
- Using Portrait Displays
- Video wont play properly
On this page
Xibo for Android will issue memory alerts when the application has been asked by Android to release its resources more than 10 times. It is normal and routine for Android to make these requests of running applications, however repeated requests can be a cause for concern.
When over 10 notifications have been received which affect the foreground application (Xibo is designed to run in the foreground), then the below log message will be output:
(1) Memory Notifications. Current level=(2) at Total: (3)MB. Used: (4)MB. Device Total: (5)MB. Device Free: (6)MB.
- The number of occurrences (should always be 10)
- The current “trim level” 5 = low memory, 15 = critical memory
- The total amount of memory allocated to Xibo
- The amount Xibo is currently using
- The total on the device (only available on some devices)
- The percentage free (only available on some devices)
Versions of Xibo for Android before 1.7 R52 reported each occurrence of a memory trim request - this only served to provide repeat notification, which often proved to be unnecessary.
Memory alerts are often normal and nothing to worry about, however if repeated alerts occur in a consistent manner it may be an indication that another application installed on the device is consuming a lot of memory.
In these cases it is useful to look at the installed applications and remove unnecessary ones.
Most of us are used to memory on our desktop/laptop PC’s, where we have 8GB of RAM and an application can consume all of the available memory on the PC without the operating system intervening. Android is fundamentally different as the operating system assigns each application an allocation of memory for it to use. This allocation is far less than the total available on the device and is actively managed by Android. If the application uses more than its allocation, it will be terminated by Android.
Android will also ask applications to “trim” their memory usage at certain points in their life cycle - it may do this because there is general memory pressure in the system and it would like to keep everything running. Android likes to keep everything running so that applications resume faster.
Xibo is designed to run in the foreground - always, which gives it a priority over other applications loaded into memory and should mean that it is last on the list for any memory management activity. However we are interested in tracking this activity so we can better understand how this has been implemented on different devices - hence logging the above message.