Week 12 2024: Development and Testing Updates

[Manoj]

Summary of 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 emoji.

Release

v1.21

Status Testing in progress

Issues being fixed can be viewed here

• Builds that missed v1.20 will be available in v1.21
  • Google Pixel XL marlin
  • Motorola Moto G7 Play channel
  • Google Pixel sailfish
  • LG V30 joan
  • LG V30 h932

Coming with v1.21

• Fairphone: FP3 : S (A12) → T (A13) OS OTA upgrade build
• Fairphone: FP4 : S (A12) → T (A13) OS OTA upgrade build

ETA: To be shared

Info about ongoing development tasks click here

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

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

• Tentative release dates of builds that will come in future
   

Previous 5 releases & user feedback

Links to the last 5 releases click here

• v1.20
• v1.19.1
• v1.18
• v1.17
• v1.16
• v1.15

Documentation Updates

• Stable builds will now be referred to as Official and dev builds will be Community. This change will be visible in our Supported device list.

• Official / Stable support dropped for these devices

  • Easy Installer will flash the community or previously known as dev build for these devices
    • Google Pixel 4a sunfish
    • Google Pixel 4a 5G bramble
    • Google Pixel 4 XL coral
    • Google Pixel 4 flame
    • OnePlus 7 Pro guacamole
    • OnePlus 7T hotdogb
    • OnePlus 8 instantnoodle
    • OnePlus 8 Pro instantnoodlep

• This week we will update the Supported devices table to display the Safetynet and Rootbeer status for all supported devices

• How to backup and restore and /e/OS device

• Users may have noticed a difference in the internal storage size on fresh installations. We have created a guide to explain this.

 

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 click here

Updated to NC 26.0.8.12

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

• Release notes

• Check this guide for help with the upgrade

 

How to check the NextCloud version click here

🤓 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 click here

v1.17

• Download available here
  • Sources available here
  • version is /e/OS Q (A10)
• The Q v1.17 GSI build is the last build in /e/OS Q
• 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 click here

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)

• Samsung: S7 ‘herolte’ ‘hero2lte’: Q ( A10) → R (A11)

• Google Pixel ‘redfin’: S(A12) → T(A13)

• Gigaset: GS290: R(A11) → S (A12)

  • All OTA OS upgrades are on stable builds

Testing

• Fairphone: FP3 : S (A12) → T (A13)
• Fairphone: FP4 : S (A12) → T (A13)
  • ETA v1.21

To Plan

• Samsung: S9/9+ : R(A11) → S(A12)
  • ETA Will be shared later

 

Support Dropped

Motorola Motorola Moto G7 Play channel

• Support for the Motorola Moto G7 Play channel is being dropped.
• We have been unable to build builds for the device post v1.17 which was on /e/OS T.
• Builds for the MOto G7 Play channel are failing as there is not enough space on the device to sustain all our default applications.
• Users with ROM building skills will be able to create customized builds of the channel if they so desire as the device trees will be available on our servers.

We are checking for build issues with Pixel XL marlin and Pixel sailfish . Will update if these two are also in the list of devices for which support will be 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

• 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

  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

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.

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

• eCloud related websites

• /e/OS related

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.

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

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.

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.

/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

• Murena
• /e/OS website
• Documentation
• Where to Report issues
  • How to report issues

Telegram Channel

• Link to all the available Telegram channels

Social Media

• On XDA
• Twitter
• Mastodon
• LinkedIn
• Medium

Newsletters

• eFoundation news
• Murena products and promotions

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

[piero]

@Manoj

This week we will update the Supported devices table to display the Safetynet and Rootbeer status for all supported devices

[Harrier]

@Manoj

@Manoj

To Plan

• Samsung: S9/9+ : R(A11) → S(A12)
  • ETA Will be shared later

There’s already a dev build of T(A13) for the S9 , but there isn’t any dev S(A12) build, so just wondering if this OTA upgrade is going to be R(A11) → T(A13) instead ?

[Manoj]

The Supported device list has been updated to reflect the SafetyNet and Rootbeer status.
A document of the updates is available here

We will share names of some apps you can install on your device to test SafetyNet and Rootbeer implementation. In case you find they are not working on your device contrary to what has been mentioned in the Supported device list please do let us know.

[PraksuQ]

@Manoj

The Supported device list has been updated

@Manoj : There is non official /e/OS Version for dream2lte at the list. But at many locations you write that it still belongs to official/stable?

[Manoj]

@PraksuQ

There is non official /e/OS Version for dream2lte

The dream2lte is Samsung s8+. Let me know where it shows as official build and will have it corrected.

[PraksuQ]

Here are three places:

@Manoj

stable builds will be available for devices we sell in our Murena Shop . That means stable builds will continue to be available for the following devices FP3 , FP4 ,FP5 , Murena one, Murena Two, GS290, zirconia, emerald, herolte, hero2lte, dreamlte, dream2lte, starlte, star2lte, redfin

@Manoj

stable builds will be available for devices we sell in our Murena Shop . That means stable builds will continue to be available for the following devices FP3 , FP4 ,FP5 , Murena one, Murena Two, GS290, zirconia, emerald, herolte, hero2lte, dreamlte, dream2lte, starlte, star2lte, redfin

@Manoj

Official / stable builds

Both Safetynet and rootbeer working

The devices are

- Gigaset GS290 
- Teracube zirconia 
- Teracube emerald 
- FP3 
- FP4
- FP5
- Samsung Galaxy S8+ **dream2lte**
- Samsung Galaxy S8 dreamlte

[Manoj]

Hmmm none of the developers corrected me on this! Let me recheck the s8+ plans with them

[piero]

https://images.ecloud.global/stable/dream2lte/

[Manoj]

That is what needs to be checked. The builds are getting made but the stable build is not showing up on documentation. Could be an error where documentations files got overwritten or there could be other plans. Will get back with details once the team is in office during EU hours.

[Jean_Karlos]

I’m a little confuse. The “test.ota.ecloud” page is returning 404. When I was participating of v1.20 test my device received OTA beta by updater, the same zip was available at test.ota.ecloud and I was able to access the page to get subsequente RC. But now, my device received v1.21 beta by updater, but there isn’t a list of “dev” zips in issue page and the test.ota.ecloud is offline. In telegram channel nobody answered me about it.
Where is the links to v1.21 beta dev? There’s alredy rc version?

Xiaomi MI9 SE - grus

[PraksuQ]

@Jean_Karlos : I’ll send you an message

@Manoj

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 ca

[Manoj]

Samsung s8+ dream2lte will get the official / stable builds. The link in documentation was overwritten. It has been corrected. You should be able to download the builds as well from the link on the server

[Manoj]

@Manoj

Pixel XL marlin and Pixel sailfish

This is to confirm that Pixel XL ‘marlin’ and Pixel ‘sailfish’ are being dropped from the Supported device list.

The reason is the same with lack of enough internal space for the /e/OS builds. Users wth ROM building skills should be able to make unofficial builds from device trees which would still show up.

[aibd]

@Manoj

/e/OS T builds

Status : Build and testing

Team is working on adding firmware along with the T builds. This will make it easier for users to flash the builds without having to flash the stock ROM first.

• First list of devices getting the /e/OS T build.
• Builds will require manual download and installation by users. It is advisable to take a complete backup of data before any OS upgrade.

I wonder if you would consider a Feedback page for the manual upgrade S → T in dev or Community builds.

LineageOS Upgrade pages do not tell users to Format data but they generally do or did include in their links upgrade only their equivalent of Android S → T.

• (Now these LineageOS upgrade pages have to be read with care as some Upgrade pages are now written for T → U.)