Skip to main content

Setting developer mode and usb-debug on the Amino Media Players

Daniel Gonçalves
  • Updated

Introduction

The purpose of this article is to guide the user on how to set developer mode and USB debug on the Amino media player.

 

Prerequisites

This article assumes that basic setup of the devices has been completed and the device is configured to use Orchestrate, USB, or DHCP to receive any necessary configuration settings.

The article also assumes that you understand the use of Amino INI configuration settings and that you can edit and apply INI configuration parameters to your media player.

 

In this article:

Enabling Developer Mode

Android SDK Installation

Using adb keys

Debugging examples

 

Summary

Developer Mode

To enable the developer mode the following parameter is needed to be set:

adb.mode=on

 

Android SDK installation

Windows

  1. Download the Android SDK Platform Tools ZIP file for Windows.
  2. Extract the contents of this ZIP file into an accessible folder (such as C:\platform-tools).
  3. Open the Windows Explorer and navigate to the folder you extracted the contents of the ZIP file.
  4. Open a Command Prompt from the same directory where the ADB binary is present. This can be done by Right-clicking within the folder area and clicking the “Open in terminal” option. (Some Windows 10 users may see “PowerShell” instead of “terminal”).
  5. Enable Developer Mode in your media player.
  6. Find the IP address of your media player and enter the following command to launch the ADB daemon:  adb connect <IP>
  7. On the media player screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you want to avoid seeing that prompt again).

mceclip1.png

 

MacOS

  1. Download the Android SDK Platform Tools ZIP file for macOS.
  2. Extract the ZIP file to an accessible folder (like the Desktop for example).
  3. Open the Terminal.
  4. Navigate to the folder where you extracted the files by entering the following command:             cd /Users/Daniel/Desktop/platform-tools/
  5. Enable Developer Mode in your media player.
  6. Find the IP address of your media player and enter the following command to launch the ADB daemon:  ./adb connect <IP>
  7. On the media player screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you want to avoid seeing that prompt again).

mceclip1.png

 

Linux

  1. Download the Android SDK Platform Tools ZIP file for Linux.
  2. Extract the ZIP file to an accessible folder.
  3. Open a Terminal window.
  4. Enter the following command: cd /path/to/extracted/folder/
  5. Enable Developer Mode in your media player.
  6. Find the IP address of your media player and enter the following command to launch the ADB daemon:  ./adb connect <IP>
  7. On the media player screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you want to avoid seeing that prompt again).

mceclip1.png

 

Some Linux users should be aware that there can be an easier way to install ADB on their computers. The guide above will certainly work for you, but those on a Debian or Fedora/SUSE-based distro of Linux can skip steps 1 and 2 of the guide above and use one of the following commands:

 

Debian-based Linux users can type the following command to install ADB:

sudo apt-get install android-tools-adb

Fedora/SUSE-based Linux users can type the following command to install ADB:

sudo yum install android-tools

 

However, it is always better to opt for the latest binary from the Android SDK Platform Tools release, since the distro-specific packages often contain outdated builds.

Just to cover all of our bases here, users may need to put a ./ in front of the ADB commands we list in future tutorials, especially when they are using the extracted binaries directly from the Platform Tools ZIP. This is something that is likely known by any *nix user (or Windows user running PowerShell) already, but again, we want as many people as possible to understand how to do these tweaks for Android no matter how much of your operating system you know.

 

Using adb keys

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 or MacOS 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 MEDIA PLAYER IP>

Linux or MacOS Terminal:

cd /platform-tools
./adb connect <YOUR MEDIA PLAYER 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 debugging in a production environment should be considered a security risk and we do not recommend this being enabled by default on devices where debugging is not required.

 

Debugging examples

Taking a screenshot

To take a snapshot run the following command on the command line:

adb shell screencap -p /sdcard/screen.png

Then grab the screenshot from /sdcard/screen.png to the current directory of your PC.

adb pull /sdcard/screen.png
 

Screen recording

To start a screen recording run the following command on the command line:

adb shell screenrecord /sdcard/test.mp4

Note: Recording continues until Ctrl-C is hit or the time limit is reached

 

Then grab the video from /sdcard/test.mp4 to the current directory of your PC.

adb pull /sdcard/test.mp4

 

Retrieving the INI parameters

Run the following command on the command line:

adb shell device_param -l

Here is an example output:

C:\Utility\platform-tools>adb shell device_param -l
[rcu.enable_ssu]: [1]
[standby.deep_sleep.enable]: [0]
[system.disable_rescue]: [0]
[endebug]: [1]
[ensight.redirect_server]: [ensight-cmd.aminoengage.com]
[enspect.server]: [https://enspect-svr.aminoengage.com]
[firmware_upgrade.ignore_version_binding]: [1]
[rcu.allow_ota_downgrade]: [1]
[ZZZ99_ENGAGE_INI_VERSION]: [3]
[app.debug]: [1]

 

More debugging examples

For more debugging examples please check the ADB commands list.

 

References 

None

 

 

 

Related articles

Powered by Zendesk