Your PIN decides what opens.
ee1os (ee·1·os: two environments, one OS) is a personal research fork of GrapheneOS for Pixel phones. One lock screen, several PINs, each with its own outcome: your everyday phone, a protected space with its own keys, an immediate restart, or a wipe.
Fig. 1 One PIN pad, four outcomes. Choose one to see it typed (example PINs).
Alpha 3 Builds 2026101520 (Pixel 8 Pro) and 2026101521 (Pixel 10a) – early test builds
Anything else says "wrong PIN". The reboot and duress PINs are optional. All PINs on the phone have the same number of digits.
This is alpha software built and tested by one person on one test phone. Expect bugs, data loss and changes. It is not meant for anyone whose safety depends on their phone. No warranty, no liability: see the terms. Found a problem? Get in touch.
The protected space
A second profile on the same phone, with its own apps, its own data and its own encryption key.
- Opened from the normal lock screen
- by typing its own PIN.
- Separate keys
- Unlocking the everyday profile does not unlock the protected space.
- Locked again when you leave
- When the screen turns off, the phone goes back to the everyday profile's lock screen and the protected space is stopped. Its data stays encrypted until its PIN is typed again.
- Straight from boot
- After a restart you can open it without unlocking the everyday profile first.
- Holds the security settings
- The duress PIN, the reboot PIN and user management are set from inside the protected space. Someone holding the phone unlocked in the everyday profile can't see or change them.
- PIN only
- Fingerprint unlock opens the everyday profile; the protected space always asks for its PIN.
The everyday profile works as a normal phone and doesn't list the protected space. That is all: the protected space is kept out of the way, not hidden. Anyone who examines the phone, or knows this build, can tell that it exists. Don't rely on it staying secret.
Everything else is GrapheneOS
ee1os keeps GrapheneOS's protections and follows its releases: sandboxed Google Play (optional), network and sensors permissions, storage and contact scopes, hardened memory allocation, auto-reboot, USB-C port control, PIN scrambling, the Vanadium browser, verified boot with a locked bootloader. Full list: grapheneos.org/features.
Status
- Release
- Alpha 3 (builds 2026101520 and 2026101521) – early test builds. Releases are at github.com/ee1os/releases, each one stating which GrapheneOS release it is based on.
- Devices
- The Pixels GrapheneOS supports. Builds so far: Pixel 8 Pro, Pixel 10a (untested). The Pixel 11 series is not supported and won't be: it lacks hardware memory tagging. See devices.
- Based on
- GrapheneOS 17 (Android 17).
- Install
- From Windows, macOS or Linux: install guide.
- Guides
- Setting up, installing apps, crypto wallets.
Source
Design notes, test scripts and per-feature patches:
ee1os/ee1os. The code is on the
envs-17 branch of each fork in github.com/ee1os.