Skip to content

Office Address

1301, Building B, Smart Valley, Country Garden, No. 50, Tiezai Road, Xixiang Street, Bao'an District, Shenzhen, CN

Phone Number

+8613686469587

Email Address

[email protected]

Firmware & hardware engineering

Custom Android Firmware and Board Development

AOSP system work, middleware and DRM integration, private APIs, OTA and board-level modification — delivered on a firmware branch named for your SKU, by the same factory that later manufactures it.

RockchipAmlogicAllwinnerAOSP · Google TV

Firmware branches & OTA
PLATFORM BSP · MAIN YOUR-SKU BRANCH release-1.0 OTA · staged rollback plan

The full engineering stack

From Launcher Down to Device Tree and Board

One team owns all five layers, so a requirement never gets handed across a software–hardware gap.

  1. L5

    Application & provisioning

    What the end user and the operator touch.

    • Custom launcher
    • Kiosk / lock-down
    • Provisioning flow
    • Remote management hooks
  2. L4

    Middleware, DRM & content

    Secured content and operator platform integration.

    • DRM framework integration
    • CAS clients via partner SDK
    • Operator middleware
    • EPG / catch-up / VOD hooks
  3. L3

    Framework & AOSP

    System behaviour, policies and private APIs.

    • AOSP system customization
    • System API exposure
    • Permission & input policy
    • Multi-user / signage modes
  4. L2

    Kernel, BSP & device tree

    Bring-up, drivers and hardware abstraction.

    • Board bring-up & BSP
    • Kernel & device-tree config
    • Peripheral & tuner drivers
    • Power & thermal policy
  5. L1

    Hardware & modification

    Changes on qualified or newly designed boards.

    • Port / interface changes
    • Memory & connectivity options
    • Cellular & hybrid variants
    • DVT with factory tooling
What we build

Engineering scope on the table

  • AOSP and Google TV branch customization on qualified platforms
  • Boot experience, launcher, system UI and input behaviour
  • DRM framework and CAS client integration where licensed
  • Operator middleware, provisioning and private API endpoints
  • AV-over-IP, HDMI-CEC, serial and peripheral integration
  • Hardware variants: tuner, cellular, connectivity and port changes
How it ships

Named branch, versioned releases

  • A firmware branch named for your SKU, not a shared generic image
  • Structured releases with version notes and change log
  • OTA over your endpoint, with staged rollout where supported
  • Recovery path and rollback plan defined per platform
  • Security patches carried on active branches under a support plan
  • Source and licensing terms documented, including open-source obligations

How a custom project runs

From Engineering Brief to Field OTA: Five Stages

Software and board work follow one shared timeline, so a driver change and the plastic around the connector are validated on the same pilot lot.

  1. 01

    Engineering brief & platform check

    You send the requirement, target platform and any source or licence constraints. Engineering confirms feasibility, selects the right qualified board and names the engagement model before anything is quoted.

    Feasibility note + platform choice
  2. 02

    Scope & acceptance freeze

    Deliverables, interfaces, acceptance criteria and the responsibility split for licences, credentials and programme accounts are written into the statement of work.

    Signed scope & statement of work
  3. 03

    Named-branch development

    Work happens on a branch named for your SKU with a managed change set, weekly engineering reports and milestone builds you can flash and test on real devices.

    Milestone firmware builds
  4. 04

    Joint validation

    Software acceptance on production-intent units; where hardware changes are included, EVT/DVT builds pass through the factory process with ageing and functional test.

    Acceptance report (+ DVT if hardware)
  5. 05

    Field release & retained support

    The first OTA ships over your endpoint with the rollback path defined, followed by security-patch cadence and lifecycle component notices under a support plan.

    OTA release + support plan

How to engage

Three Ways to Buy Engineering Time

Fixed scope

A defined specification, deliverables list and acceptance criteria, quoted as one package. Best when requirements are already clear.

  • Scope frozen up front
  • Named deliverables
  • Acceptance criteria per release

Time & materials

Engineering time against an agreed backlog for exploratory work, platform evaluation or integration with your team.

  • Weekly engineering report
  • Backlog you can steer
  • Suits R&D and spikes

Retained firmware support

Ongoing branch maintenance, security patches and feature work for products already deployed in the field.

  • Patch cadence per branch
  • OTA release handling
  • Lifecycle component notices

The responsibility split

What You Bring, What DataMax Engineers

