Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Android to Windows

28 views
Skip to first unread message

Optimist

unread,
Apr 6, 2020, 10:32:19 AM4/6/20
to
Why is it that Windows does not allow pictures to be upload from Android to Windows using a wireless
LAN? And is there a way of uploading text messages apart from emailing each one individually?

Anyone would think we are not in the 21st century!

Andy Burns

unread,
Apr 6, 2020, 10:49:05 AM4/6/20
to
Optimist wrote:

> Why is it that Windows does not allow pictures to be upload from Android to Windows using a wireless
> LAN? And is there a way of uploading text messages apart from emailing each one individually?

Not sure if anyone is offering pre-built versions of this?

<https://github.com/google/samba-documents-provider>

> Anyone would think we are not in the 21st century!

Or just let the phone sync your photos half-way round the world to a
google photos account, and then let the PC copy them back again ...

R. Mark Clayton

unread,
Apr 6, 2020, 2:35:01 PM4/6/20
to
Mine has a PC program called SideSync. You can type in and copy texts in an image of the phone on the screen.

actodesco

unread,
Apr 6, 2020, 2:38:57 PM4/6/20
to
I'm not 100% sure I understand. I use an app "Airdroid" which allows me
to exchange pics between my windows computer and android phone, in
either direction.

Andy Burns

unread,
Apr 6, 2020, 2:55:19 PM4/6/20
to
actodesco wrote:

> Andy Burns wrote:
>
>> let the phone sync your photos half-way round the world to a
>> google photos account, and then let the PC copy them back again ...
>
> I'm not 100% sure I understand.

Tell the phone to upload each new photos to your google account [you can
restrict it to wifi only if you don't have a generous 4G data allowance]

then, a few seconds after each photo has been taken, it is available to
view or download from <https://photos.google.com>

Big Al

unread,
Apr 6, 2020, 3:29:45 PM4/6/20
to
For text messages, I have PushBullet add-on in Firefox, and the app in
Android. It allows me to send and receive (and view) text messages on
my computer, I don't have to touch the phone. As a matter of fact, my
wife went for a drive the other day and I still got the text message
that my prescription was ready at the Px.

Windows 10 supposedly has a app to link your phone but I've never gone
there, I run Linux.

Al

Andy Burns

unread,
Apr 6, 2020, 3:34:59 PM4/6/20
to
Big Al wrote:

> For text messages, I have PushBullet add-on in Firefox, and the app in
> Android.   It allows me to send and receive (and view) text messages on
> my computer, I don't have to touch the phone.

If you use Android's standard text message app, that functionality is
built-in, simply visit on your PC

<https://messages.google.com/web>

It shows a QR code on screen, you scan that on your phone, and then you
can send/receive text messages on the computer.

Arlen Holder

unread,
Apr 6, 2020, 3:51:46 PM4/6/20
to
In response to what Optimist <curmu...@mailinator.com> wrote :
Hi Optimist,

Windows can treat Android over WiFi the same as Windows treats Windows...
o Even down to the command line (& certainly at the file manager GUI level).

To that end, here's a summary snippet from a thread referenced below which may help you:
o *From Windows, how can we open a command line on the Android filesystem?*
<https://groups.google.com/d/msg/comp.mobile.android/vmWWLzPHKt0/dZJGwHt9AwAJ>
=== === <begin verbatim summary snippet> === ===
The best Windows solution is to mount Android as a drive letter over WiFi:
o WebDAV <http://www.bild.me/bild.php?file=8605173dir05.jpg>
o DirectNetDrive <http://www.bild.me/bild.php?file=6340420dir012.jpg>
o NetDrive v1.3.2.0 <http://www.bild.me/bild.php?file=1383190dir014.jpg>
o webdav <http://www.bild.me/bild.php?file=2373390dir019.jpg>
o netdrive <http://www.bild.me/bild.php?file=3994244dir020.jpg>
=== === <end verbatim summary snippet> === ===

Diving into more detail on only the first question you asked in this thread today:
o *Android to Windows*, by Optimist <curmu...@mailinator.com>
<https://groups.google.com/forum/#!topic/uk.telecom.mobile/Wluxln3nP1w>
The permanent Usenet record will clearly show there are _many_ ways to
bidirectionally send/receive photos to/from Android/Windows
(over LAN or USB or ad hoc networks) in our permanent public tribal
knowledge archives:
o <http://tinyurl.com/comp-mobile-android>
o <http://comp.mobile.android.narkive.com>

For just one example we recently discussed how to do this over an ad-hoc
encrypted Wi-Fi network, using KDEConnect open source freeware.
o *KDE Connect is a keeper for sending & receiving files over your Wi-Fi LAN*
*to/from any desktop to/from any Android phone!*
<https://groups.google.com/d/msg/comp.mobile.android/4x1rf1JefW8/vAuFR7ltAQAJ>
Where KDE Connect does more than just transfer from/to desktops over WiFI:
o End-to-end TLS encryption
o Send/receive files
o Notification on desktop of SMS texts
o Notification on desktop of incoming phone calls
o Syncing of contacts between phone & desktop
o Shared clipboard, e.g., copy and paste URLs between devices.
o Turns the phone screen into a wi-fi wireless mouse
o Android notifications show up on the desktop
o Control desktop video/audio player from Android
o Controls desktop slideshow next slide/previous slide from Android
o Runs commands remotely
etc.

However, given Android essentially 'mounts' (as a drive letter) on Windows
such that it looks the same as any other Windows drive letter over the LAN,
you can even run Windows commands from Windows on Android (like "copy"),
which, of course, work from the file manager GUI level also (of course).

Here's a thread that shows exactly how I tested that capability years ago.
o *From Windows, how can we open a command line on the Android filesystem?*
<https://groups.google.com/d/msg/comp.mobile.android/vmWWLzPHKt0/bG6EHd8GBQAJ>

Bear in mind that thread contains technical value of import to your question,
but, unfortunately, the dozen proven worthless pieces of shit trolls below
grossly infested that thread such that you can ignore anything & everything
they said (and even ignore everything Paul said) and just concentrate on about
10% of what Frank said, and just read my posts for the added value of that thread).

This thread is literally the PERFECT thread to show how these proven worthless
pieces of shit ruin Usenet for everyone trying to add on-topic technical value.
Don't take my word for it - just read the thread - which proves every statement
by me just now to be a fact.

Literally, _every_ post from these posters _proves_ that they can only subtract
value, which is why they're all easily proven worthless pieces of shit you'll
just have to ignore in that otherwise rather useful technical thread.
o *Ken Blake* [From: Ken Blake <K...@invalid.news.com>]
o *Wolf K* [From: Wolf K <wol...@sympatico.ca>]
o *Danny DeVito* [From: Danny DeVito <inv...@invalid.invalid>]
o *Char Jackson* [From: Char Jackson <no...@none.invalid>]
o *Rudy Wieser* [From: "R.Wieser" <add...@not.available>]
o *Sam Hill* [From: Sam Hill <s...@example.com>]
o *joe* [From: joe <no...@domain.invalid>]
o *Good Guy* [From: �� Good Guy �� <Hello...@Example.com>]
o *Mike S.* [From: Mike S. <Mi...@fred.com>]
o *Idaho Homo Joe* [From Idaho Homo Joe <dick...@aol.com>]
o *Knarf Gewtools* <th...@ddress.is.invalid> (also Knarf Gewtools Slootweg)
o *Diesel* [From: Diesel <nob...@haph.org>]
(Not one of which knows _anything_ about either Android or Windows)
Where, of over 100 posts by 15 authors, only _two_ authors added value:
o Frank Slootweg & me (where 90% of Franks posts were childish & worthless)
(But 100% of the posts from the named trolls were even more worthless)
o Where even Paul posted wholly off-topic pure drivel in that thread.
Where, for example, this one post adds more on-topic value than those many
worthless pieces of shit have ever posted to Usenet in their entire lives):
<https://groups.google.com/d/msg/comp.mobile.android/vmWWLzPHKt0/MRnbOIp5BQAJ>

=== === <begin verbatim tiny snippet of on-topic value> === ===
============================================================
How to mount Android filesystem as a drive letter on Windows
over WiFi using a free WebDav server on Android

Download and install any desired WebDav server on Android:

<https://play.google.com/store/apps/details?id=com.theolivetree.webdavserver>
Read basic documentation:
<https://www.webdavsystem.com/server/access/windows/>

