How to Ensure Security and Compliance in Custom Secure Android Tablets Using Non-GMS Android and Third-Party MDM Solutions

Introduction

Custom Android devices—especially custom secure Android tablets—are critical tools in regulated industries like healthcare, finance, and logistics. Yet many organizations avoid Google’s default Android ecosystem due to privacy concerns about Google’s direct access to sensitive data through its proprietary services. Instead, they opt for non-GMS (Google Mobile Services) Android platforms combined with third-party mobile device management (MDM) tools to maintain control and compliance. This article explains how businesses of all experience levels can securely build, test, and manage compliant custom Android hardware without relying on Google services.

Why Some Companies Avoid Google’s Android by Default

Google’s Android platform, while popular, includes deep data collection through Play Services, app telemetry, and account synchronization. Lawsuits and regulatory scrutiny have exposed instances where Google collected user data without full consent—even with devices idle—triggering privacy concerns. These realities drive many private companies, especially in regulated sectors, to reject Google’s Android ecosystem in favor of greater transparency and control over sensitive device data. By using alternative software stacks, these organizations avoid exposing proprietary or personal data to Google, reducing regulatory risk and dependence on a single tech giant.

What Is a Non-GMS Android Device?

A non-GMS Android device runs the open-source Android code but excludes Google’s proprietary apps and services such as the Play Store and Google Maps. This gives manufacturers and IT teams complete control to customize apps, services, and update mechanisms. Popular non-GMS ROMs include LineageOS, GrapheneOS, and CalyxOS, which enhance privacy by disallowing data transmissions to Google’s servers by default.  It’s also possible to create a custom build of the Android OS without GMS or any other third party OS. Hatch customers often create their own apps and backend services to replace the ones from Google and other companies altogether.

Benefits of Non-GMS Android

  • No mandatory Google account or background data sharing
  • Freedom to customize OS and included applications
  • Increased suitability for privacy-sensitive and compliance-heavy industries
  • Compatible with a variety of third-party app stores and software

Challenges with Non-GMS Devices

  • Potential app compatibility issues for apps requiring GMS APIs (not relevant if the apps are created specifically for the custom Android OS)
  • Need to manage software updates independently from Google’s infrastructure
  • Create own integration and testing requirements

Quality Assurance for Non-GMS Android Hardware: Using CTS and Other Testing Tools

Despite the absence of Google services, non-GMS devices can undergo the same rigorous quality assurance testing as GMS devices through tools like the Android Compatibility Test Suite (CTS). CTS is an open-source, commercial-grade test suite provided by Google to verify that Android devices meet compatibility standards for the Android platform.

CTS verifies core Android APIs, platform stability, and hardware-software integration to ensure that apps function reliably across devices. It is the cornerstone for ensuring consistent behavior, avoiding software fragmentation, and future-proofing devices—even non-GMS customized models. Manufacturers can run CTS in continuous integration environments to catch issues early and validate core functionality before deployment.

For non-GMS devices, some CTS tests tied to Google services may be irrelevant or excluded, but the majority ensuring API consistency and device stability remain essential. Running CTS demonstrates commitment to quality and ensures custom tablets provide predictable, robust performance similar to mainstream devices. This testing raises confidence among customers and regulatory auditors alike.

Third-Party Mobile Device Management (MDM) for Non-GMS Devices

Why Third-Party MDM?

Without Google’s cloud services, enterprises rely on independent MDM providers like TinyMDM, Hexnode, Miradore, or our friends at Esper to securely manage and control their fleet of non-GMS tablets. These platforms enable:

  • Enrollment without Google accounts or Play Services
  • Remote app deployment, configuration, and policy enforcement
  • Real-time compliance monitoring and audit logging
  • Device lockdown, kiosk mode, and remote wipe features
  • Separation between corporate and personal data

Key MDM Features for Non-GMS Tablets

  • Remote Lock & Wipe protects devices if lost or stolen
  • Policy Enforcement locks down security parameters such as passwords and screen lock timeout
  • Kiosk Mode dedicates devices to specific apps or workflows, common in retail or service environments
  • App Whitelisting ensures only vetted apps run on managed devices
  • Automated Compliance Checks confirm data encryption and timely patching

Building a Custom Secure Android Tablet: Hardware and Software

Hardware Security Basics

  • Tamper-resistant enclosures and hardened cases prevent physical manipulation
  • Secure boot ensures only authorized firmware runs
  • Hardware-backed encryption increases data protection at rest
  • Durable materials and rugged design support industrial use

Software Approach

  • Choose a privacy-centric, non-GMS custom ROM like LineageOS or GrapheneOS
  • Use Android’s standard AOSP platform without embedding Google apps
  • Replace Google APIs with open-source microG or similar alternatives
  • Use alternative app distribution platforms such as F-Droid or Aurora Store or completely control which apps can or can’t run on the device
  • Implement verified boot, SELinux enforcement, and full-disk encryption
  • Maintain software updates independently, with MDM pushing patches

Data Protection and Authentication

Encryption Explained

Encryption scrambles device-stored data, requiring a key to decrypt. Activating encryption protects against data breaches from lost or stolen devices and is supported by most custom ROMs.

Authentication Strategies

  • Use passwords, pins, and biometrics
  • Employ multi-factor authentication (MFA) with independent providers
  • Centralize authentication policy management through MDM

App Ecosystem Without Google Play

  • Use open-source app stores for vetted applications or only load necessary apps at the factory level or using the MDM
  • Aurora Store for access to Play Store apps without Google accounts
  • Test app compatibility carefully to avoid disruptions

Compliance and Documentation

  • Maintain detailed logs of ROM versions, security patch levels, and configuration changes
  • Use third-party MDM for audit trails and regulatory compliance proofs
  • Ensure factory reset and data wiping processes comply with data protection laws

Vendor Considerations

  • Vendor support for non-GMS ROM installation and maintenance
  • Security patch guarantees provided by the chipset manufacturer or third-party MDM
  • Compatible with third-party MDM demonstrating experience with non-GMS fleets
  • Compliance documentation and audit assistance

Conclusion

Organizations increasingly reject Google’s default Android due to privacy and compliance concerns, especially regarding Google’s extensive data collection from devices. By building custom secure Android tablets on non-GMS platforms and managing them with trusted third-party MDM tools, companies gain total control over their data and device security while meeting stringent regulatory standards. With quality assurance through CTS testing identical to that used for mainstream Android devices, and strong hardware and software security practices, enterprises can confidently deploy secure, Google-free Android devices tailored to their needs. This approach safeguards sensitive information, enables customization, and future-proofs mobile hardware investments in privacy-conscious industries.

Understanding eFuse in Custom Android Device Development

Introduction: Why Hardware Security Matters

When people think about Android security, they usually picture passwords, biometrics, or encryption. But in the world of custom Android device development, security starts much deeper—at the hardware level. One of the most important but least understood tools in this space is the eFuse.

For companies designing and manufacturing their own Android hardware, eFuse technology plays a vital role in keeping devices secure, protecting intellectual property, and ensuring firmware integrity. It has become a key part of the production process for brands ranging from consumer smartphones to industrial IoT devices. In this article, we’ll dive into what eFuse is, how it works, who uses it, its advantages, drawbacks, and best practices for any team working on a custom Android device.

What is eFuse?

At its simplest, an eFuse (short for “electronic fuse”) is a tiny piece of programmable memory built directly into a system-on-chip (SoC). Unlike traditional storage, eFuse bits are one-time programmable (OTP)—once you “blow” a fuse, it permanently changes state and cannot be reversed.

Think of eFuse like a light switch that can only ever be flipped once. Once it’s set, there’s no turning it back. This permanent change makes eFuse especially useful for storing critical, security-related information such as:

  • Cryptographic keys for secure boot
  • Device identity information
  • Version numbers to prevent rollback attacks
  • Warranty and repair indicators

In the context of custom Android hardware manufacturing, eFuse provides a way to “lock in” important security decisions at the factory level, ensuring every device that ships is consistent and protected.

How Does eFuse Work?

