Related
I have all kinds of Android devices and I use Cyanogenmod on all of them. I like to have the same exact system on each; saves me time, to have to learn only one. Plus I very much like CM.
But on this device, for some reason, most of the development effort seems to go to the *toad releases. Could someone elaborate why? Secondly, why use a *toad instead of the "real" Cyanogenmod?
hardy81 said:
I have all kinds of Android devices and I use Cyanogenmod on all of them. I like to have the same exact system on each; saves me time, to have to learn only one. Plus I very much like CM.
But on this device, for some reason, most of the development effort seems to go to the *toad releases. Could someone elaborate why? Secondly, why use a *toad instead of the "real" Cyanogenmod?
Click to expand...
Click to collapse
Because the official releases are posted in the CyanogenMod website under downloads>official devices...the device maintainer for cm on apexqtmo was also banned from xda
Sent from my R3L4Y 4G using xda-developers app
Ummm, What? The official device maintainer for CM is @Nardholio who is definitely still here.
The HypnoToad images started as TeamApexQ's test bed, as time went on, there were tweaks that were made that were not accepted by CM for one reason or another, but we liked them. They became part of our internal builds, which as that stabilized and diverged more from CyanogenMod, we made available as FatToad. OmniToad is based on Omnirom, not CyanogenMod. The majority of TeamApexQ likes the Omni base better, so that has become our development platform.
One of the tweaks that are part of FatToad have bitrotted a bit, and the developer of that tweak has moved on to OmniToad, and has no intention of going back and maintaining said tweak, so FatToad likely will not be seeing any more releases.
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Magamo said:
Ummm, What? The official device maintainer for CM is @Nardholio who is definitely still here.
The HypnoToad images started as TeamApexQ's test bed, as time went on, there were tweaks that were made that were not accepted by CM for one reason or another, but we liked them. They became part of our internal builds, which as that stabilized and diverged more from CyanogenMod, we made available as FatToad. OmniToad is based on Omnirom, not CyanogenMod. The majority of TeamApexQ likes the Omni base better, so that has become our development platform.
One of the tweaks that are part of FatToad have bitrotted a bit, and the developer of that tweak has moved on to OmniToad, and has no intention of going back and maintaining said tweak, so FatToad likely will not be seeing any more releases.
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Click to expand...
Click to collapse
XDA refuses to ban me
Nardholio said:
XDA refuses to ban me
Click to expand...
Click to collapse
i thought it was lbcoder....well thats what i was told anyway....grats on being a good maintainer Nard
hi
The difference between the original ROM and Kastvm
Magamo said:
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Click to expand...
Click to collapse
This is good to hear. Programmers of free software tend to jump ship pretty quickly and get bored with anything that is not new & cool. But Cyanogenmod should be seen as cool, since it's just awesome to have the same system on so many devices.
Thanks for the clarifications.
hardy81 said:
This is good to hear. Programmers of free software tend to jump ship pretty quickly and get bored with anything that is not new & cool. But Cyanogenmod should be seen as cool, since it's just awesome to have the same system on so many devices.
Thanks for the clarifications.
Click to expand...
Click to collapse
As a very agreeable argument...the same could go for other great ROMs too and not just CyanogenMod..just takes developers to bring em to the device including CM...to each his own and that's why there is a variety to choose from
Sent from my R3L4Y 4G using xda-developers app
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
Hi all,
Over the past few months I have been building CyanogenMod (now LineageOS) 13.0 for my personal use. It's based off Kumajaya's sources and was roughly parallel to emfox's builds. I'm doing this because I'm dissatisfied with the stability and reliability of existing ROMs. (I can't claim that mine is any better, however it does put me in a position to debug the issues.)
This is an interest check. I am considering publishing my nightlies for people to download. I know that everyone will give a blanket "yes" to the question "should I publish my nightlies for people to download?". So instead I would like to ask:
Given the other excellent Mi 4c ROMs, including @Hikari no Tenshi's LineageOS 14.1 builds, Resurrection Remix N and Team Superluminal CM13.0, what reason would people have to use Yet Another ROM?
(Long time reader, first time poster!)
This will sound kind of cliche but , the more options , the better . Maybe some of us will find your ROM more suited to their daily use or something .
So yeah definitely share it man
philipnzw said:
This will sound kind of cliche but , the more options , the better . Maybe some of us will find your ROM more suited to their daily use or something .
So yeah definitely share it man
Click to expand...
Click to collapse
I second this! More roms/more activity keeps this device alive longer too
1. Your development wil keep this device alive longer.
2.(maybe) attract other dev/team to build rom for this device.
3.it will make your rom better,by sharing and let many people using it, will helps you find problem faster and improve it.
so yes!
Always useful to have more I have an Aqua (mi4s) and the rom scene is very poor :/ a few Libra roms do support it but in recent months even the SD card support has gone making for quite a sad outlook for the device. If there were someone building nightlies, it would be ace as from time to time you might be able to dip into the aqua stuff too and we'd all appreciate that
Whatever you decide, it's a nice thing to even consider doing for the community. You have my thanks
honestly i think Marshmallow is waste of time, most of the people are interested only in newest Android and i don't see much interest since we have official nougat ROMs from Mokee, AICP and Resurrection remix
if you want to do something different there is Nougat AOSP ROM missing, blobs from Xiaomi are already available, Nexus 5X as well, so...
more roms, more options. i want my mi4c looks better than Nexus 5X
terence.tan said:
Given the other excellent Mi 4c ROMs, including @Hikari no Tenshi's LineageOS 14.1 builds, Resurrection Remix N and Team Superluminal CM13.0, what reason would people have to use Yet Another ROM?
Click to expand...
Click to collapse
It really depends on what you would have to offer. The available CM13 (or are we calling them LO13 now?) ROMs are TeamSuperluminal's and Emfox's builds which are really not actively maintained anymore, although they are pretty damn stable. Except of course the few bugs that seem to go unfixed -- the touchscreen bug, which appears to be really complicated to fix without newer Xiaomi's kernel sources, the 2% battery bug which is present in TeamSuperluminal's builds and isn't a gamebreaker, and the way the SoC uses its cores in most of the ROMs based on Kumajaya's kernel sources (always active big cores) which results in lower battery life.
If you solved some of these problems, expect users to flock to your ROM. If not, I wouldn't bother, since you'll just be flooded with requests for fixing stuff that isn't broken in the first place. In fact, expect the second even if you deliver on the first.
I don't maintain any ROMs so I'm not one to give advice, but it seems to me it's a lot of work, and that you're paid with criticism and demands for more of your time. Get in contact with a ROM author and ask them for advice on this
Thanks for the thoughts.
As far as I can figure, there are 3 things people want:
Features/being on the cutting edge
Performance
Stability/reliability
We want all 3 but unfortunately it is a trade-off. In particular it takes special effort to achieve stability when combined with the other 2.
The CM14.1 builds satisfy the people who want to live on the cutting edge. The Xceed ROM is built for speed for those who think that Snapdragon 808 should perform like the top-tier chipset that it is
But out of all the ROMs I've tried (haven't tried the CM14.1 builds yet but have tried most of the others) I've had the following stability problems:
Screen freezes, requiring reboot
Sleeps of death
Random reboots in the middle of the night (waking up at 3 a.m. to find my phone clicking at me on the "decrypt your device" screen)
Stuttering or hangups
OpenGL-based games crashing
And that's not including the well-publicised touchscreen and battery problems.
So my personal strategy is:
Marshmallow build. Sorry for those who want Nougat, but I don't consider it stable enough (yet). Plus, all the proprietary MIUI vendor blobs from Xiaomi are targeted at Android L, and getting them working on Android M is hard enough already...
For the kernel, track CAF closely. Probably take their Android N release on the assumption that it's stable
Use as few proprietary blobs as possible; build from CAF source where available. This is what most developers are doing already
Use the most recent proprietary MIUI vendor blobs from Xiaomi, on the assumption that they've been buillding this version of MIUI on Android L for such a long time that it's stable
Avoid importing proprietary blobs from other devices (Nexus 5X, Moto X Pure etc.) where possible for licensing reasons. I don't intend to try and make this an offical LineageOS build, but this might be important for whoever attempts in future...
All this is difficult and @ketut.kumajaya and friends put in some impressive hacks to get it to work in the first place. I can't promise that I can build on this! But if I ever get to a stage where it's fit for consumption, I'll publish something...
in my opinion this will be great for development on Libra devices, i think Nougat rom with clean source will be great for user like me sir. For now iam using RR Nougat and for me its stable for daily use, if we can make Libra official for Lineage it can open other rom change to get official build too. Best luck for you sir and cant wait for your contribution
i'm extremely grateful for all of the ROMs in the development section currently, but i'm kinda bummed there aren't more AOSP ROMs. i know only the developers have the definite answer to this question, but i'm curious to see what everyone else thinks. do you guys think we'll see an increase in ROM development (specifically AOSP) once Oreo officially launches?
IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..
tomascus said:
IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..
Click to expand...
Click to collapse
I am one of the people you mention, although as I stated to you in the slim thread, the limit of my ability seems to be at a command line... I tested numerous builds for nick and reported back with logs to no avail...
If you have a working build of 14.1 which is 'almost stable' why dont you have plans to release it? Surely others could start using your base to make their own roms as you previously stated.
PS not an insult, just a query.
miffymiffy said:
I am one of the people you mention, although as I stated to you in the slim thread, the limit of my ability seems to be at a command line... I tested numerous builds for nick and reported back with logs to no avail...
If you have a working build of 14.1 which is 'almost stable' why dont you have plans to release it? Surely others could start using your base to make their own roms as you previously stated.
PS not an insult, just a query.
Click to expand...
Click to collapse
The main reason is that I try not to release builds with some essential things broken, such as Edge Sense right now, which I consider a major feature for our device. Also, you can understand how terrible Aussie upload speeds are, especially without NBN in my area (coming soon my ass), so upload test builds would take forever.
Anyone is free to see my device tree and kernel anyway on my Github, same username as my XDA one.
tomascus said:
The main reason is that I try not to release builds with some essential things broken, such as Edge Sense right now, which I consider a major feature for our device. Also, you can understand how terrible Aussie upload speeds are, especially without NBN in my area (coming soon my ass), so upload test builds would take forever.
Anyone is free to see my device tree and kernel anyway on my Github, same username as my XDA one.
Click to expand...
Click to collapse
Is the dualsim variant DUGL working on your build ? If it is then i can build some custom roms using yours and slim base..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS
amit_sen said:
Is the dualsim variant DUGL working on your build ? If it is then i can build some custom roms using yours and slim base..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS
Click to expand...
Click to collapse
As I said before in the slim thread, I don't have a dual sim device so it's broken and I can't fix. If you are a dev then I assume you have some skills to troubleshoot the issue.
Actually I don't know why we need this boring looking roms
The stock sense rom is perfect with ultra smooth performance
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Actually I wanna try
Miui rom ❤
tomascus said:
IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..
Click to expand...
Click to collapse
I just flashed slimrom and it's pretty stable for me. I'd love to help out. What can I do?
Hi all, a quick thought that fits this topic, I think.
I was wondering if there is any chance we see the U11 Life Android One ROM ported to the U11, when the U11 Life will be out?
I'm asking because I saw this was the case for some Xiaomi devices:
https://forum.xda-developers.com/re...-androidone-7-9-21-xiaomi-redmi-note-t3691907
Thanks in advance !
So all of a sudden just a little while back the phone I had at the time just suddenly was, without warning, abandoned by LineageOS and all ROM downloads removed. So I started using a third party ROM with mostly minimal issues (but there's definitely a difference between official support and not it seems.) Then when I broke that phone I started looking into other possibilities and I started to notice: a shocking number of devices have been dropped. Many are even fairly standard well supported devices (like Nexus devices!) And more and more now I find more and more devices listed as no longer supported with no ROMs available. I ultimately did finally find a suitable phone for my needs that was still officially supported, but it's getting harder and harder to find anything whenever I search for a new device for a friend to find something with official support. Plenty of devices have various unofficial ROMs out there with varying degrees of issues, but the list of devices with official support and official builds available seems to be shrinking almost daily. I tried to look at possibilities for a certain sort of tablet for someone and found that there are virtually no tablets even left in the list anymore even.
Is LineageOS dying or what? What is going on with it all of a sudden lately? It seems a real shame to see LineageOS devolve into just an unofficial collection of unofficial ROMs from random people on the Internet who are just putting in a bit of their spare time and often enough not even able to really test it out well, yet it really feels like that's what is happening to me. After whatever happened with CyanogenMod I am, I believe, justified in being a bit worried.
BTW, is there any sort of alternative for something relatively clean with official support for a lot of devices? Maybe some sort of official AOSP porting project or something?
Nazo said:
So all of a sudden just a little while back the phone I had at the time just suddenly was, without warning, abandoned by LineageOS and all ROM downloads removed. So I started using a third party ROM with mostly minimal issues (but there's definitely a difference between official support and not it seems.) Then when I broke that phone I started looking into other possibilities and I started to notice: a shocking number of devices have been dropped. Many are even fairly standard well supported devices (like Nexus devices!) And more and more now I find more and more devices listed as no longer supported with no ROMs available. I ultimately did finally find a suitable phone for my needs that was still officially supported, but it's getting harder and harder to find anything whenever I search for a new device for a friend to find something with official support. Plenty of devices have various unofficial ROMs out there with varying degrees of issues, but the list of devices with official support and official builds available seems to be shrinking almost daily. I tried to look at possibilities for a certain sort of tablet for someone and found that there are virtually no tablets even left in the list anymore even.
Is LineageOS dying or what? What is going on with it all of a sudden lately? It seems a real shame to see LineageOS devolve into just an unofficial collection of unofficial ROMs from random people on the Internet who are just putting in a bit of their spare time and often enough not even able to really test it out well, yet it really feels like that's what is happening to me. After whatever happened with CyanogenMod I am, I believe, justified in being a bit worried.
BTW, is there any sort of alternative for something relatively clean with official support for a lot of devices? Maybe some sort of official AOSP porting project or something?
Click to expand...
Click to collapse
The reduction in development is probably partly due to lack of manpower on the official LineageOS team and fewer developers owning certain devices(if there are no developers that own the device, that device doesn't receive any development). It is also partly due to devices becoming more and more secure, this leads to fewer people creating development and fewer devices that are capable of being customized.
It isn't just devices being dropped from development, the size of the XDA community and amount of overall activity on this whole website is also declining.
Sent from my SM-S767VL using Tapatalk