2.2 blows.... they ruined the phone

[eraursls1984]

Formatting my sd card isn't something I've tried yet. I'm really excited that it will fix my problems, but I just can't get myself to believe that that would fix anything... I will definitely try it though.

If in the future I am still unhappy, do you think if I called verizon they would replace my phone for the same one or a different one? Even if I bought it on day 1? I did not pay for insurance on my phone. This is a big if.

I know ranting won't help much, but I think a little bit is necessary otherwise we would not have any interesting threads on this forum lol...

Give it a shot, it has helped some people. Back up the sd card on your computer and reformat it, don't reinstall anything from the backup. See if that helps, then slowly add each folder. If something is corrupted you should be able to figure out what by doing this.

 

[eraursls1984]

Using the autokiller is just a bandaid for what is really causing the problems.

Why suffer? Take your device back and get a replacement like Tom108 suggested above.

I've had it a month and a half, I tried shortly after 2.2 but they won't exchange it because it works, just not well. I can't file the insurance claim unless it's lost or broken and then pay the $90. Then I'd be out a phone for a week or more.

 

[tom108]

I've had it a month and a half, I tried shortly after 2.2 but they won't exchange it because it works, just not well. I can't file the insurance claim unless it's lost or broken and then pay the $90. Then I'd be out a phone for a week or more.

an insurance claim will set you back a few bucks but they normally overnight it to you. especially if you ask.

 

[Outlaw71]

I've recently found autokiller and that seems to be helping, I haven't had much lag all day. The first time I installed it my phone went crazy and I had to uninstall, but after my problems persisted I gave it another try and its been running much better with autokiller installed. I think once I tweak the program I might get it running as smooth and consistent as I had 2.1.

I responded to you about AutoKiller in the other thread, but you might not have seen it. I have read the 'Details' write up (go to Autokiller, hit the menu key, click on 'settings', at the top of settings you will see Home page, click on that and at the bottom of the very first paragraph you'll see 'details', 'process manager' and 'FAQ') and can tell you that I understand Android 100 times better simply by reading that article. It's a bit long, but he does a great job of explaining the Android philosophy which is... keep apps running in the background at all times. This is the very foundation in which Android is built on, keeping your apps open so that when you close out of something it stays running in the background. Then when you come back to it, BAM, it's there at your finger tips, ready to use without having to wait for it to boot back up from scratch again.

So Android's management system assigns these apps a number that represents how important it is to you (this is all custom, the phone learns your habits, likes, dislikes, etc...), and when you start to run out of memory, it closes the apps that are least important to you. So by design an Android device is constantly using most of it's memory... that's by DESIGN... which means that going in a killing off all or most of the tasks to 'free up memory' is a huge waste of time because by design the phone is just going to go and use up all that memory again anyhow, that's how Android works. Which makes me realize why everyone has been telling us (yes, I used to use ATK's as well) that task killers go against Androids very nature. If you don't want your phone to keep apps running in the background, don't buy an Android device.

But what AutoKiller does is lets you set the buffer zone higher than it's set at normally. So where a stock Android phone doesn't start to kill unimportant apps until you reach something like 10 mb, you can change that figure to give your phone more free memory at all times (not just when you hit the kill switch in a task killing app... after doing which your phone started working on using up all that memory again anyhow). So take me for instance, I set my profile on 'Aggressive', which resets that value up around 90 mb's (there are actually 3 values, but I'm not exactly sure what each of them means)... so now my phone has a much larger buffer zone built into it so that it doesn't ever run out of memory. You can set that buffer zone as high as 250 mb's, but I honestly don't think you would see much difference between that and 100... unused memory is simply that, unused.

I checked my phone's free memory through Titanium Back-Up 3 times today and each time it was over 100 mb's...... Super sweet!!!!

 

[eraursls1984]

So by design an Android device is constantly using most of it's memory... that's by DESIGN... which means that going in a killing off all or most of the tasks to 'free up memory' is a huge waste of time because by design the phone is just going to go and use up all that memory again anyhow, that's how Android works. Which makes me realize why everyone has been telling us (yes, I used to use ATK's as well) that task killers go against Androids very nature. If you don't want your phone to keep apps running in the background, don't buy an Android device.

