A couple of CarPlay bugs
Quote from PuddleDuck on 27.02.2024, 16:04Hi, I’ve been using CarPlay this week in v3.5 and came across a couple of bugs.
- The elevation displayed is 1000th of the actual elevation. I.e. if the elevation is actually 2400 metres, it is displayed as 2m. If it is actually 499 metres, it is displayed as 0m.
- The speed limit is often shown as “-0”. I think this is different to when it is unknown on the map, because in those circumstances it is not displayed at all.
Overall though, really like the new version!
Hi, I’ve been using CarPlay this week in v3.5 and came across a couple of bugs.
- The elevation displayed is 1000th of the actual elevation. I.e. if the elevation is actually 2400 metres, it is displayed as 2m. If it is actually 499 metres, it is displayed as 0m.
- The speed limit is often shown as “-0”. I think this is different to when it is unknown on the map, because in those circumstances it is not displayed at all.
Overall though, really like the new version!
Quote from Guido on 27.02.2024, 17:03Thanks for the feedback.
2nd one is definitely a bug, and will be fixed in the next update.
Are you sure about the 1st one? I can't reproduce this. Elevation seems fine here (I'm at 1970 meter more or less and Elevation is indicated correctly for me). Is it possible you are mistaken the thousand separator for the decimal separator? Elevation uses a thousand separator based on your Number Format setting in iOS Settings > General > Language & Region > Number Format.
Are you only seeing wrong elevation on CarPlay, or also directly on iPhone?
Best regards,
Guido
Thanks for the feedback.
2nd one is definitely a bug, and will be fixed in the next update.
Are you sure about the 1st one? I can't reproduce this. Elevation seems fine here (I'm at 1970 meter more or less and Elevation is indicated correctly for me). Is it possible you are mistaken the thousand separator for the decimal separator? Elevation uses a thousand separator based on your Number Format setting in iOS Settings > General > Language & Region > Number Format.
Are you only seeing wrong elevation on CarPlay, or also directly on iPhone?
Best regards,
Guido
Quote from PuddleDuck on 27.02.2024, 17:14Yes, definitely seeing the elevation bug. It’s not showing a separator at all, just a single digit and then “m”. Also tried it with units set to miles and feet, and had the same problem - elevation showing as 0 ft instead of 400 ft, and 1 ft instead of 1000 ft. It’s in a hire car rather than my own car, but I’ll see if I can get a photo of it and upload here.
It’s showing correctly directly on the iPhone, but not when displayed on the CarPlay screen.
Yes, definitely seeing the elevation bug. It’s not showing a separator at all, just a single digit and then “m”. Also tried it with units set to miles and feet, and had the same problem - elevation showing as 0 ft instead of 400 ft, and 1 ft instead of 1000 ft. It’s in a hire car rather than my own car, but I’ll see if I can get a photo of it and upload here.
It’s showing correctly directly on the iPhone, but not when displayed on the CarPlay screen.
Quote from Guido on 27.02.2024, 18:50I wonder if it's the car. Some cars / CarPlay systems have their own GPS receiver and some will force the iPhone to use that signal. If that signal does not provide elevation, or provides it wrong, then this could cause this problem. Would definitely like to see a picture of that. And, if possible, if you have another CarPay enabled app that indicates elevation... could you give that a test too in that car? It would not surprise me if that would indicate the same (wrong) elevation. But, I could be wrong of course 🙂.
I wonder if it's the car. Some cars / CarPlay systems have their own GPS receiver and some will force the iPhone to use that signal. If that signal does not provide elevation, or provides it wrong, then this could cause this problem. Would definitely like to see a picture of that. And, if possible, if you have another CarPay enabled app that indicates elevation... could you give that a test too in that car? It would not surprise me if that would indicate the same (wrong) elevation. But, I could be wrong of course 🙂.
Quote from Karlchen on 27.02.2024, 22:52Guten morgen,
bei mir war die Höhenangabe im Skoda Octavia 4 falsch. (10 x zu hoch) Das war mit der alten Karte. Seit Mitte Januar habe ich einen Skoda Caroq. Dort ist die Angabe richtig, auch mit der neuen Karte.
Beides über CarPlay.
Beste Grüße
Guten morgen,
bei mir war die Höhenangabe im Skoda Octavia 4 falsch. (10 x zu hoch) Das war mit der alten Karte. Seit Mitte Januar habe ich einen Skoda Caroq. Dort ist die Angabe richtig, auch mit der neuen Karte.
Beides über CarPlay.
Beste Grüße
Quote from PuddleDuck on 28.02.2024, 09:32You’re right - it’s a bug with the car’s GPS and CarPlay implementation, not with Scenic. I tried another app and it showed the elevation incorrectly too. Then, I looked at the iPhone’s display whilst still plugged into the car, and Scenic was showing the wrong elevation there too. As soon as I unplug from the car, the elevation in apps (including Scenic) is displayed correctly on the phone.
The car is a 2019-ish Seat Leon, just in case somebody else searches for the same problem and comes across this post. I’ll double check on our Mazda when we get home, but I imagine it will work as expected on that.
You’re right - it’s a bug with the car’s GPS and CarPlay implementation, not with Scenic. I tried another app and it showed the elevation incorrectly too. Then, I looked at the iPhone’s display whilst still plugged into the car, and Scenic was showing the wrong elevation there too. As soon as I unplug from the car, the elevation in apps (including Scenic) is displayed correctly on the phone.
The car is a 2019-ish Seat Leon, just in case somebody else searches for the same problem and comes across this post. I’ll double check on our Mazda when we get home, but I imagine it will work as expected on that.
Quote from Guido on 28.02.2024, 09:52OK. Thanks for letting me know. Will be helpfull for others running into the same problem indeed.
OK. Thanks for letting me know. Will be helpfull for others running into the same problem indeed.
