Database Users

[Q] Adding Eris to CyanogenMod Supported Devices?

Here's what Cyanogen said on the Official CyanogenMod Forums.
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
With this said, why don't we jump on the bandwagon and just join the CM team? Why don't we make this thing official (if we haven't tried already)? Just a thought, so don't kill me with your opinions. The Devs here are freakin' legit here and I'd like to see 'em do some of the work on the CM Team.

I trust the devs I download from because I follow their work. I don't need it to be "official". Besides, I like the personal touch and one-on-one support I get right here on the xda eris forum. And there's variety.
We could debate the politics of branding and what is CM and what is not CM. But the devs here disclose their sources, changes, known issues and brand their roms as uniquely their own while providing the support and updates. I don't think there's any confusion as to what is 'official' and what is not as the Android Police article referenced in CM's statement implies.

+1. The devs here are excellent, and the devs that base there ROMs on CM list them as "based" on CM not the official CM ROM. I'm not aware of any confusion that this has caused. I'm also not sure what creative constraints would be put on our devs if they went CM. I like the way they individualize the roms for thier personalities and their audiences. I also am not sure what benefit would come with being an "official" CM rom. Just my 2 cents.

Don't get me wrong, I'm not discrediting the Developers that cook these ROM by ANY MEANS whatsoever. They do incredible work with what they push, but here's what I'm saying. The CM ROMS are based off of Official CM Source Code, yes, but I think we'd be making it way easier on ourselves and the developers if we were an actual part of CyanogenMod. If we were a part of CM, then we'd get the CM ROMS as perfect as they can get and THEN the developers can add their own customization to a ROM based off of the Eris Release of CyanogenMod. They all are already doing the work that it would take to actually /BE/ a part of the CyanogenMod team, so why not get on with CyanogenMod so we can be official, and THEN the devs can customize and tweak ROMS they way they see fit?
Once again, absolutely NO discredit to the developers here, and I understand what it takes to keep these ROMS current and I am very appreciative of their work.

The CM ROMs that we have are either built from CM source or ported from the Hero builds already. I'm not really sure what this would give us other than maybe a "go team go" feeling and maybe a little more help than we already get. But the Eris and CDMA Hero are so similar, that doesn't matter much in my opinion as long as any Hero issues get worked out.
The CM buildbots are just building from source and posting the results, much like you would get if you ran EasyDev or did it manually. Now, there's a lot of work going on before that with the code, of course. But... That's what we use too.
I'm not against this at all. It just means that someone will have to 1) want to do it 2) have the time 3) convince Team Douche to let them in. I seem to remember that someone asked early on and the response was that we had to send them an Eris. This might have changed.
This comes up every so often. I guess one of us can find out what we would need to do at least...

Nothing would really change for the end user if we became official cm at this point. Basically one of the devs here that builds from source would submit their vendor tree to the cm source and they would be responsible for maintaining it just like we do now. The only real difference would be that it would get built by the cm build bot and nightly's would be released. I tweeted to cyanogen about getting my 2.2 tree in there along time ago when 2.2 was new but either I did it wrong(not a twitter person lol) or it just got lost in the many many tweets that go through cyanogens account. I never really pushed the issue more because of the extra time it would take me personally and it was just easier to work on my own schedule.
The only added benefit would be that maybe if there was an issue we could not fix then the cm team would take an extra look at our specific phone to help out but really since our phone is so close to the hero and it has official support they sort of fix most of our bugs anyway. I've personally always tried to give the cm team all the credit they deserve(which is alot) and I think the other dev's do the same.

Here's what Cyanogen posted up to www.cyanogenmod.com a week or so again. It looks like we'd need an interested dev here to stop by #cyanogenmod-dev on Freenode to start the process.
I think (and I use xtrSENSE, so I could be wrong) that a lot of people would like and "official" CM port for the Eris, just so they'd have "peace of mind" knowing they've got something "official."
And again, as we've seen mentioned in this post, it couldn't hurt to ask. Provided Team Douche doesn't actually want an Eris, we only stand to gain extra help on our ports.
Cyanogen said:
There’s been some recent talk about unofficial versions of CyanogenMod being created and released on sites like XDA, with large amounts of missing features and broken functionality, and I just wanted to talk about our position on this.
An “official” CyanogenMod version is one that uses our code review system, our source repository, and our mirror network. It should look, act, and feel like CM on any other device, and more importantly, it should follow our release schedules (which is a “when it’s ready” kind of thing, but we do plan our final/RC releases when we feel it’s ready). Most importantly, no major hardware functionality should be broken.
We want to see CM available for every device out there, and our infrastructure (and our developer community) is there for anyone to use. We spend a lot of time making new releases of Android backward-compatible with devices that are not ready for them, and we also spend much time making all of these (sometimes not so pretty) changes co-exist together without breaking other devices. The more eyes on your code, the better it will be.
That said, as much as we’d like it to be, the CMSGS project is not yet an official part of CyanogenMod. There are also a number of other unofficial ports out there which haven’t been submitted to us that we’d love to include. If you’re interested, stop by #cyanogenmod-dev on Freenode. If you didn’t get it from our mirror network or the CM forums, don’t expect it to be up to our standards.
The biggest thing to keep in mind when porting to a new device is to think about how your change is going to affect other devices. This is the biggest reason why we aren’t supporting Samsung devices other than the Nexus S yet. Don’t change hardcoded default values just to suit your device. Use the configuration options available, or add new ones with the original values as defaults. Do a build for another unrelated device after you make your changes (it helps to have another device to test with, of course) and verify it as well. Android was made for this, so do it right.
Like I’ve said so many times before, CyanogenMod is all about the community. And our community can help you too. I’d love to see more of these ports contributed to the project- it’s only going to make things better. We’ve grown from just a mod to what I’d call an “Android distribution” and we need to keep our standards high.
Click to expand...
Click to collapse

Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft

hallstevenson said:
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
Click to expand...
Click to collapse
+1 10 char......

A dev would have to maintain the device and be committed to building it up, like Darchstar was (is?) for the Hero CDMA. It really all depends on the Dev/Devs for the device, for example I've seen Cyanogen say in his twitter that he would also like to see the Dream/Saphhire continue to be developed for but no one has stepped up to maintain it. I can also only imagine that there are some qualifications for someone to maintain a device. Here is a list of the current maintainers for the devices
https://github.com/cvpcs/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn

Yeah, I can understand that. That's all I was saying, though. If they were doing all of the same work anyway I just thought it would be nice to have. I also didn't know if anyone had pursued this in the past, but seeing as how Conap had already tried I think I'm good with that. I also have no problems running the unofficial ROMs, just so you know. Thanks, guys!

It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.

Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
the way i do it is best for me,,and seems to be going fine,,, the cm7 ports have been alot better then the froyo ,, and alot faster ,, look how long it took the froyo camera to work,, gb the camera works outta the box,,

Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)

