Microg hell after 3.3 upgrade

/e/OS Smartphone Operating System
, ,
1

upgraded my fp6 from 3.2 (the version I recently got it with) to 3.3 when prompted, and I’ve been stuck in microg hell ever since. lots of people have had the same issue, with it constantly crashing on 3.3, but most folks have reported that “enabling device registration” fixes it. welp, not for me. it was already enabled, still crashing. I toggled it on and off, still crashing. fully cleared all storage for microg and reconfigured, still crashes. tried to switch back to boot slot A which presumably still had v3.2 installed, just got a boot loop.

it’s brutal, because of course any app I’ve got that wants to do messaging notifications uses the google services for push, and so I don’t get notified for anything now.

does anyone know what the root cause is here, how to actually fix it? or a way to downgrade the OS back to v3.2 which worked fine? this bug is killing me, and in a few days I’m going to have to go back to work and do on-call, which isn’t working because no push notifications… :pensive_face:

2

Maybe give information about your build you have. But I presume you have an ‘official’ build since a bootloop happens for slot switch.

3

Perhaps review

It is currently marked fp5

If it is your issue please consider adding your FP6 experience Report an issue.

If slot change won’t work you would have to consider fresh install which will include Format data as almost certainly a downgrade will be refused (or worse if bootloader is locked, is it?)

2 Likes
4

and yeah it’s an official release upgrade, I’m currently on 3.3-a15-20251210556408-official-FP6.

I can’t do a fresh install on the phone, I’ve fully migrated from my old phone, and all my 2FA, work on call, and other stuff is on here. I need it to just work, since it’s a brand new phone, and it’s pretty distressing that /e/OS has had such a major bug right out the gate for me.

honestly don’t get the point of the multi-slot approach when you can’t actually switch back to the previous slot if there’s problems. that used to work on an older phones I’ve had, so this smacks of google making android even more hostile to users in an attempt to court corpo interests. real unfortunate for me, anyway, since 3.2 was working fine.

I just tried to go register for the /e/OS gitlab, and it rejected my e-mail, saying “Please use your regular email address”, which is a pretty wild take for my personal e-mail domain which I’ve owned since 2007, and is hosted on Google and includes all the latest e-mail security features. feels very weird since the same address worked fine for signing up for this forum, and means I can’t really actually file this bug report.

if someone wants to update that ticket with info that it’s busted on the fp6 as well, and that it worked perfectly with the same settings on v3.2, and that I do have a google account registered for use with microg, that’d be much appreciated. :pensive_face:

5

There is a section why you get the error.

Why do you need a google account? I have FP6 community build and I don’t use a google account, no issues like reported.

Were you able to switch with an open bootloader? Was that on stock android? Please elaborate

1 Like
6

Really some “known or traceable” ID is required but Gitlab Enterprise tends to throw an unhelpful message. Fresh advice was given last week.

In case any other user can help with slot change advice please can you tell us if the Bootloader is locked.

If you wanted to experiment with recovering the situation would you consider removal of your Google account if only to establish if this is a part cause of your issue? No guarantee this would help, ofc.

Capture a debug information from /e/OS might ofc help.

Seedvault is available from Settings > System > Backup. You might find this helpful if you decided to go for Factory reset. It is not a fully comprehensive backup so please take notes as you proceed so that you are fully aware of what is not backed up.

7

Maybe zyvod needs the Google account for some work apps.

Still, two questions to or suggestions for @zyvod :

  1. You do not need a Google account just for push messaging - this may seems surprising, but I think that even the official Google Play Services offer push functionality without a Google login.
  2. Hence as suggested by @aibd, can you try to (maybe temporarily and as a workaround) remove the Google account? I am however aware that you may currently have to restore your phone first. :frowning: Maybe some more experienced user can tell how to do this without losing your data.

I have added a link to this thread in the /e/OS GitLab. :crossed_fingers: Feel free to comment here if I should change something.

2 Likes
8

hi folks, appreciate all the responses. I’ll address one at a time:
This e-mail address policy is unfortunate, but I’ll see if I can find something gitlab will accept.

I need my google account active for work apps, so yeah. it’s not optional for me. I’m on a FP6 I bought about a month ago, imported from the UK to Canada, unlocked the bootloader and installed /e/OS after receiving it using the official ROM. install was much easier than the last time I did a custom ROM, nice work done by FP and the EOS folks on that. would’ve loved to buy directly from Murena, but they don’t sell the Fairphone to Canada yet, just other models I wasn’t interested in.

I will try removing it and see if the situation improves…

ok so here’s some interesting results. the “trust google for app permissions” toggle was unchecked. checked that, and it stopped crashing. definitely wondering if the person on the FP5 bug can check that specific setting and see if they’ve got it enabled or disabled, might be the combination of the two (having a google account setup, but not having “trust google for app permissions” enabled) causing the crash.

I thought push notifications were still broken, but I did a test of my work apps, and they work. I’d just initially tried with Discord, and it didn’t work, but then again I remember discord’s notifications on mobile have always been pretty garbage.

I also did the debug log thing, filtered on unique lines containing “microg”, but there was nothing interesting in there after I re-enabled that “trust google” setting, so that may have been the fix for me.

I’ll update this thread if I have further problems, but this seems like it might have done the trick! thanks so much for everyone’s help and suggestions, really appreciate it. was really stressing about this bug, but my test notifications with my most important apps are working again, so I’m hoping it’s solved now.

3 Likes
9

Excellent, I have added a corresponding comment in the GitLab thread.

EDIT: And thank you for trying and the solution found!

3 Likes
10

thanks, appreciate it!

1 Like
11

Not everyone has that error, even such without google account but maybe it is such a individual setting which some might have and others don’t :thinking::thinking:

12

Removing the Google Account set in microG resolved the error.

1 Like
13

I have also this problem on FP6 with official /e/ OS. Could this bug be fixed in some way? Removing the Google account is no solution of course. That is hiding the problem.

Please… This is a serious issue with an official release of the OS.

14

did you try the fix above that worked for me, where I needed to enable the “trust google for app permissions” toggle in the microg settings? it’d be helpful for the devs working on that to know if this solves the issue for you or not.

2 Likes
15

Thank you @zyvod. This indeed solves the problem.

Next I had also to install Outlook again to have this fixed.

1 Like