Mobile navigation

YOUR SPEED. YOUR DEVICE.

GPS Speedometer Not Working? Check Permissions and Signal

If a GPS speedometer is not working, check location permission, device Location Services and whether the page has a usable recent reading. Press Start to request access; an existing block must be changed in the browser or device settings.

Check location permission first

Xpeed calls the browser's location API directly when you press Start. It does not request location when the page loads. Permission already granted can let the watch begin without another prompt.

In Chrome or Edge, open the site permission controls beside the address and check Location. In Firefox, review or clear the site's location block. Menu labels vary by browser version.

Check device location settings

Safari, Chrome and other browsers also depend on the operating system's location permission. Check that Location Services is enabled and the browser may use it. If your device offers precise location, check that setting too.

On an iPhone or iPad, review system Location Services and the website's location setting. On a Mac, review Safari website permissions and system location permission. This guide does not claim those screens were tested on your exact OS version.

Wait for a usable reading

A permission prompt allows access; it does not guarantee a fresh location. Indoor spaces, tunnels and covered areas can make a reading unavailable. Move to an appropriate safe location and press Retry when offered.

Xpeed displays a dash when data is missing or stale. Zero is reserved for a valid zero-speed reading. Keeping an old number on screen would hide a gap.

Keep the page visible

Browsers may suspend location work when a tab is hidden or the screen is locked. Xpeed releases its watch while hidden and checks for fresh readings when the page returns.

If access is denied, change the permission and press Start again. Repeatedly pressing Start cannot override a browser block.

Describe a persistent problem

Contact Xpeed with the tool name, browser, device and steps that produced the issue. Do not include precise coordinates or private journey details.

The steps here are based on the browser API contract and Xpeed's permission implementation. Real-device behavior still needs to be checked on the device where the problem occurs.

Sources and methods