Feedback for v3.0

[Fox]

Hello to everyone,

recently I’ve had a reason to full reset, update and experiment with one of my phones and so far I’m quite happy with /e/ OS. Cleaner and more functionally (basic system applications) than microG LineageOS, let alone the brand original stock ROMs, which are a bloatware- and telemetry-horror.

Vendor Name: OnePlus
Device name: OnePlus 9 Pro Europe Vers. (LE2123)
Device CodeName: lemonadep
Version which existed previously: Varying. Before /e/ 3.0 it was Stock OxygenOS 14.0.0.1901(EX01)
Is the device Rooted / Not rooted: Not rooted right now.
There’s only a community version for this device, so that’s what I used.

I’ve experimented with vendor most recent Android 14 (OxygenOS 14.0.0.1901) as full update(s) after flashing a clean vendor partition array via MSM tool.

Initially as an experimental tryout, if it would work based on this A14 (I could always reset it, even if it soft-bricked).

Afterwards flashed the necessary /e/ partitions (dtbo, vbmeta and vendor_boot) via command line, then sideload of the community 3.0 /e/ for lemonadep.

Almost everything works fine and without any noticeable hassle.

What caught my attention in terms of bugs:
→ there are three antenna signal strength symbols in half-extended scroll down, while (left) two are clones (dual SIM phone, no eSIMs).

In full-extended (two time scroll down) mode only one sim is shown with one signal strength (antenna) icon.

→ The “Dark design” - “full / pure black” function works in several desktop menus, as shown in the images upwards, but as example in “settings” it is a light grey not “OLED full black” option.

→ The “Trust” status shows “vendor: outdated”, while it is presumably newer than recommended (latest official security vendor update which the device probably gets, as update timeline ran out after it).

Those aside it works, even with the unfortunate bug found in 3.0 mostly associated by the unfortunate FairPhone users (fixed in 3.0.1 that might take a few days for community versions like mine for the OnePlus 9 Pro) I’ve had no problems aka automatic reboots or even just any crash, it never crashed anything.

Flashing hung two times at restarts, which was easily fixable by manual enforced shutdown, but that’s possibly linked to me not using an A13 vendor image priorly to /e/ 3.0.

Another find is related to the embedded Google applications (mainly Google assistant) in a probably non-functional form as system app, which was initially mentioned for the OnePlus 9 Pro by @Ahappo in this thread:

Pre-installed Google Apps on a De-Googled System? My Frustrations with /e/OS Latest Updates

Lately, the developers of /e/OS have started releasing pointless apps and bundling them into system updates—apps that can’t be removed without using adb. For example, the recently added parental control feature: seriously, how many users actually use this? Maybe 0.01%? Fine, but what about “Find My Device”? I installed version 3.0 and wanted to disable it, but of course, that wasn’t possible. Sure, this feature might be important to some, but why not give users the option to turn it off? Anothe…

It was brought to attention by @particularteal as the thread’s Original Poster for another device initially.

Thank you, @Manoj and all others for the good communication regarding the withdrawal of v3.0 and the coming v3.0.1.

I’m interested if other users of v3.0 on the OnePlus 9 Pro or different devices as well experience the mentioned effects with signal strength symbol / pure black mode on their devices.

[MIB]

Hi,

On my side, not possible to update to 3.0 because no update is available : /e/OS community beyond0lte download

Vendor Name : Samsung
Device name : S10e
Device CodeName : beyond0lte
Version of /e/OS or Stock which existed previously : 2.9
Is the device Rooted / Not rooted : Not rooted

@Manoj , when is it plan to give again access to update for S10e (no 2.9, no 3.0) ?

[MIB]

Hi,

On my side, not possible to update to 3.0 because no update is available : /e/OS official tangorpro download

Vendor Name : Murena
Device name : Pixel tablet
Device CodeName : tangorpro
Version of /e/OS or Stock which existed previously : 2.9
Is the device Rooted / Not rooted : Not rooted

