bmccrary

I looked at the fingerprint briefly, and noticed that one of my fingerprints keep getting it's md5sum changed. I assume it's one, I have 3 fingerprints saved and each one is in the directory plus a .bak file. Deleting them and re-adding them still gives the same result though. I've tried setting the modify time back, and copying over the old files, but the apps still detect a fingerprint change. I'm not sure if the md5sum should ever change or not, I really don't see why it would. I'll look into this some more.

I have the same problem as @itsdevilslettuce with test 22, which I'm still on since it's working great and I'm a little hesitant to fix something that isn't broke, given the past. I've deleted all the fingerprints under security settings, then removed /persist/data/fingerprint. I can re-add the fingerprints and the directory is made like it should be. The real problem seems to be that for some reason most apps think the fingerprints have changed whenever you reboot. They are still set correctly and work fine, it's just that for your banking apps and such, you have to set them back up to wo

I did not change any settings at all. In fact, I avoided the *#*#4636*#*# menu altogether. It seems touching anything in there is an immediate death sentence, even if you put it back. I understand the pain, it's took me several days working on it when I can and I'm still not all set back up yet. I don't think you'll have any luck without flashing back to stock first but I could be wrong. I took all the updates but the only one that really seems to matter is the 20191111 one. After that you should be able to make everything work on the stock ROM, then flashing Lineage hopefully will work

I'm happy to report Verizon still working great on test22. I finally rooted with Magisk this time around and restored all of my apps and SMS/call logs. Everything is still working! I've tried powering the whole thing off too, several times. Maybe it's all fixed now and all that awaits me is more Lineage goodness! 😁 I've made a pretty good number of calls, texts as well as MMS messages by now. It's almost too good to be true! I have to go to the About screen now and then and make sure I'm still on Lineage and just didn't have this wonderful dream!

It's really crazy how it seems to work. If you reflashed to stock and did the one OTA update to the 20191111 it would probably work, at least for a little bit. I'm kind of scared to restart or power cycle my phone. I miss root, for one thing I can't restore all my apps but I'm going to just rock it for a few days and see what happens. The VoLTE did seem to fix outgoing calls. Before only incoming worked, outgoing never worked. It's just that it doesn't seem to last too long and I have no idea why.

Well I just had to flash test22. So far all voice/SMS/data is working just like it should on Verizon. I'm not going to root or install many apps and see how it does.

My time with test21 was limited, but the radio power and wifi would switch off at the same time at least once a minute then come back on, even the "radio power" switch in the phone testing menu would switch to off on it's own. I was trying to do a 100GB transfer to put my stuff back on and noticed if it went to the 5ghz wifi band, it would only stay for a short time (even with excellent 5ghz signal) then drop back to 2.4ghz. Eventually it would go back to 5ghz but only for a short time. I probably wouldn't have noticed except my 2.4ghz is 4x slower than the 5ghz so it makes a big difference

Mine looks fine too if it's on LTE/CDMA, until you actually try to make/receive a call. It shows the phone network as "1x RTT" but I'm quite sure Verizon never authorized the phone to work on CDMA at all so I guess that's why it then fails. I always have had to run mine in "LTE Only" on the stock ROM to make it work correctly. On the stock ROM, as soon as I flip the VoLTE switch the voice goes to "In service." I tried disabling the persist in the Lineage ROM so the switch was flippable, but toggling it didn't make a difference. @tdmI can still send you a Verizon SIM you can have if yo

I just put the factory image back on and paid attention to the fact the original 20191028 image behaves exactly the same as Lineage, however updating to the 20191111 build fixes the problem. I just wonder if something needs to be added from that build to Lineage, although I know it has way more updated vendor and modem images.

I've been off of here forever, mainly due to the fact it was depressing seeing all of the cool Lineage stuff and knowing I never could use it. However, I really wanted my keyboard fixed, and decided to upgrade from the January firmware which required a complete wipe in my case, and was amazed to see Verizon was working!! 🤩 So I flashed the test21 last night to try it out. I'm sorry to say my results haven't been as good. While it did work the first boot, as it always did in the past, it seems after a good full power off it doesn't work anymore. I did install the addonsu and used Titanium

I'd be happy to send you a working SIM card you could use if you would ever want to play around with it.

I had to go back to stock because somehow "VoLTE" got turned off again. I could not get/make calls or send/receive SMS/MMS when this happened. I was nowhere near a computer either so it was a major hassle for the day. FWIW, it never worked under the older stock builds either, so I'm not sure if any of the vendor blob updates would change anything. I get the impression this issue will be ongoing for a long time as there is no one to keep up with it, and that's OK, but it does mean anyone in the US using the largest carrier in the country can't use Lineage. I would think Sprint would h

@tdmhttp://www.mytelescan.com/vendor_2020-01-06.img.gz It was vendor_b, I should have checked the mounts on the OS beforehand.

That's an older build then. The one the phone OS has mounted has a January 2020 date. Maybe it's vendor_b? I'll pull that one and loopback it and see now that I know what to look for.

@tdmhttp://www.mytelescan.com/vendor.img.gz

I'm not sure I know exactly what to do but if you mean basically tar up a copy of /system/vendor I can do that. I had to go back to stock for now.

For us qwerty peeps, can we use the boot image too? I'd be really happy just to have arrow keys that go in the right direction.

I'm having the same problem with VoLTE. I wasn't 100% sure it was my phone as the cause as sometimes my signal isn't the best but I'm sure of it now. What I've noticed, and this could be pure coincidence, is that whenever I have the phone up to my ear and the screen is turned off the audio stops shortly after. When I pull the phone away and the screen turns back on the audio comes back. The speakerphone is only playing audio out of the bottom speaker which is right by the mic so the callers complain of really bad echo if I try to use it. Today I did out of desperation though, and the call

That's a great idea and I had thought of that myself. However, for whatever reason my mule, a Moto Z2 Play (direct from Motorola, not a Verizon one, but working on Verizon) would not enter the menu with the *#*#4636#*#* code. However, I just checked a minute ago and lo and behold my VoLTE switch is turned off again! Fortunately I can still get calls this time though. So I don't know. I'm happy to try anything if it helps anyone out.

Just for the record, when I flashed to test3 the first time somehow my VoLTE switch got turned back off. I had to go reflash stock again to turn it on. No calls at all work with it off on the Linage ROM for me.. It does indeed make a difference with the Linage ROM. I can now get incoming calls and visual voicemail on Verizon but no outgoing calls yet.

@tdm Wiping data allowed me to boot ok. I reflashed test3 and it would boot but the boot animation would just run on forever. I had problems with the first flash for some reason, at least I think that was my initial problem as I never could get /system to mount using the menu in the recovery, or was able to mount it in the recovery adb shell.

Ah cool, didn't know you could do that! I've got a shell up, I'll play around.

Yes, I had been running test2 before. I repeated the steps to install the test2 build but I didn't reset anything. I can try that but was just hoping to not have to. I understand what you're saying though if it can't access the main decryption key my PIN would then use to decrypt the /data partition.

Is there anything specific to be done to update? I've tried several times but can't get it to boot. The Lineage recovery is saying the OS can't start and to do a factory reset but I have several hundred apps and GB of data already on the phone and would prefer not to if I can somehow get it to work. Reflashing test2 won't boot either at this point. The adb sideload completes without any problem.

@Polaris Thanks for all of your help looking into this! I did check the issue tracker but was thinking my issue was different than the one I saw on there. Sounds like we'll have an awesome Lineage ROM soon! Thanks to @tdm for doing a lot of work and the test builds!