After long last, I have a bit of good news It's not much at this point and I don't want to raise your hopes too high for a quick fix, but I thought I'd share this anyway as it was starting to look quite grim.
I've been forwarding your feedback about this issue to the product team and they've now come back to me with something more promising. The investigations into this issue are bearing fruit and a potential solution is in sight. It's still too early to say anything further about it, e.g. regarding the nature or time table. However, I wanted to post this to ensure you that the issue is being investigated and progress has been made.
Regarding my troubleshooting advise above, we can never guarantee a troubleshooting step will solve any particular issue. We can only suggest steps with some confidence based on how effective we've seen the steps to be for a particular issue. That's why it's called troubleshooting
We've just released a new v17.200 software update. Although it doesn't specifically address this issue, we'd like to hear from you whether you notice a difference or not.
Too bad they are not willing to publish what they fixed in the latest release. It is a long list they said. So there is a list. Someone at tomtom had to write the bug fix list. The service is going worst. Now we have to found out by ourselves if our problems have been solved.
Publish the long list. A simple copy paste action.
Unfortunately, I don't have further news at this point. I'll post back here as soon as I have news to share.