Xperia 10 II. And I think that the problem is not in SFOS core but in Android AppSuport
Yes. If youāre motivated you could flash sfos version 4.2.0.19 and set the android lock pin there and then update the system.
You can use an older version of Danske ID to circumvent this. This is what I do. I would also strongly suggest you 1-star rate the Danske ID with a complaint that the app requires the pin.
Open up Aurora and search for Danske ID. Once you open its store page, click the vertical ellipsis (ā®) menu and choose Manual download. Put in: 1690000023 and youāll get version 1.6.2. This version does not have the pin requirement. After this, go back to the home screen of Aurora, then click the cog settings button in top right. Choose Blacklist manager, then make sure you check Danske ID. This will ensure you never accidentally update to pin-locked version of it.
For what itās worth, my bank actually dropped the requirement for the Android lock PIN from their app once I pointed out to them that it was superfluous (they have their very own PIN). Apparently, the development team hadnāt even meant to introduce the Android PIN requirement - it came in as a side effect of a library update.
But you might want to contact the app developers directly, they might have more resources than SFOS. Worked for me.
Unfortunately, I have the same problem right now. What is particularly annoying is that they claim to require it as a protection of personal data, but in my opinion a notice would suffice (Mobile pass authentication | Interrail.eu). Have you also contacted the manufacturer and asked them to remove the requirement for a lock code? If enough users get in touch, they might change it at some point.
Same for Yale Home app, which is used to unlock door at home. To unlock door, it requires pin, face or any other extra security behaviour which is ānot setā in Sailfish. I am running C2 och 5.x.x.67
The same problem with Cl@ve, a Spanish app used by the āAgencia Tributariaā to validate the user in government procedures.
New revision [19/12/2025]:
ADAC Kreditkarte (100,000+ downloads)
ATOSS Staff Center (100,000+ downloads)
A-Trust Signatur (1 million+ downloads)
Cl@ve (10 million+ downloads)
Danske ID - Danske Bank (500,000+ downloads)
Eurail/Interrail Rail Planer (1 million+ downloads)
ID Austria (1 million+ downloads)
i-Kfz (100,000+ downloads)
Microsoft Authenticator (100 million+ downloads)
SMARTBROKER+ Aktien & ETF (100,000+ downloads)
Yale Home (100,000+ downloads)
The Austrian eID implementations:
- A-Trust Signatur (1 million+ downloads)
- ID Austria (1 million+ downloads)
I donāt believe this version of sfos can be installed on Xperia 10 iii. First version supported was 4.4
Yes, the replied-to post did specify the X10 II though.
Does Danske ID work for you guys? Iām on version 1.6.2 and entering PIN hasnāt been working on past few days.
E: Okay, I did reset for the app data and it asks to update the app. No workarounds left anymore!
After taking a pause with Sailfish OS due to issues like this, I decided to refresh my mind and even order a Jolla C2. I still had my XPeria 10 III laying around and Iām currently using it as test device to be able to know how to set up my C2 to my liking when it arrives next week or so.
Iām usually very āOKā with stuff like this breaking, as compared to other platforms, Sailfish OS is small.
What I donāt like though, is that a company that I gave 300+ ⬠for a phone and peripherals to, as well as additional money for a Sailfish X license for my existing phone, does not really react to these kinds of things for multiple years.
There are several showstoppers that prevent a broader adaption of Sailfish OS and itās usually stuff like this.
Are there any news about this issue? I canāt access the StaffCenter app to look at my work schedules on the go, as it mandates a PIN or password to be set on the Android side.
NettoHikari, I agree completely.
This must surely be something that is a 'low hanging fruit '.
This is absolutely one of the reasons why I have an iPhone as my daily driver, and my Xperia 10 iii (that I am using to write this) is āwaiting for better timesā.
Iāll only consider another Salfish device when the ābetter timesā have arrived , and such obvious showstoppers as this have been fixed
There is a new android app in Germany: i-Kfz.
It letās you load a digital version of your vehicle registration certificate to your phone. Sadly it requires you to have a device lock. There is a support email. Iāll write to them and ask whether they can just display a warning.
@hschmitt @NettoHikari Thanks for the two new app entries, added them to my table from June.
Happy new year, dear sailors!
My company recently started to use ATOSS Staff Center SaaS and I wanted (like some others here @NettoHikari @m183037) to use the mobile client for time tracking. However, the application requests a password protected device and without that it will not allow you to login. Trying to set an Android PIN didnāt work and so I started messing aroundā¦
Finally here comes a workaround
for Staff Center that might help with other apps checking for the password security constraint.
This is what needs to be done for Jolla C2 / Xperia devices with the latest appsupport runtime:
#
# Jolla C2 / Xperia AppSupport PIN Workaround
#
# 1. enable developer mode, open terminal or ssh into your device. Appsupport container must be running.
# 2. become r00t
devel-su
# 3. launch appsupport shell
appsupport-attach /system/bin/sh
# 4. launch gatekeeper HAL process (GK HAL)
/bin/hw/android.hardware.gatekeeper@1.0-service.software &
# 5. kill gatekeeperd (it will be restarted automatically and connection to GK HAL established, oh well, that's about it for process isolation with SE extension running this as root vs. system)
pkill gatekeeperd
# 6. launch Android security settings
am start -a android.settings.SECURITY_SETTINGS
# 7. now set a PIN using the security settings UI and your're done!
# NOTE: I tested this with ATOSS Staff Center and after a reboot of C2 without connecting the GK HAL I was able use the application.
# 8. older appsupport runtime for Xperia devices allows you to set the PIN
# via shell command "locksettings set-pin 1234". You can remove the lock PIN
# with "locksettings clear --old 1234".
Technically speaking the Android security settings application will talk to gatekeeperd service that will connect with the gatekeeper HAL service. The HAL service will use hardware keystore (TEE) or in case of appsupport a software-based keystore for storing your PIN credential.
The problem in current appsupport is the launch of GK HAL service thatās missing inside the image. There is sadly no init.rc service found to launch the service.
And thatās it for a five years old unfixed bug
.
Cheers,
Nek
Hopefully, with that great ingo we will have native bugfix ![]()
Thanks nekron, but I think Iām done with Jolla and Sailfish OS, unfortunately. I will focus on PostmarketOS, I guess. Not to say that I wonāt return to Sailfish OS at some point, but right now, Iām just too disappointed with the progress here.
Thanks for taking your time to write down this info for everyone, though. <3
Thanks @nekron I hope itās ok, Iāve documented this at Jolla C2 / Xperia AppS... | SailfishOS community wiki