Week 08 2024: Development and Testing Updates

A summary of the weekly development and testing activities by /e/OS developers and volunteers. Efforts mentioned here are continuation of tasks in progress or new development activities. Updated content will have the :new: emoji.

Release

v1.20 :new:

Status: :green_circle: Release initiated

:point_right: Release starting on 22 Feb to 29 Feb

  • Issues being fixed in this release
  • The next set of new devices along with existing ones that will be upgraded ( all builds on /e/OS T) should come as part of this release.
  • Share your build v1.20 feeback here
More development tasks

Status : :green_circle: Development and internal testing

  • Updated version of the Bliss Launcher or Bliss launcher 3
  • Currently undergoing testing and code cleanup. Launch planned early 2024.
  • /e/OS browser will be updated to the latest chromium version. Team is working on adding some features to the interface
  • A tablet with /e/OS T. Tablet name will be shared once we have the go ahead from build team. The release is tied with the launch of the updated Bliss launcher. Launch planned early 2024 :crossed_fingers:
  • Easy Installer to be updated to flash /e/OS T builds. ETA to be planned
  • GSI builds to be made to run on /e/OS T. As users may be aware the current GSI is on /e/OS Q.We will skip (Android 11) R and (Android 12) S and directly update the GSI to (Android 13) T. ETA to be planned

:nerd_face: ETA: Estimated time of arrival - term used in software development to denote the estimated time when a product can be expected to be released.

Upcoming milestones information

Previous 5 releases & user feedback

Links to the last 5 releases

 

:warning: Posting information on test builds

