The developer's point about vehicle magnetic interference and Android location polling makes a lot of sense. Phone magnetometers are super sensitive to all the metal and electronics in a car or even a bike frame, which completely explains that sudden 3-5 second heading jump when the sensor tries to correct itself. Whenever I notice my map jumping around or drifting like that, I like to isolate whether it's an app issue or just my phone's hardware acting up. I usually run a quick sanity check on https://123compass.org/ because it launches a clean compass and calibration test right in the mobile browser. If the heading behaves smoothly on the webpage but jumps in the mapping software, you know it's a polling conflict—otherwise, it's just the phone's hardware needing a serious figure-8 reset.
I’ve run into similar issues before, and one thing that helped was double-checking app permissions and forcing a refresh/reload after changing the settings. Sometimes the app keeps old data cached longer than expected. Hopefully that points someone in the right direction while a more permanent fix is worked out.
Little tips like these can save a lot of frustration when you're out caching. I’ll definitely give it a try next time I'm setting things up - always nice to learn a simpler way of doing things.
That’s a clever idea. It’s always nice when tools like this make geocaching a bit more interactive and help discover places you probably wouldn’t have visited otherwise.
I’ve noticed that too with some GEOOH hunts - sometimes the difficulty feels more about spotting the hidden pattern than the actual terrain. The creative hides are what make it fun though, even when they’re a little frustrating at first.
A lot of GPS weirdness like this ends up being surprisingly device-specific too. I had one phone that constantly drifted or lost lock while another on the same app worked perfectly. Clearing the AGPS data and forcing a fresh satellite download helped a ton in my case.
