-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade adb to support Wireless debugging? #2
Comments
It was for android 11 |
Any progress with compiling adb 1.0.41 (api 30, Android 11) binaries for arm64? It can be a gamechanger: adb phone to phone without the need for a pc the first time and without otg cables... And even adb to itself would be possible, when pairing command is supported. |
Already possible to adb phone to phone via otg. Also adb to itself without need of another phone or pc via adb connect localhost Just one step needs the pc that is setting up adb in tcpip mode after that its all pc free. And if phone is rooted that step is also gone |
Adb to itself does not seem to work by me, Android 11 unrooted with termux and MasterX adb version: $ adb connect localhost $ adb shell In a terminal emulator without termux i get even less, access denied or not exist. And yes, i am aware of the other 2 possibilities -pc and otg cable, would be nice to get without them, pure wireless. |
Thanks to osm0sis and surge 1223 we now have a solution to that problem. |
Does it work for connection adb on same device without root if yes the what commands did you used? I tried But when i tried |
You are using the wrong binary (use the one from magisk) AND the wrong command :) If you had, you had known, the new command is adb pair localhost:12345 , then adb connect localhost:54321 What you are doing is ok for every android version, but with that method you still need usb cable to allow the connection once and to switch to tcp server. As i said...read the help and play everything once more on a pc first because right now you do not know what you are doing. |
Can i use same steps on android 9? And i don't have any pc so if you can help me to do this without a pc then i will be very greatful of you(i know my english is bad please bare with me). •‿• |
No. The new method is introduced in the middle of 2020 with some very late update of Android 10 and early beta of 11. On android 9 you follow the old guides like https://support.honeywellaidc.com/s/article/How-to-use-adb-over-TCPIP-connect p.s. I have seen some apps on google play https://play.google.com/store/apps/details?id=com.htetznaing.adbotg that use 2 phones and otg cable, have not tried personally. |
update latest platform tools |
on Android 11, turn on wireless debugging and look at the port generated (it'll be random everytime). Then in Termux, run: adb connect localhost:port (where port is the one you got from wireless debugging). This will pair Termux to wireless debugging. Once done, Termux should be able to run adb commands, such as "adb devices -l" to list the currently connected adb devices. All this is done without another device. You can also run "adb tcpip 5555" (after the above steps have been completed) and this will allow Tasker or MacroDroid to run more ADB elevated commands. The problem is trying to automate the first part. There's a Google Play app called LADB and once you've done the initial pairing of LADB with wireless debugging, then it'll survive phone reboot. This means that the next time you reboot your phone and run LADB (with wireless debugging turned on of course), LADB will automatically pair with wireless debugging. So it should also be possible for Termux to do the same. |
And a small addition: might be needed to go split screen, because android changes the pin every time the window is refreshed. |
As described here https://developer.android.com/preview/features#wireless-adb
The text was updated successfully, but these errors were encountered: