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.
If Verizon couldn't PUSH and update out. They still should have provided the Update.ZIP for us so we can do it ourselves. They meet their release date, but just hold off on pushing it out.
 
Well, I gave verizon a call and they did say that I could bring in the phone into the store and that they would update it to ESE53 and that there were no internal records of delays.
 
**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.”
 
umm yeah

If Verizon couldn't PUSH and update out. They still should have provided the Update.ZIP for us so we can do it ourselves. They meet their release date, but just hold off on pushing it out.

Only if we promised that 1000 people would download it so they could monitor the boards for issues.
 
If Verizon couldn't PUSH and update out. They still should have provided the Update.ZIP for us so we can do it ourselves. They meet their release date, but just hold off on pushing it out.

I was just thinking this. If the update itself is fine and they just can't get it sent OTA, why not post it for people to do it manually?

...then fire the distribution company.
 
If Verizon couldn't PUSH and update out. They still should have provided the Update.ZIP for us so we can do it ourselves. They meet their release date, but just hold off on pushing it out.

I was just thinking this. If the update itself is fine and they just can't get it sent OTA, why not post it for people to do it manually?

...then fire the distribution company.

ie like apple does. That would be a good idea.
 
Well if that's how apple does it... I can wait. Haha not!

Don't fire the distribution company... Crap happens at the last minute, it's just how things work.

I still want my download.
 
Yes, fire HP for making bitfone.

+1 on the update.zip, but I don't believe the store telling goinskiing they can update it.

So here:

Goinskiing, go to the store, get the update.zip and bring back, upload to us.

Simple!
 
**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?
 
Status
Not open for further replies.
Back
Top