On what device? I’m on a FP5 and I STILL cannot find any updates, on V2.0 it says I’m on the latest available version.
Touch the refresh button atleast 4 times
Okay, I don’t know why that made a difference…
but it’s gonna try and go straight to 2.4.1, skipping the intermediate versions. I hope that goes well…
Because that’s how they apparently stagger the staggered release of an update.
The update server when asked by the updater rolls the dice and either says there is an update, or not. With the refresh button you can ask until the dice roll in your favour.
It should, in all likelihood, but be prepared with a backup nonetheless before any update.
Can’t, because in my version the backup doesn’t work…
You can always backup important stuff one way or another. Convenience is a different matter with this, though, especially on Android OSes.
My data is safe, that’s not the point. I can’t backup app settings and all that, or 2FA stuff. That’s the big nuisance.
But, to my relief, update went smoothly. Let’s see if the bugs are gone now :-).
@GaelDuval, FWIW : the quoted ‘update on murena.io service outage’, above, is extremely difficult to find (I’m not a regular user here).
I now have selected ‘watching’ and ‘pinned’ it (for myself), although as nobody can comment it, probably this will be of no use.
I am a bit fearful that this trouble expands to /e/OS credibility.
Having to retry hours and hours before getting the last update wasn’t a critical issue for me, nor even was the fact of not being warned that the second update was useless for me (and an extra overload for you).
But really I believe the key issue here is how to maintain /e/ credibility,
For instance, I think maintaining Murena.com becomes extremely important, since that’s now the only contact you have with potential users for /e/ and potential customers for the phones…
And I believe the server for Gbyte-sized /e/ updates should not be based on Nextcloud, however we love them. It should be a plain ftp server, basic and robust…
Meanwhile there are some problems.
The Bluetooth connection has some malfunction, it doesn’t connect to headphones like it flawlessly did before, only after several tryouts the connection gets established.
Also there were several calls that crashed for no apparent reason.
Any others? Any idea from the devs?
- Vendor Name: Fairphone
- Device name: Fairphone 4
- Device CodeName: FP4
- Version of /e/OS or Stock which existed previously: Unsure, update from July I think
- Is the device Rooted / Not rooted: Not rooted
Update went smoothly, no issues observed. Even better than no issues - after my last update the speaker stopped working. I thought that this was actual physical damage as I had been on the beach with my phone around the time it stopped working, so I was very surprised to find my speaker started working again after this update!
Fairphone 4
The device is not rooted.
Hello
I now have 2.4.1.
But my @e.email is still not working.
Regards
Pehbeh
I finally got a crash to boot animation. Nevertheless, frequency has dropped significantly.
Vendor Name: Fairphone
Device name: Fairphone 3+
Code name: FP3
Version of /e/OS which existed previously: 2.4 dev version
Is the device Rooted / Not rooted : Not rooted
Installed on 25.09.24 while charging, install time 0:50 hrs, display on 30 minutes shut off, only the timer app was broken as long as the new version had not rebooted.
No issues.
- OnePlus
- 8 Pro
*instantnoodlep - Android 13
- Not rooted
Calling Volte is working.
Wifi is not working…investigating- fixed.
Yes very well go ahead !
Thanks for pointing this out. I have to +1 this. Also using the Fairphone 5.
I just thought the new update put some load on my brand-new fairphone that it just couldn’t handle, but now I see what the problem is. Thanks for the heads up.
My way to go around this is by always activating battery-saving mode, which sets the 90hz setting to “no schedule” internally, thus keeping a 60hz refreshrate, which is more than enough for me and much better than the choppy 20-30hz it shows after unlocking.
Edit:
Wow. I just realized that the problem only occurs when enabling smooth mode (Which was enabled by default), so I thought this is just how it works, when I don’t have battery saving mode enabled. Just turned smooth mode off and it works fine. Uff.
This probably happens for all, one has to ask helpdesk to help onboard manually as this advice:
Unable to update
- Vendor name : Fairphone
- Device name : Fairphone 4
- Device code name : FP4
- Version of /e/OS : 1.21.1-s-20240325389527-stable-FP4
- Not rooted
Updater will not show new versions even after refreshing and/or restarting the phone.
Please help me.
Please first try
Settings > Apps and notifications > See all … apps > 3 dot menu top right > Show system > Updater > Storage & cache > Clear storage … that is Storage and Cache.
If this fails, it seems that this has been reported a number of times with a Fairphone recently.
I searched issues for #FP4 and #/e/OS Updates and found no open topic, there is this closed issue from a year ago Updater cannot offer new update (#6540) · Issues · e / Backlog · GitLab.
As you have a stable
build; does this signify that you bought the phone from Murena? If yes, you are a #Customer you could contact helpdesk [1] and / or Report an issue.
[1] Address at foot of Support topics
Same her, refresh it frequently goint way down, have to reactive smooth display manually…
Seems to be related to sleep mode.