Versions Compared

Old Version 31

changes.mady.by.user Arun P Madhavan

Saved on

compared with

New Version 32

changes.mady.by.user Arun P Madhavan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Functionality

Plugin

Method

Events

Returns connected audio output ports

org.rdk.DisplaySettings

getConnectedAudioPorts


Returns the current volume level

org.rdk.DisplaySettings

getVolumeLevel


Returns whether audio is muted on a given port

org.rdk.DisplaySettings

getMuted


Adjusts the Volume Level on a specific port

org.rdk.DisplaySettings

setVolumeLevel


Mutes or unmutes audio on a specific port

org.rdk.DisplaySettings

setMuted


How To...

The following section details about few debug steps to confirm some generic issues and doubts when working with an RDK-V stack and this UI.

How to confirm platform key press events is reaching UI

Platform keymap could be differing from the UI keymap which could result in unexpected behaviors or UI not responding to key press events.

In general; UI receives the key press events through webkit browser when user interacts with STB using RCU or connected keyboard.

How to check the browser is able to receive the key events and which keyCode its being received from platform:

  1. Using Controller UI(a.k.a. ThunderUI); activate HtmlApp and load https://keycode.info/ as url. Controller UI is only available on a development build RDK-V image and it can be accessed from a local network connected computer where RDK-V device is connected. Note down the RDK-V deviceIP (Eg: let it be 192.168.1.30). Then from the same network connected computer; open any web-browser and type in deviceIP:9998 in the address bar.
  2. Press any keys and confirm the keyCode being reported by https://keycode.info/.

How to check the browser is able to receive the key events and which keyCode its being received from platform:

How to debug UI not responding to key press events