Week 06, 2026: Development and Testing Updates

:mobile_phone: /e/OS Weekly Development and Testing Activities

  • Summary of weekly development and testing activities by /e/OS developers and volunteers.

  • Updated content is marked with the :new_button: emoji.


:rocket: Release Information

Upcoming Release v3.5 :new_button:

  • Tentative list of fixes and updates to come with v3.5
    (This link has multiple build which will include various builds we create during the testing phase. The issues in each test build will be updated or deleted based on the QA certification of the fix.)

Current Release v3.4

  • Release notes
  • An issue was detected in the Task application. An update fix was release of Tasks v1.4.4 was released via App Lounge.
    :backhand_index_pointing_right: Release specific issue bug. Add logs to the issues you report.

:star: /e/OS - A16 :new_button:

Planned release along with v 3.6 in March 2026 :crossed_fingers::new_button:

Will share the list of devices which will get the upgrade to A16. Upgrades will be manual for community builds and OTA for official builds. Manual upgrades will require users to download and install the builds over existing build. A backup of data is advised in all cases.

Status: :white_check_mark: under testing.

:star: /e/OS - A15 - /e/OS U

:clipboard: A15 new additions released with v3.3

:clipboard: A15 builds released with v3.2

:clipboard: A15 builds released with v3.1

:clipboard: Supported devices to get A15 builds

:clipboard: View the complete list of supported devices

:stop_sign: If a device build fails during compilation due to last-minute upstream code changes, we either try to rebuild these devices during the same release cycle or accommodate them in the next release cycle.


Documentation

:open_book: We are planning on updating our documentation site. Besides making navigation easier the plan is to make user contribution easier. Currently under planning stage, will share details once there is any progress on it.

:cloud: Migrate your data from google cloud to your Murena account. Follow the instructions in this guide.

:bug: Want to report an issue in /e/OS. Create the bug in Gitlab. If you are facing an issue in creating the ID, check this suggestion.


:locked: Security Information

:shield: Security Patch Release Process explained here


:bar_chart: Previous Releases & User Feedback

:memo: Feedback Threads

3.4

3.3

v3.2

v3.1.4

v3.1.1


:stop_sign: Support Dropped

These devices will no longer get /e/OS builds. We are dropping them from our release system. We tried to build v3.3 for them but the builds failed. Efforts to build with the Minimal Apps configuration did not succeed.

Vendor Device Name CodeName
Google Pixel XL 2 taimen
Google Pixel 2 walleye
Motorola Moto G7 Power ocean
Motorola Moto G6 Plus evert

Community builds dropped for these devices

  • We will be moving to supporting one build type for devices which have an official build.

  • Which means we will not be linking the community builds in our documentation. While the community builds will continue to be built, they will not be linked in our documentation. They will be available for OTA updates.

  • We plan to eventually have only official builds for these devices. Where devices have the same OS version in community and official we would recommend users to migrate to the official builds. Take a backup before proceeding. Also, it would be a manual install process.

  • Where the official builds are on a lower level compared to the community builds, we plan to migrate them to the higher OS level for official builds as well.

  • This change in the community builds links not showing up in the documentation for these devices can be expected from the upcoming v3.4

:backhand_index_pointing_right: Devices which will be impacted:

Vendor Device Name CodeName Official OS version Community OS version
Gigaset GS290 GS290 A12 A12
Samsung Galaxy S7 herolte A12 A12
Samsung Galaxy S7 edge hero2lte A12 A12
Samsung Galaxy S8 dreamlte A12 A12
Samsung Galaxy S8+ dream2lte A12 A12
Teracube Teracube 2e zirconia A12 A12
Teracube Teracube 2e emerald A12 A12
Samsung Galaxy S9 starlte A12 A13
Samsung Galaxy S9+ star2lte A12 A13
Fairphone FP3/FP3+ FP3/FP3+ A13 A15
Google Pixel 5 redfin A13 A15
Nothing CMF phone 1 tetris A14 A14
OnePlus nord avicii A14 A14
SHIFT SHIFTPhone 8 otter A14 A14
Teracube Teracube 2s saphire A14 A14
Volla Volla tablet mimir A14 A14
Fairphone FP4 FP4 A14 A15
Google Pixel Tablet tangorpro A14 A15
Fairphone FP5 FP5 A15 A15
Fairphone The Fairphone FP6 A15 A15
Google Pixel 7 panther A15 A15
Google Pixel 8 shiba A15 A15

:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 31.0.10.11

Resources:

:clipboard: Release Notes

:house: Self-Hosting

Current Version: v26.0.8.23

Resources:

