Week 13, 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 Updates

Current v3.6 :new_button:

Upcoming Milestones

  • Release planned in the future are marked as milestones in gitlab
  • Milestones

:rocket: A16 OS Release

  • Released: 24 March 26 :new_button:

  • List of Supported devices that will get the A16 community build

  • New devices joining the supported devices list and coming with A16 community build.

    • These builds are community builds. Will require a manual download and install
    • Official A16 builds will take some time and may not be coming with v3.6 . Will share information as to when they will be released.
    • Installation guides for the A16 builds are in the process of being updated and should be released this week.

Murena Account Recovery Email

Ensure your Murena Workspace account (e.email or murena.io ) has a recovery email set. New Accounts without a recovery email will face reduced functionality for 30 days and post that will be marked for deletion. The process will be the same for existing accounts without a recovery email

:backhand_index_pointing_right: To check if your Murena account has a recovery email click here

  • Link will require you to log in to your Murena workspace.

Documentation

:open_book: Please note that we have transitioned to a process requiring all Murena accounts to have a recovery email. The recovery email ID is is an external email address that can be used to recover your account details should you lose access to your Murena email for any reason.

  • Accounts without a configured recovery email will experience reduced functionality for a period of 30 days. After the 30-day period, such accounts will be marked for deletion. The deletion does not happen automatically.
  • All users with Murena workspace IDs (murena.io, e.email) are requested to set a recovery email immediately if one has not already been configured.
  • Check the documentation that mentions this requirement.
  • Please do not wait for your account to be disabled, Set the recovery email ID today, if not done already :folded_hands:
  • What to do if you have not set a recovery email ID and you account is already disabled?
    • Contact me @manoj and I should be able to help you with the unlocking.

: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

  • We will be sharing a detailed document about our security policy.

:bar_chart: Previous Releases & User Feedback

3.6

3.5

3.4

3.3

v3.2


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 have been made post release of v3.4.

Devices 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 will be shared

  • :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

:bank: To send in your Donations : Use the email ID donation@murena.io


: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

11 Likes

3.4 is not upcoming anymore :wink: .

1 Like

:slight_smile: Thanks for pointing that error. Have made the correction.

1 Like

Shared comments related to Android Auto having issue post v3.6 release with the developers. Will update in case there is a response. Also, would recommend users impacted to create an issue on gitlab as the developers prefer logs as it helps them debug issues.

2 Likes

Dedicated issue created to track v3.6 bugs. Links to the forum posts have been added. Users can add logs or details to the issue on GitLab. if they are facing the issue

3 Likes

Hi,

So if I understand, no Fairphone will get the A16 version ?

Why not?
If you are referring to the list, it states that “Devices can be added or removed from this list based on the status of the build.”

It’s hard to imagine FP6 not getting Android 16, because Fairphone have now released Android 16 for it and could help via the Fairphone - Murena partnership, and FP6 is actively being sold by Murena.

FP3 should be a big question mark for technical reasons (I read about kernel trouble), so FP3 users like me shouldn’t bank on it, but the end of security updates for the available Android 15 is to be expected in early 2028 if prior Android versions are any indication, so no reason to panic now.
Same goes for FP4 and FP5, which should be in a better position than FP3, of course.

4 Likes

I think it will just take time. The FP4 official A16 is still to be planned.

It’s just weird to develop A16 for some smartphones and not Fairphone, even though the two brands have a partnership.

Of course, the list is subject to change—I’ve read that—but if the A16 comes out next week, I’m afraid the Fairphones won’t be on it.

Hi!

When you say there no reason, according the security patch, to worry about for FP3 users, does it cover Community and Official ? Because on my understanding and with my basic knowledge, I assume there is to worry as official are on A13 and therefore, no security update at all ? Am I right ? Same does not apply for Community, which is on A15 right ?

Thanks for your help

1 Like

Yes, you are correct, I made this sound too simple, apologies.
If your FP3 is on official, security updates just ran out for Android 13.
You could manually install community to go where the security updates are if you want to prioritise them, but it was announced that community would not be available forever either once official caught up to newer Android, so then it would mean to manually switch back.
It’s a concern, I agree.

But there are still users with supported phones on Android 12 official out there, so it could be worse for FP3, if that’s any consolation.

2 Likes

Yeah, so when will the FP3 get a stable A15 release? Is it before 2028?

As long as it’s mentioned up there, there’s hope :wink: .

1 Like

It will but on official build only, which will be delivered OTA

My understanding is that the current list is for community builds only.

The official builds getting A16 take longer to build and test and will most likely be upgraded to A16 in a subsequent version of /e/os.

All Fairphone and official devices will get the A16 unless we are unable to build it for any reason. The reason will be specified. In such cases we will then go for the next lower OS possible like A15..

9 Likes

Yes the current list is for community devices only as is mentioned in the initial post.

Device builds that failed as part of v3.6

  • OS versions on which the failure occurred is mentioned.
  • We will retry these builds
  • They may receive other OS version builds. will have more clarity as some of the builds are still in progress
Vendor Devicename Codename OS build failed
Google Pixel 8a akita A16
Google Pixel 7 Pro cheetah A16
Google Pixel 9 Pro Fold comet A16
Google Pixel Fold felix A16
Google Pixel 8 Pro husky A16
Google Pixel 7a lynx A16
Google Pixel 6 oriole A16
Google Pixel 6 Pro raven A16
Google Pixel 8 shiba A16
Google Pixel 9 tokay A16
Xiaomi Redmi Note 10S rosemary A15
Nubia Mini 5G TP1803 A14
F(x)tec Pro¹ X pro1x A14
Xiaomi Pad 5 nabu A13
2 Likes

Update: Some bad news. OnePlus Nord avicii A16 official will not be coming with v3.6. Testing and debugging still in progress. Will update when it can be released.

4 Likes

Update:

:loudspeaker: A16 community bhttps://doc.e.foundation/devicesuilds as mentioned in our list have been released.:loudspeaker:

These builds will require you to manually download and install them from the documentation site. Check the device name / codename in the table and download the A16 build for the device

4 Likes

Hello @Manoj ,
It seems that the certificate of https://push.murena.com has expired. Can you forward this to the admins? Or should I open a bug ticket?

2 Likes