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.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!
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.