Bug 336043

yes, me also vote for this feature  :-) :-)

*** Bug 336862 has been marked as a duplicate of this bug. ***

Git commit 5b2756b7f807c68d0f19e1f76a17a2decbd44d6f by Albert Vaca.
Committed on 10/10/2014 at 22:49.
Pushed by albertvaka into branch 'master'.

Added support for devices with more than one external storage

A  +101  -0    src/main/java/org/kde/kdeconnect/Helpers/StorageHelper.java
M  +51   -3    src/main/java/org/kde/kdeconnect/Plugins/SftpPlugin/SftpPlugin.java
M  +6    -0    src/main/res/values/strings.xml

http://commits.kde.org/kdeconnect-android/5b2756b7f807c68d0f19e1f76a17a2decbd44d6f

Hi,

I'm unable to access my SD card.

I have a Galaxy S4 Mini. It worked with Jelly Bean, but stopped working with KitKat (4.4.2).

I get the following message in a red notification box in Dolphin when I click the "SD Card" folder link:
> The file or folder /home/laurent/.kde4/share/apps/kdeconnect/7285b670cb7a861f/mnt/media_rw/extSdCard does not exist.

Anyway, thanks for the GREAT work!

Curious behaviour that I further observed:

When popping up a shell, and typing
> $ cd ....../7285b670cb7a861f/mnt/extSdCard
> $ ls
> ls: reading directory .: Operation not permitted [with return value = 2]

...but when I then access a folder that I know exists on my SD card...
> $ cd ....../7285b670cb7a861f/mnt/extSdCard/Music
> $ ls
...then I get all my music files listed!

However,
> $ touch test.txt
> touch: setting times of ‘test.txt’: No such file or directory
...the directory is not writeable.

I hope this gives you some useful clues :) Let me know if you need further tests!

I just published a new version to the Play store where this issue should be fixed. Since I have no way to test it, I would like if you could try it and say if it fixed the problem. Note that the update may take some time to be available to everybody.

Fixes the issue for me - thanks :)

works like a charm

Hi,

Sorry, but it still doesn't work for me. I suppose that this is the problem:

> Prior to Android 4.4 KitKat, applications, provided they had permission to
> access the externalSD card, could read and write to any area on removable
> storage, including the system folders like DCIM, Alarms, etc. That has all
> changed, and now third-party applications, as in ones you download from
> Google Play or elsewhere can only write to files and folders that they have
> created or have taken ownership of.
> [ http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/ ]

The update just gave me a lot of folders (directories in /mnt I suppose) but did not fix the permission issue.

i add some info to help.

samsung S2 Plus
android 4.2.2
opensuse 13.1

what i tested :
- browse ok
- delete a folder in extsdcard ok (put it in dustbin)
- delete files in etxsdcard : ok (put them in dustbin)
- copy-past files from smartphone to pc : ok
- copy past files from pc to smartphone : ok
- icon preview of jpg's : ok
- folder with icon contazinig icon preview of jpg's inside : ok
- copy-past a folder from pc to smartphone : ok
- copy-past a folder from smartphone to pc : ok

Android 4.2.2 should not have this issue yet. AFAIK, only devices with Android 4.4+ should be concerned.

Hi Laurent, 

I was using 4.4 and just upgraded to 5.0 and it works well, so I think it's more a problem with your phone using different mount points than the default Android. Can you tell me what phone do you have, the list of folders you see when browsing, and where is the actual storage mounted?

On 11/23/2014 02:08 AM, Albert Vaca wrote:
> https://bugs.kde.org/show_bug.cgi?id=336043
>
> --- Comment #6 from Albert Vaca <albertvaka@gmail.com> ---
> I just published a new version to the Play store where this issue should be
> fixed. Since I have no way to test it, I would like if you could try it and say
> if it fixed the problem. Note that the update may take some time to be
> available to everybody.
>
on my PC=Dell latitude E6510, RAM=8Gb, GPU=GT218 NVS 3100M, CPU=i7 Q 720 
@ 1.60GHz, OS=opensuse 13.1 KDE= 4.14.3
and my phones samsung S4 mini with android 4.4.2
and my phone sony Z1 compact with android 4.4.4
it doesn't works.

