• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Google to Acquire Motorola Mobility

It means zilch for the Droid X.

It does mean, though, that we could get Motorola build quality and radios in a Nexus-series phone, though!
 
I just read this. All I can say is...damn. Could this be an 'Apple-esque' move to total vertical integration? Could the Moto build quality be merged with a pure Google experience?

And what does this mean for Samsung, LG, HTC, etc.? I'm sure they didn't view Google as a competitor. With this acquisition, Google now is a competitor.

Lots of potential here; but a lot of unknowns yet.
 
I don't think it will affect the DX, but it does mean that my next phone will also be a Motorola.

Of course, we can always hope that Google will unlock the bootloader...
 
Unlocked bootloader? I don't see that happening. An unencrypted bootloader that can be opened, should the user want to (see the Motorola Xoom for example); that I can see. I think locked bootloaders are here to stay. It seems most of the companies and carriers want the security a locked bootloader brings. It is good that companies are beginning to offer solutions to unlock the bootloader to those who want them (HTC, hopefully Moto, etc.) to further open source development.
 
PACAnesFan said:
Unlocked bootloader? I don't see that happening. An unencrypted bootloader that can be opened, should the user want to (see the Motorola Xoom for example); that I can see. I think locked bootloaders are here to stay. It seems most of the companies and carriers want the security a locked bootloader brings. It is good that companies are beginning to offer solutions to unlock the bootloader to those who want them (HTC, hopefully Moto, etc.) to further open source development.
Click to expand...

I think when most people say "unlocked bootloader" - what they really mean is, a bootloader that can be unlocked. To the best of my knowledge, I don't know of any phone shipping with an unlocked bootloader - even the Nexus series of phones requires the fastboot unlock command to switch the bootloader into an unlocked state.

It is interesting that Google will now be a major player in the phone space. HTC, Samsung, etc. should be scared; Motorola has big manufacturing capabilities and have had some absolutely huge sellers.

I only hope this doesn't turn potential Android handset manufacturers away to pursue Windows Phone where they won't be in direct competition with their mobile OS provider.
 
binary visions said:
I think when most people say "unlocked bootloader" - what they really mean is, a bootloader that can be unlocked. To the best of my knowledge, I don't know of any phone shipping with an unlocked bootloader - even the Nexus series of phones requires the fastboot unlock command to switch the bootloader into an unlocked state.

It is interesting that Google will now be a major player in the phone space. HTC, Samsung, etc. should be scared; Motorola has big manufacturing capabilities and have had some absolutely huge sellers.

I only hope this doesn't turn potential Android handset manufacturers away to pursue Windows Phone where they won't be in direct competition with their mobile OS provider.
Click to expand...

I figured everyone knew what I meant about the bootloader discussion. Just being clear for the sake of discussion.

Although Google says it has informed the other OEMs about the Motorola Mobility purchase, I am sure they can't be too pleased. However, they are heavily invested in Android. I can't see them going to WM7, or developing their own OS in an already crowded market.
 
What it means is that Google can now leverage Moto's patents to defend Android from competitors. While I think this may suck for other manufacturers in some ways, the fact that Google may have saved everyone from being sued out of existence due to patent violations may be worth it.

Hopefully, future versions of the Android OS on Moto phones may be a bit more stock and/or updated more frequently.
 
Exciting and interesting news, nonetheless ;).

This certainly does give hope to some future things that we've all hoped might happen, even if its not retroactive.

I should mention that I purchased my Moto Xoom instead of a Galaxy Tab purely because it was a developer device, akin to the original Droid, and I didn't want to miss-out on the benenfits that come with that (first, early releases of Honeycomb, for example).

Sounds like Google wants to lead by example and this should raise all ships, if you know what I mean.

Cheers!
 
My only concern is that the other manufacturers who use Android will jump ship because Motorola will have an advantage. If they do, that could hurt Android as a whole.
 
PACAnesFan said:
Although Google says it has informed the other OEMs about the Motorola Mobility purchase, I am sure they can't be too pleased. However, they are heavily invested in Android. I can't see them going to WM7, or developing their own OS in an already crowded market.
Click to expand...

While they are invested in Android, most of them are also invested in Windows Phone - HTC, LG, and Samsung all produce WP7 handsets. So, it's not as if they need to drop their existing lines and pick up a totally unfamiliar OS.

We'll see. Frankly, this is a win for me because I don't really love HTC/LG/Samsung handsets, so I'd happily go with a Google handset if it keeps up Motorola's history of great radios and great build quality.
 
Another interesting thing about this is that surely people will say this is the "end of Blur" and that Moto phones will get an AOSP feel now...

But in reality I think there is a better chance that Moto's UI development will have a larger influence on what AOSP is...I expect a more polished AOSP Android to come from this...
 
ylexot said:
"Well, it's not really Moto any more..."

That's the excuse you will hear. ;)
Click to expand...

I don't think it will be an excuse, it will simply be a Google phone with the Moto brand name on it ;)

If they don't encrypt the bootloader (and hopefully kill off blur) I will definitely give Google, I mean Moto, consideration.
 
bouchigo said:
and hopefully kill off blur
Click to expand...

i truly believe the most likely scenario is that future versions of AOSP Android will be influenced by Blur...

it just makes sense...Google just took God knows how many UI developers onto their payroll...if they are going to make Moto use AOSP on their devices then they have two options...

1. Incorporate the Moto UI developers into AOSP UI development causing Blur to influence AOSP
2. layoff all the Moto guys: don't think thats happen
 
Metfanant said:
i truly believe the most likely scenario is that future versions of AOSP Android will be influenced by Blur...

it just makes sense...Google just took God knows how many UI developers onto their payroll...if they are going to make Moto use AOSP on their devices then they have two options...

1. Incorporate the Moto UI developers into AOSP UI development causing Blur to influence AOSP
2. layoff all the Moto guys: don't think thats happen
Click to expand...


1. I could see that happening, but the difference will be that Google won't allow a crappy/bug filled version of blur to be released as Moto has been doing.

2. I'm sure some guys will be let go and only the more essential guys kept, their programming skills haven't really impressed if you ask me.

It's nothing but speculation now; we'll see in about 6 months or so what's really going to happen.
 
bouchigo said:
1. I could see that happening, but the difference will be that Google won't allow a crappy/bug filled version of blur to be released as Moto has been doing.

2. I'm sure some guys will be let go and only the more essential guys kept, their programming skills haven't really impressed if you ask me.

It's nothing but speculation now; we'll see in about 6 months or so what's really going to happen.
Click to expand...


I dont think the UI guys are to blame for bugs to be honest
 
You must log in or register to reply here.
Back
Top Bottom