Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #183315 > unrolled thread

Tutorial: How to send files between Windows & iOS over the LAN using LocalSend

Back to article view | Back to alt.comp.os.windows-10

Contents

  Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-07 09:19 +0000
    Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend wasbit <wasbit@REMOVEhotmail.com> - 2025-04-07 10:43 +0100
      Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-07 10:29 +0000
        Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-07 11:20 +0000
          Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Graham J <nobody@nowhere.co.uk> - 2025-04-07 13:29 +0100
            Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-07 12:57 +0000
              Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Paul <nospam@needed.invalid> - 2025-04-07 14:49 -0400
                Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-07 21:25 +0000
            Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Kash Patel <kash.patel@fbi.gov> - 2025-04-07 13:30 +0000
            Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Eli the Bearded <*@eli.users.panix.com> - 2025-04-07 20:18 +0000
    Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend wasbit <wasbit@REMOVEhotmail.com> - 2025-04-08 16:46 +0100
      Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-08 21:24 +0000
    Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-13 05:24 +0000
      Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Alan <nuh-uh@nope.com> - 2025-04-12 23:15 -0700
        Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend david <this@is.invalid> - 2025-04-13 01:00 -0600
          Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Chris <ithinkiam@gmail.com> - 2025-04-13 07:19 +0000
          Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Alan <nuh-uh@nope.com> - 2025-04-13 00:43 -0700
      Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-04-14 19:10 +0000
        Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Marion <marion@facts.com> - 2025-04-15 17:21 +0000
          Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Alan <nuh-uh@nope.com> - 2025-04-15 10:34 -0700
          Re: Tutorial: How to send files between Windows & iOS over the LAN using LocalSend Alan <nuh-uh@nope.com> - 2025-04-17 16:11 -0700

Page 1 of 2  [1] 2  Next page →

#183315 — Tutorial: How to send files between Windows & iOS over the LAN using LocalSend

Tutorial: How to send files between Windows & iOS over the LAN using LocalSend.

  LocalSend is a free, open-source application for all common OS platforms.
  LocalSend uses HTTPS to transfer files between the OS platforms.
  LocalSend does not need to use the Internet to transfer files.
  LocalSend uses only the local Wi-Fi (LAN) network.
  LocalSend must be installed on both the sending and receiving devices.
  Both sending & receiving devices must be on the same network.
  LocalSend does not require creating any online accounts or logins.
  LocalSend bypasses Apple's arbitrary file-transfer restrictions.
  There is no need for iTunes, iCloud, Apple Mobile Devices, etc.
 
A. Install LocalSend on all devices you wish to transfer files between.
   <https://localsend.org/download>
   For the LocalSend Windows portable zip archive:
   <https://localsend.org/download?os=windows>
   <https://github.com/localsend/localsend/releases/download/v1.17.0/LocalSend-1.17.0-windows-x86-64.zip>
    Name: LocalSend-1.17.0-windows-x86-64.zip
    Size: 18766124 bytes (17 MiB)
    SHA256: A4FFB41FCBC3BD0F2F0CBD30B62A58D9A478EAF1DA63EB410886886064ABE70C
   This extracts to "LocalSend-1.17.0-windows-x86-64" which contains:
    Name: localsend_app.exe
    Size: 161280 bytes (157 KiB)
    SHA256: 9AA728853377643FBB13368E2A52ED816A448E0B5F28404AFB2154D2068F007A
   For the LocalSend iOS IPA: 
   <https://apps.apple.com/us/app/localsend/id1661733229>
   For the LocalSend Android APK:
   <https://github.com/localsend/localsend/releases/download/v1.17.0/LocalSend-1.17.0-android-arm64v8.apk>
   Name: LocalSend-1.17.0-android-arm64v8.apk
   Size: 17491108 bytes (16 MiB)
   SHA256: 2C7F5FD4872DA25115BB8E5E62F92DE94DDA47B0F249FF387AC667B13871DC3E

Step by step tutorial that I tested so that you can use it with confidence.
1. Both the PC & iOS device need to be on the same local network
   To find what IP address the iOS device is, go to "Settings".
   Then click on the Wi-Fi connection in the left top pane.
   Press the circled (i) for information about that connection.
   Scroll down to the "IPV4 Address" section & note the "IP Address".
   To ping that IP address from the Windows PC, use "Win+R > cmd"
   C:\> ping 192.168.1.3
