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

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

App Compatible With AirDrop (iPhone)?

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

Contents

  App Compatible With AirDrop (iPhone)? "tb" <nospam@example.invalid> - 2016-07-26 20:23 +0000
    Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-26 16:39 -0400
    Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-27 16:14 +0000
      Re: App Compatible With AirDrop (iPhone)? "tb" <nospam@example.invalid> - 2016-07-27 18:40 +0000
        Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-27 14:50 -0400
          Re: App Compatible With AirDrop (iPhone)? "tb" <nospam@example.invalid> - 2016-07-27 19:41 +0000
            Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-27 15:43 -0400
              Re: App Compatible With AirDrop (iPhone)? "tb" <nospam@example.invalid> - 2016-07-27 20:06 +0000
                Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-28 12:52 -0400
                  Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-30 01:00 +0000
                    Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-29 21:22 -0400
                      Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-30 15:59 +0000
                        Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-30 12:28 -0400
                          Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-31 03:12 +0000
          Re: App Compatible With AirDrop (iPhone)? "s|b" <me@privacy.invalid> - 2016-07-27 22:32 +0200
            Re: App Compatible With AirDrop (iPhone)? ANTant@zimage.com (Ant) - 2016-07-27 17:16 -0500
              Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-29 04:07 +0000
                Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-29 00:35 -0400
                  Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-29 05:08 +0000
                    Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-29 13:02 -0400
            Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-29 04:07 +0000
              Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-29 00:35 -0400
                Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-29 05:08 +0000
                  Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-29 13:02 -0400
        Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-30 01:00 +0000
          Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-29 21:22 -0400
            Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-30 16:19 +0000
              Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-07-30 12:28 -0400
              Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-30 13:21 -0400
                Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-31 03:12 +0000
                  Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-30 23:50 -0400
                    Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-31 20:27 +0000
                      Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-31 21:52 -0400
                        Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-08-01 05:55 +0000
                          Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-08-01 02:11 -0400
                            Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-08-01 21:59 +0000
                              Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-08-01 18:47 -0400
                    Re: App Compatible With AirDrop (iPhone)? crankypuss <undisclosedUserid@gmail.com> - 2016-08-05 08:31 -0600
                      Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-08-06 04:04 -0400
                        Re: App Compatible With AirDrop (iPhone)? Andy Burns <usenet@andyburns.uk> - 2016-08-06 13:58 +0100
                          Re: App Compatible With AirDrop (iPhone)? crankypuss <undisclosedUserid@gmail.com> - 2016-08-06 08:59 -0600
                            Re: App Compatible With AirDrop (iPhone)? ANTant@zimage.com (Ant) - 2016-08-07 02:07 -0500
                              Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-08-07 03:57 -0400
                        Re: App Compatible With AirDrop (iPhone)? Frank Slootweg <this@ddress.is.invalid> - 2016-08-06 14:08 +0000
                          Re: App Compatible With AirDrop (iPhone)? crankypuss <undisclosedUserid@gmail.com> - 2016-08-06 09:10 -0600
                            Re: App Compatible With AirDrop (iPhone)? nospam <nospam@nospam.invalid> - 2016-08-06 12:01 -0400
                        Re: App Compatible With AirDrop (iPhone)? Nigel Wade <nmw@local.domain> - 2016-08-08 15:51 +0100
        Re: App Compatible With AirDrop (iPhone)? crankypuss <undisclosedUserid@gmail.com> - 2016-08-05 08:28 -0600
      Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-28 05:02 -0400
        Re: App Compatible With AirDrop (iPhone)? "s|b" <me@privacy.invalid> - 2016-07-28 19:48 +0200
        Re: App Compatible With AirDrop (iPhone)? Frank Slootweg <this@ddress.is.invalid> - 2016-07-28 19:18 +0000
        Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-28 15:26 -0400
          Re: App Compatible With AirDrop (iPhone)? Frank Slootweg <this@ddress.is.invalid> - 2016-07-28 20:02 +0000
            Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-29 03:31 -0400
              Re: App Compatible With AirDrop (iPhone)? Frank Slootweg <this@ddress.is.invalid> - 2016-07-30 17:50 +0000
                Re: App Compatible With AirDrop (iPhone)? The Real Bev <bashley101@gmail.com> - 2016-07-30 12:49 -0700
                  Re: App Compatible With AirDrop (iPhone)? Frank Slootweg <this@ddress.is.invalid> - 2016-07-30 20:18 +0000
                    Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-30 23:19 -0400
                      Re: App Compatible With AirDrop (iPhone)? Frank Slootweg <this@ddress.is.invalid> - 2016-07-31 19:22 +0000
                        Re: App Compatible With AirDrop (iPhone)? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-07-31 22:02 -0400
    Re: App Compatible With AirDrop (iPhone)? "s|b" <me@privacy.invalid> - 2016-07-27 21:10 +0200
    Re: App Compatible With AirDrop (iPhone)? Aardvarks <aardvarks@a.b.c.com> - 2016-07-31 00:45 +0000
      Re: App Compatible With AirDrop (iPhone)? "s|b" <me@privacy.invalid> - 2016-07-31 22:21 +0200

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

