Feedback for v3.0.4

[Manoj]

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.

Release Date: This week

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)

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

---

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 services

[apeloff]

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

[N200]

Hey you may want to post this under Apps.

Check this other recent post about AA

Android Auto Setup: "Troubleshoot" section / enable Unknown sources - AA not opening up

Hi, I recently installed /e/os on my FF4 and got the Android 14 update as well. Following this official guide, I made it so far. Everything that basically needs to work to my needs, works… Meaning Android auto connects, I can use navigation and do calls while driving without having to fiddle around with the phone itself. Nice … It’s just that some other apps that used to work with AA before the switch to /e/os won’t work there now, and that would also be nice to have. Now to …

[MIB]

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

[Manoj]

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.

[tyxo]

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

[Manoj]

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