2.1 ESE53 will be Official Release on the VZW Motorola Droid

[REMilk]

It's not Verizon's fault this got delayed.

In reality it is Verizon's fault that there was a delay. Verizon has responsibility for the upgrade, from contracting with Motorola for the hardware, Google for the OS, and the firm to push out the upgrade. Verizon should have completed "due diligence" prior to contracting with a firm to push out this upgrade to ensure they could accomplish the rollout to Verizon's specification.

In my industry, as in many others we conduct 'stress testing' to ensure that the system can handle the maximum expected load plus a percentage above that maximum threshold. Since I am not involved either directly or indirectly, I cannot say with certainty if stress testing was conducted and/or the stress test results reviewed by Verizon.

In reality, Verizon has shown they execute a quality assurance plan in two phases thus far, though the delay caused by these QA plans have angered some individuals.
1. The first delay last month when Verizon determined there was some kind of problem between the OS and the hardware; better to delay than have a lot of Droids not working as expected.
2. The delay when the rollout vendor could not handle the rollout plan. Nothing could be worse than receiving partial or corrupted updates.

I will state that I am disappointed in the delay, but life and my Droid goes on. If I really had the incentive, I would root my Droid and might possibly have different or most likely increased functionality.

I wish everyone would take a deep breath, now exhale; deep breath, exhale; deep breath, exhale.

Bob

 

[RW-1]

Se7enLC,

I would aggree, but it would have to poll something on the selected phone would it not?

The answers we got to the "what happens if we manually upgrade to 2.0.1?" questions was it would not be pushed to the phone, based upon what was reported by the phone etc at the time.

Please correct if wrong.

If something is actually being pushed out to the phone, then no, nothing has to poll for an update.

For the 2.0.1 update, they said they would push the update out to users, which is why when people tried to click on "check if their is an update for my phone", they got nothing stating that "your phone is already up to date." and yes, I did try back with the update 2.0.1

Take a step back for a minute.

SW update is selected to go to a phone by whatever means they decide.

Phone has to be queried in some respect, because:

"Moving/deleting otacerts.zip (like most ROMs do) removes the certificates that allow a particular server or set of servers to be authorized to connect and push an update "

Unless the phone is queried, the updater has no choice other than to put the update.zip on all the phones selected, and for the non rooted who did it manually:

I never got a notification to update, nor did another update.zip appear on my SD (I removed after manually installing)

Hitting check for updates doesnt go out into the cloud, it looks on your SD root for the update.zip ...

 

[Purgatory]

Se7enLC,

I would aggree, but it would have to poll something on the selected phone would it not?

The answers we got to the "what happens if we manually upgrade to 2.0.1?" questions was it would not be pushed to the phone, based upon what was reported by the phone etc at the time.

Please correct if wrong.

If something is actually being pushed out to the phone, then no, nothing has to poll for an update.

For the 2.0.1 update, they said they would push the update out to users, which is why when people tried to click on "check if their is an update for my phone", they got nothing stating that "your phone is already up to date." and yes, I did try back with the update 2.0.1

Take a step back for a minute.

SW update is selected to go to a phone by whatever means they decide.

Phone has to be queried in some respect, because:

"Moving/deleting otacerts.zip (like most ROMs do) removes the certificates that allow a particular server or set of servers to be authorized to connect and push an update "

Unless the phone is queried, the updater has no choice other than to put the update.zip on all the phones selected, and for the non rooted who did it manually:

I never got a notification to update, nor did another update.zip appear on my SD (I removed after manually installing)

Hitting check for updates doesnt go out into the cloud, it looks on your SD root for the update.zip ...

All they would have to do is send out a test file, and ask the phone if it is up to date by checking the version number. Then it will ask if the user wants to update. There does not have to be any type of polling in the system to querry an update to the system.

I did get a notification asking me if I would like to update (I did not manually update).

"Moving/deleting otacerts.zip (like most ROMs do) removes the certificates that allow a particular server or set of servers to be authorized to connect and push an update "

