Introduction

This article will help you create a public and private adb key so the media player does not request access to USB debugging constantly.

Prerequisites

This article assumes that you have completed the basic setup on:

• Android SDK Platform Tools installation
• Activation of the Developer Mode by enabling the adb.mode parameter
• Having a secure HTTP server to store the adb key

Summary

Creating adb keys

1. The adb command generates a private and public key pair.

Open a terminal window and go to the platform-tools folder. Then run the adb command as shown in the example below.

Windows CMD:

cd /platform-tools
adb keygen adbkey

Linux Terminal:

cd /platform-tools
./adb keygen adbkey

This will create a pair of keys, public and private with the names, taken from the previous example:

adbkey.pub (public) and adbkey (private)

2. Host the adb.pub on a secured HTTP server (making sure it is reachable by the media player) and set the adb.key_url INI parameter in Orchestrate or DHCP VCI server as the example below:

You must reboot the media player for the changes to take effect.

Note: If the public key is not hosted in a secured HTTP server, the H200 won't download the key for security reasons.

3. Open the terminal and go to the folder where the private key and the adb are located and run the following commands:

Windows CMD:

cd /platform-tools
adb connect <YOUR H200 IP>

Linux Terminal:

cd /platform-tools
./adb connect <YOUR H200 IP>

4. On the first connection attempt you will have to allow a USB debugging request. After that, and if everything was done correctly, the media player won't prompt the USB debugging dialog box anymore. 

Note: - enabling debug in a production environment should be considered a security risk and we do not recommend this being enabled by default on devices where debug is not required

References

Android SDK Platform Tools