in samsung I have this root tree:
/cache
/data
/efs
/sdcard
/dev
/etc
/root
/tombstones
/sys
/storage
/persdata
/mnt
/knox_data
/firmware
/config
/acct
/vendor
/system
/persist
/sbin
/proc
/preload
/d

and my external storage is mounted in:

/storage/extSdCard/Nearby
/storage/extSdCard/Android
/storage/extSdCard/DCIM+++++++here are my pictures
/storage/extSdCard/LOST.DIR

where storage tree is:

/storage/emulated
/storage/sdcard0
/storage/extSdCard
/storage/UsbDriveF
/storage/UsbDriveE
/storage/UsbDriveD
/storage/UsbDriveC
/storage/UsbDriveB
/storage/UsbDriveA


on my sony Z1 compact the external sd card is :
/storage/sdcard1/

where storage is:

/storage/sdcard0
/storage/emulated
/storage/usbdisk
/storage/removable
/storage/remote
/storage/sdcard1

I usually access with ftpserver app and access to the root /, could 
kdeconnect access at the root /??

thnx, ciao, pier :-)

Oh, okay, it seems that your phones have directories for all kinds of external storages, even if they are not present at the moment. Knowing this it should be easier to write a fix: I should be able to display only the ones that are mounted, assuming that they are not all always mounted. To check that last thing, can any of you provide the content of the file /proc/mounts in your phones?

On 11/24/2014 04:38 AM, Albert Vaca wrote:
> https://bugs.kde.org/show_bug.cgi?id=336043
>
> Albert Vaca <albertvaka@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|RESOLVED                    |REOPENED
>           Resolution|FIXED                       |---
>       Ever confirmed|0                           |1
>
> --- Comment #14 from Albert Vaca <albertvaka@gmail.com> ---
> Oh, okay, it seems that your phones have directories for all kinds of external
> storages, even if they are not present at the moment. Knowing this it should be
> easier to write a fix: I should be able to display only the ones that are
> mounted, assuming that they are not all always mounted. To check that last
> thing, can any of you provide the content of the file /proc/mounts in your
> phones?
>

in my samsung S4 mini with android 4.4.2 and on sony Z1 compact with 
android 4.4.4 it seems empty, 0byte and when opened wirth kwrite is empty
thnx, :-) ciao :-) pier

The file will look empty but when you try to read from it Linux will write there the list of mount points. You should be able to get something from it. Could you try to read it again in some other way? I've tried to find it with the file browser "Ghost Commander" (open source) and then open it with the "HTML Viewer" and it worked. Thank you very much! I still hope we can fix the bug at the end :)

Created attachment 89708 [details]
contents of the smartphone

hello i forgot to say there is a little pb (android 4.2.2 , kdeconnect 0.7.3.3)

look at browse.png

when you click on "SD card" then dolphin displays nothing .
when you click on "sd card 7" then dolphin displays the contents of the sd card .

(In reply to Albert Vaca from comment #12)
> Hi Laurent, 
> 
> I was using 4.4 and just upgraded to 5.0 and it works well, so I think it's
> more a problem with your phone using different mount points than the default
> Android. Can you tell me what phone do you have, the list of folders you see
> when browsing, and where is the actual storage mounted?

Hi,

I have a Samsung S4 Mini.
The mount points are
-  /mnt/extSdCard (which is a symlink to...)
-  /storage/extSdCard (so this is the actual mount point).

My folder list is equivalent to the one from pier andre.
I have posted the contents of my /proc/mounts (30 lines) here: http://pastie.org/pastes/9739921/text
I should further mention that my phone is *not* rooted.

However, I'm quite sure that all this is not the problem. The folder list before your "fix" was alright, now I see all those useless UsbDriveX folders too. I have tried a bit to find other paths that work (like going to /storage/extSdCard directly) and the result was the same. I'm quite sure that it is a permission issue.

If I may ask, which phone do you have? Just to be clear, the external SD worked with Android 4.4+ (but < 5)?

I googled a bit, and as I understand it, you may need other API methods for 4.4.x. See here: http://stackoverflow.com/questions/26744842/how-to-use-the-new-sd-card-access-api-presented-for-lollipop and here: http://www.doubleencore.com/2014/03/android-external-storage/ .

Thanks! hth :)

