GPS Test

Introduction

The DeviceHub GPS Test is a free online geolocation smoke check that requests a browser location fix and shows coordinates, accuracy, and timestamp, without installing vendor GPS tooling, without claiming survey-grade GNSS, and without uploading your coordinates to DeviceHub for advertising or storage when you merely run the test. Delivery drivers verifying permission UX in WebViews, developers debugging getCurrentPosition failures, educators teaching indoor accuracy collapse, privacy advocates demonstrating on-screen-only display, support staff confirming Location Services toggles, and QA comparing Precise Location modes on iOS all open HTTPS, answer the browser’s geolocation prompt, and read the fix locally. GPS/geolocation accuracy varies indoors; coordinates shown by DeviceHub stay on screen for the diagnostic and are not uploaded by DeviceHub for advertising profiles. DeviceHub typed permissions remain none (PermissionKind has no geolocation or motion member); OS or browser prompts may still appear for geolocation or motion, editorial copy explains those prompts without inventing union values. Complementary sensors in this category are often mobile-oriented with desktop unsupported; iOS motion tools still need gestures, but geolocation uses its own prompt model. This page is not Compass Test, not a mapping product that loads third-party tiles by default as a tracker, and not IP-based city guesswork from Network tools like IP Address. Pair with Compass and Orientation when heading and tilt join the story. Pair with Device Information for hub context without coordinates. Pair with Accelerometer when motion plus location appear in one bug. Schools should emphasize revoke-after-demo and shoulder-surfing awareness because coordinates on screen are visible to anyone nearby.

What this tool does

GPS Test calls the Geolocation API using getCurrentPosition or watch-style flows as implemented in the UI, renders latitude, longitude, accuracy in meters when provided, and a timestamp, and labels denied, unavailable, and insecure-context states clearly. It explains that DeviceHub typed permission metadata is none while the OS or browser geolocation prompt still appears, allow or deny consciously. It does not reverse-geocode to your street address as a tracking product, does not upload fixes to DeviceHub backends for profiling, and does not bypass HTTPS requirements. Indoor Wi-Fi positioning may yield coarse accuracy measured in hundreds of meters, honesty copy says so up front. Users can deny the prompt; the page should fail closed without dark patterns. Cross-links avoid mixing public IP egress identity with GNSS fixes. Session display clears when you leave; still treat screenshots as sensitive personal data. Optional high-accuracy flags, when exposed in UI, trade battery for potentially better fixes without promising survey stakes.

When to use it

Use GPS Test when PWAs fail to obtain location, when indoor versus outdoor accuracy must be demonstrated to stakeholders, when WebView permission bugs appear, when teaching privacy of on-screen coordinates, when confirming OS Location Services interact with Chrome or Safari site permissions, and when matrices need a geolocation row beside NFC and sensor support. Prefer Network IP tools for public egress identity, not latitude and longitude. Prefer Compass Test for heading. Prefer Orientation Test for tilt. Avoid using a single indoor 500-meter accuracy sample as proof the GNSS chip is dead, retest outdoors. Retest after denying then allowing permission, after toggling Precise Location, and after moving from basement to open sky. Use in privacy workshops alongside the typed-permissions-none explanation so students understand metadata versus real prompts. City transportation PWAs should verify WebView geolocation prompts on the exact package users install, not only in desktop Chrome remote debugging. Journalism classrooms can contrast IP Address city guesses with GPS fixes to teach media literacy about location claims. Field technicians confirming that Location Services were disabled by MDM can use a denied state as evidence in tickets. Event staff checking venue Wi-Fi positioning coarseness can run indoor versus doorway tests and record accuracy meters for stakeholders who expect pin-point pins indoors.

How it works

