Litui.Net

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 ‘local telephone companies’) a 911 caller’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:

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 PSAPs with Phase I information plus more accurate longitudinal and latitudinal (X,Y) information regarding the location of wireless E9-1-1 callers.
- CRTC 2009-40/Introduction/2

Further, this technology requires that GPS functionality be automatically enabled:

automatic enabling of cell phone Global Positioning System (GPS) functionality where GPS technology is being used; – CRTC 2009-40/Issues/I/7

This is subdivided into two stages of implementation:

1. “Provision of X,Y coordinate information and location system parameters that PSAPs use to determine a caller’s location.” – CRTC 2009-40/Issues/I/7
2. “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.” – CRTC 2009-40/Issues/I/7

While no strict timeline appears to have been defined for Stage 2 implementation, Stage 1 is very clear:

All WSPs 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. – CRTC 2009-40/Issues/III/20/3

So it seems that not only has Rogers fallen behind on its ability to provide even a basic Phase I level of wireless e911 service on the HTC Dream and Magic, but they are treading the borderline of failing to meet Phase II Stage 1 implementation timeline demands by the CRTC (and other interested parties) as well.

This might give insight as to why Rogers decided to disable data in late January 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 hijacking all outbound calls.

This may also explain some of Rogers’s misgivings about non-standard firmwares as the degree of compliance of 3rd party software to the Phase II requirements can’t be accounted for by Rogers.

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’t support Phase II Stage 1 e911 services, what is the process? Will this regulation allow wireless carriers to lock out “unauthorized” hardware?

In light of this information, certain answers given by @RogersMary make a lot more sense:

@bradarsenault Not sure. I know we don’t support unlocked or rooted phones b/c we can’t guarantee how they device will work on our network.
@mcantelon Hi. We can’t support rooted/unlocked phone b/c we don’t know how those devices work on our network. Custs should d/l the bug fix.
@4Lou We cannot support unlocked devices b/c we can’t guarantee how that will impact the device on our network.
…

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.

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?

Why can’t we simply waive our right to Phase II e911 and have this issue solved?

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’s possible we will see an increase in costs on account of this implementation.

Thanks again to Carson for the link. It provides much to consider.

Updates

2010-02-10 @ 3:00 PM – Rogers Waiver

Posted by Joniel, not 10 minutes ago, a link to a new 911 waiver form for HTC Dream and Magic customers who refuse to “upgrade”.

I really have to wonder if this (fairly well viewed) post had any impact on the decision, but I guess I’ll never know.

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’ll remind you doesn’t affect those of us who are on unofficial mods with Android 1.6), Rogers has taken their methods to the next level. They’ve begun diverting outbound telephone calls from phones that they still have marked (by whatever means they’re marking them) as non-updated in their systems.

The first report of this today on the XDA-Developers Forum Rogers Mandatory Update thread clearly states that this redirect is, in a spectacle of comic irony, preventing 911 calls as well. As ben.selinger put it [minor punctuation fixes]:

Rogers is rescanning phones again and blacklisting non-1.5 phones. The voice services are then being diverted to Rogers support. Better, they’re diverting 911 calls! When I realized they’d diverted my first call, I promptly hung up and called 911 to see if it would also be diverted. It was.

Later in the thread, and similarly on Twitter, @RogersMary states:

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.

Perhaps it hasn’t been completely tested, or if 911 was being redirected it’ll be solved shortly, but I for one am willing believe ben.selinger. I don’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’ve had to place to 911, please post here.

Fortunately, still running CyanogenMod 1.4.13 with bcrook’s netfix3-dream after having had Rogers perform a “network refresh” 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 “upgrade”.

This latest move on Rogers’ part is just nonsensical. It’s bad enough that we’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’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’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.

I’m not on board, Rogers.

Update: Some links to other mentions and discussions of the issue:

• Howard Forums
• Blistov’s Tech Review: Rogers disconnects data services to G1 users! Rogers tech support swamped with angry calls !

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’t heard much background about my latest beef with Rogers. Here’s the scoop broken down into detail as much as possible for those who may not be in the loop.

Android and HTC Phones

Before I get into the details, it helps to know some things about the above phones. First, these are both Android 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.

Rogers didn’t carry either of these phones until June, 2009. Prior to Rogers carrying these phones there had already begun to be a large ‘modding’ 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 CyanogenMod which is currently based on Android 1.6 (Donut). In spite of the fact that T-Mobile in the US has already distributed Android 1.6 for their G1 and myTouch phones, HTC and Rogers made a joint statement that the Dream and Magic would not be getting 1.6 upgrades.

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.

