Slashdot Mirror


Skyhook Wireless Sues Google Over Anti-Competitive Practices

dwightk writes "According to a lawsuit brought by Skyhook Wireless, Google allegedly forced Motorola, among other Android handset makers, to use Google's own location services instead of alternatives like Skyhook's. Quoting the lawsuit: 'In complete disregard of its common-law and statutory obligations, and in direct opposition to its public messaging encouraging open innovation, Google wielded its control over the Android operating system ... to force device manufacturers to use its technology rather than that of Skyhook, to terminate contractual obligations with Skyhook, and to otherwise force device manufacturers to sacrifice superior end user experience with Skyhook by threatening directly or indirectly to deny timely and equal access to evolving versions of the Android operating system and other Google mobile applications.'" John Gruber points out another interesting excerpt from the complaint regarding Google's procedure for determining Android compliance, which includes what Skyhook calls an "amorphous outline of additional, non-standardized requirements" that "effectively gives Google the ability to arbitrarily deem any software, feature or function 'non-compatible.'"

6 of 228 comments (clear)

  1. FUD by Anonymous Coward · · Score: 5, Informative

    1) This requirement only applies to Android that is bundled with Google's proprietary apps/services. If you take Android without Google's integration and market... you can use what you want.

    2) There are many alternative markets out there.

    3) You can use alternate location services in apps from the market...

    4) Google tried to work with Skyhook requesting examples of their location data.... Skyhook refused... so since Google couldn't guarantee it would work with their services... etc

  2. It's only partially about Android being "open" by papa_lizard · · Score: 3, Informative
    If you had read the actual jury demand (oh wait, this is Slashdot, nevermind), you would've realized it's not just about Android being sold as "Open". The main things that will probably get Google fried are:
    1. 1. Skyhook had a contract with Motorola to include Skyhook's technology in their handsets. When Google found out, they forced Motorola to breach their contract and replace Skyhook's technology with Google's.
    2. 2. Skyhook had a contract with a company (called "Company X" in the demand) to include Skyhook's technology in their handsets. These handsets, with Skyhook's technology integrated, passed the Android certification tests put forth by Google. Then Google discovered that the handsets weren't using Google's location services, and forced Company X to remove the Skyhook tech or face losing the "Android" certification. (Again, forcing another breach of contract)

    As a result of Google forcing Skyhook's partners to breach their contracts, Skyhook lost millions of dollars of licensing revenue and is seeking reparation.

  3. Re:Fanboys by Space+cowboy · · Score: 3, Informative

    SkyHook had a contract to supply Motorola (worth tens of millions of dollars - lifeblood to a company of that size) and when Andy Rubin (a Google VP) heard about it, he phoned up Motorola. "Conversation" ensued, involving the use of a "stop ship" order to prevent Android from shipping on that Motorola hardware. When the dust settled, Motorola was using Google's location services, not Skyhook's.

    This has nothing to do with Google integrating anything, and it's totally evil. Quote from Google-IO: "If you believe in openness, if you believe in choice, if you believe in innovation from everyone, then welcome to Android" - Vic Gundotra, another Google VP. I don't think so Vic. You and Andy ought to talk...

    Simon.

    --
    Physicists get Hadrons!
  4. Re:Fanboys by Space+cowboy · · Score: 3, Informative

    Source: e-week

    Simon

    --
    Physicists get Hadrons!
  5. Re:Pretty simple by canajin56 · · Score: 3, Informative

    To add further clarification, Skyhook is suing not, as they claim, because Google said you can't use Skyhook. This is false, as Samsung phones come with serveral Skyhook-based apps installed by default, at least on Bell. No, if you read the complaint, Skyhook had a contract with Motorola that said you have to disable Google Location Services as part of the API. Google is correct that disabling the API would mean some apps in the store would not work. They have made the choice that if an Android device cannot run apps from the store even if it's on the correct version of AndroidOS, then it's not allowed on the store. Motorola was not told that they can't use Skyhook, they were told that they can't use it exclusively. Though since Google Location Service was off by default on my phone, I'm inclined to believe that Skyhook is lying when they say Google demanded that GLS be on by default, and impossible to turn off. As far as I know, there is absolutely nothing wrong with a Droid phone that uses Skyhook by default, so long as the user has the option of turning GLS on as well. You're probably even allowed to make it so Skyhook is always on and can't be disabled. But, you can't disable part of the Android API and expect to be compliant.

    --
    ASCII stupid question, get a stupid ANSI
  6. Re:"Deemed non-compatible"? by canajin56 · · Score: 3, Informative

    That's not what happened, though. It's not that Skyhook is incompatible. Skyhook software is allowed. My Droid came with Skyhook software on it, and on the first page with Google Maps bumped to page 2 of the app list. The issue is that Skyhook tried to force Motorola to make Skyhook always on, and make it so the user cannot use Google Location Service, or any software that relies on Google Location Service, such as Google Maps. Google said "no, you can use Skyhook as the default but you are not allowed to disable parts of the AndroidOS API" and Skyhook is crying. The Motorola AndroidOS implementation is what was decided "non-compatible", because they disabled part of the API. It's not Skyhook that's not compatible.

    --
    ASCII stupid question, get a stupid ANSI