Of course, I’m well aware of my own impatience haha.
For the record, I’m running with Orange network in France.
I don’t expect contacting support to speed up things but perhaps give me some insights as whether or not they know about update propagation, and/or if they can eventually provide with flashable OTA file in the event where some device would not receive the update.
I think there’s something wrong with my device: I followed the guide to microG replacement of Google native service.
After reboot the update was proposed to me through notification.
However, since I had trouble with maps not working anymore, I uninstalled nanodroid and reverted to regular Google service. After reboot, the update notification was gone and system update module did not want to find it anymore.
Edit: so I did a factory reset and update was available at first boot. I don’t know what I messed with my device but it appears I was not likely to receive the update the usual way
Hello,
I still cannot see the update in my FP4. Is there any way to install it manually?
I have installed the F-Droid store and a few Apps via this store. Does this prevent me from getting updates?
Thank you for your ideas and comments.
Moin
Here is still nothing going on.
Seems the same like the last update (A.091) for Medionmobile users to take 1 month.
So until january 21.
Let’s see if my fp4 still gets it or the G-free versions are faster.
PS: 1 month, … totally unacceptable,… we have 2022, 5G network and the gui is also no longer chiseled in slate
Or do i have to wait until the doorbell rings and someone is at the door with a disk or cd?
That will be nice
For what it’s worth, here’s an explanation of the support when I reached them about update not showing up. They seemed to point toward carrier responsability.
(It turns out it was my replacement of Google services with microG that stopped the update from coming for some reason…)
Note that support mistakenly mentionned fairphone 3/3+ when I specifically wrote about fp4 and the FP3Q.A update, but It think the logic is the same anyway.
For anyone really desperate to update (and not already on /e/), the update OTA from A.091 → A.094 recently turned up in a logcat by accident:
To be clear, I don’t suggest using it, there’s no guarantee that it works, but it might be useful for somebody.
If you plan to and have a unlocked bootloader
And post those hashes in that topic (before updating)
Or better yet, please dump the original recovery partitions beforehand, those would be great to help people that flashed TWRP by accident.