Database Info

Submitting Patches to the Repo / Forking

Hi all!
I'm an android developer, and I regularly read the official android-dev and android-porting lists, but on all the fan blogs and from lurking here, it seems that all the good development is coming from XDA-dev!
So why don't you guys do some patch submission? Features like auto-rotating browser and the transition animations should really, really be in the main source, but the official Android team have their thumbs up their asses in regards to UI/polished stuff.. (I bet they're too busy working on the lower level cellular stuff and the ARM-generating stuff like in the *flinger libraries).
So you guys should make some patch submissions over at (http://source.android.com/submit-patches)!
That way, the next RC will have all of these lovely features you guys have implemented.
((Or, alternately (but more ambitiously), fork the entire codebase. Strip out the DRM and add a framework for native code execution. Perhaps that's a pipe dream, though..))
Thoughts?

I think forking the Android source would be a very nice touch, if Google doesn't pull it together. We could still add on to stuff from the official code, but add on all the special stuff that Google refuses to (they've said they won't add the ability to change CPU speed, etc).

Oh, absolutely, there would be numerous advantages to having a fork. It should definitely be discussed! I'm afraid that Google may be trying to exert too much control on their platform in ways that we don't always want, so there is nothing legally to stop us from forking and maintain a more badass tree. GitHub could provide the hosting.
Of course, it might be a waste of effort. If you submit the badass patches, then the good features here go out into all the phones in the next versions. Work on the fork, and only the selected users who are able to flash their own phones can use it, unless some Chinese companies start using it or something like that.
Names?
XanDroid? I'd rather like to see Mandroid with in a slick black theme..

Well to me it seems like the only people doing cool things right now with android have rooted devices
So why cant you ***** a little on google lists to make them actually do some work. The Roadmap @ http://source.android.com/roadmap is a joke. Either they give us root or they start working imo. =)

Seanambers said:
Well to me it seems like the only people doing cool things right now with android have rooted devices
So why cant you ***** a little on google lists to make them actually do some work. The Roadmap @ http://source.android.com/roadmap is a joke. Either they give us root or they start working imo. =)
Click to expand...
Click to collapse
Do you think that the release of the new unlocked Dev phones will change things?

Yeah it'll most probably shake things up a bit, however what about all those that already have a g1?
I for sure isnt buying a new phone to get root.

But even so, we're still talking about modifications to the OS and the packaged applications, which would be released in the next RC version, so even non-root users would get the features in the next update, along with anyone running Android on something besides a G1.

my .02
Id say submit some of the things found here and see what goog does with it, if they openly add these things that need root at this point and let xda dev participate in the OS with such submitions...then cool thats how open source works best, when anybody can add to the project, a phone OS utopia
If they ignore it then, a fork is the way to go but give google a chance to do the right thing first before, just leaving them in the xdadevs dust with a custom distro...

bhang said:
Id say submit some of the things found here and see what goog does with it, if they openly add these things that need root at this point and let xda dev participate in the OS with such submitions...then cool thats how open source works best, when anybody can add to the project, a phone OS utopia
If they ignore it then, a fork is the way to go but give google a chance to do the right thing first before, just leaving them in the xdadevs dust with a custom distro...
Click to expand...
Click to collapse
Google has refused to add multiple features. They feel that they aren't necessary, or that your average consumer wouldn't want it (main thing I can think of atm is CPU speed).
If they don't add the features we request, simply because *they* don't like them, then a fork would get us exactly what we want/need. After we fork it, and the number of users using stock Android plummet, maybe they will listen .

I see a problem with forking... who says what is allowed and not allowed? That is the main problem. Now if you wanted to just add an app that would be one thing but there is not going to be an easy way to do this.

Gary13579 said:
Google has refused to add multiple features. They feel that they aren't necessary, or that your average consumer wouldn't want it (main thing I can think of atm is CPU speed).
If they don't add the features we request, simply because *they* don't like them, then a fork would get us exactly what we want/need. After we fork it, and the number of users using stock Android plummet, maybe they will listen .
Click to expand...
Click to collapse
Given the number of G1s with modified fw installed compared to the total number of sold units, I somehow doubt the number of users is going to plummet.
IMHO it would be a needless fork unless some new or considerably modified features were planned. Better to just patch the functionality into the official builds, if at all possible.

I'm not convinced by that logic. There would be an important difference between a fork and patched versions of the firmware, as a fork would have a totally different design philosophy. Whereas Android is focused on speed (or whatever the hell they're concentrating on..but to be honest, I think they're dicking about over there), Mandroid could have more focus on polished features and low-level access. ((And! No DRM, and I'd like to see some more security features..ZRTP?))
Either way, I think it's really important for the success of the open future of phones that the open source community take and give back. There's no need for the back-and-forth like with, say, PSP-cracking as we have the source code and we are allowed to do whatever we like with it. If we just keep patching what they give us and keeping the modifications closed, then we aren't really in control.
As for project management, I'm absolutely sure there are people who are capable of maintaining an active open-source project such as this, as long as there is a well-thought out design philosophy. I'd love to be involved, if enough people are willing to give it a shot. But, first, it'd be easier just to submit patches.

Miserlou! said:
PSP-cracking
Click to expand...
Click to collapse
PSP cracking is insanely different. If you were in that scene, does my name look familiar ? Was net admin at toc2rta/malloc, admin of psp-hacks.com, worked with a lot of people on a lot of stuff that I barely remember as it was years ago .
But for the PSP, we were working with a system we knew nothing about. So yes, Android would be a lot simpler to work with. But if Google doesn't listen to us, it's not like it would really matter.

neoobs said:
I see a problem with forking... who says what is allowed and not allowed? That is the main problem. Now if you wanted to just add an app that would be one thing but there is not going to be an easy way to do this.
Click to expand...
Click to collapse
Android is licensed by both the Apache Software License (do whatever you want with it) and the General Public License (do whatever you want with it as long as you make the source code available for others). We are certainly allowed to do this, but the problem lies with the G1 owners running the official RC30. They wont have the rights required to flash the image which leaves them out of the party.

2 words
The community(did I spell that right?)
Bhang

Datruesurfer said:
Android is licensed by both the Apache Software License (do whatever you want with it) and the General Public License (do whatever you want with it as long as you make the source code available for others). We are certainly allowed to do this, but the problem lies with the G1 owners running the official RC30. They wont have the rights required to flash the image which leaves them out of the party.
Click to expand...
Click to collapse
I meant who is going to the be decision maker of what features will be added... The Community as a whole? What about some that want it but only 25% of the community wants it?

neoobs said:
I meant who is going to the be decision maker of what features will be added... The Community as a whole? What about some that want it but only 25% of the community wants it?
Click to expand...
Click to collapse
That's what project leads are for. And hypothetically when enough people are dissatisfied with the xda-dev fork they will go and create their own fork. Except I don't think there is any real argument yet to go and create an xda-dev fork in the first place. Forking an operating system meaningfully is not a weekend project for a single person.

I have said it before, let's give them a bit more of a chance, a fork isn't something a guy can do in a weekend.
So let's see what happens in RC3X, the next release will give folks a bbetter idea of where their heads are at. If enough of the community is unhappy there will be a fork
Bhang

If you have twitter....tweet to HTC so we can get our Kernel!!

I'm just putting this in a new thread so that everyone can see it without having to accidentally come across it in the Hero Source Attempts thread... Some other users have realized that if everyone who has a twitter account messages HTC through twitter, it becomes bad PR for them because everyone sees it, and they are more likely to meet our demands at a speedier pace.
If you really want lots of cool ROMs and lots of options, we gotta get that dang kernel, and this seems to be the best tactic so far. Supposedly it worked in getting the GSM kernel. SO GET TO WORK PEOPLE! START TWEETING/Messaging THROUGH TWITTER @HTC!!
Here is the original post by another user:
I personally believe that these two methods would work fastest. If they get 1000 emails, no one hears about it. But if they get 1000 tweets, or an article on Engadget, it's bad PR. This is basically what happened with the GSM Hero:
slashdot article - tech.slashdot.org/story/09/10/16/1720224/HTC-Dragging-Feet-On-GPL-Source-Release-For-Hero-Phone
acknowledgement - twitter.com/htc/status/4928377685
compliance - twitter.com/htc/status/5071201112
admission of responsibility - twitter.com/htc/status/5071514606
(sorry, I've been a member for almost 3 years but this is my first post... can't post links)
I tweeted the following, please retweet or write your own similar: @htc When can we expect to see the CDMA (Sprint) Hero kernel source code? It's been 3 months, this is ridiculous! #gplviolation

I posted a tweet, lets hope this will push them to at least acknowledge the requests.

posted a tweet too hope it helps

Posted a Tweet, i pray engadet will pick up on this.

lol been posting at least 2 tweets a day for the last 3 days. glad to see others are joining in.

Yup. Tweeted
@HTC come on, it's long past the weekend.CDMA Hero sources please.#HTC get your act together #GPL #Violation #CDMA #Hero #Sources
Click to expand...
Click to collapse
to try and get as many tags in as possible...
EDIT: Well, a search for #gplviolation on twitter is certainly interesting! (Try it...)

if you search htc you get a lot of people asking how to update to 2.x reply tweeet them to get the word out if you can.

Done! I hope we see something soon.

Done! Tweeting twice a day.

If you post a tweet regarding this, please be sure to include @htc, @sprint, and add the #gplviolation hashtag for tracking purposes.

tweet sent!

Does it really matter much if we get the kernel? As I understand it, there's a load of closed-source proprietary software running under the hood on our devices.

It depends. If HTC compiled proprietary code into the kernel itself, they're between a rock and a hard spot. Under the GPL, anything physically compiled into the kernel MUST have its source released. If HTC licensed proprietary camera drivers from anyone (Qualcomm, most likely) under terms that forbid them from disclosing the source, it's *their* problem to worry about.
IMHO, if that's the situation HTC is in, the best thing they could do to at least get everyone off their back would be to just go ahead and release their best 2.1 internal build (officially, for testing with the Android Emulator, since they can't officially condone rooting) as a "developer's preview". If they did, the necessary files would be ripped and built into a working 2.1 heroc distro within days, if not hours, and pretty much everyone would forget about the source for now & give them some breathing room for a few months.
As I understand it, even if HTC's 2.6.29 kernel had bugs, as long as those bugs weren't with msm_camera itself, we could use THAT 2.6.29 kernel to bootstrap newer builds of 2.6.29 (kind of like how Microsoft used prerelease versions of Visual Studio 2010 and Windows 7 to build Windows 7 itself). The problem now is that there's a literal hole in the 2.6.29 kernel that we can't fill, because we have neither the include file's source nor a compiled binary to drop in place.
Now, it's important to remember that we can't actually demand the 2.1 kernel yet under the GPL, since it hasn't actually been released yet. I'm only mentioning that as an *alternative* that would satisfy pretty much everyone for now, to give HTC some constructive alternatives to consider if releasing the full 1.5 kernel source for heroc is, in fact, completely out of the question due to licensing problems arising from msm_camera. Regardless of whether or not HTC can release the source to msm_camera for heroc, they can obviously redistribute 2.6.29 binaries built from it... and one of those binaries would be more than adequate for our purposes right now.