#32901

On Wed, 27 Jul 2016 22:32:40 +0200, s|b wrote:

> I agree. Tried it once and it took forever!

Transferring a file by bluetooth is like using a motorcycle courier.
It's fast and efficient for small files - and you can go anywhere.

I just transferred a screenshot from my Android device to my laptop.
Tap. Tap. Done.

It was done so fast, that I didn't even finish selecting the *next* set of 
pictures and I saw the notice that it completed.

Now, I would *not* try to transfer a video file over bluetooth.
That's like trying to transport a refrigerator with a motorcycle.

For that I'd use a simple USB wire which is the fastest method possible 
(and not, using the Cloud is not suitable to transfer a file two feet from 
your device to your computer).

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

#32904

In article <nnekqd$4bj$1@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:

> 
> > I agree. Tried it once and it took forever!
> 
> Transferring a file by bluetooth is like using a motorcycle courier.
> It's fast and efficient for small files - and you can go anywhere.
> 
> I just transferred a screenshot from my Android device to my laptop.
> Tap. Tap. Done.
> 
> It was done so fast, that I didn't even finish selecting the *next* set of 
> pictures and I saw the notice that it completed.
> 
> Now, I would *not* try to transfer a video file over bluetooth.
> That's like trying to transport a refrigerator with a motorcycle.

so you admit it's slow
> 
> For that I'd use a simple USB wire which is the fastest method possible 

wrong

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

#32906

On Fri, 29 Jul 2016 00:35:23 -0400, nospam wrote:

>> Now, I would *not* try to transfer a video file over bluetooth.
>> That's like trying to transport a refrigerator with a motorcycle.
> 
> so you admit it's slow

It's actually more like using a bicycle courier in the streets of San
Francisco. 

It's simple (tap-tap you're done), and way more than fast enough for small
files (which is what I use it for).

Using bluetooth to transfer video would be like transporting a video by
bicycle; however, using a truck to transport an envelope is just as
inefficient in the other direction.

You use the tools that fit the job ... oh -- I forgot - you don't even
*have* the tools for bluetooth file transfer on iOS.

Which is the reason you deprecate it.

You'd deprecate a simple screwdriver if Apple didn't provide one in your
toolbox. That's the only way you know how to think. Applethink.

>> For that I'd use a simple USB wire which is the fastest method possible 
> 
> wrong

Tell me, bit for bit, what's *faster* than wire?

NOTE: The cloud can't possibly count simply because of the immense
infrastructure overhead that is required, including accounts, storage
limits, storage rents, Internet access, two-way transition requirement,
sync setups, etc.

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

#32916

In article <nneod1$7q4$5@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:

> 
> >> Now, I would *not* try to transfer a video file over bluetooth.
> >> That's like trying to transport a refrigerator with a motorcycle.
> > 
> > so you admit it's slow
> 
> It's actually more like using a bicycle courier in the streets of San
> Francisco. 
> 
> It's simple (tap-tap you're done), and way more than fast enough for small
> files (which is what I use it for).

it's only useful for very small files, where the overhead of tapping is
dominant.

> Using bluetooth to transfer video would be like transporting a video by
> bicycle; however, using a truck to transport an envelope is just as
> inefficient in the other direction.
> 
> You use the tools that fit the job ... oh -- I forgot - you don't even
> *have* the tools for bluetooth file transfer on iOS.

