<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:osnews="http://www.osnews.com/rss2#">
	<channel>
		<title>OSNews: </title>
		<link>http://www.osnews.com/story/24967/BlackBerry_PlayBook_OS_v1_0_7_Released</link>
		<description>Exploring the Future of Computing</description>
		<language>en-us</language>
		<copyright>Copyright 2001-2013, David Adams</copyright>
		<webMaster>adam+nospam@osnews.com</webMaster>
		<lastBuildDate>Thu, 23 May 2013 04:49:24 GMT</lastBuildDate>
		<image>
			<url>http://www.osnews.com/images/osnews.gif</url>
			<title>OSNews.com</title>
			<link>http://www.osnews.com</link>
		</image>
		<item>
			<title>It broke BB Bridge</title>
			<link>http://www.osnews.com/thread?481771</link>
			<guid isPermaLink="true">http://www.osnews.com/thread?481771</guid>
			<description>The 1.0.7 release was rumored to be available on 7/15 but it never came. Since it was only a rumor, no worries right?  For Blackberry phone users, there was a Bridge update early Tuesday morning which worked fine.  After TabletOS 1.0.7 was released on on Tuesday after the Bridge update, customers could no longer see the Bridge applications even though the bridge would connect.<br />
<br />
I wonder if the initial delay was the reason RIM angered customers on Friday after telling vendors earlier in the week the update would come then.<br />
<br />
I don't use a BB phone for now so I use my Playbook Bridgeless.</description>
			<pubDate>Wed, 20 Jul 2011 19:39:00 GMT</pubDate>
			<author>donotreply@osnews.com (libray)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: It broke BB Bridge</title>
			<link>http://www.osnews.com/thread?481887</link>
			<guid isPermaLink="true">http://www.osnews.com/thread?481887</guid>
			<description>TabletOS 1.0.7.2670 is now available.  The broken update linked in this article and released Tuesday was 1.0.7.2650</description>
			<pubDate>Thu, 21 Jul 2011 17:03:00 GMT</pubDate>
			<author>donotreply@osnews.com (libray)</author>
			<category>Comments</category>
		</item>
	</channel>
</rss>
