Feedback for v3.0.4

Release Information

Please share feedback on v3.0.4 build for your device and let us know how it is working with applications that you use.

:point_right: Release Date: This week

:point_right: Release Note - will show up here once the release has been initiated.

Some points about the v3.0.4 release

  • Release will be sent out to both official and community devices

  • Community devices that did not get v3.0.2 will directly move from v3.0.1 to v3.0.4

  • Official devices will move from v3.0.2 to v3.0.4

  • A13 Official/Community will move from 3.0.1 to 3.0.4 this includes June security patch, browser security updates and accessibility related updates

  • A14/15 Community move from 3.0.1 to 3.0.4 includes June security patch, browser security updates and accessibility related updates

  • A14/15 Official builds move from 3.0.2 to 3.0.4 contains June security patch and Browser security updates


Feedback poll

We will also have a poll to rate this build.

  • I have updated to v3.0.4 on my device and it is working well
  • I updated to v3.0.4 but I am having issues (Please share the issue details on this thread)
  • I am not able to update to v3.0.4 (Please share the issue details on this thread)
0 voters

:point_right: To report issues with the build or applications raise an issue on gitlab. Ideally first discuss the issue here and check if users of the same device on this build are having the same issue.

When sharing your feedback or issues, Please add the following details

  • Vendor Name

  • Device name

  • Device CodeName

  • Version of /e/OS or Stock which existed previously

  • Is the device Rooted / Not rooted

Refer this table for vendor, codename details

Refer this guide to share more details in your feedback


:warning: Do not share test build information on the forum or in this thread

  • This thread has been created specifically for posting information on official and community /e/OS builds.

  • To understand the difference between build types refer this guide

  • Please do not post information or links to /e/OS test builds on the forum.

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

  • As part of the testing team you can share your comments on the dedicated testing telegram channel.

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

6 Likes

What’s the status of Android Auto on A14/15?
The doc currently states that AA only works on A13.

Hey you may want to post this under Apps.

Check this other recent post about AA

1 Like

Hi,

On my side, not possible to update to any version since 2.8 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.8 A14 (e-2.8-a14-20250220470208-community-beyond0lte)
Is the device Rooted / Not rooted : Not rooted

@Manoj , do you know when update will be back for Android 14 on S10e

Unfortunately the S10 series sources are not updated upstream and on our side we are not able to proceed with the builds. Since we do not have a maintainer on our side we are dependent on the upstream device code trees. If the situation does not improve we may have to drop these devices from our list.

That is bad. I specifically purchased a new S10+ because it was always on the lists for upgrade.
Is there anything we can do?

If would help if we had a dedicated ROM Maintainer who owned the devices , can build, test and debug the device ROM.

2 Likes

In this forum, there are certainly some who might be able to do this. This sounds we need something like a miracle. :pensive:

@Manoj, I will add a side note for others. Please move if it, if it is not appropriate here.

Sidenote: It appears that iodéOS is still supporting (unofficially supported models by the iodé community) the S10 (S10e (beyond0lte), Galaxy S10 (beyond1lte), Galaxy S10+ (beyond2lte)). This might be some alternative, albeit I prefer to stick to /e/OS.

2 Likes

…and if the miracle doesn’t happen, unfortunately leave eOS and go to LineageOS to have an up-to-date OS. :disappointed_relieved:

@MIB @Lionel.R Methinks, our task is to figure out why iodéOS can build their ROMs (seems they can handle the bugs from current tree). Thus, in general it is doable. Now, we just need to figure out how considering the hints given by @Manoj.

2 Likes

Hi @tyxo,

For /e/os you have two Android versions available for S10e:
Android 14 : update available until 2.8 (my case)
Android 13 : update available until 3.0.1

For Iodé you are talking about, they released version 6 which seems to be based on Android 15.

Is it the reason why they are able to released something for S10e ? I dont know

@Manoj, do you plan to migrate S10e to Android 15 ? Can it fix the issue you are talking about ?

I saw here ([LIST] Supported devices which would receive an AOSP 15 or /e/OS V build) that Android 15 was planned for S10e. Is it still the case ?

On LineageOS, it seems Android 14 is not supported anymore but Android 15 is (Info about beyond0lte | LineageOS Wiki)

1 Like

Yes, the s10 devices including the s10e are all in the A15 list.

3 Likes

Thanks a lot! So we have juste to wait some weeks to have again updated OS. I will wait

From what I understood of the previous conversation with @Manoj, there is no maintainer for the devices, so I don’t see why there should be a functional version with Android 15. Maybe (hopefully) I misunderstood something here completely.

UPDATE: It seems that the non-working builds affect the Android ̶1̶̶3̶̶ ̶̶a̶̶n̶̶d̶̶ ̶14 versions. S10 owners, please be patient and wait for A15 builds, which are in the making.

UPDATE: from 14 to 15 works now Week 29, 2025: Development and Testing Updates - #5 by tyxo

🆂🅾🅻🆅🅴🅳

6 Likes

Device: DRE
e/os: e_dre-user 14 AP2A.240905.003 eng.root.20250709.150023

Issues:

  • Take screenshot action missing in App Drawer when in 90º degree view.
  • Kill foreground app missing from long press action
  • stock camera app - unreadable text when taking close range pictures
  • Advanced Privacy - location breaks/stuck
  • Not receiving incoming SMS texts.

All issues carried over since e/os 2.0

Fairphone | FP3+ | FP3 | previously on e-3.0.1-a14-20250608498955-community-FP3 | not rooted

Update went smooth, not much testing done yet.


Other FAIRPHONERS, feel free to check what’s online for you right now (no direct download links, just overviews of available downloads):

/e/OS community FP3 download or /e/OS official FP3 download
/e/OS community FP4 download or /e/OS official FP4 download
/e/OS community FP5 download or /e/OS official FP5 download
/e/OS community FP6 download (not yet) or /e/OS official FP6 download

6 Likes

Vendor Name: Xiaomi

Device Name: Mi 9SE

Code Name: grus

Version of /e/OS which existed previously: e-3.0.1-a14-20250608498955-community-grus

Device Not rooted

Vendor Name: Xiaomi

Device Name: Redmi K20 / Mi 9T

Code Name: davinci

Version of /e/OS which existed previously: e-3.0.1-t-20250609499174-community-davinci

Device Not rooted

Vendor Name: Oneplus

Device Name: 7 Pro

Code Name: guacamole

Version of /e/OS which existed previously: e-3.0.1-a14-20250608498955-community-guacamole

Device Not rooted

OTA Update Installation without errors

all devices run very smoothly.

no mistakes so far, wonderful work

Big thanks to the developer team, everything works perfectly. :slight_smile:

Updated to /e/OS 3.0.4-20250710507811-community-bardockpro
No issues, all good.
BQ Aquaris X Pro
Previous Version /e/OS 3.0.1-t 20250608499174-community-bardockpro
Device is not rooted

  • Vendor Name : Google
  • Device name : Pixel 6a
  • Device CodeName : Bluejay
  • Version of /e/OS or Stock which existed previously : v.3.0.1-T-community
  • Is the device Rooted / Not rooted : Not rooted

FP3
previously on e-2.9-a14-community
not rooted
not relocked

I see always more system apps with problematic permissions that cannot be disable…

IT IS VERY VERY DISAGREABLE …

i am at a point where i am tempted to build myself (using /e/ sources, Thank you) to be able to use a user respectfull android system !

My trust in /e/ team policy is more and more damaged each month as i feel it is becoming more and more a mainstream android OS…

3 Likes