miamicanes said:
, it's important to remember that we can't actually demand the 2.1 kernel yet under the GPL, since it hasn't actually been released yet.
Click to expand...
Click to collapse
I realize you are referring to a CDMA-specific kernel (I thought 2.0 and after would be GSM and CDMA ready?), but the kernel for 2.1 HAS been commercially released. It's running on the Nexus One. Demanding the code under GPL is perfectly reasonable.
I mention this because this problem is now beyond any specific device. The manufacturers and carriers are, in my opinion, abusing the GPL and we ought to have a united front on that fact.

5tr4t4 said:
I realize you are referring to a CDMA-specific kernel (I thought 2.0 and after would be GSM and CDMA ready?), but the kernel for 2.1 HAS been commercially released. It's running on the Nexus One. Demanding the code under GPL is perfectly reasonable.
I mention this because this problem is now beyond any specific device. The manufacturers and carriers are, in my opinion, abusing the GPL and we ought to have a united front on that fact.
Click to expand...
Click to collapse
The source for the kernel compiled for the Nexus One, which uses completely different hardware, is (or must be) available. HTC does not need to provide it, as they are not the company selling the device - Google is.

^^^ Just to add to what he said, the kernel for the Nexus One also lacks the compiled-in driver for the CDMA Hero's camera.
Here's an example to illustrate why the GPL places so much practical importance upon the availability of ALL source used to build the kernel... and why it's generally accepted that proprietary binary kernel loadable modules are OK (at least, among pragmatists like Linus). Suppose the maker of your PC used a proprietary NVIDIA chipset with no public documentation, and shipped it with Ubuntu Linux on the hard drive. However, suppose they compiled the video driver directly into the kernel.
Anyone who bought the computer would be put in a needlessly bad position -- unless someone reverse-engineered the chipset, you wouldn't be able to use any distro of Linux not officially blessed and released by the computer's maker. You might be able to use a slightly newer build of Ubuntu if someone did a binary diff on the newer kernel and pulled out the metaphorical duct tape. You might possiblybe able to get away with using the old kernel in a newer distro (enjoying some bugfixes in the other programs besides the kernel itself). You might even be able to diff a newer build of Linux on a newer, but similar, computer released by that maker that they happened to ship with a newer kernel. But you'd never really be able to build your own kernel the way God and Linus intended, because the kernel and proprietary video driver would be inseparable. If you tried, the compiler would complain because it was missing a very, very important #include file -- the proprietary video driver.
On the other hand, suppose the manufacturer bundled the proprietary video driver as a loadable kernel module (.ko file). NOW, things change significantly. Richard Stallman might still grouse because you don't have the source to the video driver, but in utilitarian terms, you're much better off than you were in scenario #1. Although you're still dependent upon the manufacturer for a newer video driver, because it's physically separate from the kernel itself, you can build your own newer, better, and different kernels whenever and however you'd like. As long as the low-level interface between the kernel itself and the kernel module doesn't change on your platform, the two are sufficiently abstracted from each other to allow one to change without affecting the other.
IMHO, the most disgraceful part of this whole thing is that we theoretically have phones running an open platform, but we're still reduced to ripping binary images and tacking them together with metaphorical duct tape, just like we were with Windows Mobile. If anything, it's gotten worse. At least Windows Mobile didn't have to be rooted, and the newer versions generally didn't break the previous version's device drivers. Sigh.

miamicanes said:
^^^ Just to add to what he said, the kernel for the Nexus One also lacks the compiled-in driver for the CDMA Hero's camera.
Click to expand...
Click to collapse
Right, I understand this. I was making the point that the fact that 2.1 has a commercial release means the we can demand the code under GPL. Shouldn't we be aiming for a unified android kernel source with GSM and CDMA support, adding binary drivers/libs (or setting device-specific compile flags) as needed? Nexus being controlled by Google (who seems to be releasing their modifications immediately on git) might be a starting place for this de facto Android.
I'm simply advocating for thinking beyond our own personal devices.

Holy shut!!! Welcome to the age of technology.... **** with us and we will tweet Ur ass to death. Lol. It's an all Twitter offensive. Were declaring Twitter war on HTC until we get source. ROFL

@5tr4t4: well, it was more for the benefit of others who might stumble on this thread and aren't quite sure why it's such a big deal
I think what Jonnythan was saying is that there's no need to get the source to the Nexus One's kernel from HTC, because you can download it right now directly from Google.
As far as platform neutrality goes, we'd be 99.9% of the way there if HTC would just move the proprietary stuff out of the kernel proper and into loadable kernel modules so they'd simultaneously be in compliance with the GPL and not making our lives needlessly difficult by making us jump over hurdles that shouldn't be blocking our way in the first place

