Subcategories

• ---

• [App] Problems, Bugs and other Issues

  949 8k
  949 Topics

  8k Posts

  undefined

  I tried that but it didn't seem to work What do you mean by it didn't seem to work?
• [App] Suggestions and Discussion

  550 4k
  550 Topics

  4k Posts

  undefined

  @Arjan-de-Vries Dat doe je toch voor je vertrekt neem ik aan....
• [App] Announcements

  41 643
  41 Topics

  643 Posts

  undefined

  Hi everyone! Coming week update 4.4.0 will be released to the public! This update might not have the most spectacular changes but I'm sure you will be happy with it! Why? After a very long time of working together with HERE we identified why some users still experience a massive amount of battery usage. This update is the first in which that is reduced! The first? Yes! More updates to come for sure regarding issue now that we know where to look. After testing on a lot of different devices we see a relative improvement of ~20%. Note: not all devices had this issue and not all devices will experience the same improvement. That said, I am confident everyone will have a smoother app experience and less strain on the CPU / GPU leading to better battery life and charging capabilities. What else is new in this update: The route "eat-up" is now seamless meaning that the route line won't have a weird animation anymore where the progress (part you drove) was ahead or far behind your current position Fixed an issue where the start page map position would not show your heading correctly Fixed issue where tap to recalculate would not trigger Support new SilverFox firmware (soon to be released by them, solving issue where long press a button also resulted in short press being triggered) Improved contrast in menu's when navigating them with a bluetooth controller Minor improvements to waypoint skip algorithm Internal updates Curious to learn your experiences regarding the battery usage! Do know that more improvements will be coming Cheers, Corjan
• [App] Android Auto & CarPlay

  109 837
  109 Topics

  837 Posts

  undefined

  @Marinus-van-Deudekom ik volg altijd het spoor dus als xt iets anders bedacht heeft dan negeer ik dat in 50% heeft xt gelijk bv bij afsluiting of een richtingsverkeer en ander 50% dan klopt het gewoon niet en blijkt weg gewoon toegankelijk. route is dan in here kaart dus zou 1 op 1 moetren zijn. MRA ging trouwens ook een paar keer in de fout. Here kaart materiaal is niet altijd correct bij offline gebruik.