The MCCI ADB Interface Driver provides debug and diagnostic capabilities for Android product developers as well as features for end users.
Android products are normally debugged using USB, using a protocol called ADB (short for "Android Debug Bridge"). ADB also gives engineering access for users who wish to access their product at a low level. ADB is not a standard protocol, and Microsoft does not provide in-box drivers that support ADB. Therefore, system vendors must provide an ADB driver for use by developers and end users.
In the past, Google provided and supported such a driver. However, since late 2010, Google only provides reference code; it no longer supports the ADB driver. If it is to be used, the reference Driver in the SDK must be adapted and maintained. Google, however, is also not currently providing adaptation, maintenance, customization, or support services for this driver. In addition, the driver is not ready to pass WHQL testing without modification.
MCCI supplies an ADB Interface Driver that is fast, reliable, and passes WHQL testing. This driver's throughput for data transfers is not only better than the other available ADB Interface drivers but it can also be customized to meet specific needs. For example, you can use it with MCCI's composite driver to maximize battery life. Both drivers support selective suspend.
MCCI supports the ADB Interface Driver on current and legacy Windows versions (see below), allowing developers to focus efforts on product differentiation instead of developing and maintaining standard software components.
The MCCI ADB Interface Driver outperforms the ADB Interface Driver provided as a part of the Google SDK (version 4.0) as well as an adapted version of this driver (based on Google SDK Driver 5.2). The MCCI ADB Interface Driver is a clean-room implementation that is not an adaptation of the Android ADB Interface Driver.
Average Transfer Speed (KB/Second) for 20MB File Transfers (100 Runs)
Average Transfer Speed (KB/Second) for 886MB File Transfer (1 Run)
As shown in the test results above, the MCCI ADB Driver is between 10% and 20% faster than the drivers based on the Google SDK. This translates to time saved by developers, increasing productivity. In addition, using the MCCI ADB Interface Driver allows system vendors to focus their talents on more substantive product improvements, rather than fixing bugs in reference code or altering the code to comply with the requirements of Windows HCT testing.