[GH-ISSUE #94] Sometimes LADB goes back to pairing screen after wireless debugging shows a successful pair #73

New issue

Open

opened 2026-03-04 02:11:24 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 02:11:24 +03:00

Owner

Originally created by @ShadowFlare on GitHub (Jan 5, 2023).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/94

As described by title, sometimes when I try to do the pairing, the wireless debugging screen indicates a successful pairing (and even may indicate there's a debugging connection), but LADB goes back to pairing mode instead of showing the terminal output. I don't know of a specific way to reproduce it, just seems to happen at random.

I think it's been happening since the updated pairing screen was implemented in the app.

Originally created by @ShadowFlare on GitHub (Jan 5, 2023). Original GitHub issue: https://github.com/tytydraco/LADB/issues/94 As described by title, sometimes when I try to do the pairing, the wireless debugging screen indicates a successful pairing (and even may indicate there's a debugging connection), but LADB goes back to pairing mode instead of showing the terminal output. I don't know of a specific way to reproduce it, just seems to happen at random. I think it's been happening since the updated pairing screen was implemented in the app.

kerem commented

2026-03-04 02:11:25 +03:00

Author

Owner

@hirenshah commented on GitHub (Feb 8, 2023):

I'm having the same issue.

@hirenshah commented on GitHub (Feb 8, 2023): I'm having the same issue.

kerem commented

2026-03-04 02:11:25 +03:00

Author

Owner

@ElizabethWega commented on GitHub (Feb 28, 2023):

I'm facing the very same issue :/

@ElizabethWega commented on GitHub (Feb 28, 2023): I'm facing the very same issue :/

kerem commented

2026-03-04 02:11:25 +03:00

Author

Owner

@cyberfrog77 commented on GitHub (Jun 12, 2023):

same here

@cyberfrog77 commented on GitHub (Jun 12, 2023): same here

kerem commented

2026-03-04 02:11:25 +03:00

Author

Owner

@boognish-rising commented on GitHub (Oct 18, 2023):

So you mean it acts like you just launched the app and tries to connect accordingly, despite it already successfully connecting seconds prior? If so, I've experienced this a number of times and each time it turned out that something was wrong with the command syntax. Once corrected, the command ran successfully and / or returned the correct error message. Not sure why it doesn't do so the first time around instead of trying to reconnect or whatever, but if experiencing this particular issue, I'd say to take a close look at the entire command and ensure that all of your arguments are in the proper order, etc. It can also help to have a CLI open on PC or another device to see what the same command does issued on that device

@boognish-rising commented on GitHub (Oct 18, 2023): So you mean it acts like you just launched the app and tries to connect accordingly, despite it already successfully connecting seconds prior? If so, I've experienced this a number of times and each time it turned out that something was wrong with the command syntax. Once corrected, the command ran successfully and / or returned the correct error message. Not sure why it doesn't do so the first time around instead of trying to reconnect or whatever, but if experiencing this particular issue, I'd say to take a close look at the entire command and ensure that all of your arguments are in the proper order, etc. It can also help to have a CLI open on PC or another device to see what the same command does issued on that device