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 #90] not working on Samsung running OS12 #72

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

Originally created by @ToysoftInc on GitHub (Oct 26, 2022).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/90

I compiled the latest and installed on my S10 running OS12.
Paired and waiting over 2 minutes

libadb.so: no device with transport id '1'

Originally created by @ToysoftInc on GitHub (Oct 26, 2022). Original GitHub issue: https://github.com/tytydraco/LADB/issues/90 I compiled the latest and installed on my S10 running OS12. Paired and waiting over 2 minutes libadb.so: no device with transport id '1'
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

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

Me too.

Device: Samsung Galaxy S20 Ultra with Android 12

<!-- gh-comment-id:1293101743 --> @victorjaviermartin commented on GitHub (Oct 27, 2022): Me too. Device: Samsung Galaxy S20 Ultra with Android 12
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@lautit commented on GitHub (Nov 15, 2022):

Can confirm this is also happening on a Samsuns S20 FE 5G (SM-G781B/DS), Android 12 with Oct22 Patch

<!-- gh-comment-id:1315253856 --> @lautit commented on GitHub (Nov 15, 2022): Can confirm this is also happening on a Samsuns S20 FE 5G (SM-G781B/DS), Android 12 with Oct22 Patch
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@qinlili23333 commented on GitHub (Nov 15, 2022):

verified on s21 ultra, stuck at connection

<!-- gh-comment-id:1315263629 --> @qinlili23333 commented on GitHub (Nov 15, 2022): verified on s21 ultra, stuck at connection
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Nov 17, 2022):

@tytydraco when I've done pair and later connect, currently is not connected. This is my ADB log, inside device. If I've paired the device, close and kill the app and rerun again, it connects and let me run commands.

--- adb starting (pid 5822) ---
adb I 11-17 10:23:38 5822 5822 main.cpp:63] Android Debug Bridge version 1.0.41
adb I 11-17 10:23:38 5822 5822 main.cpp:63] Version 33.0.3-vanzdobz@gmail.com
adb I 11-17 10:23:38 5822 5822 main.cpp:63] Installed as /data/app/~~2fsz5NMRY6J0bfWN-CNxLA==/es.sia.siaadb.app-x6JuA4h8IK3zyPzirH5wVA==/lib/arm64/libadb.so
adb I 11-17 10:23:38 5822 5822 main.cpp:63]
adb I 11-17 10:23:38 5822 5822 auth.cpp:417] adb_auth_init...
adb I 11-17 10:23:38 5822 5822 auth.cpp:220] User key '/data/user/0/es.sia.siaadb.app/files/.android/adbkey' does not exist...
adb I 11-17 10:23:38 5822 5822 auth.cpp:64] generate_key(/data/user/0/es.sia.siaadb.app/files/.android/adbkey)...
adb I 11-17 10:23:38 5822 5822 auth.cpp:152] loaded new key from '/data/user/0/es.sia.siaadb.app/files/.android/adbkey' with fingerprint 48D3AEEEE5207C9FDC524DA028894839AED370BBC0AF174E41F504C00D3A3E4D
adb I 11-17 10:23:38 5822 5822 auth.cpp:392] adb_auth_inotify_init...
adb I 11-17 10:23:38 5822 5822 adb_wifi.cpp:105] Known hosts file [/data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb] does not exist...
adb I 11-17 10:23:38 5822 5822 mdnsresponder_client.cpp:141] service_name=adb-R5CN315AH2B-qJ5bln not in keystore
adb I 11-17 10:23:38 5822 5822 adb_wifi.cpp:105] Known hosts file [/data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb] does not exist...
adb I 11-17 10:23:38 5822 5822 mdnsresponder_client.cpp:141] service_name=adb-R5CN315AH2B-qJ5bln (2) not in keystore
adb I 11-17 10:23:38 5822 5831 tls_connection.cpp:87] [client]: Initializing adbwifi TlsConnection
adb I 11-17 10:23:38 5822 5831 tls_connection.cpp:213] [client]: Starting adbwifi tls handshake
adb I 11-17 10:23:38 5822 5831 tls_connection.cpp:300] [client]: Handshake succeeded.
adb I 11-17 10:23:38 5822 5830 adb_wifi.cpp:105] Known hosts file [/data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb] does not exist...
adb I 11-17 10:23:38 5822 5830 adb_wifi.cpp:80] Failed to rename /data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb: No such file or directory
adb W 11-17 10:23:38 5822 5830 network.cpp:149] failed to connect to '192.168.1.121:38455': Connection refused
adb I 11-17 10:23:45 5822 5822 mdnsresponder_client.cpp:141] service_name=adb-R5CN315AH2B-qJ5bln (2) not in keystore
adb I 11-17 10:23:45 5822 5844 transport.cpp:335] localhost:39287: read thread spawning
adb I 11-17 10:23:45 5822 5845 transport.cpp:307] localhost:39287: write thread spawning
adb I 11-17 10:23:45 5822 5844 transport.cpp:354] localhost:39287: Received STLS packet. Stopping read thread.
adb I 11-17 10:23:45 5822 5848 auth.cpp:491] t->auth_key not set before handshake
adb I 11-17 10:23:45 5822 5848 transport.cpp:1706] fetching keys for transport localhost:39287
adb I 11-17 10:23:45 5822 5848 auth.cpp:496] Attempting to TLS handshake
adb I 11-17 10:23:45 5822 5848 tls_connection.cpp:87] [client]: Initializing adbwifi TlsConnection
adb I 11-17 10:23:45 5822 5848 tls_connection.cpp:213] [client]: Starting adbwifi tls handshake
adb I 11-17 10:23:45 5822 5848 auth.cpp:514] adb_tls_set_certificate
adb I 11-17 10:23:45 5822 5848 auth.cpp:534] Checking for fingerprint match [48D3AEEEE5207C9FDC524DA028894839AED370BBC0AF174E41F504C00D3A3E4D]
adb I 11-17 10:23:45 5822 5848 auth.cpp:543] Got SHA256 match on a key
adb I 11-17 10:23:45 5822 5848 tls_connection.cpp:300] [client]: Handshake succeeded.
adb I 11-17 10:23:45 5822 5848 auth.cpp:499] Handshake succeeded. Waiting for CNXN packet...
adb I 11-17 10:23:45 5822 5851 transport.cpp:335] localhost:39287: read thread spawning
adb I 11-17 10:23:45 5822 5822 adb.cpp:172] localhost:39287: already offline

