Throughout 2016 I carried a Nexus 5 mobile phone. So did my wife. Hers is the red one. She loves it.
My Nexus 5 suffered a crack in the display the very week that I bought it. In fact, that happened the very day that the screen protector was to arrive from Amazon. In frustration, I merely applied the tempered glass screen protector and kept using the phone for a year!
Over that time, although the phone worked perfectly, the crack grew. By the end of the year it was something of an embarrassment, so I broke down and bought a Pixel from Google.
Some have heard me rant that the move from Nexus to Pixel was disappointing. I maintain that the Nexus phones were an outstanding value, whereas the Pixel, while a fine instrument, is just another costly device.
My experience with the Pixel has been great. It’s a big step up in performance. Nougat is nice. I really like the fingerprint unlock feature. Battery life is exemplary, at least in my use case. USB C fast-charging is ok, although I do miss wireless charging.
One of the things I liked about the Nexus 5 on T-Mobile was that I enjoyed HDVoice calling to the few people I call most often. They are also T-Mobile customers, with suitably capable handsets.
This morning, for the very first time, I noticed that the Pixel indicates when it’s connected in HDVoice. I’m not sure if this indication is a new thing, or I simply never noted previously.
There aren’t too many people who get excited about HDVoice. I still do. It’ll be great we can pass HDVoice between carriers. Some say that’s happening now, but I see no evidence of it.
Last month we made our annual trek to the Great White North. While making plans an associate, who is also a T-Mobile customer, recommended that I call T-Mobile and make sure that we had the correct plan. Failure to do so would result in us incurring the usual roaming charges for platinum-plated voice and data service while travelling.
On the very eve of our departure I remembered to call T-Mobile and make the change to the account. In fact, I called from the airport (IAH) while we were awaiting the departure of our initial flight to Toronto.
Of course, I called the from my mobile phone. The automated system advised that there would be some on-hold time, and I could opt to have them call me back, which I did. The callback took about ten minutes.
On occasion I can be impulsive. This combined with the fact that my two-year Nexus 4 has been troublesome of late, left me open to suggestion. When Dave Michels offered an invitation to order a OnePlus One I jumped at the opportunity.
I ordered the OnePlus One largely without investigated it’s details. That’s unusual for me, even in an impulsive moment. The Nexus 4 has been behaving like a two-year-old…pitching fits, and generally not doing what it should. There have been numerous times when it would spontaneously reboot. Other times a call would come it, but it would not ring. If I was lucky I’d see the screen light up. Then yet other times I’d answer a call and there’d be no audio at all. That situation would persist until it was rebooted.
The One+ One seems like a suitable replacement. It would run on T-Mobile’s HSPA+ and LTE networks. It wasn’t as large a Nexus 6. And at $349 for the 64 GB version stipulated in the invitation, it was priced right.