not working on Samsung running OS12 #90

ToysoftInc · 2022-10-26T04:19:31Z

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'

victorjaviermartin · 2022-10-27T07:22:23Z

Me too.

Device: Samsung Galaxy S20 Ultra with Android 12

lautit · 2022-11-15T12:38:43Z

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

qinlili23333 · 2022-11-15T12:48:17Z

verified on s21 ultra, stuck at connection

victorjaviermartin · 2022-11-17T09:43:13Z

@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 [email protected]
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

tytydraco · 2022-11-17T16:34:08Z

@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.

tytydraco · 2022-11-17T16:34:44Z

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.

sharpordie · 2022-11-19T22:35:26Z

Does it even work with the official desktop adb?

lautit · 2022-11-21T12:37:21Z

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

victorjaviermartin · 2022-11-22T14:56:41Z

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

victorjaviermartin · 2022-11-23T13:47:12Z

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

sharpordie · 2022-11-23T16:22:20Z

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.

victorjaviermartin · 2022-11-24T07:09:20Z

I will try it and say something.

victorjaviermartin · 2022-11-24T10:28:12Z

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.

PAIR+CONNECT = FAILURE
PAIR+CONNECT+RESTART APP = OK

tytydraco · 2022-11-24T16:54:49Z

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.

victorjaviermartin · 2022-11-25T07:08:57Z

@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

victorjaviermartin · 2022-11-28T08:16:39Z

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

hyperio546 · 2022-12-30T06:54:28Z

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.

Maximoff · 2023-01-08T20:59:19Z

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).

hyperio546 · 2023-01-09T12:35:59Z

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

Maximoff · 2023-01-17T23:35:45Z

@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.

hyperio546 · 2023-01-18T02:58:02Z

@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?

Maximoff · 2023-01-18T09:01:00Z

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

hyperio546 · 2023-01-18T09:58:31Z

@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.

hyperio546 · 2023-01-22T11:20:21Z

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.

codecoachai · 2023-02-22T16:10:04Z

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

hyperio546 · 2023-02-22T16:22:07Z

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

sharpordie · 2023-02-23T14:45:53Z

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

Cr4z33 · 2023-06-20T12:35:01Z

@tytydraco any improvement on this issue? :)

tytydraco added the bug Something isn't working label Nov 17, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

not working on Samsung running OS12 #90

not working on Samsung running OS12 #90

ToysoftInc commented Oct 26, 2022

victorjaviermartin commented Oct 27, 2022

lautit commented Nov 15, 2022 •

edited

Loading

qinlili23333 commented Nov 15, 2022

victorjaviermartin commented Nov 17, 2022 •

edited

Loading

tytydraco commented Nov 17, 2022

tytydraco commented Nov 17, 2022

sharpordie commented Nov 19, 2022

lautit commented Nov 21, 2022

victorjaviermartin commented Nov 22, 2022

victorjaviermartin commented Nov 23, 2022

sharpordie commented Nov 23, 2022 •

edited

Loading

victorjaviermartin commented Nov 24, 2022

victorjaviermartin commented Nov 24, 2022 •

edited

Loading

tytydraco commented Nov 24, 2022

victorjaviermartin commented Nov 25, 2022 •

edited

Loading

victorjaviermartin commented Nov 28, 2022

hyperio546 commented Dec 30, 2022

Maximoff commented Jan 8, 2023

hyperio546 commented Jan 9, 2023

Maximoff commented Jan 17, 2023

hyperio546 commented Jan 18, 2023

Maximoff commented Jan 18, 2023

hyperio546 commented Jan 18, 2023

hyperio546 commented Jan 22, 2023

codecoachai commented Feb 22, 2023

hyperio546 commented Feb 22, 2023

sharpordie commented Feb 23, 2023

Cr4z33 commented Jun 20, 2023

not working on Samsung running OS12 #90

not working on Samsung running OS12 #90

Comments

ToysoftInc commented Oct 26, 2022

victorjaviermartin commented Oct 27, 2022

lautit commented Nov 15, 2022 • edited Loading

qinlili23333 commented Nov 15, 2022

victorjaviermartin commented Nov 17, 2022 • edited Loading

tytydraco commented Nov 17, 2022

tytydraco commented Nov 17, 2022

sharpordie commented Nov 19, 2022

lautit commented Nov 21, 2022

victorjaviermartin commented Nov 22, 2022

victorjaviermartin commented Nov 23, 2022

sharpordie commented Nov 23, 2022 • edited Loading

victorjaviermartin commented Nov 24, 2022

victorjaviermartin commented Nov 24, 2022 • edited Loading

tytydraco commented Nov 24, 2022

victorjaviermartin commented Nov 25, 2022 • edited Loading

victorjaviermartin commented Nov 28, 2022

hyperio546 commented Dec 30, 2022

Maximoff commented Jan 8, 2023

hyperio546 commented Jan 9, 2023

Maximoff commented Jan 17, 2023

hyperio546 commented Jan 18, 2023

Maximoff commented Jan 18, 2023

hyperio546 commented Jan 18, 2023

hyperio546 commented Jan 22, 2023

codecoachai commented Feb 22, 2023

hyperio546 commented Feb 22, 2023

sharpordie commented Feb 23, 2023

Cr4z33 commented Jun 20, 2023

lautit commented Nov 15, 2022 •

edited

Loading

victorjaviermartin commented Nov 17, 2022 •

edited

Loading

sharpordie commented Nov 23, 2022 •

edited

Loading

victorjaviermartin commented Nov 24, 2022 •

edited

Loading

victorjaviermartin commented Nov 25, 2022 •

edited

Loading