I have two question about libwdi,they are:
1,Are all of the Android mobile phones WCID device?
2,Can Libwdi's driver installer install all of the Android mobile phone's driver automatically on Windows platform? Can the
coverage reach more than 98% or above?
thanks so much!
From: Pete Batard <pbatard@gm...> - 2013-01-06 22:05:17
On 06/01/2013 06:44, 赵子赢 wrote:
> I meet two question while studying libwdi and they are:
> 1,Are all of the Android mobile phones WCID device?
I don't think any of them is. I'm not an Android phone user (yet), but
I'd be very surprised if any of them uses WCID.
But it would really only be a matter of google to decide to add WCID
support to the USB stack or Android, as all the device has to do really
is reply with the right data when queried, and my understanding is that
the Android OS is in charge in the USB descriptors being returned from
In other words, if google wanted to do it, I believe all of the Androids
phone could be WCID and not require the installation of a driver for
WinUSB transfers in Windows Vista or later.
Now, this being said, most of the time the driver you want to use to
access a mobile phone is the Mass Storage driver rather than WinUSB
(which is what WCID would install), and it is not possible to use both
at the same time. Therefore, it is doubtful that google (or Android
phone operators) would want to force mobile phone users to install and
use a WinUSB application to access their data, when they can just
continue to present the device as Mass Storage to the OS.
> 2,Can Libwdi's driver installer install all of the Android mobile
> phone's driver automatically on Windows platform?
The only way I know to get automated USB driver installation on Windows,
if the device is not HID or Mass Storage, is through WCID.
> Can the coverage reach more than 98% or above?
If google decided to let Android users switch between Mass Storage mode
and WCID mode when connecting the device, then they could probably
achieve 100% coverage for all the versions of Android post the
introduction of that the feature. But of course, there would have to be
a global need for it, which I don't think exists at this stage: very few
users are expected to want to connect their Android phone to do anything
but transfer data using Mass Storage.
Thus, I'm afraid that you would have to convince google that there is a
need for WinUSB communication with an Android devices to use a WinUSB
based application that a very large number of Android owners will want
to use, if you want them to enable automated driver installation on
Windows. In all likelihood, unless you really do have a revolutionary
application to present, I'm doubtful there is much of a case for that...