it has improved a bit, but is still noticeable
Reading this thread, I realise that I don’t even know if the adaptive refresh rate is always enabled or can be disconnected.
In the settings, I can choose 60/90/120 Hz but I don’t see how to enable or disable adaptive refresh rate.
So I wonder if 60/90/120 is a fixed refresh rate or the maximum for the adaptive. And, in this second case, if (and how) it can be enabled/disabled.
So is the problem that unlocking without pressing the power button results in the phone not waking fully, staying in power saving mode (low FPS). Disable fingerprint and you then have to press the power button, fully waking the device and then you don’t get the issue?
Hence why with fingerprint unlock enabled, locking and re-unlocking the phone works when you get the issue, because you’ve pressed the power button.
2 Likes
Worked for me! Thanks!
Quand je lis cela ,je ne suis pas certain que c’est ,pour l’instant ,n bon choix pour moi de prendre un FP6
ne suis pas un technicien et je
Kindly post in EN in EN topics
Yeah thats off still happens as it dit before nothing changed
Sad to hear. It’s been more than a week for me with 0 frame drops. I’d say you enable the AOD and wake by notifications for a day and then remove the wake up by notifications. Just to give a test matching my setup.
I guess (and hope) the developers are still working on a final fix.
Yes i have try that and yes turning always on display (on) does make it go away but as soon as you turn it off its insta back to the same problem
Something i also noticed is that wen you rotate the screen to 1 side its smooth no freezing or lag but if you turn it the other way freez for a sec
So in short what ever the devs have done to tweak the display they need to remove it all there display tweaks need to be removed
And i turned AOD back off as that is how the phone came out of the box+i like to save om battery
So the devs still need to fix there
They need to fix it for sure, but at least you have a workaround. Does it consume a bit of battery? sure. But I would say is worth keeping it like that for a month (or what it takes) while devs fix it.
So combination that seems to work is AOD on + No wake by notifications.
Does anyone tried to enter developer mode (settings, system, system build > tap 5? times > developer settings under system) and set the display display refresh rate to on?
I saw the dropping rate as well but it seems not refresh rate related but maybe cache or app related (I see it the most if I scroll down a news feed..).
Yes, I noticed the same thing
Did the same when I had issues and frame rate shown stable but was still slow AF.
I disabled wake on notifications on my phone, and I no longer get frame drops, but now every once in a while my fingerprint reader doesn’t work when I try to unlock my phone. I need to turn off the screen and then turn it back on for the fingerprint reader to work again. This didn’t happen before disabling wake on notifications, which is weird.
1 Like
They said it was due to baterry optimisations not being disabled correctly, so the screen might be refreshing at the target refresh rate, but the processor can’t keep up in battery saving mode. But regardless, it manifests in extremely choppy performance.
1 Like
sure but that does not explain why turning the screen to left is fine but once you turn it to the right everything on phone also freeze’s im still going with the same point that there display driver is messed up to hell
also now using the always on display setting to on
the problem is gone but battery life is **** now
went from 2-2.5 days to to 1-1.5 days now
i hope i can get lineage os soon as i have a feeling the this is never gone get fixed or addressed by the devs there just gone do more useless tweaks instead of the fixing the problem
Update on the disabling wake on notifications fix: after a few days, I still notice occasional frame dropping on unlock, it’s far rarer than before, but it still happens. However, now the fingerprint reader doesn’t work about 20-40% of the time. As with the previous bug, I have to turn my screen off and then back on again for the fingerprint reader to work. I have set it to be disabled when the screen is off, so I’m assuming it probably has to do with that.
1 Like
FP published a summary and created a questionnaire. Please read
1 Like
Hello everyone,
Thank you for your patience and detailed reports regarding the refresh rate issues you’re experiencing on the Fairphone (Gen. 6). We’ve been actively investigating this problem and have made significant progress in understanding what’s happening.
What we’ve identified so far Through in-field reports and internal investigations, we’ve categorized the refresh rate issues into five distinct scenarios:
Scenario 1 - AOD + Covered Light Sensor: When Always-On Display is enabled, unlocking via fingerprint while the light sensor is covered causes slow UI performance.
Status: 
Fixed in August release (FP6.QREL.15.122.0)
Scenario 2 - Media Playback Unlock: During video playback, if the screen auto-locks and is unlocked, refresh rate drops causing slow UI response.
Status: Fix ready for next release
Scenario 3 - Notification Wake Stuttering: When the device briefly wakes for notifications then sleeps, subsequent unlocking may cause stuttering.
Status: 
Solution in development Workaround: Disable “Wake screen for notifications” in settings
Scenario 4 - General UI Stuttering: Stuttering while scrolling through apps or webpages, especially when loading new content.
Status: Solution in development Workaround: Close and reopen problematic apps
Scenario 5 - Post-Call UI Sluggishness: Reduced responsiveness after ending calls via WhatsApp, Zoom, or Instagram.
Status: Solution in development Additional workarounds for all scenarios:
General: Lock and unlock the screen to restore normal refresh rate Alternative: Some users report that switching to 60Hz manually reduces the frequency of issues
Upcoming release The September update will resolve Scenario 2.
Note that Scenario 1 was already addressed in the August release (FP6.QREL.15.122.0). If you’re still experiencing AOD-related issues, please make sure you’ve updated to the latest release, and let us know if the problem persists.
Help us finalize the remaining fixes To make sure we provide comprehensive solutions for Scenarios 3, 4, and 5 and validate our current fixes in all real-world conditions, we need your help with gathering additional details.
We’ve prepared a comprehensive questionnaire that will help us:
Confirm which scenario(s) you’re experiencing Identify any additional patterns or edge cases Validate that our fixes work as expected when you receive the updates Fine-tune the remaining solutions currently in development.
Your reports have been incredibly helpful in helping in tracking down and fixing these display issues. We’re working hard to get comprehensive fixes for each remaining scenario.
Please fill out the questionnaire - your feedback will help us get these final fixes out faster.
Thanks,
19 Likes