Before the Terminology: The Acceptance Decision
A widespread belief in video-on-demand hardware is that the decisive specification is the chipset name. That is wrong. A processor can pass a laboratory benchmark and still fail in service because firmware, memory, DRM, output timing, thermal behavior, or factory evidence does not match the deployed service.
Treat every candidate as a repeatable acceptance target, not a catalog entry. For an android tv box checklist, establish whether the platform decodes the actual service profile, runs the intended Android build, sustains the workload, acquires the required DRM entitlement, exposes the required interfaces, and matches a controlled golden sample. The canonical RK3568 Android Box Checklist for Procurement provides the broader procurement sequence; this article concentrates on VOD engineering acceptance.
A purchase order should identify an unambiguous hardware configuration, fixed software baseline, codec and DRM test matrix, interface requirements, and objective pilot sign-off criteria. “Latest,” “optional,” and “to be confirmed” belong in an exception register, not the production specification. A platform capability is not a qualified configuration until the fitted option and its evidence are named.
Decoded video is not necessarily playable video. A 4K decoder declaration does not establish a 4K output mode; Widevine L1 does not establish a working multi-DRM service; Wi-Fi 6 does not guarantee stable delivery; and AOSP does not automatically provide an operator launcher, middleware, management policy, or update path. Each requires an acceptance line.
Evidence must identify the serial number, hardware revision, software image, service profile, and result. Otherwise it cannot be reproduced during a second purchase order or supplier change. This android tv box checklist should be a controlled document: every candidate receives pass, fail, or open status, while each open item has an owner, required evidence, and deadline.
Verification You Can Ask for on Paper
Factory verification should form a traceable sequence from component control to pilot sign-off. The objective is not merely visual inspection of assembled units; it is to show that deviations are detected before they reach service.
- Lock the build Record board revision, SoC, RAM/ROM combination, Android build, firmware identifier, bootloader state, middleware version, and approved peripherals.
- Control surface-mount assembly Retain SMT records, AOI results, component-lot traceability, and the approved bill of materials.
- Verify boot and interfaces Test display, Ethernet, Wi-Fi, Bluetooth, USB, audio, storage, remote input, power, and recovery against the accepted configuration.
- Age the assembly Apply the defined burn-in or aging process and correlate failures to serial numbers, test stations, operators, work orders, and firmware revisions.
- Run dark-room validation Check the approved display condition, image rendering, interface behavior, and repeatability.
- Audit the evidence Review sample records, rejected units, corrective actions, and application of the same gate to the production lot.
Evidence rule
Accept evidence only when it identifies the tested configuration and unit or lot. A capability declaration without traceability is not a qualification record. Confirm process details or configuration options against the production datasheet.
Add a functional gate for VOD. Install the target client, play representative assets, confirm the output format and frame rate, exercise the DRM path, and record network behavior. The title set should include the operator’s actual codec ladder, DRM combinations, ad-insertion modes, catch-up windows, and live-to-VOD transitions. Test audio separately: a valid video path can conceal wrong HDMI, S/PDIF, or analog-audio routing.
Define whether the factory is assembling an Android TV box or qualifying a complete VOD appliance. Assembly evidence covers soldering, boot, interfaces, and aging. Service acceptance adds playback, licensing, middleware integration, updates, and the operator’s entitlement flow. A full commercial-title test on every unit may be impractical, so distinguish daily line checks from statistically sampled title checks and periodic regression cycles.
For a catch-up-VOD pilot, the line test can verify boot, Ethernet negotiation, HDMI output, remote input, and a short unencrypted asset. A sampled test should use a protected operator title, representative bitrate, expected audio format, actual licence server, and forced network interruption. Record why the title is representative, which units were selected, the pass threshold, and the action following failure. This prevents one convenient laboratory asset from becoming the entire acceptance basis.
Firmware recovery requires its own gate. A device may play normally after a clean boot but fail after an interrupted application update or corrupted configuration. Document the trigger, expected state, recovery time, network dependency, and whether entitlement data survives. Recovery is part of service availability, not a convenience feature.
This android tv box checklist should distinguish three evidence levels: process evidence proves a control exists; lot evidence proves it ran on the delivered population; configuration evidence proves the tested unit represents the ordered product. A factory may satisfy the first two while failing the third if the golden sample differs from the production bill of materials. Require all three before releasing a deployment lot.
Entry Tier versus Commitment Tier: Price the Differences
An entry configuration minimizes hardware and qualification cost. A commitment configuration pays for capacity, interface choices, and program evidence across a larger deployment. Neither is inherently better; the error is assigning commitment-tier operating assumptions to an entry-tier product.
| Decision area | Entry tier | Commitment tier | Procurement consequence |
|---|---|---|---|
| Memory | Lower RAM/ROM combination | Larger or selected family option | Specify the exact fitted combination, not the family ceiling. |
| Ethernet | 100M as listed | Selected 1G option where supported | Match access-network traffic and installation cabling. |
| DRM | Listed service may be optional | Named implementation with title-level evidence | State the production configuration and licence flow. |
| Decoding | Common service profile | Complete operator ladder | Compare codec, profile, level, resolution, and frame rate separately. |
| Factory stage | Component and boot verification | Pilot-batch functional sign-off | Contract the evidence and defect-containment process. |
| Software baseline | Generic platform acceptance | Frozen middleware and upgrade baseline | Identify every binary and configuration by version. |
The entry tier fits a narrow service profile, controlled deployment, and accepted memory or connectivity constraints. The commitment tier becomes relevant when application updates, background services, analytics, higher-bitrate delivery, or long operating cycles can expose storage, RAM, or thermal limits. These are engineering configurations, not universal product rankings.
A frequent quotation error compares headline platform families while omitting fitted RAM/ROM, optional Ethernet speed, DRM configuration, or USB arrangement. The quotations then describe different products. Require each quotation to enumerate these lines and identify standard items, selected options, and changes.
Hidden engineering work also belongs in the comparison. An entry-tier request may use an existing operator image and limited title matrix. A commitment-tier request may require a launcher, middleware adaptation, device enrollment, broader burn-in, site testing, and a larger regression suite. These activities are qualification costs even when the SoC remains unchanged.
Price each consequence. A fixed 100M Ethernet can simplify access-network validation but constrain concurrent traffic. Larger RAM/ROM can provide application headroom but adds a controlled variation. Optional DRM can meet a future catalogue requirement while adding licence, content, and display testing. The relevant difference is therefore not only hardware; it is the number of tests and failure modes the buyer owns.
The android tv box checklist should also name a “configuration owner.” The manufacturer owns hardware and factory records; the platform integrator may own middleware; the operator owns entitlement infrastructure; the installer owns display, network, and site integration. Optional features need an owner before release, especially where the accepted sample and production delivery can diverge.
For an editorial view of control depth, DataMax uses a qualitative planning scale rather than measured production data.

