Related
http://groups.google.com/group/android-building/browse_thread/thread/091172a81604c8a0?pli=1
Nexus S went on sale yesterday morning in the US, running Gingerbread.
Just like I did for Froyo, I'm open-sourcing the matching Android
platform source code, right after the first consumers get their hands
on it. I'm going to start literally right now, and the process will
take a few hours.
I'll give more details once the source code is available. However,
there are three aspects that you need to know ahead of time:
-As part of the process to push the source code, there will be some
points in time when the master branch doesn't build. Sorry about that.
If you're working on the master branch, I recommend that you don't
sync until I send an "all clear" when I'm done and things look good.
Other branches are expected to work fine as soon as their manifests
are created.
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
-Please take it easy on the kernel.org servers. They are very helpful
in hosting the AOSP source code, and I don't want to hurt the high
quality of their service with an onslaught of full Android downloads.
If you're not going to immediately work on porting Gingerbread to
devices with the intent of distributing the result to end-users, I'm
kindly asking that you wait a few hours or a few days before you
download it (just roll a 6-sided die and wait that long). In addition,
the slower the servers are, the harder it is for me to do the push.
Thanks for being patient.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
Yay!
Let's bombard Cyanogen's Twitter! J/K``
Hope something good for my incredible comes out of this
Sent from my ADR6300 using XDA App
Can't wait! The quicker the source is released the faster we will have Gingerbread baked into our roms
First one to get an AOSP build of 2.3 running on the G2 will be my new hero.
lol @ the software engineer having two Nexus B's already ;D
silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Wowo!!!!! Can't wait! I've been on the virtous for some time now, because I really like the sense shell, but it's strait over to CM again (been there many times allready) when 2.3 comes!!!
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
@cyanogen
Prepare for spam!!
I just looked at aosp and I see next to nothing updated yet so I dunno
@cyanogen WILL come through quickly for the G2. I'm sure of it.
Shady Gambino said:
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
Click to expand...
Click to collapse
Why wouldn't you permroot now? Nearly double CPU clock, the ability to disable throttling, superuser access.
In my experience, the first implementation of new code is often quite buggy. While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
tornado9015 said:
While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
Click to expand...
Click to collapse
That's half the fun
Follow cmrsc on twitter for updates on compiling a blue-berry flavored gingerbread.
Sent from my HTC Vision using XDA App
sino8r said:
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Come on msm7x30 support!
Blades said:
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Click to expand...
Click to collapse
He probably has a stack of cell phones and probably tries to brick some of them on purpose. He probably just gives back the bricks to Samsung.
ctraywick1 said:
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
Click to expand...
Click to collapse
Thanks, I guess... hard to detect sarcasm in writing My point was... bricks happen!
Just flashing the proper way, epecially packed ones with a bootloader, you can brick even when you do everything correctly. I've flashed over 500 phones (may be more) and it will happen. The nice thing is though, when you are a cell tech, just pop out the board and get another one. Manufacter's warranties for carriers are surprisingly lax... so, yeah we did brick some on purpose, lol
Cyanogen via twitter:
My G2 seems to have Gingerbeard on it. How did that happen?
Click to expand...
Click to collapse
Well via to an article over at Android Central, and Bloomberg: Business Week, its been said by Google that they wont be releasing the source code for Honeycomb. The reasoning behind it apparently is to keep your small time, crap companies, from trying to put 3.0.x onto a device and giving android a bad rep. So I dont think we will be seeing any ROMs until Ice cream.
Source: http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
http://www.androidcentral.com/google-not-open-sourcing-honeycomb-says-bloomberg
Google Holds Honeycomb Tight
It will delay distribution of new Android tablet source code to outside programmers
We'll get it eventually..
Eventually we may but they are saying they dont want craplet devices coming out that aren't intended to run HC. Yea I can see them releasing the source code, after they get a version of this new style android that runs on phones and tables, AKA ice cream. They also say that it wont be release in the foreseeable future, I take this as dont loose sleep waiting for it.
jmc2543 said:
Eventually we may but they are saying they dont want craplet devices coming out that aren't intended to run HC. Yea I can see them releasing the source code, after they get a version of this new style android that runs on phones and tables, AKA ice cream. They also say that it wont be release in the foreseeable future, I take this as dont loose sleep waiting for it.
Click to expand...
Click to collapse
+1
running Tiamat .1.1.6 for the OCing & USB
I Saw somewhere that they are only holding the source code back from the masses to ****up. you can still request & sign for the source code if you ask google directly.
IANAL, but if the owner of the source code decides not to publish, isn't that their right? regardless what "Licence" they publish it under?
When it comes to preventing carriers from putting money sucking spamware on your phone googles "that would jepordize the very definition of open source". But when it comes to releasing the source code for developers to smooth out and patch their half baked OS so each consumer (who paid an unwarranted premium for their device in the first place) can have the free choice of how they would like their "open source" OS to function googles.
Say it aint so.
MOD EDIT: Language
I think people need to relax on this issue. Google will release it when they are ready. Either way I can almost guarantee that it will be leaked. The Dev community always gets what I needs. To be honest it is a little annoying that the android community freaks out over everything. Everyone just relax. I am going to go back to enjoying my Xoom.
Sent from my Xoom using XDA App
orionshock said:
I Saw somewhere that they are only holding the source code back from the masses to ****up. you can still request & sign for the source code if you ask google directly.
IANAL, but if the owner of the source code decides not to publish, isn't that their right? regardless what "Licence" they publish it under?
Click to expand...
Click to collapse
Not if they have already distributed product using it. AKA Xoom.
colbyb25 said:
I think people need to relax on this issue. Google will release it when they are ready. Either way I can almost guarantee that it will be leaked. The Dev community always gets what I needs. To be honest it is a little annoying that the android community freaks out over everything. Everyone just relax. I am going to go back to enjoying my Xoom.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I believe this is not just a simple issue.. leaked <> AOSP
one thing for sure, if we don't have HC AOSP, never expect custom rom..
this android open source is going into nightmare .. Google please remember this "Don't be Evil" ..
this is ur second Evil move after c&d letter to cyanogen..
peace all..
Curious why there haven't been any Zip Aligned or Deodexed roms put out, even if that is as far as we can go other than Kernel Tweaks.
I'm not complaining, just curious.
I guess well have stuff in due time.
So if I type assassinate and then.....Google, do u think they will send a team of nerds and lawyers to get me. Be a martyr...start a revolution..Viva la Zoom
...j/k. Not serious
Sent from my ADR6300 using XDA App
You don't need the source code to make a quality rom.
Sent from my PC36100 using XDA Premium App
whitedragon33 said:
+1
running Tiamat .1.1.6 for the OCing & USB
Click to expand...
Click to collapse
Ftw
Kcarpenter said:
Curious why there haven't been any Zip Aligned or Deodexed roms put out, even if that is as far as we can go other than Kernel Tweaks.
I'm not complaining, just curious.
I guess well have stuff in due time.
Click to expand...
Click to collapse
Bauxite said:
You don't need the source code to make a quality rom.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Here's the deal guys. The legend JesusFreke has stated that he needs source to update his programs smali / baksmali. The are the base tools for decompiling framework and apk.
we cannot deodex rom without those tools. Thus we cannot modify smali and XML. So we are stuck with a stock rom. But we have kernel source which is far more important.
So, its all good for now
Is it still possible to theme the Stock ROM without deodexing? I thought I read somewhere that you could but it was not as easy.
Samsung probably pissed them off for putting their craptastic TouchWiz on the new Galaxy Tabs.
I bet you we'll see the Honeycomb source around the I/O in May. I bet we'll also get the deal on 2.4 and some hints for the next version which will unify the tablet and phone forks back into one.
th0r615 said:
I bet you we'll see the Honeycomb source around the I/O in May. I bet we'll also get the deal on 2.4 and some hints for the next version which will unify the tablet and phone forks back into one.
Click to expand...
Click to collapse
3 weeks after io..I think that's how long it took for froyo source.
Sent from my Samsung-SPH-D700 using XDA App
My guess is Google is probably more worried about all the bagnasty China tabs that have flooded the market all running earlier versions of Android.. Imagine the cheap China crap that would hit the streets if they released the HC Source.. No way the masses would pay the big bucks for the Google sanctioned Tablets when they could pick up a China tab for pennies on the dollar..
While I don't think Google is doing themselves any favors by taking this approach, I would point out that folks would probably make more headway spending time porting Ubuntu or one of the other Linux distributions to the Xoom than trying to prevail on Google to change their ways.
Let's Take A Deep Breath Folks
I'm going to keep this short because I'm not a developer yet, so I'm only qualified to speak as a user and as a grateful member of this forum. As I understand it, in order to be "open" the code has to eventually be released (kind of like non-packaged Linux, i.e. CentOS, Ubuntu, etc.).
From what I've experienced, the only people that DON'T want code coming to us are the carriers. When you folks develop way better ROMs than the crap with bloatware that they try to pass off to us, it hurts their wallets - BFD!!
I'm honored and proud of you guys and I KNOW that the Google probably held it for legitimate problems that they're going to fix for us. Once that's done, they KNOW that once you get a hold of it, more people are going to be exposed to it which only makes more people want future versions. that's how I got snagged by you folks, first with Windows Mobile and then with Android.
I have faith in parts of the system. I have faith in Google to deliver their end, it's the carriers and their greedy practices that I don't trust. Keep the faith folks, take a deep breath and relax. XOOM has been here for only a minute, but we KNOW that it's unlocked, it's rooted and as soon as the 4G hardware and the SD card issues are resolved, we're going to be hip-deep in better versions of the ROMs. I believe that with all my heart because you folks have shown it to me time and again.
It's gonna be great - just wait and see.
So, you see headlines like this:
"Samsung Releases Conquer 4G Kernel Source Code Before The Phone Even Hits Shelves"
http://www.androidpolice.com/2011/0...urce-code-before-the-phone-even-hits-shelves/
And I can't help but think to myself..."OK, so Sammy is starting to see the benefit of getting source code out for its devices, this is good", and then I sit back and reflect upon the fact that the Epic still doesn't have the source code we're looking for (amirite?).
Now, I'm not going to piss and bemoan the fact, BUT, I am going to wonder why it is so. Is there some sort of secret sauce there? Or perhaps is there something VERY embarrassing in their source code? OR, is Sammy really that schizo?
In all, I've been pleased with the steps Sammy has taken. Sure, it would be nice to have me some GB, or even better some CM7, but hey, the Epic is still a great device despite some of the quirks that need to be straightened out.
Thoughts?
Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons
musclehead84 said:
Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons
Click to expand...
Click to collapse
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?
the reason CM7 isn't fully functional for our phones is a kernel and drivers issue. Without GB source for those, we have a hacked together partially working port.
Got it.
Well, if that didn't make your head asplode, then this surely will:
http://www.homestarrunner.com/sbzone.html
It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.
MeetFace said:
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?
Click to expand...
Click to collapse
Plus driver source isnt open source so they don't have to give it to us
it ships with GB, what do you mean it's not being built yet? I think they are not releasing source for us because our phones are reaching EOL and they want us to buy new ones.
theduce102 said:
Plus driver source isnt open source so they don't have to give it to us
Click to expand...
Click to collapse
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App
CapsLockKey said:
It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.
Click to expand...
Click to collapse
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.
mkasick said:
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.
Click to expand...
Click to collapse
This makes rational sense. Would be nice if they released those driver sources this next time around. Would be a good measure to producing goodwill & brand loyalty IMO.
No phone company has ever released driver sources and nor will they. Its open kernel source not open driver source. There is some other reasons they don't release driver source but it would be nice if all phone manufacturers did but that's a perfect world
Phone companies haven't but what about component companies like Nvidia they released Nvflash
Sent from my Transformer TF101 using XDA Premium App
xopher.hunter said:
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
No. As stated 1000 times, it is 100% possible to write drivers, a kernel and etc from scratch just much more labor intensive than using source code.
Sooo, just wondering if since the conquer 4g is VERY similar to the epic since its gb source code was released would it help us at all?
I'm just asking cause my moment ran on a frankenstein froyo port that came mostly from the transform and a little bit from the intercept and it was awesome.
Sent from my SPH-D700 using XDA Premium App
just as the title says, android 4.0 ice cream sandwich was just dropped into aosp
Jean-Baptiste Queru
More options Nov 14, 5:59 pm
Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.html Check out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
simms22 said:
just as the title says, android 4.0 ice cream sandwich was just dropped into aosp
Click to expand...
Click to collapse
That first link is supposed to be:
http://source.android.com/source/downloading.html
vansmack said:
That first link is supposed to be:
http://source.android.com/source/downloading.html
Click to expand...
Click to collapse
fixed it. mr Jean-Baptiste messed up, and i copy/pasted his typo
This is the google group where the message is found:
http://groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f
Sooooo, when's it coming to a custom rom near us?
rentaric said:
Sooooo, when's it coming to a custom rom near us?
Click to expand...
Click to collapse
As long as this is easy enough to work around...
"Build configurations for other devices will come
later. "
Oh snap
If only I knew enough about exactly why/how excited I should be. But none the less I was waiting for this. Let the games begin
CM9 here we come!
now how do i convince a dev to cook up some ICS for my vortex?
mtmerrick said:
CM9 here we come!
now how do i convince a dev to cook up some ICS for my vortex?
Click to expand...
Click to collapse
by buying him Beer
mtmerrick said:
CM9 here we come!
now how do i convince a dev to cook up some ICS for my vortex?
Click to expand...
Click to collapse
I think you'll find a small donation goes a long way! Someone will have a little free time to give it a bash, why not give him some encouragement ?
good to know. does someone need a phone to make a rom for it?
Ha sgs4g has donated a device no cm7 yet small donation probably gets nothing
Sent from my SGH-T959V using xda premium
The first cm9 build will appear in 2 months, so wait for that .
Sent from my GT-I9000 using XDA Premium App
Two month? I think the first nightlys will arrive in about two weeks.
Sent from my R800i using XDA App
mtmerrick said:
CM9 here we come!
now how do i convince a dev to cook up some ICS for my vortex?
Click to expand...
Click to collapse
Follow his Twitter: ..and we're off. check back in 2 months #cm9 #ics
I hope the first ROMs will appear in a few hours.. Is that too much to ask? Maybe by tomorrow then?
ert69 said:
I hope the first ROMs will appear in a few hours.. Is that too much to ask? Maybe by tomorrow then?
Click to expand...
Click to collapse
I hope the cure for cancer will happen this year too.. Seriously you hope by tomorrow? You apparently don't realize what goes into developing ROMS.
At least a few weeks for anything relatively usable..
kuci06 said:
Just compiling it takes 6+ hours on blazingly fast supercomputers
Probably a couple days
Click to expand...
Click to collapse
5-6 hours per core. A modern PC with an I7 Proc and an SSD HD can compile it in just under 1.5 hours that is including the half hour of wall time.
kuci06 said:
Just compiling it takes 6+ hours on blazingly fast supercomputers
Probably a couple days
Click to expand...
Click to collapse
I can compile gingerbread in just under 1.5 hours on my i5 (1st gen) LAPTOP. So six hours is a little long don't you think?
svenvv said:
I can compile gingerbread in just under 1.5 hours on my i5 (1st gen) LAPTOP. So six hours is a little long don't you think?
Click to expand...
Click to collapse
Gingerbread is much much smaller. Also the dependency on LLVM greatly increases the compiling complexity.
ICS is 6GB of download. 25GB disk space to do a single build. 80GB disk space to build all AOSP configs at the same time. 16GB RAM recommended, more preferred, anything less will measurably benefit from using an SSD. 5+ hours of CPU time for a single build, 25+ minutes of wall time.
I played with compiling my own code before but I think I'm going to invest in some ram since it's cheaper now and see how far I can get. I'll probably wait for someone to post device specific instructions though.
Just saw it was released, who's porting it to the nexus 6? Sucks PA is dead for now but I'm sure oxygen will be good
Isn't oxy os just aosp with a few minor tweaks ?
Sent from my Nexus 6
Yes it is but none the less always nice to see new things. And arnt all Roms a modified aosp? Cm,omni
I would love to see a port! And it bumped to 5.1 woohoo!
Not open source or for this device so pretty unlikely
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
Not open source or for this device so pretty unlikely
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
How can you not open source android? Especially based off Google? Is that even legal?
Frozt said:
How can you not open source android? Especially based off Google? Is that even legal?
Click to expand...
Click to collapse
Ever heard of touchwiz, sense, blur, etc?
Sent from my Nexus 6 using XDA Free mobile app
Frozt said:
How can you not open source android? Especially based off Google? Is that even legal?
Click to expand...
Click to collapse
Android is open source yes however the skins, customizations and frameworks companies do to it are not.
Is there much of a need for a pott of this anyway? Its got less features than cyanogen nightlies have atm and is pretty much a very basic ROM as it stands atm. Most of the things CM12s didn't even make it over to oxygen (yet)
I do hope the PA guys can now get a new build out for everyone else soon. The gerrit had a a couple of weeks of no movement there.
Roxas598 said:
Android is open source yes however the skins, customizations and frameworks companies do to it are not.
Is there much of a need for a pott of this anyway? Its got less features than cyanogen nightlies have atm and is pretty much a very basic ROM as it stands atm. Most of the things CM12s didn't even make it over to oxygen (yet)
I do hope the PA guys can now get a new build out for everyone else soon. The gerrit had a a couple of weeks of no movement there.
Click to expand...
Click to collapse
That's because they got pissed and they pulled out of XDA, I'm sure they're taking a long break from PA
Smallsmx3 said:
That's because they got pissed and they pulled out of XDA, I'm sure they're taking a long break from PA
Click to expand...
Click to collapse
what are they pissed of? so far PA is doing quite well then suddenly development stopped from 5.0 onwards.
Looks very AOSP to me now, only a few minor tweaks.
hope someone could port this!
bradputt said:
what are they pissed of? so far PA is doing quite well then suddenly development stopped from 5.0 onwards.
Looks very AOSP to me now, only a few minor tweaks.
hope someone could port this!
Click to expand...
Click to collapse
I don't know anything about this particular situation but my read is that they got an actual paying job to make Oxygen so PA got put on the back burner. If they got hit by some flank on XDA over some issues it would further drive them into paid work vs unpaid as PA is a very non-funded project. I doubt we'll see a port of this. The big push from OnePlus with going with there own custom OS was some mix of butthurt about cyanogen and the ability to further control the OS/have unique features. I am also very certain that there job contract will exclude them from being able to 'port' features from OxygenOS back into PA or some other rom.
There is literally nothing unique to OxygenOS this early in the game. It's AOSP with QS customizations and the gestures from ColorOS.
akellar said:
Ever heard of touchwiz, sense, blur, etc?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Aren't those skins?
thunderx2000 said:
Aren't those skins?
Click to expand...
Click to collapse
Same as OxygenOS, yes
My question is, do they plan on releasing the code for the open source community? if not will all the trolls and flamers who said cygn was super evil for not releasing source to CM11S, do the same here? Of course not because hating CM is cool. I lost lot of respect for the PA devs after their continued CM bashing over the last few months, continually pointing out how CM11S source was never released, yet it will be the same with oxygenos.
Circaflex said:
My question is, do they plan on releasing the code for the open source community? if not will all the trolls and flamers who said cygn was super evil for not releasing source to CM11S, do the same here? Of course not because hating CM is cool. I lost lot of respect for the PA devs after their continued CM bashing over the last few months, continually pointing out how CM11S source was never released, yet it will be the same with oxygenos.
Click to expand...
Click to collapse
They already said they won't I believe.
Circaflex said:
My question is, do they plan on releasing the code for the open source community? if not will all the trolls and flamers who said cygn was super evil for not releasing source to CM11S, do the same here? Of course not because hating CM is cool. I lost lot of respect for the PA devs after their continued CM bashing over the last few months, continually pointing out how CM11S source was never released, yet it will be the same with oxygenos.
Click to expand...
Click to collapse
I don't see a reason why they would release anything other than finished builds at this point.
8Fishes said:
I don't see a reason why they would release anything other than finished builds at this point.
Click to expand...
Click to collapse
because android is open and their devs preached how cyanogen was breaking the mold of open android, yet they do the exact same?
Circaflex said:
because android is open and their devs preached how cyanogen was breaking the mold of open android, yet they do the exact same?
Click to expand...
Click to collapse
They just have no business sense. Now that they're getting paid to code, they understand they don't own the code they produce, the people that pay them for their work own it. Same thing with Cyanogen, they can't get investors to put money into software that is publicly published or it isn't worth anything. Problem with that situation is that a lot of CM commits were made by the community not solely by the guys who started it.
joshm.1219 said:
They just have no business sense. Now that they're getting paid to code, they understand they don't own the code they produce, the people that pay them for their work own it. Same thing with Cyanogen, they can't get investors to put money into software that is publicly published or it isn't worth anything. Problem with that situation is that a lot of CM commits were made by the community not solely by the guys who started it.
Click to expand...
Click to collapse
trust me, i agree with what you just said. I have preached that to the zealots who wanted to flame cyanogen, like you said it wasnt cyanogens code to share because of the deal with one plus. No one seemed to understand that.