I’m rebuilding our interactive kiosk platform around an AOSP-based Android image that must boot natively on x86 / x64 hardware. The goal is to give end-users a fluid, multi-point touch experience while giving our team a simple yet powerful way to push, schedule, and manage content of every kind—text, images, video, and interactive elements—through an integrated CMS layer. Smooth performance, advanced multi-touch handling, and airtight license validation are non-negotiable. The UI must be skinnable so we can brand each deployment, the CMS workflow should feel as intuitive as uploading files to a website, and the entire stack needs rock-solid security to guard against tampering. Key deliverables • Flashable Android x86_64 system image (ISO or IMG) built from AOSP or your preferred stable fork • Kernel and HAL tuned for our touchscreen controller with full multi-point gesture support • On-device CMS app with playlist-style scheduling (drag-and-drop, timed loops, dayparting) • Remote license verification that calls our HTTPS license server at startup and on an adjustable heartbeat, disabling playback if the key is invalid or expired • Customisable launcher / kiosk shell locked to our application suite, with optional remote OTA update hooks • Security hardening: verified boot, disabled unnecessary services, user access lockdown, root blocked in production builds • Complete build scripts and documentation so we can reproduce the image internally Acceptance criteria 1. System boots and runs continuously for 72 h with no touch or video latency spikes on our reference Intel-based panel PC. 2. CMS successfully schedules mixed media playlists and switches content at the exact programmed times. 3. License server rejects an invalid key and the OS falls back to the branded “license required” screen within 10 s. 4. Re-branding the launcher (logo, colours, default layout) can be done by replacing asset files and rebuilding once. 5. OS itself must be "read only" to prevent corruption If you already maintain an Android-x86 fork, use Yocto, or have experience in kiosk-grade AOSP customisation, this should feel familiar. I’ll supply the touchscreen specs, current license API, and test hardware access as soon as we kick off.