I’ll rephrase I don’t get why it’s marked as solved if the problem still persists. I would like to add it to the known and reproducible issues list. But if it’s marked as solved here while it’s still an issue, it wouldn’t make much sense, it will cause confusion. The topic also closes sooner if marked as solved. In this case I might as well create a duplicate topic to keep the described issue open. I’m fine with that as a solution, but it’s not great that I have to.
Please dont create duplicates just for the wiki. I removed the solution tag, @rokejulianlockhart hope you can agree retrospectively, if not let me know.
Edit: sometimes a workaround might be marked as solution as well, as in long topics its just easier to find it. So solution cant be taken always literally and people still need to think and read a bit…
The best solution would probably be to remove the arbitrary duration after which posts are archived, but thanks anyway, and much thanks to @UPPERCASE for adding to the list of issues.
And to state this again as I so frequently do, it would be great if @fairphone would allow us to use gitlab.fairphone.org, or just issuetracker.fairphone.org for the fp3/fp3plus/#fp4 so that poor @UPPERCASE doesn’t have to do their work for them.
There is no @fairphone tag to address fairphone here.
To let them know, you would have to contact support.
I doubt we will see any public bug tracker, as long as development is outsourced.
Support is the way to got and they have their own tracker its just not public for us.
I have the same problem. As I understand it now, the problem has already been reported to support, hasn’t it? Does it make sense to report the same problem again?
Yes. The more reports Support receives, the more likely it is that the problem will gain priority, but they’ll need details on the user context to help work out where the problem is coming from.
However, running the latest update, I’m not seeing any special problems with brightness. Make sure “Extra dim” is OFF (under Accessibility). You might also try turning off Adaptive brightness (I see no mention of that in this topic so mention it just in case). That’s under Settings > Display but you can also turn it off/on in the quick settings pull-down pane, by tapping the little sun symbol with an “A” in it, next to the brightness slider. White symbol means AB is OFF. Light blue means ON.
Other possibilities: Have you installed any apps that might have a bearing on brightness? Screen control, that sort of thing?
Thanks for your answer! I contacted the support
I have the lastest update installed as well, Extra Dim is off and adaptive brightness is off. I have also no other app installed that could influence the screen brightness.
I’m not really sure if this is the same issue, but after the Android 12 update I feel like the maximum brightness is a lot less bright than it used to be on Android 11. Yesterday I was driving, it wasn’t even that sunny and my navigation was really hard to read. When the sun shined directly on the phone, I couldn’t read a thing. (I compared it with my car’s infotainment display. The brightness of my phone’s display and my car’s display used to be pretty much the same. Now it’s noticeably less bright.) Note that the brightness slider was in fact put on the maximum value. Is this the case for everyone having this issue, or does the slider actually decrease for you when the brightness drops?
Wow, so happy someone else marked this, I thought I was hallucinating. It’s weird how it randomly drops down but is not indicated at all in the brightness.
And no, it’s not adaptive brightness or any other setting, it is a bug. I bet a lot of people don’t even notice, I only noticed when I was taking pictures outside and it kept jumping and I finally realized that it wasn’t just me, indeed it was the phone.
What exactly did you change with the brightness? I’ve noticed sometimes the screen suddenly clipping from max brightness to ~80%. The brightness slider will still be at 100% but the top 20% just doesn’t do anything. I’m not sure how the slider worked before the update but I certainly never saw this sudden darkening and I don’t remember the phone typically being this dim in sunlight. Not using automatic brightness or the “extra dim” setting.
This happened already before the recent update, please see above.
I have seen 1 report saying it even happens when adaptive brightness is turned off.
To all: please #contactsupport to report this.
The slider doesn’t reflect the change for me, as affirmed by the other responders.
Yeah, I know that. That’s why I mentioned http://gitlab.fairphone.org; it’s their internal tracker and source repository. I only used the @ for future-proofing for if every they happen to create an account. It was some vague perfectionism.
Outsourcing explains well how issues such as these manage to not be noticed. My FP4’s software is seriously buggy, in not solely this regard. It’s noticeable, even compared to my old Pixel 3’s.
As long as they fix it, eh.
Anyone find hard using the phone in sunny days? I cannot see the screen because the brightness is too low. Is there a way to fix it?
Best you can do is to make sure dark mode is not enabled. The screen indeed doesn’t perform well in sunlight.
Further: Have you turned off Adaptive brightness to ensure you can manually select the brightest setting?
Nope, that works fine.
Yes, at least switch Dark Mode off from sunrise to sunset. Anything else does not really make sense unless you have an AMOLED display anyway.
I think thats new and was not the case last summer… Its def too dark outside. Or lets say its more like this, because suddenly while writing its brighter while the slider was already at max.
I had the same issues last year, there were discussions about it on the forum as well. I don’t think the brightness is different. Also retest indoors, then the max brightness is more blinding. But in daylight that light is just not enough. And at night the lowest is too bright But at least the auto brightness is better now (for me).