MTP testing

Does anybody have any devices that support MTP? (later Android versions do).

I've built the libmtp tools - you'll need libusb.library if you don't have it - but on my Nexus 7 they pause for ages recursing silently into several thousand directories:
http://homepage.ntlworld.com/cdyoung/tmp/mtp.lha

Just wondering if this was just me, the device, or some ridiculous design flaw in libmtp.

My phone and tablet do but I will not be able to test them until Sunday since I am currently away from home. I didn't know it was supported but now I do, I want to give it a go.

I have an HP slate 7 (I know, it's crap but I needed the long battery life) using android 4.1.1.
mtp-detect just reports no device found, the tablet reports it's connected in PTP mode as a camera.

@Severin

If you tap on the USB connection notification, it should give you an option to switch between PTP and MTP.

I can test it later on my Galaxy Tab 3

I just need to know what I am testing for :)

Connect it up.
Run mtp-detect from the Shell.
Output will be something like "Found MTP device: Samsung Galaxy Tab". A few lines later it will say something about Android bugs.
At this point I have to wait about ten minutes before anything else is printed (it is recursing through every single directory on the device). <--- I'm interested to know if this stage is slow for everybody.

I should probably try libmtp under Linux to see if it is similarly rubbish there.

@Chris

Quote:

I don't get any notifications any more maybe an update killed it because I used to get them. I suspect USB is only for charging on this crap tablet, I've tried a couple of USD diagnostic / settings apps and they just sit there doing nothing, they don't detect anything.

@Chris
I just got a DSI error.

@Severin

The notification is hidden here (Android 4.3), needs a swipe down on the notification area and appears in the list.

@yssing

Crashlog? Although I'm not sure how useful that'll be.

I've got both 4.1.3 and 4.0.4 versions of Android with a phone + tablet that I will test with

I have a 2.3 android phone I can try and I am sure my girlfriends android phone is newer, maybe I can try it on that one.

If I choose to ignore the DSI error, the program continues, but with no connection.

@Chris

Yeah, I saw them a few times when I first got the tablet but haven't had any for several weeks and iirc there was aa android update around the same time or it could be I'm using a different lead, maybe the incredibly cheap USB F to micro USB M lead I got from china is borked, charging works which is what I need but no other usb devices work with it.

I know HP cut corerners with the tablet, no hdmi output etc. maybe it boesn't support mice or keyboards either.

@yssing

2.3 supports Mass Storage instead of MTP.

Apparently you can enable mass storage on newer ones with the USB debugging option, but it doesn't work with devices using the merged/virtual filesystem like the Nexi.

About the libusb.library when i type version in shell i get 0.1

Here is the output from shell. It doesnt take time. just outputs some info, i get a crash and when ignoring DSI the rest of the info is typed.

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 0, dev 0
Attempting to connect device(s)
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
OK.


Here's the crashlog.


Crash log for task "mtp-detect"
Generated by GrimReaper 53.16
Crash occured in module mtp-detect at address 0x7E5128C0
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 00000002 54B0BB60 00000000 5680C658 00000000 FFFFFFFF 00000068 6FF8F000
8: 6860D1FE 00000000 00000000 49000207 0000079C 60350648 568232BC 568232E8
16: 56823248 568231D0 568232DC 568232B4 568232D0 00000000 00000000 5680C428
24: 5680C430 00000000 5680C478 5680C408 56827048 5680C658 5680C408 55D2A4E8


FPR (Floating Point Registers, NaN = Not a Number):
0: nan -4.4678e+307 nan -4.4678e+307
4: -3.57144e+250 -4.4678e+307 -4.4678e+307 -4.4678e+307
8: -4.4678e+307 901 5 101
12: 115 12 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 0 0 0 0

FPSCR (Floating Point Status and Control Register): 0x82004000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0000B030
Condition (cr) : 0x5686F390
Instruction Pointer (ip) : 0x7E5128C0
Xtended Exception (xer) : 0x02028A78
Count (ctr) : 0x00000000
Link (lr) : 0x00000000
DSI Status (dsisr) : 0x020462B0
Data Address (dar) : 0x00000000



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x7E5128C0 belongs to module "mtp-detect" (HUNK/Kickstart)

Stack trace:
module mtp-detect at 0x7E5128C0 (section 5 @ 0x2589C)
module mtp-detect at 0x7E512864 (section 5 @ 0x25840)
module mtp-detect at 0x7E4F9DA4 (section 5 @ 0xCD80)
module mtp-detect at 0x7E4ED4E0 (section 5 @ 0x4BC)
native kernel module newlib.library.kmod+0x000020a4
native kernel module newlib.library.kmod+0x00002d0c
native kernel module newlib.library.kmod+0x00002ee8
_start()+0x170 (section 1 @ 0x16C)
native kernel module dos.library.kmod+0x00024f18
native kernel module kernel+0x00042514
native kernel module kernel+0x00042594

PPC disassembly:
7e5128b8: 809f021e lwz r4,542(r31)
7e5128bc: 3b200000 li r25,0
*7e5128c0: 88040005 lbz r0,5(r4)
7e5128c4: 1c790016 mulli r3,r25,22
7e5128c8: 3b800000 li r28,0

System information:

CPU
Model: P.A. Semi PWRficient PA6T-1682M VB1
CPU speed: 1800 MHz
FSB speed: 900 MHz
Extensions: altivec

Machine
Machine name: AmigaOne X1000
Memory: 2097152 KB
Extensions: bus.pci bus.pcie

@Kicko

Quote:

Well, that doesn't look good. Are you sure the rest of the info it prints out is valid?

If you run mtp-albums (??) or one of the other ones does it give you lists of files on the device?

@Chris

Quote:

then I ignore upcoming DSI...

Quote:

This is MTP enabled on device... and it's a Samsung-Galaxy-Tab-2-GT-P3110

cheers Gerograph

The Galaxy does not work with libmtp: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/903422

Old thread but anyway wanted to try out mpt-detect with my LG G2 with android 4.4.2 (still waiting for lollipop).

I got this after trying out mtp-detect
assertion "LibusbBase != NULL" failed: file "autoinit_libusb_base.c", line 31

Im on AmigaOS4.1 FE on X1000

@Kicko

You need to install libusb.library.

@Chris
I tried it with a Galaxy phone but get only a Grimreaper.Sadly that it doesn`t work with Galaxy phone`s