But what AutoKiller does is lets you set the buffer zone higher than it's set at normally. So where a stock Android phone doesn't start to kill unimportant apps until you reach something like 10 mb, you can change that figure to give your phone more free memory at all times (not just when you hit the kill switch in a task killing app... after doing which your phone started working on using up all that memory again anyhow). So take me for instance, I set my profile on 'Aggressive', which resets that value up around 90 mb's (there are actually 3 values, but I'm not exactly sure what each of them means)... so now my phone has a much larger buffer zone built into it so that it doesn't ever run out of memory. You can set that buffer zone as high as 250 mb's, but I honestly don't think you would see much difference between that and 100... unused memory is simply that, unused.

I noticed my phone would start to lag when between 50-70 mb's and would almost stop under 50. The 90 mb settings sounds perfect. When I used task killers I didn't have a problem with the system putting them back in memory for awhile, I could do whatever I wanted for atleast an hour, unless I let the lock screen come up, then the memory was full again. Now, going into settings to kill an app, I notice its back in the memory in about 5 seconds. Autokiller seems to take care of my problems, very little lag in the last 24 hours and I'm a heavy user. I also noticed someone say to make sure the stock home screen is empty if using LPP or ADW, so I went and cleared those(it had about 20 widgets and 20 short cuts from the factory reset.)

 

[Outlaw71]

I also noticed someone say to make sure the stock home screen is empty if using LPP or ADW, so I went and cleared those(it had about 20 widgets and 20 short cuts from the factory reset.)

Interesting... how do you do this?

 

[bouchigo]

Interesting... how do you do this?

Download Home Switcher from the market. Use it to switch to the native launcher.....once there, delete all the shortcuts and widgets, making sure all home screens are empty, then just switch back to LPP.

 

[Outlaw71]

Super sweet, I'm on it!



BTW, what do those things do to the phone anyhow?

 

[Outlaw71]

When I went to download it the dev says right on his page that it isn't compatible with 2.2 on the Droid X. There is another app that says it is compatible with 2.2, but it says all it does is let's you go into settings and select 'clear defaults' or something like that, doesn't say anything about being able to actually switch your home screen.

So I downloaded HomeSwitcher just for shits and giggles because... what could it hurt to try? Worked like a charm, I don't know if that's because I'm rooted or what, but it booted right up, let me switch over to my original home theme, clean it up, then switch back over to LP.

Man I must have had 40 shortcuts and widgets in my homescreens, didn't even realize they would still be there.

 

[tom108]

When I went to download it the dev says right on his page that it isn't compatible with 2.2 on the Droid X. There is another app that says it is compatible with 2.2, but it says all it does is let's you go into settings and select 'clear defaults' or something like that, doesn't say anything about being able to actually switch your home screen.

So I downloaded HomeSwitcher just for shits and giggles because... what could it hurt to try? Worked like a charm, I don't know if that's because I'm rooted or what, but it booted right up, let me switch over to my original home theme, clean it up, then switch back over to LP.

Man I must have had 40 shortcuts and widgets in my homescreens, didn't even realize they would still be there.

home switcher works i have it installed. getting rid of those widgets is a good idea. i suggested this in another thread i think.

 

[eraursls1984]

Man I must have had 40 shortcuts and widgets in my homescreens, didn't even realize they would still be there.

Same here, after my last reset first thing I did was install LPP so I didn't realize all that crap was there.

 

[Outlaw71]

Thanks for the tip. Between this, freezing all the bloatware on my phone, setting Autokiller to 'aggressive', and doing the factory reset/SD card format I have seen a HUGE improvement in the utilization speed of my phone. The only lag I experience at this point is the unlock screen upon wake up, but I attribute that to having it underclocked while sleeping, and then taking a few seconds to get back up to speed once I wake it up.

