Related
Hello all
I have spent much time recently attempting to modify the zImage included with the Fascinate to include a working recovery image for us to use. However without source code this an extremely difficult (if not possible) goal to achieve.
I am requesting that anyone who owns this device please request the kernel source code from Samsung, so that we may be able to fully utilize our devices. Even if you do not know anything about coding or have any personal use for this source code, it is your right to request it as an owner of the device, and this code will help us all immensely once it is in the right hands.
Requests for source code can be filed on Samsung's website at : opensource . samsung.com/ (remove the extra spaces, apparently I can't post links yet)
Click on the mail icon at the top to submit your request.
Thank you for your assistance.
Requesting right now. Thanks for what your doing! Any updates since last night?
i just finished sending one in
jt1134 said:
Hello all
I have spent much time recently attempting to modify the zImage included with the Fascinate to include a working recovery image for us to use. However without source code this an extremely difficult (if not possible) goal to achieve.
I am requesting that anyone who owns this device please request the kernel source code from Samsung, so that we may be able to fully utilize our devices. Even if you do not know anything about coding or have any personal use for this source code, it is your right to request it as an owner of the device, and this code will help us all immensely once it is in the right hands.
Requests for source code can be filed on Samsung's website at : opensource . samsung.com/ (remove the extra spaces, apparently I can't post links yet)
Click on the mail icon at the top to submit your request.
Thank you for your assistance.
Click to expand...
Click to collapse
You just want everything handed to you, don't you? Quit being so lazy and do some actual work.
But seriously everyone, please take the time to fill out the request. The sooner we get the source, the quicker we'll see some ROMs.
namebrandon said:
You just want everything handed to you, don't you? Quit being so lazy and do some actual work.
But seriously everyone, please take the time to fill out the request. The sooner we get the source, the quicker we'll see some ROMs.
Click to expand...
Click to collapse
This guy again, huh
Seriously, thank you to anyone who fills out the request. Remember, as an owner of the device it is your right to have access to the kernel source code, and it takes less than 2 minutes to fill out the request form. Tell your friends!
http://opensource.samsung.com/reception/reception_main.do?method=inquiryView
There's the direct url for the lazy.
Thanks for direct link. Filled one out through my phone. Made it sound pretty formal lol. Let's hope we get the ball rolling soon, starting to miss all the active development on the older phones.
Submitted a request.
frostman89 said:
Thanks for direct link. Filled one out through my phone. Made it sound pretty formal lol. Let's hope we get the ball rolling soon, starting to miss all the active development on the older phones.
Click to expand...
Click to collapse
Once we get source we will be able to get a working recovery, then the floodgates will be open. My personal mission is to get AOSP/CM on the phone immediately after that happens, can't stand the TouchWiz and I intend to destroy it!!
Submitted a request. Only way I'll be buying this phone is if I can eliminate all Verizon/Samsung UI/apps. Even a vanilla ROM will do over the TouchWiz crap.
I am a little confused. What source code are you requesting?
If you go to h**p://opensource.samsung.com/, click on 'Mobile' at the top, then Ctrl-F for "i9000", you can find (what looks like) a zip containing both the kernel image and files you can plop in an aosp tree in order to build roms for the Galaxy S.
Maybe you guys are talking about source specifically for Fascinate?
partner55583777 said:
I am a little confused. What source code are you requesting?
If you go to h**p://opensource.samsung.com/, click on 'Mobile' at the top, then Ctrl-F for "i9000", you can find (what looks like) a zip containing both the kernel image and files you can plop in an aosp tree in order to build roms for the Galaxy S.
Maybe you guys are talking about source specifically for Fascinate?
Click to expand...
Click to collapse
Yes, we are requesting the source for the fascinate. As the i9000 is a completely different device, and we have the sch-i500
fallingup said:
Yes, we are requesting the source for the fascinate. As the i9000 is a completely different device, and we have the sch-i500
Click to expand...
Click to collapse
Okay, thanks. That clears it up.
So I guess Samsung is currently in violation of the GPL, then? (And probably other licenses).
partner55583777 said:
Okay, thanks. That clears it up.
So I guess Samsung is currently in violation of the GPL, then? (And probably other licenses).
Click to expand...
Click to collapse
Well i am sure they will release the source, its just taking them longer than i would like. They released the source for the Epic about 3 days after the hardware was released, and we are at about a week now.
Yeah, they'll post the code soon, they're just taking their sweet time about it.
Source code released! Thanks guys!
jt1134 said:
Source code released! Thanks guys!
Click to expand...
Click to collapse
and source code fail!
Is the source code on opensource.samsung.com still the wrong one?
ludeboy said:
Is the source code on opensource.samsung.com still the wrong one?
Click to expand...
Click to collapse
Not sure yet. We've confirmed they've had at least two different files for download since last night. The original one wasn't' working. I'm at work, so can't tell you much about the second (latest) one.
Just thought some might be interested in this (so sue me, i had to ask it):
http://nookdeveloper.zendesk.com/en...-updated-1-2-source-code?page=1#post_20056491
We will be publishing the updated source in the coming weeks. Thanks for your patience.
Click to expand...
Click to collapse
It will be interesting to see what their new source brings, and what we can use from it. Here is hoping that it is sooner rather than later...
EDIT: Well, i am happy to say it didn't take long.. have at it here: http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor-source-code.zip
Awesome news! The faster we can get dalingrin the updated kernel source the better!
Does complying with the gpl allow for a reasonable delay? Because once you get into grey areas like that, what's reasonable? 2 weeks? 3 months?
Obviously they have the source already, so I don't understand when companies release it some time afterwards.
Aye. I hate the "weeks" portion.. given that its out, i dont think its unfair to demand it now. As it is though, i think the GPL gives 60 days (??) for them to publish the code though, so it may be a while.
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
ArmitageID said:
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
Click to expand...
Click to collapse
There isn't much an updated kernel will do to help the Honeycomb SDK.
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
They will do whatever they want until someone sues. What if we lost?
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
I may have been wrong (and will happily say its not the first time); but i did do some reading and found this: http://gplv3.fsf.org/wiki/index.php/User:ashawley/Making_copyleft_work_with_implied_compliance
Not sure if it is totally relevant though..
Source Code
I got this:
Dear Brandon Bennett,
Thank you for your inquiry.
Barnes and Noble will post the updated source code in the near future.
There is still no specific date yet. The link will be posted under terms
of service on the website.
Please accept our sincere apologies for any inconvenience this may have
caused and we look forward to hearing from you.
Sincerely,
Ella
Customer Service Representative - Digital Support
Barnes & Noble
http://www.bn.com/
Visit our NOOK Support site for the latest updates and downloads at:
http://www.barnesandnoble.com/nook/support/
Click to expand...
Click to collapse
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
nemith said:
I got this:
Click to expand...
Click to collapse
Thanks for the info. The nook dev board had another update:
Well, if history is a guide, we released source of 1.0 about 2-3 weeks after launch...
Click to expand...
Click to collapse
As i replied, the anxious part of me does not understand any delay really, other than trying to keep the source code away from us "hackers" for as long as possible. The code is obviously in use, so why not release it?
Ah well..
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
chadamir said:
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
Click to expand...
Click to collapse
Perhaps, but the code is already shipping - its not to say an update can't get pushed out, but just because we can't see the source, doesn't mean current violations are excused.
As it is, the linux kernel is GPL; they can't not release it. So again, i am still frustrated at the hold up...
Probably just the usual corporate speed. They don't like to publish anything before they have to, if only for liability and exposure. Probably the last thing on the rollout list, too.
poofyhairguy said:
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
Click to expand...
Click to collapse
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
Rock on good sir.. That sounds most exciting indeed!
Perhaps a silly question, but to the end user- what will the difference be between the current and .32 kernel? Faster/better/stronger/able to make cappuccinos?
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Nburnes said:
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Click to expand...
Click to collapse
The clock/governor issue is because only the performance governor is compiled into the kernel right now. The broken SD warning is mostly fixed and I believe the same for the battery.
or does anyone else feel like we dont have enough aosp love? I mean we have miui, cm7, had decks(went ghostbusters on us) and empiire(heard he got grounded for molesting his hard drive.) I understand theirs still kinks to be worked out but everything is Sense. Just wanted to see who else felt this way. PLEASE DONT COME IN AND START A PARAGRAPH WAR, I read enough in high school.
Temari x Shikamaru
Evervolv exists.
il Duce said:
Evervolv exists.
Click to expand...
Click to collapse
Link please. Ive been hunting it.
Temari x Shikamaru
Talked to shift on twitter yesterday, he said CM7 is being worked on. I honestly think what it is that people are happy with their phones just the way they are, so it brings less crowd. While it is smaller than the original Evo, there is still a pretty big following. Plus, this is just a US phone, so when comparing the Sensation with us is like apple and oranges. We just got mike and androidrevolution! Which is great.
Sent from my PG86100 using xda premium
PatrickHuey said:
Talked to shift on twitter yesterday, he said CM7 is being worked on. I honestly think what it is that people are happy with their phones just the way they are, so it brings less crowd. While it is smaller than the original Evo, there is still a pretty big following. Plus, this is just a US phone, so when comparing the Sensation with us is like apple and oranges. We just got mike and androidrevolution! Which is great.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Its not just US. Theres gsm models for overseas.
Temari x Shikamaru
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Can the gsm users get some aosp love? Any roms?
Sent from my Evo 3D GSM...bring on the AOSP!!!
housry23 said:
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Click to expand...
Click to collapse
This man is right. Most AOSP is done by Cyanogenmod devs and kanged from there. I can guarantee you when they come out with a CM7 RC, there will magically be other AOSP roms.
housry23 said:
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Click to expand...
Click to collapse
Your right. I forgot about that.
Temari x Shikamaru
housry23 said:
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Click to expand...
Click to collapse
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Sad Panda said:
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Click to expand...
Click to collapse
Damn. Such a long read. It was good though.
Temari x Shikamaru
knowledge561 said:
Damn. Such a long read. It was good though.
Temari x Shikamaru
Click to expand...
Click to collapse
I'm sorry, I originally had hoped for a much shorter post. I always try to get the thoughts in my head out "on paper" in the shortest, most efficient and least complex manner. This is my vision of a more free, "open source" world though. I think the freedom of information could be applied to many facets of society that would create a better future for all of us, and still preserve the competition that drives a more peaceful, better, cheaper, faster world. Sorry again!
Sad Panda said:
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Click to expand...
Click to collapse
The problem is that people don't always give credit where credit is due, which is one of the reasons some people don't like sharing stuff. I mean, let's say I made this awesome mod and let everybody use it. Then some kitchen dev comes along, kangs the **** out of it, doesn't mention me in his rom, and slaps a gigantic DONATE button at the bottom of his signature. It's frustrating.
Now I'm all about open source. I won't use a rom that doesn't post the source. That's the exact reason I won't use MIUI.
SolsticeZero said:
The problem is that people don't always give credit where credit is due, which is one of the reasons some people don't like sharing stuff. I mean, let's say I made this awesome mod and let everybody use it. Then some kitchen dev comes along, kangs the **** out of it, doesn't mention me in his rom, and slaps a gigantic DONATE button at the bottom of his signature. It's frustrating.
Now I'm all about open source. I won't use a rom that doesn't post the source. That's the exact reason I won't use MIUI.
Click to expand...
Click to collapse
I fully understand your frustration. I am a software engineer too so I know what you are going through. I have not yet begun developing for Android, but will. There is a little bit of a problem here that could easily be solved, and the community has a responsibility to protect the intellectual property rights that you and every other developer like you is entitled to. In fact it is a right that is protected by the integrity of the constitution of the united states, and many other countries and law enforcement around the world. This is a failure that not just developers, mods, and admins have, but a responsibility and failure that every user at xda shares no matter who they are.
First off; not to offend any MIUI developers that may be watching, but if you are developing for Android you need to be using a license that is open, and your source needs to be open too. This is especially true if you are using xda as a distribution medium, but sadly while xda has said they encourage, and want every development to be open source they are not forcing the matter. This is a failure I think. It also makes MIUI look suspicious too, as there isn't a way to verify if their source is uniquely theirs'. I personally believe xda should not allow software that is not open source to be distributed. If google didn't keep the open source principle when they acquired Android roms like MIUI would NOT exist! It is highly unethical to take the base ROM from google because it is open source, and then close the source. That is wrong wrong wrong! It is also illegal! You can not redistribute the Android OS even if you have made changes and then close the source and not maintain the software license google has on place.
Second; I believe as a user of xda it is your duty to maintain the integrity of the principles of xda, and Android. Don't support closed source works, voice your disgust so that xda sees the will of its users, that the over whelming majority wants things to remain open source. Tattle your ass off if someone has broke the copyright law and used someone's work without permission and credit.
It is important to keep both xda and Android running on the same principles it started with. Don't let this keep happening guys! This is very serious, a lot of developers are breaking the law doing what they are doing!
Sad Panda said:
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Click to expand...
Click to collapse
Or learn to code yourself and create roms from the ground up. Most devs do what they do for themselves first, and allow us to ride on their coattails. Not a bad ride if your like me and have no coding skills. Otherwise, I doubt your plea is going to convince a dev to do anything more or less then they do now, unless it interest them personally.
I do agree with you though. I'm coming from Android on the Touch Pro 2 where a small group of devs are building EVERYTHING from scratch. From the modems to the light sensor. It's a huge job done out of love for the hardware, for fun, and a passion for coding.
knowledge561 said:
Link please. Ive been hunting it.
Temari x Shikamaru
Click to expand...
Click to collapse
he links only via twitter posts and in his IRC, send him a tweet. iirc still in beta, but he does some nice ROMs
Serren said:
Or learn to code yourself and create roms from the ground up. Most devs do what they do for themselves first, and allow us to ride on their coattails. Not a bad ride if your like me and have no coding skills. Otherwise, I doubt your plea is going to convince a dev to do anything more or less then they do now, unless it interest them personally.
I do agree with you though. I'm coming from Android on the Touch Pro 2 where a small group of devs are building EVERYTHING from scratch. From the modems to the light sensor. It's a huge job done out of love for the hardware, for fun, and a passion for coding.
Click to expand...
Click to collapse
Thank you for your comment and support. I don't disagree with you. If you steal a loaf of bread to feed yourself, is it any less of a crime than to steal a loaf of bread to feed you and your family and friends? Or is it the same or worse?
I think either way it isn't ethical. People need to think less about themselves I think. I must reiterate and clarify so I am not misunderstood. I don't think it is inherently bad to be using a ROM as your base, but it is wrong to then close the source of a previously open piece of work and/or not maintain the original license, and give credit in every spot it should be given in. That would include its distribution, the license, the source code itself, and any where else that you put your own version, app info, and copyright notice. Am I wrong?
Sad Panda said:
I fully understand your frustration. I am a software engineer too so I know what you are going through. I have not yet begun developing for Android, but will. There is a little bit of a problem here that could easily be solved, and the community has a responsibility to protect the intellectual property rights that you and every other developer like you is entitled to. In fact it is a right that is protected by the integrity of the constitution of the united states, and many other countries and law enforcement around the world. This is a failure that not just developers, mods, and admins have, but a responsibility and failure that every user at xda shares no matter who they are.
First off; not to offend any MIUI developers that may be watching, but if you are developing for Android you need to be using a license that is open, and your source needs to be open too. This is especially true if you are using xda as a distribution medium, but sadly while xda has said they encourage, and want every development to be open source they are not forcing the matter. This is a failure I think. It also makes MIUI look suspicious too, as there isn't a way to verify if their source is uniquely theirs'. I personally believe xda should not allow software that is not open source to be distributed. If google didn't keep the open source principle when they acquired Android roms like MIUI would NOT exist! It is highly unethical to take the base ROM from google because it is open source, and then close the source. That is wrong wrong wrong! It is also illegal! You can not redistribute the Android OS even if you have made changes and then close the source and not maintain the software license google has on place.
Second; I believe as a user of xda it is your duty to maintain the integrity of the principles of xda, and Android. Don't support closed source works, voice your disgust so that xda sees the will of its users, that the over whelming majority wants things to remain open source. Tattle your ass off if someone has broke the copyright law and used someone's work without permission and credit.
It is important to keep both xda and Android running on the same principles it started with. Don't let this keep happening guys! This is very serious, a lot of developers are breaking the law doing what they are doing!
Click to expand...
Click to collapse
Let me preface this by saying that I agree with you..
However android is meant to be open source, the license that they use (Apache) does not require it.. The reason they chose the Apache license was to give people the freedom to choose (their words). So technically people like miui don't have to post source for anything other than kernel (which is GPL).
This link has some good info on it.
http://source.android.com/source/licenses.html
But even CM doesn't have to provide source, which in recent history they haven't while starting builds.. We can't demand source, when the licensing doesn't demand, but that doesn't mean we still can't prove direct kang. The reason I have android over anything else is the freedom it gives and the open nature of it.
Edit: and you should always credit someone if you are using their work, and also have their permission. I was referring to general source from android itself, not from each other.
_______________________
No d3rp left behind - ranger61878
The problem is, nobody wants to start a ROM from the ground up, and the people that do are already involved into team projects (CM/MIUI). It takes a long time to create a ROM from the ground up that utilizes all of a phone's hardware properly. Look how long it took CM to get 4G onto the EVO 4G, and that was a team of highly skilled individuals practically reverse engineering code to do it.
Now imagine all of the copy and paste kitchen users here trying to accomplish that. It just won't happen lol.
That's why we have pretty much the same thing in different colors. It kind of sucks, but hey, HTC did the majority of the work, and if something already works good enough, the average person will be fine with and use that.
Yeah, it does slow down the evolution and innovation of Android as a whole, but you have to put some of the blame on OEMs for pushing out 45 different phones a year. Nobody is going to be encouraged to create something from the ground up for a phone that will be replaced and obsolete by the time they're finished.
The G1 is the prime example of a great phone that got tons of developer support, tons of new things, and tons of unique ROMs. But that was the beginning, and I doubt that's ever going to happen again.
HTC all but pushed this EVO 3D out, and forgot about it. They've released a good 19 phones since then at the rate they're going, most of us will have moved on to the next one in a few months. Sad but true.
That is why I have stuck with and will probably continue to use a Stock ROM, modified to my liking and stripped. There isn't much else you can hope for. 3D has failed to really take off like HTC and the rest of us wanted. There is no motivation for any of the teams out there to focus on reverse engineering their ROMs to use 3D. MIUI to this day hasn't bothered with WiMAX and with good reason. Sprint all about blatantly announced its slow death in favor of LTE. It would have been a waste of time for the MIUI team to implement it. Kudos to Team Win and CM for gracing us with it on the EVO 4G. But, hindsight has probably made people mad that all of their time and energy went into something that's getting canned.
Alot of good points freeza. These are paragraphs I like to read.
Temari x Shikamaru
Hello Everybody,
I just wanted the ICS for my device as we are still running on GB and which is awful thing for an Dual-Core,Tegra-2 device(Micromax A85 a rebranded Mobile of K-Touch w700/Cherry Magnum 2X).We tried to create a ICS for our device but we failed as we are not having kernel sources for our device and they haven't released kernel for any device.
And so i started asking developers that can they help us and the only answer i got was no and they kept saying no way , your situation is hopeless and all that.
And Now I Just Wanted to know That when a mobile is manufactured first time they didn't have any kernel source for it they create it for the device or develop it for the device and when they can develop it then why we can't develop it as we all are humans and what they can do i can do.So Please Tell me now how to create kernels not that you can't,nothing can be done.And I think that Xda Is A Great Site and now i wanna know that are there real developers or there are some kind of script kiddies present in Xda.
Now Show me What developers have got and i know deep inside my mind that there are developers which can help me.They are just needed to be discovered.!!!!!
Well....it is possible, but ts a ton of work and will take months...its something no one wants to do for free, as the end result isn't worth all the work.
I'm no expert on kernels...I'm actually pretty new to them, but I'll tell you this: you have to identify every single chip in your device, you then need to implement there drivers...you need to make thousands of files....the end result is a folder that is over 100 MBS....almost completely "text" documents....I would never even attempt it unless I was getting paid a lot of money...
The people who make these from scratch (manufacturers) typically have teams of people who are specialized who have gone through years of schooling and work to get where they are at now.
And keep in mind there is different kinds of development....don't start calling people script kiddies if they don't know how to make kernels from scratch...for all you know thy could be one of the best app or game developers around...they are just specialized in a different area
I really dislike the way you are asking for help...you seem to be indirectly putting down a lot of people in the OP...and basically saying if you can't build a kernel from no source then you're not a developer...these people have jobs and life's, they don't have the time to make a kernel from nothing. The reason manufacturers are able to is because that is there job...that's what they do for hours a day everyday...
Anyways...try bugging the manufacturer for source...they have to release it or they are in violation of GLL (I think that's the name...) and they could get sued...as far as I know due to android being open source kernel source must always be released.
Sent from my SGH-I997 using Tapatalk 2
mg its GPL v2.0
mg2195 said:
Well....it is possible, but ts a ton of work and will take months...its something no one wants to do for free, as the end result isn't worth all the work.
I'm no expert on kernels...I'm actually pretty new to them, but I'll tell you this: you have to identify every single chip in your device, you then need to implement there drivers...you need to make thousands of files....the end result is a folder that is over 100 MBS....almost completely "text" documents....I would never even attempt it unless I was getting paid a lot of money...
The people who make these from scratch (manufacturers) typically have teams of people who are specialized who have gone through years of schooling and work to get where they are at now.
And keep in mind there is different kinds of development....don't start calling people script kiddies if they don't know how to make kernels from scratch...for all you know thy could be one of the best app or game developers around...they are just specialized in a different area
I really dislike the way you are asking for help...you seem to be indirectly putting down a lot of people in the OP...and basically saying if you can't build a kernel from no source then you're not a developer...these people have jobs and life's, they don't have the time to make a kernel from nothing. The reason manufacturers are able to is because that is there job...that's what they do for hours a day everyday...
Anyways...try bugging the manufacturer for source...they have to release it or they are in violation of GLL (I think that's the name...) and they could get sued...as far as I know due to android being open source kernel source must always be released.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
It's GPL my friend.
But to answer OP's question, taking the Linux kernel and configuring it to boot on a phone/tablet takes a HUGE amount of effort and time. This is something that paid developers do for companies like HTC or Samsung. It usually requires a whole team of developers who work on it months, or even years before the release of the device. Even then, the developers still continue to improve on the kernel and the manufacturer can release an OTA update. I'm not saying that it's impossible, but it is a task that is definitely not worth it. It's just better to ask the company for the kernel sources.
Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1
Why are some people too good to hang out in their threads and answer questions about the builds they post???
It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN
Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT????
Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet
WOW Man..
pitbull8265 said:
Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1
Why are some people too good to hang out in their threads and answer questions about the builds they post???
It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN
Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT????
Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet
Click to expand...
Click to collapse
Could not have said it better.... You hit the nail right on the head.. People respect those who back their work with support:good::good::good:
This DOES seem to be in SHORT reserve.. WELL STATED
Impressive
I have noticed this too.. Its like these people are too GOOD for Q&A and sometimes even respond to questions like they are PETTY and an inconvenience.. There ARE some who DO help, and those people deserve to know they are appreciated.. You in particular, have helped me a ton, so thanks.. Maybe you'll start a movement, and more people will start doing their part to help their followers...
+1
There is a SERIOUS shortage of helpers and an overage of shovelers
All these builds keep coming, and still the same problems on the one they put out before with a different NAME for the ROM.. Its like they change the name and recycled it..
I read through threads now, and if the OP doesn't hang out and help their users, I wont use their builds anymore.
Couldn't agree more!! Nicely said too
Be proud of your work.. Stick around and make sure people can..ya know, enjoy it too..
It's quality not quantity that matters. Stepping on other teams and developers to rush something out just to say "FIRST" will get you no where.. So while timely updates are important, if that's the only thing you post in your own thread.. "New build is up" when there's been 10 pages of people asking questions... I'll never support you, both publicly or financially.
I understand new enthusiast can be quite frustrating or maybe you just aren't a people type of person.. team up with someone that is... pass the q&a on to them, but do fricking something, people want support for YOUR roms and if you put out 20..that means all 20.
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
mapatton82 said:
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
Click to expand...
Click to collapse
Yea, I'm somewhere between this and the op. They shouldn't be 100% absent, but on the same note, some consideration for the above quote is in order too.
While were venting, its possible the devs haven't figured out how to fix some of these issues, but it doesn't do a dam bit of good for 50 people to complain about the same thing and no one is posting logcats. So don't complain about things not getting fixed, if your not attaching logs to every post about issues.
Just my 2c, add 97c more and go buy a cheeseburger.
Sent from my G3, Unlocked by Team Codefire
mapatton82 said:
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
Click to expand...
Click to collapse
Then why put out 20 instead of 1 that they can handle is the point!!
Variety is the spice of life. I'd rather have 20 that will get fixed eventually than just 1 that works perfectly. If they are all too similar for you then just move on to another one, build your own, or just wait for fully featured lollipop which will be here soon enough. If a thread is maintained or not - I'm just happy to have a thread. A couple devs have walked away already and it'd suck if more left. Just be grateful for what we've got and be patient.
Kris Nelson said:
Then why put out 20 instead of 1 that they can handle is the point!!
Click to expand...
Click to collapse
The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes.
I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?"
Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home.
I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs.
Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report.
Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it.
Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time.
I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple.
However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some.
In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person.
Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand.
Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well.
Ciao!
If you're a good parent, when you bring a child into this world, you raise it, and nurture it... creating it is not enough...
noun
1.
the act or process of developing; growth; progress:
iBolski said:
The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes.
I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?"
Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home.
I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs.
Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report.
Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it.
Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time.
I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple.
However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some.
In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person.
Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand.
Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well.
Ciao!
Click to expand...
Click to collapse
Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making..
I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL
Kris Nelson said:
Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making..
I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL
Click to expand...
Click to collapse
I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs.
And since it does appear that you do not have to be a developer to post in the standard DEV forum, then that makes even more sense.
I do know that in another forum I frequented a lot, you were given developer status and only developers could create new threads in the DEV/ROM forum. That was to prevent a lot of "spam" postings of ROMs.
Makes me wonder if that's what is happening here.
iBolski said:
I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs.
Click to expand...
Click to collapse
I wish you were correct but nope, he is the builder and maintainer. Trust me many more than 5+ when you include other carriers as well.. But not just the one, others have started as well... It's very frustrating that after 1 week, several messages of a very specific problem (not mine just someone i was helping) on different sites where they are posted.. I have to track down someone that i know can help but has NOTHING to do with any of these roms...and gets zippy cash.. Though he should..lol
Anyway, i truly value great developers and have learned who to support and who not to. I like to help people so the developers can build awesome stuff and its my way of keeping the simple crap of your plate so you can do just that..but when i can't even find the answer, the developer should be available.
Just saw your edit.. Yes i think that is happening too. I was always under the assumption that builders/maintainers did so for the actual devise and carriers they use.. I guess that's no longer the case.
Oadam11 is a builder of various roms for our G3's from source repositories available for anyone to build from, and anyone to commit to. He may or may not be doing any commits/merge requests - and even if he did those contributions might not be accepted into the various G3 forks.
In any case, he might not be in a position to contribute to feature requests or bug fixes. He might not be running his own builds of all these roms, past checking to see if they will boot and more or less work.
Say Team Vanir does a fork of their work for the G3, an official one. Ok, then you would ask for support from members of Team Vanir, sure, though you might not get much, depending on a lot of factors (including your attitude...) Then consider the possibility that someone just builds something like Commotio from publicly available sources, with just enough tweaks from somewhere to get it to compile and run, unofficially, on one or more G3 variants. I suspect that is where oadam11 is coming from. He doesn't create the roms, he builds them for G3's. He watches the repositories for each rom he has built for us, and when he sees that rom's devs have checked in and merged useful updates, then he rebuilds for us when he has time. Builds take a while. Then he makes them available for us users to download and install them, after some degree of testing.
The point is that he is in no way responsible for supporting the builds he produces of these team's work. It would be impossible for him to anyway. I am sure he gets permission and some degree of cooperation from any team project he builds from, but he is NOT a team member, or major contributor, for all of them. He is a noble builder and distributor, and you should expect nothing more from him than What he is already providing.
If you want to get a problem or new feature dealt with on any given rom, you must deal with the team's source contributers by raising issues on their gerrit or maybe working on an outstanding and team-prioritized bug as a contributor.
Sent from my VS985 4G using Tapatalk
Thank you..you actually confirmed the point I was making. However, is the average person going to know all this? Of course not...should they do their research prior, of course but they don't... I see good teams being hurt by this as well.. Vanir just had an issue the other day.. Something is being lost in translation and by no means was i only referring to Adam.
I understand. It is interesting that in G+ just a little why ago someone asked David Kessler of Team Vanir who was their maintainer of the G3 Vanir and he replied that they don't have one.
There was also discussion about someone providing support, like answering questions. The idea of supporting a clueless user who had tried to flash TouchWiz onto a Vanir device, by beating the user over the head with an iPhone6+ was suggested. The devs have no patience with such users, generally.
That said, Holy Angel seems exceptional.
Sent from my VS985 4G using Tapatalk
The problem I have, is that when a person POSTS a Rom, and are the OP, they need to support what they post, and help the people posting questions in the thread, or BOW OUT!!! There are people posting and dumping... DONT Post a ROM if you're not willing or able to help the team you are Posting links to... Dont post it and then say "Any problems, contact THEM"
THAT PERSON mentioned, has a lot of them, all as OP, none supported other than.."New build up"
Raising the age limit for COPPA
The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to your liking.
That will really teach those mean developers a lesson.
Don't forget to complain about the slow speeds of free downloads as well.
It's also a good idea to stop using a build if the developer won't add features you want, and soon, too.
DeanGibson said:
The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to his/her liking.
That will really teach those mean developers a lesson.
Don't forget to complain about the slow speeds of free downloads as well.
It's also a good idea to stop using a build if the developer won't add features you want, and soon, too.
Click to expand...
Click to collapse
Just because you want a feature, doesn't mean it's a good feature to add. If you did that, you would end up with something that could eventually become impossible to maintain.
There are SO many bugs right now in the AOSP code that these devs are trying to fix to make it work on this phone. I would rather those get fixed first.
And, do you think you are the only one to ask for features?
I'm a developer, not for android, but I write code for a living. And what you are asking for is what we call "scope creep". We have to weed out the "must haves" with the "wants". Must haves are the things that they user must have in order to perform their job. This is usually adding functionality that isn't there currently that is needed to complete their job. The "wants" are "I would like to have the ability to clear out all background apps with a single button or swipe". That is NOT needed on this phone, but it's a nice "to have" option, but it doesn't affect the overall performance of the OS itself. Yes, you might say it does because you can clear out the background apps, but in reality, those apps are NOT running. I don't want to get into the specifics of android app management, but those apps you see in the "recent apps" history are NOT running. They are suspended and not taking up ANY CPU cycles, what-so-ever. If they happen to be, then it's a poorly written app, and it means the dev knowingly circumvented the Android OS app management process which is a big no-no. In that case, you should go back to the dev of the app and demand they fix that.
But, you are free not to install the ROM. That's fine and that's your choice, but it just irks me when I see people make complaints like this who probably have no idea what the software development life cycle is all about. To me, fixing bugs right now is the main issue, not adding pretty enhancements to the OS.
And who's to say they aren't working on what you ask, especially if you ask for fixes to major issues (such as battery life, radio, etc)?
Remember, these are UNOFFICIAL releases. They are based off of AOSP source which is pretty much device-agnostic except when it comes to Nexus devices since those are Google devices and therefore, the AOSP source is built for those type of devices.
Android is completely different from iOS. iOS is built for a set of hardware that doesn't have much variance like Android does. Hence, that is why Apple controls both the software AND the hardware of iPhones. It means less fragmentation across devices, but it also means, they decide what is best and you have no way of getting the source.
Google releases the source for Android so you CAN have these custom ROMs built. But, because one Android device has a different hardware configuration from another (CPU and GPU's being the biggest ones), then anything that can take advantage of the hardware architecture for a particular phone means having to change the AOSP source to use any of those "advantages" from that hardware. Which then means, that source no longer works on other phones, only for the phone they modified it for.
So, give the devs some slack, please. They are working hard on it and it's not one dev. If it were, then give the guy even MORE slack. The source for Android is over 12gb along. That is where it's not even compiled. And, compiling the android source generally takes about 90 minutes. So, each "fix" they do requires recompiling (90 minutes) and then testing.
Then, more than likely, the "fix" either didn't work or it possibly broke something else. That means, going back, determining the issue, fixing it, recompiling (wait another 90 minutes) and test again.
That all takes time, people. We developers are NOT magicians, even though it might seem like it.
So, try to imagine trying to fix all the big bugs that you know about, then have to come here, read through ALL the posts and then log those requests down, prioritize them based on all the other work you have, make those changes, recompile, test, etc. It's not a easy and it gets frustrating. But believe me, when we do fix an issue or are able to give the users what they want, we get an extreme amount of satisfaction knowing that we were able to satisfy the "customer".
So please, be careful what you state about devs. Those that do read here usually have thick skins, but complain enough, and they might just quit and then you have nothing.
I understand where people are coming from, but you've been blaming the devs when it's not their fault. Again, the android source is huge and it takes more than one person to work on it. Especially if they are responsible for more than one device. Some devs are working on source for more than just this phone. So, add that to what I already stated and hopefully, you can begin to understand what the devs are going through.