Week 03 2024: Development and Testing Updates

Next Release

v1.19.1

Status: :green_circle: Release due

  • Staggered release : 15 Jan - 22 Jan

  • Issues and fixes

  • Release notes will appear here once the release is initiated

  • User Feedback and voting for v1.19.1

Upcoming milestones information

Upcoming Development information

Click here to Read more

Status : :green_circle: Development and internal testing

  • FP4 /e/OS T stable release is planned with v1.20 (tentative ETA Feb 2024)
  • 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.

 

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

Current Murena cloud version

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 25.0.8.19

 

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

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

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/ the unGoogled mobile OS and online servicesphone

14 Likes

Thanks for your work.
Will there be a dev version of s1.19 for the fairphone 3? it missed version 1.18dev, so i’m quite curious.

2 Likes

When you are on dev, then you will need to manually switch to T v1. 9.1.

https://images.ecloud.global/dev/FP3/

Because of the ‘one OS version per device’ policy there will be no more OTA for S on FP3.

3 Likes

Hi @Manoj ,
my best wishes for you and your family for that new year.

About the 1.19 upgrade :

  • Appolon 1.18S to 1.19.1S : OK no issue so far.
  • Kebab 1.18T to 1.19T : “installation error” coming “automatically” at the end of the download. So no possibility to upgrade. If more data are needed please feel free for requesting.

You might try

1 Like

@Manoj , how can I join on the gitlab? I was looking to see if I could contribute to the bliss launcher, but I am not able to find a way to join. I have tried multiple ways.

Also, I saw that the launcher3 update references were deleted. Do you know why?

Thank you,
Layne

thanks @aidb for your swift answer. Unfortunately it doesn’t help, still impossible to upgrade.

@Manoj , please add the link Feedback for v1.19.1 in your initial post . I switch to that topic to expose my issue with v1.19.1 update.

1 Like

Thanks for pointing that out. Have added the link.

1 Like

You can refer this guide for gitlab access.

@Manoj

Hi Manoj,

Thanks for your weekly reports, which help understand what is going on “behind the scene”.

In that regards, I’m surprised that my FP3, bought on Murena, is still stuck on stable-s and not even planned for the OTA upgrade. Can you ask the team for mire info on that concern ?

Thanks and again, even without, I’m more than happy after all thoses years with eOS !

Here are some Infos:

1 Like

@solanum Thanks for your kind answer. I did see this information as well ; this is why, after several month of “to be planned”, I was looking for detailed informations via @Manoj ; if he had any.

Are there no tablets officially supported yet?

(I’m almost to 100% in moving off my iPhone to my /e phone and just started looking into a tablet to look at switching off the iPad too. :slight_smile:

-robin

We do support a few tablets as of now. You can set the filter to tablet and view them here

2 Likes

Hah; the filter on that table doesn’t work at all on either of the browsers I use on the laptop and I hadn’t tried it on my phone. :slight_smile:

Thanks.

Works fine on my Windows 11 Pro 23H2 desktop with

  • Firefox 121.0.1
  • Vivaldi 6.5.3206.55
  • Edge 120.0.2210.133

Could you share browser and OS details, so that this can possibly be examined by the team?
What does “doesn’t work at all” mean? Can the search options be made visible at least? (Doesn’t work if e.g. all JavaScript is blocked.)

That probably wouldn’t be a good use of anyone’s time; I run an older MacOS (though my Firefox is current) with a lot of content filtering. My experience is not going to be normal. :slight_smile:

(My /e/os phone is the only device I have that renders any Discourse site usably, for example. On my Mac, this site just shows the “e” at the top of the page and the text of the current post; none of the buttons or nav features are visible at all. And that’s in Safari with JS enabled; I haven’t even bothered to try it in Firefox with noscript.)

It’s really not worth trying to replicate most web site display issues I have. :slight_smile:

Thanks, though.

Hi @Manoj,
What is the meaning of the FP4 1.19.1 build for t-stable here? Does that mean we can have an upgrade OTA with 1.19.1 or should we wait for 1.20 as you said on this post?

The meaning is that you could install this build manually using the instructions given at https://doc.e.foundation/devices/FP4/install (which links to the download page).

No. This download page doesn’t indicate OTA upgrades to new Android versions. OTA upgrades, once available, arrive via the updater.