The short answer

A phone update breaks pairing when the companion app, Bluetooth permissions or glasses firmware no longer match the phone’s new OS. Prevent this by updating the companion app and the glasses firmware first, take screenshots of app settings and permissions, disable battery optimisation for the app, run a short baseline test, then install the phone update.

Time needed about 60–90 minutes total, spread over a single session plus any firmware downloads

Key takeaways
  • Update the companion app and the glasses firmware before the phone OS update to avoid most breakages.
  • A single screenshot inventory of OS build, app version, firmware and paired device name speeds recovery.
  • Disable battery optimisation and prevent permission auto‑revocation for the companion app before updating the phone.
  • Run and record a short baseline test before the update and repeat it immediately after the update.
  • If pairing breaks, try restart, forget & re‑pair, reinstall the app, then test with a spare phone before contacting vendor support.
Before you start
  • Phone charged and connected to Wi‑Fi for app and firmware downloads.
  • Glasses charged and the companion app already installed and signed in.
  • USB or charging cable for the glasses if a wired recovery method exists.
  • Access to the companion app sign‑in method or Google account credentials to reauthenticate.
  • A second phone available to test whether the problem is the updated phone.

The steps

  1. Capture phone OS and buildOpen Settings > About phone (or About device) and take a screenshot of the OS version and build string.You should see: A screenshot in your photos showing the phone model, Android version and build string.
  2. Note companion app versionOpen the companion app or its Play Store listing and take a screenshot of the app name and full version.You should see: A screenshot showing the companion app name and version number saved to your photos.
  3. Record glasses firmware versionIn the companion app open Device info or Firmware update and capture the firmware version shown for the glasses.You should see: A screenshot showing the glasses' firmware version or an 'Up to date' confirmation.
  4. Export app settings and permissionsIf the companion app offers an export, save it; then open Android Settings > Apps > [companion app] and screenshot permissions and battery settings.You should see: Saved exported settings or screenshots of permissions and battery settings in your photos or files.
  5. Update the companion appOpen the Play Store and update the companion app, then confirm the new version in the app About page.You should see: Play Store shows the app is updated and the app About page shows the newer version.
  6. Update the glasses firmwareUse the companion app's firmware update flow to install any available firmware on the glasses and wait for confirmation.You should see: The companion app reports the firmware update completed or shows 'Up to date'.
  7. Set battery and permission exceptionsIn Android Settings > Apps > [companion app], set battery optimisation to not optimised/unrestricted and confirm required permissions are allowed.You should see: The app shows permissions are granted and battery optimisation is disabled or set to allow background activity.
  8. Run baseline testsWith the glasses connected, play audio or a test video, start a short call or voice assistant, enable captions if used, and leave the app running in background for five minutes.You should see: Audio plays through the glasses, captions appear when enabled, and the companion app remains connected without errors.
  9. Install the phone update and retestInstall the phone OS update following the phone's prompts, restart the phone after installation, then repeat the baseline tests and note any permission prompts or errors.You should see: Phone shows the update completed message; after restart the companion app either reconnects and passes the baseline tests or displays specific error prompts you can screenshot.

How phone updates interrupt pairing

Phone OS updates change the Bluetooth stack, permission rules or background service behaviour. When the companion app or the glasses firmware are still written for the old OS, the app can crash, fail to request a new permission, or be prevented from running in background. Update the app and firmware first and snapshot settings to avoid this sequence.

  • OS changes that matter: Bluetooth behaviour, permission model, background service policies.
  • Prepare by updating companion software and recording settings before you install the phone update.

Record your inventory before the update

Capture the phone OS/build, companion app name and version, glasses firmware version and the Bluetooth paired device entry. Save screenshots so you can prove what changed or restore settings. This inventory is the single artifact that speeds vendor support and lets you reproduce the pre‑update state.

  • Phone OS and build string (Settings > About phone).
  • Companion app name and full version (app About page or Play Store).
  • Glasses firmware version shown in the companion app's device info.
  • Screenshot the paired Bluetooth device entry so the device name and pairing type are visible.

Back up app state and pairing metadata

Back up system data and export companion‑app settings where the app allows it; screenshots of permission pages and pairing entries are essential. General phone backups rarely include the app's pairing metadata, so export logs or diagnostics from the companion app if it offers that option.

  • Run an Android system backup if you use one and save exported app settings where available.
  • Take screenshots of app permissions, battery settings and the Bluetooth paired device entry.
  • Export diagnostics or logs from the companion app if the option exists.

Update companion apps and glasses firmware first

Install the latest companion app from the Play Store and apply any firmware updates the companion app offers before updating the phone. Newer app and firmware releases often include fixes for a changed Bluetooth stack or permission handling introduced by phone updates. Check the app's About page and the vendor support page for compatibility notes.

  • Open the Play Store and update the companion app; confirm version in the app About page.
  • In the companion app, run the firmware update flow and wait for confirmation that firmware is current.
  • Check the vendor support page or release notes for any compatibility warnings before you update the phone.

Phone settings to check before updating

