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

Groups > comp.mobile.android > #156695 > unrolled thread

Re: How to copy text on the iPad to the Windows PC THE EASY WAY

Back to article view | Back to comp.mobile.android

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: How to copy text on the iPad to the Windows PC THE EASY WAY Maria Sophia <mariasophia@comprehension.com> - 2026-10-28 16:01 -0400
    Re: How to copy text on the iPad to the Windows PC THE EASY WAY "Carlos E.R." <robin_listas@es.invalid> - 2026-10-28 21:19 +0100
      Re: How to copy text on the iPad to the Windows PC THE EASY WAY Maria Sophia <mariasophia@comprehension.com> - 2026-10-28 21:01 -0400
        Re: How to copy text on the iPad to the Windows PC THE EASY WAY knuttle <keith_nuttle@yahoo.com> - 2026-10-28 22:19 -0400
          Re: How to copy text on the iPad to the Windows PC THE EASY WAY Maria Sophia <mariasophia@comprehension.com> - 2026-10-28 23:00 -0400
            Re: How to copy text on the iPad to the Windows PC THE EASY WAY Paul <nospam@needed.invalid> - 2026-10-29 03:01 -0400
              Re: How to copy text on the iPad to the Windows PC THE EASY WAY Maria Sophia <mariasophia@comprehension.com> - 2026-10-29 14:14 -0400
                Re: How to copy text on the iPad to the Windows PC THE EASY WAY Brock McNuggets <brock.mcnuggets@gmail.com> - 2026-10-29 11:57 -0700
            Re: How to copy text on the iPad to the Windows PC THE EASY WAY "Carlos E.R." <robin_listas@es.invalid> - 2026-10-29 12:03 +0100
              Re: How to copy text on the iPad to the Windows PC THE EASY WAY Paul <nospam@needed.invalid> - 2026-10-29 11:24 -0400
                Re: How to copy text on the iPad to the Windows PC THE EASY WAY "Carlos E.R." <robin_listas@es.invalid> - 2026-10-29 21:05 +0100
                  Re: How to copy text on the iPad to the Windows PC THE EASY WAY Paul <nospam@needed.invalid> - 2026-10-29 16:31 -0400
                    Re: How to copy text on the iPad to the Windows PC THE EASY WAY Maria Sophia <mariasophia@comprehension.com> - 2026-10-29 21:20 -0400
                      Re: How to copy text on the iPad to the Windows PC THE EASY WAY Brock McNuggets <brock.mcnuggets@gmail.com> - 2026-10-29 18:45 -0700

#156695 — Re: How to copy text on the iPad to the Windows PC THE EASY WAY

Carlos E.R. wrote:
> On 2026-10-28 05:02, Maria Sophia wrote:
>> Carlos E.R. wrote:
>>> Write an email, but do not send it. Keep it in drafts. Can be opened in
>>> any machine that shares that imap account (doesn't have to be google,
>>> and it can even be local only if you set up the server).
>> 
>> When the news comes out that the head of the CIA is caught, then it's
>> rather interesting *how* he got caught, in this case, using draft emails.
> 
> Yes, I know. But are you a drug lord, so that the CIA is interested in 
> you? :-D
> 
> My ISP is not after me, they will not read my drafts. Not unless the a 
> court orders them to.
> 
> 
> And then, I have my own IMAP server inside my LAN, which I can use for 
> this and nobody will see, unless they break in my house.

Carlos E.R. wrote:
> But are you a drug lord, so that the CIA is interested in you?

Good point! I used to have top-secret clearance (which is now called
TS/SCI), but that was long ago when I worked in a building with heavy
curtains on all the windows at Fort Meade on "stuff" (while they were
building their new secure facility that had no windows at all in it).

But if you've ever gone though their interviews (and I have, although it
was in the days before social media was prevalent) you'd be amazed at what
they ask and the money they spent interviewing everyone who knows you.

I have to openly admit, while I've found a dead body while hiking (so I
was, briefly, the first suspect by LE as the RP), I'm sure they "checked me
out" thoroughly (and even demanded my DNA, which I refused and they told me
they'd be back with a subpoena within days, which they never came back
with, as there was nothing connecting me to the dead person other than the
fact I hiked all over the backcountry and that body happened to be there).

So I'm clean with the CIA/FBI/NSA, etc.. For now. I think.... 
(although maybe the IRS wants me now that I take senior citizen deduction.)

