Re: Transferring contents of a large folder (eg 3000 photos) from Android to Windows 10

On Sun, 20 Jul 2025 20:24:13 -0400, Paul wrote:

 
On Sun, 7/20/2025 7:18 PM, Stan Brown wrote:

On Sun, 20 Jul 2025 14:45:49 -0400, Paul wrote:

>
On Sun, 7/20/2025 1:44 PM, Stan Brown wrote:

On Sun, 20 Jul 2025 11:35:43 -0400, Paul wrote:

On Sun, 7/20/2025 9:16 AM, Frank Slootweg wrote:

[quoted text muted]
with a USB-C connector probably are, but those with a USB-A connector
most likely need a OTG adapter. Look for a 'OTG' label on the packaging,
in the 'manual', etc..
>

>
Just about every method of transferring sucks.
>
Just for the record.
>
Individuals doing this, need a good supply of tooth enamel
to handle the failure cases. For example, some computer rooms,
file sharing is hit and miss, and nothing but trouble.

>
Paul, I'd be foolish to argue with you. I'll just say that LocalSend
works or me, every time, to transfer to my desktop PC from my Android
phone. This is the _only_ transfer method that has worked for me,
reliably and promptly. (I can MMS-text a picture from my phone to my
PC, but sometimes, for reasons I don't know, such a transfer takes
over an hour or never competes at all.)
>
Maybe I've just been lucky because I haven't tried to do something
that LocalSend sucks at?
>
>
>

>
https://github.com/localsend/protocol
>
    "The goal is to have a simple REST protocol that does not rely on any external servers."  [Cloud? reference]
>
    "The protocol only needs one party to set up an HTTP server."
>
    "The default multicast group is 224.0.0.0/24 because
     some Android devices reject any other multicast group.
>
     Multicast (UDP)
>
        Port: 53317
        Address: 224.0.0.167
>
     HTTP (TCP)
>
        Port: 53317
    "
>
    "It is important to note that the unencrypted HTTP protocol
     is used because browsers reject self-signed certificates."  [But it does have https:// options, in config]
>
  Paul

 
Sorry, I don't understand how that quote relates to what I said. I
definitely did not have to set up _any_ http servers. (If LocalSend
works by setting one up for me, I don't see the objection.)
 

 
The complexity of the implementation, is roughly the same as FTP.
 
I don't understand the significance of the multicast in there.
 
Presumably you are running LocalSend on both ends, and one end
is functioning as a server, the other end as a client.

Yes, I have it on my phone and my PC, and they negotiate with each
other based on the direction of file transfer.

I don't understand multicast either. The complexity under the hood
may be similar to ftp, but all of that is hidden. I just click the
share icon on whatever I want to transfer from phone to PC, select
localsend, and tell it to send to the PC.

--
After using my real address in 37 years of Usenet articles,
I am now reluctantly posting a fake address because of the
large number of sites scraping Usenet articles without
permission and putting them on their own pretend forum sites.