Embedded projects fail most often at ownership boundaries. This split is written into the SOW before the first commit — especially the licensed layers. Read more about how content-security licensing is arranged in the DRM & content security guide, and where new-tool engineering sits in the ODM process.

  • Your side Rights & source

    Access to your trees and brand assets

    Where work uses your AOSP tree, applications or trademarks, you grant access and confirm the rights. Mutual NDA terms are in place before code is shared.

  • Your side DRM / CAS accounts

    Provider agreements and credentials

    Widevine, CAS and operator-platform agreements, credentials and any provider fees remain with the rights holder; engineering integrates against the licensed SDK under that arrangement.

  • Your side Programme enrolment

    Google or operator programme membership

    For a certified target build the brand holds the programme enrolment and commercial agreement; DataMax drives the device through the technical requirements and submissions.

  • DataMax Branch & BSP

    Platform code and the named-SKU branch

    The maintained BSP for the chosen chipset, your customisation as a reviewed change set, and the branching and release structure documented for your team.

  • DataMax Integration & builds

    Middleware, private APIs and provisioning

    System, framework and application-layer integration, reproducible release builds, version notes and the packaging pipeline that feeds your OTA endpoint.

  • DataMax Documentation

    Source terms and open-source obligations

    A deliverables list, source-ownership schedule and open-source licence obligations are produced per release so compliance is never reverse-engineered after launch.

Engineering FAQ

Source, Chipsets, DRM and OTA

Want a complete new product rather than custom engineering? The ODM stage-gate process covers hardware design and tooling.

Can you work from our AOSP or Google TV source tree?

Yes. Where you control the source and rights, engineering works on your branch and follows your branching and review rules. Otherwise we build on the platform BSP we already maintain for the target chipset and apply your customisation as a managed set of changes.

Which chipsets do your engineers develop on?

Our TV box, signage and edge platforms span Rockchip, Amlogic and Allwinner families. Board bring-up, kernel and device-tree work is scoped per platform at the start of a project, and we recommend the chipset that matches the use case rather than forcing a favourite.

Can you integrate DRM or our operator’s CAS?

We integrate DRM frameworks and CAS clients — typically against the provider’s SDK under the licensing arrangement that applies to your project. Credentials, certification agreements and any provider-specific fees sit with the rights holder; we build and support the integration through joint qualification.

How do OTA updates and rollbacks work?

Releases are delivered from your OTA endpoint with versioned packages and, where the platform supports it, staged rollout and A/B or recovery-based rollback. The exact mechanism depends on the hardware partition scheme, and the recovery path is defined before the first field release.

Do we receive the source code?

That depends on the components. Your application and configuration source are delivered per the agreement; open-source code is provided under its licence obligations; and DataMax platform BSP and third-party code follow their ownership terms. Deliverables and source terms are listed in the statement of work rather than assumed.

Can hardware changes be included?

Yes. Small changes on a qualified board (ports, memory, connectivity, tuners) are handled as custom development, while larger changes route through the ODM stage-gate process with EVT and DVT builds. We recommend the lighter path whenever the existing tooling can be reused.

Who owns the intellectual property in a custom firmware project?

It is allocated by component in the statement of work, not left to goodwill. Your application code, assets and custom configuration are yours; the platform BSP, chip vendor code and third-party modules remain under their existing ownership and open-source licences; the custom layer DataMax writes for you is assigned or licensed according to the SOW. Trademarks, signing keys and operator credentials always remain with the brand. A clean IP schedule is part of every release package.

What does a realistic project timeline look like?

It is scoped after the brief rather than promised in the first email. A fixed-scope integration — launcher, provisioning or a peripheral driver on a qualified platform — typically runs in a matter of weeks on milestone builds; programmes involving board variants, operator certification or DRM joint qualification run in months. Hardware changes add EVT/DVT cycles on top. The SOW fixes milestones against dates so progress is measurable rather than open-ended.

How do we validate firmware before it reaches the field?

Validation starts on engineering samples of the actual product, not on reference boards: milestone builds are flashed on your units, a pilot lot runs the release candidate through factory ageing and functional test, and the first field deployment uses a staged OTA with rollback held ready. The samples and pilot process is the same flow described on the order samples page, so software validation and production validation never diverge.

Tell Us What the Stock Firmware Can’t Do

Send the requirement and target platform. Engineering replies with an approach, the right engagement model and an indicative scope.

Stay Updated with the Latest TV Box Trends

Subscribe to our newsletter and be the first to know about new products, OEM/ODM tips, exclusive offers, and factory updates.

Your experience on this site will be improved by allowing cookies.
Chat with us on WhatsApp