Hacker News Reader

Comment by tejohnso | Hacker News Reader

Forked from Lineage but it's unclear what problems are being solved that aren't already solved by Lineage.

Worse, it's forked from an old version of LineageOS that will be deprecated/unsupported once 16.0 is out.

Are they skipping 15 for a bunch of phones? I'm on a 2015 Motorola phone that still gets weekly 14.1 updates, and I kinda wonder if it's just EOL even for Lineage.

It's probably EOL.

Generally speaking you still depend on the device manufacturer to ship a compatible vendor partition in order to run a given version of LineageOS. This means that if your device doesn't have an official version of Android 8, then it will never be able to run LineageOS 15.

> Are they skipping 15 for a bunch of phones?

If your device doesn't already support 15, then it's highly unlikely that it will ever seen an official release with 15, or 16, or anything >14.1.

I wouldn't call it a hard fork, more a downstream derivative. In a similar way, Ubuntu rebases itself on debian unstable every 6 months or so.

That is to say Duval based his product on whichever LineageOS release was 'current' at the time but plans to sync to the next available release when his next development cycle allows (which is Oreo, currently).

Smartphones are heavily tied to services. I think their goal is to create services that respect privacy and integrate them with their fork of Lineage.

In other words, they're making the complete package and they plan to target average people.

Services is the thing /e/ is also trying to solve. They plan to make the complete package. For the tech savvy, you'll be able to install those services on your own server.

Reply on news.ycombinator.com