when official 2.2 is released we wont have to wait

[tilejoesham]

Blur Allows for “Pull” Updates to DROID X and 2 | Droid Life: A Droid Community Blog

just wanted to share this here so everyone can rest a little easier that this method is confirmed so when verizon decides to release froyo for us then we will be able to grab it asap as long as we dont kill the servers lol but one positive thing is we wont be 2 weeks in still waiting for that little notification stating there is a system update !! for once i have to say ty moto blur lol

 

[dguy]

Makes sense. When the first Droid X OTA update came out, just hitting "check for updates" would get you the update, you didn't have to wait for a notification first.

 

[Wolfedude88]

Makes sense. When the first Droid X OTA update came out, just hitting "check for updates" would get you the update, you didn't have to wait for a notification first.

That is not the same thing, the original droid could not pull it from the server if you notice it says that. Yes you could check like you said but that just means your phone had the update pushed to it, but you did not receive a notification yet.

This means if true for the Droid X/2, that as soon as Motorola has it on their server we can get it by checking. We wouldn't have to wait for them to start sending it out.

 

[Doit2it]

Makes sense. When the first Droid X OTA update came out, just hitting "check for updates" would get you the update, you didn't have to wait for a notification first.

That's all well and good, but my "check for updates" has given me this response for the past month:
Check for update was not available at this time.
Try again later.

Yes I did get the 1st update by doing a check. And I have not rooted or installed the leaked Froyo. Not sure why update hasn't been working. Anyone else? I have seen a couple of posts here in the Droid X forum stating the same problem/response.

 

[dguy]

That is not the same thing, the original droid could not pull it from the server if you notice it says that. Yes you could check like you said but that just means your phone had the update pushed to it, but you did not receive a notification yet.

This means if true for the Droid X/2, that as soon as Motorola has it on their server we can get it by checking. We wouldn't have to wait for them to start sending it out.

What are you talking about? The Droid 2 and X have a button for checking for updates that actually does something. Stock Android devices like the Droid 1 do not have this feature, they have to wait to have the update pushed to them.

 

[dguy]

That's all well and good, but my "check for updates" has given me this response for the past month:
Check for update was not available at this time.
Try again later.

Yes I did get the 1st update by doing a check. And I have not rooted or installed the leaked Froyo. Not sure why update hasn't been working. Anyone else? I have seen a couple of posts here in the Droid X forum stating the same problem/response.

Maybe because there is no new update out yet?

 

[zandroidx]

Maybe because there is no new update out yet?

I just tested mine twice. Mine says: - Your device is up to date! No update is necessary at this time.- -Thank you for pressing the self-destruct button. (j/k) -

 

[Lightninrod]

Check for update was not available at this time.
Try again later

That's all I've been getting for weeks now. Glad it's not just my phone.

 

[vr4]

I just tested mine twice. Mine says: - Your device is up to date! No update is necessary at this time.- -Thank you for pressing the self-destruct button. (j/k) -

same here

 

[CrashF16]

Same here but usually if I check immediately again, it does check for updates.

 

[j_ryan]

That's all well and good, but my "check for updates" has given me this response for the past month:
Check for update was not available at this time.
Try again later.

Yes I did get the 1st update by doing a check. And I have not rooted or installed the leaked Froyo. Not sure why update hasn't been working. Anyone else? I have seen a couple of posts here in the Droid X forum stating the same problem/response.

Have you tried checking on wifi instead of 3G? That fixed it for me.