[OnePlus 3 & 3T Cross Device Development] pilikia:
I used to use netguard when I didn't have root. If I recall, netguard only offers filtering if you donate. I stopped using it because I changed phones and lost the pro features at the same time. I refused to have to login to google just to be able to use what I already payed for. The unlock method the netguard dev uses apparently involves a 3rd party or whatever, and I consider that too involved, if you will.

On my 1+3T, I have the correct radio, I believe-9.0.6/11.20.19, to dirty flash from this v16 microg rom to the nightly lineageOS 17.1 official. Anyways, after flashing, rebooting to twrp, rebooting to the OS, I still lost my left-most hardware button, just like with your rom. WEIRD. I give up. I'll try one more iteration of yours but for the life of me can't figure out how a successful boot from 16-17 roms, known to be good, renders a hardware button unusable. As for fdroid, or any ap, I do not want to use adb commands just to install a rom which is dirty-flashable. The only option the phone gives me is to disable fdroid. That's it. The whole aps being signed by fdroid bs I don't want to be involved with. I just want it to update and work. If it doesn't that fdroids problem, not mine.

I noticed the new network permission settings in the v17 microg rom had some lame options. "Only allow when active?" LAME. If you allow a permission it should never depend on whether or not the ap you installed is "active". Say you give an ap the ability to use the gps chip. If you aren't using the ap and your gps is on for some other ap usage, why need a setting to differentiate between active and not active? WHY? The entire 'fuse' bs google uses is exactly what makes controlling all your permissions a major PITA. Albeit they are somewhat simpler in 17, it's obvious google is moving forward with obfuscating any real control by the user. In essence pretending permission/security depends on a checkbox labeled "active?, no?, maybe?" is pure utter BS!

Google sells their own phone. The pixels? There are 2 roms, graphene and calyx, that will only work on google phones. They are similar to this one in a lot of ways, but just using their hardware and then putting ANY version of android on it is, imo, a security risk. Like I said. Who cares if your phone is encrypted if your comms aren't? That's why I love mse's rom. He gets it and strives for control. Unfortunately, every next version of google's android is like chasing your own tail. Google changes the permissions, always with more "security" features (snicker), and the community has to figure out what in the f the problem is now. Believe me when I say the newer permission settings are pure BS. Google tries to figure out how to fool the masses into some 'trust' postion of pretentious, "But I checked the box...". Really I'd go back to an older flip phone before I'd trust google ever again, ever. I started dumping google before their gmail was even out of beta.

I tried. Too bad you don't own a oneplus 6. I'd have bought one just for your rom (my 3T was pre-owned when I bought it). I also will never own a 5G phone for that matter. I don't care the phones change and get better hardware, but the roms should not 'require' a specific versioning of said hardware. If the phone works good still, any rom install should cater to the existing hardware, not the other way around. And that in a nutshell is the problem with smartphones. They keep forcing newer roms, which then force you to 'upgrade' the device. The pattern is obvious and it's one of a carrot on a stick you never actually get to hold on to. "I like my phone, I think I'll hold on to it". Google's response? NOPE. FU GOOGLE!