Hi there,
this request addresses the /e/OS infrastructure rather than the OS itself.
Each time a new release is available, everyone attempts to download that new release. Apparently, this causes a significant overload on the servers distributing the images.
As a result, the download aborts frequently (currently every ~100MB on average; the chunks had been larger last night). Yes, the updater allows for resuming the download but this always requires user interaction. What’s more frustrating: After spending some 80 minutes for downloading (and making the update resume frequently), the downloaded image appeared unusable. This has happened several times now and is thus probably caused by some data corruption in the context of abort/resume.
In consequence, users will attempt to download the same image several times causing even more server load.
Do you see a possibility to implement some improved bandwidth control which avoids closing a connection once it has been established?
In the feedback for V3.3 thread, you said “I downloaded the OTA image via wget and updated to 3.3-a15-20251210556408-official-FP6 via that local file.”
Is the procedure for doing this available anywhere?
I’m very new to /e/OS (got the Murena FP6 a week ago and previously I used a 11 years old FireFoxOS phone ) .
You don’t say what phone you use. I have done probably 50-75 updates of phones over last few years and never once had the issue you mention? What phone are you using?
I did not intend to get server bandwidth control myself. My post was rather meant to be a recommendation or strong wish for murena to implement a better bandwidth control than “just accept all connections even if that causes server overload” (which seems to be the current policy). I’d expect that simple rules like “allow for maximum n concurrent connections and serve these reliably” would easily and significantly improve the situation and reduce the overall amount of data to be transferred.
I am well aware of murena’s size in comparison with the big players. Therefore I did neither complain about some unbearable user experience when upgrading (or similar heated comments) nor requested more and better servers but focused on potentially easy measures which do not require large budgets.
BTW, I’d expect that the “Request a Feature” category is monitored by murena folks (albeit maybe not on a daily basis) and that certain well known persons already receive enough notifications…
It’s a Fairphone Gen6 (official, preinstalled). However, I don’t really think that the download problems are device specific: just read the feedback thread for 3.3 and scan for reports of download problems. Furthermore, wget was running on my PC (rather than the smartphone) and reported “connection closed” every ~100MB.
Have shared the concerns of user regarding the slow download speed with the team. The reason is the large number of downloads that start with each release. Will share all the inputs provided in this and other threads on this topic with the teams and get back with the response.
) .