Changes on the tab are not reflected until the cable is replugged about android-file-transfer-linux HOT 7 CLOSED

Works. A "Refresh" button would be convenient to have.

from android-file-transfer-linux.

Android spawns mtp-daemon every time you plug the cable. Maybe this is related to #27 . Could you create directory via fuse?
./aft-fuse-mount
It might say that your filesystem is readonly ( #31 ), but it will not prevent you from creating directories.
Seems to be android's MTP implementation does not process 'any' storage destination well. FUSE wrapper sets storage explicitly.

from android-file-transfer-linux.

Do you mean ./aft-mtp-mount ?

GUI program refuses to start if the device is already connected via FUSE. Should I file a bug?

FUSE mounting has the same issue. I can create directories on the tab via FUSE, but if I change something, I cannot see it by FUSE until I unplug the cable and plug it back in.

from android-file-transfer-linux.

Just in case: the device is Samsung Galaxy Tab Pro SM-T525, and it lacks Android MTP extensions.

from android-file-transfer-linux.

GUI program refuses to start if the device is already connected via FUSE. Should I file a bug?

No, this is intended. You cannot share usb device.

from android-file-transfer-linux.

Could you please uncomment the following line (Session.cpp:136) and test once again? MTP specification is unclear about whether I need sending empty object after creating association(directory) or not. Google devices returns error 'no valid object info', so I considered that it's not needed.

//SendObject(std::make_shared<ByteArrayObjectInputStream>(ByteArray()));

from android-file-transfer-linux.

could you test it now? I added storage selection combo box and many other improvements.

from android-file-transfer-linux.