WP-S1 Proprietary USB Modem #2 Driver Download

I do wish that Apple had embraced USB-C rather than continue with lightening plugs e.g. But my intention with this story is to reflect upon the merits of open and proprietary standards. Driver Description Version Download; All-In-One PC Drivers: USB-to-serial drivers installer package for 32 and 64-bit versions of Windows XP (32-bit only), Vista 7, 8, 8.1 and 10. This package contains four drivers. The first and fourth drivers are for the Opticon cradles. The second driver is for the OPN200x scanners along with many other.

Hold the modem along the side edges and gently insert it into your device’s USB port. On most devices, insert the modem with the label facing up. It should fit easily into the port. Some devices might orient the USB port so the modem label faces down or sideways. Do not force the modem into the port as this might damage both the modem and the. I am still really surprised that there aren’t just some totally generic USB modem drivers for Win7 that work with the phone. I have successfully installed and used them on XP Pro. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks. Windows 7 Home Premium 32bit. Driver Skypephone Amoi Wp-S1.

This tutorial explains how to setup and configure OpenWrt for using a USB 3g/UMTS-modem for WAN connection using the older (and slower) ppp protocol.
Many modern (and most LTE) usb modems provide qmi, mbim, ncm, rndis protocol for connection instead of legacy ppp protocol, they are faster and better, overall recommended. For more information:

• qmi and mbim, see How To Use LTE modem in QMI mode for WAN connection
• ncm, see How To Use LTE modem in NCM mode for WAN connection
• rndis, see How To Use LTE modem in RNDIS mode for WAN connection

You may also want to checkout the multiwan_package package to use this simultaneously with other connections to the internet.

Cellular mobile telephony can be intercepted very easily. Remember this is a wireless connection.

Many mobile ISPs block certain (or most) ports. Port forwarding will probably not work (as the traffic is blocked by the ISP's firewall).

If you've got a Huawei E367 (which will work), or a Huawei E585 (which does not currently work), you may want to read the following tutorial (which includes info on why you may not be able to get the on-board micro-SD card to function):http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=836

If you have the Leadtek FlashOFDM card (Flarion) from T-Mobile in Slovakia and the Asus WL-500g Premium, you may use the image on http://www.accalio.com/index.php?id=301. If you wish to get more information, or another distribution with the driver, please contact Accalio http://www.accalio.com

Some modem sticks provide an usb-ethernet-device (e.g. Huawei “HiLink” - device numbers with 'h', but also other manufacturers like ZTE has such products MF823, MF831, …) In that case you should install usb-modeswitch package and follow usb tethering tutorial. Tethering will in most cases add an additional NAT layer. If you prefer to let OpenWRT care about dialing in, routing, NATting, firewalling or if your provider assigns you an external IPv4 (which is most useful for setups, that need port forwarding), you will most likely want to set (“modeswitch”) your 3g/4g modem to act as a serial device.

Serial device modes: If a dongle in permanently configured for serial mode, it is advised not to install usb-modeswitch onto your router device. Modem sticks are commonly equipped with a flash space containing drivers and software and/or provide a slot for a micro-SD-card. These features (like the 'NO-CD' feature) can be configured in various ways. These configurations may be stored permanently. In that case a modeswitch will behave in an unpredictable way.A modem stick, that was previously configured as a modem will show up as serial devices (typically /dev/ttyUSB0-2). A default setting in combination with modeswitch may additionally show the sd-card reader. See the Troubleshooting section in this document for further information.

Preparations

Required Packages

First install required packages:

• Appropriate host controller interface for your USB hardware (precompiled images will most likely already contain the correct one)
  • kmod-usb-ohci
• Support for serial communication; needed to send control commands to the dongle and receive its responses.
• kmod-usb-serial-option, and
• kmod-usb-acm i.s.o. the last two, depending on dongle/phone hardware.
  • kmod-usb-serial-option is not available for 2.4 kernel, install kmod-usb-serial and put a line equivalent to “usbserial vendor=0x12d1 product=0x1003 maxSize=2048” in /etc/modules.d/60-usb-serial)
• modeswitching tools, if your modem initially presents itself as a storage device - one of the following, depending on your modem:
  • usb-modeswitch (recommended) Automatic mode changing to place the device in USB modem mode.
  • (currently not available anymore) sdparm - utility to send SCSI commands (needed on Ovation MC935D)
• luci-proto-3g for proper support in luci in RC6 and later

Dependencies

If you are doing an offline installation, you might need some of these packages handy

• kmod-usb-core, usually already in the default install
• ppp, dependency of chat, usually already in the default install
• kmod-usb-serial, dependency of kmod-usb-serial-option
• libusbor the 'compatible' library from libusb-1.0, dependency of usb-modeswitch

Installation

First install needed packages:

Now plug your USB Dongle to the USB port and restart the router.

Check dmesg for:

If above lines do not appear in dmesg, but instead you see something like:

then, depending on your modem, you have to switch device mode (described below).

If you can't see usbserial_generic go to usbserial_generic missing in dmesg

switching USB mode

Manual Configuration

The shown configuration replaces the WAN line, so no further changes are needed to the firewall/other configuration. Note that if you also want to use the WAN port, you have to define it as WAN2 in the configuration. If you define the 3g connection as WAN2, you have to do more changes to other parts, like firewall and so on.

Network configuration

Edit your '/etc/config/network' file: (see network 3G section for more details)

Replace 'pincode' with the correct pincode of your SIM card. Note that a disabled pincode on the SIM card is problematic, please enable it.If you are connecting to a phone where the pincode has already been entered, there is no need for this.

Replace 'device' with the correct USB port of your modem. On a phone this might for example be /dev/ttyACM0.

Replace 'apn' with the correct APN of your 3g/umts provider.

Note in case your APN also requires an username/password, you can configure this too, just add to the network configuration file:

Replace 'username' and 'password' with the correct username/password you received from your 3g provider. You can also look for this information (apn, username and password) in the mobile-broadband-provider-info database from the Gnome project.

For some providers, apparently it is necessary to add 'noipdefault' to 'pppd_options'. If logread shows that the connection was established and CHAP authentication was successful, but the connection was immediately dropped after, then try:

If your provider supports PAP authentication only then you need to disable all other protocols via these added options:

Now you have configured the network interface.

Wp-s1 Proprietary Usb Modem #2 Driver Download Windows 10

Chat configuration

Now we need to check if the default chatscript does work with your 3g provider or not.

You can find it here '/etc/chatscripts/3g.chat', it looks like this:

If your modem needs a special AT command, your can add it to this file.You may have to edit the dial number of the ATD command to fit in with your provider's settings (for example “*99#” instead of “*99***11#”).

Establishing connection

Just type on console 'ifup wan'

Now check dmesg logread for successful connect:

That's it, now you should be connected.

If you want an permanent connect from startup, add 'ifup wan' command to '/etc/rc.local' file.

Debugging signal strength issues

For troubleshooting or locating the best position for the USB Dongle, you can use

from the console. This tool will report signal strength, but also network registration and SIM status. If it returns a port-in-use error because your connection is already up, try

where x represents a port number not used by the wan connection itself.

gcom returns the signal quality in RSSI (Received signal strength indication) and in BER (Bit error rate, reported in percent). A higher RSSI value represents a stronger signal - scale is from 0 to 99, where 1 is the lowest detectable signal and 31 a very good signal. Don't expect your signal to go all the way up to 99, though. If BER returns 99 it means not known or not detectable.

If your 3G modem is e.g. a ZTE K3565-Z featuring a LED SSI indicator to show it's status (Not Connected, GPRS, UMTS) you may be mislead to believe, that a strong signal strength of e.g. 17 may be better, while you only get GPRS, but a value of 4 allows for UMTS access. This is owed to the circumstance, that the device may switch over to another cell. The only method to prevent a handover between a GPRS and an UMTS station during the process of optimizing, is to initiate the device to use 'UMTS only' in the first place.

You can also add the AT command

to your chat script to check signal quality.

Command return is “+CSQ: <rssi>,<ber>” and looks like this in logread:

If you have problems establishing a connection and multiple modem devices (/dev/ttyUSB0, /dev/ttyUSB1, …) are present, try all of them. Some may not work at all while others seem to work at first, but will give a NO CARRIER during the connection process.

AICCU interaction

/etc/hotplug.d/iface/30-aiccu starts aiccu when the WAN connection is established. It seems however that, in the case of 3G connections, the start scripts are started just a bit too early and the start of aiccu fails. I have butchered the script a bit:

Note that sixxs really frowns upon quick re-re-restarts of aiccu, it may get your account blocked for unjust use of resources. Be careful with these scripts.

Installing multiple 3G dongles

You can use many usb 3G dongles easily by using an active USB hub.

Prepare for the next steps:We assume you have at least one 3g dongle configured. You will need an active internet connection in order to install modules for 3g support. Check 3gdongle for more information.

1. Connect an active USB hub to the OpenWrt router. You need to assure, that the power supply will deliver sufficent power for all of your 3g dongles. A proper estimation is, that you will need 500+ mA per one 3g dongle. Remember that modem can slightly exceed its declared power consumption in HDSPA+ modes. Be generous and pick USB hub with some power source overhead.

2. Connect all 3g dongles and start.

3. Browse through logread to check if modems are properly recognized and /ttyUSB ports are assigned.

4. Usually a 3g modem has a few “modem ports” - one for connection and others are service types. Exeplum gratum: A Huawei E1750 has three ports. The first in is a communication port and last is a service port. If you only have one modem, it will be recognized as /ttyUSB0, /ttyUSB1 and /ttyUSB2. You need to configure interface using /ttyUSB0 (first one). A Huawei E372 has five ports, but similar to other Huawei devices, the communication port is the first one.

5. You need to configure interfaces. An example of “/etc/config/network” could look like this:

Usually you need to provide an APN name in “option 'apn' 'Name-Of-APN-HERE'”.If your sim card is locked with a PIN, or if your porvider requires to use a username and/or pass, add it accordingly.

6. Check in log read next /ttyUSB[X] ports. In my case I have second modem starting with /ttyUSB3 (previous one use /ttyUSB0 to /ttyUSB2) so second interface looks like this:

7. Remember to add second interface to the zone “wan” in the firewall's config file “/etc/config/firewall” (it may differ in your case):

Look at last line - there is wan2 added.

8. Now you have both interfaces configured and they should work.

9. You can use both interfaces as a failover.

LOADBALANCER / MULTIWAN

: This section needs a complete rewrite to fix spelling and grammar errors.

loadbalncer - https://forum.openwrt.org/viewtopic.php?id=23904

Note: It seems multiwan isn't perfectly suited for 3G modems in terms of stability. Modems don't reconnect automatically by HealthMonitor. Also, after a manual modem restart, multiwan doesn't use the newly reattached interface until it's restarted.

WP-S1 Proprietary USB Modem #2 Driver Download

Configuration files for two 3G modems paired in multiwan:

Network (default route to 0 and peerdns to 0):

Firewall - add second wan zones

Multiwan - Additionally add option 'health_monitor' 'serial' at the beggining to help healthmonitor check for dropped ppp interface (Proposed by Jolouis).

I had issues with auto reconnecting modems so I've modified script for checking if modems are up. This script checks modems separately.I've based this on a great tutorial found at http://eko.one.pl/?p=openwrt-3g#automatycznyrestartpoczenia

Create script:

Create CRON job:

This will ping through two wans: 3g-wan and 3g-wan2 and restarts the interface in case of no replies.Additionally, It will wait 5 seconds and force a multiwan restart as it seems wouldn't recognize the new wan interfaces.Restart of multiwan should take care of this situation.

Additional DNS configuration

Easy Configuration Using Luci Web Interface

Luci has supported 3G configuration. Be sure to have luci and luci-proto-3g installed. If you want to do multiwan configuration, make sure that luci-apps-multiwan is installed and optionally, luci-app-mwan3.

To create a new 3g connection, go to Luci web interface. Navigate to Network ⇒ interfaces. Click on Add new interface button. Give a simple name to the interface, for example 3g and choose UMTS/GPRS/EVDO as its protocol.

Here is basic configuration to get the connection working.

Obtaining IPv6 address

If you want to enable IPv6 on 3G connection, make sure that your dongle supports PDPv6¹⁾ and your 3G provider is providing IPv6 service.

To enable IPv6 negotiation on the PPP link, issue the following command.

Be sure to replace 3g with the correct name of 3G interface.

In addition, be sure to edit file /etc/chatscripts/3g.chat for PDPv6 configuration as currently there is no UCI entry for PDPv6.

You may use the following chatscript for PDPv4v6 configuration. Make sure that your dongle supports PDv4v6²⁾ before attempting to modify the chatscript.

If you are using Luci, be sure to check Enable IPv6 negotiation on the PPP link and optionally Use builtin IPv6-management on the Advanced settings section of the 3G interface configuration page. Also, be sure to modify /etc/chatscripts/3g.chat file for PDPv6 as explained above.

Of course you can use other methods to obtain IPv6 instead of relying on PPP negotiation. See IPv6 for more explanation.

Compile things yourself

If you want to build an own firmware containing support for a UMTS Modem, maybe this BuildHowTo will help you: Wireless router with a 3G dongle and multiwan for failover on Wired, Wireless client (routed) and 3G

Troubleshooting

Howto activate serial mode through web browser on CDC-Ethernet devices

WARNING - this will deactivate WEB-GUI access on these devices!!!You need to know howto submit AT commands to a modem in order to restore the GUI.

Huawei

Browse to http://192.168.1.1/html/switchProjectMode.html with JavaScript enabled browser.

ZTE

Browse to http://192.168.0.1/goform/goform_process?goformId=MODE_SWITCH&switchCmd=FACTORY with JavaScript enabled browser.

Howto restore CDC mode on CDC-Ethernet capable devices

Huawei

AT^U2DIAG=255 or AT+U2DIAG=276 see http://www.3g-modem-wiki.com/page/Huawei+AT-commands

ZTE

Workarounds for specific devices

General information on modeswitching

Modeswitching issues can occur especially on devices, in fallback modes (Huawei).It is advisable to install usbutils

You can look for the usb ids from

in /etc/usb-mode.json, to see what modeswitch actions are being taken.

If you prefer to permantently switch a modem to serial/fallback mode, seehttp://www.3g-modem-wiki.com/page/Huawei+AT-commands and take actions to deactivate the json-based modeswitch for that specific product id. The following section will go into details on how to do this for the ancient E220. The following sections for MA260 explain, how such workarounds have looked like before the introduction of OpenWRT Chaos Calmer.It may in some cases be easier to delete the file /etc/usb-mode.json with a custom modeswitch file, if necessary. A previously configured serial modem, that is unknown to the kernel can be manually associated with it's driver by assigning it the manufacturer and product id as shown by lsusb as follows:e.g. for E220 in fallback mode:

Huawei E220/Chaos Calmer

If you encounter problems with an undetected Huawei E220, you can try the following - this resets the E220 to its factory defaults, so it can again be handled by the new JSON-based modeswitch.This will reenable the CD-ROM Mode.

1. Make the modem work once, by manually telling the kernel to use generic (option) drivers.

2. Shutdown WWAN (necessary only if WWAN was previously configured)

3. Modes of the E220Modem + PC UI

Modem + CD

4. Reboot

usbserial_generic missing in dmesg

If you can't see usbserial_generic in dmesg, try loading the usbserial module (<vid> and <pid> are Vendor and Product ID of your device):

Alternatively, you can also use option GSM driver on your dongle. Option driver is more reliable, as it can distinguish between serial port and storage port.

To automate the process of attaching option serial driver on boot, just edit /etc/rc.local and place

before the exit code

Adding the above to hotplug instead of rc.local:You can easily integrate this into hotplug in the following way - in this example we will use a fictional “3G Dongie HSPA+” Dongle:

Create and edit the file /etc/hotplug.d/usb/22-dongie_hspaplus:

If your modem's switched product id is 0815:9000, the above will work.So for your modem you will have to replace all appearances of the variable DONGIEHSPAPLUS_PRODID and all appearance of “0815” and “9000” in the above example with your matching product's name, vendor and product id.

Check dmesg again for:

Also check kernel USB debug for loaded drivers

¹⁾³⁾

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.

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:

• 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.

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: https://source.android.com/, 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 (https://source.android.com/compatibility) 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: https://developer.android.com/reference/android/speech/RecognitionService, 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: https://privacy.google.com/businesses/gdprprocessorterms/, 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.

10. DISCLAIMER OF WARRANTIES

10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE SDK IS AT YOUR SOLE RISK AND THAT THE SDK IS PROVIDED 'AS IS' AND 'AS AVAILABLE' WITHOUT WARRANTY OF ANY KIND FROM GOOGLE.10.2 YOUR USE OF THE SDK AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SDK IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE.10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

11. LIMITATION OF LIABILITY

11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.

12. Indemnification

Wp-s1 Proprietary Usb Modem #2 Driver Downloads

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.

Wp-s1 Proprietary Usb Modem #2 Driver Download Windows 7

January 16, 2019I have read and agree with the above terms and conditions

Wp-s1 Proprietary Usb Modem #2 Driver Download 64-bit

latest_usb_driver_windows.zip