@Manoj , when is it plan to give access to 3.0 update for Murena product ?

[Gmurena]

Hi aibd,

I’m actually here as a result of the 3.0 update problem. I was previously on 2.9. Phone was working fine for a few days after the 3.0 update. Then the morning I posted, my phone started behaving exactly as an Anonymous user posted above in what looks like post #189:
( “for my Pixel 5 this process doesn’t work.
The failure point is after step 8 : as soon as I unlock the screen the phone restarts automatically so I have no time to change the settings unfortunately.
I’ve tried the plug/unplug of the USB method you mentioned at steps 4 and 7 but it did not gave me more time to change settings after I entered the pin code…”)

At that point, the only way I could even turn my phone off was to pull the battery. It now boots directly into the recovery screen. I am able to “move about” through that recovery mode so I think the side load will work. The problem is, I suppose I have to wait for an official Emerald build, as you also stated.

And yes, I’ve always heard to give an update a week or so and check forums before updating, but against my better judgment, I jumped the gun. Won’t be doing that again…

For now, I’ve got my SIM in my previous flip phone and can run it as a hot spot for a laptop. Hopefully an emerald comes soon because I love this phone and OS. Not going back to the other guys…

Thank you!

[aibd]

Let’s ask @nicofonk if there is a 3.0.1 cooking for emerald.

[Manoj]

@aibd

is a 3.0.1 cooking for emerald.

3.0.1 will be released for all devices which should have or got the 3.0 build. If there are any exceptions we shall update on the forum.

[Gquirt]

I just decided to wait. I was too scared to try it.

Glad to see another Zenfone 8 user

[SCOT1]

When approximately can we get 3.0.1 OTA ?

[Manoj]

@Manoj

11 June Official builds
09 June Community builds

There is an update on the release dates. We are going ahead with a staggered release to avoid any issues with the roll out. The updated dates are given above.

[aibd]

@Fox

→ The “Trust” status shows “vendor: outdated”

This comes up quite often and I find that section unhelpful at best; as I understand it neither AOSP nor /e/ has tried to eliminate it.

Loosely speaking when a manufacturer gets into bed with Google’s software they undertake to keep the firmware up to date by release of Vendor Security Patches as frequently as required. Manufactures vary, some may do this for < 18 months others longer. Once Google deems the Updates were not sufficiently frequent this “Trust” is lost. Some would say that this is a fine way to encourage users to buy a new phone.

You can check the actual Vendor SPL from Settings > About phone > tap Android version.

Most devices will follow this example; with /e/OS correctly installed observing the install page (quoting lemonadep)

Before following these instructions please ensure that the device is on the latest Android 13 firmware.

this will result in the user having already installed the final manufacturer’s software revision.

Of course, never mind the “Trust” issue, having the final manufacturer’s software revision is very much worth checking in the event of problems.

Many /e/OS builds from AOSP 13 (T) on do actually contain the vendor parts in the ROM that provide these final blobs.

These comments should not apply in the case of a phone here the Android OS is still in active development.

[Aln]

@Manoj:

Hi,

I’ve been having major problems since 3.0 and 3.0.1. Version 3.0.1 fixed the recovery boot issue, but it’s also causing other major problems.

1. My system battery level is frozen (it won’t go down). I was at 68%, and I recharged with the USB cable for a short while (smartphone off). I’m at 70%, and E/OS is showing 70%. However, I used the internet for 15 minutes, and the battery percentage hasn’t changed. This is a very big problem.

2. Regarding the internet, last night, I tried using the internet via 4G and 5G, but I couldn’t. This morning, I tried again, and it’s fine (on 4G and 5G). However, IP address masking was enabled. I disable IP address masking. I restart the browser, and it tells me: “No internet connection.” OK. I reactivate IP address masking, I restart the browser, and it tells me: “Connection established,” but it doesn’t display anything. I can’t connect to the search engine (errors).

Notes:

