# How to Set Up Samsung Galaxy XR Glasses on Android XR: Phone Pairing, Apps and Gemini

> AI Release · @ai_release1 · https://ai-release.org/guides/kak-nastroit-ochki-samsung-galaxy-xr-na-android-xr-sopr_en.html

## TL;DR

- **Time to complete:** about 30 minutes (20 minutes of setup, 10 minutes of verification)
- **Difficulty:** Basic
- **You need:** Samsung Galaxy XR headset + charger, an Android phone with the Play Store, a Google account signed in on both devices, one Wi-Fi network that both devices can reach, and — optionally — a PC with Android platform-tools (`adb`) if you want to inspect installed packages.
- **The part most guides skip:** pairing is initiated **from the phone to the headset**, not the other way round, and every stage has a different failure mode. A headset that shows a Wi-Fi icon is *not* evidence that the phone link works.
- **Where this does NOT work:** you cannot finish the first-boot wizard phone-free — the wizard expects a companion app on an Android phone. And the phone-link features are tied to specific phone models; the supported list is version-specific, so **check the documentation** for your region and build before buying anything.
- **Not covered by any source post:** exact firmware versions, prices, and the precise wording of on-screen labels. Those change per build — verify them in the headset's own setup card.

## Requirements and setup
![Illustration: Requirements and setup](https://ai-release.org/guides/img/kak-nastroit-ochki-samsung-galaxy-xr-na-android-xr-sopr-en-1.jpg?v=1794559740)


- [ ] Samsung Galaxy XR headset, charged above 50% before first boot
- [ ] Android phone with Google Play Services active and the same Google account you will use on the headset
- [ ] Wi-Fi network on a single SSID — 5 GHz or 6 GHz preferred; both devices must be on the *same* subnet
- [ ] Router with **AP isolation / client isolation disabled** (this setting silently breaks pairing)
- [ ] Bluetooth enabled on the phone
- [ ] Optional: PC with Android platform-tools for `adb`, plus a USB-C data cable
- [ ] 2 GB of free space on the phone for the companion app and the apps you will push to the headset

Install `adb` on the PC if you want the verification steps to work:

```bash
# Debian/Ubuntu
sudo apt install android-tools-adb

# macOS
brew install android-platform-tools
```

**Example:** after installing, `adb version` should print a first line beginning with `Android Debug Bridge version`. If the shell answers `command not found`, platform-tools are not on `PATH` — export the folder containing the `adb` binary.

**Why this works:** `adb` is the same bridge used for phones; Android XR is built on Android, so the host-side tooling is unchanged. That is why the headset-side checks later are plain `pm list packages` calls. For more Android tooling context, see [Best AI apps for Android in 2026](https://ai-release.org/guides/luchshie-ii-prilozheniya-dlya-android-v-2026-godu.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide).

## Step 1. Prepare accounts, network, and the phone side

**What to do:** sign the same Google account into the phone's Play Store, join the 5 GHz SSID, and confirm the router does not isolate clients. Then power on the headset and keep it on the charger during the whole procedure.

**Why:** the headset inherits accounts and app entitlements from the phone during setup. If the phone is on a 2.4 GHz SSID guest network and the headset lands on the main 5 GHz SSID, the discovery broadcast never reaches the headset and the wizard stalls at "looking for your phone" without an error message.

**How to check:** on the phone, open Wi-Fi settings and confirm the network name. On the PC, run:

```bash
adb start-server
adb devices
```

Expected output when nothing is connected yet:

```
List of devices attached

```

An empty list after the header means the daemon started correctly — that is the pass condition here. A `cannot connect to daemon` line means a port conflict; fix it with `adb kill-server && adb start-server`.

**Example:** phone on `HomeNet_5G`, headset on `HomeNet_5G`, both getting addresses from the same `192.168.1.0/24` pool. If the phone shows `192.168.1.24` and the headset's network details show `192.168.8.x`, they are on different subnets — stop and fix the network before pairing.

## Step 2. Pair the headset with the phone, then install apps and enable Gemini
![Illustration: Step 2. Pair the headset with the phone, then install apps and enable Gemini](https://ai-release.org/guides/img/kak-nastroit-ochki-samsung-galaxy-xr-na-android-xr-sopr-en-2.jpg?v=1794559745)


**What to do:** put the headset on, complete the on-screen wizard, and when it asks for a phone, open the companion app on the phone and confirm the pairing code shown in both places. After the link is established, install apps from the headset's Play Store or push them from the phone. Then sign in to Gemini with the same Google account.

**Why:** the confirmation code is a mutual authentication step — it proves the phone and the headset are the two devices in the same room, not two devices on the same Wi-Fi. Skipping or mistyping it leaves the headset in a "paired but not linked" state where notifications and phone apps never arrive.

Concrete sequence with expected result at each point:

1. Power on the headset → the wizard appears inside the lenses.
2. Wizard reaches the phone step → the companion app on the phone lists a device name.
3. Select the device and compare the code → both screens show the same digits.
4. Confirm on the phone → the headset returns to the wizard and continues.
5. Wizard finishes → the home environment renders and the app grid is reachable.

**How to check:** on the headset, open the app grid and launch the Play Store; it must open signed in with your account, not with a sign-in prompt. On the phone, the companion app must show the headset as connected rather than "not connected" — the exact label varies by build, so **check the documentation** for your firmware's wording.

If you prefer installing apps from a computer instead of the headset store, the sideloading rules are identical to phones and are covered in [How to download and install AI apps on Android via RuStore](https://ai-release.org/guides/kak-skachivat-i-ustanavlivat-ii-prilozheniya-na-android.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide).

**Example — enabling the debug path before you need it:** in the headset's settings, open *About* and tap the build number repeatedly until the developer options unlock, then enable USB/wireless debugging. On the PC:

```bash
adb connect <headset-ip>:5555
adb devices
```

A successful connect prints `connected to <headset-ip>:5555` and then lists the serial with the state `device`. A state of `unauthorized` means the RSA prompt inside the headset was never accepted — put the headset on and accept it.

## Step 3. Verify pairing, apps, and Gemini end to end
![Illustration: Step 3. Verify pairing, apps, and Gemini end to end](https://ai-release.org/guides/img/kak-nastroit-ochki-samsung-galaxy-xr-na-android-xr-sopr-en-3.jpg?v=1794559752)


**What to do:** run three independent checks — one on the phone, one on the PC, one inside the headset — instead of trusting a single "connected" badge.

**Why:** each layer fails separately. Bluetooth can be paired while the account link is missing; the account link can be fine while Gemini has no microphone permission. Three checks isolate which layer broke.

| Layer | How to check | Pass signal |
|---|---|---|
| Phone link | Companion app on the phone | Headset listed as connected |
| Installed packages | `adb shell pm list packages` on the PC | Your target packages appear in the list |
| Gemini | Ask a spoken question in the headset | Answer renders in the panel and audio plays |

```bash
# Host-side filter; grep runs on your PC, not on the headset
adb shell pm list packages | grep -i -E "xr|gemini|assistant"
```

**Example:** the command returns lines of the form `package:com.google.android.googlequicksearchbox` and `package:com.samsung.android.xr.<something>` — the exact package names depend on your build, so treat any line containing your app's vendor prefix as the pass condition. An empty result means the package list was read but nothing matched: either the app is not installed, or it is installed under a different user profile on the headset.

**How to check Gemini specifically:** say a short question out loud. Success = the panel shows a transcript and then an answer, and audio comes out of the headset speakers. If the transcript appears but no answer arrives, the issue is the account/network, not the microphone.

## Troubleshooting

**Problem. The phone cannot find the headset during the wizard.**

- Error: `Couldn't pair with Galaxy XR. Check the PIN or passkey and try again.`
- Cause: the two devices are on different subnets, or the router has client isolation enabled, so the discovery packet never arrives; the code therefore times out and the retry produces this message.
- Solution: put both devices on the same SSID and subnet, disable AP isolation in the router settings, then forget the headset on the phone (Bluetooth settings → the device → *Forget*) and restart the wizard:

```bash
adb kill-server && adb start-server
```

**Problem. `adb` sees no headset even though the cable is connected.**

- Error: `adb: no devices/emulators found`
- Cause: developer options or USB debugging is off in the headset, or the RSA authorization prompt was dismissed.
- Solution: enable developer options in the headset settings, run `adb kill-server`, reconnect, and put the headset on to accept the prompt. If it still fails, switch to wireless debugging and use `adb connect <headset-ip>:5555`.

**Problem. The Play Store inside the headset refuses to load the app list.**

- Error: `Error while retrieving information from server. [DF-DFERH-01]`
- Cause: the headset-side Play Store is holding a stale account token, usually because setup finished before the phone finished syncing the Google account.
- Solution: in the headset, open Settings → Apps → Play Store → *Storage* → *Clear cache*, then reopen the store. If the error persists, remove and re-add the Google account on the headset and reboot it once.

## Summary and next steps

Pair from the phone, install from the headset's own Play Store, and verify with three independent checks so you know which layer broke. Once the link is stable, expand your app set using [Best AI apps for Android in 2026](https://ai-release.org/guides/luchshie-ii-prilozheniya-dlya-android-v-2026-godu.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide) and keep `adb` configured for package-level debugging.

## FAQ

**Can I set up the Samsung Galaxy XR without a phone?**
Not through the standard first-boot wizard — it expects a companion app on an Android phone. Whether a given build allows a phone-free path is version-specific; check the documentation shipped with your unit.

**Do I need a PC to install apps on the headset?**
No. The headset's own Play Store covers normal installs. A PC with `adb` is only needed for package inspection or sideloading, and sideloading follows the same rules as on phones.

**How do I know the headset is really paired and not just on Wi-Fi?**
The companion app on the phone must list the headset as connected, and the Play Store inside the headset must open already signed in. A Wi-Fi icon alone proves nothing about the phone link.

**Why does Gemini answer in text but not in voice?**
The transcript shows the microphone works, so the failure is downstream — account entitlement or network. Re-check that both devices use the same Google account and that the headset's network allows the assistant's endpoints.