Final Words

After taking in this new information, I suppose that the final question is whether or not my original verdict about the Pixel C still stands. That's a complicated question to answer, as the update from Google has addressed many, but not all of the issues I experienced with the original. I suppose it's worth doing a recap of what has and hasn't changed before deciding if this changes things for the Pixel C.

The most significant improvement with the updated firmware from Google is the fix for broken touch input. I really cannot overstate just how broken touch is on the Pixel C with its original shipping firmware, and the updated version feels like a completely different device. It's honestly like moving from a resistive touch display to a modern capacitive touch display, and even then, one could argue that resistive touch displays only had some of the problems that the Pixel C initially had. I think it's safe to say that this issue with the Pixel C is completely resolved, and that's a huge step toward making it a tablet that is worthy of commanding its $500 price.

The Pixel C drops fewer frames now than on the original firmware

On top of the fixes to touch input, the new software build has addressed a number of problems relating to performance and stability. I'm no longer experiencing frequent app and OS crashes, and in general there's far fewer stutters and slowdowns throughout the UI. Unfortunately, things aren't perfect. I still can't run our GPU battery test, which is really disappointing for Tegra X1's mobile debut. PCMark's battery test doesn't work for me either, even with the public version from Google Play. The test runs for some period of time, but eventually crashes, and I simply can't keep running it in the hopes that one run will eventually make it through. There are also a lot of applications that are just janky, including Google's Calendar app, and of course the eternally problematic Google Play and Google Chrome.

Chrome in particular is really bad regarding responsiveness and latency, and as far as web browsing goes it honestly feels like going back to something like an iPad 2 after the past five years of iOS updates have taken their toll on its responsiveness and performance. I have a feeling that Google is well aware of Chrome's problems, and I'm hopeful that they're something we'll see addressed in the near future, but for now you're really not getting the web browsing experience that a $500 device should provide.

As far as connectivity goes, I haven't seen improvements to the problems I experienced, which is disappointing. While I never had issues keeping connected with my home WiFi, the speeds and reception haven't been very good. I'm unable to maintain a signal at any appreciable distance, even when other smaller devices keep connected. Google tells me that poor antenna performance on 2.4GHz networks is a known issue, but 2.4GHz should be used as a fallback for when 5GHz can't provide sufficient range so that defeats the purpose entirely. Both Josh and I have also run into situations where the link rate drops below 400Mbps even when right beside the router, which is less than half of what it should be for a 2x2 802.11ac device.

In the end, Google's fixes to the Pixel C's software have done a lot to address the issues I noted in the original review. Its gone from being a tablet that I could not possibly recommend to anyone, to potentially being the best Android tablet you can buy. Unfortunately that's not a high bar to clear, but it's still a great improvement over the Pixel C with its original firmware. I still think I would forgo the keyboard, as Android just doesn't work well with it, and there aren't nearly enough tablet-focused applications to use it with to justify the additional cost.

I'm still reluctant to recommend high priced Android tablets due to the application situation, along with continued issues relating to input latency, multitasking, and gestures. However, if you really need something running Android then the Pixel C is an obvious option to consider. At the very least, the Pixel C is greatly improved with its new firmware. Once that happens I'll feel comfortable recommending the Pixel C provided you're okay with Android's general lack of tablet apps, and that's something that I certainly couldn't have said before.

Software Improvements
Comments Locked

67 Comments

View All Comments

  • ESC2000 - Thursday, February 18, 2016 - link

    You must be new here:p. (Although in fairness I think the reporting in this article is not biased...but if you want to see annoying apple bias keep surfing this site)
  • Nintendo Maniac 64 - Wednesday, February 17, 2016 - link

    Just yesterday there was an article lamenting the lack of 16:10 displays.

    Yet here we are with a 10:7 device...

    (yes I realize said article was talking about monitor-sized displays!)
  • a2x - Wednesday, February 17, 2016 - link

    For any Pixel C users reading this: There's a custom kernel on XDA which includes Nvidia's reference WiFi driver. As far as I can tell, it has basically fixed the WiFi issue. You can't miss it, it's the only custom kernel for the Pixel C available on XDA.
  • tuxRoller - Wednesday, February 17, 2016 - link

    Regarding multitouch zoom, try Firefox. I just verified that it tracks very closely to ideal. Far better than chrome.
  • johnny_boy - Wednesday, February 17, 2016 - link

    Been using Firefox for Android for ages because of how good it is and how bad Chrome is. I also tested the pinch to zoom when reading the article oin my Nexus 9 on Firefox and it works flawlessly.
  • tuxRoller - Thursday, February 18, 2016 - link

    Same here.
    I'm really not sure why more people don't use it on Android.
  • funkdancer - Thursday, February 18, 2016 - link

    After reading the comments on Firefox here I've set it up on my Samsung 8" S2 Tab, and it's pretty flawless. I must admit I have no idea where the reviewer is coming from about Android tablets; mine is ultra responsive, my son's previous gen ipad Air is an annoying POS in comparison. So many things don't work properly on that. Pinch zooming in Firefox though, bloody awesome. So fast also. Thanks guys.
  • tuxRoller - Thursday, February 18, 2016 - link

    Good to hear:)
  • andy o - Wednesday, February 17, 2016 - link

    Brandon, could you quickly check if it now supports bluetooth hands-free profile, so you can make calls over bluetooth with a headset? It does not currently have that ability. See this link for more https://productforums.google.com/forum/#!topic/nex...
  • Brandon Chester - Wednesday, February 17, 2016 - link

    I just tried to do a Skype call with my MBR10RBT and Plantronics BBP and neither even fed the audio to the headset even when I explicitly selected Bluetooth in Skype. The person on the other end did say that the quality of my voice got better when I switched the Bluetooth setting OFF and used the built in setting, so I don't know exactly what was going on there.

    In any case it seems like hands free is still not working, and there's no phone audio profile in the settings app like there is on the Nexus 5X. That's a pretty major omission that I never thought to check for because I tend to not use Bluetooth headphones on Google devices due to erratic behavior and generally poor audio quality.

Log in

Don't have an account? Sign up now