search

chenxiaolong / BCR

A Basic Call Recorder for rooted Android devices
GNU General Public License v3.0
1.66k stars 108 forks source link

Installed module breaks system biometric features (LineageOS, Android 14, Magisk 27.0) #547

Closed NikMAX2077 closed 1 week ago

NikMAX2077 commented 4 months ago

BCR module versions I tried: 1.62, 1.61, 1.59 and 1.53 (release) Device: Redmi 8 (olive) ROM: LineageOS 21.0-20240502-nightly-Mi439 (Android 14) Root: Magisk 27.0 stable (with Zygisk on)

Problem: after installing the module and reboot the system biometric unlock of the phone and applications stopped working. It's looks like no fingerprints were added. Biometric features disappeared from system settings. They are still visible in the search in the settings app, but trying to open them crashes the settings app.

After disabling the module from Magisk and reboot the phone, everything returns to normal and fingerprint features starts working again. Very strange.

UPD4: Everything start working fine after I turned off all other modules. Searching for conflict modules... UPD5: So I tried to reinstall Magisk and install modules in following sequence (single module per reboot):

  1. BCR - everything OK
  2. MicroG installer revived - OK
  3. Advanced Charging Controller - OK
  4. Viper4AndroidFX - problem appears!

Then I turned off Viper module and after reboot problem was gone. So it's look like Viper module make some changes that conflicts with BCR, but it's very strange that this conflict affect system biometric functionality

chenxiaolong commented 4 months ago

Interesting! I don't really have any idea why BCR and the Viper module would conflict. Especially right after reboot, since BCR doesn't run in the background until a call is active.

It might be worth trying to grab a logcat right after a reboot, but before logging in the first time. If there's a system component crashing, it'll likely show up in there.

NikMAX2077 commented 1 week ago

Problem has gone after some LineageOS updates several months ago. So it was ROM bug I think