Custom ROMs have me excited about Googlebooks

When I went to Google’s presentation on its new Googlebooks, it was an act of convenience. I happen to be near New York City, so I’m used to schlepping my way onto a bus for media events. As the Performance desk lead, I really don’t have any personal interest in Google’s successor to its Chromebook venture, especially since it’s packed with “AI.” So I was there mostly to support our AI expert, Ben Patterson.

But one bit of news caught my attention: You get access to the bootloader.

A brave new (old) world

This requires a bit of context. See, I’m an Android guy. I started my tech journalism career on Android-focused sites, back when smartphones were still the hottest, newest tech on the planet, and tons of people were obsessing over every new model. One of the most exciting parts of Android was the ability to modify the software fairly easily. You could “root” them to get access to all the various bits and bobs, or even load up your own custom-cooked, open-source operating system, colloquially called a ROM.

Rooting and ROMs are still a thing in the Android world, but they’ve fallen off by an order of magnitude since the glory days of 2010-2015. Somewhat because phones are far more locked down, aside from some where open access is a feature, like Google’s Pixel line or the Fairphone. But mostly it’s because phones are powerful and flexible enough to do pretty much everything you want now, no risky or skilled modifications required.

I installed an AOSP-based ROM on my Barnes & Noble Nook Color e-reader to turn it into one of the first full-power Android tablets. But I can’t remember the last time I looked at an Android phone’s bootloader, despite trying dozens (maybe hundreds!) of different ROMs back in the day.

Googlebooks are, at least in the purest technical sense, Android-powered laptops. They’re running Intel and Qualcomm chips — some of the same ones that power Windows laptops, in fact. But Android software is based on open-source code, loath as Google is to admit that these days. That means it should be possible, if not easy or straightforward, to modify it. At the NYC event I asked various representatives from Google and its hardware partners if they would allow users to wipe the laptops clean and install Windows, and they didn’t have an answer ready for me.

Fast forward to this week, and we have confirmation via Google support that Googlebooks will arrive with an unlockable bootloader. For those of you who’ve never dug deep into an XDA forum to find a Gapps ZIP that will work with your tweaked CyanogenMod build, that means you should be able to load up custom ROMs.

That’s got the nerdiest part of my soul extremely excited. Custom ROM developers advanced Android’s early years in ways that might be invisible to those outside of that particular niche. Google, Samsung, and others apparently took direct inspiration from the ways that developers modified their software in order to improve it, particularly in terms of the user interface and performance.

You know how you can swipe up from the bottom of your phone to go home and swipe on the side to go back? How there’s an easy shortcut to turn on the rear camera flash and make a quick flashlight? Yeah, both of those showed up in custom Android ROMs and other modifications years before they were stock in either Android or iOS. The prospect of seeing users customize the operating system in Googlebooks is absolutely tantalizing.

…but it’s not very likely to happen

But there’s a fly in this particular ointment. The early Android ROM scene was so vibrant specifically because millions and millions of people were excited about smartphones. It was the Wild West, and everybody wanted the fastest horse. For the same thing to happen with Googlebooks, Google’s AI-laden “reinvention” of the laptop, people will need to be excited about Googlebooks. And I don’t see that happening, not even to the degree that people were interested in Chromebooks when they debuted back in 2011.

There’s an extremely narrow slice of the consumer market for whom I think a Googlebook purchase makes sense. You need to be A) really, really happy with your Android phone, B) really want a new laptop, C) not reliant upon any tools or software that only works on Windows or Mac, and C) not particularly bothered by a lack of native game support. Oh, and you need to have a budget of about a thousand dollars or more, because even limiting the RAM to 8GB isn’t making Googlebooks cheap.

There’s a faint possibility of an exciting new world in custom laptop software. But it’s very faint indeed without a large, dedicated group of people making it happen. And as much as I want to see it, I doubt that I will.