Yellow Jerseys in San Diego
Off-topic from RideTrac, but I thought I’d post a picture I took today from Stage 8 of the Tour of California. Its not everyday the world’s best riders finish a major race in your town.
Off-topic from RideTrac, but I thought I’d post a picture I took today from Stage 8 of the Tour of California. Its not everyday the world’s best riders finish a major race in your town.
Version 1.0.4 adds customized exports in the form of CSV (comma separated value) files. These can be easily imported into spreadsheets like Microsoft Excel. Once in a spreadsheet you can perform custom calculations, graphing, etc.
You need to create a custom export format first before using one:
You can create additional custom exports as well as view/edit/delete existing ones by selecting them drop the drop-down menu.
If you have one or more custom exports defined, they will appear as additional Export options along with GPX and KML.
Exported files will have a .csv extension.
This version also adds a progress indicator that displays during export so you know whats going on during a long export. It also adds release notes under Help->Release Notes.
1.0.3 is a maintenance release that fixes a problem experienced by some users with non-English locale G1 phones where RideTrac 1.0.2 would crash on start-up. There are no new features in 1.0.3 other than this fix.
By coincidence I received the new RC33 OTA update for my G1 today in the middle of debugging this problem and I can verify that RideTrac runs fine with it.
Sorry for any inconvienence this bug caused non-US users.
Note: In releasing this emergency fix I inadvertantly put a version out there for a bit that was titled RideTrac 1.0.3 (beta). This was a mistake so as soon as I saw the problem I replaced it with one titled RideTrac 1.0.3. If you happened to update during the time the one with the beta word was out there you may have received an extra update notification in the My Downloads part of the Market (if you have RC33 installed). Sorry for the double update, all the second one does is fix the title.
Some users have reported problems with version 1.0.2 crashing on start-up. We are working on a fix for this now, but if you wish to revert back to version 1.0.1 until a permanent fix is available you can download it by right clicking here, saving the file to your computer, and re-installing it with ApkInstaller (available from the Android Market).
Sorry for the inconvenience. We hope to have a new version ready shortly which corrects this issue.
Note: Do not revert back to 1.0.1 if your 1.0.2 version is working correctly! For most users version 1.0.2 is working well.
Version 1.0.2 adds a few new capabilities and fixes two known problems. All of these have been requested by RideTrac users:
Explanation of New “Keep Map Centered” Setting in 1.0.2
This new setting forces the currently reported location to always stay at the center of the screen whenever GPS is turned on (whether you are tracking or not). A consequence of turning this setting on is that you will be unable to roam off of the current location (for example to look ahead on the map) for very long while GPS is on. Whenever a new fix is received the map will jump back to keep you at the center.
The default behavior is the same as in previous RideTrac versions:
The location marker moves on a fixed map until its about to move off-screen and then re-centers the map about your current location. It does this unless you have manually moved the marker off-screen yourself, in which case you can hit the re-center button to get your location back on-screen.
Explanation of Export Problem Corrected in 1.0.2
Some users (all in Europe) were reporting that track export would fail and RideTrac displayed a message stating that the sdcard was unavailable. It did this even though sdcard access was actually fine. This problem was tracked down to an issue in converting date strings that used the GMT+01:00 type notation for the time zone into the name of the exported file. Thanks to two of our users in Europe for helping me pinpoint the actual problem here.
Explanation of Inaccuracy Problem Corrected in 1.0.2
Some 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 the same time. RideTrac would receive location fixes from both providers and not distinguish between them. GPS is generally much more accurate than cell tower triangulation, so if two fixes came in sequence, one from GPS and one from the network, if the two locations were far from each other RideTrac could think you were moving at light-speed type rates and report bad statistics. This has been fixed so RideTrac now only utilizes the most accurate provider available at any given time and ignores all others.