At this point, shouldn’t we just start to assume that Motorola has moved on from Milestone users and is instead focusing on new devices with newer versions of Android? The phone is the exact same device as the original Droid who is now running 2.2.1, yet the carrier partners can’t figure out a way to get even 2.2 running on it? Are they struggling with how pieces of bloatware to include? There shouldn’t be a hold up. I apologize for the rant, but this is one of the top selling devices of all time and there are thousands of users in dozens of countries that are stuck on an OS that is about to be 2 stages behind. Unacceptable.
Via: Motorola Europe
Poor Motorola Milestone users. The original Droid has been on Android 2.2 for months now, yet Moto continues to test it again and again for its worldly brother. It’s the exact same hardware as the U.S. version which is running Froyo flawlessly…what’s the hold up? Well, they posted an update to their Facebook page yesterday that has as you can imagine, left Milestone owners even more frustrated than before.
Testing seems to be done, but now it’ll be up to operators and retail partners to decide if Froyo is good enough. And I’m speechless. So we’re another 6 months out then?
Via: Motorola Europe
Anyone feel like tinkering around with the Droid X Android 2.2 source code? You can grab it right now since Motorola just released it to the public. Who knows exactly what this means for our rooting/hacking crowd, but maybe it’ll help in the efforts to permanently unlock this device. OK, that’s probably unlikely, but feel free to poke around in the code anyway.
Samsung announced today that their Galaxy S lineup of phones is starting to see Android 2.2 in the “Nordic” region of the world, but should filter out to the states by the end of the year. OK, it doesn’t even say “end of the year” it says “gradually.” Quite the timeline right? At least it’s happening!
One interesting thing to note is the point made in their press release about Froyo featuring “Google Maps with Navigation.” The release specifically mentions our favorite navigation app as one of the key features, but as you all know, the Fascinate (review) comes packed full of Bing. Any chance this sneaks onto the Verizon version without that other search engine suite? Unlikely. (more…)
The Motorola Forums manager has posted a list of pretty well-known issues that people are running into after they have installed Android 2.2 on their Droid X. The list isn’t huge, but some of the problems have frustrated many of you since day one on Froyo. They won’t release a timeframe for when these will be fixed, so try your best to be patient. Here they are…
Stuck on Moto logo after reboot – this was tough on a few owners. Very sorry about that. A fix has been developed for this and should eliminate the problem. It will be distributed in a future software release. If you are still experiencing this issue, click here.
Random rebooting – while there always seem to be new conditions that can cause an electronic device to panic, we do have improvements coming that address and eliminate identified panic states. They will be distributed in a future software release.
WiFi connection and stability – improvements in WiFi have been developed, to address several problem areas. They will be distributed in a future software release.
Battery Manager “force close” errors – under some circumstances, pressing the battery icon under Menu > Settings > Battery Manager results in a forced close error. A fix has been developed for this and should eliminate the problem. It will be distributed in a future software release.
Media won’t play – includes “sorry the player does not support this type of audio file,” custom ringtone stop working, video won’t play, etc., until after a reboot. We believe we have identified the cause of these errors. A fix has been developed for this and should eliminate the problem. It will be distributed in a future software release.
Music files cutting off the final four seconds or so – a solution has been developed. It will be distributed in a future software release.
Put me into the “random rebooting” category. Anyone else experiencing any of these?
Via: Motorola Forums
Android 2.2 for the Motorola Milestone has been quite the hot topic over the last few months. Some countries were left out entirely when it was announced, only to be included after owner outrage, but now with the timeline semi-locked down Moto is ready to start testing. The European Milestone is up first for user trials…
Hello. From next week we start user trials of the European Milestone upgrade to Froyo. Once these are complete, we will know what further work is required to
optimise, before going into final testing and approval stage. As previously we plan to start rolling the update at the end of this year, but wanted to keep you updated. Thanks
Looks like Moto is setting its sights on that Q1 2011 deadline. And how about this super early progress report? You’ve got to love that.
Source: Motorola Europe Facebook
One of our readers from Israel just sent in the screenshots above which show his Motorola Milestone running Android 2.1, but with a market that allows apps to be auto-updated just like 2.2. He received some sort of an update to his market within the last couple of days which happened essentially at the same time that the Android team announced support of paid apps to a new batch of countries (including Israel of course). Does this mean that all Milestones in new paid app countries will have this wonderful Froyo option? Let’s hope so. I can’t even imagine life without it.
There is a known text messaging issue with the Droid X running official Android 2.2 that Motorola is apparently aware of and already working on. According to their forums manager, their dev team has realized that an actual software upgrade is the only way to fix the problem.
Most right now are reporting that the issue has to do with text messages appearing out of order, but from my early experience with the leaked 2.2 and after talking with one of our readers, the problem is actually in the date and time settings of the phone. Messages aren’t appearing out of order, but are showing with a 4 hour time difference to when you actually received the message.
What’s funny about this issue, is I ran into so long ago and was unable to find a fix. At the time, I had a pretty good idea that the OS was to blame, but figured it was a big enough problem that it would have been ironed out in the official version. Apparently I was wrong and should have made a bigger deal out of it.
It should be noted that the problem is found in the native text app, Chomp and Handcent so there is really no work around at this time.
Anyone experiencing this issue?
Source: Motorola Forums