Oneplus
8 pro
Iceman
Actual e\OS 1.21 r
Update e\OS 2.1
I tried two times, it didn’t worked it stock in the page say Start it reboot and comeback at the same page before the update was automatic. I found the way to turn on the phone and I have to download the update again.
Thanks for your reply, sadly this doesnt work for me…
It would also undermine the privacy aspect of staying in airplane mode to not connect to celltowers to find out your location.
But i dont get how an OS update is rolled out while these level of bugs are still in them(software engineer here).
I literally have been resetting my phone every 15min the last days…
@Manoj can you please look into this critical issue?
Issue 1
Callers get tagged as “Unknown”, even contacts I have saved. I have turned the “Block calls from unidentified callers” off. Turning the feature on and off does not help. This started the day I updated to 2.1.
Issue 2
Trying to remove a number from the blocked numbers list in the e/OS SMS app results in me being taken back to the overview of the numbers, then if I try again, the app crashes. Removing numbers from the phone app/call app functions (why do they have separate block lists?).
Account manager sync often ends up producing a davx5-debug.zip file.
I can’t send it to gitlab since there is personal stuff in it.
Is there a mean to anonymize it ?
Other than that, no extra problem but still the annoying echo in call when speaker is on.
Device Name : Fairphone 5
Device Code Name : FP5
Previous version of /e/OS: 2.0-t-stable
Device is not rooted
Update to 2.1-t-20240603406607-stable-FP5 with no problems.
Everything I’m using is working on the phone.
On my Laptop (connected over USB-Tethering) there is now a 5-7seconds lag for the Internet-connection since 2.1. My Laptop Setup has not changed.
Anyone else see this?
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 2.0-t-20240508399779-dev-FP3
Is the device Rooted / Not rooted: Not rooted
Vendor Name: Google
Device name: Pixel 4a5g
Device CodeName: bramble
Version of /e/OS or Stock which existed previously: 2.0t
Is the device Rooted: Not rooted
I haven’t dare try this update on my FP5 yet after reading some of these messages… do we know if the devs have a revision of this update incoming based on current feedback?
Fairphone 3+
FP3
Update from v2.0-t-stable to v2.1-t-stable
Not rooted
Update straightforward and completed within 40 minutes.
Initial testing of basic functions & apps shows these appearing to be working fine: wi-fi, mobile data, bluetooth, GPS, phone, message, mail, browser, camera, app lounge and various other apps.
All looking very good so far, thanks again for all the good work.
Under Settings → Display → Dark design → Pure black does not work.
Then the power consumption of the displqy seems to be very high. More than under the stock software.
the adjustment of the display brightness is always too high, even in the apartment it is always at 51% and that is way too high, the manual adjustment does not help either because it is always adjusted again immediately.
If you set the brightness from auto to manual and then back to auto, the sensor recognizes the correct brightness and adjusts the display accordingly, but after a short time it returns to 51% brightness.
standby energy consumption is far too high. Under stock I only needed to charge my FP5 for 2-3 days, now I’m only at 18 hours, even though Google and everything else is gone.
These are the 4 problems I have noticed.
I went straight from stock to /e/OS 2.1. Bootloader is also locked.
Checking if the issue with FP5 has already been reported on Gitlab
Do not see an issue created. Pl can one of the impacted FP5 users create an issue in gitlab with details. Developers can then check for the reason for this regression.
If your problem persists and no solution comes up here, you might also want to give it a try over in the Fairphone Community forum (make sure to mention you’re on /e/OS). There’s a permanent topic on all things hearing aids and Fairphones.
I have t he same issue with Blocked callers on FP4, with the same results as you. If you need to remove a block, install Fossify Message, make it your default and import your existing messages, then you can delete the cache and data of the original app, and then switch back.
The four ticks are created.
However, when I look at the complete post here, the power consumption of the OS seems to be rather high for all users, and it doesn’t seem to be a device problem either, as the increased consumption affects a wide variety of devices (Asus, Google, Fairphone, etc.)