Android News
Froyo Android 2.2 causing trouble with popular Android apps
May 24, 2010 | by Andrew Kameka
Firmware updates
For all the excitement of Froyo being unveiled at Google I/O and then delivered to Nexus One owners days later, it’s been an afterthought that Froyo is actually causing quite a few headaches where apps are concerned. As we saw when Android 1.5 (Cupcake) and Android 1.6 (Donut) were first introduced last year, certain apps have become spotty or downright unusable after the introduction of 2.2
Whether it’s the CoPilot Live navigation app, Rhapsody streaming music app, or Seesmic Twitter/Buzz client, several Twitter users are reporting that their must-have apps aren’t working since applying the update. The apps will likely be operational once developers are able to diagnose problems and release an update into the Android Market, but devs haven’t had much time to do that.
This episode of update-prompted app woes is a glaring reminder that Google is not giving developers enough time to test their apps on new versions of Android. Every time Google releases a new treat, the buffer between developers getting the SDK and consumers getting the update shrinks. The latest buffer lasted all of 48 hours. That just leads to frustrated devs receiving waves of complaints and support requests before they even get a chance to fire up the emulator and see what still works.
Google does a great job of getting new features to users, but the Android team needs to give developers a bit more time making sure their apps will be compatible with those features.
I've seen a couple of poor reviews like this one. I thought the Android was bomb proof!
At least devs will be able to see that the new app error notification system is working! haha
At some point, all of the blogs and users have to calm down. Google was rolling it out very slowly to N1 users. Someone found the direct link to upgrade and it has been passed around with excitement to all. A new software update requires testing as you state, short cutting this testing period by acting like a kid in a candy shop does not help matters. Those that facilitate circumventing this process are as responsible for failures just as much as Google. (http://androinica.com/2010/05/23/manual-froyo-update-available-plus-initial-impressions/) If you are not able to wait, then deal with the results and quit crying when your tummy aches from eating too much candy.
Agree with Mojo. Most people who have it updated manually. Not something that Google really pushed users to do. So how can we be complaining when we circumvented the slow release process.
personally, I don't think it should have been sent at all, including the OTA. even if it was just a few thousand people getting, 2 days after devs get the SDK is a little soon.
Well, as I understand it, the original OTA update was just supposed to be for the free N1s they gave out to the media at I/O rather than a GA. Google has yanked it from the servers now. But really, if you are grabbing updates and manually applying, you are going to be an early adopter type anyway and should be prepared for some issues.
App developers: Just get on the ball. Froyo opens more to the world. Quit complaining, the majority of 2.2 users are on the way so light that fire.
As usual, Google Copy Protection for Android applications is a part of the problem. Pure calendar, as copy protected app, is not visible with Froyo… This copy protection is really faulty. Google needs to improve it.
Surely patience is the key here. Grabbing updates and impleenting without the official release is always going to lead to tears. Patience is your friend.
The original OTA update was just supposed to be for the free N1s they gave out to the media at I/O rather than a GA
Early adopters must surely be prepared for problems right?….or they would wait until the second third version.