The same figures, in searchable form:
| Stage | Editorial score |
|---|---|
| Requirements only | 25/100 |
| Requirements plus target price | 46/100 |
| Approved golden sample | 74/100 |
| Pilot batch sign-off | 91/100 |
Source: DataMax editorial team, qualitative planning scale (0-100), not audited or measured data.
The Mechanism Behind the Specification: Decode, Licence, Connect, Control
Video playback has four distinct layers: media decoding, output timing, DRM entitlement, and application orchestration. A VOD acceptance checklist must separate them because one can pass while another fails.
Decode and output. Codec support is defined by codec, profile, level, bit depth, resolution, and frame rate. AV1 Main Profile Level 5.1 at 4K60 is not interchangeable with 4K120. The processor may decode frames faster than the selected output mode, but the HDMI mode, display, television, scaler, and player configuration must form a valid chain. A device may advertise 4K while its decoder is limited to 4K30. “4K” alone is not an acceptance criterion.
DRM. Widevine L1, PlayReady, HDCP, Dolby Vision, and DTS describe different parts of the protected-content chain. Widevine L1 and PlayReady concern secure-client and licence mechanisms; HDCP protects content over a display path. Dolby Vision and DTS involve format, display, device, and content compatibility. Request a matrix showing the application, device, stream, licence server, output mode, and result for every required combination. “DRM supported” does not identify a qualified service configuration.
Connectivity. Ethernet is predictable for fixed installations, while Wi-Fi 6 may suit flexible deployments. Relevant variables include negotiated rate, signal strength, contention, multicast behavior if used, power management, and the access-network profile. Bluetooth and Wi-Fi coexistence, USB peripheral behavior, and remote pairing also require acceptance tests.
Control and update. AOSP Android 11 or Android 14 identifies a base operating-system generation, not the operational control architecture. Depending on the program, control may use the Android Management API, operator middleware, an MDM platform, TR-069, or a vendor-specific update service. The android tv box checklist should cover enrollment, policy delivery, application deployment, update policy, rollback, diagnostics, and recovery. A device that streams but cannot be enrolled is not deployment-ready.
| Layer | Specification evidence | Runtime evidence | Primary failure owner |
|---|---|---|---|
| Decode/output | Named codec profile, level, resolution, frame rate | Representative title playback with frame and output capture | SoC, firmware, display chain |
| DRM | Named implementation and optionality status | Licence acquisition and protected playback by service | Device build, licence infrastructure, content |
| Network | Interface speed, wireless generation, antenna configuration | Target-site test with target access network | Hardware, radio configuration, network |
| Operations | Management and update architecture | Enrollment, policy, upgrade, rollback, recovery | Software integration, operator |
The mechanism is sequential: secure boot and the system image establish a trusted platform; the VOD application receives the selected stream; the decoder produces frames; the display path negotiates an output mode; DRM binds entitlement to playback; and the management layer maintains configuration. Each arrow is a test boundary.
A valid licence request can fail because DNS or routing differs. Decoded frames can be dropped because the HDMI mode is unsupported. A display can negotiate 1080p despite 4K decoding. An update can erase middleware settings. Require the end-to-end result and record the intermediate boundary that failed.
Output timing requires separate decisions. Decode capability establishes what the device can process; the selected display mode establishes what is transmitted; the application or scaler establishes what is seen. Acceptance records should identify the negotiated mode rather than copying a datasheet maximum into the report. This exposes a 4K-capable device operating at a lower mode and identifies whether the cause is application policy, firmware, EDID, cable, display, or network.
The Platform Shortlist with Datasheet Values
The following DataMax options support comparison across base Android versions, memory families, decoder targets, and interface options. Values are limited to the supplied product facts. Confirm every optional item against the production datasheet and purchase order.
| Model | SoC and CPU | OS | RAM/ROM | Decode | DRM | Ports and connectivity |
|---|---|---|---|---|---|---|
| DM21P | Amlogic S905Y4, quad Cortex-A35 | AOSP Android 11 | 2GB / 8GB (4GB; 16/32/64GB optional) | AV1 [email protected], VP9/H.265 4K@60, H.264 4K@30 | Widevine L1 / PlayReady / HDCP 2.2 optional | HDMI 2.0b out x1, USB2.0 x2, TF, S/PDIF, 3.5mm AV, RJ45 100M, Wi-Fi6 2x2 + BT5.4, DC 5V/2A |
| DM21S | Amlogic S905Y5, quad Cortex-A55 | AOSP Android 14 | 2GB / 16GB (2/4/8GB; 16/32/64GB optional) | AV1 / H.265 [email protected] 4K@60 | Widevine L1 / PlayReady optional; Dolby Vision/DTS | HDMI 2.0b out, S/PDIF, AV, USB2.0 x2, TF, RJ45 100M (1G optional), Wi-Fi6 2x2 + BT5.4 |
| DM21T | Amlogic S905X5, quad Cortex-A510 (ARMv9) | AOSP Android 14 | 4GB / 64GB (family options) | H.266/VVC [email protected] 4K@120, AV1/VP9/H.265 4K@120, AVS3 4K@120, H.264 4K@60; inline AI-SR | Widevine L1 / PlayReady optional | HDMI 2.0b out (no HDMI in), USB2.0 x1 + USB3.0 x1, TF, S/PDIF, AV, RJ45 100M (1G opt), Wi-Fi6 + BT5.4 |
| DM22Q | Amlogic S905X5M, quad Cortex-A55 up to 2.5GHz | AOSP Android 14 | 4GB / 64GB (2/4/8GB; 16/32/64GB optional) | AV1/H.265 L5.1 4K@60; inline AI-SR (no NPU TOPS stated) | Widevine L1 / PlayReady optional; Dolby Vision/DTS | HDMI 2.0b out, USB2.0 x2, TF, S/PDIF, AV, RJ45 100M (1G opt), Wi-Fi6 2x2 + BT5.4 |
DM21P is positioned for 4K IPTV and operator middleware set-top-box work. Its 2GB / 8GB base and optional memory combinations make the fitted bill of materials especially important. DM21S targets 4K Android TV use for IPTV/OTT white-label projects and offers Android 14 with a wider listed memory family. Its Dolby Vision/DTS entry requires confirmation as an optional production configuration rather than an automatic entitlement to every format.
DM21T addresses premium UHD and cloud-gaming use, with the highest listed frame-rate decode targets and no HDMI input. Despite marketing references that may imply an “8K” class, the production facts cap output and decoding at 4K. Do not convert that wording into an 8K output claim.
DM22Q targets gaming-oriented Android TV use and lists Android 14, 4GB / 64GB, and a 1G Ethernet option. Its maximum listed decode result is 4K@60. The facts provide no NPU TOPS figure, so inline AI-SR must not become a numeric accelerator claim.
The comparison is a starting point for this android tv box checklist, not a universal ranking. DM21P’s AOSP Android 11 base may fit an established operator image, while the Android 14 models may align with a newer application baseline. DM21T’s listed 4K@120 paths suit a demanding media target, but the absence of HDMI input constrains source capture. DM22Q lists 4GB / 64GB and optional 1G Ethernet for a gaming-oriented configuration, while its maximum decode result remains 4K@60.
Every option requires the same document discipline. State the selected RAM/ROM combination, Ethernet option, DRM configuration, and port set on the order. If a port, memory family, DRM implementation, or network speed is optional, confirm it against the production datasheet and record it in the approved sample. Never use the widest listed family as if every unit contained it.
For a broader sourcing review, the TV box vendor selection checklist helps separate supplier capability from the configuration accepted for a specific service.
Where This Matters in a Deployment
The same device can fail for different reasons in an operator network, an integrator project, and a venue installation. The evidence must match the deployment scene.
A telecom engineering laboratory bench provides the controlled reference: units connected through repeatable HDMI and network paths while engineers validate display, connectivity, playback, and recovery.

| Situation | Dominant requirement | Acceptance emphasis | Model direction |
|---|---|---|---|
| IPTV or OTT operator | Managed rollout and service stability | Middleware, entitlement, enrollment, updates, 100M or 1G access-network behavior | DM21P for 4K IPTV; DM21S for Android 14 IPTV/OTT white-label |
| System integrator | Repeatability across venues | Fitted configuration, port map, boot image, display mode, recovery, site-network test | Select by the accepted bill of materials |
| Premium UHD or cloud-gaming venue | High-frame-rate decode and display capability | 4K@120 title path, output negotiation, latency, thermal stability | DM21T direction |
| Gaming-oriented Android TV | 4K60 service path and application responsiveness | AV1/H.265 playback, 4GB / 64GB, interfaces, control latency | DM22Q direction |
| Retail or hospitality display | Simple installation and stable boot | HDMI, Ethernet, remote input, startup, scheduled recovery | Any shortlisted model after qualification |
For an IPTV operator, deployment risks are often more operational than silicon-level. The box must obtain addressing, authenticate, receive middleware or device policy, maintain a streaming session, expose diagnostics, and update without losing configuration. A fixed wired laboratory network does not cover captive portals, Wi-Fi contention, multicast behavior, or an ISP access network. Sample the actual environment, including the slowest supported access path.
For AV and IT integrators, the important artifact is a repeatable installation record. It should capture hardware revision, firmware, output configuration, network setting, remote pairing, application version, and test result. If an installer can substitute storage or Ethernet options without updating that record, the approved configuration is not controlled.
For premium displays, codec support is one element. The path includes source packaging, CDN delivery, application behavior, decoder, HDMI negotiation, television scaling, and audio routing. Test at the target resolution, frame rate, color format, and refresh mode. A 4K decoder can still display at 1080p if the display, cable, EDID, or application configuration forces a lower mode.
The matrix clarifies that model direction is not final selection. DM21P may suit 4K IPTV or operator middleware, but the accepted variant determines memory, Ethernet, DRM, and software. DM21S may suit an Android 14 IPTV/OTT white-label image. DM21T becomes relevant when the service genuinely requires a listed 4K@120 path. DM22Q may fit a gaming-oriented 4K@60 program. None removes site qualification.
Fleet management adds another dimension. The test unit must complete enrollment, receive policy, install the designated client, report diagnostics, and recover from a failed update. An integrator rollout needs serial-number and installation records so a returned unit maps to its accepted image. A venue adds display, audio, peripheral, and environmental repeatability.
This android tv box checklist should include a worksheet with model, hardware revision, fitted memory/ROM, Ethernet option, Android build, client version, serial-number range, display model, access network, remote model, installer, result, and exception reference. That turns product qualification into an installed-base record and gives support teams a defensible starting point.
The Selection Sequence That Removes Rework
Start from the service contract, not the model list. Convert every operational requirement into an observable acceptance line. This prevents an attractive specification from replacing an incompatible service definition.
- Freeze the service profile Record title codecs, profiles, levels, resolutions, frame rates, bitrates, audio formats, DRM combinations, live/VOD behavior, and application requirements.
- Freeze the operating environment Define access-network speed, topology, display capabilities, peripherals, remote control, installation method, and update policy.
- Map requirements to models Compare models against decode, OS, memory, interfaces, and intended use; reject unresolved options.
- Build the golden sample Approve one exact hardware and software configuration with photographs, bill of materials, hashes, display settings, and results.
- Run pilot-batch validation Sample the intended production process, including inspection, aging, dark-room checks, playback, networking, DRM, and recovery.
- Release the production specification State accepted models, exact variants, prohibited substitutions, firmware baseline, evidence, containment, and change control.
The RFQ can then use lines such as: “Device shall decode AV1 [email protected] at 4K@60 and H.264 at 4K@30; fitted configuration shall be 2GB / 8GB; Ethernet shall be RJ45 100M; Wi-Fi shall be Wi-Fi6 2x2; protected-content testing shall cover Widevine L1 and PlayReady; approval requires a golden sample and pilot-batch sign-off.” Where a value is optional, name the selected option.
Resolve ownership. Name who supplies the Android image, installs middleware, operates the licence service, defines the content ladder, approves the display mode, and signs the pilot. A decode error could belong to the SoC, firmware, application, stream packaging, or output chain. Preserve the failing boundary rather than recording only “playback failed.”
- Convert features into test statements Replace “supports 4K” with codec, profile, level, resolution, frame rate, output mode, and representative-title requirements.
- Convert DRM names into combinations Pair each implementation with its application, content set, licence environment, and display path.
- Convert connectivity into site conditions Define interface speed, topology, signal assumptions, multicast use, power behavior, and peripherals.
- Convert factory claims into evidence requests Request assembly, aging, dark-room, rejected-unit, playback, and traceability records.
- Convert sample approval into change control Define which hardware, firmware, application, DRM, memory, and Ethernet substitutions require reapproval.
An optional Ethernet line must identify 100M or the selected 1G option, confirm it against the production datasheet, and require the network test. A RAM/ROM line must state one fitted combination. A DRM line must identify the production configuration. This prevents the accepted sample from being treated as proof of every variant.
For a first engineering discussion, send the complete service profile, display modes, connectivity requirement, exact candidate configuration, software-control method, and pilot evidence through the DataMax inquiry page. The first message should state “VOD set-top-box acceptance: service profile, candidate platform, fitted memory/ROM, DRM requirements, network profile, and pilot sign-off plan.” For physical evaluation, the sample-order path should reference the golden-sample revision rather than a generic showroom unit.
Revise this android tv box checklist whenever the service profile, display environment, software image, or factory process changes. A version-controlled baseline prevents an accepted sample from silently authorizing a later configuration.
Specification discipline
Reject a quotation that changes the SoC, Android version, memory, Ethernet speed, DRM option, or port set without an engineering impact review. A change can alter boot behavior, media timing, thermal load, application performance, and the evidence basis of the approved sample.
Failure Modes That Reach the Field
Most field failures originate at unresolved boundaries between quotation, qualification, and deployment. Correct them before mass production because a post-deployment hardware or firmware change multiplies the affected population.
Field trap 1
“Optional” DRM, Ethernet, or memory is often treated as standard. The result is a mixed fleet with different software, cabling, and test procedures. Name the fitted option on the purchase order, test it, and prevent unrecorded substitutions.
Field trap 2
“4K” and “Wi-Fi 6” are accepted without a service profile. A decoder can lack the required profile or frame rate, while a nominal wireless generation can fail under contention or poor signal. Record codec, level, resolution, frame rate, display mode, network conditions, and playback outcome.
| Quotation wording | Field consequence | Required correction |
|---|---|---|
| AOSP Android version | Missing launcher, middleware, management, or update path | Identify the complete image, installed software, enrollment method, and update owner. |
| Family RAM/ROM options | Devices ship with inconsistent capacity | State the fitted combination and control substitution. |
| DRM name without service matrix | Licence, output, or content failure | Require application, content, output, and licence-server records. |
| 4K-capable decoder | Wrong profile, level, frame rate, or display mode | Test the actual stream and negotiated output separately. |
| Factory functional test | Assembly passes but the VOD application fails | Define line checks, sampled title tests, and regression ownership. |
Thermal behavior is another blind spot. Decode complexity, wireless activity, display circuitry, and sustained application use alter the operating profile. Run the device for the intended session length under expected network and peripheral load, then inspect stability and playback continuity. Do not infer a thermal result from a five-minute demonstration.
Recovery matters equally. Support requires a repeatable path after a failed update, corrupted application state, network loss, or accidental configuration change. Test the approved recovery mechanism, document data-retention behavior, and verify that operators can distinguish device failure from service or entitlement failure.
Other failures occur at hardware-environment boundaries. A USB peripheral may enumerate but draw unstable power. A remote may pair but lose input after restart. A display may accept the unit but negotiate an unintended color or refresh mode. Ethernet may connect while DNS, multicast, or captive-portal handling fails. Each issue needs a named test, expected result, and owner in this android tv box checklist.
Include packaging and identification. If model label, serial number, hardware revision, or fitted memory cannot be reconciled with the purchase order, the factory cannot contain the correct unit efficiently. An identifier mismatch can trigger unnecessary replacement, a blank or unauthorized unit, or support escalation before playback is tested. Reconcile label, bill of materials, and software report during incoming inspection.
Distinguish recoverable content failure from device failure. A denied entitlement can resemble an application defect; a changed display mode can resemble a decoder fault; an expired licence can resemble a DRM implementation failure. Capture logs, timestamps, application version, device configuration, and service response at failure. Without that context, support may replace a functioning device while the service issue remains.
The reliable quotation therefore includes three identifiers: approved golden sample, exact production configuration, and pilot sign-off record. For broader factory-control diligence, review the factory-quality evidence path and use the RFQ checklist to identify missing commercial, technical, and acceptance lines before comparison.
Further reading
- RK3568 Android Box Checklist for Procurement Teams
- Android TV boxes
- Rockchip Android TV boxes
- Edge computing boxes
- 4K 60fps Android TV box guide
- DataMax DM21P specifications and fit
- DataMax DM21S specifications and fit
FAQ
What is the most important item in an android tv box checklist?
The most important item is the fully defined configuration: exact SoC, Android version, RAM/ROM, DRM, decoder targets, ports, and network options. A platform family name is insufficient because a quotation can satisfy the headline while delivering an unsuitable fitted configuration. Identify the approved software baseline and pilot evidence as well.
Does Widevine L1 automatically make a set-top box production-ready?
No. Widevine L1 identifies one secure-client capability, but deployment readiness also depends on the content service, licence infrastructure, application integration, output path, and protected-title playback. Demonstrate licence acquisition and playback for every required service and DRM combination rather than relying on the security-level label.
Is 100M Ethernet sufficient for a 4K VOD box?
It may be, because the requirement depends on bitrate, concurrent streams, network overhead, and service behavior. Define the actual access-network profile and test representative traffic rather than selecting Ethernet speed from the “4K” label. If the model supports a 1G option, confirm the fitted configuration against the production datasheet.
Should every unit receive a full VOD playback test?
Test depth can be risk-based. Line checks can cover boot, interfaces, display, network, and a short playback path, while sampled testing covers the complete title and DRM matrix. Define sampling, failure containment, regression, and traceability. This provides stronger evidence than one laboratory demonstration without imposing unnecessary cycle time.
What should a buyer request before approving a pilot batch?
Request the approved golden sample, exact bill of materials, software versions, test matrix, factory records, rejected-unit disposition, and pilot results. Records should identify the tested unit or lot and the criteria met. A factory’s broader certification position supports diligence but does not replace model-specific acceptance evidence.
When should an android tv box checklist trigger a new pilot?
Trigger a new pilot after any change to the SoC, board revision, fitted RAM/ROM, Android image, DRM option, Ethernet configuration, display path, middleware, update mechanism, or production process. A change may alter boot behavior, media timing, thermal load, recovery, or enrollment. Reuse unchanged evidence only where the engineering owner accepts that justification.