The phone is Android 14, Samsung Galaxy A13 SM-A137F/DSN....
Unfortunately this phone only has internal storage, so it's not even possible to copy files to Micro SD card in the phone and then remove it
and put it in a card reader on the PC.
Is there is way around this?
The phone is Android 14, Samsung Galaxy A13 SM-A137F/DSN. The PC is Win
10 Pro.
My mother has a lot of photos (both taken on her Android phone's camera and received as attachments in WhatsApp) which she wants to transfer to her Windows PC for permanent storage and backup to a USB HDD.
The phone is Android 14, Samsung Galaxy A13 SM-A137F/DSN. The PC is Win 10 Pro.
The obvious way would be by USB cable, such that the phone appears as a "pseudo disk drive" in Windows Explorer and files can be selected for copying/moving. I know about the various USB modes: "Transferring files/Android AUto", "USB tethering", "MIDI", "Transferring images", "Charging phone only". Of these, only the two "Transferring" options would seem to be relevant. "Transferring photo" only shows the DCIM folder; "Transferring files" also shows Android/media/com.whatsapp/WhatsApp/Media/Whatsapp Images.
However Windows 10 (unlike Windows 7) seems to crash Explorer as it is gradually transferring the list of files (not the files themselves) in a selected folder (eg DCIM) order to populate the Explorer window so files can be selected.
On Win 7, even a folder with a large number of files (photos), as seen by Windows Explorer, gradually (slowly!) populates with filenames/icons and then allows them to be selected and copied.
Unfortunately this phone only has internal storage, so it's not even possible to copy files to Micro SD card in the phone and then remove it and put it in a card reader on the PC.
Is there is way around this?
Files can be transferred in small quantities as email attachments, but with a folder of 2000+ files, that will take forever. And it needs to an ongoing process, not just a one-off process: as she takes new photos into the DCIM folder or receives them to Whatsapp, she wants to transfer the new files to Windows.
And above all, it needs to be a SIMPLE solution because unlike a Windows PC, I can't connect to the phone remotely by TeamViewer. (I live 200 miles away.)
There are various solutions that transfer by Bluetooth but they also seem to be geared up for selecting fairly small batches of files.
Is there a known problem (and solution!) with Win 10 viewing the contents of a folder on Android via USB if there are a large number of files to be enumerated before copying?
You could set up FTP on the computer end, to give the various
phone methods another "push" option. Maybe a Wifi protocol would
have slightly better performance than the USB2 (and mainly because
"not using MTP", not just because the link runs at a different speed).
File Sharing might work. FTP might work.
My mother has a lot of photos (both taken on her Android phone's camera
and received as attachments in WhatsApp) which she wants to transfer to
her Windows PC for permanent storage and backup to a USB HDD.
The phone is Android 14, Samsung Galaxy A13 SM-A137F/DSN. The PC is Win
10 Pro.
The obvious way would be by USB cable, such that the phone appears as a "pseudo disk drive" in Windows Explorer and files can be selected for copying/moving. I know about the various USB modes: "Transferring files/Android AUto", "USB tethering", "MIDI", "Transferring images", "Charging phone only". Of these, only the two "Transferring" options
would seem to be relevant. "Transferring photo" only shows the DCIM
folder; "Transferring files" also shows Android/media/com.whatsapp/WhatsApp/Media/Whatsapp Images.
However Windows 10 (unlike Windows 7) seems to crash Explorer as it is gradually transferring the list of files (not the files themselves) in a selected folder (eg DCIM) order to populate the Explorer window so files
can be selected.
On Win 7, even a folder with a large number of files (photos), as seen
by Windows Explorer, gradually (slowly!) populates with filenames/icons
and then allows them to be selected and copied.
Unfortunately this phone only has internal storage, so it's not even possible to copy files to Micro SD card in the phone and then remove it
and put it in a card reader on the PC.
Is there is way around this?
Files can be transferred in small quantities as email attachments, but
with a folder of 2000+ files, that will take forever. And it needs to an ongoing process, not just a one-off process: as she takes new photos
into the DCIM folder or receives them to Whatsapp, she wants to transfer
the new files to Windows.
And above all, it needs to be a SIMPLE solution because unlike a Windows
PC, I can't connect to the phone remotely by TeamViewer. (I live 200
miles away.)
There are various solutions that transfer by Bluetooth but they also
seem to be geared up for selecting fairly small batches of files.
Is there a known problem (and solution!) with Win 10 viewing the
contents of a folder on Android via USB if there are a large number of
files to be enumerated before copying?
Perhaps your phone phone supports a thumbdrive. Stick one in (using an USB-C thumbdrive or a standard one using an USB-A to USB-C conversion plug) and see what happens.
On 2025-07-19 14:07, Paul wrote:
You could set up FTP on the computer end, to give the various
phone methods another "push" option. Maybe a Wifi protocol would
have slightly better performance than the USB2 (and mainly because
"not using MTP", not just because the link runs at a different speed).
File Sharing might work. FTP might work.
So do you know a good ftp or sftp android app that actually works?
I have been using the FTP server within the ES File Explorer app for
many years, and it works fine. ...
Roger Mills <mills37.fslife@gmail.com> wrote:
I have been using the FTP server within the ES File Explorer app
for many years, and it works fine. ...
ES File Explorer got banned by Google at their Play Store when they
got caught as spyware back in 2015. It is still not listed there.
ES File Explorer got banned by Google at their Play Store when
they got caught as spyware back in 2015.
VanguardLH wrote:
Roger Mills <mills37.fslife@gmail.com> wrote:
I have been using the FTP server within the ES File Explorer app
for many years, and it works fine. ...
ES File Explorer got banned by Google at their Play Store when they
got caught as spyware back in 2015. It is still not listed there.
Guess Amazon is more trusting. ES File Explorer is still available for download in their Appstore...
On 19/07/2025 14:30, Carlos E.R. wrote:
On 2025-07-19 14:07, Paul wrote:
You could set up FTP on the computer end, to give the various
phone methods another "push" option. Maybe a Wifi protocol would
have slightly better performance than the USB2 (and mainly because
"not using MTP", not just because the link runs at a different speed).
File Sharing might work. FTP might work.
So do you know a good ftp or sftp android app that actually works?
I have been using the FTP server within the ES File Explorer app for many years, and it works fine. I use AceFTP 2 as the FTP client on my PC (simply because it came free on the cover disk of a PC magazine many years ago) but any other FTP client should work.
The process is this:
Turn on ES File Exlorer on the phone
Select 'View on PC'
Tap TURN ON
This turns on the server and displays the IP address and port at which the PC's FTP client needs to be pointed
Run the FTP client on the PC
Point it at the address/port displayed on the phone (You can save this for future use)
Click on CONNECT
The connection is made (using WiFi - no cables), and two explorer-type windows are displayed on the PC
Navigate to where the files are on the phone, and to where you want them to be on the PC
Using the right and left arrows displayed on the PC (in Ace FTP, but other clients will have the equivalent) you can copy files in either direction between the two devices. [This means that you drive everything from the PC end, which is far simpler than having to do it on the phone].
[The description of the process (above) looks far more complicated than it actually is!]
NOTE: Until a few years ago, you could install ES File Explorer from Play Store, but it has now been removed due to some alleged security issue - so it has to be side-loaded. I've done this on several Android devices, and have never experienced any issues. If you search for ES File Exploreer in Play Store, it will offer you EX File Explorer, which looks similar but is *not* the same.
AJL <noemail@none.com> wrote:
If you got ES File Explorer from Amazon's app store, you have a
month until it may malfunction.
Or, maybe Amazon is just eliminating access to their app store on
non-Amazon devices. Maybe you can still access their app store
using their store app on Amazon devices (e.g., Fire tablets nee
Kindle).
I'm not wasting money and time on a Fire tablet to find out after the
cutoff date.
The app is not available at Google's Play Store. It never came
back. Looks like Amazon is dropping access to their Android app store
to users on non-Amazon devices. The app author doesn't even point to
the Amazon app store. So, for me, there is no point in wasting time
retesting this app of dubious reputation that will soon be
unavailable except at a dubious download source by a site that
doesn't use a site cert.
My mother has a lot of photos (both taken on her Android phone's camera
and received as attachments in WhatsApp) which she wants to transfer to
her Windows PC for permanent storage and backup to a USB HDD.
The phone is Android 14, Samsung Galaxy A13 SM-A137F/DSN. The PC is Win
10 Pro.
Unfortunately this phone only has internal storage, so it's not even possible to copy files to Micro SD card in the phone and then remove it
and put it in a card reader on the PC.
Is there is way around this?
Localsend (free and open source) lets you transfer files between--
devices that are on the same Wifi LAN. I've seen and tried many other solutions, but this is the first one that actually worked for me. (I
tried transfers in both directions.)
https://github.com/localsend/localsend/releases/tag/v1.17.0
You load the app on your phone (I found it in the Google Play Store)
and the appropriate version from the above link on your computer.
Yes, you can have more than two devices with Localsend, though I
didn't test that. Each install creates a device identifier name that
is unique to Localsend, to identify the sending device to the
receiver and vice versa.
You need to have Localsend actually running on both devices involved
in the transfer. A nice feature is that in Android when you have a
picture, you can just tap the Share icon and the picture will appear
in Localsend. I transferred a couple of pictures that were a few
hundred K each, and the transfer was instantaneous.
Source:
https://www.howtogeek.com/open-source-android-apps-to-install/
My mother has a lot of photos (both taken on her Android phone's camera
and received as attachments in WhatsApp) which she wants to transfer to
her Windows PC for permanent storage and backup to a USB HDD.
The phone is Android 14, Samsung Galaxy A13 SM-A137F/DSN. The PC is Win
10 Pro.
The obvious way would be by USB cable, such that the phone appears as a "pseudo disk drive" in Windows Explorer and files can be selected for copying/moving. I know about the various USB modes: "Transferring files/Android AUto", "USB tethering", "MIDI", "Transferring images", "Charging phone only". Of these, only the two "Transferring" options
would seem to be relevant. "Transferring photo" only shows the DCIM
folder; "Transferring files" also shows Android/media/com.whatsapp/WhatsApp/Media/Whatsapp Images.
However Windows 10 (unlike Windows 7) seems to crash Explorer as it is gradually transferring the list of files (not the files themselves) in a selected folder (eg DCIM) order to populate the Explorer window so files
can be selected.
On Win 7, even a folder with a large number of files (photos), as seen
by Windows Explorer, gradually (slowly!) populates with filenames/icons
and then allows them to be selected and copied.
Unfortunately this phone only has internal storage, so it's not even possible to copy files to Micro SD card in the phone and then remove it
and put it in a card reader on the PC.
Is there is way around this?
With FTP, you can push or pull.
net use Z: \\192.168.0.2@8000\DavWWWRoot /USER:foo * /PERSISTENT:YES--- Synchronet 3.21a-Linux NewsLink 1.2
The version 4.2.1.3.a at the Amazon store is pretty old, and not the
latest version available according to the app author's version history. >4.2.1.4 is dated Jun 2022. Before you say that is not a web site for
the app, go to http://www.estrongs.com/, and click on Android, and,
guess what, you're taken to the uptodown.com site. They don't link to
the Amazon app store nor, obviously, to the Google app store. Also
notice www.estrongs.com does not have a site certificate. You trust
them if you want. I don't.
The app is not available at Google's Play Store. It never came back.
Looks like Amazon is dropping access to their Android app store to users
on non-Amazon devices. The app author doesn't even point to the Amazon
app store. So, for me, there is no point in wasting time retesting this
app of dubious reputation that will soon be unavailable except at a
dubious download source by a site that doesn't use a site cert.
On Sat, 7/19/2025 11:20 AM, Roger Mills wrote:
On 19/07/2025 14:30, Carlos E.R. wrote:
On 2025-07-19 14:07, Paul wrote:
You could set up FTP on the computer end, to give the various
phone methods another "push" option. Maybe a Wifi protocol would
have slightly better performance than the USB2 (and mainly because
"not using MTP", not just because the link runs at a different speed). >>>> File Sharing might work. FTP might work.
So do you know a good ftp or sftp android app that actually works?
I have been using the FTP server within the ES File Explorer app for many years, and it works fine. I use AceFTP 2 as the FTP client on my PC (simply because it came free on the cover disk of a PC magazine many years ago) but any other FTP client should work.
The process is this:
Turn on ES File Exlorer on the phone
Select 'View on PC'
Tap TURN ON
This turns on the server and displays the IP address and port at which the PC's FTP client needs to be pointed
Run the FTP client on the PC
Point it at the address/port displayed on the phone (You can save this for future use)
Click on CONNECT
The connection is made (using WiFi - no cables), and two explorer-type windows are displayed on the PC
Navigate to where the files are on the phone, and to where you want them to be on the PC
Using the right and left arrows displayed on the PC (in Ace FTP, but other clients will have the equivalent) you can copy files in either direction between the two devices. [This means that you drive everything from the PC end, which is far simpler than having to do it on the phone].
[The description of the process (above) looks far more complicated than it actually is!]
NOTE: Until a few years ago, you could install ES File Explorer from Play Store, but it has now been removed due to some alleged security issue - so it has to be side-loaded. I've done this on several Android devices, and have never experienced any issues. If you search for ES File Exploreer in Play Store, it will offer you EX File Explorer, which looks similar but is *not* the same.
With FTP, you can push or pull. Considering the potential asymmetry
of the capabilities of the two OSes, you will likely have to
look at both options before deciding what to do. (I was thinking
more along the lines of Android Client, and Windows FTP server.)
The obvious way would be by USB cable, such that the phone appears as a "pseudo disk drive" in Windows Explorer and files can be selected for copying/moving. I know about the various USB modes: "Transferring files/Android AUto", "USB tethering", "MIDI", "Transferring images", "Charging phone only". Of these, only the two "Transferring" options
would seem to be relevant. "Transferring photo" only shows the DCIM
folder; "Transferring files" also shows Android/media/com.whatsapp/WhatsApp/Media/Whatsapp Images.
However Windows 10 (unlike Windows 7) seems to crash Explorer as it is gradually transferring the list of files (not the files themselves) in a selected folder (eg DCIM) order to populate the Explorer window so files
can be selected.
On Win 7, even a folder with a large number of files (photos), as seen
by Windows Explorer, gradually (slowly!) populates with filenames/icons
and then allows them to be selected and copied.
Unfortunately this phone only has internal storage, so it's not even possible to copy files to Micro SD card in the phone and then remove it
and put it in a card reader on the PC.
On 19/07/2025 20:05, Paul wrote:
With FTP, you can push or pull. Considering the potential asymmetry
of the capabilities of the two OSes, you will likely have to
look at both options before deciding what to do. (I was thinking
more along the lines of Android Client, and Windows FTP server.)
Considering that the user interface is on the *client*, it's far
easier if this is the PC. You don't have to touch the phone once you've turned on the server.
put "|dd if=/dev/sda bs=73728" sda
NY <me@privacy.net> wrote:
[...]
Unfortunately this phone only has internal storage, so it's not even
possible to copy files to Micro SD card in the phone and then remove it
and put it in a card reader on the PC.
As others have mentioned, just plug in a compatible [1] USB memory-
stick (might need an adapter) and copy the photos to the stick. There
are also USB card-readers for a SD-card or MicroSD-card, which can do a similar thing.
Alternatively, use the Cx File Explorer method which Arno mentioned to
copy the photos to a share on the Windows PC.
[...]
[1] The stick shoould be (Android) 'OTG' (On-The-Go) compatible. Most
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..
The phone on the other hand, does seem to have some clients
that can handle FTP, and without pestering you constantly
for things to enter.
With FTP, you can push or pull. Considering the potential asymmetry
of the capabilities of the two OSes, you will likely have to
look at both options before deciding what to do. (I was thinking
more along the lines of Android Client, and Windows FTP server.)
Considering that the user interface is on the *client*, it's far easier
if this is the PC. You don't have to touch the phone once you've turned
on the server.
On Sun, 7/20/2025 9:16 AM, Frank Slootweg wrote:
NY <me@privacy.net> wrote:
[...]
Unfortunately this phone only has internal storage, so it's not even
possible to copy files to Micro SD card in the phone and then remove it >> and put it in a card reader on the PC.
As others have mentioned, just plug in a compatible [1] USB memory-
stick (might need an adapter) and copy the photos to the stick. There
are also USB card-readers for a SD-card or MicroSD-card, which can do a similar thing.
Alternatively, use the Cx File Explorer method which Arno mentioned to copy the photos to a share on the Windows PC.
[...]
[1] The stick shoould be (Android) 'OTG' (On-The-Go) compatible. Most
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.
USB sticks fail. USB sticks run slow. Nobody wants to spend big money
on a "real" USB stick. (My computer store, no longer stocks anything
but schlock. Cruser Glide, in a USB3 world.) And the phone likely
can't run fast enough, to get the value from a "real" USB stick.
# Internal SSD arch, USB stick. Maybe 600-700MB/sec.
# Likely TLC inside, with SLC cache and it slows down after a while.
# Yes, it gets warm. Lots of this stuff should use metal casings.
"Patriot Supersonic Rage Prime USB 3.2 Gen 2 Flash Drive - 1TB - PEF1TBRPMW32U"
https://www.amazon.ca/Patriot-Supersonic-Prime-Flash-Drive/dp/B095HZ2S8B
I don't know if there is a USB-C version of that, there might be.
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 <nospam@needed.invalid> wrote:
On Sun, 7/20/2025 9:16 AM, Frank Slootweg wrote:
NY <me@privacy.net> wrote:
[...]
Unfortunately this phone only has internal storage, so it's not even
possible to copy files to Micro SD card in the phone and then remove it >>>> and put it in a card reader on the PC.
As others have mentioned, just plug in a compatible [1] USB memory-
stick (might need an adapter) and copy the photos to the stick. There
are also USB card-readers for a SD-card or MicroSD-card, which can do a
similar thing.
Alternatively, use the Cx File Explorer method which Arno mentioned to >>> copy the photos to a share on the Windows PC.
[...]
[1] The stick shoould be (Android) 'OTG' (On-The-Go) compatible. Most
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.
USB sticks fail. USB sticks run slow. Nobody wants to spend big money
on a "real" USB stick. (My computer store, no longer stocks anything
but schlock. Cruser Glide, in a USB3 world.) And the phone likely
can't run fast enough, to get the value from a "real" USB stick.
I don't share your pessimism. I've had only one USB stick fail. It was
a 'no-brand' one (brand of a local drugstore). As to slow, there are USB 3.<whatever> ones and the phone is probably the same.
# Internal SSD arch, USB stick. Maybe 600-700MB/sec.
# Likely TLC inside, with SLC cache and it slows down after a while.
# Yes, it gets warm. Lots of this stuff should use metal casings.
"Patriot Supersonic Rage Prime USB 3.2 Gen 2 Flash Drive - 1TB - PEF1TBRPMW32U"
https://www.amazon.ca/Patriot-Supersonic-Prime-Flash-Drive/dp/B095HZ2S8B
I don't know if there is a USB-C version of that, there might be.
I'm quite sure 'NY' won't need a 1TB one. The phone probably has 128GB
or less, maybe just 64GB or even just 32MB.
Trust me/'us', this stuff *does* work.
[...]
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?
Roger Mills has the right idea, where, at least for Android, you *never*
have to touch the actual phone once you "mirror" that phone onto the PC.
The OP's mother wants her photos which are located in ONE folder (DCIM). Connect a USB-C hard drive to the phone and copy the one folder. Then
connect it to the PC and copy them there. This way there's a copy on the
PC /and/ a backup on the hard drive. Two birds with one stone.
As for WhatsApp media: install WhatsApp Desktop and copy the Media
contents to the PC without even connecting the phone.
Come on, people: KISS!
On Sun, 7/20/2025 9:16 AM, Frank Slootweg wrote:
NY <me@privacy.net> wrote:
[...]
Unfortunately this phone only has internal storage, so it's not even
possible to copy files to Micro SD card in the phone and then remove it >>> and put it in a card reader on the PC.
As others have mentioned, just plug in a compatible [1] USB memory-
stick (might need an adapter) and copy the photos to the stick. There
are also USB card-readers for a SD-card or MicroSD-card, which can do a
similar thing.
Alternatively, use the Cx File Explorer method which Arno mentioned to
copy the photos to a share on the Windows PC.
[...]
[1] The stick shoould be (Android) 'OTG' (On-The-Go) compatible. Most
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.
USB sticks fail. USB sticks run slow. Nobody wants to spend big money
on a "real" USB stick. (My computer store, no longer stocks anything
but schlock. Cruser Glide, in a USB3 world.) And the phone likely
can't run fast enough, to get the value from a "real" USB stick.
FTP, while an ancient protocol, and as long as it is configured
by someone who cares about what they're doing, it could behave
itself better than some other things. Our modern technical world
seems to specialize in "crap". The simpler the transfer protocol
is, the better. With an ADB bus serial connection and Kermit,
I bet you could perform wonders :-) And you'd be doing that, when
the computer name refuses to show up in the file sharing dialog
on the client software.
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
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.)
My personal solution:
FolderSync with automatic uploading of all photos to a self-hosted
NextCloud server which is automatically synced with my computers. Works
like a charm. No, not a solution for everyone, but possible.
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.
Paul, 2025-07-20 17:35:
On Sun, 7/20/2025 9:16 AM, Frank Slootweg wrote:
[...]
FTP, while an ancient protocol, and as long as it is configured
by someone who cares about what they're doing, it could behave
itself better than some other things. Our modern technical world
seems to specialize in "crap". The simpler the transfer protocol
is, the better. With an ADB bus serial connection and Kermit,
I bet you could perform wonders :-) And you'd be doing that, when
the computer name refuses to show up in the file sharing dialog
on the client software.
FileZilla works quite well with Cx File Explorer as server:
<https://filezilla-project.org/download.php?type=client>
So first enable FTP in Cx File Explorer and then connect to the
displayed IP address and port - works fine whenever I have no other
choice and I am in a trusted network of course.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,064 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 146:29:55 |
| Calls: | 13,691 |
| Calls today: | 1 |
| Files: | 186,935 |
| D/L today: |
23 files (2,078K bytes) |
| Messages: | 2,410,869 |