Yes, because now the certification to see that it is a Verizon phone and a legitimate phone to use on the system are not there, now it doesn't need to update the phone. Or... it recognizes that the phone now is not the same ROM as a standard ROM on the phone, so it can't update the phone effectively without causing harm to the contents on the phone.
I didn't have to do anything in terms of pulling my SD card, or putting widgets back onto my phone after installing the pushed out update.

 

[n0inf0]

Verizon tweeted...

Clarifying the Verizon Android 2.1 Update for Droid, http://www.phonescoop.com/news/item.php?n=5676

 

[Technoman]

Verizon tweeted...

Clarifying the Verizon Android 2.1 Update for Droid, http://www.phonescoop.com/news/item.php?n=5676

Old news, and has already been posted.

 

[n0inf0]

Verizon tweeted...

Clarifying the Verizon Android 2.1 Update for Droid, http://www.phonescoop.com/news/item.php?n=5676

Old news, and has already been posted.

I realise that but it looked like we were devolving into an angry mob. Just throwing up Verizon's actual response.

 

[bradgsanford]

Beavers & ducks!

 

[FMofdeath]

Beavers & ducks!

I agree. Everyone should take some time and think about this.

 

[Aero320]

The 2.1 .sbf that is listed on the VZW website is already available

The .sbf file that VZW has listed on their website is already available for download. ...C-01.3E.03P... Supposedly the only difference in that build and the previous one is that changes were made to the radio.

Last night I installed the new build using RSDLite. Everything went well (there were even instructions on how to root the new build using adb).

The only problem that I have seen so far is that Google Maps will not update. It produces and error message that says that the installation was unsuccessful. I went into adb and deleted the Maps.apk, then tried to reinstall the Google Maps application. This time a different error appeared.

If I were guessing, I would say that the radio update that was included in the latest install interfered with the Google Maps update. And, I would also guess that VZW did send the update OTA to 1000 and all of them had the same problem when they tried to update their Google Maps, thus the delay until they figure out a fix.

The instructions for rooting the ESE53 are at this link:

How-To: Root ESE53 .sbf

 

[tehpriest]

The European 2.1 sbf also seems to be genuine. So Milestone got 2.1 before Droid LOL

 

[yourname93]

how do you flash the devic with the update? i open rsd lite and then i choose the sbf file and i dont know how to get it on from there help?

 

[adrynalyne]

The .sbf file that VZW has listed on their website is already available for download. ...C-01.3E.03P... Supposedly the only difference in that build and the previous one is that changes were made to the radio.

Last night I installed the new build using RSDLite. Everything went well (there were even instructions on how to root the new build using adb).

The only problem that I have seen so far is that Google Maps will not update. It produces and error message that says that the installation was unsuccessful. I went into adb and deleted the Maps.apk, then tried to reinstall the Google Maps application. This time a different error appeared.

If I were guessing, I would say that the radio update that was included in the latest install interfered with the Google Maps update. And, I would also guess that VZW did send the update OTA to 1000 and all of them had the same problem when they tried to update their Google Maps, thus the delay until they figure out a fix.

The instructions for rooting the ESE53 are at this link:

How-To: Root ESE53 .sbf

PM me. I will show you how to fix this issue.

 

[RW-1]

"and ask the phone if it is up to date by checking the version number. "

Gee if that isn't : "Phone has to be queried in some respect" THAT is a POLL.

Then you are on a differnet planet than I am.

If phone responds with the 2.1 from a manual, then the file is not pushed. You do not get the notification to even do it until after the file has been DL'd to your phone.

 

[adrynalyne]

The European 2.1 sbf also seems to be genuine. So Milestone got 2.1 before Droid LOL

We have had ESE53 for two weeks.

 

[LifeIsABeach]

Anyone know of an Android website where I can get Android info without all the drama?

There are others such as androidcommunity and alldroid, but I find this site has the best info. I just ignore any threads where a pissing match starts (thankfully there are not many of them).