Database Info

CM has pretty poor update waiting times.

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...

[Q] VilleC2 and Android Lollipop

Hi to everyone reading this
I am a fairly long time user of xda, usually just lurking and watching threads as they go along, but have now decided to try my hand at developing a rom or two for our (unfortunately) long forgotten villec2, since everyone seems to develop for the S4 variant. I have seen android 5 ported to the S4 variant, and I would like to know if what I am trying to do is at all possible, and if it is, if anyone can point me in a starting direction.
What I am trying to accomplish, is to get a working (bootable, not much else) rom that can boot up on my phone, and then from there add drivers/modules (unsure about naming conventions used in android, coming from a java/C++ background) for the different phone functions as I learn more about the system. So far, I have not found much on upgrading device trees / vendor files (not even exactly sure what these are for since most I see are completely different, even for the same version of android) from 4.4 to 5.0.1, and if I should simply write many of these files from scratch. I know this is a huge en devour, and I am in for much frustration, but I am doing it for two main reasons. One, everyone seems to have forgotten the villec2 device, and I feel like I will still be using it for quite a long time, and being able to use the latest and greatest in android technology will be quite nice to say the least. And two, I am doing it for learning, broadening my own experience with android, since I have yet to really write my own rom, I have only done a few rough builds from other people's repositories like cm.
At this point, I have a AOSP build environment from the master branch, have not yet done a build from it, and would just like any nudge someone can give me in a starting direction. Would it be possible to obtain some of the files I need for android L from my current device,, which is running a android 4 variant? Should I look elsewhere for these files?

niekz said:
Hi to everyone reading this
I am a fairly long time user of xda, usually just lurking and watching threads as they go along, but have now decided to try my hand at developing a rom or two for our (unfortunately) long forgotten villec2, since everyone seems to develop for the S4 variant. I have seen android 5 ported to the S4 variant, and I would like to know if what I am trying to do is at all possible, and if it is, if anyone can point me in a starting direction.
What I am trying to accomplish, is to get a working (bootable, not much else) rom that can boot up on my phone, and then from there add drivers/modules (unsure about naming conventions used in android, coming from a java/C++ background) for the different phone functions as I learn more about the system. So far, I have not found much on upgrading device trees / vendor files (not even exactly sure what these are for since most I see are completely different, even for the same version of android) from 4.4 to 5.0.1, and if I should simply write many of these files from scratch. I know this is a huge en devour, and I am in for much frustration, but I am doing it for two main reasons. One, everyone seems to have forgotten the villec2 device, and I feel like I will still be using it for quite a long time, and being able to use the latest and greatest in android technology will be quite nice to say the least. And two, I am doing it for learning, broadening my own experience with android, since I have yet to really write my own rom, I have only done a few rough builds from other people's repositories like cm.
At this point, I have a AOSP build environment from the master branch, have not yet done a build from it, and would just like any nudge someone can give me in a starting direction. Would it be possible to obtain some of the files I need for android L from my current device,, which is running a android 4 variant? Should I look elsewhere for these files?
Click to expand...
Click to collapse
Have you seen this thread?
http://forum.xda-developers.com/showthread.php?t=2581659
I know it's not for C2 but maybe you can find some info there or someone can give you some advice
Sent from nowhere over the air...

I have checked out the thread, but unfortunately most of these guides refer to an already made vendor/device tree, which does not yet exist for the c2 (for android 5 anyways). Ill likely need to write my own it seems. Sadness..

Hi!
i really excited for this thread. i have a villeC2 and its very sad that phone just update at 4.1. its a really great phone whit much potential... if i can i help you but i don't know everything about compile roms. but i can try the rom like a beta tester. i really glad to do that. so.. if you continue whit this, i help you like a beta tester contacte me.

You can examine recent posts c2 development cm11 kitkat and offical pacman pages.

https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
https://forum.xda-developers.com/ch...ide-how-to-port-lollipop-marshmallow-t3283452
https://forum.xda-developers.com/showthread.php?t=2707438

i think we should port HTC Sensation roms
i dont know what's the difference between C2 and Sensation kernels . but i saw viperC2 and SAM rom files is the same
---------- Post added at 17:39 ---------- Previous post was at 17:06 ----------
https://forum.xda-developers.com/showthread.php?t=2178042

