Harry's GPS Suite Forum

I have a samsung Galaxy S4, and sky pro gps 160. The gps works for trackdays, and when I go to the GPS page it says the accuracy is 2ft.

When I try to set the start point for the course it says "no gps move to an area with a clear view of the sky or adjust you settings"

The only way it works is if I turn off the bluetooth, set the start and end points using the phone's internal gps, then turn it back on. Except that the phone's gps is so bad that it saves the start and end points are 30-50ft from where they should be.

Any ideas?

You are carrying the XGPS with you? When looking into GPS View, please make sure you have the current GPS fix selected. There is a control in the top allowing you to switch to older fixes (the one with fastest speed ever, etc).

Harry

I set the gps to current and it still shows 3ft accuracy, I have the gps with me, it still wont let me define start point. It says there is no gps signal, but Without changing anything I walk to where the gps thinks the start point(that I set with the phone GPS) is and it will ask me to "stage".
Any ideas?

I've also tried different gps providers and it still doesn't work.

So I tried it through sensor list instead of the gps app, works now. Ha, only took me 4 months of playing with the app to figure it out.
Thanks for a great app.

First off, sorry for the approval requirement for your posts. This is an issue with the new forum version. Future posts should go through directly.

The message you are getting is "No GPS position available currently. Please check your device's settings (Android Settings ‣ Personal ‣ Location access) and move to a spot with a good view to the sky."?

In case this is the message, there seems to be something wrong with validity checking of the GPS positions delivered by the XGPS. It is a bit strange because the same function is used all over the place to verify GPS fixes and would introduce tons of other issues when always behaving like this... I tried the AX assistant with a Nexus 6 and my XGPS160 a minute ago and can't reproduce the problem. I doubt the issue is related to the smartphone model. It is either an issue with other apps accessing your Dual (1), or the Dual configuration (2) itself.

To check (1), please make sure you have not installed any helper app. This is the most common issue with BT GPS devices on Android. Android does not come with integration of GPS devices on OS level like iOS. Instead, manufacturers provide these helper apps which allow the use of an external GPS for arbitrary GPS apps. LapTimer is different here and access the external GPS directly to get higher precision and work around helper app issues. To fix this, please uninstall any helper apps or a Dual app you may have installed too. Try again afterwards.

In case it isn't (1), we need to check what is going on within the app. As I am fully in v20 development currently, you need to join the v20 beta in case you want me to have a look into it. The procedure to join is described here: viewtopic.php?f=2&t=3471. Once you have joined, I will add some extra logging to the app and run some tests with your device.

- Harry