As this is a community forum, for official statements #contactsupport . that is also advisible, because the more “complaints” the faster solution.
4 Likes
Just because I thinks its not really mentioned here: have you all the auto brightness activated? If so what happens when you deactivate?
I think this behaviour was already discussed here, but don’t find the thread.
I had this also one, twice.
Changed default launcher fixed it for me. Never had it thereafter.
But, I also deactivated all google and unneeded apps and use only FOSS Apps and f-droid
So, means I have no standard setup for reference.
Yep you mentioned it, but had the feeling it was not really tested, so thought I throw it in again😉
However maybe it was tested without success (was not sure about the comment meaning)
Yes I mentioned trying toggling the Adaptive (auto) Brightness as well as switching to a slew of other launchers didn’t do anything for me only the morse code powerbutton camera trick worked so far I haven’t yet taken the time to factory reset the device (the problem with having a solution now is that no matter how stupid it is, it works, so it’s hard to go on and erase everything to start over ^^)
4 Likes
I got the same Problem, my solution was to disable doze_always_on.
You can check if its on with
adb shell settings get secure doze_always_on
and to disable
adb shell settings put secure doze_always_on 0
I too did a restore from a backup (Pixel 3). I could not believe there is no other solution other than a factory reset so I invested some time. 
PS: or you could use the App
and disable “Ambient Display”
Hope this helps!
greez n3utrino
13 Likes
Thanks @n3utrino_ch for putting the time in on researching this (this would have been my next step, glad someone beat me to it though).
I can confirm that this was the problem and that the solution above works. (I haven’t tried the app “System UI Tuner” just the adb command line)
So to anyone restoring from an always on display enabled phone and getting this issue, this post should be pinned or put forward as the working solution.
8 Likes
Thanks for this, I haven’t managed to get it to work yet as I’m new to all this. How long before they do an official fix, in your opinion?
Did you try the solution with the app I linked?
It does the same thing the command line commands do.
You can delete the app afterwards and the setting stays.
The whole adb settings abracadabra was just to show what the low level offending setting was.
Concerning an official fix I don’t know.
1 Like
Your solution isnt the issue. I’m a bit useless. I got the app but tried to get the root on my laptop except it’s a pixel slate. Wasn’t sure which OS it uses. Will try property in the morning. Thanks for reaching out.
1 Like
Thank you @n3utrino_ch
I had the same issue and this solved it!
However, I really like the ambient display feature and think Fairphone should resolve this glitch asap.
Thanks again.
Good the community found a workaround. Everyone who has a ticket open with Fairphone, please inform them, else it will be difficult to fix it.
1 Like
This is not a full solve. Not everyone will check this forum. This needs an official fix and soon.
1 Like
Yes for sure but you must tell this Fairphone, this here is just a user forum. And when they are aware of the workaround they might be able to fix this faster.
suggestion for goodness: the mods or admins may always have a hot wire in the development, right?
They could also pass on such information.
Or am I totally wrong here?
This seems to have worked for me as well. No other solution worked - auto brightness, different launcher, … Wasn’t prepared to do the factory defaults reset and set up my phone from scratch just yet, so I checked this and lo and behold, I had Ambient Display turned on… Coming from a Pixel 3a backup restore. Hasn’t happened since I disabled it.
1 Like
This worked for me. I did use the wizard eventually and that is working for me.
OP here…
Today I got a replacement FP4 and I wanted to try if it would actually work without any magic. I first used the phone for some 8 hours without Google login and everything was working just fine. Then I did a factory reset and migrated my account from my Pixel 4a to FP4 and immediately it stopped opening the screen. So this confirms my assumption that this was not a HW issue. Probably your are right and it has got something to do with the (Pixel) settings migration and ambient display.
I guess it’s time to play some adb games 
edit. I also reported this thread to the support on my open case
5 Likes
Hi I just had the same problem with my new FP4. I imported my old account from my pixel 2. The solution was simply go to settings on my pixel 2, turn off always on display and make a new backup. Now it works fine 