BTW, you do things "the right way" not because you are being chased by the
feds. You do interoperability the right way because it's the right way.

For example, my data pins in my USB part are bad so for me, the right way
is over Wi-Fi, where WebDav servers do a great job mounting Android as a
drive on Windows, which, unfortunately, iOS is too brain dead to do.
 <https://i.postimg.cc/QtbR1GY0/webdav13.jpg>

Or, just as good, the "right way" is to use adbcopy.bat to copy single
files over back & forth bidirectionally between Android & the desktop.

But always remember that Apple designed iOS to be basically non functional
when it comes to working in the real world, and they're not stupid to do
that as they make a LOT of money forcing people to buy only Apple stuff.

If you're in the Apple ecosystem, things happen to work a little bit.
But the instant you leave the Apple ecosystem for the real world, almost
nothing works when you are trying to get Apple to work with non_Apple
stuff.

Anyway, the "right way" with privacy for people might be the way Herbert
suggested (which is fine, as long as we trust the encryption) of using
something like WhatsApp (or any similar draft-saving messenger tool).

Or, the right way for some might be the way Nick Charles kindly suggested,
using Files on iOS and SMB on Windows, which works for most people.

In decades of being on Usenet I've never disagreed with a working solution,
where the right way for me, since I don't have passwords on any machine but
iOS, simply because Apple requires you to create a mothership account if
you want to load anything... 

Which by the way, is one reason Apple products are the LEAST PRIVATE in the
industry, because nobody but Apple tracks everything you do (which is
saying a lot when compared to Google!) even to the point of inserting
essentially your unique account information into every IPA you install.

Given Apple products are the WORST in the industry for security, the "right
way" of doing things is to avoid the way Apple suggests, which is iTunes.

