[Bug] ODoH custom proxy fails silently and falls back to naked DoH without warning (v055y)

[PortableMaker]

Device Information:

• OS: Android (Vivo Origin OS)
• App Version: v055y (observed behavior change from v055t)

---

Description

When configuring a custom ODoH (Oblivious DoH) profile using a valid Target Server paired with a custom Relay Proxy, the app shows "Connected" but completely bypasses the proxy. It performs a silent fallback to a "Naked DoH" connection without throwing any errors or warning the user that their real IP is exposed to the target resolver.

Note: In older versions like v055t, the DNS logs falsely stated "resolved anonymously" even without a proxy. While this UI bug was fixed/removed in newer versions (v055u-v055y), the actual custom proxy routing engine still fails to engage.

---

Steps to Reproduce

1. Go to Configure -> DNS -> Other DNS -> ODoH and tap the + button.
2. Create a custom ODoH profile:
   • Target Resolver: https://odoh.cloudflare-dns.com/dns-query
   • Proxy Relay: odoh.seby.io or odoh1.surfnet.nl
3. Activate the newly created profile (it will show as "Connected").
4. Visit dnsleaktest.com and run a standard test.

---

Actual Behavior

The DNS Leak Test reveals the ISP as Cloudflare located in the user's local region (e.g., Manila, Philippines) instead of the proxy's country (e.g., Singapore or Netherlands). This confirms that the proxy is being bypassed silently, defeating the core privacy purpose of ODoH.

Expected Behavior

1. The app should successfully route queries through the specified ODoH proxy relay.
2. If the proxy connection or handshake fails, the app should throw a connection error or alert the user instead of silently falling back to a naked DoH connection.

[ignoramous]

ODoH will not hide your actual IP. Setup Configure -> Proxy for that.

ODoH will not hide the DNS upstream from authoritative DNS resolvers vending fingerprinted DNS requests (like dnsleaktest.com, browserleaks.com/dns, dnscheck.tools, etc).

What ODoH does is hide your client identity (your client's public IP address, for example) from the DNS upstream (in your case, Cloudflare).

        --- [ DNS Request encrypted w/ Target public key ] -->
   +---------+             +-----------+             +-----------+
   | Client  +-------------> Oblivious +-------------> Oblivious |
   |         <-------------+   Proxy   <-------------+  Target   |
   +---------+             +-----------+             +-----------+
       <-- [ DNS Response encrypted with symmetric key   ] ---