Don't Want 2.2......Yet

[purple95]

Rather atypically, for me at least, I purchased a Droid X on launch day. I normally wait for others to test new technology.

Anyway.....after a few minor bumps getting my X set up, I am EXTREMELY happy with it. It's not broken and doesn't need fixing. The phone is stone cold stock except for a few well known, mainstream apps.

Now to my question:
At some point will Verizon force 2.2 on me via an OTA update without my approval and/or acknowledgment ? At present I can check the update function and the 2.2 update appears but I can select "Later" and not install. Is there a method to prevent Verizon from automatically updating my phone if such an attempt is made?

I have spent all morning reading the horror stories on this and other boards and right now don't want any part of the upgrade. I might want 2.2 sometime in the future however, after Motorola fixes the fixes it made to 2.1, but I want to make that decision for myself, and not have Verizon force it upon me.

dan

 

[MacII]

I'm not absolutely positive, but I think you will just have to keep refusing the download when it gets pushed to you.

Honestly though, I've only seen a few posts about people having trouble with the install and they all had made some modification i.e rooted or used a leaked froyo without using sbf back to 2.1 beforehand. What scares you about the update? If you think you're extremely happy with the DX now, you will be pleasantly surprised with 2.2 I think. To each their own though.

 

[xliderider]

I can tell you, the 2.2 OTA is running flawlessly, so far (knocks on wood). All settings and data is retained through the update, so no worries there.

The difference is dramatic, screens are scrolling much more fluidly, the keyboard is keeping up with fast typing, etc. I say, if you aren't into rooting, theming, etc. there is no reason not to accept the update.

 

[northernmoris]

If you haven't rooted, which it sounds like you haven't, you will have no problem getting he update. Its only people that have modded stuff.

 

[purple95]

Mac,

Thanks for your thoughts.

Yes, I've noticed MOST of the people reporting problems had modified the X in some manner prior to the upgrade and yet some did not.

What scares me is the potential for problems. I would like to have the benefits supposedly associated with 2.2, just not deal with the problems many have reported. This old man is not not technologically equipped to deal with a bricked phone or one with serious issues as some of you are.

dan

 

[xliderider]

After the download was done, it took approximately 5 minutes for the update to install and boot up. If that isn't easy, I don't know what is.

The benefits are noticeable. Feels like you have a new phone amped up on caffeine, it's snappier and much more lively and responsive.

 

[EKG]

Haven't noticed any problems yet. Go upgrade! It is 10000x better.

 

[Willyg44]

You won't regret it. If you are on unrooted 2.1 and upgrading to unrooted 2.2, you're fine. Most of the problems were probably from people who were rooted. I was on forums all last night for hours, and saw no problems with people going from 2.1 to 2.2 unrooted.

 

[cygnusloop]

Yeah, if your not rooted or modded, the update is nothing but goodness. It's inevitable, so I would just go ahead and do it. For me, the updated gmail app, and the improved battery management are worth it alone. But there is much, much more (including the improved keyboard that I am using right now).

 

[Deleted User]

I'm not so worried about the problems. I'm concerned about that bootloader update. I am holding off on the 2.2 OTA update until I see some kind of evidence that upgrading the bootloader isn't going to be a major impediment to future custom software builds.

 

[vr4]

mine took about 10 minutes start to finish downloading over 3g.

no issues other than a couple minutes for the phone to be happy with the update. overall i very happy i decided to do it.

3 other friends also had no issues with theirs.

 

[jksilva]

Is anyone else getting this message? I had used universal root and then unrooted, renamed apps back to the *.apk and shut the phone down, but still get this message when I check for updates.
Right now I am on vacation at Lake Tahoe, so maybe it is something to do with the network coverage. Any ideas?

 

[northernmoris]

I'm not so worried about the problems. I'm concerned about that bootloader update. I am holding off on the 2.2 OTA update until I see some kind of evidence that upgrading the bootloader isn't going to be a major impediment to future custom software builds.

That's exactly it.. If rooting and beyond that is something your interested in, it sounds like you might be s.o.l.. If your rooted stay with the leak,


Guys "The leak is your friend, at this point cherish it for what its worth.."

 

[bbuck002]

@Purple, you sound like you have come over from blackberry...haha...
I'm from a bbstorm1 and did all the leaks, updates, whatever, and can fully understand your trepidation with upgrading (after the pisspoor excuses for OS that verizon allowed released for blackberries) however, and a BIG however, this ain't a blackberry. I have an unrooted/modded X and really I was waiting to do any rooting or modding until after 2.2 was officially released so I wouldn't have upgrade problems. and i am EXTREMELY happy i waited. My phone is acting like a new device (read as, it's acting the way I think it should act). it's way faster with some pretty nice app changes (gallery, camera, gmail) but also my biggest complaint was fixed. I don't loose my data connection (when listening to pandora) when i leave a wifi area and my phone switches to 3g. I used to have to close and restart programs so they would reconnect. That alone, when I saw it was fixed, was the biggest reason for upgrading right away...

after I upgraded, my phone did run a little slowly, but a battery pull and fresh restart cleared that up.. there has been no lag so far, and my battery life has also been noticably improved...and its still just the first day with it.

i suggest you go for it! takes just a few minutes...

 

[Old Man]

Honestly though, I've only seen a few posts about people having trouble with the install and they all had made some modification i.e rooted or used a leaked froyo without using sbf back to 2.1 beforehand.

Not true. My DX was not rooted, no leaked Froyo and even running the stock Blur interface yet it was bricked by today's Froyo OTA update. And if you look at the poll in http://androidforums.com/motorola-droid-x/148070-official-2-2-froyo-ota-thread.html, it looks like several people have had similar experiences.

