SFOS 3.4 encryption jolla account

Bug Reports
#1

REPRODUCIBILITY (100%):
BUILD ID = OS VERSION (3.4):
HARDWARE (XA2):
UI LANGUAGE: German
REGRESSION: (compared to previous public release: Yes:

DESCRIPTION:

I did an succesful update to SFOS 3.4 (from 3.3). After this I did a backup and startet to encrypt my XA2 for the first time. After encryption the phone startet without any personal settings. I restored the backup. The Android Apps were still missing. So I wanted to install Aptoide from the Jolla store. For this I had to connect to my Jolla account. When I try to to this, I am getting an error message (in german: Kontofehler, Leider konnten die App-Schlüssel nicht gespeichert werden - in English: Account Error: Unfortunately, the app keys can’t be stored). What went wrong and how can I improve it?

Update: When I delete the jolla account on the phone and add it again, the error message changes to “Login not possible with this username and password”.

Also my old e-Mail-Accounts do not work any more…

Looks like there may be a problem with the encryption and accounts?

2 Likes
[release notes] Koli 4.0.1
#2

I have the same problem!!! I Purchase the license for XA2 but if I can’t enter to my account Then I can’t use the Android app!
SUPPORT PLEASE

#3

The same kind of problem…
I just installed sailfish on a new xperia xa2, but after the first startup (I tried logging later to the sailfish account, and, after reflashing, logging at the setup prompt), and then I can’t download alien-dalvuk from the store, nor predictive text input, nor do I have acces to android emulation menu in the settings. And of course, the installation of aptoide from the store fail.
I’m logged to a sailfish account where I have bought the licence, so I don’t understand why the paing features aren’t accessible, if it’s a licence bug or a store one…
I can reproduce the bug and send log info if needed.

Android Support/Alien Dalvik no longer working [3.4.0.22]
#4

Please let us know what do you get with command ssu lr (i.e., list repositories)

(You need the Terminal app for this, and you get it by enabling the developer mode at Settings > Developer tools)

#5

When I do it, that’s what I get :

[defaultuser@XperiaXA2 ~]$ devel-su ssu lr
Password:
Enabled repositories (global):
 - adaptation0    ... https://store-repository.jolla.com/releases/3.4.0.24/jolla-hw/adaptation-qualcomm-sony-nile/armv7hl/
 - adaptation1    ... https://store-repository.jolla.com/releases/3.4.0.24/jolla-hw/adaptation-qualcomm-sony-nile-dhd/armv7hl/
 - aliendalvik    ... https://store-repository.jolla.com/releases/3.4.0.24/aliendalvik/sony-nile/
 - apps           ... https://releases.jolla.com/jolla-apps/3.4.0.24/armv7hl/
 - customer-jolla ... https://releases.jolla.com/features/3.4.0.24/customers/jolla/armv7hl/
 - hotfixes       ... https://releases.jolla.com/releases/3.4.0.24/hotfixes/armv7hl/
 - jolla          ... https://releases.jolla.com/releases/3.4.0.24/jolla/armv7hl/
 - sailfish-eas   ... https://store-repository.jolla.com/features/3.4.0.24/sailfish-eas/armv7hl/
 - xt9            ... https://store-repository.jolla.com/features/3.4.0.24/xt9/armv7hl/

Enabled repositories (user):
 - openrepos-coderus ... https://sailfish.openrepos.net/coderus/personal/main
 - openrepos-osetr   ... https://sailfish.openrepos.net/osetr/personal/main
 - store             ... https://store-repository.jolla.com/h3113/armv7hl/?version=3.4.0.24

Disabled repositories (global, might be overridden by user config):

Disabled repositories (user):
 - home ... https://download.jollamobile.com/home:/honeybadger/latest_armv7hl/

I don’t know what is this home repo disabled, if it’s anormal, can it be the root of the problem ?

#6

Disabled repo not abnormal:

XA2LR
XA2LR1798Ă—680 298 KB

#7

When updating the OS from 3.3.0 to 3.4.0, your phone was signed in to your Jolla account, or else it would not have been possible to get the OS update. Why was there no account any more when you encrypted the phone?

#8

That home/honeybadger repo is a relic that we should have removed a long time ago. But it is harmless. It it not causing any trouble.

#9

Right, it was signed in.
After the update I started the encryption. I noticed, that all my android apps were missing after the encryption so I loaded the backup in the hope they will appear again (I did not control if my accounts were still working). After loading the backup I tried to sync my e-Mails and noticed. It did not work. Also Jolla store did not work. So I found out, that the passwords of my e-Mail-Accounts had to be re-entered. This did not work, only solution was to delete the E-Mail-accounts and enter the complete date new again.
The Jolla account also did not work after re-entering the password. But the Jolla account also did not work after deleting and creating it new again (only on the phone, using my existing Jolla account).
–> So, I am not sure if there was a Jolla account after encrypting the phone, but there was one not working one after I loaded the backup. Then I deleted it, in the hope it will work if I create it again. Without success…

#10

Please run the following command:

devel-su -p rm ~/.local/share/system/privileged/Keys

It seems that when restoring a backup, something bad (*) happens to that ^ directory.
After deleting it, it should be possible again to sign in to one’s Jolla account at Settings > Accounts. The directory will be re-created while signing.

(*) to be fixed, of course

1 Like
#11

I deleted the Keys directory, then the Jolla account (and also in inverse order), then re-added my Jolla account, but still I can’t access android support nor predictive text input in Jolla store. Meanwhile, checking the updates always continued to function. Does it mean the problem is even more obscure ? :frowning:

#12

The original problem reported by Tomas3000 was that signing in to Jolla account was not possible. That is being handled in this post. Your problem, not getting the licensed apps, is a different problem.

If one can sign in to Jolla account and install apps from Jolla Store but is still unable to see Android App Support in Jolla Store, then there is a problem with the Sailfish X licence. It could be that the licence was bought for another Jolla account (different username) or for a different device model. If the problem persists, please contact Jolla customer support.

https://jolla.zendesk.com/hc/en-us/articles/115003837053-What-is-Sailfish-X-licence

.

#13

Thank you, this works!