Before the terminology: the decision
A Dolby Vision android tv box is not a single procurement category: the decisive variables are operating-system baseline, device tier, output path, DRM configuration, thermal design, and the evidence attached to each production lot. The supplied DataMax portfolio spans AOSP Android 11 and AOSP Android 14, base RAM from 2 GB to 4 GB, and platform positioning from operator middleware through white-label OTT and gaming use. The correct comparison therefore separates published capability from an individual purchase order.
The short answer is straightforward. Select a platform whose production datasheet explicitly lists Dolby Vision, then freeze the Android version, RAM/ROM configuration, output mode, network option, DRM package, and firmware-support commitment on the PO line. Do not infer Dolby Vision certification from a processor name, 4K label, or HDMI 2.0b port. Do not infer lifecycle control from a generic “industrial” description. For broader terminology, see Dolby Vision Android TV Box: the question buyers get wrong.
This article answers a narrower procurement question than the canonical guide. It compares the four quoted DataMax production platforms field by field, maps them to operator, integrator and venue requirements, and identifies the factory evidence needed to keep a quoted configuration aligned with delivered hardware. It also separates a product’s published decode capability from a complete Dolby Vision service path: source licensing, middleware, DRM, output mode, downstream display behavior and update control all need named acceptance evidence.
A practical buyer should reject any quotation that leaves “Dolby Vision” as a standalone phrase. Ask instead whether the box is intended to receive Dolby Vision content, which service profile must pass, which display mode is required, and which downstream television or projector is included in the acceptance test. The same rule applies to “4K,” “AI-SR,” “1G optional” and “HDCP optional.” Each term needs a configuration state, test method and responsible owner.
Decision rule: “Dolby Vision supported” is not a complete acceptance criterion. The purchase order should name the platform, OS baseline, memory configuration, DRM configuration, output behavior and lifecycle evidence package.
The lifecycle decision is equally concrete. Before volume release, the buyer should receive one traceable evidence chain connecting the approved bill of materials, board revision, fitted memory, firmware image, display test and shipment release. A platform that meets the playback requirement but cannot identify the tested lot is not yet a production platform. Conversely, a documented platform with the wrong Dolby Vision implementation cannot be rescued by stronger lifecycle controls. Capability and control are parallel gates, not substitutes.
Five production SKUs compared
The portfolio contains four quoted production SKUs, not five independent models. The fifth comparison axis is lifecycle control: model choice and lifecycle evidence must be evaluated together. All specifications below are reproduced from the supplied product facts. Any configuration not listed here must be confirmed against the production datasheet.
| Model | SoC and CPU | OS | RAM/ROM | Decode | DRM | Interfaces |
|---|---|---|---|---|---|---|
| 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 | 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 |
The baseline memory spread affects system selection more than peak decode capability. DM21P and DM21S begin at 2 GB, while DM21T and DM22Q are quoted at 4 GB. Higher memory tiers exist on most platforms, but the configured tier must be fixed line by line in the PO. This distinction matters because a sample with 8 GB of RAM cannot validate the behavior of a 2 GB production SKU without a separate low-memory test.
The Dolby Vision listing also differs materially: it is explicit for DM21S and DM22Q, but not for DM21P or DM21T in the supplied facts. A procurement team should not normalize that omission into either a claim of support or a claim of absence. For a purchase requiring Dolby Vision, the explicit DM21S or DM22Q listing is the cleaner starting point, subject to service-profile testing. For either platform without an explicit listing, request the production-datasheet statement and implementation evidence before including it in the comparison.
Interface differences can decide an integration even when playback capability appears equal. DM21T has one USB2.0 port and one USB3.0 port, while the other quoted models list two USB2.0 ports. DM21T also has no HDMI input. A venue may need USB3.0 for a particular peripheral; an operator may need a specified number of USB2.0 ports; a rack or signage installation may depend on the absence of HDMI input. These are not minor mechanical differences when the installer builds a cable schedule.

