Actinis AOSP Consulting
Services · Professional engagement

Code-level review for your Android platform.

Architecture reviews, security reviews, and bring-up triage for teams shipping Android on custom hardware. We review the code, configuration, logs, and build artifacts behind the issue, then write a report with prioritised findings, reproduction steps, and references.

What we do
// aosp-consulting.md

Architecture reviews of the whole stack: bootloader, kernel, HAL, framework and app layer. Each recommendation points to the AOSP commits and vendor docs behind it.

Security reviews: SELinux policy, verified-boot chain, keystore and attestation behaviour, OTA/update paths, and third-party SDK exposure. We look at platform risks, not just CTS/VTS results.

Bring-up triage when hardware is stuck in the kernel, init sequence, HAL or first boot, as a short engagement.

Technical due diligence for vendor, SDK, or codebase evaluation: repo reads, risk summaries, and references you can hand to stakeholders.

Who it's for

Is this a good fit?

Good fit when
  • Your team owns an AOSP device and needs an outside read on architecture, security, or performance before a release.
  • You are about to ship and need an independent release review focused on platform risks.
  • A new SoC or BSP is blocking a release and you need someone to find out why.
  • You are evaluating a vendor, SDK, or codebase and need a written technical assessment with references to the reviewed material.
Not a fit when
  • You need a long-term embedded team — see Custom AOSP Development.
  • You want generic mobile-app advice with no platform or device angle — see Mobile App Development.
  • You are looking for broad platform opinions without a concrete product or device in mind. We work from code, logs, builds, or device behaviour.
How we engage

How the work runs

01

Discovery call

If you can share it, we review the architecture doc, repo README, or specific ticket before the call. If the work is not a fit, we say that before proposing a scope.

02

Written scope

Objectives, deliverables, hourly estimate, and a fixed ceiling. You approve or adjust the scope before work starts.

03

The work

We read, test, and reproduce. You get regular short updates with current findings, affected files or components, and open questions.

04

Report and handoff

A written report with prioritised findings, reproduction steps, and references to AOSP, CVE, and vendor documentation. Remediation is optional and scoped separately.

Example engagements

Typical projects

01

Pre-launch review

Before an AOSP device ships, we review its SELinux policy, verified-boot chain, keystore, attestation and OTA pipeline, and write up what we find.

02

Stuck bring-up

When a new board or SoC is blocking a release, we look at kernel config, init, HAL and first boot until we find the cause, and write down how to reproduce it.

03

Fleet security review

Device-owner posture, verified boot, attestation chain, and third-party SDK triage across a deployed fleet. You get a list of findings, most serious first, with notes on fixing them.

Contact

Tell us about your project

Tell us what you're building and where you're stuck. We reply with what we think the work involves, and say so if a smaller engagement or a different route would serve you better.