Everything is fine, thank you Murena team !
1 Like
Please add the following details
Vendor Name Gigaset
Device name GS290
Device CodeName GS290
Version of /e/OS or Stock which existed previously:
3.1.4-s-20250915526531-official-GS290
Is the device Rooted/ Not rooted
There is an issue this time. Mobile internet is not working, that is: dns is not working at all with mobile internet. The same physical sim with the same settings does work perfectly on a motorola G(9)play, version e-3.3-a14-20251214557451-community-guamp.
Also, the time before the PIN for the simcard is accepted is much much longer (at least double) when mobile internet is set to on in the setting for the phone.
The issue may have existed much longer, since I have not used mobile internet data on this phone since at least March 2025 (2.9-s)
Vendor Name: Google
Device name: Pixel 5
Device CodeName: Redfin
Previous Version of /e/OS: 3.2-t-20251022539004-official-redfin
Version of /e/OS: 3.3-t-20251210556411-official-redfin
Device: Not rooted
Bootloader: Locked
The Advanced Privacy âfrenzyâ is still here.
I have to toggle off the âTracker controlâ flag to calm it down.
In 3.2, Advanced Privacy showed up as an active app.
In 3.3, there are two active apps :
Prior to 3.2, there were no app listed.
So, why these apps show now ?
Do we have to expect new apps in next release ?
What about power consumption, memory footprint ?
By the way, the V3.3 release notes says that Advanced Privacy permanent notifications was removed, because of negative feedback.
But not for me nor for others as some screenshots show.
The âextraâ active app ntfy crops up a lot in a search of this thread, for instance Feedback for v3.3 - #365 by aibd.
From what I read, it seems that ntfy existed prior to V3.3.
But was not showing as an active appâŚ
Not sure I (will) need it, but canât be disabled.
Hopefully, the system really needs it.
Research unified push, then you know why we might need ntfy
1 Like
Well, this had been a failure.
It resulted in not being noticed about incoming missed calls earlier than two days and stuff like that. So I put it on LTE again.
Result is a constant drain of the battery to the effect that I have a lasting of about 2.3 days, which is the worst ever since v1.7, as you see in the graph:
It currently needs about 2.43 hrs/11.5% daytime of dayly charging, where the average lies at 2.0 hrs/8.3% daytime.
Vendor Name: Fairphone
Device name: Fairphone 6
Device CodeName: FP6
Version of /e/OS or Stock which existed previously: FP6.QREL.15.162.0.20251121144015_VS1V-factory.zip
Is the device Rooted / Not rooted: not rooted
Fairphone 6 running /e/OS 3.3 is experiencing random reboots. The crash log indicates a SIGSEGV (null pointer dereference) in the media.audio.qc.codec process, specifically in android::RefBase::decStrong within /vendor/lib64/libutils.so. The crash appears to be related to the media/audio subsystem. Happened several times over last days and always when watching youtube videos in Vivaldi. It seems that the software finds the audio hardware unresponsive and reboots the entire phone to prevent a total freeze.
Interestingly from v3.3 logs I can see:
Build: Fairphone/FP6/FP6:15/FP6.QREL.15.138.0/VS1J:user/release-keys
which can be interpreted that v3.3 is built on fairly outdated drivers (15.162.0 is the last version AFAIK). Any comment @Manoj ?
Will share with the build team and get back with the response.
1 Like
Hi @etacarinae the developers would like more details of the issue. Pl can you create a bug in gitlab and add logs to it. Mark it confidential in case you feel the logs may have some personal detail.
We need Unified Push, we donât need nfty + murena infrastructure being forced upon us without any way to disable it. I use my own Unified Push infrastructure & distributor app and donât use any cloud facilities from murena. Including it, great, not being able to disable it: very bad.
1 Like
Hi @Manoj looks like I canât create Gitlab account so some guidance would be appreciated (email I tried to use is my regular business email):
Pl check the suggestion given here
AppLounge issues solved now. In case of need, ⌠pls find extra info in GitLab: app lounge stops working (#9017) ¡ Issues ¡ e / Backlog ¡ GitLab
Looks like working perfectly fine now!
Missed that, thank you. The bug is now reported as #9134.
Did you manage to check the firmware version used in 3.3 as FP6.QREL.15.138.0?
Sounds like you know how they implemented it? Atleast that is the impression I get from your post. Please explain what exactly they are doing wrong?
I am not happy with all that Murena does. From their selling point they are trying to have an OS which works out of the box without the need to install anything else tolbe able to use it. The part I am not happy with it, is that sometimes things should be improved but turn out worse. Atleast they fix it at a later point
Murena FP4
3.3-a14-20251210556409-official-FP4
I have posted about my mail app not working in the past. Happy to report, after 3.3 update: cleared storage and cache, sync enabled, it works 
One thing I feel like Iâm noticing is reduced battery life on 3.3 for FP6. But Iâm not entirely sure. Anyone else with FP6 noticing this by any chance?
Thanks for adding the issue on Gitlab. Pl can you add the build type as well - official or community.
I notice it too. Battery life was much better under 3.2. Seems microG services activity is higher than before.