Thank you so much for answering my "What is your personal usage ratio FC / MSFE and why?" message,
If that's alright with you I will carry carry on the discussion about the Android problems
in this newly-created bug report to keep the two threads separate for forum clarity.
This was our current subthread on the Android problems topic:
Strawberry wrote: Interacting with the file system of a USB-connected Android device is really ultra-buggy compared to doing it with MS File Explorer
so I have for now given up using FC for that (fingers crossed FC will become better with USB-connected Android devices in future FC versions!)
So, first, my Windows, Android and FC configs:Marek wrote: I can not test all possible Android devices but on my Windows 10 I have no problems with my Samsung smartphone or tablet.
- copy/move files and folders
- rename file/folder
- delete files/folders
- view files (Ctrl+Q, F3)
- edit files (F4)
- thumbnails view
What do you have to do with MS Explorer?
Maybe you use older Windows?
Windows 7 Home Premium 32 bits SP1
Android Lollipop version 5.0.2
FreeCommander XE 2018 Build 780 32-bit public beta
I am not going to exhaustively list all the problems I have encountered with USB-connected Android device file system interactions
but here are a couple that are reproducible all the time on my config combination (some other problems happen more unpredictably),
hopefully this will help you identifying some reasons I am encountering these problems:
1) When I try to rename a file located on my Android device I get this error message in a dialog box titled "FreeCommander":
"No such interface supported"
2) When I try to create a new folder on my Android device, a dialog box titled "FreeCommander" pops up
with a big white on red cross but no text inside the dialog box.
Any ideas what could be the main reason(s) for these problems?
Many thanks in advance and kind regards