Database Info

Can someone explain the difference between all the aokp builds?

Sorry if this was answered already. At the moment there is 4 you could choose from. I've read countless posts in each thread but that may be the reason why this goes over my head. I'm just trying to understand the difference between them all. I also thought I read that xoomdev said the devs couldn't make their own builds and could only release the official bricks. I know this was answered over in one if the rootz threads too but there's so many posts it would be like finding a needle in a haystack. So if anyone has the time and would like to elaborate, thank you in advance.

I am confused by this as well - it seems like there are multiple aokp and CM10 builds going around.

Very simply put you have the official builds of each which is how the main developers want the ROM to act/feel/look/etc... They also provide the code for these builds so any other developers that want to can add/subtract little tweaks here and there to make it how THEY want it to act/feel/look/etc... And that is what the unofficial builds are, "aftermarket" developers tweaking it.
EDIT: Also, if you have a bug on the official build of either then there's a 99% chance it's on all the other ones too.

Brian Gove said:
Very simply put you have the official builds of each which is how the main developers want the ROM to act/feel/look/etc... They also provide the code for these builds so any other developers that want to can add/subtract little tweaks here and there to make it how THEY want it to act/feel/look/etc... And that is what the unofficial builds are, "aftermarket" developers tweaking it.
EDIT: Also, if you have a bug on the official build of either then there's a 99% chance it's on all the other ones too.
Click to expand...
Click to collapse
Thank you!

Unofficial CM10 - IMPORTANT - Please Read.

As im sure most of you all know, I have locked the Unofficial CM10 thread. It isnt because of one person or one event, but something that has been coming for a long time. I have been stressing myself with this build and making sure that everyone was happy and doing pretty much everything i could do, but it didnt seem to be enough. While i appreciate the feedback, it is very disappointing to release cm10.1 when pretty much no other phones have released it (due to the lack of source merged and changes necessary for jellybean 4.2.1) and have nothing but post after post of this doesnt work and this doesnt look right and this is running horrible and blah blah blah even after i made it absolutely clear time after time that there may be issues since there is alot of source changes that are missing. You would think that since i took the time to merge the needed changes and work tirelessly to make changes and get the changes merged into our device/kernel trees to get CM 10.1 built and IMO running nicely, there would be alot of positive feedback and alot of understanding from the community that there may be little issues here and there since not everything was completely merged in on the CM side, but that was not the case as everyone expects perfection right and nothing else. Anyways, with that said, Building CM10 was becoming more of a job instead of something fun that i loved to do. And believe me... I havent had nearly enough donations to be ok with considering this a job... Nor do i expect alot of donations and for those of you who have supported me, I greatly appreciate it. I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.

scott.hart.bti said:
As im sure most of you all know, I have locked the Unofficial CM10 thread. It isnt because of one person or one event, but something that has been coming for a long time. I have been stressing myself with this build and making sure that everyone was happy and doing pretty much everything i could do, but it didnt seem to be enough. While i appreciate the feedback, it is very disappointing to release cm10.1 when pretty much no other phones have released it (due to the lack of source merged and changes necessary for jellybean 4.2.1) and have nothing but post after post of this doesnt work and this doesnt look right and this is running horrible and blah blah blah even after i made it absolutely clear time after time that there may be issues since there is alot of source changes that are missing. You would think that since i took the time to merge the needed changes and work tirelessly to make changes and get the changes merged into our device/kernel trees to get CM 10.1 built and IMO running nicely, there would be alot of positive feedback and alot of understanding from the community that there may be little issues here and there since not everything was completely merged in on the CM side, but that was not the case as everyone expects perfection right and nothing else. Anyways, with that said, Building CM10 was becoming more of a job instead of something fun that i loved to do. And believe me... I havent had nearly enough donations to be ok with considering this a job... Nor do i expect alot of donations and for those of you who have supported me, I greatly appreciate it. I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.
Click to expand...
Click to collapse
you have a charachter flaw. you're a people pleaser. once you get over that and become a true asshole you will be much happier in life.

