What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

SUPER UPSET about this 2.2 crap

Status
Not open for further replies.
LATE SUMMER. Exactly. Summer ends in a week!

Also, if you want to be a top dog in the smartphone world I would think you would do everything in your power to get the top software on your phone. If the Droid2 has it...the X should have had it weeks ago!
The Droid2 was built from the ground up with 2.2. DX development started sooner, and was version locked to 2.1 for development. 2.2 dev probably didn't start until after the device went gold. It's not as simple as slapping the AOSP onto any device, it requires specialized code, bug fixing, and a lot of testing. And bugs still make it through. Not to mention verizon's testing requirements, which are separate from, and on top of, motorola's.

Also I am NOT out of line at all with this post...>Think about this:
Even if 2.2 isn't out MOTO knows there is a volume issue. Why not push that fix without 2.2 to correct a known problem.

That would be like a car company saying we know where is something wrong with the CD players and speakers in our cars, but we will not fix them until the next time you get your oil changed. That is unacceptable!

You're forgetting about Verizon's role in this. Moto can't just push out an update whenever it feels like it. Verizon has to approve every individual software release that gets put on their network (officially anyway). They have their own process, and it's a nightmare from all accounts.

You're analogy is flawed. Changing out the CD player doesn't in some way fundamentally change the car in such a way that it would affect an oil change. Fixing the volume issue very well might. It's a part of the base OS (linux), and thus affects, albeit indirectly, all other aspects of the device. It makes more sense to wrap it up into a much larger project, so many steps can all be done at once. Including the Verizon approval process.
 
I don't think anybody thinks that they are holding it out on purpose. But you cannot be upset with people being upset(like myself) over the fact that every Android phone has this update except us. How come the Droid 2 can have this already installed on it but we have to wait for "bugs" to be fixed? Is the Droid 2 so special that it has no bugs? I thought these phones were basically the same? If so how come we here can't get the identical Froyo OS as they have? Just an observation.
 
Since for the droid 2 they could start the development with 2.2 they had time to fix any issues... though chances are that it shipped with known issues (or bugs they pretend are not there until noticed) just to get the phone on the market. To some extent slapping the same version onto the DX would work... but once you get down to the hardware control, since the phones have different hardware, you wouldnt get too far. Specific drivers have to be built in and tested.

As a developer I can only hope that the moto devs are talking with each other and helping each other out. If the droid 2 devs fixed the exchange issue, I would hope they are working with the DX devs to get it cleaned up. Sometimes that is a pie in the sky thought though.
 
I don't think anybody thinks that they are holding it out on purpose. But you cannot be upset with people being upset(like myself) over the fact that every Android phone has this update except us. How come the Droid 2 can have this already installed on it but we have to wait for "bugs" to be fixed? Is the Droid 2 so special that it has no bugs? I thought these phones were basically the same? If so how come we here can't get the identical Froyo OS as they have? Just an observation.

I think everyone is a little bit upset about it, I am too. But looking at a broader picture helps. Not all phones have 2.2 yet, look at the different Galaxy S phones. Hell, look at the numbers from Google themselves. As of September 1st, 41% of all devices are running 2.1, with only 28% running 2.2.

As I said, the Droid2 started development on 2.2. The DX started on 2.1. Moto has had much longer dev time with 2.2 on Droid2 than they have had so far with the DX. And they are far from the same hardware. They have the same SoC (CPU, GPU, system bus), but everything else is different. If anything, the Droid2 is more similar to the Droid1.
 
As I concur with the frustration maybe people need to sit back and look at the big picture and pass some blame on Google for some of this. Who in there right mind makes 3 going on 4 MAJOR OS ( 2.0 D1 release, 2.1 early 2010, 2.2 May 2010, and now word it 3.0 will be done around Nov 2010) changes in under a year. Come on already use your head. IMO they are just to lazy to fix current source code so they just push out a new release which recks havoc on the mfgs & carriers.

So to think the carriers and mfgs can keep up with getting updates done for all devices and make new ones all in the same time frame is just plain dumb IMO. To further add anyone in there right mind should know better that whatever a corp company tells us never happens when they say it does. Plus as mentioned and most people don't think about there is way more that goes into getting a quality build of the OS pushed out to the masses.

