New beta! v4.1.2 (304)
-
Hi everyone!
Only just after the 302 beta has become available for Android, a new one is already being distributed for all platforms. Hopefully Android is a bit quicker available than last time
A full overview of the changes will be presented below compared to the 4.1.1 release. Compared to the last beta, only resume navigation from AA / CP, improved search behavior and nearby fuel adjustments are interesting!
Tracklogs in groups / events
You can now view tracklogs of not only yourself / friends but also for groups & events!
The main reason to implement this is to also facilitate the Navigation specific events (yes, this might needs some renaming on the website). When you've marked an event as such, the tracklogs recorded for those routes will be added to the event automatically 
As this means the tracklog needs to be saved while the route is still open, you will see a slight change in the app regarding stopping your navigation. When you stop the navigation, the route will still be displayed in the main (home) screen.
iOS crashes
We've continued working on the stability of the app. This should have led to a dramatic decrease in random crashes you get on iOS when for example not actively using the app.Nearby fuel stations
We've massively improved the search algorithm for fuel stations along your route. Get on the road with this version and do let us know what your experiences are!
Besides providing you with better recommendations, the fuel station is also displayed on the map
That is also visible on your CarPlay / Android Auto display.
Display of search results
When searching for destinations along your route, we now display them on the map too!
This gives a great overview of any search results relevant to you. If searching for fuel, we will quickly show all the possibilities along your route.
Resume navigation from CarPlay / Android Auto
When you've got the possibility to resume an active navigation session, CarPlay / Android Auto will ask you if you want to resume this in a more instinctive manner.
Fix incorrect lane assist
Lane assist icons were often incorrect due to a mistake from our side. That has now been correctedWhat is next?
The 4.1.3 update will definitely include the possibility to select any of your routes from CarPlay / Android Auto. Besides that we will add some more stuff to those platforms and continue working on the stability.Have a great weekend,
Corjan
@Corjan-Meijerink
I also tested "Nearby fuel stations" with my electric car.
I think it's good that you can simply click on a fuel station before you select it and get some information such as the provider, distance, etc.BUT: I also would like to see the power of the electric charging station. As you can imagine there is a big difference between an 11 kW charger and a 350 kW charger. For fast charging while driving, you might need at least 150 kW.
So this information is essential for electric fuel stations
Maybe an option to configure the minimum power for proposed charging stations whould solve my issue.
Under configuration of travel mode for the electric car mode you should be able to select "CCS" and "Type 2" as supported charger.
Maybe only selecting CCS would already solve my issue -
undefined Corjan Meijerink referenced this topic on
-
@Tom-Johann thanks for the feedback
I’ll give the waypoint placement algorithm another test - did not experience the same issue with my tests. Fallback for failed placement is however indeed end of route.I’m getting an EV end of next month which will definitely help in pushing some EV features on our internal roadmap
-
@Tom-Johann thanks for the feedback
I’ll give the waypoint placement algorithm another test - did not experience the same issue with my tests. Fallback for failed placement is however indeed end of route.I’m getting an EV end of next month which will definitely help in pushing some EV features on our internal roadmap
@Corjan-Meijerink, I tested the Next fuel station navigation within a route again.
You are right, it works usually.
I only have one route were it doesn't. So it seems to be just minor
BEFORE I selected the fuel station:
AFTER I selected the fuel station:
-
GREAT! good progress
-
@Tom-Johann thanks for the feedback
I’ll give the waypoint placement algorithm another test - did not experience the same issue with my tests. Fallback for failed placement is however indeed end of route.I’m getting an EV end of next month which will definitely help in pushing some EV features on our internal roadmap
@Corjan-Meijerink said in New beta! v4.1.2 (304):
I’m getting an EV end of next month which will definitely help in pushing some EV features on our internal roadmap
I Presume your EV will look something like this?
You don’t stop riding when you get old, you get old when you stop riding.
-
@Corjan-Meijerink said in New beta! v4.1.2 (304):
I’m getting an EV end of next month which will definitely help in pushing some EV features on our internal roadmap
I Presume your EV will look something like this?
@Lynchy67 hahaha no. I would love the torque but range still sucks on electric motorcycles and they are too damn expensive.
-
@Lynchy67 hahaha no. I would love the torque but range still sucks on electric motorcycles and they are too damn expensive.
4.1.2 - 304 is now available on Android
-
@Corjan-Meijerink
I tested v4.1.2 (304) on 265 km yesterday.
Everything worked perfect including next fuel station calculation. What I really like is that you can see the distance to the next fuel station already 100 m in front of the current fuel station.Sometimes it skipped some waypoints after I took a short diversion which didn’t really make sense.
But all in all it worked really good.
Thanks for the good progress. -
@Corjan-Meijerink
I tested v4.1.2 (304) on 265 km yesterday.
Everything worked perfect including next fuel station calculation. What I really like is that you can see the distance to the next fuel station already 100 m in front of the current fuel station.Sometimes it skipped some waypoints after I took a short diversion which didn’t really make sense.
But all in all it worked really good.
Thanks for the good progress.On route to eiffel, i found.
1.Roundabout exit is always announced and shown in icon left above as first exit to take.
2. Skipping waypoint , sometimes strange behavior
3. After a tankstop. (Did not stop the app. But to background) I found the pointer was at 1/3 from te top in portrait. No way to fix it ,except for closing the app and restarting it. -
Happy to say that 4.1.2 (304) is working perfectly for iOS using pre-planned routes and A -B from a postcode search. No problems with roundabouts or spoken announcements.
-
@Lynchy67 hahaha no. I would love the torque but range still sucks on electric motorcycles and they are too damn expensive.
Just an observation regarding the Fuel Stops.
My Route is the NC500 (Scotland)
As you will see from the screenshots below, the actual displayed Fuel Stops seem to be roughly limited between Carlisle and Dundee.
I have used full zoom on the whole route to check that there are none being hidden.
There are no Fuel Stops showing at my start point and none appear on the actual NC500 part of the route?
-
Wow the whole NC500 with only 96 points. Says enough about the variety of roads in Scotland.
-
I was out for a short ride today. Ths fuel stops look great. Will be nice when I do 10k kms trip this summer. My route today was only 5 waypoints. I was surprised when it auto skipped wp2 well before I got there. Then it tried to auto skip wp3 and I resumed it. A few minutes later I looked at the screen and it had auto skipped to wp5 which is the end of the route. I had not seen auto skip issues since last summer and never this bad.
2010 GL1800 Goldwing using Samsung Galaxy S20 5G Android 13.
-
I was out for a short ride today. Ths fuel stops look great. Will be nice when I do 10k kms trip this summer. My route today was only 5 waypoints. I was surprised when it auto skipped wp2 well before I got there. Then it tried to auto skip wp3 and I resumed it. A few minutes later I looked at the screen and it had auto skipped to wp5 which is the end of the route. I had not seen auto skip issues since last summer and never this bad.
@RetiredWingMan yeah I saw the same issue on a ride today, and did not experience it like this before (autoskip was always pretty good for me) so this seems like a new (regression?) issue
-
I noticed that exit number was correct for the only roundabout that was on my route this morning.
2010 GL1800 Goldwing using Samsung Galaxy S20 5G Android 13.
-
I noticed that exit number was correct for the only roundabout that was on my route this morning.
@RetiredWingMan That would be great as it means HERE has solved the issue relatively quick
-
The release version 305 will have some tweaks to the auto skip algorithm
