It's a great little app (i've got v1.78). I'm still fiddling with it, trying to learn all the tricks, but I've noticed a couple of quirks.
1
It's not all that accurate - sometimes when uploaded to Google Maps a few points are out by 100-200 metres - it has me suddenly flying across the river then back again on my ride home from work. Is this just a limitation of the
N95's inbuilt GPS receiver? The only thing is, I've noticed
that Nokia Maps (the built in app that came with V30 firmware) appears to be more accurate - i.e. when I have it running and zoom right in, the little red dot always stays on the road I am actually on.
2. Secondly - yesterday when riding home,
it only recorded 2.5km out of the 9km ride, it just stopped tracking about 1/4 of the way home, resulting in a very slow average speed. I had the phone mounted on the handlebars and open to the sky. The bizarre thing is, it cannot be explained by the GPS receiver dropping the satellite link, as I had Nokia Maps on the entire ride home and it never once dropped the connection - the little red dot faithfully followed the map the whole way.
Note: It has been suggested elsewhere on this forum that this problem can be avoided if you set your default access point to NONE prior to running a tracker (I had it set to my home WiFi point) - you just have to remember to switch back to none after uploading
Anyone experience something similar?
Apparently the next version will have some limited mapping integration - sounds good!
A few questions on the live tracker (where people can go to the Nokia website and see where you are in real time)
- presumably you have to be in 3g range and have a mobile access point switched on?
- Does this incur a lot of kilobytes of data upload/download? My carrier charges AU$4 per megabyte so I'm extremely unlikely to use this feature, but I'm just curious.
- Also, if you have an access point set, won't this cause issue no. 2 above to re-occur?