[Verizon Galaxy Note 3 General] capnkrunch:
That's a good question. I thought I heard a while back that Hashcode was making good progress on the drivers but NFC still don't work (on cm12 at least. Did it make it into the more recent cm11 builds?) and he seems to have jumped ship. I flashed the old one out of habit when I first flashed Lollipop and a couple files weren't there. That zip was just an edify script that deleted things. Shouldn't be terribly hard to figure out what needs to be changed or added.

[MENTION=4530182]LillieBennett[/MENTION]

I knew it, but, I figured he would stop out of spite because Note 3 owners kept asking him dumb questions, not posting logs, etc. He threatened to stop all hlte builds about a week ago. Also, the vzw there were probably less downloads of all the Verizon variants on all his hosts than the some single releases for the international variant.

Funny thing about the blobs, the KK ones were identical for Sprint and Verizon. With any luck the new Sprint ones will work for us. I was going to try building with the updated blobs but I'm still having build box issues. Here's the updated repos if someone wants to try building with them (use Temasek's default and I can post my local if you need it).

https://github.com/capnkrunch/android_device_samsung_hltevzw

https://github.com/capnkrunch/proprietary_vendor_samsung

Too bad beans and Hashcode aren't around anymore. It kind of looks like we're going to lose CM support. The official hltevzw repo doesn't even have a 12.0 branch yet and when last I checked gerrit (a few days ago) there's no pending commits for us.

About streaming:

logcat and dmesg look like selinux is the culprit. Permission issues are causing vidc to crash, and I've also seen it crash the audio driver (while streaming Pandora) and cause WiFi disconnects. This also explains why we're the only variant with this issue. Anyone else been having WiFi or streaming audio issues as well? Hopefully it can be fixed by cherry-picking from the Sprint or GSM trees, otherwise it is over my head.

About the bootloader:

I odin'd beans "stock" tar a couple weeks ago and when I booted updater said there was an update to NC4 available. Verizon's rep said it was "maybe" DE specific and "probably" wouldn't lock my bootloader. So flashed it and it failed. Then again. Odin'd beans back on and forgot about it. Modem is the same and aboot's hashes match with before I did this. I asked Verizon about the update on Twitter and they want to know the exact revision number of the update so I need to odin bean's tar again (in the next day or two if you haplen to be doing an emergency odin or are going back to stock for whatever reason let me know what the update is called. It would be a huge time saver).

EDIT: Temasek's htlevzw device tree (not the official CM one though) has the NFC HAL in it someone (Hashcode?) got it working. Thing is, NFC is broken on Lollipop for all note 3 flavors. IF we get future builds and IF the NFC HAL does work for us then at some point it stops being an issue. Until then, if BBS shows NFC draining battery I can't imagine it would take much to update the nfc-remove patch.

EDIT: I messed up the vendor repo. It's inline with temasek right now. I'll fix it sometime tonight.