In C. Scott Brown’s reported Google Pixel Tag tracking test, Find Hub first pointed to a general area; Bluetooth then reconnected the phone to the tag, and UWB guided him closer. His downtown search and wooded-trail search took different paths to that nearby finding stage. Google’s documented Find Hub modes explain how offline location reports can work in busy or remote places.
What happened in the city and on the trail
Brown used a Pixel 11 Pro and deliberately hid his keys in two settings. In the downtown test, a “keys left behind” alert arrived in under five minutes. The map narrowed the search to a general area, but the sound command initially failed while his phone was out of Bluetooth range. At about 30–40 feet, the phone reconnected to the tag, and UWB Precision Finding guided him to the keys in a bush. Those distances and timings are Brown’s observations from this test, not general performance specifications. Android Authority’s account describes both searches.
At a wooded trailhead, Find Hub’s last recorded location was in a nearby neighborhood. Brown searched the woods, then received a general hint from his partner. After the phone reconnected to the tag over Bluetooth, UWB guided him to the keys at the base of a tree.
Treat the map location as the start of the search; close-range Bluetooth and UWB can take over once the phone is near the tag.
How Find Hub’s offline modes work
Google’s default “With network in busy places only” setting aggregates detections from multiple Android devices before reporting an item’s location. Its “With network everywhere” mode can use a single participating device, including in remote areas. For a phone to help its owner find items through the network, it must have a PIN, pattern, or password. Google describes Find Hub location data as end-to-end encrypted. Google’s Android help and Find Hub privacy documentation explain these settings and protections.
These modes are useful context for understanding why a network location can differ from nearby finding. The reported searches move from a broader map location to a Bluetooth connection, then to UWB guidance. The account does not identify which offline mode the test phone used, so the documented settings should not be mistaken for an explanation of that particular trail result.
If you’re also deciding between tracking ecosystems, our Pixel Tag and AirTag 2 comparison covers that separate choice.
Nearby finding depends on the phone
Bluetooth provides the reported connection between the phone and tag before nearby UWB guidance. Ultra-wideband (UWB) supports precise, close-range finding on compatible devices; Google says support varies by phone and tag. Its listed UWB support includes Pixel 8 series and newer Pro models, Samsung Galaxy S21 and newer Plus and Ultra models, and Motorola Edge and Razr devices.
Google lists Pixel 9 devices and newer, together with Google Pixel Tag, for Bluetooth Channel Sounding. That feature requires Android 16 or later and Bluetooth enabled. Basic pairing is a different requirement: Android Authority reports pairing support for Android 9 or later, but that does not mean every paired phone supports UWB or Channel Sounding.
A separate early-use account offers another limited observation: Ben Schoon reported that directional cues disappeared at about 10–12 feet on his Pixel 11 Pro XL. That was his experience with one phone, not a general UWB threshold. Schoon’s report describes the observation.
