This issue happened to me yesterday, when switching between default user and guest (Access disk of device not starting properly). I did have patchmanager installed, so I haven’t been able to rule that cause out.
What I did find was that when I tried to start Jolla-settings from icon it failed to start. But when starting from terminal it successfully launched, though with warnings that “manager” couldn’t be created (can’t remember the exact wording) and that the database was locked. Will try to recreate the behavior when I have more time.
I never manually start or stop Android service. It may have been OOM killed, before I tried to switch to guest user, or implicitly started by me launching an Andoid app.
Unfortunately I can’t recall the exact details, as I was focusing on the user switching rather than Android support
Same experience for me this morning. I need to reflah the smartphone !
I loose few datas but i loose some
And reflash is very easy, it’s after : you need one day to restore the smartphone as before the bug.
Jolla has the chance that i’m an afficionado
Same.
Happened again today, all data lost (secondary user is my main user) , after failing to start android in defaultuser.
No way to use recovery since the new (and appreciated) alphanumeric user as recovery is not accepting the password.
It happend to me today. When I checked my phone (XA2 plus, 4.4.0.72) guest user was activated. I don’t know how it happend. So I switched back to device owner/admin and all data was lost, \nemo was almost empty and only an android data folder (don’t remember the excact name) was there.
Is there any chance to restore the data? My last backup is some weeks old. I think the whisperfish database (used mybackup) changed in the meantime and the backup would not be functional for it.
Hi, very sorry. This prob is a big annoyance.
Nemo? I guess coming from an old SF version.
Anyway. I don’t remember if data subsists. Seems once I switched off immediately and could find some data through recovery mode. Not sure though. Maybe worth it exploring the filesystem from there.
Strange that it happened all of a sudden. Scarry!
Generally happens after fiddling Android start/stop button and changing user.
About WF, sorry, I don’t know. Maybe ask on the WF thread.
Good luck.