<!-- gh-comment-id:1318358122 --> @victorjaviermartin commented on GitHub (Nov 17, 2022): @tytydraco when I've done pair and later connect, currently is not connected. This is my ADB log, inside device. If I've paired the device, close and kill the app and rerun again, it connects and let me run commands. > --- adb starting (pid 5822) --- adb I 11-17 10:23:38 5822 5822 main.cpp:63] Android Debug Bridge version 1.0.41 adb I 11-17 10:23:38 5822 5822 main.cpp:63] Version 33.0.3-vanzdobz@gmail.com adb I 11-17 10:23:38 5822 5822 main.cpp:63] Installed as /data/app/~~2fsz5NMRY6J0bfWN-CNxLA==/es.sia.siaadb.app-x6JuA4h8IK3zyPzirH5wVA==/lib/arm64/libadb.so adb I 11-17 10:23:38 5822 5822 main.cpp:63] adb I 11-17 10:23:38 5822 5822 auth.cpp:417] adb_auth_init... adb I 11-17 10:23:38 5822 5822 auth.cpp:220] User key '/data/user/0/es.sia.siaadb.app/files/.android/adbkey' does not exist... adb I 11-17 10:23:38 5822 5822 auth.cpp:64] generate_key(/data/user/0/es.sia.siaadb.app/files/.android/adbkey)... adb I 11-17 10:23:38 5822 5822 auth.cpp:152] loaded new key from '/data/user/0/es.sia.siaadb.app/files/.android/adbkey' with fingerprint 48D3AEEEE5207C9FDC524DA028894839AED370BBC0AF174E41F504C00D3A3E4D adb I 11-17 10:23:38 5822 5822 auth.cpp:392] adb_auth_inotify_init... adb I 11-17 10:23:38 5822 5822 adb_wifi.cpp:105] Known hosts file [/data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb] does not exist... adb I 11-17 10:23:38 5822 5822 mdnsresponder_client.cpp:141] service_name=adb-R5CN315AH2B-qJ5bln not in keystore adb I 11-17 10:23:38 5822 5822 adb_wifi.cpp:105] Known hosts file [/data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb] does not exist... adb I 11-17 10:23:38 5822 5822 mdnsresponder_client.cpp:141] service_name=adb-R5CN315AH2B-qJ5bln (2) not in keystore adb I 11-17 10:23:38 5822 5831 tls_connection.cpp:87] [client]: Initializing adbwifi TlsConnection adb I 11-17 10:23:38 5822 5831 tls_connection.cpp:213] [client]: Starting adbwifi tls handshake adb I 11-17 10:23:38 5822 5831 tls_connection.cpp:300] [client]: Handshake succeeded. adb I 11-17 10:23:38 5822 5830 adb_wifi.cpp:105] Known hosts file [/data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb] does not exist... adb I 11-17 10:23:38 5822 5830 adb_wifi.cpp:80] Failed to rename /data/user/0/es.sia.siaadb.app/files/.android/adb_known_hosts.pb: No such file or directory adb W 11-17 10:23:38 5822 5830 network.cpp:149] failed to connect to '192.168.1.121:38455': Connection refused adb I 11-17 10:23:45 5822 5822 mdnsresponder_client.cpp:141] service_name=adb-R5CN315AH2B-qJ5bln (2) not in keystore adb I 11-17 10:23:45 5822 5844 transport.cpp:335] localhost:39287: read thread spawning adb I 11-17 10:23:45 5822 5845 transport.cpp:307] localhost:39287: write thread spawning adb I 11-17 10:23:45 5822 5844 transport.cpp:354] localhost:39287: Received STLS packet. Stopping read thread. adb I 11-17 10:23:45 5822 5848 auth.cpp:491] t->auth_key not set before handshake adb I 11-17 10:23:45 5822 5848 transport.cpp:1706] fetching keys for transport localhost:39287 adb I 11-17 10:23:45 5822 5848 auth.cpp:496] Attempting to TLS handshake adb I 11-17 10:23:45 5822 5848 tls_connection.cpp:87] [client]: Initializing adbwifi TlsConnection adb I 11-17 10:23:45 5822 5848 tls_connection.cpp:213] [client]: Starting adbwifi tls handshake adb I 11-17 10:23:45 5822 5848 auth.cpp:514] adb_tls_set_certificate adb I 11-17 10:23:45 5822 5848 auth.cpp:534] Checking for fingerprint match [48D3AEEEE5207C9FDC524DA028894839AED370BBC0AF174E41F504C00D3A3E4D] adb I 11-17 10:23:45 5822 5848 auth.cpp:543] Got SHA256 match on a key adb I 11-17 10:23:45 5822 5848 tls_connection.cpp:300] [client]: Handshake succeeded. adb I 11-17 10:23:45 5822 5848 auth.cpp:499] Handshake succeeded. Waiting for CNXN packet... adb I 11-17 10:23:45 5822 5851 transport.cpp:335] localhost:39287: read thread spawning adb I 11-17 10:23:45 5822 5822 adb.cpp:172] localhost:39287: already offline
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

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

