Bug 27292

M8 Beta 1 Plasma. Updated.

All access permissions on android phone set.
Shorewall4 and 6 set to open KDEConnect ports.

Select a file to send via right-click on it and selecting "Send to Mi9T Pro via KDE Connect". Nothing happen but:
1) On phone side a notification Can't receive file from aurelien@mageia.local (mine computer)

2) Sending file to computer from KDE-Connect phone app is OK.

3) Browsing phone storage from Dolphin is inoperative. No error message on GUI.
# journalctl -f shows:
dolphin[3585]: Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls")


Upstream bug?

CC: (none) => ouaurelien
Source RPM: kdeconnect-kde => kdeconnect-kde-20.08.1-1.mga8.src.rpm

I thought we had an earlier bug on similar lines, but cannot find it (if it existed).

@Jose : thank you for the report.
Can you please say what mobile phone you have; and the version of its OS (iOS, Android). I do not know whether this matters, but in case it does.

Aurelien's test differs from the bug, but is not much better. This is outside my territory, so can I leave it with Aurelien?

Hi!

I have a mobile phone Sony Xperia XA2 with Lineage OS and Android 10 version.

I have had this bug too with a Nokia 7 Plus with Android One 10.

Greetings!

It seems it has been reported upstream:
https://bugs.kde.org/show_bug.cgi?id=419897

Different phone models, cryptic notification. Can't get such error message with my phone but I set all permissions on good state on my Android phone-side.
I can't browse my phone from dolphin. This is inoperative for now.

I have the same general problems using:

desktop:
Mageia 8 Beta
kdeconnect 20.08.01
FUSE library version 3.10.0
using FUSE kernel interface version 7.31
fusermount3 version: 3.10.0

phone:
Samsung J3
Android 7.1.1
kdeconnect 1.15.1

All permissions and ports are open. I can send individual files from the phone app and send files from dolphin, but cannot browse the phone files due to "Error when accessing filesystem. sshfs finished with exit code 1".

dolphin detects the phone and indicates it as mounted, but it isn't.

mount shows:
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=199180k,nr_inodes=49795,mode=700,uid=1000,gid=1000,inode64)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

I tried to mount the phone as an external file system but didn't succeed.

BTW, I get the same issues on Fedora 32 with kdeconnect 20.04.1-1.fc32, as mentioned in the upstream bug report, so perhaps it's not Mageia's problem.

CC: (none) => support

I have the same problem with a Huawei P8 and an Android 6, which makes me think that it is not a Mageia problem. So we can give the error closed and hope they fix it from Kde.

I tried kdeconnect a couple years ago (Possibly Mageia6 / Fairphone2 android 6), i could also not move files but did not dig into it (syncthing was a better choice for me regardless)

Could some of you users register on linked upstream bug so you get updates if something there happens, and that also give it more weight :)

I *Guess* it is the same problem on Mageia7 - anyone know?

Keep this bug open until fixed so other users find it.

CC: (none) => fri
URL: (none) => https://bugs.kde.org/show_bug.cgi?id=419897
Keywords: (none) => UPSTREAM

FWIW, updated Mageia release 7 (Official) for x86_64.
Current phone:  Android Blackberry Key2 BBF100-2

[rolf@x570i ~]$ rpm -qa | grep kdeconnect
lib64kdeconnectpluginkcm1-1.3.4-2.1.mga7
kdeconnect-kde-nautilus-1.3.4-2.1.mga7
kdeconnect-kde-handbook-1.3.4-2.1.mga7
lib64kdeconnectcore1-1.3.4-2.1.mga7
kdeconnect-kde-1.3.4-2.1.mga7
lib64kdeconnectinterfaces1-1.3.4-2.1.mga7

