Open risacher opened 10 years ago
It bould be fine, if those devices are recognized by libmtp. See libmtp devel page to add your devices.
As it turns out, both devices are recognized by libmtp in git, but were not in version 1.1.6, which was what I had installed via Homebrew (http://brew.sh/). I haven't gotten around to testing yet with the updated libmtp because I'm not familiar enough with Homebrew. Like most things, it's probably easy if you know how to do it.
I just had the same experience with a Google/LG Nexus 5 on Mac OS X Mavericks. I also tried with libmtp build from the latest git sources and got the same result: the mount only works when the -d/--debug argument to simple-mtpfs is given. I'm happy to provide more information, e.g. the debug output from simple-mtpfs if it would be useful.
I can mount my Nexus 5 to Fedora box (f20) without any problem.
Same experience with a Google Nexus 7 on OS X Mavericks. Worked fine in debug mode.
Used the libmtp available on home-brew.
All, I am trying to get this project going on OSX and am having little luck. I admit, I am an XCode user looking to get access to an MTP device and so my knowledge of standard Linux/Unix tools is limited. I would appreciate any help in getting this project up and running on OSX.
+1 here. Only works in debug mode.
Ok it seems that it is not debug mode which is the thing, it is foreground mode.
So running:
simple-mtpfs -f /Users/cs/Desktop/nexus
will work
Ok, found the problem:
Running in the background disabled because of an imcompatiblity between fork and libmtp under Max OS X
I installed with homebrew with osxfuse and running in the foreground doesn't work either. Even with -o debug
I get no output.
@terinjokes Here try my fork;
I'm similarly only seeing it work with foreground operation. I'm on OSX 10.9.5, using mtpfs "stable 0.2" and libmtps 1.1.10, both installed from homebrew. I'm using a Moto G.
Thanks for making an alternative to android file transfer and extracating the SD card from my phone every time!
Confirm. Only working with -f
or -d
. So it's probably foreground issue. Without -f
it starts but burns 100% CPU, volume shows as mounted but device is empty.
I will try to reproduce this asap. Thanks.
I came here because, like @terinjokes above, mounting wouldn't work at all. It turns out that the problem was that I tried a mount point under /Volumes
. Once I created a mount point on my desktop (and I used the foreground mode) things started to work.
To mount on /Volumes, try:
sudo mkdir /Volumes/VOLUME_NAME # create directory
sudo chmod -N /Volumes/VOLUME_NAME # remove access control restrictions
sudo chown USER_NAME /Volumes/VOLUME_NAME # allow user access
simple-mtpfs -f /Volumes/VOLUME_NAME # mount
Question: is this incompatibility between fork and libmtp under Max OS X possible to be fixed?
simple-mtpfs only works for me in debug mode. If I don't use debug mode, it will appear to succeed, but the mounted directory is empty. When using "simple-mtpfs -d ~/mtp" the mount succeeds and actually accesses files.
FWIW, tested with an Kindle Fire HDX and HTC One, both of which are unrecognized devices by libmtp at this time.