Technically, eFuse works by physically altering tiny conductive links inside the chip. When a manufacturer programs an eFuse, a small electrical charge permanently blows that link, changing its binary value from 0 to 1 (or vice versa). Unlike flash memory, this change cannot be undone, rewritten, or erased.

From a software perspective, the system’s bootloader or operating system can query the state of these fuses during startup. For example:

  • If the secure boot eFuse is set, the bootloader will only load signed and verified firmware.
  • If an anti-rollback fuse indicates that version 3 is the minimum acceptable firmware, the device will refuse to boot version 2, even if someone tries to flash it.

This is how smartphone manufacturers prevent users—or attackers—from downgrading firmware to versions with known vulnerabilities. For custom Android device developers, this mechanism ensures that once the device is in the field, its software integrity can’t be easily bypassed.

Who Uses eFuse?

Nearly every major semiconductor and mobile manufacturer makes use of eFuse technology. Here are some of the most well-known examples:

  • Qualcomm: Uses eFuses for secure boot, device attestation, and digital rights management.
  • MediaTek: Integrates eFuses in its chipsets for bootloader security and rollback protection.
  • Samsung: Implements the famous “Knox Warranty Bit,” an eFuse that flips if a device is rooted or flashed with unofficial firmware.
  • NXP / STMicroelectronics: Apply eFuses in industrial and automotive contexts where tamper resistance is critical.
  • Apple (though not Android): Uses a similar concept for unique device identifiers and firmware locks.

For teams building a custom Android device, it’s helpful to know that the same eFuse mechanisms found in flagship smartphones are also available in the chipsets you might use for smaller-scale or specialized hardware projects.

Why is eFuse Useful in Custom Android Devices?

In today’s connected world, the stakes for device security are high. A vulnerability in your hardware can lead to data breaches, IP theft, or compromised user trust. eFuse is a powerful line of defense for several reasons:

  1. Secure Boot Enforcement
     With eFuse, you can lock a custom Android device so it only boots firmware signed by your team. This stops unauthorized software from running, protecting both your brand and your users.
  2. Rollback Protection
     By burning version numbers into eFuse, you can prevent attackers from downgrading a device to older, vulnerable firmware.
  3. Unique Device Identity
     eFuse can store cryptographic keys that make each device unique. This is essential for enterprise authentication, payment systems, or secure IoT applications.
  4. Intellectual Property Protection
     For OEMs, eFuse can help prevent cloning and counterfeit devices by ensuring only your signed software will run on your hardware.
  5. Compliance with Security Standards
     Many enterprise and government contracts require hardware-backed security features. eFuse helps custom Android hardware manufacturers meet these expectations.

Different Use Cases for eFuse

eFuse isn’t limited to smartphones. It plays a role in many categories of devices:

  • Consumer Electronics: Locking bootloaders in smartphones, tablets, and smart TVs.
  • Enterprise Devices: Ensuring company-owned devices can’t be rooted or modified.
  • Payment Terminals: Preventing tampering or unauthorized software installations.
  • Industrial IoT: Protecting edge devices that control critical infrastructure.
  • Network Equipment: Enforcing trusted firmware in routers, gateways, and custom Android-based modems.

For companies creating a custom Android device, the flexibility of eFuse means you can tailor its use to your industry—whether you’re building for consumers, enterprises, or specialized markets.

When eFuse May Not Be a Good Option

Despite its strengths, eFuse isn’t always the right choice. Its permanent nature introduces some challenges:

  1. Irreversible Changes
     Once an eFuse bit is set, it’s set forever. If you make a mistake in programming, there’s no undo button. This can be risky during prototyping or early production runs.
  2. Bricking Risks
     If a secure boot fuse is burned incorrectly, you can accidentally make a device unbootable.
  3. Overkill for Low-Security Devices
     Not every product needs the highest level of hardware security. For inexpensive consumer gadgets or short lifecycle products, eFuse might add unnecessary complexity.
  4. Limited Flexibility
     eFuse is not updatable. In contrast, software-based solutions (like trusted execution environments or secure elements) can sometimes be updated in the field.

Does eFuse Damage the CPU or Memory?

A common misconception about eFuse is that it “destroys” a chip if unauthorized firmware is loaded. In reality, that’s not how eFuse works.

eFuse does not burn out the CPU or physically damage memory. Instead, it serves as a security checkpoint. When firmware doesn’t match what the eFuse values expect, the system simply refuses to boot. To the user, this might look like the device is “bricked,” but it’s actually a protective lockout — not hardware destruction.

For example:

  • In a custom Android device, if secure boot fuses are set, the bootloader will only accept signed firmware. Any tampered or downgraded version will be blocked at startup.
  • In Samsung devices, the Knox eFuse flips if unofficial firmware is installed, permanently disabling some features — but the hardware remains intact.

True “self-destruct” mechanisms do exist in certain military or defense chips, but consumer-grade SoCs from Qualcomm, MediaTek, or NXP don’t use eFuse this way. For most device makers, the worst-case scenario is a device that won’t boot unauthorized code, not one that fries its CPU.

Best Practices for Using eFuse in Custom Android Hardware

If you decide to leverage eFuse in your product, here are some practical guidelines:

  • Program eFuses at the End of Manufacturing
     Don’t burn critical fuses during prototyping. Wait until final testing and quality assurance.
  • Double-Check Your Keys and Versions
     Build strict workflows to verify signatures, hashes, and version numbers before programming.
  • Pair eFuse with Other Security Features
     Combine with TPMs, secure elements, or software-based integrity checks for layered security.
  • Work Closely with Chipset Vendors
     Documentation from companies like MediaTek and Qualcomm can be complex. Rely on their resources to avoid costly mistakes.

For OEMs and startups alike, eFuse is best handled with a cautious, structured process—especially when building custom Android devices at scale.

Closing Thoughts

eFuse is one of those hidden technologies that quietly powers the security of many modern smartphones, IoT devices, and custom Android devices on the market. It provides a permanent, tamper-resistant anchor for security decisions, ensuring that only trusted software can run on your hardware.

But with that power comes responsibility. Once you burn an eFuse, there’s no going back. For device makers, this means balancing the benefits of bulletproof security with the risks of irreversibility.

At Hatch, we help companies navigate these trade-offs in custom Android hardware manufacturing. Whether you’re designing for consumers, enterprises, or industrial markets, understanding eFuse is key to building secure, reliable, and trusted devices.

How Google VTS Helps Custom Android Manufacturers Build Better Devices

Designing and manufacturing a custom Android tablet involves more than selecting components and installing Android. Achieving system reliability, performance consistency, and long-term maintainability requires thorough validation of how the Android operating system interfaces with the hardware. This is especially true when building custom devices with unique hardware requirements, advanced sensors, or niche-use applications.

Among the system integrity verification tools provided by Google, the Vendor Test Suite (VTS) plays a critical role in ensuring that a device’s low-level software aligns with Android’s standards. VTS is not as well-known as CTS (Compatibility Test Suite), but it addresses a foundational part of the Android system—the interface between the operating system and the underlying hardware.

This article provides a detailed overview of VTS: what it does, how it works, why it matters, when to use it, and how it benefits devices both with and without Google Mobile Services (GMS). It also includes other valuable tools that a custom Android manufacturer like Hatch uses to build stable, secure Android products.

What Is Google VTS?

The VTS is a set of automated tests developed by Google to validate the vendor implementation layer in Android. This layer includes:

  • The Linux kernel
  • Device drivers (e.g., for Wi-Fi, audio, USB)
  • Hardware Abstraction Layers (HALs), which allow Android to communicate with hardware in a consistent and modular way
  • SELinux policies and other low-level security configurations

These components live in the /vendor partition, which is separate from Android’s /system partition. This separation was formalized under Project Treble, which was introduced in Android 8.0 to make Android more modular and easier to update across different hardware platforms.

VTS ensures that the vendor partition is implemented in compliance with Android’s standards, promoting system stability and upgradeability.

Why VTS Matters in Custom Android Development

Devices built using the Android Open Source Project (AOSP) often include customized hardware. These may be tablets with industrial sensors, medical interfaces, rugged housing, or enterprise-specific software stacks. Custom HALs and drivers must be written to make these hardware components work properly with Android.

