Revision history [back]

The battery has been draining surprisingly quickly on this Xperia XA2 running Sailfish 3.2.0.12, even with the phone mostly locked and resting, battery went from fully charged to 70% in 4 hours. Finally, I logged in over ssh and ran top. A process with "fingerprint" in its name is running at full throttle. That would do it.

 3109 system    20   0   11972   2396   1788 R  98.0   0.1   1:13.67 android.hardwar 
 

$ ps lp 3109
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000  3109  2807  20   0  11972  2396 -      Rl   ?          1:21 /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony

When I was setting up the phone after flashing, I did not configure finger unlocking. Suspecting that perhaps the unconfigured thing gets itself stuck in a loop, I tried to set it up now through settings (Device lock -> Add fingerprint), but I could not get past the "Place and lift your finger" screen: it never detecting me placing the finger.

I do not know if the fingerprint sensor worked at all before I flashed the phone to Sailfish, I did not test that aspect. I do not particularly care for finger unlocking.

The parent process of this runaway process is /sbin/droid-hal-init, which starts a bunch of other things (according to all the other processes with the same PPID), so I probably would not want to disable droid-hal-init.service altogether. I will be looking for ways to get this runaway process stopped, I do not at the moment have a work-around to offer. When I kill -9 the process (from devel-su), the droid-hal-init restarts it and the thing gets into its busy loop again.

The model number of the phone is H3123. The ZIPs that I used for flashing were SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile.zip and Sailfish_OS-Jolla-3.2.0.12-h3113-0.0.7.10.zip.

Neither a reboot not a power cycle fix the problem.

The battery has been draining surprisingly quickly on this Xperia XA2 running Sailfish 3.2.0.12, even with the phone mostly locked and resting, battery went from fully charged to 70% in 4 hours. Finally, I logged in over ssh and ran top. A process with "fingerprint" in its name is running at full throttle. That would do it.

 3109 system    20   0   11972   2396   1788 R  98.0   0.1   1:13.67 android.hardwar 
  

$ ps lp 3109
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000  3109  2807  20   0  11972  2396 -      Rl   ?          1:21 /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony

When I was setting up the phone after flashing, I did not configure finger unlocking. Suspecting that perhaps the unconfigured thing gets itself stuck in a loop, I tried to set it up now through settings (Device lock -> Add fingerprint), but I could not get past the "Place and lift your finger" screen: it never detecting me placing the finger.

I do not know if the fingerprint sensor worked at all before I flashed the phone to Sailfish, I did not test that aspect. I do not particularly care for finger unlocking.

The parent process of this runaway process is /sbin/droid-hal-init, which starts a bunch of other things (according to all the other processes with the same PPID), so I probably would not want to disable droid-hal-init.service altogether. I will be looking for ways to get this runaway process stopped, I do not at the moment have a work-around to offer. When I kill -9 the process (from devel-su), the droid-hal-init restarts it and the thing gets into its busy loop again.

The model number of the phone is H3123. The ZIPs that I used for flashing were SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile.zip and Sailfish_OS-Jolla-3.2.0.12-h3113-0.0.7.10.zip.

Neither a reboot not a power cycle fix the problem.

The battery has been draining surprisingly quickly on this Xperia XA2 running Sailfish 3.2.0.12, even . Even with the phone mostly locked and resting, battery went from fully charged to 70% in 4 hours. Finally, I logged in over ssh and ran top. A process with "fingerprint" in its name is running at full throttle. That would do it.

 3109 system    20   0   11972   2396   1788 R  98.0   0.1   1:13.67 android.hardwar  

$ ps lp 3109
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000  3109  2807  20   0  11972  2396 -      Rl   ?          1:21 /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony

When I was setting up the phone after flashing, I did not configure finger unlocking. Suspecting that perhaps the unconfigured thing gets itself stuck in a loop, I tried to set it up now through settings (Device lock -> Add fingerprint), but I could not get past the "Place and lift your finger" screen: it never detecting me placing the finger.

I do not know if the fingerprint sensor worked at all before I flashed the phone to Sailfish, I did not test that aspect. I do not particularly care for finger unlocking.

The parent process of this runaway process is /sbin/droid-hal-init, which starts a bunch of other things (according to all the other processes with the same PPID), so I probably would not want to disable droid-hal-init.service altogether. I will be looking for ways to get this runaway process stopped, I do not at the moment have a work-around to offer. When I kill -9 the process (from devel-su), the droid-hal-init restarts it and the thing gets into its busy loop again.

The model number of the phone is H3123. The ZIPs that I used for flashing were SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile.zip and Sailfish_OS-Jolla-3.2.0.12-h3113-0.0.7.10.zip.

Neither a reboot not a power cycle fix the problem.

The battery has been draining surprisingly quickly on this Xperia XA2 XA2 running Sailfish 3.2.0.12. Even with the phone mostly locked and resting, battery went from fully charged to 70% in 4 hours. Finally, I logged in over ssh and ran top. A process with "fingerprint" in its name is running at full throttle. That would do it.

 3109 system    20   0   11972   2396   1788 R  98.0   0.1   1:13.67 android.hardwar  

$ ps lp 3109
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000  3109  2807  20   0  11972  2396 -      Rl   ?          1:21 /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony

When I was setting up the phone after flashing, I did not configure finger unlocking. Suspecting that perhaps the unconfigured thing gets itself stuck in a loop, I tried to set it up now through settings (Device lock -> Add fingerprint), but I could not get past the "Place and lift your finger" screen: it never detecting me placing the finger.

