Feedback for v2.5

was the same for me

For testing with Molly-UP I used this tutorial (and therein suggested services of adminforge)
It works ok … but in the case of my S7 it does not with the integrated ntfy (which already fails the test with UP-example) but only with an extra install of ntfy (as I state in my post earlier in this thread). Yet still it´s odd on S7 as the test notifications don´t get through for molly whilst setup / in molly settings (whereas the “real” signal notifications do…).

For now, I’ve gone back to Websocket for Signal/Molly on the S7, as the (rather massive anyways) battery consumption didn’t improve with UP setup…

•	Vendor Name: Murena
•	Device name: Murena One
•	Device CodeName: “One”
•	Version of /e/OS or Stock which existed previously: v2.4.1
•	Not rooted

I have a problem with v2.5 update on my phone.
/e/OS version: 2.5-s-20241108446631-official-one
Problem description: Phone randomly restarts a 2-3 times per day

I still love the phone & it’s not a big deal for me. Hope to have it stable again.

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.