maemo.org - Talk - Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3) (https://talk.maemo.org/showthread.php?t=100877)

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

[QUOTE=pagis;1567892]

Quote:

Originally Posted by rinigus (Post 1567857)

Under initiative and drive of @piggz, we managed to add fingerprint support for community devices.

For Sony Tama, instructions are at https://github.com/sailfishos-sony-t...rprint-support .

I cannot add a fingerprint on XZ3,
fingerprint app status shows:

Code:

Connection: Disconnected

State:Unknown:DBus interface invalid

That suggests that the daemon is not running. What does

Code:

systemctl status sailfish-fpd-community

say? If not running, have you tried to reboot? Other commands of interest:

Code:

journalctl | grep fpd

/usr/libexec/droid-hybris/system/bin/logcat -d -b all | grep -i fpc

Those are probably longer, use https://dpaste.org/ or some other pastebin service

PS: I expect that you rebooted after install

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

I've disabled security code to unlock the device from settings and rebooted

fpd status shows loaded

logcat -d -b all | grep -i fpc

Code:

6-09 17:42:22.967 13922 13922 I FPC IMP : INIT FPC TZ APP

06-09 17:42:22.969 13922 13922 I FPC UInput: Successfully created uinput device! rc=0

06-09 17:42:22.969 13922 13922 I FPC IMP : Starting app keymaster64

06-09 17:42:22.969 13922 13922 I FPC IMP : Starting app fpctzfingerprint

06-09 17:42:22.969 13922 13922 I QSEE_WRAPPER: Starting app fpctzfingerprint

06-09 17:42:23.665 13922 13922 I QSEE_WRAPPER: TZ App loaded: fpctzfingerprint

06-09 17:42:23.668 13922 13922 I FPC IMP : Keymaster Response Code : 4294967272

06-09 17:42:23.668 13922 13922 I FPC IMP : Keymaster Response Length : 0

06-09 17:42:23.668 13922 13922 I FPC IMP : Keymaster Response Offset: 0

06-09 17:42:23.669 13922 13922 D FPC IMP : FPC_SET_KEY_DATA Result: -6

06-09 17:42:23.669 13922 13922 F AOSP FPC HAL (Binder): Could not init FPC device

06-09 17:42:23.694 13960 13960 F DEBUG   : Abort message: 'Could not init FPC device'

06-09 17:42:23.697 13960 13960 F DEBUG   :     #02 pc 0000000000004500  /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony (fpc::BiometricsFingerprint::BiometricsFingerprint()+288)

06-09 17:42:29.622 14132 14132 I FPC IMP : INIT FPC TZ APP

06-09 17:42:29.624 14132 14132 I FPC UInput: Successfully created uinput device! rc=0

06-09 17:42:29.624 14132 14132 I FPC IMP : Starting app keymaster64

06-09 17:42:29.624 14132 14132 I FPC IMP : Starting app fpctzfingerprint

06-09 17:42:29.624 14132 14132 I QSEE_WRAPPER: Starting app fpctzfingerprint

and journalctl shows:

Code:

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: QSEECOM: qseecom_load_app: App with id 29 (fpctzfingerprint) now loaded

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: PMI: smblib_set_prop_system_temp_level: Changed Thernal LV from 0 to 0

Jun 09 18:37:52 Sailfish kernel: thermal thermal_zone79: failed to read out thermal zone (-19)

Jun 09 18:37:52 Sailfish kernel: sdm845-v2-pinctrl 3400000.pinctrl: not freeing pin 126 (GPIO_126) as part of deactivating group gpio126 - it is already

 used for some other setting

Jun 09 18:37:52 Sailfish kernel: QSEECOM: qseecom_receive_req: Interrupted: exiting Listener Service = 8192

Jun 09 18:37:52 Sailfish kernel: PM: suspend exit 2020-06-09 17:37:52.247832733 UTC

Jun 09 18:37:52 Sailfish healthd: battery l=57 v=3829 t=24.0 h=2 st=3 c=163 fc=3082000 chg=

Jun 09 18:37:52 Sailfish healthd: battery l=57 v=3829 t=24.0 h=2 st=3 c=163 fc=3082000 chg=

Jun 09 18:37:52 Sailfish kernel: ptrace attach of "/vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony"[9975] was attempted by "cras

h_dump64 9870 9958 1"[9972]

Jun 09 18:37:52 Sailfish audit[9870]: ANOM_ABEND auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj=kernel pid=9870 comm="android.hardwar" exe="/vendor/bin

/hw/android.hardware.biometrics.fingerprint@2.1-service.sony" sig=6

Jun 09 18:37:52 Sailfish unknown: type=1701 audit(1591724267.233:160): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj=kernel pid=9710 comm="andro

id.hardwar" exe="/vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony" sig=6

Jun 09 18:37:52 Sailfish unknown: type=1701 audit(1591724272.267:161): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj=kernel pid=9870 comm="andro

id.hardwar" exe="/vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony" sig=6

Jun 09 18:37:52 Sailfish kernel: QSEECOM: qseecom_unload_app: App id 29 now unloaded

Jun 09 18:37:52 Sailfish lipstick[4336]: [C] unknown:0 - evdevkeyboard: Could not read from input device (No such device)

Jun 09 18:37:52 Sailfish droid-hal-init: Service 'fps_hal' (pid 9870) received signal 6

Jun 09 18:37:52 Sailfish droid-hal-init: Sending signal 9 to service 'fps_hal' (pid 9870) process group... HYBRIS: killing PID instead of process group.

Jun 09 18:37:52 Sailfish lipstick[4336]: [W] unknown:0 - evdevkeyboard: Failed to query led states

Jun 09 18:37:52 Sailfish kernel: ## mmc0: mmc_gpio_set_uim2_en: gpio=129 value=1

Jun 09 18:37:52 Sailfish kernel: sdm845-v2-pinctrl 3400000.pinctrl: not freeing pin 126 (GPIO_126) as part of deactivating group gpio126 - it is already

 used for some other setting

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

Quote:

Originally Posted by pagis (Post 1567895)

I've disabled security code to unlock the device from settings and rebooted

fpd status shows loaded

logcat -d -b all | grep -i fpc

Code:

6-09 17:42:22.967 13922 13922 I FPC IMP : INIT FPC TZ APP

06-09 17:42:22.969 13922 13922 I FPC UInput: Successfully created uinput device! rc=0

06-09 17:42:22.969 13922 13922 I FPC IMP : Starting app keymaster64

06-09 17:42:22.969 13922 13922 I FPC IMP : Starting app fpctzfingerprint

06-09 17:42:22.969 13922 13922 I QSEE_WRAPPER: Starting app fpctzfingerprint

06-09 17:42:23.665 13922 13922 I QSEE_WRAPPER: TZ App loaded: fpctzfingerprint

06-09 17:42:23.668 13922 13922 I FPC IMP : Keymaster Response Code : 4294967272

06-09 17:42:23.668 13922 13922 I FPC IMP : Keymaster Response Length : 0

06-09 17:42:23.668 13922 13922 I FPC IMP : Keymaster Response Offset: 0

06-09 17:42:23.669 13922 13922 D FPC IMP : FPC_SET_KEY_DATA Result: -6

06-09 17:42:23.669 13922 13922 F AOSP FPC HAL (Binder): Could not init FPC device

06-09 17:42:23.694 13960 13960 F DEBUG   : Abort message: 'Could not init FPC device'

06-09 17:42:23.697 13960 13960 F DEBUG   :     #02 pc 0000000000004500  /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony (fpc::BiometricsFingerprint::BiometricsFingerprint()+288)

06-09 17:42:29.622 14132 14132 I FPC IMP : INIT FPC TZ APP

06-09 17:42:29.624 14132 14132 I FPC UInput: Successfully created uinput device! rc=0

06-09 17:42:29.624 14132 14132 I FPC IMP : Starting app keymaster64

06-09 17:42:29.624 14132 14132 I FPC IMP : Starting app fpctzfingerprint

06-09 17:42:29.624 14132 14132 I QSEE_WRAPPER: Starting app fpctzfingerprint

and journalctl shows:

Looks like something is wrong in Android bits. No idea why; I will ask around

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

@pagis, just in case if I am missing something obvious - please send me logcat via email or PM. to avoid exposing some possible keys in logcat publicly (not sure if imei is there), let's keep it off the public space.

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

@rinigus I can confirm I see the same log output as @pagis. The daemon startup fails with a timeout.

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

Quote:

Originally Posted by ljo (Post 1567898)

@rinigus I can confirm I see the same log output as @pagis. The daemon startup fails with a timeout.

if you turn off "Use security code" in settings the daemon can load if you restart it, but I could not go any further.

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

The daemon on SFOS side (sailfish-fpd-community) doesn't matter as Android side fails. No Android lib => no FPD :(. So, it should be fixed on AOSP side...

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

Issue opened at https://github.com/sailfishos-sony-tama/main/issues/76. From old logs that I was sent at the beginning of the port, I could see that XZ3 had this issue already before. In contrast to XZ2 and XZ2c. Getting help from AOSP developer who has been working on FPC stack.

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

Thanks to Piggz, Ubuntu Touch developer erfanoabdi, Sony AOSP devs to provide insides, we can test whether fingerprint can be fixed by installing

http://repo.merproject.org/obs/nemo:...07.armv7hl.rpm

XZ3 owner(s), please download, install, reboot and test if it fixed the issue. Please report back

Re: Sailfish OS on Sony Xperia Tama devices (XZ2, XZ2c, XZ3)

Just got a report from one XZ3 user regarding fingerprint workaround. According to that, it did not help. As it is, I would like to ask someone to test on XZ3 whether installing "fake crypt service" RPM helps. If it does not help XZ3 users, I will have to revert FP support for XZ3 to avoid battery drain caused by current restarts of android service.