:clipboard: Release Notes

:open_book: Upgrade Guide

Status:

:memo: Self-hosting guide update pending

๐Ÿ” How to Check NextCloud Version

Method 1: Murena Settings

Go to Murena Settings

Look for โ€œNextCloud xx user documentationโ€

Method 2: NextCloud Scan

Visit NextCloud scan link

Input https://murena.io

:information_source: Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad. This is normal - patches are tested before deployment.


:mobile_phone: GSI (Generic System Image)

Current Version: /e/OS A10 v1.17

Resources:

:inbox_tray: Download

:open_file_folder: Sources

Next Version: /e/OS T (A13) - skipping A11 and A12

:date: Release dates to be announced


:counterclockwise_arrows_button: OS OTA Information

โœ… Completed
Teracube -zirconia -  S(A12) โ†’ V(A15) ๐Ÿ†•

Teracube : S(A12) โ†’ V(A15) ๐Ÿ†• 

FP5 -  Fairphone: S (A13) โ†’  V (A15)  

FP5 - Fairphone: U (A14) โ†’ V(A15)

FP4 - Fairphone : S (A12) โ†’ T (A13)

S9/9+ - Samsung : R (A11) โ†’ S (A12)

GS290 - Gigaset : R (A11) โ†’ S (A12)

GS290 - Gigaset : Q (A10) โ†’ R (A11)

avicii - OnePlus : A12

FP3 - Fairphone : S (A12) โ†’ T (A13)

S7/7+ - Samsung : R (A11) โ†’ S (A12)

FP4 - Fairphone : T (A13) โ†’ U (A14)

S8/8+ - Samsung : R (A11) โ†’ S (A12)

:information_source: Note: OTA upgrades are for official or stable builds only

:test_tube: Under Development and Testing

  • :mobile_phone: avicii - OnePlus : S (A12) โ†’ A16 :new_button: ETA v3.6 :crossed_fingers:

  • :mobile_phone: avicii - OnePlus : S (A12) โ†’ U (A14)

  • :mobile_phone: FP4 - Early 2026

:clipboard: To Be Planned :new_button:

  • :mobile_phone: FP3
  • :mobile_phone: tangorpro - Google Pixel tablet 7
  • :mobile_phone: Murena One - A12 - A15
  • :mobile_phone: GS290* - A12 - A15
  • :mobile_phone: Galaxy S9* - A12 - A15
  • :mobile_phone: Galaxy S8* - A12 - A15
  • :mobile_phone: Galaxy S7* - A12 - A15

(Devices marked with an โ€˜*โ€™ have an issue with FDE encryption which requires format before the OS can be upgraded. This essential means there would be data loss. If we are able to build a A15 build for these devices, the user will have to manual install it and that would require first taking a backup of all data.)

:backhand_index_pointing_right: Check the section titled A16 Updates below

๐Ÿ“– What is OS OTA Upgrade?

Traditional Process:

:inbox_tray: Download correct OS build from supported device list

:inbox_tray: Download stock ROM from vendor site (for some devices)

:floppy_disk: Back up your data

:counterclockwise_arrows_button: Install stock ROM, then /e/OS ROM

:counterclockwise_arrows_button: Restore backups if needed

OTA Benefits:

:white_check_mark: Simplifies the entire process

:warning: Requires significant development and testing


:speaker_high_volume: A16 Updates :speaker_high_volume: :new_button:

  • We plan to update all devices currently on A12, A13, A14 and A15 to A16 :speaker_high_volume:
  • In case any device is not able of handling the A16 builds we will share that information.
  • The team expects that A16 would not be buildable or installable on some of the older gen devices like the Samsung S7 or S8. There could be more.
    • For such devices we we will work on getting them to the highest OS version possible.
  • As you may be aware A12 does not receive security patches anymore. This will next impact A13 and so on. This is a standard Google policy to end of life (EOL) older Android versions.
  • All devices we sell in our shop, with official builds are priority candidates for OTA OS upgrades. The difference is the official builds get OTA OS upgrades. Community devices will require manual upgrade.
  • Will share dates and ETA once I get them from the team.

:link: Miscellaneous Information

:bar_chart: Real-Time Service Status

:cloud: eCloud Real-Time Status

:mobile_phone: /e/OS Real-Time Status

New Gitlab account creation

  • If you are trying to create a new /e/OS Gitlab ID and facing issues with the email ID, you can try and create a Murena Workspace ID and use it to log into Gitlab. Check the updated documentation here

๐ŸŽซ Helpdesk Services

:white_check_mark: For Paying Murena Customers

:mobile_phone: Murena device purchasers

