2.1 ESE53 will be Official Release on the VZW Motorola Droid

[cereal killer]

As CK said on page 146 this thread isn't going anywhere. Continue the discussion.

I guess we'll just have to start handing out infractions to those that insist in steering the thread off into a root discussion.

Don't want to have to do this people but you really are leaving us no choice.

Last warning

 

[masterxchief]

Hmm so I'm guessing the inside information we had about the update possibly rolling out today wasn't true. :sad:

 

[BlazinCaucasian]

yeah not looking good, unless its tonight

 

[TimChgo9]

Okay... answer time...

Is there anyone out there who might have an idea how long a roll out of a file that is more or less 20MB in size to 200,000 devices would take.

I have some IT background, I understand a bit about networks, IP addressing, and bandwidth issues, but I am not sure how they transmit this. Is there 200,000 files that go out simultaneously, or is it they are sent out a few milliseconds apart, in other words the rollout starts with the update to Phone A at 06:00 :00.00000 and then at 06:00:00.00002 it goes to Phone B, etc. etc. so as to not immediately overload the transmission equipment. Or is it a longer duration? Like 10,000 an hour, or something, so they can manage it easier? And, is the update relayed from tower to tower to tower until it reaches the necessary phone. (edit: I imagine it is) Also, is it done by phone number, or area code? In otherwords, Verizon transmits the update to phones in 708, and since it is intended for Droids only, does every other non-droid phone ignore the incoming signal, or is it sent to each individual Droid using a phone number, or some other ESN that is encoded in the transmission?

So many questions, so few answers... so hard to keep this thread on topic,......

 

[yourname93]

the updae should be on the 2nd of april

 

[Grabraham]

Okay... answer time...

Is there anyone out there who might have an idea how long a roll out of a file that is more or less 20MB in size to 200,000 devices would take.

I have some IT background, I understand a bit about networks, IP addressing, and bandwidth issues, but I am not sure how they transmit this. Is there 200,000 files that go out simultaneously, or is it they are sent out a few milliseconds apart, in other words the rollout starts with the update to Phone A at 06:00 :00.00000 and then at 06:00:00.00002 it goes to Phone B, etc. etc. so as to not immediately overload the transmission equipment. Or is it a longer duration? Like 10,000 an hour, or something, so they can manage it easier? And, is the update relayed from tower to tower to tower until it reaches the necessary phone. (edit: I imagine it is) Also, is it done by phone number, or area code? In otherwords, Verizon transmits the update to phones in 708, and since it is intended for Droids only, does every other non-droid phone ignore the incoming signal, or is it sent to each individual Droid using a phone number, or some other ESN that is encoded in the transmission?

So many questions, so few answers... so hard to keep this thread on topic,......

I don't think it is pushed to all the phones like that.. at least with the previous update I had to OK the download and update- so it is more like the 'push' is that an update is available. Once the phone says yes--- it pulls it from the server

 

[TimChgo9]

Okay... answer time...

Is there anyone out there who might have an idea how long a roll out of a file that is more or less 20MB in size to 200,000 devices would take.

I have some IT background, I understand a bit about networks, IP addressing, and bandwidth issues, but I am not sure how they transmit this. Is there 200,000 files that go out simultaneously, or is it they are sent out a few milliseconds apart, in other words the rollout starts with the update to Phone A at 06:00 :00.00000 and then at 06:00:00.00002 it goes to Phone B, etc. etc. so as to not immediately overload the transmission equipment. Or is it a longer duration? Like 10,000 an hour, or something, so they can manage it easier? And, is the update relayed from tower to tower to tower until it reaches the necessary phone. (edit: I imagine it is) Also, is it done by phone number, or area code? In otherwords, Verizon transmits the update to phones in 708, and since it is intended for Droids only, does every other non-droid phone ignore the incoming signal, or is it sent to each individual Droid using a phone number, or some other ESN that is encoded in the transmission?

So many questions, so few answers... so hard to keep this thread on topic,......

I don't think it is pushed to all the phones like that.. at least with the previous update I had to OK the download and update- so it is more like the 'push' is that an update is available. Once the phone says yes--- it pulls it from the server

Ah, yeah, I should have realized that.... Overthinking things as usual, and I miss the obvious.. But some of my questions don't change much.. So, instead of a push of the entire file, do they do all 200,000 notifications at once, or do they do it incrementally through the day, say 15 or 20,000 an hour... I wonder what the capacity of the servers are that provide the update once the user taps the "Okay" button..

 

[bradgsanford]

Found this on a post about the delay

http://www.informationweek.com/blog...l;jsessionid=MQ153USGPHDH5QE1GHOSKHWATMY32JVN

the interesting bit was the comment by someone named AndroidSQA:

AndroidSQA
commented on Mar 19, 2010 11:47:12 AM

M.T.

You are spreading false information. The 2.1 update is perfectly fine. The issue that happened was with the OTA process, which is controlled by Bitfone, an HP company, not Verizon, Google, or Moto. The OTA process is now fixed and being tested, locally, by me and my team plus a limited amount of field testers/users before full rollout.

Make of it what you will. It could be someone commenting under false pretenses.

 

[TimChgo9]

Found this on a post about the delay

http://www.informationweek.com/blog...l;jsessionid=MQ153USGPHDH5QE1GHOSKHWATMY32JVN

the interesting bit was the comment by someone named AndroidSQA:

AndroidSQA
commented on Mar 19, 2010 11:47:12 AM

M.T.

You are spreading false information. The 2.1 update is perfectly fine. The issue that happened was with the OTA process, which is controlled by Bitfone, an HP company, not Verizon, Google, or Moto. The OTA process is now fixed and being tested, locally, by me and my team plus a limited amount of field testers/users before full rollout.

Make of it what you will. It could be someone commenting under false pretenses.

That's what I figure... until we hear something official, it's all rumor, speculation, or in some cases, hallucination...

 

[TimChgo9]

the updae should be on the 2nd of april

Link?

Proof?

Until VZW, or Motorola makes an announcement, I will take any dates or time frames posted as pure speculation, or rumor... and nothing more.

 

[RW-1]

Without proof - it's another line of crap.

How long does it take to test the OTA?

Can't be any longer than trying the original rollout looking for the known issues you ended up having in the first place.

So if it was fixed, they only need 24-48 hours to check, and that's elapsed...

 

[Anomander]

OTA is nice, but with a majority of us owning computers it would be nice if we could just download the updater and install it that way.

 

[droidmikes]

I can't beleive that no one has mentioned that the Milestone is currently receiving the 2.1 official update. I just visited the Motorola German site and it even alows you to download the OS.

 

[BlazinCaucasian]

There is a milestone thread, someone posted stuff about the milestone and was told to only post news about the droid in this thread

 

[tehpriest]

Your not allowed to mention it here (Don't mention the war (Faulty Towers)) You have to go to the Milestone thread at the bottom. It is very upsetting otherwise LOL :icon_evil: