I already have the full AOSP source checked out and the proprietary blobs for a piece of dedicated in-vehicle hardware. What I need now is an Android engineer who has been through the full custom-ROM cycle before and can take the lead on turning that raw tree into a production-ready build. Scope of work • Strip every trace of Google Mobile Services and replace only what is strictly necessary with open-source or in-house components. • Harden the system: SELinux in enforcing mode, verified boot, secure default props and permissions, plus any kernel-level mitigations you normally deploy. • Update or create the device tree and BoardConfig so the microphone, speakers, Bluetooth and the built-in camera work flawlessly; the unit does not rely on a touchscreen, so please make sure everything is fully operable through physical controls and Bluetooth interfaces. • Produce a clean, reproducible build environment (bash scripts or a Dockerfile are fine) along with an incremental OTA update mechanism. • Deliver a flashable image and a brief technical report summarising every change to kernel, framework and vendor partitions so my team can pass compliance review. Acceptance criteria 1. The image boots reliably on the target hardware, shows no crashes after 24 h continuous soak. 2. Device boots with SELinux enforcing and passes SafetyNet-like internal checks without Google services present. 3. Microphone, speakers, Bluetooth and camera are recognised by the framework and work in sample apps. 4. OTA zip installs and rolls back correctly. If that checklist sounds routine to you and you can jump straight into lunch-time syncs about kernel defconfigs, let’s talk.