And here we’ve got yet another application (Blue Square Speedometer | F-Droid - Free and Open Source Android App Repository), which - according to Fairphone - must also be broken due to current android versions, because the bug definitely can not be caused by their device’s firmware…
(The speed refresh rate on the gif isn’t quiete as high as in reality because the built-in android screen recorder for some reason only recorded with ~10 fps, but its close.)
Are we going to see any official updates from Fairphone on this topic or do they actually intent to drive their customers away to other smartphone manufacturers?
If I’m not mistaken, this board is operated / offered by Fairphone itself. Hence I’d expect a company that sells devices for hundreds of euros to take a look at their own board’s contents. This thread consists of 40+ posts informing them about the problem occuring in multiple apps. And in difference to a support ticket, these are luckily public and hence cant be swept under the carpet as easily.
And regarding the question who has to proof what to whom: I’ve searched the web for this problem with and without the keyword “Fairphone” without any meaningful results except for this thread on like page 15. If this was a general problem with A14+, I highly doubt that no one on the internet would have reported it somewhere else.
In order for the manufacturer to be able to deny responsibility for solving this problem along the lines of “it’s known and it’s not up to us”, I would expect this to be backed up with publicly available examples of other occurrences of this problem at various other manufacturers. That would be transparent communication to their customers.
I reserve now and then (ones a 1,5 month) a massage, telling they are very busy at the moment, and they have not a answer yet, and will come back to me when they have a answer.
i think its best if you experience the problem as discussed in this topic and ‘don’t’ have a open support ticket (you can check on the website. there you can see a list of all sepot tickets on your email address.)
to send them a email using the code of your closet sepot ticket if you have that one.
explain schort but more important very clearly wat the problem is you experience and share a link to this topic on the community form, that will probably make it easier for them to link you question to everyone here ho have a open seport ticket on this problem.
if you ticket is still displayed as open on the website. no need to send a other email.
That is wat i think is the best approach.
for now we can only wait for Fairphone ho neet to solve this bug.
@d19e84 thank you for sharing that video, i think its a very good way of showing wat is going on.
In this case you are mistaken as you are told when creating an account. The forum is not lead by FP and is no place to report issues. Please also see contactsupport
Alright, I’ve been under the (appearently wrong) assumption, that a board hosted on a subdomain of fairphone.com would be somewhat related to the company controlling fairphone.com.
Turns out I was mistaken on that assumption according to their own definition:
@all please dont go further off-topic and discuss interpretations of FP activities. Stick here to discuss the actual issue. The rest can be discussed in other topics that are spread already all over the forum.
please check if i dit forgot something important or dit get it wrong, just trying to make a compact summary:
the speed indicator jumps around to fast to read.
the problem is only present on Fairphone 5.
the problem was already present when the phone was released.
the problem is always present. (not something wat only shows sometimes)
the problem is pressed in all apps. (excep Google maps)
the problem is not and was never present in the Google maps app.
the problem present on all FP5 FPOS devices.
there is no workaround for this issue.
please tell with one is true, i’m not so sure about this:
the problem is also present on all Fairphone 5 with alternative OS installed.
or
the problem is pressed on some Fairphone 5 alternative OS:
oideOS, …, …, and …
the problem is not present on the alternative OS:
…, …, …, and …,
Please check if i dit forgot something important or dit get it wrong, just trying to make a compact summary:
The speed indicator jumps around to fast to read.
The problem is only present on Fairphone 5.
The problem dit appear after installing Software Version: FP5.UT20.B.041 (Android 14)
The problem is always present. (not something wat only shows sometimes)
The problem is pressed in almost all apps.
The problem is not and was never present in:
Google maps app.
Geovelo app.
The problem is present on all FP5 FPOS devices.
There is no known workaround for this issue.
Please tell with one is true:
The problem is also present on all Fairphone 5 with alternative OS installed.
Or
The problem is pressed on some Fairphone 5 alternative OS:
oideOS, …, …, and …
The problem is not present on the alternative OS:
…, …, …, and …,
I would describe that as “too frequent/erratic position updates”. One of the consequences of that is the described behaviour of the speed indicator, another one is the the complete distortion of average speed, top speed, etc. (basically all statistics related to the speed) when tracking routes. I tried to track a walk and ended up with an alleged average speed of 12 km/h and a maximum speed of about 32 km/h! Additionally the map direction/rotation (when set to be rotated according to moving direction) keeps jumping around permanently due to the very frequent position updates - at least in my experience.
Of course i can’t be sure whiteout checking your Tracklog (I don’t mean you should share them, just chek it yourself), i think its a normal behaviour, not something only Fairphone5’s suffer.
if you export your GPX and open it in a good computer software programma like Garmin Basecamp. (is free) or the one you prefer.
and check all the points of the GPX you will probably find one or more miss calculations (offten a reflection from a window or something else) . this is something you see on the best walking GPS devices. it happens often.
the dot is probably misplaced, 10 meters left or right wat increase the distance a lot and do effect the max speed reading. if you remove this dot from the GPX File the value will be right again.
i know its a bit stupid but its just the way GPS is made. not much to do about it. ofcourse its possible to make software wat will eliminate thos miscalculations as much as possible still that software can make mistakes again.
can you check it this was the case way average and maximum speed were incorrect.
im not talking about the live speedometer whare this topic is about, Fairphone 5 FPOS definitely does something different there than other android devices wat what causes the unreadable speedometer. i dont know what exactly.
I do get your point, but I dont agree with it. I tracked walks and bicycle tours with the last two android devices I had before I made the mistake to buy this phone - a huawei and an asus. I used the same application to do so (Osmand~ with the exact same settings) and always had plausible values - compared to the built-in step counters of the smartphones when walking and compared to my bicycle speedometer when riding my bike. Hence I’m pretty sure that the gross misscalculations in speed and distance are related to the (probably firmware-related) bug discussed in this thread.
i have checked it on my phone, dit i testet the right thing @d19e84?
using my old OnePlus 6 and my Fairphone 5.
started the tracking in OSMand+ on both phones at the same moment and started cycling.
The Fairphone 5. i noticed the location marker dit get stuck in corners and left behind, strangely the Tracklog was not effected by this error, i change a setting in OSMAnd and now the location marker is not longer fixed on the phat, this dit fix the issue.
strangely this didn’t ignore me that much before.
the OnePlus 6 dit not show this issue, it is set to be fixed on the phat. the location marker was on spot all the time and no flickering of the screen.