:cloud: Paid Murena cloud account holders

:heart_with_ribbon: Active donors from the past year

:alarm_clock: Response Time

:hourglass_not_done: 5-10 day response wait period due to high volume of requests.

:telephone_receiver: Contact

:ticket: Murena Helpdesk Contact Form

:free_button: For Free Users

:speech_balloon: Forum

:bug: GitLab Issues

:mobile_phone: Telegram Channels

:warning: Warning: Old helpdesk email IDs are no longer monitored.

๐Ÿ“ฑ Device and Vendor Announcements

:mobile_phone: Gigaset GS290

:stop_sign: Sales stopped (vendor ceased production)

:white_check_mark: Support continues for existing users

:mobile_phone: Murena One

:stop_sign: Sales stopped

:white_check_mark: Support continues for existing users

:mobile_phone: Murena Two

:stop_sign: Sales stopped

:white_check_mark: Support continues for existing users

:shopping_cart: Pre-Flashed Devices

:globe_showing_europe_africa: Available in EU, US, Canada, and Australia. Check the complete list on the Murena shop

:shopping_cart: Purchase via Murena Shop

๐ŸŒ /e/OS Website and Social Media Links

:globe_with_meridians: Official Websites

:house: Murena

:mobile_phone: /e/OS Website

:books: Documentation

:bug: Report Bugs

:open_book: How to Report Bugs

:mobile_phone: Telegram Channels

:speech_balloon: Available Channels

:mobile_phone: Social Media

:mobile_phone: XDA

:bird: X

:elephant: Mastodon

:briefcase: LinkedIn

:memo: Medium

:e_mail: Newsletters

:newspaper: eFoundation News

:tada: Murena Promotions


:warning: Important Notice

:prohibited: Do Not Post Test Build Information on the Forum

Why this is important:

:warning: Test builds are untested and may cause device issues

:fire: These builds can potentially soft brick user devices

:thinking: Such information can confuse other users who donโ€™t see these builds in the updater

:busts_in_silhouette: Not all forum users are experts in custom ROM installation

For Interested Testers:

:test_tube: If you understand custom ROMs and can perform basic testing

:busts_in_silhouette: Join the testing team

:speech_balloon: Share feedback on the dedicated Telegram channel

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

16 Likes

Hello, just one question,

the pixel 8 pro device is so different to the pixel 8 (not pro)? so that it donโ€™t geht an official /e/ with OTA update and has to be with community build?

Devices with official builds have Rom Maintainers. While those with community builds follow the device tree from Lineage with customization as specific to /e/OS. Unless we get a dedicated maintainer for a device, we have to release community builds.

I propose to add https://status.murena.io/ to the status section of the weekly update header section and to add status of murenas Unified Push-(or ntfy or whatever) server to either https://status.murena.io/ or to https://status.e.foundation/.

Yes yes I know.

Sorry maybe iโ€™ve not well express myself.

Does not the pixel 8 pro in the same build than the pixel 8?

Does it have a reaaly big difference both so that they re handled separatly?

Unfortunately, it would not work. The same build would not work on two different devices. As during the build process, we pick up files specific to a device. Trying to flash a different build can brick a device.

Hi @Manoj, are you able to reconfirm this or has the fix been withdrawn?

I cannot find it in App Lounge and the same is reported by others.

you means thatโ€™s not only a difference on the size, but on chips & sensorsโ€ฆ:head_shaking_vertically:

Which version of the OS build are you on.
Task v1.4.4 should show up on the App Lounge again. There was some issue in GitLab which is being rectified.

Search Tasks or foundation.e.tasks โ€“ โ€œTasks 1.4.4โ€ is simply not in the results on
3.4-a15-20260117570255-community-FP3 and
3.2-a15-20251024539369-community-ocean.

As mentioned, Tasks v1.4.4 will be restored to the App Lounge ASAP. We are working on adding it back.

Update: Pl can you check now. Tasks v1.4.4 should be visible now in App Lounge.

1 Like

Checking 1 hour later, after App Lounge Clear storage, both phones not found atm.

Some users may see a notification showing up post the v3.4 update. This is the notification to encourage users to migrate to OpenID Connect (Single Sign-On or SSO). Itโ€™s designed to appear every time after a reboot until the users migrate to it. After clicking on the notification, itโ€™s the typical login flow to Murena account in the Browser.

Itโ€™s not directly related to the Murena Workspace app, but the overall Murena service.

We have recently changed the wording of the notification and mentioned it in the v3.4 release note (v3.4-a15 ยท e / os / ๐Ÿš€ Releases ยท GitLab).

3 Likes