This guide aims to assist customers in adding the Patient Entertainment app to their Android TV devices. It requires familiarity with your organization's device management software and sideloading of APK applications.
Before you begin, ensure your company meets the following requirements.
Requirements
Swank provides the Patient Entertainment Android APK file for direct distribution (not through Google Play).
Supported Devices: Your organization is using one of the Supported Android TV Devices listed below:
Device Management Software: Each OEM provides its own management platform or installation tool for sideloading APKs.
Device ID Requirement: Each device must be registered with Swank using its DeviceID (MAC Address or Serial Number, depending on the OEM)
-
Network Requirements:
Ensure your devices have open network access to the following domains and IPs, plus the endpoints for your device management platform.
| Domain / Service | Notes |
|---|---|
*.swankmp.net
|
20.221.242.164, 12.38.100.99, 12.38.100.75, 71.14.206.75 |
cdn.swankidc.com
|
See Fastly IP list |
swankcontentuseast.blob.core.windows.net
|
See Microsoft IP ranges |
*.easeltv.com
|
Easel TV Platform |
*.suggestedtv.com
|
Alternative domain for Easel TV Platform |
*.mux.com
|
Mux video streaming services |
*.litix.io
|
Mux analytics services |
*.sentry.io
|
Error reporting and monitoring |
android.clients.google.com
|
Google Play Services core; may be contacted by the Android OS on GMS-certified devices |
imasdk.googleapis.com
|
Google IMA SDK; not active in patient entertainment configurations |
Please also verify the device-specific requirements. The domains above are required by the Patient Entertainment app itself and apply to every deployment. Your device management platform needs additional network access of its own, which differs by OEM. Before submitting a firewall change request, review Supported Devices and Device Management Requirements below and include the entries for the platform you deploy.
Supported Devices and Device Management Requirements
Each OEM supplies its own management platform for sideloading the APK and managing devices, and each platform has its own network endpoints. Find your OEM in the table below, then open the matching section for its device management requirements. If you deploy a single OEM, the other sections do not apply to you.
| OEM | Models / Product Line | Form Factor | Required DeviceID | Management Platform |
|---|---|---|---|---|
| Amino | H200, H200w | Set-top box | Serial Number | Orchestrate (requirements) |
| Lincata | LincTV 01 | Set-top box | MAC Address | LincTV (requirements) |
| PDi | A-C & A-C2 series | Smart TV | MAC Address | GENiO (requirements) |
| PDi | TVB series | Set-top box | MAC Address | GENiO (requirements) |
Endpoints in the sections below are owned and maintained by each OEM. Where a vendor publishes its own network requirements document, that document is the authoritative source and should be attached to firewall change requests.
Amino H200 / H200w — Orchestrate
Amino publishes a full network requirements document: Orchestrate Network Requirements. The table below lists the endpoints required for Orchestrate to manage your devices.
| Hostname | IP | Port | Protocol | Purpose |
|---|---|---|---|---|
orch-acs.aminoengage.com |
18.193.34.170 | 7743 | TCP (HTTPS) | TR-069 device management channel |
ensight-cmd.aminoengage.com |
Resolved by Amino | 443 | TCP (HTTPS) | Redirects each device to its assigned command server |
orch-logfile.aminoengage.com |
3.77.100.119 | 10446 | TCP (HTTPS) | Device log upload |
files.amino-orchestrate.com |
18.193.34.170 | 443 | TCP (HTTPS) | Firmware and application package download |
gcs.amino-orchestrate.com |
35.227.212.246 | 80 | TCP (HTTP) | Firmware download |
orch-stun.aminoengage.com |
18.198.29.184 | 3478 | UDP (STUN) | NAT traversal for device connections |
connectivitycheck.gstatic.com |
Google ranges | 80 | TCP (HTTP) | Android connectivity check. Blocking this can leave the device reporting no internet access. |
www.google.com |
Google ranges | 443 | TCP (HTTPS) | Android connectivity check |
Administrators who manage Orchestrate from a workstation browser also need access to the Orchestrate web console at webapp.amino-orchestrate.com over port 443. This is workstation traffic rather than device traffic, so it is often already permitted by a standard web policy.
Lincata LincTV 01 — LincTV
| Domain / Service | Port | Notes |
|---|---|---|
*.linctv.co |
443 | Device enrollment, kiosk configuration, application deployment, and status reporting. Each organization is issued its own subdomain, so the wildcard entry covers both the device endpoint and the management console. |
PDi A-C, A-C2, and TVB series — GENiO
| Domain / Service | Port | Notes |
|---|---|---|
genio.pdiarm.com |
443 | GENiO cloud management for A-C, A-C2, and TVB series devices. Used for the management console, device check-in, and application installation. |
For GENiO configuration specific to the Patient Entertainment app, see Patient Entertainment TV App: GENiO (PDi) Installation Settings.
Step 1. Obtain the APK
Contact your Swank Account Manager to obtain the Patient Entertainment APK file.
Store the APK securely within your IT organization's deployment environment.
Step 2. Install the APK
-
Use your device vendor's management software, as listed in Supported Devices and Device Management Requirements above:
Amino → Orchestrate
Lincata → LincTV
PDi → GENiO
-
Each platform may have its own side-loading or bulk installation procedure. Refer to your OEM's documentation for details. Some device-specific guides below:
Some platforms require the app Icon separately. Please use the following Icon:
Step 3. Gather DeviceIDs
Each device must be registered with Swank before it can connect to Patient Entertainment.
-
Depending on OEM:
Amino → Serial Number
Lincata → MAC Address
PDi → MAC Address
Export a list of DeviceIDs from your device management system.
Format:
File type:
.xlsx(Excel) or.csv(Comma-Separated Values)-
Include:
DeviceID (required)
Device name, location, or room number (optional but recommended for support identification)
Step 4. Send DeviceIDs to Swank
Send your compiled DeviceID list to your Swank Account Manager.
Swank will register the devices against your organization's Patient Entertainment app license.
Step 5. Confirm Installation
After Swank confirms device registration, open the Patient Entertainment app on one of your devices.
Verify it connects successfully to your content catalog.
Step 6. Complete!
Your Android TV devices are now enrolled and ready to deliver Patient Entertainment to your users.
Comments
0 comments
Article is closed for comments.