Android mainboards · Touch displays · Firmware — since 2013
Android mainboards · Touch displays · Firmware

Android hardware, engineered down to the firmware.

We design Rockchip and Amlogic mainboards, build them into touch displays and kiosks, and write the Android firmware that runs on them — so your device does exactly what your project needs.

Burn-in racks, assembly, panel testing and board testing in our Shenzhen factory
Real footage · our line in Shenzhen
2013Building Android hardware since
1,685+custom & development projects
235products developed
12boards documented in our public wiki
Inside every iTEMP device

Five layers. One team builds all of them.

Most suppliers assemble parts. We engineer the whole stack — which is why we can change any layer when your project needs it.

  1. Cover glass

    Tempered or anti-glare glass, sized and shaped to your enclosure.

  2. Touch sensor

    Projected-capacitive touch, matched to the panel and the enclosure.

  3. Display panel

    LCD and e-paper panels, from compact screens to 65-inch, including stretched and special shapes.

  4. Mainboard

    Our own KTM boards on Rockchip and Amlogic SoCs, with the I/O your device needs.

  5. Firmware

    Rooted Android builds with a system API, kiosk lockdown and OTA updates — written in-house.

Firmware & documentation

Firmware you actually control.

Our Android builds are rooted, so your app can manage the device directly — no platform signing, no device-owner workarounds.

  • System API. Power schedules, display, kiosk mode, network and GPIO from one class.
  • Kiosk lockdown. Hide the system bars and start your app on boot.
  • OTA updates. Ship firmware updates to devices already in the field.
  • Custom builds. Changing the firmware for your project is the service, not an exception.
MainActivity.javaPower schedule
// Every day: off at 23:00, on at 07:30
ItempApiPub.setPowerOffTime(context, "23", "0", "0", true);
ItempApiPub.setPowerOnTime(context, "7", "30", "0", true);
How a custom project runs

From first call to mass production.

See the ODM process
  1. Consult

    Requirements, SoC choice and a feasibility check.

  2. Sample

    Engineering samples with your firmware changes.

  3. Validate

    Testing on your side and a pilot run.

  4. Mass production

    Built and tested in our Shenzhen factory.

  5. After launch

    Firmware updates and documentation for your fleet.

Made in our factory

See the line for yourself.

Real footage from our floor in Longgang, Shenzhen — or come and see it in person.

Factory & quality
10-inch units on burn-in racks during quality control
Burn-inFinished units run one to two days before packing.
Test fixture used to check boards and modules before final assembly
Board testEvery board is flashed and checked on a fixture.
Technicians assembling and adjusting Android touch displays on the line
Dust-free roomCover glass and panels are joined away from dust.
FAQ

Questions engineers ask us first.

Answers come from our FAQ library — the same source the on-site assistant will use.

Web Publish #1

Web Publish #1

Do I need platform signing or device-owner mode to control the device?

No. iTEMP firmware runs with root (SU) privileges, so a normally signed APK — even a debug build — can call every function in our system API: power schedules, display, kiosk lockdown, network and GPIO.

On stock Android these actions need a platform key or device-owner provisioning; on our boards they are one method call. Start here: ItempApiPub overview.

What can you customize for our product?

Every layer, because we build all of them:

  • Firmware: system behaviour, kiosk lockdown, preinstalled apps, boot logo and animation, default settings, OTA delivery.
  • Mainboard: I/O mix (RS232/RS485, GPIO, LAN, USB), display interface, size and connector placement.
  • Display: panel, touch sensor and cover glass; open frame or finished unit, including stretched and special shapes.
  • Enclosure and branding.

See Engineering, or start a project.

Which SoC should I choose for my project?

Start from what the device must do:

Decision guide: AI or LLM and 3–4 screens point to RK3588 or RK3576; standard 4K signage to RK3568; low-power fanless designs to RK3566
Choosing a SoC by workload

Each chip has a reference page listing the boards that use it: SoC reference. Not sure? Describe your project and we will recommend a board.

Can I read the documentation before I buy?

Yes. The developer wiki is public, with no account and no NDA: board pin tables and serial maps, flashing and MaskRom recovery, the full system API and on-device AI guides. Engineers usually check it before choosing a board.

What is the minimum order quantity? Can we order samples first?

It depends on how much is customized: a standard board or display, modified firmware, or a fully custom device each have different minimums. Engineering samples are the normal first step of a custom project.

Share your expected quantity and timeline in Start a project, and we will reply with options for samples and production.

See all questions