@victorjaviermartin Thank you for bringing this issue to my attention. So it seems that killing the server and starting it again may broadcast to the newly paired device! Let me push an update that does that after the pair. Or, I can try pushing it to a beta branch on the Play Store.

<!-- gh-comment-id:1318899893 --> @tytydraco commented on GitHub (Nov 17, 2022): @victorjaviermartin Thank you for bringing this issue to my attention. So it seems that killing the server and starting it again may broadcast to the newly paired device! Let me push an update that does that after the pair. Or, I can try pushing it to a beta branch on the Play Store.
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

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

Also, is this reproducible? As in if you undo everything and try the same thing with the fix of restarting the app, does it work? Because that would be a major breakthrough.

<!-- gh-comment-id:1318900646 --> @tytydraco commented on GitHub (Nov 17, 2022): Also, is this reproducible? As in if you undo everything and try the same thing with the fix of restarting the app, does it work? Because that would be a major breakthrough.
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@sharpordie commented on GitHub (Nov 19, 2022):

Does it even work with the official desktop adb?

<!-- gh-comment-id:1320984081 --> @sharpordie commented on GitHub (Nov 19, 2022): Does it even work with the official desktop adb?
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@lautit commented on GitHub (Nov 21, 2022):

I'll try debugging with your suggestions @tytydraco and @sharpordie, sorry for the delay.

