t-m-w

> We are already handling each packet from every app today in Orbot Yes, it has to happen at some stage. I didn't dig too deep, but it looked like...

Wow, that's something. I suppose it was worth a try...? Sadly, the most relevant thing there is the `allowBypass` option, which would allow any app to decide on its own...

This could be great news. I haven't tried it because re-compiling is more than I'm up for at the moment, but if it works (can anyone else confirm?), I think...

To clarify: In 21.02.2, nothing has been fixed related to this issue, at least for me. Even with WPA2, 802.11w still causes the same behavior as it always has for...

Yes, this accurately describes the behavior on a physical device running Android 13, and I have tested it. I have not confirmed Android 12's behavior, but I assume it suffers...

Sure thing... Here's what I know and how to test. The behavior I've described is for when a VPN connection is *not* established, in which case, for Android 13, [all...

This all sounds fine to me! I haven't looked into it in a while. AOSP hasn't even weighed in on whether the behavior is intentional or not, and they haven't...

Thank you. I wish I had seen this sooner. I was not receiving random errors, but a very consistent "Server Error" bar at the top of the page (or 500...

Sounds good, thanks for all the info; happy to look into moving things around and following those suggestions. You had mentioned the fused location provider before, but I was having...

> * I am unsure if locations should be restricted at the network location provider if they mismatch GPS. I would assume it's the task of the network location provider...