Same for me since Android11 update 2 days ago. The same while rebooting in secure mode. Sent a request to the support, now waiting…
Stupid to know that all data and apps are there, ready to be used, and I have only 20 seconds to attempt extracting something before the smartphone reboots… Arrrh
Same issue since updating an FP3 to 11/8901.4.A.0017.3/gms-15368f27
The factory reset is also triggered when switching to a newly created user or a guest user account and even in Safe Mode.
Same problem here 
Same problem here. Interestingly, I had not installed the October update when the problem arose. I had only received the push-notification.
Too bad I decided to remove the whole secondary user account before checking if this was a recurring issue.
Same here with my FP3 running OS v11 (8901.4A.0016.6) and switching between users smoothly before this morning.
Here are some recurrent errors from the log right before the restart:
10-25 20:44:19.727 10071 12633 E AssistantConnector: Couldn't read whether gRPC is supported from public value
10-25 20:44:19.727 10071 12633 E AssistantConnector: java.lang.IllegalStateException: Failed to query AGSA value. This is most likely caused by a Google signature check failure. Please make sure both of the AGSA app and the client app are either release or dev builds.
10-25 20:44:19.727 10071 12633 E AssistantConnector: at bfcy.call(PG:17)
10-25 20:44:19.727 10071 12633 E AssistantConnector: at bvuk.call(PG:2)
10-25 20:44:19.727 10071 12633 E AssistantConnector: at cavo.a(PG:1)
10-25 20:44:19.727 10071 12633 E AssistantConnector: at caul.run(PG:4)
10-25 20:44:19.727 10071 12633 E AssistantConnector: at cavp.run(PG:1)
10-25 20:44:19.727 10071 12633 E AssistantConnector: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-25 20:44:19.727 10071 12633 E AssistantConnector: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-25 20:44:19.727 10071 12633 E AssistantConnector: at java.lang.Thread.run(Thread.java:923)
...
10-25 20:44:19.888 12583 12653 E AndroidRuntime: FATAL EXCEPTION: android.fg
10-25 20:44:19.888 12583 12653 E AndroidRuntime: Process: com.qualcomm.location, PID: 12583
10-25 20:44:19.888 12583 12653 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.android.location.service.v3.NetworkLocationProvider pkg=com.google.android.gms cmp=com.google.android.gms/com.google.android.location.network.NetworkLocationService }
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1838)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at android.app.ContextImpl.bindServiceAsUser(ContextImpl.java:1783)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at android.content.ContextWrapper.bindServiceAsUser(ContextWrapper.java:782)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at com.android.server.ServiceWatcher.rebind(ServiceWatcher.java:339)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at com.android.server.ServiceWatcher.onBestServiceChanged(ServiceWatcher.java:310)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at com.android.server.ServiceWatcher.lambda$register$0$ServiceWatcher(ServiceWatcher.java:282)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at com.android.server.-$$Lambda$ServiceWatcher$K66HPJls7ga1t3t859fKACfAgZc.run(Unknown Source:2)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
10-25 20:44:19.888 12583 12653 E AndroidRuntime: at com.android.server.ServiceThread.run(ServiceThread.java:44)
Trying the last update from the 5th of October (4.A.0017.3)…
Same problem with ‘latest greatest’ version available.
And same recurrent error in the logs:
10-25 21:21:02.838 18923 18969 E AndroidRuntime: FATAL EXCEPTION: android.fg
10-25 21:21:02.838 18923 18969 E AndroidRuntime: Process: com.qualcomm.location, PID: 18923
10-25 21:21:02.838 18923 18969 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.android.location.service.v3.NetworkLocationProvider pkg=com.google.android.gms cmp=com.google.android.gms/com.google.android.location.network.NetworkLocationService }
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1838)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at android.app.ContextImpl.bindServiceAsUser(ContextImpl.java:1783)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at android.content.ContextWrapper.bindServiceAsUser(ContextWrapper.java:782)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at com.android.server.ServiceWatcher.rebind(ServiceWatcher.java:339)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at com.android.server.ServiceWatcher.onBestServiceChanged(ServiceWatcher.java:310)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at com.android.server.ServiceWatcher.lambda$register$0$ServiceWatcher(ServiceWatcher.java:282)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at com.android.server.-$$Lambda$ServiceWatcher$K66HPJls7ga1t3t859fKACfAgZc.run(Unknown Source:2)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: at com.android.server.ServiceThread.run(ServiceThread.java:44)
From what I can read online, such an unauthorized access could trigger a soft reboot as this one!
My best guess is some permissions are missing for the non-admin users, possibly related to location services…
The weirdest part is that I did upgrade from Android 10 to 11 a week ago (Wed 26th of Oct).
And everything was working well. I’ve switched between users a dozen times…
Then this morning around 10AM, I’ve found the phone waiting on the ‘hard reset’ boot prompt.
I was not even using it while it happened…
Very strange bug that takes a week to arise!
Anyway, I’ve also opened a support request as I was not sure I could see/join the one mentioned here above.
Hi
You cannot ‘join’ a support request as it’s not a list. Making one as an individual is the proper way to inform Fairphone.
As a beta tester I have already posted it on the issue list and reffered to this topic and your post showing the log.
Thanks
Exactly the same problem on my side.
I thought it was linked with my upgrade to system version 8901.4.A.0017.3 (I was previously under Android 10 and upgraded directly to this version). But it seems to be linked with something else as I understand.
Thanks in advance for any news on that.
Dear Forum
Since two days I cannot use the second user account on my fairphone 3+ anymore. Around 15 seconds after switching the phone wants to reset to factory settings and restarts.
I tried deleting the user (which worked) and then recreating it. After entering the account-name it takes again around 15 seconds before switching to reseting to factory settings. The same happens with a guest user.
Luckily there seems to be a problem with the reset process and I can choose to try again to restart the phone. Therefore I didn’t lose the data from the main account.
Disabling a secondary user, restarting the phone (as well as taking out the battery inbetween) all didn’t help.
Any ideas?
Please see above it a known issue so I moved your post here.
Experienced the same behaviour as described in so many posts here. Having updated to 8901.4.A.0016.6, previously working alternative users (mainly to use Teams with different identities) crash the system causing it to reboot into recovery mode:
10-31 10:59:38.452 19982 19982 I uncrypt : received command: [--prompt_and_wipe_data
10-31 10:59:38.452 19982 19982 I uncrypt : --reason=RescueParty
10-31 10:59:38.452 19982 19982 I uncrypt : --locale=nl_NL
10-31 10:59:38.452 19982 19982 I uncrypt : ] (59)
10-31 10:59:38.466 1542 19971 I RecoverySystemService: uncrypt setup bcb successfully finished.
10-31 10:59:38.466 19982 19982 I uncrypt : received 0, exiting now
10-31 10:59:38.470 1542 1676 D ShutdownThread: Notifying thread to start shutdown longPressBehavior=1
10-31 10:59:38.472 20097 20116 D TelephonyRegistryManager: onSubscriptionsChangedListener callback received.
10-31 10:59:38.476 1542 1676 D ShutdownThread: Attempting to use SysUI shutdown UI
Since the logs seem to indicate an issue with (a permission denial from) a location subsystem I decided to give user switching while in airplane mode a go. This in an attempt to prevent the fatal call. Although a long shot, it unfortunately produced the same behaviour, so dead end there.
On further note (and perhaps not related but occurring since the update as well): Control messages sent by connected bluetooth devices, such as headphones or a car (not Android Car), fail to do anything. No pause/play/skip et cetera possible anymore.
Thats not the most recent system version and this was causing the BT issues which were fixed with the latest update
Hi Yvonne, thanks for your reply. Indeed, already updated to that version and it fixed the BT control issue.
Multi-user problem persists though.
Kind regards!
Hi all,
Any news on this issue?
I’m having the same 
Hi if you have read the above you will see you are the news 
Same problem here. Since Friday 28th October when I log into my secondary user the function restore default features is activated automatically
Well, I was hoping that all those people who have created support tickets already a couple of weeks ago might have heard something back and could give an update. So see it as a little reminder
I recently received a confirmation that a ticket was made. That’s it.
Same for my support ticket opened on 25th of Oct.
I was then asking:
According to the forum, support request 553494 already exists.
Secondary User -> forces Factory Reset
Can I be in CC? Or is there some sort of public issue to track?
And the answer came yesterday:
As soon as we have an update we will let you know, but I am afraid there is no public tracker or thread you can be CCed to. That being said, your request is now marked so that whenever an update is available for your particular issue you will be informed.
I find it a bit sad there is no such thing as a public issue/ticket so impacted users could just subscribe and get notified accordingly.
One could expect FairePhone to use git repo and issue/ticket system opened to their community…
Anyway, we can only be patient, or give up on the inaccessible data and scratch the phone with some other OS!
Though, the bug might also be present in LinageOS and other Android derivative.
Too few information here to know the extend of this issue.