Introduction
The purpose of this article is to guide the user on how to install a CMS application on an Amino media player and to demonstrate the supported methods.
In This Article
Install a CMS Using Orchestrate
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.
Orchestrate
Select the CMS application in your Group
Click the "Add Application" button to select which CMS application you want automatically deployed to your devices that belong to this group.
Select the "Amino-ACME-CMS" application and press save.
If you don't find your preferred CMS application from the list, please contact Amino to publish it into your domain.
Auto-Launch CMS Application on start-up
It is possible to configure an application as the main application which a device will auto-launch when it boots. To use this feature, the tvapp.package_id INI parameter must be set to the application "package_id" or "Application ID", as it is sometimes named.
To find the "package_id" or "Application ID" of the app you wish to run, navigate to the "Manage Android Apps" screen and select the app you would like to auto-launch.
For example, in the screen capture below, the "AminoACME CMS" application has the ApplicationID of "com.aminocom.amino.acmecms".
Now go to the Group Details screen for the Group of which your media player is a member and click on the "Add/Remove Parameters" button then include the "tvapp.package_id" parameter in the list of parameters to be configured and click "Apply".
Add the "Application ID" which you found previously as the value of the "tvapp.package_id" field and press Save.
All H200 media player devices that are assigned to this group will have the Amino ACME CMS application remotely installed and it has been configured to Auto-Start on bootup.
USB
Create a USB image with our Offline Image Creator
Get the image from the Offline Image Creator here, by selecting only the latest available FW and skipping the next 2 steps. Export the image and download the zip file to your PC.
Prepare the USB thumb drive
1. Format a USB thumb drive with FAT32.
2. Unzip all the files from the previously downloaded USBImage.zip to the root directory of the USB thumb drive.
3. Place your CMS application file (.apk) in the root directory of the USB thumb drive. The total size of the APK file should be less than 976MB.
4. On the root directory create the file apk_list.txt and add the file name of your apk file.
ie. CMS.apk (replace CMS.apk with your CMS application name)
5. The root directory of your USB thumb drive will look like this:
6. Finally open the amino_h2xx_usb_upgrade.txt and add the line --apk_list=/udisk/apk_list.txt so it looks like this:
In case you previously added INI parameters and created a channel lineup in the Offline Image Creator the amino_h2xx_usb_upgrade.txt would contain the following lines:
--update_package=/udisk/25.3.2330.7R.zip
--update_ini=/udisk/usb_boot.ini
--update_channel_list=/udisk/zapper_lineup.json
--apk_list=/udisk/apk_list.txt
Flash and install the FW and the CMS application
1. Insert the USB thumb drive into the USB slot nearest to the H200's power adapter.
2. Connect the power adapter to the H200.
3. The H200 should detect the USB thumb drive and start to upgrade automatically without user interaction.
4. Once you see the on-screen prompt confirming the system upgrade was done, remove the USB thumb drive and reboot the H200.
5. After the reboot, the H200 will then install the CMS application and an on-screen message will appear to confirm it.
Please note that you will need an extra reboot for the CMS application to appear as an auto-launch app once it's rebooted.
DHCP
If you are using DHCP with VCI to bootstrap your media players and provide the necessary references to configuration data then it is necessary to edit the INI files which you have deployed and provide a link to the CMS application.
If you would like more information about how to use DHCP with VCI in your deployment please follow this article.
CMS application Deployment
You must firstly configure the device permissions to allow applications to be installed from an unknown source and provide the URL from which the device can download the CMS. Your INI file will therefore require the the following lines:
system.allow_install_unknown_sources="ALLOW_INSTALL_UNKNOWN_SOURCES"
appinstaller.link="<insert here the CMS application's link>"
The CMS Application URL must be reachable from all devices in your deployment so that they can download the CMS when the INI file is updated
Automatically Launch the CMS application
If you wish to launch the CMS application on device boot, add the following line to the INI file:
tvapp.package_id="<insert here the CMS application's id>"
INI file example
# Application Firmware and Version
firmware_upgrade.url=http://<preferred ip and path>/25.3.2022.9R.zip
firmware_upgrade.version="25.3.2022.9R"
# App Parameters
adb.mode="1"
key.link.blue="pkg://com.android.tv.settings?cls=com.android.tv.settings.MainSettings"
system.allow_install_unknown_sources="ALLOW_INSTALL_UNKNOWN_SOURCES"
appinstaller.link="https://<domain>/cms.apk"
tvapp.package_id="com.cms.app"
Reboot the media player for the changes to take effect.
References
None