The same figures, in searchable form:
| Platform | Base RAM |
|---|---|
| DM21P | 2 GB |
| DM21S | 2 GB |
| DM21T | 4 GB |
| DM22Q | 4 GB |
Source: DataMax production datasheets (base SKU; higher RAM is a configured option on most platforms). Base configuration only; optional RAM tiers exist and must be fixed line-by-line in the PO.
For AV1-oriented procurement, the AV1 Android TV Box guide helps distinguish codec support from the complete playback chain, including source resolution, output mode and display capability. The same discipline applies to the term android tv box used in a PO: a platform label must be followed by the exact SoC, memory, OS and output lines.
The operator, the integrator and the venue
The same model can fail economically in one deployment and work in another. An operator may prioritize middleware integration, controlled firmware and service recovery; an integrator may prioritize USB, display and network options; a venue may need a fixed configuration, wall-mount logistics and a repeatable installation test.
The “five” framing above is a governance error worth correcting: there are four quoted SKUs and three buyer situations. Each situation should convert into a testable requirement before a platform is shortlisted. The matrix below is a direction-setting tool, not a substitute for a project acceptance plan.
| Situation | Primary requirement | Model direction | Acceptance evidence |
|---|---|---|---|
| Operator — 4K IPTV or operator middleware set-top box | Stable middleware image, controlled firmware and defined I/O | Start with DM21P for the operator middleware fit; use DM21S or DM22Q where Dolby Vision/DTS and Android 14 are required | Image revision, port map, middleware test report, pilot-to-production change record |
| Integrator — IPTV or OTT white-label integration | Android 14 baseline, optional Ethernet speed and brand-level software control | DM21S is the direct white-label candidate; DM22Q adds the 4 GB base and gaming positioning | White-label boot test, 1G option evidence, IR and network test, update procedure |
| Venue — premium UHD or cloud-gaming installation | Higher-memory baseline, high-frame-rate decode and installation flexibility | DM21T where 4K@120 decode and USB3.0 matter; DM22Q where Dolby Vision/DTS is listed and 4K@60 is sufficient | Display-mode matrix, thermals under load, input inventory, restart and recovery test |
| Operator procurement — multi-site refresh with managed recovery | Consistent image identity, remote update route, serial-level traceability and spare-unit matching | Consider DM21S for an Android 14 white-label image or DM22Q where the 4 GB base and Dolby Vision/DTS listing align | Update pilot report, serial-to-firmware map, recovery test, lot release record |
| Integrator procurement — display and peripheral bundle | HDMI mode control, named USB generation, audio path and Ethernet speed | DM21T where USB3.0 and high-frame-rate decode dominate; otherwise match the published port map directly | EDID and mode matrix, peripheral enumeration test, audio-path test, port photo |
| Venue procurement — digital signage or premium display | Fixed memory tier, repeatable installation, boot behavior and long-running display stability | DM21T or DM22Q where the 4 GB base is justified; DM21S where its 2 GB base and explicit Dolby Vision/DTS fit the workload | Soak test, cold-boot count, screen artifact review, configuration record |
A real laboratory scene for this comparison places multiple black set-top boxes on an engineering bench with HDMI and network connections, test monitors and RF measurement equipment in active use.

