Skip to main content

Engineering FAQ · Wanlin

H618 OEM/ODM Android board: Board Qualification

Published: · Updated:

Direct answer

Review H618 OEM/ODM Android board requirements, interfaces, software and acceptance scope. Confirm the exact model configuration against current controlled project documents.

Product overview: What the A18 H618 board actually is

The A18 is an HDMI dongle class smart motherboard built on the Allwinner H618 platform: a 64-bit quad-core Cortex-A53 cluster paired with a G31 MP2 GPU and running Android 12. It belongs to the same deployment family as Android TV sticks, streaming dongles, OTT and IPTV set-top sticks, digital signage players, wireless casting units, hospitality television projects, portable projectors and in-vehicle screens - which is exactly why one carrier now gets re-spun into eight different product lines.

  1. Allwinner H618, 64-bit quad-core Cortex-A53. Enough headroom for a 4K player, a browser-based portal and a launcher shell. Not an application-class CPU, so heavy UI work has to be re-scoped or moved up a platform.
  2. G31 MP2 GPU with the full media pipeline. 4K at 60fps on VP9 Profile-2, H.265 Main10 at L5.1 and AVS2 JiZhun 10-bit, with H.264 topping out at 4K and 30fps. The encoder profile you hand your content team decides whether a 4K loop plays smoothly.
  3. 2GB LPDDR4 and 16GB eMMC as standard. Comfortable for a single-stream player with a local cache. Tight if the unit also runs a camera preview, a local database and a browser shell at the same time.
  4. TF card expansion to 64GB. 4GB, 8GB, 16GB, 32GB and 64GB cards are supported. The card is the offline content store for vehicles, classrooms and sites with no reliable link.
  5. WiFi 802.11 a/b/g/n/ac/ax on 2.4G and 5.8G. Dual-band with WiFi 6 on the same radio seat. The A18 specification lists WiFi only, so Bluetooth is a combo-module option on the custom build rather than a catalog default.
  6. HDMI output at 4K and 2K UHD. The feature block specifies HDMI 2.0a and the I/O line specifies HDMI 2.1; on a custom build we pin the exact transmitter and the exact cable qualification at design freeze rather than leaving it to the housing vendor.
  7. DC 5V at 1.5A with LED state, RTC, auto power-on and OTA. Blue LED for working, red for standby. That 1.5A figure is the single most violated number in the field, and it is where most of the incidents below start.

Specifications: What the AS-H618-MPF-CUS custom H618 board ships with

The AS-H618-MPF-CUS is a re-spin of the standard A18 carrier: the H618 platform, a compact multi-layer PCB laid out for the customer housing, industrial-grade components throughout, with conformal coating optional. The specifications below are the A18 default; every line is re-specable on request.

BlockSpecification
SoCAllwinner H618, 64-bit quad-core ARM Cortex-A53
GPUG31 MP2, hardware compositing and the full media decode pipeline
Memory2GB LPDDR4 standard
StorageOn-board eMMC 16GB standard; TF card socket supporting 4GB, 8GB, 16GB, 32GB and 64GB cards
Operating systemAndroid 12; AOSP or GMS build; kiosk mode with a locked launcher and auto-start app
Display outputHDMI at 4K*2K UHD; HDMI 2.0a in the feature block and HDMI 2.1 on the I/O line, pinned at design freeze on a custom build
USBTwo USB lanes: one USB host port and one USB OTG port
InfraredIR receiver and remote receiver connection
WirelessWiFi 802.11 a/b/g/n/ac/ax on 2.4G and 5.8G; Bluetooth 5.0 or 5.4 as a combo option on custom builds
Wired networkNot on the A18 base; USB-to-Ethernet at 10/100M or Gigabit available on the custom carrier
PowerDC 5V at 1.5A; LED indicator, blue when working and red on standby
Clock and schedulingRTC real-time clock; auto power-on; scheduled power on and off on custom builds
Upgrade pathsOTA upgrade support; USB and TF card upgrade; A and B slot with rollback on custom builds
CastingDLNA and Miracast support on the base image; AirPlay and Google Cast receive paths on request
Input devices2.4G wireless mouse and keyboard support; IR remote; app-based control from phone or tablet
LanguageEnglish, French, German, Spanish, Italian and other multilateral languages
ApplicationsOnline browsing of video websites, support for Netflix, Hulu, Flixster and YouTube; applications from Android market and Amazon App Store; local media playback from HDD, U disk and TF card; email and office suite
Software servicesSDK development kit, BSP porting, driver adaptation, API development, system UI trimming, boot animation and pre-installed applications

