MX Linux Forum

Hi All,

Can't seem to download photos from my android phone. Here's what was tried so for:

In developer options, I enabled debugging over USB and set USB format to data transfer.

When MX is connected to the phone over USB, MX throws a dialog box telling me to select an app for the mounted device. I choose "open with file manager" and a two-pane file manager pops up. Drilling down into Store --> DCIM --> camera, the picture filenames are visible. When I try to copy photos to the linux box, MX tells me it's copying but no transfer takes place. After 30 seconds or so, linux throws an error: Unknown error -- timeout reading from or writing to port.

Kinda lost here -- permissions problem maybe? Any thoughts on what I'm doing wrong?

I have not tried a USB connection, but have been successful by using kdeconnect. The phone shows up in dolphin and you can drill down to the appropriate camera folder. Both computer and phone need to be on the same wifi network.

richb wrote: Thu Nov 19, 2020 4:46 pm I have not tried a USB connection, but have been successful by using kdeconnect. The phone shows up in dolphin and you can drill down to the appropriate camera folder. Both computer and phone need to be on the same wifi network.

I was sure happy to have found a way thru this -- then I looked at the permissions on the APK. Holy cow:


Permissions

view Wi-Fi connections
Allows the app to view information about Wi-Fi networking, such as whether Wi-Fi is enabled and name of connected Wi-Fi devices.
run at startup
Allows the app to have itself started as soon as the system has finished booting. This can make it take longer to start the phone and allow the app to slow down the overall phone by always running.
have full network access *****
Allows the app to create network sockets and use custom network protocols. The browser and other applications provide means to send data to the internet, so this permission is not required to send data to the internet.
view network connections
Allows the app to view information about network connections such as which networks exist and are connected.
change network connectivity *****
Allows the app to change the state of network connectivity.
connect and disconnect from Wi-Fi
Allows the app to connect to and disconnect from Wi-Fi access points and to make changes to device configuration for Wi-Fi networks.
allow Wi-Fi Multicast reception
Allows the app to receive packets sent to all devices on a Wi-Fi network using multicast addresses, not just your phone. It uses more power than the non-multicast mode.
read phone status and identity *****
Allows the app to access the phone features of the device. This permission allows the app to determine the phone number and device IDs, whether a call is active, and the remote number connected by a call.
read your contacts *****
Allows the app to read data about your contacts stored on your phone, including the frequency with which you've called, emailed, or communicated in other ways with specific individuals. This permission allows apps to save your contact data, and malicious apps may share contact data without your knowledge. *****
read the contents of your shared storage *****
Allows the app to read the contents of your shared storage. *****
control vibration
Allows the app to control the vibrator.
modify or delete the contents of your shared storage *****
Allows the app to write the contents of your shared storage. *****
android.permission.DOWNLOAD_WITHOUT_NOTIFICATION *****
run foreground service
Allows the app to make use of foreground services.
read call log
This app can read your call history. ******
send and view SMS messages ******
Allows the app to send SMS messages. This may result in unexpected charges. Malicious apps may cost you money by sending messages without your confirmation.
read your text messages (SMS or MMS)
This app can read all SMS (text) messages stored on your phone. *****
receive text messages (SMS) *****
Allows the app to receive and process SMS messages. This means the app could monitor or delete messages sent to your device without showing them to you. *****
receive text messages (MMS) *****
Allows the app to receive and process MMS messages. This means the app could monitor or delete messages sent to your device without showing them to you.
prevent phone from sleeping
Allows the app to prevent the phone from going to sleep.
request install packages *****
Allows an application to request installation of packages.
android.permission.USE_FULL_SCREEN_INTENT
access precise location only in the foreground
This app can get your exact location only when it is in the foreground. These location services must be turned on and available on your phone for the app to be able to use them. This may increase battery consumption.
record audio
This app can record audio using the microphone at any time. ********



I really appreciate the suggestion but those permissions look like a perfect recipe for a privacy/security disaster. I'm running a custom Android ROM without Gapps because I just can't see my way to agree to become a victim.

I thought I would try the ADB utilities. Typing "adb --help" gave me this:

file transfer:
push [--sync] LOCAL... REMOTE
copy local files/directories to device
--sync: only push files that are newer on the host than the device
pull [-a] REMOTE... LOCAL
copy files/dirs from device
-a: preserve file timestamp and mode
sync [system|vendor|oem|data|all]
sync a local build from $ANDROID_PRODUCT_OUT to the device (default all)
-l: list but don't copy


Looking for clarification, I went to https://www.androidauthority.com/androi ... ll-601015/

I pulled up the Dolphin browser and set it to show the full path in the location bar and title bar. Taking the locations, I put together this in a term:


user451@debian:~
$ adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
f0f1bbbe device

user451@debian:~
$ pull camera:/Google%2520Inc%2520Nexus%252FPixel%2520(MTP+ADB)@usb:003,007/store_00010001/DCIM/Camera/*.jpg /home/user451/Downloads/oneplus/
bash: syntax error near unexpected token `('

It doesn't seem to like my syntax .......

I suspect disabling some of plugins in kdeconnect would eliminate some of those permissions. Just keep what you want.

Most KDE connect privileges are simply intended for use. The application is used to send text messages, connections, file transfer, and find a device. This is not a bad idea. I've been using it for a long time and I'm not complaining.

A nice and fast solution to transfer files to/from android devices (via a wi-fi network) is installing "Sweech" on the device. It's a free app, without adds, that shares files over http (this means you only need to use a browser on the other side of the file transfer)

P.

It has always just worked for me, as long as I remember to pull down the top bar and change the USB mode. I also just use one of the web-based apps, which are incredibly easy--for me, AirDroid.