This bug is months old if you count beta versions of Fairphone’s Android 7, and even a lot older if you consider LineageOS on the Fairphone 2 (which has the same bug since bringing Android 7 to the Fairphone 2 last year and with the bug still being there this year with Android 8).
There’s no evidence supporting that it will be fixed in the next update … but then there’s no evidence against it either, so I like your optimistic question here much better than people complaining in the bugtracker about how this should have been fixed already.
Sometimes things just aren’t simple, and supposed entitlement to a solution doesn’t help in bringing about a solution.
Mine doesn’t do that either, I’ve had to take out the battery when I’ve been at the movies or theatre. Now I’m at the opera and will check if the flashlight trick works.
It (flashlight trick) worked weel few times for me but I just noticed right now that it doesn’t work anymore !
my FP2 does’t shut down (restarts automaticaly)
I ve also an issue with GooglePlayServices update. Some apps (ie: garminConnect) aks for update. I don’t understand when this update occurs ? everyday ?
GooglePlayShit seems to update only on wifi, not on 4G/LTE…is it linked to my issue ?
As funny as that screenshot is , could someone please provide a neutral looking (and more complete) screenshot instead? Lesser experienced Android users will inevitably think the Russians are coming, so let’s just avoid any avoidable confusion for them.
Ideally, just include your screenshot right into the first “Power issues” section here:
Correction :
Now that was a unique case, when it did turn off.
Repeating the test shows the reboot again .
With “Torch Light on” it shuts down.
The world is not in order, but consistent
BR Erich
Thank you for the workaround. I first tried it several times without success. I tried on more time turning off the bluetooth, and then it worked perfectly. I can now use the workaround with bluetooth on…
Strangely enough, my brand new FP2 from November was shutting down properly until I installed the last update early December. I’m really confused about the fact it was working before with the previous OS version, but not with this one.