Feedback for v3.4

/e/OS Smartphone Operating System Build Feedback
22

The link was not intended for OTA zips, more to see what is available but irrlicht has a certain idea in mind how the overview should be.

In that regard you are absolutley right

23

i am for

  • image.ecloud.global/<devicecodename> giving IMG files
    and
  • ota.ecloud.global/<devicecodename> giving OTA files

but they are the same, both only showing IMG files, and both also hosting hiden OTA filesā€¦

1 Like
24

Did you find the app on Aurora? I didnā€™t (I got an FP6), therefore I do not expect it do be accessible on Aurora. I suppose there is some logic behind which allows App Lounge to be able to download it on a FP6. I remember the same when I used stock years ago, there were OEM apps which canā€™t be found by other brands.

You will need to use App Lounge just for that. But youā€™ll find it out soon enough :slight_smile:

25

Thanks. Indeed I will probably have to use app lounge only for this. I would have loved to get those apps from a specific FDroid repo with e/OS apps though.

26

I find the power usage at present practically unbearable.

From the battery point v3.4 is by far the worst I have seen since 1.109 days.

This is how the graphs look on the fifth day after installing:

20260121_FP3_PU_xsv
20260121_FP3_PU_xsv923Ɨ542 45.1 KB

The crossing lines are a little astounding as the power usage nearly trippled. It was bad at v3.3, now it is devastating.

And I had to even drastically change the scaling in order to get the graph inside the chart:

20260121_FP3_Ch_xsv
20260121_FP3_Ch_xsv923Ɨ542 61.6 KB

Top users are the mobile network, Matrix, Advanced privacy and the ntfys.

Anyone caring for this?

28

Iā€™m not yet on v3.4 (waiting for official release for FP6) but I also saw an increase in power consumption between v3.2 and v3.3. However are you not supposed to wait a few days after an update to let the system complete some adjustments before taking those measurements? With v3.2, I initially experienced a high drain after the update which settled after a few days. With v3.3, the drain seem to remain even after weeks though.

29

Suggest you create an issue in gitlab and share these details there. If already done pl share the issue ID.

1 Like
30

Measuring is good. And I think you provide constant and comparable measuring conditions.

But I canā€™t imagine these absolute numbers. I call my FP3 fine tuned related to energy consumption, this has always been a matter for me. But in daily life I never had more than 2.5 days with my FP3 (the nights already in flight mode) before it came below 15%. Even when I switch off all the connections permanently and let it in the pocket I donā€™t get more than 3.5 days. And this has been the case with all previous /e/ versions. So, six days with 2.8 - how??? This makes the absolute level of the upper diagram questionable.

Nevertheless there are also relative statements in the diagram. But knowing my device what should I expect now? 3.4 gives me half a day? Not sure.

1 Like
31

Thank you for yet another exciting release of /e/OS! Iā€™m looking forward to try it when it releases to official.

ā€œFairphone Moments is now available on /e/OS: :tada: Itā€™ll be automatically updated via App Lounge whenever an update is available.ā€

@Manoj This is a good approach. What about the Fairphone camera app, is it also getting updates from Fairphone? Is it a manual process for your team to include new releases of the camera app? Could it be updated by App Lounge whenever an update is available? (Asking for FP6 and also previous Fairphone models)

32

Checked with the developers. Unlike the Moments app the camera is integrated into the system code and cannot be separated from it to be delivered as a standalone app. The updates to the camera happen along with OS updates as on the version of the FPOS we are picking up. For example, v3.4 has the latest camera code as on FPOS.

6 Likes
33

Excellent, thank you for the clarification!

34

Everything works fine so far. Thanks :+1:

1 Like
35

Fairphone 6, v3.4:

  1. I had a custom launcher (Kvaesitso) configured when I enabled Moments.
  2. I used it for a short bit and then turned it off again.
  3. I changed the switch setting back to Privacy Sensors.
  4. My launcher was reset to Bliss Launcher and I had to reenable my custom launcher from settings.

I now tried to recreate the issue following the above steps, but it keeps my launcher somehow on my custom one. So it was perhaps a one off? The animation of ā€œessentials activatedā€ with the green bar on screen next to the switch is no longer displayed though. Not sure if that is as intended.

36

v3.2 started on 25.10.25 with a consumption of 40.4%/day resulting in a running time of 2.47 days and ended with an overall average of 23.3%/4.30 days on 04.12.25. Overall the charging time was 1:28 hrs/day.

v3.3 ran from 11.12.25 through 12.01.26 with rates from 1.91% per hour, 45.6% per day, resulting in a running time of 2.19 days at the beginning to 45.8%/day and 2.19 days overall running time. Charging time was 2.44 hrs/day.

I calculate the theoretical running time as if you would charge to 100% and let the device drain until itā€™s empty at the eventual rate. This way those numbers are created that I do not expect anyone will ever achieve practically.

My measurement for v2.8 began on 20.02.25 with 13.0%/day and 7.71 lasting days and ended on 20.03.25 with 16.6%/day resulting in a (theoretical) lasting of 6.01 days. Charging time was 1:16 hrs per day.

These are the numbers I found. They differ dramatically from the current numbers.

Will take this to Gitlab.

37
  • Samsung
    S10e
    beyond0lte
    Version previously: 3.3-a15-community
    Not rooted

Update went smooth and fast. No issues so far.
Thanks to the team maintaining this device.

2 Likes
38
  • Vendor Name: Google
  • Device name: 6a
  • Device CodeName: Bluejay
  • Version of /e/OS or Stock which existed previously: 3.3-a15 ā†’ 3.4-a15 community
  • Is the device Rooted / Not rooted: No
  • Bootloader locked / not locked: unlocked

Update went smoothly, thanks to the team.

39
  • Vendor Fairphone
  • Device The Fairphone
  • Device FP6
  • Version of /e/OS or Stock which existed previously a15-3.3-community
  • Is the device not rooted

@Masqueey I also quickly tried Moments but the switch back worked as expected.

Translation in German is not available in the Switch menu for the new Moments option.
Great that double tap to wake is here.

23.01.2026: In the battery settings there is a (not in German translated) new option to chooose charging speed. But seems not to work.

1 Like
40

  • Vendor Xiaomi

  • Device Redmit Note 9s

  • Miatoll

  • Version of /e/OS or Stock which existed previously a15-3.3-community

  • device not rooted

As with 3.3, it is only possible to update via the system updater if previously the latest recovery image is manually flashed via fastboot. This manual intervention was not necessary up until 3.2 and it is not entirely clear to me what caused the change in behaviour.

Otherwise, thank you for your continued great work and efforts!

41

Hi,

In the relaease note, it doesnā€™t state, sadly, that this bug has been resolved. Iā€™m experiencing the same annoying issue, despite some seems not being affected by it :man_shrugging:

1 Like
42

Thanks for checking! Even with a custom Launcher? (Home screen)

Also, how do you enable double tap to wake?