[Verizon Galaxy Note 3 General] capnkrunch:
I believe this is an issue with the vidc kernel driver. That driver is a mess and I don't think qcom (via CAF) has even ironed out all the issues upstream. That being said temasek hasn't touched the vidc driver since the 8th so maybe the other variants are working and it's an issue with our device tree (or the proprietary blobs* maybe?). Streaming has been broken for me since 2.5 (I think). Has anyone had YouTube et al working on any lollipop builds? Has anyone reported to temasek with a logcat? Unfortunately I can't post in dev forums. I've trying to build a version with CAF's mainline vidc but I've been having build box issues**. Maybe I can get it done on Wednesday or Thursday.

WiFi seems spotty on 3.4; at least on the 5GHz, 2.4 is just as awful as it always is. Looks like it is disconnecting amd immediately reconnecting on logcat. Generally has no effect but messes with bandwidth heavy actions. How is it on 3.5? Once I upgrade I'll grab some logcats and maybe someone who can post on development forums can try to duplicate it point temasek towards them.

How is GPS on 3.5? It's still broken on 3.4 for me.

About the bootloader, is ryan still working on updating the 4.3 one? I have my aboot if that helps. Also, I was reading the modem thread and beans said he has all the stock partitions backed up just not all are uploaded. Someone could probably get in touch with him for anything ryan still needs (bigbiff too I think needed something in the twrp thread).

Lastly, would anyone be interested in another kernel for TW ROMs? I was throwing some stuff together butryanon't have a build I like and I am not a developer (literally and in terms of posting privileges). The main features are touchwake (from yank555.lu) a updated vidc driver (from CAF) that partially fixes HD YouTube

-it now works on slower connections; before the fw crashed on timeout

-it still doesn't recover properly from fw crashes (despite what some commits would have you believe)

-screen off still causes crashes (possibly less frequently? This one confuses me)

There's a few other odds and ends but I kind of abandoned it for temasek's preview. If there's some demand for a hltevzw kernel though I'd be happy start working on it again. Or feel feer to fork it or submit pull requests, that would be much easier on me. Heck, just PM and I will probably give you collaberator status.

source

Super off topic footnotes:

*These scare me because I don't understand them. I feel like when VZW drops support (before the other carriers of course) we might lose "stable" support from CM since our blobs are not quite the same as the variants

**Abbreviated list: Windows Update broke VBox on Windows 7, I mistook it for a corrupt virtual drive (my laptop battery has a tendency to fall out and corrupt them, often irrecoverably), I deleted it, when I reinstalled it was still broke, downgraded VBox, Architekt has the wrong java for L and I fail at the Arch way and couldn't switch it (seriously archlinux-java set changes archlinux-java status but not java --version; O think it's due to Architekt using an AUR java6 since the official repos only have openjdk), Microsoft fixed the broke update, reinstalled current VBox, dropped the battery twice while install Ubuntu, guest additions not working properly