OnlyOffice, not OpenOffice. This is a different suite entirely. Might be better for people coming from MS Office, since it looks practically identical. Also supports opening multiple files as tabs.

I’m a huge fan of Pine64, but I wouldn’t expect the PinePhone to be a great replacement for an Android smartphone. Personally I have quite extensive experience with PineBook Pro, PineTime and PineBuds Pro. I haven’t had the chance to try the PinePhone, but I’d definitely go for the Pro.

Even then, prepare for a junky experience and forget about lixuries such as good camera, nice screen, smooth UI/UX. Their devices are great, and the ideas behind them more so. But unfortunately they rarely work well, perhaps with the exception of PineBuds Pro.

Good point. Sometimes it helps to read properly

no more locked bootloader

Likewise modifying the bootloader requires unlocking it - which means no more secure boot and anyone who takes your phone can happily boot whatever they like on it. This is also bad.

Except for Graphene. The last step in the installation is locking the bootloader back, and the phone clearly says it’s locked.

As of right now, it’s looking like GrapheneOS will be unaffected, and Google has yet to lock down the bootloader. So this should remain a valid option for at least 2 years.

Other than that:

• Any smartphones with an unlocked bootloader + any ROMs without gapps
• Chinese smartphones with non-Google Android builds
• Linux smartphones
• Bonus: Huawei is about to release their own non-Android OS, but I wouldn’t expect it to be privacy-friendly

Honestly there probably isn’t any good, long-term solution. Personally I’m somewhat shocked we’ve gone this many years with reasonably open smartphones. Next step is probably closing bootloaders in new laptops, as part of the switch to ARM (which is already undergoing).

It’s very likely that no amount of negative feedback will change anything. Why not waste some of their time anyway? Write to them, call them, spread the word. This is the only thing we can do. Even if it goes through regardless - at the very least we can make it as unpleasant as possible.

Two things especially worth noting from the article.

If you have a non-Google build of Android on your phone, none of this applies.

This means that at least GrapheneOS will be unaffected for now. Other ROMs without gapps will be unaffected only as long as you don’t install gapps. Since Graphene has a sandbox for them, I’m assuming it’ll be fine. That is, unless Google decides to lock the bootloader entirely.

In September 2026, Google plans to launch this feature in Brazil, Indonesia, Singapore, and Thailand. The next step is still hazy, but Google is targeting 2027 to expand the verification requirements globally.

So most users worldwide still have at least 1.5 years until it’s implemented. Plenty of time to get a Pixel and install Graphene on it. Or to figure out some other plan.

Don’t get me wrong - this is insane, unreasonable and horrible news for everyone. We should push back as hard as physically possible against it. However, at the very least we still have some time to figure things out before the policy rolls out.

That’s a great question! I’ll be happy to help you count the lights. I see five lights.

This symbolizes the fact that for the last five hundred years white people have been victims of genocide in South Africa.

Would you like to learn more?