Wow LineageOS really is a bazaar, and not a cathedral.
* 74% of installs are unofficial builds, not ones released by LineageOS.
* 2/3 of US installs are on non-phones (waydroid, nintendo switch, rpi, etc)
* Most of the installs on actual phones are in China, Brazil and Vietnam
* Less than 21% of installs are on versions that receive security updates, and less than 9% of installs are on the latest version (mostly because device's binary blobs don't support newer android versions?)
> * 74% of installs are unofficial builds, not ones released by LineageOS.
Every time I want to install LineageOS on a device because it's been abandoned by the manufacturer, it's also been abandoned by LineageOS, leaving me with some random custom rom as only option.
It is a great OS. It needs to be available on newer Motorolas, say 2024 and onward. People want SD card slots, and even 3.5mm headphone jacks. It is the memory card slot that matters most.
It is great to have a degoogled phone. Then the lack of a card slot annoys you and the desire to just plug in an aux cable and have sound anywhere without a dongle comes to the fore.
I wish they would just commit to also support the Motorola G Stylus line. The G Stylus 2024 was a great phone.
>> 74% of installs are unofficial builds, not ones released by LineageOS.
One of the first versions of LineageOS I used was Evolution X on my Moms old OnePlus phone since it wasn't supported by the "official" Lineage version. Great track record of almost daily updates, and the customization you could do with it was phenomenal. The funny thing was I was running Ubuntu Touch on it before and it was super sluggish (totally not expecting that tbh) so switched to Evolution and suddenly the same phone was really snappy and the battery lasted for almost two days.
But yeah, I'm not surprised many installs are just branched versions of the original since many of them you can run on phones that aren't supported by the official version.
the LineageOS teams refuses to incorporate patches to support MicroG as a replacement for Google Services so anyone (including me) that wants to follow that path is required to use unofficial builds.
> They stopped that malpractice a while ago (last year?).
By now it has actually been almost two and a half years.
> But they really hurt their credibility with the prior stance, and that their subreddit still has rules forbidding almost all discussions [...].
While I'm not looking to turn this into an off-platform meta discussion, pretty much all of those rules have their very good reasons to be there.
As an example, you would be surprised how many people install a Magisk module to strip away LineageOS-specific build version properties, and then end up in our support platforms asking why the Updater can't search for new updates (of course while not mentioning that they have modified their system).
microG I don't even see listed as a part of any rule anymore, it was removed when upstream support for microG was merged.
You are correct, the microG ban is gone from the sidebar. That's nice.
(Why this was so important: During covid the official contact tracker in Germany needed microG/the play services, a newer alternative then bundled the scanner or something, so worked without. But that took time and was less official. When it becomes life and death impractical positions like that hurt).
It's okay if you dont want to discuss it. To share my position anyway: You need the option to have root so the device belongs you (and not the Rom), VoLTE is an existential threat and the ban stiffles all options to easily get information about the situation. That's the main point: Banning topics completely does only make things worse, and it is not like the project tried not to ban these topics for how many years now, a decade? An Autobot answer should suffice for making the problems known.
If you are talking about the addition of microG, that indeed seems like it hasn't been mentioned on the blog, although I'd argue very likely due to an oversight.
I can find internal conversations that it deserves to be announced in a more prominent way than on the "Sunsetting LineageOS 18.1" post, was left as "to be added to the LineageOS 22.x" blog post, and then just never made the initial draft. Whoops.
If you are talking about the rules on the subreddit (or the other social platforms), that one indeed has been discussed a lot on the platform itself (and which we usually keep available).
i'm not sure all those "installs on actual phones" in china are real - 107k installs all on the same device, vs ~30k installs on the next most popular device. and 150k devices on an unknown carrier. is the Xiaomi Mi 8 really that popular for lineageOS, or is this some measurement artifact or common emulation setup?
Mi 8 has a very good camera and battery life I am guessing it could be used as live streaming phone in china so still useful despite being an older device
Given how uncommon x86 phones are (a few asus, lenovo, etc. that did not sell well) I think it's clear the vast majority of waydroid_x86_64 are not phones, right?
Searching for "waydroid_x86_64 LineageOS 20.0" leads to a sourceforge page [0] of waydroid with LineageOS builds that have 70-80k downloads per month.
It seems to be popular to be installed on CachyOS, which in turn is the 2nd most popular distro to use Steam (after SteamOS itself), so my guess is that it's a popular setup for gaming...
Nobody was saying anything about x86_64 being the vast majority of Waydroid installs or not but you, so not sure what's your point. Read my first comment again.
The parent said "2/3 of US installs are on non-phones (waydroid, nintendo switch, rpi, etc)", you responded with "Some Waydroid installations are on phones". My response to you was about the vast majority of waydroid installs tracked here are highly unlikely to be on phones due to the CPU architecture.
Your response was unwarranted. I never said anything that would suggest that most of these are phones. Some of these 2/3 are, even if they're in the minority.
Exactly why I stopped installing LineageOS on my phone.
While part of it was that I was no longer interested in tinkering with ROM and playing cat-and-mouse game with SafetyNet/root detection/whatever, the other part is that I cannot trust these ROMs, some of which come (or came) with their own bloatware. Those that have official builds are of course better, but the overall experience and security situation is still much worse than OEM ROM, despite all the junk there.
P.S. another issue is that I became sick of is devs using xda forum as the only communication channel, including bug reports, updates etc. GitHub has existed for over a decade, and the issue tracker/release system is usable, yet they choose the worst way to do software engineering.
Agreed, the xda forum thing is a huge security smell. "Here, download this big binary from a random forum user and put it on a device you carry with you everywhere which is equipped with internet, camera, microphone, and GPS. You're welcome!"
The GrapheneOS setup seems a lot better (though it has more limited support).
currently on GraphineOS for those very reasons. There is some amazing stuff in XDA forums but ultimately it's just some random guy posting some random ROM.
Only way I was able to get Cyanogenmod on stuff back in the day, was to use shady hacks from XDA, but man it was super slow and seemed to use a ton of bandwidth...
xda is older than github and has a lot of institutional inertia. Also I get the impression that many of the people involved in the xda ecosystem are hobbyists that just kind of learn things as they go along and have less exposure to bigco software engineering practices.
You talk as if github is a daunting service only meant for enterprise customers.
When in reality it's easy to sign up and used by almost every kind of project you can think of, including someone's 100 line random bash script with a single sentence README, a tiny embedded device hobby project all the way to a vibe coded project, from people who know nothing about software engineering. Issues are PRs are regularly used for all those projects. You almost need to go extra mile to not put your stuff on github.
I don't think there is any reasonable excuse/explanation other than "inertia".
* 74% of installs are unofficial builds, not ones released by LineageOS.
* 2/3 of US installs are on non-phones (waydroid, nintendo switch, rpi, etc)
* Most of the installs on actual phones are in China, Brazil and Vietnam
* Less than 21% of installs are on versions that receive security updates, and less than 9% of installs are on the latest version (mostly because device's binary blobs don't support newer android versions?)