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!

2.1 ESE53 will be Official Release on the VZW Motorola Droid

Status
Not open for further replies.
I should have just bought the Migo,
verizon-migo.jpg
 
**UPDATE**


Android Central has a great inside source over at Verizon and they are leaking more details of the pending Android 2.1 update for the Motorola Droid. The latest information states that Verizon will begin pushing out the first OTA updates around 9 AM PDT.
Only 1,000 customers will receive the update and then Motorola and Verizon will monitor the blogs for any potential issues. If everything goes ok, then the another 9,000 users will get the update at 9 PM. This will then be followed by a 24 hour waiting period, before Verizon sends out the update to the remaining phones in batches of 200,000.
The rollout schedule for the Droid 2.1 OTA is:

  • The first batch of 1,000 updates will be pushed out at 9 a.m. PDT.
  • Assuming all goes well, another 9,000 updates will go out at 8:59 p.m. PDT.
  • After that, there’s a 24-hour waiting period (to make sure all’s still well.)
  • Then 200,000 updates will go out on Saturday, March 20.
  • Another batch of 200,000 goes out after that, until everyone has the update.
So what took so long for this OTA to reach our phones? Motorola originally posted on their Facebook page that Android 2.1 was coming “this week“, but that was over a month ago.
A tipster is pointing the finger at Bitfone who actually manages the distribution of the updates for Motorola. We have seen problems with other OTA updates from Motorola (CLIQs to BRIQs) so this really isn’t that surprising. We wish Motorola and Verizon the best of luck, and hope this OTA goes out without issue.
From our anonymous tipster: “Not sure if you’ve heard, but the real reason for the latest delay on the Android 2.1 update for Droid phones is due to Motorola’s distribution vendor (Bitfone- now owned by HP). They are having capacity problems with a) the Bitfone application that distributes the updates and b) capacity issues with the current network infrastructure that hosts this application. I spoke to one of the engineers personally and they mentioned that Motorola reps have been “bugging them all day” because of the 3/18 commitment date.”

That's the same old news, where's the update?

9 a.m. PDT is 12 pm Eastern time.......we will have to wait.
 
Don't fire the distribution company... Crap happens at the last minute, it's just how things work.

I've seen some inferences that the first failure to launch may have been BitFone's problem too. Regardless, zero hour is not the time to suddenly change your mind. They have know for months that this OTA update is coming, and should have tested / planned accordingly. The distribution of a file should be substantially less complex than the development of the actual application being distributed.
 
I think it would save the company time and money if you could just go on the local moto site and install the files there. They should have a step by step guide and let the people choose to do it themselves or wait for the ota.
 
Just got off the phone with my local VZW store (Burlington Mall in Mass) and they stated that they do NOT do any in store software upgrades, and the rep stated she received an email last night about the same schedule we all have seen. Word for word with the "update schedule" we saw on BGR. Even the 24 hour wait period for the next batch of pushed updates.

At this point... only time will tell.
 
I'll just go back to waiting for the update.

I've waited 2+ months...

What's a little more time?

Anyway, at least the problem is with the distribution, and not the update itself. Hopefully they can remedy the situation soon enough.
 
Sorry CK, that is an older post that was made on Wed of this week.

Though I would also suspect this better be a distribution issue, there would be NO excuse for something being a "Bug" in the actual resultant upgrade at this juncture. Simply none.
 
Status
Not open for further replies.
Back
Top