<!-- gh-comment-id:1322000937 --> @lautit commented on GitHub (Nov 21, 2022): I'll try debugging with your suggestions @tytydraco and @sharpordie, sorry for the delay.
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Nov 22, 2022):

adb start-server goes freezing, the only commnand that I can run to wake up adb was adb connect localhost:ADBport

<!-- gh-comment-id:1323808452 --> @victorjaviermartin commented on GitHub (Nov 22, 2022): adb start-server goes freezing, the only commnand that I can run to wake up adb was adb connect localhost:ADBport
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Nov 23, 2022):

I think that the pair process is not done correctly. Unfortunately, my samsung s20 ultra has updated this night to android 13, and now I don't have permission to explore Device File Explorer of Android Studio.

It's frustrating. Thank you @tytydraco

<!-- gh-comment-id:1325091514 --> @victorjaviermartin commented on GitHub (Nov 23, 2022): I think that the pair process is not done correctly. Unfortunately, my samsung s20 ultra has updated this night to android 13, and now I don't have permission to explore Device File Explorer of Android Studio. It's frustrating. Thank you @tytydraco
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@sharpordie commented on GitHub (Nov 23, 2022):

Could those who have a problem try using the .so files (all of them) from adb_tool and test if the pair command is working with their devices? I find it strange that it needs several .so files for arm64-v8a but not for armeabi-v7a.

<!-- gh-comment-id:1325335557 --> @sharpordie commented on GitHub (Nov 23, 2022): Could those who have a problem try using the .so files (all of them) from [adb_tool](https://github.com/nightmare-space/adb_tool/tree/main/android/app/src/main/jniLibs/arm64-v8a) and test if the pair command is working with their devices? I find it strange that it needs several .so files for arm64-v8a but not for armeabi-v7a.
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Nov 24, 2022):

I will try it and say something.

<!-- gh-comment-id:1326040541 --> @victorjaviermartin commented on GitHub (Nov 24, 2022): I will try it and say something.
kerem commented 2026-03-04 02:11:22 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Nov 24, 2022):

Same result @sharpordie @tytydraco

I've noticed that if I do a pair process, and a connect (when it connects). The send of commands gives me timeouts.

But! If I do a complete restart of the app, I achieve the connection and the send of commands fast.

I don't know why is this happening.

  1. PAIR+CONNECT = FAILURE
  2. PAIR+CONNECT+RESTART APP = OK
<!-- gh-comment-id:1326254594 --> @victorjaviermartin commented on GitHub (Nov 24, 2022): Same result @sharpordie @tytydraco I've noticed that if I do a pair process, and a connect (when it connects). The send of commands gives me timeouts. But! If I do a complete restart of the app, I achieve the connection and the send of commands fast. I don't know why is this happening. 1. PAIR+CONNECT = FAILURE 2. PAIR+CONNECT+RESTART APP = OK
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@tytydraco commented on GitHub (Nov 24, 2022):

Same result @sharpordie @tytydraco

I've noticed that if I do a pair process, and a connect (when it connects). The send of commands gives me timeouts.

But! If I do a complete restart of the app, I achieve the connection and the send of commands fast.

I don't know why is this happening.

1. PAIR+CONNECT = FAILURE

2. PAIR+CONNECT+RESTART APP = OK

Super easy then, we will have the adb server restart after connect.

<!-- gh-comment-id:1326680818 --> @tytydraco commented on GitHub (Nov 24, 2022): > Same result @sharpordie @tytydraco > > I've noticed that if I do a pair process, and a connect (when it connects). The send of commands gives me timeouts. > > But! If I do a complete restart of the app, I achieve the connection and the send of commands fast. > > I don't know why is this happening. > > 1. PAIR+CONNECT = FAILURE > > 2. PAIR+CONNECT+RESTART APP = OK Super easy then, we will have the adb server restart after connect.
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Nov 25, 2022):

