427 Mile Test Ride with 4.0.4-215

[Dave J 0]

Big ride today with version 215 on my Google Pixwl 6 Pro phone running Android 14 Beta 5.2.
Tracklog and route

Fifteen hours (427 miles / 687 km) of non-stop use and no grey screen and no crashes - multiple stops and resumes and also with auto tracking. Awesome work @Corjan-Meijerink and the new features work brilliantly. The only issue that persists is when resuming navigation when in poor reception areas (sometimes):

• At waypoint 11 in the route, the navigation tried to start but the app seemed to get paused with the spinning icon not yielding anything although I could see the route in the background. Not able to select offline so had to close and restart with a successful resume (signal was 1 bar of H+). Further 'stop navigation' testing whilst stopped at the same location caused no problems.
• At waypoint 29, there was again a very weak signal as before but I was able to select offline after I received a 'something went wrong' warning.

Why does the app not automatically go into offline in these situations? Offline when going from strong to weak whilst navigating works a charm but not, it would appear, when resuming navigation in a weak phone signal area. I know that I am not the only one seeing this.

Other observations:

1. Mentioned in another thread about the logic of audio prompts for when selecting 1-4. I am currently using 3 to get the 500m prompt but would ideally just like 2 prompts at 500m and turn etc.
2. Detailed lane assistance is great but it is hard to read the signs in the picture given the size of text.
3. I know power consumption is ongoing but the use of simple maps does ease the problem slightly. Wireless charging is better but I can full charge with wired charging. That said, TomTom Go app will full charge on wireless as a comparison.
4. Auto skip of waypoints did not work as well today with several between waypoints between 16 and 28 having to be manually skipped when auto skip should have worked. Not sure why and will do some more testing.
5. Position lag is still there (about 4 seconds) unless I run Flitsmeister in the background. Curiously, TomTom Go is also laggy without Flitsmeister running in the background using this Android 14 Beta which was not apparent with Android 13.

Just want say what a great update this has been for me and I love the new features. Brilliant, brilliant work

[Corjan Meijerink]

@Dave-J-0 Thanks so much for the detailed feedback!

About the poor reception, that is a difficult one!
The difference between poor reception and no reception is quite big.
We now do a very quick and easy "do I have reception" test which then yields a "yes". However, when then requiring the internet to do a complex recalculation, the reception might be a bit less (while still there) and then it won't work. I think we will need to adjust the internet check test to something more complex to indicate a minimum required internet speed or something like that

Over to the rest:

1. Changed this in the upcoming release version based on the beta feedback!
2. Made some minor adjustments but we struggled with this too. Making the image larger, hides crucial information which is undesirable too. The most important part, the big blue arrows indicating which lanes to take, are quite well visible. I am pretty certain we will tune this after more feedback.
3. Working on it with HERE.
4. Auto skipping has quite some complex logic and is also configured to not accidentally start skipping waypoints while not wanted to. We prefer the user needing to stop to manually skip rather than having to stop to correct accidentally skipped waypoints.
5. Very interesting that TomTom Go has the same issue!

Brilliant, brilliant work

Thanks