The challenge arises when these low-level components are not implemented correctly or diverge too far from Android’s standards. This can result in:

  • Unpredictable behavior under stress or over time
  • Incompatibility with future Android versions
  • Security vulnerabilities due to misconfigured access policies
  • Failure to pass certification tests if GMS is required

Running VTS helps identify and correct these issues during the development cycle. It verifies that HALs, kernel drivers, and SELinux configurations meet strict guidelines—reducing risk during deployment and post-launch updates.

Benefits of VTS for Devices with GMS

Devices that include Google Mobile Services (GMS) must pass a suite of compatibility and quality tests defined by Google. This includes CTS, GTS (Google Test Suite), and other security and performance benchmarks.

While VTS is not mandatory for GMS certification, it strongly supports the certification process in several ways:

  • Prevents HAL or driver issues that could cause CTS failures
    CTS tests rely on stable HAL implementations. If a device’s camera, Wi-Fi, or sensor HAL is unstable, CTS may fail.
  • Improves system robustness, reducing GTS and field failures
    GMS includes background services, analytics, and auto-updating apps that can stress test a device in real-world usage. A solid vendor implementation reduces crash rates and system errors reported back to Google.
  • Ensures readiness for future Android versions
    GMS-certified devices are often required to support at least one major Android update. VTS compliance helps ensure that vendor-specific code won’t block future upgrades.

In summary, VTS complements CTS and GTS by focusing on the foundation: if the base layers of the system are not stable, app compatibility and user experience cannot be guaranteed.

Benefits of VTS for Devices without GMS

For custom Android devices that do not include GMS, VTS is equally important.

Non-GMS devices often serve specialized roles: point-of-sale terminals, kiosks, rugged industrial tablets, educational devices, or region-specific products that do not rely on Google services. These products may not be subject to Google’s certification requirements, but they still need to:

  • Maintain system stability under load
  • Provide long-term software support
  • Support regulatory and enterprise certifications
  • Reduce development and maintenance costs

In short, for any custom Android manufacturer serving enterprise or industrial markets, VTS helps avoid costly support issues and accelerates product reliability.

How VTS Works: A High-Level Overview

VTS is executed from a host Linux machine connected to the device via ADB (Android Debug Bridge). It uses Trade Federation (TradeFed), a test harness that controls the test execution and collects results.

VTS includes a wide range of test categories:

Test TypeWhat It Does
HAL Interface TestsEnsures HALs follow AIDL or HIDL interface definitions
Kernel API TestsChecks system calls, memory access, and driver behaviors
SEPolicy TestsVerifies SELinux security policies are not overly permissive
Binder FuzzingTries unexpected data inputs to test system robustness
Device Tree and Boot Config TestsConfirms system configuration files are correct

Each module produces pass/fail results, with detailed logs that guide developers in fixing issues.

How VTS Fits into the Product Development Lifecycle

A typical custom Android manufacturer integrates VTS into multiple stages:

StageUse of VTS
Early PrototypingRun targeted VTS modules to catch hardware-specific bugs
BSP FinalizationRun the full suite before vendor code is considered stable
Pre-Certification (GMS or internal QA)Combine VTS with CTS, GTS, and CTS Verifier for full validation
Factory QA (Optional)Spot-check units during production to ensure consistency

This staged approach ensures alignment with Android standards throughout development.

VTS vs. Other Android Test Suites

Several other Android test suites complement VTS in different areas:

SuitePurposeBest For
CTSTests Android APIs and app behaviorRequired for GMS certification
CTS VerifierManual tests for sensors, displays, USB, etc.Hardware integration QA
GTSTests Google apps and servicesGMS validation
Monkey / MonkeyRunnerSimulates random UI inputsStability under stress
Burn-In TestsSimulates real-world continuous usageFactory and batch QA
Syzkaller / AFLKernel fuzzing toolsAdvanced security validation

Together with VTS, these tools form a complete QA strategy for any custom Android tablet project.

Common Causes of VTS Failures

The most common VTS failures stem from issues such as:

  • Incorrect or incomplete HALs
  • Misconfigured SELinux policies
  • Non-compliant kernel drivers
  • Improper system properties or boot parameters

Addressing these issues often requires coordination between the firmware team, kernel engineers, and platform developers—a process where an experienced partner like Hatch provides clear value.

Conclusion: Why Every Custom Android Manufacturer Should Use VTS

The Vendor Test Suite provides a foundation for building a high-quality, long-lasting Android device. Whether a product includes GMS or operates independently, VTS delivers benefits in the form of greater system stability, easier OS upgrades, and better long-term maintainability.

For any custom Android manufacturer, incorporating VTS into the development process leads to:

  • More reliable hardware-software integration
  • Fewer bugs during and after deployment
  • Faster certification and time-to-market
  • Lower post-sale support costs

Hatch is a global custom Android manufacturer offering full-stack engineering services for hardware, firmware, and certification support. From HAL development to VTS, CTS, and GMS compliance, Hatch ensures that every custom Android tablet meets the demands of modern enterprise, industrial, and commercial markets.

Contact Hatch to explore how Android testing and compliance services can improve product quality and reduce development risks.

Using Android CTS for Non-GMS Custom Android Hardware

As an open source platform, Android is customizable by design. This comes with advantages and disadvantages. The advantage is that custom Android products can be designed with flexibility to support countless applications. The disadvantage is that customization leads to inconsistency in specs and performance. Google manages the tradeoff by providing a readily available testing platform, the Android Compatibility Test Suite (CTS), that serves to ensure the core functionality of Android devices meet a standardized set of operational protocols. This means that whatever a custom Android device is used for, apps will all perform with consistency and as intended.

The CTS is a cornerstone of the Android ecosystem. Passing CTS is a prerequisite of obtaining the Google Mobile Services (GMS) certification, the required certificate for embedding Google’s apps into Android devices, but can also be run on non-GMS devices. Passing CTS is critical for aligning the multitude of developers and manufacturers that build custom Android hardware as it provides a robust framework for validating device quality, stability, and consistency. This article explains what CTS is, how it works, and why it is invaluable for testing custom Android hardware, regardless of whether they eventually get GMS certification or not.

What is Android CTS?

The Android Compatibility Test Suite (CTS) is a free, commercial-grade set of software tools and automated tests used to verify that Android devices meet compatibility standards defined by Google. The suite is intended for integration into the daily workflow of engineers and can be executed on a desktop machine, directing tests to attached devices or emulators. CTS is built to reveal incompatibilities early in the development process, ensuring that Android implementations remain compatible throughout the product lifecycle.

Key Components of CTS

  • Trade Federation: A test harness and framework enabling automated execution of tests.
  • CTS Automated Tests: Unit and functional tests that run using the Trade Federation framework.
  • CTS Verifier (CTS-V): A set of manual tests (and an accompanying app) for features requiring human interaction, such as sensors, audio, and camera functions.
  • Test Cases: Individual tests (usually JUnit-based, packaged as APKs) executed on the Device Under Test (DUT).
  • Test Plans and Modules: Collections of test cases organized by feature area or specific use cases.

How Does CTS Work?

The workflow for running CTS is straightforward but rigorous:

  1. Download and Install CTS: The test environment is set up on a workstation, and the device to be tested is connected.
  2. Run Automated Tests: The CTS harness pushes test APKs to the device, executes them, and collects results.
  3. Review and Troubleshoot: Results are stored, reviewed, and analyzed. Failed tests may be rerun or debugged as needed.
  4. Iterate: The process is repeated throughout development to maintain compatibility and quality.

CTS automated tests cover a wide range of Android APIs and core platform features. They include unit tests (testing atomic code units), functional tests (combining APIs for real-world scenarios), robustness tests (system stress), and performance tests (benchmarking). The CTS Verifier app handles manual tests for features that cannot be automated, such as accelerometer or audio quality checks.

Why CTS is Essential for Custom Android Hardware Ensuring Platform Compatibility

