The short answer

Run a focused 15–20 minute demo on a returnable unit. Sign into your Google account, install or sideload each app, play a DRM-protected title with subtitles for 15 minutes, pair a Bluetooth controller and start a Google Maps route. Any DRM, input mapping, or navigation failure is a dealbreaker.

Time needed about 20–30 minutes, mostly in a single store visit with a 15-minute playback run

Key takeaways
  • A focused 15–20 minute demo exposes the most common failures: sign-in and Play Store issues, sideload runtime crashes, controller mapping and DRM refusals.
  • If a streaming app refuses Widevine-protected content on the demo unit, treat that as incompatible until the vendor confirms a firmware fix.
  • Sideloaded APKs that install but do not accept input or updates are functionally unusable on glasses.
  • Navigation is quick to check: missing turn prompts, off-screen overlays or permission dialogs you cannot accept make mapping unusable.
  • Always test with your own Google account and the controller you intend to use; store demos can hide real-world problems.
Before you start
  • A Google account that can sign into Play Store and streaming services
  • Working test accounts for the streaming services you need to verify
  • Phone with USB‑C cable and any APK files you want to sideload
  • Bluetooth controller and a keyboard (if you use text input)
  • Access to a demo unit or a returnable unit you can test privately

The steps

  1. Sign into Google on the unitOpen Settings or the Play Store on the glasses and sign in with the Google account you use for Play Store and streaming servicesYou should see: Play Store shows your account name and your library; Install buttons are active for apps
  2. Install a streaming app from Play StoreSearch for the streaming app in the Play Store and install it normallyYou should see: The app installs and opens to its home screen without an 'unsupported device' or install error
  3. Play a protected title for 15 minutesOpen the installed streaming app, select a DRM‑protected title and play it for at least 15 minutesYou should see: Playback starts, player controls are visible and no DRM or 'cannot play' message appears
  4. Enable subtitles and verify syncDuring the same playback, turn on subtitles or closed captions and watch for correct text and timingYou should see: Subtitles appear on screen and remain in sync with spoken audio for the duration of playback
  5. Pair your Bluetooth controllerPut your controller in pairing mode and connect it via the glasses' Bluetooth settingsYou should see: Controller appears in the Bluetooth devices list and can be used to navigate the app UI
  6. Sideload and open an APKTransfer an APK via USB or your phone, enable installs from unknown sources, and install the APK using the package installerYou should see: The app installs, appears in the apps list and opens to its expected launch screen
  7. Test Google Maps turn-by-turnOpen Google Maps, enter a short route and start navigation to observe turn prompts and overlay placementYou should see: Current location and next‑turn information are visible and turn prompts appear with enough time to act
  8. Compare native vs casting playbackCast from your phone to the glasses if supported, then play the same title natively in the glasses app to compare behaviourYou should see: Both casted and native playback run without DRM errors and controls work as expected
  9. Run a thermal and stability playbackContinue streaming for 15 minutes while interacting with the device and watching for frame drops, audio desync or app exitsYou should see: Playback continues smoothly with no sudden app closures and device temperature remains within a reasonable feel

Test Google TV app compatibility on glasses in 15–20 minutes

Run a short, ordered checklist to confirm Play Store sign-in, app install or sideload, a 15‑minute DRM playback with subtitles, Bluetooth controller mapping and Google Maps turn‑by‑turn. Do these checks on a demo or returnable unit and stop if a core capability fails; that failure is a legitimate reason not to buy.

What to bring and prepare for the demo

Bring the exact phone, accounts and controller you use at home so you can reproduce your real setup. Ask to use a demo unit or borrow a returnable unit and test privately for at least 20 minutes. Record failures on your phone to show the seller if you need to return the device.

  • Your phone signed into the Google account you use for Play Store and streaming services
  • Test accounts or trial credentials for the streaming services you want to verify
  • USB‑C cable and a small hub or adapter for file transfer if the unit exposes a port
  • The Bluetooth controller you plan to use and a small keyboard for text entry
  • Any APK files you plan to sideload and a microSD or USB drive if the glasses accept external storage
  • A phone camera to record visible errors and permission dialogs

Step-by-step checklist you run on a demo unit

Run the checks in order. Each action is one observable step: confirm account and Play Store access, install or sideload apps, start a DRM playback with subtitles for 15 minutes, pair your controller and start a Maps route. Verify the expected on-screen result at each step before proceeding to the next.

  • Sign into the unit with your Google account and open the Play Store: see your account and library and be able to install apps
  • Install the streaming app from Play Store where available and open it to its home screen
  • Play a protected title: player controls appear and no DRM error shows
  • Turn subtitles on and confirm they remain in sync
  • Cast from your phone and then test native playback to compare behaviour
  • Pair a Bluetooth controller and navigate menus and player controls
  • Sideload an APK and confirm it opens, accepts input and signs you in
  • Open Google Maps, start a route and confirm turn prompts and overlays
  • Stream for 15 minutes watching for frame drops, AV desync or crashes
  • Note thermal warnings and whether the device throttles or closes apps

How to test navigation and location behavior

Open Google Maps, start a short route and confirm current location, next‑turn prompts and permission dialogs are usable via the glasses' input method. Check overlay placement relative to your field of view and, if the device supports a camera passthrough AR mode, verify arrow alignment. If Android XR is involved, consult Google's Android XR documentation.

  • Start a turn‑by‑turn route and confirm current location and next‑turn info are visible
  • Verify permission dialogs present Accept or Allow buttons you can activate with your input method
  • Confirm overlays sit where you can see them in your field of view and are not off‑screen
  • If a camera passthrough AR mode is available, check alignment of arrows with the real world
  • If the device uses Android XR, check Google's Android XR documentation for known limitations

