Making a route recalculate in the Android app

The weather was (relatively) clement the other day so I took my bike out for a quick pilgrimage to two bike stores. I also saw this as a good occasion to "get the feel" for riding with the c.t app as my primary navigation tool. I created a route to the first store in the c.t web tool, synced it over to my Android phone and set out. The route looked fine and after my GPS position had been found (always takes a bit of time in the "city canyons" around here) I got rolling. But after a while I decided to test what would happen if I deviated from the planned route, so I overshot a turn and entered a parallel street to where I was supposed to be. I expected the navigation to recalculate and give me an updated route after I'd been off-track for a while, but no. I could see the planned route a city block (about 100 m) to my left of the "you are here" dot and that was it.

Since the first store didn't have what I wanted, I then set off for the second one, right across town to the other side. This time I entered the address manually in the Android app and it, too, gave a good route proposal, but of course, I didn't stick to it. Same thing happened - I could see the calculated route off to my left, a lot further away this time, but nothing happened, no recalculation/update.

Now, based on my previous experiences with Garmin navigators on bikes as well as with Google Maps and Waze in cars, I've grown accustomed to the navigation software detecting my going too far off a proposed route and recalculating it, but this did not seem to happen here. I can see that there's some logic to the YAFIYGI ("You Asked For It - You Got It") mind set (I'm old enough to have worked with text-processing systems before WYSIWYG editors) and I could probably learn to live with it, IF there's a "recalculate" button somewhere that I can hit to manually force it if, say, something has happened so a large chunk of my planned route is inaccessible. Flooding, avalanches, terrorist attacks, whatever. Of course I realize that this can be done in multiple ways. Nearest route to the next via point or the destination. Nearest route to the nearest point on the original one. This is all "prior art" (Garmin, Google and Waze all do it. I haven't tried it on Osmand yet) so it's definitely doable. And I can't really think I'm the only one this has happened to, so, what am I missing?

RFE: Make via point note text visible in Android app

The title is really self-explanatory. I'd find it very helpful if it were possible to see the note text from a via point in the Android app. To me, that would serve as a reminder exactly why I made that note, so as an example it could be the closest point to some food store where I might consider to shop, if I happen to be passing there at a convenient time. For extra bells and whistles, a checkbox in the note editing dialog could serve as an indicator whether or not this is something I'd like to pop up on my screen as I approach the via point (the note MIGHT be just for my route planning purposes and irrelevant when I'm on the road).

Edit: I just noticed that this overlaps with a comment from Hobbes on my "Personal POI" request. See? This is definitely something we need! ;-)

Goodbye yellow brick road?

In Germany and the Netherlands it is common practice to use bricks or tiles on some streets and cycle paths as a means to calm down traffic and make a distinction between "country" and "town". I've noticed that in c.t routes such stretches get highlighted in green if my preference is set to "any", which I thought would indicate that they're unpaved, but if I switch my preference to paved only, the route remains the same but the green color goes away. And a couple of looks at samples in Google streetview shows that this happens exactly on stretches that have tiles or bricks.

Now, I have no serious objection to this and I certainly don't mind riding on tiles, but I *do* dislike long stretches of gravel paths (or at least want to look at them in advance to assure myself that they're not too loose) so I'd really like if it were possible to somehow tell the difference between unpaved (gravel/dirt/sand) and tiles/bricks. I'm assuming this is all info that comes out of OSM so how is it classified there? Do they lump together tiles, bricks, gravel, dirt and sand as all the same? That would seem rather crude to me.

Edit: and what about cobbles?

RFE: Add my own personal POIs or shortlist items

(RFE stands for Request For Enhancement and is what we used to ask our customers to submit when they had ideas about new features they wanted added to our software, back in the days when I worked as technical software sales support.)

I think that the ability to somehow save points that I find "interesting" for one reason or other would be a great enhancement to CT. The shortlist is good but right now it only lets me save points that "you" (Richard & C:o) know about and only lodging places. I'd like the ability to save my own interesting sights, eating places, friends' addresses...The list goes on. Primarily, I'd only expect mine to be visible to me. Being able to share them with others would be nice but could lead down the slippery slope of requiring "you" to validate them and that would mean more administrative work for you, so it's best left as "out of scope" (as we used to say when customers wanted features that we felt didn't fit with the intended use of the product).

It needn't be fancy. A small flag symbol, pair of long/lat coordinates and a name, would be enough for me. Some sort of "category" tag (lodging, food, whatever, possibly just strings that I choose myself) counts as a "nice to have" function and in a pinch I could just prefix the names with something like "Eat_", "Sleep_", "See_" so this has much lower priority. And unlike the lists of campgrounds and hotels "you" maintain (and which must contain thousands and thousands of entries) "my" list would be orders of magnitude smaller so I don't think it would put much load on your servers.

Best practices for multi-day tours?

So, I'm planning for a tour next year, about three weeks (~1500 km) in the Netherlands, Germany and a bit of Belgium. And right now I'm trying to figure the best way to use c.t for my planning and navigation. I've noticed that if I plan a multi-day trip in the web version of c.t, the black "overnight stay" markers don't make it to the Android app, so I'm led to believe that the recommended way is to let the web service split the route into separate days and then open them on the phone, on a day-by-day basis. Is this a correct interpretation of the designer's intentions?

And if I change my mind about where to go or when to sleep, will I be better off adjusting the "master route" and splitting it again?

What if, in some area where campgrounds (or wild camping spots) are plentiful and rarely far apart, I just follow the route outline without any pre-determined places to stay overnight, will the c.t phone app be able to recognize next day where I am and understand that I want to resume the tour from this location? Even if I've, say, made a multiday stopover with sightseeing at some nice place along the way?