Develop Bugs

Fingerprint scanner stopped working

Just recently my fingerprint scanner will decide to stop working. I'll dirty flash my ROM (latest PureNexus) and it'll go back to normal for a little while. Is this a known issue with nougat I'm not aware of?

JeauxAdam said:
Just recently my fingerprint scanner will decide to stop working. I'll dirty flash my ROM (latest PureNexus) and it'll go back to normal for a little while. Is this a known issue with nougat I'm not aware of?
Click to expand...
Click to collapse
No, that is not a nougat issue or an issue with that particular rom. It's either firmware, which is in vendor our a failing fingerprint sensor. Try re flashing vendor and see if that helps

I was having that problem too. I tried several things with no luck. The menu option for the fingerprints (under personal/security) disappeared, and since I am clueless about the Nexus phone (iPhone convert), I was baffled. For a separate reason, I had used the ad blocker plus browser to clear the cache of suspicious garbage, then restarted my phone. The fingerprint menu item reappeared, and now the sensor works again....so try clearing your cache.

I got too i fixed by clean fingerprint connector in the phone.

PSA: Don't use anything higher than TWRP 3.0.2-0 for the M919

Can say definitively that 3.0.2-0 is the last full working version of TWRP recovery 99% without issue for the M919. Yesterday I spent the day installing different versions of TWRP since 3.0.2-0, installing the same Lineage 14.1 nightly, installing apps and testing wifi, ODINing back to factory, and installing the next version.
Originally I was on 3.2.1 and noticed crazy WiFi disconnect issues and system slowness and general bugginess. Read all the problems other people with other models of S4s were having with later builds of TWRP on later builds as well. I don't know what changed, but everything after 3.0.2-0 caused all the issues people hate to see with custom ROMs for this phone.
I have no WiFi drops, no lagginess, no issues with cell network, no random reboots. I say 99% because I'm sure there's something that might crop up that I haven't found, but if you're looking to get a brand new life out of your S4, stick with 3.0.2-0, and Lineage 14.1 works great.

Wonder if that's why I've been having dropped calls and a occasional freezes/reboots...
Overall the S4 has been working well, but its not 100% reliable. On my daily commute there's a couple spots I will always drop calls. I also noticed randomly I will lose all bars for no reason and it will come back a few seconds later. Last I've noticed that my phone will randomly freeze. All of these faults are occasional but its enough for me that it can lead to problems. These problems have shifted between ROMs as well, optimized lineage, standard lineage, etc.
Can you tell me if I need to reinstall my ROM too, or can I just flash the twrp you mention here?

I just flashed twrp-3.1.1-0-jfltexx with the latest nightly, wifi worked fine the past two days. Not sure about calls, haven't talked long. It's the version lineage suggests to use in their instructions.
I did notice that the CPU heats up in TWRP though, have to hold phone under a fan if backing up or flashing.
How would recovery would affect the wifi and calls though? I would think it would depend on the last firmware you had (I guess modem etc) and lineage itself...?

This is interesting. I just did my m919 with the new lineage 15.1 os and used twrp 3.2.2 and I havent noticed any issues so far. Maybe the latest 3.2.2 fixed the issues you described?

doom3crazy said:
This is interesting. I just did my m919 with the new lineage 15.1 os and used twrp 3.2.2 and I havent noticed any issues so far. Maybe the latest 3.2.2 fixed the issues you described?
Click to expand...
Click to collapse
Perhaps, I'm still rocking 14.1 as we just use the phone as our "house phone" and as a baby monitor (call myself via Hangouts from this phone, put it in kid's room) so I'm not sure about going through the whole upgrade/update process. If I get an itch for punishment I'll set aside some time on a weekend to try

How did you find 15 thought this only had 14.1

WangChung81 said:
Can say definitively that 3.0.2-0 is the last full working version of TWRP recovery 99% without issue for the M919. Yesterday I spent the day installing different versions of TWRP since 3.0.2-0, installing the same Lineage 14.1 nightly, installing apps and testing wifi, ODINing back to factory, and installing the next version.
Originally I was on 3.2.1 and noticed crazy WiFi disconnect issues and system slowness and general bugginess. Read all the problems other people with other models of S4s were having with later builds of TWRP on later builds as well. I don't know what changed, but everything after 3.0.2-0 caused all the issues people hate to see with custom ROMs for this phone.
I have no WiFi drops, no lagginess, no issues with cell network, no random reboots. I say 99% because I'm sure there's something that might crop up that I haven't found, but if you're looking to get a brand new life out of your S4, stick with 3.0.2-0, and Lineage 14.1 works great.
Click to expand...
Click to collapse
I had the same problem you did but found this custom TWRP 3.3..0.0 worked great if you want to try roms above 14.1
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
yoshkapundrick said:
I had the same problem you did but found this custom TWRP 3.3..0.0 worked great if you want to try roms above 14.1
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...p/jdcteam-twrp-3-3-0-0-custom-builds-t3925619

Help Needed - No Fingerprint After Backup

Hey so I'm new to the OnlePlus 5T. I used to be on the 3T and never had any issues like this, I was a flashaholic on that device so I know my way around the process of flashing custom roms. Or at least I thought so?
So before I ask, here's what I'm running:
- Latest OOS Firmware, I believe 9.0.4
- Resurrection Remix Pie (Official), Dumpling.
- TWRP (Can't remember the version but it's the latest by codeworkx, was posted this month)
- I AM encyrpted
- I AM rooted with the latest Magisk
So here's what I did: Yesterday I got irritated by the lack of official RR updates, so I tried out an unofficial luisroms build. I reverted back because I realised not much had changed, but when I restored my backup I couldn't get into my phone as it said I needed a password even though I made sure to remove all lockscreen security before making the backup in the first place.
After a few hours of trying, I got in but couldn't register a fingerprint. It just wasn't recognising my finger when I tried to actually set it and stayed on the "Touch the fingerprint sensor" screen.
So I went back to Oxygen OS, made sure I was fully updated and encrypted and then re-flashed official Resurrection Remix Pie for Dumpling.
(Important: As of this point, the fingerprint sensor was working perfectly again, so the physical sensor is working fine!)
I've only just got the phone fully set up, I removed the lockscreen security (Including the fingerprint) and went into TWRP. I made a backup. Then I rebooted back into the OS and now when I'm trying to apply my fingerprint again, it's not recognising my finger. Exactly the same as it was before I re-installed OOS.
So summary: TWRP Backups and Restores are breaking my phone's ability to use the fingerprint sensor. Is this a known issue, and how do I fix it?
Thanks for your time, hopefully the good people of XDA can help me out here :good:
EDIT: Progress has been made, ish.
By going into root/data/system/users/0 and deleting "fpdata" and "settings_fingerprint.xml" I can now get the fingerprint setup to recognise my finger in the settings, but right as I'm about to do the final fingerprint press to set it up I get the error: "enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger"
FURTHER EDIT: So as unrelated as it seems, with the issue happening right after making a backup in TWRP, it appears the issue was caused by a Magisk module called NFS-INJECTOR. Not knocking that project, it's amazing and I'm still using it, but after disabling it in magisk and rebooting I was able to set a fingerprint just fine. I've now re-enabled the module and all seems to be working correctly. I've reported the issue over there and linked to here for steps to reproduce, hopefully it's something that can be fixed. I'll leave this up in case anyone else experiences the same thing.

OnePlus 5t screen blinking/flashing and freezing problem

Hi All,
I am having a strange problem with my OnePlus 5t.
I have used msm flashing tool to flash oxygen os (4.7.4) and after that if I perform an OTA update to 5.1.4 (treble) which creates a vendor partition, phone stands mis behaving (blink, freeze, screen flash like old CRT TV when it has no signal and millions of dots of different colour)
Everything works fine if I use the below link to download one by one all the full updates and perform an update via local storage. https://forum.xda-developers.com/on...s-5t-mirrors-official-oxygen-os-t3708099/amp/
don't know what is the real problem but I am flashing/reflashing all the things which I find in XDA including customer rom, different msm flash etc but problem comes back.
It has been almost 6 months since I am reflashing the stock oos using msm when ever the problem comes back.
I need some advanced help.
I think there is some problem when oos update creates vendor partition.

Fingerprint enrollment fails on custom ROMs

For the past two days I've been trying to get fingerprint to work on custom roms. I've never experienced any issues while going from stock to Lineage 16, then to Havoc/MSM Extended. The issue started happening when I first installed Lineage 17.1 Now whenever I try to enroll my fingerprint on a custom rom(LOS16/16/Havoc/MSM), it fails with error: "Fingerprint enrollment didn't work. Try again or use a different finger.". When I go back to stock it works again but as soon as I go back to a different rom the error happens and prevents me from using the fingerprint scanner.
Has anyone else experienced this issue and knows how to fix it? Thanks in advance.

luukvbaal said:
For the past two days I've been trying to get fingerprint to work on custom roms. I've never experienced any issues while going from stock to Lineage 16, then to Havoc/MSM Extended. The issue started happening when I first installed Lineage 17.1 Now whenever I try to enroll my fingerprint on a custom rom(LOS16/16/Havoc/MSM), it fails with error: "Fingerprint enrollment didn't work. Try again or use a different finger.". When I go back to stock it works again but as soon as I go back to a different rom the error happens and prevents me from using the fingerprint scanner.
Has anyone else experienced this issue and knows how to fix it? Thanks in advance.
Click to expand...
Click to collapse
Don't directly go from stock to q, flash Oreo rom or pie rom then flash q rom.

Sohit5s said:
Don't directly go from stock to q, flash Oreo rom or pie rom then flash q rom.
Click to expand...
Click to collapse
Thanks so much, this indeed has me back on MSM9 with fp working!