The issue with the âSIM is HD-Capableâ-notification is still not fixed unfortunately. Otherwise there is the missing touch sensor feedback when on silent mode. Other than that, no issues so far.
We would like to have the small vibration when touching the fingerprint sensor back. And, no, we donât want any other haptic feedback. This vibration when performing a gesture or touching buttons is rather unpleasant.
Thanks for the update.
After the update I donât get haptic feedback from the fingerprint sensor. It used to give feedback even with âTouch feedbackâ turned off.
In the release note your write: Fixed an issue where fingerprint haptics were not functioning correctly.
Can you elaborate what was not functioning correctly? I sure hope you donât mean that fingerprint haptic feedback should be linked to screen touch feedback.
kindly scroll up a bit and read what was written before about this if not done yet. It indeed seems that people complained that there was haptic feedback on the sensor when vibration was turned off and I guess this is what is meant by the âfixâ
and now its related to this setting. If they consider it bug or intended, needs indeed to be clarified, there has been no answer to this so far, neither in the beta group
I did read the thread and also read that comment and hope for an explanation more than a guews. Seems like you also want an explanation.
I want to make it visible that some fairphone owners actually see this âfixâ as a regression as it has never been working the way your quoted comment is referring to.
Havenât updated yet, saw the thing about the fingerprint sensor vibration. I also have vibration disabled normally but I need the vibration feedback to know if the sensor is reading my fingerprint correctly. It worked the same way on my old phone (Android 11, Motorola), small vibrate once for unlock and twice if it was rejected (even with phone silent and touch vibration disabled). This is a standard Android behavior and if this change is intended then imho Fairphone shouldnât be deviating from the stock behavior or if this really is a devisive issue (I can see how some people would be annoyed by the vibration) then it should be made configurable.
Also disappointed to see that none of the long-standing issues (background apps being killed, wallpaper being reset, weird reboot/settings behaviour if brightness is set below 34%) have been addressed.
Very disappointed to see âfixingâ of stuff that is not broken (and breaking it in the process) and no work being done on fixing the existing issues.
It seems that with the latest updates we have practically no options to control vibrations, even though the settings imply otherwise. For example, I would have preferred the keyboard to have the haptic feedback, as also the fingerprint sensor. Nothing more. This was my setting in an old Sony before FP5. First when moved to FP5, lost the option for the keyboard, and now for the fingerprint sensor. Somehow the coding of these settings is all confused and now it is all or nothing.
My problem seems to be quite the opposite from this one. The latest upgrade had the note Fixed an issue where fingerprint haptics were not functioning correctly. But since then, my phone no longer vibrates on unlock.
Unlock still works, but Iâm not getting any haptic feedback anymore (used to be on successful unlock as well as not recognizing my finger).
I found that enabling âTouch feedbackâ in the âUse vibrations & hapticsâ section also re-enabled unlock-vibration, but I donât want general touch feedback, I only want it on unlock as it used to be.
Android 15, security update October 5, 2025, FP5.VT2F.C.065
Welcome to the club!
Youâre probably the only one who found this a problem
I would prefer it to be left as it was (just haptic feedback for the power button without the need to enable touch feedback in the settings). But weâll get used to it I guess
Exactly! These are the moments when itâs really hard to remain serious. Every day we read about the provider name in the status bar, we read about SIM 1 being HD-capable, we know that the GPS keeps updating way too fast and so on and so on. And what do we get a fix for? We get a fix for a problem that most people didnât even know that it was a problem.
I usually try to take Fairphoneâs perspective to get a better understanding of why things are as they are. But in these situations I really fail to understand that. Iâm sorry.
If someone with the tag âFairphone Angelâ next to their name is saying âI would prefer it to be left as it wasâ and âweâll get used to it I guessâ rather than saying âIâll make sure to pass this feedback back to the team and try to get this resolved in the next update with a revert or a new toggle settingâ then something is seriously wrong.
I get that âthis is not an official support/bug report forumâ etc. etc. but this feels like Fairphone are just trying to have some kind of empty âpresenceâ on the forum to quiet the masses while the software team hides behind a faceless entity pushing buggy cr*p with no connection to the people who are actually using the product.
Please note the following
You will be able to recognise and differentiate Fairphone Employees ( with FP logo), Angels (with Angel) and Community Moderators, from now on, I hope ![]()
3 posts were merged into an existing topic: Communicating with the users