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.

Custom Android Prototyping Best Practices

Prototyping in Custom Android Development: Turning Concepts into Reality

Bringing a custom Android product to life is a journey filled with innovation, iteration, and discovery. At its core lies the process of prototyping—the creation of tangible, testable versions of your concept. Each prototype serves a distinct purpose, helping refine the product step by step until it’s ready for the hands of users.

In the world of custom Android development, prototyping takes many forms. It could be as simple as an app prototype created in design tools like Figma to test UI and UX, or as complex as a physical prototype, such as a working sample or a trial production unit. No matter the stage, the goal remains the same: bring ideas to reality for testing and improvement. Here’s how the magic unfolds.

App Prototyping Matters in Custom Android Development

Custom Android products almost always run unique software, meaning the development of hardware and apps must proceed hand-in-hand. For app developers, the process often starts with a UI/UX prototype—a digital mockup designed to test the user experience and interface flow. Once these designs are approved, programmers dive into coding.  This is not something Hatch works on, but it’s relevant to the overall product development.

But here’s the challenge: the custom hardware the app is destined for often doesn’t exist yet! How can software developers ensure their apps are optimized for hardware that’s still in development?

The Parallel Sample: Jumpstarting App Development

We solve this challenge with a parallel sample. This is a functional sample of an existing tablet or phone that uses the same core architecture as the final product. By providing a parallel sample at the project kickoff, we give app programmers a platform to start development immediately, rather than waiting months for the first working samples.

An early start is crucial because software development often takes the longest time. With the parallel sample, app developers can test compatibility and functionality from day one, setting the stage for seamless integration with the custom hardware.

The First Working Sample: Bringing It All Together

It takes about 2-4 months to finish the initial development engineering.  At that point it’s time for the first working sample. This prototype represents the initial physical manifestation of a custom Android device.

  • What it includes:
    A 3D-printed case, electronics from a small PCBA batch (usually fewer than 10 pieces), and peripheral components like the screen, battery, and camera.
  • How it’s used:
    About five units are typically produced. Some go to the customer, while others stay with Hatch for intensive testing. Over 1-2 weeks, this prototype is put through its paces to identify obvious issues—casing design, core electronic functions, firmware stability, and overall user experience.

This phase is all about ironing out big wrinkles and ensuring the basic foundation is solid before scaling up.

Trial Production: A Glimpse of the Final Product

Once the working sample is approved, it’s time to take a bigger leap: trial production. Here, we shift from small-scale prototypes to a limited run of 50-200 units, produced using the same mass production tooling and processes as the final product.

  • Purpose of trial production:
    These units are the closest thing to the final product, designed for broader testing. By distributing them to end users, we can get feedback about hidden issues that might only appear in real-world conditions or over time. This stage also provides invaluable insights into hardware durability, software performance, and usability.

Why it matters:
No amount of internal testing can replace the feedback gained from actual users. Trial production bridges the gap between controlled environments and the unpredictability of real-world usage.

Prototyping with Purpose: Faster, Better Results

Each stage of prototyping plays a unique role in the custom Android development process. By understanding and embracing these stages—parallel samples, working samples, and trial production—you can achieve faster timelines and superior results.

Hatch believes in empowering customers with the tools and strategies to bring their vision to life. Whether it’s jumpstarting app development with a parallel sample or refining the final product with trial production units, every step is designed to ensure your custom Android product exceeds expectations.

Reach out if you have a solid team, great business, and long term vision for your custom Android product.  We’re here to help.

Behind the Scenes: Android Device Customization

Creating a custom Android product requires going through a series of smaller processes that, in succession, become the whole product development process.  First, we figure out if the client knows what they want and then ask ‘why’.  Second, we research the client’s use case.  This step is ongoing, both for Hatch and our customer, this way the product continuously gets better.  Hatch then validates the client’s initial product details, based on a better understanding of the use case.  This is an interactive process that takes place over email or phone calls, with written call recaps.

Once the detailed product architecture has been confirmed, based on an in depth understanding of the use case, Hatch proceeds with product engineering. This mainly includes designing the PCBA, mechanical design (internals of the case), and firmware.

Keeping this theoretical process in mind, below highlights a real communication example from a current project.  Witnessing an actual conversation will clarify the concept.  Plus you can envision how it would work with your project.  To understand exactly what this process entails, let’s look at a recent email exchange with an actual customer.

