I really like this Pixelbook

[tbayrgs]

Google needs to stop thinking they are Apple and charging as such. Heck, I don't even think Microsoft charges as much as Google does for some of its surfaces and you can do way more with a surface.

The hardware itself is really nice but you're right concerning functionality. Chrome OS just doesn't stack up fully to Mac OS, Windows, or even iOS. Yes, I'm aware of some of the advantages available on a Chromebook vs. iOS but the overwhelming majority of people aren't going to touch Linux and Android apps still just feel like tacked on afterthoughts in so many instances. The entire experience just feels disjointed. Lack of any sort of biometrics also makes it less user friendly--just having to manually type my 1Password master password so damn often is driving me nuts.

There is a lot I like about the Pixelbook but those primarily surround the hardware itself (terrific keyboard, great display once you look past the huge bezels, very nice trackpad, super light device). I'm just not sold on Chrome OS yet. I'm keeping my Pixelbook but it's going to be primarily a family device (one big upside of Chrome OS is how flexible it is for multiple users). I'm going back to an iPP 12.9 (found insanely good deal) for most of my everyday work, with my iMac for my full desktop needs.

 

[sracer]

The hardware itself is really nice but you're right concerning functionality. Chrome OS just doesn't stack up fully to Mac OS, Windows, or even iOS. Yes, I'm aware of some of the advantages available on a Chromebook vs. iOS but the overwhelming majority of people aren't going to touch Linux and Android apps still just feel like tacked on afterthoughts in so many instances. The entire experience just feels disjointed. Lack of any sort of biometrics also makes it less user friendly--just having to manually type my 1Password master password so damn often is driving me nuts.

As I mentioned earlier, since Chrome OS 71 or so, Google has broken things within the Android and Linux app support. This was a significant step backward. Even with OS 74 beta, those things are still broken.

There is a lot I like about the Pixelbook but those primarily surround the hardware itself (terrific keyboard, great display once you look past the huge bezels, very nice trackpad, super light device). I'm just not sold on Chrome OS yet. I'm keeping my Pixelbook but it's going to be primarily a family device (one big upside of Chrome OS is how flexible it is for multiple users). I'm going back to an iPP 12.9 (found insanely good deal) for most of my everyday work, with my iMac for my full desktop needs.

I have found my Pixelbook to be far more useful as a 2-in-1 than my 12.9 iPad Pro. Support for trackpads, mice, USB peripherals, extended displays, fully accessible file system, etc. all help to make the PB more useful... Even with it being temporarily hobbled by issues with the Linux container and CrossOver.

But having said that, I choose my 2017 Macbook Air over both PB and iPP for productivity.

I'm with you on the iMac... it is my full desktop too.

 

[slitherjef]

Just an update, mine is still in use, mostly just a larger screen for watching YouTube

But I've noticed for a while actually that especially in full screen I'll be watching a vid and the vid will just stutter or pause about 3 times in a row, no problems with the audio when the video studders. Don't really seem to matter what resolution the video is.

Also noticed chrome has started to crash or "not shut down properly" and will need to be restored after shutting down for a bit and turning it back on.

Just a few moments ago it just crashed or hung for almost a minute while watching a video. Nothing responded. It finally came back up but never seen it do this before

Kinda been having these issues since the latest update

 

[sracer]

Chrome OS 77 seems to be improving the stability to where it was at version 69. I haven't gone back to using Linux apps though because it is still in beta and squirrelly as all get out.

OFFLINE USAGE TIP

Last week I needed to attend a meeting where I wouldn't have internet access. It was the first time using my Pixelbook in offline mode so I knew I had to take some preparatory steps. I took a few of the steps that I knew would be needed and so I thought I was good to go. Nope. There was one vital step missing. After that meeting, I did a bit more research and made another adjustment that then turned out to be what I needed.

So to help anyone else avoid the same pitfall, I recommend following this article on the proper way to prepare your Pixelbook (any chromebook) for offline use.

https://support.google.com/chromebook/answer/2809731?hl=en

 

[sracer]

It's been a year... here's the latest escapades with my Pixelbook.

It's been a mixed bag with this device. So much power and potential that has gone untapped. The 2 apps that I heavily rely on aren't offered for Linux, Android, or Chrome. Any of these platforms would've been fine. I had WINE working on it until a ChromeOS update broke it (never to run well again).

So there was only one thing to do... install Windows 10 on it. ? I already had great success of installing Win 10 on my Acer Chromebook 14... completely wiping out ChromeOS, flashing new firmware, and installing Win 10.

STEP 1. Disable the hardware write-protect.
In order to be able to wipe out all traces of ChromeOS, it is necessary to disable the write-protect. On the Acer, I simply had to unscrew the bottom, remove the bottom cover, and unscrew a literal write-protect screw.

With the Pixelbook, it would require removing the rubber feet, unscrewing the tiny screws, and disconnecting the battery.... or, get a "Suzy-Q" ChromeOS Debug Cable, put the PB into developer mode, open a terminal window, and run a few commands.

I didn't want to risk physically damaging my PB, so my wife gave me a Suzy-Q cable as part of my birthday present. I ran through the steps.

STEP 2. Flash the new firmware.
Using Mr. Chromebox's firmware script, it was a piece of cake to back up the standard PB firmware and flash the new UEFI firmware that would allow for any OS to be installed.

STEP 3. Download and create a Win 10 installation bootable USB thumbdrive.
Downloaded the .iso from Microsoft's site and used Rufus to create the bootable thumbdrive.

STEP 4. Install Windows 10.
Booted up the thumbdrive on the Pixelbook, and ran through the install process. When it prompted me for an activation key, I clicked on the "I don't have one" and continued on.


STEP 5. Boot Windows 10 and update drivers.
Once installed, I booted up off the Pixelbook's internal drive. Connected to my WiFi network and allowed it to update Windows and drivers. All the hardware was supported, though downloading the tap-to-click driver enabled that feature on the touchpad, and an additional audio driver improved the audio.

Performance is great. The only thing that I've noticed that doesn't quite work is screen rotation (going from landscape to portrait). That'll require a little digging. I'm curious to see how some heavier apps work on it.

And hey, if I get bored, I can install Linux, or go back to factory Chrome OS.