The 911 Issue

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:

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 – Select Settings – Select Location – Uncheck Enable GPS Satellite

This is, indeed, an urgent bug. The real surprise was that neither Rogers nor HTC had fixed it yet considering it had been fixed 4 months prior in the Android Open Source Project. The fix was submitted on September 17, 2009:

author	Mike Lockwood <nobody@android.com>
	 Thu, 17 Sep 2009 14:29:17 +0000 (07:29 -0700)
committer	The Android Open Source Project <initial -contribution@android.com>
	 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

From there, the patch would be in every subsequent version of Android. Immediately after entering Android Open Source, the patch was incorporated into CyanogenMod and other mods.

In fact, this was one of the important fixes discussed by T-Mobile in their press release for 1.6 back in October [emphasis added]:

The rollout of Android 1.6 (Donut) to T-Mobile’s G1 and myTouch 3G customers is now underway, and provides new features and software enhancements. The update also includes an important fix for isolated instances of system reboots after dialing 911. 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.

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.

This is pretty damning evidence that Rogers has been out of touch not only with the Android community, but other vendors as well. I’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’s 1.6 update.

Okay, so large fault on their parts, but fortunately it didn’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.

The Great Disconnect

The evening of Friday, January 22, many of the users of Rogers Dream and Magic devices (though not all users) received a text message similar to the following:

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.

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 ‘update’ was a 1.5 firmware with the following main modifications:

1. The requisite 911 fix.
2. ‘Fixes’ to the kernel to prevent exploits from functioning (the kind of ‘exploits’ used to allow modders to gain “root” and install their own mods)
3. 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.
4. SenseUI, an “improvement” 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.

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 do not have the 911 issue and do not want or desire HTC Sense UI (some users already have Sense UI through other 3rd party modifications).

Of course, come Sunday morning those of us who had not installed the Rogers Mandatory Update or CursorSense 1.2 (a mod based on the Mandatory Update) were left without data access on our phones.

The most official reason for the forced disconnect comes from @RogersMary:

You’re right that disabling GPS fixes the issue and allows 911 calls to complete. So does disabling data.

While it’s understandable that Rogers did have an obligation to take action and a responsibility to its customers, what’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.

In response to my assertion that all 1.6 firmwares were safe and that CyanogenMod had this fix already, I was told by @RogersMary,

Hi Aron. I can’t offer assistance on rooted devices. For customer safety, all customers need the 1.5 fix downloaded to device.

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.

To be fair, in an extended version of the announcement, 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.

Reconnection

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.

What is clear is that this can legally be no more than a temporary measure. As Ben Selinger put it in his blog post yesterday,

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.

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.

Additional Updates

2010-01-26 @ 12:02 PM – Additional downsides to the Rogers Mandatory Update

• SenseUI apparently drains the (already poor) battery on an HTC Dream at a higher rate than the stock firmware does.
• 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 @IWMOPS and @gervai5
• Multiple reports of Fido customers having to enable Roaming Mode in order to have access to data after performing the update.

2010-01-26 1:53PM – Free Magic deal called off due to 911 fix?

It seems the Free HTC Magic 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.

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 the deal only existed due to the 911 issue. Remember from my post above that the text message sent out regarding the 911 issue was on January 15, 6 days later!

Via Tyrell’s comments below come some excerpts from Rogers support emails,

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.

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.

So, which is it Rogers? If the promotion only existed because of 911 problems then why didn’t we hear about the problem sooner?

2010-01-26 4:17 PM – More confirmation of the cancelled Magic upgrade

From this comment by Lee:

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.

Edit: From Calvin’s comment below 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.

2010-01-26 4:20 PM – Additional problems with the mandatory update

Looks like more problems with the new firmware have been observed including:

- Fido customers report their phones now constantly say they are roaming (data I believe)
- Some people report various FCs and spontaneous reboots
- One person says he was unable to delete icons from the home screen (including Rogers icons)… has anyone else encountered this?
- Photo gallery error (GBD)
- Task manager “end all” causes FCs (GBD)
- Possible problem with MS Exchange (via Twitter)
- Twitter user XBrav is having problems with freezing, buzzing, and calls not completing.
- Flash player not always working
- Battery possibly draining faster
- Some apps previously available in the marketplace are now not available.

More information on I Want My One Point Six.

2010-01-27 12:51 PM – Magic upgrade plan just delayed

Tweet from @RogersMary in response to @bcrook88, confirming the purpose of the upgrade and that it’s just on hold:

The upgrade is just temporarily on hold. It was set up for Dream customers who wanted a new OS. Hope that helps.

