Yesterday I made my first attempt at using c.t as my primary navigation support. It was along roads that I already knew well and I also had my old Garmin on, for comparison, but I wanted to give c.t a chance.
It worked beautifully until lunch but by then the phone's battery was running low so I turned off c.t, hung around and ate well for an hour before resuming my ride. And c.t did NOT play well after that! It cheerfully chimed "you have arrived" and stopped when in reality I still had some 25 km to go. I tried it several times and always got the same result. It showed my correct location on the map and the route was there but still maintained that "you have arrived".
This cuts into the usefulness of c.t significantly. There are multiple scenarios where one might want to stop before the planned end of a route and then resume it later.
So, am I doing something wrong? Is there some way to tell the c.t app that I'm still on the road and would like to pick it up from here and continue?
Comments
Can you say (a) what the route was (e.g. link to it and make sure it’s public not private), (b) where you were when you were resuming?
Thanks Richard.
I've moved the route to my "no folder" folder and made it public. It's the only route there, "hem fr landet".
I had lunch at the "TM Bagarstuga" marker, some 38 km in. My phone's battery was running low so I closed down the c.t app while recharging, maybe that was the issue?
Thanks! Tricky one to track down – I must have tried to reproduce it 100 times now and have only been able to do so twice. So there’s something there but I’m not sure what it is.
For the time being I’ve put a little extra check to guard against this in the next version which is currently sitting with Google for review (but they’re being slow at the moment).
Two things I might suggest. One is to close the route and reopen it if this happens again. The other is that I think it might be connected with accidentally tapping "Extend route" and causing the route to double back on itself to the current location – worth checking that this hasn’t happened.
The new version is now live in the Play Store – oddly this version took a few minutes to go through whereas the previous one was sitting there for a week!
Thanks Richard! You're spoiling us with such good work.