This Device Cannot Add To Location History

Understanding the Error

This Device Cannot Add To Location History is a pretty common notification you'll see on Android devices when Google's location tracking service refuses to cooperate. It usually pops up in the Google Maps app or in your Google Account settings under Location History. The device isn't broken, and your GPS hardware is almost certainly fine. What's actually happening is that some piece of the software chain between your phone and Google's servers has gone out of sync or hit a permission wall. I've seen this error on everything from a three-year-old Pixel to a brand new Samsung Galaxy S24. The root causes tend to cluster into a handful of categories. Most often it's a corrupted cache in the Google Play Services app, which is the background process that handles all location-related tasks on Android. Sometimes it's a simple toggle problem where Location History is disabled at the account level even though the phone thinks it should be writing data. Less commonly, it's a conflict with Do Not Disturb or battery optimization settings that kill the background process before it can commit your location data. I had a device come through my shop last month running a Pixel 7a that threw this error persistently even after every standard fix. The owner had recently restored from a backup that included an outdated version of Google Play Services. The version mismatch between the OS and the services app was what kept the location writer from authenticating properly. What fixed it was clearing the cache on Google Play Services, forcing a manual update to the latest version from the Play Store, and then toggling Location History off and back on in the Google Account settings. The error disappeared within about ten minutes of doing that sequence.

Step-by-Step Fixes

Start with the easiest thing that accounts for the majority of cases. Go to Settings, then Apps, find Google Play Services, open Storage, and clear the cache. Don't clear the data unless the cache clear doesn't resolve it, because clearing data will reset some preferences. After that, restart the phone. It's a small step but it forces Google Play Services to reload its configuration from scratch. If that doesn't work, check whether Location History is actually enabled at the account level. Open the Google Maps app, tap your profile picture, and look for Location History. If it says it's paused, toggle it on. If it says it's on and you're still getting the error, toggle it off, wait thirty seconds, and toggle it back on. This resets the account-side recording state without touching anything on the device. The next layer is checking Google's Location Services settings. Go to Settings, then Location, and make sure Location Services is turned on. Under that, tap Google Location Accuracy and enable both Wi-Fi and Bluetooth scanning. These aren't optional extras. They're what let the phone triangulate position when GPS signals are weak, and turning them off can sometimes cause the location writer to fail silently and then throw this error instead.

Battery optimization is another quiet culprit. If your phone has aggressively optimized Google Maps or Google Play Services, the background process gets killed mid-write and the next attempt fails with a permission-style error. Go to Settings, Apps, find Google Maps, open Battery, and set it to Unrestricted. Do the same for Google Play Services if that option is available on your device. On Samsung phones this setting is buried under Battery > App wake-up, so it takes a bit more fiddling. For devices that have been updated recently, a stale system cache can cause conflicts. Boot into recovery mode by holding Volume Up and the Power button simultaneously, then select Wipe Cache Partition. This doesn't touch any of your personal data. It just clears the system cache that accumulates during OTA updates. I've resolved this exact error on a couple of Motorola devices by doing nothing more than this step after a major Android update.

When the Standard Fixes Don't Work

Sometimes you'll do everything above and the error persists. At that point the issue is usually deeper. One possibility is that the Google account itself has a corrupted Location History record. You can check this by visiting myactivity.google.com and looking for the Location History timeline. If it's blank despite the phone supposedly recording, the server-side record is broken. The workaround is to delete the Location History data from that page, then toggle it off and on again from the phone. It takes a few hours for the new timeline to populate, but it's cleaner than trying to force the existing corrupted history to accept new writes. Another edge case involves devices that are registered as managed or work profiles. If the phone has a separate work profile enabled through Samsung Knox or a similar MDM solution, the work profile may have its own location permissions that conflict with the personal profile. In my experience this shows up most often on company-issued devices. The fix is usually to disable Location History for the work profile specifically, or to remove the work profile entirely if it's not needed for personal use. There's also the rare scenario where the device's hardware ID has been flagged by Google's anti-abuse systems. This happens when a device has been flashed with custom ROMs or when location spoofing apps have been installed. Google ties location history writing privileges to the device's security state, and if that state looks compromised, the error surfaces. There's no official workaround for this other than restoring the device to a stock firmware state and ensuring no location-modifying apps remain installed.

What This Error Is Not

A few things to clear up before you spend time on dead ends. This error does not mean your GPS receiver is broken. You can test GPS independently by opening a map app and seeing if your position drops correctly on the map. If the blue dot appears, your hardware is fine. This error also does not mean you've run out of storage. While extremely full devices can struggle with background processes, the error message is specific to the location history service, not general storage failure. And this is not the same as the "Location not available" error, which is a connectivity or permission issue rather than a recording service issue. The simplest way to verify whether the problem is on the device side or the account side is to log into the same Google account on a different Android phone and check whether Location History works there. If it works on the second device, the issue is with the first device's software state. If it doesn't work on either device, the problem is likely account-side and the myactivity.google.com approach is the right path forward.