Moto and VZW don't need Google to "allow" them to do a damn thing.
Exactly...especially control when they can release an update.
Moto and VZW don't need Google to "allow" them to do a damn thing.
I doubt the relationship is as cut and dry as you put it.Why do people keep making posts with weird speculations about which company has the most "clout"?
Google has nothing to do with this. Once the source code for 2.1 was put out, they have nothing to do with it anymore. The only way their status as a company matters, is if they paid Moto or Verizon to not update. Some of you guys are acting like Android is the same as WinMo or something. But it's not. It's free. There's no paid licensing. When new source code is released, it's up to the handset manufacturer/provider to decide when/how each device gets updated. Moto and VZW don't need Google to "allow" them to do a damn thing.
Isaiah, thats the beauty of Open Source. If say Google in Android 2.2 decides to block Flash, then Motorola can patch that out to allow flash again.
As it has been said before, once the source code is officially released (which Google is required by law to do) then it is out of their hands. Google can delay it a little bit, for example the Nexus One came out early Jan while the SDK was released a little over a week later and the source wasnt released till about 2.5 weeks after the Nexus One.
That is the extent of what Google can do. The only real reason that Android 2.1 could have been delayed is either Motorola and/or Verizon finding an issue (stability, security, etc) that caused them to either code their own fix or wait for Google.
We know of currently 2 issues with 2.1, 1 is the issue with Widgets and a memory leak, the other is the Nexus One having 3G connectivity issues which may/may not effect verizon's network if 2.1 was released on the Droid now.
So to sum this all up? It'll be released when it is ready so breath and relax.
As it has been said before, once the source code is officially released (which Google is required by law to do)
As it has been said before, once the source code is officially released (which Google is required by law to do)
I'm about 99.9% sure there is no law surrounding releasing open source material.
K evoeryone needs to stop with this its google! Its verizon! Its moto! Shut up!!! Who cares? It comes when it comes. So shut up. Deal with it. If you really want 2.1 that bad. Root your droid. Install 2.1 rom. And bam. I just did it last night and I have 2 issues. Led with handcent or 3rd party. And live bacground lag. That's it. It works great. So really. It does not matter how or who is holding its release up. I'm as anxious as the rest of you. But still. Arguing aboutclout or w.e or who is in the process of releasing it doesn't matter! It will be out soon. We hope!
Makes sense, I was just trying to provide a little defense for the theory that flash mobile got canned. Could Google stop making it open source if they wanted to? Please don't make me read that legal document to find out :icon_eek:Isaiah, thats the beauty of Open Source. If say Google in Android 2.2 decides to block Flash, then Motorola can patch that out to allow flash again.
As it has been said before, once the source code is officially released (which Google is required by law to do) then it is out of their hands. Google can delay it a little bit, for example the Nexus One came out early Jan while the SDK was released a little over a week later and the source wasnt released till about 2.5 weeks after the Nexus One.
That is the extent of what Google can do. The only real reason that Android 2.1 could have been delayed is either Motorola and/or Verizon finding an issue (stability, security, etc) that caused them to either code their own fix or wait for Google.
We know of currently 2 issues with 2.1, 1 is the issue with Widgets and a memory leak, the other is the Nexus One having 3G connectivity issues which may/may not effect verizon's network if 2.1 was released on the Droid now.
So to sum this all up? It'll be released when it is ready so breath and relax.
As it has been said before, once the source code is officially released (which Google is required by law to do)
I'm about 99.9% sure there is no law surrounding releasing open source material.
Makes sense, I was just trying to provide a little defense for the theory that flash mobile got canned. Could Google stop making it open source if they wanted to? Please don't make me read that legal document to find out :icon_eek:Isaiah, thats the beauty of Open Source. If say Google in Android 2.2 decides to block Flash, then Motorola can patch that out to allow flash again.
As it has been said before, once the source code is officially released (which Google is required by law to do) then it is out of their hands. Google can delay it a little bit, for example the Nexus One came out early Jan while the SDK was released a little over a week later and the source wasnt released till about 2.5 weeks after the Nexus One.
That is the extent of what Google can do. The only real reason that Android 2.1 could have been delayed is either Motorola and/or Verizon finding an issue (stability, security, etc) that caused them to either code their own fix or wait for Google.
We know of currently 2 issues with 2.1, 1 is the issue with Widgets and a memory leak, the other is the Nexus One having 3G connectivity issues which may/may not effect verizon's network if 2.1 was released on the Droid now.
So to sum this all up? It'll be released when it is ready so breath and relax.
Makes sense, I was just trying to provide a little defense for the theory that flash mobile got canned. Could Google stop making it open source if they wanted to? Please don't make me read that legal document to find out :icon_eek:Isaiah, thats the beauty of Open Source. If say Google in Android 2.2 decides to block Flash, then Motorola can patch that out to allow flash again.
As it has been said before, once the source code is officially released (which Google is required by law to do) then it is out of their hands. Google can delay it a little bit, for example the Nexus One came out early Jan while the SDK was released a little over a week later and the source wasnt released till about 2.5 weeks after the Nexus One.
That is the extent of what Google can do. The only real reason that Android 2.1 could have been delayed is either Motorola and/or Verizon finding an issue (stability, security, etc) that caused them to either code their own fix or wait for Google.
We know of currently 2 issues with 2.1, 1 is the issue with Widgets and a memory leak, the other is the Nexus One having 3G connectivity issues which may/may not effect verizon's network if 2.1 was released on the Droid now.
So to sum this all up? It'll be released when it is ready so breath and relax.
hmmm I'm not sure how that works. They can't go back and make previous open code be "not open source" anymore, but maybe they could branch android into another tree and change the license for that branch and make it not open? or more restrictive? I don't really know how those licenses work. Really if Google tried to close source android they would just have completely killed the platform.
also why would google want to block flash? google owns youtube don't they? so I'm sure high def flash viewing would only be good thing.