Test results of release Pro 1.6.0:
- GPS elevation error: the GPS filter that I understand was introduced in version 1.6.0 completely screwed up the altitude. I ran Locus, GPS Status, and MyTracks at the same time to verify the results. I parked the car at elevation 890m according to MyTracks. GPS Status showed 840m. Locus Pro 1.6.0 reported 187m. From the parking lot I hiked to the top of the top of the mountain. MyTracks reported 1700m, GPS Status reported 1650m, Locus reported 341m. On my way down I switched to Locus Free 1.5.1. I checked the reported elevation at several points: Locus Free 1.5.1 and MyTracks always reported exactly the same elevation, and both consistently 50m higher than GPS Status. I know that there is a Settings/GPS/"Adjust Altitude" in Locus that I can use for calibration, so I use that now.
- Phone hangs while recording: earlier on this trip I used Pro 22.214.171.124 a lot at the same time as Co-Pilot. I had one incidence of hangs, but I have no proof that is because of Locus. On my hiking up to the mountain today (see above), I had no incidences of hang even though Pro 1.6.0 was running at the same time as MyTracks. However, on my way down with Free 1.5.1 and MyTracks, the phone hang completely 3 times within one hour and I had to take out the battery. Question: are there any changes from 1.5.1 to 1.6.0 that could explain this? Having two GPS programs running at the same time, can that cause any trouble?
- Sorting tracks by creation date doesn't apply to MyTracks: the sorting works perfectly for Locus tracks (I have reported this before). However MyTracks tracks are always listed with the newest at the bottom, and the Reverse command has no effect on those.