For operator programs, a second selection axis is the management model. An AOSP build is not a Google Android TV device, and app compatibility must be tested rather than inferred from an Android version. The AOSP versus Google Android TV guide helps define that distinction before middleware validation begins. The android tv box qualification should therefore include application installation, launch, DRM playback, input handling and restart behavior on the exact image proposed for deployment.
The venue case adds another constraint: nominal decode limits do not guarantee the chosen television or projector exposes the required mode. Procurement evidence should therefore include the output mode, display EDID handling, scaling behavior and recovery after signal changes. Do not let “4K” or “Dolby Vision” remain unqualified marketing labels. For a gaming-oriented venue, record whether the acceptance target is decode at 4K@120, output at 4K@120, input support, or all three. Those are separate requirements.
An integrator also needs the accessory list before declaring a winner. Include the remote-control path, power adapter, HDMI cable, Ethernet adapter if required and mounting arrangement. Then freeze the port map and cable schedule. If the buyer samples one interface arrangement but the production quotation names another, the validation is no longer representative. Every android tv box comparison should distinguish the physical product, the configured SKU and the tested sample revision.
How to choose, step by step
A reliable selection sequence prevents the Dolby Vision label from outrunning the rest of the specification. It also makes the RFQ answerable: a supplier can quote one configuration, and the buyer can test that configuration without interpreting several competing meanings of “supported.”
- Start with the service workload Record whether the device serves operator IPTV, white-label OTT, premium UHD or cloud gaming. Identify the Android baseline required by the middleware, launcher, app set and security policy.
- Write the display contract Specify output resolution, frame rate, color format, HDR/Dolby Vision behavior, audio output and required interfaces. Treat each as a testable line rather than a feature phrase.
- Select the platform family Compare the published SoC, RAM/ROM and connectivity. Do not move to a higher tier solely for a codec label; identify the constrained workload, such as 4K@120 decode or a listed Dolby Vision/DTS package.
- Freeze memory and firmware State the exact RAM/ROM configuration, AOSP Android version, firmware image identifier, preinstalled apps and update mechanism. Optional tiers must appear in the PO.
- Define lifecycle evidence Require traceability from incoming inspection through assembly, firmware loading, aging, RF/EMC checks and shipment. Define the document set and sampling plan before volume ordering.
- Run representative acceptance Test the actual source content, display, network, peripheral set, power interruption, thermal load and recovery behavior. A laboratory-only codec demonstration is not an end-to-end acceptance result.
- Lock the production change process Require written approval for SoC, memory, wireless module, firmware branch, launcher, middleware and accessory substitutions. Tie each change to impact analysis and a sample decision.
- Approve a continuity plan Define the security-patch route, image cadence, component end-of-life notification process, field-failure feedback process and replacement traceability before volume release.
The resulting RFQ can use this structure:
Please quote model, AOSP Android version, exact RAM/ROM, SoC, output and decode modes, Dolby Vision implementation status, DRM configuration, Ethernet option, port inventory, firmware revision, lifecycle-support plan, test reports and proposed sample-to-production gate.
For a focused request, send the model shortlist, required output mode, memory line, operator middleware or white-label application, target display profile, expected annual volume profile, destination markets and required certification documents to the inquiry team. The first message should contain those items rather than only asking for “the best Dolby Vision box.” Include the actual PO wording for optional features so the supplier can respond line by line without reinterpretation.
A visual decision flow keeps the sequence compact:
Two quotation-control rules prevent delay at the sample stage. First, require the quotation to identify the exact android tv box model and configuration revision. Second, prohibit unlabeled substitutions in the response: “same as previous model” is not an acceptable revision reference. If the supplier proposes a different RAM tier, Ethernet option, Wi-Fi module or firmware branch, state whether the price, test plan and delivery plan remain valid.
The evaluation record should also identify what is outside scope. A supplied platform description may not establish thermal limits, regulatory status for every destination, display-mode support, input support or long-term software maintenance. Those points belong in the acceptance matrix as confirmation items, not silent assumptions. This prevents an attractive sample from becoming the wrong production baseline.
The traps in this category
Quotation differences usually come from omitted qualifiers. “Same platform” can conceal a different SoC or memory tier; “Dolby Vision ready” can conceal a different certification scope; “same firmware” can conceal different regional operator middleware, launcher or preinstalled applications. The technical mismatch may appear only after the display, source and app stack reach the lab.
Field trap
Do not order from a logo or family name. The cost of getting this wrong is a lot-level rework cycle: rejected inventory, duplicated certification work, operator middleware changes and a delayed deployment gate even when the SoC remains unchanged.
Field trap
Do not equate Dolby Vision, Widevine L1, HDCP and display support. A box can carry content-protection functions without guaranteeing the complete display chain, source profile, licensed service behavior and downstream display compatibility required by the operator.
Other traps include output overspecification. DM21T is listed with 4K@120 decode across several codec families, but it also has HDMI 2.0b output and no HDMI input. The quoted facts do not establish that every 4K@120 source can be passed through at 4K@120 to every attached display. Conversely, the supplied facts cap DM21T output/decode at 4K, so no 8K output claim belongs in the specification.
A second comparison trap is confusing codec capability with product positioning. DM21T’s decoding list includes H.266/VVC [email protected] 4K@120, AV1/VP9/H.265 4K@120, AVS3 4K@120 and H.264 4K@60, but its DRM line does not explicitly list Dolby Vision. DM22Q lists Dolby Vision/DTS, while its maximum decode statement is 4K@60. Buyers must define which constraint matters: codec breadth, high-frame-rate processing, service protection or output behavior.
A third trap is treating base RAM as a benchmark result. The 2 GB and 4 GB figures identify the quoted configurations; they do not measure application responsiveness, startup time or concurrent workload capacity. If a middleware image has an approved minimum memory profile, use that profile to set the production tier. If no profile exists, run the representative app set against the exact base and intended optional configurations. The android tv box selected for volume should match the configuration tested under that load.
Connectivity wording creates a fourth trap. The quoted models use RJ45 100M, with 1G optional or 1G opt on DM21S, DM21T and DM22Q. “1G optional” is not a selected 1G interface. Require the physical Ethernet implementation, negotiation result and transfer acceptance condition on the PO, particularly where the application depends on sustained local traffic or operator management traffic.
How the factory controls the variable
Factory control starts before final assembly. A repeatable BOM revision, approved component list, firmware identity and route card form the baseline. Each production lot should be able to answer: which board revision was built, which SoC and memory configuration were fitted, which image was loaded, which tests ran and which unit passed or was quarantined.
- Incoming material control Match SoC, RAM, ROM, Wi-Fi/Bluetooth module, ports, power supply and other critical parts to the approved configuration revision. Record substitutions through a formal engineering change.
- SMT and AOI Inspect soldered assemblies for assembly defects. The objective is to detect board-level faults before software loading and enclosure assembly obscure them.
- Program and firmware loading Bind each device to the correct firmware image and configuration identity. Verify boot, application presence, version reporting and required service interfaces.
- Dark-room display and audio test Exercise the quoted output path against defined source material, display profiles and audio outputs. Capture serial number, fixture ID, test profile and result.
- Thermal, RF and regulatory checks Apply the applicable product, market and component requirements. Keep equipment calibration and sampling visible in the lot record.
- Aging and shipment release Stress the assembled unit under defined conditions, complete the final functional test, apply traceability labels and retain the release record.
- Configuration reconciliation Compare the fitted SoC, memory, Ethernet option, wireless module and firmware identity with the PO. Quarantine any mismatch rather than allowing it to enter the shipment pool.
- Change notification Route any board, component, firmware or accessory change through impact analysis covering playback, thermal, regulatory, middleware and field-replacement effects.
Evidence package: BOM and board revision, component-substitution log, firmware checksum, serial-number mapping, SMT/AOI result, dark-room test report, aging record, RF/EMC records where applicable, final inspection report and corrective-action log. DataMax should be able to show how this package maps to the customer PO.
For an OEM/ODM program, this evidence chain is part of the product rather than administrative paperwork. A supplier-level overview is available at factory quality, while DataMax manufacturing describes the broader production context. Certification documents, including the documents relevant to the destination market, should be reviewed through certifications and compliance rather than inferred from the chipset.
The lifecycle gate should include written procedures for firmware updates, security patches, bootloader or image controls, component end-of-life notification, field failure analysis and replacement traceability. The request should specify the support period and evidence cadence required by the operator, not rely on an undefined word such as “long-term support.”
The unit of traceability must also be defined. A lot-level record can establish that a production run used a particular BOM, while serial-level mapping establishes which unit received which firmware and test result. For an android tv box program with field replacement, the latter is especially useful: a replacement should not silently receive a different image, region profile or hardware revision. Define whether the evidence map ends at shipment, extends through warehouse issue or continues through installed-base returns.
Thermal and display evidence must be connected to the actual use condition. A dark-room pass proves the defined source and display profile worked during the test; it does not establish performance in a sealed cabinet, a hot venue or a long-running signage loop. The aging procedure should identify the workload, duration and operating condition agreed for the project. Supplier records should identify equipment, fixture and sampling rather than merely declaring that the lot passed.
Two routes, one bill of differences
The economical route is to specify a base configuration whose published features match the service and accept the associated limits. The commitment route adds explicit platform configuration, validation and lifecycle evidence before volume release. The commitment route costs more in engineering and validation work; it reduces the risk that a nominal specification becomes a deployment dispute.
| Decision line | Entry configuration | Controlled production commitment |
|---|---|---|
| Model | Select from the published fit descriptions | Name one model and one approved configuration revision |
| Memory | Use base 2 GB or 4 GB platform memory for evaluation | Freeze exact RAM/ROM in the PO and verify fitted components |
| Android baseline | Use AOSP Android 11 for DM21P or AOSP Android 14 for the other quoted platforms | Freeze image version, middleware, launcher, apps and update route |
| Dolby Vision/DTS | Use only where explicitly listed in the supplied facts | Require implementation evidence and service-profile acceptance test |
| Connectivity | Use published base RJ45 100M arrangement | Specify 1G option where selected and verify every sample/lot |
| Evidence | Basic sample functional check | Lot traceability, firmware records, test reports, change control and lifecycle plan |
| Decode and output | Record the highest published capability without implying display support | Test the required source, output mode, display profile, audio path and mode recovery |
| DRM | Name Widevine L1, PlayReady, HDCP and Dolby Vision separately | Freeze the selected implementation, service license flow, entitlement result and protected-content playback |
| Interfaces | Use the published port inventory for initial screening | Freeze port map, selected accessories, cable schedule and peripheral enumeration |
| Samples | Use one functionally configured sample | Require samples from the proposed production configuration and retain revision evidence |
| Change control | Rely on the supplier’s general change process | Set advance notice, approval, impact-analysis and requalification gates |
| Release | Use a basic final functional check | Link serial-level results, aging outcome, configuration reconciliation and shipment authorization |
This is not a claim that one route is technically superior in every project. The entry configuration is appropriate when the workload is stable, the supplied platform fit is explicit and the deployment risk is contained. The controlled route is appropriate when an operator needs repeatable firmware, middleware qualification, regional compliance and a predictable field replacement path.
The bill of differences is therefore not a binary product-quality claim. It is a change in how ambiguity is handled. The entry route accepts published limits and focuses on functional screening. The controlled route identifies where the supplier must provide configuration evidence, where the buyer must perform service acceptance and where a future substitution could disrupt deployment. For an android tv box sourced across multiple sites, the controlled route usually creates less operational ambiguity because the same revision language can govern samples and volume.
For samples, ask the sample-order team to state the proposed RAM/ROM, OS, connectivity, firmware and accessory set in the request. If the project is still at the platform-definition stage, custom development is the relevant path for requirements not met by the standard configuration.
A commercial comparison can then be made without hiding the engineering scope. Ask each supplier to return the same configuration matrix, including whether the quoted unit is a base sample or production-representative sample, which DRM implementation is selected, which display test is included and which documents accompany the shipment. If one quotation omits a line, mark it “unconfirmed” rather than treating silence as inclusion. That prevents the lowest numerical quotation from carrying an undefined acceptance scope.
How the requirement actually works
Dolby Vision is a display and content-processing ecosystem, not a decoder switch. The procurement chain includes licensed content, an application or middleware path, a DRM service, the device’s platform integration, the output mode and the downstream display or television. A Dolby Vision logo on a quotation does not prove every link in that chain.
Widevine L1 and PlayReady are content-protection functions. They should be specified independently from Dolby Vision. HDCP 2.2 is another separate line: DM21P lists it as optional. The supplied facts list Dolby Vision/DTS for DM21S and DM22Q, while the other platforms require confirmation against the production datasheet. DTS is also an audio capability and should not be collapsed into a video-protection statement. For a mixed audio/video deployment, write separate lines for the video service path, S/PDIF or AV behavior and the required endpoint decode.
AOSP is the source platform; “AOSP Android 14” does not by itself mean the device is a Google-certified Android TV device. Application compatibility, launcher behavior, device-owner policy, middleware integration and update control need separate validation. The distinction is detailed in AOSP versus Google Android TV. The Dolby Atmos Android TV Box guide can also help distinguish an audio branding requirement from the end-to-end audio path.
AV1, H.265/HEVC and H.266/VVC are separate codec capabilities. AV1 is listed across the quoted platforms; H.265 is listed across them; H.266/VVC main10 appears in DM21T’s decode specification. Codec support does not resolve output bandwidth, display capability, DRM entitlement or middleware integration. The same separation applies to inline AI-SR: it appears in the DM21T and DM22Q decode descriptions, but no NPU TOPS figure is stated for either platform, so it should not be used as a quantified performance claim.
The architecture should be written as a traceable chain:
- Content and service licensed source, operator catalogue and entitlement
- Software path middleware or OTT application, DRM integration and display configuration
- Hardware path SoC decode, memory, output mode and physical interfaces
- Endpoint television, projector or signage display with matching mode support
- Operations firmware updates, security patches, failure analysis and lifecycle records
For a complete architectural review, the operator-tier Android TV Box solution provides the relevant operational frame. The procurement result should then be an acceptance matrix: service, device, output, display, update and evidence rows, each with an owner and a pass condition.
That matrix should use observable results. For content, identify the service and protected stream. For software, record the image and application revision. For hardware, record the fitted configuration. For output, state the negotiated mode and audio path. For the endpoint, record the display or projector profile. For operations, record the update result and evidence identifier. A final android tv box approval should therefore read like a controlled release record, not a product-feature summary.
Further reading
- Dolby Vision Android TV Box: The Question Buyers Get Wrong
- AOSP Android TV boxes
- H.265 HEVC Android TV box guide
- Widevine L1 certification guide
- Dolby Atmos Android TV box guide
- DataMax DM21P specifications and fit
- DataMax DM21S specifications and fit
FAQ
Does Dolby Vision support determine which box to buy?
No. It is one requirement among OS baseline, memory, output mode, DRM, connectivity and lifecycle evidence. In the supplied portfolio, Dolby Vision/DTS is explicitly listed for DM21S and DM22Q. For a platform without that listing, confirm the exact implementation against the production datasheet rather than inferring support from codec capability.
Is 8K output available in the quoted DataMax range?
The supplied production facts do not establish 8K output. DM21T and DM22Q are limited by their quoted datasheets to 4K output/decode capabilities, including 4K@120 for specified codecs on DM21T and 4K@60 on DM22Q. Specifications outside those statements should be treated as unverified.
Does AOSP Android 14 equal a Google Android TV device?
No. AOSP identifies the software foundation and stated Android version, not Google certification. Device provisioning, application compatibility, launcher behavior, middleware integration and update management require separate validation. This distinction can determine whether an operator image or commercial application behaves as intended.
What should be written on the PO?
Write the model, AOSP Android version, exact RAM/ROM, SoC, output and decode limits, Dolby Vision status, DRM configuration, Ethernet option, port inventory, firmware revision, required accessories and lifecycle evidence. Optional features should not remain phrases such as “1G optional” or “Dolby Vision/DTS” without the selected state.
Which model fits an operator middleware deployment?
DM21P is explicitly positioned for 4K IPTV and operator middleware set-top box use. If the project requires AOSP Android 14 and an explicit Dolby Vision/DTS listing, DM21S or DM22Q provides a documented alternative direction. Final selection still depends on middleware, memory, output and acceptance requirements.
How should samples be ordered for this evaluation?
Send the sample-order request with the proposed model, RAM/ROM, OS baseline, Ethernet option, required firmware content, output targets, display profile, accessories and acceptance criteria. Recording those items before shipment prevents the sample from becoming an unspecified representative of the production build.