I created this app for helping mounting remote shares from a NAS or any other network drive. It works with Samba (CIFS) and NFSv3 shares.
The app requires root permissions (tested with SuperSU) because shell's "mount" command can be executed only as root.
It also requires in-kernel support for CIFS and/or NFS, without at least one of them the app won't work.
At first start you will be prompted with an empty shares list as you can see here:
My suggestion is to go to the Settings (top right icon) and change the "Mount point" to a writable path. You can use a path to the internal storage (/storage/sdcard0) or to the microsd (/storage/sdcard1) but I discourage you from doing that, and instead, on WeTek devices you can use "/tmp" that is mounted as a writable tmpfs.
After that just go back to the main window, press the "+" floating action button and add a share:
"Share name" will identify the share by creating a folder with that name in the previously selected "Mount point" so the share will be mounted there.
"Share address" must be a valid CIFS or NFSv3 share. An example of a valid CIFS share is "//192.168.0.100/Downloads", while a valid NFSv3 share is "192.168.0.100:/volume1/Portage/distfiles".
In "Mount options" you can set you username and password as shown in the screenshot, when this field is empty these options will be used for CIFS "username=guest,password=" and these for NFS "port=2049,nolock,proto=tcp".
The spinner will let you set the share as CIFS or NFS (if your device supports only one of them you will see only one).
You can't leave blank "Share name" and "Share address", and you cannot add or modify a share by using the same name or address of a share already present in the database.
Once added you will go back to the main screen that will look slightly different:
The share is not mounted yet, you have to turn on the switch on the right.
This switch will mark the share as "enabled". For example if you enable "Start service at boot", only the enabled shares will be mounted.
Once marked enabled the share will be probed for mount. You will see a circular progress bar on the left of the share name and, when it stops spinning, you will see a green check if the mount succeeded or a red cross if it failed.
To unmount a device you can disable it or long press on a mounted share. You can also long press on a share to mount it (in case it had previously failed for example because you had set a wrong password and you edited the share details to fix it, a short press on a share will bring you to the edit panel where you will be able to edit or delete the share) as long as the switch is turned on.
So to summarize long pressing on the share name will toggle mount/umount if the share is marked as enabled.
In case of failures check logcat that will give you more info.
This app has been developed to be used with a remote but it will work on phones/tablet as well, the UI might be a bit awkward but in case some people is interestead in using it on such devices I will consider working on a different layout for them.
The app is compatible starting with JB 4.1 devices but it's been tested on WeTek Core running 5.1
Download links
1.0.1
The app requires root permissions (tested with SuperSU) because shell's "mount" command can be executed only as root.
It also requires in-kernel support for CIFS and/or NFS, without at least one of them the app won't work.
At first start you will be prompted with an empty shares list as you can see here:
My suggestion is to go to the Settings (top right icon) and change the "Mount point" to a writable path. You can use a path to the internal storage (/storage/sdcard0) or to the microsd (/storage/sdcard1) but I discourage you from doing that, and instead, on WeTek devices you can use "/tmp" that is mounted as a writable tmpfs.
After that just go back to the main window, press the "+" floating action button and add a share:
"Share name" will identify the share by creating a folder with that name in the previously selected "Mount point" so the share will be mounted there.
"Share address" must be a valid CIFS or NFSv3 share. An example of a valid CIFS share is "//192.168.0.100/Downloads", while a valid NFSv3 share is "192.168.0.100:/volume1/Portage/distfiles".
In "Mount options" you can set you username and password as shown in the screenshot, when this field is empty these options will be used for CIFS "username=guest,password=" and these for NFS "port=2049,nolock,proto=tcp".
The spinner will let you set the share as CIFS or NFS (if your device supports only one of them you will see only one).
You can't leave blank "Share name" and "Share address", and you cannot add or modify a share by using the same name or address of a share already present in the database.
Once added you will go back to the main screen that will look slightly different:
The share is not mounted yet, you have to turn on the switch on the right.
This switch will mark the share as "enabled". For example if you enable "Start service at boot", only the enabled shares will be mounted.
Once marked enabled the share will be probed for mount. You will see a circular progress bar on the left of the share name and, when it stops spinning, you will see a green check if the mount succeeded or a red cross if it failed.
To unmount a device you can disable it or long press on a mounted share. You can also long press on a share to mount it (in case it had previously failed for example because you had set a wrong password and you edited the share details to fix it, a short press on a share will bring you to the edit panel where you will be able to edit or delete the share) as long as the switch is turned on.
So to summarize long pressing on the share name will toggle mount/umount if the share is marked as enabled.
In case of failures check logcat that will give you more info.
This app has been developed to be used with a remote but it will work on phones/tablet as well, the UI might be a bit awkward but in case some people is interestead in using it on such devices I will consider working on a different layout for them.
The app is compatible starting with JB 4.1 devices but it's been tested on WeTek Core running 5.1
Download links
1.0.1
