dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 But /dev/fuse is mounted in three places: $ mount | grep fuse The above shows that the filesystem mounted at /storage/sdcard1 is /dev/fuse. dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 (which is confusing because I thought, and mount indicates, that /storage/sdcard is the mount point rather than the filesystem).Īnd the relevant output of mount: /dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 Here's the output of df related to the microSD card: Filesystem Size Used Free Blksize no access to stat() or other low-level calls at least not without some NDK development, which is a deep swimming pool to dive into, requiring architecture-specific builds.df doesn't output the 'mounted on' column.

dmesg doesn't run (klogctl: operation not permitted).Since we're on Android, we have some limitations relative to more typical Linux: I could take a guess that /sys/class/mmc_host/mmc1 corresponds to the microSD card mounted at /storage/sdcard1, but on some Android devices it's mmc0. I need to find the right directory so that I can grab the contents of files under it, such as cid, serial, oemid, and so on. sys/class/mmc_host/mmc1 (which is a link to /sys/devices/msm_sdcc.2/mmc_host/mmc1). sys/class/mmc_host/mmc0 (which is a link to /sys/devices/msm_sdcc.1/mmc_host/mmc0) vs. What I need: To find out which device folder it corresponds to, e.g. What I have: I know the place in the filesystem where a microSD card is mounted, e.g.

Multislot sysfs