This problem seems to affect several users. Is there any chance that this problem may be fixed with an app update distributed by App Lounge, or by a patch version 4.1.x of /e/OS?
If not, is there a workaround? I have tried to describe two possible ones in /e/OS 4.1.1 error OAuth 2.0 on email server connection - #11 by Tentos, but I do not know whether they really work because I am not affected by the problem.
May users be informed about a workaround by a UnifiedPush message?
Hello,
an idea when A16 will be available on FP4 ?
Thanks.
That is great and I appreciate the work around these backup options. However 4.1.1 is still completely deprived from such options and current users have no ability to restore their seedvault backup until these new options will be made available. In the future, it would be great if the team could allow an overlap between introducing of a new important feature and eventually dropping existing solutions, especially on the stable channel. But itâs good to read this will be solved soon hopefully.
@Manoj Not sure that you have seen my post so I retry my suggestion. Please feel free to redirect me to another link if my post is not at the best place (I did not succeed to create an account to gitlab because my email has not been accepted :/)
I will request the developers to add this fix in one of the next releases.
Regarding the not being able to create a gitlab account part, please check this guide.
Dear @Manoj ,
would be sad, therefore there are still builds for dubai from lineageos
Best wishes Johannes
There is an option to set a server but when I tried to add my server it complained that there is no CalDav/CardDav available.
Iâm not sure what the requirements for the server are but I hope that with the Murena Backup Iâm able to backup at least app settings to my own server.
Contact and files are already backed up and should not be required by the backup solution.
when eos gonna update to lineage 23.2 @Manoj
We will jump to A17 instead of moving to 23.2. Team is working on customizing A17 for /e/OS.
Thank you for confirming @manoj, this is in line with what iodé are doing:
It could easily shift a lot of users onto an alternate OS if local backups are not available.
What exactly do you mean? There is a 4.1.1 update available for this device, but the device is on A13. So you mean the upgrade to A16 has failed? Permanently? I canât imagine that since Lineage and the other Custom ROM built upon Lineage all have successfully build A16 builds for this device.
Not permanently. The team keeps on trying to build for the device. If successful we release the build or it is moved to the next release.
Do you mean that /e/os wonât be based on LineAgeos ?
@Manoj This has been copy-pasted in every weekly development thread for the past few months but has some advances been made on this âdetailed documentâ regarding e/OS security policy? The last information on the topic dates back from July 2025.
Unfortunately, until the team completes the document, I cannot mention that it is complete. This was a heads up that such a document is in the works.
No, I did not mean that.
What was meant is that the LOS build for this device with the /e/OS customization failed to build. As you are aware we do not copy paste the LOS as is but add some /e/OS specific code to it. With that the builds failed.
The developers will try to build it but if it consistently fails, we may have to drop that particular device from the build system.
I will share the device names and code for the devices which we would drop so that those particular device users can make changes accordingly.
The thing is, this now leaves me as an FP6 user at the choice of either updating and loosing both my previous backups and the ability to create new ones with my preferred backup flow, or staying at an unpatched OS release not on the latest available security patch level.
Not a pleasant choice to make. And with your statement of not targeted for 4.2 it is also not clear how long I am stuck between this rock and a hard place.
I read there were no change between June and July âandroid security updateâ
Indeed, thanks.
There are no security vulnerabilities in this bulletin.
Thatâs helpful then for the decision not to update right now to 4.1. But if I am still faced by the same situation for 4.2, then thereâll likely be a security impact.