Last month I published my review of the Pixel C. While I thought it was a very interesting tablet, in the end I was unable to give it any sort of recommendation due to the severe software bugs that were present. To me, this was quite surprising, as Google has a relatively good track record when it comes to the software on the Nexus devices. During the review process I reached out to Google to voice my concerns about the issues. What both concerns me and gives me hope for the Pixel C is that Google was readily aware of most of the problems I brought up. It concerns me because I think the appropriate decision would have been to delay its release, but it gives me hope that these issues will be fixed. 

During my discussions with Google, I was offered the chance to test a new unit that would run a new unreleased build containing fixes that Google planned to release to the public in the future. Given the fact that the Pixel C has solid hardware that's only let down by buggy software, the chance to see Google's improvements before they are officially released presented a great opportunity to revisit the Pixel C and determine if Google's upcoming changes can change my original verdict about the device. It seems that instead of releasing a large patch, Google has instead included these fixes with their February security bundle for the Pixel C. With it, the build number has changed from MXB48J to MXB48T, and we're looking at a slightly newer version of the Linux kernel.

Before getting into my testing and experiences with this updated Pixel C, it's worth going over the major issues that I identified during my initial review. By far the most significant problem was the dysfunctional touch input. Taps wouldn't register, swipes wouldn't register or would register as taps, and in general the touch screen was just not usable. This is something that Google was aware of, and has claimed to address in this new firmware. The second big issue was the stability and performance of the software. I encounted so many app crashes and entire OS crashes that I ended up losing a page of the review that I was writing on the Pixel C, and I was forced to abandon any attempts to do so due to the high likelyhood of it occurring again. 

While the app and OS crashes seemed to happen at random, there were two very important applications that consistently had problems. The first was PCMark, and the second was our build of GFXBench with an infinite battery test. PCMark consistently crashed at some point during its battery test, leading me to abandon my attempts to get a final result after having the test crash several times. GFXBench presented an issue where the detection of charging would cause the test to stop. I suspected that this related to the inductive charging used for the keyboard, but I couldn't confirm it.

The purpose of this article is to take a look at the new Pixel C unit provided by Google, and compare it to the one sent for the original review with the launch firmware. The main area of focus will be Google's work to fix the performance, touch input, and connectivity problems, along with some comparions that we rarely get to do due to the nature of single device sourcing. After looking at the areas where Google has made improvements, along with the areas where work is still needed, I've be able to reevaluate my original verdict on the Pixel C, and hopefully the changes will be enough to make it a tablet that is worth recommending.

Display Comparison
Comments Locked


View All Comments

  • neothe0ne - Wednesday, February 17, 2016 - link

    Have you tried the Sony Xperia Z4 Tablet? I was under the impression that was the best large-ish Android tablet that money could buy.
  • dan82 - Thursday, February 18, 2016 - link

    I haven't. It does sound pretty nice on paper but my main issue with it would be that it's not a Nexus, so it's late with software updates. Sony is better than others of course, but they are still behind.
  • tuxRoller - Thursday, February 18, 2016 - link

    The issue is with chrome not the tablet. Try firefox. I can verify that it doesn't have any of the issues mentioned in the article that chrome had.
    I do have one issue with the on-screen keyboard that pops up, afaict, randomly where I'll be gesture typing and I start a new word and it registers as a series of taps (this picking up letters along the way rather than waiting till I finish the gesture to determine the word) rather than a single touch trail.
  • Klug4Pres - Thursday, February 18, 2016 - link

    Yes, I feel this article puts too much emphasis on shortcomings in the Chrome browser, which after all is merely just the default shipping browser. Nobody worried too much about Internet Explorer from Windows 3.1 onwards.
  • R. Hunt - Wednesday, February 17, 2016 - link

    OLED and expandable storage keep me buying Samsung tablets. The best thing for me about the Pixel C is that, hopefully, it will set a new standard to follow in regards to the aspect ratio.
  • djayjp - Wednesday, February 17, 2016 - link

    I don't see the problem with the Chrome pinch to zoom.
  • Brandon Chester - Wednesday, February 17, 2016 - link

    The position of my fingers relative to whatever content I originally placed them on is completely different after zooming. If you put your fingers on two UI elements and pinch your fingers end up being far away from those same objects, which means it's not tracking properly. On top of that, the animation is pretty janky in several cases.
  • Pissedoffyouth - Wednesday, February 17, 2016 - link

    The link to original review is wrong
  • Qbancelli - Wednesday, February 17, 2016 - link

    This reviewer is obviously a Apple fan.
  • The Garden Variety - Wednesday, February 17, 2016 - link

    OOOH BOOOM! HEADSHOT! TEABAG IN PROGRESS! Qbancelli, I stand at attention and offer you a traditional military salute, for you have brought the pain, and perhaps a little bit of the funk, to the shores of Anandtech and sent the anti-American Apple Death Squads scurrying back to Nazi Germany. USA! USA! USA!

Log in

Don't have an account? Sign up now