Just updated to Froyo.

[Ni Dieu Ni Maitre]

Not having any troubles. It's working as smoothly as 2.1 was.

But my question is...what's the difference? I don't really notice any changes other than cosmetic ones.

Either way, I've had this thing since Monday and I love it.

Google Shopper seems to have a less effective scanner than ShopSavvy does. Has anyone else noticed this?

 

[scary alien]

Lol! I agree...didn't really notice that much difference, except for some new menu choices, etc. (oh, and Flash player capability--which I actually have not yet used or tested (which I was really excited about months ago, but now, not so much)).

The OTA update kind of snuck up on me...mine prompted me at midnight of the second day and I "snoozed" it. Then, I forgot all about it until after lunch the next day and I saw that it had auto-installed the OTA and rebooted, etc.

No biggie...haven't noticed too much difference. Still works as great as it did before.

Oh, and I did root it later that week...grabbed drocap2 and wi-fi tether just to play.

 

[quickaudi]

you're one of the few that has had zero issues - trust me, they're out there

 

[bigbadwulff]

I love the Froyo dispensing now. I carry cones with me wherever I go...

 

[Deleted User]

you're one of the few that has had zero issues - trust me, they're out there

No. He's one of the majority who have had zero issues.

 

[chippy]

you're one of the few that has had zero issues - trust me, they're out there

I would disagree with the first part of the sentence.

 

[Outlaw71]

you're one of the few that has had zero issues - trust me, they're out there

I'd say it's just as hard to say he's one of the few who didn't than it would be to say that I was one of the few who did. I haven't seen any market research pie charts on the update.

I had problems, as did quite a few others on this board... but don't let a relatively small community like this get you thinking that just about everyone had a problem doing the update because there are thousands of Droid X's out there (what was the first release, something like 100,000... and those sold out within the first day?), and how many users have come on here to say they had a problem... a dozen or two? Even if 100 people came on here and complained, that would still only be one tenth of one percent of the original order... that's not very high.

So it's hard to speculate because for starters, people with problems are much more likely to go somewhere and complain about that problem than someone who did the update and it went off without a hitch would be to get online and say, "hey everyone I just wanted to say my update went smoothly". So you get an unbalanced selection of feedback on a forum such as this. The other thing is it's a very, very low percentage of Droid X owners who come onto any of these sites at all period. So basically it's too hard to make very accurate predictions on what is going on with the masses.

Although I have to say that it occurs to me that if the vast majority of people who got the update had as many issue's as we've read about here on Phandroid, then Verizon would be completely swamped with customers wanting to return their phones, or at least get the issue's fixed. Because most casual owners don't have the time to sit down at their computer, get online, riffle through different forums until they find people with similar issues that they are experiencing, and then troubleshoot their phone until they get those issues cleared up.

The majority of people will just walk into a Verizon store, throw their phone at the agent and say, "this thing is a piece of shit"! So while it is completely possible that the majority of Droid X's had issues with the update, it is just as possible that the majority of them didn't.

We just don't know.

 

[Deleted User]

The majority of people will just walk into a Verizon store, throw their phone at the agent and say, "this thing is a piece of shit"! So while it is completely possible that the majority of Droid X's had issues with the update, it is just as possible that the majority of them didn't.

We just don't know.

No, we know. Or at least, we have a pretty good guess.

If a majority of the phones suffered from problems, two things would have happened:

a) the update would have been pulled very quickly, and

b) stock of the DX would have vanished overnight and backorders would have gone through the roof replacing them

It's pretty likely there would also have been substantial fallout in the news media over it since it would have also resulted in support call centers being overwhelmed. I agree that we don't know the full scope of issues, but it wasn't even close to a substantial percentage. The first run of phones was 300k and it sold out in the first week. By this point, they have to be at well over half a million if not closer to a million phones sold. Moto and Verizon would have been crushed with returns if any major portion of those had serious issues.

 

[nj02vette]

you're one of the many that has had zero issues - trust me, there's a very few who have had issues

fixt

 

[nj02vette]

No, we know. Or at least, we have a pretty good guess.

If a majority of the phones suffered from problems, two things would have happened:

a) the update would have been pulled very quickly, and

b) stock of the DX would have vanished overnight and backorders would have gone through the roof replacing them