Custom Android hardware—whether built for enterprise, industrial, or specialized consumer use—must still adhere to Android’s core standards to ensure reliable operation and compatibility with third-party applications. CTS provides a standardized benchmark for this compatibility, regardless of whether the device ships with GMS. By running CTS, manufacturers can identify and resolve issues early, reducing the risk of software bugs and incompatibilities that could undermine device performance or user experience.

Benefits for Non-GMS Android Hardware

Non-GMS Android hardware refers to devices that do not include Google Mobile Services—meaning they lack access to Google Play, Gmail, Maps, and other proprietary Google apps and Google’s APIs. Such devices are often deployed in closed environments, for specialized use cases (e.g., kiosks, digital signage, industrial controllers), or in regions where Google services are restricted.

Even without GMS, these devices must still run Android applications reliably, and CTS is the best tool to ensure this. Here’s why:

  • API Consistency: CTS verifies that the device’s implementation of Android APIs matches the standard, so third-party apps (including those not reliant on GMS) will function as expected.
  • Quality Assurance: CTS includes robustness and performance tests, helping to ensure that custom hardware is stable and efficient under various conditions.
  • Future-Proofing: As Android evolves, CTS tests are updated to reflect new API requirements and best practices. Running CTS helps ensure that custom hardware remains compatible with future Android releases.

Flexibility and Control

For non-GMS and custom Android hardware, manufacturers have greater flexibility in provisioning, deploying, and updating devices. However, this flexibility also means taking on more responsibility for quality assurance. CTS provides a standardized, repeatable process for validating device software, reducing the risk of fragmentation and incompatibility that can plague custom Android implementations.

Integration with Development Workflows

CTS is designed to be integrated into continuous integration (CI) systems, allowing for automated, ongoing testing throughout the development lifecycle. This integration is especially valuable for custom hardware projects, where rapid iteration and validation are critical to meeting project timelines and quality goals.

CTS in Practice: Testing Non-GMS and Custom Hardware Setting Up and Running CTS

To run CTS on custom Android hardware (with or without GMS), follow these general steps:

  1. Prepare the Environment: Install the required dependencies (Java, Python, ADB, AAPT) and download the appropriate CTS package for your Android version.
  2. Connect the Device: Enable USB debugging and developer mode on the device.
  3. Run CTS: Launch the CTS console and execute the desired test plan. For large test suites, consider using test sharding to distribute tests across multiple devices and reduce execution time.
  4. Review Results: Analyze test results, rerun failed tests, and debug issues as needed.

Addressing Non-GMS Specifics

Since non-GMS devices do not include Google’s proprietary apps and services, some CTS tests that rely on GMS may fail or be irrelevant. However, the vast majority of CTS tests focus on core Android APIs and platform features, which are still critical for any custom hardware. Manufacturers can exclude GMS-specific tests or focus on the modules most relevant to their device’s use case.

Custom Test Plans

CTS allows for the creation of custom test plans, enabling manufacturers to focus on the specific features and APIs relevant to their hardware. This targeted approach saves time and ensures that testing resources are allocated efficiently.

The Broader Impact of CTS on the Android Ecosystem

CTS is more than just a tool for individual manufacturers. It is a key mechanism for maintaining consistency and quality across the diverse Android ecosystem. By requiring devices to pass CTS (and related suites like VTS for hardware abstraction and GTS for GMS compatibility), Google ensures that users and developers can rely on a consistent experience, regardless of the hardware or software customization.

For non-GMS and custom Android hardware, passing CTS is not a strict requirement (since GMS certification is not needed), but it remains the best practice for ensuring device quality and compatibility. Manufacturers who invest in CTS testing demonstrate a commitment to quality and are better positioned to succeed in competitive markets.

Conclusion

The Android Compatibility Test Suite (CTS) is an indispensable tool for anyone developing custom Android hardware—including non-GMS devices. By providing a comprehensive, standardized framework for testing Android compatibility, CTS helps manufacturers ensure that their products are stable, reliable, and compatible with the broader Android ecosystem. Even without Google Mobile Services, CTS remains the gold standard for quality assurance in custom Android hardware, enabling manufacturers to deliver high-quality products that meet both user expectations and industry standards.

Key Takeaways

  • CTS is a free, commercial-grade test suite for verifying Android compatibility.
  • It is essential for custom Android hardware, including non-GMS devices.
  • CTS ensures API consistency, quality, and future-proofing for custom hardware.
  • The suite is flexible, allowing for targeted testing and integration into development workflows.
  • Even without GMS, CTS is the best tool for validating the quality and compatibility of custom Android hardware.

For manufacturers of non-GMS Android hardware and custom Android solutions, investing in CTS testing is a strategic decision that pays dividends in product quality, user satisfaction, and market success.

Exploring Custom Android Hardware

At Hatch, we manufacture custom Android hardware that adapts to a wide range of industries and applications. The Android platform’s open architecture and flexibility enable us to design custom Android tablets tailored to meet unique operational requirements. In this article, we highlight two diverse examples that showcase how custom Android tablets can be engineered to deliver exceptional value, functionality, and reliability across vastly different environments.

Custom Android Tablet for Laboratory and Product Inspection

One of the most compelling justifications for making a custom Android tablet is to facilitate the delivery of a high value service. Relative to the cost of the custom Android device, there’s a lot of money connected to laboratory testing and product quality inspection. One oversight that occurs when testing medications, chemicals, materials or inspecting high volume consumer products before they leave the port could cost millions of dollars in lost development, product, or reputation cost. Accuracy, accountability, and efficiency are critical.

Use Case and Value

This device is designed for use at elite laboratories across biology, chemistry, physics, and other scientific fields to document and verify experiment and inspection processes. This standing tablet has two cameras—one front-facing to capture the inspector’s identity via facial recognition, and an elevated camera, looking down, to record the item being inspected—the tablet ensures full transparency and traceability.

At a cost of less than $200 per unit in volumes above 5,000, this custom Android tablet offers a highly affordable solution in the world of thousand dollar tests and inspections in precision or medical equipment inspections. By video recording inspection workflows, it eliminates the risk of bribery or human error that historically plagued quality control, protecting companies from costly defective shipments and damaged business relationships.

Key Features

  • Powerful Hardware: Eight-core Rockchip RK3576 CPU, 10″ IPS display, 4GB DDR RAM, 64GB flash storage, Wi-Fi and Bluetooth connectivity.
  • Dual Cameras: Front camera for facial recognition and elevated camera for detailed inspection recording.
  • AI-Driven Inspection: Machine learning algorithms confirm completed inspections, track inspection duration, and detect potential defects missed by inspectors.
  • Accountability: Enhanced quality control through digital evidence and inspector verification.

Custom Android Tablet for Industrial Inspection and Patrol

In stark contrast, our second example is a rugged custom Android tablet built into a high power flash light. Engineered for frontline inspection and patrol operations in industries such as railway maintenance, chemical plants, security, and power grid monitoring, this custom Android device turns frontline workers into productivity powerhouses.

Use Case and Value

This custom Android device is a digital toolbox serving as a multifunctional inspection assistant that enhances worker safety, operational accuracy, and communication in hazardous and challenging environments. It integrates advanced high powered lighting, high-precision positioning technology, hazardous gas detection, and real-time voice and video communication into a single, ruggedized Android platform.

Detailed Specifications and Features

  • Hardware Platform: MediaTek Helio G36 2.2GHz processor, paired with 3GB RAM + 32GB eMMC storage.
  • Display: 2.8-inch IPS touchscreen (640×480 resolution) with 2-point touch capability.
  • Cameras:
    • Main autofocus 13MP camera
    • Secondary 2MP fixed-focus macro camera for close-up detail.
  • Lighting System:
    • White floodlight (≥5 Lux at 3 meters) with two brightness modes.
    • Powerful spotlight (>1500 Lux at 1 meter).
    • Warning lights with red and green LEDs for train alerts.
    • Red and blue strobe lights for emergency signaling.
    • Laser positioning module for precise location marking.
  • Battery: Built-in 5000mAh battery (or an optional 10,000mAh for extended use), supporting over 8 hours of continuous video recording and over 6 hours of continuous lighting.
  • Communication:
    • Wide cellular network support including TDD-LTE, FDD-LTE, GSM, and WCDMA bands.
    • Wi-Fi 802.11ac (2.4G/5G), Bluetooth 5.0, NFC support.
    • Dual microphones with noise cancellation and AI echo suppression for clear voice communication.
    • Push-to-talk (PTT) and real-time voice/video communication.
  • Positioning:
    • Built-in GPS/Beidou module with RTK compatibility for centimeter-level accuracy (<1m).
    • Supports multiple Beidou frequency bands.
  • Hazardous Gas Detection: Optional modular sensors for detecting gases such as CO2, ammonia, methane, hydrogen sulfide, carbon monoxide, and chlorine.
  • Durability: IP65-rated rugged design, drop resistant up to 1.5 meters, operating temperature range -10°C to 55°C.
  • Additional Features: Magnetic attachment for hands-free use, multiple physical buttons for quick operation (power, photo, video, PTT, flashlight), and a Type-C USB port supporting OTG.
  • Software: Runs Android 10.0, enabling extensive customization and integration with third-party inspection and dispatch systems.