1. I would like to point out that I received an error message last night when I enabled IP address masking: “orbot configuration invalid” and “random country” was set by default.
2. If I remember battery level still worked on e/os 3.0. After connecting my FP4 with the usb cable on the computer and updating e/os with 3.0.1 version, battery level won’t down anymore.

So, two major issues for now (FP4 A14 Official). A 3.0.2 version will be necessary.

[Aln]

Thank you very much to you.

[ralxx]

@nicofonk for non-pactes users:
Will they be able to download and install the 3.0.1 update as usual via the built-in updater?

[Fox]

@aibd

This comes up quite often and I find that section unhelpful at best; as I understand it neither AOSP nor /e/ has tried to eliminate it.

Definitely - while I can understand the wish/need for this “analysis” through Trust, it is misleading in many ways and might confuse “novice” users.

@aibd

You can check the actual Vendor SPL from Settings > About phone > tap Android version.

Yes, I’ve an A14 /e/ 3.0 flashed over an A14 latest vendor setup with latest updates (probably the last updates OS-version related to this device, as the three-year support time ran out end of may, if I’m correct).

The vendor security patch level is from 5th Jan. 2024, which seems to be the latest time they added new vendor security patches in their vendor firmware (and as such in any third-party OS, as well).

Even as it is still describing A13 as the necessary firmware, I was interested in checking if it works well with the newest stock vendor updates prior to the community (only available) A14 /e/ for lemonadep.

And it works fine, no big flaws, aside those described upwards.
No crashes, sound is okay, camera app works with photos (didn’t try videos yet) and is ways more versatile and configurable compared to what official vendor ROM and LineageOS offered 2023 (LOS added GCam if I’m right on a later version).

So the “please ensure that the device is on the latest Android 13 firmware.” is not an ultimate necessity for the actual /e/ for this device to work fine - but it is a good information for all those which are not into the technical backgrounds and just “want to install and use it”.

@aibd

Of course, never mind the “Trust” issue, having the final manufacturer’s software revision is very much worth checking in the event of problems.

Definitely, that’s the reason why I went the “latest stock vendor ROM updates of May 2025” route prior to /e/, because there were critical security flaws patched by it and if some were based on the device vendor firmware… better to have them fixed. Edit: Seems not to be the case, as of the Jan. 2024 latest vendor patches.
Even if it goes against the “Android 13” requirement of the FAQ.

@aibd

Many /e/OS builds from AOSP 13 (T) on do actually contain the vendor parts in the ROM that provide these final blobs.

That’s good to know, thanks! I’m no Android programmer / developer, so even if I can understand and follow the technical compositions, I don’t have the experience to “know” what’s standard in the ROMs nowadays, even less for /e/.

@aibd

These comments should not apply in the case of a phone here the Android OS is still in active development.

I guess the A13 instruction could be changed to “A13 or A14” for lemonadep, if the 3.0(.1) releases are available (again), as the latest vendor parts seem to work just fine. I didn’t try it with /e/ 2.9, tho.

They work fine with A15 of LineageOS, as well, I tested this prior as they changed their information to “requires A13 or A14 latest firmware” in the FAQ already).

[Fox]

A quick information for interested users:

On OnePlus 9 Pro aka lemonadep with /e/ 3.0 the update to 3.0.1 is now available.
BUT: It does not show on each manual refresh in the update menu/component under Settings.

It sometimes takes 1 - 5 retries until it is shown.
If it is shown, don’t click “refresh” again, else it is gone again - until you click a few times and it pops back up.

I assume that’s a slight bug, which could be existent for other devices, as well.
So: if you want to check if 3.0.1 is available for a community build (device), you should not just refresh it once, but instead wait a few seconds and refresh it 2, 3, 4… times.

If there’s no update after 4-5 tries, it is fair to assume that it is not yet available.
Edit: If you start the download and then pause it, it will stay visible - even after refresh / check for new versions again.

(Other alternative would be to download it manually and use “local update” method in the updater, but that’s more work than checking a few times.)

