Week 43 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 :new_button:

  • v4.4.1

  • Fix and optimization planned

    • Issues would be added or removed from this list based on QA validation
    • GS6 double tap to wake up fix :crossed_fingers:
    • Google Pixel 5 redfin A16 OTA upgrade
    • Murena One A15 OTA upgrade
    • Murena Two A15 OTA upgrade
    • Device builds that failed v4.3 release

    ETA : Early next week :new_button:

    • Current Status: Release Notes under review, builds to be initiated

Future Release

:bar_chart: Current and Previous Releases and User Feedback


Murena Account - Important information

  • Murena Workspace account’s (e.email or murena.io) should have 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

: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

  • Go to Murena Settings
  • Look for β€œNextcloud xx user documentation”

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: FP4 – FP4 – A14 β†’ A16
  • :mobile_phone: FP6 – FP6 – A15 β†’ A16
  • :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: Fairphone – FP5 – A15 β†’ A16
  • :mobile_phone: Murena One – A12 β†’ A16 after release of A15
  • :mobile_phone: Murena One – A12 β†’ A15 (v4.4.1 :crossed_fingers :crossed_fingers:)
  • :mobile_phone: Murena Two – A12 β†’ A15 (v4.4.1 :crossed_finger :crossed_fingers: )
  • :mobile_phone: Nothing – CMF Phone 1 tetris A14 β†’ A16 (v4.5 :crossed_fingers :crossed_fingers:)
  • :mobile_phone: Google - Pixel 5 – redfin A13 β†’ A16 (v4.4.1 :crossed_finger :crossed_fingers:)
πŸ“‹ 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 A16 Already on A16
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 v4.4.1 :crossed_fingers:
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 v4.5 :crossed_fingers:
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 EOL
Samsung S7+ * hero2lte A12 EOL
Samsung S8 * dreamlte A12 EOL
Samsung S8+ * dream2lte A12 EOL
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

11 Likes

It’s very nice to have a summary list of features, optimizations and fixes for the upcoming release right in your post. Thanks for doing this @Manoj .

5 Likes

Check out the updated workflow for an issue raised in Gitlab.

1 Like

for when the v4.4 is planned ? just for curiosity… and little difficult to stay patient :grin:
(double tap effect :wink:)
Is that meant with ETA?

ETA is Estimated Time of Arrival.

3 Likes

microG announced having β€œmultiple high severity security vulnerabilities” almost ONE MONTH ago, and /e/OS has not been patched yet. All /e/OS users have been vulnerable. This is ridiculous.

Regarding MicroG, @Manoj is it already possible to update MicroG through AppLounge as described in this MR :

Or is this something for a future release?

1 Like

Let me check and get back.

Update from the team about microG

  • Not as yet. It is planned and will be part of a future release.

  • latest version with security patches is part of /e/OS already

3 Likes

is there some major block to getting A16 on FP5? It has been under development & testing for a while now

1 Like

What is, bearing in mind this?

1 Like

@Manoj: I saw with excitement that the Pixel 5 Redfin OTA update A16 is listed under 4.4 Fixes & Optimization, ETA next week - but it’s still listed among the OTA updates as β€œTo Be Planned”. Is it going to make it as part of 4.4 or was that a typo?

The user is asked after first launch if he wants to install microG or not.

β€œor not” - interesting :nerd_face:

Redin upgrade to A16 is scheduled for release with v4.4.1

That’s simply not true, the latest version with security patches is NOT part of released /e/OS.
Check the microG version on your phone. On mine, it’s 0.3.16.252432-38. The patched one is 0.3.16.1.252432 (or 0.3.17.252432).
I’m running the latest available /e/OS for my FP5 (e-4.3-a15-20260917677554-official) and it’s unpatched.

1 Like

The new microg version will be in upcoming e/OS 4.4. So it is already in e/OS but not yet released.

This should not be left ambiguous.

@Manoj: Does the microG version displayed as 0.3.16.252432 in /e/OS 4.3 have the security patches already and the team decided against displaying the version number as 0.3.16.1.252432, or is a newer microG version including the security patches only coming with /e/OS 4.4?