Hi.
are there any updates to this problem?
im still have this problem using Waze.
is there a way to solve this problem?
greetings
wat @Johannes_Cannoodt mangend it’s looks like this problem is more common on the waze app.
and less on google maps ore OSMand.
i will try to test this again but i manly use Waze.
are There different experience with this problem?
please response if you have ore don’t experience this problem.
thanks a lot.
It’s super annoying in Osmand especially because the speed doesn’t use a fixed-width font, so when you’re (for instance) between 19 and 20 (or between 99 and 100) it keeps flickering back and forth and you cannot quickly read the speed.
But you’re right, Gmaps seems to use its own smoothening (or a different API call? I’m not familar with the underlying API), so the issue is not really present there.
2 Likes
Still occurring when using Organicmaps, the bug is logged at FP and under investigation…
3 Likes
I received the following feedback
It seems to be an issue with third-party navigation apps and Android 14 , not only Organic Maps and the Fairphone 5.
Thanks for sharing, but that’s exactly what we’ve found in this thread already, too. Basically all apps except for Google Maps have this issue since we switched to Android 14. But it is an issue with FP5, it seems, because when I search for this without FP5 in the query then one would expect it to pop up in general for those apps on other phones, too. But I didn’t see that.
1 Like
I shortly tested on my Tablet running A14 sitting in a train and could not reproduce. FP says they tested on different devices. Will report back about the tablet…
1 Like
So although they agree it should happen as well on the tablet, they recommend to flag this to the app developers, so that they can look into that and understand. Because they were able to consistently reproduce the exact issue on smartphones of different brands.
Are they sure they have seen what we are complaining about? I’ve now spent maybe half an hour searching on the web and the only real match about this issue is this thread. I’ve searched with “Osmand” and without, tried “Android 14 gps speed” with additional words like “flickering”, “smoothening”, “update rate” and so on, the same in German. I need to find someone with a non-Fairphone and Android 14 with any other map app than GMaps installed to validate this.
For Osmand I could still check a nightly build as they are addressing some issues of the stable version in those builds already - but since it doesn’t seem to be an Osmand-only issue…
One thing more: Do those of you who encounter the issue have “Improve location accuracy” (or similar, that’s translated from German) enabled? I didn’t check if that makes a difference (and my phone currently can’t see the sky to check this quickly).
Yes on both my FP5 and the tablet.
Edit: I dont think its better when its off
1 Like
I was (am) in touch about the issue with support. This was the reply:
“We have investigated these symptoms internally, and our findings indicate that this behavior is occurring across several Android devices running Android 14. However, we found that the issue does not occur in Google Maps, which suggests that the third-party navigation app you are using may not be fully compatible with Android 14.”
Now, the weird thing is I thought I discovered (a part of) the problem and sent this in an earlier email to support:
"I switched off However, i think I just discovered something interesting, namely:
Location source: Google Play Services or Android API.
It turns out that when i use Android API al is fine…"
But the annoying thing is: now using the Android API and after rebooting the phone, the problem is back, but WITH the Android API (you can switch in Settings on OsmAnd with location source (Locatiebron in Dutch, Instellingen → OsmAnd instellingen → scroll down ‘Andere’ and there is Locatiebron (looks confusing, but I am not sure what the translations in English are probably Settings, OsmAnd Settings, Other, Location Source/services?)
Anyway, I hoped to know more, but no. Google maps seems relatively smooth. But saying it is a problem of other app developers (I have it with OsmAnd, Navionics, MarinTraffic) and not an Android 14 problem… well 
)
Same here with iodeOS 5.8 (A14) on Fairphone 5 using OsmAnd.
(speed - and position! - updating several times a second, hence the speedometer is not readable and the position and with it the map view keeps jumping around slightly)
Cant reproduce the issue with another device running LOS 21 (A14) and OsmAnd!
Aside from that (and probably slightly OT): According to OsmAnd (and GPS Test from fdroid) the FP5 finds by far the most satellites of any android phone I’ve ever had. First I suspected that might be the cause of this issue - some kind of “information overload” - but since I didnt test navigation on A13 and according to other responses in this thread it didnt occur with A13 that should probably be ruled out.
2 Likes
Interesting. If it’s the same on non-FPOS then this means it isn’t in Fairphone’s Android flavor but in the firmware of the phone/the chipset. So Fairphone might have to rely on QCom’s support to get this fixed? I fear this is going to be a long-standing issue…
Btw: GPS performance used to be really good on A13 already, there wasn’t any change when going to A14 except for the refresh rate.
2 Likes
Dont forget, FP is the opinion its an issue of the Apps with Android14 because they
were able to consistently reproduce the exact issue on smartphones of different brands.
2 Likes
If it’s the same on non-FPOS then this means it isn’t in Fairphone’s Android flavor but in the firmware of the phone/the chipset.
I thought so, too. Hence I deemed it relevant to share my experience here.
I obviously also went to the search engines of my choise to search for anything similar and the only thing I found on like page 15 of the results was this thread. Nothing until I added “Fairphone 5” to the search terms. Kinda s*cks on a new >500€ device tbh, but I suppose the support would just tell me to install FPOS because they cant support other ROMs.
2 Likes
Hey guys, it looks like the issue is at least solved with the last update of Google Maps. However, Waze still has the speed reading jittering like mad so it’s probably going to be either waiting for FP to fix it or the GPS speed displaying apps.
The Maps version I have is 24.50.04.705335264
For me it never was an issue using GMaps.
2 Likes
Just updated to iodeOS 6.0 (A15). The issue is still present.
Are there any official updates on this from Fairphone? Or do they keep blaming non-google navigation apps?
1 Like
No updates and with your set-up you would even proof they might be correct, as I doubt its a hardware defect
My set-up is a pointer to the combination Fairphone 5 + Android 14(/15). If the problem lies in the firmware, not the system partition as @Martin_Anderseck suggested, it would make sense that the ROM installed doesnt make a difference.
Besides I wasnt able to reproduce this bug on another device with A14, hence I doubt their reported answers and also tend to suspect the cause to be in the firmware.
Is it normal for Fairphone to ignore issues like this? This is my first Fairphone, thats why Im asking. For someone who uses their device to track routes this bug is a total failure, as the permanent updating completely distorts essential values such as average speed and top speed.
2 Likes