But if I have to live with a slight lag in the unlock screen to conserve battery, then what the hell, no skin off my back. Everything else runs smooth as silk!

 

[droidx_fan]

Does anyone here know the difference between ignorance and stupidity? Ignorance is the absence of knowledge. Stupidity is refusing to accept it. Blaming lagging issues on the 2.2 update is like taking your car in to get painted, and when you get it back and it starts running like crap blaming it on the new paint job, when in fact one of your plugs fouled out while driving out of the parking lot.

Now I'm not doubting that anyone has truely experienced problems since doing the 2.2 OTA update, but just what exactly do you think Google went out and did to deliberately hijack your phone? If you honestly don't think Google knows their ass from a hole in the ground then please free to pick up a Windows Mobil or iPhone and live in sweet mobile phone bliss.

The froyo update is just a slight refinement of their already outstanding OS, not a complete overhaul. That's not to say there aren't any bugs in it, there have been bugs in every one of their OS's so far, why would this one be any different? But overall nothing should be acting completely different from when eclair was in charge. If it is then something else has gone wrong in your phone. And if that's the case then do some research into what issue's people have been having with their phones and what they did to resolve those issues. Knowledge is power, and for every problem there is a solution.

But jumping on here and posting that 2.2 is the root of your freeze up's and crashes... well to be honest, that just makes you look like the guy running around telling everyone not to paint their car blue because once he did his car started running like crap!

I guess, based on your description then, you're a moron. That someone who is both ignorant and stupid.

Already outstanding OS? LMAO! Dude, really, you're over dosing on the koolaid. I will give you the Android OS has the potential to be outstanding but as is before Froyo, and after, is anything but outstanding.

If 2.2 is okay, then why would someone with a phone that works okay prior to the upgrade, with no changes aside from the upgrade, suddenly be experiencing horrendous problems? If that's your definition of ok, I'd hate to hear your definition of bad.

I like your "painting the car" analogy except is is terribly flawed. Here's the more accurate analogy. You take your car in to have the oil changed. Later in the day, the engine locks up. You find the mechanic forgot to put the drain plug back in resulting in all the oil quickly leaking out. You go back to the shop where you got the oil changed and all the mechanics are sitting around drinking Jack Daniels, drunk as skunks. You describe the problem and they all blame you!!! They give you some moronic analogy about painting your car and then blaming the engine failure on the painter.

This isn't some "machine" made for hi tech scientists or engineers, this is a consumer device designed (well, better put, should have been designed) to sell to the masses. In other words, it should just freaking work. You shouldn't have to perform battery pulls, factory resets, root, etc.. It should just work. Period. And this just simply isn't the case. Clearly. Factually.

Epic Fail Dude. Keep drinking the koolaid and making the moronic analogies, I get a real kick out of someone who is pompous as hell when in reality, they're a moron.

 

[Kevmueller]

I guess, based on your description then, you're a moron. That someone who is both ignorant and stupid.

Already outstanding OS? LMAO! Dude, really, you're over dosing on the koolaid. I will give you the Android OS has the potential to be outstanding but as is before Froyo, and after, is anything but outstanding.

If 2.2 is okay, then why would someone with a phone that works okay prior to the upgrade, with no changes aside from the upgrade, suddenly be experiencing horrendous problems? If that's your definition of ok, I'd hate to hear your definition of bad.

I like your "painting the car" analogy except is is terribly flawed. Here's the more accurate analogy. You take your car in to have the oil changed. Later in the day, the engine locks up. You find the mechanic forgot to put the drain plug back in resulting in all the oil quickly leaking out. You go back to the shop where you got the oil changed and all the mechanics are sitting around drinking Jack Daniels, drunk as skunks. You describe the problem and they all blame you!!! They give you some moronic analogy about painting your car and then blaming the engine failure on the painter.

This isn't some "machine" made for hi tech scientists or engineers, this is a consumer device designed (well, better put, should have been designed) to sell to the masses. In other words, it should just freaking work. You shouldn't have to perform battery pulls, factory resets, root, etc.. It should just work. Period. And this just simply isn't the case. Clearly. Factually.

