Update: As it turned out, deactivating background data for Play Store is not enough. I updated the instructions below to completely deactivate Google Play Store instead.
As far as I know, Google Play Services is not a regular app. That’s why switching off the regular “automatic updates” setting won’t make a difference. Google Play Services is aggressively and automatically updated by the Google Play Store whenever it’s possible, because it’s so “mission critical” to many other apps and Google doesn’t want it to get old on phones where automatic updates are disabled. It’s on the border of being morally sound I guess, but in our case it’s clearly contraproductive.
Having searched the Internet, one of the rare possible workarounds in our case is to disable Google Play Store and stop using it until the issue is fixed.
Steps:
First open Google Play Store app info (Store, not Services!):
Long press Play Store icon → little (i) sign
Now disable it with the “Deactivate” button
Do not use/open/reactivate Google Play Store until the issue is fixed by Fairphone+Google. Deny any prompts for Google Play updates by other apps, unless you know the issue has been fixed.
Note 1: Once it has been fixed, you can reactivate Google Play Store by searching it within Settings → Apps → All apps to continue to receive automatic updates again. Updates are usually a good idea. (“Ausnahmen bestätigen die Regel”)
Note 2: You probably want to let Google Play Services activated (along with its background data etc.), as afaik it handles things like push messages for some messengers and so on, things that you want to keep working. The one that actually updates (!) Google Play Services is the Google Play Store.
I got my phone working again last night thanks to @Pilo11. First I tried deactivating just background data of Play Store but it was not enough. This noon I have redone the procedure and deactivated Play Store completely and so far it’s working.
PS: One other complete alternative would be to just completely disable WiFi and mobile data - you decide what suits you better.
I have tried again to narrow down the affected version. The problem is not with version 22.44.16. The problem already exists with version 22.43.56. The last version that worked for me is 22.43.12. I have now installed exactly this version so that I at least have the latest executable GMS version. I even tried the newest Beta version 22.45.14 (150408-487603456). It also crashes.
Last working version for me: 22-43-12-150408-483592595. you can download the version at apkmirror on the website.
Thanks for the instructions. However, it worked only temporarily. After switching off the phone the same error occurs again (Groundhog day today?). I tried again and got the phone running - as long as I do not switch it off. Then even the older version of GMS seems to conflict with something. There seems to be something else that needs “fixing”.
Hopefully, FP will be able to provide a patch soon.
Goodmorning. Yesterday I got my phone back after doing the downgrade as per @Pilo11 s instructions. This morning my phone was stuck in the boot loop again. Although “automatic updates” was turned off, Google Play Services got updated to 22.44.16 overnight (crazy really). I downgraded again and disabled “Background Data” on Google Play Services and Google Play (thanks @Jonibhoni ). Hoping this holds now…
Just to let you know: version 22.43.12_150408-483592595 did not work for me (still boot looped). I went back to version 22.02.21_150408-428111784.
I’m a Mac user, never heard of OR used Android Debug Bridge (ADB) before and am attempting to now with limited success.
I’ve followed all steps provided by the legendary @Pilo11 however cannot seem to get ADB running in terminal despite attempts and am stuck here:
EDIT: After several youtube tutorials on using ADB for mac, the process worked like a charm! I’m now backing EVERYTHING up which i’ve not done in a long time. Thanks again @Pilo11 !
Same problem here, but boot loop appears after 3 seconds, which doesn’t give me the time to open settings & enable usb debugging. Any workarounds for this issue would be greatly appreciated…
I’m affected as well. Did a factory reset, keeps running into the issue again when auto-updating Google Play Services. Switched to my old Phone until this is resolved.
Hello,
Same problem here, since November 4th. I’m glad to discover now that I’m not alone !
Starting in safe mode and factory reset did not solve this issue. I’m currently trying to access the settings before phone reboots, but didn’t succeed yet. It happens only a few seconds after unlocking.
Phone : FP3
Country : France
Also adding myself to the affacted Users.
Fp3 02 (Germany). Occured somewhere between 16 and 17 on Friday. It seems that the Problem isnt Limited to FP3 but also affects FP4 Phones, a friend of mine had the same Problem last Week, but it fixed itself after he simply rebooted the Phone, he didnt have a Problem since then.