Harry's GPS Suite Forum

I have one log from my prior track day that showed 10Hz data, all the others were 1Hz. I cannot be 100% sure, but I don't think I could achieve 10Hz with anything but the QStarz.

The Insecure connection did not help.

Hi Harry,

I have the same problem.

I was on the track last week-end, and my 818XT could not stay connected to my phone.
It always swapping between internal and external GPS sensor. (i use GPS view to verify)
I had to recording with internal sensor (1hz) to get some data.

I regularly use the software, and it is the first time that this problem appear.

I thinks this problem is linked with the last version upgrade.
My external sensor is working fine with other software.

This is my confuguration :

SOFTWARE
Product: Harry's LapTimer (DVP)
Edition: Grand Prix Edition - Features: Petrolhead Edition, Grand Prix Edition
Version: v19.0.27 - Nov 7 2015 23:10:02

SYSTEM
Manufacturer: WIKO - Model: RIDGE 4G
OS: 5.0.2 (SDK 21) - Databases: G65L66V6CP00
Screen: xhdpi, 720x1184, normal
Sensor: Internal
Available Storage: 1,32 Go internal / 8,60 Go SD card
SD cards: /storage/sdcard1/Android/data/com.harrys.laptimer/files/Movies
/storage/emulated/legacy/Movies
/storage/emulated/0/Android/data/com.harrys.laptimer/files/Movies
RAM: 1,87 Go - CPU cores: 4
Dalvik Heap: 13,83 Mo/19,72 Mo/128 Mo
Native Heap: 9,12 Mo
UDID: 00000000-48c0-fb9b-e917-0a36120da85f
Product: l5510

The latest version of LapTimer add two new features you may check:

1) Sensor connection time is limited to a few minutes. Afterwards, no new connections are made. Exception: the app is sent to background and forwarded again, or an accessory has been connected successfully and lost connection. This will restart the connection timeout. It is possible to change the timeout in LapTimer's Expert Settings. I doubt this item is related to one of the above issues, I recommend to use standard settings to benefit from power saved.
2) Support for BT LE sensors (namely Kiwi3 and custom connections). I have seen a phone's BT stack crash after a longer time in BT LE discovery mode. Once this happens, the system service might be down / limited until the device is restarted. Issues like this are highly dependent on smartphone model / make and Android version. To test if BT LE operation disturbed standard BT operation, please turn BT LE sensors off in LapTimer's Expert Settings. In case you see a change, please report here. Thanks.

- Harry

Harry wrote:The latest version of LapTimer add two new features you may check:

1) Sensor connection time is limited to a few minutes. Afterwards, no new connections are made. Exception: the app is sent to background and forwarded again, or an accessory has been connected successfully and lost connection. This will restart the connection timeout. It is possible to change the timeout in LapTimer's Expert Settings. I doubt this item is related to one of the above issues, I recommend to use standard settings to benefit from power saved.
2) Support for BT LE sensors (namely Kiwi3 and custom connections). I have seen a phone's BT stack crash after a longer time in BT LE discovery mode. Once this happens, the system service might be down / limited until the device is restarted. Issues like this are highly dependent on smartphone model / make and Android version. To test if BT LE operation disturbed standard BT operation, please turn BT LE sensors off in LapTimer's Expert Settings. In case you see a change, please report here. Thanks.

- Harry

I done some tests :

For the 1) : i think it is the problem, because, my app alway return on the Start Screen when bluetooth is active and sensor add in HLT. So i deduce " the app is sent to background and forwarded again". I change the timer 15min to 120min but there is no difference.

On the track past week-end i was on 6 November version, no return to the main Screen.

Now my version is 7 November 19.0.27

For the 2 ) :

(default)
Force insecure BT Connection : unchecked
Use WIFI sensors : checked
Use Bluetooth LE Sensors : checked
Connection Timout : 15

No connection to external sensor and always return to main screen

Force insecure BT Connection : unchecked
Use WIFI sensors : checked
Use Bluetooth LE Sensors : checked
Connection Timout : 120

No connection to external sensor and always return to main screen

Force insecure BT Connection : checked
Use WIFI sensors : checked
Use Bluetooth LE Sensors : checked
Connection Timout : 120

No connection to external sensor and always return to main screen

Force insecure BT Connection : unchecked
Use WIFI sensors : checked
Use Bluetooth LE Sensors : unchecked
Connection Timout : 120

No connection to external sensor and always return to main screen

With the internal sensor : no problems it is working

Help ?

In case LapTimer is going back to the startup screen by itself, the app actually crashed. Please restart the device to work around a probably corrupted BT stack. The named changes were introduced in the beginning of October, the November versions had changed on the front end only, no changes in low level functions.

Harry

And what about a failure to actually connect to the Qstarz within HLT? HLT is never going to the background, never crashing.

Not a known issue. I connected a 818XT yesterday and had it active for 2 hours without a disconnect...

You may recheck the basics: unpair the device, make sure no other device is accessing the Qstarz, remove the sensor entry in LapTimer, reboot the smartphone. Remove / kill any other app accessing It (helpers in particular).

Harry

Harry wrote:In case LapTimer is going back to the startup screen by itself, the app actually crashed. Please restart the device to work around a probably corrupted BT stack. The named changes were introduced in the beginning of October, the November versions had changed on the front end only, no changes in low level functions.

Harry

My last track-day use was on July (it was working fine), no use between July and November.

I already try to restart, my phone , my app , but no changes.
When harry's not working, i start an other app, and it is working, so the bluetooth stack is not HS.

What do you mean by "helpers" ?

Can @mail me an oldest version APK to test that the problem come from the latest version ?

dydy77 wrote: My last track-day use was on July (it was working fine), no use between July and November.

I already try to restart, my phone , my app , but no changes.
When harry's not working, i start an other app, and it is working, so the bluetooth stack is not HS.

What do you mean by "helpers" ?

Can @mail me an oldest version APK to test that the problem come from the latest version ?

Downgrading to an older version will not change anything (and is not supported), you need to check your configuration. I understand once a theory the app version causes the issue has developed in your mind it is hard to go the other path, but you really need to.

There are several possible scenarios in case you see another app using the external GPS and LapTimer not using it:

#1 Other app uses Android's location service and you have installed a helper app. These helper apps run in background and connect to the external GPS and feeds data into Android's location service. All apps can access this data afterwards and in parallel. In case you want to keep this scenario, remove any QStarz sensor added to LapTimer's Sensor List and LapTimer will use the Android location service just like the other app. NB: LapTimer will display it is connected to your phone GPS - not aware the data is actually delivered by the external GPS. This is not the recommended solution because the helper app adds additional latency, may introduce addition issues and is simply one more element that may brake or be misconfigured.
#2 Other app accesses the QStarz directly and is proper configured. If that's true, make sure the other app is killed before starting LapTimer. Otherwise both apps will access a unsharable resource. Remove your existing QStarz entry from Sensor List and follow instructions in viewtopic.php?f=39&t=2463 precisely to add it again.

I know this is cumbersome, but it is the way Android handles GPS resources. Pretty much like in the old Windows world where the end user needed (and still needs) to handle resources and drivers.

- Harry