<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Should Google De-Frag Android, Get All Phones on 2.1?</title>
	<atom:link href="http://gigaom.com/mobile/android-21-phones/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/mobile/android-21-phones/</link>
	<description></description>
	<lastBuildDate>Sun, 27 May 2012 10:16:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dave</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434439</link>
		<dc:creator><![CDATA[Dave]]></dc:creator>
		<pubDate>Tue, 02 Mar 2010 09:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434439</guid>
		<description><![CDATA[&lt;p&gt;Seriously.  Make sure you know what you&#039;re talking about before you make a comment.  That video isn&#039;t a true build and the phone runs damn slow.&lt;/p&gt;

&lt;p&gt;You can&#039;t blame everything on the manufacturers.  There&#039;s a big issue here in that manufactures need to differentiate their products from their competitors.  Otherwise, they might as well just be OEMs (and be paid like one).  Google chose a strategy to grab as much market share as quickly as possible even if they knew it would lead to fragmentation.  For that, they are to blame.&lt;/p&gt;

&lt;p&gt;For manufacturers, they need to make a choice of if it&#039;s worth the time and resources to release a compatible update that doesn&#039;t hurt the user experience.  My guess is that they won&#039;t put it high on their priorities because Android isn&#039;t their platform and they aren&#039;t guaranteed high volumes for producing an Android phone.  Remember, outside of the Nexus One, every Android phone on the market is selling below manufacturing costs and depending on carrier subsidies to make a profit.  (I would also bet the they aren&#039;t getting the high subsidies that the iPhone commands).&lt;/p&gt;

&lt;p&gt;But fragmentation isn&#039;t the biggest problem I see for Android.  That would be how quickly Android be able to keep up with the evolution of the iPhone.  iPhone 4.0 promises to be to a major upgrade and with Apple&#039;s integrated hardware and software structure, they will be able to push new product features out much faster than Android.  Any innovations will surely be accompanied with a slew of patents that Android will have to figure out how to work around.  Of course that&#039;s just speculation.  We&#039;ll see in June.&lt;/p&gt;

&lt;p&gt;Lastly.  For tech heads, the idea of jail breaking your phone to get updates may seem easy, but for a mass market appeal, these issues must be handled for a user.  Until this issue is solved, I don&#039;t see Android gaining mass adoption.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Seriously.  Make sure you know what you&#8217;re talking about before you make a comment.  That video isn&#8217;t a true build and the phone runs damn slow.</p>
<p>You can&#8217;t blame everything on the manufacturers.  There&#8217;s a big issue here in that manufactures need to differentiate their products from their competitors.  Otherwise, they might as well just be OEMs (and be paid like one).  Google chose a strategy to grab as much market share as quickly as possible even if they knew it would lead to fragmentation.  For that, they are to blame.</p>
<p>For manufacturers, they need to make a choice of if it&#8217;s worth the time and resources to release a compatible update that doesn&#8217;t hurt the user experience.  My guess is that they won&#8217;t put it high on their priorities because Android isn&#8217;t their platform and they aren&#8217;t guaranteed high volumes for producing an Android phone.  Remember, outside of the Nexus One, every Android phone on the market is selling below manufacturing costs and depending on carrier subsidies to make a profit.  (I would also bet the they aren&#8217;t getting the high subsidies that the iPhone commands).</p>
<p>But fragmentation isn&#8217;t the biggest problem I see for Android.  That would be how quickly Android be able to keep up with the evolution of the iPhone.  iPhone 4.0 promises to be to a major upgrade and with Apple&#8217;s integrated hardware and software structure, they will be able to push new product features out much faster than Android.  Any innovations will surely be accompanied with a slew of patents that Android will have to figure out how to work around.  Of course that&#8217;s just speculation.  We&#8217;ll see in June.</p>
<p>Lastly.  For tech heads, the idea of jail breaking your phone to get updates may seem easy, but for a mass market appeal, these issues must be handled for a user.  Until this issue is solved, I don&#8217;t see Android gaining mass adoption.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434438</link>
		<dc:creator><![CDATA[JB]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 20:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434438</guid>
		<description><![CDATA[&lt;p&gt;Fragmentation is inevitable.  But you don&#039;t let it run loose, you try to keep it under control.  Of course Google owns this with whatever strategy they picked.  What did Google do, a mix of Apple innovation and Microsoft model?  Microsoft model had issues (I hated Microsoft phones).  You will still find v3.x phones all the way to v6.x phones in the market today. Lack of consolidation is an issue that we fight everywhere all the time.  Put controls in place to stop the proliferation.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Fragmentation is inevitable.  But you don&#8217;t let it run loose, you try to keep it under control.  Of course Google owns this with whatever strategy they picked.  What did Google do, a mix of Apple innovation and Microsoft model?  Microsoft model had issues (I hated Microsoft phones).  You will still find v3.x phones all the way to v6.x phones in the market today. Lack of consolidation is an issue that we fight everywhere all the time.  Put controls in place to stop the proliferation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ratnok</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434437</link>
		<dc:creator><![CDATA[Ratnok]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 16:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434437</guid>
		<description><![CDATA[&lt;p&gt;I&#039;ll make it simple. YES. 2.1 for all devices will make all current Android owners happy, as well as most developers happy.&lt;/p&gt;

&lt;p&gt;Carriers may be irritated at having to OTA or answer support questions, but who cares??? HTC already has Sense optimized for 2.1, so now Motorola (Blur), Sony (Xperia series) and Samsung (Behold II) have to get off their butts and get their custom builds ready as well. They never should have messed with Android in the first place. They should have differentiated with what they were good at - HARDWARE, and left the OS to Google. If they wanted to add some of their custom crap, make an app and preload it or have it available on the Android Market.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ll make it simple. YES. 2.1 for all devices will make all current Android owners happy, as well as most developers happy.</p>
<p>Carriers may be irritated at having to OTA or answer support questions, but who cares??? HTC already has Sense optimized for 2.1, so now Motorola (Blur), Sony (Xperia series) and Samsung (Behold II) have to get off their butts and get their custom builds ready as well. They never should have messed with Android in the first place. They should have differentiated with what they were good at &#8211; HARDWARE, and left the OS to Google. If they wanted to add some of their custom crap, make an app and preload it or have it available on the Android Market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virtuous</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434436</link>
		<dc:creator><![CDATA[Virtuous]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 02:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434436</guid>
		<description><![CDATA[&lt;p&gt;With the carriers involved this process will take several months.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>With the carriers involved this process will take several months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oliver</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434435</link>
		<dc:creator><![CDATA[oliver]]></dc:creator>
		<pubDate>Sun, 28 Feb 2010 17:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434435</guid>
		<description><![CDATA[&lt;p&gt;I guess following your logic my iPhone isn&#039;t really running iPhone OS 3.x because the OS upgrade didn&#039;t give it features like compass and video camera (yeah, it&#039;s jb&#039;en, so a 3rd party hack fixed that).&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>I guess following your logic my iPhone isn&#8217;t really running iPhone OS 3.x because the OS upgrade didn&#8217;t give it features like compass and video camera (yeah, it&#8217;s jb&#8217;en, so a 3rd party hack fixed that).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Harper</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434434</link>
		<dc:creator><![CDATA[Tim Harper]]></dc:creator>
		<pubDate>Sun, 28 Feb 2010 15:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434434</guid>
		<description><![CDATA[&lt;p&gt;fragmentation? Does MacOS X Snow Leopard run on non-Intel computers?&lt;/p&gt;

&lt;p&gt;If you have an out of date computer running MacOS X (pre-Tiger), it&#039;s practically useless. You can&#039;t hardly download any versions of applications that run on your computer.&lt;/p&gt;

&lt;p&gt;On the other hand, Windows 2000 is STILL able to run many modern applications.&lt;/p&gt;

&lt;p&gt;I&#039;m not saying Windows 2000 is my operating system of choice (I use MacOS X), but I think the fragmentation issue is a non-issue.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>fragmentation? Does MacOS X Snow Leopard run on non-Intel computers?</p>
<p>If you have an out of date computer running MacOS X (pre-Tiger), it&#8217;s practically useless. You can&#8217;t hardly download any versions of applications that run on your computer.</p>
<p>On the other hand, Windows 2000 is STILL able to run many modern applications.</p>
<p>I&#8217;m not saying Windows 2000 is my operating system of choice (I use MacOS X), but I think the fragmentation issue is a non-issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dkpa</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434433</link>
		<dc:creator><![CDATA[dkpa]]></dc:creator>
		<pubDate>Sun, 28 Feb 2010 10:38:35 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434433</guid>
		<description><![CDATA[&lt;p&gt;Well, Android is backward compatible, it was never said it would be forward compatible!... So phone have good processors others have not so good ones and it&#039;s perfectly acceptable that some phones aren&#039;t capable to upgrade to a newer version of Android if it requires a more advanced hardware configuration.
The same applies to applications like Google Earth that push devices to their limits and because of that require advanced hardware features like a snappy processor and good graphics and Android v2.1 or better in this case.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Well, Android is backward compatible, it was never said it would be forward compatible!&#8230; So phone have good processors others have not so good ones and it&#8217;s perfectly acceptable that some phones aren&#8217;t capable to upgrade to a newer version of Android if it requires a more advanced hardware configuration.<br />
The same applies to applications like Google Earth that push devices to their limits and because of that require advanced hardware features like a snappy processor and good graphics and Android v2.1 or better in this case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Grace Augustine</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434432</link>
		<dc:creator><![CDATA[Dr. Grace Augustine]]></dc:creator>
		<pubDate>Sat, 27 Feb 2010 21:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434432</guid>
		<description><![CDATA[&lt;p&gt;I say motor ahead. Since hardware advances are accelerating at warp speed you cannot downgrade your latest software to play with the common denominators as this WILL WEAKEN THE OS and we do not want a watered down phone OS.&lt;/p&gt;

&lt;p&gt;Phone customers almost always upgrade their phones when their current plan expires anyway. So what really needs to happen is all the carriers need to adopt ONE YEAR data plans that will sync with the hardware upgrades mo betta.&lt;/p&gt;

&lt;p&gt;I would not waste any resources on the bottom feeders. Remember most people that stick with old phone OS tend to stay well behind the curve anyhow so you will never bring this type of slag to the forefront of the pack.&lt;/p&gt;

&lt;p&gt;Android needs to stay in pack leader mode. The weaker dogs need to be brushed aside. These are &quot;smart phones&quot; not Nokia junk feature phone boys.&lt;/p&gt;

&lt;p&gt;A 6 month hardware &amp; software upgrade path needs to be firmly embedding into the cerebral cortex of the buying public. If your cranium is too dense to accommodate this rapid update cycle then you are not the type of purchaser The Google needs to fatten their R&amp;D budget to keep ahead in the mobile space race.&lt;/p&gt;

&lt;p&gt;DO NOT WASTE TIME AND RESOURCES DE-FRAGGING FOR OLD HARDWARE.&lt;/p&gt;

&lt;p&gt;&#039;NUFF SAID before my head explodes.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>I say motor ahead. Since hardware advances are accelerating at warp speed you cannot downgrade your latest software to play with the common denominators as this WILL WEAKEN THE OS and we do not want a watered down phone OS.</p>
<p>Phone customers almost always upgrade their phones when their current plan expires anyway. So what really needs to happen is all the carriers need to adopt ONE YEAR data plans that will sync with the hardware upgrades mo betta.</p>
<p>I would not waste any resources on the bottom feeders. Remember most people that stick with old phone OS tend to stay well behind the curve anyhow so you will never bring this type of slag to the forefront of the pack.</p>
<p>Android needs to stay in pack leader mode. The weaker dogs need to be brushed aside. These are &#8220;smart phones&#8221; not Nokia junk feature phone boys.</p>
<p>A 6 month hardware &amp; software upgrade path needs to be firmly embedding into the cerebral cortex of the buying public. If your cranium is too dense to accommodate this rapid update cycle then you are not the type of purchaser The Google needs to fatten their R&amp;D budget to keep ahead in the mobile space race.</p>
<p>DO NOT WASTE TIME AND RESOURCES DE-FRAGGING FOR OLD HARDWARE.</p>
<p>&#8216;NUFF SAID before my head explodes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doctor-don</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434431</link>
		<dc:creator><![CDATA[doctor-don]]></dc:creator>
		<pubDate>Sat, 27 Feb 2010 20:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434431</guid>
		<description><![CDATA[&lt;p&gt;Features available for my 1.6 work. Will they work under 2.1? I&#039;m willing to take the chance and look forward to it.&lt;/p&gt;

&lt;p&gt;And, I&#039;ll be the one to say it - please proofread what you write.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Features available for my 1.6 work. Will they work under 2.1? I&#8217;m willing to take the chance and look forward to it.</p>
<p>And, I&#8217;ll be the one to say it &#8211; please proofread what you write.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://gigaom.com/mobile/android-21-phones/#comment-434430</link>
		<dc:creator><![CDATA[tim]]></dc:creator>
		<pubDate>Sat, 27 Feb 2010 20:00:35 +0000</pubDate>
		<guid isPermaLink="false">http://jkontherun.com/?p=58434#comment-434430</guid>
		<description><![CDATA[&lt;p&gt;I also think that Google needs to slow down. In stead of trying to dazzle analyst at upcomming trade shows, they should think about their existing customers. They remind me of Microsoft who kept making Windows larger and larger so that Intel could have greater margins. I thought that Android was suppose to be slim, trim and powerful and would fit on any device. Whether it be a TV remote control or a Mainframe but as it is going the TV remoter will have to rum 1.5 while the Mainframe runs 6.5. I wish Google would instate Device Advocates who would argue for their device. As a G1 customer who wanted to see my device soar with the eagles, well, I am resigned to believe that that dream was in my head alone and that there is no device advocates at Google. I belived in Google and their montra. Now it turns out that they are just another Microsoft. Ans as far as the rumers go, 2.1 can&#039;t fit on a G1. CyanoginMod runs 1.5 with a 2.1 SDK. That&#039;s not a true 2.1 build.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>I also think that Google needs to slow down. In stead of trying to dazzle analyst at upcomming trade shows, they should think about their existing customers. They remind me of Microsoft who kept making Windows larger and larger so that Intel could have greater margins. I thought that Android was suppose to be slim, trim and powerful and would fit on any device. Whether it be a TV remote control or a Mainframe but as it is going the TV remoter will have to rum 1.5 while the Mainframe runs 6.5. I wish Google would instate Device Advocates who would argue for their device. As a G1 customer who wanted to see my device soar with the eagles, well, I am resigned to believe that that dream was in my head alone and that there is no device advocates at Google. I belived in Google and their montra. Now it turns out that they are just another Microsoft. Ans as far as the rumers go, 2.1 can&#8217;t fit on a G1. CyanoginMod runs 1.5 with a 2.1 SDK. That&#8217;s not a true 2.1 build.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

