<?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>Litui.Net &#187; e911</title>
	<atom:link href="http://www.litui.net/archives/tag/e911/feed" rel="self" type="application/rss+xml" />
	<link>http://www.litui.net</link>
	<description></description>
	<lastBuildDate>Thu, 19 Aug 2010 22:41:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Rogers and its e911 Commitment to the CRTC</title>
		<link>http://www.litui.net/archives/850</link>
		<comments>http://www.litui.net/archives/850#comments</comments>
		<pubDate>Tue, 09 Feb 2010 03:15:50 +0000</pubDate>
		<dc:creator>litui</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Politics]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[911]]></category>
		<category><![CDATA[crtc]]></category>
		<category><![CDATA[crtc 2009-40]]></category>
		<category><![CDATA[dream]]></category>
		<category><![CDATA[e9-1-1]]></category>
		<category><![CDATA[e911]]></category>
		<category><![CDATA[htc dream]]></category>
		<category><![CDATA[htc magic]]></category>
		<category><![CDATA[magic]]></category>
		<category><![CDATA[phase ii]]></category>
		<category><![CDATA[rogers]]></category>

		<guid isPermaLink="false">http://www.litui.net/?p=850</guid>
		<description><![CDATA[It seems there may be more to this whole e911 issue than Rogers is letting on. By way of Carson Brown comes a link to Telecom Regulatory Policy CRTC 2009-40: Implementation of wireless Phase II E9-1-1 service. Phase I, defined in 2003, provides ILECs (Incumbent Local Exchange Carriers, aka &#8216;local telephone companies&#8217;) a 911 caller&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>It seems there may be more to this whole e911 issue than Rogers is letting on.</p>
<p>By way of <a href="http://scs.carleton.ca/~cbrown7">Carson Brown</a> comes a link to <a href="http://www.crtc.gc.ca/eng/archive/2009/2009-40.htm">Telecom Regulatory Policy CRTC 2009-40</a>: <em>Implementation of wireless Phase II E9-1-1 service</em>.  Phase I, defined in <a href="http://www.crtc.gc.ca/eng/archive/2003/dt2003-53.htm">2003</a>, provides ILECs (Incumbent Local Exchange Carriers, aka &#8216;local telephone companies&#8217;) a 911 caller&#8217;s location cell within the mobile network and phone number. Phase II E9-1-1 service appears to be the evolution of that technology given the prevalence of GPS in mobile phones:</p>
<blockquote><p>The level of information required by Telecom Decision 2003-53 is referred to as Phase I. Phase II, which has not yet been widely implemented in Canada and is the subject of this decision, provides <abbr title="Public Safety Answering Point">PSAP</abbr>s with Phase I information plus more accurate longitudinal and latitudinal (X,Y) information regarding the location of wireless E9-1-1 callers.<br />
- CRTC 2009-40/Introduction/2</p></blockquote>
<p>Further, this technology requires that GPS functionality be automatically enabled:</p>
<blockquote><p>automatic enabling of cell phone Global Positioning System (GPS) functionality where GPS technology is being used; &#8211; CRTC 2009-40/Issues/I/7</p></blockquote>
<p>This is subdivided into two stages of implementation:</p>
<ol>
<li>&#8220;Provision of X,Y coordinate information and location system parameters that <abbr title="Public Safety Answering Point">PSAP</abbr>s use to determine a caller&#8217;s location.&#8221; &#8211; CRTC 2009-40/Issues/I/7</li>
<li>&#8220;Provision of mid-call location updates, plus provision of wireless Phase II E9-1-1 service for roamers and unsubscribed handsets, to be deployed as technology solutions become available.&#8221; &#8211; CRTC 2009-40/Issues/I/7</li>
</ol>
<p>While no strict timeline appears to have been defined for Stage 2 implementation, Stage 1 is very clear:</p>
<blockquote><p>All <abbr title="Wireless Service Provider">WSP</abbr>s are to complete their respective implementation of wireless Phase II Stage 1 E9-1-1 services by 1 February 2010, wherever wireline E9-1-1 service is available across Canada. &#8211; CRTC 2009-40/Issues/III/20/3</p></blockquote>
<p>So it seems that not only has Rogers fallen behind on its ability to provide even a basic <em>Phase I</em> level of wireless e911 service on the HTC Dream and Magic, but they are treading the borderline of failing to meet <em>Phase II</em> Stage 1 implementation timeline demands by the CRTC (and other interested parties) as well.</p>
<p>This might give insight as to why Rogers decided to <a href="http://www.litui.net/archives/796">disable data in late January</a> for HTC Dream and Magic users before their deadline came up, and why they have become increasingly persistent in their warnings, even to the point of <a href="http://www.litui.net/archives/838">hijacking all outbound calls</a>.</p>
<p>This may also explain some of Rogers&#8217;s misgivings about non-standard firmwares as the degree of compliance of 3rd party software to the <em>Phase II</em> requirements can&#8217;t be accounted for by Rogers.</p>
<p>As far as I can tell, however, there is no provision either in the CRTC file or by Rogers themselves for 3rd party hardware.  If an unlocked phone from a 3rd party doesn&#8217;t support Phase II Stage 1 e911 services, what is the process?  Will this regulation allow wireless carriers to lock out &#8220;unauthorized&#8221; hardware?</p>
<p>In light of this information, certain answers given by @<a href="http://www.twitter.com/rogersmary/">RogersMary</a> make a lot more sense:</p>
<blockquote><p>@bradarsenault Not sure. I know we don&#8217;t support unlocked or rooted phones b/c we can&#8217;t guarantee how they device will work on our network.<br />
@mcantelon Hi. We can&#8217;t support rooted/unlocked phone b/c we don&#8217;t know how those devices work on our network. Custs should d/l the bug fix.<br />
@4Lou We cannot support unlocked devices b/c we can&#8217;t guarantee how that will impact the device on our network.<br />
&#8230;</p></blockquote>
<p>The above has been the standard line and has been perplexing to many of us who understand that rooted and unlocked phones as such do not interfere with the network.  If the firmwares are simply not known to work with Phase II Stage 1 e911 services and Rogers is required to have phones on their network comply, however, it makes more sense.</p>
<p>What does this mean for the future of modded phones and even ordering unlocked (standards-compliant) handsets from out-of-country?  Will they be subjected to the same restrictions?</p>
<p>Why can&#8217;t we simply waive our right to Phase II e911 and have this issue solved?</p>
<p>Of note also is that the payment model for e911 services (eg: that they are paid for by the wireless providers) has not changed, and it&#8217;s possible we will see an increase in costs on account of this implementation.</p>
<p>Thanks again to Carson for the link.  It provides much to consider.</p>
<h3>Updates</h3>
<dl>
<dt>2010-02-10 @ 3:00 PM &#8211; Rogers Waiver</dt>
<dd>
<p>Posted by Joniel, <a href="http://www.litui.net/archives/796#comment-2043">not 10 minutes ago</a>, a link to a new <a href="http://www.rogers.com/HTCwaiver">911 waiver form</a> for HTC Dream and Magic customers who refuse to &#8220;upgrade&#8221;.</p>
<p>I really have to wonder if this (fairly well viewed) post had any impact on the decision, but I guess I&#8217;ll never know.</p>
</dd>
</dl>
]]></content:encoded>
			<wfw:commentRss>http://www.litui.net/archives/850/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Latest in the Rogers debacle &#8211; All calls redirected</title>
		<link>http://www.litui.net/archives/838</link>
		<comments>http://www.litui.net/archives/838#comments</comments>
		<pubDate>Sun, 07 Feb 2010 22:56:22 +0000</pubDate>
		<dc:creator>litui</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[911]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[call redirection]]></category>
		<category><![CDATA[dream]]></category>
		<category><![CDATA[e911]]></category>
		<category><![CDATA[htc]]></category>
		<category><![CDATA[magic]]></category>
		<category><![CDATA[rogers]]></category>
		<category><![CDATA[rogers mandatory update]]></category>
		<category><![CDATA[sapphire]]></category>

		<guid isPermaLink="false">http://www.litui.net/?p=838</guid>
		<description><![CDATA[It seems that now, after disconnecting data and weeks of harassment of Dream and Magic customers to update their phones due to the 911 issue (which I&#8217;ll remind you doesn&#8217;t affect those of us who are on unofficial mods with Android 1.6), Rogers has taken their methods to the next level. They&#8217;ve begun diverting outbound [...]]]></description>
			<content:encoded><![CDATA[<p>It seems that now, after disconnecting data and weeks of harassment of Dream and Magic customers to update their phones due to the 911 issue (which I&#8217;ll remind you doesn&#8217;t affect those of us who are on unofficial mods with Android 1.6), Rogers has taken their methods to the next level.  They&#8217;ve begun <a href="http://www.iwantmyonepointsix.com/?p=194">diverting outbound telephone calls</a> from phones that they still have marked (by whatever means they&#8217;re marking them) as non-updated in their systems.</p>
<p>The <a href="http://forum.xda-developers.com/showthread.php?p=5560346#post5560346">first report of this today</a> on the <a href="http://forum.xda-developers.com/showthread.php?t=622106">XDA-Developers Forum Rogers Mandatory Update thread</a> clearly states that this redirect is, in a spectacle of comic irony, preventing 911 calls as well.  As <em>ben.selinger</em> put it [minor punctuation fixes]:</p>
<blockquote><p>Rogers is rescanning phones again and blacklisting non-1.5 phones. The voice services are then being diverted to Rogers support.  Better, they&#8217;re diverting 911 calls!  When I realized they&#8217;d diverted my first call, I promptly hung up and called 911 to see if it would also be diverted. It was.</p></blockquote>
<p><a href="http://forum.xda-developers.com/showthread.php?p=5563201#post5563201">Later in the thread</a>, and similarly <a href="http://twitter.com/RogersMary/status/8771088076">on Twitter</a>, @<a href="http://twitter.com/RogersMary/">RogersMary</a> states:</p>
<blockquote><p>Hi This is Mary with Rogers online communication team. To clarify, this is not so. Safety is always our primary concern and while customers are being directed to Care to ensure they are aware of the bug fix, this in no way impacts their ability to call 911 direct.</p></blockquote>
<p>Perhaps it hasn&#8217;t been completely tested, or if 911 was being redirected it&#8217;ll be solved shortly, but I for one am willing believe ben.selinger.  I don&#8217;t see any real reason why someone would lie about that.  Additional confirmation would be useful though.  If anyone has encountered this redirect on a call they&#8217;ve had to place to 911, please post here.</p>
<p>Fortunately, still running CyanogenMod 1.4.13 with bcrook&#8217;s <a href="http://briancrook.ca/magic/rogers/Rogers-netfix3-dream-signed.zip">netfix3-dream</a> after having had Rogers perform a &#8220;network refresh&#8221; back when they were allowing us to, my data still works and I have not had calls redirected.  I still, however, get the phone calls and text messages at least once every day telling me to &#8220;upgrade&#8221;.</p>
<p>This latest move on Rogers&#8217; part is just nonsensical.  It&#8217;s bad enough that we&#8217;ve had our data plans disabled, but now to not even be able to make outbound phone calls?  Ridiculous.  Yes, we get it Rogers, you take 911 seriously and don&#8217;t want to be blamed for a failure to act on your part (in spite of being 4 months late to act), but pissing off your customers is not the way to do it.  The fact is that those of us who refuse to downgrade to Rogers/HTC&#8217;s 1.5 firmware from our up-to-date, fully functional, and 911-friendly 1.6 and up firmwares are being punished by Rogers for not complying in the campaign to make them look good in the face of 4 months of neglect.</p>
<p>I&#8217;m not on board, Rogers.</p>
<h3>Update: Some links to other mentions and discussions of the issue:</h3>
<ul>
<li><a href="http://howardforums.com/showthread.php?t=1617898" title="Howard Forums: Rogers Diverting All Calls, INCLUDING 911 Calls for Some Unupdated Dream/Magic">Howard Forums</a></li>
<li><a href="http://techreview.eatuniverse.net/2010/01/24/rogers-disconnects-data-services-to-g1-users/">Blistov&#8217;s Tech Review: Rogers disconnects data services to G1 users! Rogers tech support swamped with angry calls <img src='http://www.litui.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  !</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.litui.net/archives/838/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Rogers Mandatory Update Debacle</title>
		<link>http://www.litui.net/archives/796</link>
		<comments>http://www.litui.net/archives/796#comments</comments>
		<pubDate>Tue, 26 Jan 2010 04:40:15 +0000</pubDate>
		<dc:creator>litui</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Politics]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[911]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[canada]]></category>
		<category><![CDATA[cyanogenmod]]></category>
		<category><![CDATA[dream]]></category>
		<category><![CDATA[e911]]></category>
		<category><![CDATA[htc]]></category>
		<category><![CDATA[htc dream]]></category>
		<category><![CDATA[htc magic]]></category>
		<category><![CDATA[magic]]></category>
		<category><![CDATA[mandatory update]]></category>
		<category><![CDATA[RCI.B]]></category>
		<category><![CDATA[rogers]]></category>
		<category><![CDATA[rogers communications]]></category>
		<category><![CDATA[rogers update]]></category>

		<guid isPermaLink="false">http://www.litui.net/?p=796</guid>
		<description><![CDATA[Unless you happen to be a user of an HTC Dream or Magic smartphone on Rogers (or someone I rant at on a daily basis) you probably haven&#8217;t heard much background about my latest beef with Rogers. Here&#8217;s the scoop broken down into detail as much as possible for those who may not be in [...]]]></description>
			<content:encoded><![CDATA[<p>Unless you happen to be a user of an <a href="http://en.wikipedia.org/wiki/Htc_dream" title="Wikipedia: HTC Dream">HTC Dream</a> or <a href="http://en.wikipedia.org/wiki/Htc_magic" title="Wikipedia: HTC Magic">Magic</a> smartphone on <a href="http://en.wikipedia.org/wiki/Rogers_Wireless" title="Wikipedia: Rogers Wireless">Rogers</a> (or someone I rant at on a daily basis) you probably haven&#8217;t heard much background about my latest beef with Rogers.  Here&#8217;s the scoop broken down into detail as much as possible for those who may not be in the loop.</p>
<h3>Android and HTC Phones</h3>
<p>Before I get into the details, it helps to know some things about the above phones.  First, these are both <a href="http://en.wikipedia.org/wiki/Android_%28operating_system%29" title="Wikipedia: Android (operating system)">Android</a> phones.  Android is a phone operating system that was released over a year ago by Google.  The HTC Dream (aka: the G1) was the first Android phone released in October of 2008.  Since that time Android has been updated constantly and new versions of the operating system have been released with new features and bugfixes.  The HTC Magic (aka: Sapphire/MyTouch) was the second phone released (in April of 2009).  That phone was released with Android 1.5 (cupcake) on T-Mobile in the US.  In May, the T-Mobile G1 (HTC Dream) was given an update to Android 1.5 as well.</p>
<p>Rogers didn&#8217;t carry either of these phones until June, 2009.  Prior to Rogers carrying these phones there had already begun to be a large &#8216;modding&#8217; community whose purpose was generally to modify existing firmware to operate better, allow more user control, and fix bugs in the operating system that were being neglected by carriers.  When Rogers brought Android phones to its network, it was only natural that the modding popularity would spread up North.  One popular modification is <a href="http://wiki.cyanogenmod.com/">CyanogenMod</a> which is currently based on Android 1.6 (Donut).  In spite of the fact that T-Mobile in the US has <a href="http://www.cnet.com/8301-19736_1-10365229-251.html"><em>already</em> distributed Android 1.6 for their G1 and myTouch phones</a>, HTC and Rogers made a joint statement that <a href="http://www.hotmobilebuzz.com/2009/12/no-android-16-to-rogers-htc-dream-magic.html">the Dream and Magic would not be getting 1.6 upgrades</a>.</p>
<p>This left many Rogers Dream and Magic users installing 3rd party modifications (including CyanogenMod) in order to gain the Android 1.6 experience their providers refused to give them.  The tradeoff?  No operating system support from Rogers.  This can be likened somewhat to Jailbreaking and modifying an iPhone.</p>
<h3>The 911 Issue</h3>
<p>On January 15 of this year, I (and many other users of the Dream and Magic phones) received a text message from Rogers.  It read as follows:</p>
<blockquote><p>Rogers/Fido service message: URGENT 911 Calls: Please disable GPS location on your HTC Dream device to ensure all 911 calls complete. HTC is urgently working on a software upgrade and we will provide details shortly so you can re-enable GPS. Instructions: Select Menu &#8211; Select Settings &#8211; Select Location &#8211; Uncheck Enable GPS Satellite</p></blockquote>
<p>This is, indeed, an urgent bug.  The real surprise was that neither Rogers nor HTC had fixed it yet considering it had been fixed <em>4 months prior</em> in the Android Open Source Project.  <a href="http://android.git.kernel.org/?p=platform/frameworks/base.git;a=commit;h=610419eae1d35b4da27b91de2dc98982d43c7deb" title="AOSP: Git commit for 911 GPS issue">The fix</a> was submitted on September 17, 2009:</p>
<blockquote><pre>author	Mike Lockwood &lt;nobody@android.com&gt;
	 Thu, 17 Sep 2009 14:29:17 +0000 (07:29 -0700)
committer	The Android Open Source Project &lt;initial -contribution@android.com&gt;
	 Thu, 17 Sep 2009 14:29:17 +0000 (07:29 -0700)
...
AI 151388: Fix null pointer exceptions that can occur if the GPS is started due to E911</pre>
</blockquote>
<p>From there, the patch would be in every subsequent version of Android.  Immediately after entering Android Open Source, the patch was <a href="http://code.google.com/p/cyanogenmod/issues/detail?id=388#c15" title="Comment #15 on CyanogenMod issue #388: Reboot when caling 911">incorporated into CyanogenMod</a> and other mods.</p>
<p>In fact, this was one of the important fixes discussed by T-Mobile in their <a href="http://www.t-mobile.com/company/PressReleases_Article.aspx?assetName=Prs_Prs_20091001&#038;title=DETAILS%20ON%20ANDROID%201.6%20%28DONUT%29%20ROLLOUT" title="T-Mobile: 1.6 Press Release">press release for 1.6</a> back in October [emphasis added]:</p>
<blockquote><p>The rollout of Android 1.6 (Donut) to T-Mobile&#8217;s G1 and myTouch 3G customers is now underway, and provides new features and software enhancements. <strong>The update also includes an important fix for isolated instances of system reboots after dialing 911.</strong> We have worked with Google and HTC on a solution, and the rollout of Android 1.6 is being accelerated to ensure the system reboot fix is rapidly delivered to our customers.</p></blockquote>
<p>The update was released by HTC as an over-the-air update. Users received notification that there was an update on their phones and had a choice whether or not to install.</p>
<p>This is pretty damning evidence that Rogers has been out of touch not only with the Android community, but other vendors as well.  I&#8217;m inclined to say that HTC dropped the ball on this one too since they were clearly aware of the issue at the time of T-Mobile&#8217;s 1.6 update.</p>
<p>Okay, so large fault on their parts, but fortunately it didn&#8217;t affect me or any of the other individuals who had already upgraded our phones to 1.6 or higher firmware by way of mods.  Clearly Rogers needed to take action to help those of their users who were still on stock Android 1.5.</p>
<h3>The Great Disconnect</h3>
<p>The evening of Friday, January 22, many of the users of Rogers Dream and Magic devices (though <a href="http://islandlinux.org/story/rogers-turned-internet-access-my-htc-dream" title="Island Linux: Rogers Turned Off Internet Access for my HTC Dream">not all users</a>) received a text message similar to the following:</p>
<blockquote><p>Rogers/Fido Safety Message: URGENT 911 Calls HTC Dream software update: Mandatory software update is now available to help ensure 911 calls are completed from your phone. Please go immediately to rogers.com/dreamsoftwareupdate on your PC to download. In order to help ensure 911 calls are completed internet access will be temporarily disabled on your phone at 01/24/10 6:00AM EST. To minimize loss of internet service, please complete your software update immediately. Upon completion, internet access will be re enabled within 24 hours. For users of Macintosh and Windows 7, please call 1-888-764-3771(1-888-ROGERS1) for update instructions. We apologize for the inconvenience but we prioritize customer safety above all.</p></blockquote>
<p>In short, internet access was to be disabled for all users of HTC Magic and Dream unless an update was completed 24 hours prior to 6AM Sunday morning, January 24.  The &#8216;update&#8217; was a 1.5 firmware with the following main modifications:</p>
<ol>
<li>The requisite 911 fix.</li>
<li>&#8216;Fixes&#8217; to the kernel to prevent exploits from functioning (the kind of &#8216;exploits&#8217; used to allow modders to gain &#8220;root&#8221; and install their own mods)</li>
<li>A new radio and recovery image that continue (in the same vein as the original firmware) to prevent modders from flashing new versions of Android onto the phone.</li>
<li><a href="http://en.wikipedia.org/wiki/Sense_UI">SenseUI</a>, an &#8220;improvement&#8221; by HTC on the Android interface.  There is some contention over whether or not it is actually an improvement, and many prefer the simplicity of the original Android interface.</li>
</ol>
<p>In short, while providing a much belated and important fix along with some interface changes to those on their stock firmware, Rogers is imposing a downgrade (and preventing re-modding) upon those of us who <strong>do not</strong> have the 911 issue and <strong>do not</strong> want or desire HTC Sense UI (some users already have Sense UI through other 3rd party modifications).</p>
<p>Of course, come Sunday morning those of us who had not installed the <a href="http://forum.xda-developers.com/showthread.php?t=622106">Rogers Mandatory Update</a> or <a href="http://forum.xda-developers.com/showthread.php?t=592856">CursorSense 1.2</a> (a mod based on the Mandatory Update) were left without data access on our phones.</p>
<p>The most official reason for the forced disconnect comes from @<a href="http://twitter.com/rogersmary">RogersMary</a>:</p>
<blockquote><p>You&#8217;re right that disabling GPS fixes the issue and allows 911 calls to complete. So does disabling data.</p></blockquote>
<p>While it&#8217;s understandable that Rogers did have an obligation to take action and a responsibility to its customers, what&#8217;s not clear is why those of us with a fixed version of Android are being subjected to the same treatment.  If Rogers has the ability to detect out-of-date firmware on their network, it should be equally easy to detect more recent firmware and exempt it from disconnection.</p>
<p>In response to my assertion that all 1.6 firmwares were safe and that CyanogenMod had this fix already, I was told by @RogersMary,</p>
<blockquote><p>Hi Aron. I can&#8217;t offer assistance on rooted devices. For customer safety, all customers need the 1.5 fix downloaded to device.</p></blockquote>
<p>I can accept that no assistance or support would be granted to someone using a non-standard version of Android, however I was not asking for support any more than I asked to have my data connection disabled.  The only thing being asked for is the data service that is already being paid for.</p>
<p>To be fair, in an <a href="http://www.mobilemag.com/2010/01/25/rogers-announces-htc-911-fix-magic-1-5-with-sense-ui/">extended version of the announcement</a>, Rogers has stated that they will be offering one month of data service in compensation for the outage, but again there is no provision for those of us who do not require the update to have working 911 service.  Compensation is not service.</p>
<h3>Reconnection</h3>
<p>There are still many questions regarding the disconnection and reconnection process.  Callers to technical support have gotten mixed answers as to whether they can have their connections reactivated while using non-standard firmware or if a reinstated connection will last.  It seems not every support agent is even familiar with the situation.</p>
<p>What is clear is that this can legally be no more than a temporary measure.  As Ben Selinger put it in <a href="http://techreview.eatuniverse.net/2010/01/24/rogers-disconnects-data-services-to-g1-users/" title="Rogers disconnects data services to G1 users! Rogers tech support swamped with angry calls :) !">his blog post yesterday</a>,</p>
<blockquote><p>Some of you may recall legal precedence for this kind of issue, dating waaay back to the 70’s when Bell (then Northern Telecom) tried to force its customers to use Bell branded phones, and tried to attach a special fee to modem/fax use.  The courts ruled against Bell, and the CRTC jumped in and made all sorts of rules to prevent telecom’s from requiring proprietary hardware, on standardized networks.  This does, legally, carry over to GSM carriers.   GSM is GSM.  If your phone supports GSM on the frequency of a carrier, the carrier must provide a signal.  Period.</p></blockquote>
<p>Rogers would face an uphill battle trying to maintain their hard-line against those who refuse to upgrade and there is already talk in the community of presenting a case to the CRTC.</p>
<h3>Additional Updates</h3>
<dl>
<dt>2010-01-26 @ 12:02 PM &#8211; Additional downsides to the Rogers Mandatory Update</dt>
<dd>
<ul>
<li>SenseUI apparently drains the (already poor) battery on an HTC Dream at a higher rate than the stock firmware does.</li>
<li>Voice dialing not functional for some people after updating.  This makes it illegal in some provinces to make phone calls while driving using these phones.  Hat tip to @<a href="http://twitter.com/IWMOPS">IWMOPS</a> and @<a href="http://twitter.com/gervai5">gervai5</a></li>
<li>Multiple reports of Fido customers having to enable Roaming Mode in order to have access to data after performing the update.</li>
</ul>
</dd>
<dt>2010-01-26 1:53PM &#8211; Free Magic deal called off due to 911 fix?</dt>
<dd>
It seems the <a href="http://mobilesyrup.com/2010/01/09/rogers-to-offer-htc-dream-owners-a-limited-time-opportunity-to-upgrade-to-magic/">Free HTC Magic</a> deal that was available for a limited time to Dream owners has been called off for dubious reasons.  The deal was originally offered by Rogers as a good faith gesture to Dream owners who were disappointed that their devices did not have enough storage space for the Android 2.1 update Rogers was planning for eventual release.  This announcement was made no later than January 9.</p>
<p>We had heard a few days ago that this deal was on pause until the 911 issues were worked out on both the HTC Dream and Magic, which have both been pulled from shelves, but now it seems Rogers is claiming that <strong>the deal only existed due to the 911 issue</strong>.  Remember from my post above that the text message sent out regarding the 911 issue was on January 15, <em>6 days later</em>!</p>
<p>Via <a href="http://www.litui.net/archives/796/comment-page-1#comment-1906">Tyrell&#8217;s comments below</a> come some excerpts from Rogers support emails,</p>
<blockquote><p>I am pleased to inform you that the issue with the HTC Dream has been resolved; as such, the promotional offer for an upgrade to the HTC Magic is no longer available.</p></blockquote>
<blockquote><p>Thank you for your most recent email. I have contacted our technical department and they have advised that in the beginning the 911 issue was only affecting customer with the HTC Dream. However, within hours we received confirmation from HTC that this issue was also affecting the HTC Magic. Once it was brought to our attention that this issue was affecting both devices the promotion was placed on hold until further notice.</p></blockquote>
<p>So, which is it Rogers?  If the promotion only existed because of 911 problems then why didn&#8217;t we hear about the problem sooner?
</dd>
<dt>2010-01-26 4:17 PM &#8211; More confirmation of the cancelled Magic upgrade</dt>
<dd>
From <a href="http://www.iwantmyonepointsix.com/?p=172&#038;cpage=1#comment-271">this comment</a> by Lee:</p>
<blockquote><p>I called into Rogers and asked the CSR about the Dream to Magic upgrade, and was told they are no longer offering it since the mandatory software update fixes the problems the Dream had.</p></blockquote>
<p><strong>Edit:</strong> From <a href="http://www.litui.net/archives/796#comment-1918">Calvin&#8217;s comment below</a> it would seem that the confusion over the Dream to Magic upgrade pause is simply misinformed support staff and that the deal will resume when the 911 issue is resolved.
</dd>
<dt>2010-01-26 4:20 PM &#8211; Additional problems with the mandatory update</dt>
<dd>
Looks like more problems with the new firmware have been observed including:</p>
<blockquote><p>- Fido customers report their phones now constantly say they are roaming (data I believe)<br />
- Some people report various FCs and spontaneous reboots<br />
- One person says he was unable to delete icons from the home screen (including Rogers icons)… has anyone else encountered this?<br />
- Photo gallery error (GBD)<br />
- Task manager “end all” causes FCs (GBD)<br />
- Possible problem with MS Exchange (via Twitter)<br />
- Twitter user XBrav is having problems with freezing, buzzing, and calls not completing.<br />
- Flash player not always working<br />
- Battery possibly draining faster<br />
- Some apps previously available in the marketplace are now not available.</p></blockquote>
<p>More information on <a href="http://www.iwantmyonepointsix.com/?p=172">I Want My One Point Six</a>.</p>
</dd>
<dt>2010-01-27 12:51 PM &#8211; Magic upgrade plan just delayed</dt>
<dd><a href="http://twitter.com/RogersMary/status/8291435067">Tweet</a> from @<a href="http://twitter.com/RogersMary">RogersMary</a> in response to @<a href="http://twitter.com/bcrook88">bcrook88</a>, confirming the purpose of the upgrade and that it&#8217;s just on hold:</p>
<blockquote><p>The upgrade is just temporarily on hold. It was set up for Dream customers who wanted a new OS. Hope that helps.</p></blockquote>
</dd>
<dt>2010-01-28 7:29 PM &#8211; Not much has changed</dt>
<dd>Things still appear to be the same as a couple of days ago, though I hear via rumour that the support tickets are piling up at Rogers.  A couple of nights ago the issue was featured on <a href="http://mobile.slashdot.org/story/10/01/26/2358237/Canadian-Android-Carrier-Forcing-Firmware-Update">Slashdot</a> which sent a lot of hits this way and hopefully increased public awareness of the issue.</p>
<p>In general, Rogers is still telling callers that the update is required and as many tell it, they&#8217;ve stopped issuing network resets/refreshes when asked as well.</dd>
</dl>
]]></content:encoded>
			<wfw:commentRss>http://www.litui.net/archives/796/feed</wfw:commentRss>
		<slash:comments>51</slash:comments>
		</item>
	</channel>
</rss>