Decode and format matrix: What the H618 media pipeline actually plays

The single most expensive misunderstanding on this platform is the frame rate per codec. The part decodes VP9 Profile-2, H.265 Main10 at L5.1 and AVS2 JiZhun 10-bit at 4K and 60fps, and it decodes H.264 at 4K and 30fps. Everything else in the list below tops out at 1080P and 60fps. Hand your content team this table before they author a single file.

FormatProfile and levelMaximum decode
VP9Profile-24K at 60fps
H.265 / HEVCMain10 at L5.14K at 60fps
AVS2JiZhun 10-bit4K at 60fps
H.264BP / MP / HP at L4.24K at 30fps
H.263BP1080P at 60fps
MPEG-4SP / ASP at L51080P at 60fps
MPEG-2MP / HL1080P at 60fps
MPEG-1MP / HL1080P at 60fps
Xvid--1080P at 60fps
Sorenson Spark--1080P at 60fps
VP8--1080P at 60fps
AVS / AVS+JiZhun Profile1080P at 60fps
WMV9 / VC1SP / MP / AP1080P at 60fps
AudioMP3, AAC, WMA, RM, FLAC, OggFull rate
ImageHD JPEG, BMP, GIF, PNG, TIFFull resolution

Read as a procurement rule: if your content pipeline outputs H.264 at 4K, you have already given up half the frame rate the part can deliver. Re-encoding to H.265 or VP9 is a free performance upgrade, and it is the first thing we flag in the feasibility study.

Interface layout and I/O map: Four positions, and no spares

The A18 is deliberately minimal: one HDMI output, two USB lanes, one IR receiver and one TF card socket. That is what keeps the bill of materials and the thermal envelope sane, and it is also why the interface positions and the lane allocation have to be agreed before the housing is cut. The map below is the standard allocation; the AS-H618-MPF-CUS re-spin can move any of it.

No.NameDefinitionNote for the custom build
1HDMIHDMI output at 4K*2K UHDTransmitter and cable qualification pinned at design freeze
2USBUSB host portReserved for keyboard, mouse, Ethernet bridge or local disk
3USB OTGUSB OTG portDoubles as the power input on most housings
4IRIR receiver and remote receiver connectionProfile tuned for the enclosure window material
5TF cardTF card socket, 4GB to 64GBOffline content store with the filesystem sized deliberately
6PowerDC 5V at 1.5A inputBlue LED when working, red LED on standby
7RTCReal-time clock with auto power-onCoin cell fitted and the schedule written before shipment
8UBOOTSystem software burn keyRecovery path for the A and B slot update scheme

Two positions on this map cause more field returns than the rest of the board combined: the power input and the lane that carries it. If USB OTG is the power path, the USB host lane is the only peripheral lane left, and that decision has to be made at schematic time rather than at integration time.

Power and electrical performance: DC 5V at 1.5A is the whole budget

The A18 runs on a single 5V supply rated at 1.5A. Unlike a board with a wide-input tree, there is no second rail to fall back on, so the supply is the system. The figures below are the specification limits, plus indicative bench measurements taken on the A18 reference build at 25C for budget planning.

