LADB
LADB copied to clipboard
tytydraco
Frozen after pairing
After I've setup wireless adb with the pairing code, I get stuck waiting, with the following as the only log on my screen: "Enter pairing code: Successfully paired to localhost:34295 [guid=adb-RFCNC0G771B-Ju0YNA]"
I am unable to enter any text into the field at the bottom. I've also waited around 5-10 minutes to make certain it wasn't just lagging. This is a bug that has persisted for me since I updated to Android 12 almost a month ago.
Device: Samsung S21+ OneUI Version: 4.0 Application Version: 1.7.5
I've tried to solve this issue so many times, I truly am stumped. The workaround is to close the app completely and open it again.
Update: Unsure whether it was due to a Samsung update or app update, but it works most of the time now! If I have any issues, restarting the app or re-enabling ADB tends to fix things now! Thanks for all you do!
[I'll leave it to you to close this issue in case this issue isn't resolved for others, or you simply want to take one last look at things ;P]
Awesome! I just got a new Samsung S21 FE and it also worked perfectly. I'll leave this open in case a software update wasn't the actual fix.
100% working
- Go to LADB help, click on Reboot and close the app
- disable usb debugging and wireless option
- First enable wireless debugging then enable usb debugging (order is important)
- Open LADB app and then go to wireless debugging and pair the code.
Samsung S21 Ultra here - same problem. I can pair successfully, then freeze and lose any ability to type. Or if I follow Kashi's instructions something flashes by before leaving just the command window, but the app refuses to accept any commands (so I assume the pairing fails)
Just to add more context, I've also uninstalled/reinstalled, cleared the data/cache every time, disabled/enabled wireless & USB debugging and various network connections.
I apologize for how frustrating this is. I'm hoping for a better way to make this work soon. I think Android 12 kick-started the issues.
Still works pretty well for me. Not sure what you've done between v1.7.5 and v1.9.1 but things seem to be a lot more smooth and seamless.
I'm on a new device and everything works great. I use the quick settings shortcut now and don't even need to enable wireless debugging on my own, which I really like. Developer Options are always an agitating amount of effort to sift through.
There is the occasional app hangup where I'll have to restart the instance from the app switcher, but I don't seem to need to force stop the entire application anymore. It takes 10-20 seconds to launch into the shell most of the time. My computer's been stuck on the Insider green screen for about a week now so ladb has been incredibly useful. Keep up the good work man, we love and appreciate it.
Device: Samsung S22 Ultra OneUI Version: 4.1 Application Version: 1.9.1
For what it's worth, I managed to get it working. I blew out everything and installed an older version then updated it. This worked. I have no idea why.
100% working
- Go to LADB help, click on Reboot and close the app
- disable usb debugging and wireless option
- First enable wireless debugging then enable usb debugging (order is important)
- Open LADB app and then go to wireless debugging and pair the code.
NOTE: Dropped into ADB shell automatically Success! ※(^o^)/※
Shell is dead, resetting Enabling wireless debugging Waiting a few moments... Starting ADB client Waiting for device respond (max 5m)
Please help
Same here with your latest code. After pairing, the start-server keeps frozen the process.
Following @Kashifrazabb does to connect "sometimes" but not always:
- Go to LADB help, click on Reboot and close the app
- disable usb debugging and wireless option
- First enable wireless debugging then enable usb debugging (order is important)
- Open LADB app and then go to wireless debugging and pair the code.
Device: Samsung Galaxy S20 Ultra with Android 12 with the lastest security patches.
