geolocation off in Android

[larsbromley]

Hello from Geneva! I am experimenting with AuGeo and find that my location on the map in the Android app is off by several hundred meters. This of course largely moots my data, ie I am not shown what is around me, I am shown what is around a point several hundred meters away. Note this does not happen on my iPad.

My phone is a Samsung Galaxy S7 edge. The positional accuracy in its other mapping apps and online maps is fine. Let me know if you want more info.

Best,

Lars

[spatialdude]

Hi @larsbromley

Thanks for taking the time to try out AuGeo.

When you're on the map page (tap on the overview map), what accuracy is being reported?

This will appear next to the location coordinates.

Also did you happen to find that you can set your location manually (as a temporary workaround while we figure this out on your device)? Tap the the location sensor icon so it is no longer blue. You will then see a small cross hair appear on the map which represents your location that can be set by scrolling the map around.

[larsbromley]

It's very erratic honestly, right now it's showing the proper location but it took several minutes to find it, it seemed to be frozen in the last place I used it yesterday. This was a few miles away. So, maybe some way to refresh the location is good.

On a side note, measurements in meters / kilometers would be good ; )

Lars

[spatialdude]

Hi Lars

AuGeo determines the measurement units to use from your device's locale. e.g. US uses miles/feet, AU is metres/km

What locale are you using?

On the position, what you are observing seems quite strange.

I believe we have the same device here on the team and have not observed the same, but would like to figure out what's going on. Are there any other things about the way you're using that device that you think may be an influence that could give us some clues?

[larsbromley]

For locale, my time zone is CEST and my language is US English. Is it the language setting determining feet/miles?

For positional accuracy, note I just installed the latest Android update and from home my position is now accurate. My kernel is now 3.18.14-11104523. I'll check it out in coming days and let you know if the position problem has been resolved.

[spatialdude]

Hi Lars

Great news on the position problem.

And, Yes - US English would select feet/miles (imperial) vs say Australian English which selects meters/km (metric)

[larsbromley]

Hello again, sorry but position problem still exists. I am currently at office, about 8 miles from home, but AuGeo is 'stuck' at the location of home. Note at some point I changed the sensitivity for the compass and sensors in the Settings. Not sure if that had an effect.

[spatialdude]

Hi @larsbromley Are you sure you are not in "manual mode" for the position?

When you see a flashing blue ring on the overview map, or the location cursor is blue in the map view you are using the location sensor.

If the there is no blinking ring on the overview map or the location icon is black you are using a fixed location indicated by the small cross at the centre of the map.

Tap this button to toggle modes.

[larsbromley]

No, I am not in manual mode, the icon is blue. Another thing I noticed: the location is being reported accurately on the map, ie the flashing blue ring is where it should be. However, the AuGeo 'red view field' will remain stuck in a previous location. As an aside, the red view field 'shakes' even if the phone is still, and if I am seeing popups in the AR screen (ie not the map screen), they also shake a lot. The visual effect is relatively annoying. Not sure if the issues are related.

[spatialdude]

@larsbromley We're preparing an update which includes a lot of improvements since the first release.

Would you be interested in trying out the Android version of the update before we submit it to Google Play?

[larsbromley]

Hello, very sorry for missing this. Can I still try the update?

[spatialdude]

@larsbromley We've identified the problem with cached locations on Android and will be updating AuGeo accordingly.

[larsbromley]

Great! Congratulations...

…

On Wed, Jul 26, 2017 at 1:43 AM, Elvin Slavik ***@***.***> wrote: @larsbromley <https://github.com/larsbromley> We've identified the problem with cached locations on Android and will be updating AuGeo accordingly. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABFwlEmox4aTjW_lRARCYGNVgYm7Cyo4ks5sRn2IgaJpZM4NhS-W> .

[JohnHasthorpe]

This has been resolved - closing this issue