I found the issue to be solved for Waze on Android Auto since a few days. I think it has been dealt with at Waze, the way the gps speed is displayed looks updated.
Haven’t checked it on Waze without Android Auto.
That’s nice,
Unfortunately, the issue is still present when using the phone display,
On Waze and OSMand, (and probably more apps)
I don’t have a Android auto device / display.
The attempts of the developers of OSMand to build in a solution/bypass for this bug specifically for the Fairphone 5 haven’t helped yet.
Thank you all a lot for trying, is much appreciated.
My seport request is now closed without a solution.
i will send a new seport request to Fairphone.
i hope everyone how have this issue will do the same.
Just had a FP6 next to my FP5 both running Osmand. This was motivation enough to contact support again to ask them to fix this. With FP6 doing it correctly it’s hard for them to claim that FP5’s behavior is the correct one - hopefully they don’t destroy it on FP6 now ![]()
Time to celebrate after 2 years?
Didn’t get the update yet (but had only little time in WiFi since the release) but will definitely report back here.
Edit: Update went smoothly and from a first check at the window it indeed looks like the issue is fixed. To be honest I almost had given up hope, so this is really great.