Hey Community,
i’ve little Problems with the Xibo Client 1.8-102 on my Android Players.
Sometimes the Android Player said “app is closed” or it just stops working and the default Menu from the Player ist showing at the screen.
In the FAQ i’ve read that it should restart it self but that doesn’t work always.
I’ve some Players and can’t finde any regularity. Sometimes it works for a Week, or just for one hour or a day.
it doesn’t matter if a Video is played, an image or just the default Layout from the Player is showed.
Have you any idea?
Some Informations about my Player - i know it’s not supported but i didn’t think thats the reason of the issus.
Bqeel M9C max comes with upgraded 2GB/ 16G eMMc high-speed flash memory which makes M9C max possess the double storage performance. 32G Max Extended Capacity provides you more space to download your favorite APPs and caches to browse websites, play games, and run apps smoothly.
Operation as Easy as ABC:
Bqeel M9C max has both HDMI and AV out port. You can connect this Android box to your TV through either a HDMI cable or an AV cable. Two 2.0 USB ports are provided in case you want to connect with your mouse or keyboard for more convenient operation. Infrared Remote control lets you easily master your TV and freely playing anything you like.
System Config:
CPU: S905X quad-core cortex-A53 frequency - 2.0G
GPU: Mali-450 5-Core GPU
FLASH: 16GB emmc
SDRAM: 2GB DDR
Power Supply: DC 5V/2A
OS: Android6.0
WIFI: RTL8189 802.11b/g/n
High Difinition video output: SD/HD max.1920x1080 pixel
LAN Ethernet: 10/100M, standard RJ-45
Wireless: Built in WiFi
Mouse/Keyboard: Support mouse and keyboard via USB;Support 2.4GHz wireless mouse and keyboard via 2.4GHz USB dongle
HD: HD 2.0 up to 4k2k Output
4K2k hd decoding: 4k2k H.265 Hardware Video Decode and 4k2k Output
1080P/AV/Dolby/3G: Support
SPDIF/IEC958: Coaxial
Package Contents:
1x M9Cmax Android Smart Box
1x HDMI cable
1x remote control (2x AAA battery excluded)
1x US adapter
That’s not the case, looking at the specification it should be fine, however since we did not test this device it’s not recommended by us, but that does not necessarily mean that it isn’t suitable for Xibo.
You could try enable auditing display profile (Display settings page in CMS) and auditing on the display itself (Displays page → Edit display → Advanced page set the auditing display profile you’ve created and enable auditing on the display)
Perhaps that will log some useful information about the problems your device may have.
Is it using default Android launcher or some custom made one?
I’ve activat the Auditing now.
I hope i get more informations now, to resolve the errors.
At the Log always shown this Errors which repeat each 5 minute.
1465554 06-09-2017 11:08 Unable to start XMR queue: class java.lang.IllegalArgumentException/java.net.UnknownHostException: Unable to resolve host "cms.example.org": No address associated with hostname
Yes I do have a pretty good idea what that means, it’s XMR configuration error.
Could you please tell me if you’re using docker or is it manual/custom installation on a webserver?
If it’s docker, then please navigate to CMS Settings page -> Displays tab
set the xmr public address to tcp://Your.IP.Address:9505 tcp://Your.domain.Name:9505
Changing the values above to match your CMS of course.
After that’s done, you can navigate to Displays page -> Edit Display -> Advanced tab -> Reconfigure XMR (enable it and Save the form).
If it’s manual/custom installation, then please see here http://xibo.org.uk/manual/en/install_xmr.html
But I recall that you’re using docker so you should only need to change the xmr public address in CMS settings.
Thanks!
I’ve change it, yes it’s a docker installation.
Know there are the next Errors in the List.
1468749 06-09-2017 13:05 Local Web Server is dead. Start again.
1468570 06-09-2017 13:00 startWebServer - cannot start webserver: bind failed: EADDRINUSE (Address already in use)
As for those two errors, it may happen if you’d have more than one Xibo player instance running or anything else running on the same local webserver port as the player.
If it’s not occurring all the time, then perhaps when you were restarting the player it didn’t close the connection properly and then tried to open a new one (slightly speculating here) - but in this case it should not cause problems.