<?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: BlackBerry OS 4.7.0.113 To Be Next Official Firmware Update For BlackBerry Storm</title>
	<atom:link href="http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm</link>
	<description>The Official, Unofficial BlackBerry Weblog</description>
	<lastBuildDate>Sat, 21 Nov 2009 10:34:27 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Will Verizon Update The BlackBerry Storm Already! &#124;</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-122095</link>
		<dc:creator>Will Verizon Update The BlackBerry Storm Already! &#124;</dc:creator>
		<pubDate>Tue, 26 May 2009 14:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-122095</guid>
		<description>[...] leaked OS updates are now up to 4.7.0.113, which is rumored to be the next official update, but other carriers have already officially [...]</description>
		<content:encoded><![CDATA[<p>[...] leaked OS updates are now up to 4.7.0.113, which is rumored to be the next official update, but other carriers have already officially [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linkfeedr &#187; Blog Archive &#187; Will Verizon Update The BlackBerry Storm Already! - RSS Indexer (beta)</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121389</link>
		<dc:creator>linkfeedr &#187; Blog Archive &#187; Will Verizon Update The BlackBerry Storm Already! - RSS Indexer (beta)</dc:creator>
		<pubDate>Wed, 15 Apr 2009 12:27:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121389</guid>
		<description>[...] use BlackBerry Storm OS 4.7.0.75 for much too long.The leaked OS updates are now up to 4.7.0.113, which is rumored to be the next official update, but other carriers have already officially [...]</description>
		<content:encoded><![CDATA[<p>[...] use BlackBerry Storm OS 4.7.0.75 for much too long.The leaked OS updates are now up to 4.7.0.113, which is rumored to be the next official update, but other carriers have already officially [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Verizon Update The BlackBerry Storm Already!</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121388</link>
		<dc:creator>Will Verizon Update The BlackBerry Storm Already!</dc:creator>
		<pubDate>Wed, 15 Apr 2009 11:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121388</guid>
		<description>[...] leaked OS updates are now up to 4.7.0.113, which is rumored to be the next official update, but other carriers have already officially [...]</description>
		<content:encoded><![CDATA[<p>[...] leaked OS updates are now up to 4.7.0.113, which is rumored to be the next official update, but other carriers have already officially [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: x313x</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121182</link>
		<dc:creator>x313x</dc:creator>
		<pubDate>Mon, 06 Apr 2009 17:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121182</guid>
		<description>Where can I DL the original FW to downgrade? This update has given me more problems then it&#039;s fixed :(</description>
		<content:encoded><![CDATA[<p>Where can I DL the original FW to downgrade? This update has given me more problems then it&#8217;s fixed <img src='http://www.rimarkable.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kernel32.dll</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121165</link>
		<dc:creator>kernel32.dll</dc:creator>
		<pubDate>Sun, 05 Apr 2009 21:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121165</guid>
		<description>Ok, I pasted the link to this earlier and now my post is gone.  I wouldn&#039;t be able to produce the clearest definition so here&#039;s the first paragraph from Wiki:

&gt;&gt;In computer science a memory leak is a particular type of unintentional memory consumption by a computer program where the program fails to release memory when no longer needed. This condition is normally the result of a bug in a program that prevents it from freeing up memory that it no longer needs.

This term has the potential to be confusing, since memory is not physically lost from the computer. Rather, memory is allocated to a program, and that program subsequently loses the ability to access it due to program logic flaws.&lt;&lt;

So basically when we&#039;re referencing memory leaks when talking about the Storm we&#039;re referring to the imperfection in the OS that causes it to hang off and on.</description>
		<content:encoded><![CDATA[<p>Ok, I pasted the link to this earlier and now my post is gone.  I wouldn&#8217;t be able to produce the clearest definition so here&#8217;s the first paragraph from Wiki:</p>
<p>&gt;&gt;In computer science a memory leak is a particular type of unintentional memory consumption by a computer program where the program fails to release memory when no longer needed. This condition is normally the result of a bug in a program that prevents it from freeing up memory that it no longer needs.</p>
<p>This term has the potential to be confusing, since memory is not physically lost from the computer. Rather, memory is allocated to a program, and that program subsequently loses the ability to access it due to program logic flaws.&lt;&lt;</p>
<p>So basically when we&#8217;re referencing memory leaks when talking about the Storm we&#8217;re referring to the imperfection in the OS that causes it to hang off and on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nathan</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121161</link>
		<dc:creator>nathan</dc:creator>
		<pubDate>Sun, 05 Apr 2009 12:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121161</guid>
		<description>ok although my question was never answered, I gather from all the comments that this is a OS update for the Storm so question answered in my books.
   Now a new newbie question...what is memory leakage and how do you know if your having this problem? I have the 8220 pearl with OS 4.6.0.174.  The way most people make it sound it seems like your vitural memory &quot;leaks&quot; somewhere even though there are no other programs open that would be responsible for using up more virtual memory.  Am I correct?

Thanks again and sorry if this really isn&#039;t the place for this type of question.

Nathan</description>
		<content:encoded><![CDATA[<p>ok although my question was never answered, I gather from all the comments that this is a OS update for the Storm so question answered in my books.<br />
   Now a new newbie question&#8230;what is memory leakage and how do you know if your having this problem? I have the 8220 pearl with OS 4.6.0.174.  The way most people make it sound it seems like your vitural memory &#8220;leaks&#8221; somewhere even though there are no other programs open that would be responsible for using up more virtual memory.  Am I correct?</p>
<p>Thanks again and sorry if this really isn&#8217;t the place for this type of question.</p>
<p>Nathan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cecilia</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121157</link>
		<dc:creator>Cecilia</dc:creator>
		<pubDate>Sat, 04 Apr 2009 20:45:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121157</guid>
		<description>I did go back and downgrade my software back to the vzw version .75 and my phone seems to back in working order and back on the warrenty. :)
Like kernal32 I had nothing but problems the few days I had it on my storm I lost ALL of my connections to the internet- browser, email and all others that use the web. I learened a lesson faster is not always better. 
I too will wait for any new offical updates from VZW my advice to those looking to update theirs with the leaked version its reallt not much better other than moves a lil bit faster.</description>
		<content:encoded><![CDATA[<p>I did go back and downgrade my software back to the vzw version .75 and my phone seems to back in working order and back on the warrenty. <img src='http://www.rimarkable.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Like kernal32 I had nothing but problems the few days I had it on my storm I lost ALL of my connections to the internet- browser, email and all others that use the web. I learened a lesson faster is not always better.<br />
I too will wait for any new offical updates from VZW my advice to those looking to update theirs with the leaked version its reallt not much better other than moves a lil bit faster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bluehorseshoe</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121156</link>
		<dc:creator>bluehorseshoe</dc:creator>
		<pubDate>Sat, 04 Apr 2009 20:40:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121156</guid>
		<description>Aside from the memory leak, .113 has been solid and stable for me.</description>
		<content:encoded><![CDATA[<p>Aside from the memory leak, .113 has been solid and stable for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kernel32.dll</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121155</link>
		<dc:creator>kernel32.dll</dc:creator>
		<pubDate>Sat, 04 Apr 2009 19:20:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121155</guid>
		<description>And The Saga Finally Comes To A Close......  So I&#039;m sitting there at dinner after previous posts about this, thinking my phone is fine.  But NO.  I realize I have no browser.  When I open Maps, I get a message saying &quot;Your device is not configured for BES or BIS.  Please contact your provider or system administrator.&quot;

So I try upgrading again to .113 and this time I&#039;ve got my browser back.  Only voila!  All of my contacts are completely gone.  So I restore them from a backup.  Only now, guess what?  NO FVCKING BROWSER AGAIN!  Same message when I launch Maps.

So, finally I decide to repeat a previous act hoping for different results.  I decided to downgrade yet again to .75.  I don&#039;t know why, but this worked.   I have my browser and phone.  The network and carrier data is configured correctly, I have all of my contacts and my Jawbone bluetooth was already configured and working (previously it was present but didn&#039;t work until I deleted and paired with it all over again).

Again, lesson learned.  If it&#039;s not an official release, you should probably keep your pants and wait for the real deal.  Even if it ends up sucking, at least it won&#039;t be a game of Russian roulettte.</description>
		<content:encoded><![CDATA[<p>And The Saga Finally Comes To A Close&#8230;&#8230;  So I&#8217;m sitting there at dinner after previous posts about this, thinking my phone is fine.  But NO.  I realize I have no browser.  When I open Maps, I get a message saying &#8220;Your device is not configured for BES or BIS.  Please contact your provider or system administrator.&#8221;</p>
<p>So I try upgrading again to .113 and this time I&#8217;ve got my browser back.  Only voila!  All of my contacts are completely gone.  So I restore them from a backup.  Only now, guess what?  NO FVCKING BROWSER AGAIN!  Same message when I launch Maps.</p>
<p>So, finally I decide to repeat a previous act hoping for different results.  I decided to downgrade yet again to .75.  I don&#8217;t know why, but this worked.   I have my browser and phone.  The network and carrier data is configured correctly, I have all of my contacts and my Jawbone bluetooth was already configured and working (previously it was present but didn&#8217;t work until I deleted and paired with it all over again).</p>
<p>Again, lesson learned.  If it&#8217;s not an official release, you should probably keep your pants and wait for the real deal.  Even if it ends up sucking, at least it won&#8217;t be a game of Russian roulettte.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kernel32.dll</title>
		<link>http://www.rimarkable.com/blackberry-os-470113-to-be-next-official-firmware-update-for-blackberry-storm/comment-page-1#comment-121143</link>
		<dc:creator>kernel32.dll</dc:creator>
		<pubDate>Fri, 03 Apr 2009 21:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rimarkable.com/?p=4182#comment-121143</guid>
		<description>Celia - Connect your device to your computer.  Do not launch your Desktop Manager.  Go in to your browser and go to http://www.blackberry.com/storm/update

You can then click &quot;Check For Updates&quot; which will then cause your desktop manager to launch (this for me has been the most affective way of handling updates).  At some point you will then be able to downgrade back to the original OS.

Once this process is completed, in your BlackBerry Desktop Manager, go to Backup/Restore.  When you upgraded your OS, it backed up everything first.  Your databases, contacts, perferences, everything.  By default it probably dumped the output file to your My Documents folder.  Just do a restore using that file (you&#039;ll know it when you see it).

This should resolve all of your issues.  Now, all my buddy had to do was revert back to the old OS.  I personally had to do all the steps I just listed in order for me to get my device back to the way it was. 

Oh and by the way, the Verizon guy is a liar and is just enjoying being an a$$hole.  Typical of the lousy in-store experience.  He either didn&#039;t want to be bothered,  or (more than likely)) didn&#039;t konw how to fix it as these are smartphones and are not under lockdown by Verizon.</description>
		<content:encoded><![CDATA[<p>Celia &#8211; Connect your device to your computer.  Do not launch your Desktop Manager.  Go in to your browser and go to <a href="http://www.blackberry.com/storm/update" rel="nofollow">http://www.blackberry.com/storm/update</a></p>
<p>You can then click &#8220;Check For Updates&#8221; which will then cause your desktop manager to launch (this for me has been the most affective way of handling updates).  At some point you will then be able to downgrade back to the original OS.</p>
<p>Once this process is completed, in your BlackBerry Desktop Manager, go to Backup/Restore.  When you upgraded your OS, it backed up everything first.  Your databases, contacts, perferences, everything.  By default it probably dumped the output file to your My Documents folder.  Just do a restore using that file (you&#8217;ll know it when you see it).</p>
<p>This should resolve all of your issues.  Now, all my buddy had to do was revert back to the old OS.  I personally had to do all the steps I just listed in order for me to get my device back to the way it was. </p>
<p>Oh and by the way, the Verizon guy is a liar and is just enjoying being an a$$hole.  Typical of the lousy in-store experience.  He either didn&#8217;t want to be bothered,  or (more than likely)) didn&#8217;t konw how to fix it as these are smartphones and are not under lockdown by Verizon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
