Hi,
I have a very big problem.
After I’ve flashed this rom (Unofficial cm13 Mr. Coldbird), the fingerprint sensor disappeared from the settings
How can I fix it?
P.s
It 's my first message , I hope I used the correct section of the forum
Do you flash mm-firmware.zip?
for me it works sometimes and sometimes keep hanging " just vibrating without unlock " .. sometimes it says " hardware is not found "
i entered the recovery and flashed mm-firmware.zip again and the same problem exist ... i'm thinking to back to COS 12.1 it was working perfectly !
I have exactly the same problem, fingerprint option totally disappeared from my lockscreen settings. No idea how to fix it.
Shivver said:
I have exactly the same problem, fingerprint option totally disappeared from my lockscreen settings. No idea how to fix it.
Click to expand...
Click to collapse
when I'm looking for a setting, that I can't find in the settings dialog, I'm using the search function, there. This showed already quite some features.
I'm still on original Cyanogen OS 12.1 (5.1.1), though...
best regards
m
meikelrix said:
when I'm looking for a setting, that I can't find in the settings dialog, I'm using the search function, there. This showed already quite some features.
I'm still on original Cyanogen OS 12.1 (5.1.1), though...
best regards
m
Click to expand...
Click to collapse
Install mm firmware.zip
Sent from Zuk Z1 using Tapatalk
Same Problem here.. In cm13 official and Mr coldbirds Version.. Even with installing mmfirmware.zip
I have the same problem too. It have tested on official CM13 and om Mr.Colbird CM13 versions.
me too
the problem of vibrating that was because of third party app like " screen lock " but if you locked it with power button or double tap the fingerprint sensor will work perfectly :good:
I happen the same. Since I installed unofficial CM 13 (Mr. Coldbird) fingerprint sensor has disappeared.
I have even tried to solve it installing stock COS with qfil, but although the app has appeared again, the sensor doesn't work. I put the finger on it, but no signal arrives to the phone.
I have tried hard reset, install mmfimware, official CM 12 and 13, unofficial 13, but nothing work.
Any idea? Thanks.
Vfc73 said:
I happen the same. Since I installed unofficial CM 13 (Mr. Coldbird) fingerprint sensor has disappeared.
I have even tried to solve it installing stock COS with qfil, but although the app has appeared again, the sensor doesn't work. I put the finger on it, but no signal arrives to the phone.
I have tried hard reset, install mmfimware, official CM 12 and 13, unofficial 13, but nothing work.
Any idea? Thanks.
Click to expand...
Click to collapse
Try this method I have described earlier. It has recovered my Fingerprints already twice. Also because of trying unofficilal cm13. http://forum.xda-developers.com/showpost.php?p=64742948&postcount=2
Planet X said:
Try this method I have described earlier. It has recovered my Fingerprints already twice. Also because of trying unofficilal cm13. http://forum.xda-developers.com/showpost.php?p=64742948&postcount=2
Click to expand...
Click to collapse
I'll try and report. Thanks!!!
I've tries, but it hasn't worked.
Just one question, how do you exit fastboot mode?. I'm a beginner, sorry.
Vfc73 said:
I've tries, but it hasn't worked.
Just one question, how do you exit fastboot mode?. I'm a beginner, sorry.
Click to expand...
Click to collapse
Fastboot reboot or just press the power button until the phone shut down. I don't know went it didn't help you but i have recovered my fingerprint reader already twice with that procedure. You will lose nothing when just flashing the modem and the bootloader. My guess is that the persist.img is the partition you need to restore for the fingerprints. My fingerprint reader has been acted really crazy when i tried the unofficial cm13. Until it stopped working. I restored my backup and did the procedure to recover my fingerprint reader. I'm now on self built odexed cm13 nightly 's with working fingerprint reader.
Stopped working here too. Tried to restore COS but even if the setting is there, fingerprint doesn't get detected (phone keeps vibrating)
simoneser said:
Stopped working here too. Tried to restore COS but even if the setting is there, fingerprint doesn't get detected (phone keeps vibrating)
Click to expand...
Click to collapse
Read my post above. I have recovered two times from this issue. I had it also because of trying unofficial cm13. You will loose nothing but get back your fingerprints.
I have tried but it doesn't work
Inviato dal mio Z1 utilizzando Tapatalk
I have tried too, but it doesn't work.
Vfc73 said:
I have tried too, but it doesn't work.
Click to expand...
Click to collapse
Yesterday my fingerprint stopped again too. So I did the same procedure again and it didn't work anymore for me too. So I tried to flash the official cm13 again. First it didn't work but after a few minutes it started to work again. I really don't know how this is possible but there is one difference. The radio from official cm13 is newer than the one from COS. I'm happy that it works fine again but I'm afraid it will stop again when I try a different rom again.
Hey!
today I noticed something very weird on my OnePlus 5 (64GB)
somehow unlocking the phone with the fingerprint scanner isn't working anymore!
it always says that I have to use my code, like when you unlock it the first time after powering on!
the hardware is working, fingerprint scan works for example fine with my banking app and the option is still available in the settings menu!
Android 7.1.1
security patch 1st september 2017
francokernel 4.4.21
xxx nolimits rom 4.2 based on oos 4.5.14
rooted with magisk
xposed framework v88.2 installed
I did not make any changes to the phone, it simply stopped working!
I have already removed the security unlock and added new fingerprint scans, it did not work...
can anybody help me?
Are you using Greenify? If so, make sure "Alternative Screen Off mode" is enabled in Settings.
Sent from my ONEPLUS A5000 using Tapatalk
Just restart your phone and all works fine again...
If your fingerprint unlock still doesn't work I would try stock OOS instead of xXx No Limits and see if you still have the issue. I found that ROM extremely buggy both times I tried to run it and the other stock based ROM I tried (Freedom) really wasn't much better.
okey I fixed it by wiping cache and dalvik
thanks for your answers
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
rzarectha said:
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
Click to expand...
Click to collapse
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Choose an username... said:
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Click to expand...
Click to collapse
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
rzarectha said:
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
Click to expand...
Click to collapse
Yeah, I just didn't know what you meant. I guess it might be a root app or something. I used Material Notification Shade on stock but it had a couple of problems that i didn't figure out until some time ago (it was pretty obvious though)
And for something physical, have you fitted a screen protector lately? I had one that interfered with pull down.
For starters, ive been using the same lockscreen pin on ALL of my devices for the past3 years, I know im using the right one. I recently installed the Evolution ROM and set it up with fingerprint and PIN. Fingerprint was working just fine, I rebooted the phone after installing a magisk module and now its telling me the pin for the lockscreen and TWRP is wrong. Again, I only use ONE pin and its telling me its wrong. Tried deleting the locksettings.db file to take off the screen lock and that worked but now phone just stays on "Phone is starting" and TWRP is still excrypted but lets me see all of my files, correct storage amount, and install zips.
When you installed did you format data?
I know this says Lineage, but it works for most custom ROMs, post #2 has the cliff notes version: [Guide]Installing Lineage
As for the locksettings.db, this isn't like older Android devices. You can't just do that, it doesn't fix the problem here.
Hi all,
Is there any Custom ROM running Android 11, with encryption working. I tried PE11 and Crdroid 7.4 and Arrow11.
All are going to boot loop, if encryption is initiated.
I'm looking for a ROM which can do encryption (for work purpose). It will be helpful, if someone can share working custom ROM tested.
Also is this some kernel issue or TWRP settings which is causing encryption to fail?
I would also love encryption. This is one of the persistent issues I have with custom ROMs and why I'm moving to a real Linux phone once they get a bit better.