We tried to install using the standard client and although the system installs it does not show anything except the xibo logo or static text.
I understand the MK802 is not recommended due to performance issues:
https://springsignage.freshdesk.com/support/solutions/articles/3000018938-device-compatibility-guide
As we don’t need to do much more than show some animated text in a small screen this should not be an issue.
Unfortunately the standard Client image doesn’t seem to work.
Could someone please help us determine the steps to install a working client into a MK802IIIS?
You need to configure the Player to talk to your CMS, and then licence it there and send content to it.
Animated text is one of the most CPU intensive things you can do in Xibo so I fear the hardware may not be suitable for your use.
If you’ve already connected it to your CMS and it’s still showing the splash screen, please post a screenshot of the Player status screen so I can see what the problem is.
Hi Alex,
Thank you for your reply.
We are very excited about the idea of using Xibo as your support is outstanding.
I know the hardware we are trying to get seems small, but, to make the whole idea economically viable we need a hardware that is as cheap as possible so we can afford hardware plus your license. 
Here is a pic of the Status window:
https://app.box.com/s/y86p1lrja6skjfjdh0jca1f3nvvn785h
Thank you,
Sheilon
It’s hard to say as that’s only half the status screen, but it looks to me like you’ve got the storage settings wrong.
Try selecting “Use Public Storage” and selecting the first option from the list of storage locations. That will put the files the Player downloads on the emulated SD card on the device.
Here is a more detailed collection of screenshots that hopefully should give you a better idea of what is going on in the device:
https://app.box.com/s/6d0vhccid3rx03trubhtr3v2yijhin6y
I did try to use the public storage already, however, that seems to not make a difference.
Have you read and followed the CMS Post-Installation guide at all? It seems like there are module files missing from the CMS which may be preventing the layouts playing too.
It does seem that the device can’t write to the storage. Try switching back then to internal storage after sorting out the missing module files and see how you get on
I think I found the issue!
I did some more digging after you said and played around the public storage.
Under “Storage options” there is a radio button “External SD Card1” that is by default unselected.
I decided to select.(even though I don’t have an SD card plugged in)
And to my surprise, things started working…
I’m not sure why, but, it could be that internally you guys need “some” option to be selected to truly use public storage.
If this is a bug or not I’ll let you decide. But for now it seems like is working, the performance with the text animation is great, and the device does not get hot at all…
We’ll run a few more tests and will be contacting you guys in the next month or so about special licensing as well as some customization using v1.8.
Thanks Alex!!
Yes if you re-read my instructions I said to select Use Public Storage and then to select the first item from the list of storage locations. Different devices name that differently but the emulated SD card is normally first in the list. You have to select a storage location when switching to Public Storage per my instructions
Alex,
But the odd thing is that the Public Storage needs to be selected only to select the SD option. Once that is done the Public storage needs to be once again unselected.
If I keep Public storage selected nothing is shown except the splash screen with Xibo and SpringSignage at the bottom right corner.
If you unselect Public Storage then the setting you make in the storage options does nothing.
You need to select Public Storage and then select the correct storage location for your device.