RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
UI initiates Bluetooth scan for HID profile to connect and pair with at this point with a configured time-out. How to put the RCU in Bluetooth pairing mode is dependent on the RCU design which is not within UI scope.
UIv3.9 onwards Navigator UI will prefer to use Remote Control plugin on supported platforms to pair with RCU instead of classic Bluetooth plugin. RCU Pairing using RemoteControl pluginOnly one plugin shall be used to onboard the RCU - if preferred Remote Control plugin is available it will not fall back to use Bluetooth plugin to scan and pair with RCU.
...
Note: this feature of automatic RCU pairing requires RCU model support integrated with BLERCUDaemon at platform firmware build time and RemoteControl plugin enabled. If your RCU and platform does not support this feature yet, you can still pair your RCU through the using the Classic Bluetooth plugin based RCU pairing through "Settings" menu detailed in later section - "Pair Remote Control".
TBD
The updated UI uses classic Bluetooth plugin to pair with the very first HID input device appearing in the scan response.
The UI currently supports two languages, English and Spanish. New language support can be integrated with The UI currently supports two languages, English and Spanish. New language support can be integrated with proper resource files added along with the defaults as detailed in upcoming sections. UI will reload to refresh the entire settings and during that time user may see display going blank and a spinner appearing for the reload time.
...
User can access the device settings by interacting with the Settings icon which will redirect him on to dedicated settings screen. Time display is also available in the home UI.
Preview Mode: Navigator UIv3.9 supports basic Alexa skills on aligning to Alexa Voice Integration Manual on a supported platform using Voice Control plugin. This implementation now relies on Alexa provided generic OOBE implementation for authenticating the users. Upcoming navigator UI updates shall include the authentication pages into itself.
Alexa's OOBE will be activated only when user is at HOME page and internet is available. User shall have an option to disable this support by selecting "Skip" button. Later onwards UI shall deny all the Alexa related notifications until a Clear Cache or Factory reset is done through the UI.
UI shall display following Alexa SDK status if enabled and authenticated. The following screens shall time out itself without any need for user interaction.
TBD Alexa Status screens
...