The Flexibility of Custom Android Hardware

These two products illustrate the incredible versatility of custom Android hardware. Whether it’s a sleek tablet designed for precise laboratory documentation or a rugged, multifunctional device built for frontline industrial use, Android’s open ecosystem allows Hatch to tailor devices to exacting specifications.

  • Cost-Effective Innovation: Custom Android tablets bring proven enterprise-grade features at affordable prices, enabling industries to upgrade workflows without prohibitive costs.
  • Hardware Customization: From specialized cameras and sensors to advanced positioning and communication modules, Android hardware can be adapted to any environment and use case.
  • Software Integration: The Android platform supports machine learning, facial recognition, and real-time data processing, empowering smarter, more accountable operations.
  • Scalability: Whether deploying hundreds or thousands of units, custom Android hardware solutions scale to meet growing business needs.

Why Choose Hatch for Your Custom Android Tablet Needs?

No two industries or applications are alike. Our experience in designing and manufacturing niche custom Android hardware enables us to deliver tailored solutions that maximize performance, reliability, and cost-efficiency. By leveraging the flexibility of the Android platform, we help businesses create value and drive innovation.

If you’re interested in exploring how a custom Android tablet can transform your operations—whether for laboratory testing, industrial inspection, or beyond—contact Hatch today. Let’s build the future of Android hardware together.

Custom Android Smartphone CPU Review

As the third part of the Android CPU review, this month we cover the most popular Android smartphone CPUs. Custom Android devices which use a smartphone chipset generally require mobile data support and have a screen size smaller than 6.5 inches. Some smartphone CPUs will support a larger screen size and make their way into tablet size devices.

When tablet-size devices use smartphone chipsets it’s usually a cost driven decision. Using a smartphone CPU in a tablet only works for tablets which have lower resolution screens. The main difference between CPUs for tablets which support mobile data and smartphones CPUs is their resolution support. Smartphone CPUs don’t support as high of a screen resolution as tablet CPUs.

There’s a big price difference between 4G and 5G CPUs. 4G meets the demands of most custom Android devices, so that’s still the prevalent choice for Hatch’s customers and why we focus on them. Even though mainstream consumer models use 5G, smartphone CPU manufacturers still release 4G models.

Due to Mediatek’s overall competitive advantages, including the ease of customizing hardware and firmware, this list includes exclusively Mediatek chips. Here’s the list of the most common Android smartphone CPUs we consider for new projects:

MediaTek MT8766

The MediaTek MT8766 is a quad-core processor designed for entry-level smartphones and tablets. It features four ARM Cortex-A53 cores clocked at up to 2.0 GHz, providing efficient performance for everyday tasks. Manufactured using a 12nm process, the MT8766 balances power efficiency with adequate processing capabilities. The integrated IMG PowerVR GE8300 GPU supports basic graphics rendering, suitable for standard applications and media playback. The chipset supports LPDDR3 and LPDDR4X memory types, ensuring compatibility with various device configurations. Connectivity options include 4G LTE, Wi-Fi 5, and Bluetooth 5.0, catering to essential communication needs. The MT8766 supports camera resolutions up to 13MP and video playback at 1080p, making it suitable for basic photography and video consumption. Its design focuses on delivering a cost-effective solution for budget-friendly devices without compromising on essential features.

MediaTek Helio G36

The MediaTek Helio G36 is an entry-level octa-core processor launched in March 2023. It comprises four Cortex-A53 cores at 2.2 GHz and four Cortex-A53 cores at 1.8 GHz, offering a balance between performance and power efficiency. Built on a 12nm process, the G36 is optimized for budget smartphones, providing reliable performance for daily tasks. The integrated IMG PowerVR GE8320 GPU, clocked at 680 MHz, supports graphics rendering for casual gaming and media playback. The chipset accommodates LPDDR4X memory up to 8GB and eMMC 5.1 storage, ensuring smooth multitasking and data handling. Connectivity features include 4G LTE Cat-7, Wi-Fi 5, and Bluetooth 5.0, facilitating seamless communication. The G36 supports camera configurations up to 50MP and video capture at 1080p, catering to basic photography and videography needs. Its design emphasizes affordability while delivering essential smartphone functionalities.

MediaTek Helio G37

The MediaTek Helio G37 is an entry-level octa-core processor introduced in June 2020, designed for budget-friendly smartphones. It features four Cortex-A53 cores clocked at 2.3 GHz and four Cortex-A53 cores at 1.8 GHz, delivering efficient performance for everyday tasks. Manufactured using a 12nm process, the G37 ensures a balance between power efficiency and performance. The integrated PowerVR GE8320 GPU, operating at 680 MHz, supports graphics rendering suitable for casual gaming and media playback. The chipset supports LPDDR4X memory up to 8GB and eMMC 5.1 storage, facilitating smooth multitasking and data handling. Connectivity options include 4G LTE Cat-7, Wi-Fi 5, and Bluetooth 5.0, ensuring reliable communication. The G37 supports camera configurations up to 50MP and video capture at 1080p, catering to basic photography and videography needs. Its design emphasizes affordability while delivering essential smartphone functionalities.

MediaTek Helio G81

The MediaTek Helio G81 is a mid-range octa-core processor launched in August 2024, designed for gaming and multimedia applications. It comprises two Cortex-A75 cores at 2.0 GHz and six Cortex-A55 cores at 1.8 GHz, providing a balance between performance and power efficiency. Built on a 12nm process, the G81 ensures optimal energy consumption. The integrated Mali-G52 MC2 GPU, clocked at 950 MHz, delivers enhanced graphics performance for gaming and media tasks. The chipset supports LPDDR4X memory up to 8GB and storage types including eMMC 5.1 and UFS 2.1, facilitating smooth multitasking and faster data access. Connectivity features encompass 4G LTE, Wi-Fi 5, and Bluetooth 5.4, ensuring reliable communication. The G81 supports camera configurations up to 48MP and video capture at 2K resolution, catering to advanced photography and videography needs. Its design emphasizes delivering robust performance for gaming enthusiasts and multimedia consumers.

MediaTek Helio G99

The MediaTek Helio G99 is a high-performance octa-core processor introduced in May 2022, targeting mid-range smartphones with gaming capabilities. It features two Cortex-A76 cores at 2.2 GHz and six Cortex-A55 cores at 2.0 GHz, offering a blend of performance and efficiency. Manufactured using a 6nm process, the G99 ensures superior power efficiency and thermal management. The integrated Mali-G57 MC2 GPU, clocked at 1100 MHz, delivers robust graphics performance for gaming and multimedia applications. The chipset supports LPDDR4X memory up to 12GB and UFS 2.2 storage, enabling swift multitasking and rapid data access. Connectivity options include 4G LTE Cat-13, Wi-Fi 5, and Bluetooth 5.2, ensuring seamless communication. The G99 supports camera configurations up to 108MP and video capture at 2K resolution, catering to high-quality photography and videography. Its design focuses on delivering top-tier performance for gaming and multimedia enthusiasts in the mid-range segment.

Comparison Matrix