This customer has been working with Hatch since 2018.  They originally asked for our help to get through a complicated and challenging situation with another supplier.  Once that was resolved, they asked Hatch to redevelop their product with quality improvements.  Over the years they’ve grown their business and we’ve maintained a positive working relationship.  Now they’re ready to get started on their second generation product.

Many companies consider using custom Android hardware to get a steady long-term supply of their optimized hardware, rather than using a generic retail device that gets updated every 6-12 months.  Sticking with the same hardware doesn’t last forever though.  After 5-6 years, enough time and updates have gone by to justify an update.  The development process is similar to the first time, but the customer’s understanding of user experience is even better.

The customer pointed out a few things that they’d like to change in the next generation product.  One of the changes they want to make involves the SD card slot.  That component is exposed to enough water and dust that it must be cleaned after a few years to continue working smoothly.  The ideas that Hatch presented were dismissed by the client based on their acute knowledge of the product’s operational environment and users.  This conversation shows how the client presents product needs, Hatch comes back with ideas, and decisions are made.

After receiving new spec requirement from the client, Hatch responded with the following questions:

Reviewed the specs.  Here are some questions.

1. Does the new version use the same case design?  If not, do you have a new case design in mind?  We may be able to make the current mold thicker, like you requested, which is a lower cost option than having to make a new one.

2. It looks like there will be 2 sets of specs (Model A and B).  I’m thinking we use the same PCBA, but Model A doesn’t include the WiFi chip and uses 32GB memory, while Model B has WiFi and 64GB of flash.  Any other differences?

3. You mention using a heavy duty USB port.  What do you think makes the USB ports ‘heavy duty’?  What experiences inspire this comment?

Here’s the client’s response as well as Hatch’s reply to the client:

1. Same design, yes. Thicker and stronger definitely!  I would really like to strengthen the trim bezel around the screen.

(Hatch) In this case I’d like to see if we can modify the tooling of your current case rather than making a new mold as this will save you thousands of dollars.  Modifications based on the changes you’ve outlined: thicker plastic, USB-C, and something to accommodate the suggestion I’ll make below regarding SD card ports.

2. You hit it spot on.  We also need to change the chipset to a more modern one that can handle a newer Android OS.

3. I would like a real USB-C.  We have had customers use the wrong chargers and cook the mainboards and, in real bad situations, cook the batteries. I feel with USB-C and a supporting chipset, we can utilize fast chargers and higher current. Also, USB-C would be a little more modern.

(Hatch) I know the current CPU only supports USB 2.0.  We’ll make ‘USB 3.0 chipset’ and USB-C port par of the new requirements.

Since last fall we have seen an outbreak of SD Ports not working. A solution seems to be cleaning the ports in the service department.  After spending months trying to figure out the problem, I learned the contacts are slowly becoming corroded, in particular the upper SD Port.  These SD ports are probably the most used SD ports in the world, next to professional photographers. Every day customers are using these and they may be inserting sd cards 10 times a day 4 days a week; which means heavy heavy use.  Is there any way to get a heavy duty sd port? Gold contacts? Better builds?

(Hatch) We’ll explore more durable SD card port options.  I’m impressed that you’re not seeing the SD card component breaking off the board based on the heavy usage and rugged clientele.  We’ll note to continue with the same mechanical design in the new versions.

Having that SD card port constantly open in outdoor environments and in different weather conditions exposes the slot to dust and moisture.  With that in mind, what do you think about these ideas:

1. Adding a silicon (soft rubber) plug to the SD card port opening.  It can be attached to the case so it won’t get lost (unless someone breaks it off).  We can attach it in a way that makes it more difficult to remove unintentionally, if you think that’s useful.  A bike light of mine uses this concept to cover the USB charging port and I accidentally pulled it off.  Now, I can’t get it to reconnect.  I can send a photo if you want.

2. A flap, like the one that covers a letterbox, that is closed by default using a spring mechanism, but is flexible to get pushed back when someone inserts the SD card.  That way the hole stays protected and the user doesn’t deal with a plug.  We just need to make sure this is designed to withstand abuse.

The above 2 ideas are ways to achieve the same end result.  If you’re interested in either we can check the mechanical viability of making modifications to the original mold.

And, finally, we established a clear direction with this response from the client:

I like your thought on the port covers for the new models but I will have to say no, it would be more troublesome and they would certainly break off. (just like on your bike)

