How to map special remote keys in H200

Introduction

Amino provides each H200 with an Oak remote control. This remote has several keys that can be customized.

Key handling integration

As Global keys will most likely not cover all the needed actions, we provide two different ways of customizing their behavior:

1. Defining Function Keys in the Amino Device Management System (INI parameters);
2. Receiving the global key and handling them directly in APP.

Global key - Define the function

Using a default configuration, your H200 STB will raise the keys as global, which means they will be processed either by AOSP itself or by any foreground APP that can process it.

Here's a list of all the keys available as Global keys:

Receiving the Global Key

In order to receive the global keys, the APP has to have the following:

1. A receiver that implements an intent filter for the intent android.intent.action.GLOBAL_BUTTON;
2. The package ID should be defined in this INI parameter: tvapp.package_id.

Here's an example of the global key receiver intent filter, defined in APP AndroidManifest.xml:

<receiver
  android:name="com.android.tv.livetv.receiver.GlobalKeyReceiver"
  android:exported="true" >
  <intent-filter>
    <action android:name="android.intent.action.GLOBAL_BUTTON" />
  </intent-filter>
</receiver>

Customized key handling

Amino provides the capability of customizing the behavior of a big part of the OAK remote keys. There are three different ways these keys can work:

1. Trigger Deeplink;
2. Trigger an APP, based on package ID;
3. Trigger a specific Activity within an APP;

In order to switch from the default Global key to one of the three options above, the following INI parameters need to be added:

These should then point to one of the three preferred actions, as shown:

More documentation on Deep-links can be found on the Android documentation: https://developer.android.com/training/app-links