Specification MT8766 Helio G36 Helio G37 Helio G81 Helio G99
Launch Date
2020
March 2023
June 2020
August 2024
May 2022
CPU Cores
4x Cortex-A53
8x Cortex-A53
8x Cortex-A53
2x A75 + 6x A55
2x A76 + 6x A55
Max CPU Frequency
2.0 GHz
2.2 GHz
2.3 GHz
2.0 GHz
2.2 GHz
Process Technology
12nm
12nm
12nm
12nm
6nm
GPU
PowerVR GE8300
PowerVR GE8320
PowerVR GE8320
Mali-G52 MC2
Mali-G57 MC2
Max GPU Frequency
660 MHz
680 MHz
680 MHz
950 MHz
1100 MHz
Max Display Res
1920×1200
2400×1080
2400×1080
2520×1080
2520×1080
Max Camera Res
13MP
50MP
50MP
48MP
108MP
Memory Type
LPDDR3/LPDDR4X
LPDDR4X
LPDDR4X
LPDDR4X
LPDDR4X
Max Memory Size
4GB
8GB
8GB
8GB
12GB
Storage Type
eMMC 5.1
eMMC 5.1
eMMC 5.1
eMMC 5.1 / UFS 2.1
UFS 2.2
Video Capture
1080p @ 30fps
1080p @ 30fps
1080p @ 30fps
2K @ 30fps
2K @ 30fps
Video Playback
1080p @ 30fps
1080p @ 30fps
1080p @ 30fps
2K @ 30fps
2K @ 30fps
Connectivity
4G, Wi-Fi 5, BT5
4G Cat-7, Wi-Fi 5, BT5
4G Cat-7, Wi-Fi 5, BT5
4G, Wi-Fi 5, BT 5.4
4G Cat-13, Wi-Fi 5, BT 5.2
AI Processor (NPU)
No
No
No
Yes
Yes
TDP (est.)
~2W
~2.2W
~2.2W
~5W
~5W

Custom Android Tablet with Mobile Data CPU Review

Last month’s article went over popular Android Wi-Fi tablet CPUs.  This month we’ll review popular CPUs with Wi-Fi and mobile data for use in custom Android tablet projects.  The main difference between Android Wi-Fi tablet CPUs and mobile data equipped Android tablet CPUs is that the tablet CPUs have mobile data connectivity.  Otherwise they’re the same.

Android tablet CPUs with mobile data are used in products that need internet connectivity in the absence of Wi-Fi.  Custom Android devices are commonly used in third party environments, meaning the owner of the devices uses the local infrastructure, like Wi-Fi, that’s provided by a different entity.  Therefore, having a backup way to connect to the internet, like mobile data, means the device won’t go offline if it can’t connect to Wi-Fi.

The decision to include mobile data functionality in a custom Android tablet should be based on the use case and use environment of the device.  As a general rule, an Android device with mobile data has a higher hardware cost than one with Wi-Fi only, so there should be a reason to justify the extra cost of including it.

This CPU review focuses on popular CPUs used in custom Android tablets.  Custom Android products differ from mass market retail devices in large part because custom devices don’t usually need the newest and highest performing CPUs.  Customers’ primary demands of custom Android tablets include long term supply, stable performance, and reasonable pricing.  For these purposes CPUs which support 5G data have a hard time competing with the lower cost and mature 4G chipsets.  Most custom Android devices don’t need 5G data speeds, so this article focuses on 4G CPUs.

Now the moment you’ve been waiting for:

Certainly, here’s the updated comparison including the MediaTek MT8789:

1. MediaTek Helio G99 (MT8781) – Best Performance

  • Release Date: Q2 2022
  • CPU: 2x Cortex-A76 (2.2 GHz) + 6x Cortex-A55 (2.0 GHz)
  • GPU: Mali-G57 MC2
  • Fabrication: 6nm (power-efficient)
  • Max Screen Resolution: 2520×1080 (Full HD+)
  • Max Camera Resolution: 108 MP
  • Max RAM: 8GB LPDDR4x (2133 MHz)
  • Storage Type: UFS 2.2
  • AI Performance: MediaTek APU (AI enhancements)
  • Cellular Support: 4G LTE only (no 5G)

Summary: Launched in mid-2022, the Helio G99 is a mid to high-range chipset optimized for gaming, multitasking, and multimedia. With its two powerful Cortex-A76 cores and a Mali-G57 MC2 GPU, it delivers smooth performance in everyday use and gaming. The 6nm fabrication means better power efficiency and less heat compared to older 12nm chips. It supports high-resolution screens up to 2520×1080, advanced AI features, and a mega 108MP camera, making it ideal for gaming tablets, mid-range smartphones, and multitasking multimedia-focused devices. This chip supports high-refresh-rate displays, fast app loading, and extended battery life.  So YUMMY!Best for: Mid-range gaming tablets, performance-focused budget smartphones, and multimedia devices.

2. MediaTek MT8789 – High Performance

  • Release Date: Q2 2023
  • CPU: 2x Cortex-A76 (2.6 GHz) + 6x Cortex-A55 (2.0 GHz)
  • GPU: Mali-G76 MP4
  • Fabrication: 12nm
  • Max Screen Resolution: 2560×1600 (WQXGA)
  • Max Camera Resolution: 64 MP
  • Max RAM: 8GB LPDDR4x
  • Storage Type: UFS 2.1
  • AI Performance: Dedicated AI processing unit
  • Cellular Support: 4G LTE only (no 5G)

Summary: Introduced in Q2 2023, the MediaTek MT8789 is a high-performance processor designed for upper mid-range devices. It features two Cortex-A76 cores clocked at 2.6 GHz and six Cortex-A55 cores at 2.0 GHz, providing robust performance for multitasking and demanding applications. The Mali-G76 MP4 GPU enhances gaming and graphics-intensive tasks. Despite its powerful capabilities, the 12nm fabrication process is less power efficient compared to newer 6nm technologies meaning the battery drains faster. It supports high-resolution displays up to 2560×1600 and cameras up to 64MP. However, it lacks 5G support, limiting connectivity to 4G LTE networks. This chipset is well-suited for high-end tablets and large screen smartphones focusing on performance and multimedia capabilities.

Best for: High-end tablets, performance-focused smartphones, and multimedia devices.

3. Unisoc T616 – Budget-Friendly

  • Release Date: Q3 2021
  • CPU: 2x Cortex-A75 (2.0 GHz) + 6x Cortex-A55 (1.8 GHz)
  • GPU: Mali-G57 MP1
  • Fabrication: 12nm
  • Max Screen Resolution: 2400×1080 (Full HD+)
  • Max Camera Resolution: 48 MP
  • Max RAM: 8GB LPDDR4x
  • Storage Type: UFS 2.2
  • AI Performance: Basic AI processing
  • Cellular Support: 4G LTE only (no 5G)

Summary: The Unisoc T616, released in late 2021, is a budget-friendly processor designed for entry-level smartphones and tablets. It has an octacore architecture featuring two Cortex-A75 performance cores and six Cortex-A55 efficiency cores. This distribution offers balanced performance for everyday tasks. The Mali-G57 MP1 GPU provides acceptable performance for casual gaming, and the UFS 2.2 storage improves app loading times. It supports Full HD+ screens and up to 48MP cameras, making it a good choice for affordable smartphones and tablets. However, it only supports 4G LTE networks and lacks 5G connectivity. It’s mainly suitable for budget conscious, low requirements applications.

Best for: Budget smartphones and tablets, social media users, and light productivity tasks.

4. MediaTek MT8786 – Likely Weakest

  • Release Date: Q1 2022
  • CPU: Likely Cortex-A73/A53 (exact details unclear)
  • GPU: Mali-G72 (variant unknown)
  • Fabrication: 12nm
  • Max Screen Resolution: Likely 1920×1200 (Full HD)
  • Max Camera Resolution: Likely 16-32 MP
  • Max RAM: Likely 4-6GB LPDDR4x
  • Storage Type: eMMC 5.1
  • AI Performance: Limited AI processing
  • Cellular Support: 4G LTE only (no 5G)

