
<?phpxml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<channel>
<title>Haaze.com / dkavpnorket / All</title>
<link>http://www.haaze.com</link>
<description>Test Web 2.0 Content Management System</description>
<pubDate>Fri, 04 Mar 2011 08:10:35 +0000</pubDate>
<language>en</language>
<item>
<title><![CDATA[Motorola won't update Charm or Flipout beyond Android 2.1]]></title>
<link>http://www.haaze.com/story.php?title=motorola-wont-update-charm-or-flipout-beyond-android-2-1</link>
<comments>http://www.haaze.com/story.php?title=motorola-wont-update-charm-or-flipout-beyond-android-2-1</comments>
<pubDate>Fri, 04 Mar 2011 08:10:35 +0000</pubDate>
<dc:creator>dkavpnorket</dc:creator>
<category>Technology</category>
<guid>http://www.haaze.com/story.php?title=motorola-wont-update-charm-or-flipout-beyond-android-2-1</guid>
<description><![CDATA[As shown by this chart on Motorola's support page, the list of phones getting left behind with older versions of Android grows by two with the Charm and Flipout.(Credit:Motorola)Motorola has decided to pull back on plans to update its Charm (T-Mobile) and Flipout (AT&amp;T) handsets with Android 2.2 Froyo.Of course, that means that the smartphones, which were released with Android 2.1 back in the fall, will remain on Eclair indefinitely. The handsets join a growing list of Motorola phones being left behind on older versions of Android. Most recently, the company decided that the Cliq XT would stay on Android 1.5 and never see features such as Google Maps Navigation or live wallpapers. Looking at the list of devices represented on Motorola's support page (see above chart), it's apparent that the company doesn't intend to spend much time or development on older devices. Let's hope that new handsets such as the Atrix 4G or Droid X get more than one update.As to why these handsets aren't going to see much beyond Android 2.1 could be anyone's guess. Motorola talks of wanting to provide an &quot;optimal customer experience,&quot; but that may be interpreted many ways. Perhaps the problems stem from having to work with so many form factors and hardware configurations.On the other hand, the issues could stem from the Motoblur interface, which overlays Android. Perhaps Moto integrated the custom UI too heavily, which prevents it from acting quickly to roll out updates. Another likely scenario might be that these phones aren't selling as well as anticipated and that it would be a waste of time and resources to work on updates for such a limited quantity of devices. <br/><br/>0 Vote(s) ]]></description>
</item>

<item>
<title><![CDATA[Dialed In 163: Mobile World Congress recap (podcast)]]></title>
<link>http://www.haaze.com/story.php?title=dialed-in-163-mobile-world-congress-recap-podcast</link>
<comments>http://www.haaze.com/story.php?title=dialed-in-163-mobile-world-congress-recap-podcast</comments>
<pubDate>Wed, 23 Feb 2011 08:10:41 +0000</pubDate>
<dc:creator>dkavpnorket</dc:creator>
<category>Technology</category>
<guid>http://www.haaze.com/story.php?title=dialed-in-163-mobile-world-congress-recap-podcast</guid>
<description><![CDATA[Mobile World Congress 2011 is over, and the gang's back together once again, but before we say adios to MWC, we thought it'd be good to recap some of the highs and lows of the show. Plus, Nokia may have signed on with Microsoft andWindows Phone 7, but the Finnish handset manufacturer says it's still committed to Symbian. We discuss their future, as well as RIM's, and much more (hologram phones!) on this week's episode of Dialed In.<br/><br/>0 Vote(s) ]]></description>
</item>

</channel>
</rss>