Ensure Bluetooth is on and the companion app has the permissions it requests (Location or Nearby Devices, microphone where needed). Disable battery optimisation for the companion app and prevent automatic permission revocation by running the app just before the update. Note any OEM device‑management features that could change after the OS update.

  • Bluetooth turned on and discoverable if required by setup.
  • Grant Location/Nearby Devices and microphone permissions if the app requests them.
  • Set the companion app to not be battery‑optimised or to run unrestricted in background.
  • Run the app just before updating to avoid Android auto‑revoking unused permissions.

Pre‑update and post‑update test plan

Run a short baseline test before the update and repeat it immediately after: connect the glasses, play audio or a test video, start a call or voice assistant, enable captions if you use them, and let the companion app run in background for five minutes. The same scripted checks make it clear whether a failure is caused by the phone update.

  • Baseline tests to run: connect, audio playback, captions/translation, background persistence.
  • After the update, reconnect, reopen the companion app, grant any new permission prompts, and compare behaviour to the baseline.
  • Capture screenshots of any permission prompts, errors or crash dialogs.

Recovery steps when pairing fails

If pairing breaks, work through restart, forget & re‑pair, reinstall the companion app, then test with a spare phone. Collect screenshots and exported logs before contacting vendor support; those artifacts let the vendor identify whether the fault is the phone OS, the app, or the glasses firmware.

  • Restart both phone and glasses, then try reconnecting.
  • Forget the device in Bluetooth settings and follow the companion app's pairing flow.
  • Reinstall the companion app and re‑grant permissions if the app crashes or refuses to connect.
  • Test with a spare phone to isolate whether the updated phone is the source of the problem.

Typical failure sequence you will see

Most failures follow the same steps: the phone updates first, the old companion app either crashes or fails to request a new permission, Android auto‑revokes unused permissions or a battery saver stops the app, and the glasses appear as paired in Settings but the companion app shows them offline. Updating app and firmware first prevents this chain.

  • Order error: phone updated before app and firmware.
  • Permissions revoked: Android marks the app unused and revokes permissions.
  • Background service killed by aggressive battery settings, preventing reconnection.

What to do next

Follow the checklist now: capture your inventory, update companion software and firmware, set battery and permission exceptions, run the baseline test, then install the phone update and repeat the tests. After that, confirm device and app compatibility on the GlassesApps device page for your model and consult our Android checklist if you are updating a major Android release.

  • Check device pages: /devices/ray-ban-meta or /devices/xreal-air-2-ultra.
  • See our Android guidance at /articles/android-17-xr-checklist and app listings at /apps.
  • Run the caption test in /articles/10-minute-smart-glasses-test if you rely on captions or translation.

Where this usually goes wrong

  • Companion app shows the device offline though Bluetooth shows pairedThe app lost required permissions or its background service was stopped by battery optimisation after the OS update.Open app permissions and battery settings, allow required permissions and background activity, kill and restart the app, then forget & re‑pair the device if needed.
  • Connection attempts fail with authentication or pairing errorCached pairing metadata mismatched after OS changes or the glasses firmware is incompatible with the phone's updated Bluetooth behaviour.Forget the glasses in Bluetooth settings, reboot both devices, run the companion app pairing flow again; if it still fails, test with a spare phone to isolate the phone as the cause.
  • App repeatedly crashes after the phone updateThe companion app is outdated or a vendor SDK in the app needs an update for the new OS.Reinstall the companion app from the Play Store to get the latest build; if crashes continue, export diagnostics and contact vendor support with the saved screenshots and logs.
  • Features such as captions or translation stop workingA required permission (microphone, location) was auto‑revoked or not requested under the new OS rules.Open Android Settings > Apps > [companion app], grant the missing permissions, restart the app and repeat the relevant feature test.

The checklist

  • Capture phone OS and build
  • Note companion app version
  • Record glasses firmware version
  • Export app settings and take permission screenshots
  • Update the companion app
  • Update the glasses firmware
  • Set battery and permission exceptions
  • Run baseline tests
  • Install the phone update and retest

Frequently asked questions

Will a phone OS update always break my smart glasses pairing?

No. Most phone updates do not break pairing. When pairing does fail, it is usually because the companion app or the glasses firmware needed an update, or because permissions or battery settings changed; updating those first and running a baseline test avoids most problems.

Can I roll back a phone update if pairing breaks?

Rolling back a phone OS update is rarely straightforward and often not possible without vendor tools. Try the recovery steps first: restart devices, forget & re‑pair, reinstall the companion app, and test with a spare phone. Only consider rollback if vendor support instructs you to do so.

What logs or screenshots should I collect for vendor support?

Capture phone About > OS/build, companion app About/version, glasses firmware screen, the Bluetooth paired device entry, and any error messages. If the companion app offers a diagnostics or log export, save and attach that file to your support case to speed diagnosis.

My companion app asks for a permission after the update and then fails — what now?

Grant the permission and then kill and restart the companion app; if it still fails, uninstall and reinstall the app and re‑grant permissions when prompted. If Android repeatedly auto‑revokes permissions, set the app to not be battery‑optimised and run it just before the phone update.

Find apps that work on your glasses

Every app in the directory lists the glasses it runs on, how it works on each, and the official source that proves it.

Browse the app directory