Epic Fail Dude. Keep drinking the koolaid and making the moronic analogies, I get a real kick out of someone who is pompous as hell when in reality, they're a moron.

The problem with your analogy is that these same mechanics had to work on everyones car at the same time and and left out the drain plug on everyones car. Guess what, the mechanics did it right on my car because my X is running as good if not better than before with all the enhancements that were listed in the release being added. Not everyone is having problems, and I would be willing to say the majority are not having problems otherwise this would be a huge news story and it is not just some people.

I would be willing to buy this analogy, that one location where the cars were being produced used the wrong drain plug so after it was removed the first time it would not go back in and fit perfectly so it would fall out on the cars built at that location on that day from using the wrong size. I heard this in another thread that maybe there was a quality control issue at one location or something that would cause this to be so hit and miss. I personally know 14 people with X's and not one of them have had an issue with 2.2.

 

[Outlaw71]

I guess, based on your description then, you're a moron. That someone who is both ignorant and stupid.

Already outstanding OS? LMAO! Dude, really, you're over dosing on the koolaid. I will give you the Android OS has the potential to be outstanding but as is before Froyo, and after, is anything but outstanding.

If 2.2 is okay, then why would someone with a phone that works okay prior to the upgrade, with no changes aside from the upgrade, suddenly be experiencing horrendous problems? If that's your definition of ok, I'd hate to hear your definition of bad.

I like your "painting the car" analogy except is is terribly flawed. Here's the more accurate analogy. You take your car in to have the oil changed. Later in the day, the engine locks up. You find the mechanic forgot to put the drain plug back in resulting in all the oil quickly leaking out. You go back to the shop where you got the oil changed and all the mechanics are sitting around drinking Jack Daniels, drunk as skunks. You describe the problem and they all blame you!!! They give you some moronic analogy about painting your car and then blaming the engine failure on the painter.

This isn't some "machine" made for hi tech scientists or engineers, this is a consumer device designed (well, better put, should have been designed) to sell to the masses. In other words, it should just freaking work. You shouldn't have to perform battery pulls, factory resets, root, etc.. It should just work. Period. And this just simply isn't the case. Clearly. Factually.

Epic Fail Dude. Keep drinking the koolaid and making the moronic analogies, I get a real kick out of someone who is pompous as hell when in reality, they're a moron.

And I'm getting a real kick out of your handle.

 

[Outlaw71]

People who are swift to run in at the slightest sign of a situation where they may actually have to... oh I don't know, use their 'brain' to actually 'figure something out'... like, all on their own and stuff... who then immediately start criticizing everything in sight without giving the slightest effort to help improve, resolve or make things any better = worthless.

