Request for a little help: MTP ProductIDs

Search This thread

mdmower

Senior Member
Sep 14, 2011
826
1,044
Can anyone on a JB OTA sense rom gather some info regarding USB MTP for me? I need the Hardware ID for it to implement MTP support (optional!) in AOSP based ROMs. The information is very simple to gather:

I just need someone with Windows and a JB OTA sense rom installed to
* Plug in your phone via USB
* Mount your USB Storage
* Right-click your MTP device in Device Manager, choose Properties
* Go to Details tab, and choose "Hardware IDs" out of the dropdown box.
* Paste the PID_#### here.

Please do this with USB debugging enabled, and then repeat with USB debugging disabled.

Thanks.

EDIT: Request fulfilled, thanks RockR172.
 
Last edited:

Goatshocker

Senior Member
Oct 23, 2010
945
416
I cant help you, but I have to ask...
WHAT IN GODS NAME have you been smoking to even consider adding MTP support!? Its such a pathetic excuse for a file transfer protocol the original maker should be ashamed of himself. :eek::eek:
 

mdmower

Senior Member
Sep 14, 2011
826
1,044
I cant help you, but I have to ask...
WHAT IN GODS NAME have you been smoking to even consider adding MTP support!? Its such a pathetic excuse for a file transfer protocol the original maker should be ashamed of himself. :eek::eek:
Please read this wiki under the heading Prerequisites > Full hardware support. Though this device is in CM already, complying with this rule is still an objective.
 

Goatshocker

Senior Member
Oct 23, 2010
945
416
template.jpg



Okay, I change my "question" to: WHAT IN GODS NAME have the CM devs been smoking to come up with that rule.

Everyone should refuse to use MTP to show the world that ITS NOT AN ACCEPTABLE PROTOCOL!

... But thats just what I think..
 

Darknites

Senior Member
Jul 2, 2011
6,264
2,528
template.jpg



Okay, I change my "question" to: WHAT IN GODS NAME have the CM devs been smoking to come up with that rule.

Everyone should refuse to use MTP to show the world that ITS NOT AN ACCEPTABLE PROTOCOL!

... But thats just what I think..

Don't see the issue he did say it be optional.
 

mdmower

Senior Member
Sep 14, 2011
826
1,044
I will bump this just once in hopes that someone posts a useful reply. The information is quite simple to gather.
 

RockR172

Senior Member
Jun 12, 2011
1,420
1,503
Erm, I have 2 PID_### with USB Debugging enabled.. want both?

Sent from my HTC One S using Tapatalk 2

EDIT:
USB Debugging Enabled:
Code:
USB\Vid_0bb4&Pid_0df9&Rev_0228&MI_00

USB\Vid_0bb4&Pid_0df9&MI_00


With USB Debugging Disabled:
Code:
USB\Vid_0bb4&Pid_0f91&Rev_0228&MI_00

USB\Vid_0bb4&Pid_0f91&MI_00


Hope this is what you wanted.
:)
 
Last edited:
  • Like
Reactions: mdmower

mdmower

Senior Member
Sep 14, 2011
826
1,044
Erm, I have 2 PID_### with USB Debugging enabled.. want both?

Sent from my HTC One S using Tapatalk 2

EDIT:
USB Debugging Enabled:
Code:
USB\Vid_0bb4&Pid_0df9&Rev_0228&MI_00

USB\Vid_0bb4&Pid_0df9&MI_00


With USB Debugging Disabled:
Code:
USB\Vid_0bb4&Pid_0f91&Rev_0228&MI_00

USB\Vid_0bb4&Pid_0f91&MI_00


Hope this is what you wanted.
:)

That is exactly what I was looking for, thank you for the help!

The MTP PID (0f91) is shared between evita, jewel, and ville, it seems. The MTP+ADB PID (0df9) is distinct from other devices though.
 
Last edited:

RockR172

Senior Member
Jun 12, 2011
1,420
1,503
That is exactly what I was looking for, thank you for the help!

The MTP PID (0f91) is shared between evita, jewel, and ville, it seems. The MTP+ADB PID (0df9) is distinct from other devices though.
Is the MTP+ADB PID of evita and jewel the same?
Also, how will these product ID's help in implementing MTP in CM code? :)
 

mdmower

Senior Member
Sep 14, 2011
826
1,044
Is the MTP+ADB PID of evita and jewel the same?
Also, how will these product ID's help in implementing MTP in CM code? :)

The MTP+ADB PID is distinct between evita and jewel as well. So this falls in line with that pattern.

Windows is finicky about identifying devices and loading the correct drivers/connection type. It is important that the correct PID is specified so windows will know how to interact with the device.

Mac and Linux (although MTP support in Linux isn't terrific) do a better job of working with a device regardless of PID.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Is the MTP+ADB PID of evita and jewel the same?
    Also, how will these product ID's help in implementing MTP in CM code? :)

    The MTP+ADB PID is distinct between evita and jewel as well. So this falls in line with that pattern.

    Windows is finicky about identifying devices and loading the correct drivers/connection type. It is important that the correct PID is specified so windows will know how to interact with the device.

    Mac and Linux (although MTP support in Linux isn't terrific) do a better job of working with a device regardless of PID.
    1
    I cant help you, but I have to ask...
    WHAT IN GODS NAME have you been smoking to even consider adding MTP support!? Its such a pathetic excuse for a file transfer protocol the original maker should be ashamed of himself. :eek::eek:
    1
    Erm, I have 2 PID_### with USB Debugging enabled.. want both?

    Sent from my HTC One S using Tapatalk 2

    EDIT:
    USB Debugging Enabled:
    Code:
    USB\Vid_0bb4&Pid_0df9&Rev_0228&MI_00
    
    USB\Vid_0bb4&Pid_0df9&MI_00


    With USB Debugging Disabled:
    Code:
    USB\Vid_0bb4&Pid_0f91&Rev_0228&MI_00
    
    USB\Vid_0bb4&Pid_0f91&MI_00


    Hope this is what you wanted.
    :)