Yet I doā¦ Fairphone has form with buggy releases, especially lately (FP4.TP32.C.0144, FP4.QREL.15.15.2ā¦). This here reminds me of the FP4.TP32.C.0144 update, which was a reasonable 27 MB but was initially also offered as a buggy 2 GB download.
And no, there is no logical reason why my update should be that much bigger, Iām on FP4.QREL.15.16.1, the latest A15 FP4 patch level (AFAIK).
My phone mostly works, and I would like to keep it that way. 
Your choice.
I only said that though I did worry a lot and now finally updated to A15, everything works now fine and perfectly well for me and I consider myself a very heavy and multitasking user. 
Kudos to Fairphone for this update 
Same issue here! I was hoping this would be addressed. A month ago customer support told me the were working with proximus to fix it, so I was counting on this update.
I have to report two things Iāve seen only after applying the update:
As I wrote here (Software Update: FP4.QREL.15.16.1.20260220155828 š² - #108 by KleinerAdmin), I determine this two aspects already for a longer time (since the buggy 15.15.2 update);
reboot āhangsā and USB connectivity randomly drops and requires a reboot to be activated again.
I am too tired but if you want to report a ticket to FP, I will encourage you to do this.
From first reading āhangsā does not seem to Će to be the same as āshuts down instead of rebootingā
@deandrade what does āhangsā mean and how do you reboot?
However I still have no issues at all to reboot and I had 15.15.2 installed with zero issues.
āhangsā means, on reboot (manually or by system update), the phone shuts down and nothing happens any more. The screen stays black. Than I have to long press the start button to restart the phone.
You dont know what hangs mean for @deandrade
It could also mean it hangs before or after the black screen. Thats both pure interpretation and speculation.
ā¦ so letās wait on @deandrade 's answer.
It means the exact same thing described by @KleinerAdmin .
To be precise, the screen goes black (the phone seems to be off ā but Iāll wait to get this behavior once again in the darkness to see if thatās the case).
This doesnāt seem to happen all the times. In the last 24 hours I tried rebooting the phone 3 times: two in a row, with both reboots going well, and once after using the phone for a while. In this case, the issue occurred again.
About USB connectivity, I suspect this may be something else. My phone has had regular problems with the USB connector (I had to change in twice in 3 years and I fear I might have to do it again soon), so Iāll wait before blaming the update. Though the timing coincidence is striking.
In the meantime, at least one Proximus user managed to break out of this deadlock, read here. Hope that helps.
Today I wanted to test my USB connectivity with the internal testing tool, only to find out that the tool doesnāt start at all.
Am I particularly unlucky?
No the internal tests dont work properly since some time.
FP promised to bring them back. But ETA isā¦ FP ETA, so expect it in a few yearsā¦
Just got the update automatically, all went well 
Got the update yesterday on SFR Red (France), all went well. Nothing to report so far.
Since the update, Iāve noticed time and again that the power and volume buttons sometimes donāt work. When the phone is switched off, the power button always works to switch it on. When the phone is switched on, it can sometimes stop responding; a little while later, everything works again. If the phoneās screen is black and you canāt wake it up using the buttons, it works, for example, if you charge it briefly via a USB cable. The fingerprint sensor works smoothly at all times. Does anyone else have this problem?
I had this problem from time to time.
First, install Software turn off button app and volume app. Then change the settings of you Power button to start by just touching the Fingerprint sensor. In case the problem reaccure.
Then to the real solution
For me the problem actually was hardware related. The connection of the buttons had a glitch and by adding a folded piece of paper to press on it, the problem was resolved.
You can probably send it to Fairphone as well but I felt that was unnecessary.
For the sake of science, I bought a new USB module and installed it to see if it was indeed the root cause of my problem.
The answer is no: I still cannot use Android Auto even with the new USB module.
Just to clarify, I was able to use it before the software update, and I can use it on the same vehicle with another phone.