adb root, running in the Android Studio emulator.The author of a Habr article has been writing Android code since 2015: grunt-work gigs, major retail, then banks and fintech — everything from business features and custom views to SDKs, security, and OpenGL 3D scenes. Yet he had never once built AOSP from source. So over a quiet weekend he decided to close that gap and built Android 17 on a MacBook. The official guide on source.android.com looks like a one-evening job: install the packages, download the tree, lunch, m, run it.
In reality, the guide turned out to be a pirate map where the X is drawn but the reefs between the X and the treasure aren't. What he ended up with: a userdebug build, adb root, and his own OS running in the Android Studio emulator; a one-line edit in a system utility that measures how much a rebuild costs; tweaking ART parameters for every app on the system at once; and his own boot animation.
The motivation wasn't just curiosity. The author cites a case from retail: an app using the Camera1 API kept crashing on two stock Samsung devices, with the stack trace pointing into native code. The culprit was the white balance mode — the vendor had removed it from the camera but left it in the list the system reported. The app asked "what can you do?", got an answer, and crashed the moment it asked for exactly what was promised. That gap between AOSP and the vendor's "enhancements" is exactly what he wanted to see with his own eyes.
Our take: the value here isn't "built it on a Mac" — it's the list of places where the documentation lies. Android 17 in the tree is a fresh branch, and the Mac has long been the primary work machine for mobile developers. Google writes its guide for one reference Ubuntu, and everything outside that you have to figure out yourself. This guy walked that exact path and wrote down where he stumbled.
What it changes in practice: userdebug plus adb root plus your own build lets you test hypotheses about vendor patches without begging DevOps for hardware. In our experience, most teams run this kind of thing through CI or a remote server, not a laptop. So the "over a weekend on a local machine" route is really about the solo developer, learning, and debugging "only on X devices."
Who wins: the Mac as an Android developer's machine gets another point in its favor, and the author gets a reputation boost. Who loses: anyone who bought a dedicated Linux box purely to build the OS — and, to some extent, the official guide's credibility. One important caveat: "free" here means "no money," not "no time" — the whole weekend went into it, and the author measured rebuild cost separately.
The source gives no MacBook model or chip, no macOS version, no build number or Android 17 branch tag. Not a single timing figure: how long the first build took, how long the incremental rebuild after the one-line edit took, how long repo sync ran. There's no link to scripts or an explicit list of documentation discrepancies either. This is one person's personal experience, not a report with measurements across multiple configurations, so you'll have to verify the numbers yourself.
Forecast: within a quarter, at least one public write-up of the same pitfalls — the steps after lunch and m — will show up in AOSP build threads, citing this experience.
Disclaimer: a single source — the author's personal experience; Google has officially confirmed nothing about building Android 17 on macOS.
Source: Habr
Source: habr.com · post in Telegram