On Wed, 4 Mar 2020 04:20:56 -0000 (UTC), Arlen Holder wrote:
> Do you think kdeconnect can allow us to write to the non-rooted Android
> system file system (as adb is documented to do, but it didn't work for me).
Hi J.O. Aho,
Thank you very much for being a purposefully helpful adult on Usenet, and
by letting us know that the libMTP solutions aren't well supported but that
KDEConnect suggestion appears to be a keeper!
KDE Connect runs on 4 of the 5 common consumer platforms, most notably
o Android (the Wi-Fi client)
o Linux (the Wi-Fi server)
I installed the Windows version of KDE Connect and tested on my $100 Moto
G7 running Android 9, where my high-level summary is these 3 comments:
1. *The KDE Connect "Send files" over Wi-Fi button is to die for!*
2. There's some "strange magic" in addition to the "Send files" button.
3. I haven't found yet how to copy a desktop hosts to Android /etc/hosts.
*Regarding the "Send files" button, it's FANTASTIC!*
o You hit the button on Android & select the files you want to send.
o Those files end up on the desktop, in the KDE Connect "default" folder.
You'd "think" the default folder would be what the installer created:
C:\Users\{you}\AppData\Local\kdeconnect\.
But you'd be wrong as _nothing_ (yet) shows up in that default folder:
Instead, the "Send files" sends files to the Windows "Downloads" folder:
C:\Users\{you}\Downloads\.
Which, for most people, would make sense, but for me, that folder didn't
even _exist_ prior to me installing KDE Connect.
So KDE Connect must have _created_ that Downloads folder with a hard-coded
call, since I long ago _moved_ all the "special" folders to a
well-organized hierarchy that is well planned ahead of time consisting of
only four folders for all single-user Windows systems I own:
C:\data {for data I care about long term}
C:\tmp {for data I only care about short term}
===
C:\software {virgin software installers saved in an organized hierarchy}
C:\apps {installed software in the exact same well organized hierarchy}
For those organizational purposes the Windows "special folders" were moved
long ago to the "tmp" hierarchy, I was surprised that KDE Connect had a
hard-coded call to _create_ that Windows special folder, because most
application programs use the Windows %whatever% link to put things in the
special folder in my tmp hierarchy.
I'm sure we can set the desktop KDE Connect defaults, but every time I
tried, the desktop KDE Connect crashed; but once I found that KDE Connect
created the "Downloads" folder via a hard-coded call, I realized that the
coders probably never assumed anyone would be intelligent about an
organized file system on Windows (I do the same on Linux & Android as the
philosophy transcends operating systems - where only on iOS is it not
possible to have an organized file system).
All I really want out of KDE Connect is two things:
1. The "Send files" from Android to the desktop (which is to die for), and,
2. The ability to "Receive files" from the desktop to Android
(where the ideal goal would be to receive a 'hosts' file)
As an aside, it's interesting the unexpected "magic" of KDEConnect, where,
for example, the Android phone can control the cursor and right and left
click of the desktop. That's magic that I don't know what I'd do with.
More "magic" is that the phone can control a slide show "next slide" and
"previous slide" button.
Even more "magic" is the phone can control the media player on the desktop,
and the phone can run commands on the desktop and the phone can receive
commands from the desktop.
In addition, there's "magic" for the desktop to send and receive SMS
messages, and for the desktop to receive notifications (e.g., that calls
are coming in on the phone).
While I don't know if I'll ever use the "magic" above, the KDE Connect app
is a keeper if only for it's rather nice ability to extremely easily "send
files" over WiFi to four of the five common consumer OS's on the LAN
(although I didn't try to send files to another Android device).
The one thing I haven't seen yet, but I'm still just scraping the surface
of KDE Connect, is the ability to bring the desktop hosts file over into
the protected file system of the non-rooted Android 9 hierarchy.
--
Together, purposefully helpful people make Usenet a useful public helpdesk.