As I mentioned in the first post, not all bugs are listed, and we will be working on updating the list.
The fact that an issue isn’t listed doesn’t necessarily mean it’s low priority. It just means it isn’t on the public issue list.
Well apart from asking Fairphone exactly why the list is as it is, then it will remain a mystery, and of course any answer could and would likely be questioned/challenged and would not really help in the fixing.
Similarly this subject is really just a sound of by users I suppose
The Public Issue Tracker and website have been updated. You now will be able to have a broader overview of the high and medium priority bugs we are aware of. The list will be updated around every 8 weeks.
Please, read the statement on the website thoroughly as we explain different matters such as what high and medium priority means or what if your bug is not on the list, among others.
Hope this work helps to better understand where we are now and sheds some light on the topic.
Hmmm, I’m not sure I fully understood your question. But if I got it right, your complaint has to do with the fact that locking the bootloader may brick the phone.
If that’s the cause, then we’ve confirmed it before: installing software with an older security patch than the one you had before will trigger Android Rollback Protection. This is a well-established security feature since Android 6 and we’ve made numerous warnings about it. It’s in our support articles.
In addition to that, it’s important to keep in mind that when installing software manually there are risks such as random data transfer interruptions (bad cable or power stops), buggy software, etc.
However, if you are talking about a reproducible bug we weren’t aware of, we’ll be happy to take a look. For that, please contact our amazing Customer Support team who will be keen on taking a look.
There is a lower than 1% chance that I’d be the first person to submit a ticket about that issue if I did so, so no, I won’t be doing that. People have literally sent their devices in for repair over this, so trust me, the customer support team is aware.
Here are three threads full of people detailing the issue. Basically, if you lock the bootloader then in some cases the bootloader goes from unlockable to not unlockable. This has nothing to do with the rollback protection, as is evident by the fact that every other phone I’ve ever had hasn’t had that issue. Generally, if you lock the bootloader then you should be able to unlock it again if something goes wrong. Currently, the Fairphone 4 doesn’t work that way.
Here’s a post by hirnsushi that describes it better than I ever could: