Android 14
Recommended Test Cases and Deployment Guidance
Recommended Test Cases
Partners are encouraged to complete the following validation activities before deploying Android 14 into production environments.
1. Application and CMS Compatibility
Validate that all applications used in your deployment continue to function as expected on Android 14.
Recommended checks:
- Confirm CMS compatibility with Android 14.
- Validate zero-screen applications.
- Validate customer applications and web applications.
- Confirm application launch, navigation, configuration, and recovery behaviour.
- Review any Android 14 platform behaviour changes that may affect applications.
- For applications targeting newer Android SDK versions, confirm manifest settings such as android:exported are correctly defined.
2. Playback and Media Validation
Android 14 includes updates to decoder libraries and media framework components. Partners should complete playback regression testing across their typical deployment scenarios.
Recommended checks:
- Live playback validation.
- VOD playback validation.
- Playback across commonly used codecs.
- Playback across required streaming formats.
- RTSP playback validation.
- Multicast playback validation.
- Low-latency stream playback validation.
- Subtitle validation.
- Multi-language audio validation.
- Trick play validation, including pause, resume, rewind, and fast-forward.
- Multiple video view scenario validation.
- Instance switching between cached streams.
3. Lifecycle and Recovery Testing
Validate expected behaviour across common operational lifecycle scenarios.
Recommended checks:
- Standby and resume.
- Device reboot and recovery.
- Network disconnect and reconnect.
- Background-to-foreground transitions.
- Application restart after interruption.
- Playback recovery after network loss.
- Long-duration playback stability.
4. Network and Security Validation
Partners should validate network and certificate behaviour on Android 14.
Recommended checks:
- HTTPS/TLS connectivity.
- Certificate validation.
- Public CA trust validation.
- Connectivity to CMS platforms and backend services.
- Wi-Fi and Ethernet network behaviour.
- Any customer-specific network authentication or security requirements.
5. Amino API Regression Testing
For deployments using Amino APIs, regression testing is recommended to confirm compatibility after the Android 14 OS upgrade and media framework migration.
Recommended checks:
- Video Service API compatibility.
- JSAPI compatibility.
- EELM API compatibility.
- Playback control behaviour.
- Device management and reporting behaviour.
- Any partner-specific API integrations.
6. Upgrade and Rollback Testing
Partners should validate upgrade and rollback procedures before production rollout.
Recommended checks:
- Upgrade from Android 12 to Android 14.
- Confirm device configuration is retained after upgrade.
- Confirm applications and services start correctly after upgrade.
- Validate rollback to Android 12 firmware version 25.6.2610.6R
- Confirm factory reset behaviour after rollback.
- Confirm rollback is not attempted to unsupported versions earlier than Android 12.
Deployment Guidance
Android 14 should be deployed using a controlled rollout approach. Partners should complete validation before upgrading customer production environments.
1. Pre-Deployment Planning
Before deployment, partners should:
- Confirm the target devices are supported.
- Review Android 14 release notes.
- Review known issues and limitations.
- Complete application and playback validation.
- Confirm customer upgrade windows.
- Confirm support and escalation processes.
- Ensure rollback requirements are understood.
Supported devices:
- H200
- H200W
2. Pilot Deployment
A pilot deployment is recommended before wider rollout.
Recommended approach:
- Select a small group of representative devices.
- Include devices using typical customer applications and playback workflows.
- Monitor playback, application behaviour, network connectivity, and remote management.
- Confirm no critical operational issues are observed.
- Capture feedback before wider deployment.
3. Production Rollout
Once pilot validation is complete, partners can plan a phased production rollout.
Recommended approach:
- Roll out in controlled batches.
- Avoid upgrading all customer devices at the same time.
- Monitor device health and playback performance after each batch.
- Confirm support teams are ready to respond to any customer issues.
- Keep rollback procedures available during the rollout window.
Android 14 production firmware will follow Amino’s standard firmware distribution process and will be delivered through the Amino Orchestrate server.
4. Post-Deployment Verification
After deployment, partners should verify:
- Device upgrade completed successfully.
- Applications launch and operate correctly.
- Playback functions as expected.
- CMS and backend connectivity is working.
- Remote management functions are available.
- Network connectivity is stable.
- No unexpected certificate or TLS issues are present.
- Customer workflows continue to operate as expected.
5. Rollback Guidance
Rollback is supported back to Android 12 firmware version 25.6.2610.6R.
Important notes:
- Rollback to versions earlier than Android 12 is not supported.
- A factory reset is required after rollback.
- Partners should confirm rollback procedures during evaluation or pilot testing before production rollout.
6. Support and Escalation
Partners requiring support with Android 14 evaluation, testing, or deployment planning should contact Amino through the Partner Portal or the nominated Android 14 support contact.