Good point, especially since the everything we've seen to date has said 1,000 TEST users, not random Droid owners. IIRC it was the 9,000 and then 200,000 rollouts that were "random."
DroidForums.net | Android Forum & News
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
2.1 ESE53 will be Official Release on the VZW Motorola Droid
- Thread starter cereal killer
- Start date
- Status
- Not open for further replies.
Good point, especially since the everything we've seen to date has said 1,000 TEST users, not random Droid owners. IIRC it was the 9,000 and then 200,000 rollouts that were "random."
richrcp;318914[SIZE=3 said:][/SIZE]I agree with both of your statements but I beleive that Verizon has some serious Quality Control issues!!!!!!! I think most of us on the forums understand what it takes to roll out updates but vzw is really dropping the ball.
Did you happen to read any of the previous pages/posts from yesterday? It's not Verizon's fault this got delayed.
I think it should be required for people to actually read thread postings before spewing forth their own conspiracy theories.
My opinion only, of course. Well, at least I'm the only one saying it out loud.
In a manner of speaking, yes it is. Selecting a 3rd party distributor with no capability to handle the load is entirely a quality of service issue, and completely in Verizon's lap. (If that happens to be the case).
This supposed update has been in the works for over 6 months, and only now they find this out ??? Either true, or they are making this up to cover something else.
you're right, we should stomp our fist and get mad and demand justice! I think I'm getting rid of my Droid over this whole fiasco! No way can I be happy with Verizion or the Droid knowing these kind of business practices are accepted!
As near as I can tell, there are two main stories floating around the ether about why the update didn't happen..
There is the: "We encountered a distribution problem with our distribution people and it's been delayed".
Then, there is the "Verizon rolled out the update to a small number of test users, with the rest of us to get it "soon"". As no date has been set for the continuation of the update, you get to define the meaning of "soon".
Both scenarios are plausible. CK posted something a couple of pages back about Bitphone needing a consultant to consult with them on the "redesign" of their distribution system to handle the large rollouts.
Verizon reps, and Verizon itself have indicated, in various ways, that the 2.1 update was given to some test users to evaluate.
Either one of these scenarios, given that they are the most plausible of everything I have heard, will take some time to rectify. If it is being used by some "test users", it will take at least a week for the update to be properly evaluated. If the first one is true, it will easily be a couple of weeks before the correction of the issue at Bitfone allows for the update to go out.
So, either way, this entails another week of wating, in my opinion.
There is the: "We encountered a distribution problem with our distribution people and it's been delayed".
Then, there is the "Verizon rolled out the update to a small number of test users, with the rest of us to get it "soon"". As no date has been set for the continuation of the update, you get to define the meaning of "soon".
Both scenarios are plausible. CK posted something a couple of pages back about Bitphone needing a consultant to consult with them on the "redesign" of their distribution system to handle the large rollouts.
Verizon reps, and Verizon itself have indicated, in various ways, that the 2.1 update was given to some test users to evaluate.
Either one of these scenarios, given that they are the most plausible of everything I have heard, will take some time to rectify. If it is being used by some "test users", it will take at least a week for the update to be properly evaluated. If the first one is true, it will easily be a couple of weeks before the correction of the issue at Bitfone allows for the update to go out.
So, either way, this entails another week of wating, in my opinion.
I know what happened!
I know what happened!
The first 1000 randomly-selected phones were all rooted and rejecting updates, so after Verizon sent out 1000 updates and saw none of them actually installing it, they assumed something went wrong and stopped the distribution.
Ha, not really. But I did have some really suspicious crashes the other day starting a little after noon. blinking notification light still worked, but screen wouldn't turn on, had to pull the battery. Happened a few times over a few hours, but works fine, now. Does anybody know what would actually happen if an update got pushed to somebody blocking updates? Does it silently and gracefully fail out when it can't open otacerts.zip, or does it crash, burn, and take everything down with it?
I know what happened!
The first 1000 randomly-selected phones were all rooted and rejecting updates, so after Verizon sent out 1000 updates and saw none of them actually installing it, they assumed something went wrong and stopped the distribution.
Ha, not really. But I did have some really suspicious crashes the other day starting a little after noon. blinking notification light still worked, but screen wouldn't turn on, had to pull the battery. Happened a few times over a few hours, but works fine, now. Does anybody know what would actually happen if an update got pushed to somebody blocking updates? Does it silently and gracefully fail out when it can't open otacerts.zip, or does it crash, burn, and take everything down with it?
Ha, not really. But I did have some really suspicious crashes the other day starting a little after noon. blinking notification light still worked, but screen wouldn't turn on, had to pull the battery. Happened a few times over a few hours, but works fine, now. Does anybody know what would actually happen if an update got pushed to somebody blocking updates? Does it silently and gracefully fail out when it can't open otacerts.zip, or does it crash, burn, and take everything down with it?
Coincidence?
If I'm not mistaken, the phone searches for updates, not the other way around. If you're rooted with SPRecovery, your phone simply never looks for updates.
Did you happen to read any of the previous pages/posts from yesterday? It's not Verizon's fault this got delayed.
I think it should be required for people to actually read thread postings before spewing forth their own conspiracy theories.
My opinion only, of course. Well, at least I'm the only one saying it out loud.
In a manner of speaking, yes it is. Selecting a 3rd party distributor with no capability to handle the load is entirely a quality of service issue, and completely in Verizon's lap. (If that happens to be the case).
This supposed update has been in the works for over 6 months, and only now they find this out ??? Either true, or they are making this up to cover something else.
you're right, we should stomp our fist and get mad and demand justice! I think I'm getting rid of my Droid over this whole fiasco! No way can I be happy with Verizion or the Droid knowing these kind of business practices are accepted!
I'm not stomping and shouting, however I know where the faults lie in this fiasco, period.
If I'm not mistaken, the phone searches for updates, not the other way around. If you're rooted with SPRecovery, your phone simply never looks for updates.
Actually, yeah, you are a little mistaken. The update notification is pushed, not polled. The Verizon instructions for the last update mentioned that you may need to connect to wifi and just leave it connected for a period of time to wait. The "check for updates" option in the menu only seems to check for updates that have already been pushed to the phone.
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 (so it disallows the update from being pushed). It's assumed that the update push would just get rejected.
SPRecovery only disallows update.zip from being installed once it's already downloaded to the SD card. It doesn't come into play at all except when you are intentionally rebooting into recovery.
I'm actually not sure that the SPRecovery option to allow update.zip will actually do anything at all to prevent an OTA installation. Unless SPRecovery actually responds to the commands to automatically install an update issued by the OTA installer, it just won't do anything at all. I'm 99.9999% sure that the factory recovery image is needed to install an OTA update, unless you manually initiate it.
I'm not stomping and shouting, however I know where the faults lie in this fiasco, period.
I'm sure that's ever so satisfying. Knowing is 1/2 the battle!
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.
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.
richrcp;318914[SIZE=3 said:][/SIZE]I agree with both of your statements but I beleive that Verizon has some serious Quality Control issues!!!!!!! I think most of us on the forums understand what it takes to roll out updates but vzw is really dropping the ball.
Did you happen to read any of the previous pages/posts from yesterday? It's not Verizon's fault this got delayed.
I think it should be required for people to actually read thread postings before spewing forth their own conspiracy theories.
My opinion only, of course. Well, at least I'm the only one saying it out loud.
KevinJ,
Yes sir I do read and respectively disagree with your statement that the delay is not Verizon's fault. From my experiences and whatever your profession is in this life you must ensure that the people that you manage, hire , and work with are competent and capable of completing assignments. Again, this a Quality Control issue which may not directly be vzw's fault, but is a direct reflection on their leadership.
joshuaclee
Member
Anyone know of an Android website where I can get Android info without all the drama?
They should create a thread on here for that. Maybe call it . . . Official 2.1 release news thread?
armeddroid
Senior Member
geez people
get a grip
get a grip
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
- Status
- Not open for further replies.
Similar threads
- Replies
- 5
- Views
- 2K
- Replies
- 565
- Views
- 160K
- Replies
- 3K
- Views
- 645K