Thanks for this update (and all those for which I got too lazy to post anything).
Two quick notes regarding the “Remove animations” accessibility feature (on my FP3+ but probably true for many devices, if not all):
Since, I think, version 2.1, there is a big distracting animation when going back to the home screen, whereby the application that was being used “slides” back towards its home screen icon. This does not honor the aforementioned “Remove animation” setting and is therefore a bit so-so regarding accessibility. (Overall, this might be true for Bliss Launcher as a whole, but it is far more noticeable here.)
The visual glitch from 1.21 that I mentioned there Feedback for v1.21 - #223 by alice_m still exists. My current “workaround” is to force the menu to jiggle up and down by doing a weird little back-and-forth vertical swipe – this forces a full refresh of the glitched area.
The fact that these are my only “complaints” basically means that /e/ is great, though, haha.
(Well, my GPS has been acting kind of unreliably for 6–12 months but this might not be OS-related and investigating this is far from being my top priority right now. )
Late reply, but I tried all the solutions before I dared to post.
I did not mention it because it’s my personality to first try to find a solution by research and then post about issues. Born in the 1970s, you know.
Yes, the 3 dot menu for a local update is there, but the downloaded image .zip is declined. It says verification error. I downloaded it twice. I got a stable and fast broadband FTTB connection at home plus stable WiFi and the last time I got a corrupted download ever is over 10 years ago.
No issues shutting down or booting up, btw.
So I guess I have to wait until the next update is rolled out and see what happens.
I guess this doesn’t work because the downloads on the download page in case of your phone are images for installing with fastboot, while the updater processes the so-called OTA format (= over the air), which is different, so the verification error would be correct.
Already tried multiple times the first fix with no success. The second discussion does not have a clear set of instructions except for a new install from scratch but I would like to avoid this …
Vendor Name: Fairphone
Device name: FP4
Version of /e/OS or Stock which existed previously: none, came from LineageOS 21 for MicroG
Is the device Rooted / Not rooted: not rooted.
My issue is that changing the default browser does not change what browser apps use for embedded logins, and I use services that can only login when Chromium is used.
Yes, they fail in the final phase, either right before, or when trying to “report back” to the app, it also happened when I was on LineageOS, if I had Firefox as default browser. Our public apps (Denmark) are really picky in their auth.
Only Chomium or Chrome, some of them, not even with that, not giving a proper error, just failing.
I fixed my issue by disabling the built in browser via adb.
I used this method: https://www.xda-developers.com/disable-system-app-bloatware-android/
Now the question to the community, why is it so non-obvious and hard to get a proper download for a manual update because of a bad documentation?
Each single information piece needs to be pulled out of the nose of this board as it seems.
The official downloads are proper and are matching the official documentation for the manual install of your phone. While this procedure would successfully update your phone, the catch of course is that it is a new install and would wipe your data.
The community is currently helping you with your unofficial, undocumented way instead …
Vendor Name: Fairphone
Device name: FP3
Device CodeName:
Version of /e/OS or Stock which existed previously: /e/OS 2.4
Not rooted
I have the following problems:
Since the update to 2.4.1, I have had major problems with the battery charge level: The Fairphone reports at random times (even, for example, when the battery charge level is over 90%) that the battery level is low and switches the device off shortly afterwards.
If I then restart the Fairphone, it switches off again. It can start on the charging cable and then actually starts charging at 1% battery charge. Two different battery apps report that the battery is in good condition.
And a dramatic error message appears when I click on the button at the bottom right to view the photos taken: “Something bad has happened. The file could not be opened.” When I open the gallery app, I can view the photos.
As has been the case for years, the GPS positioning continues to work poorly.
Vendor Name: Google
Device name: Pixel 5
Device CodeName: Redfin
Version of /e/OS: 2.4v
The 2.4.1 operating system update has been working flawlessly for me on my phone.
Disgregarding the current growing pains with the Murena infrastructure, I continue to be very happy with the product provided.
Once again I wish to thank all those both officially and unofficially invovled in the project. My loyalty and enthusiasm for e/OS/ remains undiminished.
Vendor Name: Fairphone
Device name: Fairphone 3
Code name: FP3
Version of /e/OS which existed previously: 2.4-t stable
Is the device Rooted / Not rooted : Not rooted
The mail-app is buggy, crashes ever so often, mails already read show up as unread after a restart of the mail-app, and I can’t send mails, which is kind of annoying. How can I fix that?
Since some time (1-2 weeks) the app Lounge is not able to show any apps. It hangs at the first screen, sometimes complaining it cannot login (anonymous account):
Account unavailable.
Then I can ignore, but it refuses to show updates or allow me to search. Apps won’t update and start complaining they are old.
Yes, forget about the e.os project - it’s a noble idea but it’s not properly supported. The App Lounge is unreliable, the OS restarts randomly, and UI is eccentric. I’ve spent too many hours fiddling with this OS.
)
)