(In reply to Philippe ROUBACH from comment #17)
> [...]
> when you click on "sd card 7" then dolphin displays the contents of the sd
> card .

I tested this too. "SD card 7" displays my photos (i.e. /storage/extSdCard/DCIM/Camera/). However, the folder is not writeable and I cannot delete/rename the existing photos. This corresponds with my findings from comment #5 .

On 11/24/2014 09:28 AM, Albert Vaca wrote:
> https://bugs.kde.org/show_bug.cgi?id=336043
>
> --- Comment #16 from Albert Vaca <albertvaka@gmail.com> ---
> The file will look empty but when you try to read from it Linux will write
> there the list of mount points. You should be able to get something from it.
> Could you try to read it again in some other way? I've tried to find it with
> the file browser "Ghost Commander" (open source) and then open it with the
> "HTML Viewer" and it worked. Thank you very much! I still hope we can fix the
> bug at the end :)
>

:-) ok, I succeed to open /proc/mounts, before I tried to acces with 
ftpserver from my pc, now from the phone with astro file and HTMLviewer.

this is /proc/mounts of samsung S4 mini:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,mode=700 0 0
/dev/block/vold/179:33 /mnt/secure/asec exfat 
rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 
0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.whatsapp.wallpaper-1 ext4 
ro,dirsync,seclabel,nosuid,nodev,noatime,errors=continue 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 
ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 
rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 
0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 
rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 
0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 
rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 
0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 
rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 
0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat 
ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 
0 0
/dev/block/platform/msm_sdcc.1/by-name/hidden /preload ext4 
ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 
rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/data/knox/sdcard /mnt/shell/knox-emulated sdcardfs 
rw,nosuid,nodev,relatime,uid=1000,gid=1000,derive=none 0 0
/data/media /mnt/shell/emulated sdcardfs 
rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/block/vold/179:33 /mnt/media_rw/extSdCard exfat 
rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 
0 0
/mnt/media_rw/extSdCard /storage/extSdCard sdcardfs 
rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=unified 0 0
tmpfs /storage/emulated tmpfs 
rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
/data/media /storage/emulated/0 sdcardfs 
rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/legacy sdcardfs 
rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0

and this is /proc/mounts from sony Z1 compact:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
securityfs /sys/kernel/security securityfs 
rw,nosuid,nodev,noexec,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 
ro,seclabel,nosuid,nodev,relatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 
rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 
rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apps_log /mnt/idd ext4 
rw,seclabel,nosuid,nodev,noexec,noatime,discard,nobarrier,data=ordered 0 0
tmpfs /storage/remote tmpfs 
rw,seclabel,relatime,size=1024k,nr_inodes=256,mode=750,gid=1028 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 
ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse 
rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 
0 0
tmpfs /storage/emulated tmpfs 
rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 texfat 
rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,nls=utf8,min_prealloc_size=64k,max_prealloc_size=60874M,readahead=4M,fail_safe,discard,errors=continue 
0 0
/dev/fuse /storage/sdcard1 fuse 
rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 
0 0
/dev/fuse /storage/emulated/0 fuse 
rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 
0 0
/dev/fuse /storage/emulated/legacy fuse 
rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 
0 0


manythnx :-) ciao :-) pier

Okay, second attempt :) I've just uploaded a new version to the Play Store. Can you tell me if it's fixed for you now? I hate not being able to test this myself :/

Hi,

Unfortunately, no change (except that I can see my own smartphone in the "Available Devices" list in the Android Client, but this is hopefully unrelated ;) ).

I had a look into your git commits. I am not an Android programmer, but as far as I can tell, you only tried to *find* the mounted folders (e.g. extSdCard) using a different method. Is this correct?

If so, please keep in mind that this is actually not the problem. You can see the extSdCard folder in the overview, but
- you cannot see the contents of the SD card root folder (/.../extSdCard/)
- however, you can see the contents of the subfolders (e.g. /...extSdCard/Music/, /...extSdCard/DCIM/, and so on)
- none of the SD card folders is writeable. File names cannot be changed, new files cannot be created.

Just to make sure that you know exactly what I see: Here's a little photo story ;)
http://imgur.com/a/oJBRb

Good luck with debugging. Being unable to test yourself sure is hard. Thanks for your time!

