--- title: "Android XR and who owns the body of your assistant" url: "https://kyberdeck.com/blog/android-xr-and-who-owns-the-body" description: "On Android XR one company makes the glasses, another the system, the assistant and the store. What that layering means for the person wearing them, and how we see it." --- # Android XR and who owns the body of your assistant October 13, 2026·4 min read·Editorial team A rounded yellow compute puck with its back cover lifted off beside it, showing the board, plain display glasses folded behind it You pay for a pair of display glasses. They are on your face all day, they hear what you say and see what you look at. Six months later an update arrives: the assistant answers differently, one feature now needs an account it did not need before, and a setting you relied on has moved. Nothing broke. You just learned that the device on your face takes instructions from more than one place, and you are not first on the list. That is the question behind [XREAL Aura](https://kyberdeck.com/blog/glasses-with-a-puck) and every other device on Google’s Android XR: not whether the hardware is good, but whose system runs the body. ## The real cause: a body built in layers by different owners Android XR is Google’s platform for XR devices: headsets, glasses with a display and glasses with audio only, with Gemini as the assistant layer. It is developed with Samsung and Qualcomm. The first device was Samsung’s Galaxy XR headset in October 2025. At Google I/O in May 2026 Google showed glasses made with Samsung and Qualcomm, with frames from Warby Parker and Gentle Monster; Samsung has announced its own Gemini glasses for November 2026, without a price or a date. Aura is the first priced Android XR device in the class of glasses with a display. Each of those devices is built in layers, and each layer has an owner. The frame and the optics belong to one company. The chip to another. The system, the assistant and the app store to Google. The person wearing it owns the object and a licence to everything that makes it work. That is normal for phones. On a phone you can put it in a drawer. On your face, with a camera, the layering matters more. ## Where control over the body actually sits **The system decides what the sensors are for.** Which app may use the camera, when the microphones listen and what counts as consent are rules of the platform, written by its owner, changed by its updates. **The assistant belongs to the system, not to the device.** On Android XR, Gemini is a layer of the platform. XREAL describes it as able to understand what you are looking at, open apps and navigate the interface for you. That makes it the most powerful program on the device, and it is not the device maker’s to change. **The brain may be somewhere else.** For glasses, the Android XR SDK offers Jetpack Projected: the app runs on a host device, such as a phone, and projects its experience to the glasses. The audio glasses shown at I/O work with a phone (Android and iOS), and Gemini carries out multi-step tasks on the phone in the background while the glasses are its voice and camera. The body you wear may be a terminal for a computer in your pocket, which is fine, as long as you know which computer and whose. **Where the work happens is not stated.** Google has not published how much of the assistant’s work runs on the glasses, on the phone or in the cloud. Until it does, you cannot tell what a glance sends away. **The store decides what runs, unless a door is left open.** Apps come from Google Play. Aura is interesting because XREAL also documents full ADB access on its puck. That is the maker leaving a door in a layer it does not own. ## How KyberDeck approaches it Kyber does not build on Android XR and does not integrate with it. What the platform shows us is how much of a body’s behaviour is decided above the hardware, and that is where we start. **One system you can read on every body.** Every KyberDeck form runs KyberLinux, with verified boot and atomic updates, so an update cannot quietly change what a device does. Android XR is also built on a Linux kernel, and [Android XR is Linux underneath](https://kyberlinux.com/blog/android-xr-is-linux-underneath) explains why that is not the same as an open system. **The assistant is yours, not the platform’s.** KyberBot runs on your devices and keeps its memory there, encrypted. What changes when the assistant is part of someone else’s system is the subject of [Android XR: the assistant in the system](https://kyberbot.com/blog/android-xr-assistant-in-the-system). **A body can be a terminal, and the host should be yours.** We like the idea behind Projected: a light body, a host that does the work. In our design the host is your own Pocket or [home node](https://kyberdeck.com/blog/the-home-node), not an account. **An exit you can use.** The system image, the schematics and both SDKs are meant to be published together, so that a device can be reinstalled by its owner. For a company, building on any platform should come with a way out, which KYBERTIS covers in [Android XR with an exit clause](https://kybertis.com/blog/android-xr-with-an-exit-clause). To be fair about it: Android XR has things we do not. It has a working SDK, an emulator and devices you can order. KyberDeck has designs, prototype boards and a [homepage](https://kyberdeck.com/) that says so. ## A test you can run today Open the permission settings on your phone and find the assistant app. Write down what it may do: microphone, camera, location, notifications, acting inside other apps. Then ask who can change that list without asking you. That is the body problem in miniature. If you write software, the glasses emulator and the Jetpack Projected documentation are on [developer.android.com/xr](https://developer.android.com/xr). Build one sample and note which device the code actually runs on. The answer to “whose body is this” starts there. - Android XR - platforms - ownership - XR glasses ## Keep reading - [A lost deck: what a stranger can read from it](https://kyberdeck.com/blog/a-lost-deck) - [Battery, not processor: how long a deck runs off the grid](https://kyberdeck.com/blog/battery-not-processor)