@tytydraco This step 1. in connect gives connection refused 95% of times :(.

Doing a pair command, connect command (that refuses) and later kill-server, doens't work. :(

I'm sad, fucking samsung

<!-- gh-comment-id:1327095264 --> @victorjaviermartin commented on GitHub (Nov 25, 2022): @tytydraco This step 1. in connect gives connection refused 95% of times :(. Doing a pair command, connect command (that refuses) and later kill-server, doens't work. :( I'm sad, fucking samsung
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@victorjaviermartin commented on GitHub (Nov 28, 2022):

Tested in Samsung S20 Ultra with Android 13 and have the same result :(

<!-- gh-comment-id:1328698254 --> @victorjaviermartin commented on GitHub (Nov 28, 2022): Tested in Samsung S20 Ultra with Android 13 and have the same result :(
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@yurikodesu commented on GitHub (Dec 30, 2022):

Same here. Used to work with Android 11 OneUI Core 3.1 but doesn't work on Android 12 OneUI Core 4.1 on my Samsung A03.

<!-- gh-comment-id:1367756572 --> @yurikodesu commented on GitHub (Dec 30, 2022): Same here. Used to work with Android 11 OneUI Core 3.1 but doesn't work on Android 12 OneUI Core 4.1 on my Samsung A03.
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@Maximoff commented on GitHub (Jan 8, 2023):

Same on Realme (RUI 3.0, Android 12). The first time you connect, "no device with transport id 1" pops up, you can't connect in any way. At the same time, the application previously worked on the same device on Android 12. I suspect that the reason is to update the system (security patches).

<!-- gh-comment-id:1374925908 --> @Maximoff commented on GitHub (Jan 8, 2023): Same on Realme (RUI 3.0, Android 12). The first time you connect, "no device with transport id 1" pops up, you can't connect in any way. At the same time, the application previously worked on the same device on Android 12. I suspect that the reason is to update the system (security patches).
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@yurikodesu commented on GitHub (Jan 9, 2023):

Same here. Used to work with Android 11 OneUI Core 3.1 but doesn't work on Android 12 OneUI Core 4.1 on my Samsung A03.

Edit: still broke with OneUI 5.0 Android 13 on same device

<!-- gh-comment-id:1375564199 --> @yurikodesu commented on GitHub (Jan 9, 2023): > Same here. Used to work with Android 11 OneUI Core 3.1 but doesn't work on Android 12 OneUI Core 4.1 on my Samsung A03. Edit: still broke with OneUI 5.0 Android 13 on same device
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@Maximoff commented on GitHub (Jan 17, 2023):

@Maximoff
I seem to have sorted out this problem! You need to allow the program to work in the background, after that everything was successfully connected. Also, I would advise disabling traffic saving in the background.

<!-- gh-comment-id:1386240896 --> @Maximoff commented on GitHub (Jan 17, 2023): @Maximoff I seem to have sorted out this problem! You need to allow the program to work in the background, after that everything was successfully connected. Also, I would advise disabling traffic saving in the background.
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@yurikodesu commented on GitHub (Jan 18, 2023):

@Maximoff
I seem to have sorted out this problem! You need to allow the program to work in the background, after that everything was successfully connected. Also, I would advise disabling traffic saving in the background.

Does that work on Android 13?

<!-- gh-comment-id:1386405193 --> @yurikodesu commented on GitHub (Jan 18, 2023): > @Maximoff > I seem to have sorted out this problem! You need to allow the program to work in the background, after that everything was successfully connected. Also, I would advise disabling traffic saving in the background. Does that work on Android 13?
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@Maximoff commented on GitHub (Jan 18, 2023):

@hyperio546 I don't know, I still have Android 12.

<!-- gh-comment-id:1386706106 --> @Maximoff commented on GitHub (Jan 18, 2023): @hyperio546 I don't know, I still have Android 12.
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@yurikodesu commented on GitHub (Jan 18, 2023):

@hyperio546 I don't know, I still have Android 12.

I had Android 12, but then I upgraded to Android 13 and it's still broke. I really think @tytydraco should do something about this.

<!-- gh-comment-id:1386782258 --> @yurikodesu commented on GitHub (Jan 18, 2023): > @hyperio546 I don't know, I still have Android 12. I had Android 12, but then I upgraded to Android 13 and it's still broke. I really think @tytydraco should do something about this.
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@yurikodesu commented on GitHub (Jan 22, 2023):

Update guys: Downgrading to version 2.0 works on OneUI 5 for me. @tytydraco please take a look. v2.1 is broken. Atleast now I can use adb.

<!-- gh-comment-id:1399457956 --> @yurikodesu commented on GitHub (Jan 22, 2023): Update guys: Downgrading to version 2.0 works on OneUI 5 for me. @tytydraco please take a look. v2.1 is broken. Atleast now I can use adb.
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@codecoachai commented on GitHub (Feb 22, 2023):

Update guys: Downgrading to version 2.0 works on OneUI 5 for me. @tytydraco please take a look. v2.1 is broken. Atleast now I can use adb.

Hi, I have tried it on a samsung sm-g988b with android 13 and oneui 5 and 5.1 and I have not been able to get it to connect every time. In the case of connecting I am not able to use it in a stable way, it freezes and stops responding. As far as I have understood, it's a multicast problem in samsung with the ndsmanager that manages the randomization of the sockets of the adb ports with tcp.

I am lost with this issue

<!-- gh-comment-id:1440325590 --> @codecoachai commented on GitHub (Feb 22, 2023): > Update guys: Downgrading to version 2.0 works on OneUI 5 for me. @tytydraco please take a look. v2.1 is broken. Atleast now I can use adb. Hi, I have tried it on a samsung sm-g988b with android 13 and oneui 5 and 5.1 and I have not been able to get it to connect every time. In the case of connecting I am not able to use it in a stable way, it freezes and stops responding. As far as I have understood, it's a multicast problem in samsung with the ndsmanager that manages the randomization of the sockets of the adb ports with tcp. I am lost with this issue
kerem commented 2026-03-04 02:11:23 +03:00
Author
Owner
Copy link

@yurikodesu commented on GitHub (Feb 22, 2023):

Update guys: Downgrading to version 2.0 works on OneUI 5 for me. @tytydraco please take a look. v2.1 is broken. Atleast now I can use adb.

Hi, I have tried it on a samsung sm-g988b with android 13 and oneui 5 and 5.1 and I have not been able to get it to connect every time. In the case of connecting I am not able to use it in a stable way, it freezes and stops responding. As far as I have understood, it's a multicast problem in samsung with the ndsmanager that manages the randomization of the sockets of the adb ports with tcp.

I am lost with this issue

Something is up

<!-- gh-comment-id:1440346849 --> @yurikodesu commented on GitHub (Feb 22, 2023): > > Update guys: Downgrading to version 2.0 works on OneUI 5 for me. @tytydraco please take a look. v2.1 is broken. Atleast now I can use adb. > > Hi, I have tried it on a samsung sm-g988b with android 13 and oneui 5 and 5.1 and I have not been able to get it to connect every time. In the case of connecting I am not able to use it in a stable way, it freezes and stops responding. As far as I have understood, it's a multicast problem in samsung with the ndsmanager that manages the randomization of the sockets of the adb ports with tcp. > > I am lost with this issue Something is up
kerem commented 2026-03-04 02:11:24 +03:00
Author
Owner
Copy link

@sharpordie commented on GitHub (Feb 23, 2023):

Did you try with the latest Android SDK Platform-Tools (34.0.0)?

<!-- gh-comment-id:1441915206 --> @sharpordie commented on GitHub (Feb 23, 2023): Did you try with the latest Android SDK Platform-Tools (34.0.0)?
kerem commented 2026-03-04 02:11:24 +03:00
Author
Owner
Copy link

@Cr4z33 commented on GitHub (Jun 20, 2023):

@tytydraco any improvement on this issue? :)

<!-- gh-comment-id:1598688256 --> @Cr4z33 commented on GitHub (Jun 20, 2023): @tytydraco any improvement on this issue? :)
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#72
No description provided.