XPost: comp.sys.mac.system, alt.comp.os.windows-10, comp.mobile.android   
   From: robin_listas@es.invalid   
      
   On 2025-04-15 20:27, Frank Slootweg wrote:   
   > Carlos E.R.  wrote:   
   >> On 2025-04-15 15:18, Frank Slootweg wrote:   
   > [...]   
   >>>     For a non-automated backup you can use MTP. With MTP you *can* access   
   >>> the /Internal storage/Android folders. For example in Windows File   
   >>> Explorer, this accesses the folder which contains the OsmAnd+ maps:   
   >>   
   >> MTP is what I do. Sometimes I have used a WiFi file server app on the   
   >> phone instead. Sometimes I found that one can see files the other   
   >> doesn't, but I don't remember which.   
   >   
   >    Yes, I have  also found such servers, but none for recent Android   
   > versions (10 and higher), which can access the /Internal storage/Android   
   > folders.   
      
   I have not tried recently.   
      
   >   
   >>> This PC\Frank's Galaxy A51\Internal storage\Android\data\net   
   osmand.plus\files   
   >>>   
   >>>     But 'This PC\Frank's Galaxy A51\Internal storage' is only accessible   
   >>> in File Explorer, it's not part of the normal file system, nor   
   >>> accessible as a Network Share, so you can't use normal copy or backup   
   >>> utilities. (Perhaps in Windows PowerShell one can 'program'/control File   
   >>> Explorer? No idea.)   
   >>   
   >> In Linux we can access the filesystem. Once I tell the equivalent of the   
   >> file explorer to access the phone, then it is also accessible under:   
   >>   
   >> /run/user/1000/gvfs/mtp:host=motorola_moto_g52_SOME_LETTERS   
   >>   
   >> for any app. This is using with a gtk desktop, with KDE it is somewhere   
   >> else.   
   >>   
   >> Then I can use rsync and copy links to the files in the previous backup.   
   >   
   >    Could you give an example (Linux) 'cp' command which shows what the   
   > source and destination paths look like?   
      
   cp /run/user/1000/gvfs/mtp\:host\=motorola_moto_g52_ZLETTERS/Almacenamiento\   
   interno\ compartido/DCIM/Camera/ /home/cer/Photos   
      
      
   The trick is that "gvfs" means something virtual filesystem. The G could be   
   gnome or gtk, dunno.   
      
      
   >    In Windows you can't specify a source path for a 'copy', etc., because   
   > such a path does not exist for MTP, so - being an old Unix/UNIX and   
   > current GNU user - I am interested what it looks like on Linux (for   
   > MTP).   
   >   
   >    Or is the source just a path relative to /run/user/1000/gvfs/mtp?   
   >   
   > [...]   
      
   It is an emulation layer. MTP does not support every operation a true   
   filesystem does.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)