gnarlyc said:
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
Click to expand...
Click to collapse
I thought it was a girl

tazzpatriot said:
I thought it was a girl
Click to expand...
Click to collapse
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0

refthemc said:
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
Click to expand...
Click to collapse
nope still a girl
http://www.youtube.com/watch?v=vwIa2S0YQs4

FYI: http://twitter.com/cyanogen/status/45246447385452544
@cyanogen said:
@Algamer we don't officially support the eris, it would be nice if someone doing the porting joined up with us though
about 8 hours ago via web in reply to Algamerhttp://twitter.com/Algamer/status/45235578886815744http://twitter.com/Algamer/status/45235578886815744
Click to expand...
Click to collapse

I think OUR devs are doing just fine. Why change now?
wildstang83

wildstang83 said:
I think OUR devs are doing just fine. Why change now?
wildstang83
Click to expand...
Click to collapse
Our devs are doing more than just fine, especially considering the amount of development we STILL have going on even though the Eris was a short-lived device that was EOL'd after like 8 months, was mid-range compared to the original Droid, and is a pretty niche device being MDPI on Verizon...
Why change now? That's a good question and I don't have a great answer. Like some have said on this post, maybe we'll get more support with bugs, etc. Additionally, a lot of the users here on XDA are looking for consistency. Since many who read and post here lack the skill set to do any meaningful ROM development themselves, they rely on the kindness of willing devs. However, devs will often add their own "personal touches" to their ROMs, which is great and well within their right to do. Having said that, many users are just looking to for something where they know, "Oh OK, so this is the base CM ROM that's officially distributed."
Personally, I don't care whether we have an "official" CM build or not for the Eris. I'm pretty reserved when it comes to ROMs for everyday use and am still using xtrSENSE as my default. The only reason I posted up cyanogen's recent tweet was to show that cyanogen himself is well-aware of the Eris development, is personally following the Eris ports, and is open to a partnership. My hope is that, by bridging communication, I am doing my part in helping to expose any possible mutual benefit (Eris XDA devs, ROM end-users, and Team Douche at CM) that could be gained by considering an "official" build. Ultimately, I understand that this is a decision that can only be made by the devs and also, not fulling understanding ROM development or having the skill set myself, I believe they are in the best position to make that decision. Like I said, I'm merely acting as a messenger, bringing this communication to light on our forum.

Should ROM devs focus on stability or progress?

Since I don't think I can re-phrase myself in a better way, I'll just quote myself from a different topic:
CrisR82 said:
The more I look at it, the more I'm convinced that the problem is the ROM devs themselves - seems like most rush ahead and as soon as a new Android version pops out - scrap bug-fixing what they made so you can have a fully stable version and move straight to a new one, bringing all the old bugs along with a ton of new ones.
I have to be honest, after some replies and PMs I decided to use dual-boot and try some other stuff...and I'm convinced the ROMs that can be classified as "stable" are less than 5...total. All others seem to have some type of issue that can screw over a person's daily life in one way or another.
Am I the only one that feels this way?
Click to expand...
Click to collapse
I would really like to see what you guys think on the subject: should developers slow down [maybe skip a version] to provide a genuinely stable ROM, or leap ahead for the new version and patch it out to a "usable" degree?

Most ROM developers are pretty much unpaid volunteers.
They should do whatever they want.
If you do the ROM, you get to choose.
It all shakes out one way or another.

^^^^^
Exactly. What a presumptuous thread. Also, why do you even need a 2nd thread to pose this question given your ongoing thread about not dissimilar issues ?

