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.
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.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.)