[feature request] restart of fingerprint interface needed in settings utilities

asked 2019-09-30 10:25:13 +0200

cemoi71 gravatar image

Hi Sailors,

for many days i was able to spare my fingerprint interface on my XA2+.
But i didn't knew how, and the only possibility to retrieve it was to restart sfos.
Since today i'm able to spare it every time if i use the dedicated test in csd-tool.
The problem is with sfos it still impossible to retrieve it without to restart the phone.

Would it be possible that the jolla dev team may kindly develop a procedure to restart the interface by the settings utilities?
That would be really cool. please

Many thanks in advance for any effort for this, at last to consider this wish.

Have a nice sails. Cheers

edit retag flag offensive close delete


What else should we pack into sailfish utilities?

sensorfwd bluetooth/bluebinder nfcd usbmoded udisks2 ...

There are lot of services and I guess we got the most reasonable covered already in the sailfish utilities, even all those can be handled via CLI.

So I do not see the necessity for it. https://together.jolla.com/question/214407/bug-csd-tool-lock-the-fingerprint/?answer=214443#post-id-214443

peterleinchen ( 2019-09-30 22:14:42 +0200 )edit

I'm not a fan to restart a device if an interface broke up, crash or freeze. that should be always a possibility to restart it. for the question what else or how, that is a design question which need reflection.
Here it is feedback on an interface which is relative new implemented and has no was to be redirected in a good way.
To resume the situation that is bad enough.
that is a part of a concept which need to be done from begin to the end. but where is the end?
The bluetooth has already its own escape with wifi. The nfc one i don't know, but should be logically with all the network interfaces, like the usb one (i think).

cemoi71 ( 2019-09-30 22:26:09 +0200 )edit

seems that BL would not be restarted with utility to restart network... obviously it concerned only the wlan and network over sim-card... :-(

cemoi71 ( 2019-09-30 22:49:39 +0200 )edit

But that is the fun this device/OS makes. Find bugs/quirks, search for fixes, apply them and forget about it ...

You just found out on your own: bluetooth will need another switch. And there are lots of other services and I would NOT like a utility with tens/hundred service kill/restart switches, only for the rare circumstance of misbehaving.

I do remember pulseaudio going crazy on my N900 from time to time (strange loud sound out of the blue): open keyboard, ctrl-shift-x, 'sudo gainrrot; killall pulseaudio'
Way faster than opening some setting app, find the right entry under tens of switches and so on.

But that is just my personal view...

peterleinchen ( 2019-09-30 23:11:26 +0200 )edit

understand your point of view, and your own situation. but i think for other people like me, who have no idea of those cli commands, and is too much for some singular days. even if it happens rarely.
For a dev point of view or a tester one, it is more precious if other else may restart some service specifically, even if they have no idea of it. user feedback has it weight of gold

cemoi71 ( 2019-09-30 23:30:34 +0200 )edit