ADB over TCP and Wireless Debugging modes not working

[Bingblop]

Please check before submitting an issue

• I have read CONTRIBUTING.md and the relevant sections of the ROADMAP.md.
• I am running the latest AppManagerNG release from GitHub Releases, IzzyOnDroid, or Obtainium (not an upstream App Manager build).
• I have searched open and closed issues and could not find an existing report.
• I can reproduce the issue and have collected the support-bundle fields below, or have noted what is missing.

Describe the bug

I use App Manager frequently so decided to give this fork a try but only Shizuku working mode works for ADB access. Tried all the usual fixes, but nothing worked, even though it is paired.

Steps to reproduce

Try to use ADB over TCP or Wireless Debugging Modes of Operation.

Expected behavior

No response

Screenshots or screen recording

No response

Logcat or crash log

No response

AppManagerNG + mode

• AppManagerNG version (Settings → About):
• Active mode: Auto / Root / Shizuku / ADB-WiFi / ADB-USB / No-root
• Privilege provider: Magisk / KernelSU / APatch / Shizuku / Sui / ZygiskNext / None
• LocalServer bootstrap signature (Settings → Mode of operation, if shown):
• Install source: GitHub Releases / IzzyOnDroid / Obtainium / F-Droid / sideload

Device + Android

• Manufacturer + model:
• Android version + API level:
• Build / ROM:
• Security patch level (YYYY-MM-DD):
• Architecture (arm64-v8a / armeabi-v7a / x86_64):

Affected operation (if applicable)

No response

Additional context

No response