I do not know if the fingerprint sensor worked at all before I flashed the phone to Sailfish, I did not test that aspect. I do not particularly care for finger unlocking.aspect.

The parent process of this runaway process is /sbin/droid-hal-init. I found /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.sony.rc. According to this README.md, which starts these files understand an option called disabled, so I added that to the .rc file and rebooted. That worked. (When I just renamed it to a bunch file not to have the .rc extension, that did not help.)

It will take some time for me to assess the battery life after this, but for the benefit of other things (according to all the other processes with whoever finds themselves in the same PPID), so I probably would not want situation and does not care for the fingerprint unlock either, here is the change that I made (under devel-su) in order to disable droid-hal-init.service altogether. I will be looking for ways to get this runaway process stopped, I do not at the moment have that process:

--- /home/nemo/android.hardware.biometrics.fingerprint@2.1-service.sony.rc.ORIG
+++ /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.sony.rc
@@ -1,7 +1,8 @@
 service fps_hal /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony
     # "class hal" causes a work-around to offer.  When I kill -9 the process (from devel-su), the droid-hal-init restarts it and the thing gets into its busy loop again.
 
The model number of the phone race condition on some devices due to files created
     # in /data. As a workaround, postpone startup until later in boot once
     # /data is H3123.  The ZIPs that I used for flashing were SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile.zip and Sailfish_OS-Jolla-3.2.0.12-h3113-0.0.7.10.zip.
 
Neither a reboot not a power cycle fix the problem.mounted.
+    disabled
     class late_start
     user system
     group system input

The battery has been draining surprisingly quickly on this Xperia XA2 running Sailfish 3.2.0.12. Even with the phone mostly locked and resting, battery went from fully charged to 70% in 4 hours. Finally, I logged in over ssh and ran top. A process with "fingerprint" in its name is running at full throttle. That would do it.

 3109 system    20   0   11972   2396   1788 R  98.0   0.1   1:13.67 android.hardwar  

The name of that process in its full glory:

$ ps lp 3109
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000  3109  2807  20   0  11972  2396 -      Rl   ?          1:21 /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony

The model number of the phone is H3123. The ZIPs that I used for flashing were SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile.zip and Sailfish_OS-Jolla-3.2.0.12-h3113-0.0.7.10.zip.

When I was setting up the phone after flashing, I did not configure finger unlocking. Suspecting that perhaps the unconfigured thing gets itself stuck in a loop, I tried to set it up now through settings (Device lock -> Add fingerprint), but I could not get past the "Place and lift your finger" screen: it never detecting me placing the finger.

I do not know if the fingerprint sensor worked at all before I flashed the phone to Sailfish, I did not test that aspect.

The parent process of this runaway process is /sbin/droid-hal-init. I found /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.sony.rc. According to this README.md, these files understand an option called disabled, so I added that to the .rc file and rebooted. That worked. (When I just renamed it to a file not to have the .rc extension, that did not help.)

It will take some time worked.

Since then, the battery percentage has stayed the same for me to assess the battery life after this, but for at least 20 minutes by now. So that fixed it.

For the benefit of whoever finds find themselves in the same situation and does do not care for the fingerprint unlock either, here is the change that I made (under devel-su) in order to disable that process:

--- /home/nemo/android.hardware.biometrics.fingerprint@2.1-service.sony.rc.ORIG
+++ /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.sony.rc
@@ -1,7 +1,8 @@
 service fps_hal /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony
     # "class hal" causes a race condition on some devices due to files created
     # in /data. As a workaround, postpone startup until later in boot once
     # /data is mounted.
+    disabled
     class late_start
     user system
     group system input

The battery has been draining surprisingly quickly on this Xperia XA2 running Sailfish 3.2.0.12. Even with the phone mostly locked and resting, battery went from fully charged to 70% in 4 hours. Finally, I logged in over ssh and ran top. A process with "fingerprint" in its name is running at full throttle. That would do it.

 3109 system    20   0   11972   2396   1788 R  98.0   0.1   1:13.67 android.hardwar  

The name of that process in its full glory:

$ ps lp 3109
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4  1000  3109  2807  20   0  11972  2396 -      Rl   ?          1:21 /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony

The model number of the phone is H3123. The ZIPs that I used for flashing were SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile.zip and Sailfish_OS-Jolla-3.2.0.12-h3113-0.0.7.10.zip.

When I was setting up the phone after flashing, I did not configure finger unlocking. Suspecting that perhaps the unconfigured thing gets itself stuck in a loop, I tried to set it up now through settings (Device lock -> Add fingerprint), but I could not get past the "Place and lift your finger" screen: it never detecting me placing the finger.

I do not know if that is relevant, but I will note that I did not install the android subsystem.

I do not know if the fingerprint sensor worked at all before I flashed the phone to Sailfish, I did not test that aspect.

The parent process of this runaway process is /sbin/droid-hal-init. I found /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.sony.rc. According to this README.md, these files understand an option called disabled, so I added that to the .rc file and rebooted. That worked.

Since then, the battery percentage has stayed the same for at least 20 minutes by now. So that fixed it.

For the benefit of whoever find themselves in the same situation and do not care for the fingerprint unlock either, here is the change that I made (under devel-su) in order to disable that process:

--- /home/nemo/android.hardware.biometrics.fingerprint@2.1-service.sony.rc.ORIG
+++ /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.sony.rc
@@ -1,7 +1,8 @@
 service fps_hal /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service.sony
     # "class hal" causes a race condition on some devices due to files created
     # in /data. As a workaround, postpone startup until later in boot once
     # /data is mounted.
+    disabled
     class late_start
     user system
     group system input