Summary: The MT8786 is a lower-end MediaTek chipset, released between 2021 and 2022. It appears to be based on an older Cortex-A73/A53 architecture, making it the weakest of the processors listed here. While it supports Full HD screens and decent cameras, it lacks the power efficiency and speed of the newer G99 or even the MT8788. The Mali-G72 GPU is outdated, limiting gaming performance. It is best suited for entry-level tablets that prioritize affordability over speed. eMMC 5.1 storage further slows down performance, making it less ideal for multitasking. Devices using this chip are usually budget tablets with limited capabilities, good for basic browsing and video playback but not for gaming or intensive tasks.

Best for: Entry-level tablets, budget multimedia devices, and basic productivity use.

Custom Android Tablet CPU Review (Non-Telecom)

The foundation of all custom Android devices, as true with digital devices in general, is the CPU.  Since all of an Android device’s core functionality flows through the CPU, its performance limits define the device’s features.  When Hatch architects a new custom Android tablet the first step is defining the customer’s spec requirement and identifying which CPU delivers enough performance to match the requirements.

Choosing the right CPU is the first element of the development process because it’s the most critical.  The right decision sets the path for a smooth development.  The wrong decision leads to severe financial pain and lost time.  Using a CPU that fails to deliver on the requirements renders the device useless, while choosing a CPU that delivers too much performance unnecessarily increases cost.  The risk doesn’t stop there.  There are many considerations to take into account.  Here’s an example.  Different CPUs support different sets of screen connector interfaces.  Screen connector interfaces, like EDP and MIPI, vary based on the size of the screen and release date.  Like all technology products, specs change with time.  If the chosen CPU only supports MIPI, but the vast majority of screens that meet the customer’s requirements are EDP, the options of screens becomes limited, sometimes resulting in unstable pricing or availability.  

CPU manufacturers come out with new chips every few years.  Some become popular and stay in production for 7-8 years, while others fizzle out more quickly.  Android CPUs are broken into 3 categories:

  1. Wi-Fi only. (Non-Telecom)
  2. Mobile data enabled for tablet size screens. (Telecom enabled)
  3. Mobile data enabled for mobile phone size screens.

Since the sub-7” mass market for Wi-Fi only Android devices is fairly limited, the CPU manufacturers don’t separate those CPUs by screen size.  The Wi-Fi only CPUs are the only option for both large and small screen sizes.  Even Apple barely pushes the iPod Touch, their small screen Wi-Fi only device, anymore, instead focusing on the iPad which has a larger screen.  That being said, the lines get blurred sometimes.  A lot of times companies will use a CPU that supports mobile data in a Wi-Fi only device for other features that it offers.  Also, sometimes companies use CPUs that are intended for mobile phone screen size devices in larger screen tablets due to cost benefits, although there’s a limit to this because the mobile device CPUs rarely support anything greater than 8” screens by design.

Let’s take a look at the CPUs that Hatch has identified as today’s most popular Wi-Fi only chipsets.

1. RK3576

The RK3576 is a powerhouse designed for premium devices, unveiled around 2022 by Rockchip. It combines Cortex‑A72 and Cortex‑A53 cores at speeds up to 2.2 GHz with the robust Mali‑G52 MC3 GPU, built on an advanced 8nm process. This manufacturing node not only improves performance but also significantly reduces power consumption, ensuring that the chip remains cool even during prolonged heavy use. In gaming tablets, the RK3576 excels with high‑frame-rate gaming and efficient thermal regulation that conserves battery life; in educational and creative devices, its efficient power draw allows for long sessions of interactive learning and multimedia editing. Brands like Chuwi and Teclast have embraced this chip, often in high‑end tablets, where stable energy usage under load is critical. Industrial applications also benefit from its balanced power consumption, combining high performance with minimized heat generation and energy wastage in environments with continuous operation.

2. MT8183

The MT8183, released around 2019–2020 by MediaTek, strikes an excellent balance between performance and efficiency with a blend of Cortex‑A73 and Cortex‑A53 cores and the Mali‑G72 MP3 GPU. Operating on a 12nm process, it is engineered to deliver robust multimedia and light gaming performance while maintaining relatively low power consumption. This efficiency is crucial for mid‑range tablets used in educational settings, where long battery life during remote learning sessions is essential. In gaming tablets, while it may not compete with premium chipsets in raw performance, its energy efficiency allows devices to run cooler and longer. Teclast, Fusion5, and similar brands have incorporated the MT8183 into products that emphasize balanced performance for streaming, multitasking, and interactive applications. The chip’s design also ensures a controlled power draw, making it a dependable choice in settings where consistent energy usage is as important as performance.

3. A523

The A523 from Allwinner, introduced around 2020–2021, is a modern, efficient processor built with Cortex‑A55 cores and a Mali‑G57 GPU that excels at 4K video decoding. Running at 1.8 GHz, its architecture prioritizes per‑core efficiency, and its design on a 22nm process ensures that the chip maintains a moderate power envelope. This efficiency is particularly beneficial in mid‑range tablets used for streaming high‑resolution media, e‑learning platforms, and moderate gaming applications. Brands like Alldocube and Chuwi have found the A523 to be a compelling option for devices prioritizing battery life and effortless performance in everyday multimedia tasks. In educational devices, longer battery endurance means continuous video lectures and interactive educational apps without frequent recharging. Moreover, while its clock speed is modest, the A523’s optimized power consumption ensures that devices can operate reliably under varied workloads without significant thermal throttling, making it a balanced solution for both entertainment and functional productivity.

4. RK3562

The RK3562, launched around 2020 by Rockchip, is a budget-friendly SoC built on Cortex‑A53 cores running at 2.0 GHz and paired with a Mali‑G52 2EE MC2 GPU on a 22nm process. Although its process technology is not as advanced as newer nodes, it’s calibrated to deliver adequate performance while keeping power consumption in check for low-cost devices. This balance makes it an attractive option for affordable educational tablets that run interactive apps and basic multimedia, as well as for devices in industrial applications where energy efficiency is critical despite modest computing needs. Brands such as Cube and Alldocube deploy the RK3562 in markets where price sensitivity is paramount. Its controlled power draw ensures that basic tasks like web browsing, video streaming, and light gaming do not excessively drain the battery, making it a reliable and economical choice for entry-level computing while ensuring that operational costs remain low in energy-constrained environments.

5. MT8168

The MT8168, introduced around 2018 by MediaTek, is tailored for entry-level tablets that demand basic functionality with efficient power usage. Engineered around the Cortex‑A53 architecture and paired with the Mali‑G52 MP1 GPU on a 12nm process, it offers reliable performance for everyday tasks such as web browsing, video playback, and e‑reading while maintaining low power consumption. This is especially important in educational devices that need to last through long school days or remote learning sessions without frequent recharging. Although it struggles with resource-intensive applications and high‑end gaming, its low energy footprint ensures that battery life is maximized—making it ideal for budget devices. The MT8168’s emphasis on efficiency appeals to emerging market brands focused on cost-effectiveness, ensuring that even devices built with limited hardware resources provide steady performance and reliable energy management for consistent everyday use.

6. A133

The A133 is an older entry-level processor from Allwinner, introduced around 2016–2017, that features Cortex‑A53 cores paired with the PowerVR GE8300 GPU, fabricated on a 28nm process. Its design targets lightweight applications in basic tablets and mobile devices, where power consumption is minimal yet sufficient for tasks like email, web browsing, and standard video playback. Though its higher process node means less energy efficiency compared to modern chips, it remains practical for devices geared toward low-cost and energy-sensitive markets. In educational environments, the A133 powers affordable tablets and e‑learning kits where simplicity and prolonged battery life meet basic computing needs, even if not suited for gaming-intensive tasks. Regional and budget brands have historically adopted the A133 for entry-level devices. Its straightforward architecture ensures a predictable power draw, which, while not optimized for modern intensive applications, reliably meets the minimum energy demands necessary for everyday, light‑duty use.

Custom Android Hardware: Not for Everyone

While the three sexiest words in the English language are Custom, Android, and Hardware, do not allow their seduction to fool you into thinking the combination of the three is right for you.  In fact, more often than not, Custom Android Hardware is lipstick on a pig.  Let’s get into some of the different shades of lipstick.

Better Specs

