Google Pixel phones do not remove Android's background-location rules simply because Google makes the device. A continuous tracker still needs the appropriate location permission and must coexist with Android's battery-management system.
Open Settings, find the tracker under Apps and inspect Location permission. For a route-level tracking use case, precise location should be enabled if you expect detailed coordinates.
If you intentionally chose approximate location, respect that choice: the tracker should not claim more precision than the platform provides.
An app that records only while visible can work with foreground location. An app whose core purpose is to continue tracking after you lock the phone may need background location in addition to its foreground-service design.
Android deliberately makes background location a more explicit permission because it is sensitive.
Pixel devices use Android battery features such as adaptive behavior and app restrictions. If a tracker stops unexpectedly, inspect the app-specific battery setting after confirming permissions.
Do not assume that selecting the most permissive battery option is always required; test the app under the mode recommended by its developer and change it only when the normal setting prevents the intended function.
Start a trip, lock the screen, and later check whether timestamps continued. Then reboot the phone and verify whatever automatic behavior you expect. A tracker that survives one scenario may still require additional setup for the other.
LocationOf relies on Android's standard location permission model. That makes Pixel a useful baseline for understanding the platform behavior before dealing with manufacturer-specific layers on Samsung or Xiaomi.
See Android background location for the concepts and GPS troubleshooting if the problem is inaccurate points rather than missing updates.
If a Pixel stops recording when locked, troubleshoot from the simplest layer upward. First confirm that Android Location is on and that the app still has precise permission. Next verify the app's background-location setting if that is required for the feature. Then inspect the app-specific battery mode and whether the foreground-service notification remains present while tracking.
After every change, repeat the same short test route. Note the time you locked the screen and compare it with the last point that reached the map. If the tracker stops exactly at a permission or lifecycle boundary, that timing is useful evidence.
If the app behaves correctly on Pixel but fails on another manufacturer, the difference may lie in that manufacturer's additional power-management layer rather than in Android's core location API.
If tracking stops when the phone is locked, start at the simplest layer. Confirm that Android Location is enabled and that LocationOf still has precise location permission. Next check the background-location setting required for the tracking mode you use, then inspect the app-specific battery mode and the foreground-service notification while tracking is active.
After each change, repeat the same short route. Note the time you locked the screen and compare it with the last point that reached the map. The timing of the failure often tells you more than randomly changing several Android settings at once.
Pixel phones generally expose Google's Android behavior without an additional manufacturer skin as aggressive as some competitors. If the same tracker works correctly on a Pixel but fails on another brand, the difference may point toward that manufacturer's additional battery-management layer.
That does not mean Pixel is immune to Android restrictions. Background access is intentionally sensitive, and system updates can change behavior. Re-test the setup after a major Android upgrade if you rely on continuous recording.
When testing a Pixel, note the exact time the screen was locked and compare it with the newest recorded point. If points continue with fresh timestamps, background execution is working even if the web page itself was not open. If the last timestamp freezes immediately, focus on permission and service state before blaming GPS reception.