About our Android Client
Supported device line-up
Currently recommended device line-up
Select the perfect device to make your content stand out!
Here's a quick overview of the device models we typically recommend and are well-acquainted with:
| Manufacturer / Device model | Platform / FW | Chromium version |
|---|---|---|
| Giada DN74 | Android 11 | 114 |
| Qbic BXP320, BXP321 | Android 8.1.0 | 84 |
| Qbic TD1050, TD1060 | Android 8.1.0 | 84 |
| Sony | Android TV 10 | 83 |
Currently supported device line-up
Here's a quick overview of the device models we typically support and are acquainted with:
We recommend that our partners always test devices before they order a large quantity.
Rooted Android devices are always recommended.
With root privileges, our application can access system functions such as time sync, remote device restart, and be able to update the application in silent mode.
| Manufacturer / Device model | Platform / FW | Chromium version |
|---|---|---|
| Giada DN76 | Android 11 | 83 |
| Giada DN74/DN75 | Android 8.1 | 81 |
| Giada DN74 | Android 11 | 81/83 |
| Giada DN73 | Android 10 | 74 |
| Giada DN73 | Android 7.1.2 | 81 |
| Qbic BXP300 | Android 7.1.1 | 84 |
| Qbic BXP301 | Android 5.1.1 | 66 |
| Qbic BXP100 | Android 10 | 96 |
| Qbic TD1050Pro | Android 10 | 96 |
System Requirements
Minimum System Requirements
Below Android 5 OS version, we cannot support any devices
We also do not support devices above Android 11 OS due to limited testing and potential compatibility issues.
- Android 5+ OS system
- 4 core CPU
- 2 GB of RAM
- 32 GB of internal storage
Recommended System Requirements
- 6 core CPU
- 4 GB of RAM
- 32 GB of internal storage
Selecting the right Android player is crucial for carrying out a successful Digital Signage project.
Wallboard cannot take any responsibility for performance if the player used is not adequate for the content that you are trying to run.
There are numerous Android devices, and it is daunting to choose between them. We've categorized devices by price and performance to help you find the best fit for your needs.
Professional Devices
- Built for 24/7 Performance: These premium devices, priced over $200 USD, are engineered for continuous use.
- Advanced Features: Enjoy automatic on/off scheduling, superior RAM, and robust metal housings.
- Top-Tier Performance: Effortlessly handle 4K videos and heavy animations. We recommend testing before major deployments.
Mid-Range Devices
- Balanced Value and Performance: Priced between $100 - $200 USD, these devices offer great features without breaking the bank.
- Enhanced Reliability: Not designed for 24/7 use, but perfect for moderate workloads.
- Reputable Brands: Consider options from Rikomagic, Minix, and Beelink. Ensure you test performance against your content needs.
Basic Devices
- Budget-Friendly Options: Priced between $20 - $100 USD, these devices are ideal for simple consumer use.
- Simple Content Only: Perfect for displaying pictures and basic videos.
- Performance Testing: Always test these devices with your content to ensure they meet your needs.
We do not recommend specific models in this category due to their limited performance.
How does Our Android Client work?
Our Android client displays Content, Loop, and Schedule. It is a full-screen HTML browser that also allows other functionalities:
- Control the device and the performance of the client application
- Communicate with content inside the Wallboard CMS
- Maintain the system
Content Caching On Android
Our client application stores all components of a piece of content on the device storage and supplies the embedded browser locally. This allows the device to load in the content without an internet connection.
The cache also reduces the network traffic significantly because media files are downloaded to the device only once, and when you display content that includes media, the device will initially load it in from the local storage.
NTP Time Synchronization on Android
NTP time synchronization is used to provide an accurate base for our content synchronization.
NTP (Network Time Protocol) synchronization works automatically if the server (that the device is connected to) has an NTP server. If the server does not have an NTP server, or the connection is lost between the device and the NTP host, then the device will search for other time sources, like Wallboard server system time.
The device requests a new timestamp from the NTP server every 2 minutes to ensure content synchronization is accurate. In theory, it would be enough to synchronize the time only once. However, sometimes the time on Android devices can deviate so it has to be refreshed regularly in order to have the most accuracy.
Does my device need an internet Connection?
Since our application communicates with our server it is mandatory to enable the wifi or an Ethernet connection for communication. However, when the device is successfully registered and caches the Content / Loop / Schedule it can be run in an offline mode.
The below features are unavailable if you run the device in offline mode:
- Background updates
- System time synchronization to a server clock
- Receive any command from the server
Does my device need to be rooted?
It is recommended to run our client application on a rooted device, but it can also be run on non-rooted devices.
The below features are unavailable on non-rooted devices:
- Background Updates
- System time synchronization to a server clock
- Lock down device
- Replace WebView
Demo mode (deprecated since 2.0)
Demo mode is not available after 2.x.x version
DEMO mode can be enabled in the device configuration dialog box.
In DEMO mode the device behaves the same as in DISPLAY mode until it gets a touch event.
This touch event could be global or on a chosen image. Once the touch occurs the device will finish displaying the content.
At this point, the device switches to the default Android Launcher and the user can look into the phone or tablet while the Android Settings (or other selected applications) are disabled. After 30 seconds of inactivity the device continues working in DISPLAY mode.
We also have a lifting module that could be enabled. This feature detects if the device is lifted up and in this case it disables the 30 second timer.