Dani897 said:
you have a charachter flaw. you're a people pleaser. once you get over that and become a true asshole you will be much happier in life.
Click to expand...
Click to collapse
Lol! So true!
Sent from my SGH-I997 using xda app-developers app

Just wanted to put my two cents in...I've been an avid user of the roms from this site for quite awhile now & have never felt the need to register because any issues I've ever had,I've been able to rectify with some searching or have been on roms that have clearly stated they were beta's & expected to have flaws. That being said...after watching what happened on your infuse board, I just wanted to let you know the fact that you're continuing to develop & keep our phones updated with the best features gave me the first true reason to register so I could say thanks...
Sent from my SGH-I997 using xda app-developers app

Thank You.

I don't blame Scott for having the thread closed, not one bit.
And Dani is correct, Scott's character flaw is only that he's missing the "asshole" gene that some tend to have.
Now on to the good part...
I'm getting back into the swing of things as far as porting and development goes. My first attempt is going to be a nearly pure AOSP build using Aries repos and some Maguro/Takju code base, with parts from the most recent CM10.1 base. I have an idea of what I want to incorporate, but it should be light and clean, with a smooth interface.
Scott, I will be in touch with you shortly on this, as I need to finish and finalize my SDK installs and get everything going correctly for a first build.

Just checked Scotts goo link. Can I safely assume the development continues? If so hallelujah the infuse lives on.
Sent from my SGH-I997 using xda app-developers app

Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?

hattrickinc said:
Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?
Click to expand...
Click to collapse
But Scott specifically asked multiple times not to post bugs on the 4.2/cm10.1 releases due to the fact that source is still being merged -cm said themselves that the 4.2 code would be buggy and that you probably wouldn't be able to build anything with it...for the most part Scott proved both of those wrong
However I do like the idea of the three threads
Sent from my HTC Holiday using Tapatalk 2

openwheelracing said:
Just checked Scotts goo link. Can I safely assume the development continues? If so hallelujah the infuse lives on.
Click to expand...
Click to collapse
scott.hart.bti said:
I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.
Click to expand...
Click to collapse
Yes, he will keep developing, but don't expect to see updates on this forum, which is a shame. His CM10 thread was actually the only reason I got on XDA.

Thanks for the update, Scott. Don't let the drama llamas get you down
Sent from my SGH-I997 using xda app-developers app

hattrickinc said:
Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?
Click to expand...
Click to collapse
For the most part I agree with you. Its why I probably pissed a bunch of people off defending the late comers and those that just don't know about logcats and such.
However, it was stated multiple times by not just Scott but the more senior and knowledgeable members that the 4.2 was going to have problems.
I agree searching through 1000 plus posts can be a daunting task and maybe I just don't have a life but I've done it for every ICS/JB rom I've flashed.. But I was there at the beginning of that development so it made it easier. But you didn't have to read more than 2 pages between warnings for the 4.2.
I'm on Scott's side on this one.
If nothing else click on the op's profile and just read all their posts.
Personally I think only devs should be allowed to post on a dev thread but I don't see that happening anytime soon.
Sent from my SGH-I997 using xda app-developers app

I agree. I think there should be a minimum post count of 100 and a requirement to agree to a separate 'contract' to post in dev. threads. I read dev threads to find out what's going on in development not the rubbish that appears in most dev threads. The infuse forums have been fairly tolerant of this kind of thing. Other forums on xda, much less so.
Sent from my SGH-I997 using xda app-developers app

Changelog
I think another part of the problem is that very little actual development discussion happens here. It seems that people release their stuff here, and respond to bug reports, but that's about it. You can learn a lot about Linux by reading the archives of the Linux Kernel Mailing List (LKML). It's not quite the same situation here, learning about android is much harder (i have yet to find an android equivalent for the LKML)
Anyway, Thanks for continuing development! Will you be posting a change log between releases? I just like to know what I'm flashing ahead of time
Thanks,
woody

Scotts just released CM10.1 on goomanager 12/10 build go check it out
Sent from my SGH-I997 using xda app-developers app

