[Bug]: adb termux-usb

[RohitVerma882]

Problem description

need adb support with termux-usb

What steps will reproduce the bug?

adb not connecting with usb

What is the expected behavior?

No response

System information

termux-info:

TERMUX_API_VERSION=0.50.1
TERMUX_APK_RELEASE=GITHUB
TERMUX_APP_PID=12663
TERMUX_IS_DEBUGGABLE_BUILD=1
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.0
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://packages-cf.termux.org/apt/termux-main/ stable main
Updatable packages:
curl/stable 7.83.1 aarch64 [upgradable from: 7.83.0-1]
git/stable 2.36.1 aarch64 [upgradable from: 2.36.0]
golang/stable 3:1.18.2 aarch64 [upgradable from: 3:1.18.1]
libcurl/stable 7.83.1 aarch64 [upgradable from: 7.83.0-1]
Android version:
11
Kernel build information:
Linux localhost 4.14.186+ #1 SMP PREEMPT Tue Apr 5 22:31:47 CST 2022 aarch64 Android
Device manufacturer:
realme
Device model:
RMX2151

[stale[bot]]

This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nohajc]

If anyone is following this issue, I have a solution which lets you use the unmodified adb from android-tools with a special launcher: https://github.com/nohajc/termux-adb

[Rudxain]

( Continuation of https://github.com/termux/termux-app/issues/2890#issuecomment-1537693516 )

I've just tested SM-A315G connected via OTG to SM-J327VPP. The regular OTG connection was successful (as usual), but the ADB server running on J3 didn't even detect A31 as an "unauthorized device", nor the A31 detected the server.

The other device I tested previously ("reverse" OTG), was an SM-G532M connected to A31, using the same cables, with same connections