Sideloading APKs safely and what to expect

Sideloading lets you run apps not published to the glasses' Play Store. Enable installs from unknown sources, transfer the APK to the unit and use the system package installer. Expect some apps to install but fail at runtime if native libraries or drivers are missing; also note whether updates succeed later.

  • Enable install from unknown sources when prompted and use the built‑in package installer
  • Open the sideloaded app and confirm it accepts input and can sign in where required
  • Check that updates install normally; if updates fail due to signature mismatch, record that
  • If sideloaded apps crash while running on the glasses but run on your phone, ask the seller for firmware details

Controller and input checks

Pair the exact controller you plan to use and exercise every button and axis the app needs. Confirm the controller appears in Bluetooth settings and, if supported, shows battery level. If you rely on hand‑tracking or a touchpad, test those fallbacks for menu navigation and text entry so you do not discover missing input later.

  • Pair via Bluetooth and confirm the controller appears in Settings
  • Use the controller to navigate menus, select content and control playback
  • Test text input with a keyboard and confirm cursor placement and onscreen keyboard invocation
  • Check hand‑tracking or touchpad fallbacks if you do not have a controller

Battery, thermal and playback sanity checks

Stream continuously for 15 minutes while interacting with the device and watch for frame drops, audio/video sync drift and abrupt app exits. Note surface temperature and any visible throttling or UI sluggishness. Record the exact time a problem appears so you can report it to the seller or compare against firmware notes.

  • Start a 15‑minute DRM playback and watch for frame skips or audio desync
  • Observe device surface temperature and UI responsiveness during the run
  • If an app force‑closes, reproduce once and record logs or timestamps
  • Note any sudden quality drops or background service shutdowns

How to interpret results and what to ask the seller

Treat failed core tests as red flags. Record firmware and OS build numbers and ask whether the unit is a production build. Get the return window in writing. If the seller cannot reproduce a working app under your account and controller, do not buy the device.

  • Ask for firmware and OS build numbers and note them down
  • Request a written confirmation of the return policy or demo period
  • If the seller offers an update as a fix, ask how updates are delivered to retail units
  • If DRM fails, ask whether the vendor supports the required Widevine coverage and request proof

Why this fails in practice and the failure sequence you will see

Failures usually follow a predictable sequence: account or Play Store sign‑in blocks installs, sideloads install but crash, controller mapping fails, then DRM or thermal issues break playback. Running checks in that order helps you triage quickly and ask the seller targeted questions during a short demo.

  • Typical sequence: cannot sign into Play Store → app won't install → sideload installs but crashes → controller mapping fails → DRM blocks playback
  • Store demos can hide problems by using shared accounts or restricted networks; always use your account
  • An app listed in the store can still be blocked from playing protected content; verify a protected title plays for the full test

Next step: run the checklist and compare results

Run the checklist on a demo or returnable unit and record which steps passed and failed. After testing, compare your results with our GlassesApps directory and device pages to find known workarounds or vendor notes before you decide to buy.

Where this usually goes wrong

  • App installs but playback shows a DRM or 'cannot play' messageDevice lacks the required Widevine DRM level or the vendor has not registered the device with the DRM providerAsk the seller for firmware and DRM support details and insist on proof of a working protected title on your account; treat unresolved DRM as a dealbreaker
  • Sideloaded app installs but crashes on launch or lacks input responseMissing native libraries, incompatible GPU or missing input mapping in the glasses' Android buildTry a different APK build if available and ask the manufacturer about firmware updates or known incompatibilities
  • Map overlays or turn prompts are off‑screen or permission dialogs cannot be acceptedUI scaling or input methods on the glasses do not support the app's permission dialogs or AR overlaysConfirm whether the device supports AR overlays or a glasses‑optimized UI; if not, consider a different device
  • Device becomes hot and playback performance drops or the app exitsThermal throttling or power management shutting down services during heavy useRequest documentation on thermal limits and ask if a firmware update addresses throttling; avoid devices that cannot sustain expected sessions

The checklist

  • Sign into Google on the unit
  • Install a streaming app from Play Store
  • Play a protected title for 15 minutes
  • Enable subtitles and verify sync
  • Pair your Bluetooth controller
  • Sideload and open an APK
  • Test Google Maps turn-by-turn
  • Compare native vs casting playback
  • Run a thermal and stability playback

Frequently asked questions

Can I rely on streaming app store listings to prove compatibility?

No. Store listings show availability, not whether a protected title will play, subtitles render correctly or controller mapping works. Verify by signing into your account on the unit and playing a DRM‑protected title for 15 minutes while testing subtitles and controller input.

What if the demo unit uses a locked or shared account?

Ask to sign in with your own Google account. Shared accounts often hide DRM, sign‑in or purchase issues. If the seller refuses, treat the demo as unreliable and insist on a returnable unit or a written demo policy you can use to retest at home.

Is sideloading safe on Google TV glasses?

Sideloading is an Android feature when enabled in settings. It is reasonable for short tests if you use official APKs and revoke unknown‑source permissions afterwards. The main practical risk is that sideloaded apps may not update or may fail due to missing device libraries.

How do I check Widevine or DRM level quickly?

Play a protected title inside the official streaming app; DRM failures usually show a content‑blocked or cannot‑play message. For official confirmation, ask the seller for firmware details and the device's DRM declaration and check the vendor support page.

What should I do if the device overheats during the 15-minute test?

Record when overheating or throttling appears and ask the seller about thermal limits and firmware updates. Overheating that degrades playback or causes app exits on a demo unit suggests the device will be unreliable for longer sessions.

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