Revisiting The Google Pixel C - Better, But Not There Yet
by Brandon Chester on February 17, 2016 8:01 AM ESTFinal 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.
Facebook
Twitter
RSS
67 Comments
View All Comments
Brandon Chester - Wednesday, February 17, 2016 - link
That's good to know. I received contradictory information from Google, but that source looks legitimate. Thank you for that.andreoidb - Thursday, February 18, 2016 - link
No problem. Though for me the wifi issue is terrible, I get no range and the speeds are consistently worse by a large number then my other devices. Makes using this to consume content almost impossible unless I'm near my router. That rep said the have yet to fix the wifi issue yet. I think they just updated some binary blobs in the February OTA because nothing much is in commit history besides the security fixes.R.M.P. - Wednesday, February 17, 2016 - link
I've felt from the start that Pixel C was something rushed out the door to have a "2-in-1" answer to the iPad Pro and the Surface Pro. It's an unfortunate inevitability. To avoid all the unhelpful confusion it's caused, I just wished they'd called it something like "Nexus Pro" instead of Pixel C. While Android has earned its place by attracting developers in droves, its best place is on smartphones. Like iOS and W10, it's too bloated tied to the world of native apps. In an ideal world, Chrome OS would have an equal complement of Web app developers. Then Google would have a PC product that no one else could even come close to competing with.andychow - Wednesday, February 17, 2016 - link
I would buy this device in two seconds if it came with Chrome OS. Give me chrome, native SSH client, a really good screen and a great battery, then shut up and take my money!jabber - Wednesday, February 17, 2016 - link
Give me a phone with ChromeOS on it too!mystilleef - Wednesday, February 17, 2016 - link
Brandon, can you do a YouTube video comparing the input latency and lag on the iPad vs the Pixel C. Cos, I just couldn't see much of any lag or latency in the videos you posted especially when you pinched and zoomed on the Pixel C. Or I'm I missing something?tuxRoller - Thursday, February 18, 2016 - link
You really can't see that the objects under his fingers before he starts moving them are different than the objects under his fingers when his fingers are actually moving? All OSs have some input latency, but Android has the most of any of the major OSs....and its not something that has really ever gotten better.Unfortunately I'm not sure it's something that they'll fix because the OS is "good enough" for their purposes.
BTW, and this really shouldn't matter, but I have only ever bought Android, specifically Nexus/pixel devices, and the input latency is just a travesty and has always been my biggest source of annoyance. IMHO, I think some of the problems are due to Android's absurd HAL, and, in general, their reluctance to use the much more mature GPL Linux userspace libraries. Audioflinger is just dreadful at latency, even today. A developer at collobora ported PulseAudio to Android a few years ago and demonstrated how much less latency it introduced to the stack relative to audioflinger (a bit less than 20ms total, which is high, but much, much less than audioflinger on the device, and could easily have been improved).
dan82 - Wednesday, February 17, 2016 - link
I've been using the new firmware for a 2 weeks as well and think the touch input has been only partially fixed. Things are still somewhat broken if the device is plugged in to charge. One finger is usually ok, but using two fingers (e.g. to pinch-to-zoom) and one of the fingers won't be tracked correctly. While not charging everything is ok and as the tablet luckily has really great battery life, this isn't too much of an issue.The keyboard also got much better. The new system version comes with an updated keyboard firmware which improves bluetooth connectivity a lot. The keyboard is no longer randomly disconnecting (and repeating keystrokes). I don't use the keyboard a lot to type, but it is pretty nice as a stand and cover. The magnetic mechanism is still fun to use.
I also think the Pixel C is currently the best Android tablet. It does get some things wrong that other Android tablets have no issue with, but those are minor:
- Wifi often disconnects while sleeping (this might of course explain the amazing battery life)
- No GPS or NFC
One more grip I have with it is long-term value. Ancient devices like the iPad 2 (2011, around of the time of the Motorola Xoom) and Surface Pro (2013) are still receiving system updates, so they remain current until today. Google promises updates for only 2 years. Of course, an Android system update is somewhat less important as a lot of apps get updated through the Play Store (e.g. Chrome), but you are missing out on some new features (like the new permissions of Android 6.0 that the Nexus 10 didn't get). In my view, that makes it difficult to recommend high priced Android devices, even when the hardware is totally worth it like in this case.
Brandon Chester - Wednesday, February 17, 2016 - link
This fix has not gone out to the public yet. The February security patch didn't include any fixes for touch input or performance. It was only 14MB.dan82 - Wednesday, February 17, 2016 - link
I installed the factory image MXB48T. The touch accuracy is night and day compared to before. A touch firmware can easily be fixed in 14 MB :-)A good way to try this is using the Markers app (https://play.google.com/store/apps/details?id=org.... Try drawing with a bunch of fingers at the same time. With the old version, fingers would frequently get dropped (the line has gaps). The reason is that Android thinks a finger got temporarily lifted of the device. With MXB48T, things are fine, as long as you are not charging the tablet. I'm happy to record a video.