Feedback for v2.5

I can also confirm this problem on Samsung S7 (herolte).

  • Vendor Name: Google
  • Device Name: Pixel 6 Pro
  • Code Name: Raven
  • Version of /e/OS which existed previously:
  • Device is not rooted

Working awesome as usual.
Thanks team for your great work.

Vendor Name: Oneplus
Device Name: Nord N200
Code Name: dre
Previous Version: 2.4.1

BlissLauncher versión 3.0.1-beta memory usage increasing.
Taking 1gb up to 1.9gb
Memory usage spikes up within a few minutes after terminating Blisslauncher app or rebooting, and even when the phone is idle.

Something is definitely not right.

Looking forward for upcoming Android U release.

Try to delete cache and if you want you can also delete storage but it will delete all changes you made. For example the order of apps.

I, too, have a S7. If i were to rely on where the map locates me, i would say i don’t have this problem.

Did so @mihi and it was taking about 100mb then.

This how it stands after 9hours

I think it is waaay to much memory for a1,3mb launcher app.

Hmm, I don’t use Bliss Launcher. I would suggest you to try narrow it down why. Didn’t see along time such issues on the forum.

I know you can’t create gitlab issue. Should I take care of that?:thinking:

Can you set mock location through the third party app and then try it?

GPS is working fine, fake (mock) location isn’t so apps can track your real location.

@gab wrote how you can test it:

Hello @mihi

In efforts to somehow improve battery lifetime, the other day I enabled Dev Option Don’t keep activities under Apps.

If turned off, BlissLauncher is happy!

If on, it starts going crazy in very little time until it takes whatever memory is free

I would appreciate your help creating the gitlab issue for me. Danke schƶn.

Also remember than android is based on linux :penguin:, and that linux has a very different approach to RAM than windows.

It’s quite normal for linux systems to use as much RAM as needed, as only free RAM is truly wasted. The system will reallocate RAM to more demanding apps on the fly, as needed. All RAM cleaners and ressources optimizers are mostly unneeded on gnu/linux systems, and that also applies to android

You should worry about memory usage only if you notice performance issues.

Sources :bookmark: :

1 Like

Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: 2.4.1-t
Device not rooted

Since 2.5 the Google Maps app no longer displays (loads?) any maps. GPS is working fine. Search is working but images for locations (e.g. cafƩs) are not loading either.

edit: downgrading the Maps app solved the issue

In addition, i noted that ā€˜Files’ APP changes the sort option always back to ā€˜File Name (A-Z)’ :unamused:

  • Vendor Name: Fairphone
  • Device name: Fairphone 3
  • Device CodeName: FP3
  • Version of /e/OS or Stock which existed previously 2.4.1-t
  • Is the device Rooted

This was the second time that an OTA-update for this phone killed the running system even before rebooting.
The first time the phone was unrooted after the installation was complete (I repeat: before rebooting! The old version was still running), but all apps without root permission still worked.
This time the system was unusable. Except Tasker no other app could be opened, even the launcher and the system settings crashed.
Perhaps it helps others with a rooted FP3: I found this How-To Step-by-step guide on how I install Magisk using adb Ā· GitHub that describes how to install Magisk via adb before rebooting.

OTA-updates must not touch the current slot!

I’m not using a third party app to set a fake location, i’m directly using advance privacy for that and magic earth still believes i’m in budapest. However i haven’t tried using gpstest…

Hmm, it looks like the reason why DNG capture does not work is that support for RAW has been dropped (upstream?). The only options for imageformat is JPEG, WebP and PNG. If this is the case it would be nice if the menus were updated to reflect the change.

@Manoj Do you know anything about this?

Sharing this with the team to check and update.

Fairphone / FP5 / FP5 / 2.5-t-20241108446629-official-FP5 / Not rooted


  • Camera app crashes when selecting Photo parameters
  • Gallery crashes when saving from picture editing
  • Fennec from FDroid crash when launched, solved by reinstalling the app.

Under Camera Settings >> Photo Settings >> RAW should show up below Image format.

This one is a known issue:

Unfortunately, there’s currently no running activity.

However, this is obviously unrelated to /e/OS version 2.5

If someone has time to take over from me to create the issue please do, I can’t find the time for it in the coming days…