They're going to fix it by doing what they should've done to begin with. Take the stupid firmware out of debug mode.
Do the backups need to take so long? No. It's backing up entire apps when it should only be backing up user data from those apps.
Do installs need to take so long? No. It's recreating an application table every time an app is installed. Why? When I install an app on my Mac it doesn't need to recreate the list of every app that's on the machine.
Does it need to open up a connection to MobileMe every time I open my contacts? No. Those changes should be made in the background.
Does it need to use up so much processing time for the Push client? No. The picture Apple showed at the WWDC made me laugh as they showed a Windows Mobile device with processes running in the background. How do you think the device knows when it receives a push request? What do you think is eating up some of that CPU time?
In short, 2.0 basically was the release candidate of the software. 2.1 turned some stuff off, but clearly this thing is very much in "debug" mode.
Do the backups need to take so long? No. It's backing up entire apps when it should only be backing up user data from those apps.
Do installs need to take so long? No. It's recreating an application table every time an app is installed. Why? When I install an app on my Mac it doesn't need to recreate the list of every app that's on the machine.
Does it need to open up a connection to MobileMe every time I open my contacts? No. Those changes should be made in the background.
Does it need to use up so much processing time for the Push client? No. The picture Apple showed at the WWDC made me laugh as they showed a Windows Mobile device with processes running in the background. How do you think the device knows when it receives a push request? What do you think is eating up some of that CPU time?
In short, 2.0 basically was the release candidate of the software. 2.1 turned some stuff off, but clearly this thing is very much in "debug" mode.