Comments for Hubrisware

Comment on RideTrac 1.0.4 Released by ben

ben — Sun, 15 Mar 2009 19:06:25 +0000

Hi, Have a problem exporting a file (to KML) from G1/Android, looks like software loops, sits on the “exporting…” dialog. Can provide db file if you like, may be a bug.
Otherwise nice software.

Comment on RideTrac 1.0.2 Released by dave

dave — Sat, 07 Feb 2009 16:16:55 +0000

@arnd
Did version 1.0.1 work for you?

Comment on RideTrac 1.0.2 Released by arnd

arnd — Sat, 07 Feb 2009 11:15:47 +0000

Version 1.0.2 always crashes on startup on my German G1

Comment on A Note on Accuracy by dave

dave — Fri, 06 Feb 2009 18:58:28 +0000

FYI: Version 1.0.2 is now released and fixes this problem.

Comment on RideTrac 1.0.1 Update Released by dave

dave — Fri, 06 Feb 2009 18:57:24 +0000

Version 1.0.2 is now released and fixes this problem.

Comment on A Note on Accuracy by Hubrisware » RideTrac 1.0.2 Released

Hubrisware » RideTrac 1.0.2 Released — Fri, 06 Feb 2009 18:47:17 +0000

[...] users were reporting wildly inaccurate statistics displayed in RideTrac (see A Note on Accuracy). These problems were tracked down to phones that had both GPS and Network Location turned on at [...]

Comment on RideTrac 1.0.1 Update Released by dave

dave — Thu, 05 Feb 2009 07:33:05 +0000

Thanks to some help from guido I now understand the nature of this problem. It is related to the local time zone formatting for European phones. The code is fine for US style time zone formatting, but not for some others. When it tries the program to export a track it uses the date of the ride as the name of the exported file. For certain kinds of date formatting this generates an error. RideTrac as I originally coded it assumed the problem was an off-line sdcard. I now see this was a bad assumption.

I am working on a fix right now. Hopefully we will have an update this weekend which corrects this problem as well as the speed problem reported on the other post and a few new features that have been requested.

Comment on RideTrac 1.0.1 Update Released by pellix

pellix — Thu, 05 Feb 2009 07:23:49 +0000

I have this problem always, with or without the usb cable attached.

Thank you.

Comment on A Note on Accuracy by dave

dave — Wed, 04 Feb 2009 02:48:02 +0000

@Adam
Thanks for pointing this out. I verified it myself and you are correct. I am working on the next upgrade which addresses this issue. Here is the situation in a nutshell:

RideTrac 1.0.1 ignores what the location provider is (GPS, cell network, etc) and simply assumes that all providers are equal and consistent. Now I know this isn’t true. The next version of RideTrac only uses locations from a single, “best available” provider at a time. This means if you have both GPS and wireless network location ON and both are in range, then GPS will be used and wireless ignored. However, if you lose GPS signal for some reason but still have wireless, then RideTrac will automatically use wireless. I’m testing this out now and it seems to be working. Look for a new version this weekend addressing this plus a few other issues that have cropped up.

Comment on A Note on Accuracy by Adam

Adam — Tue, 03 Feb 2009 18:38:55 +0000

@dave
The “use wireless networks” setting allows for rough location estimation based on the known locations of cell towers within the phone’s range. Leaving this on while RideTrac is running caused, at least on my phone, the route to jump all over the place.