--- title: "A pocket computer with ADB: what XREAL Aura opens up" url: "https://kyberlinux.com/blog/a-pocket-computer-with-adb" description: "XREAL Aura puts a full Android computer with ADB in your pocket. Debug access is real openness, but it is not ownership. Here is where the line runs." --- # A pocket computer with ADB: what XREAL Aura opens up October 13, 2026·4 min read·Editorial team Plain folded display glasses joined by a short cable to a rounded pocket compute puck, a second cable plugged into the puck's side port Read the spec sheet of [XREAL Aura](https://www.xreal.com/aura) the way a developer reads it and one line stands out. Not the 70-degree field of view or the micro-OLED panels. It is the compute puck at the other end of the cable: a Qualcomm Snapdragon Reality Elite with 48 TOPS for SI work, 12 GB of memory and 256 GB of storage (or 16 GB and 512 GB), a 4455 mAh battery, Wi-Fi 6E, GPS, a fingerprint reader, a second USB-C port that takes DisplayPort in, and full ADB. That last item turns a pair of glasses into a pocket computer you can plug a laptop into. You can install your own software, read its logs and open a shell. For a consumer device, that is more than most offer. It is also worth being precise about what it is not. ## The real cause: openness has layers A device is open in as many ways as it has layers. ADB, the Android Debug Bridge, opens the top of the stack: apps, files, logs, a shell with the permissions the system grants it. Below that sit the system image, the boot chain and the firmware, and above it sit the assistant and the services it talks to. Aura runs [Android XR](https://kyberlinux.com/blog/android-xr-is-linux-underneath), with Gemini as the built-in assistant and Google Play as the store. Debug access does not change who builds those layers, who signs them or who decides when they change. That is not a criticism of XREAL. It is how almost every phone works. But a puck in your pocket with cameras on your face is about to carry an assistant that sees what you see, so the question of which layers you actually control matters more than it did on a phone. ## Where debug access stops **Debugging is not owning.** ADB lets you work inside the system someone else built. It does not, by itself, let you replace that system. Whether the bootloader can be unlocked, and what happens to the device’s other features if it is, XREAL’s public material does not say. Ask before you assume. **The image is signed by someone else.** Verified boot checks that the system has not been changed. That protects you, as long as the keys that define “unchanged” belong to someone you trust. On a typical Android device they belong to the maker. **The assistant is part of the platform.** Gemini is not an app you add; it is the assistant layer of Android XR. It understands what you look at, opens apps and navigates the interface for you. That is useful, and it means the most capable software on the device is the one you can inspect least. **Where the work runs is not written down.** The puck has 48 TOPS, and the glasses carry tracking cameras, a high-resolution camera with a privacy light and four microphones. XREAL does not publish which parts of the assistant’s work run on the puck and which go to the cloud. A spec sheet tells you what the hardware could do locally, not what the software does. **Updates on someone else’s schedule.** The system, the assistant and the apps each update on their own clock. You get a better device and a different device at the same time, and you cannot hold one back without the others. ## What KyberLinux is built to do instead The form itself is good. Glasses for the display and a puck in the pocket for the compute is close to what KyberDeck calls a Pocket, and the [KyberDeck view of Aura’s form](https://kyberdeck.com/blog/glasses-with-a-puck) covers what the weight, the cable and the battery teach. KyberLinux is about the layers underneath, and the design answers each of the points above. **An image you can read and build.** The definition of a [KyberLinux](https://kyberlinux.com/) image is a public file. You can see what goes into it, build it yourself and compare the result with ours. **Verified boot with keys you can hold.** The boot chain checks every stage, and where the hardware allows it, the keys that define a trusted system can be yours rather than a vendor’s. Why that matters more than it sounds is in [immutable, verified, boring](https://kyberlinux.com/blog/immutable-verified-boring). **The assistant as a guest, not the landlord.** KyberBot runs on KyberLinux like any other workload, and the agents it hands work to run each in its own KyberCell, with files fixed at creation and the network closed by default. How the system enforces that is in [how KyberLinux keeps a swarm in its cells](https://kyberlinux.com/blog/how-kyberlinux-keeps-a-swarm-in-cells). What it means for an assistant that sees what you see is the subject of [KyberBot’s piece on Aura](https://kyberbot.com/blog/an-assistant-that-sees-what-you-see). **A record of where work ran.** Every step an agent takes is logged as a trajectory, including whether it ran on the device or left it. The question of what should stay on a 48 TOPS puck at all is taken up by [KyberFusion](https://kyberfusion.com/blog/what-stays-local). KyberLinux does not integrate with Android XR and is not built to run on Aura. Nothing here describes a feature on that device. ## The honest limits KyberLinux is pre-launch: there is nothing to install, and no glasses or puck have been tested with it. Owning the keys also means owning the consequences: lose them and you lose the ability to update your own device. And Aura is not yet available everywhere. Preorders opened on 7 October 2026 for people who had reserved one, from 1279 USD, and the first wave ships to the US, Canada, Japan and South Korea, with other markets in 2027. Poland and the rest of the EU are not on the first list. ## A test you can run today You do not need Aura for this. Any Android phone with developer options and USB debugging switched on will do. Connect it to a computer with ADB installed and run: 1. `adb shell uname -r` shows the Linux kernel version under the system. 2. `adb shell getprop ro.boot.verifiedbootstate` returns a colour: `green` means the system was verified against the maker’s keys. 3. `adb shell getprop ro.boot.flash.locked` returns `1` if the bootloader is locked. 4. `adb shell "pm list packages | wc -l"` counts the packages installed, most of which you never chose. Then write down, for each answer, who could change it: you, the maker or nobody. That list is the real openness of the device in your pocket. Ask the same four questions of the next one you buy, glasses included. - XREAL Aura - Android XR - ADB - verified boot - KyberDeck ## Keep reading - [Logs an agent can read and a person can understand](https://kyberlinux.com/blog/logs-an-agent-can-read-and-a-person-can-understand) - [Drivers for hardware we have never seen](https://kyberlinux.com/blog/drivers-for-hardware-we-have-never-seen)