After using the HP Chromebook x360 14b with MediaTek K1200 silicon, my first impressions still hold. I’ll share why in my HP Chromebook x360 14b review but the long and short of it is this. The MediaTek K1200 chipset is a solid step forward for ARM laptop performance, which is great. The materials and other internals HP surrounded it with simply holds it back from being a great $449 Chromebook overall.
Inside the HP Chromebook x360 14b
Overall, this is a nice package of parts. The 13.3-inch multi-touch display with 1080p resolution is nice. Brightness is average so this isn’t a Chromebook I’d use outdoors or next to a window. I tried. It didn’t work out that well. The screen is certainly nice enough for watching high resolution YouTube videos or other streaming content. And the B&O tuned speakers under the keyboard are surprisingly loud and have more bass than I would have thought.
The star of the show is the MediaTek K1200, which I’ll get to in a bit from a performance and power-efficiency standpoint. You get either 4 GB of memory or 4 GB of memory. Meaning: That’s it. It’s nice to see a fast NVMe SSD inside with 128 GB of capacity though. For $30, you can double the storage.
Here are the full specifications:
CPU | Octa-core MediaTek K1200, 4 Cortex A-78, 4 Cortex A-55, Clock speed up to 2.6 GHz, fanless |
GPU | 5 cores, Mali-G57 |
Display | 13.3-inch IPS 1920 x 1080 touch display, 16:9 aspect ratio, 250 nits brightness |
Memory | 4 GB memory |
Storage | 128 GB NVMe M.2 storage (256 GB option available) microSD card reader |
Connectivity | 802.11ax (2×2) WiFi 6, Bluetooth 5.2 |
Input | Non-backlit keyboard, multi-touch trackpad, 720p wide view webcam with temporal noise reduction, dual-array microphones, privacy shutter |
Ports | 2 USB Type-C 3.2, 1 USB Type-A, headphone/microphone jack |
Battery | 2-cell battery, 47 WHr capacity, claimed runtime of up to 15 hours |
Weight | 2.95 pounds |
Software | ChromeOS automatic updates through June 2030 |
Surrounding the internals is a nice design, even if it’s not terribly inspiring.
Having used many HP Chromebook x360 models, I can almost tell this one just by looking at it.
I will say it has a nice upgrade or two compared to older ARM-based laptops. You get a USB Type-C port on each side, which is great. There’s also a single USB Type-A port and a microSD card reader, plus you standard mic/headphone jack, power button and volume rocker. Earlier ARM-based Chromebooks and ChromeOS tablets had fewer ports.
I find the keyboard a bit shallow but it’s perfectly serviceable and comfortable to use.
There’s even some extra top-row hardware keys, which I appreciate. I like the “hamburger” menu key so I don’t have to use the trackpad as much. Tapping it opens the Quick Settings area of ChromeOS. The trackpad experience is good, save for an issue based on the chassis design and/or materials HP used. More on that in a bit.
MediaTek K1200 performance and power efficiency
To illustrate the improved performance of MediaTek’s K1200, here are benchmark scores between it and three other ARM-based ChromeOS devices.
While you’d expect the K1200 to show a performance boost thanks to a newer design, I didn’t expect this much of a relative boost.
Test | HP Chromebook 14b MediaTek K1200 | Lenovo Chromebook Duet MediaTek P60T | HP Chromebook X2 11 Snapdragon 7c | Lenovo Duet 5 2nd-gen Snapdragon 7c |
---|---|---|---|---|
Speedometer 1.0 | 140.5 | 48.59 | 90.93 | 93.31 |
Speedometer 2.0 | 81.55 | 29.52 | 51.4 | 55.0 |
JetStream 2 | 99.34 | 37.65 | 58.25 | 61.55 |
Basemark 3.0 | 495.22 | 210.02 | 276.69 | 269.97 |
Octane 2.0 | 31,320 | 10,518 | 22,314 | 24,152 |
Keep in mind that most ARM-based ChromeOS devices still aren’t using the latest and greatest ARM designs. So we’re not talking about Apple M1 or M2 performance here. Instead, think of the HP Chromebook x360 14b offering 10th gen Intel Pentium-like power. It’s unfortunate because more modern ARM designs provide more power and use less energy. Those chips simply haven’t found their way into Chromebooks or ChromeOS tablets yet.
It’s like there’s a two-year lag between the latest and greatest ARM designs and ChromeOS. Remember, the MediaTek K1200 was officially announced as the MT8195 back in November of 2020. It’s taken this long to get the chip inside Chromebooks.
Still, I find the MediaTek K1200 performance to be quite good for my own day to day tasks and I think most typical Chromebooks users will too.
In fact, after using the HP Chromebook x360 14b full time for several weeks, I didn’t feel like the processor limited me much at all. The only time I wanted a little more “oomph” was doing some development work with JavaScript and NodeJS in Linux. But even then, I was still productive; just a little slower when doing certain things that hit the processor heavily.
A good summary take is this. If you’re worried about performance for daily browsing and Android apps, even Android games, don’t be.
The chipset inside the HP Chromebook x360 14b isn’t going to let you down. No, you’re not getting what I’d call premium performance but you’re not paying a premium price either. And you’re getting a fanless Chromebook with excellent battery life.
On that front, HP says you’ll get “all day battery life”, or about 15 hours, from this Chromebook. And this is one of the rare times a manufacturer’s battery life claim rings more fact than fiction.
I can use the x360 14b for 10 hours and still have some gas in the tank.
One night I decided not to recharge it and I worked for 1.5 hours in the morning before the battery ran out of juice. This is highly dependent on your use case, of course. For my day to day activities though, I can easily get through a full day and then some. Having a CPU/GPU combination that sips, instead of guzzles, power helps here.
Should you buy the HP Chromebook x360 14b?
After touting the positive processing power of the MediaTek K1200, you’d think I’d be recommending this Chromebook. But I can’t at full price nor if certain aspects are important to you. And these have nothing to do with MediaTek. It’s where HP’s choices bring the let-downs.
The 720p webcam for example, isn’t even what I’d call average. It’s fine for occasion use with family or friends, although they may disagree. Clarity just isn’t there, nor is speed, so when you move the camera can’t really show that motion without blurriness. You also need really good lighting conditions.
While the device design is nice, the keyboard chassis is flimsy. I can see that on a super-thin detachable ChromeOS keyboard but that’s not acceptable on a laptop. At least not to me.
The chassis is fine on a perfectly flat surface. Use this laptop on your… you know, lap… and your palms can easily press down hard enough to enable a trackpad click. Even when flipping the 360-degree display for tablet mode makes that trackpad click. That’s disappointing.
And it’s a no-go for me, personally. I like to use my devices in any situation or scenario. The flimsy chassis holds me back from doing that.
I also wish there was a model with 8 GB of memory because I think any Chromebook is better suited with 8 compared to 4. I wouldn’t say the 4 GB of RAM lets down the device. However, it wouldn’t hurt. And more Chromebooks, even entry-level models, are including or giving the option of 8 GB of memory. More are coming with backlit keyboards too while my review unit doesn’t have that option. You’ll pay $30 extra for that.
In summary, if you don’t care much about the webcam and you’re going to be using this device primarily on a desk or table, then you’ll be happy. If not, I think there are better options in the same price range although they may not have the same battery life. Look to Lenovo’s slightly more expensive but often on sale Chromebook Flex series, for example, or spend a little extra on the more powerful Acer Chromebook Vero 514.
Honestly, I could get over the poor camera on the HP Chromebook x360 14b by adding a better external one. However, I have a hard time recommending a Chromebook with such a flimsy chassis for most people, no matter how much of a champ the MediaTek K1200 is.
4 Comments
Yes, any Chromebook should have a minimum of 8 GB of Ram. The operating system alone uses between 6 to 7 GB. I’ve been using Chromebooks since 2013 and bought quite a few of them, including the Google Chrombook 2 in 2015. Even that one had 8 GB of Ram. It was a beast though. It did however had its hardware problems after only one year of use.
A few things.
1. MediaTek doesn’t need to use “the latest and greatest ARM designs.” The Cortex-X1 was 3 years ago. There is nothing preventing them from making a laptop and tablet SOC with 4 Cortex-X1 cores plus “whatever” for the efficiency cores. They are now making a midrange mobile chip, the Dimensity 7200, on TSMC 4. So they could use that, or even TSMC 5 to save even more money. They just won’t. Google killing the 2022 Pixelbook represented the last hope for anyone to take ChromeOS on ARM seriously, and remember this accompanied their abandoning the excellent Chromebit idea back in 2014.
2. Were Google serious about this, they could work with Samsung or Intel to design SOCs specifically for ChromeOS. Intel, for example, has this architecture they are pushing called “tiles” where each SOC component is its own “tile”: a “compute tile” for the CPU, a “graphics tile” for the GPU, a “controller tile” for Thunderbolt and other I/O and controllers etc. Of course, Google could have a Tensor for ML/AI and a Titan tile for security. But why stop there? Emulate Apple and have a “RAM tile.” And go a bit further? An “OS tile”, maybe 8 GB or 16 GB of flash storage that would have the main parts of ChromeOS itself. (The regular 32-64 GB eMMC or 128-256 GB SSD storage that contains the apps and data can be joined to it with LVM.)
But we get stuff like this – an ARM PC that performs on the level of a 10th gen Pentium with 4 GB of RAM and costs $450, or $120 more than AMD Mendocino Windows machines that have much better performance and similar battery life https://liliputing.com/hp-launches-amd-mendocino-powered-laptops-for-330-and-up/ – precisely because Google isn’t serious.
The Cortex-X1 is built with Cortex-A78 cores for performance with less emphasis on power efficiency. And the MediaTek K1200 uses A78 cores plus some efficiency cores. So I’d rather have the K1200 in lieu of the X1 in this case, gaining a balance of performance and power efficiency. But I get your point. I have no idea why ARM-based ChromeOS boards lag behind the more modern designs.
The Snapdragon 8cx Gen 3 has 4 Cortex-X1 performance cores and 4 Cortex-A78 efficiency cores made on a 5nm process. And it has been available since 2021. Last year’s Lenovo Thinkpad X13s used it, as did the Huawei MateBook E Go. It had a better single core Geekbench score than the HP x360c 14 with a 10th gen Intel Core i3. And a better multicore than the Intel Core i5-1130G7.
https://www.notebookcheck.net/Snapdragon-8cx-Gen-3-launched-First-5-nm-Windows-PC-SoC-with-four-Cortex-X1-cores-at-3-GHz-6-nm-Snapdragon-7c-Gen-3-announced-too.582290.0.html
The 8cx Gen 3 can’t be used on ChromeOS because the 8c line is exclusive to Windows on ARM. But MediaTek is free to emulate that design or do something similar but more traditional like 4 Cortex-X1/4 Cortex-A55 that would have given the same single core and a lower (but still better than 10th gen Core i5) multicore. Instead, their Kompanio 1200 and 1380 have the same 4 Cortex A-78/4 Cortex-A55 Snapdragon 7c+ Gen 3. ChromeOS OEMs can use the 7c+ Gen 3 – it has 5G where the MediaTek chips don’t even have 4G, plus the GPU is WAY better – but won’t because the Snapdragon 7c Gen 2 and Gen 1 Chromebooks and tablets didn’t sell.
MediaTek is content with simply offering a (slightly) cheaper alternative to the 7c line. They aren’t making an 8c line equivalent at all. But, you can’t blame MediaTek really. In fact, in retrospect I was being WAY too hard on them. The root issue is that the ARM PC market is extremely tiny. According to Counterpoint Research, Apple had 90% of the ARM PC sales last year. Meaning other 10% was split between Windows on ARM, ChromeOS plus niche stuff like the Ubuntu on ARM mini PCs that I have seen. And as Apple only sold 26 million PCs last year, that 10% wasn’t very many.
Windows on ARM is Qualcomm exclusive, meaning that Qualcomm is guaranteed at least SOME revenue in return for the expense of designing and manufacturing ARM PC SOCs with the latest tech and process. Were MediaTek to do the same for Chromebooks that cost $1000 like the Thinkpad X13s, would they even sell enough to recover the investment? Unlikely. People would get the Intel Core i5 Chromebooks that cost $300 less.
The real solution, then, is for Google to once again allow smartphone and other mobile chips to be used on Chromebooks like they were until 2016. That is the only way to get the best performance with the latest cores, GPUs and processes. It is also the only way to get really cheap devices like the Chromebit again … ChromeOS running on Android TV box hardware.