Many thanks to http://gpl-violations.org/! Without their pressure this would have taken considerably longer. (Or wouldn't have happened at all?)
Google releases full Android 4.0.1 source code, includes Honeycomb too
91–100 of 122 posts
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#92Earlier quoted context omitted.
I agree that pressure and strict timelines can be a pain, but compliance with the GPL is not optional.
Only Android's modifications to the Linux kernel and a few other tools are under GPL. Most stuff is Apache 2.0.
That's what Google used to tell us, but according to the guys of gpl-violations.org, this has always been a flat-out lie. Those "few other tools under GPL" are quite a lot and in no way negligible.
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#93Earlier quoted context omitted.
> This release doesn't change Google's strategy nor the > fact that they will continue to release Android's source > code in the future with a significant delay compared to > early-access partners. As of today there is not a single phone on the market that runs Android 4.0. Besides, open-source does not mean open-development. They have every right to release the code to whomever they want, whenever they want. And bec…
Besides, open-source does not mean open-development. Google has done a lot to confuse this by referring to everything as just "open". They were still calling Android open even when it didn't meet Andy Rubin's own tweeted 'definition of open'.
"open" is an overloaded term that doesn't mean anything nowadays. "open source" on the other hand has a clear definition and Android definitely fits that definition.
Even yesterday, when Android 3/4 was not available as open-source, Android 2.2 and 2.3 which are the most deployed versions were definitely available as open-source.
And this is relevant, because that's the power of open-source. If you're unhappy with how Google is managing the project you do have the right to fork it. Amazon did just that. Xorg also came into existence that way, amongst other projects.
And yes, it takes resources and you've got to make it popular somehow and that ain't easy and I also fear that Google may close future versions of Android completely, but is it mature enough for a fork to be possible and to survive? Hell yes. Can the parent (Google) attack forks based on patents? No, because the Apache license protects you from that scenario (it's a little ironic that a pro-commercial license is safer than GPL v.2)
Which is why I consider Android to be a lot more "open" than the other 2 alternatives floating around, iOS and WinMo. That's my own definition anyway, which is why I began by highlighting the meaninglessness of the word.
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#94Earlier quoted context omitted.
The only stated reason I've heard is "the code is ugly," which was found to be... unconvincing here on HN. Are you aware of another reason, specifically one which would be convincing?
It had everything to do with fragmentation. Honeycomb (by Googles admission) was a stop-gap to get something out for tablets. They chose not to release the source as they wanted to limit the number of devices shipping with honeycomb in favor of a more compatible (and developer friendly) version in ICS.
How is that related to fragmentation?
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#95Earlier quoted context omitted.
Some people criticized AOSP because they believe the delayed release is unfair (a reasonable criticism). Other people (sheep) criticized them because they actually believed Google was never going to release more source or because needed an arguing point against the OS.
Actually until Google releases the source you can never be sure if they're going to release it. They release this time.. you and I can only hope that they keep doing it in the future. It wouldn't be all that surprising if it would go closed source (except for key partners) at some point (and except for the GPL content). Specially when any company could just rip the source, make it nicer looking and release their own…
It wouldn't be all that surprising if it would
go closed source
Xorg came into existence because of disagreements with the XFree86 license, while XFree86 died ... http://en.wikipedia.org/wiki/X.Org_Server#History
Specially when any company could just rip the source
You see, forks from small players cannot survive because they'll lack the advantages of the main branch (especially the Marketplace). On the other hand, Google must play nice because a fork coming from an alliance between several of these players can kill the main branch.
Imagine if many cheap Chinese manufacturers release
decent phones with it, that cost 3x cheaper than
the rest
Also, most people don't want cheap. Most people want reliable and affordable, which is why iPhones and Galaxy S2 are selling quite well, even though there are cheaper alternatives on the market, even from trusted brands. Consumers don't want the cheapest products, instead they want the best value/price ratio (as long as they can afford it). Making an analogy with cars, there's always going to be a big market for Audi, BMW and Mercedes. Some people even prefer to buy second-hand cars from these brands, instead of a cheaper but out-of-the-factory alternative. That says a lot.
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#96In the past, I've spent a fair bit of time criticizing Google for calling Android "open source", but not releasing the source. Now that it appears that they are actually doing it, let me be the first to say that this is great. Well done, Google.
What people criticized about them was the delay of an open source release to sustain their business strategy (commoditize their products' complements via open source but keep a integrated experience by proprietary early-access agreements - see also http://www.joelonsoftware.com/articles/StrategyLetterV.html ). This release doesn't change Google's strategy nor the fact that they will continue to release Android's sour…
No, what the OP and I have criticized them for is not releasing the code for 4. If you are unable to understand this, that is your problem. Google have done good. What you are talking about is another issue, and an important one, but it does not change the fact that WE HAVE CRITICIZED them for exactly what the OP said.
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#97Earlier quoted context omitted.
Honest question from a maybe-future Android dev: is it notably more challenging to develop for Android during periods when the source is not yet public? For example, is a lot of platform doc written from the POV of someone who expects you'll just peep the code when questions arise? Update: +1 to everyone thinking 'man, I bitch about google sometimes, but this kind of thing is totally legit and awesome'
I do Android dev full time and it's pretty rare to actually need to look at the source. The only time is when encountering a strange bug that you suspect is caused by the underlying implementation. Google has generally been good about releasing emulator images prior to releases, though usually it's only a few weeks. Luckily, it takes time for Android versions to achieve large market share, so any bugs can be squashed…
Sometimes when I'm in a bad mood, the API and online doc are not cutting it - I start wondering why it doesn't work the way I'd expect it to, and from there I have multiple options, from StackOverflow to Google Groups to ordering a book on Amazon.com, and this is the true productivity killer because of, you know, the internet.
The definitive and fastest answer will always come from reading and understanding the source code, as I don't have to hope that someone had the same problem I'm having and someone else had an answer, or that someone will reply to my question before I give up. Eclair, Froyo and Gingerbread sources were enough for 99% of my needs though, but there was always this shadow of doubt for Honeycomb-specific features...
For the most part, having the latest source readily available will greatly reduce the amount of open browser tabs, and for that I'm thankful :)
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#98Not _quite_ full source code --- some proprietary graphics drivers are supplied in binary-only form. It won't matter much for most uses of the source code, but purists will be displeased. http://source.android.com/source/building-devices.html
That is probably not in Google's hands to change. It's the same with the vendor-supplied GPU drivers in desktop Linux as well.
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#99Now the only thing missing is a winning strategy for desktops/laptops. :-) Seems like Chrome OS should be folded into Android and many people would be comfortable using it at home. Same apps could run and sync on all devices.
Unfortunately the two systems are very different and largely incompatible. Merging them would not be impossible, but it's not easy.
I don't know about that. Certainly there are large differences under the hood, but isn't Chrome OS just supposed to run browser apps really well? I don't think that's a very hard compatibility measure for Android to match.
Re: Google releases full Android 4.0.1 source code, includes Honeycomb too
#100Earlier quoted context omitted.
I doubt they released the 3G stack part though. Unless I can't make a 3G equivalent to wireshark I'll have a hard time calling the platform open.
I don't know of any phones being sold that have open source basebands.
I can say with some confidence that an open source baseband will never happen. The carriers won't allow it, and there is good (technical) justification for that. Basically, it is easy to mess up some "tiny" detail of the standard, and disrupt the local network for all nearby users. The compliance testing needed for any phone is huge and expensive.