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

Upcoming v3.7 :new_button:

status: testing

  • Issues and fixes

  • Google Map issue

  • Multiple builds with the same version number will show up in this link, that is because testing involved different phases. More issues may be added or removed to the list.

:rocket:Current v3.6

Status: Released

:rocket: A16 OS Release

Status: Released :new_button:

  • List of Supported devices that got the A16 community build

  • New devices joining the supported devices list and come 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 have been updated
    • There will be further addtions to the list of devices we will release on A16.
    • The plan is to update all devices where possible to the latest OS version.

Upcoming Milestones

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

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.
  • In case your account is disabled, you can contact me - @Manoj on this forum and I can assist to have the account reenabled.

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

  • 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


:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

:loudspeaker: Murena Cloud just got an update

Current Version: 32.0.6.11 :new_button:

Resources:

:clipboard: [Release Notes]( v32.0.6.11 · e / infra / ecloud / nextcloud · GitLab) :new_button:

: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: OnePlus nord avicii - A12 → A16

  • :mobile_phone: FP4 - FP4 - A14 → A16

:clipboard: To Be Planned :new_button:

  • :mobile_phone: FP3 - FP3 - A13 → A15
  • :mobile_phone: Google Pixel tablet - tangorpro - A14 → A15
  • :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

12 Likes

Hi

You might want to add A15 → A16 in the “OS OTA Information” section for some clarifition for people on official A15 devices.

Thank you.

2 Likes

Thanks for pointing that out. Have updated the details. These are all official builds. Official builds get OTA OS upgrades and require more time to for the development and testing.

2 Likes

@Manoj I still do not get the point with the recovery e-mail. Suppose, e.email or murena.io is the only accont one has? Does it mean one needs an account at gmail or sth like that?

1 Like

In case you lose access to your Murena email due to any reason the recovery ID will be used to send you the recovery details.
This does not have to be a gmail ID it can be a safer option like protonmail or any other email you chose.
We will be adding more secure features to the services in future, and it will be good to have a recovery email set in your ID just in case some feature does not work or you lose out the passwords or access due to any reason.

1 Like

@Manoj, concerning the FP4, is there any more precise information about the update from A14? I’m mostly eager to get it because I hope that it’ll correct my earpiece speaker being is so low, even set to max, that it’s hard to have a phone call in an environment that’s not calm. I’m also curious as to whether an update will make the stock keyboard work better in swedish (or maybe the internal dictionary will be the same?).

Thanks for all the good work!

Hi @Eeasy,
I have added your low call volume feedback here Issues reported on v3.6 (#9277) · Issues · e / Backlog · GitLab let’s hope someone will be able to address this issue.
Thanks

1 Like

There are no precise ETAs available as of now. The teams both development and QA are working on multiple devices and unless they clear the builds, we will not have a date to share.

2 Likes

Hi @Manoj ,

I cannot find informations regarding the A16 builds that failed with v3.6, in my case Google Pixel 7a “lynx”.

You wrote in Week 13 that the team would try to build it again, should we expect to maybe see a A16 build along with v3.7 if the build process succeeds ? Or should we consider that A15 will be the last version for those devices ?

Thank you !

The builds that failed will be a part of v3.7.

2 Likes

FP4 - FP4 - A14 → A16

Is that a typo?

links for a Fresh installation : (you will loose your /data content)
/e/OS community FP4 download /
/e/OS community FP5 download /
Note this are links to download builds from the “community” branch (where bootloader is not relockable), builds from the “official” branch will be released in some weeks / months once the development is done on them.
.
A safe guide to install /e/OS on your Fairphone

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UNOFFICIAL TIP :

(not tested recently, please share feedback !)
if coming from an already installed “official” /e/OS and you want to upgrade to a16 “community” (without loosing data and locked bootloader)

  • using → Settings → System updater → Local_update
  • or using “recovery mode” and “adb sideload”

you will face a signature mismatch, simply choose “install anyway”
A clear guide to Upgrade your /e/OS to a new Android major version without loosing /data

Files for upgrading an existing /e/ system via local update or the /e/ recovery can be found here:

https://ota.ecloud.global/api/v1/FP4/community/

https://ota.ecloud.global/api/v1/FP5/community/

3 Likes

Thank you. But there is no way to get back to offical build later without erasing right?

No, it is not a typo.

Dears.

Am happily using e/os 3.6 on a S9+. Working very well and I keep my finger crossed for the dev of an upgrade up to A15.

Meanwhile, am very grateful that e/os exist and be so performing

Best

David

6 Likes