Feedback for v3.3

/e/OS Smartphone Operating System Build Feedback
252 
* Samsung
* Galaxy S7
* herolte
* e/OS 3.2 - s 
* the device is Not rooted

all working well so far

2 Likes
253

Just wanted to send a big thank you to you guys for putting out that update.. Everything fixed and working now, really appreciate the effort and timing, hope you all got away for xmas..

254

Others have mentioned disabling the installed ntfy but for me they coexist without problem. Maybe significant, no work at all is assigned to default ntfy (but better discussed on the thread perhaps).

255
  • Fairphone3
  • fp3
  • 3.3-t-20251210556411-official-FP3

In video from Crunchyroll I have no image and no sound but I have subtitles. It was ok in 3.1, not since 3.2

1 Like
256

Do, like written in the description on top, the best way to get it fixed.

1 Like
257

Happy to report on 3.3 official on FP5: Android Auto now works again.

To be fair on the second attempt days apart, but i suspect a faulty usb-c kabel over an software issue.

2 Likes
258

  • Vendor Name: Fairphone

  • Device name: Fairphone 6

  • Device FP6

  • Version of /e/OS or Stock which existed previously: 3.2 (A15 official edition)

  • Is the device Rooted / Not rooted: I don’t think is rooted, but not sure. I’ve replaced Android with E/OS and locked the bootloader.

  • 1 eSIM (Portuguese), 1 physical SIM (Polish);

Everything is working fine. The download was a bit slow, but the installation went smoothly.

For now everything is working as it should (I only updated two hours ago).

Scheduled dark theme is still not working. I wonder if this will be corrected in the future?

But great work nonetheless!

259
  1. Vendor Name: Fairphone
  2. Device name: Fairphone 6
  3. Device FP6
  4. Version of /e/OS or Stock which existed previously: 3.3-a15-20251210556408
  5. Is the device Rooted / Not rooted: I don’t think is rooted, but not sure.

Download works fine

Update works without problems.

After the update, a microG error message appears again and again at unequal intervals.

I would appreciate a quick resolution to the problem.

The error message is very annoying!

THX and greetings

260
  1. Vendor Name: Google
  2. Device name: Pixel 7
  3. Device codename: Panther
  4. e-3.2-official

Download took quite a while and had to resume it a couple of times, but the update went smooth. Everything seems to work fine. Thanks for the update.

261

I would like to ask for the exact error message as soon as possible.

262

You work with both Sims? Is mobile internet working on both Sims?

264

No, only one physical sim card. Mobile internet works for that one. I think a second sim can only be e-sim right? so I can’t test it I guess.

265

I’ve seen a couple of screenshots from different languages. I think in my English installation it says something like “MicroG keeps stopping”, and then two options: App information, and Close app.

I will post a screenshot when it happens to me again.

Update: This post has a screenshot of the exact same error message: Fairphone 2 (v2.0-r) Error "microG Services keep stopping"

1 Like
266

Maybe same problem as this one

Edit: It is the same user and there is a picture

@TillHH Usually cache doesn’t help much. Storage is better but that will delete aslo all the settings made within microg and I suppose therefore lose all registrations for notifications and other things related to microg

267

No, my problem with the messages is completely different; I manually disabled them so I could no longer receive messages. The problem with the error message “microG has crashed” is a completely separate issue.

268

See MicroG frequently stopping FP5, /e/os 3.3 official (#9099) ¡ Issues ¡ e / Backlog ¡ GitLab

2 Likes
269

Liitle Update to the MicroG Problem in FP6, 3.3.

I’ve noticed that when I receive a message, for example from Xing or Whatsapp, the error message appears.

I hope that helps a little to solve the problem.

270

It will maybe if you write it on the gitlab issue, just here on the forum it is a community post with not knowning how and even if it will be relayed to the developers.

2 Likes
271

AppLounge/updates/new app install NOT working yet!!!

  • Vendor Name: Fairphone

  • Device name: 5

  • Device CodeName: FP5

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

  • The device came straight from Murena with /e/OS in June 2025.

Version download got interrupted/restarted several times.

AppLounge still not working after update to 3.3!!!

Lots of apps waiting for updates. Some stopped working (Dutch government) as update is required!

272

  • Vendor Name: OnePlus

  • Device: Nord

  • Device CodeName: avicii

  • Previous OS: /e/OS: 3.2-s-official (A12)

  • Not rooted

Download of the update was a bit lengthy and stopped several times (as reported by other users), but with infinite Caffeine, connecting the phone to a charger and continue the interrupted download as soon as I noticed that, it finally succeeded. Installation went fine and after restarting the OS it seems that every is ok so far. Thanks to the team!

The only thing I’m a bit confused is that I can’t find the possibility to enable/disable the Unified Push service in the settings. Instead there was a request to allow mircoG to send push messages. In the microG settings I did not find any Unified Push settings.