One small bug though: It shows under apps and notifications that I have one app with notifications turned off. Unfortunately Android doesn’t show which one. But I scrolled through all of them and there is no app with muted notifications.
Just had mine, too. How many of us got it right at the last moment, when FP declared the roll-out complete? anyway, there now, some exploring to do when it’s settled down!
Everything went smoothly with my update, thank you so much!!! Some apps seemed to be running slower than usual in the beginning, but now after some days it’s back to normal. A banking pin number was lost during the process, strangely, but I could reset it. So - no big issues.
FP2 running for 5 years now. Great.
Does anyone have experience with a encrypted phone and the update to Android 9?
I only get my company emails and calendar via Microsoft “Unternehmensportal” which needs an encrypted phone. Do I have to decrypt the phone before?
From what I remember in other forum topics and from what @anon83191809has said above you should do the upgrade with your encryption ON. From what I have read, encryption is currently not possible if you decrypted it before the upgrade:
As I said: My own FP2 was already encrypted with A7 and it updated quickly and smoothly, without any problems.
While the one of my wife, also being encrypted with A7, when rebooting after the installation of the new OS forced us to do a complete reset, and it said this is due to the encryption. No way to save the data before that.
Well, she has a newly installed FP2 by now with A9. While I have an updated FP2 with A9 that by the way does a lot of spontaneous reboots which is a bit annoying…
There is a bug where inputting the wrong encryption PIN can cause a message that the data is corrupt and prompting for a full reset (instead of saying the PIN is wrong) - however if you cancel out of that and put in the right PIN, it will unlock successfully. So it may be that your wife’s phone didn’t need to be reset. I hope that issue can be fixed as your situation is a perfect example of how it will lead to people losing data!
Have updated to Pie successfully.
The FP2 now asks me to enable Open GL ES 3.0. Do you recommend to enable this or should I better dismiss the request?
A report of my first experiences and impressions will follow soon.
I see that the path to the individual support pages is given at the top of the respective page, but I don’t think it’s obvious or clear enough to not confuse people landing on an Android 7 page coming from e.g. an internet search or a forum link.
Can the Android 7 support pages perhaps get an obvious (red, bold) pointer saying that the page refers to an old OS version and that there’s a more recent one, with a link to the distinction page?
Searching for ‘fairphone android 7 support’ does take me to the 7 support otherwise I get the choice your links point to. I’m not sure I get what you mean?
Apart from the really unremarkable “Support → Fairphone 2 (Android 7.1.2) ->Using OS (Android 7.1.2)” path near the top of the page there’s almost no hint that this page is about Android 7, and absolutely no hint that there is an extra version of this page for Android 9.
Let me be an unsuspecting user wanting to install Fairphone OS manually, possibly I found a link to this page in the forum where it was proposed as a solution to an issue … ok, the page tells me how to do that, check … it says Fairphone OS 19.11.2 … like I care, the page says it’s an upgrade, so it seems new enough, check.
But what if I have Android 9 on the phone already?
I think this is bound to lead to confusion.
I didn’t target my initial request to update the links on the pages at support either, and it seems to have worked out fine nonetheless .
You’re right, of course, but I’ll leave a support request for when I have an actual example of confusion, it may still be that I’m concerned for nothing.