@Linda_CH: I moved your post to the FP2 topic. I never used RadioDroid. In my post you replied to I just explained to someone how to make sure the newest version (of any app) is displayed in F-Droid.
I can use radiodroid without problems or special settings. Maybe you should check, if you change the correct volume type while pressing vol+ button (not ring tone)? You should try this DURING the radio is already playing!
What I’m doing is using WireGuard over public WiFi and mobile (LTE) to connect to my home router and use that as DNS. The DNS (dnsmasq) uses blacklists to filter ads, so I don’t see any ads in any apps. It then forwards to unbound which uses DNS over TLS (its slightly slower because of this setup, but doable). This solution doesn’t require root on clients though WireGuard runs better as root. Furthermore, all outbound traffic on my router with destination port 53 (TCP and UDP) is redirected to dnsmasq. So it catches 22.214.171.124 and 126.96.36.199 and anything else unencrypted.
can you explain how do you block ads via DNS?
I’m using openWRT with adblock (with custom lists), but the majority of ads are not blocked since the block is not possible at DNS level.
Remember that 188.8.131.52 and 184.108.40.206 are google DNS. It is much better to use OpenNIC via DNScrypt (220.127.116.11 and 18.104.22.168 or via DNScrypt 22.214.171.124 and 126.96.36.199) or, if you like DNS over TLS, cleanbrowsingDNS (188.8.131.52 and 184.108.40.206) or cloudflare (220.127.116.11 and 18.104.22.168) that are more privacy focused that google .
Why is the block not possible at DNS level?
These are the rules I use:
DNAT tcp -- 0.0.0.0/0 !192.168.0.1 tcp dpt:53 to:192.168.0.2:53 DNAT udp -- 0.0.0.0/0 !192.168.0.1 udp dpt:53 to:192.168.0.2:53 DNAT tcp -- 0.0.0.0/0 !192.168.30.1 tcp dpt:53 to:192.168.0.2:53 DNAT udp -- 0.0.0.0/0 !192.168.30.1 udp dpt:53 to:192.168.0.2:53 DNAT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 to:192.168.0.1:53 DNAT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53 to:192.168.0.1:53
All loose DNS traffic is being forwarded through 192.168.0.1 (my gateway internal LAN address). Except when it is going to 192.168.0.2 (my main server). That’s for failover. The 192.168.30.1 rules are for VPN. The DHCP server also already gives the correct DNS information; the above is just for stuff which (for whatever reason) still wants to use something else.
OpenDNS = Cisco. I use Quad9, but that’s owned by IBM. I don’t assume any of these companies are not data hungry (including Cloudflare) but I will agree with you that Google seems to be one of the worst offenders.