Tizen Display Commands
- 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
Settings for the Xibo for Tizen Player and the monitor itself can be controlled in the Xibo CMS. This can be done by Commands sent directly to the Display or via Tizen Display Profile settings.
This page will explain what Commands can be sent to the Tizen Player and what impact will they have on the Player and monitor.
Commands need to be first created and configured as explained on the Command Functionality page.
Display Commands available for the Tizen Player are very straightforward, as listed below:
Advanced Commands can be sent from the CMS to set specific Monitor Settings for the Xibo for Tizen Player and are created in the same way as all other Commands in Xibo.
Set using the following format:
- backlight 0
- brightness 50
A full list of the available Commands and their ranges is shown below:
|Setting name||Data Type||Explanation and Range|
|backlight||Number||The backlight level of the display. Range: [0–100]|
|contrast||Number||The contrast level of the display. Range: [0–100]|
|brightness||Number||The brightness of the display. Range: [0–100]|
|sharpness||Number||The sharpness of the display. Range: [0–50]|
|hSharpness||Number||The horizontal sharpness of the display. Range: [0–50]|
|vSharpness||Number||The vertical sharpness of the display. Range: [0–50]|
|color||Number||The color saturation of the display. Range: [0–100]|
|tint||Number||The tint of the display. Range: [0–100] Red: 0, Green: 100|
|colorTemperature||Number||The color temperature of the display. Range: [0–100] Warm: 0, Cool: 100|
|dynamicContrast||String||The dynamic contrast level of the display. Range: [“off”, “low”, “medium”, “high”]|
|superResolution||String||The super resolution level of the display. Range: [“off”, “low”, “medium”, “high”]|
|colorGamut||String||Color Gamut of the display Range: [“normal”, “extended”]|
|dynamicColor||String||Dynamic color saturation level of the display. Range: [“off”, “low”, “medium”, “high”]|
|noiseReduction||String||Noise reduction level of the display. Range: [“auto”, “off”, “low”, “medium”, “high”]|
|mpegNoiseReduction||String||The MPEG noise reduction level of the display. Range: [“auto”, “off”, “low”, “medium”, “high”]|
|blackLevel||String||The black level of the display. Range: [“low”, “high”]|
|gamma||String||The gamma level of the display. Range: [“low”, “medium”, “high”, “high2”]|
Please note: This feature is supported from vR201/R107 and later.
It is also possible to send osdlock with true or false values via a Display Command.
osdlock - with this Command you will not be able to access the monitor settings, change volume, brightness etc from the remote control.
It is important to note that Settings applied to a Display Profile will override individually sent Commands.
Scenario: The Display Setting has brightness set to 60, A Command is sent to that Display to set the brightness to 100 At some future point (most likely at the next collection interval) the Display will revert to the original setting applied - brightness 60.
In this case, the best practice to control brightness via a Command on an ad-hoc basis, a preset value in the Display Setting should not be configured.