- Xibo for Android
- Install a White Label or a different Player version on DSDevices
- CEC Screen Power on/off with DSDevices
- Hardware Recommendations
- Philips Signage SoC Monitors
- 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
- 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
- Testing with Xibo
- 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
- SSL Support
- Using Portrait Displays
- Video wont play properly
On this page
Xibo for Android supports all main image formats with the exception of animated GIF’s.
Images are downloaded from the CMS and cached in the local Player library (on internal storage or SD card) and are preloaded into memory shortly before they are due to be shown.
Size and Format
Images served through the Image module are sampled so that only the quantity of pixels that can be displayed on the screen are loaded into memory.
Recommendations to display Images for best results:
- Ensure your Image is saved at no more than 96 dpi
- Ensure your Image is a similar size to your Region
- Use PNG/JPG file format
Why is this necessary?
When an image is shown, the physical space the image takes up in memory is far greater than the size of the file - the majority of file containers use compression to reduce the file size.
A JPEG image with a resolution of 2160 x 3840 at 600 dpi (common for printed media) shown without any sampling, would take ~24 MB of memory to paint on screen. If a graphics package were used to drop the resolution to 1080x1920 at 96 dpi, it would only take 6 MB of memory to open.
Xibo for Android needs to “decode” the image from the format it has been saved in (i.e. PNG) and load it into the graphics card for display. Some images may be in a format that Android is not able to decode. In these cases the image will be blacklisted and the Layout will not be shown.
Xibo for Android caches images in the local library and opens them when they are needed for display. If Xibo cannot open the image for some reason it will provide an I/O Exception and skip the Layout.
Common causes for this error are:
- Read Only Storage
- Corrupted Storage
- Corrupted Download (will be re-downloaded)
- Corrupted Upload to the CMS
As a general rule, if this error message is happening for every image, the most likely cause is that the storage has become read only. If it is happening for 1 image only, then it is more likely to be a corruption.
Images on embedded or web page media observe the rules of the browser application on the Android device