Updated beta v4.1.2 (305)

[Walter Coady]

I had about 10 crashes over the weekend and tried to submit comments when it happened, however, kind of hard to do while riding.

[Corjan Meijerink]

@Edwin_M agree! Out of my power pushing HERE

[Edwin_M]

@Corjan-Meijerink when changing apps on android for example to take a picture. The pointer moves to the upper 3rd of the screen in portrait

[Edwin_M]

@Corjan-Meijerink roundabout issue is solved

[Corjan Meijerink]

@Edwin_M it is not Seems related to motorcycle mode. Got confirmation that HERE reproduced the issue so hopefully solved soon now.

[Edwin_M]

@Corjan-Meijerink agreed..i had the issue again today
Also had some waypoint skips when i was very close to the waypoint but not yet there.

[Tom Johann]

Yesterday I tested again iOS v4.1.2 (305) at a 230 km ride.
As I already said all in all very good.
I identified 2 reamaining issues:

1. HERE Roundabout exit 1
   In most Roundabouts the App tells me to exit the Roundabout at exit 1 even if 2, 3, or 4 would be the right exit.
   @Corjan-Meijerink mentioned already that this has to be fixed by HERE.

2. Skiping of waypoints
   yesterday it skipped one or two times even if I followed the proposed route without any reason.

[Tom Johann]

@Corjan-Meijerink
Hi Corjan, I just read in the Announcements of MyRoute-app (NOT Beta!) that the Nearby fuel stations function is only working for straight A to B navigation but NOT for curvy A to B navigation as curvy navigation is implemented as TRACK while straight navigation is implemented as ROUTE.

Wouldn't it be possible to also implement it for TRACKs (curvy) as tracks are routes with many many waypoints internally. Isn't this right?

I am just asking because I think it is currently hard to understand for users that there is a difference for straight and curvy routes or roundtrips

[Corjan Meijerink]

@Tom-Johann good point, however slightly more complicated. Track navigation (curvy / roundtrip) have no waypoints but thousands of coordinates. Therefore internally a waypoint as stop cannot be added easily

We would be able to display the fuel station / remaining distance but then you can’t add it. Would that me sufficient / better?

[Jörgen]

@Corjan-Meijerink said in Updated beta v4.1.2 (305):

display the fuel station / remaining distance but then you can’t add it. Would that me sufficient / better?

That would be a good compromise to start with. To be honest, I even think that would be quite good. Yesterday I drove to petrol stations just like that.

[Stefan Hummelink]

@Corjan-Meijerink said in Updated beta v4.1.2 (305):

Therefore internally a waypoint as stop cannot be added easily

And how about automatically ending the track navigation at the petrol station if 'added' by the user? Instead of trying to insert the petrol station as a 'via' point, simply make it the final destination of the track artificially. Afterwards the track navigation can be resumed manually from that point onwards, right? I feel like this would be what most people would accept as absolutely fine. The tracklog is still active, and the resume option will recalculate from the current location forward, win win imho .

[Stefan Hummelink]

This post is deleted!

[RetiredWingMan]

Yesterday I was out for a full day ride. MRA worked perfectly with no issues. Tried both online and offline. At stops I left MRA running in the background until we left.
Today, different story today. I deviated from the route and shortly after MRA skipped a wp. Shortly after I noticed that it skipped all wp's to the final destination! I reset to the next wp on my route. Shortly after it skipped a wp and I hit reset on the skip message. A little later again all wp's were skipped to the final destination and the route was modified. This went on several times. I eventually gave up and turned off autoskip. This was a very frustrating drive. I was not familiar with the route and trying to deal with MRA was a serious distraction.

[Corjan Meijerink]

@RetiredWingMan Could you share the route and indicate where you were when it decided to skip everything?

[Tom Johann]

@Corjan-Meijerink
Hey Corjan, ok, understood.
Your proposal to only display the fuel stations on the track would be a good alternative.
Maybe with the option to navigate to the selected fuel station.
After ariving at the fuel station you could resume the curvy track?

[Tom Johann]

@RetiredWingMan
@Corjan-Meijerink
I had a similar situation yesterday. Sometimes even without deviating from the route MRA autoskipped one or more waypoints, sometimes up to 6 waypoints which completely destroyed the route..
@Corjan,

1. MRA started skipping on the way from WP 18 to 23..
2. A friend (v4.1.2 (NO Beta)) used the same route without WP 13 (older version). As soon as we deviated from his route after wp 12 his MRA skipped to his wp 20 which is my wp 21 (next via point (red)).
   .
   

[RetiredWingMan]

@Corjan-Meijerink here is my route. https://www.myrouteapp.com/en/social/route/3868004?mode=share
The problem started when I exited the 407 onto the 403 and then onto the QEW rather than continuing on the 407.
The first time it skipped to the end was on the QEW just past, SW, of Oakville. South of wp's 10 or 11. Later on I reset to wp 14 or 15 to get the correct exit from the Hwy. I had to reset again to wp 15 and a little later I had to reset to another wp and then turned off autoskip. My memory may be a little fuzzy on exactly when i noticed if had skipped to the end and when I had reset. By reset I mean Long press on a waypoint ahead of my current location. I hope this helps.

[Corjan Meijerink]

@Tom-Johann thanks! How did your drive between those waypoints? When not deviating it should start skipping

[M. Schrijver]

My last tripwith 4.1.2 (305) wasn't good as well.
Also strange autoskip behavior.

On my route i went through 2 very short tunnels (10-20 meters long). Directly behind these tunnels was a shaping point. Due to these tunnels. The GPS signals was disrupted shortly. Shown as a straight line in the tracklog. Both shaping points were on these straight lines.
Both shaping points were not seen as "visited/reached" and there were also not auto skipped (i have auto skip enabled). Other shaping points were autoskipped. Not these 2.

First i had my "Waypoint Notifications" set to All. This was a disaster.
I missed a lot direction announcements. A lot of shaping points were annoumced as next waypoint (in Dutch: Aankomend Routepunt). It was very quiet in my helmet from time to time.
Autoskip did not work proper also.
After i change the setting for "Waypoint Notifications" to "Via". Everything was much better. Normal direction announcements and kind of normal autoskip functionality.
But the level of stability i experienced with version 4.1.0 (AA and ACP revamp) is not there anymore.

This version is not good enough.
My wife begged me to go back to TomTom Go. According to her I am much more pleasant guy when riding with TomTom Go.

[Michel van Hagen MRA-Founder]

Ik rij nu in de Harz met app versie 4.1.3 - 306 (alpha test versie), geen crashes, app hervat de route goed, tussenstop toevoegen ging goed, audio goed, navigeren goed, Apple CarPlay geen klap verkeerd gegeven, dat geeft geen garantie dat het bij iedereen goed gaat en ik heb niet alles getest, maar het lijkt een bijzonder stabiele versie te zijn!

I am now driving in the Harz with app version 4.1.3 - 306 (alpha test version), no crashes, app resumes the route well, adding a stopover went well, audio good, navigating well, Apple CarPlay did not give a wrong blow, that doesn't matter. guarantee that everyone will be fine and I have not tested everything, but it seems to be a very stable version!