ItemSpecification or measurementNote
Supply voltageDC 5VSpecification limit
Rated supply current1.5ASpecification limit
Working indicatorBlue LEDSpecification
Standby indicatorRed LEDSpecification
Idle, launcher resident, no playbackAbout 0.30AIndicative bench measurement
1080P at 60fps decodeAbout 0.58AIndicative bench measurement
4K at 60fps H.265 decodeAbout 0.94AIndicative bench measurement
Peak with WiFi streaming and a USB peripheralAbout 1.34AIndicative bench measurement, near the rated limit
Television USB-A host portOften 0.5AField observation, the most common brownout source
Long cable run sagCommonly 4.3V to 4.6VField observation, causes a reset at scene changes

Read as a system: the difference between the 1.34A peak and the 1.5A rating is 0.16A, and that margin is consumed by a single USB peripheral or by a cable run that is one metre longer than the one on the bench. The projector product manager in Madrid who budgets the adapter, the cable and the peripherals together never sees the random-reset failure mode.

Assembly and integration notes: Eight things that void a return

Every one of these is taken from the A18 constraints and from field returns we have handled, and every one of them belongs on the incoming QC sheet before the housing is closed.

  1. Power the unit from an adapter that actually delivers 1.5A. A television USB-A socket that delivers 0.5A will run the launcher and then reset the moment the decoder hits 4K. Ship a dedicated adapter in the box.
  2. Check the supply at the end of the cable, not at the adapter. A one-metre run commonly sags to between 4.3V and 4.6V, which is inside the reset window at scene changes. Measure under load.
  3. Decide the OTG and host lane allocation at schematic time. If USB OTG carries power, the host lane is the only peripheral lane left on the board.
  4. Qualify the HDMI cable for 4K at 60fps, not for 1080P. A cable that passes 1080P will drop a 4K link at the worst possible moment, and the symptom looks like a decoder fault.
  5. Fit the RTC coin cell and write the schedule before shipment. Without a clock source the scheduled power-on reverts to a manual press, and the property portal or the channel list never rejoins on time.
  6. Size the TF card filesystem deliberately. The socket reads 4GB to 64GB cards, but the image has to be built to index the whole card, and an offline content store grows faster than a content team expects.
  7. Match the IR window to the enclosure. A tinted window or a recessed receiver changes the profile, and the remote then reads only from certain angles.
  8. Never ship an OTA without a fallback slot. A single-slot update that fails mid-write turns a remote fleet into a truck roll, which is the most expensive failure mode on this platform.

Application matrix: 8 customization scenarios for the AS-H618-MPF-CUS

The H618 is one carrier platform across eight different commercial media deployments. The matrix below shows the most common OEM/ODM customization angles a projector product manager in Europe walks through in the first scoping call.

ScenarioCatalog board limitAS-H618-MPF-CUS customization
Android TV stick and streaming dongle9.4 s to first frame, no rollback slotLocal boot asset, A and B slot OTA
Digital signage and commercial playerNo remote OTA, one merged proof logCustomer-keyed OTA, per-screen proof-of-play
Wireless casting and meeting room11 s negotiation, Miracast onlyCached pairing, Miracast plus DLNA and AirPlay
Hospitality television dongle9 s welcome screen, session persistsLocal welcome asset, checkout teardown
IPTV and OTT operator stick4.2 s channel list, no kiosk lockCached channel index, operator launcher lock
Portable and pico projectorDesktop thermal policy, stick mechanicalsSealed-block thermal profile, re-laid-out board
In-vehicle rear-seat entertainment8 s first frame, no ignition senseLocal content store, ignition-sense shutdown
Multi-scenario OEM/ODM familyThree carriers, two BSP trainsOne carrier, one BSP train, one MOQ

OEM/ODM workflow: 8 steps from kickoff to first article

