Week 38, 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.


Release Information

Upcoming

  • v4.3
    • Tentative list of fixes and optimizations
    • A16 release for FP4 official and community coming as part of v4.3.
    • Team working on adding Seedvault back to the available backup options.
    • Fix for users getting locked out of their accounts after resetting password.
    • Fix for FP4 low volume issue.
    • ETA : Early next week
    • Current phase : Porting of security patches (they came in late this month) and testing for various OS versions.

Current

Milestones

  • Releases planned for the future are marked as milestones in GitLab.

:bar_chart: Current and Previous Releases and User Feedback


Murena Account related issues

  • Ensure your Murena Workspace account (e.email or murena.io) has a recovery email.
  • Accounts without a recovery email will face reduced functionality for 30 days, after which they will be deleted.
  • Check if your Murena account has a recovery email, click an log in here.
  • If your account has been disabled or you are facing password reset issues after setting up Murena Password contact me (@Manoj) on this forum and I can assist with re-enabling it. You would be required to verify account ownership by sharing additional details.

Documentation

:magnifying_glass_tilted_right: Always use the search feature first before raising new bugs on or creating new posts. Add details to existing issues. Share as much details about the phone as possible.

:backhand_index_pointing_right: Anyone with a /e/OS GitLab account can now edit the Documentation site.

A brief explanation of how users can edit the Documentation site

The process for editing the /e/OS Documentation site is as follows:

  • Share your /e/OS GitLab ID with me (@Manoj). I will pass it to the team member who will grant you the necessary access to the documentation project.
  • Once access is granted, your changes will be created as a Merge Request (MR).
  • The MR must then be reviewed.
  • The MR can be rejected or approved. If rejected, reasons will be shared.
  • Once approved, the content is published and appears on the documentation site :bouquet:

:backhand_index_pointing_right: Important guides on the Documentation site

:information_source: Guides marked with (*) are features still in beta phase. Additional development, detailed testing, and improvements are in progress. We look forward to your positive comments and feedback which you can post on the forum.


:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

: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

Method 2: Nextcloud Scan

:information_source: Note: If the Murena Cloud patch number differs from the Nextcloud patch number, the rating may appear as “bad”. This is normal — patches are tested before deployment.


:counterclockwise_arrows_button: OS OTA Information

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

:backhand_index_pointing_right: All official builds are candidates for upgrade to A16 or the next OS version for which a build is possible.

:backhand_index_pointing_right: The absence of a device with an official build from this list does not mean the device has been abandoned. We continue efforts to build for all official devices ever sold on the Murena Store. Release dates for these builds will be shared when available.

📢 Completed
  • :mobile_phone: FP6 – FP6 – A15 → A16 :new_button:
  • :mobile_phone: FP3 – FP3 – A13 → A15
  • :mobile_phone: OnePlus – Nord – avicii – A12 → A16
  • :mobile_phone: Teracube – emerald – A15 → A16
  • :mobile_phone: Teracube – sapphire – A14 → A16
  • :mobile_phone: Teracube – zirconia – A15 → A16
  • :mobile_phone: Teracube – 2e – zirconia – A12 → A15
  • :mobile_phone: FP5 – Fairphone – A13 → A15
  • :mobile_phone: FP5 – Fairphone – A14 → A15
  • :mobile_phone: Galaxy S9* – A12 → A15
  • :mobile_phone: GS290* – A12 → A15
  • :mobile_phone: FP4 – Fairphone – A12 → A13
  • :mobile_phone: S9/9+ – Samsung – A11 → A12
  • :mobile_phone: GS290 – Gigaset – A11 → A12
  • :mobile_phone: GS290 – Gigaset – A10 → A11
  • :mobile_phone: FP3 – Fairphone – A12 → A13
  • :mobile_phone: S7/7+ – Samsung – A11 → A12
  • :mobile_phone: FP4 – Fairphone – A13 → A14
  • :mobile_phone: S8/8+ – Samsung – A11 → A12
