WithGoogle
Latest
Internal emails reveal Google's desperation over Skyhook's Android deal with Motorola
While Skyhook's lawsuit against Google has been ongoing since September, we've yet to hear the latter's side of the story to fight back anti-competition claims. That's all changed now that a Massachusetts state court has published a collection of internal emails from Mountain View, shedding some light on the reasons behind Motorola's -- and apparently Samsung's as well -- abandonment of Skyhook's XPS location service on its Android phones. In particular, soon after the deal was announced in April 2010, an Android product manager became worried that such a deal would pull more manufacturers away from Google's Location Service, thus jeopardizing the company's ability to maintain and improve its location database through continued data collection. "That would be awful for Google," wrote the manager. Fair enough, but here comes the juicy part of the story: in the following month, Google informed Motorola that it wasn't happy with the way Skyhook blends location data from WiFi, GPS, and cellular signal. Or in Google's words: this is data "contamination." Despite Motorola refuting such concern, a week later it informed Skyhook that Google had told Moto that its choice for a third-party location service "renders the device [Droid X] no longer Android Compatible." It's not exactly clear what this compatibility issue is, but it's believed to be the ultimate reason that forced Motorola -- being a close pal of Google -- to drop Skyhook's XPS in favor of Google's Location Service. If you're still not feeling sorry for Skyhook, then note that last month Google called this "a baseless complaint" and a "thinly veiled fishing expedition" for internal Google documents and emails. Funnily enough, one email quotes an Android manager saying it was obvious to phone manufacturers that "we are using compatibility as a club to make them do things we want." Question is: which direction will the club swing now that the two companies are battling it out in court?
LG Optimus 2X review
The world cried out for a dual-core smartphone and LG and NVIDIA answered the call. Actually, the world only ever dreamt about multicore mobile architectures up until late last year, but sometimes that's all it takes to get those zany engineers engineering. So here we are, in early February 2011, beholding the world's first smartphone built around a dual-core processor, the Optimus 2X. This is a landmark handset in more ways than one, however, as its presence on the market signals LG's first sincere foray into the Android high end. Although the company delivered two thoroughly competent devices for the platform with the Optimus S and T in 2010, they were the very definition of mid-range smartphones and the truth is that Samsung, HTC and Motorola were left to fight among themselves for the most demanding Android users' hard-earned rubles. So now that LG's joined their ranks, was the wait worth it? %Gallery-115835%
Skyhook: Google forced Motorola to drop our location service, delay the Droid X
We figured Skyhook's business interference and patent infringement lawsuits against Google would turn up some dirt, and we didn't have long to wait: the location-services company's complaint flatly alleges that Google's Andy Rubin ordered Motorola's Sanjay Jha to "stop ship" on the Droid X because it used Skyhook's XPS positioning system instead of Google Location Services, a tiff that ultimately delayed the phone's release while Moto reworked the software and dropped Skyhook entirely. Following that, Skyhook claims that Google then went after an unidentified "Company X" (likely Samsung) and forced it to drop XPS as well -- which would certainly explain why Samsung's Galaxy S phones have WiFi positioning turned off by default, unlike every other Android phone. Ouch. If you're thinking that makes no sense because Android is "open," well, you might have another think coming -- Skyhook claims that Google's decisions to allow access to Android Market and its branded apps are an entirely subjective ruse based on something called the Compliance Definition Document, which can be "arbitrarily" interpreted any way Google wants with no recourse. Skyhook says that Google has now told Android OEMs that they're required to use Google Location Services, preventing Skyhook from fulfilling its contracts and costing the company millions in expected royalties. Now, this is Skyhook's side of the story and we're sure Google will make a persuasive argument of its own, but let's just back up for a moment here and point out the obvious: Google's never, ever come out and clearly said what's required for devices to gain access to Android Market and the branded apps like Gmail -- even though we've been directly asking about those requirements since Android first launched. Remember when Andy Rubin told us that there would be full-fledged "Google Experience" phones with no carrier or handset manufacturer limitations? Or when we were told that phones with skins like HTC Sense or additional features like Exchange integration wouldn't have Google branding? And then all of that turned out to be a lie? Yes, Android might be "open" in the sense that the source code is available, but there's no doubt Google's wielded incredible power over the platform by restricting access to Market and its own apps -- power that hasn't been used to prevent carrier-mandated bloatware or poorly-done manufacturer skinning, but has instead apparently been used to block legitimate competitors like Skyhook from doing business. We're dying to hear Google's side of this story and fill in some of the gaps -- and you can bet we're digging as hard as we can for more info. Stay tuned, kids.
HTC's Sense UI not coming to any "Google" branded phones
We've got some good and bad news... mostly bad, though. First, the good news: HTC is looking into finding a way to bring its new Sense UI -- the one featured prominently in the new Hero -- to its non-Google branded Android devices, such as Canadian carrier Roger Wireless' Magic. Unfortunately, and this is the bad news, even that's not a sure thing, and as you can probably guess from the wording, any phone that's got the "with Google" branding, like T-Mobile USA's G1 and myTouch 3G, won't be getting a chance at all due to the same licensing terms that prevented Microsoft Exchange clients on those same phones. Them's the breaks, folks, but we're sure some hacker with enough know-how will bypass the silly restrictions and do it anyway.
