#975 Unable to open folder

[Anonymous]

Here's the result. The Folder 'interner Speicher' is visible, but won't open

richi@richi-Mint16-Product-Name ~ $ mtpfs ./handy/
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=0bb4 and PID=0f64) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:0f64 @ bus 2, dev 5
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: (NULL)

[Anonymous]

btw: Device is a HTC One

[Linus Walleij]

DEVICE ADDED

This device has been added to the libmtp database in GIT.
You can verify it by browsing the database here:
https://sourceforge.net/p/libmtp/code/ci/HEAD/tree/src/music-players.h

If you want to test your device with the new support added in
GIT, refer to making a GIT check-out:
https://sourceforge.net/p/libmtp/code/ci/HEAD/tree/

You can further help us with libmtp by identifying if this device
needs some futher special device flags. If a device has "siblings"
in the database (similar devices from same manufacturer) we
often add default bug flags like its closest siblings, and sometimes
this is right, sometimes bugs have been fixed so it's wrong.

If you have special problems, refer to the README file:
https://sourceforge.net/p/libmtp/code/ci/HEAD/tree/README

If you have problems installing and linking the library refer to
the INSTALL file:
https://sourceforge.net/p/libmtp/code/ci/HEAD/tree/INSTALL

For Android devices: notice that these often have SEVERAL device IDs,
not just one. Usually all combined USB modes (like MTP+MSC, MTP+modem,
MTP+ADB etc) have their own device ID. This is because Windows cannot
handle a VID+PID changing functionality on-the-fly. (Linux can, BTW.)