Nexus 6 Review: Wi-Fi Done Right

I've been a Droid user for many years.  Started out with the Droid 1 then onto a Droid 2, Droid RAZR Maxx, Droid Ultra, a very short-lived and painful experience with the Droid Turbo, then a Droid Maxx which is essentially a slightly fatter Ultra with more battery.  When my battery's capacity started to run short, I started looking at other phones.  I decided to get a Nexus 6 (unlocked from Amazon) when Google announced that they would roll out Wi-Fi Assistant to all Nexus phones.

Wi-Fi Assistant was originally a Google Fi feature that applies a VPN to open Wi-Fi access points - without user intervention.  In fact, Wi-Fi Assistant is now (once you have the Play Services 9.6 update) capable of securing all open Wi-Fi, even ones where you manually connect.  This is a huge move by Google that will hit the cellular carriers hard because if I'm able to use public Wi-Fi with confidence, and my phone is latching on to open Wi-Fi by itself - why do I need a large data plan?

This all takes Wi-Fi a step closer to being a viable alternative to cellular data, although there are still many issues.  The problem is that managing a Closed SSID network is painful and complex, and Open SSID networks are subject to abuse.  Wi-Fi also suffers from a handoff problem (i.e. it has no handoff method) and it's fairly easy to do a man-in-the-middle attack in coffeeshops - without 802.1X there's no way to know if that "xfinitywifi" hotspot is really Comcast or not.  Wi-Fi Assistant solves that problem by providing a VPN back to Google's servers.

zOMG so fast!

So far I'm very happy with the Nexus 6.  It's a two year old design but it feels quite snappy.  Google's clearly still putting effort into development, and the Android is pure - no Verizon or Motorola/Lenovo weirdness.  It's a bit larger than I'm used to, so I'm glad I didn't get the Nexus 6P, but I have large hands so it works for me.  Wi-Fi in the 5 GHz band using 802.11ac on the Nexus 6 is fast.  It easily maxed out my 75 Mbps DSL connection in a speed test.

For a while I'd been using an iPad in the evening because the screen was much better than my Droid Maxx.  Now the iPad sits forgotten for days at a time, as I find the Nexus 6 screen good enough to handle almost anything.

You're doing it wrong

The ARRL kicked off 2011 with a news item that hopefully is not a harbinger of more retro-tech lameness to come during the new year.  (Hint: It is.)  "Ring in the New Year with Morse Code Ringtones" started off well enough; make your cellphone ring with CQ CQ CQ or some such.  I did this almost two years ago and it's great fun; I even made ringtones with my wife's name, the callsigns of hams in the Bay-Net group, etc.  I got lots of good comments on my ringtones from folks at the 2010 Dayton Hamvention; a few even requested that I email them copies of my MP3 files for their phones.

The ARRL article fails on two fronts; first off it talks about creating Morse Code ringtones like it's a completely new thing (clearly it's not), and secondly it goes into detail about the horribly convoluted process Tom AD1B used to create his tones.  Tom actually used his Ten-Tec rig and a keyer paddle to generate the Morse Code, recorded the audio (article is unspecific on how he did this; my money is on "8-Track Tape Deck"), massaged the audio files in Audacity, and then generated MP3 files.  Talk about using a bazooka to kill a mosquito.

Clever.  And completely unnecessary.  I generated my MP3 files by going to LWCO.net, a website created by Fabian Kurz, DJ1YFK.  Fabian's website (the URL is an acronym for "Learn CW Online") offers a number of useful tools, many of which are based on Fabian's excellent open source "ebook2cw" library.  One of the tools on LCWO is "Convert text to CW".  You type in text.  It generates an MP3 file for download.  You put the file on your phone.  Done.  I can generate a library of unique ringtones for twenty people in the time it takes Tom to record and process one.

And even my method is now somewhat obsolete with the advent of apps for smartphones that convert text to Morse Code on the fly.  MorseRing for Android is available in the Android Market for 99 cents.  It converts Caller ID strings to Morse Code.  The beauty of MorseRing is that I now know who's calling me even if my phone is 25 feet away.  I'm sure there is similar apps for the iPhone, possibly one for Palm, likely not for Blackberry.

Skype Mobile lameness continues in Android

During the past week my wife and I upgraded our mobile phones and made a major shift away from Blackberry to Android.  This ends (for me) an era which began in 1998 when RIM gave me an Inter@ctive Pager (aka the RIM-900) as part of a pre-sales effort to convince Verifone to use a RIM data module in their Omni 3000 handheld credit card terminal. 

I'll have more to say in future posts about why we made this change, but for today I'm focusing on the ongoing lameness that is Skype Mobile.  You'll recall that I wrote last month about how Skype Mobile's privacy features are sorely lacking because it doesn't allow you to block IM from people not in your contact list.  It also doesn't offer you the ability to report abuse via the mobile client. 

During the switch from Blackberry to Android I'd hoped that these limitations would prove to be a limitation of the Blackberry client, but alas the lameness extends to the Android client as well.  Queries to Skype support have proven fruitless; they basically have said "Skype Mobile doesn't filter non-contact IMs.  Thanks for using Skype Mobile."  This needs to get fixed.  I'm going to launch a Twitter campaign against @SkypeMobile to put pressure on them; if you're interested in lending your voice then follow @W6DTW.