115
115
time intensive, and in these cases it's better than the user do this
118
Q. I have an Android device and .... isn't working?
119
A. There are a few answers or explanations with Android.
120
1. Some device vendors have opted to use their own MTP software stack with
121
their device, and some of these implementations are horribly broken.
122
Contact your device manufacturer for further assistance. (AFAIK, this is
123
primarily Samsung with Android 2.x devices, and some lesser known Chinese
124
developed handsets often rebadged as Carrier own-brand handsets).
125
2. Android 1.x-2.x doesn't have a native MTP implementation, so if your
126
device has MTP functionality, see the above comment.
127
3. Android 3.x-4.x has native MTP functionality, but is missing some
128
features and does have some bugs in the implementation. Some noted
130
a. Does not support albums or album metadata. So you can't upload custom
132
b. Some users have reported issues with Playlist support. (Try to get a
133
newer revision of your version of Android).
134
c. Android 3.2 has a nasty bug, in that an application is unable to
135
call the Storage APIs more than once in a session. gMTP 1.3.2 works
136
around this by caching the device storage information. (but not the
137
file listing or related metadata).
138
d. Samsung Galaxy and Google Nexus devices have connectivity issues, that
139
I'm hoping can be resolved via patches to libmtp. Sorry, there is
140
nothing I can do about that situation. Complain to Samsung and Google,
141
and try to get them actively involved in libmtp.
120
145
1. Bugfixes as needed.