DREMDEV // AOSP STUDIO
DREMDEV // AOSP STUDIO
Dremdev helps OEMs and Tier‑1 suppliers build Android platforms — from vendor bring-up to runtime. Time & materials or fixed-scope, on the kind of problems where the docs run out and the source tree begins.
Bring-up, vendor integration, custom HAL, AOSP branch management, repo manifests, Soong/bp and reproducible builds.
IVI platform bring-up, Vehicle HAL integration, AVM camera, head-unit graphics, multi-display and CarService.
A rare specialty: running Android inside a hypervisor, in x86 emulation, or as a VM on automotive silicon. From Genymotion to Cuttlefish, all the way to AAOS VMs on Qualcomm.
AOSP porting on non-Qualcomm silicon, vendor partition integration, custom HAL, bootloader, device tree and platform-specific drivers.
The phone is AOSP's comfort zone. The real test is everything else — the form factors where the OS has to be tamed, recompiled, sometimes stripped down. Here are a few ports Dremdev has shipped.
Android bring-up on outdoor payment terminals. Fast boot, NFC/credit card reader, payment security, environmental ruggedness.
AOSP port on a wearable AR platform. Extreme resource constraints, dual display, inertial sensors, aggressive thermal management.
Android digital signage on large-format displays. Forced rotation, remote content management, scripted reboots, 24/7 uptime.
AOSP port on residential and commercial intercoms. SIP/VoIP stack, access control, camera and RFID reader integration, always-on operation.
Which one fits depends on how much technical uncertainty the project carries and how much budget visibility you need. Both modes can be combined: scoping under fixed bid, execution under T&M, or the other way around.
Embedded into your team for the long haul, contributing directly to the codebase. Best when you need to scale an existing AOSP team, transfer expertise, or work through a deep blocker where the solution isn't clear yet.
Defined scope, named deliverables, clear milestones. For a bring-up, a version migration, a one-off vendor integration, or a hardened POC with measurable value.
A career spent digging into what the docs don't say — SoC registers, binder traces, builds that break at 3am.
Dremdev is the consulting and development practice of Daniel Fages, a systems engineer working on embedded Android and Linux. The work is shaped by one question, asked on every engagement: what's actually happening, at this level, on this hardware?
The track record spans varied form factors — urban parking meters, smart glasses, digital signage, supercar IVI — each bringing its own constraints (boot time, power, certification, vendor partition) that end up cross-pollinating.
First AOSP contributions at the launch of Ice Cream Sandwich (Android 4.0, late 2011). Out of that work came Buildroid — the project that gave rise to Genymotion, the Android emulator now used by hundreds of thousands of developers.
The approach is pragmatic: no slideware, no methodology in capital letters. Read the code, reproduce the issue, form a hypothesis, verify. Deliverables are written in English, in the form of a commit message or a design doc — not a consultancy report.
● Based in Lyon, France, working with clients across Europe, Asia, and the U.S. On-site for the critical phases (bring-up, hardware debug), remote the rest of the time.
First call is free and always technical. No commercial pre-qualification: we look at what's broken and figure out together whether Dremdev is the right fit.