A government authenticator app written for Android installs fine but does not start up because it assumes a precondition of the device being protected by a PIN code or pattern or fingerprint is not met. Any clever ideas to make the app understand the equivalent SFOS protections are nevertheless in place?
1 Like
Some further, likely trivial, info to add to my question: within the Security section of the common Android settings (launch devel-su -p apkd-launcher com.android.settings from Terminal and insert developer SSH password) the Screen Lock is indeed set to ‘None’. And it’s impossible to add a Screen Lock from within the common Android settings, as an error message (something like -translation from Dutch- ‘Screen Lock has already been modified’) appears. This neither works when disabling/removing the SFOS screen lock protections.
OK. This is a long known issue and a bug report has been created for it: Unable to set lock pin for Android apps requiring it. There has been no recent developer intervention in that thread, so I’m afraid there will not be any solution soon. That’s a real pity.
2 Likes
This is needed for many apps I need to use.
1 Like
@dad_and_alive @MRQ Can you guys tell me which specific Android apps you have mind, so I can add them to my list of affected apps?
…just read this thread. If you want to add another app if not already done:
UntisMobile
(one has to enter credentials every time when changing to another app or when screen turns black or restarting Untis.
Thx.
1 Like
I did, but nobody has named their apps in question so far.
Well, that is indeed annoying, but not the problem being mentioned above, the issue with the missing ability to set an Android lock PIN is that a host of apps are denying their usage altogether, until said PIN was set, not that logged-in sessions get discarded when one re-opens a minimized app (such as UntisMobile).
I also wanted to mention untis. There was a workaround to switch to an earlier version of appsupport, i think through flashing also an early sfos version, where it was still possible to set a pin in appsupport and then update. That way the pin stays set. I also read this is not only a problem of sfos, but of the underlying aosp or maybe even lineage? One can of course only do that up to an xperia 10 iii. Because c2, 10 iv and 10 v don’t have these old appsupport versions.
I have problems with two banking apps of three in Estonia: Swedbank and LHV.
With first one (my mistake) is problem, that it ask me to enable notifications (it is done under setting) and with second one it does not recognize screen lock (which is needed to login without identifying myself everytime).
Citation needed.
have you tried a native authenticator app like “foil auth” as an alternative?