Review: Verizon Android 3G Mobile Hotspot

Due to some unforeseen travel complications, I had to reschedule my Comcast install. As such, I'm relying on my HTC Droid Incredible and the Verizon 3G Mobile Hotspot feature for a few days.

Point one: DHCP & Verizon-assigned DNS is horrendous -- they make the feature unusable. Use a static IP address and Google or OpenDNS or other known reliable third-party DNS servers. Once I switched over to this configuration, connectivity has been flawless -- zero interruptions.

Point two: Still can't use voice + data at the same time. If you receive an incoming call while using the Mobile Hotspot feature, you will lose data connectivity for the duration of the call, just like using the plain old handset.

Point three: While it is better than some hotel WiFi I've dealt with, this feature does not appear to be a speed demon. With 3/4 bars, from a Chicago suburb, I performed a Speakeasy speedtest against Chicago-based target servers with the following results:

Conclusion: while having some connectivity on my laptop is certainly better than no connectivity, or smartphone-only, I absolutely cannot see multiple users using this as a hotspot simultaneously. USB dongles and ad hoc networks, or MyFi type devices, in my experience, provide much better performance, if you, or your boss, can pony up the cash for them -- plus you are not then forced to choose between voice or data.

SOLVED: 5GHz 802.11n networks not showing up with Dell DW1520 wireless-N adapter

In rebuilding/building out my home office network, I've been adding some wireless-N equipment that finally seems reliable -- the Netgear WNDAP350 and WNDR3700. After poor experiences with N since late 2007, I had purchased a new laptop (Dell Studio) in May with a G-band wifi card only. My more recent, happy experiences with N led me to purchase a replacement mini PCIe 802.11n adapter from Dell - the DW1520.

The adapter arrived yesterday, and I of course eagerly popped open the back of my Windows 7 Ultimate x64 laptop to install it. Everything in place, machine rebooted, and ... it got a great signal from my G-band access points, but not a sign of the N-band APs.

I rebooted the PC, the router and the AP, all to no avail. No sign of the Ns. Did some research online, found problems with previous adapters in the series, but researched the Broadcom component on the DW1520 to find that 5GHz was, in fact, supported. I was stymied.

Hours later, I took another stab at it. In reviewing the driver settings, I found that my Location value was set to Japan, and I had no way of changing it! Recalling the multiple sets of localized drivers on the driver CD provided by Dell, I made the lucky assumption that Windows had found the wrong set of drivers and regional telecom/wireless compliance mismatch was probably interfering with the adapter finding my 5GHz networks.

I uninstalled the network controller and driver via Device Manager, making sure to specify the Windows should delete the driver software to ensure I replaced it with the properly localized binaries. Scanned for hardware changes, specified browsing for the driver, made certain to select the Win7\DRIVER_US folder for searching.

Voila! The wifi adapter reinstalls painlessly, and this time my location is correct:

Now connected to my nearby N-band AP with speeds of up to 300mbps (varies):