(Unrelated question: What IDE are you using? Tried to import KDE Connect in Android Studio, but had trouble with Gradle. I'm using a 64-bit Arch Linux machine btw.)

Hi Laurent,

Actually there was a typo in the new code, that made it not having any effect. Having a look at your /proc/mounts I still think this approach should work. I'm uploading a version with this fixed right now. Let's see when you get the update if it fixes the problem. Thanks everybody affected by this bug for your patience and thanks again for helping me to address it.

Albert

I've had the same problem and after today's update file browser started to work, but only after full configuration wipe both in the phone and the laptop.

Hi Albert,

Got the update. The small quirk where I saw my own phone in the "Available Devices" list is now gone. Also, I only have the relevant folders (Camera pictures, internal storage, SD card) in the overview, the paths of them are correct, exactly as it should be :)

However, it doesn't fix the permission issue. In other words, everything from my screenshot story in comment #22 , except the first screenshot, stays the same.

> Thanks everybody affected by this bug for your patience and
> thanks again for helping me to address it.
Same goes for you, thank you for your time and your great work!

(In reply to Eugene Shalygin from comment #24)

Hi Eugene,

Could you please specify your smartphone model and your Android version?

Also, did you browse your external SD card in your file manager? And do you have write permissions on your SD card (from within your file manager in KDE)?

(In reply to Laurent from comment #26)
Hi, Laurent ,

I must have had another issue, because for me the browsing did not work at all before the update today with Galaxy S 4, Android 4.4.2. I was so happy that browsing got working, that had not read your posts carefully. So, in my case I also do not see contents of the SD card, I can go inside any directory by entering its name explicitly, and I can not write to the card. So sorry for the  confusion.

I am also experiencing the behaviour described in comment 5.


$ cd /home/reuben/.kde4/share/apps/kdeconnect/9583045ea4161072
$ ls
ls: reading directory .: Operation not permitted
$ ls storage
emulated     sdcard0
$ ls storage/emulated
0    legacy
$ ls storage/emulated/*
emulated/0:
ls: reading directory emulated/0: Operation not permitted
emulated/legacy:
ls: reading directory emulated/legacy: Operation not permitted
$ ls storage/sdcard0
ls: reading directory sdcard0: Operation not permitted
$ ls emulated/0/DCIM
100ANDRO Camera

Seems to be a permissions issue. The folders returning those errors have 700 permissions on the PC, 771 on the tablet (owners are root and sdcard_r).

Device: Nexus 7 (2013)
Device OS: Android 5.0.2 (rooted, but otherwise stock)
PC OS: Sabayon amd64 with KDE 4.14.3
KDE Connect 0.8

/proc/mounts on tablet:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Git commit 57871802d83b4fd23e8fb8837956f145825bb928 by Albert Vaca.
Committed on 16/03/2015 at 00:52.
Pushed by albertvaka into branch 'master'.

Only try to mount the root of the phone if we have read access to it

M  +5    -4    src/org/kde/kdeconnect/Helpers/StorageHelper.java
M  +38   -34   src/org/kde/kdeconnect/Plugins/SftpPlugin/SftpPlugin.java

http://commits.kde.org/kdeconnect-android/57871802d83b4fd23e8fb8837956f145825bb928

Same issue as in #5
Samsung Galaxy S4 i9505, Cyanogenmod 12.1
KDE Connect 0.8h from F-Droid
Feel free to request any additional information.

Feature suggestion: may be add an option to browse storage as root if supported?

However, writing works in my case.

I am also experiencing the behaviour described in comment #5.

$ apt-cache policy kdeconnect
kdeconnect:
  Installed: 0.8-1
  Candidate: 0.8-1
  Version table:
 *** 0.8-1 0
        990 http://ftp.it.debian.org/debian/ testing/main amd64 Packages
        500 http://ftp.it.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Why is this marked as "resolved fixed"?

Why is this marked as resolved?? It isn't working for me.... Samsung S3. I would be happy to provide any details needed.

*** Bug 345613 has been marked as a duplicate of this bug. ***

DItto Comment 33.

I am also having the issue. On my Huawei Ascend MAte 7, the internal storage gets detected just fine, the external not.
On my Jide Remix Ultratablet, I just get an empty listing for the devices internal storage. That's so weird because it just worked before.

I experience this bug as well.

Isn't working for me too.

not working on my Samsung Galaxy S5 running  Android 5.0, desktop is openSUSE Leap 42.1

internal storage works fine but not external

Hi,
Having the same issue also

Desktop - Arch Linux
kdeconnect 0.9.g
plasma-desktop 5.5.5
plasma-desktop 5.5.5
linux 4.4.5

Android - CyanogenMod (ASOP 6)
kdeconnect 0.9.g

I have the same issue with a Samsung S4 Mini 9195i - I can view the internal storage but not the SD card - it seems as if I am missing read permissions to that folder/mount, because I can see the mount, but its contents are empty. Android 4.4.4.

I can't even browse the internal storage.

When I click the "folder" icon in the tray menu of KDE Connect, Dolphin pops up and shows a path at kdeconnect://<hex id>/ with 3 folders: "Camera pictures(Internal storage)", "Internal storage" and "SD card". However, when I try to open any of those, Dolphin says that the relevant folder (for example, ~/.kde4/share/apps/kdeconnect/<hex id>/storage/emulated/0/) does not exist.

I have the same issue with Lenovo K3 Note. I can view the internal storage, but not the external SD card.

same here with an android 4.4.4 device and android 6.0.x based tablet.
Internal storage can be accessed by kdeconnect protocol in dolphin, but external sdCard folder is always emty. Even navigating to the respective 'emulated' folder inside the device tree results in an empty folder (of the ext. sdCard)

Same here, except I can see photos and videos on my SD card in a folder named "Camera pictures(SD card 2)".  I can't see anything else on the SD Card.  There are two folders named "SD card" and "SD card 2", but they are seemingly empty.  I can see the contents of my phone in a folder named "Internal storage".

When I right-click on a file in Dophin, I get the option "Send to [phone] via KDE connect".  When I click on on it, the file starts transferring immediately, without other choices.  It then lands up in a folder "kdeconnect" on the internal storage.  I'd like the option of transferring it to the SD card.

My set-up is Fedora 23 and a Hisence Pureshot phone running Android 5.0.2.

Thanks for a great program!

Would be very helpful if this was added

As a some kind of workaround it's possible to convert SD Card to 'adoptable' storage. 

In such case it'll be mounted instead of internal memory to /sdcard.

But please read about drawbacks of this before (it's no longer possible to remove SD card).

At least it works on my Samsung S7 Edge.

Browsing internal phone storage works, but browsing …/storage/extSdCard/ is not possible unless you enter existing folder name after extSdCard/.
Than is possible to browse this folder and subfolders in it.
Everything comes with only root permissions - no way to change/delete things.

(In reply to Gilberto Caetano de Andrade from comment #48)
> Browsing internal phone storage works, but browsing …/storage/extSdCard/ is
> not possible unless you enter existing folder name after extSdCard/.
> Than is possible to browse this folder and subfolders in it.
> Everything comes with only root permissions - no way to change/delete things.

I can confirm that is how things work for me with the Samsung S4 mini.
Reading is possible if I drill into a directory, and writing is not.
To me, it seems this is an OS restriction of Android 4.4.4 and not a bug in KDE connect itself.

I've just encountered this bug on a new phone (LG G5) running AOS 6. When I open the device in Dolphin I get:

> Camera pictures(Internal storage)
  Camera pictures(SD card)
> Internal storage
  SD card

"SD card" is a real card, "Internal storage" is the emulated card. No directories are detected on the SD card. But if I step into the apparently empty SD card directory, then edit the path and add /DCIM on the end (or any other directory that exists) its contents appear. The contents are readable but nothing is writeable, which is a bit of a limitation.

I believe the (bonkers) restrictions on the external card introduced in AOS 4 were removed in 5 & 6, so the SD card should be browseable. Non-privileged file managers such as Explorer (non-root version) can see the directories on the card, so KDEconnect should be able to as well.

Is there maybe a new API since AOS 4 for doing this?

Hello All...

I also can confirm I have an issue with seeing and browsing /mnt/extsdcard on my Galaxy S4 with KDE Connect.  I CAN type that into Dolphin and add the name of a folder that *exists* and see its contents...  I CANNOT write in it once there.

OS version of desktop: opensuse leap 42.2
Android OS: 5.0.1
kdeconnect version on desktop: 1.0.3
kdeconnect version on Android: 1.5 

It would be awesome if this worked.  AWESOME piece of software otherwise.
I hope all each of you are well!

I have similar issue with ALE-L21 (P8 Lite).
I can view Internal storage, until recently I was able to also view external storage.
I also can view photos stored on SD card via Camera folder, which is interesting.

Currently SD shows an empty folder without write permissions.

I'm not sure if it's related but I am unable to write to any Android SD card via kio mtp file managers. That's via USB mtp connection.

Is kdeconnect using kio-mtp ? Just thinking out loud.

> Is kdeconnect using kio-mtp ? Just thinking out loud.

KDE Connect is not using MTP. Android permissions (since Android 4.4 I think) might make KDE Connect not be able to access your SD Card, which is the core issue here. I don't know if this can affect MTP as well... but I think it shouldn't.

Since I don't have a device with this problem, I can't reproduce the problem though. 

It might be possible to fix this if we request access to the SD card from the app, via a file picker, using the new Android Storage Access Framework API. It's hard for me to implement this if I can't test it though :/

Hi Albert

I'm happy to test out any code changes you want to try. I see the same sympton as others are reporting on AOS 7 (no write access, and can't browse the top-level of the external card - see comment 50).

Let me know if I can be any help.

Let's make a list of affected phones, so I can see if I can borrow one of these from a friend to test :)

- LG G5
- Samsung Galaxy S4
- Samsung Galaxy S5

Also affected:
- Sony Xperia Z1 Compact (Android 5.1.1)
- Sony Xperia Z3 (Android 6.0.1)

The Z1 Compact also lists the SD card in a strange way - listed are "Internal Storage" (the correct internal storage at storage/emulated/0/), "SD card" (this is blank and points to storage/remote/), and "SD card 2" (correctly points to storage/sdcard1/ which is the real SD card but suffers from this bug whereby you cannot see deeper contents without manually lengthening the path). /storage/remote/ probably shouldn't be displayed as an "sd card", but I have no idea what it is.

I can see this on a Sony Xperia Z2 as well.

I have this access problem to my sd card on my Galaxy S7 edge, Note 7 (which is gone) and on my old S5

Updated list of affected phones:
- LG G5
- ony Xperia Z1 to Z3
- Samsung Galaxy S4, S5 and S7

Also affected:
- Lenovo K3 Note (Android 5 and 6)

Also affected:
- Lenovo K3 Note (Android 5 and 6)

Also encountered on:
Huawei P8 Lite
Huawei P9

Created attachment 103401 [details]
attachment-7703-0.html

Also encountered on
Samsung Galaxy S3

On Fri, Jan 13, 2017 at 10:11 AM Piotr Kloc <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=336043
>
> --- Comment #62 from Piotr Kloc <pepko94@gmail.com> ---
> Also encountered on:
> Huawei P8 Lite
> Huawei P9
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Checking online it looks like Galaxy S3 didn't get upgraded to Android 4.4. Which Android version do you have?

Created attachment 103403 [details]
attachment-16835-0.html

Unfortunately I don't have the S3 anymore, but I originally subscribed to
this bug because of it. Sorry if I'm giving not-useful information.

On Fri, Jan 13, 2017 at 9:02 PM Albert Vaca <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=336043
>
> --- Comment #64 from Albert Vaca <albertvaka@gmail.com> ---
> Checking online it looks like Galaxy S3 didn't get upgraded to Android 4.4.
> Which Android version do you have?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

For reference, I am still on Android 4.4.4 on my Sony Z2 (I haven't upgraded the software currently).

Also affected:
Alcatel Idol 3 (Android 6.0).

Same as comment 50, excepted I can write in sub-directories created with mkdir by shell user in /SD card.
Moto G4 Play
Android 6

Already posted in https://bugs.kde.org/show_bug.cgi?id=341175 but this seems more active.

I'm seeing the same problem of not being able to browse the top level sdcard folder. I can browser sub-folders on the sdcard if I specify them manually, but can't change/create files. 

I've seen this on 
LG G4 (android 6 and 7)
Zenfone 2 (android 6 and 7)

I'd be happy to test any code as well. Other apps seem to have solved this in the way described earlier, by asking for perms and announcing that before hand.

*** Bug 341175 has been marked as a duplicate of this bug. ***

*** Bug 377735 has been marked as a duplicate of this bug. ***

Galaxy S8+ can be added to the list.

Root folder on the external SD card is shown empty. If I manually enter the path of a subdirectory, then I can browse it.

I am also unable to write a file to the external SD card (permission problem). This is the most problematic part imho.

AB

I can't tell if this is the same problem as what others are reporting. I am using the indicator-kdeconnect project to interact with kdeconnect from GNOME. When I browse files with sftp, internal storage shows up fine, but I don't see any evidence of the external SD card. I don't have a mnt folder, so no mnt/extSdCard folder like others have talked about. When I look in the file manager on the phone, the external SD card is viewable as a separate device. I can't navigate to it through the directories of the internal storage. It's like kdeconnect doesn't know the SD card exists. However, for the share & receive destination setting, I was able to choose the external SD card and sending files works fine with this setup. So kdeconnect actually can see the SD card.

Is there anything I can do to debug why kdeconnect can't see SD card?

I think my Sony Xperia Z3 compact shows the same problem with android 6, kde-connect not being able to write to the external sdcard, and not being able to read select directories(like the sdcard root). For some reason, the kde-connect process is missing the groups required for being able to read/write sdcards, namely sdcard_rw. I don't have a clue how the permission system works, but web research makes me believe it has something to do with (missing?) android.permission.WRITE_MEDIA_STORAGE. But i don't seem to be able to grant the app such a thing through the systems app permissions dialogs(all permissions there are enabled).

*** Bug 391464 has been marked as a duplicate of this bug. ***

*** Bug 389851 has been marked as a duplicate of this bug. ***

*** Bug 377058 has been marked as a duplicate of this bug. ***

I've noticed other apps like ES File Explorer, when they try to write something to the external SD card for the first time, pop up a file browser and tell the user to select it, to grant it permissions, and after that, it can write to subfolders of the SD card. It seems to require some kind of user interactivity to grant those permissions to each app the first time.

I think the following is relevant:

https://developer.android.com/training/data-storage/files#ExternalStoragePermissions

I can't write files to the external storage of a Galaxy S8 running Oreo.

*** Bug 399223 has been marked as a duplicate of this bug. ***

Add HTC M8 to the list.
user:/run/user/1000/93928376705e8277$ ls -l
ls: reading directory '.': Operation not permitted
total 0
user:cd /sdcard
user:/run/user/1000/93928376705e8277/sdcard$ ls -l
total 148
-rw-rw-rw- 1 administrator admin 72245 Aug 19  2017 0000_deleted.vcf
drwxrwxrwx 1 administrator admin     0 Jun 30  2017 Alarms

I have that problem with Galaxy S7, Android Oreo. SD Card is empty.

(In reply to jpo from comment #79)
> I think the following is relevant:
> 
> https://developer.android.com/training/data-storage/
> files#ExternalStoragePermissions
> 
> I can't write files to the external storage of a Galaxy S8 running Oreo.

You have reason. I think that's the problem. As KDEConnect doesn't let me access SD Card from my Linux, I tried other apps for Android like SyncMe or FileExplorer. These apps ask me to grant permissions first time I try to access to SD Card. So maybe to modify "manifest" file is all those apps not showing SDCard content needs.

(In reply to Rafael Linux User from comment #83)
> So maybe to modify "manifest" file is all those apps not showing SDCard content needs.

It's already there:

https://cgit.kde.org/kdeconnect-android.git/tree/AndroidManifest.xml#n29

Thank you jpo, I was just thinking in take a look to that file. However, it's curious (and maybe IS the trick) that apps I related ASK user about location of the SD Card root just when you try to access an external SD Card and you grant the access. That's to say, in SyncMe or "ES Explorer" apps, you are not asked about SD Card permission until you try to access SD Card from inside those apps. So, some way (maybe I'm wrong) KDEConnect should let user try to access SD Card and in that moment, Android system will ask for the very first time about grant or not to KDEConnect access to the SD Card till uninstallation.

I'll just make a test tonight about this theory.

(In reply to Rafael Linux User from comment #83)
> FileExplorer. These apps ask me to grant permissions first time I try to
> access to SD Card.

It is explained here :
https://developer.android.com/training/permissions/requesting.html

I understand the code has to handle specifically the permissions READ/WRITE_EXTERNAL_STORAGE because they are considered as "dangerous permissions". It is required since android 6.0. Any android developer can confirm ?

> I'll just make a test tonight about this theory.

I test and confirmed that permission to access SD Card are granted for KDE Connect in my Galaxy S7, but as we all know, there is no any moment in which KDE Connect let user try to access to the SD Card (as I said, that's the difference with other apps). 
I can confirm too something someone wrote here. Once you access to SD Card from Dolphin, if you modify the path and add a existent subfolder, you have READ access to that subfolder!!

Example:
My SD Card path thru KDEConnect is:
/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/

I know that I have a subfolder called "Music", so I put:
/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/Music
and mysteriously, I have read access to that folder.

Created attachment 118614 [details]
attachment-2069-0.html

Confirmed on the s8 .  The only failure appears to be listing the root directory of the so card.


On March 6, 2019 5:56:20 PM CST, Rafael Linux User <bugzilla_noreply@kde.org> wrote:
>https://bugs.kde.org/show_bug.cgi?id=336043
>
>--- Comment #87 from Rafael Linux User <rafael.linux.user@gmail.com>
>---
>> I'll just make a test tonight about this theory.
>
>I test and confirmed that permission to access SD Card are granted for
>KDE
>Connect in my Galaxy S7, but as we all know, there is no any moment in
>which
>KDE Connect let user try to access to the SD Card (as I said, that's
>the
>difference with other apps). 
>I can confirm too something someone wrote here. Once you access to SD
>Card from
>Dolphin, if you modify the path and add a existent subfolder, you have
>READ
>access to that subfolder!!
>
>Example:
>My SD Card path thru KDEConnect is:
>/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/
>
>I know that I have a subfolder called "Music", so I put:
>/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/Music
>and mysteriously, I have read access to that folder.
>
>-- 
>You are receiving this mail because:
>You are on the CC list for the bug.

> Example:
> My SD Card path thru KDEConnect is:
> /run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/
>
> I know that I have a subfolder called "Music", so I put:
> /run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/Music
> and mysteriously, I have read access to that folder.

it's looks like a bug about internal storage.

you can't add any file into a folder "download" for example.

but if you create a folder "toto" in "download" then you can add a file in "download" but not in "toto".

but if you create a folder "titi" in "toto" then you can add a file in "toto" but not in  "titi".

etc.

Created attachment 118621 [details]
ES Explorer: Access to storage is enabled from installation

Created attachment 118622 [details]
ES Explorer: User is asked about SD Card root folder where he want to access

Created attachment 118623 [details]
ES Explorer: Obtain sd card permissions

(In reply to Philippe ROUBACH from comment #89)
That's a madness Philippe. I only tried to create a folder in "Music", but it didn't let me do it, so I didn't try to do anything more complex, like you did.

Anyway, I insist in the way other apps does grant access to SD Card. Again, my example is "ES explorer". On installation, it ask about permissions to access storage, and I grant them. I checked that effectively (see attached screenshot), is enabled. However, that's not sufficient to access SD Card. User is asked for permissions when trying to do any operation on SD Card (see attached screenshot) OR user can configure in "ES Explorer" own configuration to "Obtain sd card permissions", obtaining removable drive (sd card) write permissions. And this is the way other apps works with SD Cards. However, KDEConnect have no options in config to obtain sd card permissions, only notify in installation about that possibility and if we agree.

This bug report actually addresses several different bugs.

All knows issues should be fixed by commits:
  5b2756b7f807c68d0f19e1f76a17a2decbd44d6f
  78c69a0cdcfcd44d8e8be2d3973265a11ffdc05a
  a6fdddf84379dc6d6da06295217870d1a1e970d2

and probably some more

Awesome ! I confirm, it works !
Thanks much, we were waiting since a long time to see a fix :)

When will it be out there for android updates to see it?


On 3/8/19 11:35 AM, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=336043
>
> --- Comment #95 from hamelg@laposte.net ---
> Awesome ! I confirm, it works !
> Thanks much, we were waiting since a long time to see a fix :)
>

Should be real quick, since yesterdays release was rejected by google

(In reply to Harry Coin from comment #96)
> When will it be out there for android updates to see it?
> 
> 
> On 3/8/19 11:35 AM, bugzilla_noreply@kde.org wrote:
> > https://bugs.kde.org/show_bug.cgi?id=336043
> >
> > --- Comment #95 from hamelg@laposte.net ---
> > Awesome ! I confirm, it works !
> > Thanks much, we were waiting since a long time to see a fix :)
> >

*** Bug 377058 has been marked as a duplicate of this bug. ***