New beta! 5.1 (457)

[b0hd1]

@Corjan-Meijerink @bluetuz is one of the participants in this weekend's rally. We'll raise a glass to your health with some good beers!

[Jörgen]

Why is the Android version not available after 7 days?

[b0hd1]

@Jörgen I think we should ask Mr. Google that...

[Guzzist]

Guys, chill out - Android has always taken 1 - 2 weeks longer than iOS. It was the same with the last update...

[white.mouse]

My 4-day trip to Belgium is almost over. I had hoped to try out the beta version, but unfortunately, it’s still not available. Bad luck.

Mijn 4-daagse trip in België zit er bijna op. Ik had gehoopt de beta te kunnen proberen. Maar helaas nog steeds niet beschikbaar. Pech gehad.

[bluetuz]

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.

[Corjan Meijerink]

@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]

@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.

[b0hd1]

@bluetuz My altitude wasn't showing up on my Chigee aio-06 either, but it was showing up on my car this morning... I have no idea why.

[Lluis Arasanz]

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 ...)

[Corjan Meijerink]

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.

[richtea999]

@Lluis-Arasanz said:

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 ...)

From https://support.chigee.com/portal/en/kb/articles/how-the-chigee-display-works#How_to_Navigate_Without_Cellular_Data_Offline_Maps

'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.