Feedback for v3.3

obacht · December 27, 2025, 4:56pm

The built-in UP- function disappeared from the device settings and seems to be rather dysfunctional (at the moment?) …

Meikel · December 27, 2025, 5:53pm

Vendor Name: Fairphone
Device Name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: 3.2-t-official-FP3
Not rooted

No issues so far. Thanks to the team!

wintil · December 27, 2025, 6:30pm

Can you confirm the build in ntfy connect or attempt to connect to the Murena push server? I see battery drainage and I suspect the build in ntfy and the MicroG crashes cause it.

mihi · December 27, 2025, 6:38pm

It did disapear but for me it works on FP6 a15-3.3 community

aibd · December 27, 2025, 6:51pm

Negative.

… but importantly

if apps have changed in this build, I feel it extra important to Clear cache in those apps.

(Otherwise those apps may be inclined to behave as in the previous build wasting resources.)

Relates ?? MicroG frequently stopping FP5, /e/os 3.3 official (#9099) · Issues · e / Backlog · GitLab.

obacht · December 27, 2025, 7:32pm

I observed delays for signal notifications and UP-example test notifications did not arrive so I moved over to ntfy-install for the time being.

Tundra · December 27, 2025, 8:18pm

Vendor Name Fairphone
Device name FP4
Device CodeName FP4
Version of /e/OS: 3.3-a14-20251210556409-official-FP4
Not rooted
Locked bootloader

I updated this morning and my main profile works fine, but I have a “work” profile of apps that I do not trust. I cannot access this profile anymore, once I input the correct 4 digit Pin, A Dark grey overlay appears and I cannot do anything other lock the screen. (The brightness will also sometimes start turning itself down)

I’ve found a way of sometimes getting past the blank screen but it seems sporadic, you have to swipe up from the bottom of the blank grey overlay - then the lock-screen will reappear and then after the pin login it loads properly.
I’ve also tried different launchers & gesture settings but the same issue remains.

wintil · December 27, 2025, 9:18pm

Cleaning up the cache did seem to improve the battery usage a bit, but I’m by far not back at the level of 3.2. I’ve seen the bug on MicroG crashing, and it should be noted in addition that Google push notifications don’t seem to work because of it.

But enabling Unified Push with ntfy running on the Mureno infrastructure without any way of disabling it, is a deadly sin: not only are radio wakeups the biggest battery drain of a phone in stand-by mode, and a push infrastructure needs to wake the radio up regularly, it also forces users to make use of an infrastructure they haven’t chosen. The lack of an option to disable it, is a bug on its own.

(NB I like unified push very much, so much that run my own push server with a distributor of my choice, I don’t need a parallel useless infrastructure beside that)

xander2m · December 27, 2025, 9:43pm

I installed on a second device today. The download server was a lot slower than the other day (maybe an hour) - perhaps one too many mince pies!

Vendor Name: Google

Device: Pixel 3a

Device Code Name: Sargo

Previous OS: I installed official OS and fresh installed

Not rooted

My phone is working as expected. Thanks devs

wintil · December 28, 2025, 1:20am

What do you mean with ‘it works in the community edition?

Does the community edition have a toggle to turn the build in distributor (ntfy) of?
Do you get the MicroG crashing messages in the community edition?
Do you receive google push messages without delay?
Do you receive unified push messages without delay?
Do you observe increased battery usage?

Your feedback can help with making the decision to migrate out of 3.3-official mess by migrating to 3.3-community or not…

kilou · December 28, 2025, 5:48am

I’m on FP6 official edition v3.3 and don’t seem to experience ntfy or microg problems. After the update, microg “complained” once that I had to register, which I accepted, and since then no message or error. Push notifications also seem to work. The only “issue” I get is that the v3.3 update broke the basic level play integrity, which passed under v3.2. However none of my apps seem to complain so far. I don’t use ntfy so cannot really comment on that. I have slightly worse battery drain under v3.3 compared to v3.2 but I experience this regularly after an update: things take 1-2 weeks to settle after an update and after that battery life gets back to normal. I had the same under v3.2 initially.

APSchmidt · December 28, 2025, 7:16am

I just noticed that this ntfy was open in the background and I didn’t open it. So you may be using it unknowingly.
I don’t need it so I shut it down; hopefully I’ll stay that way.

KaHu · December 28, 2025, 8:32am

Hello. I have been following this thread for a few days now. As a murena-newbie and not-at-all-techie I’m unsure if I should now update my FP6 (official) to v3.3 or if I should wait for the big migroG-issue getting fixed. Does it make sense to wait that out or do I put my phone to risk by doing that and not loading the latest security updates?

Thanks in advance for a piece of advice.

aibd · December 28, 2025, 8:48am

Wait till you are 100% comfortable. Only (slight imho) downside is your October Android SPL.

mihi · December 28, 2025, 9:57am

I only wrote my version I have installed and confirmed that on my device there is also no more UI accesesible. No advice to change ‘community’, just being transparent as possible (forgot to mention the device, oh snap). Anyhow, since we don’t know the actual reason (as far as I know) it could also individual settings a user has set. I also have an app which won’t work and it is a different device (rest is mostly the same).

anitaz · December 28, 2025, 11:58am

Successfully updated to 3.3 from previous version of official /e/OS on:

“herolte” Galaxy S7, not rooted, official /e/OS
“redfin” Pixel 5, official, still updating after 4 hours “finishing installation” but % are going up.

Hopefully after 10 hours it will finish on Pixel 5. I can only click “hang”, but can wait, because system is usable while “Ending Installing …”.

***Update.

After 15 hours, it finished “Ending Installing…” and allowed me to just click “update”.

Everything went smooth after that, and it installed an update and restarted the phone.

Revolut is working now fine. Before that, it complained, not allowing to login.

On Galaxy S7, Revolut is not working, as before.

Chrikle · December 28, 2025, 3:05pm

I can still not use Neftlix or the Onleihe App with the Fairphone 3. I use the stable version of EOS. Why doesn’t anyone test the updates before they are released?
This bug has been around since the last three updates…
I think certain apps should be usable and tested on a smartphone, especially streaming services, as they are used by a lot of people. Here are the error screenshots:

Didou · December 28, 2025, 4:58pm

Vendor Name : OnePlus

Device name : Nord

Device CodeName : Avicii

Version of /e/OS or Stock which existed previously : 3.2 community a14

Is the device Rooted / Not rooted : Not rooted

Had a problem while trying to connect to a WiFi through qr code, because of 3 button navigation :
Couldn’t validate because of the superposition of the right button over the validation text.

denux · December 28, 2025, 10:00pm

Samsung S9+ “star2lte” bought at Murena
SM-G965F
updated to :3.3-s-20251210556410-official-star2lte
(Android 12)
previously running : /e/OS 3.2 (S, stable)
not rooted

Works very well,
Thanks!

Maxwell175 · December 29, 2025, 3:10am

Vendor Name: Fairphone

Device: The Fairphone 6

CodeName: FP6

Previous OS: /e/OS 3.2 official

Rooted using Magisk.

Tried the update multiple times with and without Magisk. Reboots to recovery mode. Had to change back slot.

Logcat output:

12-28 21:45:35.767  4961  4961 E Zygote  : System zygote died with fatal exception
12-28 21:45:35.767  4961  4961 E Zygote  : java.lang.AbstractMethodError: abstract method "android.content.pm.ParceledListSlice com.android.internal.app.IAppOpsService.getPackagesForOpsForDevice(int[], java.lang.String)"
12-28 21:45:35.767  4961  4961 E Zygote  : 	at android.app.AppOpsManager.getPackagesForOps(AppOpsManager.java:8093)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.server.AppStateTrackerImpl.refreshForcedAppStandbyUidPackagesLocked(AppStateTrackerImpl.java:602)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.server.AppStateTrackerImpl.onSystemServicesReady(AppStateTrackerImpl.java:537)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.server.DeviceIdleController.onBootPhase(DeviceIdleController.java:2775)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:318)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.server.SystemServer.startOtherServices(SystemServer.java:3008)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.server.SystemServer.run(SystemServer.java:971)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.server.SystemServer.main(SystemServer.java:686)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at java.lang.reflect.Method.invoke(Native Method)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
12-28 21:45:35.767  4961  4961 E Zygote  : 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:889)
12-28 21:45:35.767  4961  4961 D AndroidRuntime: Shutting down VM
12-28 21:45:35.767  4961  4961 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
12-28 21:45:35.767  4961  4961 E AndroidRuntime: java.lang.AbstractMethodError: abstract method "android.content.pm.ParceledListSlice com.android.internal.app.IAppOpsService.getPackagesForOpsForDevice(int[], java.lang.String)"
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at android.app.AppOpsManager.getPackagesForOps(AppOpsManager.java:8093)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.server.AppStateTrackerImpl.refreshForcedAppStandbyUidPackagesLocked(AppStateTrackerImpl.java:602)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.server.AppStateTrackerImpl.onSystemServicesReady(AppStateTrackerImpl.java:537)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.server.DeviceIdleController.onBootPhase(DeviceIdleController.java:2775)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:318)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.server.SystemServer.startOtherServices(SystemServer.java:3008)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.server.SystemServer.run(SystemServer.java:971)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.server.SystemServer.main(SystemServer.java:686)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
12-28 21:45:35.767  4961  4961 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:889)