miamicanes said:
As far as platform neutrality goes, we'd be 99.9% of the way there if HTC would just move the proprietary stuff out of the kernel proper and into loadable kernel modules so they'd simultaneously be in compliance with the GPL and not making our lives needlessly difficult by making us jump over hurdles that shouldn't be blocking our way in the first place
Click to expand...
Click to collapse
If they were to move some stuff to binary *.ko's they'd most likely move all non-boot-essential hardware support out there, which would actually make things much, much more challenging for us. That way they could have a "universal" kernel (and GPL source tree) that is used across devices, and each device just has its own *.ko's. They'd only have to release one (fairly useless) tarball for GPL compliance. Be careful what you ask for.

[NEWS][KERNEL][4.10.2011] Thunderbolt Kernel by Ziggy

For those familiar with Ziggy's work, he finally compiled a kernel for the Thunderbolt. It is a beta kernel so there will be bugs, so test it out. For reporting bugs please comment on his website. He is a great kernel dev. Please donate to him if you like his work. I am in no way affiliated with Ziggy, just wanted to spread the news.
UPDATE: My previous thread was closed because of a direct link I provided. I decided to create a new thread just for discussion purposes and bug tracking. You can google "ziggy471" to get to his site for the kernel. You can also google the name of the latest kernel update for the link.
Latest Kernel Update:
Beta Kernels 10 Apr 11

Running BFS kernel, and getting the best battery life I've ever experienced. HIGHLY HIGHLY HIGHLY RECOMMEND.

Last thread was closed because ziggy is not following GPL and is not posting his source, which is required. XDA cracks down hard on people who do not follow GPL.

nemesys504 said:
For those familiar with Ziggy's work, he finally compiled a kernel for the Thunderbolt. It is a beta kernel so there will be bugs, so test it out. For reporting bugs please comment on his website. He is a great kernel dev. Please donate to him if you like his work. I am in no way affiliated with Ziggy, just wanted to spread the news.
UPDATE: My previous thread was closed because of a direct link I provided. I decided to create a new thread just for discussion purposes and bug tracking. You can google "ziggy471" to get to his site for the kernel or use the pic attached for reference. You can also google the name of the latest kernel update for the link.
Latest Kernel Update:
Beta MECHA Kernel 6 Apr 11
Click to expand...
Click to collapse
You don't get it...

cabagekiller said:
Last thread was closed because ziggy is not following GPL and is not posting his source, which is required. XDA cracks down hard on people who do not follow GPL.
Click to expand...
Click to collapse
You are correct and I spoke to Ziggy on this issue and was told when his kernel is stable enough he will release his source.
adrynalyne said:
You don't get it...
Click to expand...
Click to collapse
Whether I get it or not, I think his kernel deserves a forum for discussion. Thank you for your 2 cents.

I agree, my battery life is amazingly good.
Sent from my ADR6400L using XDA Premium App

His new test ones are out.

ridobe said:
His new test ones are out.
Click to expand...
Click to collapse
Yeah and it comes with a script! lol

Anyone else's phone running super hot with the new kernel that was released today? Mine is just too hot to touch almost...thinking about going back to the kernel before this update if it doesn't change soon.
Thunderbolt Rooted!

andrew53517 said:
Yeah and it comes with a script! lol
Click to expand...
Click to collapse
I don't have access to a computer all the time (or very often). Is there a way to copy/paste that script into the init.d folder through Root Explorer (or another app) instead of having to push it with ADB? Thanks in advance for any help!
Edit: Nevermind I figured it out. Having random restarts with the Kernel though so I'm reverting back to the BFS 4-6-11 kernel. That one was rock solid and the only issue was the proximity sensor.

I have his 4-10 BFS, what are you suppose to do with the script and why?

Going by what Ziggy said on his blog, the script is used to lower voltages/save a lot of power. I didn't have good luck with the kernel/script combo or just the kernel itself. It ran super hot and I was getting random lockups and random reboots on even the stock clock frequency. I moved back to the 040611 BFS kernel since the only issue I had with that kernel was the proximity sensor. The 040611 kernel also had insanely good battery life (or at least for how I use the phone, it did).

LSUstang05 said:
Going by what Ziggy said on his blog, the script is used to lower voltages/save a lot of power. I didn't have good luck with the kernel/script combo or just the kernel itself. It ran super hot and I was getting random lockups and random reboots on even the stock clock frequency. I moved back to the 040611 BFS kernel since the only issue I had with that kernel was the proximity sensor. The 040611 kernel also had insanely good battery life (or at least for how I use the phone, it did).
Click to expand...
Click to collapse
+1. It locked up on me too and ran super super hot. Reverted back till fixed.
Thunderbolt Rooted!

nemesys504 said:
Whether I get it or not, I think his kernel deserves a forum for discussion.
Click to expand...
Click to collapse
+1
LSUstang05 said:
Going by what Ziggy said on his blog, the script is used to lower voltages/save a lot of power. I didn't have good luck with the kernel/script combo or just the kernel itself. It ran super hot and I was getting random lockups and random reboots on even the stock clock frequency. I moved back to the 040611 BFS kernel since the only issue I had with that kernel was the proximity sensor. The 040611 kernel also had insanely good battery life (or at least for how I use the phone, it did).
Click to expand...
Click to collapse
mine didn't lock up, but it was warm all the time (even when i wasn't using it) and had insane battery drain, like 40% in 2 hours. i reverted to 4-6-11 kernel and all is well again
edit: this is obvious to xda regulars, but noobs should download & flash the MECHA kernels for Tbolt. all other roms are for other devices. if you flash your new Tbolt with an EVO rom, you will be a very sad panda

Where is the source for this kernel?

jlevy73 said:
Where is the source for this kernel?
Click to expand...
Click to collapse
This has been asked several times, so I figured i would jump in and share what I know...
I speak to Ziggy almost daily when helping him debug stuff and he has spoken rather openly about this. He's not playing games or avoiding the issue and is going to post his sources and patches soon. There are one-and-a-half reasons he hasn't so far:
The half reason: There are some voltage issues and frankenstine tree problems that are causing some non-booters that need to be fixed before a public release can be considered safe. Now, the reason this is a "half reason" is because some may argue that he still needs to release it under GPL terms even though it's a beta, while others would argue that HTC doesn't release their betas under the GPL until they are safe either. If they did, HTC would have dropped their source 6 months ago, but they didn't. So it's an argument of where you stand semantics. I'm not telling you where to stand on that one - make up your own mind. However, it is worth noting that Ziggy himself never started a TB kernel thread SPECIFICALLY for the reason that he did not want to violate XDA's terms in accordance with the GPL. Other users started their own Ziggy threads independently
The bigger reason: He is currently in talks with an intellectual property attorney in order to retain personal IP rights on some of the code he has personally written, and was advised by that attorney to not release his full source under the GPL since that source would include the code he is trying to secure. Once that is taken care of, he will release the bulk of his source and patches, while retaining a few flashable patches for himself of his own personal code to further enhance the kernel - assuming he gets that all worked out with the IP lawyer.
That may frustrate some people, while making others very happy. I can also tell some of the devs are getting anxious since they see Ziggy added/changed/removed over 35,000 lines of code in the TB kernel and their eyebrows raise a little and they want his source so they can see what he's up to I don't know where you stand on the issue, nor will I tell you which side to take. I already have his source so quite frankly I don't care either. Again, I'm just the messenger sharing what I know. Don't hate on me if you don't like the info above - it's not my call
You'll all get the source/patches soon enough

i can't say i blame ziggy for doing things this way. it's his kernel, he has the right to do what he wants with it, including seeking intellectual rights. i'm glad he made his kernels available for the rest of us to try. more rom/kernel options is good for all of us

IANAL but sounds like walking a fine line...any of the witheld patches will be designed specifically for the purpose of merging with GPL licensed code. I'm sure the attorney knows his stuff, but at minimum doesn't seem in the spirit of AOSP.

eschelon said:
This has been asked several times, so I figured i would jump in and share what I know...
I speak to Ziggy almost daily when helping him debug stuff and he has spoken rather openly about this. He's not playing games or avoiding the issue and is going to post his sources and patches soon. There are one-and-a-half reasons he hasn't so far:
The half reason: There are some voltage issues and frankenstine tree problems that are causing some non-booters that need to be fixed before a public release can be considered safe. Now, the reason this is a "half reason" is because some may argue that he still needs to release it under GPL terms even though it's a beta, while others would argue that HTC doesn't release their betas under the GPL until they are safe either. If they did, HTC would have dropped their source 6 months ago, but they didn't. So it's an argument of where you stand semantics. I'm not telling you where to stand on that one - make up your own mind. However, it is worth noting that Ziggy himself never started a TB kernel thread SPECIFICALLY for the reason that he did not want to violate XDA's terms in accordance with the GPL. Other users started their own Ziggy threads independently
The bigger reason: He is currently in talks with an intellectual property attorney in order to retain personal IP rights on some of the code he has personally written, and was advised by that attorney to not release his full source under the GPL since that source would include the code he is trying to secure. Once that is taken care of, he will release the bulk of his source and patches, while retaining a few flashable patches for himself of his own personal code to further enhance the kernel - assuming he gets that all worked out with the IP lawyer.
That may frustrate some people, while making others very happy. I can also tell some of the devs are getting anxious since they see Ziggy added/changed/removed over 35,000 lines of code in the TB kernel and their eyebrows raise a little and they want his source so they can see what he's up to I don't know where you stand on the issue, nor will I tell you which side to take. I already have his source so quite frankly I don't care either. Again, I'm just the messenger sharing what I know. Don't hate on me if you don't like the info above - it's not my call
You'll all get the source/patches soon enough
Click to expand...
Click to collapse
I do appreciate the quite thorough explanation regarding the rationale of not releasing his kernel source. While GPL is a discussion for another day, the whole thing for me is by definition, Android is AOSP. I'm seeing a disturbing trend not amongst developers so much but from manufacturers re-writing the rules on being Open Source. Take Motorola for example. They release all phones with a hardware lock on their bootloaders. Poor folks using the Atrix have to go through a ridiculous side loader app to download anything not from the market. Perhaps Google should start a new branch called the Android Unopen Source Project
Anyway, I don't know all the specifics behind Ziggy's IP issues so not knowing the full extent of the facts I won't comment on that. I respect Ziggy and appreciate what he brings to Android. I just don't want to see developers close their source code because if Cyanogen took that some approach where do you think the development community would be today?

Post removed

appeal: let's make CM11 stable!

Hello,
I made that account in order write about some things that I’m annoyed of or which I find very alarming. I’m sure there are some other people in here, who feel the same. I think it’s time to change something about it. I know some of you might be not interested in that and many people just want to get CM12 as fast as possible. This people should maybe not take part of this. To each man his own. I do understand that but this is about changing CM11 to a REAL “Daily Driver”, where everything works right and stable (at least the device-independent things).
This is about the following:
For many mobile phones like the well known Samsung Galaxy Models will be a Kitkat for real the last “halfway functioning” system. Also there has been put a lot of work into CM11, which a have a lot of respect for. Newly Cyanogenmod got a company and as such this Custom Rom is totally different than others – which do their work completely non-paid and voluntary e.g. Omnirom. As a company you have, except of making a lot of money, some responsibilities. You have to place a working product on the marked and I appeal here and today for calling in this responsibility or rather to introduce CM to move form there previous “Kindergarden” to a CM11 which is made perfect. After all Cyanogenmod as a company benefits of us using CM11 (the Community/Open source Project) on your mobile phones. We users are the best Beta-Testers and if CM just doesn’t fix bugs it is not better than Samsung.
Everyday we are complaining about producers like Samsung, because they e.g. do not bring out a 4.4 for the S3. But they at least perform their obligations somehow and continue improving and fixing 4.3. Anyway it (mostly) gets a real functioning product. CM should be interested in satisfying us with this/their product (CM11/s; Oneplus one). Even if we don’t actually have Oneplus one now we are ALL potential, future costumers! And nearby the most buy a Oneplus one BECAUSE they feel confident with CM and their Android Rom! Unfortunately in reality CM11 is far away from real stability and I don’t mean features, which are hardwarenear and sources for drivers like the S3 camera are needed, but completely normal features in the system.
If you only use a few Apps a few times then the current CM11 will work for you and it is usable, but as soon as you need something which is rarely used or which is more complicated you will find bugs. Although, this could be different.
I think it’s shocking that I often read when people are swearing “why should we want Android 5.0 if not even Android 4.4 is working stable!” (Look at the people from N7000, who have not even a M-Release from CM11). But no one is doing anything against it. CM should know that there are people who want stability! Please note that I’m talking about device-independent features. Especially because CM11 current is the BASIS for the CM11S, which is the system for Oneplus one! But what does the community see? The “CM12 roadmap” in which they are talking about: “freezing” CM11 and focusing on CM12. No, that can’t be. Every lifeblood-Custom-Rom maybe could get away with that (even Omni tries to go on with 4.4 for older devices as a “long-term-project”), but no new, real organization. Some may argument and say that with CM10.2 it has been the same, that with the first Nightlys or in general at the beginning of CM11 the final has been there after a very short time, but CM 10.2 as we all know, from past developers who left CM and now work for Omnirom, never had gone through as a stable. They just wanted it to seem like that in order to get sponsors and to show with the statistics, which CM introduced at that time, how many people already use CM. And the i9300 practically is the most used device in that case!
I have posted this post on November the 22nd 2014(as abruptly the Nightlys from CM11 stood still) in a German Android Forum. On the 24th of November 2014 all the Nightlys suddenly worked again, but if you look at the most Changes you could think that CM had not interest in creating a stable OS or a really stable CM and they are only trying to make it seem like they would still work on that. (Changes like the design template file or adjusting readmes).
Nevertheless there are still many bugs and some elementary features are missing! That can’t be. The worst is, that CM doesn’t get things straight for the community. I can understand if the creators don’t want to have any pressure because many people are asking for appointments but at least they should get the things straight concerning if and how long CM11 should be supported! ESPECIALLY if CM bet on that with their Oneplus One!
I have started to work on this on November the 22nd 2014 and reported about 40 bugs and maybe needed but simply to integrate features in the CM Bugtracker JIRA. I commit that I have never done this before. I do have enough other things to do and I always thought the creators would take care of that or anyone else would report the problem. But apparently this won’t happen. In order to prohibit a fiasco like CM10.2, should we all take care of it NOW!
I will post a list of bugs and eventually some useful and first of all realisable features in the course of this theme. Some of them I already have reported –but the most of them have been closed again. One of them was a appeal to CM and it said that they should get CM11 ready and stable – this Bug of course has been closed immediately and without actual statement.
I want to ask you to vote for all these things. If you have bugs yourself and never have been reported such please make an account on JIRA, it is easy and doesn’t take much time. Even if it’s just in order to vote for my bugs and features later. It would be nice to spread this and the text in JIRA, in other Android / CM-Forums and in social networks in order to have a real group or better sent a link or the post itself to some devs of cyanogenmod so that they are knowing about the problem and can take action on this.
Please don’t see this as agitation or something like that. I have great respect to the creators and their achievements! But CM now is a company and they geared to their (potential) customers. Without us making noise CM will concentrate on CM12 and we all have (again), a half-finished “gerfrickel”-Sytem. Also think that all the improvements in CM will get back to the Custom Roms.
Willingly you can send me your bugs, ideas or suggestions per PM here but better post it here or write it down to the JIRA bugtrakcer. The more, the better!
For so many Smartphones the CM11 is the last thing which they will be seeing more or less stable without an unbelievable reduced battery power. If we don’t do something now, the game will be replayed with CM12. And don’t hope that it will be different there. A really STABLE Custom Rom – that is missing somehow. That’s at least what I think and if read in the forums now, there are many others who think the same…
I hope on active cooperation, feedbacks and opinions on that and ask for not deleting this thread but eventually moving it to the right place (maybe a seperate section about android in general?) and make it sticky for all people to see. I hope we can find some way here to CM changing his mind about working on their custom rom and supporting CM11 for some time until it's a really stable product (maybe until first or second “stable” M-release of CM12 is out). If you want a stable CM11, please write it down here!:good::victory:
BTW: I am from Germany, sorry for my maybe bad English.
Chris

