serverless-dns VS issues

sky is a stub resolver, which after stripping out all request information, forwards the dns query to both Cloudflare and Google DoH servers (code), and replies from which ever responds back the fastest. Both the client app and the resolver (server) are open source, so if you find any leaks and know what's up, we're open to changes.

There is also https://github.com/serverless-dns/serverless-dns that works on user-configurable list combinations using Cloudflare Workers (100k queries per day), though it can't be integrated with WARP.

Max (fly.io) and Sky (cloudflare) are both are no logs. You can examine the code to ascertain this (here) and also check the version of the code we've deployed too (via github actions).

You can selfhost your own adblocking server on Cloudflare Workers and edit the upstream, you get Quad9 malware filtering, Cloudflare's nearest servers, and whatever blocking list you want.

Took us wayyy longer than originally planned, because not only personal life got in the way, we also run our own resolver (open source) maintaining which took away some of our time too. Especially, as the costs were mounting, we couldn't ignore it and had to optimize it as much as we could (which we since have).

Even those who weren't interested in self-hosting might spend a couple of minutes hosting their own DNS proxy since it's much more flexible and don't require root or dedicated port (at least with DoH).

I swear this idea wasn't generated over chats and coffee with GPT3; though, most of the code for this feature was most certainly written by it (commit). Be careful with your reviews of this feature then; you don't want to upset a sentient Optimus Prime AI.

If you are deploying your own rdns, then logs and analytics are up and running (check the github readme). NRDs and other things will happen as we near launch (in a month or two, perhaps). But we are just 2 developers, and our time is really all spent on the Android app, and not the service...

Maybe, this is what you want? https://github.com/serverless-dns/serverless-dns

I've just created a problem here: https://gitlab.com/LineageOS/issues/android/-/issues/6363

Checking if it's a known issue, and if it's not, reporting it

We use GitLab for bug reporting. Please see the instructions there.

Yes, that was my first idea too and I looked whether it is possible to deactivate the hardware acceleration in the settings - but I couldn't find anything. Ancient? Hey, the devices are only 9 years old. Planned obsolescence... ;-) In the meantime I found the following bug report - also a klte: https://gitlab.com/LineageOS/issues/android/-/issues/5999

Afaik there is no known way to fix your current issue. If any and all wired headsets seem to produce the issue and you are sure that this issue wasn't there when you used your 5a on stock rom before flashing it, raise a bug report here: https://gitlab.com/LineageOS/issues/android/-/issues

Yes, the same issue happen after the OTA update, i have created one ticket on lineage OS https://gitlab.com/LineageOS/issues/android/-/issues/5950

This problem has been reported here: https://gitlab.com/LineageOS/issues/android/-/issues/5890

You could bring it under attention with a general thread here: https://gitlab.com/LineageOS/issues/android