What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Motorola Droid 2.1

Status
Not open for further replies.
Okay so I saw this post on another Thread and thought it should be said here. If I am duplicating someone's post I apologize as I did not see it here when reading through all the pages.

Basically, it looks like Motorola is getting close to announcing a release date for the 2.1 update.

Motorola (MotoMobile) on Twitter
 
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.
I doubt the relationship is as cut and dry as you put it.
Well, maybe Adobe wants google to incorporate it into all future releases? (if and after flash gets released) And if google didn't want flash on android for HTML5 reasons they could probably patch android to block flash... then VZW might not want it for network reasons... I'm not saying i believe any of that... just saying
 
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.
 
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!
 
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.

I don't know if you know what you are saying for sure or if it is just a guess, but it would seem you make a great deal of sense!
 
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.


It's released I think under the apache 2.0 license which is from what I understand pretty compatible with the gpl2.0-3.0 license? so yes, they do have to provide source upon request as far as I know. also anyone that uses the source i think has to also... or did apache 2 allow them to change the license for their own copy they make? I dunno. it's wierd stuff, but yes in the end google has to open the source up.
 
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!


dude you need to take a chill pill lol. you say who cares, but apparently you do by your very hostile post. There are a lot of things to be excited about from an official 2.1 release. sure you can get hacked roms that work pretty nice, but they won't have any hardware optimizations that motorola might put into the new release.

and there are a lot of people who wish to have an updated os and not void their warranty..... so I'd probably suggest you leave your keyboard and go relax, breathe a little bit hahah. it's only a forum post. you can't get all pissy if you just don't read the thread.
 
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:
 
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.

If any open source app, OS, software is using the GPL code then by law they have to release source code. When Apple went to OS X using the BSD kernel the had to release part of the code they used so anyone can use it.

The law surrounding the GPL is a lot more worse then most people think.
 
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:

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.
 
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:

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.

they could just expand their coverage with HTML5 instead of flash, just to get another company out of there way. But yeah, idk much about it
 
I'm really getting sick of waiting! :-( I purchased the Droid with the understanding that we were going to get an update that improved the UI and possibly enable Flash...I'm starting to get deppressed. I guess I'm just going to have to Root...not looking forward to that :-(
 
Status
Not open for further replies.
Back
Top