Installation went fine, but I had no possibility to connect to Wi-Fi anymore at home. I have Mikrotik Access Points using their CAPsMAN method (wlan controller) and I could connect to them anymore with my FP2.
Other devices like windows10 laptop and an iPad tablet did still work fine.
Removed associations on FP2 and tried to connect, not possible, requests denied.
After puzzling with the FP2, I tried to experiment with the Mikrotik and it seems that with their software version 6.46 I needed to provision the configuration again, no changes in configuration are made, just the provisioning whereby the AP’s renewal their Wi-Fi configuration.
May be related to the software update changes from Mikrotik last week (or week before) and some security fixes on both sides.
I have gone through the update to 19.11.2, and here is what happens:
Download successful, APP says to restart to continue
I do so
Phone reboots to a “TeamWin” image, then NOTHING
I wait for 15 minutes, then open up phone, remove battery
turn on, phone boots as though nothing happened.
My guess: the update was not properly tested.
two SIMS in the phone, plus 64gb sdisk.
The zip file for the open->gms switch is part of the gms file set, and therefore has the same middle bit as the manual update for gms. The link to the switcher, however, gets published on the code site. I guess code.fairphone.com is updated by the devs, whilst the main site goes via web/support teams (and therefore can lag a bit).
Added: for anyone reading this in a hurry - don’t use files from fairphone open / code.fairphone.com for updates to regular fairphone OS.
Somewhat concerningly, it’s been a tad quiet on this thread. The bugtracker’s been quiet for the past three weeks, and I have not come across mentions of an upcoming beta.
My impression was that since the release of Android 7 the updates for the FP2 would come at 3 month intervals. That’s sparse, but with the FP3 being developed in parallel it kind of was to be expected. With most bugs sort of solved with Android 7 now, the main motivation for rolling updates is fixing security issues. Obvs they matter, but people don’t complain about them quite as much… so hereby, a bit of noise(!!!) Anyone knows whether there’s a security update on the way for February or the start of March?
Companies discontinuing support hasn’t stopped Fairphone before But thanks for posting that link, I was not aware of this. Still, it’s feasible and valuable to back-port relevant kernel fixes, as the kernel version is decoupled from the android version. Granted, updating a 3.4 kernel gets more and more tedious over time, but given it’s open-source software it can be done and all the helpful bits to this end are published on-line.