Week 12, 2025: Development and Testing Updates

[Manoj]

Summary of weekly development and testing activities by /e/OS developers and volunteers. Updated content has the emoji.

Server outage

Current status:

• Email: send and receive working

• OTA device build download: Legacy OS builds like Pie, Q or R are not available.Users may get a file / page not found error if browsing. We will try to add these builds. ETA of when this would happen will be shared.

• Murena cloud services and File Drive access :

  • Restoration of access to Murena cloud for premium services and users who made donations
  • Restoration of access to Murena cloud for free user ongoing.
  • All apps enabled on the Murena Cloud Dashboard. The sync for some of these apps may not be working for now.
  • The MurenaRecovery folder will not be visible right now. It will be enabled ASAP.
  • Team is working on enabling third party app access.
  • This week we start work on sharing access to users with IDs with the initial alphabet from p-z. This was the portion of the storage where we had the issues, that triggered the outage.
    -The slow progress is because we are being cautious with the opening up of the drives to avoid unexpected data deletions or data loss.

• We will share a plan to compensate the loss of service to paying users. The details will be shared by the team over email and through our channels

Read Gaël’s explanation and updates for the outage

Release

v2.9

Status: Testing in progress

Tentative list of issues and updates to come as part of v2.9

• Multiple builds will show up in this filter as we go through multiple builds to test fixes. Bugs may be added or removed based on the quality of the fix.

Upcoming releases

• Tentative release dates of builds that will come in the future

/e/OS Installer

The /e/OS installer has replaced the Easy Installer. You can check out the /e/OS Installer guide here.

Ongoing development tasks 🆕

• /e/OS V or Android 15 related code work in progress. No ETA available on completion.

• /e/OS GSI on T or Android 13. The team is working to see if GSI can be made available OTA. An app to detect what works and what does not work with the GSI is also in the works. ETA for release will be shared

 

Previous 5 releases & user feedback

• 2.8
• 2.7
• 2.6.3
• 2.5
• 2.4.1

Murena Cloud and Self hosting

Murena cloud current version : 28.0.9.6

• The deployment to Nextcloud 28 was successful, bringing better performance, numerous fixes, and exciting upgrades.

• You can view the full changelog here: 28.0.9.6 · e / infra / ecloud / nextcloud · GitLab

• Issues raised by users are being looked at by the team.
  Upgrade on work for v29.xx in progress

Self Hosting current version v 26.0.8.23

• Release notes

• Check this guide for help with the upgrade
  Next release - team to plan this development activity. ETA’s will be shared.

  • The self hosting guide is outdated. We will have that updated ASAP.

How to check the NextCloud version click here

You can find the complete documentation and current NC version under Login – Murena >> NextCloud xx user documentation. The xx should show the latest version.

• Another way to check the current version is to check the NextCloud scan link and input https://murena.io this should display the current version number as well as the security level.

Please note if MurenaCloud patch number is not the same as the NC patch number, the rating would show up as bad \U0001f610 This is not exactly a problem. We do not immediately jump to the next NC patch as soon as it is released. We first test it and then set out with the deployment.

GSI

• Current GSI version is on /e/OS Q and v1.17

• Download available here

• Sources available here

GSI OS version will next move to T or A13 skipping the R and S . Team is working on /e/OS T GSI. Will share release dates once available

 

OS OTA Related information

Completed

• Fairphone: FP4 : S (A12) to T (A13)

• Samsung: S9/9+ : R(A11) to S(A12)

• Gigaset: GS290 : Q (A10) to A 11 (R)

• Oneplus: avicii : A12

• OnePlus : avicii : Q ( A10) R (A11)

• Fairphone: FP4 : R ( A11) to S (A12)

• Fairphone:FP3 : R (A11) to S (A12)

• Fairphone:FP3 : Q (A10) to R (A11)

• Samsung: s7 / s7+ : Nougat (A7) to Q (A10)

• Samsung: s9 / s9+ : Oreo (A8) to Q (A10)

• Samsung: Galaxy S9/9+ : Q (A10) to R(A11)

• Samsung: s8 / s8+ : Pie (A9) to R (A11)

• Teracube: 2e / zirconia: Q (A10) to R (A11)

• Teracube: emerald & zirconia : R (A11) to S (A12)

• Samsung: S7 ‘herolte’ ‘hero2lte’: Q ( A10) to R (A11)

• Google Pixel ‘redfin’: S(A12) to T(A13)

• Gigaset: GS290: R(A11) to S (A12)

• Fairphone: FP3 : S (A12) to T (A13)

• Samsung: S7/7+ : R(A11) to S(A12)

• FP4: T (A13) to U (A14)

• S8/8+ R (A11) to S (A12)

All OTA OS upgrades are on stable or official builds

Testing

• OnePlus : avicii : S ( A10) U (A14)

To be planned

• FP5
• FP3

Our definition of an OS OTA upgrade

Usually for /e/OS ROMs to upgrade the OS you have to do the following

• If available download the correct OS build from the supported device list

• For some devices you also need to download the stock ROM from the vendor site.

• Take a back up of your data

• First install the Stock ROM

• Next install the /e/OS ROM. Here you can take help of the install guides available on our documentation site.

• If required apply the backups you downloaded before starting the whole process

An alternate to this tedious process is where we offer the user the option to upgrade the OS OTA. This option is available for stable device builds only.

This process is easy for the user but requires a lot of development and testing effort.

Different /e/OS build types

Misc information

• eCloud real time availability status

• /e/OS real time availability status

Helpdesk services - Exclusively for paying Murena customers

Murena helpdesk services will be exclusively for

• Customers who purchased Murena devices
• Paid for a Murena cloud account
• Active donors from past year

Paying customers can write in here with issue details

Users who use the /e/OS or Murena cloud for free will have the following modes for issue resolution:

• This Forum
• Gitlab
• Telegram channels

Free services users will also get assistance on this forum for issues such as:

• Gitlab Account opening related issues
• Murena Workflow / cloud account issues

Please note, the old helpdesk emails ID’s are not monitored any more

Device and Vendor specific Announcements

Gigaset GS290

• We have stopped the sales of the Gigaset GS290 on the eSolutionsShop as the vendor has stopped production of the device. We will continue support for existing users.

Message being shared on the request of our vendor partners

• Vendors whose phones we sell on our eSolutions Store do not directly sell /e/OS flashed devices.

• The vendors only sell their devices with their own stock ROM.

• To get pre flashed /e/OS phones, you have to purchase them from the eSolutions Shop.

/e/OS Pre flashed device sales

• We sell directly in EU, US, Canada and Australia

• Find details of what devices are available in which countries here Murena Shop.

/e/OS website and social media Links and Support

Websites

• Murena

• /e/OS website

• Documentation

• Report Bugs

• How to report Bugs

Telegram Channel

• Link to all the available Telegram channels

Social Media

• On XDA

• Twitter

• Mastodon

• LinkedIn

• Medium

Newsletters

• eFoundation news

• Murena products and promotions

Do not post test build information on the forum

• Please do not post information or links to /e/OS test builds on the forum.

• These builds are as yet untested and under development and may in some cases cause user devices to soft brick.

• Such information can confuse other users who do not see these builds in the updater.

• Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds

• If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team

• As part of the testing team you can share your comments on the dedicated testing telegram channel.

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[postal8555]

Will a 2025 roadmap be published?

What will version 3.0 include?

What is the progress on OTA updates?

[piero]

@Manoj

Legacy OS builds like Pie, Q or R are not available.Users may get a file / page not found error if browsing. We will try to add these builds. ETA of when this would happen will be shared.

[LEGACY_BUILDS] collection for /e/ OS supported "legacy devices"

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services[phone] . As developpement on some devices has been dropped, the /e/ management decided to qualify those dropped devices as “legacy devices”. But since the latest builds released by the /e/foundation for “legacy devices” are currently unavailables, . these LEGACY builds are not Updates nor Upgrades but a rebuild of the last version missing on official website… . my intentions here are : collecting available dev …

[Manoj]

@postal8555

Will a 2025 roadmap be published?

Yes. Will share ASAP

@postal8555

What will version 3.0 include?

Will be revealed in the roadmap

@postal8555

What is the progress on OTA updates?

If you mean the OS OTA progress it is there in the updates.

[gatienleclercq]

Hello! Thanks for the updates.
I saw that the OnePlus Nord (avicii) is still in testing for A12 to A14.
I do have this device, is there a way to help you with testing? I would be glad to help if possible.
Have a good day

[aibd]

@gatienleclercq

is there a way to help you with testing?

@Manoj

• If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team
• As part of the testing team you can share your comments on the dedicated testing telegram channel.

…

[gatienleclercq]

I should have been more cautious while reading, the information was right there…
Thanks!

[Manoj]

@Manoj

Reg the sync of notes app

From /e/OS v2.9 release, the eos-notes app should be able to sync notes.

If users want to enable sync now, they can also enable client sync from Murena workspace settings.

Step would be as under:

• Open murena workspace->settings->client Synchronization & enable the check mark (this may be already enabled for some users )
• Please note, this settings will enable sync for client apps, so there is a chance of data loss.
• Backup your data as there is a possibility of data loss .

Reg notes app sync queries

[kipry]

Thanks for the great News!
Just enabled the client synchronization. but doesnt seem to work via the notes app yet. i already updated the /e/ notes via app lounge to 3.7.4.

[rlees85]

@Manoj time to address the elephant in the room which is the fact that people that spent good money on the Murena Fairphone 5 are still:

• on Android 13, with no ETA
• on 60 hz refresh rate

If that announcement is just that you are working with Fairphone and are a bit stuck, then fine. I, and I expect others, feel abandoned at this point.

I’ve unlocked my phone and installed Iode and I will never ever be looking back.

But people will, if not already are, speaking on other communities about this now and some sort of status or assurance the Fairphone 5 hasn’t just been given up on might go some way to prevent further brand damage.

[Aymeric]

I did it, it works, but strange things happen, my “notes” ended up copied in 6/10/sometimes 12 copies.

[postal8555]

This, 100%. I wonder what the team is working on if not on this. Sadly we cannot know because the source code is hidden on https://gitlab.e.foundation/. And I hope the updates are not retarded because of some AI useless feature.

Saying that the update to Android 14 has still “to be planned” while LineageOS is already on Android 15 is simply not enough.

[mihi]

You can’t compare LineageOS and the official build of e/OS. Community build is more like LineageOS.

[Manoj]

I see a number of posts on the FP5 in this thread. Not sure why some are assuming that we have abandoned the FP5. We have not. Users need to understand that we do not simply copy paste LOS code. That would have been easy, change the label and publish it! That is not what happens. There are /e/OS specific applications, themes , framework level changes that are applied. Add to this the fact that when we talk of official builds we are talking about an OTA OS upgrade then the task is more complicated. We want to release a build that installs smoothly and does not result in any data loss to the user. This takes time. The team is working on getting this right and we will share details on this forum, once the build is ready.

[postal8555]

Ok, let’s compare it with CalyxOS, iodéOS, and GrapheneOS then: they all are on Android 15 already.

And saying that users need to understand is not enough, especially when we don’t see what happens behind the scenes with the code. I am disappointed for the delay in providing updates and for the persisting bugs that are not solved (camera quality, 60hz display, network failing…), so I wonder whether there is some work going on or the team is focused on something else.

[toggiburger]

I’m on a Murena FP5, too. I kind of understand your frustration with missing features and existing bugs on the current version. I myself am disappointed by the missing double tab to wake feature that once was about to be released and then got abandoned and was never again mentioned since.
But I also don’t feel represented by your choice of words and tone that you show in your comment. When you bought a Murena phone, I assume you did this for privacy reasons. If having the newest versions and features of android was most important to you, you just could have bought a Pixel phone from Google. Unfortunately this amazing company and community can’t deliver you both.

[mihi]

Here it says double tap works:

"Tap to wake" (still) not working

So, as an update: I don’t know what changed, I’m not aware of any updates since, but out of nowhere this started working. With and without AoD, I can now smoothly wake up my phone by double tapping the screen. Nice. (I did install Google TTS to get Duolingo working again, but that can’t be related, can it?)

[toggiburger]

This sounds promissing. Thank you.
Me missing the feature sure has to do with being on the official channel and therefore, as mentioned above, still on android 13. This makes me hopeful that I will get this beloved feature back as from the time when I used this all the time on my perviouse phone.

[msp]

@postal8555

… they all are on Android 15 already.

What would we benefit from A15 ?

I think focussing on bugfixes is more imported.

[mihi]

I don’t see in the comment if a14, there is also a13 with 2.8. It says about FairphoneOS .

@msp I switched recently from a13 to a14 on Pixel 4a community build, the only thing I saw as ‘new’ was showing the actual health of the battery. Nothing else was visibly changed.