...
My Apps, App Catalog, Manage Apps tabs now is dedicated for supporting DAC Apps or app-store on a supported device and firmware with provisioned ASMR ASMS Cloud app-store functionality.
On selecting the Apps Icon from left banner; User shall be presented a new page with 3 tabs highlighted with "My Apps" which shall list the list of all installed app bundles on that particular platform. If no installed app bundles are found; user shall be presented with the "App Catalog" tab which will display all available downloadable app bundles from remote server from which user shall be able to install selected app. Installation progress shall be displayed when user interacts with that selected App Icon. After installation competes; that app will be displayed under "My Apps" as well as "Manage Apps" tabs. From "My Apps"; user shall be able to launch the App. To "EXIT" from that app instance; user need to press HOME key which will redirect him to UI HOME page. From "Manage Apps"; user shall be able to uninstall the installed App.
Here is video on Youtube explaining that UI section "https://www.youtube.com/watch?v=ZVDOnWyvvho "
Respective snapshots are listed below for reference.
- Note: "App Catalog & Manage Apps" are supporting only the minimal LISA API features. In future it will have the extended features of details of apps, view memory usage etc. Also the App bundle hosting shall not be covered in this section as it is not under the scope of UI.
Device configuration for fetching ASMR DAC App Catalog details:
UI supports ASMR Cloud based app store if proper configuration is available. Firmware need to have the following JSON format with proper details matching below template.
| Code Block |
|---|
|
root@raspberrypi4-64-rdk-android-mc:~# cat /opt/appmanagerregistry.conf
{
"app-catalog-cloud": {
"url": "<ASMS Cloud Base URL>",
"firmwareVersions": [
{
"platform": "rpi4",
"ver": "1.0.0-aabbccddeeffgghhiijjkkllmmnnooppqq112233-dbg"
},
{
"platform": "ah212",
"ver": "1.0.0-aabbccddeeffgghhiijjkkllmmnnooppqqrrsstt-dbg"
}
]
}
} |
Note: Each platform should configure appmanagerregistry.conf (above template) with proper "url", "platform" and "ver" keys since those are platform specific.
auto discovery of Cloud microService that provides App catalog ASMS :
Information about DAC 1.0 can be found here DAC - Downloadable Application Containers. Information on how to build and publish a DAC1.0 App to store is here HOWTO build App with DAC SDK, cloud publish and run on VA
The UI should auto discover the URL to the Cloud microService that provides the list of Apps and its metadata (ASMS is the cloud microservice). UI is automatically discovering by requesting config_url to LISA MW plugin (which on it turn has configured that in its thunder plugin config. Default config should automatically bring you to ASMS and is defined here ) See also info in link.
Not all VA platform and firmware versions, you will be able to download and run DAC1.0 apps. Only Appbundles for specific platforms and dacPlatformFWCompatibleBundleVersions are actively supported
By default following combinations are supported, see link. The technical information behind that is explained here.Reference: https://github.com/stagingrdkm/lgpub/blob/master/dac/labci/dactest.py#L36 shall have the ASMS Cloud Base URL and matching platform VER.
Featured Video Player
The redesigned video player utilizes UVE implementation and has kept the minimal controls such as a progress bar with pause and play buttons. Various player controls are detailed below.
...
- Navigation
- The overlay screen has timeout of 5 sec. You can bring up the overlay by pressing Arrow UP key.
- Enter to pause and play.
- Back and Home key will take you back to home screen from Featured video player instance.
Settings Screen
Settings screen has several new options which allows user to interact with device capabilities.
...
Miracast Feature:
- Turn on location and Wi-Fi on your mobile device, ensuring it is not connected to any SSID.
- Open the "Cast" option on your mobile—it will start searching for available devices.
- You should see a device named "Living Room" in the list.
- Tap on "Living Room" from your mobile. This will trigger the onClientConnectionRequest() event in the logs, and a Miracast notification page will appear on the TV. This page will display your mobile phone details along with "Accept" and "Deny" buttons and a 30-second timer.
- If you click "Yes", the mobile screen will be mirrored on the TV, and the onStateChange event will be logged with the corresponding state.
- If you click "No", you will be redirected back to the RDKUI home page.
- If you disconnect the Cast option from your mobile, the RDKUI home page should appear again.
- In case of a failure, a failure screen will be displayed, showing the error code and reason.
Additional Steps - Launching YouTube while Miracast is playing:
While the Miracast feature is in the playing state, execute the following CURL command:
| Code Block |
|---|
curl -X POST http://127.0.0.1:9998/jsonrpc -d '{"jsonrpc":"2.0","id":3,"method":"org.rdk.RDKShell.1.generateKey","params":{"keys":[{"keyCode":115,"modifiers":[],"delay":0.2,"callsign":"ResidentApp","client":"ResidentApp"}]}}' |
- The UI should stop the Miracast screen and launch YouTube.
- Handling Home key press while Miracast is playing: the the Home key is pressed while Miracast is in the playing state, the UI should stop the Miracast screen and return to the RDKUI home page.
Image Removed
...
Image Added
...
Key Mapping
The version 3 UI supports a configurable keymap. Below lists the general functionality and keycode of keys. Detailed information of the default keycode mappings can found here in Keymap.js.
...
