Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On Android 12 GPS logger messes up with Trimble Mobile Manager #1133

Open
teverth opened this issue Apr 5, 2024 · 1 comment
Open

On Android 12 GPS logger messes up with Trimble Mobile Manager #1133

teverth opened this issue Apr 5, 2024 · 1 comment

Comments

@teverth
Copy link

teverth commented Apr 5, 2024

I have been using GPS Logger successfully on Android 14 in combination with the Trimble Mobile Manager app to log points using the precision location data provided via the Spoof GPS service coming from the Trimble precision GNSS system with 1 cm accuracy.
However, when I try to use the very same functionality on an Android Phone running Android 12, GPS Logger messes up. For a few seconds, it displays the correct information. However then, the data displayed in GPS Logger fluctuate wildly and randomly with the accuracy going from 0.01 m to 450m and the other data, such as elevation or position.
Not only that, when GPS logger is running the precision information in the Trimble Mobile Manager app becomes unreliable as well. So not only does GPS Logger not work anymore using the Spoof GPS signal, it also messes up the function of Mobile Manager itself!

@mendhak
Copy link
Owner

mendhak commented Apr 6, 2024

So it's good to hear that it works well enough on Android 14 — at least that proves it's not entirely broken 😆

On Android 12, what are the performance settings. I did make a change very recently that would log passive locations only if it matched the other location listeners (eg network or satellite). If neither network nor satellite are selected, then all passive locations would be evaluated. Have a look to see if any of the performance settings aren't the same between the A12 and A14 installations.

I've not seen that behaviour before, except on emulators where two different sources of locations are coming in and both are being evaluated. So I'm wondering if there's something like that happening, one from Trimble and one from the device itself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants