Yeah, the old fix can’t be installed, either the upgrade to the new Android version requires a new fix, or Jolla attempted to implement a devicelock on the new version and it’s incomplete
1 Like
OK - silly me ;);)
(and instructions) - do not follow blindly -VERIFY ;):) - this one - “/opt/appsupport/vendor/etc/vintf/manifest.xml and add at the bottom:“ Means - at he bottom after last ending hal, but before sepolicy ;);):) Now I can set a PIN ;);)
Someone has a working way for JP26 with Android 15 on SF OS 5.2? The wiki instructions do not work → setting a pin gives me an error message: Die Displaysperre wurde bereits geändert. Versuchen Sie es mit der neuen Displaysperre erneut“ (engl. „Screen lock was already changed. Try again with the new screen lock“)
Same goes for me too, can’t enable a government app cause of this bug. Anybody got a workaround on this?
/opt/appsupport/vendor/etc/vintf/manifest.xml and add at the bottom:“ Means - at he bottom after last ending hal, but before sepolicy ;);):) Now I can set a PIN ;);)
thanks for your update - but what steps are necessary to get a /opt/appsupport/vendor/etc/vintf/manifest.xml ?
i just installed Appsupport15-gatekeeper-pin-enabler-patch | OpenRepos.net — Community Repository System on Jolla2026 with SF OS 5.2.0.17 - set the pin in addroid setting - and it worked until a reboot of the device … like the openrepos description. the patch itself does not create a manifest.xml - it just adds 2 files: [root@JollaPhone2026 defaultuser]# rpm -ql appsupport15-gatekeeper
/opt/appsupport/vendor/etc/init/android.hardware.gatekeeper@1.0-service.software.rc
/opt/appsupport/vendor/etc/vintf/manifest/gatekeeper.xml
So setting a pin was possible - but not very durable… → before removing remove the pin with “devel-su lxc-attach -P /tmp/appsupport -n defaultuser – cmd lock_settings clear --old YOURPIN”
I would wait for the next software update that will hopefully fix this pin issue
4 Likes
Is that a certainty? That would be a great improvement for AAS, but I couldn’t find any commitment from Jolla in the forum.
Last night community meeting had conversation about this, I recommend to check the logs. Jolla explained why this is quite hard thing to achieve, but they are looking what improvements they could include in 5.3 update
5 Likes
See minutes
7. Android App Support: PIN Code and Authentication Issues
...
<Jolla> We are looking into this. Too early to comment. Let's hope that (rainemak, 16:50:58)
<Jolla> we'd have some improvements integrated for Sailfish OS 5.3 (rainemak, 16:51:00)
<Jolla> release. (rainemak, 16:51:02)
4 Likes
Has anyone had a chance to try the changes dennor suggested above?
Reading what they said in the community meeting, it seems like some of the concerns raised could already be addressed by those.
Honestly, the limitations of not having a lock screen with some Android apps are the biggest drawback for me with my Jolla Phone 2026. I’m super looking forward to having that fixed or addressed in a way that’d let those apps work, but I’ll be patient.
3 Likes
After creating the 2 files and editing manifest.xml as @dennor suggested, I was able to set a pin lock in Android.
However, apps still say that a screen locking method is not set. If I go into Android settings and try to change the screen lock, after I enter my pin, the currently selected option appears as None instead of PIN. I think this is part of the problem and the solution with the scripts isn’t working.
This is on JP2601 and SFOS 5.2.0.18.
1 Like
I’m not sur, but it looks like the PIN/password is not saved after a reboot. I had to to set a pin code Android side each time I need to access a feature requesting this “security” (it was hopefully relative rare
I tried setting a PIN again, tried removing device lock and setting it to PIN again - the app still didn’t work, so I don’t know what’s going on, but it’s obviously unsupported by SFOS so if anything works for anyone else, that’s great 
I do hope Jolla addresses this in one way or another, especially looking at the latest community meetings.
Not all apps work with this workaround 
1 Like
Which app do you try to run?
I’ll admit, patience was never one of my virtues…
I gave @dennor’s changes a try and can confirm, they do work to successfully set a pin for AAS. This has enabled 3 more apps I used to have on my old Android phone to work with JP2601. Unfortunately my bank app still doesn’t work, but that’s off topic.
Honestly, I think these scripts are at least worth considering for AAS. It shifts the needle further into relying solely on MicroG’s compatibility rather than SailfishOS’ implementation being the source of the incompatibilities.
The app in question currently is One Wallet (by Postbank) - a banking app. interestingly the other 2 apps the bank offers work without issues even without a set secure lock. This might mean that there are other checks failing and the message they’re displaying is unrelated.
They are promising that in SFOS 5.3 the pin code would work, but there is no publishing date for the update. This might take some time…..
2 Likes