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.
Issue that are being worked are pushed to the beta team who give feedback, then if all seems well, i.e. no complaints from the beat team the update will be a public release.
Not all complaints are dealt with in the next update as that could take quite a while and there are security updates to consider.
Also the each beta testers doesn’t check everything. There are often updates for network compatibility so each tester is likely to use different carriers ~ one of thge criteria for selecting a tester. Not all the testers have all the NFC and Bluetooth devices so something there may be missed.
So although I understand you want a) to notify Fairphone and hear from them a) you can email them and get a support ticket b) but you won’t hear anything other than it’s being looked at and may be resolved by the next update.
It would be interesting, then, to have an estimated delay for this problem to be solved … Or at least information about its priority level.
That could noticeably change the user’s behaviour : if no hope in a reasonable time, I guess that people will reconfigure on a ‘single session’ mode rather than waiting for a solution to use multi session again.
I understand your wishes, however you have to tell FP not the forum, as we are user like you and dont have influence on this.
Unfortunately the official fairphone support did not get me any further and the support process is interesting - including fairphone endorsing this encounter group without moderation or status updates
This solution worked for me:
What a waste of resources.
Yes support is often not up to expectations but the issue is recognised so I’m a little bewildered as to why they would direct users here ??
This comment doesn’t seem very helpful to me.
It looks like I was the first to report this problem 2 weeks ago. And now we still don’t have a solution - so what? Do I think Fairphone support has been sitting idle all this time just waiting for my support request? No, I do not think so. There will be other things they have on their plate.
So I am patient … and I recommend the same to everyone who has the same problem