How does it work?



  • 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

On this Page:

  • .Once initialised RDK TV Settings thunder module activates itself providing an interface to the 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 the current picture mode selected.
  • If the TV Application decides to reset to default, the corresponding reset APIs can be invoked and the TV Settings module will use default values for the product and apply them following the rules set in /etc/tvproduct_config.ini file.


TV Settings Future


  • RDK TV Settings will be merged with RDK Display Settings as one RDK thunder implementation named RDK Control Settings.
  • RDK Control settings will no longer have product-specific customization capability. It will be handled either in the TV Application as business rules or TV Settings HAL as platform specific customization.
  • RDK Control settings will expose thunder APIs for picture settings parameters that can be modified for any TV picture mode, any content format(SDR/HDR/DV) and any sources(HDMI, Composite, IP etc.,)
  • RDK Control settings to be more generic, more scalable, easier addition of features, standardized API formats, standardized persistent model and easy maintenance.


Useful Link



  • No labels