🧪 Under Development and Testing
  • :mobile_phone: FP4 – FP4 – A14 → A16 ETA v4.3
  • :mobile_phone: FP5 – FP5 – A15 → A16
  • :mobile_phone: Murena One – A12 → A16
📋 To Be Planned

This is the consolidated list of all devices that have an official build. The plan is to upgrade all of them to the latest possible build. This may not be feasible for every device, as some are too old and have already reached EOL from the vendor and may not work on the latest OS versions. Devices marked “No updates” fall into this category.

Vendor Name CodeName Current OS Upgrade OS
Fairphone FP6 FP6 A16 Already on A16
Fairphone FP4 FP4 A14 A14 to A16 - v4.3
Fairphone FP3/3+ FP3/3+ A15 A15 to A16
Fairphone FP5 FP5 A15 A15 to A16
Gigaset GS6/Pro GS6_venus A16 Already on A16
Gigaset GS290 GS290 A15 A15 to A16
Google Pixel 5 redfin A13 A13 to A16
Google Pixel 7 panther A15 A15 to A16
Google Pixel 8 shiba A15 A15 to A16 / A17
Google Pixel Tablet tangorpro A14 A14 to A16
Murena One One A12 A15 or A16
Murena Two Two A13 A13 to A16
Nothing CMF Phone 1 tetris A14 A14 to A16
OnePlus Nord avicii A16 A14 to A16 via sideloading possible
Samsung S9 starlte A15 A12 to A16
Samsung S9+ star2lte A15 A12 to A16
Samsung S7 * herolte A12 No OS upgrade (to be decided)
Samsung S7+ * hero2lte A12 No OS upgrade (to be decided)
Samsung S8 * dreamlte A12 No OS upgrade (to be decided)
Samsung S8+ * dream2lte A12 No OS upgrade (to be decided)
SHIFT SHIFTPhone 8 otter A14 A14 to A16
Teracube 2e zirconia A16 Already on A16
Teracube 2e emerald A16 Already on A16
Teracube 2e sapphire A16 Already on A16
Volla Volla Tablet mimir A14 A14 to A16

(Devices marked with an * have an issue with FDE encryption that requires a format before the OS can be upgraded. This essentially means data loss. If we are able to build an A15 build for these devices, users will have to install it manually and must first take a full backup of all data.)

:backhand_index_pointing_right: Check the section titled A16 Updates below.

📖 What is an OS OTA Upgrade?

Traditional Process:

:inbox_tray: Download the correct OS build from the supported device list
:inbox_tray: Download the stock ROM from the vendor site (for some devices)
:floppy_disk: Back up your data
:counterclockwise_arrows_button: Install the stock ROM, then the /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


🔊 A17 or A16 Updates 🔊
  • We plan to update all devices currently on A12, A13, A14, and A15 to A16 or A17 once it becomes /e/OS-compatible :speaker_high_volume:

  • If any device is unable to handle A16 or A17 builds, we will share that information.

  • The team expects that A16 will not be buildable or installable on some older-generation devices such as the Samsung S7 or S8. There could be more. While the team will try to OS upgrade these devices, if the attempt fail we will have to drop these devices from the supported list.

  • As you may be aware, A12 no longer receives security patches. This will next affect A13 and subsequent versions. This is standard Google policy for end-of-life (EOL) of older Android versions.

  • All devices we sell in our shop that have official builds are priority candidates for OTA OS upgrades to A16.

    • Official builds receive OTA OS upgrades.
    • Community devices require manual upgrades.

(Ideally, take backups before upgrading the OS on any device.)


:link: Miscellaneous Information

:bar_chart: Real-Time Service Status

:cloud: eCloud Real-Time Status
:mobile_phone: /e/OS Real-Time Status


🎫 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: 2–3 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 addresses 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 the 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 address 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 do not 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

15 Likes

the murena.io Google migration client seems to need re-verification - I’m unsure - Migration to Murena workspace blocked by Google

Google keeps trying its best to make things difficult for us. Will pass on the info to the team to check and resolve.

5 Likes

So, will Seedvault be back? If ETA is this week, the change should have already been implemented, no?
I’m stuck on 4.0 because updating would mean losing the backup feature, it would be problematic to skip another version and relative security patches.

Yes with v4.3 it should be back

4 Likes

According to the roadmap, v4.3 if for next week, not this week. Or am I missing something?

Team is working on getting it ready for this week if possible.

10 Likes

thank you! great.

wishes for next releases:

In the meantime, install Google webview beta from Aurora or Applounge. Works flawlessly. You’ll have to live with some privacy regressions but security patches are instant as it gets updated weekly.

you installed webview beta or dev? could it introduce new security problems anywhere else to install it? (or break something?)

I installed beta (dev and canary are even less stable). Of course running the beta version of Google webview means that some apps could possibly crash. Regarding security, I think the Google webview beta is way more secure than e/OS webview which is currently >4 months old with known exploited vulnerabilities as you have read in the other thread. The beta may possibly introduce some new vulnerabilities but the thing is updated weekly. If you prefer Google webview stable, you may also install it from APKMirror and use e.g. obtainium to track updates but it is less convenient than simply updating directly the beta using Aurora store.

Anyways, e/OS is supposed to update the (Cromite) webview in v4.4 so you may switch back to it at that time. Note that Cromite just got updated recently but unfortunately we cannot install it directly and have to wait for Murena to include it in e/OS natively, which is unfortunate… But it is a good thing that we can at least install Google webview alongside and never have to rely on an outdated webview anymore. This is critical for security and no AV is going to mitigate the risks introduced by a vulnerable webview anyway.

EDIT: note that if you have a second user profile and/or a work profile, you need to install the new webview in each profile separately. Only then will you be able to select the new webview in dev options/webview implementation. After that, updating it from any profile will work

thank you for your answer! as you already mentioned, with another user profile (using island) it is not possible to switch over to the other webview (in both), it is greyed out. how do you install it?

You need to install Google webview beta separately in each user/work profile. If you use Aurora store, this means installing Aurora in each user/work profile and then installing the new webview. When the new webview is installed in ALL user/work profile, you can switch back to the main profile, enable dev options and select the new webview from there. If the webview is not installed in all user/work profile, it remains greyed out in dev options and cannot be selected.

EDIT: I have now been able to use obtainium to install/track the current stable version of Google webview (v154.0.8037.22) from uptodown.com (APK is signed by Google). I can now choose between the beta and stable versions of Google webview and the outdated e/os one. So if you prefer stable over beta, that is another possibility.

Hallo,

e/OS 4.3 habe ich heute Mittag per OTA für mein Murena Fairphone 6 bekommen.

1 Like

Did you? Because it’s not (yet) on the releases page on GitLab. Or is that the wrong source for that?

Thanks!

v4.3 does not seem available for FP6 yet, neither for community or official releases

Official releases

Community releases

@yo1957 maybe you’re on test channel?

Most likely v4.3 official release will come next week as suggested on the roadmap, as community is not yet out and official are not made available over the weekend.

3 Likes

While ideally the release notes should directly be available with the release start of a new /e/OS version, in the past updating these pages often lagged a little behind. So, until that has improved, this is not a perfect indicator for the start of a release.

1 Like

What’s the exact version string now? … [HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc

Thank you for the clarification. So where do I find the definitive info if the new update is released? The reason I’m so eager is that I wanted to install /e/OS on my FP6+ but I had installed the latest Android update already, so the installer blocked me and told me to wait for the new release.

Ich wollte nicht für Verwirrungen sorgen. Sorry dafür. Da es sich aber weder um eine beta Version noch um eine rc Version handelt, dachte ich das wäre das ganz normal Update welches ja für diese Woche oder nächste Woche angekündigt war. Werde mich künftig zurückhalten.

I didn’t want to cause confusion. Sorry for that. But since it is neither a beta version nor an rc version, I thought this would be the normal update which was announced for this week or next week. I will hold back in the future.

2 Likes