[WFX] Android ADB 8.8

[Conan]

Hello everyone. I'm having a problem copying files larger than 1 GB. They copy perfectly to my Fold 4, but then they don't move to the correct location. The files are then named "\sdcard\7B0C8FA0.tmp." So far, only video files (.mp4) and, for example, AP_F936BXXSAGYB2_F936BXXSAGYB2_MQB93053233_REV00_user_low_ship_MULTI_CERT_meta_OS14.tar.md5 (to root my Fold 4, I have to patch the file on the Fold with Magisk). This doesn't happen with smaller files.

[Skif_off]

Linux-version is linked with libxml2-iw.so.2
What kind of library is this? The usual name is libxml2.so.2.

[Guillaume]

I'm confused:

1. When I choose Native 8.1 "ls -la --full-time", I don't get any folder listing (devices with Android 11, 13 and 15).
2. When I choose Native 8.1 "ls -la" while adding -la --full-time at the end myself, it does work (all folders get listed and full timestamps are available).

Also, when closing TC, it always crashes when before that I used ADB, did some action like powering down the device via the Power menu and then clicked "Disconnect" in TC's FTP connection toolbar: The instruction at 0x00000000EC4AF00 referenced memory at 0x00000000EC4AF00. The memory could not be written. I am now on ADB 8.11.

[slofje23]

I'm confused:

1. When I choose Native 8.1 "ls -la --full-time", I don't get any folder listing (devices with Android 11, 13 and 15).
2. When I choose Native 8.1 "ls -la" while adding -la --full-time at the end myself, it does work (all folders get listed and full timestamps are available).

Also, when closing TC, it always crashes when I used ADB and then clicked "Disconnect" in the top panel: The instruction at 0x00000000EC4AF00 referenced memory at 0x00000000EC4AF00. The memory could not be written. I am now on ADB 8.11.

This --full-time option is not implemented correctly, imho. As I described in my post of 2025-02-07 here above.
Many thanks for finding this workaround! How the $#@ did you discover this!?
It looks like I now can synchronize directories with "ignore date" UNchecked.

The crash you describe is unknown to me.
I have no "Disconnect" option when navigating with the ADB-plugin in TC. I suppose this is something like the "Disconnect" button when connected to a FTP site ?

[Guillaume]

This --full-time option is not implemented correctly, imho. As I described in my post of 2025-02-07 here above.
Many thanks for finding this workaround! How the $#@ did you discover this!?

Good question. I was confused by the fact that for some of these options the parameters field was filled in by default, but empty for others. And of course the fact that the only difference between the last two entries seems to be the presence of "--full-time", even though the last one doesn't even work. So I just tried to recreate the last entry using the other one.

It looks like I now can synchronize directories with "ignore date" UNchecked.

Yes, this has always been a major pain for me as well. So happy there's a workaround.

In my experience, ADB is also a lot faster and more reliable than using the Media Transfer Protocol (it doesn't work at all from within TC without the MediaAudio2 plugin and is very laggy when just using Explorer, completely freezing the Explorer windows for several minutes and sometimes even cutting off transfers without reporting it to the user).

The crash you describe is unknown to me.
I have no "Disconnect" option when navigating with the ADB-plugin in TC. I suppose this is something like the "Disconnect" button when connected to a FTP site ?

This can be seen when enabling the ADB plugin's option Debug logging to Total Commander FTP connection toolbar.

[slofje23]

This can be seen when enabling the ADB plugin's option Debug logging to Total Commander FTP connection toolbar.

Ah yes, I should have noticed that.
I tried it and I have no crashes. With Windows 10, Total Commander 11.51, ADB Plugin 8.11, adb.exe 1.0.40 and Android 14

[Guillaume]

This can be seen when enabling the ADB plugin's option Debug logging to Total Commander FTP connection toolbar.

Ah yes, I should have noticed that.
I tried it and I have no crashes. With Windows 10, Total Commander 11.51, ADB Plugin 8.11, adb.exe 1.0.40 and Android 14

I don't know why it does that, either. W10, TC11.51, ADB8.11, ADB1.0.41(35.0.2-12147458), Android 11/13/15.

Here's a step-by-step:

1. Open ADB panel with Debug logging to Total Commander FTP connection toolbar enabled
2. Do some action like powering down the device via the Power menu
3. Click "Disconnect" in TC's FTP connection toolbar
4. Close TC and see crash:

   The instruction at 0x00000000EC4AF00 referenced memory at 0x00000000EC4AF00. The memory could not be written.

Opening the ADB panel also freezes TC for 32 seconds when first starting ADB.

[slofje23]

Here's a step-by-step:

1. Open ADB panel with Debug logging to Total Commander FTP connection toolbar enabled
2. Do some action like powering down the device via the Power menu
3. Click "Disconnect" in TC's FTP connection toolbar
4. Close TC and see crash:

   The instruction at 0x00000000EC4AF00 referenced memory at 0x00000000EC4AF00. The memory could not be written.

Sorry, I cannot reconstruct this crash.
I copied some files and powered down the phone. Then click Disconnect and close TC. It works without problems.
I tried this with ADB over USB, and ADB over WiFi.

[BudCord]

I have been experiencing a timeout of 35 seconds when initially connecting Windows to the smartphone via USB-C for some time now:

2025-05-10 15:45:57 [1690] Connecting to ADB server...
2025-05-10 15:46:27 [1690] ADB Binary: "C:\Users\[username]\AppData\Roaming\GHISLER\plugins\wfx\ADB\bin\adb" "devices"
2025-05-10 15:46:32 [1690] Connected

If I then disconnect the cable and reconnect it later for a new connection in the same Total Commander session, the folders and files on the smartphone are displayed again immediately.
“Previously” this timeout did not exist, the connection was always established immediately.

The problem occurs on all PCs used with Windows 10 and 11.
Affected Android ADB 8.11 and various previous versions.
Regardless of whether I use the supplied ADB files or newer ones, the timeout remains.

How do I get rid of this timeout?

[Guillaume]

2BudCord
Yep, I have the same (32 seconds): https://www.ghisler.ch/board/viewtopic.php?p=471366#p470989

The adb.exe process isn't spawned until after the 32 seconds timeout, so it's a problem with the plugin or TC.

Just to be sure, I also went back to an adb.exe version from January 2018, same result.

Edit
I had an old version (7.6) of the ADB plugin in a backup. It does not have this delay.

[BudCord]

Thanks for the approach with the old versions!
I have found the following in my backups with the specified timeouts:
7.02 | 8.05 | 8.06 | 8.08 -> 7 to 8 sec
8.10 | 8.11 -> 35 sec

At the moment 8.08 is running again and I only have to wait 7 seconds.

[Guillaume]

2BudCord
Confirmed, I just restored v8.8 (dated May 14, 2020) and there's only a 2s delay. v8.10 introduces the 35s delay (I think there wasn't a v8.9 for Windows as the changelog only mentions Linux, otherwise I missed it).

[Pumpkin]

Using Win11 and latest TC & Android ADB 8.11.

Adb.exe does not start and plugin hangs TC requiring closing the task.

If I run adb devices via command line first then the plugin works fine. The same happens for previous versions of the plugin.

Changing the path to adb makes no difference.

Is there any work around on this?

The way I get around this at the moment is to start adb devices in a script and then start TC via the same script then use a shortcut to that called Total Commander.lnk.. It works but annoying.

Help appreciated.