XPost: comp.mobile.android   
   From: mariasophia@comprehension.com   
      
   Herbert Kleebauer wrote:   
   >> One is mere mapping; the other is mounting as a drive letter.   
   >> They're not the same thing.   
   >   
   > Who cares.   
      
   OK. That's a *different* issue than which is the better solution. :)   
      
   To compare FTP v WebDav objectively, I opened this comparison thread today:   
    Newsgroups: alt.comp.os.windows-11,alt.comp.os.windows-10,comp.mobile.android   
    Subject: Discussion of FTP vs WebDav for Android/iOS filesystem sharing on   
   Windows PC   
    Date: Tue, 27 Jan 2026 12:11:06 -0500   
    Message-ID: <10larja$2ai$1@nnrp.usenet.blueworldhosting.com>   
      
   > The only thing I want do do is, to copy pictures taken   
   > with the phone (or in this case a zip file generated by exporting a   
   > chat from Whatsapp) to the pc and sometimes copy videos or apk files   
   > to the phone. And that happens only every few month.   
      
   Since your needs are so simple, almost any solution I've tested in the past   
   works for you (& that's fine). Nobody said you had to use a better tool.   
      
   These will all likely work just fine for your simple copying needs:   
      AirDroid, ADB, AFT MTP client, DirectNetDrive, FTPUse, Ftpuse,   
      Fb-adb Android Linux shell, Go-mtpfs MTP FUSE filesystem,   
      Gphotofs Camera Linux mount, JMTP FS, KDEconnect, Kies Connect,   
      LibIconv, LibMTP, LibMTP, LibMTP library MTP implementation,   
      LibUSB Win32, LibUsbK, LibiConv, MTP support on KDE, MTPDrive,   
      MTPSync, MTPdude, MTPfs FUSE filesystem, NetDrive 1.3.2.0,   
      NetDrive 3.6.571, Nitroshare, PhoneLink, SFTP Net Drive, SideSync,   
      SMB Cifs (client) X-Plore, SMB Cifs (root), Scrcpy/sndcpy,   
      Termux copy, WebDav, WebDrive, XNJB Mac OS X GUI, etc.   
      
   For me, I have the added requirement that scripts (like syncing)   
   need to work without me having to specify the Android drive letter.   
      
   >> I don't do anything and my entire Android phone is permanently mounted on   
   >> Windows the moment I boot up my Android phone and I boot up Windows.   
   >   
   > That makes your solution unusable for me.   
      
   Um... er... huh?   
      
   All I would have to do is *not* run the "net use" command.   
   And then there is no mounting of Android onto Windows as a drive letter.   
      
   > If you have a pc which   
   > downloads every few month some files from the internet, do you then   
   > want that this pc is connected to the internet all the time?   
      
   Eh... ah... huh?   
      
   All you have to do is run the "net use" command when you actually need the   
   Android phone file system to be mounted as a drive letter onto Windows.   
      
      
   > The communication software on pc and phone must be active only   
   > if I transfer data. I don't want an open port to the phone all   
   > the time.   
      
   Bbbbbuuuuttttt it's just this one command you run when you need it.   
    C:\> net use Z: \\102.168.1.2@8000\DavWWWRoot   
      
   When you don't need it anymore, you just unmount the phone from Windows.   
    C:\> net use Z: /delete   
   --   
   On Usenet, we have found the best way to do everything that we need to do.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)