You can run a WebDAV, FTP, HTTP (or even SMB if you're rooted)
server on Android, which you can then mount on Windows as a drive letter.
<http://www.bild.me/bild.php?file=8605173dir05.jpg>

WebDAV:
0. Make sure your Android device is on the local WiFi network
1. Download a WebDav server on Android
2. Start that WebDav Server on Android
3. A message says: "WebDAV server available on http://192.168.1.6:8080"
Home directory: /storage/emulated/0, password disabled
4. Change WebDav Server: Settings > Home Directory = Root (/)
5. On Windows, open a r/w network share using the address:
http://192.168.1.6:8080
6. Or, on Windows, right click on "ThisPC" & select "Map Network Drive"
(Y:) = \\192.168.1.6@8080\DavWWWRoot\
7. Or, on Windows, in the command line, type:
net use X: \\192.168.1.6@8080\DavWWWRoot\

Any of those commands will mount the root of the Android file system
as a drive letter on Windows, over WiFI so that you can run DOS
commands on that Android file system over WiFi.
<http://www.bild.me/bild.php?file=8605173dir05.jpg>
=== === <end verbatim tiny snippet of on-topic value> === ===

Bear in mind there is more to that thread than just the LAN solution,
since we also solved the USB solution of mounting Android as a Windows drive,
but you only asked for the LAN (WiFi) solution, one of which is shown above.

For example, this post discussed running Windows commands (such as "copy") over
both USB & WiFi so bidirectionally copy files back & forth
(using either the native file manager of Windows, or the command line, or the
Android file managers, i.e., whatever method you prefer to employ):
<https://groups.google.com/d/msg/comp.mobile.android/vmWWLzPHKt0/YEtLmkmPBgAJ>

Where, again, this is just a tiny snippet of the useful information outlined
in that _one_ post below (which, again, itself, is more value added to this
newsgroup than every post combined by the score of named worthless
pieces of shit who infested that very same thread in droves):
=== === <begin small verbatim snippet of on-topic technical value> === ===
I seem to be able to run DOS commands on both these types of connections:
o USB + "removable drive" (to get a drive letter)
<http://www.bild.me/bild.php?file=1853998dir02.jpg>
o WiFi + "network location" + "removable drive" (to get a drive letter)
<http://www.bild.me/bild.php?file=6340420dir012.jpg>
o WiFi + "network location" + "net use" (to get a drive letter)
<http://www.bild.me/bild.php?file=8605173dir05.jpg>
... ... stuff removed ... ...
Given:
o USB solutions are faster & generally simpler (no Android software)
MTPDrive: <http://www.bild.me/bild.php?file=1853998dir02.jpg>
Linux: <http://www.bild.me/bild.php?file=6181360dir01.jpg>
o WiFi solutions (which generally require a "server" running on Android).
WebDav: <http://www.bild.me/bild.php?file=8605173dir05.jpg>
FTP: <http://www.bild.me/bild.php?file=7687244dir06.jpg>

For USB:
The best solution is a freeware equivalent to the MTPDrive functionality
o LibMTP freeware may work if we can figure out how to make it work, while
<https://sourceforge.net/projects/libmtp/files/libmtp-win32/>
o MTPDrive crippleware works (crippled to 30 files per session), and,
<http://www.mtpdrive.com/download.html>
o Dual booting to Linux works (which natively uses, apparently, LibMTP).
<http://www.bild.me/bild.php?file=6181360dir01.jpg>

For WiFi:
If a server must be run on Android, Windows probably handles SMB best, but:
o SMB server (on Android) solutions are problematic for two reasons:
(a) No known Play/F-Droid SMB server works on TCP port 445 unrooted
(b) Port forwarding on Windows is required if a nonroot server is found.
<https://play.google.com/store/apps/details?id=com.icecoldapps.sambaserver>

Where these general-use servers don't require rooting or port forwarding,
& where Windows "network location" & "removable drive" features are used:
o WebDav
<https://play.google.com/store/apps/details?id=com.theolivetree.webdavserver>
network location: <http://www.bild.me/bild.php?file=8605173dir05.jpg>
o FTP
<https://play.google.com/store/apps/details?id=com.theolivetree.ftpserver>
<http://www.bild.me/bild.php?file=7075400dir07.jpg>
<http://www.bild.me/bild.php?file=4731516dir011.jpg>

For WiFi FTP, these are possible universal free drive-mapping solutions:
o FTPuse (freeware which I was not successful with in my recent tests)
<https://www.ferrobackup.com/map-ftp-as-disk.html>
FTP Server (free): <http://www.bild.me/bild.php?file=3316456dir08.jpg>
The Olive Tree: <http://www.bild.me/bild.php?file=7355568dir09.jpg>
Anonymous: <http://www.bild.me/bild.php?file=4223201dir010.jpg>
o DirectNet (freeware which I was successful with in my tests today)
<http://www.directnet-drive.net/>
<http://www.bild.me/bild.php?file=4731516dir011.jpg>
<http://www.bild.me/bild.php?file=6340420dir012.jpg
o SFTP Net Drive (free for personal use but I was not successful today)
<https://www.nsoftware.com/sftp/netdrive/> (it took a bogus name & email)
o NetDrive (trialware, untested because it's not a general solution)
<http://netdrive.net/>
o Web Drive (trialware, untested because it's not a general solution)
<https://webdrive.com/download/>

And where Linux solutions may work under some circumstances:
o Dual-boot to Linux works perfectly (which uses LibMTP natively)
<https://groups.google.com/d/msg/alt.os.linux/oOfdMLmJ-oQ/jh_1DwTOBgAJ>
o Termux (contains a mini Linux command environment)
<https://play.google.com/store/apps/details?id=com.termux>
... ... stuff removed ... ...
=== === <end small verbatim snippet of on-topic technical value> === ===

Notice the permanent Usenet record shows that in the referenced thread
Frank and I were able to add unique tested & validated on-topic technical value,
(and Paul added worthless drivel, but he was responding to the drivel),
but that the rather valuable on-topic technical topic value was absolutely
swamped by the dozen worthless pieces of shit listed above who infested
that thread simply because they appear to _hate_ that they, themselves,
have never once in their entire lives added any on-topic technical value
to any thread - and certainly not to that thread.

If ever an adult needs to see how these dozen named worthless pieces of shit
_hate_ that they can't ever add value to any technical topic, this thread
in our permanent archives is all any adult needs to view to realize how these
dozen proven worthless pieces of shit are the type that ruin Usenet for everyone.

Luckily, the answer, if you wade through it, to your first question,
is in that thread, which we posted years ago (in advance of your question).

Hope this helps, where if you detect a sense of disgust in my voice
for the dozen proven worthless pieces of shit, it's because those proven
worthless pieces of shit are who ruin the value of Usenet for everyone.
--
Those who have never once posted value already proved that they can't.

Big Al

unread,
Apr 6, 2020, 4:39:28 PM4/6/20
to
I'll try.

😉 Good Guy 😉

unread,
Apr 6, 2020, 7:15:06 PM4/6/20
to
What's wrong with using "Google Cloud" or "Google Drive" or for that matter "OneDrive"? 

We are in the 21st century and so there are many ways of doing things but nutters here are so stupid that they won't use anything provided by Microsoft or Google or Amazon.  Why ther are still using their operating system is beyond anybody's wildest imagination.

Path: aioe.org!peer02.am4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx31.am4.POSTED!not-for-mail
From: Optimist <curmu...@mailinator.com>
Newsgroups: alt.comp.os.windows-10,uk.telecom.mobile
Subject: Android to Windows
Organization: I do not believe it
Message-ID: <etem8f1sd0etf67u6...@4ax.com>
User-Agent: ForteAgent/8.00.32.1272
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 4
X-Complaints-To: http://netreport.virginmedia.com
NNTP-Posting-Date: Mon, 06 Apr 2020 14:32:17 UTC
Date: Mon, 06 Apr 2020 15:32:17 +0100
X-Received-Bytes: 808
X-Received-Body-CRC: 2848391735
Xref: aioe.org alt.comp.os.windows-10:111742 uk.telecom.mobile:36510


--
With over 1.2 billion devices now running Windows 10, customer satisfaction is higher than any previous version of windows.

Arlen Holder

unread,
Apr 7, 2020, 4:30:46 AM4/7/20
to
In response to what Andy Burns <use...@andyburns.uk> wrote :

> Tell the phone to upload each new photos to your google account [you can
> restrict it to wifi only if you don't have a generous 4G data allowance]
>
> then, a few seconds after each photo has been taken, it is available to
> view or download from <https://photos.google.com>

Personally, IMHO, it seems, the less people know, the more they fall prey
to marketing persuading them to use the cloud to put your personal data,
just to copy a file between one room and another in your own house!
o *Do people of reasonable technical ability store their private data on*
*the Internet (if so, for what gain?)*
<https://groups.google.com/d/msg/comp.mobile.android/mBIZ-8jGdmk/aLDJkSJQAAAJ>

To help others avoid having to use the Internet just to copy a personal
file from their Android phone to or from a desktop (Mac, Linux, or
Windows), here's my tutorial where I just now again tested installing KDE
Connect on a brand new Windows 10 Pro (version 1909) installation.
o *KDE Connect is a keeper for sending & receiving files over your Wi-Fi*
*LAN to/from any desktop to/from any Android phone!*
<https://groups.google.com/forum/#!topic/comp.mobile.android/4x1rf1JefW8>

These two installation packages worked fine for me just now in my tests:
o *Windows*: <https://download.kde.org/unstable/kdeconnect/1.1/bin/windows/>
<https://i.postimg.cc/65fLFGVm/kde02.jpg>
o *Android*: <https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp>
<https://i.postimg.cc/X7fQ3PWx/kde01.jpg>

I re-installed Windows 10 Pro due to crashes explained in this thread:
o *Windows 10 BSOD indicates a hardware problem - but what hardware is the problem?*
<https://alt.comp.os.windows-10.narkive.com/oL7PTNKu/windows-10-bsod-indicates-a-hardware-problem-but-what-hardware-is-the-problem>

Hence I again tested KDEConnect setup from scratch:
o Where one method worked, and yet, two other tested methods failed.
<https://community.kde.org/KDEConnect#What_is_KDE_Connect.3F>

What worked on Windows today was...
a. I downloaded KDEConnect to Windows 10 Pro (my version is 1909) from:
<https://download.kde.org/unstable/kdeconnect/1.1/bin/windows/>
b. This resulted in the following file:
Name: kdeconnect-kde-1.1-x64-setup.exe
Size: 48096793 bytes (45 MiB)
SHA256: 61E6537322F05F52F52B625B8C24F653280BFA664E9F784770BD6A039AD7C15A
c. I doubleclicked on that file & up popped: "KDE Connect master-937d919"
"Welcome to KDE Connect Setup"
d. It wanted to install into: "C:\Program Files\KDE Connect"
e. I installed to: "C:\app\network\kdeconnect"
f. Where it automatically installed MS Visual C++ as part of the setup.
"Microsoft Visual C++ 2015 Redistributable (x64) 14.0.24210"
g. It put the KDE Connect shortcut in:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\KDE Connect.lnk
TARGET: C:\app\network\kdeconnect\bin\kdeconnect-indicator.exe
START IN: C:\app\network\kdeconnect
h. This automatically started the KDEConnect server on Windows 10 Pro.

What worked on Android was...
A. I installed the Google Play version of KDE Connect client via Aurora
(because I do not even have a Google Account on my phone)
(and because it was a 50:50 crap shoot of Google Play versus F-Droid)
B. That installed KDE Connect, by KDE Community
<https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp>
C. Which, after multiple permission requests, showed a "Send files" button
which sent files from Android to the PC users' "Downloads" directory:
C:\Users\{username}\Downloads\file_from_android.jpg

WHAT FAILED.
This KDEConnect failed to work on that same Windows PC:
<https://binary-factory.kde.org/view/Windows%2064-bit/job/kdeconnect-kde_Nightly_win64/>

This also failed to work on that same Windows machine:

<https://www.reddit.com/r/Windows10/comments/dnh1wq/test_release_01_kde_connect_for_windows/>
o Which pointed to this GitHub location for the KDE Connect desktop:
<https://github.com/taskmaster9001/kdeconnect-kde/releases/tag/v0.1.0>
o Which specifically pointed to this executable:
<https://github.com/taskmaster9001/kdeconnect-kde/releases/download/v0.1.0/KDE.Connect.for.Windows.exe>

In summary, this worked on my latest Windows 10 Pro installation:
o *Windows* <https://download.kde.org/unstable/kdeconnect/1.1/bin/windows/>
<https://i.postimg.cc/65fLFGVm/kde02.jpg>
o *Android* <https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp>
<https://i.postimg.cc/X7fQ3PWx/kde01.jpg>
--
Every thread on Usenet should increase our overall group tribal knowledge.

AnthonyL

unread,
Apr 7, 2020, 8:01:19 AM4/7/20
to
My Android connects over the LAN to my Windows and Linux machines
using Total Commander and its SMB/Samba add-on. You do need to know
the IP of each machine when setting the links up. There are Android
tools however to ping every IP on the LAN if you look around.

I did have an Android file manager that automatically saw the LAN,
might have been by AsusTek but I must have ended up preferring
TotalCommander.


--
AnthonyL

Why do scientists need to BELIEVE in anything?

Arlen Holder

unread,
Apr 7, 2020, 10:55:05 AM4/7/20
to
In response to what AnthonyL <nos...@please.invalid> wrote :

> My Android connects over the LAN to my Windows and Linux machines
> using Total Commander and its SMB/Samba add-on. You do need to know
> the IP of each machine when setting the links up. There are Android
> tools however to ping every IP on the LAN if you look around.

One caveat we learned the hard way on SMB between Windows & Android
o About port 445

If you're not rooted, then you can only run the SMB client on Android.
o If you're rooted, then you can run a SMB server on Android.

The reason is that Android requires root to use ports below 1024;
o Windows requires SMB communications using TCP ports below 1024.

See workarounds in <http://tinyurl.com/comp-mobile-android> archives:
o What's the best way to forward SMB TCP port 445 to something higher than 1024 on Windows?
<https://groups.google.com/d/msg/comp.mobile.android/3QQ8bAZeXNI/p7yqvwHrBQAJ>
--
Usenet is where purposefully helpful adults publicly share solutions.

Peter Johnson

unread,
Apr 7, 2020, 11:09:15 AM4/7/20
to
On Mon, 06 Apr 2020 15:32:17 +0100, Optimist
<curmu...@mailinator.com> wrote:

>Why is it that Windows does not allow pictures to be upload from Android to Windows using a wireless
>LAN? And is there a way of uploading text messages apart from emailing each one individually?
>
I use a Microsoft App that allows me to copy pictures from my Samsung
Android phone to my PC, which it does by WiFi. I think its use is
limited to certain Samsung models at the moment. It also allows me to
read incoming text messages while the phone is sat on its charger and
without me having to get up from the PC.

kelown

unread,
Apr 8, 2020, 4:36:37 AM4/8/20
to

> Why is it that Windows does not allow pictures to be upload from Android to Windows using a wireless
> LAN?

I use MiXplorer with SMBv2 to transfer all types of files back and forth
between my Android and Windows 10 laptop. Windows 10 needs SMBv2 for LAN
transfers.

Paul

unread,
Apr 8, 2020, 6:01:50 AM4/8/20
to
In Windows 10

Programs and Features : Windows Features

there are two tick boxes to install SMBV1.

To get to Control Panels, type "control.exe" or similar in the Run box,
then Pin to Taskbar, to restore the functionality that was removed
some time back.

Paul

Arlen Holder

unread,
Apr 9, 2020, 4:13:11 PM4/9/20
to
In response to what Paul <nos...@needed.invalid> wrote :

>> I use MiXplorer with SMBv2 to transfer all types of files back and forth
>> between my Android and Windows 10 laptop. Windows 10 needs SMBv2 for LAN
>> transfers.
>
> In Windows 10
>
> Programs and Features : Windows Features
>
> there are two tick boxes to install SMBV1.
>
> To get to Control Panels, type "control.exe" or similar in the Run box,
> then Pin to Taskbar, to restore the functionality that was removed
> some time back.
>
> Paul

Hi Paul,

Since you almost always post with purposefully helpful intent, I provide
detailed information below on why I feel SMB (and FTP) pale in comparison
to WebDAV (much to my chagrin, since Samba/CIFs should lead the pack).

I gave up on SMB, but this old thread contains useful version information:
o *Do you know of a free Android SMBv2 (or SMBv3) client?*
<https://groups.google.com/d/msg/comp.mobile.android/tl3Q05QGyAw/yBV1yLArCAAJ>

Where this old thread explains another problem with the SMB solutions:
o *What's the best way to forward SMB TCP port 445 to above 1024 on Windows?*
<https://groups.google.com/d/msg/comp.mobile.android/3QQ8bAZeXNI/p7yqvwHrBQAJ>

And where Frank Slootweg & Fokke Nauta explained the key problem with SMB:
o *Want Windows LAN viewer to open share on Android*
<https://groups.google.com/d/msg/comp.mobile.android/XxuCDi4jkbc/5E5HS_QVBQAJ>

In summary, after years of testing cross-platform copying over Wi-Fi...
1. I gave up on FTP & SMB to copy between Android & Windows over Wi-Fi.

2. I found WebDAV over WiFi more graceful between Windows & Android.
(The entire Android phone is just a standard drive letter on Windows.)
(Everything works on Windows as if the phone is a Windows filesystem.)
(You can't get any more seamless than that, can you?)
(If so, let me know how, as I'm always improving cross-platform copies.)

3. However, for _small_ quick transfers, I've been using KDEConnect lately.
(KDEConnect provides point-&-click bi-directional transfer of files.)

What _would_ be useful is to get past the SMB limitations between Android &
Windows; but until someone figures that out, WebDAV has SMB/FTP beat, IMHO.

BTW, given the most seamless bidirectional transfer between Android &
Windows has always been our goal, a search shows these relevant topics:
o *Tutorial to run any Windows command directly on Android over either USB or Wi-Fi*
<https://groups.google.com/d/msg/comp.mobile.android/JrWLPRYO-TU/2gn6KqccBwAJ>

o *KDE Connect is a keeper for sending & receiving files over your Wi-Fi*
<https://groups.google.com/d/msg/comp.mobile.android/4x1rf1JefW8/7EQp2nr-AAAJ>

o *3 WiFi tests of a network location to a drive letter mapping*
<https://groups.google.com/d/msg/comp.mobile.android/IswZ5yEcpYA/wWuqoICZBgAJ>

o *How to debug flaky Android-to-Windows FTP connection in Windows File Explorer?*
<https://groups.google.com/d/msg/comp.mobile.android/XFtsfaPAqFA/KQzDY3QtAwAJ>

o *What do you use to copy files from Windows XP to Android over WiFi?*
<https://groups.google.com/d/msg/comp.mobile.android/OkDfuDN9fZU/mFAMnIPGFQAJ>

o *Accessing a Windows shared folder from Android using SMB*
<https://groups.google.com/d/msg/comp.mobile.android/Hb5IAnebQmQ/Mc04bs0ZAAAJ>

o *How to get a Windows File Explorer Wi-Fi connection to Android*
<https://groups.google.com/d/msg/comp.mobile.android/ZTg_HVub8ho/2O2X-sAqAgAJ>
etc.

Arlen Holder

unread,
Apr 9, 2020, 7:09:43 PM4/9/20
to
In response to what Arlen Holder <arlen...@anyexample.com> wrote :

> Since you almost always post with purposefully helpful intent, I provide
> detailed information below on why I feel SMB (and FTP) pale in comparison
> to WebDAV (much to my chagrin, since Samba/CIFs should lead the pack).

Paul, and others,

The OP included "uk.telecom.mobile" but, as far as I can tell, this thread
should have gone to "comp.mobile.android" instead of "uk.telecom.mobile".
o Hence, I will set the followup to what it more likely should have been.

I ask that when we add further value to this thread, we all remove u.t.m:
o <http://tinyurl.com/alt-comp-os-windows-10> keep
o <http://tinyurl.com/uk-telecom-mobile> remove
o <http://tinyurl.com/comp-mobile-android> add

Since we all care about seamless cross-platform file copies, here's a
summary based on the half dozen detailed threads in my prior post to Paul.

*SMB/CIFs*
In summary, Android to Windows has so many solutions, IMHO, it's hard to
choose, where we would "think" (and hope!) SMB/CIFs would be the number one
choice, if it weren't for the Android SMB port & Android SMB client issues.

I'm confident the brains on the Windows newsgroup _can_ overcome those SMB
problems, but, to date, I haven't been apprised of a viable solution.

*FTP/sFTP*
In summary, FTP is a second time-honored venerable choice, where FTP
payware "can" appear to be a drive letter on Windows, but FTP freeware
inherently has problems outside of a pure file copy, due to its inherent
design (where "mounting" isn't as seamless in FTP as it is in WebDav,
unfortunately).

If the brains on this ng have a freeware solution to the FTP drive letter
mounting issue, then that would be a great solution to be apprised of.

*WebDAV*
Shockingly, beyond what we'd intuit if we hadn't actually tested this,
surprisingly, WebDav does a key thing absolutely beautifully that the other
solutions don't appear to do, which is _mount_ (literally) the Android
phone as a drive letter on Windows.

Much to my surprise, there's nothing more to do, as, literally...
o "It just works".

*Other Solutions*
For the record, this thread has suggested "other solutions", such as:
o KDEConnect (which works between Android & _any_ Desktop OS!)
o Samba & Google Sync (Andy Burns)
o AirDroid (actodesco)
o Google Cloud & Google Drive (Good Guy)
o Total Commander SMB/Samba add-on (AnthonyL)
o Samsung Wi-fi Transfer (Peter Johnson)
o MiXplorer with SMBv2 (kelown)

While _many_ solutions were purposefully helpfully provided, it's beginning
to become disconcerting that the OP ranted (completely incorrectly), and
yet, has not responded to _any_ of the adults who purposefully aided him.

If anyone complains they can't copy anything from anywhere to anywhere
else, just send them to this purposefully helpful group listed above! :)
--
fup set to [alt.comp.os.windows-10,comp.mobile.android] with removal of
[uk.telecom.mobile], as the OP doesn't pertain to UK telecoms, per se.

Optimist

unread,
Apr 17, 2020, 7:11:46 AM4/17/20
to
Thank you everyone for your replies. I stumbled on the feature in Android to connect to Windows and
it has uploaded photos and texts to the PC, without a cable from the phone!. Not sure whether it
went over my LAN or halfway around the world and back but, hey, it works!

Arlen Holder

unread,
Apr 19, 2020, 9:32:58 PM4/19/20
to
In response to what kelown <kel...@privacy.invalid> wrote :

> You're right Arlen. Thanks for the correction. The result is still that
> bi-directional file transfer is only through a Windows shared folder.
> The only alternatives I can think of for GUI bi-directional transfer are
> FTP or Feem/Airdroid apps.

Hi kelown,

Thanks for confirming, where, we can summarize in agreement that:
o Windows native CIFS/SMB "server" serves an SMBv2 share (over NETBIOS)
o Android added SMBv2 "client" bidirectionally accesses that Windows share

Advantages of this Android SMBv2 client bidirectional copy solution are:
a. It's free (so it's a good candidate for a general purpose solution)
b. It enables bidirectional copy of files over the Wi-Fi LAN from Android
c. It uses a more secure protocol than SMBv1 Android clients did
d. It avoids the Android SMB client port-below-1024 catch-22 rooting issue
e. It will work with all Windows (& Samba Linux) operating systems

The key disadvantage of this Android SMBv2 client solution seems to be:
f. You can't use the Windows file manager GUI for the copying activities

Hence, the "problem" with this solution is the Android file-copy "gui"
isn't as easy to use as compared to the Windows file-copy GUI, in my most
humble of opinions.

That's where key Android 'server' solutions have an advantage over SMB:
o Android WebDAV "server" (enables mounting Android as a Windows drive)
o Android FTP "server" (enables connecting Android as a Windows share)

Bear in mind I tested _every_ viable suggested Wi-Fi solution years ago:
<https://groups.google.com/d/msg/comp.mobile.android/3QQ8bAZeXNI/hMMHk7h4BwAJ>
1. *CIFS methods* (eg Folder Tag with CIFS plugin & Network Browser)
2. *SMB methods* (eg AndSMB, Astro, ES File Explorer, Total Commander)
3. *FTP methods* (eg PrimitiveFTP & FTP Server & WinSCP & FileZilla)
4. *HTTP methods* (eg Wifi Explorer, WiFi File Transfer, WebDAV)
5. *Sync methods* (eg MyPhoneExplorer, AirDroid)
6. *MTP methods* (e.g., libMTP, adb)
etc.

Unfortunately, without rooting, the Android SMB _server_ solution fails.

However, the good news is there are many other Wi-Fi LAN solutions!
<https://groups.google.com/d/msg/comp.mobile.android/9Lu2_dPsu6o/g-8reOTBAAAJ>
--
Usenet is a public potluck where adults politely help each other.

Arlen Holder

unread,
Apr 19, 2020, 9:44:57 PM4/19/20
to
In response to what Optimist <curmu...@mailinator.com> wrote :

> Thank you everyone for your replies. I stumbled on the feature in Android to connect to Windows and
> it has uploaded photos and texts to the PC, without a cable from the phone!. Not sure whether it
> went over my LAN or halfway around the world and back but, hey, it works!

Hi Optimist,

Thank you for reporting back, as we were worried about your success.

It's great you found a working solution, since there are many to choose
from to bidirectionally copy files between Android & Windows over Wi-Fi.
<https://groups.google.com/forum/#!topic/comp.mobile.android/xwX8S7XW-p0>

We expended a lot of work on this project so we thank you for reporting
back your successful results based on one of the replies to your thread.

The beauty of the public Usenet potluck is that everyone can benefit from
the precise details of all solutions involved, which are stored to be found
by others in the future in the web searchable permanent Usenet archives:
o <http://tinyurl.com/uk-telecom-mobile>
o <http://tinyurl.com/comp-mobile-android>
o <http://alt.comp.os.windows-10.narkive.com>
etc.

For others accessing this thread now, and in the future, see also:
o *Tutorial: How to connect Android to Windows as a drive letter*
*over a Wi-Fi LAN for free simple reliable bidirectional copy*
<https://groups.google.com/forum/#!topic/comp.mobile.android/9Lu2_dPsu6o>
--
Usenet allows purposefully helpful sharing of solutions for common benefit.

Arlen Holder

unread,
Apr 21, 2020, 2:35:17 PM4/21/20
to
> It's great the OP found a working solution, since there are many to choose
> from to bidirectionally copy files between Android & Windows over Wi-Fi.
> <https://groups.google.com/forum/#!topic/comp.mobile.android/xwX8S7XW-p0>

UPDATE:

Additionally, while helping out "The Real Bev" in this thread yesterday...
o * NEW PHONE! *, by The Real Bev
<https://groups.google.com/forum/#!topic/comp.mobile.android/d0Y8CqDTaog>

I installed & tested a couple of SMS/MMS backup/restore solutions last
night which seem to solve the OP's second question asking how to back up
(and restore) SMS/MMS messages to (and from) Windows over the Wi-Fi LAN.

Here is a screenshot of my test SMS/MMS XML backup from Android to Windows:
<https://i.postimg.cc/L5WsCrNq/xml01.jpg>

Those two free apps that I tested for SMS/MMS backup/restore are:
o *SMS Backup & Restore*, by SyncTech Pty Ltd
<https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore>
"SMS Backup & Restore is a simple Android app that backs up and
restores your phone's SMS and MMS messages and call logs."
"Backup SMS (text) messages, MMS and call logs in XML format."
o *Super Backup & Restore*, by MobileIdea Studio
<https://play.google.com/store/apps/details?id=com.idea.backup.smscontacts>
"READ YOUR TEXT MESSAGES (SMS OR MMS)/EDIT YOUR TEXT MESSAGES
(SMS OR MMS)

Where I simply copied the results from Android to Windows over Wi-Fi.
<https://groups.google.com/d/msg/comp.mobile.android/ZUEJUrPrEog/YZo2Sx3jAgAJ>

As always, please improve this process so everyone always benefits.
--
Together we can accomplish far more than any one of us can alone.

Arlen Holder

unread,
Apr 22, 2020, 3:45:09 AM4/22/20
to
In response to what Arlen Holder <arlen...@anyexample.com> wrote :

> As always, please improve this process so everyone always benefits.

SOLVED!
<https://i.postimg.cc/wj0n4P9D/xml06.jpg>
<https://i.postimg.cc/kXLV3qx9/xml05.jpg>
<https://i.postimg.cc/26LJtdmC/xml04.jpg>
<https://i.postimg.cc/MpdL7JLk/xml03.jpg>
<https://i.postimg.cc/dtDwkn3V/xml02.jpg>
<https://i.postimg.cc/L5WsCrNq/xml01.jpg>

As a test of the solution to the OP's second question, how to back up
SMS/MMS texts (including photos) to Windows, I decided to restore the XML
backup of my SMS/MMS texts, but to use a _different_ SMS app to restore it
to so I could see if the pictures were also restored.

The restore procedure is interestingly unexpected:
1. On Android, I pressed the RESTORE button in "SMS Backup & Restore"
2. It asked to be set to the default SMS app temporarily.
3. It gave the option to "Restore pictures, media, & group messages (MMS)".
4. Once it finished, it said to choose the "real" SMS app as the default.
5. I installed a different (new) SMS app to make the default SMS app.
6. Once I set that to the default SMS app, the photos showed up inside it.
Voila!

Unless someone suggests a better SMS backup & restore program, my current
recommendation, moving forward, is to back up SMS/MMS using this freeware:
"backs up and restores your phone's SMS and MMS messages and call logs."

Essentially, the steps are:
A. On Android, back up your SMS/MMS & call logs to two XML files.
B. Copy those two XML files to a safe place (e.g., to Windows).
C. On the new Android phone, restore those SMS/MMS messages & call logs.
<https://i.postimg.cc/wj0n4P9D/xml06.jpg>
--
The beauty of helping others on Usenet is we all learn more together.
0 new messages