Bottom line is relax a bit the update is not that far down the road that it a given.
 
They're adding a Nike Swoosh to the Contact Menu so that you can call Michael Jordan but he keeps answering the phone and saying "wuddup bacon neck" and hanging up so they are working on a fix for it, likely calling Kobe Bryant with a Colorado number.
 
They're adding a Nike Swoosh to the Contact Menu so that you can call Michael Jordan but he keeps answering the phone and saying "wuddup bacon neck" and hanging up so they are working on a fix for it, likely calling Kobe Bryant with a Colorado number.


Now that was funny.

I just am disappointed that by the time we have 2.2 the 3.0 update could be rolling out to some phones. At this rate the X will not have 3.0 until 2012! :icon_eek:

(Thanks for checking out my blog. The Rusty Bucket is sweet. If you havn't been to Fat Heads though you have to try it! It is worth the drive.) dancedroid
 
LOL. He the OP is moaning about not having 2.2 OTA yet he won't root. Let me tell you something and I will be VERY clear about it. Stock Android 2.1, 2.2, etc.. is nice. Root your phone and throw on a custom image and your device will become brand new again. You will be able to do things that you couldn't before and didn't even think you could. Hell my Droid will last me a LONG time as it stands especially with the dev community it has. I can't wait to see what they cook up from the AOSP when Gingerbread comes out.

I can see it now... OC'd to 1 Ghz and Compcache enabled running a Gingerbread AOSP built ROM. Oh how sweet it is. The only way this phone gets replaced is when I can get a Cortex A9 based dual core with a QWERTY slider. That being said the phone is going to be rooted and ransacked on day one just like my Droid was so I can have the better than factory install goodness.
 
They're adding a Nike Swoosh to the Contact Menu so that you can call Michael Jordan but he keeps answering the phone and saying "wuddup bacon neck" and hanging up so they are working on a fix for it, likely calling Kobe Bryant with a Colorado number.


Now that was funny.

I just am disappointed that by the time we have 2.2 the 3.0 update could be rolling out to some phones. At this rate the X will not have 3.0 until 2012! :icon_eek:

(Thanks for checking out my blog. The Rusty Bucket is sweet. If you havn't been to Fat Heads though you have to try it! It is worth the drive.) dancedroid

Then we're good because we are all dying then anyway. Problem solved!
 
They're adding a Nike Swoosh to the Contact Menu so that you can call Michael Jordan but he keeps answering the phone and saying "wuddup bacon neck" and hanging up so they are working on a fix for it, likely calling Kobe Bryant with a Colorado number.


Now that was funny.

I just am disappointed that by the time we have 2.2 the 3.0 update could be rolling out to some phones. At this rate the X will not have 3.0 until 2012! :icon_eek:

(Thanks for checking out my blog. The Rusty Bucket is sweet. If you havn't been to Fat Heads though you have to try it! It is worth the drive.) dancedroid

Then we're good because we are all dying then anyway. Problem solved!

Not me. My Droid X came with an app so I don't die that year
 
As I concur with the frustration maybe people need to sit back and look at the big picture and pass some blame on Google for some of this. Who in there right mind makes 3 going on 4 MAJOR OS ( 2.0 D1 release, 2.1 early 2010, 2.2 May 2010, and now word it 3.0 will be done around Nov 2010) changes in under a year. Come on already use your head. IMO they are just to lazy to fix current source code so they just push out a new release which recks havoc on the mfgs & carriers....

You realize the android source base is constantly being updated with patches and fixes right? Where do you think those fancy build numbers come from? FRF50, FRF83, FRG01, and FRG22 are all 2.2 Froyo builds...
 
now that was funny.

I just am disappointed that by the time we have 2.2 the 3.0 update could be rolling out to some phones. At this rate the x will not have 3.0 until 2012! :icon_eek:

(thanks for checking out my blog. The rusty bucket is sweet. If you havn't been to fat heads though you have to try it! It is worth the drive.) dancedroid

then we're good because we are all dying then anyway. Problem solved!

not me. My droid x came with an app so i don't die that year

lolmg joo has teh ginjurbredz?!?!?!?!?!?!?!
 
Moral of the story...I want my 2.2.

I don't feel like rooting. My phone works great. With my luck it would somehow screw up.
 
Status
Not open for further replies.
Back
Top