[GH-ISSUE #143] 15 Android won't connect. #106

Open
opened 2026-03-04 02:11:36 +03:00 by kerem · 9 comments
Owner

Originally created by @Vertuhai on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/143

I have connected many other similar programs without any problems.
LADB seems to get stuck in a loop when connecting and the connection doesn't work.
15 Android Hyper OS 2.0.2

Originally created by @Vertuhai on GitHub (Jan 28, 2026). Original GitHub issue: https://github.com/tytydraco/LADB/issues/143 I have connected many other similar programs without any problems. LADB seems to get stuck in a loop when connecting and the connection doesn't work. 15 Android Hyper OS 2.0.2
Author
Owner

@Golgrax commented on GitHub (Feb 1, 2026):

I have connected many other similar programs without any problems. LADB seems to get stuck in a loop when connecting and the connection doesn't work. 15 Android Hyper OS 2.0.2

can you please clarify it, maybe there's already a method for that issue

<!-- gh-comment-id:3830549876 --> @Golgrax commented on GitHub (Feb 1, 2026): > I have connected many other similar programs without any problems. LADB seems to get stuck in a loop when connecting and the connection doesn't work. 15 Android Hyper OS 2.0.2 can you please clarify it, maybe there's already a method for that issue
Author
Owner

@Vertuhai commented on GitHub (Feb 1, 2026):

I have connected many other similar programs without any problems. LADB seems to get stuck in a loop when connecting and the connection doesn't work. 15 Android Hyper OS 2.0.2

can you please clarify it, maybe there's already a method for that issue

The situation is like this ( Redmi 15C 4G - code name: dew ) does not have the ability to work with a split screen in order to connect as expected.
Perhaps that's why I get this error that I simply choose between two open windows in recently opened applications.
But why is the process looping and not just a window with a type error (it’s not possible to connect).
I would like the author to make the connection more convenient as it is implemented in Shizuku, aShellYou and many other programs use just this connection method, it simplifies connecting to the phone.
It would be incredibly interesting and convenient for everyone!

<!-- gh-comment-id:3831457188 --> @Vertuhai commented on GitHub (Feb 1, 2026): > > I have connected many other similar programs without any problems. LADB seems to get stuck in a loop when connecting and the connection doesn't work. 15 Android Hyper OS 2.0.2 > > can you please clarify it, maybe there's already a method for that issue The situation is like this ( Redmi 15C 4G - code name: dew ) does not have the ability to work with a split screen in order to connect as expected. Perhaps that's why I get this error that I simply choose between two open windows in recently opened applications. But why is the process looping and not just a window with a type error (it’s not possible to connect). I would like the author to make the connection more convenient as it is implemented in [Shizuku](https://github.com/RikkaApps/Shizuku), [aShellYou](https://github.com/DP-Hridayan/aShellYou) and many other programs use just this connection method, it simplifies connecting to the phone. It would be incredibly interesting and convenient for everyone!
Author
Owner

@Golgrax commented on GitHub (Feb 2, 2026):

I have connected many other similar programs without any problems. LADB seems to get stuck in a loop when connecting and the connection doesn't work. 15 Android Hyper OS 2.0.2

can you please clarify it, maybe there's already a method for that issue

The situation is like this ( Redmi 15C 4G - code name: dew ) does not have the ability to work with a split screen in order to connect as expected. Perhaps that's why I get this error that I simply choose between two open windows in recently opened applications. But why is the process looping and not just a window with a type error (it’s not possible to connect). I would like the author to make the connection more convenient as it is implemented in Shizuku, aShellYou and many other programs use just this connection method, it simplifies connecting to the phone. It would be incredibly interesting and convenient for everyone!

It looks like we are facing the same issue. I have forked the repository and implemented a fix using an alternative method. You can review it here:

https://github.com/tytydraco/LADB/pull/141 (Note: You can see the step by steps in here and the PR hasn't been merged yet.)
https://github.com/Golgrax/LADB/

Hope this helps.

<!-- gh-comment-id:3834584864 --> @Golgrax commented on GitHub (Feb 2, 2026): > > > I have connected many other similar programs without any problems. LADB seems to get stuck in a loop when connecting and the connection doesn't work. 15 Android Hyper OS 2.0.2 > > > > > > can you please clarify it, maybe there's already a method for that issue > > The situation is like this ( Redmi 15C 4G - code name: dew ) does not have the ability to work with a split screen in order to connect as expected. Perhaps that's why I get this error that I simply choose between two open windows in recently opened applications. But why is the process looping and not just a window with a type error (it’s not possible to connect). I would like the author to make the connection more convenient as it is implemented in [Shizuku](https://github.com/RikkaApps/Shizuku), [aShellYou](https://github.com/DP-Hridayan/aShellYou) and many other programs use just this connection method, it simplifies connecting to the phone. It would be incredibly interesting and convenient for everyone! It looks like we are facing the same issue. I have forked the repository and implemented a fix using an alternative method. You can review it here: https://github.com/tytydraco/LADB/pull/141 (Note: You can see the step by steps in here and the PR hasn't been merged yet.) https://github.com/Golgrax/LADB/ Hope this helps.
Author
Owner

