I enabled automatic system updates, still get the error on update… Tried to restart the phone, delete caches and a bit more… I’m confused
Edit: okay, I needed about 10 tries with very different preparation, now it worked
Many people reported that it helps them to enable “automatic system updates” in the developer options…
However, it didn’t help me, I’m still struggling
Edit: I needed about 10 tries with different preparation… Now the update worked.
Edit 2: message above and below this message got merged from another thread
1 Like
Just a few minutes ago I got the notification of the update again and this time it could reboot and update. 
2 Likes
No problem updating at all - and I got it pushed on my FP5 first thing in the morning even though I’m roaming in Spain with my German contact. So, everything fine.
Worked after enabling developer mode and automatic updates. That shouldn’t be a requirement though. Many of my apps dont work with developer mode on. Official updates should just work without needing to make changes to your phone.
you can disable developer options after enabling it.
Indeed, this was a weird bug, i really hope it wont happen again.
1 Like
I already have - and yes hopefully next update will just work!
Yes, the same problem on my phone, too… o_O
Now we have the case that there were already some submissions from users who could not install the new FP5 update and had to try a workaround, which feels strange. Now these topics have all been moved to another forum where hours later a staff member announces the new update.
In the end, I just wish that it would also be clarified whether you still have a safe device when following it, and above all what the problem was… and what else there seems to be.
Sorry, but this merging of topics without sense feels just as wrong!
We dont merge without sense, please accept the forum rules to keep things together and have not duplicates what the official post was.however it was kept instead of the old one as it was the official one.
1 Like
instead of the old one as it was the official one.
OK, I get it: You mean “official” as in “please move along, there’s nothing to see here”?
Or in other words: If you find out that something is wrong hours before posting… the already known error should be mentioned at the #official# beginning, too.
My wife’s phone just did the update without any issues, so it can work out of the box, too.
2 Likes
What would you have written now if it hadn’t worked as expected… especially since it was previously reported that some BETA testers had the same problem?
Something like this:
Well, as a normal user I’m also a beta tester and that’s a good thing!?
1 Like
This:
I don’t have insights into the beta program, maybe at some point in time the reports about those issues were low enough to continue. I’d be worried if the failing update had left my phone unusable, but that wasn’t the case. I’ve seen plenty of updates both on my FP2 and now on my FP5 and none of them ever broke anything for me. While I’m not happy to see this error and would prefer to not have this for every update from now on, I’m relaxed enough to not question the whole device and company just because of that. I’ve seen bigger companies struggling and I know how hard it can be to track down issues that only occur randomly (and then often not on the devices that the developers have available). Nevertheless, some feedback from @Ioiana_Luncheon or someone else at Fairphone would be appreciated, though.
8 Likes
> Nevertheless, some feedback from @Ioiana_Luncheon or someone else at Fairphone would be appreciated, though.
That’s exactly all I care about… and also a bit about the fact that in the mills of the forum the people concerned don’t find all this information when they look for it.
1 Like
I think the android is different, like shortened, that you can see only the head/upper half. But it’s such a short time it appears, one cannot be sure 
1 Like
Here I am to give feedback
We have been in contact with Google in the past days as the issue originates in the update service itself and we have received a patch that should solve the issue for future updates.
Specifically for this one, however, there is no fix planned for this update, as it is impossible to apply it retroactively.
What happens, in short, is that the updater service, sometimes, selects the wrong package to download and thus the update fails.
Waiting some time or selecting ‘Automatic system updates’ (aka the Developer Mode workaround) helps to clear the cache and consequently download the right package.
24 Likes
“restores wideangel in 3rd-party apps” - neither in XCamera nor in Open Camera it seems to work- 
It works in open camera
