USB file transfer problem - my own investigation

Lukasz Post time 2016-11-21 15:30:36 | Show all posts  Close [Copy link]
5 3305
View: 3305|Reply: 5

USB file transfer problem - my own investigation

 Close [Copy link]

5

threads

34

posts

302

credits

Platinum Member

Rank: 3Rank: 3

credits
302

Warmest Heart UMIDIGIerUMIDIGIer

Post time 2016-2-20 07:40:52 | Show all posts |Read mode
Edited by Lukasz at 2016-2-20 07:59 \n\nHello all,

I was able to determine that:
  • main USB port in UMI IRON is USB 2.0 (Hi-Speed) port (hooray!)
  • Android properly recognizes connected devices - both USB 2.0 Hi-Speed and USB 1.1
  • The speed of file transfer pendive -> phone exceeds the specifications of USB 1.1 (additional check - pendrive was successfully recognized as a USB 2.0 Hi-Speed)
  • Computer (MTP connection) recognizes the phone as it's max-speed is 12Mb/s (full)

Everything step by step:
  • I have had many theories, so I started checking them one by one.
  • At the beginning I wanted to see if USB port in UMI IRON is really USB 2.0 (Hi-Speed).
  • I connected mouse to my UMI IRON and Android detect it as USB 1.10 device

USB Mouse connected to UMI IRON

USB Mouse connected to UMI IRON




  • I connected mouse to the UMI IRON and Android detect it as  USB 2.00 Hi-Speed devise

Pendrive connected to UMI IRON

Pendrive connected to UMI IRON

  • Ok. Android detects USB 2.0 devices correctly.
  • In order to make sure that there is USB 2.0 port, I also copy 200MB file from my pendrive to phone.

File copy test 2

File copy test 2

File copy test

File copy test

USB copy test 3

USB copy test 3

  • Time of copy speed is similar on my PC too (pendrive -> PC file copy)



200MB 0:00:12 [16,6MB/s] [==================================>] 100%


Ok. Speed of file transfer pendive -> phone exceeds the specifications of USB 1.1 (additional check - pendrive was successfully recognized as a USB 2.0 Hi-Speed). If so, then finally the device propably is poorly detected by computer. I checked it, too:

My computer recognizes UMI IRON as:

IRON
Manufacturer: MediaTek
Serial Number: 0123456789ABCDEF
Speed: 12Mb/s (full)
USB Version:  2.00
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0e8d
Product Id: 2008
Revision Number: ff.ff

Config Number: 1
        Number of Interfaces: 1
        Attributes: c0
        MaxPower Needed: 500mA

        Interface Number: 0
                Name: usbfs
                Alternate Number: 0
                Class: ff(vend.)
                Sub Class: ff
                Protocol: 00
                Number of Endpoints: 3

                        Endpoint Address: 81
                        Direction: in
                        Attribute: 2
                        Type: Bulk
                        Max Packet Size: 64
                        Interval: 0ms

                        Endpoint Address: 01
                        Direction: out
                        Attribute: 2
                        Type: Bulk
                        Max Packet Size: 64
                        Interval: 0ms

                        Endpoint Address: 82
                        Direction: in
                        Attribute: 3
                        Type: Int.
                        Max Packet Size: 28
                        Interval: 6ms

More information:
Bus 006 Device 009: ID 0e8d:2008 MediaTek Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0e8d MediaTek Inc.
  idProduct          0x2008
  bcdDevice           ff.ff
  iManufacturer           2 MediaTek
  iProduct                3 IRON
  iSerial                 4 0123456789ABCDEF
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol      0
      iInterface             17 MTP
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x001c  1x 28 bytes
        bInterval               6
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

To sum up - it seems to me the problem is fully on the software side. UMI IRON seems to have USB 2.0 Hi-Speed port.

I'm very sorry if I missed something or maybe wrote somethink wrong. I'm strongly tired, but I wanted to finish this experiments.I really hope it will be helpful to fix the problem with the USB in our UMI IRON :-)

5

threads

34

posts

302

credits

Platinum Member

Rank: 3Rank: 3

credits
302

Warmest Heart UMIDIGIerUMIDIGIer

 Author| Post time 2016-2-20 07:40:53 | Show all posts
Edited by Lukasz at 2016-2-20 07:57 \n\nFor comparison, USB details for my Samsung tablet:
SAMSUNG_Android
Manufacturer: SAMSUNG
Serial Number: ***********************************
Speed: 480Mb/s (high)
USB Version: 2.10
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 64
Number of Configurations: 2
Vendor Id: ***********************************
Product Id: ***********************************
Revision Number: 4.00

Config Number: 1
Number of Interfaces: 1
Attributes: c0
MaxPower Needed: 96mA