Scott,
Glad to see you will be still be developing. Will there be some type of change log somewhere that we can view? I agree with some of the past. 500 pages of posts to read/search is alot. possibly a better brake down would have keep people posting in the correct places. Also with the 4.2 merge MY opionion would have been to make a separate thread as the last 4.1.2 was stable and really usable as its still my current daily. If the items arent merged maybe it isnt a good idea to even make a realease unless its to a few beta testers. That way 100s of people dont whine and complain about known or dumb issues.
Either way keeep up the good work.

Not sure how it would be accomplished, but a good idea would be to remove all posts from the cm10 thread and only scott could post in it (updates/changelog).
I have no idea how feasible that would be though.

Many thanks to scott
Hi scott, I never felt the need to comment in your thread because I never had any problems with your ROM.
But now I feel the need to comment here to express my gratitude for all the hard work that you have put into this ROM.
Your ROM is the first one that I tried, and also the best one I've seen/used. I'm VERY glad that you will continue your work for the Infuse.
Again, I thank you for your work, and I will be looking forward to future updates!

UnhoIy said:
His CM10 thread was actually the only reason I got on XDA.
Click to expand...
Click to collapse
This^
hovin1988 said:
Hi scott, I never felt the need to comment in your thread because I never had any problems with your ROM.
But now I feel the need to comment here to express my gratitude for all the hard work that you have put into this ROM.
Your ROM is the first one that I tried, and also the best one I've seen/used. I'm VERY glad that you will continue your work for the Infuse.
Again, I thank you for your work, and I will be looking forward to future updates!
Click to expand...
Click to collapse
And this^
I generally just read through the thread reading peoples issues if i ran into one rather than post. Issues were always sorted out if i kept reading. But thanks for all your hard work in creating roms, I know i'd be really bad off without them :good:

I think the communication and forum issues are simply a result of using a forum for "developer collaboration". Then to top it off, many are using tapatalk, which has the most useless search feature ever. I've heard the argument that a proper browser should be used, but many just won't.
As long as a forum is used for xda development, it will continue to be more like a ROM forum than anything else intended without ridiculous amounts of moderation (even judicious use of temp bans without warning).
Forums are good for arguing lol. Bugtrackers are good for tracking bugs, especially since they are easy to police. If you want feedback as well, make a special category for that. Duplicates and invalid reports can be easily identified and marked as such. For all other forums(general, q&a, accessories, etc.) a forum makes sense to me. For the development forum, a forum, IMO, makes little sense.
If the forum format is used in order to foster community, fine. You can expect a lot of drama, arguing, complaining, and everything else that goes along with it.
Just my opinion. I could be completely wrong.
Sent from my SGH-I997 using xda app-developers app lol

[Request] Tutorial for implementing HALO into a Rom

Hi,
I'm really surprised no one has made a tutorial for implementing Halo (PA Teams creation) into a rom. I think it would be really useful because lots of devs with roms would like to implement it into their rom but have no idea where to start. Making a tutorial would help a lot of people out and if you made it noobish enough it would be even better for people who aren't full time devs but would like to modify there own roms. Someone please help, it would be much appreciated from everyone here at XDA :victory:

+1

would love this

+1

