Dies when it encounters files with special chars (Transport endpoint is not connected)

[schrmh]

Literally the title. It even happens with umlauts (and those are part of ASCII!). At first I thought it were long file names but:

08:14:36 ~/POCOF1_crDroid_Dec2025/sdcard/AnkiDroid/collection.media:$ rsync -aAXHUv /home/duda/mnt5/sdcard/AnkiDroid/collection.media/maxresdefault-11baf9b1170356b2b0321a3d3773d1b39bfb86fe.jpg  .
sending incremental file list

sent 107 bytes  received 12 bytes  79,33 bytes/sec
total size is 77.801  speedup is 653,79
08:14:44 ~/POCOF1_crDroid_Dec2025/sdcard/AnkiDroid/collection.media:$ rsync -aAXHUv /home/duda/mnt5/sdcard/AnkiDroid/collection.media/gesch�ftsmann-betritt-den-raum.jpg  .
sending incremental file list
rsync: [sender] send_files failed to open "/home/duda/mnt5/sdcard/AnkiDroid/collection.media/gesch\#344ftsmann-betritt-den-raum.jpg": Software caused connection abort (103)

sent 99 bytes  received 35 bytes  268,00 bytes/sec
total size is 28.465  speedup is 212,43
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.4.1]
08:16:08 ~/POCOF1_crDroid_Dec2025/sdcard/AnkiDroid/collection.media:$ LANG=C ls ~/mnt5 
ls: cannot access '/home/duda/mnt5': Transport endpoint is not connected

I can then continue after umounting and just using `adbfs ~/mnt5``again but it breaks every time when it encounters a file with special chars.

Using Arch Linux but tried with this repo cloned as described in the README.

[spion]

I tried creating this type of file using adb shell and then attempted rsync:

rsync -aAXHUv /home/spion/Documents/adbfs/storage/self/primary/Documents/test-special-chars/test-ä-file.txt  ./
sending incremental file list
test-ä-file.txt

sent 108 bytes  received 35 bytes  286.00 bytes/sec
total size is 0  speedup is 0.00

The output of ./adbfs -f ~/Documents/adbfs while doing this is:

from cache /storage/emulated/0/Documents/test-special-chars/test-ä-file.txt
-- adb_open --/storage/emulated/0/Documents/test-special-chars/test-ä-file.txt /tmp/adbfs-yAKf1S/-storage-emulated-0-Documents-test-special-chars-test-ä-file.txt
ls -l -a -d '/storage/emulated/0/Documents/test-special-chars/test-ä-file.txt'
--*-- exec_command: adb shell "ls -l -a -d '/storage/emulated/0/Documents/test-special-chars/test-ä-file.txt'"
--*-- exec_command: adb pull '/storage/emulated/0/Documents/test-special-chars/test-ä-file.txt' '/tmp/adbfs-yAKf1S/-storage-emulated-0-Documents-test-special-chars-test-ä-file.txt'
/storage/emulated/0/Documents/test-special-chars/test-ä-file.txt: 1 file pulled, 0 skipped.
flag is: 0
invalidate cache /storage/emulated/0/Documents/test-special-chars/test-ä-file.txt

seems to work fine.

Of course, that character has utf-8 encoding, whereas the tool you use probably uses utf-16 when determining the string of the file to write (or not UTF at all).

I am prevented from creating that type of file on the /storage part of the filesystem:

$ printf 'test-\344-file.txt' | xargs touch
touch: 'test-�file.txt': Operation not permitted

However if I try to do it in /tmp and then rsync that:

❯ rsync -aAXHUv /home/spion/Documents/adbfs/tmp/test ./
sending incremental file list
test/
test/test-\#344-file.txt

sent 142 bytes  received 39 bytes  362.00 bytes/sec
total size is 0  speedup is 0.00

it works fine, with ./adbfs -f showing this

from cache /tmp/test/test-�-file.txt
-- adb_open --/tmp/test/test-�-file.txt /tmp/adbfs-yAKf1S/-tmp-test-test-�-file.txt
ls -l -a -d '/tmp/test/test-�-file.txt'
--*-- exec_command: adb shell "ls -l -a -d '/tmp/test/test-�-file.txt'"
--*-- exec_command: adb pull '/tmp/test/test-�-file.txt' '/tmp/adbfs-yAKf1S/-tmp-test-test-�-file.txt'
/tmp/test/test-�-file.txt: 1 file pulled, 0 skipped.
flag is: 0
invalidate cache /tmp/test/test-�-file.txt

Could you post the output of ./adbfs -f on your end?

[schrmh]

printf 'test-\344-file.txt' | xargs touch
works for me on storage on my Android device running a LineageOS based Android 15 ROM (even when using adb shell) as well as on btrfs on my PC.

Output is similar and weirdly when only playing around with that file now it worked a bunch of times after failing only once now (when not using -f).
But what I got to constantly get to fail right now* are copying files with $ in names (like 'Rexton_FX_$1.bin' in this case):

ls: /storage/emulated/0/Android/data/ru.oojceeoi.vpqhktcpe/files/LuckyPatcher/CustomPatches/Rexton_FX_.bin: No such file or directory
/usr/include/c++/15.2.1/bits/stl_queue.h:262: std::queue<_Tp, _Sequence>::reference std::queue<_Tp, _Sequence>::front() [with _Tp = std::__cxx11::basic_string<char>; _Sequence = std::deque<std::__cxx11::basic_string<char>, std::allocator<std::__cxx11::basic_string<char> > >; reference = std::__cxx11::basic_string<char>&]: Assertion '!this->empty()' failed.
Abgebrochen                (Speicherabzug geschrieben) adbfs -f ~/mnt5

Running rsync on the Anki directory again, it is currently copying other files than the one file with ä but it looks like it manages to copy files containing Kanji rn...

Edit:
* well such files with $ also did not work yesterday and while the file with ä funnily was copyable when I wrote its actual name and not this broken encoding those just were not unless I used adb pull.

[chronoscz]

Happens to me as well with special chars in file names like $ and `.