Official 2.1 findings thread

  • Thread starter Thread starter Roy Aguilera
  • Start date Start date
Status
Not open for further replies.
Well we have less than a week to find out.


So sometime in the next week we should get this update.
 
"Soon" and "should" are dangerous words. I'm not counting on anything before Easter, tbh. That's optimistic, too.
 
"Soon" and "should" are dangerous words. I'm not counting on anything before Easter, tbh. That's optimistic, too.

I am using those words because I am skeptical myself!


But if this doesn't hit by the end of the PROMISED time; I'll be pretty irritated.

Because this was the one official statement we received.
 
There are so many stories floating around the forums regarding this update. I think its realistic not to expect it until sometime next month, if then. Almost ready to bet money.
 
This place is getting ready to explode -- calm before the storm if you will. Kinda like the ocean pulls back and all is peaceful just before the tsunami hits.

No way they're getting that update out this week.

Everyone brace yourselves :)
 
There are so many stories floating around the forums regarding this update. I think its realistic not to expect it until sometime next month, if then. Almost ready to bet money.

This place is getting ready to explode -- calm before the storm if you will. Kinda like the ocean pulls back and all is peaceful just before the tsunami hits.

No way they're getting that update out this week.

Everyone brace yourselves :)

The "Before end of Q1" wasn't a rumor. It was a real official announcement that wasn't pulled or retracted or replaced.
 
Update from bill23 @ howardforums:

"2.1 delay

so, "I have heard" that the yet another delay in the OTA 2.1 is due to google themselves. no longer moto or vzw.seems they have found a few things that must be measures so yet again ese53 was not signed off on and now will be built over again.or should i say it has been built over again. "so i am told" lol lol"

http://howardforums.com/showthread.php?t=1631541

Sucks but what can we do.
 
Update from bill23 @ howardforums:

"2.1 delay

so, "I have heard" that the yet another delay in the OTA 2.1 is due to google themselves. no longer moto or vzw.seems they have found a few things that must be measures so yet again ese53 was not signed off on and now will be built over again.or should i say it has been built over again. "so i am told" lol lol"

HowardForums: Your Mobile Phone Community & Resource - 2.1 delay

Sucks but what can we do.




Yeah, I am not buying that.

Its not the software I bet, its the distribution of it.

The Milestone and the Droid are the same machine (minus the radio)

And the Milestone updated in how many countries?


They should just cut their losses and have a "come into the store to get your 2.1 update" thing.

It would be genius! We'd get 2.1, more people would be in the store and more likely to impulse purchase! WIN WIN
 
Update from bill23 @ howardforums:

"2.1 delay

so, "I have heard" that the yet another delay in the OTA 2.1 is due to google themselves. no longer moto or vzw.seems they have found a few things that must be measures so yet again ese53 was not signed off on and now will be built over again.or should i say it has been built over again. "so i am told" lol lol"

HowardForums: Your Mobile Phone Community & Resource - 2.1 delay

Sucks but what can we do.

You beat me to it. I ask him if that meant its a new build and he said yeah. So we are getting sometime else instead of ese53, we are probably looking at next month.
 
Last edited:
Update from bill23 @ howardforums:

"2.1 delay

so, "I have heard" that the yet another delay in the OTA 2.1 is due to google themselves. no longer moto or vzw.seems they have found a few things that must be measures so yet again ese53 was not signed off on and now will be built over again.or should i say it has been built over again. "so i am told" lol lol"

HowardForums: Your Mobile Phone Community & Resource - 2.1 delay

Sucks but what can we do.

If this is the case, it has to go through Verizons testing procedures again. That could take weeks. Uhgggg! :eek:

There must have been a significant bug for them to pull it at the last minute. I wonder why it wasn't caught during the initial testing??? That is if it really made it past the initial testing. Who knows???? :mad:

Tick Tock.... Tick Tock..... Tick Tock..... Time goes on, and on, and on and on.
 
The "Before end of Q1" wasn't a rumor. It was a real official announcement that wasn't pulled or retracted or replaced.

Oh, I fully understand that --- that's why I said brace yourself for an all out freak out -- because Verizon/Motorola is about to lie for the first time with respect to this update.

I remember when I first bought the iPhone 3GS, and AT&T kept pushing back the update for MMS feature to be enabled. People found work arounds, EVERYONE on the AT&T forums were calling AT&T reps -- and the rumors were the same as here.

This situation is IDENTICAL to the iPhone 3GS MMS update I went through last year. Figures -- I can't dodge this crap -- went through it with 3GS, and now going through the exact same thing with Droid.

Not sweatin' it though :)
 
I don't think they're going to lie... I just think they're going to push the update back to mid-April. :p Nothing to get worked up about, though heads will explode when the 1st rolls around.
 
Status
Not open for further replies.

Forum statistics

Threads
956,433
Messages
6,968,238
Members
3,163,544
Latest member
nnik67631