When i try to write something in an external SD card it denies access. Writing into internal storage works. Thinking the possibility that FUSE permissions are broken, on my desktop I tried to touch a file as root and it failed. I think the most possible case is the fact that the policy in Android 5+ which prevents any app to write to external SD cards unless it's given an explicit permission to do so. I set my destination folder as the root of the external SD card for receiving files. However, while browsing via Dolphin it's not allowed to write external SD. Does KDEConnect use a service whose privileges needs to be set?
What's your Android version? And if you're on Android 6+, did you give KDE Connect the required permissions on the add-a-device screen? If so, it should be able to write files. Saving shared files uses another mechanism to store the files, so it's certainly possible that sharing files to the external sd works and transferring files from Dolphin does not.
(In reply to Matthijs Tijink from comment #1) > What's your Android version? As written I use 7. 7.1 to be exact. > And if you're on Android 6+, did you give KDE Connect the required > permissions on the add-a-device screen? If so, it should be able to write > files. KDEConnect has all the permissions Telephone, SMS, Contacts and Storage. File system expose is already enabled and as I said I can write internal storage. > Saving shared files uses another mechanism to store the files, so it's > certainly possible that sharing files to the external sd works and > transferring files from Dolphin does not. I guess so. Since all apps denied to access external SD card on Android 5+ unless in the saving dialog user explicitly selects external SD. For file sharing (sending & receiving), I can use this trick to select save location and writes work. However File System Expose plugin does not have this sort of option to select any location in SD card to enable it to write SD card.
Maybe it's the same as this bug: https://bugs.kde.org/show_bug.cgi?id=377058? Could you check that?
*** This bug has been marked as a duplicate of bug 336043 ***