I think that one or the other could have been done better. Pointing your finger is the most pathetic thing you can do. Other devices that also have Stock Android as already mentioned the Nokia devices don’t have these ridiculous problems.
So if you did it clean and right, it would be possible. A question of motivation or quality assurance?
I don’t know, but what you get for the money here is just a disappointment. With all due respect to the concept, you won’t be able to keep your customers without clean software.
“Change is in your hands”
Good luck then… I’ll use my FP4 as long as it runs, like any smartphone I’ve had. If Fairphone doesn’t work on its quality, I can buy a Pixel phone for the money. At the end of the day, it has to work the way it was sold to you.
My FP4 was updated through the 4G network to the latest update of FP, including patch of April 5th. My FP4 rebooted but then keeps on looping with the FP logo, and finally nothing happens.
I tried to re-apply the OTA update you mentioned but there’s an error message on FP4 screen:
Now send the package you want to apply to the device with "adb sideload <filename>"...
Supported API: 3
Finding update package ...
Verifying update package ...
Update package verification took 3.6s (result 0)
E: package is for source build SP25 but expecting SP28
Install from ADB completed with status 1.
I looked at some manifest files in the .ZIP file and found information related to this SP25. But not SP28.
Is this SP xx the versioning of the security patch?
I found this reference on lineage. Where the move from SP25 to SP28 is made.
At the end, I don’t know how to pursue with this OTA file.
My FP4 has the bootloader locked, and developer mode wasn’t enabled (my bad).
My only chance is to make this sideload work so that the FP4 can bootup normally, if possible.
That’s a reference to the build number:
The OTA update you downloaded expected the previous version (SP25), but your phone is already on the latest release.
The update did succeed but something went wrong and rendered your phone unbootable, which should have made it fall back to the previous version, which it didn’t.
All right, I know it’s very bad form to berate somebody who suffers, but backups need to be made before the disaster…
Unfortunately backups are among those annoying, apparently useless things people always tend to put off until later because “they are way too busy right now”…
(That been said I’m sorry for your loss. I know today a lot of people tend to have everything on their phones, and losing it represents a major catastrophe.)
I am an American, I have seen screen dimming on this phone. I think this issue is in fact due to adaptive brightness. I’ve seen similar issues related to HDR on windows PC. This is usually a bug. It’s annoying at best. I hope they patch this in a future update. In the meantime turn visual effects off or something to negate this effect.
After updating to Android 12, the rightness of the display of my #fp4 randomly decreases, but eventually temporarily reverts to correct brightness, repetitively. The period of time during which its brightness is less than it should be is always greater than the period of time during which its brightness is correct.
This has solely started to occur after the Android 12 update, and occurred approximately immediately subsequently, so I have cause to believe that it was caused solely by it.
Yes I’m a US resident. I think the issue is a bug with adaptive brightness on this form. The colors somehow change In the motion photos. There was a bug with HDR with unrelated hardware mentioned above. Where the image did not display correctly on windows 10 a while back. Yes this post was relevant to this topic. I was also here to talk about screen dimming issue. I still think it was relevant. It was most likely adaptive brightness bug. Thanks.
I’m facing weird battery usage consumption (way too high) from time to time.
A reboot of the FP4 fixes it.
But it shouldn’t happen in the very first place.
The Battery stats says it’s mostly used by Screen and Chrome (in my case). But effectively, the device is overheating a bit too much from my taste (it gets HOT).
Rebooting fixes it, and using it the same way do not produces as much heat as before.
Difficult to say if it is app related or device/firmware related though
That usually means it’s a software issue: Some piece of software goes stale, and rebooting obviously fixes that, till the next crash… And since it happens regularly, it means that this software has been damaged, it’s not just a one-time error.
It could indeed be Chrome which has either been damaged at some point, or has some dodgy ad/spyware doing stuff in the background and crashing the whole thing.
Normally I would suggest to uninstall and reinstall it, but unfortunately the only way to uninstall Chrome is a sledgehammer, since it is a Google app…
What you can do, is to try to uninstall all and any add-ons (if you have any), and check for a couple days if the problem persists. If it does, uninstall and reinstall Chrome’s updates (the only thing you can), hoping that will refresh enough code to fix the issue.