Feedback for v3.3

/e/OS Smartphone Operating System Build Feedback
210

Successfull upgrade to 3.3;

vendor : Gigaset
device : GS290
from [/e/OS 3.2-s] to [/e/OS 3.3-s] official

new application : Murena Workspace
many thanks; brieucs.

1 Like
211

Fairphone 4 / FP4
Previous: 3.2-a14-official
Now: 3.3-a14-official

Upgrade itself went smooth
Deleted Murena Workspace because I don’t use any Murena Services.
Getting message “microG Services keeps stopping”
MicroG says “Google device registration: On”, but on Cloud Messaging: “Status: Disconnected”. Apps registered with Google Cloud Messaging don’t receive any push notifications.

I’m running my own unified push server and distributor, they still work fine. In 3.2 I disabled the build in push notifications. That option is absent now and I have two ntfy processes running I don’t want nor need. When testing with UP-example the ntfy distributor, it is dysfunct, UP-example gives as error: “A2.i javax.net.sll.SSLHandshakeException: connection closed”.

So push notifications, what is an important function for me, are seriously borked.

How can I roll back to 3.2? Or is this functional in the community edition?

212

Did you install using web-installer or script in the command line ?

213

I installed with 'System Updates’ from ‘Settings’

214

  • Vendor Name: Murena

  • Device name: Fairphone 6

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

  • Not rooted

The update took very long to download but finally worked in the end.

The brightness settings are broken now, brightness is now always set on max. Neither auto brightness nor manual changes work.

Edit: Seems to be fixed after another restart.

215

Hi,

I did the update this morning (FP5 Murena) and had also the problem with updating apps.

First logged out and in again with my Gxxgle account. cleared cache and storage, logged in again, no app update possible.

Then I stopped blokada5 and see, the applounge update worked flawless…

Hope it helps

3 Likes
216

Strange behavior of app-lounge since 3.2:

Screenshot_20251224-131135_App Lounge.geaendert
Screenshot_20251224-131135_App Lounge.geaendert378×819 78 KB

Sometimes it doubles the entries.

2 Likes
217

Vendor Name: Fairphone

Device name: FP6

Device CodeName: The Fairphone (Gen.6)

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

Is the device Rooted / Not rooted: Not rooted

Bootloader: Locked

Successfully upgraded to V3.3 Official.
Update was quite long, with 5 or 6 “restarts” of the download.
Everything looks good. No issue has been found so far.
New “Murena Workspace” app asked me login again.
And the very good new (for me) is: Bluetooth incoming calls in car seems to be fixed! I just tested right now in my Ford Fiesta (2017) and sound was correctly handled on my high-speakers and microphone unit! :folded_hands: :flexed_biceps:
Now I will have to make further tests, including in my Seat Alhambra (2014), but there are high chances that it will work as well. So pretty happy with this fix! Thank you very much dear team!

It’s also time to wish a merry Christmas to all /e/OS - Murena contributors and community members! Happy to be here for the following year to come!

Cheers, Stanwood

1 Like
218

Vendor: Fairphone

Device: Fairphone 6 (Murena)

Build: 3.3-a15-20251210556408-official-FP6

Rooted: no

After updating to the latest official e/OS Version, unified push (ntfy) doesn’t seem to work any more. Tusky and Molly won’t send any notifications unless I open the respective app.

219

Yeah , we all have to practice patienetness. Better having a slow download without any problems when OS is finally installed😉

221

  • Vendor Name Pixel

  • Device name 7

  • Device CodeName panther

  • Version of /e/OS or Stock which existed previously: IMG-e-3.2-a15-20251022539003-official-panther.zip

  • Device is Not rooted

No mobile internet !

222

Finally! :downcast_face_with_sweat: …
FP5, not rooted, 3.2-a15-official → 3.3
… successful update, all works well.
Though, after 3 painfully slow downloads that all were finally aborted when starting the verification, I had to do the update manually via ‘local update’ as @msp suggested.

I honestly appreciate the pioneering work done by Murena.
And I understand that Murena is walking off the beaten track.
But for a routine(!) update this has been a frustrating and laborious experience.
It took the best part of 2 days and 5 downloads with

  • bandwidth 200-800KB/s
  • continuous interruption of the download - hence permanent attention for resuming
  • and, most frustrating, 3 times in a row after completion of download verification failed → back to the start
223

Murena FP 3

MurenaOne

Both updated from v3.2 to v3.3 official.

All went well, no problems so far.

Thank you team.

Merry Christmas and a happy New Year.

224

Looks like this:?

225

Updated FP6 officail a few fays ago.

So far only problem I noticed today was my APN settings seem to have changed, because I had my first cross border shift at work since the update and in Germany mobile internet wouldn’t work. But selected the right APN and all was good again.

226

Fairphone 5, update worked well (expect for the very slow download of course)

1 Like
227

  • Fairphone

  • 6

  • FP6

  • /e/OS 3.2

  • not rooted

so far the update has smooth, except for one major annoyance. about every 5-10m, I get the dreaded “microG keeps closing” error pop up onscreen. microG seems to be working fine, at least for my limited usage, but it absolutely will not stop crashing in the background. I tried clearing all its data to reset its state, but no luck. would love some pointers on how to get it to stop freaking out. :sweat_smile:

1 Like
228

The 3.3 update is also draining my battery. Not good.

230

Thats strange, because on FP3 devices it works with 3.3. On FP4, … not.

231

@Manoj 3.3.1 correct the camera bug for redmi not 9 (merlinx) on android 13 t

thank to all team