Creating custom Android hardware to come out with the newest and best specs is a horrible mistake.  You do not have an advantage over global established brands.  Why would you get access to the newest specs before the big tier 1 retail brands that have money, experience, distribution, and relationships with core tech providers?  They could destroy you with a fart.  You will never be able to compete with the big brands on specs.  Choose another endeavor and we’ll re-evaluate; Hatch will not support narcissistic lunacy.

Cash Money

You need money before you get into making any custom product, especially a custom Android product.  Making custom Android hardware isn’t like funding a lemonade stand back in elementary school.  In most cases it takes a bare minimum of $250k before there’s any physical hardware to show.  There are several reasons for this.  Check Hatch’s business model outline to get a better understanding.  Until funding is in place, don’t stress yourself out with anything custom.  Use commodity Android products to test your software and attract investment.  If your idea and selling skills are so good that you can get investment without any tangible demos, at some point you’ll need to make a demo and should still use a commodity device for that.

Price Misconception

Cost plays an important role in business, so, undeniably, cost or goods matters, but don’t expect the same price for a custom Android product as for a commodity product advertised on Alibaba.  All of Hatch’s clients use dedicated apps on their custom hardware.  Most of the apps provide an ongoing service which generates recurring revenue for Hatch’s clients.  Unlike mass market low-end commodity products, custom Android products have less volume, require unique skills to develop properly, take 8-12 months to develop, and require ongoing expertise and attention for continuous improvement.  A trailer park home and a custom mansion sell at different prices.

Low Volume

Due to the fixed costs of developing a product, the economics generally work best when the initial order is at least 5k pcs, although 10k pcs helps development move faster.  If the customer accepts a relatively high unit price or the product has minimal customization requirements then a lower quantity might be a valid option.  The development cost is built into the unit price.  This business model is common for manufacturers in China since sustainable, long-term, profits come from repeat volume production rather than one-off engineering services.  In other words, the engineering services are a means to the end, rather than the profit center.  Companies looking to get 200 pcs of a custom product made are generally not viable custom Android hardware customers.

And, briefly, here are some examples of when it would make sense to develop a custom Android device.

Organic Evolution

Your company has already been distributing apps on normal brand name devices or letting the customer use their own devices.  With a proven business model, the demand for your service is either growing or at least stable.  Over time, the problems of building a business around a mass market brand name device become increasingly evident.  Finding the same hardware gets more difficult and expensive.  The models change every year, meaning the apps need regular modification and testing to work smoothly with the updated hardware and Android build.  These devices lack security, privacy, and control.  Devices go out of warranty and become impossible to repair.  The list goes on, as do the headaches.  If this describes your situation, go ahead with the custom Android device, it makes sense for you.

Funded and Focused

Your properly funded start up or established company has hired people with custom hardware project experience.  Going from nothing to a custom device is a giant leap, but since you’ve done the due diligence and brought on in-house resources, you’re doing the right things to have a successful project.  Before engaging an ODM, like Hatch, you’ve gone through the project details and have a solid understanding of what you want to have done and how you want it done.  In this case, you have the money, expertise, and a management team in place to support the effort.

Internal Use

Your company is the end user of the products.  In this case there’s a clear business case and reliable volume prediction.  If your company knows that it needs a custom product to better perform a service or function, then we start with defining the use case and build a product to perfectly address it.  Since your company uses the products directly, you don’t need to worry about finding customers.  The task is to make the best product to help your company cut costs and/or add value.  Hatch will work on acquiring a deep understanding of the use case for the product and provide ideas for product design, hardware architecture, and other details related to the development and production of your custom Android product.

These lists of reasons, for and against making custom Android hardware, focus on the most popular examples we see, but these lists are not exhaustive.  If you’re curious about whether it makes sense to get a custom Android product made, feel free to send an email.  It’s a simple and quick way to get started.

Approaching Time Sensitive Custom Android Development with Creative Solutions

Custom Andriod hardware development includes a series of steps which, together, bring products from concept to reality.  The amount of time required to complete each step is generally predictable, but there are variables throughout the process that have a significant impact on the overall development timeline.  Therefore, it’s safer to calculate the upper estimate of how long a custom Android development project will take.  At the start of a project this is the number which matters the most.  Achieving a shorter timeline is a bonus, not an expectation.

As much as everyone wants to rush the development process, it’s more time efficient to get things right the first time.  Rushing through the process is likely to cause problems which will take longer to fix than doing it right the first time.  This doesn’t mean that all steps in the process are necessary.  Later, this article will talk about ways to and reasons for skipping some of the normal steps, but when a step is undertaken, it must be done correctly.  The value in most custom Android products comes from the software more than the hardware.  The hardware is a way to support the features of the software.  Unlike mass market retail products, a custom Android product doesn’t compete against other companies providing the same hardware using the same specs.  Custom Android devices need to deliver the best experience for the software running on the custom Android device.

Close up of nurse holding and typing on tablet standing in stomatologic clinic, while doctor is working with patient in background. Using monitor with chroma key izolated pc key mockup pc display

There are a few specific parts of the development process where the length of time to finish is uncertain.  The first example is the industrial design (ID), which happens at the start of a project.  Firmware engineering and hardware architecture creation can be done in parallel, but other elements must wait until the ID is finished.  On the client’s side, app development usually takes longer than expected.  This is almost always related to aspects of the client’s actual apps, rather their compatibility with the custom Android OS.

Once the ID is finished, the engineering development work takes about 6-7 months from start to trial production.  This includes mechanical engineering (designing the inside of the case), electronic engineering (PCB layout), choosing peripheral components (the components which don’t go on the PCB, like camera, screen, touch panel, etc), making working prototypes, making the plastic injection molds for casing, and a small batch production of around 5 pcs.  Adding time necessary for testing, modifications, and shipping, the total timeline usually reaches 8-10 months.  The ID creation process, which includes designing the case, making case prototypes, and evaluating them, can take 2-3 months.

For clients with a tight go-to-market schedule, it’s important to accurately estimate the total time needed to develop a custom Android product so they know the reliability of meeting their scheduling goal.  When the timing looks impractical, we must consider solutions to reduce the development time.  The solutions often require compromises that involve completely skipping certain parts of the process.  This kind of a situation recently presented itself.

After 5+ years, a client wanted to update their product in order to introduce new features and a newer version of the Android OS.  While the product functionality and firmware requirements remain the same, the update called for a new case design, a new PCB, and new peripheral components.  The client wants the product to ship by September 2025.  With Chinese New Years happening later this month (meaning that companies in China will close for about 3 weeks) and the development process just starting, 9 months isn’t enough, especially since the ID hasn’t been started.

Hatch suggested to the client that we break the development into 2 stages.  This way they will have something new to promote next year, and then something new to promote the following year, without the stress or risk of rushing the development process.  For the first stage, we’ll develop a new PCB, using an updated CPU, that will use the same peripheral components and fit into the client’s existing casing.  We’ll design the new PCB so it can fit into their new casing, once that’s finished.  Then for the second stage, we’ll release the update with the new casing and peripheral components in 2026.

This two stage approach allows more scheduling flexibility for the most time consuming parts of the development process including ID creation, making the mold, and all the time spent testing these.  It also gives more time to choose new peripheral electronics.  Ultimately, we’ll have more than enough time to make the second stage product as perfect as possible, while reducing risk and having the benefit of learning from sales of the first stage version.  This staged approach reduces the development time from a year to about four months.

Ultimately, the two staged approach supports the client’s marketing efforts by having two updates over the course of two years to get customers excited about.  From the manufacturing side, the development process follows a reliable timeline, allowing for the ample attention to detail and time to make any necessary changes.

Similar principles apply to new product development as well.  When clients start their custom Android development with a long list of complicated customization requirements, researching the feasibility of their requirements and implementing them takes time and may increase cost.  The final product might actually be better if they refine the list, stick with just the most important customizations, and learn from the actual end user experience before trying to do everything at the beginning.  As much as we want to make the perfect product on the first try, there’s a reason that the biggest brands in the world continually release product updates.  Getting something finished in a timely manner, that has all the most important features, usually results in a better product that’s more efficiently developed.