Summary

This article outlines the steps to set up and remotely install an Android AOSP CMS Application on your H200 media player device.

Important note: A "fake" CMS application called "Amino ACME CMS" is referenced for the purposes of this article. 

Preconditions

• An Amino Orchestrate Account with Admin privileges
• At least one Amino H200 Media Player device
• Your own Android AOSP CMS application or existing Amino Supported CMS Application (.apk or .aab file)

Uploading and Deploying an Amino Supported CMS Application

Please contact Amino Support to confirm if the CMS application you would like to install on your H200 is already in Orchestrate for quick and easy deployment. 

We will then publish the Android Native Application to your Orchestrate account and then follow the steps from: "Add Android Application to your Group".

Registering, Uploading, and Installing a New CMS Application

Signing Certificate Fingerprint Registration

In order for a new CMS application to be uploaded to the Amino Orchestrate platform, we require the "fingerprint" of the Android application's signing certificate to be registered within our system.

This "fingerprint" can be obtained with the command line application "keytool" normally distributed within the Java JDK distribution.  Examples follow below:

keytool -printcert -jarfile amino-acme-cms.apk

Outputs:

$ keytool -printcert -jarfile amino-acme-cms.apk 
Signer #1:

Signature:

Owner: CN=francis reader
Issuer: CN=francis reader
Serial number: 107e5e83
Valid from: Tue Oct 11 10:47:15 EDT 2022 until: Sat Oct 05 10:47:15 EDT 2047
Certificate fingerprints:
SHA1: EA:D3:CC:E5:EC:31:28:47:6E:16:FC:F3:68:A0:A4:95:DF:27:0B:86
SHA256: 5C:F1:11:52:5A:A1:AE:B7:61:34:DE:F8:B1:A7:98:B4:20:C8:62:51:57:26:9F:F7:DD:CD:9F:E1:DA:CB:9E:E2
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions:

#1: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: 3F 3E 4D 33 1C F4 DB 25 F3 C7 9A 9C E0 02 7D BB ?>M3...%........
0010: 81 D6 DC B5 ....
]
]

Other examples of how to extract the SH1 fingerprint can be found in this "stackoverlflow" article: https://stackoverflow.com/questions/15727912/sha-1-fingerprint-of-keystore-certificate.

The highlighted SHA1: line in BOLD is the information to pass to Amino. 

Once you have the SH1 fingerprint, please contact Amino support with a request to register the application in Orchestrate which will then allow you to upload your application.

Creating a Placeholder for your Application

In the left-hand menu select "Manage Android Apps" and then click on the "Create Application" button.

You will be prompted to enter the placeholder name (Application Name) for your CMS Application. This does not need to be the exact name or PackageID name, but the general name you will use to refer to the application.

Upload Android Application into Placeholder

Click on the "Upload APK" button and then the "Choose File" button and follow the dialog prompts to navigate and upload your APK from your PC. 

Then click the "Upload" button to upload the APK file to Orchestrate.

If there are any errors on upload please contact Amino Support. These would usually be related to the Signing "fingerprint" not being registered or the APK is not signed.

Your CMS Android Application has now been uploaded to Orchestrate and is automatically published to your domain. It is now available for you to add to your groups to remotely install on your H200 media players.

Add Android Application to your Group

This article does not cover the general setup and configuration of your device's Groups as that is covered in other articles and the Orchestrate User Manual. These sections focus on configuring your group to include your CMS Application.

If you have just added a new Android CMS application or Amino has published an existing supported CMS Application to your Orchestrate "domain", you can click the "Add Application" button to select which Android applications you want automatically deployed to your devices that belong in this group. 

From the picture above, the "Amino-ACME-CMS" application has been added and published into this group and is set to "Install".

The "unchecked" checkbox shows the statistics for which version of the app installed will not be shown in the Group Dashboard. Check it if you would like to gather those statistics. 

Auto-Launch / Zero-screen CMS Application on Bootup or Resumption from Standby

One of the enhanced features of the H200 media player is for an application to be nominated to be the main application in which the device will auto-launch (or zero-screen it is sometimes called). 

For an application to use this feature, its "package_id" or "Application ID", as its sometimes named, needs to be obtained and pasted into the "tvapp.package_id" parameter. The "package_id" or "Application ID" can be obtained by navigating to the "Manage Android Apps" and selecting the app you want to auto-launch.

See below for the article's example, the "AminoACME CMS" application has the ApplicationID of "com.aminocom.amino.acmecms". 

Click on the "Add/Remove Parameters" and include the "tvapp.package_id" param to your list of parameters to be configured and then click "Apply".

Add the "Application ID" to the "tvapp.package_id" field. See below for the example "com.aminocom.amino.acmecms".

Finishing Up.

All H200 media player devices which are assigned to this group will have the Amino ACME CMS Android application remotely installed and it has been configured to Auto-Start on bootup/resumption from standby.