It's pretty likely there would also have been substantial fallout in the news media over it since it would have also resulted in support call centers being overwhelmed. I agree that we don't know the full scope of issues, but it wasn't even close to a substantial percentage. The first run of phones was 300k and it sold out in the first week. By this point, they have to be at well over half a million if not closer to a million phones sold. Moto and Verizon would have been crushed with returns if any major portion of those had serious issues.

Spot on analysis.

Even on the moto boards, there are only a very few verifiable bugs that are being tracked, like time stamp and battery force close. Others either can't be easily duplicated or are the result of bad hardware.

 

[quickaudi]

No. He's one of the majority who have had zero issues.

yeah, I guess all these bug threads on here are just BS

good call

 

[quickaudi]

No, we know. Or at least, we have a pretty good guess.

If a majority of the phones suffered from problems, two things would have happened:

a) the update would have been pulled very quickly, and

b) stock of the DX would have vanished overnight and backorders would have gone through the roof replacing them

It's pretty likely there would also have been substantial fallout in the news media over it since it would have also resulted in support call centers being overwhelmed. I agree that we don't know the full scope of issues, but it wasn't even close to a substantial percentage. The first run of phones was 300k and it sold out in the first week. By this point, they have to be at well over half a million if not closer to a million phones sold. Moto and Verizon would have been crushed with returns if any major portion of those had serious issues.

you SERIOUSLY overestimate VZW. if you don't believe me, please reference the Storm 1 that still has a bunch of bugs that never got fixed through a hoard of updates that spanned over a year

in response to the a/b

a: if the issues are deemed "minor", they won't pull an update; most of the bugs are stupid ones that can be fixed with a phone restart, and we all know VZW techs will do that first and declare a phone "fixed"

b: considering several of them were sent back before the update (I sent one back for a stuck pixel, non camera related), they have plenty of rebuilds to hand out, and on top of that, some X users could have jumped ship instead of getting another X. there are plenty of D2s available.

 

[quickaudi]

I had problems, as did quite a few others on this board... but don't let a relatively small community like this get you thinking that just about everyone had a problem doing the update because there are thousands of Droid X's out there (what was the first release, something like 100,000... and those sold out within the first day?), and how many users have come on here to say they had a problem... a dozen or two? Even if 100 people came on here and complained, that would still only be one tenth of one percent of the original order... that's not very high.

So, I'm not allowed to use this site as a reference, but you're allowed to make broad, unsubstantiated claims about a software release based on random numbers you pull out of the air?

Logic fail.

 

[quickaudi]

Spot on analysis.

Even on the moto boards, there are only a very few verifiable bugs that are being tracked, like time stamp and battery force close. Others either can't be easily duplicated or are the result of bad hardware.

case in point: I'm not on the Moto boards, and I'm sure they've missed some. it happens.

 

[Ni Dieu Ni Maitre]

Thread = hijacked.

 

[Outlaw71]

I have developed my own philosophy for why updates can hang up like mine did. I believe that Google thoroughly tests a new OS out before they release it (remember how long we had to wait for our froyo?) to make sure it plays nice with their old version. But what they don't do, and what they aren't responsible to do even if it were possible (which it isn't) is test their new OS against any issue's it might have with the apps that are available on the market.

That isn't their job, their job is to supply the OS, which the devs then take and create apps that can run on it without any instability issues (... ok so they aren't exactly batting a thousand in that respect, but they have a decent enough record). But they have no way of knowing how exactly their apps will react to the new OS. Many times they have to update their apps directly after an OS upgrade. So people like me who had their phones loaded down with apps (I had right at 100 when I did the OTA update) head into the deal with a lot of if's circling around our phones.

When I did mine I experienced quite severe lag at times, quite a few FC's and even a couple complete freeze up's before I started troubleshooting. It wasn't until I did a factory reset AND formatted my SD card that everyone played nice and froyo started acting normal. So when 3.0 rolls around I for one will be making a fresh Titanium Back-Up, as well as updating my AppBrain account, then I'll do a factory reset just before the update... perform the update... and then do another factory reset afterwards before I add back all my apps again. We'll see if I experience a smoother transition doing the update on a clean 2.2.

And you see I'd dare to estimate that for the vast majority of X'ers out there, a dozen or 2 apps is probably all they have on their phones when the update got pushed out. Peeps on forums like this one tend to do a whole lot more experienting with the different apps than the average everyday customer. And without so many apps (or variables) on their phone, the lower the chance that something could go wrong.

