Choose the version against the platform
| Reference | What the platform ships |
|---|---|
| XH-500 10.1-inch rugged tablet | Android 12 standard with 4 GB + 64 GB; Android 13 optional, with 6 GB + 128 GB or 8 GB + 128 GB configurations |
| XH-400 10.1-inch biometric tablet | Android build carrying GMS certification; confirm the exact version for the configuration you order |
| Handheld PDA series | Android 12 platform with the memory and module configuration chosen for the project |
The operating system version is tied to the build validated for that hardware, not chosen freely. If your application requires a specific version, tell us at the start so it can be matched to the right platform rather than discovered during integration.
GMS build or plain AOSP
Build with GMS
Where your deployment depends on Google Mobile Services — managed provisioning, Play services or applications from the store — the platform needs a build carrying GMS certification.
- Needed when MDM enrolment relies on Google services
- Needed when third-party applications expect Play services
- Stated as a requirement so the correct build is used
Plain AOSP build
Single-purpose devices often run better without consumer services, both for behaviour and for the support burden.
- No consumer accounts or store access on the device
- Smaller surface for unauthorized changes in the field
- Stated as a requirement so it is validated before production
What gets set before the line starts
| Area | How it is handled |
|---|---|
| Applications | Your APK and its dependencies are pre-installed as part of the image, so devices arrive configured instead of being rolled out on site |
| Launcher and kiosk | What the operator can reach is defined during feasibility and validated on the sample — including whether one application owns the screen |
| Branding | Boot logo and start-up animation carry your brand rather than ours |
| Locale | Default language set for the deployment country |
| Updates | Whether the image is frozen or updateable is agreed before production, because it affects how the image is built and documented |
Permissions deserve the same attention. If your application requires elevated privileges, say so at the start — whether that can be provided depends on the platform and the intended use, and there is often a module-level API that does the same job.
How the image is frozen
Before the sample
- Version, build type and application list agreed
- Behaviour requirements captured in the specification
- Any SDK or integration requirement confirmed with your team
At the sample
- Your team runs its own integration on real hardware
- Behaviour checked against what was specified
- Once accepted, the image is frozen for production
Changing the image after units are built costs time on every device in the batch, which is why the specification is signed off before production rather than at delivery. See the full project sequence on the Custom Solutions page.
Android customization questions
Which Android versions are available?
Can we choose a GMS build or a plain AOSP build?
Can the device be locked to a single application?
Who handles updates after delivery?
Send the software image requirements
- Android version your application requires, and why
- Whether GMS or plain AOSP is needed
- Applications to pre-install, plus versions
- What the operator may and may not reach on the device
- Whether the image should be frozen or updateable
- Quantity, destination market and target date
Request a quotation Chat on WhatsApp
Shenzhen Xinhong Smart Technology Co., Ltd. · WhatsApp and phone +86 185 9427 9341 · [email protected] · Mon–Sat, 9:00–18:30 (GMT+8). Back to the OEM and ODM centre · hardware customization · software customization · industrial design · certification support.