This is good news! Holding my thumbs, toes, and all the lucky body parts for random reboots going away now.
Some feedback for this release though:
Only calling it “Special update” in the updater looks impressively suspicious! I had to go here and look it up before touching anything else. And related,
A new update should have a new version number increment. Having different sets of software with the same version number is a great way to create support headaches. Somewhat redeemed by the “Baseband version” but I would’ve preferred the version number people sees and knows got incremented when you did an update. Even if it’s just 18.2.0.1 or 18.2.0b (easiest would’ve been 18.2.1 ofc).
Don’t let this feedback cloud the main point here though: Great work!:))
After a couple of hours after updating my new Fairphone 2 to the 18.02. special update my screen stayed black.
Manually installing the binary image “Fairphone OS 18.02.0 (Android 6.0) (~650MB)” using the computer solved the problem for me.
Now the update app on the Fairphone wants me to update to the special update again. But could the dead screen be some problem with the driver of the new Fairphone screens, that comes with the 18.02. special update? Did somebody else experience anything like that?
However thank you so much for your steady work Fairphone!!
Maybe downgrading or updating again to the already applied newest software could be added to the list of solutions? Because it only mentions updating when the Faiphone runs older software
This sounds like we should expect performance regressions, which seems logical, seeing that memory timings are tweaked to resolve the issue if I understand correctly. Not that I’ll notice much for the use I make of the phone, unless it’s really significant. But I’m still curious to hear if those who installed the update noticed any of that.
My phone is randomly rebooting once a day also, but it is a bit older than the August 2017 date usually cited for this particular bug: It was replaced on warranty in May 2017. Do we know if there were already affected phones in the circuit at that time, just maybe not in retail?
No, it does not (seem logical). I doubt that there are notable performance impacts. If I understand it correctly, the timing of the memory interface was changed, and I think @Douwe’s “performance” is more about how this update really solves the reboot problem.
I think (maybe @Douwe) can confirm this:
The version number was not incremented because of the needed google verification. If only the baseband is changed, the verification (which costs some days) is not needed again.
A rather basic question: if my phone is (quite a bit) older than August '17 but I do experience random updates, should I install the update or ignore it?
I installed also the special update and i notice the that the battery drains more quickly then before that update … actually I do not get one day usage with a filled battery
If I was you, I would skip this update. The change will be included in the next regular update anyway. And if your FP2 is too old, I’d say it’s unlikely the special update would improve the situation for you.
The ‘new’ display modules were already supported since the September update, I think something went wrong during your previous attempt and you can just update again.
Having an older Fairphone 2 of August 2016 I can tell you that the memory update didn’t cause me any problem, I see no difference in behavior whatsoever after the update.
After doing the special update I had one day with only one reboot and now on day 2 am back to constant reboots, meaning it feels like every five minutes if I am trying to use the F2. This renders the phone basically useless. Battery is quickly drained, Any suggestions?
