Unable to set lock pin for Android apps requiring it

Bug Reports
85

Absolute legend. With this (and removing my Danske ID blacklist from Aurora), I’m able to actually use Danske ID on Sailfish now! Dobby is freeeee.

4 Likes
86

With the latest Sailfish update and the included update for AAS, the Smartbroker+ app finally works for the first time ever, thank you very much for your detailed instructions for your workaround.

I unfortunately noticed that the set AAS screen lock PIN isn’t “restart-resistent” (at least on my end), once AAS gets shut down and restarted, it forgets or resets my set PIN (while the PIN screen lock remains active) and subsequently returns the error “wrong PIN” when I type in my PIN code, despite the number being correct. To fix this, I have to type in the entire command chain in the Terminal from scratch, which is rather inconvenient on such a regular basis. Do you know of this problem yourself, and/or how one could fix it (making the PIN restart-resistent/persistent)?

87

So i am a noob for building the package evtl. You can pack a 32bit version ?
please be so kind :slight_smile:

88

EDIT: had the wrong path before

You can fix this by creating the file /opt/appsupport/vendor/etc/init/android.hardware.gatekeeper@1.0-service.software.rc with the following contents:

service gatekeeper-1-0 /bin/hw/android.hardware.gatekeeper@1.0-service.software
    class early_hal
    user system
    group system
4 Likes
89

Can do, but what version of Android is your AAS running (under Settings → Android AppSupport)? It seems to only work under Android 13.

90

It is Android Version 13

91

I built a 32-bit RPM here.

92

Great thank you so much

93

Thank you, but how do I that exactly? I’m not very Terminal-literate..

94

Any chance to put this on OpenRepos?

1 Like
95

Do you have SSH access to the phone?

96

Here: AppSupport lockscreen support | OpenRepos.net — Community Repository System

3 Likes
97

Yes, I have set it up before.

98

The package is noarch but has a 64-bit dependency. 32-bit Android support is privileged, not unprivileged.

I installed with zypper, option 2: ignore dependencies.

99

Then the easiest way should be to save the file somewhere on your computer and use scp to copy it over:

scp file.txt root@your_phones_ip_address:/opt/appsupport/vendor/etc/init/android.hardware.gatekeeper@1.0-service.software.rc
1 Like
100

Oops, thanks for the report, that should be fixed now with the latest update.

2 Likes
101

I’ve copied the described file into the described folder (“data” didn’t exist before, so I created it), went through the lock PIN setup process (as described by nekron) in the Terminal once more and tested it by restarting AppSupport, unfortunately the issue still persists. What could be the culprit for the fix not working?

102

Oh sorry, I had a typo, the path should be:

/opt/appsupport/vendor/etc/init/android.hardware.gatekeeper@1.0-service.software.rc
1 Like
103

Perfect, now it works. Thank you very much!