The ports are getting the moisture from the cards themselves. Being transferred from every card.  Like I said it took me months to get this completely figured out.  Hundreds of times the cards are being transferred in and out of the device, bringing in moisture. (I traced this by having customers send me their sd cards that seemed problematic).

Also keep in mind, at a minimum, 95% of the time these sd ports are occupied with cards.

You made a very good point about the ports not being torn off the board.  I can tell you we have not had one single problem with that from any of the lots; Not once! Good job on your team’s part!

This exchange highlights the initial part of the product development process.  It starts with understanding the use case and environment.  We use creativity, experience, and communication to define the ideal approach.  Now it’s time to get to work!

Quality Checklist for Custom Android Tablets (Functional Checks)

This month’s article lists out a few of the standard functionality tests Hatch performs on custom Android tablets.  These tests are part of a longer list which includes many kinds of inspections Hatch does to ensure the product meets Hatch’s basic quality standard.  Beyond the fundamental tests, when checking the functionality of a custom Android tablet, Hatch will add custom quality checks based on the product’s specific functionality requirements.  For example, if the product uses a wide angle camera lens, Hatch will check that the viewing angle meets the special requirements.  If an unforeseen problem gets found during the development process, Hatch will introduce a test into the quality control process to cover that specific issue.

The name of each check is followed by details of the inspection process.

Functional Defects

Functional tests ensure correct performance of the custom Android tablet. The proper functionality of a tablet starts with using good components. This is why there are different functionality tests for all the key components of the tablet.

  1. Plug Insertion Force

This test ensures that the ports of a custom Android properly fit with the plugs that go in them. Generally this applies to a USB, earphone, and charging port. Plug insertion force is the force required to insert the plug into a slot. The port shouldn’t be too loose, so the plug falls out unintentionally, and it shouldn’t be too tight, making it difficult to insert or withdraw the plug.

We measure this force using gram-force. Gram-force (gf) is a metric unit of force that is equal to the force of gravity on a one-gram mass.

The tolerance range for this test is Min 250gf and Max 1500gf.

  1. Button Activation Force 

This test makes sure that the buttons are working properly, and more specifically, that they respond to the right amount of force. It applies to physical buttons which ‘click’, rather than touch buttons which use other sensing methods.

Button activation force defines the amount of pressure required to apply to a button for it to function. It’s also measured using gf.

The tolerance range for this test is Min 200gf and Max 400gf.

  1. Speaker Audio Quality

This test ensures that the audio output from the Android tablet or smartphone is clear at the highest volume.

Speaker Audio Quality is evaluated using sound pressure level (SPL) and total harmonic distortion + noise (THD+N) at peak speaker loudness on 1kHz sine wave.

The tolerances are SPL as dBa and THD+N as a percentage. These are checked at a distance of 10cm from the speaker. An acceptable SPL, dBa is ≥72 and THD+N, % is ≤15. To put things into everyday terms 40dB is the volume of a quiet library. 60dB: ordinary spoken conversation. 85dB: a food blender. 88dB: heavy traffic. (source: rnid.org.uk)

  1. Display Quality

This test applies to the image shown on an Android tablet or smartphone screen. It ensures that the screen’s colors, brightness, and pixels appear correctly.

Display defects are defects which cause total or partial image loss, image distortion, or reduces display usability under bright ambient light.

The tolerances for this test include average brightness (in nits), brightness uniformity (as a percentage), color representation (CIE1931), bright dead sub-pixels (based on size and density), and dark dead sub-pixels (based on size and density).

Additional tests include:

Age testing, where the device runs a demanding workload, usually playing a video at high volume. This test lasts for between several hours to several weeks, depending on the product. The point is to ensure that the system functions properly over a longer period of time while under a high stress level.

Drop testing, where the device is dropped at a specified height onto a hard surface multiple times at different angles. The goal is to ensure the device can sustain violent impact and continue to function properly.

And there are tests for all the other major components such as camera, microphone, battery, and memory.

The list of functional testing covers all elements of the custom Android tablet or smartphone that could affect its performance. All custom devices also undergo tests which are specific to their unique requirements as well. These tests are initially based on the devices custom requirements and new tests are added during the development process as new issues are found.

Handling Problems

Gain insights into the realities of custom Android hardware development with this article. Discover how setbacks in a current project led to valuable lessons on quality control, design decision-making, and the importance of thorough research in avoiding costly mistakes. Learn from a real-world example of navigating challenges in custom product development, ensuring that each problem becomes an opportunity for growth.

Continue reading