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
lmcd - Wednesday, February 17, 2016 - link
I mean to be fair, RemixOS looks like Windows 10 for ARM got Android apps.edeke - Saturday, February 20, 2016 - link
Problem for Android as a OS is open source, everybody works inside (skin etc) time for developers to work with a standard. Some 10-30 main developers together can change everything. Now there is no guidance, they are like chicken waiting for a roaster.tuxRoller - Wednesday, February 17, 2016 - link
Android has excellent tablet APIs, and have had these for awhile. They've even had multi window mode (tiling wm but let's you perform more sophisticated arrangements than just side by side)for a few years hidden behind a debug flag in the buildprop.What you're really, probably, complaining about are the developers not putting the time in to make their apps work well on a variety of form factors.
Speedfriend - Thursday, February 18, 2016 - link
"Android is just a shitty tablet OS."iOS is a shitty tablet OS, with giant icons spread across the page and limited ability to properly organise your desktop or use widgets. Android works far better as a tablet OS.
However, Android has shitty tablet apps while iOS has great tablet apps.
blackcrayon - Thursday, February 18, 2016 - link
Not everyone focuses on the program launcher as much as you do, but yes Android's "desktop" is more capable. But that's a pretty minor advantage. Also, I'm not sure why you don't think you can "use widgets" when they're available by a system wide pull down (even from the lock screen). The fact that iOS has official (i.e. not from a hardware vendor alone) split screen app support makes it a much better tablet OS right now than Android.ESC2000 - Thursday, February 18, 2016 - link
I would hazard a guess that part of the reason you think the home screen is a minor part of the experience of a phone is because you don't use an OS that makes good use of the home screen. Being able to arrange the home screen as I please (scrollable widgets for email, text and whatsapp along, mini icons for app drawer and all other frequently used apps, and shortcuts like double tap for Google play, swipe up for alarm clock) is extremely important to me. I love that I can see everything important on my home screen without opening any apps. I can also answer reply to emails and texts from the home screen. I love that even though I have all those widgets I still have more than enough room for icons for important apps because I'm allowed to shrink the icons, move them closer together and even replace them if I desire.I have one home screen and that's it. I don't need to swipe through pages of icons spaced with way too much wasted screen. I was thinking about trying an iPhone again after four years of android but I was dissuaded because of ios rigid home screen and the lack of an app drawer. ...yes I really chose not to get an iPhone because of what I'm describing in this post. You don't realize how great it is until you try it....although I will concede different people care for different things. But no doubt I'm not the only one who thinks android's treatment of the home screen and launcher is a massive advantage vis a vis ios.
nerd1 - Friday, February 19, 2016 - link
iPad pro is a total joke too. Giant icons on 13" screen. Absolutely terrible file management over multiple apps. Pen support is half baked, side by side multitasking was worse than Galaxy Tab 2.But at least it has quite capable pen (at least for artists)
andreoidb - Wednesday, February 17, 2016 - link
It is and has been available to the public for almost 17 days. That is the February Security patch, I have it and that build number on my pixel c right now and have since February 1st.Brandon Chester - Wednesday, February 17, 2016 - link
The security patch is a completely different thing. The point of mentioning the build number in the intro was to reflect that it probably will be different on release because ours only changed from the original based on the security update that came integrated.andreoidb - Wednesday, February 17, 2016 - link
A google rep in the product forum confirmed the February security update OTA/Build contained fixes to the touchscreen. Additionally, I have it and responsiveness is better. Here is the link:https://productforums.google.com/forum/m/#!topic/n...