Maybe this line from `mount' is relevant:
kdeconnect@192.168.1.159:/ on /run/user/501/a3xxxxxxxxxe9d type fuse.sshfs (rw,nosuid,nodev,relatime,user_id=501,group_id=501)

I've used kdeconnect on various phones and MGA releases for some years.  It has had some bugs and glitches that have been improved upon in this period.  Just now, I tested sending a small text file and ~6MB mp3 from the desktop to the phone, then back.  I can browse the phone from its entry under Devices in the Dolphin sidebar, drag-and-drop a batch of jpegs to the computer.

Basically, this arrangement is functioning fairly reliably.  Aside, there is an app in Android, at least, called File Manager that supplies an ftp server on the phone.  It's a very reliable alternative, in my experience, if/when kdeconnect falls short.
https://play.google.com/store/apps/details?id=com.alphainventor.filemanager&hl=en_US&gl=US

CC: (none) => rolfpedersen

With recent versions:

$ rpm -qa | grep kdeconnect
lib64kdeconnectpluginkcm20-20.12.0-1.mga8
kdeconnect-kde-handbook-20.12.0-1.mga8
lib64kdeconnectcore20-20.12.0-1.mga8
kdeconnect-kde-20.12.0-1.mga8
lib64kdeconnectinterfaces20-20.12.0-1.mga8

And on KDE Connect Android application changelog (https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp&hl=fr&gl=US)

New:
1.15.1:
- MMS support.
- Share plugin asks to configure receiving directory (required in Android 9+).
- Fix trusted networks on Android 10
- Several more fixes and improvements.

1.14.2:
- Fix clipboard sync
- Android 10: You can now send the clipboard contents via the notification
- Android 10: Links received will appear as notifications

I CAN navigate through my phone after setting the directory to share on the phone.
This is done the first time I connect my phone to my computer.
Right after, I can mount the phone in Dolphin with a menu in KDE-Connect applet in systray.

Can someone else test this?

Updating SRPM.

Source RPM: kdeconnect-kde-20.08.1-1.mga8.src.rpm => kdeconnect-kde-20.12.0-1.mga8.src.rpm
Keywords: UPSTREAM => (none)

(In reply to Aurelien Oudelet from comment #9)
> With recent versions:
> 
> $ rpm -qa | grep kdeconnect
> lib64kdeconnectpluginkcm20-20.12.0-1.mga8
> kdeconnect-kde-handbook-20.12.0-1.mga8
> lib64kdeconnectcore20-20.12.0-1.mga8
> kdeconnect-kde-20.12.0-1.mga8
> lib64kdeconnectinterfaces20-20.12.0-1.mga8
> 
> And on KDE Connect Android application changelog
> (https://play.google.com/store/apps/details?id=org.kde.
> kdeconnect_tp&hl=fr&gl=US)
> 
> New:
> 1.15.1:
> - MMS support.
> - Share plugin asks to configure receiving directory (required in Android
> 9+).
> - Fix trusted networks on Android 10
> - Several more fixes and improvements.
> 
> 1.14.2:
> - Fix clipboard sync
> - Android 10: You can now send the clipboard contents via the notification
> - Android 10: Links received will appear as notifications
> 
> I CAN navigate through my phone after setting the directory to share on the
> phone.
> This is done the first time I connect my phone to my computer.
> Right after, I can mount the phone in Dolphin with a menu in KDE-Connect
> applet in systray.
> 
> Can someone else test this?

Ping?

Mageia: 7-64, plasma, with almost all testing updates.
All relevant packages per above, excluding nautilus package.

Phone: Fairphone 3, running /e/ 0.12-q-2020111084008-dev-FP3 (privacy enhanced Android 10) 

History: Have not used KDE-Connect since i changed phone months ago, it was working a year ago but i never really used it much except a couple times to find my phone...
Now (re)installed KDEconnect.

Before i checkmarked it in firewall, I tried in phone app KDEConnect to enter computer IP, but no response - not even did it tell me it found but failed.

Checkmarked KDE connection in MCC firewall settings...
...After a while I see my phone listed.

The phone shows the computer, using the name set in computers KDE-Connect.  Both offer to initiate pairing.  I chose to initiate from phone: OK.

___Tests:

§ Shows charge level: OK

§ Changing phone name: Computer KDE-Connect shows new name in a while: OK, but Dolphin left pane do not get updated - upstream issue i presume.

§ Changing computer name: Phone do not update yet... 

§ Make phone ring: OK

§ Phone controls pointer and click, and used to write this line>OK except that colon became a ">" instead... so some minor character mapping issue - upstream, i presume.

§ Phone "Control Multimedia" automatically detected i had Gwenview up and i  could use it to show next/previous photo.

  After having chosen folder in phone app:

§ Send file from phone: OK - received in normal downloads folder

§ Browse phone files using Dolphin: OK


___Not tested:
§ Control a music player

Whiteboard: (none) => MGA7TOO, MGA7-64-OK

Still cannot browse phone with Dolphin. Regarding "I can mount the phone in Dolphin with a menu in KDE-Connect applet in systray.", how do you do that?

The error notifications repeat until back arrow < is pressed. Too bad I can't show a screenshot.

Samsung Galaxy  J3 (SM-J320W8)
Android 7.1.1
My Files > Internal storage All shared

Operating System: Mageia 8
Kernel: Linux 5.10.4-desktop-4.mga8
Architecture: x86-64

rpm -qa | grep kdeconnect
lib64kdeconnectinterfaces1-20.08.3-1.mga8
lib64kdeconnectinterfaces20-20.12.0-1.mga8
lib64kdeconnectsmshelper1-20.08.3-1.mga8
lib64kdeconnectpluginkcm20-20.12.0-1.mga8
lib64kdeconnectpluginkcm1-20.08.3-1.mga8
kdeconnect-kde-handbook-20.12.0-1.mga8
kdeconnect-kde-20.12.0-1.mga8
lib64kdeconnectcore1-20.08.3-1.mga8
lib64kdeconnectcore20-20.12.0-1.mga8

In KDE connect applet you have to enable the functions.
In the app on the phone you have to choose folder and grant access.
Dolphin then in left pane (where folders, filesystems, etc are shown) show youe phone - click it and browse.

What's the status of this?

Have you try the latest version of kdeconnect on Android and do you not forget to set all permissions on your device?

I can't reproduce this either.

The bug is still there, I can't get into the storage of the device.

(In reply to Jose Manuel López from comment #16)
> The bug is still there, I can't get into the storage of the device.

With Mageia 7 or M8?

With Mageia 8

Up, I will try to see what's wrong...

On Mageia 8 RC take 3 (we are in take 4 and KDE Connect is installed by default)

KDE Connect is not installed by default.
Here is the packages installed as dependencies or kdeconnect:

kdeconnect-kde-20.12.0-1.mga8.x86_64          mer. 27 janv. 2021 16:27:14
kpeoplevcard-0.1-3.mga8.x86_64                mer. 27 janv. 2021 16:27:13
kdeconnect-kde-handbook-20.12.0-1.mga8.noarch mer. 27 janv. 2021 16:27:13
sshfs-fuse-3.7.1-1.mga8.x86_64                mer. 27 janv. 2021 16:27:11
lib64kdeconnectpluginkcm20-20.12.0-1.mga8.x86_64 mer. 27 janv. 2021 16:27:11
lib64kdeconnectinterfaces20-20.12.0-1.mga8.x86_64 mer. 27 janv. 2021 16:27:11
lib64kdeconnectcore20-20.12.0-1.mga8.x86_64   mer. 27 janv. 2021 16:27:10
lib64fuse3_3-3.10.1-1.mga8.x86_64             mer. 27 janv. 2021 16:27:10
fuse3-3.10.1-1.mga8.x86_64                    mer. 27 janv. 2021 16:27:10

Could you check them on your computer?

Hi,

Yes, I have the same dependencies.

Sorry.

But, KDEConnect has changed recently.
Android can't no longer share the entire root of the internal or SD card filesystem.

Experienced today: you must set within KDEConnect Application a Folder to share.
Don't forget to authorize all KDEConnect wants after installing it.

So, under KDEConnect (on the mobile):

1) remove all configured PC.
2) Add your computer to pair it.
3) There must be a notification in the app that permission must be set to "Expose filesystem"
4) Touch it and set one folder. You can later set other folders to share, but one each time.
5) Folders will be visible in Dolphin.

In Dolphin => in places: you will see your phone and you will be able to browse it.

This runs well on a Xiaomi Mi 9 T Pro, Android 10, MIUI 12.
I do want to set it WORKS FOR ME, but, if this does not work for you, Jose, this must be reported upstream against KDEConnect app at bugs.kde.org.

I think it's right, I don't think it's an application that should be installed by default. 

For me it would be on the same level as Darktable for example, which is especially for photo editing.

(In reply to Jose Manuel López from comment #22)
> I think it's right, I don't think it's an application that should be
> installed by default. 
> 
> For me it would be on the same level as Darktable for example, which is
> especially for photo editing.

Sorry, wrong bug, please disregard.

(In reply to Aurelien Oudelet from comment #21)
> Sorry.
> 
> But, KDEConnect has changed recently.
> Android can't no longer share the entire root of the internal or SD card
> filesystem.
> 
> Experienced today: you must set within KDEConnect Application a Folder to
> share.
> Don't forget to authorize all KDEConnect wants after installing it.
> 
> So, under KDEConnect (on the mobile):
> 
> 1) remove all configured PC.
> 2) Add your computer to pair it.
> 3) There must be a notification in the app that permission must be set to
> "Expose filesystem"
> 4) Touch it and set one folder. You can later set other folders to share,
> but one each time.
> 5) Folders will be visible in Dolphin.
> 
> In Dolphin => in places: you will see your phone and you will be able to
> browse it.
> 
> This runs well on a Xiaomi Mi 9 T Pro, Android 10, MIUI 12.
> I do want to set it WORKS FOR ME, but, if this does not work for you, Jose,
> this must be reported upstream against KDEConnect app at bugs.kde.org.

Hi,

I can confirm that what you comment works now for mi, on Xiaomi Mi 8 with /e/Os Pie, and Mageia 8.

Greetings!!

Thank you
So i set this to resolved then.
If that is wrong, please reopen.

Status: NEW => RESOLVED
Resolution: (none) => FIXED