Week 36, 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
    • Fix for users getting locked out of their accounts after resetting password
    • ETA : Mid of September :crossed_fingers:

Current

Milestones

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

:bar_chart: Current and Previous Releases and User Feedback


Murena Account Recovery Email

  • Ensure your Murena Workspace account (e.email or murena.io) has a recovery email.
  • New accounts and existing accounts without a recovery email will face reduced functionality for 30 days, after which they will be marked for deletion.

:backhand_index_pointing_right: To check if your Murena account has a recovery email, click an log in here.

  • If your account is disabled, contact me (@Manoj) on this forum and I can assist with re-enabling it.

Password Reset

  • We receive multiple requests for password resets. Users have reported instances of being locked out of the Murena password after resetting their Murena Workspace password. A fix for this is targeted for v4.3.
  • Please note that users can reset their own Murena Workspace password using the β€˜Forgot Password’ link.
  • If a user is unable to reset the password on their own, requests to the support team for a password reset will not be entertained unless the user can confirm ownership of the device or account.
    • To prove ownership, you will be required to share the recovery ID or any other details requested by the infra team.
    • For assistance or guidance with a locked password, contact me (@Manoj) on the forum.

Documentation

:magnifying_glass_tilted_right: Tips for using GitLab or the Forum

  • Always use the search feature first before raising new bugs or creating new posts.
    • If others have already raised similar issues, please add your details to the existing thread.
  • When creating new issues on GitLab or new posts on the forum:
    • Share details of your device (model, build, and any other information that could help others debug the issue).
  • Never share personal details such as your email address when raising issues or creating posts on the forum or in non-confidential GitLab issues.

: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: Some important guides on the Documentation site

:information_source: Please note that some of these features are still in beta. Additional development, detailed testing, and improvements are in progress. We look forward to your comments and feedback.

:backhand_index_pointing_right: A guide explaining what Bootloader relocking means.

:bug: How to Report an issue in /e/OS

:shield: Security-related documentation

  • Security Patch Release Process explained here
  • :construction: We will be sharing a detailed document about our security policy.
  • :construction: Security updates tracking page. A guide to help track public security updates release by release from v3.0 upwards. This will include initial tracking tables for A12 to A16, covering release date, Android Security Bulletin, browser security update, and vendor security update.

:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 32.0.6.11

  • :construction: Work in progress on updating Murena Cloud to NextCloud v33 . Will share ETA once I get the same from the team. :new_button:

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

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

9 Likes

Hi@manoj ,

I really appreciate your dedicated work here in the forum!
As I do read your weekly updates regularly, I could see that the section

isn’t up to date and so slightly confusing.

Category β€œUnder Development and Testing”:
The 3 Teracubes are already on A16, that would shrink the list from 6 to 3.
Category "To Be Planned:
The 3 Teracubes are already on A16
The Gigaset GS290 is already on A15
The Samsungs S7/S7+/S8/S8+ get updates ( 4.2-s ) but no upgrades.
Category β€œCompleted”:
The list could be shortened, after update, to one line per device.
For example: Gigaset GS290 - A10->A11->A12->A15
And listed by alphabetical order.

This all would make the categories better readable.

2 Likes

Thanks for the detailed feedback. Have made some corrections.

Regarding this section I think I was publishing it in this format earlier, but a user specifically asked for this breakup. That way you can also figure out if a device got an A12 β†’ A15 upgrade. Those who are stuck on A12 can try that build and jump to A15. Putting them all in a line shortens the text but this makes it easier for some users.

3 Likes

I don’t understand the reason for keeping the existing list in this way.
Why should putting them in one line and list it in alphabethical order be a hindrance for upgrading their (some users) smartphones?

Manoj, now a cup of tea and my day is saved :wink:

I forgot to mention that in β€œTo Be Planned” the Oneplus should be corrected as already on A16.
Now I’m done.

Hi everyone,

I noticed that the Murena Cloud is currently being updated to Nextcloud v33 (Version 32.0.6.11 is live). However, the Self-Hosting version is still on v26.0.8.23.

Could you please share an estimated timeline or ETA for when the Nextcloud update will be available for the self-hosted version? We are eager to upgrade our own instances.

Thanks in advance!

@Manoj : do you confirm v4.3 will restore the ability to backup/restore to other destinations than Murena cloud?

With /e/OS up to v4.0, it was possible (through seedvault) to backup on any WebDav instance (including a self-hosted one), but also on local storage, on a flash drive etc.

If this ability will be restored, will it be through the regular seedvault (like before), or through the Murena fork of seedvault?

Hello :waving_hand: ,

Since A14 β†’ A16 OTA for the OnePlus Nord (avicii) was dropped, I’ve got a few qustions regarding sideloading.

-Is dirty flashing from A14 to A16 possible, without losing any personal data?

-Safer to update via adb and fastboot, or better update to A16 locally from within the eOS system update feature?

-Better to update from 3.3 to 4.2 directly, or go to 4.0 first - then manually update via OTA to 4.2?

Thanks in advance :slightly_smiling_face:

Seedvault will be back. Murena Backup will be the default. Users will also get the option to backup to Seedvault if they want with v4.3. Other options besides these two will be added in subsequent releases.
Pl note at a time users can select only one backup option. Which means you can either select Murena Backup or Seedvault not both. This will the same case when additional backup options are added later. Only one backup option can be selected at a time.

Yes, the only option available for upgrade from A14 to A16 is via sideloading. Our testing team did it and was successful. You will have to take a backup of the applications first.

Let me check with the team member on how he did the sideload and get back with the details.
OTA upgrade from A14 to A16 is not possible. Sideloading is the only option.