@Vertuhai commented on GitHub (Feb 2, 2026):

It looks like we are facing the same issue. I have forked the repository and implemented a fix using an alternative method. You can review it here:

#141 (Note: You can see the step by steps in here and the PR hasn't been merged yet.) https://github.com/Golgrax/LADB/

Hope this helps.

Do you have (apk) an already fixed version?
Can you give it to me?

<!-- gh-comment-id:3834904612 --> @Vertuhai commented on GitHub (Feb 2, 2026): > It looks like we are facing the same issue. I have forked the repository and implemented a fix using an alternative method. You can review it here: > > [#141](https://github.com/tytydraco/LADB/pull/141) (Note: You can see the step by steps in here and the PR hasn't been merged yet.) https://github.com/Golgrax/LADB/ > > Hope this helps. Do you have (apk) an already fixed version? Can you give it to me?
Author
Owner

@Golgrax commented on GitHub (Feb 2, 2026):

I prefer not to distribute a pre-compiled APK directly. Since I am not the original author and this is a paid app on the Play Store, I want to avoid any potential licensing or ethical issues regarding distribution. Additionally, for security reasons, it is much safer for you to build system tools like this yourself rather than installing an APK provided by a stranger in a comment thread.

I noticed you have already forked my repository. You can simply clone your fork to your computer, and run the build. This will generate a signed APK with the fix included that you can install on your device safely.

<!-- gh-comment-id:3835071118 --> @Golgrax commented on GitHub (Feb 2, 2026): I prefer not to distribute a pre-compiled APK directly. Since I am not the original author and this is a paid app on the Play Store, I want to avoid any potential licensing or ethical issues regarding distribution. Additionally, for security reasons, it is much safer for you to build system tools like this yourself rather than installing an APK provided by a stranger in a comment thread. I noticed you have already forked my repository. You can simply clone your fork to your computer, and run the build. This will generate a signed APK with the fix included that you can install on your device safely.
Author
Owner

@Golgrax commented on GitHub (Feb 3, 2026):

Have you solved the issue?

<!-- gh-comment-id:3839548962 --> @Golgrax commented on GitHub (Feb 3, 2026): Have you solved the issue?
Author
Owner

@Vertuhai commented on GitHub (Feb 3, 2026):

Have you solved the issue?

I'm not some kind of programmer)).
I don't do anything other than translate.
Building a program from source code is something complicated for me; to put it simply, I don’t understand anything about it.

<!-- gh-comment-id:3840129470 --> @Vertuhai commented on GitHub (Feb 3, 2026): > Have you solved the issue? I'm not some kind of programmer)). I don't do anything other than translate. Building a program from source code is something complicated for me; to put it simply, I don’t understand anything about it.
Author
Owner

@Golgrax commented on GitHub (Feb 9, 2026):

I'll catch you up once I release my app alternative to public, you do also can contact me in my Discord: Golgrax

<!-- gh-comment-id:3871846311 --> @Golgrax commented on GitHub (Feb 9, 2026): I'll catch you up once I release my app alternative to public, you do also can contact me in my Discord: Golgrax
Author
Owner

@Vertuhai commented on GitHub (Feb 10, 2026):

I'll catch you up once I release my app alternative to public, you do also can contact me in my Discord: Golgrax

I submitted a friend request on discord.

<!-- gh-comment-id:3877743935 --> @Vertuhai commented on GitHub (Feb 10, 2026): > I'll catch you up once I release my app alternative to public, you do also can contact me in my Discord: Golgrax I submitted a friend request on discord.
Sign in to join this conversation.
No milestone
No project
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#106
No description provided.