But without those things, it's an overpriced netbook with a CPU far too powerful.
The Chromebook Pixel (2015) Review
51–58 of 58 posts
Re: The Chromebook Pixel (2015) Review
#52$1299 for 64gb ssd ? I wish it had atleast 500gb ssd :(
This! Yes, it is a "netbook," but 64gb is becoming my minimum requirement for a mobile phone. Even a 128gb option would be appreciated.
Re: The Chromebook Pixel (2015) Review
#53That was my main complaint with the original Pixel - I was running Debian on it as my main machine, but after that happening for the 5th time at a conference and having to reinstall...
Re: The Chromebook Pixel (2015) Review
#54Re: The Chromebook Pixel (2015) Review
#55Gazelle Professional: 15.6" matte display 2.8 Ghz quad core i7 16 GB RAM 250 GB SSD Wireless AC Price as configured above: $1477
The Pixel might have it beat in weight and battery life, but that's about it.
Re: The Chromebook Pixel (2015) Review
#56Earlier quoted context omitted.
This! Yes, it is a "netbook," but 64gb is becoming my minimum requirement for a mobile phone. Even a 128gb option would be appreciated.
Genuinely curious. How do you occupy all of that space on a phone? I've had my 8GB nexus 4 for almost two years, and I'm just now hitting space limitations.
Re: The Chromebook Pixel (2015) Review
#57Does anyone know if they fixed the bug in the original Pixel where if the battery died (or just got too low!) it'd lose the dev mode setting? That was my main complaint with the original Pixel - I was running Debian on it as my main machine, but after that happening for the 5th time at a conference and having to reinstall...
That's not so much a bug but a known issue. The flag that you set at the command line to enable SeaBIOS is held in RAM. Which means if you lose power, that goes back to default.
To get around this, you need to disable the write-protect screw inside the device. Take a look at https://www.chromium.org/chromium-os/developer-information-f... for instructions on how to do this, and where the screw is.
After that, you can modify the firmware, and update the setting in NVRAM. Take a look at the Arch Chromebook wiki for the commands to use to do what you want. https://wiki.archlinux.org/index.php/Chrome_OS_devices#Boot_...