starred/LADB

Fork 0

mirror of https://github.com/tytydraco/LADB.git synced 2026-04-27 00:15:59 +03:00

[GH-ISSUE #120] Stopped working after latest update #93

New issue

Open

opened 2026-03-04 02:11:30 +03:00 by kerem · 7 comments

kerem commented

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

Owner

Originally created by @akpapathanasiou on GitHub (Jun 24, 2024).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/120

Hello :) Since the latest LADB update (June 20, v2,4), the app no longer connects to localhost.

I have tried several possible fixes, unpaired & tried to re-pair, rebooted a lot, nothing seems to work.

Any help in how to further troubleshoot this would be awsome :) Thank you!

Edit: tried with v2.3.1 and it immediately connected. So I guess it has something to do with the update and my device.

In case further details are needed, I'm using a Pixel 7 Pro, Android 14 (fully stock & updated to June security update) and Shizuku (which also works great with the previous version of LADB).

Originally created by @akpapathanasiou on GitHub (Jun 24, 2024). Original GitHub issue: https://github.com/tytydraco/LADB/issues/120 Hello :) Since the latest LADB update (June 20, v2,4), the app no longer connects to localhost. I have tried several possible fixes, unpaired & tried to re-pair, rebooted a lot, nothing seems to work. Any help in how to further troubleshoot this would be awsome :) Thank you! Edit: tried with v2.3.1 and it immediately connected. So I guess it has something to do with the update and my device. In case further details are needed, I'm using a Pixel 7 Pro, Android 14 (fully stock & updated to June security update) and Shizuku (which also works great with the previous version of LADB).

kerem commented

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

Author

Owner

@darrylyong commented on GitHub (Jun 25, 2024):

Can also confirm that upgrading to v2.4 broke LADB when it was working beautifully before. Also can confirm that uninstalling/reinstalling, unpairing/repairing doesn't seem to work. I am currently using a Pixel 8 Pro, Android 15 Beta 3.

@darrylyong commented on GitHub (Jun 25, 2024): Can also confirm that upgrading to v2.4 broke LADB when it was working beautifully before. Also can confirm that uninstalling/reinstalling, unpairing/repairing doesn't seem to work. I am currently using a Pixel 8 Pro, Android 15 Beta 3.

kerem commented

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

Author

Owner

@akpapathanasiou commented on GitHub (Jun 27, 2024):

Hello again,

Sadly the same happens with yesterday's update (26/7, v2,4,1)

When trying to pair, no matter what I try, I get the "Your device didn't connect to LADB etc" error.

Reverted to v2.3.1 and tried, immediate connection.

Sadly I have no knowledge on how to help the dev troubleshoot this, and I'm not rooted to provide a logcat

@akpapathanasiou commented on GitHub (Jun 27, 2024): Hello again, Sadly the same happens with yesterday's update (26/7, v2,4,1) When trying to pair, no matter what I try, I get the "Your device didn't connect to LADB etc" error. Reverted to v2.3.1 and tried, immediate connection. Sadly I have no knowledge on how to help the dev troubleshoot this, and I'm not rooted to provide a logcat

kerem commented

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

Author

Owner

@kssxs commented on GitHub (Jun 28, 2024):

I've had the same issues as reported for 2.4.1 on a Samsung S24 with the latest version of Android 14. I just had a system update today as well, so this is as latest as it gets for me.

I uninstalled 2.4.1, and re-installed 2.3.1, and it worked perfectly again. So it seems to be some kind of issue with 2.4.1 for sure.

I think I'll stay on this version until the issue is fixed.

@kssxs commented on GitHub (Jun 28, 2024): I've had the same issues as reported for 2.4.1 on a Samsung S24 with the latest version of Android 14. I just had a system update today as well, so this is as latest as it gets for me. I uninstalled 2.4.1, and re-installed 2.3.1, and it worked perfectly again. So it seems to be some kind of issue with 2.4.1 for sure. I think I'll stay on this version until the issue is fixed.

kerem commented

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

Author

Owner

@clubtech commented on GitHub (Jun 28, 2024):

Same here. Stopped working / connecting after the last update. Deleted app data and tried to repair. It pairs fine but never actually connects.

@clubtech commented on GitHub (Jun 28, 2024): Same here. Stopped working / connecting after the last update. Deleted app data and tried to repair. It pairs fine but never actually connects.

kerem commented

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

Author

Owner

@akpapathanasiou commented on GitHub (Jul 2, 2024):

So, I discovered something very interesting, with the latest Play Store version (2.4.1).

After a reboot, LADB still doesn't connect. HOWEVER, once I connect it to a PC and run adb tcpip 5555 for Tasker, after I disconnect the phone LADB then instantly connects so I can input the startup command for Shizuku...

(I can't do both through the PC cause shizuku will not work for some reason, I need to use adb -s emulator-5554 shell etc for Shizuku on LADB after the Tasker command for both to work)

Weird, but might give an insight on the reason behind this bug :)

@akpapathanasiou commented on GitHub (Jul 2, 2024): So, I discovered something very interesting, with the latest Play Store version (2.4.1). After a reboot, LADB still doesn't connect. HOWEVER, once I connect it to a PC and run adb tcpip 5555 for Tasker, after I disconnect the phone LADB then instantly connects so I can input the startup command for Shizuku... (I can't do both through the PC cause shizuku will not work for some reason, I need to use adb -s emulator-5554 shell etc for Shizuku on LADB after the Tasker command for both to work) Weird, but might give an insight on the reason behind this bug :)

kerem commented

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

Author

Owner

@tytydraco commented on GitHub (Jul 7, 2024):

Hey guys thank you for creating this Github issue. I'm not sure what change is breaking things, but even reverting the codebase back to v3.2.1 whilst still upgrading the Android SDKs seems to still be causing problems so I'm just going to fully revert everything back to v3.2.1 and praying that this solves the issue. In the future I will be doing an open beta in the Play Store before doing any major releases! Very sorry for all this, thanks for commenting in this thread <3

@tytydraco commented on GitHub (Jul 7, 2024): Hey guys thank you for creating this Github issue. I'm not sure what change is breaking things, but even reverting the codebase back to v3.2.1 whilst still upgrading the Android SDKs seems to still be causing problems so I'm just going to fully revert everything back to v3.2.1 and praying that this solves the issue. In the future I will be doing an open beta in the Play Store before doing any major releases! Very sorry for all this, thanks for commenting in this thread <3

kerem commented

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

Author

Owner

@kssxs commented on GitHub (Jul 16, 2024):

Can someone explain the version number differences?

I currently have 2.3.1 installed on my phone, which is working but is not 'current' because I went back from 2.4.1, but @tytydraco is mentioning 3.2.1 as the latest.

Which app version is considered current from the Play Store? Was there a significant developmental jump from 2.x.x to 3.x.x? Or is this all just a typo somewhere...

Thanks...

@kssxs commented on GitHub (Jul 16, 2024): Can someone explain the version number differences? I currently have 2.3.1 installed on my phone, which is working but is not 'current' because I went back from 2.4.1, but @tytydraco is mentioning 3.2.1 as the latest. Which app version is considered current from the Play Store? Was there a significant developmental jump from 2.x.x to 3.x.x? Or is this all just a typo somewhere... Thanks...