Hello Darran, On Sun, May 06, 2012 at 01:28:55PM +0000, Darran Kartaschew wrote: > Thank you for submitting the bug report, but would just like to confirm which > version of Android your tablet is running. (Android 3.2 or Android 4.0)
as of today I am running Android 4.0.6. Before 4.0.6 I had 4.0.5 installed. With 4.0.6 this problem still exists ... :( > There is a known issue with some Android releases related to the MTP software > stack, in that some API calls will return an error when called twice is a > row, rather than returning the desired information on each API call. As I am not a developer: How do I find out, that this happens to me? > One of the problematic MTP API calls is the GetStorage call, in that if it's > called repeatedly with no other operations occuring in between Android will > return an error, rather than just servicing the API call (which is the > correct response). I believe based on the error message you provided, it's > this MTP API call is the source of the issue you are experiencing. O.K. > I have a Toshiba Thrive 7 tablet (running Android 3.2) that has the same > problem, but have yet to determine the best course of action in how gMTP > should handle this type of error (inability to get storage parameters from > the device). Currently gMTP simply reports the error and disconnects the > device, as the storage information retrieved can't be trusted, and I want to > avoid all possibilities of device filesystem corruption. Originally I had Android 3.2.80 installed. With this Android version I could copy files to my Archos PMP (though I got a warning about creating and/or reading the album tag, IIRC). After I discovered the newer 4.0.5 on Archos' web site, I was interested to test it ... ;) > Once I have a working solution to this sort of problem, I'll be releasing > gMTP 1.3.2 as soon as possible. My only other advise is to keep libmtp up to > date as much as possible, as libmtp has many work-arounds for problematic > devices (and Android certainly has it's share of problems in it's MTP > implementation, as do all MTP implementations). In Debian Testing AMD64 the up-to-date version of mtp-tools, libmtp9 and libmtp-common is version 1.1.3-2, which is the newest version in Debian SID as well. Or is there a newer version (without compiling it from git or so), which I have not found yet? > PS. For those Android devices that support MTP and are running Android 2.x, > the MTP implementation is supplied by the device implementor and not Google, > so you should not see the above mentioned issue. Only those devices running > Android 3.x+, that may be using the MTP software stack native to Android, may > come across the above mentioned issue. (I have reports from other tablet > owners running Android 3.2 that do not have the above mentioned issue). O.K. Thank you for all these information and have a nice evening Thomas. -- Natural laws have no pity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
