<?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/"
		>
<channel>
	<title>Comments on: Android 5.0 Jelly Bean tipped for Q2 2012</title>
	<atom:link href="http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/</link>
	<description>Feeding Your Gadget and Tech Obsessions</description>
	<lastBuildDate>Mon, 14 May 2012 06:58:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: J.L. "J7" Gatewood StarrWulfe</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184742</link>
		<dc:creator>J.L. "J7" Gatewood StarrWulfe</dc:creator>
		<pubDate>Fri, 17 Feb 2012 11:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184742</guid>
		<description><![CDATA[I know, I&#039;ve seen it-- but I think it&#039;s high time Moto took a crack at it anyway.
Motorola&#039;s devices can be plain-jane, but my Atrix has survived far more abuse than it would get had it still been used in America. Here in Toyko, you live and die by your keitai (mobile phone). It&#039;s survived being dropped from a train platorm onto the trackbed twice without a scratch. That&#039;s a drop of about 8 feet or so onto concrete. Beer has been spilt on it once. It was left out in the rain once. Countless times it&#039;s been bumped, jammed, poked, and squashed due to the rigors of commuting on jam-packed trains...  And 10 months later, battery life is the same (better now since I&#039;ve rooted and use a custom ROM) GPS, and HSPA signals are strong, and the phone part is still a DAMN GOOD PHONE. Meanwhile my iPhone has had to be repaired 3 times due to treatment far lighter than this!! Also the webtop if remixed into ChromeOS, would be more compelling IMHO-- And I use the OG lapdock everyday in a work situation here.  It&#039;s nice for what I mostly do-- research writing and monitoring.]]></description>
		<content:encoded><![CDATA[<p>I know, I&#8217;ve seen it&#8211; but I think it&#8217;s high time Moto took a crack at it anyway.<br />
Motorola&#8217;s devices can be plain-jane, but my Atrix has survived far more abuse than it would get had it still been used in America. Here in Toyko, you live and die by your keitai (mobile phone). It&#8217;s survived being dropped from a train platorm onto the trackbed twice without a scratch. That&#8217;s a drop of about 8 feet or so onto concrete. Beer has been spilt on it once. It was left out in the rain once. Countless times it&#8217;s been bumped, jammed, poked, and squashed due to the rigors of commuting on jam-packed trains&#8230;  And 10 months later, battery life is the same (better now since I&#8217;ve rooted and use a custom ROM) GPS, and HSPA signals are strong, and the phone part is still a DAMN GOOD PHONE. Meanwhile my iPhone has had to be repaired 3 times due to treatment far lighter than this!! Also the webtop if remixed into ChromeOS, would be more compelling IMHO&#8211; And I use the OG lapdock everyday in a work situation here.  It&#8217;s nice for what I mostly do&#8211; research writing and monitoring.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: riteshk</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184696</link>
		<dc:creator>riteshk</dc:creator>
		<pubDate>Fri, 17 Feb 2012 08:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184696</guid>
		<description><![CDATA[Did you even understand what I said?]]></description>
		<content:encoded><![CDATA[<p>Did you even understand what I said?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: riteshk</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184697</link>
		<dc:creator>riteshk</dc:creator>
		<pubDate>Fri, 17 Feb 2012 08:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184697</guid>
		<description><![CDATA[Did you even understand what I said?]]></description>
		<content:encoded><![CDATA[<p>Did you even understand what I said?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gorgeousninja</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184626</link>
		<dc:creator>gorgeousninja</dc:creator>
		<pubDate>Fri, 17 Feb 2012 04:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184626</guid>
		<description><![CDATA[No, Google gained market share because they stole from Apple. They were then able to give away free to manufacturers in a desperate bid for marketshare. Gambling on the correct assumption that many people don&#039;t care enough about security or ethics.]]></description>
		<content:encoded><![CDATA[<p>No, Google gained market share because they stole from Apple. They were then able to give away free to manufacturers in a desperate bid for marketshare. Gambling on the correct assumption that many people don&#8217;t care enough about security or ethics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gorgeousninja</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184623</link>
		<dc:creator>gorgeousninja</dc:creator>
		<pubDate>Fri, 17 Feb 2012 04:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184623</guid>
		<description><![CDATA[Is Jelly Bean aimed at more than 1% of android customers this time?

Or are the googlies so used to being fleeced for endless new handsets that they&#039;re past caring?]]></description>
		<content:encoded><![CDATA[<p>Is Jelly Bean aimed at more than 1% of android customers this time?</p>
<p>Or are the googlies so used to being fleeced for endless new handsets that they&#8217;re past caring?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Dellinger</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184608</link>
		<dc:creator>Ken Dellinger</dc:creator>
		<pubDate>Fri, 17 Feb 2012 03:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184608</guid>
		<description><![CDATA[Ain&#039;t that some shit. If that&#039;s true and I get a Droid 4, Ice Cream Sandwich will be obsolete before I even get the long-awaited update. I hope the devs at newly Googled Motorola will just skip ICS and go straight to pure Jellybean for the update!]]></description>
		<content:encoded><![CDATA[<p>Ain&#8217;t that some shit. If that&#8217;s true and I get a Droid 4, Ice Cream Sandwich will be obsolete before I even get the long-awaited update. I hope the devs at newly Googled Motorola will just skip ICS and go straight to pure Jellybean for the update!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: In Games Mq</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184579</link>
		<dc:creator>In Games Mq</dc:creator>
		<pubDate>Fri, 17 Feb 2012 01:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184579</guid>
		<description><![CDATA[I dont knbow why... but i would see ASUS  marrie Google .. Because I use a transformer and somehow i see asus... more like a google manufacture.. Perhaps because i have a transformer hhehe
And Asus usually is not so binded to a carrier like samsung , moto, lg, or etc..

But that ICS4 delay on Transformer1  is driving me crazy, because they have no carrier addon to put in, so what is making it delay?? :X

]]></description>
		<content:encoded><![CDATA[<p>I dont knbow why&#8230; but i would see ASUS  marrie Google .. Because I use a transformer and somehow i see asus&#8230; more like a google manufacture.. Perhaps because i have a transformer hhehe<br />
And Asus usually is not so binded to a carrier like samsung , moto, lg, or etc..</p>
<p>But that ICS4 delay on Transformer1  is driving me crazy, because they have no carrier addon to put in, so what is making it delay?? :X</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pankomputerek</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184461</link>
		<dc:creator>pankomputerek</dc:creator>
		<pubDate>Thu, 16 Feb 2012 21:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184461</guid>
		<description><![CDATA[Most devices are running Gingerbread because Google won&#039;t approve ICS updates, a great example of this is Transformer ISC update.

Honeycomb is only for those who have tablets so, yeah.]]></description>
		<content:encoded><![CDATA[<p>Most devices are running Gingerbread because Google won&#8217;t approve ICS updates, a great example of this is Transformer ISC update.</p>
<p>Honeycomb is only for those who have tablets so, yeah.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DanDanRevolution</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184405</link>
		<dc:creator>DanDanRevolution</dc:creator>
		<pubDate>Thu, 16 Feb 2012 20:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184405</guid>
		<description><![CDATA[Is Google out of their mind? ICS just came out a few months ago and barely any phones run it. If they keep pushing out updates this fast without upgrading previous devices first, then people won&#039;t want to buy Android for fear of their device not being updated and left behind.]]></description>
		<content:encoded><![CDATA[<p>Is Google out of their mind? ICS just came out a few months ago and barely any phones run it. If they keep pushing out updates this fast without upgrading previous devices first, then people won&#8217;t want to buy Android for fear of their device not being updated and left behind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DanDanRevolution</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184406</link>
		<dc:creator>DanDanRevolution</dc:creator>
		<pubDate>Thu, 16 Feb 2012 20:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184406</guid>
		<description><![CDATA[Is Google out of their mind? ICS just came out a few months ago and barely any phones run it. If they keep pushing out updates this fast without upgrading previous devices first, then people won&#039;t want to buy Android for fear of their device not being updated and left behind.]]></description>
		<content:encoded><![CDATA[<p>Is Google out of their mind? ICS just came out a few months ago and barely any phones run it. If they keep pushing out updates this fast without upgrading previous devices first, then people won&#8217;t want to buy Android for fear of their device not being updated and left behind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Macman73076</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184362</link>
		<dc:creator>Macman73076</dc:creator>
		<pubDate>Thu, 16 Feb 2012 19:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184362</guid>
		<description><![CDATA[I have a Nexus S with ICS.  ]]></description>
		<content:encoded><![CDATA[<p>I have a Nexus S with ICS.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gmaninvan</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184321</link>
		<dc:creator>gmaninvan</dc:creator>
		<pubDate>Thu, 16 Feb 2012 18:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184321</guid>
		<description><![CDATA[I think the eventual result will be this if android is going to retain it&#039;s current dominance.

1. Integrate a theme engine similar to what is provided with the AOSP although much cleaner. This would allow manufacturers to provide their own custom look for devices without messing with the underlying code. If they want to differentiate further, they can limit it to replacing factory apps like the dialer, gallery, camera, etc. If the app is not initially compatible with the newest version of android pushed out, the manufacturer can release the new build stock with their theme on top and update their apps to be compatible and replace the stock ones later either through the market or OTA. This would allow OS updates to continue to come from google while putting carrier and manufacturer customization only on the surface.

2. Google should push the chipset manufacturers to take responsibility for providing updated drivers in a timely manner similar to what they do for windows builds. Motorola recently came out and said that updates take a while since Kernels and drivers need to be adapted for the various chipset manufacturers not included in the original source code.

3. Cut out the carrier from the update process. The carriers state that they need to test devices on their network but this is simply not true. The reality is that they just need some time to test their crapware on the devices prior to pushing it out. Give carriers a hub in the market to push their wares and the carrier can use SMS or account notifications and bills to encourage their users to use these services. Uninstallable carrier apps are unacceptable and should not be permitted.

4. Integrate ChromeOS and android far deeper. Eventually, the idea would be that the UI for chromeOS would disappear and be relegated to the browser while the emerging webapp development tools would be integrated into the android SDK. The idea that native apps would eventually be phased out by cross platform web apps that behave on par or better than native ones. Google could use the native code program they have been working on for this.

5. Partners need to reduce the amount of devices that they are releasing which is already beginning to happen now. Each manufacturer needs to launch one annual hero device that is made from premium materials and always updated to the latest version of android. This would also eliminate issues like Motorola is dealing with where they have stated that some devices won&#039;t get updated because there are just too many to support.

6. Android is evolving into an incredibly powerful OS. Google needs to increase the size of the android development team and set aside a group that is focused on creating a build of the software that is usable as a full scale desktop OS.

7. Improve google docs to the point where it can be considered a solid option to MS Office. Mobile apps are still sloppy in their editing functionality and people tend to lean towards third party options to get the job done. Also, Docs need to be simplified as the interface is fairly clunky and confusing for users.]]></description>
		<content:encoded><![CDATA[<p>I think the eventual result will be this if android is going to retain it&#8217;s current dominance.</p>
<p>1. Integrate a theme engine similar to what is provided with the AOSP although much cleaner. This would allow manufacturers to provide their own custom look for devices without messing with the underlying code. If they want to differentiate further, they can limit it to replacing factory apps like the dialer, gallery, camera, etc. If the app is not initially compatible with the newest version of android pushed out, the manufacturer can release the new build stock with their theme on top and update their apps to be compatible and replace the stock ones later either through the market or OTA. This would allow OS updates to continue to come from google while putting carrier and manufacturer customization only on the surface.</p>
<p>2. Google should push the chipset manufacturers to take responsibility for providing updated drivers in a timely manner similar to what they do for windows builds. Motorola recently came out and said that updates take a while since Kernels and drivers need to be adapted for the various chipset manufacturers not included in the original source code.</p>
<p>3. Cut out the carrier from the update process. The carriers state that they need to test devices on their network but this is simply not true. The reality is that they just need some time to test their crapware on the devices prior to pushing it out. Give carriers a hub in the market to push their wares and the carrier can use SMS or account notifications and bills to encourage their users to use these services. Uninstallable carrier apps are unacceptable and should not be permitted.</p>
<p>4. Integrate ChromeOS and android far deeper. Eventually, the idea would be that the UI for chromeOS would disappear and be relegated to the browser while the emerging webapp development tools would be integrated into the android SDK. The idea that native apps would eventually be phased out by cross platform web apps that behave on par or better than native ones. Google could use the native code program they have been working on for this.</p>
<p>5. Partners need to reduce the amount of devices that they are releasing which is already beginning to happen now. Each manufacturer needs to launch one annual hero device that is made from premium materials and always updated to the latest version of android. This would also eliminate issues like Motorola is dealing with where they have stated that some devices won&#8217;t get updated because there are just too many to support.</p>
<p>6. Android is evolving into an incredibly powerful OS. Google needs to increase the size of the android development team and set aside a group that is focused on creating a build of the software that is usable as a full scale desktop OS.</p>
<p>7. Improve google docs to the point where it can be considered a solid option to MS Office. Mobile apps are still sloppy in their editing functionality and people tend to lean towards third party options to get the job done. Also, Docs need to be simplified as the interface is fairly clunky and confusing for users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mattj78</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184246</link>
		<dc:creator>mattj78</dc:creator>
		<pubDate>Thu, 16 Feb 2012 16:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184246</guid>
		<description><![CDATA[Digitimes? Have they ever got anything right?  I&#039;m sure they just make stuff up.]]></description>
		<content:encoded><![CDATA[<p>Digitimes? Have they ever got anything right?  I&#8217;m sure they just make stuff up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hyundella</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184235</link>
		<dc:creator>Hyundella</dc:creator>
		<pubDate>Thu, 16 Feb 2012 15:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184235</guid>
		<description><![CDATA[Jeez, by the time my GTab 10.1 gets ICS, it&#039;ll be outdated... again... meeh!]]></description>
		<content:encoded><![CDATA[<p>Jeez, by the time my GTab 10.1 gets ICS, it&#8217;ll be outdated&#8230; again&#8230; meeh!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SATR</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184233</link>
		<dc:creator>SATR</dc:creator>
		<pubDate>Thu, 16 Feb 2012 15:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184233</guid>
		<description><![CDATA[how was it the latest nexus device? ]]></description>
		<content:encoded><![CDATA[<p>how was it the latest nexus device? </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrewlh</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184221</link>
		<dc:creator>Andrewlh</dc:creator>
		<pubDate>Thu, 16 Feb 2012 15:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184221</guid>
		<description><![CDATA[to answer your question though, yes, android can run on x86]]></description>
		<content:encoded><![CDATA[<p>to answer your question though, yes, android can run on x86</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrewlh</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184220</link>
		<dc:creator>Andrewlh</dc:creator>
		<pubDate>Thu, 16 Feb 2012 15:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184220</guid>
		<description><![CDATA[google needs to pull the reins in on the OEMs.  part of the contract for access to the google market on a device needs to be updates within 2-3 months of a new OS release.  miss the deadline, lose market access till your device is up to date.  OEMs won&#039;t let that slip.]]></description>
		<content:encoded><![CDATA[<p>google needs to pull the reins in on the OEMs.  part of the contract for access to the google market on a device needs to be updates within 2-3 months of a new OS release.  miss the deadline, lose market access till your device is up to date.  OEMs won&#8217;t let that slip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franklin Stone</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184209</link>
		<dc:creator>Franklin Stone</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184209</guid>
		<description><![CDATA[If only people had that option. People keep talking about Android fragmentation, but that&#039;s not the only problem. The deeper problem in the US is carrier fragmentation. We don&#039;t have a standard for 3G or for 4G, meaning we have all these different technologies running rampant around the country and for each technology the OEMs have to build a specific phone. Then the carrier gets that phone under an exclusivity contract meaning nobody else can get it for months or years. This isn&#039;t helping the consumers and it frustrates the OEMs and Google. Now Google is saying they&#039;re going to slow down or stop supporting CDMA, it&#039;s because the technology is too fragmented.]]></description>
		<content:encoded><![CDATA[<p>If only people had that option. People keep talking about Android fragmentation, but that&#8217;s not the only problem. The deeper problem in the US is carrier fragmentation. We don&#8217;t have a standard for 3G or for 4G, meaning we have all these different technologies running rampant around the country and for each technology the OEMs have to build a specific phone. Then the carrier gets that phone under an exclusivity contract meaning nobody else can get it for months or years. This isn&#8217;t helping the consumers and it frustrates the OEMs and Google. Now Google is saying they&#8217;re going to slow down or stop supporting CDMA, it&#8217;s because the technology is too fragmented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franklin Stone</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184203</link>
		<dc:creator>Franklin Stone</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184203</guid>
		<description><![CDATA[Motorola may not even be the next Nexus manufacturer. Google has stated time and again that they are not going to take direct control of Motorola but that it will still operate on its own. Moto will have to bid with LG, HTC, Samsung and all the others on the next Nexus device.]]></description>
		<content:encoded><![CDATA[<p>Motorola may not even be the next Nexus manufacturer. Google has stated time and again that they are not going to take direct control of Motorola but that it will still operate on its own. Moto will have to bid with LG, HTC, Samsung and all the others on the next Nexus device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: indyvoter</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184202</link>
		<dc:creator>indyvoter</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184202</guid>
		<description><![CDATA[and yet another reason i will never get an iPhone.]]></description>
		<content:encoded><![CDATA[<p>and yet another reason i will never get an iPhone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franklin Stone</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184199</link>
		<dc:creator>Franklin Stone</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184199</guid>
		<description><![CDATA[But that&#039;s Samsung&#039;s fault not Google, in your original post you placed the blame on Google for Samsung not updating your phone, that&#039;s incorrect]]></description>
		<content:encoded><![CDATA[<p>But that&#8217;s Samsung&#8217;s fault not Google, in your original post you placed the blame on Google for Samsung not updating your phone, that&#8217;s incorrect</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fox Fan</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184197</link>
		<dc:creator>Fox Fan</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184197</guid>
		<description><![CDATA[That&#039;s the beauty of Android- you can put any number of OSs on it and they change fundamental aspects of the device. ]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s the beauty of Android- you can put any number of OSs on it and they change fundamental aspects of the device. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J2</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184194</link>
		<dc:creator>J2</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184194</guid>
		<description><![CDATA[Tell that to many Sprint customers who are still waiting for the OTA update (that was stopped after being started initially)]]></description>
		<content:encoded><![CDATA[<p>Tell that to many Sprint customers who are still waiting for the OTA update (that was stopped after being started initially)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: indyvoter</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184188</link>
		<dc:creator>indyvoter</dc:creator>
		<pubDate>Thu, 16 Feb 2012 14:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184188</guid>
		<description><![CDATA[who cares what device gets what, Cyanogen will just put it out and i&#039;ll root 5.0 to my phone or Touchpad. pretty simple. no need to buy anything new.]]></description>
		<content:encoded><![CDATA[<p>who cares what device gets what, Cyanogen will just put it out and i&#8217;ll root 5.0 to my phone or Touchpad. pretty simple. no need to buy anything new.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DirtyMagic86</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184186</link>
		<dc:creator>DirtyMagic86</dc:creator>
		<pubDate>Thu, 16 Feb 2012 13:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184186</guid>
		<description><![CDATA[Hang on. Windows on ARM can&#039;t dual boot, can Android run on x86?

Edit: Sorry just re-read the part about OEMs installing both before bootlocking.]]></description>
		<content:encoded><![CDATA[<p>Hang on. Windows on ARM can&#8217;t dual boot, can Android run on x86?</p>
<p>Edit: Sorry just re-read the part about OEMs installing both before bootlocking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Bosch</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184174</link>
		<dc:creator>Rick Bosch</dc:creator>
		<pubDate>Thu, 16 Feb 2012 13:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184174</guid>
		<description><![CDATA[@920dda432aa62bb0a5dc4f80afaa0dc9:disqus That&#039;s not really true is it? I received an OTA on my Nexus S at the end of last year. Been running ICS ever since. ]]></description>
		<content:encoded><![CDATA[<p>@920dda432aa62bb0a5dc4f80afaa0dc9:disqus That&#8217;s not really true is it? I received an OTA on my Nexus S at the end of last year. Been running ICS ever since. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Duncan</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184162</link>
		<dc:creator>Brian Duncan</dc:creator>
		<pubDate>Thu, 16 Feb 2012 13:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184162</guid>
		<description><![CDATA[Bingo, ICS 4.0.3 AOSP runs like butter on my single core Nexus S 4g.  Unlocked bootloaders would free consumers from the OEM to chose to migrate upwards.  Fragmentation is caused by the carriers believing they are adding value to Android with their crippled interface add-ons.

I am the 1.12%]]></description>
		<content:encoded><![CDATA[<p>Bingo, ICS 4.0.3 AOSP runs like butter on my single core Nexus S 4g.  Unlocked bootloaders would free consumers from the OEM to chose to migrate upwards.  Fragmentation is caused by the carriers believing they are adding value to Android with their crippled interface add-ons.</p>
<p>I am the 1.12%</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Duncan</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184163</link>
		<dc:creator>Brian Duncan</dc:creator>
		<pubDate>Thu, 16 Feb 2012 13:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184163</guid>
		<description><![CDATA[Bingo, ICS 4.0.3 AOSP runs like butter on my single core Nexus S 4g.  Unlocked bootloaders would free consumers from the OEM to chose to migrate upwards.  Fragmentation is caused by the carriers believing they are adding value to Android with their crippled interface add-ons.

I am the 1.12%]]></description>
		<content:encoded><![CDATA[<p>Bingo, ICS 4.0.3 AOSP runs like butter on my single core Nexus S 4g.  Unlocked bootloaders would free consumers from the OEM to chose to migrate upwards.  Fragmentation is caused by the carriers believing they are adding value to Android with their crippled interface add-ons.</p>
<p>I am the 1.12%</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Duncan</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184164</link>
		<dc:creator>Brian Duncan</dc:creator>
		<pubDate>Thu, 16 Feb 2012 13:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184164</guid>
		<description><![CDATA[Bingo, ICS 4.0.3 AOSP runs like butter on my single core Nexus S 4g.  Unlocked bootloaders would free consumers from the OEM to chose to migrate upwards.  Fragmentation is caused by the carriers believing they are adding value to Android with their crippled interface add-ons.

I am the 1.12%]]></description>
		<content:encoded><![CDATA[<p>Bingo, ICS 4.0.3 AOSP runs like butter on my single core Nexus S 4g.  Unlocked bootloaders would free consumers from the OEM to chose to migrate upwards.  Fragmentation is caused by the carriers believing they are adding value to Android with their crippled interface add-ons.</p>
<p>I am the 1.12%</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dsitek89</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184159</link>
		<dc:creator>Dsitek89</dc:creator>
		<pubDate>Thu, 16 Feb 2012 12:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184159</guid>
		<description><![CDATA[The nexus s was the most recent nexus device and it is not scheduled to get ICS.]]></description>
		<content:encoded><![CDATA[<p>The nexus s was the most recent nexus device and it is not scheduled to get ICS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dsitek89</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184160</link>
		<dc:creator>Dsitek89</dc:creator>
		<pubDate>Thu, 16 Feb 2012 12:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184160</guid>
		<description><![CDATA[The nexus s was the most recent nexus device and it is not scheduled to get ICS.]]></description>
		<content:encoded><![CDATA[<p>The nexus s was the most recent nexus device and it is not scheduled to get ICS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dsitek89</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184161</link>
		<dc:creator>Dsitek89</dc:creator>
		<pubDate>Thu, 16 Feb 2012 12:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184161</guid>
		<description><![CDATA[The nexus s was the most recent nexus device and it is not scheduled to get ICS.]]></description>
		<content:encoded><![CDATA[<p>The nexus s was the most recent nexus device and it is not scheduled to get ICS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J.L. "J7" Gatewood StarrWulfe</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184156</link>
		<dc:creator>J.L. "J7" Gatewood StarrWulfe</dc:creator>
		<pubDate>Thu, 16 Feb 2012 12:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184156</guid>
		<description><![CDATA[What&#039;s needed is a firm example from Google themselves on what other manufacturers should be doing with their OS as far as putting and releasing hardware...  Apple is compelling because they control the OS and the hardware it runs on, avoiding fragmentation.  Now Google can do the same with their Motorola aquisition.  


They release Jelly Bean, and a new version of Motorola Nexus handsets and tablets that anyone can purchase (they did it before with the Nexus G1)  Force the carrier&#039;s hands-- I just want to be able to buy a loose SIM and place it in the device! That way we&#039;re free to use the devices how we want, whenever we want. 

The new Motorola Nexus devices should be REVOLUTIONARY designs that take advantage of the OS features-- They already have a lapdock that turns the phone into a laptop.  Asus has a Transformer Prime that goes from tablet to netbook...  COMBINE THEM.  Handset -&gt; Tablet -&gt; Netbook.  In this way, one can &quot;upgrade&quot; as they need a new form factor.  Get the phone, then when you need a tablet for a bigger screen, get that accessory.  In this manner, you keep the one bill every month and gain functions.  Do this in the face of their manufacturing partners, and they&#039;ll catch on quick! ]]></description>
		<content:encoded><![CDATA[<p>What&#8217;s needed is a firm example from Google themselves on what other manufacturers should be doing with their OS as far as putting and releasing hardware&#8230;  Apple is compelling because they control the OS and the hardware it runs on, avoiding fragmentation.  Now Google can do the same with their Motorola aquisition.  </p>
<p>They release Jelly Bean, and a new version of Motorola Nexus handsets and tablets that anyone can purchase (they did it before with the Nexus G1)  Force the carrier&#8217;s hands&#8211; I just want to be able to buy a loose SIM and place it in the device! That way we&#8217;re free to use the devices how we want, whenever we want. </p>
<p>The new Motorola Nexus devices should be REVOLUTIONARY designs that take advantage of the OS features&#8211; They already have a lapdock that turns the phone into a laptop.  Asus has a Transformer Prime that goes from tablet to netbook&#8230;  COMBINE THEM.  Handset -&gt; Tablet -&gt; Netbook.  In this way, one can &#8220;upgrade&#8221; as they need a new form factor.  Get the phone, then when you need a tablet for a bigger screen, get that accessory.  In this manner, you keep the one bill every month and gain functions.  Do this in the face of their manufacturing partners, and they&#8217;ll catch on quick! </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J.L. "J7" Gatewood StarrWulfe</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184157</link>
		<dc:creator>J.L. "J7" Gatewood StarrWulfe</dc:creator>
		<pubDate>Thu, 16 Feb 2012 12:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184157</guid>
		<description><![CDATA[What&#039;s needed is a firm example from Google themselves on what other manufacturers should be doing with their OS as far as putting and releasing hardware...  Apple is compelling because they control the OS and the hardware it runs on, avoiding fragmentation.  Now Google can do the same with their Motorola aquisition.  


They release Jelly Bean, and a new version of Motorola Nexus handsets and tablets that anyone can purchase (they did it before with the Nexus G1)  Force the carrier&#039;s hands-- I just want to be able to buy a loose SIM and place it in the device! That way we&#039;re free to use the devices how we want, whenever we want. 

The new Motorola Nexus devices should be REVOLUTIONARY designs that take advantage of the OS features-- They already have a lapdock that turns the phone into a laptop.  Asus has a Transformer Prime that goes from tablet to netbook...  COMBINE THEM.  Handset -&gt; Tablet -&gt; Netbook.  In this way, one can &quot;upgrade&quot; as they need a new form factor.  Get the phone, then when you need a tablet for a bigger screen, get that accessory.  In this manner, you keep the one bill every month and gain functions.  Do this in the face of their manufacturing partners, and they&#039;ll catch on quick! ]]></description>
		<content:encoded><![CDATA[<p>What&#8217;s needed is a firm example from Google themselves on what other manufacturers should be doing with their OS as far as putting and releasing hardware&#8230;  Apple is compelling because they control the OS and the hardware it runs on, avoiding fragmentation.  Now Google can do the same with their Motorola aquisition.  </p>
<p>They release Jelly Bean, and a new version of Motorola Nexus handsets and tablets that anyone can purchase (they did it before with the Nexus G1)  Force the carrier&#8217;s hands&#8211; I just want to be able to buy a loose SIM and place it in the device! That way we&#8217;re free to use the devices how we want, whenever we want. </p>
<p>The new Motorola Nexus devices should be REVOLUTIONARY designs that take advantage of the OS features&#8211; They already have a lapdock that turns the phone into a laptop.  Asus has a Transformer Prime that goes from tablet to netbook&#8230;  COMBINE THEM.  Handset -&gt; Tablet -&gt; Netbook.  In this way, one can &#8220;upgrade&#8221; as they need a new form factor.  Get the phone, then when you need a tablet for a bigger screen, get that accessory.  In this manner, you keep the one bill every month and gain functions.  Do this in the face of their manufacturing partners, and they&#8217;ll catch on quick! </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J.L. "J7" Gatewood StarrWulfe</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184158</link>
		<dc:creator>J.L. "J7" Gatewood StarrWulfe</dc:creator>
		<pubDate>Thu, 16 Feb 2012 12:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184158</guid>
		<description><![CDATA[What&#039;s needed is a firm example from Google themselves on what other manufacturers should be doing with their OS as far as putting and releasing hardware...  Apple is compelling because they control the OS and the hardware it runs on, avoiding fragmentation.  Now Google can do the same with their Motorola aquisition.  


They release Jelly Bean, and a new version of Motorola Nexus handsets and tablets that anyone can purchase (they did it before with the Nexus G1)  Force the carrier&#039;s hands-- I just want to be able to buy a loose SIM and place it in the device! That way we&#039;re free to use the devices how we want, whenever we want. 

The new Motorola Nexus devices should be REVOLUTIONARY designs that take advantage of the OS features-- They already have a lapdock that turns the phone into a laptop.  Asus has a Transformer Prime that goes from tablet to netbook...  COMBINE THEM.  Handset -&gt; Tablet -&gt; Netbook.  In this way, one can &quot;upgrade&quot; as they need a new form factor.  Get the phone, then when you need a tablet for a bigger screen, get that accessory.  In this manner, you keep the one bill every month and gain functions.  Do this in the face of their manufacturing partners, and they&#039;ll catch on quick! ]]></description>
		<content:encoded><![CDATA[<p>What&#8217;s needed is a firm example from Google themselves on what other manufacturers should be doing with their OS as far as putting and releasing hardware&#8230;  Apple is compelling because they control the OS and the hardware it runs on, avoiding fragmentation.  Now Google can do the same with their Motorola aquisition.  </p>
<p>They release Jelly Bean, and a new version of Motorola Nexus handsets and tablets that anyone can purchase (they did it before with the Nexus G1)  Force the carrier&#8217;s hands&#8211; I just want to be able to buy a loose SIM and place it in the device! That way we&#8217;re free to use the devices how we want, whenever we want. </p>
<p>The new Motorola Nexus devices should be REVOLUTIONARY designs that take advantage of the OS features&#8211; They already have a lapdock that turns the phone into a laptop.  Asus has a Transformer Prime that goes from tablet to netbook&#8230;  COMBINE THEM.  Handset -&gt; Tablet -&gt; Netbook.  In this way, one can &#8220;upgrade&#8221; as they need a new form factor.  Get the phone, then when you need a tablet for a bigger screen, get that accessory.  In this manner, you keep the one bill every month and gain functions.  Do this in the face of their manufacturing partners, and they&#8217;ll catch on quick! </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gerrr!</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184155</link>
		<dc:creator>gerrr!</dc:creator>
		<pubDate>Thu, 16 Feb 2012 12:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184155</guid>
		<description><![CDATA[ Or people could simply buy Nexus phones and not worry about that.]]></description>
		<content:encoded><![CDATA[<p> Or people could simply buy Nexus phones and not worry about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vanvin</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184154</link>
		<dc:creator>Vanvin</dc:creator>
		<pubDate>Thu, 16 Feb 2012 11:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184154</guid>
		<description><![CDATA[There is already that one phone. It&#039;s on the Nexus brand (Nexus S, Galaxy Nexus...)
]]></description>
		<content:encoded><![CDATA[<p>There is already that one phone. It&#8217;s on the Nexus brand (Nexus S, Galaxy Nexus&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Optimaximal</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184152</link>
		<dc:creator>Optimaximal</dc:creator>
		<pubDate>Thu, 16 Feb 2012 11:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184152</guid>
		<description><![CDATA[Google won&#039;t lose the race. 

Android activations are still flying despite the problems its rivals keep highlighting and the media keep running with - at the end of the day, even the cheapest proper Android phone is basically a web browser, a social media portal and a sat-nav device.

People will keep buying them, even if they&#039;ll hate them after a few months and wish they&#039;d saved for something better, such is human nature.

What Google need to do is either demand the OEMs offer customers an escape route (be it unlocked bootloaders, recovery that doesn&#039;t void warranty and/or full support for official Google-sourced ROMs) or take control and enforce things.  

Of course, the latter won&#039;t happen without a) violating the Apache license and b) driving the already wary OEMs away.]]></description>
		<content:encoded><![CDATA[<p>Google won&#8217;t lose the race. </p>
<p>Android activations are still flying despite the problems its rivals keep highlighting and the media keep running with &#8211; at the end of the day, even the cheapest proper Android phone is basically a web browser, a social media portal and a sat-nav device.</p>
<p>People will keep buying them, even if they&#8217;ll hate them after a few months and wish they&#8217;d saved for something better, such is human nature.</p>
<p>What Google need to do is either demand the OEMs offer customers an escape route (be it unlocked bootloaders, recovery that doesn&#8217;t void warranty and/or full support for official Google-sourced ROMs) or take control and enforce things.  </p>
<p>Of course, the latter won&#8217;t happen without a) violating the Apache license and b) driving the already wary OEMs away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Optimaximal</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184150</link>
		<dc:creator>Optimaximal</dc:creator>
		<pubDate>Thu, 16 Feb 2012 11:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184150</guid>
		<description><![CDATA[I wouldn&#039;t say Google managed to capture marketing because of the &#039;beauty of the OS&#039;.

Up until Gingerbread, Android Stock was a clusterfuck of competing design decisions, strange &#039;*nix&#039; like interface paradigms and reactionary updates to competitors. The OEMs developed skins not just to differentiate their products but to tidy up the UX. *They* made Android a valid OS in the consumers eyes by presenting something that looked good on the surface and made the devices behave well.

Of course, everyone then realised they can&#039;t just upgrade when the want, working instead to 2-3 middle men&#039;s timescales/budgets.

Gingerbread&#039;s main goal was to remove the need for skins by making the UX consistent.]]></description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t say Google managed to capture marketing because of the &#8216;beauty of the OS&#8217;.</p>
<p>Up until Gingerbread, Android Stock was a clusterfuck of competing design decisions, strange &#8216;*nix&#8217; like interface paradigms and reactionary updates to competitors. The OEMs developed skins not just to differentiate their products but to tidy up the UX. *They* made Android a valid OS in the consumers eyes by presenting something that looked good on the surface and made the devices behave well.</p>
<p>Of course, everyone then realised they can&#8217;t just upgrade when the want, working instead to 2-3 middle men&#8217;s timescales/budgets.</p>
<p>Gingerbread&#8217;s main goal was to remove the need for skins by making the UX consistent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miquel Mayol i Tur</title>
		<link>http://www.slashgear.com/android-5-0-jelly-bean-tipped-for-q2-2012-16213751/#comment-184149</link>
		<dc:creator>Miquel Mayol i Tur</dc:creator>
		<pubDate>Thu, 16 Feb 2012 11:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=213751#comment-184149</guid>
		<description><![CDATA[The dual boot is not for MS WOS 8 is for Chrome OS or Ubuntu - that now is available as an app and can be used inside Android via VNC. Or even Web OS, Aliyun, Tizen or any other Open Source OS.]]></description>
		<content:encoded><![CDATA[<p>The dual boot is not for MS WOS 8 is for Chrome OS or Ubuntu &#8211; that now is available as an app and can be used inside Android via VNC. Or even Web OS, Aliyun, Tizen or any other Open Source OS.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