Luckily, I must repeat, for MOST PEOPLE, the right way will be the Files
metehod with SMB that Nick Charles kindly outlined, while, for me, the
right way will be to use Local Send although I acknowledge with encryption,
a ton of other options arise (but I don't consider that the right way).

[toc] | [next] | [standalone]

#156697

On 2026-10-28 21:01, Maria Sophia wrote:
> Carlos E.R. wrote:
>> On 2026-10-28 05:02, Maria Sophia wrote:
>>> Carlos E.R. wrote:
>>>> Write an email, but do not send it. Keep it in drafts. Can be opened in
>>>> any machine that shares that imap account (doesn't have to be google,
>>>> and it can even be local only if you set up the server).
>>>
>>> When the news comes out that the head of the CIA is caught, then it's
>>> rather interesting *how* he got caught, in this case, using draft emails.
>>
>> Yes, I know. But are you a drug lord, so that the CIA is interested in
>> you? :-D
>>
>> My ISP is not after me, they will not read my drafts. Not unless the a
>> court orders them to.
>>
>>
>> And then, I have my own IMAP server inside my LAN, which I can use for
>> this and nobody will see, unless they break in my house.
> 
> Carlos E.R. wrote:
>> But are you a drug lord, so that the CIA is interested in you?
> 
> Good point! I used to have top-secret clearance (which is now called
> TS/SCI), but that was long ago when I worked in a building with heavy
> curtains on all the windows at Fort Meade on "stuff" (while they were
> building their new secure facility that had no windows at all in it).

Not that far, but I worked for a company that did use tempest proof 
windows, so that mobile phones would not work inside the building, then 
they had to install internal transmitters, because they gave mobiles to 
their employees. They also disabled WiFi in their warehouse section, 
they did not trust it (year 2000).

Windows laptops for people working on external sites had to connect 
typing a password that was half remembered, and the other part coming 
from a small dongle we carried somewhere in us. Every minute the key 
changed.

And we could not connect via internet, or via the networked system of 
their clients. We had to connect via modem to a gratis phone number.

Not as paranoid as the CIA, but still paranoid enough for a private 
company. Once inside, the documentation was free to access to almost 
anybody, it was a dream come true.

...

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

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

#156703

Carlos E.R. wrote:
>> Good point! I used to have top-secret clearance (which is now called
>> TS/SCI), but that was long ago when I worked in a building with heavy
>> curtains on all the windows at Fort Meade on "stuff" (while they were
>> building their new secure facility that had no windows at all in it).
> 
> Not that far, but I worked for a company that did use tempest proof 
> windows, so that mobile phones would not work inside the building, then 
> they had to install internal transmitters, because they gave mobiles to 
> their employees. They also disabled WiFi in their warehouse section, 
> they did not trust it (year 2000).
> 
> Windows laptops for people working on external sites had to connect 
> typing a password that was half remembered, and the other part coming 
> from a small dongle we carried somewhere in us. Every minute the key 
> changed.
> 
> And we could not connect via internet, or via the networked system of 
> their clients. We had to connect via modem to a gratis phone number.
> 
> Not as paranoid as the CIA, but still paranoid enough for a private 
> company. Once inside, the documentation was free to access to almost 
> anybody, it was a dream come true.

Oh, that's interesting. You learn a lot about what 'can' be done when you
work with these fellows, which, I guess, is what drove Snowden to do it.

I was there before cellphones were a thing, but, before we had clearance
(it wasn't just me, it was an entire group of people, we couldn't bring
transparencies, which, in those days, was how we did presentations. 

This wasn't the CIA, but something like that, and every department had a
numerical name, such as R123, but what I remember most vividly was the had
requirements for the software that nobody else in the world had asked for.

But, luckily for me, internally, when I needed to FedEx a magtape to the
home office for overnight bugfixes (again, that's how we did things then),
they were fixed quickly, and FedExed back, where many were buffer overflows
as much of the code was written in Fortran way back then.

It was phone, fax and Fedex, as those were the fastest means of transit.

Since this particular TLA used the software differently (which even then,
cost about a million dollars a seat), we could tell what they were doing by
the strangeness of their requirements, which no commercial company needed. 

Interestingly, since the company, like any company, had, oh, let's say 100
products, they were the only entity that bought every single product.

I never knew if that was because they didn't want anyone to know which
product was the most useful to them (since internally people knew), or if
they really were the only company that had no cost constraints at all.

But they did use some of the products that nobody else used, which, again,
made supporting them all the more difficult, as it's harder to help them.

All in all, when I learned what they were doing, which, well, in today's
day and age, I doubt anyone would be surprised, but I was shocked because
here I was this innocent little kid who played by the rules all the time.

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

#156705

On 10/28/2026 9:01 PM, Maria Sophia wrote:
> Carlos E.R. wrote:
>>> Good point! I used to have top-secret clearance (which is now called
>>> TS/SCI), but that was long ago when I worked in a building with heavy
>>> curtains on all the windows at Fort Meade on "stuff" (while they were
>>> building their new secure facility that had no windows at all in it).
>>
>> Not that far, but I worked for a company that did use tempest proof
>> windows, so that mobile phones would not work inside the building, then
>> they had to install internal transmitters, because they gave mobiles to
>> their employees. They also disabled WiFi in their warehouse section,
>> they did not trust it (year 2000).
>>
>> Windows laptops for people working on external sites had to connect
>> typing a password that was half remembered, and the other part coming
>> from a small dongle we carried somewhere in us. Every minute the key
>> changed.
>>
>> And we could not connect via internet, or via the networked system of
>> their clients. We had to connect via modem to a gratis phone number.
>>
>> Not as paranoid as the CIA, but still paranoid enough for a private
>> company. Once inside, the documentation was free to access to almost
>> anybody, it was a dream come true.
> 
> Oh, that's interesting. You learn a lot about what 'can' be done when you
> work with these fellows, which, I guess, is what drove Snowden to do it.
> 
> I was there before cellphones were a thing, but, before we had clearance
> (it wasn't just me, it was an entire group of people, we couldn't bring
> transparencies, which, in those days, was how we did presentations.
> 
> This wasn't the CIA, but something like that, and every department had a
> numerical name, such as R123, but what I remember most vividly was the had
> requirements for the software that nobody else in the world had asked for.
> 
> But, luckily for me, internally, when I needed to FedEx a magtape to the
> home office for overnight bugfixes (again, that's how we did things then),
> they were fixed quickly, and FedExed back, where many were buffer overflows
> as much of the code was written in Fortran way back then.
> 
> It was phone, fax and Fedex, as those were the fastest means of transit.
> 
> Since this particular TLA used the software differently (which even then,
> cost about a million dollars a seat), we could tell what they were doing by
> the strangeness of their requirements, which no commercial company needed.
> 
> Interestingly, since the company, like any company, had, oh, let's say 100
> products, they were the only entity that bought every single product.
> 
> I never knew if that was because they didn't want anyone to know which
> product was the most useful to them (since internally people knew), or if
> they really were the only company that had no cost constraints at all.
> 
> But they did use some of the products that nobody else used, which, again,
> made supporting them all the more difficult, as it's harder to help them.
> 
> All in all, when I learned what they were doing, which, well, in today's
> day and age, I doubt anyone would be surprised, but I was shocked because
> here I was this innocent little kid who played by the rules all the time.
When I want to transfer information from my computer (Windows) I use the 
Bluetooth function.   You can transfer any file either from or to the 
cell phone.   Using the Bluetooth, there is no fuss.  highlight the file 
Select Share (Android), select Bluetooth,  On the computer click the 
Bluetooth Icon and select share, the click the computer on the cell phone.

Going from computer to cellphone is easier as you as you select share on 
the file and select Bluetooth, and the computer.

No worry about internet, email, security or anything else it is a direct 
cellphone to computer transfer

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

#156709

knuttle wrote:
> When I want to transfer information from my computer (Windows) I use the 
> Bluetooth function.   You can transfer any file either from or to the 
> cell phone.   Using the Bluetooth, there is no fuss.  highlight the file 
> Select Share (Android), select Bluetooth,  On the computer click the 
> Bluetooth Icon and select share, the click the computer on the cell phone.
> 
> Going from computer to cellphone is easier as you as you select share on 
> the file and select Bluetooth, and the computer.
> 
> No worry about internet, email, security or anything else it is a direct 
> cellphone to computer transfer

I think there's a subtopic tangential offshoot of this very thread where
bluetooth would work just fine if Apple didn't purposely break it for iOS.

Since iOS is expressly designed by Apple to NOT interoperate with Windows,
it shouldn't be surprising that we'd "think" bluetooth would work, since it
works with every other common consumer operating system, and Windows.

Just not with iOS.

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

#156711

On Wed, 10/28/2026 11:00 PM, Maria Sophia wrote:
> knuttle wrote:
>> When I want to transfer information from my computer (Windows) I use the 
>> Bluetooth function.   You can transfer any file either from or to the 
>> cell phone.   Using the Bluetooth, there is no fuss.  highlight the file 
>> Select Share (Android), select Bluetooth,  On the computer click the 
>> Bluetooth Icon and select share, the click the computer on the cell phone.
>>
>> Going from computer to cellphone is easier as you as you select share on 
>> the file and select Bluetooth, and the computer.
>>
>> No worry about internet, email, security or anything else it is a direct 
>> cellphone to computer transfer
> 
> I think there's a subtopic tangential offshoot of this very thread where
> bluetooth would work just fine if Apple didn't purposely break it for iOS.
> 
> Since iOS is expressly designed by Apple to NOT interoperate with Windows,
> it shouldn't be surprising that we'd "think" bluetooth would work, since it
> works with every other common consumer operating system, and Windows.
> 
> Just not with iOS.
> 

I keep looking at the help files on the web from Apple,
and the only result I get from reading them, is an
indication I should not be buying the device. It's obvious
"their way or the highway". That's OK, the world won't flip
its axis because I didn't buy an Apple product :-)

I'm a desktop person, because desktops work for me. They
don't constantly disappoint me, only occasional disappointment
is the result :-)  [ And that's a real smiley there ]

For example, my new video card, the driver wouldn't load on it
in Linux. But ~5 hours work (I'm "careful" when I do this stuff
and most of the time was getting the backup done), and the problem
was solved. I only restored from backup one time, before the update
I needed, worked properly. I knew there would be carnage before
I started, so this was all purposeful steps, no novelty was involved.
I had a good idea what trouble it would cause, and it wasn't guaranteed
it would fix it either. It was just "most likely" to fix it. The Google
search didn't address the issue directly, as in what kernel release
would have the goods.

I used the same approach when my Windows box tipped over a week ago,
and things were looking pretty bad for a while. I thought I was cooked.
But I got lucky, the system died in the login prompt, and that
seemed to trigger some recovery behavior in the OS. It did "something"
to the computer, that fixed it. I would rather know what it was
that it fixed, I looked in the SRTtrail folder but could not see
any step in there that looked like a "fix".

I see one reference in Google, to

   X:\windows\system32\logfiles\Srt\SrtTrail.txt

and that means the log was actually on X: before the
system rebooted and X: was gone (as X: is a RAMdisk used
by WinPE/WinRE). It doesn't give you a chance to do anything
before it reboots, so looking at the folder would
have required a miracle. That's an auto-repair, which is
why there is no user interaction possible.

*******

By comparison, things smaller than a desktop, just
aren't a "good time". Too restrictive. Do I have to
smash everything with a hammer, to get things done ?
There must be a better way.

      Paul

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

#156727

Paul wrote:
>> Since iOS is expressly designed by Apple to NOT interoperate with Windows,
>> it shouldn't be surprising that we'd "think" bluetooth would work, since it
>> works with every other common consumer operating system, and Windows.
>> 
>> Just not with iOS.
>> 
> 
> I keep looking at the help files on the web from Apple,
> and the only result I get from reading them, is an
> indication I should not be buying the device.

I've learned, over the decades, that Apple 'says' they cripple iOS "for our
safety", but the real reason copy fails is iOS prevents interoperability.

If an Apple device worked in the real world, Apple's profits would plummet.

It would be too easy for an iPhone to just work with USB, for example.
Or to just work with bluetooth, or even to just work with Wi-Fi on the LAN.

Nope. You have to use Apple-only products in an Apple-only ecosystem if you
want an Apple device to play well with Windows (or, as noted, with Linux).

> "their way or the highway". That's OK, the world won't flip
> its axis because I didn't buy an Apple product :-)

When I first bought an iPhone for one of my kids, she wanted it pink, which
should have been a warning, and it had to have "I'm a Barbie girl" as a
ringtone (this was in the days of Limewire, well before YouTube I think).

Over the years, I've learned Apple owners are cultivated, by Apple, to do
things the Apple way, even as I grew up in a world where I do what I want.

> By comparison, things smaller than a desktop, just
> aren't a "good time". Too restrictive. Do I have to
> smash everything with a hammer, to get things done ?
> There must be a better way.

Luckily, if we are stuck on an iOS device and we want to bidirectionally
transfer the clipboard (or file) over USB or over Wi-Fi to Windows, we can.

It's just the classic Apple kluge to do it.

1. Either use the iOS native Files app and set up a two-way smb share
2. Or, start with the Files app and then use LocalSend for the sharing

Both work.

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

#156734

On 29 Oct 2026, Maria Sophia wrote in
<11c02du$pgj$1@nnrp.usenet.blueworldhosting.com>:
> Paul wrote:
>>> Since iOS is expressly designed by Apple to NOT interoperate
>>> with Windows, it shouldn't be surprising that we'd "think"
>>> bluetooth would work, since it works with every other common
>>> consumer operating system, and Windows.
>>> 
>>> Just not with iOS.
>>> 
>> 
>> I keep looking at the help files on the web from Apple, and the
>> only result I get from reading them, is an
>> indication I should not be buying the device.
> 
> I've learned, over the decades, that Apple 'says' they cripple iOS
> "for our safety", but the real reason copy fails is iOS prevents
> interoperability.

They never say that.
> 
> If an Apple device worked in the real world, Apple's profits would
> plummet.

This is not a rational statement.
> 
> It would be too easy for an iPhone to just work with USB, for
> example. Or to just work with bluetooth, or even to just work with
> Wi-Fi on the LAN.

My iPhone works with BlueTooth and Wi-Fi just fine. On the rare
occasion I have used USB with it, that has also worked fine -- but
there is rarely a need for it.
> 
> Nope. You have to use Apple-only products in an Apple-only
> ecosystem if you want an Apple device to play well with Windows
> (or, as noted, with Linux).

You just moved goalposts. And Windows works no better with iPhones
than iPhones work with Windows. So?
> 
>> "their way or the highway". That's OK, the world won't flip its
>> axis because I didn't buy an Apple product :-)
> 
> When I first bought an iPhone for one of my kids,

You hate the product and the company but you still buy iPhones? That
sounds very unlikely.

> she wanted it
> pink, which should have been a warning, and it had to have "I'm a
> Barbie girl" as a ringtone (this was in the days of Limewire, well
> before YouTube I think).
> 
> Over the years, I've learned Apple owners are cultivated, by
> Apple, to do things the Apple way, even as I grew up in a world
> where I do what I want.

Your complaint is the color. Wow.
> 
>> By comparison, things smaller than a desktop, just
>> aren't a "good time". Too restrictive. Do I have to smash
>> everything with a hammer, to get things done ? There must be a
>> better way.
> 
> Luckily, if we are stuck on an iOS device and we want to
> bidirectionally transfer the clipboard (or file) over USB or over
> Wi-Fi to Windows, we can.

I use a shared clipboard on my iPhone and my laptop with (mostly) no
issue. Just works. As it should .

> It's just the classic Apple kluge to do it.
> 
> 1. Either use the iOS native Files app and set up a two-way smb
> share 2. Or, start with the Files app and then use LocalSend for
> the sharing
> 
> Both work.
> 
Or just copy and paste... and SMB and the Files App have nothing to
do with it.


-- 
It's impossible for someone who is at war with themselves to be at peace with you.

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

#156718

On 2026-10-29 04:00, Maria Sophia wrote:
> knuttle wrote:
>> When I want to transfer information from my computer (Windows) I use the
>> Bluetooth function.   You can transfer any file either from or to the
>> cell phone.   Using the Bluetooth, there is no fuss.  highlight the file
>> Select Share (Android), select Bluetooth,  On the computer click the
>> Bluetooth Icon and select share, the click the computer on the cell phone.
>>
>> Going from computer to cellphone is easier as you as you select share on
>> the file and select Bluetooth, and the computer.
>>
>> No worry about internet, email, security or anything else it is a direct
>> cellphone to computer transfer
> 
> I think there's a subtopic tangential offshoot of this very thread where
> bluetooth would work just fine if Apple didn't purposely break it for iOS.
> 
> Since iOS is expressly designed by Apple to NOT interoperate with Windows,
> it shouldn't be surprising that we'd "think" bluetooth would work, since it
> works with every other common consumer operating system, and Windows.
> 
> Just not with iOS.

It also doesn't work with Linux (from/to Android), AFAIK. Somebody has 
to implement it, not that they don't want to.

Maybe I am mistaken and there is a desktop that does it.


-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

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

#156722

On Thu, 10/29/2026 7:03 AM, Carlos E.R. wrote:
> On 2026-10-29 04:00, Maria Sophia wrote:
>> knuttle wrote:
>>> When I want to transfer information from my computer (Windows) I use the
>>> Bluetooth function.   You can transfer any file either from or to the
>>> cell phone.   Using the Bluetooth, there is no fuss.  highlight the file
>>> Select Share (Android), select Bluetooth,  On the computer click the
>>> Bluetooth Icon and select share, the click the computer on the cell phone.
>>>
>>> Going from computer to cellphone is easier as you as you select share on
>>> the file and select Bluetooth, and the computer.
>>>
>>> No worry about internet, email, security or anything else it is a direct
>>> cellphone to computer transfer
>>
>> I think there's a subtopic tangential offshoot of this very thread where
>> bluetooth would work just fine if Apple didn't purposely break it for iOS.
>>
>> Since iOS is expressly designed by Apple to NOT interoperate with Windows,
>> it shouldn't be surprising that we'd "think" bluetooth would work, since it
>> works with every other common consumer operating system, and Windows.
>>
>> Just not with iOS.
> 
> It also doesn't work with Linux (from/to Android), AFAIK. Somebody has to implement it, not that they don't want to.
> 
> Maybe I am mistaken and there is a desktop that does it.
> 
> 

I can find a reference here.

  https://unix.stackexchange.com/questions/779545/is-it-possible-to-use-bluetooth-for-transferring-files-between-an-android-phone

      "On the odd occasion when I need to get a file to my phone (or indeed
       someone else's!) but have no alternative to bluetooth then blueman
       has filled that niche.

       Not fast and maybe a bit of juggling to get to the "accept transfer" dialogue
       on the phone, but other than this it has been reliable for me and is as simple as

          systemctl --user start obex
          blueman-sendto --device=$phone_mac_address "$filename"
      "

   Paul

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

#156743

On 2026-10-29 16:24, Paul wrote:
> On Thu, 10/29/2026 7:03 AM, Carlos E.R. wrote:
>> On 2026-10-29 04:00, Maria Sophia wrote:
>>> knuttle wrote:
>>>> When I want to transfer information from my computer (Windows) I use the
>>>> Bluetooth function.   You can transfer any file either from or to the
>>>> cell phone.   Using the Bluetooth, there is no fuss.  highlight the file
>>>> Select Share (Android), select Bluetooth,  On the computer click the
>>>> Bluetooth Icon and select share, the click the computer on the cell phone.
>>>>
>>>> Going from computer to cellphone is easier as you as you select share on
>>>> the file and select Bluetooth, and the computer.
>>>>
>>>> No worry about internet, email, security or anything else it is a direct
>>>> cellphone to computer transfer
>>>
>>> I think there's a subtopic tangential offshoot of this very thread where
>>> bluetooth would work just fine if Apple didn't purposely break it for iOS.
>>>
>>> Since iOS is expressly designed by Apple to NOT interoperate with Windows,
>>> it shouldn't be surprising that we'd "think" bluetooth would work, since it
>>> works with every other common consumer operating system, and Windows.
>>>
>>> Just not with iOS.
>>
>> It also doesn't work with Linux (from/to Android), AFAIK. Somebody has to implement it, not that they don't want to.
>>
>> Maybe I am mistaken and there is a desktop that does it.
>>
>>
> 
> I can find a reference here.
> 
>    https://unix.stackexchange.com/questions/779545/is-it-possible-to-use-bluetooth-for-transferring-files-between-an-android-phone
> 
>        "On the odd occasion when I need to get a file to my phone (or indeed
>         someone else's!) but have no alternative to bluetooth then blueman
>         has filled that niche.
> 
>         Not fast and maybe a bit of juggling to get to the "accept transfer" dialogue
>         on the phone, but other than this it has been reliable for me and is as simple as
> 
>            systemctl --user start obex
>            blueman-sendto --device=$phone_mac_address "$filename"
>        "

What I do, is fire up the Cx file manager in Android, select "network", 
then start its internal FTP server. Then reach that server from Linux 
with any standard tools in my LAN.

It works for me, easy and fast, because I am used to these kind of 
tools. And the computer source of the files I'm now transferring doesn't 
have BT configured.

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

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

#156745

On Thu, 10/29/2026 4:05 PM, Carlos E.R. wrote:
> On 2026-10-29 16:24, Paul wrote:
>> On Thu, 10/29/2026 7:03 AM, Carlos E.R. wrote:
>>> On 2026-10-29 04:00, Maria Sophia wrote:
>>>> knuttle wrote:
>>>>> When I want to transfer information from my computer (Windows) I use the
>>>>> Bluetooth function.   You can transfer any file either from or to the
>>>>> cell phone.   Using the Bluetooth, there is no fuss.  highlight the file
>>>>> Select Share (Android), select Bluetooth,  On the computer click the
>>>>> Bluetooth Icon and select share, the click the computer on the cell phone.
>>>>>
>>>>> Going from computer to cellphone is easier as you as you select share on
>>>>> the file and select Bluetooth, and the computer.
>>>>>
>>>>> No worry about internet, email, security or anything else it is a direct
>>>>> cellphone to computer transfer
>>>>
>>>> I think there's a subtopic tangential offshoot of this very thread where
>>>> bluetooth would work just fine if Apple didn't purposely break it for iOS.
>>>>
>>>> Since iOS is expressly designed by Apple to NOT interoperate with Windows,
>>>> it shouldn't be surprising that we'd "think" bluetooth would work, since it
>>>> works with every other common consumer operating system, and Windows.
>>>>
>>>> Just not with iOS.
>>>
>>> It also doesn't work with Linux (from/to Android), AFAIK. Somebody has to implement it, not that they don't want to.
>>>
>>> Maybe I am mistaken and there is a desktop that does it.
>>>
>>>
>>
>> I can find a reference here.
>>
>>    https://unix.stackexchange.com/questions/779545/is-it-possible-to-use-bluetooth-for-transferring-files-between-an-android-phone
>>
>>        "On the odd occasion when I need to get a file to my phone (or indeed
>>         someone else's!) but have no alternative to bluetooth then blueman
>>         has filled that niche.
>>
>>         Not fast and maybe a bit of juggling to get to the "accept transfer" dialogue
>>         on the phone, but other than this it has been reliable for me and is as simple as
>>
>>            systemctl --user start obex
>>            blueman-sendto --device=$phone_mac_address "$filename"
>>        "
> 
> What I do, is fire up the Cx file manager in Android, select "network", 
> then start its internal FTP server. Then reach that server from Linux with
> any standard tools in my LAN.
> 
> It works for me, easy and fast, because I am used to these kind of tools. 
> And the computer source of the files I'm now transferring doesn't have BT configured.

Between windows machines and between windows and Linux, the Bluetooth Send worked
from either end. It was something that worked earlier in the life of their
hand-hewn BT stack.

The Bluetooth TCP/IP stack on the other hand, that wasn't working until relatively
recently. And maybe that would be part of what the CX Explorer is doing.

I've had a file transfer working over the BT TCP/IP using File Sharing,
just to see if the transfer rate was the same (~75KB/sec). That seemed to
work OK, but the IP address used is outside the /24 netmask, and you have
to widen the mask to get that to work. I think I might have needed to do
that as a separate step. You use an "ipconfig" first, to see if the
address is going to be immediately useful or not, and whether an
additional step is needed.

I don't expect "details" to bother anyone at Microsoft. The IP address is
what it is, because that's handled as IFS (Internet File Sharing).

The Bluetooth Send is different, as it seems to use a different profile
and it might be OBEX.

  https://stackoverflow.com/questions/58131950/passing-arguments-to-fsquirt-exe

     Paul

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

#156748

Paul wrote:
>> What I do, is fire up the Cx file manager in Android, select "network", 
>> then start its internal FTP server. Then reach that server from Linux with
>> any standard tools in my LAN.
>> 
>> It works for me, easy and fast, because I am used to these kind of tools. 
>> And the computer source of the files I'm now transferring doesn't have BT configured.
> 
> Between windows machines and between windows and Linux, the Bluetooth Send worked
> from either end. It was something that worked earlier in the life of their
> hand-hewn BT stack.
> 
> The Bluetooth TCP/IP stack on the other hand, that wasn't working until relatively
> recently. And maybe that would be part of what the CX Explorer is doing.

Just to note the initial problem was the clipboard, but, of course, the
clipboard can be pasted into a file on most platforms other than iOS.

On iOS the clipboard can be pasted into a file too, as Nick Charles kindly
suggested, but you have to do it the Apple way, which isn't always
intuitive.

Luckily, with Vysor or scrcpy the Android/desktop clipboard is shared.
 1. Click one is copy the clipboard (on one platform)
 2. Click two is control-V on the keyboard (on the other platform)
    <https://i.postimg.cc/ZRCTyRx0/scrcpy35.jpg>

Luckily, with Vysor, even iOS can be two steps with Windows.
    <https://i.postimg.cc/TYvqdxCT/vysor35.jpg>
But, it's about 20 steps (or so) on iOS if you use the Apple way to do it.

If anyone on the Apple ng can get that down to the 2 clicks that it should
be, that would be an improvement over the kludge way Apple does things.

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

#156751

On 29 Oct 2026, Maria Sophia wrote in
<11c0rcu$eh8$1@nnrp.usenet.blueworldhosting.com>:
> Paul wrote:
>>> What I do, is fire up the Cx file manager in Android, select
>>> "network", then start its internal FTP server. Then reach that
>>> server from Linux with any standard tools in my LAN.
>>> 
>>> It works for me, easy and fast, because I am used to these kind
>>> of tools. And the computer source of the files I'm now
>>> transferring doesn't have BT configured.
>> 
>> Between windows machines and between windows and Linux, the
>> Bluetooth Send worked from either end. It was something that
>> worked earlier in the life of their hand-hewn BT stack.
>> 
>> The Bluetooth TCP/IP stack on the other hand, that wasn't working
>> until relatively recently. And maybe that would be part of what
>> the CX Explorer is doing.
> 
> Just to note the initial problem was the clipboard, but, of
> course, the clipboard can be pasted into a file on most platforms
> other than iOS.

The clipboard can be pasted into a file on iOS. Of course. In fact,
in iOS 27 they made it even easier -- maybe something that already
existed on Android. Don't know. But even before that it was easy.
> 
> On iOS the clipboard can be pasted into a file too, as Nick
> Charles kindly suggested, but you have to do it the Apple way,
> which isn't always intuitive.

Hold and get a menu or, now, just see it above the keyboard. How can
you get easier on a small touch screen?

> Luckily, with Vysor or scrcpy the Android/desktop clipboard is
> shared. 1. Click one is copy the clipboard (on one platform) 2.
> Click two is control-V on the keyboard (on the other platform)
> <https://i.postimg.cc/ZRCTyRx0/scrcpy35.jpg>

That works on iOS to macOS (well, Command+V, which is the norm there
and easier to use on most keyboards, AND Command does not cause
problems with terminals).

> Luckily, with Vysor, even iOS can be two steps with Windows.
> <https://i.postimg.cc/TYvqdxCT/vysor35.jpg>
> But, it's about 20 steps (or so) on iOS if you use the Apple way
> to do it.

On iOS you copy and paste. It "just works".
> 
> If anyone on the Apple ng can get that down to the 2 clicks that
> it should be, that would be an improvement over the kludge way
> Apple does things.

Select. Copy. Move to where you want it. Paste.

Done.



-- 
It's impossible for someone who is at war with themselves to be at peace with you.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.mobile.android

csiph-web