Dispite the fact that Android is by far the fastest growing cell phone OS in the industry and will soon not only eclipse Apple (which in and of itself would be impressive) but by the end of next year is also expected to eclipse Symbian (the OS found in Nokia phones... perhaps you've heard of them?), which is not only the current leading OS around the world, but who had long been thought to have an invincible grasp of the cell phone market for at least the next few decades due to their roots in places like China and India (meaning that every man woman and child in America would have to buy 10 cell phones a piece just to compete with those numbers)... Yes dispite those unimpressive figures I'm going to have to agree with you and say that the Android OS is complete and utter garbage. You couldn't be more right, the hoards of people who are flocking to Android are doing so because of all the bugs in the system, the poor reliability, and the general pathetic nature of each and every Android device on the market. Everyone loves an epic fail OS, there's no doubt about that bro.

Clearly.

 

[mancow]

Dunno.... I've had no problems with 2.2 at all.

 

[Outlaw71]

Dunno.... I've had no problems with 2.2 at all.

Well that goes without saying, as you are half cow. So far I'm pretty certain that they've had zero returns from cows to this point.

 

[magicfan1214]

I got my X last week, after the 2.2 updates came in, so mine's been froyo from the start. And I can attest to the fact that it runs excellently in every way.

Send in for a new one if necessary. But don't say the entire Droid X line is ruined, because it most certainly is not...

 

[Dajaha]

Too bad for those having problems.the phone had been amazing for me since going to ota 2.2

 

[Outlaw71]

This isn't some "machine" made for hi tech scientists or engineers, this is a consumer device designed (well, better put, should have been designed) to sell to the masses. In other words, it should just freaking work...

This is where you really show your ignorance btw... Android... well it actually was designed by techies for techies. Android is a completely fresh approach at OS development. Google created Android to be 'open source'... wrap your head around that for a second, 'open source' as in production and development of an OS that promotes access to the end product's source materials. Now who might a candiate be for developing such system... the guy serving you fries at McDonalds? Nah, I'd say it's the hi tech scientists and engineers you said it wasn't built for. You would be much more correct if you scrub out the word 'isn't' in the beginning of your sentence, and substituted it for 'is'.

Now, did Google know it was going to explode like it has? Likely not. But that's beside the point. You are a consumer with a choice to buy which ever cell phone you want to, just like I am... and we both chose an Android. Now, being open source, anyone who can appreciate the scope of what that means should know that everything within that relm isn't going to 'just work, period'. There are WAY too many variables for that to be a reality. If you want a phone that 'just works', then go buy an iPhone.

Because that is Steve Job's entire philosophy. He believes, that to give creative control to 'the masses', the phone is going to experience too many problems, and it would all be way too big a hassel to have to deal with. So things on the iPhone are exatly the way he wants them to be. Now, whether or not it 'just works' is not something I'm qualified to deem, as I've never had an iPhone. But that's his philosophy anyways, sounds like you are an Apple guy in Android clothing.

No, part of the entire Android experience is that it's all a work in process, and forever will be. But of course many consumers are of the mind set that if it's sold on a shelf somewhere, then it aught to be absolutely fool proof. Problem with that is, as soon as someone comes out with something that's fool proof, someone else goes out and creates a better fool.

I dunno, maybe I have partaken in a little too much of the cool-aid that is Android. But I truely appreciate this technology that Google has gone out and given us, and enthusiastically encourages us to go out and push it to it's absolute limits. I wish there were more companies like them out there. And less people who criticize them blindly when they don't even fully grasp the idea that's driving everything behind it.

 

[droidx_fan]

This is where you really show your ignorance btw... Android... well it actually was designed by techies for techies. Android is a completely fresh approach at OS development. Google created Android to be 'open source'... wrap your head around that for a second, 'open source' as in production and development of an OS that promotes access to the end product's source materials. Now who might a candiate be for developing such system... the guy serving you fries at McDonalds? Nah, I'd say it's the hi tech scientists and engineers you said it wasn't built for. You would be much more correct if you scrub out the word 'isn't' in the beginning of your sentence, and substituted it for 'is'.

Now, did Google know it was going to explode like it has? Likely not. But that's beside the point. You are a consumer with a choice to buy which ever cell phone you want to, just like I am... and we both chose an Android. Now, being open source, anyone who can appreciate the scope of what that means should know that everything within that relm isn't going to 'just work, period'. There are WAY too many variables for that to be a reality. If you want a phone that 'just works', then go buy an iPhone.

Because that is Steve Job's entire philosophy. He believes, that to give creative control to 'the masses', the phone is going to experience too many problems, and it would all be way too big a hassel to have to deal with. So things on the iPhone are exatly the way he wants them to be. Now, whether or not it 'just works' is not something I'm qualified to deem, as I've never had an iPhone. But that's his philosophy anyways, sounds like you are an Apple guy in Android clothing.

No, part of the entire Android experience is that it's all a work in process, and forever will be. But of course many consumers are of the mind set that if it's sold on a shelf somewhere, then it aught to be absolutely fool proof. Problem with that is, as soon as someone comes out with something that's fool proof, someone else goes out and creates a better fool.

I dunno, maybe I have partaken in a little too much of the cool-aid that is Android. But I truely appreciate this technology that Google has gone out and given us, and enthusiastically encourages us to go out and push it to it's absolute limits. I wish there were more companies like them out there. And less people who criticize them blindly when they don't even fully grasp the idea that's driving everything behind it.

I guess I have to disagree. The open platform was designed to allow techies to develop cheap software applications and for companies like Motorola to adopt it into their products. I cannot accept for one second that Google developed this as a science fair experiment but instead, had the volume utilization in mind from the beginning. Google isn't some small, 2nd rate tech company, it makes no sense for them to invest in something that doesn't have the potential for profound impact on the market.

The other point you've missed here is, I don't blame Google and Android. IMHO, the responsibility here lays with Motorola and Verizon. They are the ones pushing the product to the market for mass consumption. The Android OS is simply the foundation for them to overlay their own software/firmware. Now if they made a bad choice with the Android OS, shame on them.

I believe Moto and Verizon succumbed to the pressure and pushed this release out to market a couple of weeks to a month before the final bugs were rung out. I don't disagree that for many people, this release is working near perfect. The problem I have is there are far too many people, IMHO, that are having some fairly serious problems with it. Due to their impatience, incompetence or whatever you wish to call it, they are beta testing their freaking software with their Customers. And this is just wrong.

Now someone made a comment about my handle being funny. I had to laugh at that a bit. I came from an iPhone which I loved for its simplicity. I absolutely hated the AT&T network, they should be sued for billions for their blatant incompetence and horrible service. I went from Verizon to AT&T and frankly had forgotten just how much better the Verizon network is. I happen to think as simply a device for making phone calls, the DroidX is the best phone BY FAR I've ever used. The signal strength, call quality, etc. is frankly phenomenal. I dropped more calls in some days with AT&T than I have in the two months I've had the DroidX.

So I am a fan, a huge fan! But I'm also frustrated with some of the problems. I get more frustrated when the koolaid drinkers want to gloss over the problems and seemingly brush them away as non existent and of zero importance. And by the way, I expect and could accept some "bugs" but it just seems like there are far too many. And very important functions, such as cut and paste, are still non existent or simply suck.

With all that said, you'd have to pry my DroidX out of my dead fingers before you could take it away and give me the iPhone/AT&T combo back. I still reserve the right however, to bitch about the shortcomings and bugs.

 

[crboone]

I responded to you about AutoKiller in the other thread, but you might not have seen it. I have read the 'Details' write up (go to Autokiller, hit the menu key, click on 'settings', at the top of settings you will see Home page, click on that and at the bottom of the very first paragraph you'll see 'details', 'process manager' and 'FAQ') and can tell you that I understand Android 100 times better simply by reading that article. It's a bit long, but he does a great job of explaining the Android philosophy which is... keep apps running in the background at all times. This is the very foundation in which Android is built on, keeping your apps open so that when you close out of something it stays running in the background. Then when you come back to it, BAM, it's there at your finger tips, ready to use without having to wait for it to boot back up from scratch again.

So Android's management system assigns these apps a number that represents how important it is to you (this is all custom, the phone learns your habits, likes, dislikes, etc...), and when you start to run out of memory, it closes the apps that are least important to you. So by design an Android device is constantly using most of it's memory... that's by DESIGN... which means that going in a killing off all or most of the tasks to 'free up memory' is a huge waste of time because by design the phone is just going to go and use up all that memory again anyhow, that's how Android works. Which makes me realize why everyone has been telling us (yes, I used to use ATK's as well) that task killers go against Androids very nature. If you don't want your phone to keep apps running in the background, don't buy an Android device.

But what AutoKiller does is lets you set the buffer zone higher than it's set at normally. So where a stock Android phone doesn't start to kill unimportant apps until you reach something like 10 mb, you can change that figure to give your phone more free memory at all times (not just when you hit the kill switch in a task killing app... after doing which your phone started working on using up all that memory again anyhow). So take me for instance, I set my profile on 'Aggressive', which resets that value up around 90 mb's (there are actually 3 values, but I'm not exactly sure what each of them means)... so now my phone has a much larger buffer zone built into it so that it doesn't ever run out of memory. You can set that buffer zone as high as 250 mb's, but I honestly don't think you would see much difference between that and 100... unused memory is simply that, unused.

I checked my phone's free memory through Titanium Back-Up 3 times today and each time it was over 100 mb's...... Super sweet!!!!

With AutoKiller, do you have to "exclude" apps that you don't want killed? Or does it work like Android itself to know which apps shouldn't be terminated? I'm a little surprised Android doesn't have a higher memory threshold for terminating apps if it affects the performance like that, especially with Froyo.

 

[eraursls1984]

With AutoKiller, do you have to "exclude" apps that you don't want killed? Or does it work like Android itself to know which apps shouldn't be terminated? I'm a little surprised Android doesn't have a higher memory threshold for terminating apps if it affects the performance like that, especially with Froyo.

It just helps you adjust the stock Android to change the thresholds, not a different application

 

[crboone]

I guess I have to disagree. The open platform was designed to allow techies to develop cheap software applications and for companies like Motorola to adopt it into their products. I cannot accept for one second that Google developed this as a science fair experiment but instead, had the volume utilization in mind from the beginning. Google isn't some small, 2nd rate tech company, it makes no sense for them to invest in something that doesn't have the potential for profound impact on the market.

The other point you've missed here is, I don't blame Google and Android. IMHO, the responsibility here lays with Motorola and Verizon. They are the ones pushing the product to the market for mass consumption. The Android OS is simply the foundation for them to overlay their own software/firmware. Now if they made a bad choice with the Android OS, shame on them.

I believe Moto and Verizon succumbed to the pressure and pushed this release out to market a couple of weeks to a month before the final bugs were rung out. I don't disagree that for many people, this release is working near perfect. The problem I have is there are far too many people, IMHO, that are having some fairly serious problems with it. Due to their impatience, incompetence or whatever you wish to call it, they are beta testing their freaking software with their Customers. And this is just wrong.

Now someone made a comment about my handle being funny. I had to laugh at that a bit. I came from an iPhone which I loved for its simplicity. I absolutely hated the AT&T network, they should be sued for billions for their blatant incompetence and horrible service. I went from Verizon to AT&T and frankly had forgotten just how much better the Verizon network is. I happen to think as simply a device for making phone calls, the DroidX is the best phone BY FAR I've ever used. The signal strength, call quality, etc. is frankly phenomenal. I dropped more calls in some days with AT&T than I have in the two months I've had the DroidX.

So I am a fan, a huge fan! But I'm also frustrated with some of the problems. I get more frustrated when the koolaid drinkers want to gloss over the problems and seemingly brush them away as non existent and of zero importance. And by the way, I expect and could accept some "bugs" but it just seems like there are far too many. And very important functions, such as cut and paste, are still non existent or simply suck.

With all that said, you'd have to pry my DroidX out of my dead fingers before you could take it away and give me the iPhone/AT&T combo back. I still reserve the right however, to bitch about the shortcomings and bugs.

I initially posted in the thread for those who haven't experienced issues with the OTA 2.2 upgrade. But now I have had a few issues, some of them a bit frustrating. That said, I wouldn't say the phone has been "ruined" by 2.2. Sure, there are some bugs that I really, really don't like. But overall it doesn't ruin the phone.

It's ironic that many installed the Froyo leak to have it as soon as possible, and there were many wondering when Froyo would finally be released OTA. Moto and Verizon had a timeline that they were trying to meet and knew they had a waiting crowd -- so of course there are still some bugs remaining now that it's been released. And even had they worked on it longer, it wouldn't have resolved all the bugs because you can't possibly find them all until people start using it. And then, I also believe it just takes time for some users (like me) to stabilize our environment after an upgrade. It's tough to find the perfect balance in all of this. But saying 2.2 has ruined the phone is a bit strong IMO -- it's still an improvement, bugs and all.