2010-01-28 7:29 PM – Not much has changed

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 Slashdot which sent a lot of hits this way and hopefully increased public awareness of the issue.

In general, Rogers is still telling callers that the update is required and as many tell it, they’ve stopped issuing network resets/refreshes when asked as well.

The company I work for, Cansel Survey Equipment runs a network of Trimble GPS base stations across Canada in multiple VRS configurations. This network (Can-Net) is powered on the backend by Trimble Infrastructure software. I’ve been integrating around this software for about 2 years now.

Integration and Abstraction

While performing admirably at its intended job (many of the details of which still elude me as I’m no geomatics engineer) the software can be a little monolithic. It works as advertised, make no mistake, but its UI is a bit clunky and it doesn’t seem to integrate well into other applications without a great deal of massaging. [Please Note: I say this with respect for the fact that the software is easily the best available for GPS/GNSS infrastructure and it does seem as though Trimble is making strides towards modernizing their applications.]

One of my main goals with regard to the infrastructure software has been (while working within and around the known limitations of the software) to abstract account management, reporting, and our internal tech support processes from staff access to the actual servers themselves. There are many reasons why this is necessary in an operation this size:

Automation

It can be very difficult for staff to manage sales and account terms in ERP software alongside user accounts in the GPS Infrastructure. Automation is necessary to ensure that customers are getting the accounts and access they paid for and freeloaders are kept out.

Accountability

Having user access to the database abstracted through a custom management tool means a greater level of logging of historic changes to user access tables and moderation of the types of changes that can be made.

Stability

More staff accessing the servers means a greater possibility of staff accidentally closing the server applications (much of the software runs windowed) and making problematic changes. These sorts of things can interrupt end-user access. Abstraction means greater regulation of what software runs on the servers and the resources used by that software.

Security

Giving direct access to staff invites unintended use. Since simply opening a web browser to a questionable page in Windows can result in virus/malware infection it’s important to keep the list of users with access to the actual servers to a minimum.

This necessity resulted in the ongoing programming of an intranet web application (written primarily in Ruby on Rails) which I may discuss in more detail in another post.

Bolt-ons

One of the roadblocks in the abstraction process has been the lack of useful real-time output from the infrastructure software for monitoring purposes. Access logging occurs only after a user logs off. This has made it necessary for our technical support to call the server admins to obtain information on whether or not a station is streaming data or a user is online. This is not ideal and for reasons stated above, it’s even less ideal to give them server access simply to check the online users list.

Bolt-on #1: Google Maps

While not my idea, this was a good choice for (near) real-time stationary station connectivity status.  Using Google Maps allows not only our staff, but all users and the general public (required by Google’s terms of use) the ability to check our station connectivity status.

My implementation uses protocols available in the infrastructure software to obtain a list of stations and logs that to a static file on a periodic basis. This allows me to place the file off the servers (better for security) as well as to provide a very quick-loading source of data for the Google map (the server’s own protocols for obtaining this data are insanely slow).

I have a plan to implement more up-to-date station statistics to our tech support staff using a means other than Google Maps, but more on that another time.

Bolt-on #2: Who’s Online?

As mentioned earlier, getting a list of the users currently connected to our system requires access to the server. In particular, access to the User Interface software for Trimble’s NTRIP Caster service. The UI provides usernames of connected users, amounts of data transferred, mountpoints (data streams), source IP addresses and source ports. Unfortunately, owing to the fact that many of our accounts have serialized alphanumeric usernames (an important part of our ERP integration) the username itself doesn’t tell us much about who is connected. Ideally, we need an approach that allows us to cross-reference the usernames with our ERP to provide customer associations and to view the list of users via a management tool running on a separate machine.

I’ve heard of some administrators using screen scraping utilities to provide this data to their customers. This method would require the GUI to be maximized and foremost on the screen at all times. Additionally, the data would be an image (unsortable, unfilterable and unusable for anything but display).

My method requires a little more diligence but results in the type of data and access we need:

The most important part of this method is the tool TShark, part of the Wireshark package. TShark and Wireshark are network packet analysis tools. They (with the help of passive packet capturing tools) can apply filters to network traffic in realtime and output specific information about the data. For this purpose, I set up TShark to run realtime analysis on the same system running the NTRIP Caster, monitor the same ports, filter out HTTP Authentication data (NTRIP is based on HTTP and uses basic auth) on those ports and produce log files of selected fields (namely: source IP, source port, and username/password).

