I know some of you won’t care, if that’s the case, then please ignore this thread. There are several sections of the UI that are missing spaces or capital letters. For the Fairphone 4 (Android 11) I also reported this a few years ago and it never got fixed. The Fairphone 4 had some more issues, so I guess with the Fairphone 5 (Android 13) we see some progress. But there are still some issues, some of which date back from Android 11. It’s time these minor issues get fixed. Typos just make a device look cheap/buggy/low quality.
The following typos can be found in the security, battery and display settings, as well as the camera app. I’ve reported this (again) to FP support.
I do care about this sort of thing but it takes a brave and keen-sighted individual to draw attention to it. They risk having their own grammar, syntax and spelling criticised: I would prefer a semicolon or “but” after “care” in the OP.
I have two out of three of the OP’s “Auto factory reset” missing spaces on my own FP4. More importantly, should it make clear that 15 consecutive incorrect attempts will cause a reset?
The Android 14 update came with a new camera version, the typo’s in there are solved. That’s nice. But I don’t get why the typo’s still haven’t been fixed for the Android side of things. I could fix that if the code was open-source, it’s probably just an xml file with different languages? It probably takes 5 minutes to fix it (and push the changes for the next monthly update).
Yep. I’ll forever wonder why they decided to scrap their brilliant FP2 OpenOS and GitLab instance for a private one solely accessible to FP itself. It’s fundamentally nonsensical when we see the incredible amount of community support that CalyxOS and /e/OS get merely by virtue of being FOSS.
Once upon a time, their attitude was much different:
You’re assuming that the typo reports are even reaching the developers
Your bet best is probably, ironically, to become a beta tester and create a ticket for the typos. Hopefully that will make whoever is responsible for the beta testing for the FP5 create an internal ticket for it, which is where I assume the outsourced dev team is looking for stuff to fix.
But yeah, it makes no sense why they went from FOSS:ing as much as possible to… just not bothering at all.
@loseyourself, I, for one, would love to. However, I don’t see any mention of an fp5 beta programme anywhere. Do you know of a method by which one could become one?
You cant unless FP publicly searches here in the forum for new beta tester what I dont think will happen (in the near future), as the circumstances why they did so for the FP4 are not given…
I hope their internal communication works and they properly relay tickets to the right person I considered joining the beta test team, but I can’t. My phone needs to work because I need it for work. The final releases are sometimes already a bit iffy. But, they are improving.
I considered joining the beta test team, but I can’t. My phone needs to work because I need it for work. The final releases are sometimes already a bit iffy. But, they are improving. 