- 03-24-2011, 05:25 PM #2
- 03-24-2011, 05:41 PM #3
- 03-24-2011, 06:00 PM #4
All this means is that developers will turn to the Full SDK and/or the XOOM system dump to start putting Honeycomb on other devices.
It will stop the manufactures from dumping HC on devices that it's not designed for and that's probably what Google is aiming for.
- 03-24-2011, 08:13 PM #5
- 03-24-2011, 08:22 PM #6
- 03-24-2011, 08:40 PM #7
- 03-24-2011, 09:35 PM #8
They really shouldn't have released the XOOM from a code completion standpoint. Not sure how you can say it's not complete. Look at SD support. LTE support. The just arrived flash support. Lack of app backwards compatibility.
I have no trouble believing that the code is incomplete right now. Google/Motorola released it admitting it was not complete.
- 03-25-2011, 09:35 AM #11
- 390 Posts
Why not just release it with the warning that it's not designed for phones? I mean, don't we know that already anyway? This just seems like a really closed way of doing open source. In the past it felt like Google wasn't too concerned with what the software ended up on, they just handled the software end, what it was used for was up to the OEMs. Now they seem to be taking a more active role, which is a little too heavy handed for me.
- 03-25-2011, 02:39 PM #13
- 52 Posts
Agreed; while I believe supporting AOPS is still firmly one of Googles goals, they are also responsible for looking after the Android brand image.
What happens if some OEM gets hold of the latest Android OS and starts shutteling it to decives that it was not designed for or compatibe with? Marketing these devices as the "Latest" and "Best" that android has to offer would only leave a sour taste for Android in the mouths of all the consumers who bought the device, not knowing any better.
This in effect is what we are seeing to a lesser extent with the Xoom. Look at all the hits the Xoom takes for little things like the lack of flash support upon released, and for the the SD and LTE both being disabled. Although those of us who know Android, know these things will be corrected in time, many people do not. That's exactly the situation the Google needs to avoid.
Last edited by jbrown1114; 03-25-2011 at 03:20 PM.
- 03-25-2011, 02:52 PM #14
- 03-25-2011, 03:32 PM #15
- 52 Posts
It's not that they mind OEM's putting their software on different devices, they just want to make sure that their software is robust enough to handle it. And right now, Honeycomb is not.
From what I read of Andy Rubin's comments in his interview with Bloomberg, it sounds like the development team cut out a lot of the functionaliy that would allow Honeycomb to run as a phone platform in their rush to meet the Xoom release deadline.
As far as the reverse case. Previous Android releases were capable of of running just fine on a tablet platform. They weren't optimized for it the way Honeycome is; just as Honeycomb won't be optimized to run on a phone platform. But it needs to be capable
- 03-25-2011, 10:00 PM #16