Interest check: LineageOS 13.0 nightlies for Mi 4c

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

Anyone using lineage 14.1?

I used to be huge into XDA and loved getting involved with the community. I started all the way back on a Samsung Vibrant. After being so busy with life and all I kinda fell out of it but saw Lineage OS and wanted to get into it again. After looking at the device list I picked up the H830 and got to rooting but looking at the community here, it doesn't seem like many members are trying it out. If you are can I get some of your feedback on it? I tried to flash once but got stuck in the bootloop so I hope to get it soon. Any advice would be much appreciated.

OldHemp said:
I used to be huge into XDA and loved getting involved with the community. I started all the way back on a Samsung Vibrant. After being so busy with life and all I kinda fell out of it but saw Lineage OS and wanted to get into it again. After looking at the device list I picked up the H830 and got to rooting but looking at the community here, it doesn't seem like many members are trying it out. If you are can I get some of your feedback on it? I tried to flash once but got stuck in the bootloop so I hope to get it soon. Any advice would be much appreciated.
Click to expand...
Click to collapse
You won't see much on T-Mobile threads as all the ROMs and even kernels are pretty much posted in main g5 threads. As far as which ROM to use, I recommend RR (and I've tried all available ROMs for our device too), although it may or may not continue to get updated, will depend if me or someone else pick up doing builds, whereas Los will continue to be updated on a weekly basis but those are not tested before release and may end up in bootloops like you stated you had. If wanting to run LOS and you end up in bootloops with latest build, I recommend downloading an earlier build and install that. Also, no matter what ROM based on lineageos you decide to use will have a couple issues. No NFC, some report issues with Bluetooth and some issues with camera (camera quality especially in low light isn't as good as stock, recently issues with saying videos). Hopefully this helps Any other questions feel free to ask.

jeffsga88 said:
You won't see much on T-Mobile threads as all the ROMs and even kernels are pretty much posted in main g5 threads. As far as which ROM to use, I recommend RR (and I've tried all available ROMs for our device too), although it may or may not continue to get updated, will depend if me or someone else pick up doing builds, whereas Los will continue to be updated on a weekly basis but those are not tested before release and may end up in bootloops like you stated you had. If wanting to run LOS and you end up in bootloops with latest build, I recommend downloading an earlier build and install that. Also, no matter what ROM based on lineageos you decide to use will have a couple issues. No NFC, some report issues with Bluetooth and some issues with camera (camera quality especially in low light isn't as good as stock, recently issues with saying videos). Hopefully this helps Any other questions feel free to ask.
Click to expand...
Click to collapse
I loved using the this device but unfortunately mine started the continuously boot loop. Even after going back completely to stock the problem persisted so I had to get a different device. But the community was awesome for the day I got to be a part of it.

Note 5 Pro development is basically gone

Xiaomi launched poco. It marketed it as a developer friendly device. And then it decided to give the device to some devs.
Who did they give it to? People who had previously worked on Xiaomi phones.
And so it happened. Vasishath, shahah_mik and akhilnarang got it. They definitely deserved it.
But with this Note 5 Pro is utterly f****d. Original development has almost completely stopped. Vasishath and shahah_mik brought up LOS and device trees for RN5 and now all they care about is poco.
Go check AOSIP Pie thread. Till 4th October, Akhilnarang was actively working on Pie for RN5 Pro. Now its over. Only derp kernel updates.
Maybe I'm ignorant but only jhenrique seems to be doing original development. Most others are pumping out xyz rom based on same source with same bugs.
I feel so bad. These devs definitely deserved a great phone but it came at the cost of Note 5 Pro. I don't think we will ever get proper Q roms and leave alone that, I don't think we'll ever get fully stable Pie roms like Oreo roms are stable right now.
RN3 launched with 5.1 and got super stable Nougat and Oreo. We started with Oreo and will remain on super stable Oreo custom roms. Other version roms have low chances of being as stable as Oreo.
I urge some developers to pick up LineageOs for this device. "Super glide butter flow remix" rom is nice but first we should have proper Pie code. Otherwise all roms will have similar bugs.

No offense to anybody.
I'm happy to be corrected.
Besides jhenrique, are there any devs doing Original development for Note 5 Pro?

Firstly what pie bugs are you talking about?
And secondly, we have so many hard working devs here making kernels, recoveries and ROMs. New updates every day, join the telegram group...

in the ever changing competitive market! there are always newer models to replace older ones! but the problem is, now the frequency of happening such is very high!
anyways even before poco! RN5 roms on 8.1 are fruit from same tree and i found many similar bugs after trying 10 different roms!
1. all have whatsapp behaviour issues (low call volume / voice notes screen offs )
2. random ui crashing on derp kernels when trying ending call
3. random restarts when whatsapp tries wakesup screen as you move away your device from ear! (proximity sensor)
4. poor BT Audio and noise
5. switching between 4g/3g (airplane mode on/off) fails to register sims to network (specially on crdroid roms on derp kernel)
6. touchwiz goes non responsive and nothing works accept navbar on , unless you switch off and on screen. (RR and crdroid)
7. Equiliser works ONLY if its activated before music player,
i havent tested custom rom of pie but i am sure i will find many bugs!
so what is my point?
that even if poco wasnt released! these inherited (verson to version of various custom roms) issues were never fixed! and i never expect them to be fixed!

YasuHamed said:
in the ever changing competitive market! there are always newer models to replace older ones! but the problem is, now the frequency of happening such is very high!
anyways even before poco! RN5 roms on 8.1 are fruit from same tree and i found many similar bugs after trying 10 different roms!
1. all have whatsapp behaviour issues (low call volume / voice notes screen offs )
2. random ui crashing on derp kernels when trying ending call
3. random restarts when whatsapp tries wakesup screen as you move away your device from ear! (proximity sensor)
4. poor BT Audio and noise
5. switching between 4g/3g (airplane mode on/off) fails to register sims to network (specially on crdroid roms on derp kernel)
6. touchwiz goes non responsive and nothing works accept navbar on , unless you switch off and on screen. (RR and crdroid)
7. Equiliser works ONLY if its activated before music player,
i havent tested custom rom of pie but i am sure i will find many bugs!
so what is my point?
that even if poco wasnt released! these inherited (verson to version of various custom roms) issues were never fixed! and i never expect them to be fixed!
Click to expand...
Click to collapse
You underestimate the power of good devs. Most of these bugs would have been fixed if major devs had continued to work on our device.
They brought up the tree from scratch and literally fixed so many bugs that users reported. If you don't feel like reading xda threads, go watch rom videos of AOSIP etc on youtube from the march/April month. You'll see that they had so many little and big bugs. All of them were fixed slowly and steadily.
So i dont see your point. Devs and their enthusiasm matters a lot. You wouldn't have a single rom running on your phone if devices trees had not been brought up. And then if they had, you wouldn't be using custom roms because of major bugs that they had in April/May. All the bugs that you report are minor and I'm not even facing a single one of them. Oreo is daily driver material because of the months of original development that was put into it by several devs.

Some of the more famous developers got a Poco device and are now spending time with it.
Some other newcomers have come up and launched ROMs in the last 2 weeks or so. That's a chance. Finally, a roadmap to some change.

1emrys1 said:
Xiaomi launched poco. It marketed it as a developer friendly device. And then it decided to give the device to some devs.
Who did they give it to? People who had previously worked on Xiaomi phones.
And so it happened. Vasishath, shahah_mik and akhilnarang got it. They definitely deserved it.
But with this Note 5 Pro is utterly f****d. Original development has almost completely stopped. Vasishath and shahah_mik brought up LOS and device trees for RN5 and now all they care about is poco.
Go check AOSIP Pie thread. Till 4th October, Akhilnarang was actively working on Pie for RN5 Pro. Now its over. Only derp kernel updates.
Maybe I'm ignorant but only jhenrique seems to be doing original development. Most others are pumping out xyz rom based on same source with same bugs.
I feel so bad. These devs definitely deserved a great phone but it came at the cost of Note 5 Pro. I don't think we will ever get proper Q roms and leave alone that, I don't think we'll ever get fully stable Pie roms like Oreo roms are stable right now.
RN3 launched with 5.1 and got super stable Nougat and Oreo. We started with Oreo and will remain on super stable Oreo custom roms. Other version roms have low chances of being as stable as Oreo.
I urge some developers to pick up LineageOs for this device. "Super glide butter flow remix" rom is nice but first we should have proper Pie code. Otherwise all roms will have similar bugs.
Click to expand...
Click to collapse
You've never had an abandoned device.
Delevoping and modding on our Redmi Note 5 is good enough, just open Redmi 4 Pro's Thread, a 100% valid phone with some high specs (launched 2 years ago), abandoned, why? Redmi Note 4 was released like 1 month later, before Redmi 4 Pro was a best-seller, after few months production of that phone was stopped, no official ROMs with regular support (i can remember like 2/3 developers), now it has two Pie ROMs, it's not enough? Abandoned from Xiaomi with Android 6.0 (it has the same specs of Redmi Note 4), bugs never fixed and zero consideration from main developers (just minor and REALLY GOOD developers helped users with that phone), on Redmi Note 5 you have official Pie ROMs, official LineageOS with weekly update, you will have (i think and i really hope for Xiaomi Image) official Android Pie Update, what else?, i think it's really enough

m666p said:
Firstly what pie bugs are you talking about?
And secondly, we have so many hard working devs here making kernels, recoveries and ROMs. New updates every day, join the telegram group...
Click to expand...
Click to collapse
What telegram group are you talking about? Can u share it? Thank you

Search for...
whyred updates official
And whyredcloud
And hers a few more in the screenshot.

m666p said:
Search for...
whyred updates official
And whyredcloud
And hers a few more in the screenshot.
Click to expand...
Click to collapse
I need the @iD not the names

sad but true thats whats up in the new phone hierarchy to manny new phones in a shortness of time

Letrix said:
I need the @iD not the names
Click to expand...
Click to collapse
You know that you can search for groups in the telegram app right...(?)
https://t.me/whyredupdates

What are you talking about? There are literally new rom updates everyday on telegram channel

N1ck474 said:
You've never had an abandoned device.
Click to expand...
Click to collapse
like most samsung devices redmi note 5 pro I way better than samsung devices with the exception maybe being the S5 or S3

there's some updates in telegram that never got to xda. telegram is the worst thing ever happened to xda community. tons of useful discussion buried under trollish and useless questions because of the lack of regulations, probably never again to be found. and if the group ever gets deleted, everything would be gone for good.

In telegram, questions are not allways replyed because it seem theres no devs. I think guys are compiling roms and this is all, if it is a bug in a rom, no one is able to solve it when you ask about the problem.
There s only 3 fully working roms i have tested ( LOS 15.1, PIE experience and MIUI ), the rest is a simple patch of these 3 roms and only upgrades are bugs.
I fully agreed with 1emrys1 post.

I'm considering to learn about developing a rom. Anyone know where to start? Because you can really depend on yourself

gingerboy92 said:
there's some updates in telegram that never got to xda. telegram is the worst thing ever happened to xda community. tons of useful discussion buried under trollish and useless questions because of the lack of regulations, probably never again to be found. and if the group ever gets deleted, everything would be gone for good.
Click to expand...
Click to collapse
Gotta agree on that

Telegram could be used to obtain feedback for some ROM, kernel or mod quickly, but as it is an instant messaging app, and people really lack any sense or knowledge about proper issue report (info on flashing procedure, current setup, methods to reproduce and logs) it just becomes a complete useless mess where important information is easily lost. Here, at least you can properly search for something and people's tendency to post something might be lower than on IM apps.
I would argue that the development for our device is gone, because there are still devs who are working on it, it might be just slower than usual but not necessarily worse.
On another note, the user base has to be more disciplined and just a bit more educated on how each one of us can contribute to a better development. Posting irrelevant and repetitive crap like fix this pls, this not works, give me links can iritate devs and drive them off, not to make them use another device, but to avoid posting their work with others.
Biggest fail on forums today, and I'm starting to see that all around XDA, is lack of respect for another user/dev/modder/contributor. People do not use the search function, which is the first and most important rule here, do not read the OP and features/bugs section, do not post proper issue report, and demand this or that, and the worst thing is when you point a finger at them and say - you are wrong that's not the way we do things here, they either don't (or pretend) understand and come back at you with insults behaving like they own this place.
EDIT: And there we go, just as I've posted this, someone made a thread in development section asking for kernAl with some features. Just the other day, a dude made a thread in the development section about Arnova's GCam (there is already "official/main" one in Themes and Apps) saying that this works on his device and something else doesn't etc.
I mean, I understand, not everyone has the knowledge about everything, but come one if you come to know about XDA you need to be at least informed about basics.