Board bring-up, BSP integration, HAL authoring, kiosk and device-owner builds, OTA pipelines, and CTS/VTS remediation for teams shipping Android on dedicated hardware. Work happens in your repo, CI, and review process, with milestone artefacts your team can verify.
Board bring-up and BSP work: kernel configuration, bootloader integration, device trees, and hardware enablement — taking a board from first boot through the compliance work that follows.
HAL authoring — AIDL and HIDL interfaces, sensor frameworks, cameras, and audio stacks — working from your vendor’s reference code under NDA.
Kiosk and single-purpose builds: device-owner ROMs with custom launchers, managed OTA, and device-policy enforcement, scoped to what the deployment actually needs.
A/B OTA pipelines with signing, staged rollout controls, rollback handling, and update telemetry, scoped with your security and operations requirements before implementation.
CTS and VTS remediation: reading the failure logs, isolating the cause, and writing the fixes your vendor sign-off process needs.
Long-term platform patching: backported security fixes, kernel merges, and Android version maintenance for devices outside the Google release cadence.
We review your BSP, vendor constraints under NDA, device specification, and current blockers. The output is a short risk list and a proposed scope.
Written milestones, fixed price per milestone or hourly with a ceiling. You review the estimate before work starts, and each milestone has a demo or artefact you can verify.
We work in your Git, Gerrit, and CI. Branch policy, review conventions, and commit style follow your team, with no separate delivery fork unless you ask for one.
Engagements end with a written handoff document. If production standby is part of the scope, we define the response window and escalation path before launch.
A full AOSP build on an ARM SoC: kernel backport, custom camera HAL, device-owner kiosk behaviour, and an A/B OTA pipeline with documented handoff.
AIDL HAL for a vendor peripheral and the SELinux policy needed to pass CTS. Scope sized in weeks, with a demo at each milestone.
Device-owner build on a purpose-built tablet: managed OTA, custom launcher, and an offline-first update pipeline for restricted networks.
Tell us what you're building and where you're stuck. We reply with the scope we think fits, including when a smaller engagement or a different path is better.