You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 26
Next »
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFzaHJhZiBCaGFudSBLb3RoYXBldGEiLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQXNocmFmIEJoYW51IEtvdGhhcGV0YSIsImxhbmd1YWdlIjoiZW4iLCJ1aUNvbmZpZyI6Int9IiwiZGlhZ3JhbURpc3BsYXlOYW1lIjoiIiwic0ZpbGVJZCI6IiIsImF0dElkIjoiMjEzNTk5Mzg1IiwiZGlhZ3JhbU5hbWUiOiJSREsgSGlnaCBsZXZlbCBhcmNoaXRlY3R1cmUtUkRLLVYtVFYiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiUkRLIFRWIiwidGJzdHlsZSI6InRvcCIsImNhbkNvbW1lbnQiOmZhbHNlLCJkaWFncmFtVXJsIjoiIiwiY3N2RmlsZVVybCI6IiIsImJvcmRlciI6dHJ1ZSwibWF4U2NhbGUiOiIxIiwib3duaW5nUGFnZUlkIjoyMTM1OTg2NTYsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjIxMzYwMjkyNywicGFnZUlkIjoiIiwibGJveCI6dHJ1ZSwic2VydmVyQ29uZmlnIjp7ImVtYWlscHJldmlldyI6IjEifSwib2RyaXZlSWQiOiIiLCJyZXZpc2lvbiI6MSwibWFjcm9JZCI6IjNmYWFhNWZlLWExMmYtNDI3NS1iYTk5LWFhMGRiMjFjZTM0OCIsInByZXZpZXdOYW1lIjoiUkRLIEhpZ2ggbGV2ZWwgYXJjaGl0ZWN0dXJlLVJESy1WLVRWLnBuZyIsImxpY2Vuc2VTdGF0dXMiOiJPSyIsInNlcnZpY2UiOiIiLCJpc1RlbXBsYXRlIjoiIiwid2lkdGgiOiI4MjMiLCJzaW1wbGVWaWV3ZXIiOmZhbHNlLCJsYXN0TW9kaWZpZWQiOjE2NjAwMjgxMDAwMDAsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFzaHJhZiBCaGFudSBLb3RoYXBldGEiLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQXNocmFmIEJoYW51IEtvdGhhcGV0YSIsImxhbmd1YWdlIjoiZW4iLCJ1aUNvbmZpZyI6Int9IiwiZGlhZ3JhbURpc3BsYXlOYW1lIjoiIiwic0ZpbGVJZCI6IiIsImF0dElkIjoiMjEzNTk4ODU1IiwiZGlhZ3JhbU5hbWUiOiJzYW1wbGUiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiUkRLIFRWIiwidGJzdHlsZSI6InRvcCIsImNhbkNvbW1lbnQiOmZhbHNlLCJkaWFncmFtVXJsIjoiIiwiY3N2RmlsZVVybCI6IiIsImJvcmRlciI6dHJ1ZSwibWF4U2NhbGUiOiIxIiwib3duaW5nUGFnZUlkIjoyMTM1OTg2NTYsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjIxMzYwMjkyNywicGFnZUlkIjoiIiwibGJveCI6dHJ1ZSwic2VydmVyQ29uZmlnIjp7ImVtYWlscHJldmlldyI6IjEifSwib2RyaXZlSWQiOiIiLCJyZXZpc2lvbiI6MTAsIm1hY3JvSWQiOiIyYTlkYTc0ZS1iNGE2LTQ1NzQtYWNiMC1jYTJmMjJiY2MwN2UiLCJwcmV2aWV3TmFtZSI6InNhbXBsZS5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiMTAxOCIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTY4MDI1NjY2ODAwMCwiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
RDK TV has all the components that are part of RDK Video profile plus its own TV specific components mentioned in below table.
TV Specific Component Name | Description | RDK Component wiki page |
---|
HDMIInput/CompositeInput | The HdmiInput plugin allows you to control the HDMI Input on a set-top box. The CompositeInput Plugin allows you to control the composite input source on a device. - RDK extensions added to handle HDMI/Composite input ports
- Start, stop and set video rectangle for HDMI/Composite inputs
- Get EDID details, SPD information and supported game features for HDMI inputs
- Supports hotplug, input signal changes, input status changes events for HDMI/Composite
- Video Mode and ALLM change events for HDMI
Thunder API documentation: https://github.com/rdkcentral/rdkservices/blob/main/docs/api/HdmiInputPlugin.md https://github.com/rdkcentral/rdkservices/blob/main/docs/api/CompositeInputPlugin.md | RDK TV HDMIInput/CompositeInput |
MotionDetection | The MotionDetection plugin allows you to control the motion sensors that are available on a set-top box. - Motion Sensors provide more flexibility to power management and enhance user experience.
- Power saver modes can be configured based on user presence.
- New thunder plugin and RDK HAL added for Motion Detection
- Provides APIs to,
- Activate, Deactivate Motion Detection
- Get Motion Sensor details
- Control the active and inactive time period for Motion Detection
- Adjust sensitivity of Motion Detection
Thunder API documentation: https://github.com/rdkcentral/rdkservices/blob/main/docs/api/MotionDetectionPlugin.md | RDK TV MotionDetection |
TV Audio settings | | RDK TV Audio settings |
RDK TV CEC & ARC/eARC | The HdmiCecSink plugin allows you to manage HDMI Consumer Electronics Control (CEC) sink for connected devices. TV CEC Features: - One Touch Play
- Routing Control
- System Standby
- Power Status
- System Audio Control
- ARC Control
- Remote Control Passthrough
TV ARC/eARC Functionalities: - Audio device type detection
- Audio device power state synchronisation
- Audio routing control
- Digital Audio output mode configuration
Thunder API documentation: https://github.com/rdkcentral/rdkservices/blob/main/docs/api/HdmiCecSinkPlugin.md | RDK TV CEC & ARC/eARC |
Picture Settings | - RDK TV Picture Settings feature is implemented via RDK TV Settings thunder service which provides TV applications an interface to change TV picture settings.
- RDK TV Settings provides configurable options to change TV Picture settings based on viewing/picture modes and content format.
- Persists the picture setting values changed by TV applications in a non-volatile area and re applies them on every bootup.
- Provides default values for all picture settings.
- SoC picture quality drivers are responsible for handling content format change, source change and picture mode change events. Apply appropriate picture settings in response to these events
| RDK TV Picture Settings |
TV Settings | - RDK TV Settings like any other thunder module is initialized at cold bootup by the RDK thunder framework.
- Upon initialization it reads and applies the last set picture mode and associated picture settings following customization rules as specified in /etc/tvproduct_config.ini file.
- Once initialised RDK TV Settings thunder module activates itself providing an interface to TV Application for changing picture setting parameters.
- For any changes to picture setting parameters, the TV Application invokes the set thunder APIs and passes the values to be set as parameters. RDK TV Settings thunder module follows the rules set in /etc/tvproduct_config.ini file to apply the value.
- The last set value for any picture setting parameter can be queried by the TV Application using get thunder APIs. The returned value will always be for the current content format being played and current picture mode selected.
- If TV Application decides to reset to default, the corresponding reset APIs can be invoked and TV Settings module will use default values for the product and apply them following the rules set in /etc/tvproduct_config.ini file.
| RDK TV Settings |
Hardware Porting Guide
If you are a SoC or OEM trying to get RDK TV running on your device/platform, please refer the following hardware Porting guide
Porting Guide
Hardware Deployment Guide
If you are an Operator/CE manufacture trying to make an RDK TV deployment-ready, please refer the following deployment guide
Deployment Guide
Available Devices
For details of available SoC reference platforms, White labeled boards and Accelerator devices with RDK TV ported on them, please follow the below link
Available Devices
User Interface
To know about the details of RDK TV User Interface(UI) and how to integrate UI on your device/platform, please follow the below RDK TV UI link
RDK-V TV UI