Opening Google Maps to retrace your travel routes, log business mileage, or check visited restaurants only to discover that your Timeline is empty or displaying the message “No visits recorded” disrupts daily tracking. Following Google’s major architectural transition from cloud-hosted Location History to on-device Timeline storage, location records are now encrypted and stored locally on your individual smartphone rather than centrally on Google’s cloud servers. If your device has not migrated its database properly, if Android or iOS background battery optimisation aggressively restricts the Google Play services location provider, or if device-level location accuracy settings are misconfigured, Timeline stops logging coordinates. This technical guide explains the underlying mechanics of on-device Timeline tracking and outlines proven steps to restore consistent location recording across Android and iOS devices.
Why Is Google Maps Timeline Not Recording Visits?
Because Timeline coordinates are captured silently in the background, multiple system layers must operate harmoniously:
- On-Device Timeline Migration Incomplete: Google has migrated Location History to on-device storage. If you have not completed the in-app migration prompt or configured device backups, tracking may pause.
- Background Battery Optimisation: Operating systems (notably Android’s Doze mode and manufacturer-specific power managers) terminate background geofencing and GPS listener services to conserve battery life.
- Location Accuracy and High Precision Disabled: Disabling Google Location Accuracy (which fuses GPS, Wi-Fi beacons, and cellular cell tower data) leaves Google Maps unable to obtain low-power indoor position fixes.
- Restricted Background App Refresh (iOS): Disabling Background App Refresh on iPhone prevents Google Maps from receiving significant-change location notifications while the screen is locked.
- Corrupted Google Play Services Cache: Damaged location database cache files inside Google Play Services preventing geofence event triggers.
Method 1: Complete the On-Device Timeline Migration and Cloud Backup
Ensure your Google account has completed the transition to local Timeline storage and enabled encrypted backups.
- Open the Google Maps app on your smartphone.
- Tap your Profile picture in the top-right corner and select Your Timeline.
- If an on-screen prompt appears announcing “Timeline is changing”, tap Review settings and select Keep Timeline on this device.
- Tap the cloud icon with a gear or open Timeline settings (the three dots in the upper-right corner > Timeline settings).
- Under the Backups section, verify that Backup is turned On. This stores an encrypted copy of your on-device visits in your personal Google cloud account.
Method 2: Exclude Google Maps from Battery Optimisation (Android)
Prevent Android’s aggressive power management daemon from freezing Google Maps in the background.
- Open your device’s Settings app.
- Navigate to Apps > See all apps > Google Maps.
- Tap on Battery (or App battery usage).
- Change the setting from Optimised to Unrestricted.
- Return to the main Settings menu, tap Location > Location services, and tap Google Location Accuracy.
- Ensure Improve Location Accuracy is toggled On so the system can triangulate positions via Wi-Fi networks and Bluetooth beacons.
Method 3: Configure Location Permissions to ‘Always Allow’ (iOS)
On Apple devices, Timeline requires continuous background location authorization rather than access restricted to active app usage.
- Open the Settings app on your iPhone or iPad.
- Scroll down and select Google Maps from your installed applications list.
- Tap Location.
- Set the permission to Always (selecting While Using the App prevents Timeline from logging travels when your phone is in your pocket).
- Ensure the Precise Location toggle switch is enabled.
- Return to the previous screen and confirm that Background App Refresh is toggled On.
Method 4: Clear Google Play Services and Maps Cache
Stale or corrupted database fragments can prevent the location provider from registering new route checkpoints.
- Go to Settings > Apps > Google Play Services.
- Tap Storage & cache.
- Tap Clear cache.
- Return to Apps > Google Maps > Storage & cache.
- Tap Clear cache (do not tap Clear storage unless you have backed up your local Timeline).
- Restart your smartphone to reinitialize background location listeners.
Method 5: Verify Device Activity and Motion Sensors
Google Maps leverages physical motion coprocessors to detect whether you are walking, cycling, or driving.
- On Android: Open Settings > Apps > Google Maps > Permissions. Ensure Physical activity is set to Allow.
- On iOS: Open Settings > Privacy & Security > Motion & Fitness. Ensure the master toggle for Fitness Tracking and the specific switch for Google Maps are both enabled.
- Once enabled, take a short walk or drive outdoors with the phone to allow the accelerometer and GPS pipeline to record a fresh trip segment.