starred/LADB
1
0
Fork 0
mirror of https://github.com/tytydraco/LADB.git synced 2026-04-27 00:15:59 +03:00
Code Issues 51 Projects Releases Packages Wiki Activity

[GH-ISSUE #55] Frozen after pairing #42

New issue
Open
opened 2026-03-04 02:11:03 +03:00 by kerem · 13 comments
kerem commented 2026-03-04 02:11:03 +03:00
Owner
Copy link

Originally created by @thejaustin on GitHub (Jan 6, 2022).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/55

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

Originally created by @thejaustin on GitHub (Jan 6, 2022). Original GitHub issue: https://github.com/tytydraco/LADB/issues/55 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_
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@mrerror-25 commented on GitHub (Jan 12, 2022):

me too
My phone : samsung a01

<!-- gh-comment-id:1010543494 --> @mrerror-25 commented on GitHub (Jan 12, 2022): me too My phone : samsung a01
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@tytydraco commented on GitHub (Jan 14, 2022):

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.

<!-- gh-comment-id:1013347359 --> @tytydraco commented on GitHub (Jan 14, 2022): 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.
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@thejaustin commented on GitHub (Feb 17, 2022):

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]

<!-- gh-comment-id:1042602009 --> @thejaustin commented on GitHub (Feb 17, 2022): 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]
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@tytydraco commented on GitHub (Feb 17, 2022):

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.

<!-- gh-comment-id:1042605745 --> @tytydraco commented on GitHub (Feb 17, 2022): 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.
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@Kashifrazabb commented on GitHub (Apr 12, 2022):

100% working

  1. Go to LADB help, click on Reboot and close the app
  2. disable usb debugging and wireless option
  3. First enable wireless debugging then enable usb debugging (order is important)
  4. Open LADB app and then go to wireless debugging and pair the code.
<!-- gh-comment-id:1097169890 --> @Kashifrazabb commented on GitHub (Apr 12, 2022): 100% working 1) Go to LADB help, click on Reboot and close the app 2) disable usb debugging and wireless option 3) First enable wireless debugging then enable usb debugging (order is important) 4) Open LADB app and then go to wireless debugging and pair the code.
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@Symber13 commented on GitHub (Apr 17, 2022):

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.

<!-- gh-comment-id:1100941443 --> @Symber13 commented on GitHub (Apr 17, 2022): 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.
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@tytydraco commented on GitHub (Apr 18, 2022):

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.

<!-- gh-comment-id:1101028027 --> @tytydraco commented on GitHub (Apr 18, 2022): 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.
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@thejaustin commented on GitHub (Apr 20, 2022):

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

<!-- gh-comment-id:1104179774 --> @thejaustin commented on GitHub (Apr 20, 2022): 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_
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@Symber13 commented on GitHub (Apr 20, 2022):

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.

<!-- gh-comment-id:1104252306 --> @Symber13 commented on GitHub (Apr 20, 2022): 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.
kerem commented 2026-03-04 02:11:04 +03:00
Author
Owner
Copy link

@nicolai1905 commented on GitHub (May 16, 2022):

100% working

  1. Go to LADB help, click on Reboot and close the app
  2. disable usb debugging and wireless option
  3. First enable wireless debugging then enable usb debugging (order is important)
  4. 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

<!-- gh-comment-id:1127416566 --> @nicolai1905 commented on GitHub (May 16, 2022): > 100% working > > 1. Go to LADB help, click on Reboot and close the app > 2. disable usb debugging and wireless option > 3. First enable wireless debugging then enable usb debugging (order is important) > 4. 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
kerem commented 2026-03-04 02:11:05 +03:00
Author
Owner
Copy link

@tytydraco commented on GitHub (Oct 15, 2022):

I believe this issue is (mostly) resolved, if not, please reopen.

<!-- gh-comment-id:1279827115 --> @tytydraco commented on GitHub (Oct 15, 2022): I believe this issue is (mostly) resolved, if not, please reopen.
kerem commented 2026-03-04 02:11:05 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Oct 27, 2022):

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.

<!-- gh-comment-id:1293100928 --> @victorjaviermartin commented on GitHub (Oct 27, 2022): 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.
kerem commented 2026-03-04 02:11:05 +03:00
Author
Owner
Copy link

@tytydraco commented on GitHub (Oct 27, 2022):

I'll take another look then.

<!-- gh-comment-id:1293815269 --> @tytydraco commented on GitHub (Oct 27, 2022): I'll take another look then.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
target-sdk-35
revert-update
No results found.
Labels
Clear labels   
bug

   
documentation

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
question
No labels
bug
documentation
enhancement
enhancement
good first issue
help wanted
pull-request
question
question
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LADB#42
No description provided.