This article is part of a 30-day Pixel C Challenge by Chip Colandreo. Read all the articles from this series here. Pixel C Challenge.
Last week, I took a leap on Leap Day and shelved my Chromebook Pixel in favor of Google’s new Android tablet-cum-laptop, the Pixel C. I promised to use no other laptop/desktop computer for 30 days as I went about my usual business as a magazine publisher. I think I’m going to make it. In fact, I think I’m going to enjoy it. I’m as surprised as you.
That’s not to say the Pixel C is without its flaws. Early reviews of the device could talk about little else, and indeed, going exclusive with the Pixel C has brought its flaws front-and-center into my life. There are many. I’ll talk about some below and in future posts, but I want to make sure we don’t all lose sight of an important point: This experiment is proving to be fun. The fact that it has, so far, been more fun than infuriating says a lot.
The biggest Pixel C annoyance this week hasn’t been the lack of multi-window capability, it’s been the absence of active spellcheck in a few mission-critical spots. I’m talking about the red line which appears under misspelled text as you type. The biggest culprit is Google’s evolved email app, Inbox. Inside the app, active spellcheck works just about everywhere except where I need it the most: the compose window for new messages. I write for a living, so I take all my written communication very seriously, especially the stuff that goes out (usually by email) to colleagues and clients. I’m also a really, REALLY bad speller. I’ve taken to composing emails in another app when I can, and then copy/pasting the text into Inbox. I’ve also started to pay comically close attention to what I type. Maybe it’s not a bad thing.
I’ve seen the same issue pop up in Google+; an obviously misspelled word is staring me in the face, but the OS spellchecker couldn’t care less. Because it’s happening in multiple apps, I have to assume this is an Android bug. The problem exists on my Nexus 5X, too.
Death, taxes, and printer stupidity
I experienced a moment of panic when I realized this 30-day Pixel C experiment was right in the heart of American tax season. I promised myself I would prepare my taxes early this year, but I wasn’t sure the Pixel C was up for the job. I’m not a W-2 employee, so my tax return is more complicated than most. Preparing it requires a lot of research and reference of my business spending during the year. That means a lot of multitasking. Using Alt-Tab on the physical keyboard, I was able to jump between the TurboTax app and my various documents without too much trouble. Could I have done it all a bit faster on my Chromebook? Probably, but I never felt crippled on the C.
That is until I tried to print a handful of reports for my accountant. Printing is a notorious weakness of Chrome OS, so the fact that I was able to print files directly from the Android-powered Pixel C should be a plus, not a complaint. But, as with most printer experiences, the whole thing was a mess. To accomplish a variety of tasks, I’d purchased a USB Type-C adapter made by Satechi that includes Type-A USB ports (more on that adapter and my Pixel C app/homescreen setup in the next post). It took several tries as I plugged/unplugged the printer cable into the adapter, but the OS eventually recognized my printer and prompted me to install the HP printer plugin from the Play Store. I did, and everything seemed fine, but all I could print were blank pages. After about 45 minutes of troubleshooting, I was finally able to print the Google Docs files, but only after selecting “Draft” in the quality settings. Weird. As advertised, the printouts looked like crap, but they did the job. It’s impossible to know if the Pixel C, the adapter, Android, or my printer were causing all the trouble. They’re all likely candidates, though the HP looks most guilty.
At the end of the day, though, I was able to do my taxes entirely on the Pixel C. That’s an accomplishment. Even in previous tax seasons with my Chromebook, I had to fall back to my wife’s iMac to print out my reports. So, this is progress… I guess.
Any questions or requests for the next post? Sound off in the comments below. Thanks for all the great feedback on this series so far!