Subcategories

• ---

• [App] Problems, Bugs and other Issues

  1k 12k
  1k Topics

  12k Posts

  

  @M.-Schrijver My suspicion is that at that moment, point 56 was closer than point 42 and the app wanted to go there. What I always try to do myself is place a point after the turn at every change of street/direction. If I see that there are no points on a long stretch, I add a few (after a fork or turn). Then, if something happens, I can skip the points more easily, or, as in your case, prevent the app from wanting to go to a closer point. Personally, I have automatic point skipping turned off (so this doesn't happen) and recalculate enabled.
• [App] Suggestions and Discussion

  812 6k
  812 Topics

  6k Posts

  

  Heb net gezien dat ik het schuifje zelfs niet kan verzetten...
• [App] Announcements

  57 1k
  57 Topics

  1k Posts

  

  @ginogino, sideloading apps can create a hose of problems concerning the current (not yet recognized) update over an PlayStore initiated version, and also future PlayStore updates over an unrecognized sideloaded version. Also sideloading needs some (not difficult) actions to allow "unknown sources", which in turn makes android vulnerable if not reversed. I think if MRA went that way, we could expect a new forum category that no-one would really want to look into Let's just hope Google will better themselves...
• [App] Android Auto & CarPlay

  247 2k
  247 Topics

  2k Posts

  

  @Corjan-Meijerink said: @Fridjof should be fixed in v6 released late september! Released in late September and subsequently available in Google Play Store around three weeks later Sorry, couldn't resist a stab at Google.