<?xml 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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Android and Me &#187; jbq</title>
	<atom:link href="http://androidandme.com/tag/jbq/feed/" rel="self" type="application/rss+xml" />
	<link>http://androidandme.com</link>
	<description>Meet Your New Android Friend.  Your Community For All Things Google Android.</description>
	<lastBuildDate>Fri, 25 May 2012 17:14:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Google&#8217;s JBQ speaks out on Android updates, Google selling the Galaxy Nexus and more</title>
		<link>http://androidandme.com/2012/04/news/googles-jbq-speaks-out-on-android-updates-google-selling-the-galaxy-nexus-and-more/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=googles-jbq-speaks-out-on-android-updates-google-selling-the-galaxy-nexus-and-more</link>
		<comments>http://androidandme.com/2012/04/news/googles-jbq-speaks-out-on-android-updates-google-selling-the-galaxy-nexus-and-more/#comments</comments>
		<pubDate>Fri, 27 Apr 2012 19:45:33 +0000</pubDate>
		<dc:creator>Dustin Earley</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Android 4]]></category>
		<category><![CDATA[Ice Cream Sandwich]]></category>
		<category><![CDATA[jbq]]></category>
		<category><![CDATA[Samsung Galaxy Nexus]]></category>
		<category><![CDATA[sont tablet s]]></category>
		<category><![CDATA[Updates]]></category>

		<guid isPermaLink="false">http://androidandme.com/?p=59591</guid>
		<description><![CDATA[<img width="630" height="300" src="http://androidandme.wpengine.netdna-cdn.com/wp-content/uploads/2011/11/android-magazine-spread.jpg" class="attachment-59591 wp-post-image" alt="android-magazine-spread" title="android-magazine-spread" /><p>Jean-Baptiste Queru is the technical lead for the Android Open Source Project at Google. When he talks, we tend to listen. Many a time now, JBQ (as he&#8217;s more commonly known) has come to the aid of speculating bloggers and explained situations with updates, Nexus devices and much more. Today, with the Sony Tablet S [...]]]></description>
			<content:encoded><![CDATA[<img width="630" height="300" src="http://androidandme.wpengine.netdna-cdn.com/wp-content/uploads/2011/11/android-magazine-spread.jpg" class="attachment-59591 wp-post-image" alt="android-magazine-spread" title="android-magazine-spread" /><p>Jean-Baptiste Queru is the technical lead for the Android Open Source Project at Google. When he talks, we tend to listen. Many a time now, JBQ (as he&#8217;s more commonly known) has come to the aid of speculating bloggers and explained situations with updates, Nexus devices and much more. Today, with the Sony Tablet S getting updated to Android 4 and Google selling the <a href="http://androidandme.com/2012/04/smartphones-2/breaking-google-begins-selling-galaxy-nexus-on-google-play-store-for-399/">Galaxy Nexus directly</a> recently, JBQ took a moment to share his thoughts on updates on <a href="https://plus.google.com/112218872649456413744/posts/79eKhEgNYeN">Google+</a>.</p>
<p>When it comes to Sony updating their Tablet S, JBQ says that the five months time it took them to complete the update was, &#8220;very reasonable.&#8221; He continues on to say that the changes from Android 3 (Honeycomb) and Android 2.3 (Gingerbread) to Android 4 (Ice Cream Sandwich) are huge. A lot has changed from previous versions of Android to now, and the only reason Sony has managed to stay as up to date as they are is thanks to their contributions to the AOSP. ASUS&#8217; updates have also been very timely, but that&#8217;s because of the tight relationship between ASUS and NVIDIA. Both companies are extremely focused on keeping their products up to date.</p>
<p>Continuing on the subject of updates, JBQ isn&#8217;t too happy on how the Nexus program is playing out. But Google selling the Nexus directly will help that:</p>
<blockquote class="long">The part that blows my mind is that some variants of the Google-engineered flagship devices still haven't received Ice Cream Sandwich (or are stuck with older versions of Ice Cream Sandwich) because of delays introduced by operator approvals. I'm very glad that Google is back in the business of selling phones directly without any middlemen to interfere, and I'll be even happier when I see that program expanded to more countries.<cite>JBQ<small>Google</small></cite></blockquote>
<p>Personally, I take two important things out of this. For one, Google is most definitely aware of the woes delayed updates cause. Especially when it comes to Nexus devices. And number two, those delays aren&#8217;t going to change if you buy a carrier regulated device. If you really, truly want your updates from Google, you have to buy your device from Google.</p>
<p>While none of that may be new information (in fact, it&#8217;s starting to feel like we&#8217;re beating a dead horse here), it&#8217;s especially relevant after this past weeks news of Google deciding to sell the Galaxy Nexus directly. Even the <a href="http://support.google.com/googleplay/bin/answer.py?hl=en&amp;answer=2589788&amp;topic=2451685&amp;ctx=topic">support website</a> for the Google sold GSM Nexus will be directly managed by Google. And that&#8217;s all there is to it.</p>
<p>What do you think of a five month wait between updates for carrier regulated devices? Is that too long, or is it worth the wait? And while we&#8217;re at it, is anyone planning to buy an unlocked Nexus from Google? Have you already? Let us know in the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://androidandme.com/2012/04/news/googles-jbq-speaks-out-on-android-updates-google-selling-the-galaxy-nexus-and-more/feed/</wfw:commentRss>
		<slash:comments>58</slash:comments>
		</item>
		<item>
		<title>Google releases source code for Android 2.0</title>
		<link>http://androidandme.com/2009/11/news/google-releases-source-code-for-android-2-0/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=google-releases-source-code-for-android-2-0</link>
		<comments>http://androidandme.com/2009/11/news/google-releases-source-code-for-android-2-0/#comments</comments>
		<pubDate>Sat, 14 Nov 2009 02:48:59 +0000</pubDate>
		<dc:creator>Taylor Wimberly</dc:creator>
				<category><![CDATA[Android OS News]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[android 2.0]]></category>
		<category><![CDATA[aosp]]></category>
		<category><![CDATA[bits]]></category>
		<category><![CDATA[cyanogen]]></category>
		<category><![CDATA[eclair]]></category>
		<category><![CDATA[jbq]]></category>

		<guid isPermaLink="false">http://androidandme.com/?p=7495</guid>
		<description><![CDATA[Eclair source is now available in the AOSP.]]></description>
			<content:encoded><![CDATA[<p>One week after Verizon launched the Motorola Droid with Android 2.0, Google has released the source code for their latest update. I&#8217;ve been unplugged for several days so I was actually quite shocked when I heard the Eclair source code was now available in the AOSP (<a href="http://source.android.com/" target="_blank">Android Open Source Project</a>).</p>
<p>It looks like we have to thank one of our favorite (and most vocal) Android engineers, Mr. Jean-Baptiste M. &#8220;JBQ&#8221; Queru. He worked close to 100 hours the last 6 days to make this release possible.</p>
<p>Details of the Eclair drop were posted on the <a href="http://groups.google.com/group/android-platform/browse_thread/thread/db968455d490dfad" target="_blank">Android-platform</a> mailing lists.</p>
<blockquote><p>I&#8217;ve just created an eclair branch in AOSP, which contains the code that many people have been waiting for.</p>
<p>What&#8217;s in that branch? It&#8217;s basically a snapshot of part of Google&#8217;s internal eclair tree, a little bit more recent than the build that was used in Droid. It&#8217;s not the exact source for Droid and is not ready to ship on a consumer device.</p>
<p>Caveats:<br />
-There&#8217;s no change history. Google is planning to eventually make the change history available, but at the moment the history contains some things that can&#8217;t be open-sourced, and making a snapshot was the fastest way to deal with those.</p>
<p>-It&#8217;s a partial tree. We&#8217;ll be open-sourcing more of eclair over time, but we figured it would make more sense to open-source part of it now instead of waiting until everything was in place.</p>
<p>-It doesn&#8217;t build for ADP1 or ION/ADP2. We&#8217;re working with the various companies involved to try to resolve this issue, but we preferred to open-source the code in its current state instead of waiting for a solution on the hardware side.</p>
<p>-It&#8217;s not currently merged in the master tree. I&#8217;m working on it, but I wanted to get something out before the week-end. Please be patient. I&#8217;ll try to complete it as quickly as I can.</p>
<p>-It doesn&#8217;t currently contain the AOSP-specific files (build configurations, etc&#8230;). They&#8217;ll come back.</p>
<p>-Calendar is broken. I have a fix that I will release along with the master tree.</p></blockquote>
<p>Many people might be wondering when Android 2.0 might appear on older phones now that the source code is available to the public. The most popular community dev <a href="http://www.cyanogenmod.com/" target="_blank">Cyanogen</a> will most likely begin backporting certain features from Android 2.0 over the next few days. However, a complete build of Android 2.0 will not be available on older devices (G1 and myTouch) until handset makers update their device drivers for the new Linux kernel that shipped with Eclair.</p>
]]></content:encoded>
			<wfw:commentRss>http://androidandme.com/2009/11/news/google-releases-source-code-for-android-2-0/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
	</channel>
</rss>