navigator.geolocation asks the platform for a fix via GNSS, Wi-Fi, cell tower heuristics, and OS fusion. Browsers require a secure context and user permission before releasing coordinates to the page. DeviceHub keeps permissions: ['none'] in typed config because geolocation is outside PermissionKind, editorial copy must explain the real prompt every time. Accuracy is an estimate provided by the platform; indoor multipath, disabled GNSS, and Wi-Fi-only modes degrade it. GPS/geolocation accuracy varies indoors; coordinates shown by DeviceHub stay on screen for the diagnostic and are not uploaded by DeviceHub for advertising profiles. Third-party map tiles, if ever linked elsewhere, are separate concerns, this tool’s core promise is on-screen coordinates not uploaded by DeviceHub. iOS Precise Location toggles change quality. Desktop geolocation is often coarse Wi-Fi based and should not be compared blindly to phone GNSS. Emulators fake coordinates, label them in tickets. Generic Sensor Permissions-Policy issues on sibling pages do not replace geolocation permission; keep models separate. Web NFC (NDEFReader) is primarily Chromium on Android and is not available in iOS Safari for arbitrary sites. NFC is unrelated to GPS radios but appears in the same mobile suite matrices. MaximumAge and timeout options, when exposed by the UI, change whether you see a cached fix or wait for a fresh one, document which mode you used. enableHighAccuracy is a hint, not a command that forces GNSS over Wi-Fi. Some browsers show a one-time prompt while others re-prompt after permission resets; teach both. Secure context failures on misconfigured previews should be fixed at the host, not by asking users to allow location on HTTP. DeviceHub’s typed none metadata must remain synchronized with this honesty whenever PermissionKind evolves in the future, until geolocation exists in the union, copy carries the burden.

Step-by-step instructions

1. Open GPS Test over HTTPS on the target device and browser or WebView where location fails.
2. When the geolocation prompt appears, allow only if you want coordinates shown; remember typed metadata is still none.
3. Wait for a fix; note accuracy and timestamp; move outdoors or near a window if indoor accuracy is poor.
4. Screenshot sparingly; clear the screen on shared devices; revoke location permission afterward if desired.
5. Open Compass Test if heading matters; do not confuse course-over-ground with compass absolute alpha.
6. Document denied states as user or OS choice, not DeviceHub outages, and avoid pasting raw coordinates into public forums.

Common problems

Confusion about permissions none versus the visible geolocation prompt. Indoor accuracy of hundreds of meters treated as chip failure. Denied OS Location Services. WebView permission bugs differing from standalone Chrome. Emulator fake coordinates. Expecting IP city equals GPS fix. Uploading screenshots to public tickets carelessly. Confusing with Network IP Address tools. Stale cached fixes. Precise Location off on iOS. Desktop coarse Wi-Fi location mistaken for broken GNSS. Users demanding DeviceHub “store my trip” features this smoke check intentionally omits. Mixing compass magnetic interference into GPS accuracy complaints. Travelers with dual-SIM devices may see odd cell-based fixes after landing, wait for GNSS lock outdoors. Battery saver killing high-accuracy modes yields coarse results blamed on DeviceHub. Browser site permission allowed while OS Location Services is off produces confusing denies. Screenshotting coordinates into Slack public channels. Assuming VPN changes GPS coordinates, it does not; VPN affects IP tools instead. Mixing Compass magnetic errors into GPS accuracy complaints in one sentence without separation.

Privacy explanation

GPS/geolocation accuracy varies indoors; coordinates shown by DeviceHub stay on screen for the diagnostic and are not uploaded by DeviceHub for advertising profiles. Typed permissions remain none; the browser prompt still controls access, deny anytime and revoke in site settings. Clear shared screens and lock devices before walking away. Prefer coarse discussions in public forums (“fix obtained” or “denied”) without pasting latitude and longitude. Closing the tab ends watchPosition-style updates. Combining GPS with Accelerometer, Gyroscope, or Compass traces reveals routes more clearly, minimize joint public postings. Classroom facilitators should revoke location between student groups. DeviceHub’s honesty about not uploading fixes is a product promise for this diagnostic, still treat your own screenshots as sensitive data you choose to share. Prefer sharing geohashed or city-level descriptions in public issue trackers. On projector demos, pan the window so only accuracy meters show, not full latitude longitude. Parents testing family phones should revoke afterward so children do not inherit standing location access to DeviceHub. If your organization logs support screenshots automatically, mark GPS Test captures as sensitive in the ticket taxonomy.