no need, because much better and far faster options exist, even on
android, which you've been told before.

> Which is the reason you deprecate it.
> 
> You'd deprecate a simple screwdriver if Apple didn't provide one in your
> toolbox. That's the only way you know how to think. Applethink.

nothing but insults.

it's actually *you* who deprecates anything outside of your tiny little
toolbox, a box so tiny that it only has bluetooth in it.

> >> For that I'd use a simple USB wire which is the fastest method possible 
> > 
> > wrong
> 
> Tell me, bit for bit, what's *faster* than wire?

don't twist things.

you said usb wire, which in the case of phones, is usb 2, and that's
not particularly fast.

using wifi will be faster, plus there's a lot less hassle because
there's no need to find a cable or even be near the host computer.

> NOTE: The cloud can't possibly count simply because of the immense
> infrastructure overhead that is required, including accounts, storage
> limits, storage rents, Internet access, two-way transition requirement,
> sync setups, etc.

nobody said anything about a cloud. 

once again, you have't a clue.

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

#32920

On Wed, 27 Jul 2016 18:40:47 +0000 (UTC), tb wrote:

> I suppose Bluetooth would work even though I would have preferred some
> Android cross-platform app that could interact directly with AirDrop.
> I'm slowly realizing that such cross-platform app does not exist.
> 
> The Bluetooth solution is a suggestion to keep in mind.  A friend of
> mine suggested using Dropbox.

Well, the value of a cloud solution is that *both* types of devices can use
that cloud solution across the mullion that divides them otherwise, simply
because it's a standard that Apple will accept as well as Android.

Of course, the disadvantages of the cloud are immense, not the least of
which are that you almost always need logins (sometimes common logins
depending on what you're doing), and then you have the security hassle and
then you might have to rent your data back from the cloud supplier for the
rest of your life, not to mention speeds aren't that great and if there's
no Internet connection, then speeds are interminable, etc.

The beauty of bluetooth file transfer is that almost all decent laptops and
desktops support it on all three common operating systems. Android supports
it.

It's just the IDevices which don't support the common standard, and for
that, you're already using AirDrop (which I know nothing about so I'm just
advising you on the Android devices).

There's also the possibility of WiFi transfer the way, which works fine in
some cases but which is more limited than is bluetooth in how it works
because most of the apps require a web page for the transfer. If you want
to know more about WiFi transfer, just ask as I use that for both iDevices
and aDevices (but I vastly prefer the utter simplicity of bluetooth).

In addition, you *can* transfer files by USB cable, which is trivial to do
with aDevices, and problematic with iDevices (so again, the Apple
walled-garden is filled with thorny bushes - but it *can* be done, e.g., I
transfer videos over cable to/from iDevices to/from Linux all the time).

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

#32922

In article <nngu7v$1d3o$2@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:

> 
> There's also the possibility of WiFi transfer the way, which works fine in
> some cases but which is more limited than is bluetooth in how it works
> because most of the apps require a web page for the transfer. If you want
> to know more about WiFi transfer, just ask as I use that for both iDevices
> and aDevices (but I vastly prefer the utter simplicity of bluetooth).

more ignorant bullshit.

there is *no* need for a web page to use wifi.

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

#32928

On Fri, 29 Jul 2016 21:22:09 -0400, nospam wrote:

> more ignorant bullshit.
> 
> there is *no* need for a web page to use wifi.

You say all sorts of things, but you never back up anything.
It's as if you don't want to help the OP.
All you want to do is protect your decision to purchase Apple products, and 
to stay entirely within the self-imposed walled garden.

You bought on:
a. fear
b. cachet
c. single-vector solutions

So, anything that threatens that, is a threat to you.

a. You fear any operating system outside of Apple's own operating systems 
or Windows that is NOT running hundreds upon hundreds upon hundreds of 
megabytes of Apple bloatware just to get the *simplest* of jobs done, like 
transferring a file (which should take zero additional software!).