Below is the actual OEM/ODM workflow a projector product manager in Madrid walks through when commissioning a custom Allwinner H618 Android motherboard from AndroidSBC. No step is a placeholder.

  1. Day 0-2 - Requirements intake. A 90-minute call captures the housing, the display and the cable, the peripheral list and lane allocation, the OS and launcher choice, the content codec profile, the language list and the volume profile. Output: a one-page requirements sheet.
  2. Day 3-6 - Feasibility study. AndroidSBC engineers validate the memory and eMMC tier, the HDMI transmitter and cable qualification, the lane allocation for USB host and OTG, the WiFi and Bluetooth radio plan, the supply budget including the adapter, the BSP availability and the certification gap. Output: a feasibility report with go / no-go on each customization.
  3. Day 7-10 - Schematic and PCB layout. The AS-H618-MPF-CUS carrier board is laid out to the customer housing with the agreed I/O map and connector positions. Output: schematic and PCB review package.
  4. Day 11-13 - BSP porting. Android 12 AOSP or GMS is ported to the customer's build with kiosk-mode locking, scheduled power on and off on the RTC, the customer's launcher, and a local content cache. Output: a BSP build for the customer's evaluation team.
  5. Day 14-17 - Sample fabrication. Five to ten engineering samples are fabricated at the Shenzhen source factory, with conformal coating and stencil rework as required. Output: samples shipped to the customer by air.
  6. Day 18-21 - Customer evaluation. The customer's evaluation team runs display bring-up, thermal, EMC, decode matrix, peripheral integration, supply sag and field-replication tests. Output: an evaluation report with sign-off or change requests.
  7. Day 22-23 - Design freeze and mass-production tooling. Any change requests are absorbed, the design is frozen, and mass-production tooling is opened at the source factory. Output: a frozen Gerber and a frozen BOM.

Thirty days from kickoff to first article. Ninety-nine days from kickoff to mass production. This is the OEM/ODM rhythm that the projector product manager in Europe learns to expect from a Shenzhen source factory that does this work for a living.

Frequently asked questions

What is the MOQ for a custom Allwinner H618 Android board?
Answer: 150 units for OEM (a re-spin of the existing A18 carrier), 500 units for ODM (a from-scratch PCB layout). Sample orders of five units are accepted with an engineering report.

How long does OEM/ODM customization take from kickoff to first article?
Answer: 30 days on the workflow described above, including schematic, PCB layout, BSP porting, sample fabrication and customer evaluation. Mass production starts around day 99.

Can the board really do 4K at 60fps?
Answer: Yes, on VP9 Profile-2, H.265 Main10 at L5.1 and AVS2 JiZhun 10-bit. On H.264 the part tops out at 4K and 30fps, so a 4K H.264 asset will not run at 60fps on this platform.

Is there an Ethernet option?
Answer: Not on the A18 base board, which lists WiFi only. On a custom carrier we add a USB-to-Ethernet bridge at 10/100M or Gigabit on the host lane, and we document what that does to the supply budget.

Does the board support Bluetooth?
Answer: The A18 specification lists WiFi 802.11 a/b/g/n/ac/ax on 2.4G and 5.8G. Bluetooth 5.0 or 5.4 is available as a WiFi and Bluetooth combo module option on a custom build, which is what voice remotes need.

What power supply should we ship in the box?
Answer: A DC 5V adapter rated at 1.5A at the end of the cable, not a television USB-A socket that delivers 0.5A. Measure at the load, because a long cable run commonly sags to between 4.3V and 4.6V.

How big a TF card can we use?
Answer: The socket supports 4GB, 8GB, 16GB, 32GB and 64GB cards. On a custom build we size the filesystem so the whole card is indexed, which matters when the card is the offline content store for vehicles or classrooms.

Do you support Miracast, DLNA and AirPlay?
Answer: DLNA and Miracast are on the base image. AirPlay and Google Cast receive paths are ported on request, and the session negotiation is cached so a repeat cast starts in under two seconds.

What certifications can you pre-scope for our market?
Answer: CE / FCC / RoHS standard. UL / UKCA / KC / PSE / SAA, CCC, GMS and EDLA are available on request, and EMC pre-scanning is done in-house before third-party testing.

Do you accept sample and small-batch orders?
Answer: Yes. Samples ship in 1-3 days from stock where available; custom samples ship inside the 14-17 day window. Small-batch and large-volume pricing is available on request, FOB Shenzhen, CIF or an EXW price.