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
i also use the 2 options from the bugtracker site…
the flashlight option does not always work with my mobile.
Make sure the phone isn’t connected via USB or to a charger.
Else the flashlight workaround might fail to work.
Thank you for your advise. i did not have it connected at any of those times…
its a little bit frustrating, but i seldom switch it off nowadays.
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.
The bug was introduced with Android 7. Up to Android 6 this bug wasn’t there.
Ok thanks, but I had OS 18.09.01 when it got delivered, which is Android 7 I believe?
good to know anyway!
Correct, in a sense, as this would have been a beta version.
Fairphone officially released Android 7 as Fairphone OS 18.09.2 and Fairphone Open OS (the less Google variant) 18.10.0.
Was it really 18.09.1, or perhaps 18.04.1 (which would have been Android 6 and was the last non-beta version before the upgrade to Android 7 came along)?
Okay that makes more sense then. I believe it was 18.09.01, because I remember checking the new version ID number and thinking only the last number changed. But it’s not like I did a screenshot of it before so maybe I’m wrong. (maybe 18.09.01 didn’t even exist then?)
Anyway, I remember I did not experience much changes in the interface or functionalities, so I wouldn’t expect it being the update from 6 to 7.
There is zero official communication going on. I’m getting angry on the growing number of reported bugs and zero status updates or information from Fairphone… you are loosing your strongest part, loyal and confident customers.
I’m afraid that slowly turns into reality. What keeps my mood up is that my phone simply does what it should…but I am still on Lollipop…
Some official word is here on a rather high level https://www.fairphone.com/en/2019/01/23/whats-next-for-android-7-on-fairphone-2/
Thank you Ingo -at least you whow that our software team announces being at work on the next update.
But when you get to the bug tracker itself, you can notice
- still nothing has moved for seven months now,
- the bug itself is still not assigned to any person,
- and, worst of all, it is considered ‘minor’.
In my case, this ‘minor’ features means I just cannot offer the FP2 with the latest system.
I must say, in my work, this is better called a “show stopper” than a “minor bug”.
I still own Fairphones, various models 1 and 2, but am definitely halted on this for advice and distribution. I just distribute to family and friends -i. e. the people I can ensure a proper reflash before delivering.
And I see with some concern a situation where the devs themselve just do not trust their own evaluation panel (the very one from the bug tracker, where that specific bug is just the first one upvoted, and by far) and seem to consider all customers are geeks like them :
“after all, it works!”
Great news : the bugtracker guys now have allocated someone to this task (in other words, nothing happened until now by lack of any interest, but now, someone has taken the action)
Let’s hope this will translate in better news…
And now, for those of you that are beta-testers (which I am not) there is a fix proposed. If anyone of you testers can report…
(please insert here a smiley with a hopeful, staring look)
(the link I am not allowed : https://forum.fairphone.com/t/fp2-fairphone-os-fairphone-open-19-02-1/48239 )
I tested and so far it looks good. I shut down about 20 times and one time it rebooted, but I think I may have just accidentally pressed reboot.
I just wanted to note that as tempting it might be to make such assumptions, having been a professional software developer in the past I can 99% ensure you that the reasons for a seemingly lack of progress on an individual issue are hardly ever “lack of interest”. Besides having to juggle over 100 bug reports in the Android 7 tracker, communication on progress is a lot more finicky than it might seem; developers want to be as accurate as possible about a topic that they cannot assume the reader is an expert in, while at the same time maintaining realistic expectations that don’t lead to disappointment. This is easy to get wrong: technical stories get misinterpreted, the complexity of problems are underestimated by the reader, well intended timelines presented as “if everything goes right” soft targets are interpreted as hard deadlines, and so on and so forth.
The temptation for developers is thus often to “just retreat while I fix this stuff for you now, I’ll tell you when it’s ready”, which to the outside world looks like a lack of commitment or progress until the very last phase of “a fix is ready to test”. This approach isn’t great as it can frustrate engaged users, but very understandable from the developers perspective if the alternative leads to “punishment” by the very same users for not meeting expectations.
In recent days I can see that Fairphone is trying to be more systematic about their approach to communication. They have created wiki-pages explaining the lifecycle of a bug through the various statuses, what a transition from status to status means and how they prioritise issues. This is good: expectations are conveyed to the user in a generic manner decoupled from technical detail, and systematic communication is easier to deal with for developers. I suspect they’ll continue getting better at communication and with that, they’ll get better at telling you why a bug is seemingly left untouched for a while.
Coming back to the quote I highlighted: I’m sorry to hear that the team hasn’t been able to live up to your expectations so far. I’d never tell you you have no right to feel disappointed, but I hope you can appreciate that the process of bug fixing (yes, even fixing regressions, things they seemingly got right before) is filled with uncertainty on the way that sometimes is very difficult to communicate about. In that light, I would encourage you, as FP2 user to FP2 user, to reconsider the assumptions you’ve made as to why you feel they have disappointed you. It’s likely to be an oversimplification of the truth and, as a developer, reading an “accusation” like this would work demotivating if anything.
I’m personally going to look at the now half-full glass and cheer for the progress reported, hopefully there’ll be a released update in a matter of weeks.
I’m a software developer, too, and while I mostly do in-house software, the one time I developed software sold to consumers we had an external and internal bug tracker. So that people from the outside didn’t get to see all the internals. Of course it’s all guesswork, but please consider this next time before stating as a fact what RSpliet already quoted.