How does robotnix compare to building LineageOS manually?

Robotnix automates the build process using Nix for reproducibility and modular configuration, but it's currently in alpha with limited device support compared to official LineageOS builds. It simplifies signing and integration of tools like MicroG, though maintenance issues may affect stability.

How to set up robotnix for a custom kernel?

Robotnix supports custom kernels via configuration modules, but the kernels component is currently unmaintained per the status table. You'd need to refer to the documentation and may require manual Nix expressions, which assumes expertise in both Nix and Android kernel building.

Does robotnix support OTA updates?

Yes, robotnix includes modules for seamless OTA updates as mentioned in the features, leveraging GrapheneOS's updater. However, the OTA updater component is maintained, but overall alpha status means it might not be reliable for production use.

What devices are compatible with robotnix?

Robotnix supports devices listed under LineageOS wiki for the LineageOS flavor, and Pixel devices for vanilla AOSP. Device compatibility is limited, and users must check the documentation for specific codenames and flavor versions.

How to sign images with robotnix for verified boot?

Robotnix allows signed builds by specifying user keys in the configuration, supporting verified boot and bootloader re-locking. The signing component is maintained, but requires a Nix daemon with sandbox support, which isn't compatible with Docker in some cases.

Is robotnix good for privacy-focused Android builds?

Yes, robotnix excels at integrating privacy tools like MicroG, F-Droid, and alternative webviews (e.g., Bromite) into the build. However, its alpha state and unmaintained components (e.g., webview) might introduce security risks if not properly updated.

Open-Awesome

robotnix

Nix

Build Android (AOSP) images using the Nix package manager for reproducible and customizable builds.

GitHub

775 stars93 forks0 contributors

What is robotnix?

Robotnix is a build system that uses the Nix package manager to compile Android (AOSP) images, along with components like kernels, webviews, and third-party apps. It solves the problem of Android's complex, fragile build processes by providing a reproducible, declarative approach similar to NixOS.

Target Audience

Android enthusiasts, privacy-conscious users, and developers who want to build custom, reproducible Android images for supported devices, particularly those interested in GrapheneOS or LineageOS.

Value Proposition

Developers choose Robotnix because it brings Nix's reproducibility and modular configuration to Android builds, making it easier to create secure, customized images with verified boot support and integrated privacy tools like MicroG.

Overview

Build Android (AOSP) using Nix [maintainer=@danielfullmer,@Atemu,@cyclic-pentane]

Use Cases

Best For

Building reproducible LineageOS or GrapheneOS images with Nix
Creating custom Android ROMs with integrated privacy tools like MicroG
Generating signed Android images for verified boot and bootloader re-locking
Automating Android builds with declarative configuration
Integrating F-Droid and other apps directly into the system image
Extracting and including vendor blobs from official Google images

Not Ideal For

Developers needing stable, production-ready Android builds for daily driver phones
Teams without Nix expertise or unwilling to manage complex build configurations
Projects with tight resource constraints (low disk space or RAM)
Users requiring broad device support beyond Pixel and LineageOS-compatible devices

Pros & Cons

Pros

Reproducible Nix Builds

Leverages Nix for declarative and reproducible Android image builds, abstracting away Android's complex tooling as described in the motivation section.

Modular Configuration System

Uses a NixOS-style module system to easily customize flavors, apps, and settings, exemplified in the Quick Start with modules for F-Droid and MicroG.

Secure Boot Support

Enables signed builds for verified boot and bootloader re-locking with user keys, a key feature for security-conscious users.

Privacy Tool Integration

Integrates privacy-focused tools like MicroG, F-Droid, and alternative webviews (e.g., Bromite) directly into the build process without manual patching.

Cons

Alpha Software State

Explicitly labeled as in-development alpha software with many unmaintained components (e.g., webview, kernels), making it unreliable for daily use as per the README warning.

High Resource Demands

Requires at least 250GB disk space and 16GB RAM, with build times spanning hours, as detailed in the Requirements section, which can be prohibitive for casual users.

Limited Maintenance

The status table shows critical components like vanilla AOSP, webview, and kernels are not maintained, reducing functionality and long-term support.

Complex Setup

Requires familiarity with Nix and Android build systems; features like sandbox signing have specific kernel and daemon requirements, adding to setup complexity.

Frequently Asked Questions

Related Projects

Devbox

Instant, easy, and predictable development environments

Stars11,503

Forks309

Last commit10 days ago

flox

The Deterministic Foundation for your SDLC

A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]

Stars2,638

Forks142

Last commit6 hours ago

attic

Multi-tenant Nix Binary Cache

Stars1,853

Forks159

Last commit5 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub