Google is committed to advancing racial equity for Black communities. See how.

The Google USB Driver is required for Windows if you want to performadb debugging with Google devices. Windows drivers forall other devices are provided by the respective hardware manufacturer, as listed in theOEM USB Drivers document.

Drivers 3gstick Usb Devices Adapter

Note:If you're developing on Mac OS X or Linux, then you do not need to install a USBdriver. Instead seeUsing Hardware Devices.

You can download the Google USB Driver for Windows in one of two ways:

If your USB device does not work the most likely problem is missing or outdated drivers. When you plug the device into your USB, Windows will look for the associated driver, if it cannot find this driver then you will be prompted to insert the driver disc that came with your device. Common USB Device errors are ‘usb port not working. USB Drivers for Android. USB Drivers for Android is a mobile application that allows you to connect. License: Free OS: Android Language. If the device is not yet connected, first install the device-specific driver, such as by using the appropriate installer. After the device-specific driver is installed, Windows 10 will select that driver instead of the standard USB audio 2.0 driver when you first connect the device. The package provides the installation files for Microsoft Xbox 360 Controller USB Driver version If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version.

  • Or, get it from the Android SDK Manager as follows:
    1. In Android Studio, click Tools > SDK Manager.
    2. Click the SDK Tools tab.
    3. Select Google USB Driver and click OK.

      Figure 1. The SDK Manager with the Google USB Driver selected

    4. Proceed to install the package. When done, the driver files are downloaded into the android_sdkextrasgoogleusb_driver directory.

    Using the SDK Managerhelps you keep the driver up to date by notifying you when your current driveris out of date.

For installation information, readInstall a USB Driver.

Download the Google USB driver

Before downloading, you must agree to the following terms and conditions.

Drivers 3gstick USB Devices

Terms and Conditions

This is the Android Software Development Kit License Agreement

1. Introduction

1.1 The Android Software Development Kit (referred to in the License Agreement as the 'SDK' and specifically including the Android system files, packaged APIs, and Google APIs add-ons) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK.1.2 'Android' means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL:, as updated from time to time.1.3 A 'compatible implementation' means any Android device that (i) complies with the Android Compatibility Definition document, which can be found at the Android compatibility website ( and which may be updated from time to time; and (ii) successfully passes the Android Compatibility Test Suite (CTS).1.4 'Google' means Google LLC, organized under the laws of the State of Delaware, USA, and operating under the laws of the USA with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA.

2. Accepting this License Agreement

2.1 In order to use the SDK, you must first agree to the License Agreement. You may not use the SDK if you do not accept the License Agreement.2.2 By clicking to accept and/or using this SDK, you hereby agree to the terms of the License Agreement.2.3 You may not use the SDK and may not accept the License Agreement if you are a person barred from receiving the SDK under the laws of the United States or other countries, including the country in which you are resident or from which you use the SDK.2.4 If you are agreeing to be bound by the License Agreement on behalf of your employer or other entity, you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity.

3. SDK License from Google

3.1 Subject to the terms of the License Agreement, Google grants you a limited, worldwide, royalty-free, non-assignable, non-exclusive, and non-sublicensable license to use the SDK solely to develop applications for compatible implementations of Android.3.2 You may not use this SDK to develop applications for other platforms (including non-compatible implementations of Android) or to develop another SDK. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose.3.3 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. 'Intellectual Property Rights' means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you.3.4 You may not use the SDK for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK.3.5 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement.3.6 You agree that the form and nature of the SDK that Google provides may change without prior notice to you and that future versions of the SDK may be incompatible with applications developed on previous versions of the SDK. You agree that Google may stop (permanently or temporarily) providing the SDK (or any features within the SDK) to you or to users generally at Google's sole discretion, without prior notice to you.3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features.3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the SDK.

4. Use of the SDK by You

4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications.4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) the License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries).4.3 You agree that if you use the SDK to develop applications for general public users, you will protect the privacy and legal rights of those users. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so.4.4 You agree that you will not engage in any activity with the SDK, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of any third party including, but not limited to, Google or any mobile communications carrier.4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so.4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.

5. Your Developer Credentials

5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.

6. Privacy and Information

6.1 In order to continually innovate and improve the SDK, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the SDK are being used and how they are being used. Before any of this information is collected, the SDK will notify you and seek your consent. If you withhold consent, the information will not be collected.6.2 The data collected is examined in the aggregate to improve the SDK and is maintained in accordance with Google's Privacy Policy.6.3 Anonymized and aggregated sets of the data may be shared with Google partners to improve the SDK.

7. Third Party Applications

7.1 If you use the SDK to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources.7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners.7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party. In that case, the License Agreement does not affect your legal relationship with these third parties.

8. Using Android APIs

8.1 Google Data APIs8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service.8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. If you use the Android Recognition Service API, documented at the following URL:, as updated from time to time, you acknowledge that the use of the API is subject to the Data Processing Addendum for Products where Google is a Data Processor, which is located at the following URL:, as updated from time to time. By clicking to accept, you hereby agree to the terms of the Data Processing Addendum for Products where Google is a Data Processor.

9. Terminating this License Agreement

9.1 The License Agreement will continue to apply until terminated by either you or Google as set out below.9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the SDK and any relevant developer credentials.9.3 Google may at any time, terminate the License Agreement with you if:(A) you have breached any provision of the License Agreement; or(B) Google is required to do so by law; or(C) the partner with whom Google offered certain parts of SDK (such as APIs) to you has terminated its relationship with Google or ceased to offer certain parts of the SDK to you; or(D) Google decides to no longer provide the SDK or certain parts of the SDK to users in the country in which you are resident or from which you use the service, or the provision of the SDK or certain SDK services to you by Google is, in Google's sole discretion, no longer commercially viable.9.4 When the License Agreement comes to an end, all of the legal rights, obligations and liabilities that you and Google have benefited from, been subject to (or which have accrued over time whilst the License Agreement has been in force) or which are expressed to continue indefinitely, shall be unaffected by this cessation, and the provisions of paragraph 14.7 shall continue to apply to such rights, obligations and liabilities indefinitely.





12. Indemnification

12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) your use of the SDK, (b) any application you develop on the SDK that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you with the License Agreement.

13. Changes to the License Agreement

13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.

14. General Legal Terms

14.1 The License Agreement constitutes the whole legal agreement between you and Google and governs your use of the SDK (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the SDK.14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google.14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable.14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to the License Agreement.14.5 EXPORT RESTRICTIONS. THE SDK IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE SDK. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE.14.6 The rights granted in the License Agreement may not be assigned or transferred by either you or Google without the prior written approval of the other party. Neither you nor Google shall be permitted to delegate their responsibilities or obligations under the License Agreement without the prior written approval of the other party.14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction.January 16, 2019

From DD-WRT Wiki

Jump to: navigation, search

English • Deutsch • Español • Français • Italiano • 日本語 • Polski • Português • Русский • Svenska • ‪中文(中国大陆)‬ • ‪中文(台灣)‬ •

See also: USB Storage or USB Printer Sharing

  • 2USB devices

[edit] USB support

Of the Supported Devices, some support USB. These include the:

  • ASUS WL-500g Premium V.1 (German) and ASUS WL-500g Premium V.2
  • Asus WL-520GU and various devices in this same series
  • Linksys WRT610N Versions 1 and 2
  • plus many newer routers

Note: If the router hardware has a USB port, dd-wrt probably supports it. It may require a certain kernel or certain build but it should support. See the wiki page or the forums for your particular router.

Some versions of dd-wrt have USB support built in and can be enabled via the web-GUI, but all versions of dd-wrt can have USB enabled by installing the required kernel modules to JFFS, then using a startup script to mount individual devices. See USB storage for instructions and example scripts.


The cost of USB-capable network routers starts at around $26 for the TP-LINK TL-WR842ND (as of November 25, 2014), depending on capability, but the ability to add external hardware easily makes these far more powerful units.

[edit] USB devices

The various USB options include:

  • Network-attached storage including flash memories, hard discs, floppy discs and CD/DVD-ROM devices. These can be shared across a LAN using Samba; an external hard drive also provides plentiful swap space for use as virtual memory.
  • Printer Sharing; as either a pass-through driver ([p910nd] - for printers not supported directly by embedded Linux or those needing proprietary manufacturers' drivers) or CUPS (for fully Linux-supported printers only)
  • CD recording; the Optware packages provide cdrtools: common low-level CD recording tools such as cdrecord and mkisofs.
  • Local network sharing of supported scanner models using SANE drivers; these may be accessed from Linux desktop PC's or (through third-party utilities like SaneTwain) even from Windows PC's.
  • Cellular Phone/USB Modem as WAN connection for acm.o driver compartible USB devices
Drivers 3gstick usb devices wireless adapter

The availability of external storage and peripherals makes a greater number of packages, including audio and multimedia, potentially usable from these otherwise-tiny devices.

Drivers 3gstick USB Devices

[edit] Multimedia

Drivers 3gstick USB Devices

There are a number of Entware packages designed to handle audio or to convert multimedia data from one format to another. USB audio hardware is becoming more commonplace due to its use with Voice over IP softphone applications, and the 'video 4 linux' project has done much toward making analogue video capture and webcam devices operate with the Linux desktop. It would appear that, once USB support is available, many packages are available to be tested on the embedded Linux platform.

Getting video back out, however, is no easy task.

One device which may be of interest is a USB hard drive enclosure with a built-in media player, such as the Mediasonic HM2-U2TV or others like it. Install a laptop HDD into this tiny device, connect it to your USB-aware router as network-attached storage and load it with images, audio and video files. Unplug it and connect it to your PAL or NTSC TV monitor as a self-contained media playback device. Note that the media player is deactivated whenever the USB interface is connected.

Another possible combination: a Dreambox DM500 ( and a NAS-capable Linux router on the same network. The DM500's are Linux-based digital TV units (they do not tune analogue signals). Having no built-in USB or storage, these depend on network-attached storage elsewhere on the LAN in order to provide PVR-like capabilities. Pair these with a Linux-based router such as the Asus WL-700GE (which has a built-in 160GB HDD) or any of the USB-capable devices (which interface to USB hard drives) and video can be stored and displayed without relying on access to desktop PC's and without going to the higher-end Dreambox DM7000 series (which offers built-in HDD, USB, keyboard and flash memory support, but at double the price - a hefty premium to pay).

[edit] Multifunction devices

Multifunction printers (a printer and scanner in one unit, resembling a small photocopier) may be supported, depending on model. These may be treated as the individual portions - a printer and a scanner - although even an otherwise-incompatible device will normally allow just the printer portion to be used on a strictly pass-through basis through p910d even if none of the other capabilities are supported.

USB telephone-style handsets may or may not be Linux-compatible, with low-end models being more likely to be recognised as some Linux-compatible combination (typically a standard USB sound card with perhaps a USB human interface device as the keypad). Higher-end devices often are locked to one provider by being tightly-integrated to Windows-specific drivers and/or the Skype softphone application, rendering them useless. For instance, the Linksys CIT200 is useless outside Windows, while the far lower-end Skype SK04 is a relatively-standard USB device which may be worth testing in a Linux environment.

Laptop 'USB docking stations' typically provide some combination of a USB hub, an extra network interface, audio, serial/parallel ports, keyboard and mouse. Their compatibility varies depending on model; it may be necessary to determine which drivers are installed by manufacturer-supplied Windows discs for each of the individual peripherals in these bundled units and check availability of corresponding existing embedded Linux drivers before considering these for use. Some may work, some most certainly don't. Unfortunately, USB to SVGA interfaces in these packages are currently very proprietary and in no way Linux compatible - the one key stumbling block preventing a USB-aware network-storage device such as Linksys' NSLU2 or a USB-aware router from being expanded to be a small but complete self-contained embedded Linux computer system.

[edit] USB drivers

These drivers may be installed to JFFS using ipkg and then loaded (using insmod) from a startup script to enable USB support.

As of dd-wrt v.24-final the Mega version has built-in USB support.

In the web-GUI select: tab: Services -> tab: Services --> section: USB Support

For v.24 versions with built-in USB support, using ipkg will retrieve the ipkg files from the default Openwrt WhiteRussian feed. These drivers may not work correctly with v24 which uses a more recent version of the Linux 2.4 kernel. An alternative is to see the forum post here. An archive is attached in the first post that contains some file system, usb, and usb serial drivers not included in the usb enabled versions of DD-WRT. These drivers need to be copied to JFFS or a USB_storage device and loaded (using insmod) from a startup script to enable these devices.NOTE: Some dd-wrt images have no common filesystems support (ext2/ext3/ntfs/vfat), primilarly images for devices with tiny amount of flash (4MB or less) so you have no ability to mount USB drive natively. If your JFFS allows this, you can store fs modules there otherwise you can use trick Mounting_USB_drive_without_located_onboard_fs_modules if your system has USB support.

File System:

USB Extension:

USB To Serial:

For other versions of DD-WRT load the following modules:

USB base drivers:


Also read USB_storage for more on USB Storage. As of dd-wrt v.24-final the Mega version has built-in USB storage support.

Serial ports:


See - some drivers exist but these are not part of the base 2.4.x distribution. Proper sound-core and kmod-usb-audio support is provided once the newer 2.6 kernel is used. While some OpenWrt versions are beginning to support 2.6 kernels, as of Oct'97 Broadcom wireless still isn't working with the newer kernel.

Printer and multifunction:Also see USB_printer_sharing for more on USB printer support. As of dd-wrt v.24-final the Mega version has built-in USB printer support.


USB modems:

  • One example here Cellular Phone/USB Modem as WAN connection
  • General listing as of 04/04/09 .v24 SP2: 3G / 3.5G about 3G/3.5G UMTS/HSDPA/HSUPA/CDMA2000(EVO)
Retrieved from ''
Coments are closed

Most Viewed Posts

Scroll to top