I guess you just fork your desired ROM's repository (say, CM10.1) and merge the HALO repository with it.
Here are some things that you might understand (I don't):
https://plus.google.com/107979589566958860409/posts/LF2RNE9rHt1
And here is something I guess you must understand in order to continue:
https://plus.google.com/107979589566958860409/posts/fkQGDxzNRd1
Here's something I found about git that may be of some importance (to either refresh your knowledge or to give it to you in case this is your first time, like me):
http://git-scm.com/book
Forgive me for being dumb, I just can't seem to understand git no matter how many books I read
If anyone has any ideas, please let me know, I'm eager to start working

Is it possible for someone to add a step by step process for this? I have been trying to "git remote add" the various links I have found to my existing AOKP build with no luck. I fetch successful and ran a build but see no signs of HALO just my normal build.
Thanks

MARINERMOOSE241 said:
Is it possible for someone to add a step by step process for this? I have been trying to "git remote add" the various links I have found to my existing AOKP build with no luck. I fetch successful and ran a build but see no signs of HALO just my normal build.
Thanks
Click to expand...
Click to collapse
Did you add just from settings or also from framework
Sent from my GT-N7000 using Tapatalk 2

+1

Okay, you seem to be having issues regarding understanding the rules here (or pretty much anywhere on the Internet).
Let me refresh your knowledge of the rules you just broke:
Spamming. You posted a "+1" to a thread of a Forum that uses "Thanks" (for which you beg in your giant oversized signature) for a single reason; to avoid spam posts like this.
Necromancing. You brought to life a thread's two weeks short of being abandoned for a full year. I get reviving a thread after 3 months if you have anything important to contribute to it, but after a full year, posting spam!?

someone755 said:
Okay, you seem to be having issues regarding understanding the rules here (or pretty much anywhere on the Internet).
Necromancing. You brought to life a thread's two weeks short of being abandoned for a full year. I get reviving a thread after 3 months if you have anything important to contribute to it, but after a full year, posting spam!?
Click to expand...
Click to collapse
Oops.. Sorry boss.. I didn't saw the date.. First infraction on my part.. Will never happen again.. And I will take full responsibility.. Sorry again..

[R&D]New CM ROM project - TESTERS NEEDED

Hi everybody...I just moved on to this device and even if I've read this section for awhile and knew there's not much development I still have hope.
So, I've discussed with some people I know and there is at least the will to try to develop something. @javelinanddart made some nice kernels for my old device and he wants to make a CM ROM for S6 Edge. I know there were other attempts and I know they failed (at least here I couldn't find anything else).
He needs testers...and when I say tester I mean no newbies or users that just want to be cool..real, good testers. Someone who's able to flash and test kernels and ROMs, someone who has some medium to advanced knowledge and of course knows how to flash, take logcats and things like that. So don't jump in if you think you're not qualified. Devs are more than welcome to join this if they want to.
We would like to start a specific Hangouts chat for that to be easier to communicate, there will be NO public releases untill at least a bootable build is made. As with any other development, there is a small risk of bricking the device if something goes wrong but that's a risk we all know and accepted when we start flashing. So once again, THIS IS NOT FOR NEWBIES, please don't even think about asking to be a tester if that's the case.
If there is anyone interested, please let me know by posting here and send your Hangouts contact via PM (I don't want to have a public disclosure of personal info)
Also if there is detailed info about development for this device like kernel sources, device trees, vendor files and so on, please post the GITHUB links, it'll help the development.
Thank you...

Rapier said:
Hi everybody...I just moved on to this device and even if I've read this section for awhile and knew there's not much development I still have hope.
So, I've discussed with some people I know and there is at least the will to try to develop something. @javelinanddart made some nice kernels for my old device and he wants to make a CM ROM for S6 Edge. I know there were other attempts and I know they failed (at least here I couldn't find anything else).
He needs testers...and when I say tester I mean no newbies or users that just want to be cool..real, good testers. Someone who's able to flash and test kernels and ROMs, someone who has some medium to advanced knowledge and of course knows how to flash, take logcats and things like that. So don't jump in if you think you're not qualified. Devs are more than welcome to join this if they want to.
We would like to start a specific Hangouts chat for that to be easier to communicate, there will be NO public releases untill at least a bootable build is made. As with any other development, there is a small risk of bricking the device if something goes wrong but that's a risk we all know and accepted when we start flashing. So once again, THIS IS NOT FOR NEWBIES, please don't even think about asking to be a tester if that's the case.
If there is anyone interested, please let me know by posting here and send your Hangouts contact via PM (I don't want to have a public disclosure of personal info)
Also if there is detailed info about development for this device like kernel sources, device trees, vendor files and so on, please post the GITHUB links, it'll help the development.
Thank you...
Click to expand...
Click to collapse
Thanks for posting this. The kernel will probably be stock kernel with a few patches, i'll be releasing source for that immediately, however, the trees will be closed till we can get a booting build, once it boots, and maybe fix a few issues, I'll leave it there because I don't own the device (however clicking the donate buttons a few hundred times if you like the project might resolve that ) Screenshots can be posted here, and updates on what works or if it boots or not can be posted here, but most of the discussion will be in the google hangouts chat.
I'm looking mostly at @BMc08GT's stuff right now, and mythos.... something I can't remember.

Check this guys http://forum.xda-developers.com/showthread.php?p=61785445

Johnny camaro said:
Check this guys http://forum.xda-developers.com/showthread.php?p=61785445
Click to expand...
Click to collapse
Yes, we've checked that thread already but he said he's no longer working on S6 and his device start acting bad...so I don't think he will want to be into this, but maybe he can help with what knowledge gained during his tries

Johnny camaro said:
Check this guys http://forum.xda-developers.com/showthread.php?p=61785445
Click to expand...
Click to collapse
man..he wrote that allready (..... I know there were other attempts and I know they failed (at least here I couldn't find anything else)................)
so this was unneeded..
good luck at op..

thanks for trying port cm to s6 edge, good luck!!

I'm in for testing. I've been doing this sort of stuff since Android version 0.7 on the HTC Vogue, so I'm no stranger to the type of effort involved. I'll PM you my Hangouts details now.

I am up for testing on s6 edge g925f

Um, if I'm not mistaken both GS6 Flat and Edge have the same hardware so maybe you can make this thread in Flat section? It would get to bigger audience. Also what about funding the device to @javelinanddart? I have seen fundraisers couple of times so maybe we will start one here too?

Skreedi said:
Um, if I'm not mistaken both GS6 Flat and Edge have the same hardware so maybe you can make this thread in Flat section? It would get to bigger audience. Also what about funding the device to @javelinanddart? I have seen fundraisers couple of times so maybe we will start one here too?
Click to expand...
Click to collapse
I need a T-Mobile S6 Edge then, i personally don't care about getting one, I'm trying to help @Rapier out. I'll do as much as I can but I'm busy AF with school right now, idk if this will get far, or how far it will get

Tester
I am a tester for the g925f

I have a g925p, the Sprint edition. If this will be compatible with my device, I'd love to test. I know my way around a logcat haha
Sent from my SM-G925P using Tapatalk

I recently got my SG6 edge, i love the phone, it's design, the camera, but i damn touchwiz. it makes the phone look so cheap and laggy. so guys go for it - i'd also help you in testing

Edge and Flat version of Galaxy S6 share the same hardware so Flat version users can also participate in tests I suppose?
I know nothing about development but since we have unified kernels and roms that should be possible I think, right?
Wysłane z mojego One S przy użyciu Tapatalka

Count me in g925f

G925F here, I'd be willing to Test and report any bugs.

How come that you ask for testers while the thread has no pictures or progress ?!!
Do some updates tells what you did or what are you doing at the moment .
G925F , Here.

Any update?
Thank you for your work

I can help by Development and Testing too!
just send me a PM

don't know if you know about this :
https://github.com/Thecrazyskull/device_samsung_zeroltexx

Rule 12 - A New beginning

Good morning/evening,
As discussed in the other thread we started regarding changes to our site, we promised that we would change things around a bit and one of them was the long standing Sharing Rule (also known as Rule 12). We have worked diligently with the administration and moderation teams to turn the one we had into something that would make developer's works a bit safer from stealing and other unsavory things.
This thread is not meant as an announcement but rather as an open discussion platform so that you (the members/developers) can weigh in before we write it in the stone tablet along with the rest of them. This will be an open discussion regarding this topic only. Also, unlike the previous thread, which was more of a TownHall type of thread, this one WILL be moderated. In other words,
* keep the thread on topic;
* Unrelated posts will be removed;
* Members not adhering to the above two will be disciplined.
We look forward to having good, meaningful feedback from all of you (otherwise we would have added this to the rules like we always do). We want to have good, positive change into this community to make it into a pleasant atmosphere for all.
Without further ado, I give you the beta draft of Rule 12
Rule 12 - Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12-1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12-2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12-3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12-4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or sykopompos) or to a Moderator. We are here to help!
Click to expand...
Click to collapse
Have at it!

Liking what I am seeing. Well done

zelendel said:
Liking what I am seeing. Well done
Click to expand...
Click to collapse
Hey bud
Kinda miss seeing you around
Hope you are well....

I like it

looks good to me, no unofficial builds of officially supported devices is the icing on the cake :good: :highfive:

BeansTown106 said:
looks good to me, no unofficial builds of officially supported devices is the icing on the cake :good: :highfive:
Click to expand...
Click to collapse
Let's clarify, for all those developers that have no issue with unofficial builds, they can stay. This would only come into play for those developers who do not wish to allow unofficial builds. A suggestion would be to add that to your OP (many just use a C&P OP with specifics for the device being posted) if you don't want unofficial builds posted.
We will not be removing unofficial builds just for the sake of removing them. The current procedure would be followed, where you would report the post using our Report post feature, making mention in the report that you do not allow unofficial builds of your work.

Much better than the old version. One suggestion: When mentioning licenses, make it explicit that distributing any GPL software (like Linux or TWRP) requires making the source code available.

BeansTown106 said:
looks good to me, no unofficial builds of officially supported devices is the icing on the cake :good: :highfive:
Click to expand...
Click to collapse
Just to clarify that point, it only applies if the official build is already out.
Scenario: A ROM team says they don't plan to support phone X because no one on the team owns it and is fine with someone else porting it. So, a non-affiliated developer ports the ROM, but a year later, a member of the official team gets phone X and wants to officially support it. At the point of the release of the official build, no other unofficial builds are allowed, but the original one is grandfathered in. It wouldn't be fair to that developer if his unofficial build that he worked on for the last year was shut down just because someone on the official team changed his mind on owning a device.
Of course, the optimal solution would be for the ROM team to work with and pass on knowledge that helps the unofficial developer and maybe even include him on the team if his work is good.
By the way, none of this is set in stone, so if anyone disagrees with the handling of the above scenario or anything in the revised rule, please provide feedback. We don't necessarily want to get too bogged down in minutiae, but we also want the rule to properly reflect what the community wants. Because in the end, XDA is the community and we are here to support each other.

_that said:
Much better than the old version. One suggestion: When mentioning licenses, make it explicit that distributing any GPL software (like Linux or TWRP) requires making the source code available.
Click to expand...
Click to collapse
We did consider that. But there far too many different types of licenses out there to put them in writing. Thus, we needed a more general model. The gpl requirements still stand, not because of our rules but because of gpl itself. Our rules never have and never will truncate license requirements.

jerdog said:
Let's clarify, for all those developers that have no issue with unofficial builds, they can stay. This would only come into play for those developers who do not wish to allow unofficial builds. A suggestion would be to add that to your OP (many just use a C&P OP with specifics for the device being posted) if you don't want unofficial builds posted.
We will not be removing unofficial builds just for the sake of removing them. The current procedure would be followed, where you would report the post using our Report post feature, making mention in the report that you do not allow unofficial builds of your work.
Click to expand...
Click to collapse
yea thats what i figured, basically developers who allow unofficials can stay, and those who dont are now allowed to report for takedown
coal686 said:
Just to clarify that point, it only applies if the official build is already out.
Scenario: A ROM team says they don't plan to support phone X because no one on the team owns it and is fine with someone else porting it. So, a non-affiliated developer ports the ROM, but a year later, a member of the official team gets phone X and wants to officially support it. At the point of the release of the official build, no other unofficial builds are allowed, but the original one is grandfathered in. It wouldn't be fair to that developer if his unofficial build that he worked on for the last year was shut down just because someone on the official team changed his mind on owning a device.
Of course, the optimal solution would be for the ROM team to work with and pass on knowledge that helps the unofficial developer and maybe even include him on the team if his work is good.
By the way, none of this is set in stone, so if anyone disagrees with the handling of the above scenario or anything in the revised rule, please provide feedback. We don't necessarily want to get too bogged down in minutiae, but we also want the rule to properly reflect what the community wants. Because in the end, XDA is the community and we are here to support each other.
Click to expand...
Click to collapse
that seems fair enough and makes total sense

Don't see any flaws in there. Great job!
Sent from my YUNIQUE using XDA Labs

egzthunder1 said:
Hey bud
Kinda miss seeing you around
Hope you are well....
Click to expand...
Click to collapse
All is well. Hope they are with you as well.
I'm always around lol just wanted to step back for a bit while everything was sorted.
This revision to the rule is long in coming. And seems just about perfect. Ill post my thoughts more after my gf birthday dinner tonight.

coal686 said:
Just to clarify that point, it only applies if the official build is already out.
Scenario: A ROM team says they don't plan to support phone X because no one on the team owns it and is fine with someone else porting it. So, a non-affiliated developer ports the ROM, but a year later, a member of the official team gets phone X and wants to officially support it. At the point of the release of the official build, no other unofficial builds are allowed, but the original one is grandfathered in. It wouldn't be fair to that developer if his unofficial build that he worked on for the last year was shut down just because someone on the official team changed his mind on owning a device.
Of course, the optimal solution would be for the ROM team to work with and pass on knowledge that helps the unofficial developer and maybe even include him on the team if his work is good.
By the way, none of this is set in stone, so if anyone disagrees with the handling of the above scenario or anything in the revised rule, please provide feedback. We don't necessarily want to get too bogged down in minutiae, but we also want the rule to properly reflect what the community wants. Because in the end, XDA is the community and we are here to support each other.
Click to expand...
Click to collapse
+1
Very well explained.

Hopefully this goes some way to help developers feel like they want to be here and have a bit more control of their work. Great initiative

Nice job!

I agree with Zelendel and I think, as does he, that this revision to rule 12 is just about perfect, the only thing I would question is the unofficial builds thing... Technically if the work is licensed under Apache (sort of) or GPL (definitely) then we don't have much say in the matter (3rd party license should still outweigh our rules).

Jonny said:
I agree with Zelendel and I think, as does he, that this revision to rule 12 is just about perfect, the only thing I would question is the unofficial builds thing... Technically if the work is licensed under Apache (sort of) or GPL (definitely) then we don't have much say in the matter (3rd party license should still outweigh our rules).
Click to expand...
Click to collapse
In that case, ROM developers can just start modifying the Apache license to say explicitly that unofficial builds of officially supported devices are not allowed to be distributed. Because they complied with the AOSP's Apache license when forking the work, they can set their own terms at will. I don't like that though because then every ROM is going to have their own license terms and it'd become a complete nightmare to work with.

Jonny said:
I agree with Zelendel and I think, as does he, that this revision to rule 12 is just about perfect, the only thing I would question is the unofficial builds thing... Technically if the work is licensed under Apache (sort of) or GPL (definitely) then we don't have much say in the matter (3rd party license should still outweigh our rules).
Click to expand...
Click to collapse
If that's the case, someone could post a GPL-licensed tool to circumvent payment in paid apps on XDA. So clearly 3rd party licenses do not outweigh forum rules.

The Flash said:
In that case, ROM developers can just start modifying the Apache license to say explicitly that unofficial builds of officially supported devices are not allowed to be distributed. Because they complied with the AOSP's Apache license when forking the work, they can set their own terms at will. I don't like that though because then every ROM is going to have their own license terms and it'd become a complete nightmare to work with.
Click to expand...
Click to collapse
Agree totally, that would make our job a nightmare like you said. I don't think we are ever going to get a solution that makes everyone 100% happy but I think the new change is about the best we are ever going to get, it's great that it has been well received by both mods and devs

I'm not a dev so i know this doesn't apply to people like me, but can this be explained to me - I'm not clever enough to figure this out:
Rule 12-3 from your new beta draft states:
Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
Click to expand...
Click to collapse
From my previous post in that other thread:
Attention:
Redistribution, modifying files used within this project's file or integrating with other projects are prohibited with no exceptions other than my projects.
Making mirrors, re-uploading to another servers are also prohibited with no exceptions.
If you will do something which prohibited ask me for permission. If you do without my permission i will report you
Click to expand...
Click to collapse
He never owned the htc/samsung/lg created rom in the first place, and didn't create any of the mods within his rom.
From what i can tell with the new rule, as long as he gives credits to the original creator of the mods within his rom, he can still lock his rom down as he hasn't broken any rules.
I probably have the complete 'wrong end of the stick' here...