TrekBuddy

[gabor]

I am opening this topic either to make people avoid this configuration or to find a cure to this problem.

I am testing trekbuddy on a se k750i and a qstarz bt800 pro bluetooth gps receiver with Nemerix chipset (with a very long operation time). It is strange that after a while with any j2me application the bluetooth connection is stopped (gps receiver indicates bluetooth activity, but phone shows no sign of it. Luckily trekbuddy reestablishes the connection immediately (very nice feature:)!) but of course it means a loss in the recorded track.

The trekbuddy info shows:
ProviderStatus:End of stream; syncs=2; mismatches=0
ProviderError ai: javax.bluetooth.BluetoothConnectionException:security block

Same problems does not occur with a SirfStarIII chipset receiver and there is no connection loss with Qstarz Nemerix and PDA combination.

I have read in other forums that sometimes it is useful to close a bluetooth connection after acquiring data so as not to allow the phone's bluetooth buffer to be overrun.

I have also tried a firmware upgrade but without any success.

Thanks for your comments, suggestions in advance.

[kruch]

[gabor]

by loss I meant that this losing of bt connection and reconnection last time were happening so frequently that I lost recording of 1 km distance of a trip. In these cases emtpy <trkseq>-s are to be found in the track recording (gpx). This is not a problem of trekbuddy (possibly se-s bluetooth manager's buffer were overloaded), and in the meantime I replaced my receiver with a sirfstarIII model and it works all right with it.

[Phren]

I also experience this problem with a K750i in combination with a Nemerix-chipset based GPS receiver.
After some testing i found that the security block error notice only occurs when the phone has an active BT connection to my PC while accessing the BT GPS receiver.

The error message that i got is:

ProviderStatusEnd of stream, syncs=0; mismatches=0
ProviderError ai: java.lang.NumberFormatException: Not a digit: -

It looks like a loss of communication between the phone and GPS receiver but i'm not sure if it's caused by the NumberFormatException or that this exception occurs after the lost connection.

I have been able to get a few good routes with the 0.9.5 RC2 version, but the last couple of days i get constant disconnects. Not sure if its a version problem though as i rolled back to RC2 and still experienced the problem...

After running a NMEA log with the diagnostic tool of my receiver for some minutes the only '-' character i could find was for the altidtude. Negative altitudes are quite common when you live in the Netherlands

[kruch]