New beta! 5.1 (457)
-
Okay, folks. First field test of version 5.1. I don't know if anyone else has had a chance to try it yet.
I'm always referring to Android Auto.
First, the waypoint list doesn't work. I had a route loaded of about 300km with several waypoints, and when I went into the AA menu, it just kept loading, and no matter how long I waited, the list never appeared.
Second, the name of the next waypoint doesn't appear on the main screen at any point, not even when you approach it, unlike in the app.
Third, the altitude isn't displayed on the screen.
Another thing that needs improvement is the order of the buttons in the app's menu within AA. For example, the WP list appears last, and I think it's something that's used repeatedly, so it should be near the top.
One thing I liked is the Next WP icon that now appears on the main screen and tells you what kind of WP it is (food, photo, coffee, etc.) and how far away it is. It's quite useful. It seems to be running smoothly.
-
Okay, folks. First field test of version 5.1. I don't know if anyone else has had a chance to try it yet.
I'm always referring to Android Auto.
First, the waypoint list doesn't work. I had a route loaded of about 300km with several waypoints, and when I went into the AA menu, it just kept loading, and no matter how long I waited, the list never appeared.
Second, the name of the next waypoint doesn't appear on the main screen at any point, not even when you approach it, unlike in the app.
Third, the altitude isn't displayed on the screen.
Another thing that needs improvement is the order of the buttons in the app's menu within AA. For example, the WP list appears last, and I think it's something that's used repeatedly, so it should be near the top.
One thing I liked is the Next WP icon that now appears on the main screen and tells you what kind of WP it is (food, photo, coffee, etc.) and how far away it is. It's quite useful. It seems to be running smoothly.
@bluetuz thanks for the feedback.
1: I’ll investigate this tomorrow
2: already added for the updated beta version before definitive release. That’s indeed not in the version you have now.
3: is the setting enabled? See “screen layout”
4: we have reordered buttons already which be available in the next pre-release version (just like 2)Glad it runs smoothly
-
@bluetuz thanks for the feedback.
1: I’ll investigate this tomorrow
2: already added for the updated beta version before definitive release. That’s indeed not in the version you have now.
3: is the setting enabled? See “screen layout”
4: we have reordered buttons already which be available in the next pre-release version (just like 2)Glad it runs smoothly
@Corjan-Meijerink Thank you for the quick response.
I have the setting enabled for point 3.
I appreciate the effort you're making; I think the foundation of this app is very solid, and improvements will gradually be implemented to make it even better. -
@Corjan-Meijerink Thank you for the quick response.
I have the setting enabled for point 3.
I appreciate the effort you're making; I think the foundation of this app is very solid, and improvements will gradually be implemented to make it even better. -
Not sure if I'm writing anything correct or not... but I suppose altitude comes from GPS. Perhaps it takes GPS position from Carplay device and this is not providing it? (rare, I know, but ...)
-
I'm guessing it has to do with the fact that the screen resolution is too low.
In some cases there just isn't enough space (we think) to show it.
We are checking this now. -
Not sure if I'm writing anything correct or not... but I suppose altitude comes from GPS. Perhaps it takes GPS position from Carplay device and this is not providing it? (rare, I know, but ...)
Not sure if I'm writing anything correct or not... but I suppose altitude comes from GPS. Perhaps it takes GPS position from Carplay device and this is not providing it? (rare, I know, but ...)
'Note: While using CarPlay or Android Auto, the navigation position (GPS signal) is provided by your phone's GPS receiver, not the Chigee device.'
Interestingly, it does have on-board GPS, but it's only used 'exclusively for system data and dashboard metrics', such as:
- Time & Date: Automatically calibrating the time zone and ensuring accurate time display.
- Speedometer: Displaying real-time speed on the dashboard interface.
- Odometer: Tracking travel distance for trip recordings.
So it has some basic GPS-related features without the phone.
-
First test on AA today
It started whithout any problems. Did a testdrive of 125 km. Build in a false shapingpoint to see what would happen. Kept on the route ignoring the false shaping point. As expected MRA tried to sent me back. After 2 times it gave up and résumée. The route.
The gasstation indication was of no use at all. Near to the start it indicated a station at 97 km. I passend 6 stations on the route and never got a warning. Shell, totall etc gave no show.
On comming to a complete stop the map still is spinning, north -
My tests on IOS went without any problem, altitude is shown, no problem at all. Just iphone 15, no carplay.
-
I created a small route today with Via and shaping points, everything worked well, it showed altitude and fuel stations along the route, this was on AA and in the car I have not used it yet on the bike but first impressions, its fantastic
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
-
07153
-
06208
-
06161
-
6251.3k
-
0235
-
23117.5k
-
016333
-
33910.3k
