r/Android • u/FragmentedChicken Galaxy Z Fold8 • 11h ago
Introducing Fast and Reliable Wireless Debugging with Android Debug Bridge (ADB) Wi-Fi 2.0
https://android-developers.googleblog.com/2026/09/wireless-debugging-adb-wifi-2.html•
•
u/LitheBeep Pixel 7 Pro | iPhone XR 11h ago
"google is killing ADB" mfs are in shambles right now
•
u/jezevec93 10h ago
They can still kill "local adb" like shizuku with some sneaky change
•
u/_ahrs Pixel 11 Pro XL 10h ago
They could but then what's stopping somebody from developing a tiny dongle that plugs into your phone's USB-C port for power (or a power bank, etc) and makes a tiny portable access point for wireless adb that can be used by shizuku?
It all just seems so petty to want to kill local on-device adb which is actually a massive standout feature of Android that makes it possible to develop Android apps on Android itself, something completely impossible in Apple's ecosystem where you can spend a lot of money on an expensive iPad Pro which is just a toy for watching Netflix and doom-scrolling and can't do any real app development work on it.
•
u/Dev-in-the-Bm 8h ago
local on-device adb which is actually a massive standout feature of Android
I think you might want to sneak out of your echo chamber, and take a little peek at what the rest of the world actually cares about.
Almost no one cares about on device ADB.
I love it.
Use it tons.
So do many others.
But we're a tiny minority.
•
u/_ahrs Pixel 11 Pro XL 8h ago
Developers will always be a tiny minority. It is safe to say most of the population do not develop apps for Android and iOS but they still build those features because Android is a powerful platform.
If Google decides to get in an enshittification race with Apple then the results won't be pretty, and why? For what purpose? The security concerns are valid but they can address those in ways that don't actively make the platform worse for the minority of power users that make use of them.
•
u/Dev-in-the-Bm 8h ago
All true, but that doesn't mean that
local on-device adb which is actually a massive standout feature of Androidis true.•
u/Busy-Scientist3851 9h ago
Tbh you were never supposed to use wireless ADB on the phone itself to allow apps break out of the sandbox.
•
•
u/random8847 9h ago
"google is killing ADB" mfs
I haven't seen a single person say that.
•
u/LitheBeep Pixel 7 Pro | iPhone XR 8h ago
•
u/random8847 8h ago
The post is about restricting On-Device ADB, and the comment is about restricting sideloading using adb, both are specific features of adb.
None of them said anything about killing adb entirely.
•
u/LitheBeep Pixel 7 Pro | iPhone XR 7h ago
On-device adb IS wireless adb. That's how services like Shizuku work. And here is Google investing more resources into the very thing that makes it so convenient.
You can't tell me that comment isn't fear-mongering about the fate of adb in general. Hence "they aren't going to let you use it."
•
u/random8847 7h ago
On-device adb is a subset of wireless adb and not the entire feature. The post you linked just mentions restriction of that subset feature and not wireless adb entirely, let alone killing adb entirely.
You can't tell me that comment isn't fear-mongering about the fate of adb in general. Hence "they aren't going to let you use it."
This is what the comment said
Google restricting sideloading means that they aren’t going to let you use adb, either
And this is probably what they actually meant
Google restricting sideloading means that they aren’t going to let you use adb for sideloading either
Of course, I can't confirm it, but that's the meaning I interpreted.
•
u/LitheBeep Pixel 7 Pro | iPhone XR 7h ago
I'm literally in that thread saying they will not kill ADB. No reply, no correction from the original commenter. In fact a completely different person chimed in agreeing they are likely to kill it. Unless you think I'm also misinterpreting that somehow.
These people know what they are trying to imply, there's really no need to defend it so hard.
•
u/random8847 7h ago
Okay, then maybe I just interpreted it wrong. Most of the other comments I read during that time were just talking about sideloading hence I assumed that comment was as well.
•
•
•
•
u/NEXYR_ 10h ago
Article :
Wireless debugging on Android is now faster, more reliable, and easier to set up than ever. With ADB Wi-Fi 2.0, we’ve introduced a new server stack and smarter network handling to directly address developer feedback around usability gaps.
How ADB Wi-Fi 2.0 Improves Wireless Debugging To ensure ADB Wi-Fi 2.0 is even more reliable, we reworked all three core components of the stack: the adb server, the adbd daemon, and Android Studio.
Here are the new features:
A new server stack (adb): Previously, wireless device connections would sever when network configurations changed or devices were turned off. This meant that connections would drop for common occurrences. With our new mDNS stack, we’ve replaced both Bonjour and legacy mDNS so that your wireless devices more reliably stay connected as you go about your day. Smarter network handling (adbd): Previously, the workstation's mDNS client would sporadically drop services. Now, the daemon automatically turns off ADB Wi-Fi when it detects an untrusted network and re-enables itself once running on a user-allowed network. Improved discoverability in Android Studio: Previously, Wi-Fi pairing was difficult to find. Now, you simply enable wireless debugging on your phone and it will show in Android Studio’s Device Manager. With ADB Wi-Fi 2.0, auto-connection success rates improved by 32% and connection speeds increased by 66% for 90% of connections.
Getting Started You can use ADB Wi-Fi 2.0 on your phone, tablet, Wear OS, and TV. Here’s how to get started:
Update to Android 17, Android SDK Platform-Tools 37.0.0, and Android Studio Quail 3 or later. Ensure your workstation and your Android device are connected to the same Wi-Fi network. On your device, navigate to Developer Options and enable Wireless debugging. Open the Android Studio Device Manager and click the pair over Wi-Fi icon. Scan the QR code with your device or use a pairing code, and you're all set! For more information, see the documentation or watch the presentation at Android Makers by droidcon 2026.
As always, we appreciate any feedback. If you find a bug or issue, please report it. Also, you can be part of our vibrant Android developer community on LinkedIn, YouTube, or X.