Interface Number: 0
Name: usbfs
Alternate Number: 0
Class: 06(still)
Sub Class: 01
Protocol: 01
Number of Endpoints: 3

Endpoint Address: 81
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms

Endpoint Address: 01
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 125us

Endpoint Address: 82
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 28
Interval: 4ms

Config Number: 2
Number of Interfaces: 3
Attributes: c0
MaxPower Needed: 96mA

Interface Number: 0
Name:
Alternate Number: 0
Class: 06(still)
Sub Class: 01
Protocol: 01
Number of Endpoints: 3

Endpoint Address: 81
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms

Endpoint Address: 01
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 125us

Endpoint Address: 82
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 28
Interval: 4ms

Interface Number: 1
Name:
Alternate Number: 0
Class: 02(comm.)
Sub Class: 02
Protocol: 01
Number of Endpoints: 1

Endpoint Address: 84
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 10
Interval: 32ms

Interface Number: 2
Name:
Alternate Number: 0
Class: 0a(data )
Sub Class: 00
Protocol: 00
Number of Endpoints: 2

Endpoint Address: 83
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms

Endpoint Address: 02
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms
Bus 002 Device 014: ID ********************* Samsung Electronics Co., Ltd **********************************************************
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor **********************************************************
idProduct **********************************************************
bcdDevice 4.00
iManufacturer 1 SAMSUNG
iProduct 2 SAMSUNG_Android
iSerial 3 **********************************************************
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 96mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
iInterface 5 MTP
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x001c 1x 28 bytes
bInterval 6
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 105
bNumInterfaces 3
bConfigurationValue 2
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 96mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
iInterface 5 MTP
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x001c 1x 28 bytes
bInterval 6
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 1
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 2 Abstract (modem)
bFunctionProtocol 1 AT-commands (v.25ter)
iFunction 8 CDC Serial
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 6 CDC Abstract Control Model (ACM)
CDC Header:
bcdCDC 1.10
CDC Call Management:
bmCapabilities 0x00
bDataInterface 2
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 1
bSlaveInterface 2
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 7 CDC ACM Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000000
(Missing must-be-set LPM bit!)
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000f
Device can operate at Low Speed (1Mbps)
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 1 micro seconds
bU2DevExitLat 500 micro seconds
Device Status: 0x0000
(Bus Powered)

And pendrive:

DataTraveler 2.0
Manufacturer: Kingston
Serial Number: **************************************************
Speed: 480Mb/s (high)
USB Version: 2.00
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0951
Product Id: 1603
Revision Number: 2.00

Config Number: 1
Number of Interfaces: 1
Attributes: 80
MaxPower Needed: 100mA

Interface Number: 0
Name: usb-storage
Alternate Number: 0
Class: 08(stor.)
Sub Class: 06
Protocol: 50
Number of Endpoints: 2

Endpoint Address: 81
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms

Endpoint Address: 02
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms
Bus 002 Device 015: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0951 Kingston Technology
idProduct 0x1603 DataTraveler 1GB/2GB Pen Drive
bcdDevice 2.00
iManufacturer 1 Kingston
iProduct 2 DataTraveler 2.0
iSerial 3 ********************************
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

5

threads

34

posts

302

credits

Platinum Member

Rank: 3Rank: 3

credits
302

Warmest Heart UMIDIGIerUMIDIGIer

 Author| Post time 2016-2-20 08:06:49 | Show all posts
Screenshot_2016-02-20-01-05-44.png


1

threads

8

posts

52

credits

Senior Member

Rank: 2

credits
52
Post time 2016-3-8 00:29:11 | Show all posts
Are 'we' any closer to resolving this issue?
having found out that I was 1 of the people affected by the 4G misprint (band 20 not actually supported making 4G almost pointless in the UK) I've now found that I can't use Smartlink / MirrorLink to connect the Iron to my car as the transfer rate is too slow

This is a BIG shame as I though the Iron was a good phone, I could even live with the wifi dropping. Does the Iron Pro ROM fix the transfer speed issue??
Post time 2016-3-8 04:47:07 | Show all posts
According to our earlier investigations, the slow USB issue is (probably) related to the hardware, so that cannot be resolved by a software update.
The list of available 4G (FDD) frequencies was never misprinted on UMI's official product page.
http://www.umidigi.com/?page-UMIIRON_Specification.html

0

threads

9

posts

67

credits

Senior Member

Rank: 2

credits
67
Post time 2016-11-21 15:30:36 | Show all posts
From my view, maybe you can try other professional data transfer tool.
AirDroid is a nice choice to transfer data between your phone and pc.
Such android transfer tool allows you to transfer data wirelessly.
Hope it helps.
You have to log in before you can reply Login | WELCOME TO UMIDIGI COMMUNITY

Points Rules

Quick Reply Top Back to list