b. You never bought on performance so anything that works better (which is 
just about everything, if you include working outside the walled garden as 
a criterion), is a threat to you - for example, bluetooth file transfer is 
universal outside of iOS yet you deprecate it simply because you can't do 
it. You need hundreds upon hundreds upon hundreds of megabytes of bloatware 
to perform your vaunted tasks, and even then, they fail to connect so 
something as ubiquitous as Linux.

c. You can only think of the single-button-mouse solution that Apple 
provides to you. So if that's Airdrop, that's the *only* way you can think, 
and it doesn't even dawn on you that Airdrop doesn't work outside the 
vaunted walled garden. Likewise with your iTunes suggestions, which, again, 
don't work outside the walled garden and which take hundreds upon hundreds 
upon hundreds of megabytes of Apple bloatware just to perform the absolute 
simplest of tasks, and even then, you're hugely restricted as to what you 
can do, and often the bloatware will *destroy* your painstakingly prepared 
libraries without even so much as a mention that they're totally destroying 
everything you worked on outside the walled garden.

Only in the *latest* release is there even a *hint* that Apple will destroy 
everything, and that's because tens of thousands of people complained about 
your vaunted software destroying everything without a single obvious and 
overt warning at the time they were destroying *all* your data.

Trust me - I know *exactly* how you Apple Mongers think, and, I know that 
you will defend Apple at all costs (of course, never with sufficient detail 
so as to be useful) - and worse - you don't help the OP because your main 
concern is to protect your Apple image borne of 
a. Fear
b. Cachet
c. Single-button-mouse solutions

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

#32930

In article <nnik28$1ghi$1@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:

> 
> > more ignorant bullshit.
> > 
> > there is *no* need for a web page to use wifi.
> 
> You say all sorts of things, but you never back up anything.

you're lying and trolling, yet again.

> It's as if you don't want to help the OP.

i did help the op.

all you're doing is trolling.

the rest of your ignorant, fabricated and flat out nonsensical babble
snipped.

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

#32933

On Sat, 30 Jul 2016 16:19:21 +0000 (UTC), Aardvarks wrote:

> Trust me - I ...

I've learned never to trust anyone who needs to urge, "Trust me ... ."

Cheers, over, and out, -- tlvp
-- 
Avant de repondre, jeter la poubelle, SVP.

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

#32946

On Sat, 30 Jul 2016 13:21:11 -0400, tlvp wrote:

> I've learned never to trust anyone

Do you think the Google transfer method will work for you?
http://i.cubeupload.com/5LnJ8M.gif

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

#32951

On Sun, 31 Jul 2016 03:12:40 +0000 (UTC), Aardvarks wrote:

> Do you think the Google transfer method will work for you?
> http://i.cubeupload.com/5LnJ8M.gif

No idea. I use the decidedly 20th century method of copying to a microSD
card in the handset, and then moving that card to wherever I really want to
transport the copy. That's what floats my boat. Devices incapable of using
microSD cards will have to be particularly desirable before they have any
place in my equipment firmament, sorry :-) . But that's me. Cheers, -- tlvp
-- 
Avant de repondre, jeter la poubelle, SVP.

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

#32968

On Sat, 30 Jul 2016 23:50:50 -0400, tlvp wrote:

> No idea. I use the decidedly 20th century method of copying to a microSD
> card in the handset, and then moving that card to wherever I really want to
> transport the copy. That's what floats my boat. Devices incapable of using
> microSD cards will have to be particularly desirable before they have any
> place in my equipment firmament, sorry :-) . But that's me. Cheers, -- tlvp

I just had a look at this:

Use Nearby to interact with what┬ around you
https://support.google.com/accounts/answer/6260286?hl=en

Which said:
Nearby helps you find and interact with services and devices close to you
(within about 30 m or 100 ft).

Nearby discoveries" uses only low-power Bluetooth to detect broadcasts
around your device.

"Nearby apps" uses a combination of Bluetooth, Wi-Fi, and inaudible sound
to detect devices around your device.

But, apparently it's not useful for file transfer.

So, if Nearby doesn't work for that OP, then maybe Android Beam will.
Use Android Beam to share content by NFC
https://support.google.com/nexus/answer/2781895

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

#32980

On Sun, 31 Jul 2016 20:27:01 +0000 (UTC), Aardvarks wrote:

> On Sat, 30 Jul 2016 23:50:50 -0400, tlvp wrote:
> 
>> No idea. I use the decidedly 20th century method of copying to a microSD
>> card in the handset, and then moving that card to wherever I really want to
>> transport the copy. That's what floats my boat. Devices incapable of using
>> microSD cards will have to be particularly desirable before they have any
>> place in my equipment firmament, sorry :-) . But that's me. Cheers, -- tlvp
> 
> I just had a look at this:
> 
> Use Nearby to interact with what¢s around you
> https://support.google.com/accounts/answer/6260286?hl=en
> 
> Which said:
> Nearby helps you find and interact with services and devices close to you
> (within about 30 m or 100 ft).
> 
> Nearby discoveries" uses only low-power Bluetooth to detect broadcasts
> around your device.
> 
> "Nearby apps" uses a combination of Bluetooth, Wi-Fi, and inaudible sound
> to detect devices around your device.
> 
> But, apparently it's not useful for file transfer.
> 
> So, if Nearby doesn't work for that OP, then maybe Android Beam will.
> Use Android Beam to share content by NFC
> https://support.google.com/nexus/answer/2781895

What's your point? I have BT on exactly *one* device. I have NFC on *none*.
Sounds, for me, being audible, an inaudible sound is a hopeless oxymoron.
And your Nearby is pretty far from anything I'd ever need or use. 

"Trust me," I hope you don't mind :-) . Cheers, -- tlvp
-- 
Avant de repondre, jeter la poubelle, SVP.

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

#32985

On Sun, 31 Jul 2016 21:52:55 -0400, tlvp wrote:

> What's your point?

I'm trying to help the OP by giving the OP options.

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

#32987

In article <nnmo8p$uvl$1@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:

> I'm trying to help the OP by giving the OP options.

bullshit.

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

#33004

On Mon, 01 Aug 2016 02:11:02 -0400, nospam wrote:

>> I'm trying to help the OP by giving the OP options.
> 
> bullshit.

Since the OP isn't responding, he either hasn't tried the options, or,
doesn't have the time, or didn't like the answer.

Until the OP responds, we'll never know.

But please clean up your language.
This is the Usenet, after all. 

:)

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

#33008

In article <nnognh$1s4h$1@gioia.aioe.org>, Aardvarks
<aardvarks@a.b.c.com> wrote:

> 
> >> I'm trying to help the OP by giving the OP options.
> > 
> > bullshit.
> 
> Since the OP isn't responding, he either hasn't tried the options, or,
> doesn't have the time, or didn't like the answer.

or he realizes the thread has been derailed, thanks to you.

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

#33126

On 07/30/2016 09:50 PM, tlvp wrote:
> On Sun, 31 Jul 2016 03:12:40 +0000 (UTC), Aardvarks wrote:
>
>> Do you think the Google transfer method will work for you?
>> http://i.cubeupload.com/5LnJ8M.gif
>
> No idea. I use the decidedly 20th century method of copying to a microSD
> card in the handset, and then moving that card to wherever I really want to
> transport the copy. That's what floats my boat. Devices incapable of using
> microSD cards will have to be particularly desirable before they have any
> place in my equipment firmament, sorry :-) . But that's me. Cheers, -- tlvp
>

https://www.amazon.com/Lightning-iFlash-Reader-Android-iPhone/dp/B017QS7BQ4

-- 
http://totally-portable-software.blogspot.com
   [Sat Mar 26: "Documentation and Portability"]

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

#33146

On Fri, 5 Aug 2016 08:31:00 -0600, crankypuss wrote:

> https://www.amazon.com/Lightning-iFlash-Reader-Android-iPhone/dp/B017QS7BQ4

Cute USB/microUSB-based OTG card reader/writer. Thanks. Good to know of.

Cheers, -- tlvp
-- 
Avant de repondre, jeter la poubelle, SVP.

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

#33149

tlvp wrote:

> crankypuss wrote:
>
>> https://www.amazon.com/Lightning-iFlash-Reader-Android-iPhone/dp/B017QS7BQ4
>
> USB/microUSB-based OTG card reader/writer.

Presumably for iThings it functions only as a reader, but for Android 
devices it can read and write?

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

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

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

csiph-web