this post was submitted on 27 Nov 2023
780 points (97.6% liked)
Technology
59675 readers
3673 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Do report these on the FP forum when you encounter them, the staff seem pretty proactive at getting these fixed, although it takes them a while... (at least they were for the FP3 - even community requests for a very low screen brightness were honored, and now they're supporting two versions of android for the FP3 due to Google's fingerprint sensor requirement nonsense on Android 13)
Sure, done that. But the issues I have have been open for months (e.g. the really unresponsive screen since they "fixed" the ghost touch issue by reducing the screen sensitivity for all phones, even the ones not affected by ghost touches, making other phones ignore touches all the time).
Or Android 13 frequently crashing, resetting or freezing if you dare to use 5G. That's a blocker level bug that is open since Android 13 was released and support told me a week ago that they still have no clue why this happens.
And even though some of these bugs are super easy to fix (and I proposed some fixes that I got running on my phone using root, with no access to any source code) they still spend months not fixing them.
The very low screen brightness for example took from February to October to fix, even though it took me 15min and I sent my fix to support and posted it on the forums. No change happened until they updated to A13, which rewrote that part of AOSP.
And the ghost touch/screen sensitivity issue, which has a dead simple fix, is still open since launch. The issue there is that the screens have very different levels of sensitivity from the factory. So if they set one software sensitivity level, either some get ghost touches or others get an unresponsive screen. So the fix is to just add a toggle or a slider in the settings that users can use to adjust the screen sensitivity, just like e.g. Samsung has done for a long time. Instead, they just arbitrarily change that value to ruin the experience for someone else.
And yes, that proposed solution has been on the forums for years and it was also sent to support.