And: I personally would - if your device is on 3.0 right now and works without flaws - wait a few hours to days and check if there are new critical issues reported. Because there was at least one new issue reported further upwards for one device:

Feedback for v3.0

@Manoj: Hi, I’ve been having major problems since 3.0 and 3.0.1. Version 3.0.1 fixed the recovery boot issue, but it’s also causing other major problems. My system battery level is frozen (it won’t go down). I was at 68%, and I recharged with the USB cable for a short while (smartphone off). I’m at 70%, and E/OS is showing 70%. However, I used the internet for 15 minutes, and the battery percentage hasn’t changed. This is a very big problem. Regarding the internet, last night, I tried us…

[aibd]

@Fox

It does not show on each manual refresh

Many users are already aware of the nature of the “staggered release”. A previous briefing included the concept of 25% available – as if to say only 1 in 4 requests to the server can be successful.

[Fox]

Ahh, I see - wasn’t sure if it was a wanted feature or a bug.

Usually in staggered distribution it isn’t refreshed to random values, but more or less linked to something - IP address of requester, client ID (not an option if there’s no identifier or it isn’t used for such purposes, which would be privacy-oriented).
This would be helpful to actually enforce the staggered distribution, as it wouldn’t change the results by each refresh, but only by a server set time span after which it is newly “diced”.

But good to know that’s the reason.

Interesting that the update client as well removes it from the results if it isn’t received by the query anymore (a positive effect in terms of withdrawn defective updates, which are not yet downloaded to a device, I assume).

[nmatheis]

Hello. This is my first post as I just started testing /e/OS before v3.0 was released. Everything has been running smoothly before & after the update.

Vendor Name: OnePlus
Device name: 8 Pro
Device CodeName: instantnoodlep
Version of /e/OS or Stock which existed previously: Not sure. Whatever I downloaded a week or so before v3.0 war released.
Is the device Rooted / Not rooted: Not Rooted

[aibd]

@Fox

The vendor security patch level is from 5th Jan. 2024

This is good for the user to know … but my remarks started “Loosely speaking” on the subject of Vendor SPL … I mentioned firmware revisions … but one has to bear in mind around the world there can be firmware revisions which do not impact SPL.

I say this because one should not go on to think to challenge Install instructions (not that you actually were … experimentation is fine).

Back to my concern: Install instructions

@Fox

latest Android 13 firmware.” is not an ultimate
…
it is a good information

It is good information. Period.

We should perhaps look at the build frozen when the developer created the build, we look at the Device tree, there is only one branch for AOSP 13 (T) GitHub - LineageOS/android_device_oneplus_lemonadep at lineage-20.

In the Lineage world there is only one branch for a14 GitHub - LineageOS/android_device_oneplus_lemonadep at lineage-21.

In the “developing” Lineage scenario there are branches for Lineage 22.0, 22.1 and 22.2. This is where the bleeding edge lies … but not where /e/ Install instructions are at.

• Aide memoire Android / Lineage version numbers

(Maybe worth bearing in mind that lemonadp almost certainly was liberated to AOSP while active manufacturer development was ongoing … but this is not really a subject for the Feedback thread, inho.)

[WikiTang]

I followed the procedure described here: Feedback for v3.0 - #217 by nicofonk
and downloaded the correct build for FP3:
https://test.ota.ecloud.global/official/FP3/e-3.0.1-t-20250606498724-official-FP3.zip

The installation went through without any visible errors on slot B (via fastboot set_active b).
However, now my phone won’t boot at all. It gets stuck on the Fairphone logo and vibrates every 4–5 seconds.

I also tried booting on slot A (fastboot set_active a), but I get the same result: bootloop.

---

This is very frustrating. I feel completely stuck and don’t know what to do next. My phone is currently unusable, and I have important, unsaved data on it. I’m honestly really disappointed by this situation.

If anyone has advice on how to restore access to the device without data loss, I would be extremely grateful.

Thanks in advance for your help