Home Industry Deals Google sells Motorola Mobility – but why?

Google sells Motorola Mobility – but why? Featured

Fresh from buying IBM’s server division, Chinese PC giant Lenovo has announced it will acquire the Motorola Mobility smartphone business off Google.

It will pay US$2.91 billion for a business that Google acquired from Motorola in August 2011, for US$12.5 billion. That means Google loses nearly $10 billion – in less than three years. Or does it?

What it does mean Google doesn’t want to be in the smartphone business, which is interesting, given its growing presence in tablets and in lots of other hardware areas. We can only suppose that it’s all too hard and too competitive, and that other pastures are greener.

But there’s a bit more to it than that. When Google bought Motorola Mobility it stressed that the main reason it was doing so was to acquire the many patents that company owned.

Motorola almost invented the mobile phone, and those patents go way back. Lots of rubbish, bit some real gems. The sale to Lenovo does not include those patents, which Goggle will now licence to Motorola.

That makes a bit more sense. Everybody wins. Especially Lenovo, which has an instant entry into mobile markets in the West, where it is barely represented.

Google doesn't care. It's got squillions, gets a couple more, and keeps the patents.

And the mobile phone market outside of China has a new big player.

FREE - SYDNEY & MELBOURNE BUSINESS INTELLIGENCE EVENTS

The Holy Grail of the Business Intelligence (BI) industry – pervasive deployments and widespread end-user adoption – has remained an illusive dream for years. Until now!

REGISTER & SECURE YOU PLACE / BRING A FRIEND

Melbourne - venue Captain Melville’s CBD 2:30 – 6:00pm, Tuesday 28th April

Sydney - venue Redoak CBD 2:30 – 6:00pm, Thursday 30th April

DON'T MISS OUT - MELBOURNE REGISTER NOW!

DON'T MISS OUT - SYDNEY REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Graeme Philipson

Graeme Philipson is senior associate editor at iTWire and editor of sister publication CommsWire. He is also founder and Research Director of Connection Research, a market research and analysis firm specialising in the convergence of sustainable, digital and environmental technologies. He has been in the high tech industry for more than 30 years, most of that time as a market researcher, analyst and journalist. He was founding editor of MIS magazine, and is a former editor of Computerworld Australia. He was a research director for Gartner Asia Pacific and research manager for the Yankee Group Australia. He was a long time IT columnist in The Age and The Sydney Morning Herald, and is a recipient of the Kester Award for lifetime achievement in IT journalism.

Connect