Stability depends on device. CM11 is superbly stable on a Nexus 4 or 5, but could be extremely buggy on some random cheap Chinese phone bought from aliexpress because lots of people use and develop for Nexuses, but only a handful of people will be working on that Chinese one. There are also often hardware issues.

Thanks for your reply, i totally agree with you but if you have rightly read my topic you can read that I dont write about device specific features. If I can reproduce a handfull bugs everytime, on every CM11 rom, than that are real bugs on which CM should take care. I will also show some here but I need time to tanslate it here and to write it.
I also totally agree if a device have no maintainer it cant be tested and made fully working - but the problem most of the time is that there are A LOT of people who make their own kernels, own custom roms on base of CM11 and they COULD be maintainer of the device but dont want it or cant do it because of CM itself. If you look how CM is treating the people and not comunicate with them you will understand why there is a lack of maintainer and so many people which COULD be a maintainer because of the knowledge. But that is a other topic. CM need to change his way to talk with the community. If there are bugs, which are easy to reproduce and they will be reported to bugtracker and CM is closing it because the log is not attached, because the reporter CANT BRINGT IT, BUT the bug can be EASILY reproduced WITHOUT A LOG, than it is CMs fault. People want to help and they (CM) close the bugreports. It should be in their interest to test every bugreport to MAYBE find a potential bug. Also look at the bugtracker, there are issues which were reported for years and CM dont care about it. Look for the lack of using the calendar without a google account for example. On the other hand side: They add features which nobody wanted to have and mostly the people dont use. where is ther sense here?

Personally, I quit using any cm or cm based ROMs on my nexus because it seemed to lack speed and stability compared to stock or aosp based ROMs.
I had better luck with early custom lollipop ROMs than with cm. Right now I'm using slimkat until black themed lollipop ROMs are stable and bug free.
So basically, I agree that cm should be more stable. But I don't really care cause there are lots of good options out there instead of cm.
Sent from my Nexus 5 using XDA Free mobile app

Ow mannnnn .. Thank you so much !!! you are pro !!!

Well first thing is that bugs happen when you use open source drivers and software. This is because it is not coded just for a single device like the OEM drivers and software is.
Second CM is not required to do anything. That includes fixing bugs that they don't care about.
Next. And to be flatly honest they have no reason to talk to the community. Can't blame them as most have nothing more productive to say then "duh this is busted" why talk to those people when you can talk to people that can offer advise and maybe help salve an issue. Nor are they required to post any update at all.
Devs have the right to post a build in the OP and never post support, leaving all support up to the user's.
It doesn't matter if you can produce the error. They have their rules about posting bug reports. If you don't follow them and it gets closed without it even being looked at well then that's your fault.
If you want stable then stay stock. Or learn to fix it yourself. There is no obligation for anyone to even touch aosp based code. Even Google has most stopped updating those apps and files.
Now as for you saying device independent issues. The issue here is that one device could be rebooting every ten min but other devices don't do it.
The only device as a company they need to worry about is the one that sells with their roms. All others are hobby projects and treated as such.

zelendel said:
Well first thing is that bugs happen when you use open source drivers and software. This is because it is not coded just for a single device like the OEM drivers and software is. .
Click to expand...
Click to collapse
Firstly thanks for your feedback
I dont understand what you want to say. If bugs happen and when is not the content of the topic. I am using linux on my workstation and server itself, everyday. (Linus Torvalds is also talking to the people). I know that bugs can happen and open source drivers and software can have bugs. I do not blame people for this. I do respect their work! I blame people for activly ignoring bugs which are easy to fix (atleast for this people) and activly ignoring bugs in addition to don't communicate why they don't care about this bugs which they could easily fix. This is a human fault. I also have written in my text above that I DO NOT MEAN DEVICE SPECIFIC BUGS. So I don't really understand whats your point here, sorry.
zelendel said:
Second CM is not required to do anything. That includes fixing bugs that they don't care about.
Click to expand...
Click to collapse
Yes, in theory they dont have to do anything. But we are all human. We have a moral commitment. Also I think every group who wants to make their custom rom succesfull, want to make the users happy. If not so, why CM is releasing this to the community? Is it forbidden to say my and many peoples opinion here? If I follow your logic of arguing then we all were not allowed to blame samsung for their bad software and bad support, right? Or specially if something is for free we don't have the right to critisize things? Why? If you create something, you have to count on the fact that people will complain about things. If the people complain with arguments and everyone respect each other that is totally ok in my opinion. If that is too hard for the dev than he should maybe not release his work. So our world is working. Why you argue for a group which doesn't speak to you or here forself? I don't know if you would care about if you were one of those people who wait for years that a bug or improvement is realized which is important for you.
zelendel said:
Next. And to be flatly honest they have no reason to talk to the community. Can't blame them as most have nothing more productive to say then "duh this is busted" why talk to those people when you can talk to people that can offer advise and maybe help salve an issue. Nor are they required to post any update at all.
Devs have the right to post a build in the OP and never post support, leaving all support up to the user's.
Click to expand...
Click to collapse
if a human being thinks like this, he should really start to think about himself. It is a very arogant attitude against other people. If a person thinks "I have no reason to talk to you", then I would think this person is not really a nice and good human. People like you describe, they think that they are better than all other and that is not a good attitude. I totaly agree that it is not helpfull if someone says: "duh this is busted", but I and some other people report bugs, want to help, ALSO if they don't have the ability to develvop something on their own. But the point is the following: The people who are only complaining and say: "duh this is busted" are the people for who CM is making a software. They (CM) should care about them. They are mostly the people who BUY their Oneplus one. Why I don't talk to CM itself? You have written it here exactly: They "have no reason to talk to the community". So I am talking to the people here, the commnunity and looking for all this people who don't do anything because they think they are alone, can't do anything. The goal is to give the people of CM a reason to talk to the commnunity. This is a attempt to change their mind about their style of communication. and make CM11 fully stable.
zelendel said:
It doesn't matter if you can produce the error. They have their rules about posting bug reports. If you don't follow them and it gets closed without it even being looked at well then that's your fault.
Click to expand...
Click to collapse
How easy is live, what? If so, then they should close the bugtracker. I was thinking the bugtracker is for the community to HELP CM finding bugs so that THEY can make the product better. This is an opensource project. They make money with the code at the end in form of "CM11S", which is CM11 + closed source apps. And I also understand that they want to make money with their work now. If an opensource project is making benefit in form of money without the need of beta testers because the community finds the bugs they should be HAPPY. But they do ignore it, they think they are above all. You say they: "dont have to talk to the community". Look for omnirom, look for other projects, they are gracefull if someone find a bug, can reporduce it. The devs can fix it. It makes the software better and better. Samsung has to pay people for this. I totally understand if there is a bug which is to repoduce, the dev test for it, can't find it and order the log in addition from the bugreporer. Thats a real reason. But they (CM) dont read this bug. They dont care. Do you want to say that's a good attitude to the users and the community? I don't think so. We can talk with each other.
zelendel said:
If you want stable then stay stock. Or learn to fix it yourself. There is no obligation for anyone to even touch aosp based code. Even Google has most stopped updating those apps and files.
Click to expand...
Click to collapse
Sorry, but thats not a real argument. Then we all would be on stock, no one should be allowed to say: "this could be better." That would be a bad world. It is not wrong to expect a stable product. Let it be opensource or propritary. In addition: Not everyone can code something and if so, not everyone has the time to do so. This people have created the maybe most famous custom rom. They SHOULD talk to the people who are using their software, who are all potential customers of their PRODUCT, the oneplus one. The product which makes USE of CM11. So if I am thinking about to buy it, I think about all blame samsung and I think about that CM11 is ignoring user bugreports AND they "don't need to talk to the people". Not a good image, or do your think so? Samsung is not giving 4.4 to the i9300 for example, BUT they make 4.3 better and they make it STABLE and FULL. I don't like samsung for their software and other things, but it is working. But people like CM are blaming them for their support, so me and other people, we have the right to blame CM for THEIR support, or not? Also think about freedom of speech.
What google does is a other thing. Google is also making enough crap and I have also my optionion about it. I also dont install google apps for myself. But google and CM are a different story and thats not the topic of this thread. Also I don't think that it is really nice to say to the people: "Eat what we give you and shut up otherwise you don't have anything.". But you are saying this between the words.
zelendel said:
Now as for you saying device independent issues. The issue here is that one device could be rebooting every ten min but other devices don't do it.
Click to expand...
Click to collapse
I dont understand what is the point here? I have clearly written: "Device independend". I didn't writte about random reboots. I totally agree with you that this are a other sort of problem. But if you tap on a "private number" on dialer/phone statistics and will get a FC, and that on M12 and also on the newest nightly, also on 5 different devices, you report that and the mod of the bugtracker dont care about it and simply lock down the bugreport and the dev team totally IGNORE the problem because no log was added (because maybe the reporter dont have a official supported device because they also close the bugreport if this is not?), but they only had to test what the reporter described, then someone can clearly say two things: First thing is that the bug is easily to reproduce and it is device indepently. And second thing is that the CM team or at least the mod of the bugtracker really DONT CARE about the bug existence if he is simply closing down the bug without looking for it or test to repoduce it and THEN, if it is NOT easily to reproduce, order a log from the bugreporter. We are people, we can talk to each other. There is NO NEED to simply close things down, don't community and at the end write down: "This is CM11 final, look at our bugtracker: there are NO BUGS!". Yes, if you don't care about the bugs people report then yes - it is bugfree. Nice way of make something stable. Like chainfire wrote about CM10.2 to the time he left CM Team.
zelendel said:
The only device as a company they need to worry about is the one that sells with their roms. All others are hobby projects and treated as such.
Click to expand...
Click to collapse
I agree with you, but have I written something other? I have written nearly the same. CM11 is the basis of CM11S, which is THE SYSTEM THEY SELL on Oneplus one, their PRODUCT.
But in theory if someone, like the creator of "nameless rom". make HW composer working for the i9300 or Teamasek make a camera restart workaround for it and they (CM) DONT CARE about it for example, they know it, people report it. They ignore it. Then something is really wrong here. People like creator of "nameless rom" or Temasek are creating their own custom rom on basis of CM11. They (CM) could easily say: „we have no time, sorry.“ Or: "it is not stable right now, we will wait for it." or simply: „No, we can't do it because....“ Then people totally UNDERSTAND it. But they only say like you said: "We have not to talk to you." nice, nor? Everyone is talking to the people, why they think they don't need that?
And to make it clear here: I am dont fighting against CM, I really like their art of making a rom. I like their software, I want to have and sell my customers a oneplus one if it is out to the global market. I want to make CM better. I dont say look at XXX rom, they make all right, then I could go to a other rom like someone in the thread posted before. I am like this person, but I want to change something and want to help CM so that people dont all leave CM or make their own custom rom. If we would all help us togehter, every device of CM would have a maintainer. The world would be right and nice. But CM makes it to difficult to help. But why? They win, they loose nothing. Let's make them change their mind so that things will get better.
By the way: Oneplus is looking for a other rom for their oneplus one. Also there are articles about: "the flaggschiff killer kills themself". They have problems. CM11/S is not really stable on the oneplus one. Oppo is looking for a other software, CM is working on CM12, it won't make the things better. But CM is building on the oneplus two. It will make it worse. Why all the way begin new and dont make things fully stable? So in theory it would be right to further work on CM11 until it is really stable and also bring the oneplus one on the global market for real and support it some years really. Otherwise they have newest android but it is less stable than software of samsung. If you or anyone else think I am wrong than write that to CM, they can easily write down the facts here in this topic if they care about their users and the most of their further customers. So back to the topic. How can we make things on CM11 better and change CMs mind? chris

