Linux Phones Explained: Why Commodore's Callback 8020 Is Different

When Commodore announced the Callback 8020 — a $499 flip phone — much of the coverage focused on the retro brand and the no-social-media angle. The more interesting technical claim is buried underneath: it doesn't run Android or iOS. It runs Sailfish OS, a Linux-based mobile operating system, and promises to still run "most Android apps." That combination — a true Linux phone that isn't a niche hacker project — is genuinely unusual. Here's what a "Linux phone" actually is, how the app-compatibility trick works, and what Commodore changed to make the 8020 different.

What "Linux phone" means — and what it doesn't

Strictly speaking, Android is Linux: it runs on the Linux kernel. But in common usage, a "Linux phone" means a device whose entire user-facing stack is desktop-style open-source Linux — not Google's Android userland with its Google services, app model, and Play Store. The distinction is about what sits on top of the kernel.

The mainstream phone OSes are Android (Linux kernel + Google's stack) and iOS (Apple's Darwin/XNU kernel). The "true Linux" alternatives are a small family:

• Sailfish OS — developed by the Finnish company Jolla, founded by ex-Nokia staff after Nokia abandoned its MeeGo project. It's the most mature commercial option and is what the Callback 8020 uses.
• postmarketOS — a community project built on Alpine Linux, aimed at extending the life of old phones.
• Ubuntu Touch — formerly Canonical's project, now maintained by the UBports community.

These share a common appeal: no Google services baked in, a real Linux underneath, and far more control over the device. They share a common problem too, which is the whole reason the next section exists.

The app problem — and how Sailfish gets around it

The reason "true Linux" phones stay niche isn't the OS quality; it's the app gap. The apps people need — banking, messaging, transit, two-factor authenticators — are built for Android and iOS. A pure Linux phone can't natively run them.

Sailfish OS's answer is an Android compatibility layer (historically marketed as "Android App Support"). It runs Android apps inside a contained Android runtime environment — effectively a sandbox — on top of the Linux system, so you can install many Android .apk files even though the host OS isn't Android. Commodore's marketing leans hard on this, citing very high Android-app compatibility.

The honest caveat, which the marketing tends to skip: apps that depend heavily on Google Play Services often misbehave or fail. Sailfish is de-Googled, so anything that expects Google's push-notification, location, or licensing infrastructure — a lot of mainstream apps quietly do — can break, run degraded, or refuse to start. "Runs most Android apps" is true in the sense that the runtime accepts them; it's optimistic about how many work flawlessly. Treat the 99%-style figures as a best case, not a guarantee, and verify the specific apps you depend on before relying on one of these phones as your only device.

What makes the Callback 8020 specifically different

Plenty of phones run Sailfish. What's novel here is that Commodore uses the Linux base not to give you more freedom but to impose restriction by design — the same de-Googled OS, pointed at the opposite goal:

• Browser blocked at the system level. Per coverage of the device, there is no web browser and no user setting to enable one — it's blocked in the OS, not just absent.
• Social media blocked at the system level, again with no toggle to turn it back on.
• No work or email apps offered through the company's own app channel — replicating, in software, the "leave work at the door" separation.
• Keypad-first hardware: the touchscreen is disabled by default and only wakes when an app genuinely needs touch input, pushing you toward physical buttons and T9-style typing.
• It still allows the essentials it doesn't consider distracting — calling and SMS, plus messengers like WhatsApp, Signal and Telegram via the Android layer, a maps app, music, podcasts, calendar and a 48-megapixel Sony camera.

So the design thesis is the inverse of a normal phone: a capable Linux device deliberately fenced in. You can still sideload .apk files, but the browser and social-media blocks are baked into the OS rather than left to your willpower.

Linux phone vs. Android vs. dumbphone — where the 8020 sits

The 8020 is essentially a dumbphone built on a smartphone-class OS — which is why it can charge $499 and still claim to run real apps, where a true dumbphone can't.

FAQ

Is a Linux phone the same as Android?

Technically Android uses the Linux kernel, but a "Linux phone" means the whole system is desktop-style open-source Linux without Google's Android stack — like Sailfish OS, postmarketOS, or Ubuntu Touch.

Can the Callback 8020 run my banking or authenticator app?

Maybe. It runs Android apps through Sailfish's compatibility layer, but apps that rely on Google Play Services can break on a de-Googled OS. Check your specific must-have apps before treating it as your only phone.

Can I just install a browser on it anyway?

Per the device's design, the browser and social-media apps are blocked at the operating-system level with no user toggle, so this isn't a setting you can flip — though you can still sideload other Android apps.

Bottom line

A "Linux phone" is one whose whole stack is open-source Linux rather than Google's Android — and Sailfish OS, via its Android compatibility layer, is the version mature enough to run on a commercial product. Commodore's twist with the Callback 8020 is to use that de-Googled, controllable base not for maximal freedom but for enforced restriction, blocking browsers and social media in the OS itself. Just go in clear-eyed about the app gap: "runs most Android apps" is a best case, and anything leaning on Google's services may not survive the move.

If you'd rather rein in the phone you already have, our companion how-to covers the settings that get you most of the way there.

Build a low-distraction phone setup

Sources and further reading