2. LocalSend must be open & running on Windows & iOS
   On Windows, you'll get a firewall message when you first run LocalSend.
   On iOS, you'll get a popup when you first run LocalSend saying...
    "LocalSend" would like to find and connect to devices 
     on your local network. The app uses the local network 
     to find and connect to nearby devices."
         [Don't Allow] [Allow]
   Windows Firewall has to allow LocalSend on Private Networks (at least).
   a. Windows Defender Firewall: Win+R > firewall.cpl
      or Windows Firewall with Advanced Security: Win+R > wf.msc
   b. Tap "Allow an app or feature through Windows Firewall"
      A new window will open, titled "Allowed apps and features"
   c. Scroll through the list to find "LocalSend" & set it to
      LocalSend [x]Private [_]Public
3. On Windows LocalSend, press the "Send" button.
4. On Windows LocalSend, select the "File" selection.
5. On Windows, browser to the file you want to send to iOS.
6. On Windows LocalSend, in the "Nearby devices" section select the iPad.
7. The Windows LocalSend will say "Waiting for response..."
8. On the iPad LocalSend, it says Windows wants to send you a file.
   [Options][Decline][Accept]
9. Pressing "Options" gives you three choices:
    a. Save to folder = LocalSend folder
    b. Save media to gallery = on/off (default is "on")
    c. Files
10. Leaving it at the default, I pressed the "Accept" button.
11. The iOS LocalSend said "LocalSend would like to add to your photos. 
    The app saves received media to the photo library. 
    [Don't Allow][OK]
12. The iOS LocalSend will say "Saved in Photos".

Note that it works both ways, as Paul said it should. :)
By default, from iOS to Windows is saved in "C:\Users\you\Downloads".

As always, please improve so that billions of people benefit from 
every post you make, which is why we all should learn from each other.
-- 
As folks already know, Apple products don't work in the real world because
Apple restricts people to the subterranean cave called the ecosystem; but
there are ways to tunnel from Apple's ecosystem to get into the real world.

[toc] | [next] | [standalone]

#183317

On 07/04/2025 10:19, Marion wrote:
> Tutorial: How to send files between Windows & iOS over the LAN using LocalSend.
> 
>    LocalSend is a free, open-source application for all common OS platforms.
>    LocalSend uses HTTPS to transfer files between the OS platforms.
>    LocalSend does not need to use the Internet to transfer files.
>    LocalSend uses only the local Wi-Fi (LAN) network.
>    LocalSend must be installed on both the sending and receiving devices.
>    Both sending & receiving devices must be on the same network.
>    LocalSend does not require creating any online accounts or logins.
>    LocalSend bypasses Apple's arbitrary file-transfer restrictions.
>    There is no need for iTunes, iCloud, Apple Mobile Devices, etc.
>   
> A. Install LocalSend on all devices you wish to transfer files between.
>     <https://localsend.org/download>
>     For the LocalSend Windows portable zip archive:
>     <https://localsend.org/download?os=windows>
>     <https://github.com/localsend/localsend/releases/download/v1.17.0/LocalSend-1.17.0-windows-x86-64.zip>
>      Name: LocalSend-1.17.0-windows-x86-64.zip
>      Size: 18766124 bytes (17 MiB)
>      SHA256: A4FFB41FCBC3BD0F2F0CBD30B62A58D9A478EAF1DA63EB410886886064ABE70C
>     This extracts to "LocalSend-1.17.0-windows-x86-64" which contains:
>      Name: localsend_app.exe
>      Size: 161280 bytes (157 KiB)
>      SHA256: 9AA728853377643FBB13368E2A52ED816A448E0B5F28404AFB2154D2068F007A
>     For the LocalSend iOS IPA:
>     <https://apps.apple.com/us/app/localsend/id1661733229>
>     For the LocalSend Android APK:
>     <https://github.com/localsend/localsend/releases/download/v1.17.0/LocalSend-1.17.0-android-arm64v8.apk>
>     Name: LocalSend-1.17.0-android-arm64v8.apk
>     Size: 17491108 bytes (16 MiB)
>     SHA256: 2C7F5FD4872DA25115BB8E5E62F92DE94DDA47B0F249FF387AC667B13871DC3E
> 
> Step by step tutorial that I tested so that you can use it with confidence.
> 1. Both the PC & iOS device need to be on the same local network
>     To find what IP address the iOS device is, go to "Settings".
>     Then click on the Wi-Fi connection in the left top pane.
>     Press the circled (i) for information about that connection.
>     Scroll down to the "IPV4 Address" section & note the "IP Address".
>     To ping that IP address from the Windows PC, use "Win+R > cmd"
>     C:\> ping 192.168.1.3
> 2. LocalSend must be open & running on Windows & iOS
>     On Windows, you'll get a firewall message when you first run LocalSend.
>     On iOS, you'll get a popup when you first run LocalSend saying...
>      "LocalSend" would like to find and connect to devices
>       on your local network. The app uses the local network
>       to find and connect to nearby devices."
>           [Don't Allow] [Allow]
>     Windows Firewall has to allow LocalSend on Private Networks (at least).
>     a. Windows Defender Firewall: Win+R > firewall.cpl
>        or Windows Firewall with Advanced Security: Win+R > wf.msc
>     b. Tap "Allow an app or feature through Windows Firewall"
>        A new window will open, titled "Allowed apps and features"
>     c. Scroll through the list to find "LocalSend" & set it to
>        LocalSend [x]Private [_]Public
> 3. On Windows LocalSend, press the "Send" button.
> 4. On Windows LocalSend, select the "File" selection.
> 5. On Windows, browser to the file you want to send to iOS.
> 6. On Windows LocalSend, in the "Nearby devices" section select the iPad.
> 7. The Windows LocalSend will say "Waiting for response..."
> 8. On the iPad LocalSend, it says Windows wants to send you a file.
>     [Options][Decline][Accept]
> 9. Pressing "Options" gives you three choices:
>      a. Save to folder = LocalSend folder
>      b. Save media to gallery = on/off (default is "on")
>      c. Files
> 10. Leaving it at the default, I pressed the "Accept" button.
> 11. The iOS LocalSend said "LocalSend would like to add to your photos.
>      The app saves received media to the photo library.
>      [Don't Allow][OK]
> 12. The iOS LocalSend will say "Saved in Photos".
> 
> Note that it works both ways, as Paul said it should. :)
> By default, from iOS to Windows is saved in "C:\Users\you\Downloads".
> 
> As always, please improve so that billions of people benefit from
> every post you make, which is why we all should learn from each other.
> 

Does Localsend bypass the need to have to sign in to an MS account?


-- 
Regards
wasbit

[toc] | [prev] | [next] | [standalone]

#183319

On Mon, 7 Apr 2025 10:43:56 +0100, wasbit wrote :


> Does Localsend bypass the need to have to sign in to an MS account?

Hi wasbit,
You've helped me a lot over the years, so I'd love to be able to help you.
I'm not sure why you asked that, so there must be something I'm missing. 

Paul turned me on to LocalSend earlier today, so there could be stuff I
don't know about it but as far as I'm aware, it's open source software.

AFAIK, no account anywhere is needed to install & run & use LocalSend on
Windows and on Linux but you do need an account to install it on iOS.

Even on Android, you do not need to have a Google Account to install the
LocalSend APK since you can download APKs directly from the link provided.

The only platform that requires that mothership account is Apple's iOS.

Once you have the zip file unpacked on Windows, there are no limitations
that I am aware of (e.g., file type, count, size, platform or direction).

In the words of the child-like Apple trolls, it's just one step: :)
 1. Run LocalSend

Obviously it's more steps than that, but essentially what I did was
download the zip file, and then I unzipped it directly to my app folder:
 C:\apps\servers\localsend\localsend.exe
Then, on Windows, I added a link to my taskbar menu in the same location:
 C:\menus\servers\localsend.lnk

Note: I never use plurals; but I added plurals there for readability.

The interesting thing is that this LocalSend program allows you to send
bi-directionally files & folders (and even text messages) between
platforms, so, for example, you can text your wife's iPad from your PC.

Note that you don't really need this LocalSend tool for bidirectional file
transfer between the normal operating systems, since that already works.

You need this tool for bidirectional file/folder transfer when Apple's
operating systems (particularly the brain dead iOS OS) are involved.

Apple designed iOS to be a dumb terminal in that iOS doesn't do anything
without going through Apple's Cupertino maxtrix servers most of the time.

So, while Windows doesn't need a login account on the mothership servers,
iOS does need you to have an Apple App Store account on Apple's servers in
order to install the LocalSend IPA.

Worse, Apple is the only operating system vendor who inserts a unique
tracking ID which is unique to you & to you alone, into that IPA installer.

That way Apple can track everything you do with that LocalSend application.
Back to your question, AFAIK, a M$ account is never needed for LocalSend.
-- 
The best way to visualize Apple's ecosystem is to think of it as a 
subterranean cavern with passageways to itself but none to the real world.

[toc] | [prev] | [next] | [standalone]

#183321

On Mon, 7 Apr 2025 10:29:42 -0000 (UTC), Marion wrote :


>> Does Localsend bypass the need to have to sign in to an MS account?
> 
> I'm not sure why you asked that, so there must be something I'm missing.

Oh. I saw your response to nospam (aka Tyrone) in another thread, where I
realize where you're coming from now with respect to the login account.

Yes. LocalSend bypasses the need to have a *password* on an *account* that
SMB is using for the local share (unless you drop to inscure SMB 1.0).

I'm no expert on SMB, but I never could get SMB to work on "my" systems,
none of which have passwords (as I don't live in the slums). 

So the suggestion by nospam (aka Tyrone) to use the Files app, won't work
because the Files app acts like an SMB client, which has to connect to the
Windows SMB server, which will require an account on that SMB server, and,
that account must have a password (for all newer levels of SMB) AFAIK.

So, to answer the question about LocalSend, "yes", LocalSend has no need to
interact at all with the local account (or any other account) on the PC.

Q: Does SMB between iOS & Windows require an account with a password?
A: Yes. Unfortunately.

Q: Does LocalSend between iOS & Windows require an account with a password?
A: No. Thankfully.
-- 
Note that I only heard of LocalSend today from Paul, so I could be wrong.

As far as I know, LocalSend automatically acts as an HTTPS server when it's
sending files, and it acts as an HTTPS server when it's receiving files.

[toc] | [prev] | [next] | [standalone]

#183322

Why not attach the file to an email and send it to the iOS device?


-- 
Graham J

[toc] | [prev] | [next] | [standalone]

#183324

On Mon, 7 Apr 2025 13:29:34 +0100, Graham J wrote :


> Why not attach the file to an email and send it to the iOS device?

For a single 5MB photo? Sure, email is no problem. Except that it is.

What if the file is a feature-length movie? Or even a dozen of them?
With LocalSend, you can attach an entire folder of movies.

I'm well aware that what most people would do instead of using something
elegant like LocalSend appears to be, is they'd pay for cloud storage.

And that's fine - except that's exactly why companies like Apple have a
strategy to limit your choices so that you feel you must buy that storage.

I get it that once you have already paid for cloud storage, then copying a
file from your PC to that cloud storage and then back to the iPad is easy.

But with LocalSend, you don't need 'no stinkin' cloud storage anymore. :)

[toc] | [prev] | [next] | [standalone]

#183333

On Mon, 4/7/2025 8:57 AM, Marion wrote:
> On Mon, 7 Apr 2025 13:29:34 +0100, Graham J wrote :
> 
> 
>> Why not attach the file to an email and send it to the iOS device?
> 
> For a single 5MB photo? Sure, email is no problem. Except that it is.
> 
> What if the file is a feature-length movie? Or even a dozen of them?
> With LocalSend, you can attach an entire folder of movies.
> 
> I'm well aware that what most people would do instead of using something
> elegant like LocalSend appears to be, is they'd pay for cloud storage.
> 
> And that's fine - except that's exactly why companies like Apple have a
> strategy to limit your choices so that you feel you must buy that storage.
> 
> I get it that once you have already paid for cloud storage, then copying a
> file from your PC to that cloud storage and then back to the iPad is easy.
> 
> But with LocalSend, you don't need 'no stinkin' cloud storage anymore. :)
> 

You can set up an email server in your room.
I had one here, but the certificate broke, and
after several attempts, I can't self sign one
that all the software "likes" at the same time.

But with the LocalSend set up, you are likely
done at this point.

   Paul

[toc] | [prev] | [next] | [standalone]

#183336

On Mon, 7 Apr 2025 14:49:49 -0400, Paul wrote :


> You can set up an email server in your room.
> I had one here, but the certificate broke, and
> after several attempts, I can't self sign one
> that all the software "likes" at the same time.

I agree. In the words of the infamous Apple trolls, 
setting up your own email server is only a single step.
  1. Set up Email server

Just like using iTunes is a single step to Apple trolls.
  1. Use iTunes

And just as using Files with SMB (which doesn't work) is.
  1. Use Files 

The Apple trolls think if you write a tutorial that includes the actual
steps, then it's "more complicated" than their single step above is.

It's odd how these strange Apple trolls think.
Oddly, all their "arguments" are that of kindergarten children. 

They count the punctuation in a tutorial, and if it has grammatically
correct sentences, then they instantly declare it's too complicated
compared to their "single step solution", from the likes of Apple.

> But with the LocalSend set up, you are likely
> done at this point.

I love two things, no, three things about you Paul.

1. I love your humor. You say it so matter of factly', 
   but you know it's humorous when you say it. I love it.

2. The second thing I love about you is you are purposefully
   helpful, which is *different* from what these Apple trolls are.

3. And the third thing of two things I love about you is
   you are experienced & knowledgeable about that which you speak.

Is that four things?

PS: The 'two' things I've never set up are my own email server, my own VPN
server, my own WebDAV server, and my own Usenet server. Frank Slootweg
has me beat on the latter - but I suspect most have not done those things.

[toc] | [prev] | [next] | [standalone]

#183325

On 07/04/2025 13:29, Graham J wrote:
> Why not attach the file to an email and send it to the iOS device?
 >
 >

Because it's rocket science to Arlen AKA Marion {Marion 
<marion@facts.com>} who is a known nym-shifter and child molester. He 
frequents local YMCAs to find young boys.

Has he still not introduced to his child porn website? You need to ask 
him about it. Most sensible people here are ignoring him.

Useless newsgroups removed from this reply to reduce unnecessary topics.

[toc] | [prev] | [next] | [standalone]

#183334

In rec.photo.digital, Graham J  <nobody@nowhere.co.uk> wrote:
> Why not attach the file to an email and send it to the iOS device?

I use Localsend between two Android devices somewhat often. The
scenario:

Device One has a good camera, but no sim card.
Device Two has a terrible camera, but more storage, a sim card, and
physical keyboard.
Both have wifi.

Daily, I only use device Two and suffer the lower quality photos if I
take pictures. On vacation, I bring both devices and use device One for
photos, then at end of day transfer all photos and videos for the day
to device Two. 

On my more recent vacation that was about a gigabyte of files per day.
About five to ten minutes selecting what to copy and another ten minutes
copying. Then on device Two, I would properly tag the photos, because
doing that with a keyboard is much nicer than with a touch screen.


At the end of the trip, after backing up device Two, I delete the
pictures from device One (where storage is tight).

Most people don't realy tag their photos and at most let the OS guess
some tags, but I hold much higher metadata standards than I expect any
AI provided by the OS will achieve. (A lake is different than an ocean
is different than a river is different than a canal and a picture of
water will get tagged "water" and the type of water, and sometimes the
name of the water.)

Issues:

Picking the files to send is a weak point in Localsend.

Plugging in a device to charge *during* transfer also was breaking
LocalSend. Plug in before starting the transfer is not an issue. It
seems to be related to start / stop charging only.

Some wifi routers block Localsend. Devices can't see each other and
manually specifying the IP address (which is a pain in the ass in
Localsend) didn't help. This is an issue when relying on hotel or
whatever wifi instead of something you control yourself. It seems
to be a firewall between devices on the network. You should be able to
get around this with an ad hoc network, but I haven't tried.

Elijah
------
device One has 64 gigs, device Two has well over a terabyte

[toc] | [prev] | [next] | [standalone]

#183366

On 07/04/2025 10:19, Marion wrote:
> Tutorial: How to send files between Windows & iOS over the LAN using LocalSend.
> 
>    LocalSend is a free, open-source application for all common OS platforms.
>    LocalSend uses HTTPS to transfer files between the OS platforms.
>    LocalSend does not need to use the Internet to transfer files.
>    LocalSend uses only the local Wi-Fi (LAN) network.
>    LocalSend must be installed on both the sending and receiving devices.
>    Both sending & receiving devices must be on the same network.
>    LocalSend does not require creating any online accounts or logins.
>    LocalSend bypasses Apple's arbitrary file-transfer restrictions.
>    There is no need for iTunes, iCloud, Apple Mobile Devices, etc.
>   
> A. Install LocalSend on all devices you wish to transfer files between.
>     <https://localsend.org/download>
>     For the LocalSend Windows portable zip archive:
>     <https://localsend.org/download?os=windows>
>     <https://github.com/localsend/localsend/releases/download/v1.17.0/LocalSend-1.17.0-windows-x86-64.zip>
>      Name: LocalSend-1.17.0-windows-x86-64.zip
>      Size: 18766124 bytes (17 MiB)
>      SHA256: A4FFB41FCBC3BD0F2F0CBD30B62A58D9A478EAF1DA63EB410886886064ABE70C
>     This extracts to "LocalSend-1.17.0-windows-x86-64" which contains:
>      Name: localsend_app.exe
>      Size: 161280 bytes (157 KiB)
>      SHA256: 9AA728853377643FBB13368E2A52ED816A448E0B5F28404AFB2154D2068F007A
>     For the LocalSend iOS IPA:
>     <https://apps.apple.com/us/app/localsend/id1661733229>
>     For the LocalSend Android APK:
>     <https://github.com/localsend/localsend/releases/download/v1.17.0/LocalSend-1.17.0-android-arm64v8.apk>
>     Name: LocalSend-1.17.0-android-arm64v8.apk
>     Size: 17491108 bytes (16 MiB)
>     SHA256: 2C7F5FD4872DA25115BB8E5E62F92DE94DDA47B0F249FF387AC667B13871DC3E
> 
> Step by step tutorial that I tested so that you can use it with confidence.
> 1. Both the PC & iOS device need to be on the same local network
>     To find what IP address the iOS device is, go to "Settings".
>     Then click on the Wi-Fi connection in the left top pane.
>     Press the circled (i) for information about that connection.
>     Scroll down to the "IPV4 Address" section & note the "IP Address".
>     To ping that IP address from the Windows PC, use "Win+R > cmd"
>     C:\> ping 192.168.1.3
> 2. LocalSend must be open & running on Windows & iOS
>     On Windows, you'll get a firewall message when you first run LocalSend.
>     On iOS, you'll get a popup when you first run LocalSend saying...
>      "LocalSend" would like to find and connect to devices
>       on your local network. The app uses the local network
>       to find and connect to nearby devices."
>           [Don't Allow] [Allow]
>     Windows Firewall has to allow LocalSend on Private Networks (at least).
>     a. Windows Defender Firewall: Win+R > firewall.cpl
>        or Windows Firewall with Advanced Security: Win+R > wf.msc
>     b. Tap "Allow an app or feature through Windows Firewall"
>        A new window will open, titled "Allowed apps and features"
>     c. Scroll through the list to find "LocalSend" & set it to
>        LocalSend [x]Private [_]Public
> 3. On Windows LocalSend, press the "Send" button.
> 4. On Windows LocalSend, select the "File" selection.
> 5. On Windows, browser to the file you want to send to iOS.
> 6. On Windows LocalSend, in the "Nearby devices" section select the iPad.
> 7. The Windows LocalSend will say "Waiting for response..."
> 8. On the iPad LocalSend, it says Windows wants to send you a file.
>     [Options][Decline][Accept]
> 9. Pressing "Options" gives you three choices:
>      a. Save to folder = LocalSend folder
>      b. Save media to gallery = on/off (default is "on")
>      c. Files
> 10. Leaving it at the default, I pressed the "Accept" button.
> 11. The iOS LocalSend said "LocalSend would like to add to your photos.
>      The app saves received media to the photo library.
>      [Don't Allow][OK]
> 12. The iOS LocalSend will say "Saved in Photos".
> 
> Note that it works both ways, as Paul said it should. :)
> By default, from iOS to Windows is saved in "C:\Users\you\Downloads".
> 
> As always, please improve so that billions of people benefit from
> every post you make, which is why we all should learn from each other.
> 

I am going to reply to all here with thanks.

I use a Windows 8.1 Pro local account with no login. I don't have a 
mobile phone.
I get PCs, laptops & sometimes phones brought to me with either faults 
or requests of 'how do I?', & I do what I can with no charge.

Windows doesn't allow file sharing (since Windows 8) without logging in.
However files can be transferred from an iphone to Windows (local 
account/no log in) via USB but not from Windows to the iphone.
  Drag & drop doesn't work.
  Copy/Move doesn't work
  Send-to in the context menu shows but doesn't work

Photos on the iphone will open with Irfanview in Windows
Files can be deleted from an iphone if they can be seen in Windows.

An MS account is required to download apps from the App Store.
A credit card is required to set up an account to download apps to an 
iphone & often the phone owner doesn't want to give me or Apple that 
information.

As with most problems I get, the phone owner doesn't want to spend a lot 
of time whilst I diagnose/sort problems.
I really need the phone owner to either be in attendance or give me 
their passwords etc.

I have not yet been asked to sort out an Android phone with a file 
sharing problem however I do have an Android tablet but have never 
needed to transfer files to or from Windows.

Most of the answers presume I own the hardware & can do what I like with 
no time limits, but for me that's not the case.


-- 
Regards
wasbit

[toc] | [prev] | [next] | [standalone]

#183389

On Tue, 8 Apr 2025 16:46:09 +0100, wasbit wrote :


> I am going to reply to all here with thanks.
> 
> I use a Windows 8.1 Pro local account with no login. I don't have a 
> mobile phone.
> I get PCs, laptops & sometimes phones brought to me with either faults 
> or requests of 'how do I?', & I do what I can with no charge.
> 
> Windows doesn't allow file sharing (since Windows 8) without logging in.
> However files can be transferred from an iphone to Windows (local 
> account/no log in) via USB but not from Windows to the iphone.
>   Drag & drop doesn't work.
>   Copy/Move doesn't work
>   Send-to in the context menu shows but doesn't work
> 
> Photos on the iphone will open with Irfanview in Windows
> Files can be deleted from an iphone if they can be seen in Windows.
> 
> An MS account is required to download apps from the App Store.
> A credit card is required to set up an account to download apps to an 
> iphone & often the phone owner doesn't want to give me or Apple that 
> information.
> 
> As with most problems I get, the phone owner doesn't want to spend a lot 
> of time whilst I diagnose/sort problems.
> I really need the phone owner to either be in attendance or give me 
> their passwords etc.
> 
> I have not yet been asked to sort out an Android phone with a file 
> sharing problem however I do have an Android tablet but have never 
> needed to transfer files to or from Windows.
> 
> Most of the answers presume I own the hardware & can do what I like with 
> no time limits, but for me that's not the case.

Hi wasbit,

Thanks for that update and your specific use model, where I concur with
(almost) everything you said (I think you have a thinko on the MS account
where you actually meant an Apple Account - to install software on iOS).

I have tons of Apple devices, so I concur with the problem set you feel,
which is that there's no problem file sharing with Android, but with iOS, 
all you can easily do is copy from the iOS device over to the Windows PC.

But you can't go the other way (you can't easily copy to the iOS device).
Worse... much (much!) worse, you can't *install* apps on the iOS device.

You can't even copy installers (IPAs) from one iOS device to another like
you can easily do with Android (since Android always saves the installers).

And, as you've found out, SMB is a great answer except when it's not.

Effectively, for SMB you have to have an account on the PC with a password.
And even then, you have to deal with the crappy Windows "sharing" garbage.

When Paul suggested LocalSend, and when I tested it out, I was ecstatically
happy that LocalSend surmounted EVERY problem I'm listing above with iOS.

Since LocalSend works on all platforms, the only requirement is that your
customer is logged into the app store for iOS (since none of the other
platforms require a login account to the mothership to install LocalSend).

What's unique about iOS is it's the ONLY platform that requires that App
Store login (as even the Google Play Store doesn't require login accounts).

But if the customer is *already* logged into their iOS App Store account,
then you can install LocalSend on their device and then copy things over.

It's beautiful. The only other requirement is every device needs to be on
the same network. I'm not sure how that plays out in a corporate
environment, but on my home environment, as long as I could ping it on a
local address (e.g., 192.168.1.2), then LocalSend had no problem seeing it.

We all owe Paul thanks for finding LocalSend as a solution to the problem.
Finally, we tunnel out of iOS's subterranean ecosystem into the real world. 

Thanks for letting us know. Elijiah also has a great LocalSend use model
where he travels with two Android devices, one of which is a phone that
takes great photos and the other of which is, I think, a tablet which has
tons of storage. Each night he transfers the images taken during the day
from the phone with limited storage to the tablet with huge storage.

LocalSend allows device-to-device transfers which don't require the PC!
Paul saved us all, again!

[toc] | [prev] | [next] | [standalone]

#183604

Oh oh... there's another problem in iOS we didn't hit with photos.

You hit a *new* problem when you try to access a different file type.
In this case, the file type is an audio file.

 *LocalSend can't (directly) access that audio file on the iOS device!*

Here was what I needed to do:
A. I made an audio recording on iOS of a phone call (with permission).
B. I needed to transfer the 2-hour recording from iOS to Windows.
C. On Windows, I needed to reduce the file size to fit into WhatsApp.
D. Then I needed to transfer to Android to send over WhatsApp's dialer.

The problem is iOS prevents something that simple from ever being easy.

In summary, I want to transfer a specific 2-hour audio recording ("New
Recording 4") from the iOS native "Voice Memos" app to my Windows 10
machine using only my local network & without using the Internet so that I
can shrink it to below 64MB in order to send it via Android WhatsApp.

The key challenge is accessing the audio file which is ensconced deeply
within the sand boxed environment of the native Voice Memos app on iOS.

Unfortunately, iOS, by design, heavily restricts direct file system access
for user applications like Voice Memos. This means that LocalSend, or any
other app, typically cannot directly browse the internal storage of another
app to pick out a specific file like the audio recording "New Recording 4".

Here's the workaround I had to come up with to accomplish that simple task
of LocalSend being able to access the sandboxed Voice Memo audio file.

1. Make sure the Windows PC & iOS device are on the same local network.
2. Open the LocalSend app on the iPad & the LocalSend program on the PC.
3. Make sure they see each other inside of the respective LocalSend GUIs.
4. Open the native iOS Voice Memos app on your iPad.
5. Find the recording titled "New Recording 4" within the app.
6. Tap on the recording to select it.
7. Tap on the "Share" icon. 
8. In the Share Sheet tap about until you finally see "Save to Files".
9. Tap "Save to Files".
10. Choose a location within the "Files" app such as "On My iPad".
11. Then press at the top right the "Save" button to save it there.
12. Double check it worked by opening the iOS Files app to see it there.
13. When you tap on it, you'll see it's named "New Recording 4.m4a" 69.7MB.
14. On the iOS LocalSend left pane, tap the "Send" option.
15. You'd think an audio file would be under "Media" but Apple doesn't.
16. In the main pane, below "Selection," tap on "File".
17. This should open the iOS file browser interface.
18. Look for and tap on "On My iPad" within this file browser interface.
19. Tap on "New Recording 4.m4a" to select it (you may need to tap twice).
20. You will see a blue check mark inserted on the selected file.
21. In the top right of the iOS file browser, tap the "Open" button.
22. LocalSend transitions to a screen displaying discovered devices.
23. Tap on the name of your Windows 10 PC in the list of recipients.
24. The Windows LocalSend will say "iPad wants to send you a file".
25. Tap "Accept" on the Windows LocalSend GUI to receive that file.
26. The default will be "C:\Users\you\Downloads\New Recording 4.m4a".
27. The Windows LocalSend GUI will say "Finished".
28. Windows MPC-BE should play the Apple m4a file.

Voila! I successfully transferred a file out of the restrictive iOS
filespace to Windows. I then easily copied it over USB to the Android
sdcard to send via WhatsApp but WhatsApp has a 64MB file size limit.

So I had to lower the bitrate to shrink the file to send via WhatsApp.
 C:\> ffmpeg -i input.m4a -vn -acodec aac -q:a 0.5 output_aac_q0.5.m4a

That shrunk the 68MB 2-hour audio file down to about 40MB for WhatsApp.

Unfortunately that didn't change the metadata, so WhatsApp found the 40MB
file but it thought it was the same name as the original 68MB file.

So what I should have run is something like this to change metadata.
 C:\> ffmpeg -i input.m4a -vn -acodec aac -q:a 0.5 -metadata title="Our Convo" -metadata filename="our_convo.m4a" output_metadata.m4a
Or use MP3Tag on Windows:
 <https://www.mp3tag.de/en/>

[toc] | [prev] | [next] | [standalone]

#183605

On 2025-04-12 22:24, Marion wrote:
> Oh oh... there's another problem in iOS we didn't hit with photos.
> 
> You hit a *new* problem when you try to access a different file type.
> In this case, the file type is an audio file.
> 
>   *LocalSend can't (directly) access that audio file on the iOS device!*
> 
> Here was what I needed to do:
> A. I made an audio recording on iOS of a phone call (with permission).
> B. I needed to transfer the 2-hour recording from iOS to Windows.
> C. On Windows, I needed to reduce the file size to fit into WhatsApp.
> D. Then I needed to transfer to Android to send over WhatsApp's dialer.
> 
> The problem is iOS prevents something that simple from ever being easy.
> 
> In summary, I want to transfer a specific 2-hour audio recording ("New
> Recording 4") from the iOS native "Voice Memos" app to my Windows 10
> machine using only my local network & without using the Internet so that I
> can shrink it to below 64MB in order to send it via Android WhatsApp.
> 
> The key challenge is accessing the audio file which is ensconced deeply
> within the sand boxed environment of the native Voice Memos app on iOS.
> 
> Unfortunately, iOS, by design, heavily restricts direct file system access
> for user applications like Voice Memos. This means that LocalSend, or any
> other app, typically cannot directly browse the internal storage of another
> app to pick out a specific file like the audio recording "New Recording 4".
> 
> Here's the workaround I had to come up with to accomplish that simple task
> of LocalSend being able to access the sandboxed Voice Memo audio file.
> 
> 1. Make sure the Windows PC & iOS device are on the same local network.
> 2. Open the LocalSend app on the iPad & the LocalSend program on the PC.
> 3. Make sure they see each other inside of the respective LocalSend GUIs.
> 4. Open the native iOS Voice Memos app on your iPad.
> 5. Find the recording titled "New Recording 4" within the app.
> 6. Tap on the recording to select it.
> 7. Tap on the "Share" icon.
> 8. In the Share Sheet tap about until you finally see "Save to Files".
> 9. Tap "Save to Files".
> 10. Choose a location within the "Files" app such as "On My iPad".
> 11. Then press at the top right the "Save" button to save it there.
> 12. Double check it worked by opening the iOS Files app to see it there.
> 13. When you tap on it, you'll see it's named "New Recording 4.m4a" 69.7MB.
> 14. On the iOS LocalSend left pane, tap the "Send" option.
> 15. You'd think an audio file would be under "Media" but Apple doesn't.
> 16. In the main pane, below "Selection," tap on "File".
> 17. This should open the iOS file browser interface.
> 18. Look for and tap on "On My iPad" within this file browser interface.
> 19. Tap on "New Recording 4.m4a" to select it (you may need to tap twice).
> 20. You will see a blue check mark inserted on the selected file.
> 21. In the top right of the iOS file browser, tap the "Open" button.
> 22. LocalSend transitions to a screen displaying discovered devices.
> 23. Tap on the name of your Windows 10 PC in the list of recipients.
> 24. The Windows LocalSend will say "iPad wants to send you a file".
> 25. Tap "Accept" on the Windows LocalSend GUI to receive that file.
> 26. The default will be "C:\Users\you\Downloads\New Recording 4.m4a".
> 27. The Windows LocalSend GUI will say "Finished".
> 28. Windows MPC-BE should play the Apple m4a file.
> 
> Voila! I successfully transferred a file out of the restrictive iOS
> filespace to Windows. I then easily copied it over USB to the Android
> sdcard to send via WhatsApp but WhatsApp has a 64MB file size limit.
> 
> So I had to lower the bitrate to shrink the file to send via WhatsApp.
>   C:\> ffmpeg -i input.m4a -vn -acodec aac -q:a 0.5 output_aac_q0.5.m4a
> 
> That shrunk the 68MB 2-hour audio file down to about 40MB for WhatsApp.
> 
> Unfortunately that didn't change the metadata, so WhatsApp found the 40MB
> file but it thought it was the same name as the original 68MB file.
> 
> So what I should have run is something like this to change metadata.
>   C:\> ffmpeg -i input.m4a -vn -acodec aac -q:a 0.5 -metadata title="Our Convo" -metadata filename="our_convo.m4a" output_metadata.m4a
> Or use MP3Tag on Windows:
>   <https://www.mp3tag.de/en/>

Or just use the built-in SMB functionality of Windows and iOS.

[toc] | [prev] | [next] | [standalone]

#183606

Using <news:vtfkqb$28l2o$2@dont-email.me>, Alan wrote:

> Or just use the built-in SMB functionality of Windows and iOS.

Are you the guy who used the iCloud and claimed it was SMB you used?
Read what he wrote next time before you make a fool of yourself again.
The audio recording is locked inside the native iOS Voice Memos sandbox.
So you'd still have the same classic iOS sandbox problems no matter what.

[toc] | [prev] | [next] | [standalone]

#183607

david <this@is.invalid> wrote:
> Using <news:vtfkqb$28l2o$2@dont-email.me>, Alan wrote:
> 
>> Or just use the built-in SMB functionality of Windows and iOS.
> 
> Are you the guy who used the iCloud and claimed it was SMB you used?
> Read what he wrote next time before you make a fool of yourself again.
> The audio recording is locked inside the native iOS Voice Memos sandbox.
> So you'd still have the same classic iOS sandbox problems no matter what.

He means that from step 14 onwards there's no need for LocalSend. Arlen is
already in Files in step 13 so just use that app to do the transfer. 

[toc] | [prev] | [next] | [standalone]

#183609

On 2025-04-13 00:00, david wrote:
> Using <news:vtfkqb$28l2o$2@dont-email.me>, Alan wrote:
> 
>> Or just use the built-in SMB functionality of Windows and iOS.
> 
> Are you the guy who used the iCloud and claimed it was SMB you used?

I'm the guy who used a file on my iPhone and you assumed it was because
of iCloud...

> Read what he wrote next time before you make a fool of yourself
> again. The audio recording is locked inside the native iOS Voice
> Memos sandbox. So you'd still have the same classic iOS sandbox
> problems no matter what.


<https://drive.google.com/file/d/1-xDHFCEJvL9LMM42wWxJGx89nmyH4cFL/view?usp=share_link>

[toc] | [prev] | [next] | [standalone]

#183651

Marion <marion@facts.com> wrote at 05:24 this Sunday (GMT):
> Oh oh... there's another problem in iOS we didn't hit with photos.
>
> You hit a *new* problem when you try to access a different file type.
> In this case, the file type is an audio file.
>
>  *LocalSend can't (directly) access that audio file on the iOS device!*
>
> Here was what I needed to do:
> A. I made an audio recording on iOS of a phone call (with permission).
> B. I needed to transfer the 2-hour recording from iOS to Windows.
> C. On Windows, I needed to reduce the file size to fit into WhatsApp.
> D. Then I needed to transfer to Android to send over WhatsApp's dialer.
>
> The problem is iOS prevents something that simple from ever being easy.
>
> In summary, I want to transfer a specific 2-hour audio recording ("New
> Recording 4") from the iOS native "Voice Memos" app to my Windows 10
> machine using only my local network & without using the Internet so that I
> can shrink it to below 64MB in order to send it via Android WhatsApp.
>
> The key challenge is accessing the audio file which is ensconced deeply
> within the sand boxed environment of the native Voice Memos app on iOS.
>
> Unfortunately, iOS, by design, heavily restricts direct file system access
> for user applications like Voice Memos. This means that LocalSend, or any
> other app, typically cannot directly browse the internal storage of another
> app to pick out a specific file like the audio recording "New Recording 4".
>
> Here's the workaround I had to come up with to accomplish that simple task
> of LocalSend being able to access the sandboxed Voice Memo audio file.
>
> 1. Make sure the Windows PC & iOS device are on the same local network.
> 2. Open the LocalSend app on the iPad & the LocalSend program on the PC.
> 3. Make sure they see each other inside of the respective LocalSend GUIs.
> 4. Open the native iOS Voice Memos app on your iPad.
> 5. Find the recording titled "New Recording 4" within the app.
> 6. Tap on the recording to select it.
> 7. Tap on the "Share" icon. 
> 8. In the Share Sheet tap about until you finally see "Save to Files".
> 9. Tap "Save to Files".
> 10. Choose a location within the "Files" app such as "On My iPad".
> 11. Then press at the top right the "Save" button to save it there.
> 12. Double check it worked by opening the iOS Files app to see it there.
> 13. When you tap on it, you'll see it's named "New Recording 4.m4a" 69.7MB.
> 14. On the iOS LocalSend left pane, tap the "Send" option.
> 15. You'd think an audio file would be under "Media" but Apple doesn't.
> 16. In the main pane, below "Selection," tap on "File".
> 17. This should open the iOS file browser interface.
> 18. Look for and tap on "On My iPad" within this file browser interface.
> 19. Tap on "New Recording 4.m4a" to select it (you may need to tap twice).
> 20. You will see a blue check mark inserted on the selected file.
> 21. In the top right of the iOS file browser, tap the "Open" button.
> 22. LocalSend transitions to a screen displaying discovered devices.
> 23. Tap on the name of your Windows 10 PC in the list of recipients.
> 24. The Windows LocalSend will say "iPad wants to send you a file".
> 25. Tap "Accept" on the Windows LocalSend GUI to receive that file.
> 26. The default will be "C:\Users\you\Downloads\New Recording 4.m4a".
> 27. The Windows LocalSend GUI will say "Finished".
> 28. Windows MPC-BE should play the Apple m4a file.
>
> Voila! I successfully transferred a file out of the restrictive iOS
> filespace to Windows. I then easily copied it over USB to the Android
> sdcard to send via WhatsApp but WhatsApp has a 64MB file size limit.
>
> So I had to lower the bitrate to shrink the file to send via WhatsApp.
>  C:\> ffmpeg -i input.m4a -vn -acodec aac -q:a 0.5 output_aac_q0.5.m4a
>
> That shrunk the 68MB 2-hour audio file down to about 40MB for WhatsApp.
>
> Unfortunately that didn't change the metadata, so WhatsApp found the 40MB
> file but it thought it was the same name as the original 68MB file.
>
> So what I should have run is something like this to change metadata.
>  C:\> ffmpeg -i input.m4a -vn -acodec aac -q:a 0.5 -metadata title="Our Convo" -metadata filename="our_convo.m4a" output_metadata.m4a
> Or use MP3Tag on Windows:
> <https://www.mp3tag.de/en/>


I personally export the recording/photo/whatever to files (Save to Files
option), since its easier to get at those, as long as you don't mind
dumping it in a random app folder. Also, I didn't know about ffmpeg -q,
thanks :D
-- 
user <candycane> is generated from /dev/urandom

[toc] | [prev] | [next] | [standalone]

#183701

On Mon, 14 Apr 2025 19:10:03 -0000 (UTC), candycanearter07 wrote :


> I personally export the recording/photo/whatever to files (Save to Files
> option), since its easier to get at those, as long as you don't mind
> dumping it in a random app folder. Also, I didn't know about ffmpeg -q,
> thanks :D

Understood. And thanks for the confirmation of the process.

A lot of people don't know the file "type" matters greatly with iOS.
And the file "location" also matters greatly with iOS.

For others to know, Apple has only two kinds of file types on iOS (AFAICT).
a. DCIM/photos & videos
b. Everything else

Directly transferring those two types with iOS is COMPLETELY DIFFERENT:
A. Easy peasy? One way from iOS to the PC for DCIM pictures & video.
B. The other way? Not so much.
C. The other file type? Nearly impossible. 

The "trick" most Apple users employ, of course, is the cloud.
Funny how Apple designed things that way.

However, the other way is to use the native iOS Files app.
But even with Files, we still have two hurdles to overcome.
1. We have to get "everything else" into the Files app first.
2. And even then, we can't SMB to everything (e.g., iOS to Android).

In short, most people on iOS who want to transfer large amounts of data
that isn't in the DCIM directory will use the cloud (simply because Apple
designed iOS as a dumb terminal for strategic reasons); but those who use
their local LAN will often use the Files app with SMB; but, even SMB will
fail when you try to go from iOS to Android directly (without the PC).

If anyone here knows how to go from iOS & Android bidirectionally for all
file types, let me know as, otherwise, LocalSend will have to be that way.

[toc] | [prev] | [next] | [standalone]

#183706

On 2025-04-15 10:21, Marion wrote:
> On Mon, 14 Apr 2025 19:10:03 -0000 (UTC), candycanearter07 wrote :
> 
> 
>> I personally export the recording/photo/whatever to files (Save to Files
>> option), since its easier to get at those, as long as you don't mind
>> dumping it in a random app folder. Also, I didn't know about ffmpeg -q,
>> thanks :D
> 
> Understood. And thanks for the confirmation of the process.
> 
> A lot of people don't know the file "type" matters greatly with iOS.
> And the file "location" also matters greatly with iOS.
> 
> For others to know, Apple has only two kinds of file types on iOS (AFAICT).
> a. DCIM/photos & videos
> b. Everything else

False.

> 
> Directly transferring those two types with iOS is COMPLETELY DIFFERENT:
> A. Easy peasy? One way from iOS to the PC for DCIM pictures & video.
> B. The other way? Not so much.
> C. The other file type? Nearly impossible.

Also, false.

> 
> The "trick" most Apple users employ, of course, is the cloud.
> Funny how Apple designed things that way.

Nope. You can transfer files using SMB file sharing.

> 
> However, the other way is to use the native iOS Files app.
> But even with Files, we still have two hurdles to overcome.
> 1. We have to get "everything else" into the Files app first.

False.

> 2. And even then, we can't SMB to everything (e.g., iOS to Android).

Don't know if it's true or not, but it's irrelevant to your claim that 
SMB doesn't work between iOS and a Windows PC.

> 
> In short, most people on iOS who want to transfer large amounts of data
> that isn't in the DCIM directory will use the cloud (simply because Apple
> designed iOS as a dumb terminal for strategic reasons); but those who use
> their local LAN will often use the Files app with SMB; but, even SMB will
> fail when you try to go from iOS to Android directly (without the PC).

Still irrelevant, but moving goalposts when you've been shown to be 
wrong is your go-to move, isn't it?

:-)

> 
> If anyone here knows how to go from iOS & Android bidirectionally for all
> file types, let me know as, otherwise, LocalSend will have to be that way.

"Tutorial: How to send files between Windows & iOS over the LAN using 
LocalSend"

Where is "Android" mentioned there?

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | alt.comp.os.windows-10

csiph-web