Live data from Hacker News

LineageOS will be a continuation of what CyanogenMod was

lineageos.org

91–100 of 118 posts

Re: LineageOS will be a continuation of what CyanogenMod was

#91

Who's going to make sure LineageOS users get security updates in a timely manner? Is anyone going to be paid to work on it? Any large OSS distribution is going to have a fairly continuous stream of security fixes to ship to their users, and that takes a fair amount of time, and I'm always concerned about whether any new project (okay—it's not quite new, but they have a fraction of the number of developers they did tw…

Probably the same people who made sure CyanogenOS users got timely updates: no one.

Last update for my phone was early september. Not holding my breath for this.

Re: LineageOS will be a continuation of what CyanogenMod was

#92

The question is what will ensure the continual non-profitness of lineageOS? The problem is two fold: 1. Get maintainers. 2. Make sure that the high ranking individuals can't just "take the ball and go home", and (however unpopular this opinion may be here), GPL is the only way to ensure that they will never be able to sell out ever again. And especially after the CM/CyanogenOS/Focal/Paranoid Android situation, privat…

My hope is that they can find a way to collaborate with fairphone: https://code.fairphone.com/projects/fp-osos/

LineageOS needs a flagship phone, FairPhone needs a community-empowered OS.

Re: LineageOS will be a continuation of what CyanogenMod was

#93
post #80

Earlier quoted context omitted.

Volunteer open source developers are not interchangeable cogs ('resources') to be redeployed across projects at will by anyone except themselves - they are volunteers and work on stuff they are passionate about. The F/OSS 'community' has some of the most entitled folk on this blue planet - I'm yet to hear anyone suggest pet shelter volunteers work together on a mega-shelter instead of "wasting effort on duplicate rol…

That's a false equivalency. No one suggests IT staff deploying hardware are B duplicating effort because there's a physical correlation between results and resources. But 10 different desktop environments are each solving the same problem 10 different ways, consuming 10 developers time, when a collaborative project would be able to reduce that by a huge factor and benefit everyone. I would also suggest it's naive to…

>> when a collaborative project would be able to reduce that by a huge factor and benefit everyone.

Or benefit no one because you create a Desktop that no one likes because it is developed in a way to pisses everyone off

Gnome users do not like the KDE Experience

Awesome Users do not like the Gnome Experience

XFCE users do not like the Awesome Experiance

This is the reason these products exisit, and no it is not "duplicating efforts" any more than have different models of Cars is "duplicating efforts"

Do you really believe the automotive industry would be better off is all the Auto Manufacturers did away with all Models and simply made 1 car.

Re: LineageOS will be a continuation of what CyanogenMod was

#94
post #63

Earlier quoted context omitted.

I have never understood the desire to have 1 Homogeneous Platform with no variety, no customization, no personality. To have a large corporate overlord dictating how I use the device I "bought" I see these same statements in the Linux Desktop world where everyone bitches about how All the Distro's are different, and how the Arch way is different from the Debian Way, and different from Red Hat, Canonical etc. That is…

You're not the target audience.

>target audience

Of what?

Re: LineageOS will be a continuation of what CyanogenMod was

#95
post #52

Earlier quoted context omitted.

google offered to buy Cyanogen. ( http://arstechnica.com/gadgets/2014/10/google-reportedly-tri... ) Also, recall that Cyanogen (the company, not the mod) said that they were going to "put a bullet in Google's head". I bet Google has tried to offer support to them and Cyanogen turned it down.

I can't fathom why Google would buy them. Why not make a version of AOSP that people can actually use, like Cyanogenmod?

Supporting many devices is a double-edged sword. I feel what Google wanted for their AOSP code is to not support tens of different devices to make the code move fast. Part of what made CM valuable, I feel, was really the changes that made it compatible with so many devices. So CM would have to remain CM for the devices support, not for the features of the ROM.

Re: LineageOS will be a continuation of what CyanogenMod was

#96

Who's going to make sure LineageOS users get security updates in a timely manner? Is anyone going to be paid to work on it? Any large OSS distribution is going to have a fairly continuous stream of security fixes to ship to their users, and that takes a fair amount of time, and I'm always concerned about whether any new project (okay—it's not quite new, but they have a fraction of the number of developers they did tw…

Something I've wondered about: why does Android require you flash a ROM to update the system? When you buy a windows laptop you'll usually get a bunch of vendor-specific crap, but after doing a clean install you can just pick up the drivers on their website and it'll all work fine. Why isn't this an option with Android?

As I have been involved with OpenWRT/LEDE and how they make builds to different devices recently, I realized that making unified builds are actually possible. OpenWRT has the same kernel and root image for many different devices that use the same SoC. So once you have OpenWRT flashed on, the content of every OpenWRT update (for every device of the same SOC) is by and large the same. The only check in place is the artificial model check to make sure you don't unintentionally flash the wrong image.

Android can technically do like OpenWRT does, but there is much more stuff involved in the Android world so making a universal build is harder. However, I personally can't think of a hard, technical barrier. New ideas for unifying devices and separating blobs such as device tree or separate vendor partition is getting traction and makers such as Sony are embracing it. Many Sony devices boot the same kernel, and that's why you consistently seeing Sony devices getting support and builds very early on from projects like CM.

BTW, I have been trying to write an answer to you by saying a slightly different version of what dispose54312 said, but then realized it didn't make sense. I came to the conclusion (for myself) this is mostly "how it is done currently for Android." So I hope my unpopular answer is not crazily misguided, and please take my perspective with a grain of salt.

Re: LineageOS will be a continuation of what CyanogenMod was

#97
post #88

Earlier quoted context omitted.

> as has been discussed elsewhere, the ability to avoid using google services is a serious disincentive for google to support cyanogenmod. The same argument applies to AOSP (cyanogenmod's upstream), but that hasn't stopped Google from supporting it.

With a little bit of careful adjustment to settings, you can disable all Google services on a Nexus device. It takes a little effort, but it can be done - unrooted and unmodified.

interesting. I'm aware that to quell anticompetitive accusations, google allows removal of many google apps and disabling of many services. But I believe the Google Play Services is deeply embedded in the google stock rom such that it can't be safely disabled in entirety.

Re: LineageOS will be a continuation of what CyanogenMod was

#98

Earlier quoted context omitted.

as has been discussed elsewhere, the ability to avoid using google services is a serious disincentive for google to support cyanogenmod.

> as has been discussed elsewhere, the ability to avoid using google services is a serious disincentive for google to support cyanogenmod. The same argument applies to AOSP (cyanogenmod's upstream), but that hasn't stopped Google from supporting it.

Supporting the upstream is different. One cannot simply download AOSP and install it on your phone, however custom roms provide something you can actually download and install. Google deliberately does not improve the AOSP base applications because they don't want people using their proprietary apps. Google mainly supports AOSP because they can get more people hooked on google services with it than they loose from things like Kindle.

So directly supporting an easy, installable downstream with bells-and-whistles like cyanogenmod would be a serious threat to google.

Re: LineageOS will be a continuation of what CyanogenMod was

#100
I'm getting really confused here.

I thought CyanogenOS was a commercial venture that arose out of CyanogenMod. But that they were essentially separate protects. I'd read about CyanogenOS coming a cropper, but understood this wouldn't affect CyanogenMod. Now, these linked articles seem to be treating -OS and -Mod as the same project/same organisation.

Can anyone explain?

Post reply on HN