Bonjour,
Linux Mint Mate 21.2
Phone: Samsung Galaxy 20
On phone, USB debugging is activate. It is connected to PC through the USB port.
On Linux: firewall is off.
On terminal: $ mtp-connect
Device 0 is a samsung galaxy model (mtp)
$ mtp-folder: Successfully connected
libusb_claim_interface() reports interface is busy likely in use by GVFS or KDE MTP. So, no file from my phone are visible.
From gparted, phone is mounted like a disk. (Is it normal?)
I retried with Warpinator on linux and Warpinator on phone. This is the same.
So, my questions are:
Did I forget something?
Do you have an idea, a recommendation?
Regards,
Leloup
[Solved] Impossible to read image on Phone from Linux
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
[Solved] Impossible to read image on Phone from Linux
Last edited by LockBot on Tue Oct 24, 2023 10:00 pm, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Impossible to read image on Phone from Linux
It is not necessary to enable USB debugging. This is mostly for developers that need to push apps and debug them.
To connect for file transfer, you will likely need to open the notifications on the device. Select the option that says something like "Charging this device via USB". Depending on the version of Android, the notification may just expand, with a second line of text saying "Click here for more options" (or equivalent in your locale). This then opens the "USB Preferences" screen. Here you can select "File transfer" and the phone may then be visible in Nemo. If you cannot see the sidebar, press F9 to open it.
There are cases where connecting a device doesn't do anything. Invariably this is down to the USB device ID not being recognized by the MTP rules, so sometimes a little bit of file editing is required. This may sound quite technical, but have a look at this post viewtopic.php?p=2244679#p2244679 to get started.
To connect for file transfer, you will likely need to open the notifications on the device. Select the option that says something like "Charging this device via USB". Depending on the version of Android, the notification may just expand, with a second line of text saying "Click here for more options" (or equivalent in your locale). This then opens the "USB Preferences" screen. Here you can select "File transfer" and the phone may then be visible in Nemo. If you cannot see the sidebar, press F9 to open it.
There are cases where connecting a device doesn't do anything. Invariably this is down to the USB device ID not being recognized by the MTP rules, so sometimes a little bit of file editing is required. This may sound quite technical, but have a look at this post viewtopic.php?p=2244679#p2244679 to get started.
Re: Impossible to read image on Phone from Linux
Alternatively, you can try using SshDaemon from the f-droid store. No root needed. I am using it to mount my cellphone with SFTP, works fine.
Linux Mint Una Cinnamon 20.3 Kernel: 5.15.x | Quad Core I7 4.2Ghz | 24GB Ram | 1TB NVMe | Intel Graphics
Re: Impossible to read image on Phone from Linux
My phone behaves slightly differently to that:
1: Launch Nemo and show the sidebar so you can see the list of devices.
2: Log into the phone so you can see alerts
3: Connect the phone-to-PC USB cable.
You should see the phone appear in the devices list
4: Click the phone in the devices list just like when you open a USB stick.
You should see a pop-up alert on the phone asking to allow USB file transfer. Tap Yes.
1: Launch Nemo and show the sidebar so you can see the list of devices.
2: Log into the phone so you can see alerts
3: Connect the phone-to-PC USB cable.
You should see the phone appear in the devices list
4: Click the phone in the devices list just like when you open a USB stick.
You should see a pop-up alert on the phone asking to allow USB file transfer. Tap Yes.
Re: Impossible to read image on Phone from Linux
connect the phone
look at the phone - the messages it displays
Depending on the Android version it will tell you
on the phones screen
in what mode you are connected..
Probably it's:
The phone is charging - tap to change the mode
do that - to file transfer or image transfer or whatever option seems most reasonable
... It's determined by the setting on the phone
look at it's screen
look at the phone - the messages it displays
Depending on the Android version it will tell you
on the phones screen
in what mode you are connected..
Probably it's:
The phone is charging - tap to change the mode
do that - to file transfer or image transfer or whatever option seems most reasonable
... It's determined by the setting on the phone
look at it's screen
Re: Impossible to read image on Phone from Linux
Well, my Samsung phone just briefly shows a "Charging" spinner when I connect it. Nothing more.
It only shows the popup asking whether to allow or deny file access when I try to open the device with Nemo.
So anyone who's phone behaves like my Samsung will need to try to start file management from the PC before the phone asks.
Just sayin'.
It only shows the popup asking whether to allow or deny file access when I try to open the device with Nemo.
So anyone who's phone behaves like my Samsung will need to try to start file management from the PC before the phone asks.
Just sayin'.
Re: Impossible to read image on Phone from Linux
I have a somewhat similar problem, not with nemo but with Double Commander.
If anyone can help, here is my threat:
viewtopic.php?t=395191
If anyone can help, here is my threat:
viewtopic.php?t=395191
Re: Impossible to read image on Phone from Linux
Bonjour and Thank you for your messages and helps.
Several applications for managing MTP (Media Transfer Protocol) have been loaded and tried, with the same result. Unable to access phone content.
The following commands may be useful, as the USB port may be occupied by GVFS.
pkill kiod5
pkill gvfs
When the mtp-detect command is run, an authorization request is made on the phone. In any case, the phone is detected and a complete phone report is displayed on the terminal. The USB port is reset and the problem is that it won't reboot. As a result, the port remains cut off and the phone's contents inaccessible.
However, if I proceed as follows, I can access the contents of the phone.
On the Samsung:
Usb controlled by This device
Using for:
any point can be chosen, it's not important at first
then select: Image transfer
then select: File transfer /Android Auto The contents of the phone are fully accessible, whether using the mtp-detect or mtp-folders commands or the file explorer nemo, thunar, caja...
Why this path through the selections triggers access to the phone remains a mystery to me. Maybe in this condition the USB port is reset correctly. I don't know.
Here, the aim was to access the phone's contents; the next step will be to make a backup of the phone. There must be applications for restoring a phone.
Regards,
Leloup
Several applications for managing MTP (Media Transfer Protocol) have been loaded and tried, with the same result. Unable to access phone content.
The following commands may be useful, as the USB port may be occupied by GVFS.
pkill kiod5
pkill gvfs
When the mtp-detect command is run, an authorization request is made on the phone. In any case, the phone is detected and a complete phone report is displayed on the terminal. The USB port is reset and the problem is that it won't reboot. As a result, the port remains cut off and the phone's contents inaccessible.
However, if I proceed as follows, I can access the contents of the phone.
On the Samsung:
Usb controlled by This device
Using for:
any point can be chosen, it's not important at first
then select: Image transfer
then select: File transfer /Android Auto The contents of the phone are fully accessible, whether using the mtp-detect or mtp-folders commands or the file explorer nemo, thunar, caja...
Why this path through the selections triggers access to the phone remains a mystery to me. Maybe in this condition the USB port is reset correctly. I don't know.
Here, the aim was to access the phone's contents; the next step will be to make a backup of the phone. There must be applications for restoring a phone.
Regards,
Leloup