mikereidis said:
Most ROM developers are pretty much unpaid volunteers.
They should do whatever they want.
If you do the ROM, you get to choose.
It all shakes out one way or another.
Click to expand...
Click to collapse
I already know that...but here's the thing - noone makes a ROM him himself/herself only. Most people make a ROM and share it for others to use, so while the final decision is ALWAYS up to the individual dev, it's still good to know what the community prefers (or at least it would've mattered to me if I was a dev).
If we go with the logic that community opinion doesn't matter at all, we might aswell get rid of all topics that are not bug reporting or guides.
MistahBungle said:
^^^^^
Exactly. What a presumptuous thread. Also, why do you even need a 2nd thread to pose this question given your ongoing thread about not dissimilar issues ?
Click to expand...
Click to collapse
Because it has little to do with the other thread?
"Share your first experience with custom ROMs" - "Do you think custom ROMs are being made and moved on from too fast?"...see the difference?

AFTER A BIG BANG a STABLE EARTH WAS FORMED.. If u want a pure stable ROM u have to progress. So its better we leave the DEVs work on it. Moreover its free be happy... We are not supposed to judge them what they focus on...

CrisR82 said:
I already know that...but here's the thing - noone makes a ROM him himself/herself only. Most people make a ROM and share it for others to use, so while the final decision is ALWAYS up to the individual dev, it's still good to know what the community prefers (or at least it would've mattered to me if I was a dev).
If we go with the logic that community opinion doesn't matter at all, we might aswell get rid of all topics that are not bug reporting or guides.
Click to expand...
Click to collapse
OK, sure.
But I don't like the statement that "the problem is the ROM devs". It's criticism, and I think criticism is better directed at parties that are doing it for commercial purposes where I/we are paying customers, such as Google or the phone OEMs, or even CM Inc and MIUI Inc.
For popular phones there are a variety of ROMs. Some are more stable (often stock based) and many are more bleeding edge.
Even Google is more bleeding edge with AOSP on Nexus devices. How many times have we heard of longstanding AOSP Nexus bugs, such as BT issues ?
People slam the phone OEMs and carriers for taking so long to provide updates. Yet those bleeding edge updates, even from Google are often very buggy.
I'm happy to have a variety of choices. Let the chips fall where they may. Unless I've contributed financially to a ROM dev, I'm not generally going to ask him/her to follow any wishes I have about stability or leading edge features. (I've made a few exceptions where a popular ROM has nasty bugs that impact the users of my commercial apps.)
I have 20 phones to do testing and development of my apps. I go into these XDA forums and look for the most popular ROMs. Sometimes I want the latest to do KitKat testing, sometimes I want the most popular, and sometimes I want something stable (often stock based, as it turns out, or based on CM10.2 for example.)

i think first they should progress a bit then make that much part stable and move son

mikereidis said:
OK, sure.
But I don't like the statement that "the problem is the ROM devs". It's criticism, and I think criticism is better directed at parties that are doing it for commercial purposes where I/we are paying customers, such as Google or the phone OEMs, or even CM Inc and MIUI Inc.
For popular phones there are a variety of ROMs. Some are more stable (often stock based) and many are more bleeding edge.
Even Google is more bleeding edge with AOSP on Nexus devices. How many times have we heard of longstanding AOSP Nexus bugs, such as BT issues ?
People slam the phone OEMs and carriers for taking so long to provide updates. Yet those bleeding edge updates, even from Google are often very buggy.
I'm happy to have a variety of choices. Let the chips fall where they may. Unless I've contributed financially to a ROM dev, I'm not generally going to ask him/her to follow any wishes I have about stability or leading edge features. (I've made a few exceptions where a popular ROM has nasty bugs that impact the users of my commercial apps.)
I have 20 phones to do testing and development of my apps. I go into these XDA forums and look for the most popular ROMs. Sometimes I want the latest to do KitKat testing, sometimes I want the most popular, and sometimes I want something stable (often stock based, as it turns out, or based on CM10.2 for example.)
Click to expand...
Click to collapse
I think people are misinterpreting my words...I'm not saying devs are terrible, bad at their work or anything like that, I'm sharing a thought on why I think most ROMs are not stable enough for everyday use and made a poll to see if others think this too, or simply put "a topic where people can show preference", I never once said "you should listen to me" or "do it how I say because it's better". While I personally don't have any use for custom ROMs in my daily life, I'm always happy to see more and more people making ROMs, stable or not.
However, I will say one thing and back it up forever - "it's not commercial" is not a valid reason not to criticize something. Any forum or work (coding, art etc.) is fully subject to criticism. So to people telling me "you cant criticize developers because they do it for free" - yes I can (not to mention it's my real life job)...it's called "having a point of view", if you agree or don't agree - that's up to you.
In short - this is a topic to see points of view on this, NOT to force anyone into changing his/her way of work. So stop treating it like one. It's how forums work - you open a topic to discus something.
P.S. yeah, now after re-reading it, I might've picked wrong words when I said "the problem are the devs"..."problem" in particular doesn't seem like an appropriate word for it...I apologize if I offended any dev with it.

Devs should continue to do whatever the hell they want to do however the hell they want to do it & ignore people like you.
Opinions & arseholes.

In my opinion, in order for rom makers to gain loyal users, they should prioritize stability while making progresses.
Sent from my GT-I9100 using Tapatalk

I also prefer stability over features.

@CrisR82 +1 for posts.
Which ROM You now using?
And with which you feel most satisfied?

dinos3 said:
@CrisR82 +1 for posts.
Which ROM You now using?
And with which you feel most satisfied?
Click to expand...
Click to collapse
I'm using the Samsung stock ROM (Spain region) since my job requires me to do so, but I really like MIUI for its awesome stability and customization (though I have a feeling they'll never update the S2 to 4.2 or higher)...but I also like CyanogenMod 10.1 (the stable build) for the slight performance increase (and I would've probably kept it if it wasn't for the unfixable MHL and other Samsung closed source things that don't work).
I'm also keeping an eye on Omni and I plan to give it another try once it reaches a more stable stage since it fixes some graphics issues on the S2 GT-i9100.

CrisR82 said:
I'm using the Samsung stock ROM (Spain region) since my job requires me to do so, but I really like MIUI for its awesome stability and customization (though I have a feeling they'll never update the S2 to 4.2 or higher)...but I also like CyanogenMod 10.1 (the stable build) for the slight performance increase (and I would've probably kept it if it wasn't for the unfixable MHL and other Samsung closed source things that don't work).
I'm also keeping an eye on Omni and I plan to give it another try once it reaches a more stable stage since it fixes some graphics issues on the S2 GT-i9100.
Click to expand...
Click to collapse
Nice...
This http://forum.xda-developers.com/showthread.php?t=2562055 4.4.2 ROM?

dinos3 said:
Nice...
This http://forum.xda-developers.com/showthread.php?t=2562055 4.4.2 ROM?
Click to expand...
Click to collapse
Yes, that's the Omni one I used

CrisR82 said:
Yes, that's the Omni one I used
Click to expand...
Click to collapse
If you try it, let impressions. I can't even find a rom that suits me...

dinos3 said:
If you try it, let impressions. I can't even find a rom that suits me...
Click to expand...
Click to collapse
I already have and I posted my thoughts on it here: http://forum.xda-developers.com/showthread.php?t=2580635

dinos3 said:
If you try it, let impressions. I can't even find a rom that suits me...
Click to expand...
Click to collapse
you can try slimsaber 4.4.2 by FJ. good battery,stable for me and ART working on all my apps.:good:

[Q] DUAL CAMERA SUPPORT - GT-i9505

Firstly, I'm NOT a Developer - I want to make that very clear
I have been trying to get data/info about what ever happened to the Original Samsung Galaxy S4 'TouchWiz'
Camera feature/ability to be able to 'Simultaneously' record videos (not talking about taking pictures here)
with both the front and back cameras on the phone.
This question has been asked before by a very very very small number of people on the net including in XDA
developers forums, However these questions only have been asked on forums relating to NEXUS phones/devices.
When i originally bought my S4 (second hand) i used the recording feature, i absolutely love it, i think it it brilliant,
it is one of the reasons why the S4 has such appeal for me.
I later upgraded to CyanogenMod, because of privacy concerns relating to Samsungs Involvement with the NSA over
their KNOX security.
The OS seemed fine to me, but this security concern was the basis of WHY i moved over to CyanogenMod.
Then i found out, that CyanogenMod does NOT Support the Dual Camera feature.
I contacted Samsung, and they told me that the Camera app was not really an app at all, but was in fact part of the OS itself.
But remember, the Genuine Samsung Galaxy is actually model number GT-i9500, which uses the Exynos Chip, unlike the Samsung Galaxy S4
variant known as the S4 LTE GT-i9505, which uses the Qualcom Chipset.
It has also been said by some XDA developers, that Samsungs 'TouchWiz' is not Open Source, it is Closed Source.
Well belonging to the company, this is no surprise, I'll also bet that it is probably Patented as well.
I say, so what ?, CyanogenMod does NOT need the original samsung 'TouchWiz' code, it only needs to know the HardwareSpecs of the Qualcom
Chip, then programming/developing can begin.
The S4 is already Superceeded by the S5 (and any possible variant(s) of that), i feel that the GT-i9505 is getting left out of the picture.
Are there any answers to this mystery ???

The7Suggester said:
Firstly, I'm NOT a Developer - I want to make that very clear
I have been trying to get data/info about what ever happened to the Original Samsung Galaxy S4 'TouchWiz'
Camera feature/ability to be able to 'Simultaneously' record videos (not talking about taking pictures here)
with both the front and back cameras on the phone.
This question has been asked before by a very very very small number of people on the net including in XDA
developers forums, However these questions only have been asked on forums relating to NEXUS phones/devices.
When i originally bought my S4 (second hand) i used the recording feature, i absolutely love it, i think it it brilliant,
it is one of the reasons why the S4 has such appeal for me.
I later upgraded to CyanogenMod, because of privacy concerns relating to Samsungs Involvement with the NSA over
their KNOX security.
The OS seemed fine to me, but this security concern was the basis of WHY i moved over to CyanogenMod.
Then i found out, that CyanogenMod does NOT Support the Dual Camera feature.
I contacted Samsung, and they told me that the Camera app was not really an app at all, but was in fact part of the OS itself.
But remember, the Genuine Samsung Galaxy is actually model number GT-i9500, which uses the Exynos Chip, unlike the Samsung Galaxy S4
variant known as the S4 LTE GT-i9505, which uses the Qualcom Chipset.
It has also been said by some XDA developers, that Samsungs 'TouchWiz' is not Open Source, it is Closed Source.
Well belonging to the company, this is no surprise, I'll also bet that it is probably Patented as well.
I say, so what ?, CyanogenMod does NOT need the original samsung 'TouchWiz' code, it only needs to know the HardwareSpecs of the Qualcom
Chip, then programming/developing can begin.
The S4 is already Superceeded by the S5 (and any possible variant(s) of that), i feel that the GT-i9505 is getting left out of the picture.
Are there any answers to this mystery ???
Click to expand...
Click to collapse
What mystery? That Cyanogen doesn't offer the ability to record with the front and back cameras at the same time?
That's not a mystery. It's that only 1 person out of a million would ever want to do that so no one is devoting their development time to integrating that feature.

Dual Camera Support - i9505
Skipjacks said:
What mystery? That Cyanogen doesn't offer the ability to record with the front and back cameras at the same time?
That's not a mystery. It's that only 1 person out of a million would ever want to do that so no one is devoting their development time to integrating that feature.
Click to expand...
Click to collapse
I'm afraid I'm not completely sure i know what you mean?
Do you mean that there would only be 1 Developer out of a million who would use this feature, and therefore no support would be actioned for this ?
OR do you mean that in your opinion there are hardly any people who would own a phone like the S4 that would want to use this feature.
Why would anyone *NOT* want to do this. It's fun for one thing.
Maybe I've made a mistake but, i thought that one of the things that XDA devs were all about, was trying to fix or patch areas on OS's
where the mainstream had overlooked, and especially about importing and bringing new features about to free OS's such as CyanogenMod.
Could you please clarify i bit more carefully about, this.

Skipjacks said:
What mystery? That Cyanogen doesn't offer the ability to record with the front and back cameras at the same time?
That's not a mystery. It's that only 1 person out of a million would ever want to do that so no one is devoting their development time to integrating that feature.
Click to expand...
Click to collapse
You are pretty close minded even though I don't use that feature myself.
V-bloggers love using that feature.
But I do agree with you. AOSP is suppose to provide a clean experience

Dual Camera Support - i9505
Thank you for backing me up on this issue

MrAndroid12 said:
You are pretty close minded even though I don't use that feature myself.
V-bloggers love using that feature.
But I do agree with you. AOSP is suppose to provide a clean experience
Click to expand...
Click to collapse
The insults aren't needed.
I stated a fact. There is not enough desire for this feature for developers to devote time to coding it instead of coding something else that is more heavily requested.
If there were a strong desire for it developers would be looking to fill that need.
But there are alternate methods to getting this feature...like using touchwiz. So there aren't many devs who want to spend time coding a little used feature that is already available elsewhere. Especially one they don't intend to use themselves, and not when there are more popular mods that people are asking for in droves like gps fixes and updated kernels and theme manager fixes.
Keep insulting me if you like for telling it like it is. But this is the simple reason why this feature hasnt been widely developed.
If the OP really wants to do this on an AOSP rom, he can learn how to develop. Many many many people here learned how to code specifically to create a feature they wanted.

Skipjacks said:
The insults aren't needed.
I stated a fact. There is not enough desire for this feature for developers to devote time to coding it instead of coding something else that is more heavily requested.
If there were a strong desire for it developers would be looking to fill that need.
But there are alternate methods to getting this feature...like using touchwiz. So there aren't many devs who want to spend time coding a little used feature that is already available elsewhere. Especially one they don't intend to use themselves, and not when there are more popular mods that people are asking for in droves like gps fixes and updated kernels and theme manager fixes.
Keep insulting me if you like for telling it like it is. But this is the simple reason why this feature hasnt been widely developed.
If the OP really wants to do this on an AOSP rom, he can learn how to develop. Many many many people here learned how to code specifically to create a feature they wanted.
Click to expand...
Click to collapse
I didn't really back him up or said you were an insult.
I said that AOSP rooms should be free of non Google modifications.
But I am just telling you again that there are probably more than a million in one desiring for that feature because some people like to v-blog
Sent from my GT-I9505 using Tapatalk

Skipjacks said:
The insults aren't needed.
I stated a fact. There is not enough desire for this feature for developers to devote time to coding it instead of coding something else that is more heavily requested.
If there were a strong desire for it developers would be looking to fill that need.
But there are alternate methods to getting this feature...like using touchwiz. So there aren't many devs who want to spend time coding a little used feature that is already available elsewhere. Especially one they don't intend to use themselves, and not when there are more popular mods that people are asking for in droves like gps fixes and updated kernels and theme manager fixes.
Keep insulting me if you like for telling it like it is. But this is the simple reason why this feature hasnt been widely developed.
If the OP really wants to do this on an AOSP rom, he can learn how to develop. Many many many people here learned how to code specifically to create a feature they wanted.
Click to expand...
Click to collapse
OK, Fine your point is now made.
But just remember, at least on the Samsung series of phones, the S1, S2, and S3 did NOT have this feature, the S4 was the first phone by Samsung to have this feature, and the S5 is now officially the 'Flag Ship' phone for Samsung.
As with continued development of multi-media standards, i.e. 4K for a start now available on the Sony Experia Z2 phone for one,
the demand for ever increasing video recording features and abilities will continue to increase, so it would not really surprise me, if later
on this feature were to start appearing in later makes & models of phones down the line.
You really have to consider what % of people will even know or find out about free AOSP OS's like CyanogenMod, for one thing,
and even then what % of those people will even upgrade to such OS's.
The demand for Dual Camera Video Recording will probably go up and up amongst the general populace of phone users.
Right now the demands are other things, things like theme development, bug fixes, etc.
Having ones 'foot-in-the-door-now' so to speak, could be a worth while investment for later on.
Sure the demand NOW is very little, but if devs wait till later on to do this, then when the demands get bigger (presumably with newer
models of phones), devs will be flooded with all sorts of bugs to have to sort out on all the different OS types and versions,
- while the demand is great -, thats a lot of pressure on devs, which would also slow down development in other areas.
I think now, i have made my point. While this does sound purely like an argument just so i can gain something for myself - it's for ALL other people. I dont and cannot claim to represent what people in the world who own phones want. But logic sais that if i want this, then there are lots of people in the world who want this, just because XDA devs have not heard of such people, does not mean that they dont exist.
Besides I'm talking about being able to record video with 2 cameras at the same time, is that really such a grand feat ?,
Hell the XPrivacy program i use that XDA devs made was a Major Feat, Dual Camera support cant be THAT difficult to implement.
As for your other comments:
"But there are alternate methods to getting this feature...like using touchwiz." - well i think i already explained why i went to CyanogenMod in
the first place.
"If the OP really wants to do this on an AOSP rom, he can learn how to develop. Many many many people here learned how to code specifically to create a feature they wanted.[/QUOTE]" - Actually when i was a kid i programmed BASIC, but i have brain damage due to seizures affecting
my long and short term memory, so sorry, your claim that any OP can program is incorrect.
My Point Made

Your point made? I still don't even know what your point is.
Look, I get that this feature is important to you. But that does not mean that it's important to a large percentage of everyone else.
The Samsung AirView features are far more requested to be ported to AOSP roms but even then the demand is so small compared to the demand for things like floating windows, hover notifications, theming fixes, Knox workarounds, etc. No devs even want to tackle the AirView features, which get asked about at least once a week on the various S4 forums, because there isn't enough demand. And there's even less demand for simultaneous duel camera use.
In the years I've been here this is the first time I've ever heard of a request for simultaneous duel camera use. And I read nearly every post here nearly every day. So while I appreciate that this feature is something that's really important to you, it's just not in high demand.
And there is zero incentive to develop it now before it becomes high demand later. There's no money to be made in rom modding. If people suddenly want this feature down the road it'll get developed then. There is no early investment incentive in this. Phone modding is a hobby. Like fishing or model trains. We do it for fun, not for money.
As for the difficulty of simultaneous duel camera use...yes, it could be THAT hard to develop. It's not just an app. Something like this that controls 2 pieces of hardware at once would have to be coded into the kernel. And while kernel tweaking is fairly common, completely new kernel features are scarce because it's a very limited number of people who can do it. (And the stock kernel is closed source so it's not like the code can just be lifted from the Samsung version)
Second, once you had the ability to do it in the kernel you'd need an app that could take advantage of the support. You couldn't use the stock camera. You'd need something new. So that's a second layer of development. So this isn't a quick 1 hour project. It's a lot of hours that someone would have to put into it, for something that isn't being asked for very much.
This is the reason it's not being done yet. Don't be mad at me for giving you the honest answer.

Skipjacks said:
Your point made? I still don't even know what your point is.
Look, I get that this feature is important to you. But that does not mean that it's important to a large percentage of everyone else.
The Samsung AirView features are far more requested to be ported to AOSP roms but even then the demand is so small compared to the demand for things like floating windows, hover notifications, theming fixes, Knox workarounds, etc. No devs even want to tackle the AirView features, which get asked about at least once a week on the various S4 forums, because there isn't enough demand. And there's even less demand for simultaneous duel camera use.
In the years I've been here this is the first time I've ever heard of a request for simultaneous duel camera use. And I read nearly every post here nearly every day. So while I appreciate that this feature is something that's really important to you, it's just not in high demand.
And there is zero incentive to develop it now before it becomes high demand later. There's no money to be made in rom modding. If people suddenly want this feature down the road it'll get developed then. There is no early investment incentive in this. Phone modding is a hobby. Like fishing or model trains. We do it for fun, not for money.
As for the difficulty of simultaneous duel camera use...yes, it could be THAT hard to develop. It's not just an app. Something like this that controls 2 pieces of hardware at once would have to be coded into the kernel. And while kernel tweaking is fairly common, completely new kernel features are scarce because it's a very limited number of people who can do it. (And the stock kernel is closed source so it's not like the code can just be lifted from the Samsung version)
Second, once you had the ability to do it in the kernel you'd need an app that could take advantage of the support. You couldn't use the stock camera. You'd need something new. So that's a second layer of development. So this isn't a quick 1 hour project. It's a lot of hours that someone would have to put into it, for something that isn't being asked for very much.
This is the reason it's not being done yet. Don't be mad at me for giving you the honest answer.
Click to expand...
Click to collapse
"And there is zero incentive to develop it now before it becomes high demand later. There's no money to be made in rom modding. If people suddenly want this feature down the road it'll get developed then. There is no early investment incentive in this. Phone modding is a hobby. Like fishing or model trains. We do it for fun, not for money."
Well i think that everything i said above are _VALID POINTS_ points i would have though would have been important enough for XDA devs to consider.
It seems to me that there simply is TOO MUCH demand on the XDA devs in general.
"There's no money to be made in rom modding."
As for 'INVESTMENTS' - I did _NOT_ mention business or money making at all - I meant your investment in coding/programming, your time put into work.
"There is no early investment incentive in this. Phone modding is a hobby. Like fishing or model trains. We do it for fun, not for money."
Well, i guess i will have to turn to people i CAN pay money to, to make it more 'worthwhile' for minority's such as myself, if not a dev.
Ben.

The7Suggester said:
Well, i guess i will have to turn to people i CAN pay money to, to make it more 'worthwhile' for minority's such as myself, if not a dev.
Ben.
Click to expand...
Click to collapse
Nothing wrong with that! Try to find a group of likeminded people who want this on AOSP and put a bounty together to offer to a developer.

Welcome to the Exodus

Hello Guys,
welcome to the world of Team-Exodus.
What is Team-Exodus ?
We are a small group of entusiasts that like to learn more about Android and the Android-ROM developement.
We aren't exactly beginners But there is still room to learn more (you never end learning).
What is Exodus-Rom ?
Maybe, we better should start, what Exodus-Rom isn't: It isn't a (semi)professional mainstream ROM like CyanogenMod,AOKP or similar Roms. We don't focus on buzzword features, nor are we into "bling bling" options. We don't need a "change clock color" option, just because we can do it. These are "low hanging fruits", something nearly everybody can do, who has a computer to compile Android.
So what is Exodus-Rom, what is our focus on ?
We mainly focus on learning how things can be done. We are more into "quality over quantity". We prefer to have 4 or 5 real good and stable working features and not 20-30 features that work... somehow... sometimes...
We want performance, a fast, smooth fluid UI, a real good user experience, not a overbloated kang rom.
For instant that's the main reason why we currently don't have a Marshmallow Rom online, but I will give you a little more information regarding Exodus-6.0 (marshmallow) later.
But before that, who are we, who is "Team-Exodus" ?
The core team of "Team-Exodus" consists of the following guys:
@PrimeDirective - Dave, a very talented developer from the US, founder and Team Leader of Team-Exodus, specialist in App developement (for instant our Exodus Updater or the Drop Wallpaper App) and also our specialist for in deep functionalities of the Android Rom (like a complete rewritten Navbar customization). He currently uses bacon (Oneplus One) and Flounder (Nexus 9) for developenemt
 @Raja.M - Raja, a real nice guy from India, he is our java specialist, he started Android developement something link 6 month ago but his knowledge is fast growing. He developes on the bacon (Oneplus One)
 @TheCrazyLex - Alex, a kernel specialist from germany, he joined Team-Exodus like 3 month ago, mainly responsible to optimize and unify our kernels where possible. He also uses the Bacon (Oneplus One) as developement device.
 @usmcamgrimm - Adrian, our graphics and theme specialist. Beside his amazing wallpapers, he is also responsible for all our LGE G3 devices. He mainly developes on the VS985.
 @Martin_Ro - myself, Martin, also from germany, mostly responsible for the server with the build system, gerrit and download page. I'm also developing here and there if I find some time as I'm a married guy with to young boys. I'm developing on shamu (Nexus 6).
But beside this core team, there are a lot more ppl that help us making the Exodus Rom as amazing as possible, I will add some more of them step by step
So, now, back to Marshmallow and why it takes so much more time to bring an Exodus-6.0 to you guys:
For this to understand, you need to know more about where we come from.
On late 2014 we (Dave and Me) parted from VanirAOSP (that wasn't really AOSP but also used CM as base at that time btw) because we feeled like it started to get more and more into that mainstream "feature count is everything".
With 5.1 we started to directly use CyanogenMod (cm-12.1) as base, but was somewhat annoyed by upcomming issues because they used their open source branch as testfield for unfinished stuff, so for 6.0 we decided to go as near as possible back to strict AOSP.
But a matter of fact is: With strict AOSP you aren't able to support every device, and not as many devices as we want to support. So we have had to make some decisions and try some stuff. In the end we started developing Exodus-6.0 with a Mixture of strict AOSP and CAF as base, with the really amazing wide support of CyanogenMod regarding devices.
But with this, we got back to one of our main concerns: CyanogenMod is doing a fantastic job regarding device support (nobody can beat them in that department) but they are cluttering their stuff more and more. In the past few month, they started to create their own SDK, their own framework. And their SDK started to grow like a octupus, sticking his arms into every aspect of android. But we don't want to use their sdk, so we needed to remove it from everywhere.
And that was, what took so long. We wanted the device-tree and their hardware layer, but not their feature, and for sure not their SDK. And removing that stuff from everywhere inside the device-trees and Hardware layer.
Also we needed to use some of their code stuff in various places to make the connection between our AOSP/CAF based ROM and their hardware/device stuff.
So that took us nearly a month to finish up, but now we have first working experimental builds for bacon, shamu and VS985 so we can go into the real developing stuff.
There is still a lot to do (bring back all the features we want to, make the rom that fluid that you might be used to from EXODUS-5.1 etc.) But the real hard part is done now and we are way neared to a first public beta. Depending on the time Dave can find for Exodus (he is really really busy currently because of a new job), we expect to have a public beta by the end of the month...
So stay tuned and be patient

Made sticky

Hello! I enjoyed the 1/2 of the core team's and the new teams work since JB VanirAOSP to Exodus .
Just wondering, it would be cool to say what you do to seperate you guys from the rest. I know you guys build with jdk8 instead of jdk7 for the lollipop builds and use Linaro with some optimization flags.
I'd like to know if you do more than that and also I am wondering how JDK8 especially helps with optimization.

If you need a tester for bacon. I'm here very big fan of 5.1.

Nice to hear the updates... waiting patiently...

Sounds like the beta will become a christmas present.
Gesendet von meinem Nexus 5 mit Tapatalk

big fan/user of Exodus 5.1 on falcon. out of all the LP ROMs i've tried this has to be one of the most stable and lean ROMs out there. love the amount of essential customization catered here and skipping of cliche features that no one bothers to use (atleast me).
big thanks to @sachoosaini for introducing me to the ROM.

Well here it goes on
@PrimeDirective always a great human and great developer who supported Falcon despite the fact that i can never able to contribute the device to you. I find a best buddy out there who will always be my friend... Now @koshikas thanks Dave for supporting this phone, i never did anything for exodus.. But i am committed for future. If Dave continues the journey for exodus i will be with him in all way... Well what he told me around 6-7 months back is now coming to the real world. Now they support falcon or not. But I am honored by Dave for being there with all the silly questions people ask in community, falcon has great life indeed now its upto the team they develope for it not. I will donating device as soon as I am getting my salary which i am for sure going to get soon..... Wish Luck to exodus....6.0 is on the horizon

If you need a tester...
Hey, if you guys need an experienced tester for bacon, look no further. :good:

AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I'm with this guy

Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on

Coolkid90 said:
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Click to expand...
Click to collapse
Hm, ok, might be, because english is not my mother language, but for me this sound like "too much drugs and not enough sleep"....

Oh, and by the way:
we just prepared the open source manifest so you can start contribute
I will write a short Facts thread for Exodus-6.0 so you know how to build, and what we changed regarding device-support...

Excelente

Looking real forward to Exodus MM!

sir I am with you here.
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I m new here and wish to get some knowledge from senior member.

Thanks for this great rom

Exodus seems cool... hyped for MM release!

delete : found it
"err on the side of kindness"

Hi guys
Only to keep you informed: We started publishing official release builds for Exodus-6.0.
Look into your devide Android Developement sections for more information or on our g+ community: https://plus.google.com/communities/106801227383087889476

[PETITION] Ask OnePlus to implement Project Treble on currently supported devices.

Project Treble, as you've heard, is an amazing new update structure for Android devices and also can affect the speed and stability of Android development.
OnePlus has decided not to implement the current OnePlus devices with Project Treble, and they haven't given an explanation as to why they decided not to.
Project Treble can help the 3/3T as they are almost out of the OEM support days. If they do implement this, you may be looking at Android P ROMs for your device within days of the release of the AOSP commits.
Stand UP for your device and our responsibility as the community should be to bring support for our device for as long as possible. If OnePlus implements this, our device will be future proof for the aeons to come.
Your vote counts.
Change Org - https://www.change.org/p/carl-pei-w...-ask-oneplus-to-support-project-treble-in-oos
Do your part as a OnePlus 3/3T user and VOTE!

What's your drug of choice?

suraj.das said:
What's your drug of choice?
Click to expand...
Click to collapse
What do you mean?

thes3usa said:
What do you mean?
Click to expand...
Click to collapse
He means that you must be high on something to think OP will give this petition any consideration. I don't think they will either, but I signed it anyway. It'd be nice if they did. It would certainly bolster consumer confidence in OnePlus if they supported such a game changing feature.

HampTheToker said:
He means that you must be high on something to think OP will give this petition any consideration. I don't think they will either, but I signed it anyway. It'd be nice if they did. It would certainly bolster consumer confidence in OnePlus if they supported such a game changing feature.
Click to expand...
Click to collapse
This really isnt that much of a game changer really. Dont let those on the portal make you think other wise. The rom developers are laughing at him as he has no real idea of how this is gonna work. In the end it will have 0 effect on roms or OEM updates.

zelendel said:
This really isnt that much of a game changer really. Dont let those on the portal make you think other wise. The rom developers are laughing at him as he has no real idea of how this is gonna work. In the end it will have 0 effect on roms or OEM updates.
Click to expand...
Click to collapse
How so?
Sent from my ONEPLUS A3000 using Tapatalk

HampTheToker said:
How so?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Well the only this this allows is updated things from the SOC manufacturers. Making things for the oem faster, if they ran aosp. But they dont. Updates will be just as long If not longer now due to this. Why you ask. Well now the OEM has to build their entire OS completely differently now. This is from OEM changing the entire OS framework as well as every file google makes.
As for custom roms. Well this really means nothing as most custom roms are already on newer patches then even what google has pushed to aosp.

zelendel said:
Well the only this this allows is updated things from the SOC manufacturers. Making things for the oem faster, if they ran aosp. But they dont. Updates will be just as long If not longer now due to this. Why you ask. Well now the OEM has to build their entire OS completely differently now. This is from OEM changing the entire OS framework as well as every file google makes.
As for custom roms. Well this really means nothing as most custom roms are already on newer patches then even what google has pushed to aosp.
Click to expand...
Click to collapse
What? What even are you talking about? Project Treble is a huge step for AOSP ROM development.
Read here - https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/
Project Treble can bring quicker and more stable ROMs to devices faster and more efficiently.

HampTheToker said:
He means that you must be high on something to think OP will give this petition any consideration. I don't think they will either, but I signed it anyway. It'd be nice if they did. It would certainly bolster consumer confidence in OnePlus if they supported such a game changing feature.
Click to expand...
Click to collapse
OnePlus's rule is to listen to their community yeah? With the petition over 5000 signatures and the link booming on r/OnePlus, it'll make them look bad if they ignore the petition.

thes3usa said:
What? What even are you talking about? Project Treble is a huge step for AOSP ROM development.
Read here - https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/
Project Treble can bring quicker and more stable ROMs to devices faster and more efficiently.
Click to expand...
Click to collapse
Please. First of getting aosp to boot on that device is not that big of a deal. Rom devs do it all the time. The only reason those devices are left behind is because developers refuse to work with their chipset.
So explain how something only concerns the SOC manufacturer and the OEM will make roms faster?
If you really thiink this will make the OEMS update any more then they already do then you are sadly mistaken.
Thats the one that I mentioned that the devs are laughing at.
Also if you follow the thread linked you will see that things are still broken and causing issues. Nothing new.
Project treble means nothing for the average person and it is sad that the portal guys are not tech savvy, which leads them to making statements that are not even close to being true.

zelendel said:
Please. First of getting aosp to boot on that device is not that big of a deal. Rom devs do it all the time. The only reason those devices are left behind is because developers refuse to work with their chipset.
So explain how something only concerns the SOC manufacturer and the OEM will make roms faster?
If you really thiink this will make the OEMS update any more then they already do then you are sadly mistaken.
Thats the one that I mentioned that the devs are laughing at.
Also if you follow the thread linked you will see that things are still broken and causing issues. Nothing new.
Project treble means nothing for the average person and it is sad that the portal guys are not tech savvy, which leads them to making statements that are not even close to being true.
Click to expand...
Click to collapse
By your judgement, what is not true as explained by the portal guys?
Isn't the whole point of Project Treble making it easier for devs to work with chipsets such as MediaTek or Kirin?
Project Treble third party development is still early, you need to give it time. It's not like every new feature in Android sprung up to be in the top places at once. Things will be broken, and the devs will find a solution.
Also, the point of Project Treble will be having unified ROM files for many devices in a category ( eg: Same SoC, same OEM, etc), and also where the device trees have not been released, unlike OnePlus, who has their Day One project.
By your logic, you're saying that there's no use for Project Treble, and it's all a complete waste of time.
But hey, it's your opinion .
But you do have a point, the portal is not to be trusted too far, and I would wait until a developer has shown that Project Treble has been put to good use on a device. But, that does not mean that Treble support should not be given to a device like ours that's super powerful.

thes3usa said:
By your judgement, what is not true as explained by the portal guys?
Isn't the whole point of Project Treble making it easier for devs to work with chipsets such as MediaTek or Kirin?
Project Treble third party development is still early, you need to give it time. It's not like every new feature in Android sprung up to be in the top places at once. Things will be broken, and the devs will find a solution.
Also, the point of Project Treble will be having unified ROM files for many devices in a category ( eg: Same SoC, same OEM, etc), and also where the device trees have not been released, unlike OnePlus, who has their Day One project.
By your logic, you're saying that there's no use for Project Treble, and it's all a complete waste of time.
But hey, it's your opinion .
But you do have a point, the portal is not to be trusted too far, and I would wait until a developer has shown that Project Treble has been put to good use on a device. But, that does not mean that Treble support should not be given to a device like ours that's super powerful.
Click to expand...
Click to collapse
The portal guys will have you believe that this will help rom development. It wont.
The problem the devs have with the Kirin chip is that it is done in mostly Chinese and there is 0 documentation on how to work with the chips. as for MTK. Yeah that wont happen. There is a reason those chips are used mostly on devices that dont have google play services.
No that will not mean unified rom files. Another thing they lead to you believe. Even the dev doing the work (not the portal writer) has already said each device will still need its own kernel.
Project treble does have a use. Its just not something we can really use.
Project treble was made so OEM can update android without having to update their version of the android OS. Everything is between the SOC Oem and the device oem.
Now ask yourself this. What OEM is really gonna update a device without updating their OS version? Also you cant really seperate the OS framework from googles android and the OEM. This is due to the OEM changing or replacing completely every base android framework file that google releases. (another thing the portal has people not understanding. OEM do not skin android. They replace it with completely different versions of android. Like Linux distros.) Also even if you can boot AOSP on any device. Are you willing to lose all the features that Oem add to their devices? Take the one plus camera deal as a perfect example.

Quote from other thread:
regarding Project, it targets all devices launched with Android 8.x also It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over. Qualcomm has practically zero motivation to do this, infact it works against their interests.
So better petition Qualcomm