But don't think I'm saying that 100 times out of every 100 attempts you update a clean 2.1 to 2.2 it will go off without a hitch... these are computers we're talking about after all. And computers just don't always do as they're told to do, period.

 

[Fabolous]

The majority of the posters on these forums are Android enthusiasts, or people seeking help with some device issues (or both).

We're not a good representation of the general user base of these devices. Taking that into account, the large volume of 2.2 issue threads here does not mean that the majority of Droid X users are actually having these issues!

They're happily going on with their lives, most likely not even aware that this (and other similar) forums exist!

 

[Outlaw71]

So, I'm not allowed to use this site as a reference, but you're allowed to make broad, unsubstantiated claims about a software release based on random numbers you pull out of the air?

Logic fail.

Broad claim? I claimed that neither of us could accurately claim anything. Which is about as logical as it gets.

 

[Outlaw71]

And using this site as a reference to how many people have issue's with their phone's is like walking into a prison to survey how many guys have taken it in the butt. It's not going to be very accurate because places like these are for better or worse the complaints department.

It doesn't matter how well made a car a Volvo is, if you work it the complaints department at Volvo all you're going to hear all day long is how crappy Volvo's are.

 

[quickaudi]

And using this site as a reference to how many people have issue's with their phone's is like walking into a prison to survey how many guys have taken it in the butt. It's not going to be very accurate because places like these are for better or worse the complaints department.

It doesn't matter how well made a car a Volvo is, if you work it the complaints department at Volvo all you're going to hear all day long is how crappy Volvo's are.

Yeah, but volvos are crappy...

 

[quickaudi]

I have developed my own philosophy for why updates can hang up like mine did. I believe that Google thoroughly tests a new OS out before they release it (remember how long we had to wait for our froyo?) to make sure it plays nice with their old version. But what they don't do, and what they aren't responsible to do even if it were possible (which it isn't) is test their new OS against any issue's it might have with the apps that are available on the market.

That isn't their job, their job is to supply the OS, which the devs then take and create apps that can run on it without any instability issues (... ok so they aren't exactly batting a thousand in that respect, but they have a decent enough record). But they have no way of knowing how exactly their apps will react to the new OS. Many times they have to update their apps directly after an OS upgrade. So people like me who had their phones loaded down with apps (I had right at 100 when I did the OTA update) head into the deal with a lot of if's circling around our phones.

When I did mine I experienced quite severe lag at times, quite a few FC's and even a couple complete freeze up's before I started troubleshooting. It wasn't until I did a factory reset AND formatted my SD card that everyone played nice and froyo started acting normal. So when 3.0 rolls around I for one will be making a fresh Titanium Back-Up, as well as updating my AppBrain account, then I'll do a factory reset just before the update... perform the update... and then do another factory reset afterwards before I add back all my apps again. We'll see if I experience a smoother transition doing the update on a clean 2.2.

And you see I'd dare to estimate that for the vast majority of X'ers out there, a dozen or 2 apps is probably all they have on their phones when the update got pushed out. Peeps on forums like this one tend to do a whole lot more experienting with the different apps than the average everyday customer. And without so many apps (or variables) on their phone, the lower the chance that something could go wrong.

But don't think I'm saying that 100 times out of every 100 attempts you update a clean 2.1 to 2.2 it will go off without a hitch... these are computers we're talking about after all. And computers just don't always do as they're told to do, period.

Yeah, I cant prove it, but doing the factory reset helped me a lot

 

[quickaudi]

Not having any troubles. It's working as smoothly as 2.1 was.

But my question is...what's the difference? I don't really notice any changes other than cosmetic ones.

Either way, I've had this thing since Monday and I love it.

Google Shopper seems to have a less effective scanner than ShopSavvy does. Has anyone else noticed this?

there are a couple of threads on the changes on here already, fyi

 

[Outlaw71]

Yeah, but volvos are crappy...

Lol, ok you got me... I'm not going to put up a huge fight over that one!

 

[Ni Dieu Ni Maitre]

there are a couple of threads on the changes on here already, fyi

And there are a couple of threads on whether or not Froyo is buggy and the debate over whether or not we get a poor sampling of the average user on these forums and so on

Clearly my dumb ass can't find the threads you're talking about, however.

 

[quickaudi]

Clearly my dumb ass can't find the threads you're talking about, however.

http://androidforums.com/motorola-d...ave-you-noticed-after-updating-2-2-froyo.html

that's the one I was thinking of