XXchrisXX said:
Firstly thanks for your feedback
I dont understand what you want to say. If bugs happen and when is not the content of the topic. I am using linux on my workstation and server itself, everyday. (Linus Torvalds is also talking to the people). I know that bugs can happen and open source drivers and software can have bugs. I do not blame people for this. I do respect their work! I blame people for activly ignoring bugs which are easy to fix (atleast for this people) and activly ignoring bugs in addition to don't communicate why they don't care about this bugs which they could easily fix. This is a human fault. I also have written in my text above that I DO NOT MEAN DEVICE SPECIFIC BUGS. So I don't really understand whats your point here, sorry.
Think its so easy then try it your self. You seem to think anything about this is easy. Until you try to do it yourself you have no room to talk about it being easy.
Yes, in theory they dont have to do anything. But we are all human. We have a moral commitment. Also I think every group who wants to make their custom rom succesfull, want to make the users happy. If not so, why CM is releasing this to the community? Is it forbidden to say my and many peoples opinion here? If I follow your logic of arguing then we all were not allowed to blame samsung for their bad software and bad support, right? Or specially if something is for free we don't have the right to critisize things? Why? If you create something, you have to count on the fact that people will complain about things. If the people complain with arguments and everyone respect each other that is totally ok in my opinion. If that is too hard for the dev than he should maybe not release his work. So our world is working. Why you argue for a group which doesn't speak to you or here forself? I don't know if you would care about if you were one of those people who wait for years that a bug or improvement is realized which is important for you.
You have the right to blame them if you want but then they also have the right not to care. There are many bugs that I have had on AOSP for years. They have not been fixed and I cant fix them so guess what, I dont complain.
if a human being thinks like this, he should really start to think about himself. It is a very arogant attitude against other people. If a person thinks "I have no reason to talk to you", then I would think this person is not really a nice and good human. People like you describe, they think that they are better than all other and that is not a good attitude. I totaly agree that it is not helpfull if someone says: "duh this is busted", but I and some other people report bugs, want to help, ALSO if they don't have the ability to develvop something on their own. But the point is the following: The people who are only complaining and say: "duh this is busted" are the people for who CM is making a software. They (CM) should care about them. They are mostly the people who BUY their Oneplus one. Why I don't talk to CM itself? You have written it here exactly: They "have no reason to talk to the community". So I am talking to the people here, the commnunity and looking for all this people who don't do anything because they think they are alone, can't do anything. The goal is to give the people of CM a reason to talk to the commnunity. This is a attempt to change their mind about their style of communication. and make CM11 fully stable.
A nice and good human? Really?!?! What world do you live in. Alot of the best Devs here are antisocial people. They dont like other people let alone people cant follow simple instructions.
Look People did it themselves. CM used to be active in the community but then people kept doing just what you have stated. Not posting proper bug reports with logs that are needed. (if the dev says post a log with the bug report, this is not an option). The one plus one is a the joke of the Dev world. Most devs already sold theirs and will not go back.
How easy is live, what? If so, then they should close the bugtracker. I was thinking the bugtracker is for the community to HELP CM finding bugs so that THEY can make the product better. This is an opensource project. They make money with the code at the end in form of "CM11S", which is CM11 + closed source apps. And I also understand that they want to make money with their work now. If an opensource project is making benefit in form of money without the need of beta testers because the community finds the bugs they should be HAPPY. But they do ignore it, they think they are above all. You say they: "dont have to talk to the community". Look for omnirom, look for other projects, they are gracefull if someone find a bug, can reporduce it. The devs can fix it. It makes the software better and better. Samsung has to pay people for this. I totally understand if there is a bug which is to repoduce, the dev test for it, can't find it and order the log in addition from the bugreporer. Thats a real reason. But they (CM) dont read this bug. They dont care. Do you want to say that's a good attitude to the users and the community? I don't think so. We can talk with each other.
Yes it is. As long as people follow the proper bug reporting steps. Yeah and if you report some bugs to many devs without the proper logs they will ignore you as well. Many devs are moving over to the bug tracker just like CM and will require the same logs. This is troubleshooting 101. If you cant even get a log then you should rethink using custom roms.
Sorry, but thats not a real argument. Then we all would be on stock, no one should be allowed to say: "this could be better." That would be a bad world. It is not wrong to expect a stable product. Let it be opensource or propritary. In addition: Not everyone can code something and if so, not everyone has the time to do so. This people have created the maybe most famous custom rom. They SHOULD talk to the people who are using their software, who are all potential customers of their PRODUCT, the oneplus one. The product which makes USE of CM11. So if I am thinking about to buy it, I think about all blame samsung and I think about that CM11 is ignoring user bugreports AND they "don't need to talk to the people". Not a good image, or do your think so? Samsung is not giving 4.4 to the i9300 for example, BUT they make 4.3 better and they make it STABLE and FULL. I don't like samsung for their software and other things, but it is working. But people like CM are blaming them for their support, so me and other people, we have the right to blame CM for THEIR support, or not? Also think about freedom of speech.
Ill be honest and this is the thought with alot of Devs. Most normal users SHOULD stay on stock. Saying Samsung is stable is too funny. Most Devs have left those devices all together as well. Once again you dont post the proper and requested logs with the bug reprot expect to be ignored. As for freedom of speech Refer to the link below. Your on a private site. The right doenst apply.
What google does is a other thing. Google is also making enough crap and I have also my optionion about it. I also dont install google apps for myself. But google and CM are a different story and thats not the topic of this thread. Also I don't think that it is really nice to say to the people: "Eat what we give you and shut up otherwise you don't have anything.". But you are saying this between the words.
If your not part of the solution then your part of the problem. And that is with proper bug reports and logs.
I dont understand what is the point here? I have clearly written: "Device independend". I didn't writte about random reboots. I totally agree with you that this are a other sort of problem. But if you tap on a "private number" on dialer/phone statistics and will get a FC, and that on M12 and also on the newest nightly, also on 5 different devices, you report that and the mod of the bugtracker dont care about it and simply lock down the bugreport and the dev team totally IGNORE the problem because no log was added (because maybe the reporter dont have a official supported device because they also close the bugreport if this is not?), but they only had to test what the reporter described, then someone can clearly say two things: First thing is that the bug is easily to reproduce and it is device indepently. And second thing is that the CM team or at least the mod of the bugtracker really DONT CARE about the bug existence if he is simply closing down the bug without looking for it or test to repoduce it and THEN, if it is NOT easily to reproduce, order a log from the bugreporter. We are people, we can talk to each other. There is NO NEED to simply close things down, don't community and at the end write down: "This is CM11 final, look at our bugtracker: there are NO BUGS!". Yes, if you don't care about the bugs people report then yes - it is bugfree. Nice way of make something stable. Like chainfire wrote about CM10.2 to the time he left CM Team.
If the device is not supported then they shouldnt be posting a report at all. Do you have any idea how long it would take to "test" each bug report? The log is much faster and more useful. To many people are installing stupid stuff like xposed that randomly causes code crashs. This is where the logs will show this. If it is bug free on their devices then they can call it bug free. In the end it is all how it runs on their devices.
I agree with you, but have I written something other? I have written nearly the same. CM11 is the basis of CM11S, which is THE SYSTEM THEY SELL on Oneplus one, their PRODUCT.
But in theory if someone, like the creator of "nameless rom". make HW composer working for the i9300 or Teamasek make a camera restart workaround for it and they (CM) DONT CARE about it for example, they know it, people report it. They ignore it. Then something is really wrong here. People like creator of "nameless rom" or Temasek are creating their own custom rom on basis of CM11. They (CM) could easily say: „we have no time, sorry.“ Or: "it is not stable right now, we will wait for it." or simply: „No, we can't do it because....“ Then people totally UNDERSTAND it. But they only say like you said: "We have not to talk to you." nice, nor? Everyone is talking to the people, why they think they don't need that?
If they are basing their rom off of CM then they accept it. People did it themselves. As already stated. You really must be new to this.
And to make it clear here: I am dont fighting against CM, I really like their art of making a rom. I like their software, I want to have and sell my customers a oneplus one if it is out to the global market. I want to make CM better. I dont say look at XXX rom, they make all right, then I could go to a other rom like someone in the thread posted before. I am like this person, but I want to change something and want to help CM so that people dont all leave CM or make their own custom rom. If we would all help us togehter, every device of CM would have a maintainer. The world would be right and nice. But CM makes it to difficult to help. But why? They win, they loose nothing. Let's make them change their mind so that things will get better.
To be honest alot of people couldnt careless about CM. Any real team uses aosp as a base and not CM. This is due to CM changing the base AOSP code to fit what they think android should be. To me it sounds like you have a device that was dropped by the team and are now mad about it.
By the way: Oneplus is looking for a other rom for their oneplus one. Also there are articles about: "the flaggschiff killer kills themself". They have problems. CM11/S is not really stable on the oneplus one. Oppo is looking for a other software, CM is working on CM12, it won't make the things better. But CM is building on the oneplus two. It will make it worse. Why all the way begin new and dont make things fully stable? So in theory it would be right to further work on CM11 until it is really stable and also bring the oneplus one on the global market for real and support it some years really. Otherwise they have newest android but it is less stable than software of samsung. If you or anyone else think I am wrong than write that to CM, they can easily write down the facts here in this topic if they care about their users and the most of their further customers. So back to the topic. How can we make things on CM11 better and change CMs mind? chris
Click to expand...
Click to collapse
Once again CM has not posted here in years. AOSP will never be completely stable. Deal with it. and a news flash the oneplusone 2 will not have CM. They have already signed a contract exclusive in some places with another company.
Now to end this. Here is a link. Have a good read.
http://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441