I then wrote a script on a separate server that obtains these authentication log files, uses SNMP to obtain a list of source IPs and ports for current connections to the NTRIP caster, compares the IPs and ports to those in the log files, and loads the most recent matching usernames into an array. It then does some database magic to match the usernames to customers and outputs the result as a JSON file which can be parsed using libraries available in most programming languages. This script is run by Cron every minute.

Using an AJAX intranet web page that reloads and parses the JSON file every minute, I can provide a list of current users to our technical support staff that’s internal to our company network and does not require direct access to the servers.

[Edit: It should be noted that TShark chews up RAM pretty quickly.  I have it restarting on a daily basis so it doesn't eat all the system memory.  There are probably other tools that can do the job, or you could write a custom parser that's more efficient if that's a concern.  I chose TShark because it was the easiest solution to implement out-of-the-box.]

I’m really late to this news, but as it bugs the hell out of me I’ll post it anyway.

It looks like Sony was finally victorious over popular console and import game sales site, Lik-Sang.com. On Oct 24, they put up an out of business notice and closed their doors.

What’s interesting though is that they released the names of some of the people in Europe who were first to buy import PSP’s through them and many of them were top Sony Europe execs. Oh, the joys of hypocrisy.

Read on if you haven’t already:

Lik-Sang.com Out of Business due to Multiple Sony Lawsuits
Tue Oct 24 2006 21:58:51 Hong Kong Time – Corporate Info

OUT OF BUSINESS NOTICE

Hong Kong, October 24th of 2006 – Lik-Sang.com, the popular gaming retailer from Hong Kong, has today announced that it is forced to close down due to multiple legal actions brought against it by Sony Computer Entertainment Europe Limited and Sony Computer Entertainment Inc. Sony claimed that Lik-Sang infringed its trade marks, copyright and registered design rights by selling Sony PSP consoles from Asia to European customers, and have recently obtained a judgment in the High Court of London (England) rendering Lik-Sang’s sales of PSP consoles unlawful.

As of today, Lik-Sang.com will not be in the position to accept any new orders and will cancel and refund all existing orders that have already been placed. Furthermore, Lik-Sang is working closely with banks and PayPal to refund any store credits held by the company, and the customer support department is taking care of any open transactions such as pending RMAs or repairs and shipping related matters. The staff of Lik-Sang will make sure that nobody will get hurt in the crossfire of this ordeal.

A Sony spokesperson declined to comment directly on the lawsuit against Lik-Sang, but recently went on to tell Gamesindustry.biz that “ultimately, we’re trying to protect consumers from being sold hardware that does not conform to strict EU or UK consumer safety standards, due to voltage supply differences et cetera; is not – in PS3′s case – backwards compatible with either PS1 or PS2 software; will not play European Blu-Ray movies or DVDs; and will not be covered by warranty”.

Lik Sang strongly disagrees with Sony’s opinion that their customers need this kind of protection and pointed out that PSP consoles shipped from Lik-Sang contained genuine Sony 100V-240V AC Adapters that carry CE and other safety marks and are compatible world wide. All PSP consoles were in conformity with all EU and UK consumer safety regulations.

Furthermore, Sony have failed to disclose to the London High Court that not only the world wide gaming community in more than 100 countries relied on Lik-Sang for their gaming needs, but also Sony Europe’s very own top directors repeatedly got their Sony PSP hard or software imports in nicely packed Lik-Sang parcels with free Lik-Sang Mugs or Lik-Sang Badge Holders, starting just two days after Japan’s official release, as early as 14th of December 2004 (more than nine months earlier than the legal action). The list of PSP related Sony Europe orders reads like the who’s who of the videogames industry, and includes Ray Maguire (Managing Director, Sony Computer Entertainment Europe Ltd), Alan Duncan (UK Marketing Director, Sony Computer Entertainment Europe Ltd), Chris Sorrell (Creative Director, Sony Computer Entertainment Europe Ltd), Rob Parkin (Development Director, Sony Computer Entertainment Europe Limited), just to name a few.

“Today is Sony Europe victory about PSP, tomorrow is Sony Europe’s ongoing pressure about PlayStation 3. With this precedent set, next week could already be the stage for complaints from Sony America about the same thing, or from other console manufacturers about other consoles to other regions, or even from any publisher about any specific software title to any country they don’t see fit. It’s the beginning of the end… of the World as we know it”, stated Pascal Clarysse, formerly known as the Marketing Manager of Lik-Sang.com.

“Blame it on Sony. That’s the latest dark spot in their shameful track record as gaming industry leader. The Empire finally ‘won’, few dominating retailers from the UK probably will rejoice the news, but everybody else in the gaming world lost something today.”