Built-in HTTP/SOCKS proxy routing reliability

Duplicate Check

• I confirm I searched for existing reports and found no duplicates.

Describe the Bug

I tested the built-in proxy routing feature out of curiosity (I route traffic on device level thanks to @exclave) and it does not seem to work reliably for either HTTP or SOCKS proxies. The configuration appears to be accepted in the UI, but request behavior does not consistently reflect the selected proxy path. There is also no clear UI confirmation that the configured proxy is actually active and being used.

Steps to Reproduce

Open SimpMusic settings.

Configure a proxy under the built-in routing settings.

Test with an HTTP proxy.

Test with a SOCKS proxy.

Observe request behavior and routing.

Actual:
The proxy setting appears to be accepted, but routing behavior does not appear reliable. There is no obvious UI indication that the proxy is actually active or that requests are flowing through it.

Expected Behavior

Requests should consistently route through the selected proxy type, and the UI should provide clear confirmation that the proxy is active and being used.

App Version

1.6.0

Android Version

Android 16

Device Model

Samsung S25

Custom ROM

• I am using a custom ROM

Custom ROM Name (if applicable)

No response

Screenshots (optional)

No response

Log / Error Details

No response

Start by reproducing the issue from SimpMusic settings with both HTTP and SOCKS proxies on the reported Android setup, then trace the built-in routing path and its UI state. Done means requests consistently use the selected proxy and the UI clearly confirms when proxy routing is active.