Ok so I've read the cluster that is your post @XXchrisXX and I have to say a few things
First off, I'm probably the last person you would ever see saying anything remotely nice about CM but what's right is right....
1. There is no moral commitment or obligation or ANYTHING that CM (the open source side of things) has to follow. You are getting a FREE product. In exchange your feedback may or may not be useful to the developers and device maintainers. You signed no contract. You didn't agree to anything with CyanogenMod or any of it's developers or maintainers. XDA-Developers is and always has been a AT-YOUR-OWN-RISK type of site.
As stated above, you can stick with the stock ROM from the OEM if you want stability and some kind of warranty.
2. There are two different sides of CM. There is the open source side which is what you're griping about and then there's the company, CM Inc.
One is run by volunteers and hundreds of contributors (Open Source side) and the other one is run by employees who are under contract (CM Inc). Don't confuse the two and think that you can hold the open source side to the same things you hold the company to.
Do many employees from CM Inc. contribute to the Open Source side? Yes, but that is a hobby. You want a warranty and someone to yell at for not fixing bugs? Go buy a One Plus One and get you a warranty, simple as that!
3. Who are you to tell them (the Open Source side of CM) what they can and can't do? You should be lucky that your device is even supported by CM or any AOSP based custom ROM.
You talk about Samsung and other OEMs but what you fail to realize is that most OEMs give you a one and done. They give you kitkat and that's it.........they TOO move on to bigger and better things.
Don't be foolish here and think that your device that's 3 years old is going to run KitKat like a champ. You say you "understand" about open source drivers but yet continue to argue your pointless cluster because you think that CM (the open source side) should behave like the company.
YOU DON'T UNDERSTAND! If you did, you would of never made this post and thank your lucky stars that your device even got on CM's radar for support.
Again, I know CM inc has done some messed up things in the past and are arguably run by a circus but what I hate more then them is ungrateful people like yourself.
Stop while you're ahead @XXchrisXX

What... the... fk...
Seriously... It's obvious you've violated XDA's "search before posting" rules.
Now, you've given enough information that you're obviously a haxxinos4 user. (You mention N7000 so probably a 4210, but I sort of recall seeing something indicating you might have a 4412 device...)
The only devices that actually have received benefits from Cyngn corporate are their "Cyanogen OS" devices. Oppo N1 and OnePlus One. Those are the two devices where Cyngn corporate staff have NDAs signed with the OEM and Qualcomm (and other suppliers) to fully support every piece of hardware within the device. Now, if your complaint is about those devices (which Cyngn HAS ****ed up too), you have a right to complain. But to be honest, you'll find little sympathy here since the Cyngn corporate guys and XDA don't really get along.
If you're a Haxxinos4 user, and actually PAID ATTENTION, you'd know that Samsung has continually bent the community over and ****ed them time and time again. (Especially in 2012, with the Superbrick fiasco and their broken promises at BABBQ 2012). You'd also know that basically everyone that USED to be a Haxxinos4 maintainer either retired from Android development or left CM after the Focal relicensing disaster. (And even after moving to Omni, Haxxinos4 is pretty much dead to most of us...)
So Mazda is right... While he (nor I) have any love for Cyngn (Kondick has blocked me on G+ for calling him out on various things back during the Focal relicensing fiasco - and I used to be the CM maintainer for multiple Haxxinos4 devices and the Oppo Find5)... Your post just reeks of "typical ungrateful user who can't even search to find the basic backstory of their device"...
Funny thing: Oppo N1 was Cyngn's first official device. Its predecessor, the Find 5, was entirely maintained by people who left CM to found Omni after the Focal relicensing fiasco. All of those people were former Haxxinos4 maintainers who were sick and tired of Samsung's bull**** already.