That's not saying there may not be some specific reason for these problems. The folks at the VZW store where I took mine suggested my moving the phone from one room to another during the update may have caused my problem and some others may have inadvertently hit a button during the update or whatever. On the other hand, the store also said they had already seen three DXs stuck on the Motorola logo screen, although mine was apparently the only one that a battery pull could not fix.

Luckily, I backed up everything on my SD card a couple of days ago while gmail, Backup Assistant and AppBrain should make restoring my contacts and apps pretty easy. And thankfully the wait for Droid X's is much shorter right now, so with overnight delivery my replacement should be here Saturday.

 

[MacII]

Not true. My DX was not rooted, no leaked Froyo and even running the stock Blur interface yet it was bricked by today's Froyo OTA update. And if you look at the poll in http://androidforums.com/motorola-droid-x/148070-official-2-2-froyo-ota-thread.html, it looks like several people have had similar experiences.

That's not saying there may not be some specific reason for these problems. The folks at the VZW store where I took mine suggested my moving the phone from one room to another during the update may have caused my problem and some others may have inadvertently hit a button during the update or whatever. On the other hand, the store also said they had already seen three DXs stuck on the Motorola logo screen, although mine was apparently the only one that a battery pull could not fix.

Luckily, I backed up everything on my SD card a couple of days ago while gmail, Backup Assistant and AppBrain should make restoring my contacts and apps pretty easy. And thankfully the wait for Droid X's is much shorter right now, so with overnight delivery my replacement should be here Saturday.

Actually, at the time of writing that post it was true. You are the first person that I've seen that has stated that the OTA bricked their phone and they hadn't modded it at all prior and now with the link provided, six additional (assuming you voted). I never said that problems weren't a possibility, and even so, if you want to base it on that survey alone (which wouldn't really be wise): there's a four percent chance of bricking your phone - for me it's worth it to move forward. Additionally, no one can prove one way or another that a bricked DX brought into the Verizon store wasn't modded without tinkering with it.

I'm sorry you had a bad experience and quite happy that you were able to back everything up beforehand.

 

[Hrethgir]

Just got Froyo pushed to my DX, took it out of my locker and it was 20% downloaded. So no point waiting, it will be forced on you unless you cancel the DL and turn off data or something while away. But my DL and install went perfectly smooth, coming from stock never-modified 2.1.

 

[MacII]

Just finished updating my wife's DX to 2.2 and I did more reading than when I did my own. After the download completes it gives you an option to "Install Now" or "Install Later". "Later" allows you to postpone the install for 12 hours. Whether or not you can keep postponing it I don't know.

 

[purple95]

Thanks so much to everyone who responded.

I've not seen any attempt so far from Verizon to automatically update the phone although if I understand correctly someone else did.

It's good to see that not everyone had problems with the update and those people seem to be satisfied. This, of course, leaves me very much on the fence about the update.

My plan at this point is to keep abreast of others' experiences for the next few days and make a decision then.

Thanks again,
dan

 

[purple95]

Well, I didn't get an opportunity to carry out my plan.

I returned to my office about an hour ago and found my Droid X in the middle of the 2.2 download. I had received no advance notice or option to decline.

Fifty or so minutes now have passed after the download with my phone stuck on the big white "M".

Any suggestions?

dan

 

[northernmoris]

Well, I didn't get an opportunity to carry out my plan.

I returned to my office about an hour ago and found my Droid X in the middle of the 2.2 download. I had received no advance notice or option to decline.

Fifty or so minutes now have passed after the download with my phone stuck on the big white "M".

Any suggestions?

dan

Thats such BS.... And not on your end.. Motorola really dropped the ball on this one.

 

[cwrig]

I have spent all morning reading the horror stories on this and other boards and right now don't want any part of the upgrade. I might want 2.2 sometime in the future however, after Motorola fixes the fixes it made to 2.1, but I want to make that decision for myself, and not have Verizon force it upon me.

dan

The 2.2 OTA installed on my phone while I took a shower and worked flawlessly. Im having none of the problems mentioned in the problem threads and the phone is faster. I suspect many of the problems are mod based. I would not fear 2.2

 

[cygnusloop]

Fifty or so minutes now have passed after the download with my phone stuck on the big white "M".

Any suggestions?

dan

Battery pull.

 

[MacII]

Well, I didn't get an opportunity to carry out my plan.

I returned to my office about an hour ago and found my Droid X in the middle of the 2.2 download. I had received no advance notice or option to decline.

Fifty or so minutes now have passed after the download with my phone stuck on the big white "M".

Any suggestions?

dan

WOW! Ain't this an instance of "what you fear you create" (not really of course but it fits for those cosmic believers out there). Sorry to hear this. I'd try a battery pull as cygnusloop suggested, maybe more than once if needed. Chances are you will be alright afterwards...at least I hope so. Best of luck!

 

[purple95]

WOW! Ain't this an instance of "what you fear you create" (not really of course but it fits for those cosmic believers out there). Sorry to hear this. I'd try a battery pull as cygnusloop suggested, maybe more than once if needed. Chances are you will be alright afterwards...at least I hope so. Best of luck!

Hey Mac,

Yeah, ain't it the truth. Rather like "be careful what you wish for, you just may get it", only in reverse.

I tried a quickie battery pull...no luck.

I'm going to pull the battery and let it set overnight. Here's wishing myself luck.

Hitting the hay now.

Thanks for the help everyone.

dan