- Please do not post information or links to /e/OS test builds on the forum. 
- These builds are as yet untested and under development and may in some cases cause user devices to soft brick.
- Such information can confuse other users who do not see these builds in the updater. 
- Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds
- If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to [join the testing team](https://doc.e.foundation/testers) 
- As part of the testing team you can share your comments on the dedicated testing telegram channel. 

 

Murena Cloud updates

Murena cloud and Self-hosting version details

Updated to NC 26.0.8.12

Status : :green_circle: Released

  • We have upgraded Murena.io nextcloud backend to NC26, which includes performance improvements, bug fixes and security patches.
  • The release notes are available here

Self hosting Murena cloud v 26.0.8 :new:

 

How to check the NextCloud version 🤓 You can find the complete documentation and current NC version under https://murena.io/settings/help >> NextCloud xx user documentation. The xx should show the latest version. - Another way to check the current version is to check the [NextCloud scan link](https://scan.nextcloud.com) and input https://murena.io this should display the current version number as well as the security level. > Please note if MurenaCloud patch number is not the same as the NC patch number, the rating would show up as bad 😐 This is not exactly a problem. We do not immediately jump to the next NC patch as soon as it is released. We first test it and then set out with the deployment.

GSI

Current GSI version

v1.17

  • Download available here
    • Sources available here
    • version is /e/OS Q (A10)
  • :point_right: The Q v1.17 GSI build is the last build in /e/OS Q
  • :point_right: GSI OS version will next move to T or A13 skipping the R and S versions. Dates for development will be shared

 

OS OTA Related information

What OS OTA upgrade means

Usually for /e/OS ROMs to upgrade the OS you have to do the following

  • If available download the correct OS build from the supported device list
  • For some devices you also need to download the stock ROM from the vendor site.
  • Take a back up of your data
  • First install the Stock ROM
  • Next install the /e/OS ROM. Here you can take help of the install guides available on our documentation site.
  • If required apply the backups you downloaded before starting the whole process

An alternate to this tedious process is where we offer the user the option to upgrade the OS OTA. This option is available for stable device builds only.
This process is easy for the user but requires a lot of development and testing effort.

Different /e/OS build types

Completed
  • Gigaset: GS290 : Q (A10)→ Android 11 (R)
  • Oneplus: avicii : A12
  • OnePlus : avicii : Q ( A10) → R (A11)
  • Fairphone: FP4 : R ( A11) → S (A12)
  • Fairphone:FP3 : R (A11) → S (A12)
  • Fairphone:FP3 : Q (A10) → R (A11)
  • Samsung: s7 / s7+ : Nougat (A7) → Q (A10)
  • Samsung: s9 / s9+ : Oreo (A8) → Q (A10)
  • Samsung: Galaxy S9/9+ : Q (A10)→ R(A11)
  • Samsung: s8 / s8+ : Pie (A9) → R (A11)
  • Teracube: 2e / zirconia: Q (A10) to R (A11)
  • Teracube: emerald & zirconia : R (A11) to S (A12)
    • All OTA OS upgrades are on stable builds
Under Testing
  • Google Pixel ‘redfin’: S(A12) → T(A13)
  • Gigaset: GS290: R(A11) → S (A12)
  • Samsung: S7 ‘herolte’ ‘hero2lte’: Q ( A10) → R (A11)
    • All OTA OS upgrades are on stable builds
To be planned
  • Fairphone: FP3 : S (A12) → T (A13)

 

Support Dropped

Multiple OS versions
  • Support for /e/OS Q is being dropped for most of the devices.

  • Exception would be Samsung S7 / edge herolte and hero2lte which will be upgraded to /e/OS R or Android 11 :new:

  • Support of multiple OS versions on the same device has been stopped.

  • If you see multiple OS version builds on the download page, switch to the latest /e/OS version.

  • In most devices it would require a manual download and installation. Take a backup before proceeding.

  • We will add a text on the images server mentioning that older OS versions are no longer supported.

  • No longer supported will mean that build would not be made in the older OS.

  • It is always advised to switch to the newer OS versions as some of applications may not work correctly on older OS as application developer stop supporting older OS.

Nokia Devices
  • All Nokia devices

    • It is not possible to officially unlock Nokia bootloaders + lack of dedicated maintainer
  • Google

    • Google Nexus 7 2013 flox
    • Device has partition size issues. Not able to build /e/OS ROMs for this device even with minimal build

    :nerd_face: Minimal build is a setting in /e/OS build which removes the following default applications (LibreOffice viewer, PDFViewer, Maps and Weather)from the source code and builds a smaller version of the ROM.

 

Murena Two now available for purchase

Where to buy the Murena Two and Murena One from?

A phone from Murena with /e/OS installed has been launched and is available for purchase. Check here. Select a country and check availablility and device specs

Expect more device releases from Murena in future :grinning:

:nerd_face: Murena is the brand name and /e/OS is the operating system.

 

Vendor specific information

Bootloader unlockable devices

As you may be aware the bootloader needs to be unlocked to flash a custom ROM like /e/OS.
The vendors of the following devices are preventing the unlocking of the bootloader

  • Huawei
  • ASUS - unlocking tool reported as not working for last couple of months.

:point_right: We have added a warning on the install pages for these devices to warn our users before they try to attempt to flash /e/OS.

 

Misc information

Upgrade guides removed

We have removed the upgrade guides from our Documentation site. Users who are planning to upgrade the /e/OS installation on their device are now advised to

  • Follow the instructions given in the command line install guide
  • If suggested in the guide, first install the stock ROM
  • Next if required flash additional partitions
  • Finally a fresh install of the latest /e/OS build
  • Follow the instructions for your devices. The instructions would be different across devices.
  • This advice is specific for OS upgrades ie. from a lower OS version to a higher version for e.g. /e/OS R to /e/OS S or Android 11 to Android 12.
Check real time availability of /e/OS and related services websites
OS upgrade info specific to the FP3
  • The FP3 OTA OS update from Pie to Q/R is not possible as encryption method changed on FP3 between Pie and Q/R. It is not possible to change the method while updating.
  • The team spent a great deal of time on this, but has not been able to resolve this problem. For now, the manual process is the only way to upgrade the FP3 from pie to other OS versions.
End of official support for Nougat, Oreo and Pie 😞 Pie, Oreo and Nougat the official /e/OS support has ended.

Reasons for dropping official support are:

  • newly released applications like App Lounge, Advanced privacy code has not been customized for these OS versions.
  • lack of dedicated ROM Maintainers
  • no support upstream (Lineage dropped support for Pie sometime back)
  • device trees will continue to exist in the Gitlab and users with build skills can create custom ROMs on these builds
  • Security patches and vendor patches for the Pie, Oreo and Nougat code will be updated based on availability.

:nerd_face: Google stops security patches for OS after some time. Similarly, Vendors drop support for older models when they release newer models in the market. Then it depends on developers from various communities to backport the patches.

Device and Vendor specific Announcements

:loudspeaker: Gigaset GS290

  • We have stopped the sales of the Gigaset GS290 on the eSolutionsShop as the vendor has stopped production of the device. We will continue support for existing users.

:loudspeaker: Message being shared on the request of our vendor partners

  • Vendors whose phones we sell on our eSolutions Store do not directly sell /e/OS flashed devices.
  • The vendors only sell their devices with their own stock ROM.
  • To get pre flashed /e/OS phones, you have to purchase them from the eSolutions Shop.

:loudspeaker: /e/OS Pre flashed device sales

  • We sell directly in EU, US, Canada and Australia
  • Find details of what devices are available in which countries here Murena Shop.
Different /e/OS build types

Check out this guide to understand differences between build types on /e/OS

 

/e/OS website and social media Links and Support

Support

  • Facing issues with devices you purchased from us ? For issues you would want support on from the /e/OS support team, send in the details using the contact form

Websites

Telegram Channel

Social Media

Newsletters

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online servicesphone

11 Likes

Pl note the release date of v1.20 has been moved ahead, Will share the final date once the testing is complete and the team decides to go ahead with the build release.

7 Likes

Hi @Manoj ,

I know that I should wait for official announcement about the Bliss Launcher and then for the tablet, but I am patiently (well, quite impatiently, in reality) waiting for the Murena tablet since long time … any spoiler? Just to confirm the model …

Thank you

PS: I know I am a pain in the neck, but last year, I already bought the protective folio for the Samsung Galaxy Tab S5e :smiley:
I would like to understand if I should wait (I guess for another month or two), or decide what to do (I wanted to avoid installing myself because it is not my cup of tea, and I believe that purchasing the device is a way of supporting Murena). Thank you for your understanding

Hello,
I see that https://images.ecloud.global/stable/hero2lte/ provides release 1.18 but not https://images.ecloud.global/stable/herolte/.
Is there a specific problem with herolte?

Both s7 and s7+ are due for the upgrade build

1 Like

Bliss Launcher v3 is still in its final stages of development. If you remember the landscape mode of the Bliss Launcher was not working on tablets. Once the v3 is complete and testing we will share the tablet name and details as the launcher has to be testing with the tablet as well.
I know it has been taking a long time as we prioritize our bugs and issue first during development.

5 Likes

Will Bliss Launcher v3 allow the user to install Trebuchet and use it as the default home screen launcher app (which is not possible with the current version of Bliss)? Or will it continue to use code from Trebuchet, and prevent the user from using Trebuchet?

EDIT:

In the gitlab issue about this, Romain Hunault wrote

  • We have to use Trebuchet for some key features (recent view, gestures…) that Google now implement within Launcher3, and not anymore in the OS
  • We disabled the home screen intent for Trebuchet, as we don’t want users to get offered so many choices from the setup wizard. A side effect of this modification is users cannot choose Trebuchet as Launcher at all.
  • We are working on a better approach for BlissLauncher, which will solve the issue. But it will take time

Ok, thank you for your answer

Update information specific to S7 /S7+ Users :new:

Build 1.17.1 will be rolled out to herolte and hero2lte tonight. 20 Feb

This is for those who are still on Q download this build. This will also be on Q but it will have the necessary upgrade files.

The actual upgrade to /e/OS R will happen once you get the v1.20 build.

For the rest of the devices the release date of v1.20 will be announced later this week.

5 Likes

Bliss Launcher 3 will allow users to use BlissLauncher3 only. You can install another Launcher (based on Trebuchet for example), but the user will have to install it.

Will have Romain update his response on that thread.

2 Likes

Hello,

I see that for v1.20-s beta build available here. I see v1.20-s beta for Oneplus Nord N200 (dre) here but I don’t see any beta 1.20-t for dre, I would like to point out. Maybe it forgottan.

1 Like

Every week, @Manoj makes a great effort to keep users updated about Development and Testing Updates.

Many questions would be avoided if we could just take the time to read this updates.

5 Likes

Thank you, I am aware of the rules, but my question was not about the beta build itself. I just want to ask about if are there beta builds for certain device, because I couldn’t see v1.20-T beta builds for device coded “dre”. I am not installing beta builds or not asking any question about beta builds itself. But for sharing link I am sorry, let me delete, I missed about links.

1 Like

Oneplus Nord N200 ‘dre’ is in our list of devices to get a /e/OS T upgrade. You can check the list here

The /e/OS T builds for the devices in this list should be coming out along with v1.20

2 Likes

Will the update come later for the dev channel?