@XXchrisXX wow, you ungrateful twerp. If you don't like it, try another ROM. I'm anti CM after the things the company side did to the community, but they don't deserve this.
There are other ROMs that are more stable and have more features. Try those. Look at liquid smooth, omni, Dirty Unicorns... Way more options than just CM. But if you go to those Roms with this type of attitude expect zero support.

mazwoz said:
@XXchrisXX wow, you ungrateful twerp. If you don't like it, try another ROM. I'm anti CM after the things the company side did to the community, but they don't deserve this.
There are other ROMs that are more stable and have more features. Try those. Look at liquid smooth, omni, Dirty Unicorns... Way more options than just CM. But if you go to those Roms with this type of attitude expect zero support.
Click to expand...
Click to collapse
Sorry to sound like a moron from left field, but what did CM do to the community? I've been out of the loop.

Saint Isaiah said:
Sorry to sound like a moron from left field, but what did CM do to the community? I've been out of the loop.
Click to expand...
Click to collapse
They took the work of hundreds, forced people to relicense their work so that CM owned it, and then made millions on some contracts when they became a company. None of that money went to the people who spent years working on cm and helping them be what they are. It went to a few key people, and that's it. This people signed contracts with cm inc. Since then they have poached the lead developers from other ROMs to work with them, eliminating any possible competition.

mazwoz said:
They took the work of hundreds, forced people to relicense their work so that CM owned it, and then made millions on some contracts when they became a company. None of that money went to the people who spent years working on cm and helping them be what they are. It went to a few key people, and that's it. This people signed contracts with cm inc. Since then they have poached the lead developers from other ROMs to work with them, eliminating any possible competition.
Click to expand...
Click to collapse
Wow that's super ****ty! I'm guessing this is related to the work they did with the OnePlus One phone? Either way, thanks for the info.

Saint Isaiah said:
Sorry to sound like a moron from left field, but what did CM do to the community? I've been out of the loop.
Click to expand...
Click to collapse
Saint Isaiah said:
Wow that's super ****ty! I'm guessing this is related to the work they did with the OnePlus One phone? Either way, thanks for the info.
Click to expand...
Click to collapse
Yes and no, they did all of this before the OnePlus. The first CM phone was the Oppo N1, that contact came about a few months after this went down. Omni ROM was founded because of this.

Saint Isaiah said:
Sorry to sound like a moron from left field, but what did CM do to the community? I've been out of the loop.
Click to expand...
Click to collapse
I can't dig up a direct link currently, but do a search for "Focal relicensing"
I think there's a link to Guillaume's post on the issue from the CM wikipedia page, but I'm not sure.

Entropy512 said:
I can't dig up a direct link currently, but do a search for "Focal relicensing"
I think there's a link to Guillaume's post on the issue from the CM wikipedia page, but I'm not sure.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2451752

To the OP @XXchrisXX or is it @Noteguy? I am so confused. One of you has 1 post, the other one of you has 4 (all of them in here). Would the real OP PLEASE STAND UP????
That being said, it's quite obvious that you have nothing to offer this community except for whinging - and if you were the only one doing that on XDA then I would say the community should take note and listen to what you have to say. BUT - seeing as you're just another whiny user I think we can all, CM included, just ignore you.

I can't say anything more than what @Entropy512 and @Mazda has already said. You must be very young, because you seriously remind me of my kids sometimes. Get stuff for free, but still complain because its not 100% to your liking. Not sure about Germany, but here we call that ungrateful. Long ago I was not satisfied with the lack of development for my aging device, instead of calling out developers that work, have a family and spend what little free time they have giving me free stuff, I learned to develop myself as to not bother them. Its not plug and play. Most do this for themselves and share. Ranting will only cause them not to share. If you want to kill support for your device faster than the hurdles that are already present with trying to piece together the little bits of open source code we can use, then your on the right track. If you want continued support then sometimes a simple Thank you works wonders. Nobody is making a living off of this (open source side at least). Donations are nice, but I know first hand that both @Mazda and I have on certain occasions returned donations to users. We don't do it because of the money, we do it because its fun. Don't take the fun out of it is all I'm saying. Be grateful that you aren't stuck on OE jellybean or less software. You owe/need the development community more than the developers do, the sooner you realize that, the better off you'll be.

On "Original" Code

Hi, I submitted this complaint on originality through the XDA suggestions, however I'd like some community clarification too.
Hi, I recently started a hobby project here on XDA, which quite unabashedly forked a bunch of repos and picked a lot of commits, then worked to get it working for my device (Z5).
In all this I neither rebased nor changed the ownership.
While I did this I noticed a *LOT* of copied work which was simply rebranded and *NOT* forked.
I further was informed by the people I had forked that I was not supposed to fork their work although said work appeared to be a fork from another repo (though it wasn't actually forked, the file names matched)
I'm confused. Honestly.
Of features, it is known that there are very few original feature developers and they're great people.
The same features make their way across multiple roms, each with their own *cosmetic* changes (or sometimes by just rewriting the same thing). Each Rom then has an aggressive user and dev base to complain about people "copying" and not letting them get credit.
Is it really such a big deal?
I feel like it's probably less effort now to simply go the same route as many roms.
Upload a token "new" source on github by not forking repos but pushing local clones.
Is this what XDA endorses as original work?
If something is forked, isn't that a sign of respect? I feel appalled that, what honestly takes longer, after-all fixes are usually local and it's simple enough to do a hub create and push.
I took the effort of going, forking, cloning and re-doing my changes simply out of respect only to be told that my work is not original as I have "superficially" forked.
I know developers can't be everywhere. They can't develop for everyone.
This attitude of intolerance when the Roms are for DIFFERENT devices which they would NEVER support seems really sad.
Click to expand...
Click to collapse
Some developers are really excellent about this sort of stuff, I'd like to think that they're the ones who believe in their own work and don't see the need to attack others. (The CarbonRom devs are excellent, so are the SonyAosp and LineageOS guys)
The issues crop up from the other "original" roms. Basically patchwork quilts of commits, code and ideas *without* recognition for the REAL devs.
I'd also like to clarify that I have nothing against Rule 12
Rule 12 also allows for no selective sharing, and considering that for most commits you're not the original author I really don't get it.
It's not like I simply pulled a device tree and built it for my device; then removed all references and tried to make money off it.
I had to adapt it and there are commits you have not added yet from other repos too. They're donations not paywalls.
Please clarify the matter.
Additionally I only posted the rom here in the first place because I remember how bad it felt to be kept away from all the nicer new features just because no-one takes the time out to build for your device.
I can't see why a donation link is offensive. I ensured something which I did not originally develop or claim to develop available to users of another device... with credits to the original authors!
I just don't see where this is coming from.
A lot of work around is also from MapleAOSP as I see it.... along with DU, UBERROMS, Pure-Nexus, AOSP dev sources etc.

Personally speaking - I am not offended, because it takes wit and effort to integrate everything and get it working, and IMHO every dev in the world stands on giants' shoulders, taking advantage from the work of others, and all efforts deserve some kind of reward, be it fame, praise, recognition, ... - or money. The donors decide the way they show their appreciation...
That having said, I mostly decide to support devs by buying their Pro apps that unlock some extra features. But I also donate money at times.. Because i feel it's only fair - I can't do development, I learned a different profession that I'm well paid for. Why not share a little in appreciation for the devs' work that I take advantage off?
Just my 2¢