Database Users

Is it odd?

Out of all the the companies that have announced Honeycomb tablets, not one of them have laid a finger on Android 3.0? Is Google not allowing this? Or are they simply not familiar enough with 3.0 to make any dramatical changes? I don't think it is us consumers forcing them to do this, as it is very clear Motorola and Samsung will skin their devices as they please... but this struck me as odd that they aren't making any changes to the software to differentiate their tablets from the others.
Does Google want to make sure that their tablets get updated as soon as possible? Or do the manufactures believe that Android 3.0 doesn't need to be altered whatsoever and that stock Android is fine?
I know none of you may have a definite answer but I am very curious. I do know that this isn't a bad thing as people actually prefer stock Android... it just somewhat shocks me that these companies aren't trying to alter these tablets to their liking. All the tablets are essentially the same with a different shell. If this is the case, Google could have just released one Honeycomb tablet on all carriers with a decent price. Of course the answer to this will be "choice", but if ONE (and only one) Honeycomb tablet with a low enough price was announced.. that had USB ports, SD Cards slots, etc. -- we wouldn't have to look elsewhere.

The xoom will get an update for motoblur at a later date.
Sent from my EVO using XDA App

Sirchuk said:
The xoom will get an update for motoblur at a later date.
Sent from my EVO using XDA App
Click to expand...
Click to collapse
A Motorola employee said that, but then Motorola itself dismissed that as false.

It was a big race to get the first tablet out the door. It's going to take months to do a 3.0 as they need to re-do it from the group up.

Then perhaps manufacturers have finally come to the realization that google got it right and chose not to sink the money into software development and are sticking to the hardware.
Sent from my EVO using XDA App

If you watch the engadget interview with Matias Duarte, they ask him about his thoughts on manufactures laying hands on Honeycomb. He simply smiles and seems like he doesn't want no one changing up the UI. I mean he is the designer for Honeycomb and I doubt anyone would want their masterpiece being murdered by Motorblur and touchwiz! I think honeycomb looks amazing personally. I also think Google wants these tablets to succeed; therefore, leaving them in charge of updating the software, not manufactures like Samsung who never really update their devices.

Unfortunately we still have to rely on the manufacturer to do the updates I think.
Tico.ASandoval14 said:
If you watch the engadget interview with Matias Duarte, they ask him about his thoughts on manufactures laying hands on Honeycomb. He simply smiles and seems like he doesn't want no one changing up the UI. I mean he is the designer for Honeycomb and I doubt anyone would want their masterpiece being murdered by Motorblur and touchwiz! I think honeycomb looks amazing personally. I also think Google wants these tablets to succeed; therefore, leaving them in charge of updating the software, not manufactures like Samsung who never really update their devices.
Click to expand...
Click to collapse
Sent from my EVO using XDA App

Tico.ASandoval14 said:
If you watch the engadget interview with Matias Duarte, they ask him about his thoughts on manufactures laying hands on Honeycomb. He simply smiles and seems like he doesn't want no one changing up the UI. I mean he is the designer for Honeycomb and I doubt anyone would want their masterpiece being murdered by Motorblur and touchwiz! I think honeycomb looks amazing personally. I also think Google wants these tablets to succeed; therefore, leaving them in charge of updating the software, not manufactures like Samsung who never really update their devices.
Click to expand...
Click to collapse
Not to mention that Goog wants fast to market adoption of apps and the potential behind a store ala Apple.
Allowing third parties to muck around with what users can do has been the whole basis of the 'fragmentation' argument.
If Google uses its power in this case they do have a good chance to steal thunder from Apple, but only if they don't allow for the software and devices to get wildly out of sync as they are now.
And that really only pisses off the consumer, not the manufacturer folk - these hardware makers should be beholden to Google, not the consumer to the manufacturer.
Google needs to put the line in the sand so to speak and take ownership of the app side of the game with regards to the platform.. and as much as it pains me to say so, they need to start enforcing some rules about things.. within reason to their current scope/intention - a few friggin standards/rules would not hurt the platform at all.

Google - No Honeycomb AOSP for you!

http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
Google says it will delay the distribution of its newest Android source code, dubbed Honeycomb, at least for the foreseeable future. The search giant says the software, which is tailored specifically for tablet computers that compete against Apple's iPad, is not yet ready to be altered by outside programmers and customized for other devices, such as phones.

almostinsane said:
http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
Google says it will delay the distribution of its newest Android source code, dubbed Honeycomb, at least for the foreseeable future. The search giant says the software, which is tailored specifically for tablet computers that compete against Apple's iPad, is not yet ready to be altered by outside programmers and customized for other devices, such as phones.
Click to expand...
Click to collapse
More beta BS. I'll sell you a car but we only completed the frame.

Yup - Its why I just sent my Xoom back to Moto.

Perhaps it's time to change your ID to "completelyInsane".
Sent from my SCH-I500 using XDA App

_RTFM_ said:
Perhaps it's time to change your ID to "completelyInsane".
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
LMAO!
Sent from my PC36100 using XDA Premium App

i dont understand what will make it "ready" if they are planning on eventually releasing it what will keep it from being ported to phones then. If its a matter of incompleteness then what's changed since Cupcake which everyone agrees was more .8 than 1.0. Releasing it to dev's will allow for bugfixes and tweaks to get merged upstream.

It will leak eventually. It always does...
Sent from my Xoom using XDA App

Yea I dont understand google some times. I understand the the OS isnt ready, but if it really is that bad and that unstable then why even put it on a tablet. And really what harm does it do the put out the code, so people will port it to other devices, you can keep doing what you will but make lots of devs happy.

They say they're worried about a poor user experience. Who do they think these users are? "I he4rd on the int3webz I can haz h0neycombz on my G1?" I mean we already know that the percentage of people running custom Roms, while large for what it is, is not the bulk of people using Android. And we know that what we're doing may not be the smoothest experience. The SDK has already been ported to pretty much everything, and they're worried about the actual 3.0 being a poor experience? Come on Google, what's this really about?

This wasn't the best source to quote from. Google said they don't want developers trying to port it to phones yet since they can't guarantee a good user experience on phones. They're afraid XDA is going to port it, people try to run it on their phones and then say how crappy it runs on a phone even though that's not what it was designed for. You know it would happen, and word would spread that it sucks on phones and yada yada it doesn't get a fair chance.
Sent via EVO

As much of a ROM guy as I am, I admit this makes sense from a business stand point. Google makes $ from licensing and distribution (with regards to Android). The hacker communities do not make up said market for the most part.
The worst thing companies combat these days is negative publicity.
I owned an iPhone, two iterations, the 3G and the original. Why did my mother never purchase one, nor my sister? Simply because of how locked down they are due to MY advice. Were they ever going to buy said device due to their hackability? Hell no. But because I said it was sh**** that Apple locks their stuff down so much, they declined to buy said hardware.
Releasing the software for Google could have a lot of negative effects on a BRAND NEW operating system for a BRAND NEW market for Google. If people are throwing this on phones, you search it out on the internet, and everything is Honeycomb this sucks, and honeycomb that sucks, due to people using it on phones, most people who try to do basic research, like my mother, or sister,
will only see "THIS SUCKS".
Just my 2c, but I can see their stand point. Until they can find a way to keep it off the phones, I see this as an issue for google.
~m

familiarstranger said:
They say they're worried about a poor user experience. Who do they think these users are? "I he4rd on the int3webz I can haz h0neycombz on my G1?" I mean we already know that the percentage of people running custom Roms, while large for what it is, is not the bulk of people using Android. And we know that what we're doing may not be the smoothest experience. The SDK has already been ported to pretty much everything, and they're worried about the actual 3.0 being a poor experience? Come on Google, what's this really about?
Click to expand...
Click to collapse
Uhmm, are we reading the same forum? Where people knowingly purchased a device that didn't have flash or lte or an ad card working at launch but are still *****ing and whining and returning their xoom regardless? What I mean is, those same people will install Honeycomb and complain that google released a lousy product.
Sent via EVO

thegeektern said:
I understand the the OS isnt ready, but if it really is that bad and that unstable then why even put it on a tablet. And really what harm does it do the put out the code, so people will port it to other devices, you can keep doing what you will but make lots of devs happy.
Click to expand...
Click to collapse
My understanding of that article is that Google doesn't feel its ready for phones. It's not that its not ready for tablets. They understand that they won't be able to stop people from using HC on phones, but trying to stave off the inevitable...
this HC thing looks like crap.... oh.. on my phone. In the end.. we are talking about a company here.. a company that needs to keep it's image.. and products.. (or software as you may call it).. as good as possible.
I don't think it's the best move Google could have made, but I think Google should do things in it's best interest to keep itself as a company in good standing. Long and short of it.. if things go south for google.. we'll all be unhappy. Just getting things out for the sake of allowing devs to play doesn't mean its the most sound decision for the company making it.
Yes, I know.. it's 'open source', but it is still a work-product. I think it's also entirely likely this is just a marketing ploy to say 'we told you so'.. and then it will get leaked and everything will go back to normal. But I still think people often forget that this is still a company that has to keep itself together to survive.
EDIT: So many things get written in the same time when you respond to a post! It seems as though I am joining the choir of.. this isn't so bad.

Sirchuk said:
This wasn't the best source to quote from. Google said they don't want developers trying to port it to phones yet since they can't guarantee a good user experience on phones. They're afraid XDA is going to port it, people try to run it on their phones and then say how crappy it runs on a phone even though that's not what it was designed for. You know it would happen, and word would spread that it sucks on phones and yada yada it doesn't get a fair chance.
Sent via EVO
Click to expand...
Click to collapse
Well that hasn't stopped devs on xda porting it already - http://forum.xda-developers.com/showthread.php?t=978939

Darn you almostinsane, I was just about to post this but you beat me to it!
Its really unfortunate that Google is doing this, whatever happened to a completely open source OS? In my honest opinion I think they should release it to the public and let the various devs have at it and see what can be improved and take those improvements into consideration for the next release of Android. If the OS was only meant for tablets who is to say that x developer can port it to a handheld flawlessly? It would be a HUGE leap ahead for us and for big ol' G.
Either way, it'll happen with or without Google releasing the source as our one dev spacemoose1 has shown us with making a near perfect port to the Samsung tab of honeycomb.
Stinks money is such an issue, Google doesn't really need anymore haha.
Done with my rant now
Sent from my ADR6300 using XDA App

Another business reason for this decision: Google may not have programmed Honeycomb well.
An obvious(?) repercussion for grimy source code going public is more bashing of Honeycomb's alleged "beta-ness". The more app developers that use the ...poisonous open-source code, the more ...poisoned apps there will be.
Or, they want to curb full-blown Honeycomb from appearing on devices other than the Xoom for just a little longer.

you're right. I just hate that its true. Your sig shows you remember the G1 days when we were all just so happy about what our phone COULD do. It's gotten a lot whinnier around here since then.
Sirchuk said:
Uhmm, are we reading the same forum? Where people knowingly purchased a device that didn't have flash or lte or an ad card working at launch but are still *****ing and whining and returning their xoom regardless? What I mean is, those same people will install Honeycomb and complain that google released a lousy product.
Sent via EVO
Click to expand...
Click to collapse

As a ROM enthusiast; yea this sucks. Business it's understandable; but as the former it doesn't make me happy.
My NC sorely needs a aosp honeycomb, HC's tablet interface is superior to even CM7 on it.
Honestly though it's a lot of speculation here on why, but it really just sounds like an excuse (Bad one) to quiet the devs while really being a straight business decision.

How is not releasing honeycomb aosp right away not being open? Would you like all your roms without SD card support right now? Honeycomb is most likely stable enough for normal use for the average consumer and Google had to make footprint in the tablet industry before ipad2 was announced. Things were obviously rushed so i rather wait for them get everything situated. I think this unfortunate news but I'm not gonna cry foul when its something that's probably for the better. Google has proven with each iteration of android they have released source so just be patient
Sent from my Xoom using Tapatalk

almostinsane said:
Yup - Its why I just sent my Xoom back to Moto.
Click to expand...
Click to collapse
I don't understand the logic here. What alternative are you seeking? Take it back for the Galaxy 10.1? It runs the same OS. Take it back for an iPad? It runs a closed OS.
The AOSP release is delayed ... maybe. Why would you return your Xoom because of this?
Sent from my Nexus One using XDA Premium App

Honeycomb source

If you havent read they are delaying the honeycomb source code indefinetly ...not a good look ...
Sent from my Dell Streak

Whats this all about?
Sent from my Dell Streak

does this affect DJ Steve's release plans ?

DJ Steve isnt going to be able to release a HC port until the code is available, he can work to get the kernel closer to working. But without the source the rest of HC requires hacking up the SDK rom or a dump from the xoom or similar.
With enough effort you COULD make do with just the SDK rom, but it's a huge waste of energy to work towards making something polished enough for release without the source.

Sorry i made this post from my phone ....i would of linked the article
Sent from my Dell Streak

From what i have just been reading they could be braking the Law by doing this, I'm sure by next week things will change they will get bombarded with complaints about this

Android is apache license mostly, they dont have to release any code that falls under that license.
The kernel on the other hand is GPL and that source is available. Anything else GPL or LGPL should be available?
Weither or not it is the bulk of the code is Apache so it's all koscher.
(Could have some minor details wrong, but it's basically apache = dont have to release anything)

I remember when google was sending c&d out to ppl that were including gapps in roms ....i think this is another bad move just like it
Sent from my Dell Streak

Here's the article I saw yesterday. The TL;DR is that Google allegedly doesn't want OEMs to put HC onto phones and turn people off. Therefore they're going to do another AOSP drop when they get to Ice Cream Sandwich.
http://www.businessweek.com/print/technology/content/mar2011/tc20110324_269784.htm

Why am i not suprised
Sent from my Dell Streak

TheManii said:
DJ Steve isnt going to be able to release a HC port until the code is available, he can work to get the kernel closer to working. But without the source the rest of HC requires hacking up the SDK rom or a dump from the xoom or similar.
With enough effort you COULD make do with just the SDK rom, but it's a huge waste of energy to work towards making something polished enough for release without the source.
Click to expand...
Click to collapse
That massively sucks. #@$% i Google. You just did Evil.

They say it isn't ready for devices other than the ones they have basically hacked it onto. Whats the problem. The sky isn't falling.

This is evil? Delaying a source release because they don't want people putting it on devices it doesn't belong?
Alot of Xoom reviews say honeycomb feels like a beta release, and although I respect the hacker community, I don't see a reason to believe they can make it better by putting it on devices its not intended for to begin with.
Sent from my MB860 using XDA App

Sounds like Honeycomb is not at all what they want it to be, like they rushed it into production just to be ready for the hardware that was about to drop.

So give us the chance to TRY it and discover if it is worth it or not OURSELVES. Evil hides in secrets, innuendo, hearsay etc etc. Holding it back = pure evil.

Ars Technica has a good article
http://arstechnica.com/open-source/...thering-as-google-withhold-honeycomb-code.ars
Concluding paragraph
"For now, only a privileged few hardware vendors will have access to Honeycomb while the rest are left with uncertainty about the future of the platform. Even after the matter is resolved, the fact that Google is willing to withhold source code at its whim for competitive reasons is going to continue to cast a dark shadow over the company's increasingly hollow claim that Android is an open platform."

rebski said:
Ars Technica has a good article
http://arstechnica.com/open-source/...thering-as-google-withhold-honeycomb-code.ars
Concluding paragraph
"For now, only a privileged few hardware vendors will have access to Honeycomb while the rest are left with uncertainty about the future of the platform. Even after the matter is resolved, the fact that Google is willing to withhold source code at its whim for competitive reasons is going to continue to cast a dark shadow over the company's increasingly hollow claim that Android is an open platform."
Click to expand...
Click to collapse
Very good summary. I would also add that it is counter to Google's philosophy #6 "You can make money without doing evil" or more commonly written "do no evil" http://en.wikipedia.org/wiki/Don't_be_evil

Is it really evil?
It's definitely uncool, but they also control the license. Evil would be changing the license to a fully closed source license (minus the kernel code of course), which they could do at any time.
As the license holders they have that ability (and regardless, apache allows that, which pretty much every manufacturer does, how many manufacturers release the full source for their modifications?). If android were originally licensed under the current situtation it wouldnt be any different from WinMo, iOS, WP7. Android is only open when talking about it's code, google doesnt make any requirements that phones need to be open (ie encrypted bootloaders).
The hopeful explination is that the code really is rushed and they dont want to embarass themselves and are trying to fix it before releasing it. Even if you release something and say you offer no support, people are still going to bother you with questions. Even locking threads with "we provide no support" takes effort, especially when it's dozens upon dozens of threads. Providing ugly code could be an image thing they're trying to avoid if that's the case. (Then again, chrome/chromium is another google project that develops at a blistering pace)

Yes it is evil. Corporate evil usually starts out with small evil decision just like this one and get worse from there.

Themanii I think you are right. As crap as it is that Google isn't allowing honeycomb out there could be, and probably are many reasons why.
Its just something we have to live with for now. May be we can hit lucky with one of the companies allowed access to the source.
Sent from my Dell Streak using Tapatalk

Why do you think there's going to be any "dev" action on the A500?

First off, keep in mind I'm not trying to start a fight. I really don't know the answers.
Given that Honeycomb is never going to be open source, to me that means ROM changes by the dev community are impossible. Only Acer can make and push out those changes.
I don't consider changing an app out to be "development". To me, that's theming. While that's a fine thing, what I really want are changes to the core code to fix basic problems with the OS we've been given.
At some point in the near future I'd like to participate in making those changes.
Since HC source is never going to be available to me, that tells me that I'm going to be limited to theming the OS I've already got.
What do you know that I don't which leads you to think the dev community will be able to make substantial changes to our tablets?

Ice Cream is rumored to be scheduled for Q4 and Google has stated it will be the next open-sourced version.
Honeycomb was effectively a rush-to-market to try to allow companies like Motorola and Acer to compete with the iPad before it came too late, and is an incredible hack job.
I'm okay with that. Once someone breaks the boot-loader on the Acer some enterprising dev will get Ice Cream on it, even if Honeycomb is never released as source.
News sources: http://phandroid.com/2011/05/10/goo...mb-because-they-wanted-to-wait-for-ice-cream/
http://www.engadget.com/2011/05/10/google-announces-ice-cream-sadwich-for-q4-2011-for-smartphones/

It's funny that Google is so embarassed of how bad they had to code Honeycomb to get it out that they won't let the public see it. It's got to be really stinky, and it explains the problems we have. I'd rather this than Apple winning the war though.
That being said, I don't want Apple out of the game either. I want it split 50/50 or so. Encourage price and development pressure on the corporations.

muqali said:
It's funny that Google is so embarassed of how bad they had to code Honeycomb to get it out that they won't let the public see it. It's got to be really stinky, and it explains the problems we have. I'd rather this than Apple winning the war though.
That being said, I don't want Apple out of the game either. I want it split 50/50 or so. Encourage price and development pressure on the corporations.
Click to expand...
Click to collapse
Yup. I completely agree. The competition keeps them on their toes.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.

agreed , I dont think anyone wants Apple out of the game , just as kicking Microsoft to the curb is unwise! Competition makes prices go down and technology better!

I think the comparison to apple products is not really justified. These tablets are not glorified ipods (and I mean this in a good way), but they are actual intermediates from phone to laptops. I have a more efficient way of browsing, e-mail, reading, playing movies, etc that happens to have games.
I am impressed that Apple introduces well packaged and polished products to consumers, and for most consumers, these products will work well for their "needs." I agree with what another member said recently, just using the product is only half the fun. I think the reason we are on these forums and buy these products is that we enjoy the challenge that Android devices hold. They are basically the most raw form of the new tablet PC market, akin to the old IBMs and such that most of us remember using when we were younger. You know, the ones we used to open up and explore, disassemble and reassemble.
I love what the android tablet market offers: a collection of powerful hardware and the collective creativity of everyone in this dev community. I am looking forward to what kind of crazy things this community comes up with.

ICS a disappointment?

Hi all, after watching some videos of the SDK for HC, I have been both surprised and disappointed because I expected a revolution most notorious for this new OS and only seem to alter the appearance like Touchwizz style and I am surprised that the optimization by Tiamat, in my opinion provides a perfect scenario, much more possibilities both in appearance and applications than ICS
somevideos from SDK ICS Tablets
http://es.engadget.com/2011/10/19/un-primer-vistazo-a-ice-cream-sandwich-para-tablets/

I'm definitely happy with ICS. The improvements are good for phones. For tablets, think of it as a refinement to Honeycomb.
In anycase ICS does really deliver on Google's promise to unify phones and tablets.

I agree with you, for smartphone is an excellent update has new features, although almost everything is extrapolated from the HC

It was really meant for phones.
Sent from my PC36100 using XDA App

gqstatus0685 said:
It was really meant for phones.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
How do you figure that?

I frankly don't know what you were expecting exactly. This is an update to an existing OS, not a new OS. And there are a LOT of changes under the hood that haven't been really discussed at the Samsung/Google event. Something like turning the Recent button into an actual Task Manager is a very nice features. Built-in screenshot capabilities is another long-time requested feature that is in ICS. Sure, a lot of the other changes are targeted at phones, but Android is first of all a mobile device OS.
Look at http://developer.android.com/sdk/android-4.0-highlights.html for a closer detail at changes in 4.0. And look at all the non-visible, under-the-hood changes that are nonetheless major, even if they do not represent any visual or end-user impact at first: http://developer.android.com/sdk/android-4.0.html
To me, ICS looks exactly what it should have been: first of all a serious spit-shine done at Android, giving the bit of polish people often complained it lacked. And it also brings a lot of new goodies to the table.

Its because we have some of the features on our tablets that our phones had to live without....
I'm going to be happy when our tablets run most apps on the market like phones without issue.

Slightly unrelated note: Andy Rubin said at AsiaD that ICS should be opensourced a few weeks after the Galaxy Nexus launch. That will allow ROM modders to come up to plenty of new features for our tablets.

musashiken said:
I'm definitely happy with ICS. The improvements are good for phones. For tablets, think of it as a refinement to Honeycomb.
In anycase ICS does really deliver on Google's promise to unify phones and tablets.
Click to expand...
Click to collapse
Agreed. Actually, ICS is what honeycomb should have been. Motorola actually rushed Google for the developement of 3.0 to release with the xoom. Anyways that's their reasoning for not releasing the source for HC and why they are going to be releasing the code for ICS. They didn't want people to developed a platform that was rushed.

Rushed or not it works great as a tablet os.
There is alot of honeycomb in ics you can easily tell that hc was a transitional os but alot better than most other transitional OS's like.....windows ME or vista....so not sure how rushed it was.

blackgf said:
Hi all, after watching some videos of the SDK for HC, I have been both surprised and disappointed because I expected a revolution most notorious for this new OS and only seem to alter the appearance like Touchwizz style and I am surprised that the optimization by Tiamat, in my opinion provides a perfect scenario, much more possibilities both in appearance and applications than ICS
somevideos from SDK ICS Tablets
http://es.engadget.com/2011/10/19/un-primer-vistazo-a-ice-cream-sandwich-para-tablets/
Click to expand...
Click to collapse
Uh, no. I think if you were disappointed than your expectations were too high. If you've used Honeycomb, then very little in ICS should surprise you, given that Google is simply using ICS as a vehicle to link phones with the work already accomplished on their tablet OS. Honeycomb is great, and I look forward to getting ICS on both my Nexus S and my Xoom, given that Honeycomb (to me) is superior in almost every way to Gingerbread.

csseale said:
Rushed or not it works great as a tablet os.
Click to expand...
Click to collapse
I disagree. We lost features. The central complaint about the original Galaxy Tab was that it was basically a big phone. Not much has changed with Honeycomb and until very recently, that big phone had more functionality than our devices (which are bigger big phones.)
Sent from my Xoom using xda premium

Calling any iteration of Android "rushed" demonstrates a misunderstanding of Google's core development philosophy.

csseale said:
Rushed or not it works great as a tablet os.
There is alot of honeycomb in ics you can easily tell that hc was a transitional os but alot better than most other transitional OS's like.....windows ME or vista....so not sure how rushed it was.
Click to expand...
Click to collapse
Again Motorola pushed google for a tablet os to produce the xoom. Again, its their reason for not releasing the source for HC. Source http://en.wikipedia.org/wiki/Android_(operating_system)#Licensing

Jellybean will focus more on tablets. With a plethora of quad core tablets about to be unleashed, devs should jump at the chance to develop richer applications that can harness the power of 4 cores.

3devious said:
I disagree. We lost features. The central complaint about the original Galaxy Tab was that it was basically a big phone. Not much has changed with Honeycomb and until very recently, that big phone had more functionality than our devices (which are bigger big phones.)
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Galaxy tab was a big phone..just as the ipad was. They are both running os built for phones....hc is nothing like a phone and was built with tablets in mind. So the comparision is kinda ridiculous.

s14tam said:
Again Motorola pushed google for a tablet os to produce the xoom. Again, its their reason for not releasing the source for HC. Source http://en.wikipedia.org/wiki/Android_(operating_system)#Licensing
Click to expand...
Click to collapse
I am fully aware of the history. But it was far from a bad release and does not feel rushed. It fits perfect. And ics is not filling very many holes in hc. So if you don't like hc then I'm afraid you wont like ics.
All they did was merge hc with the phone world and eliminated the phone only part. Ics is hc with a dialpad.

ZanshinG1 said:
Calling any iteration of Android "rushed" demonstrates a misunderstanding of Google's core development philosophy.
Click to expand...
Click to collapse
Wow...I agree with you...crazy

ZanshinG1 said:
Calling any iteration of Android "rushed" demonstrates a misunderstanding of Google's core development philosophy.
Click to expand...
Click to collapse
csseale said:
Wow...I agree with you...crazy
Click to expand...
Click to collapse
So are you both saying that Google would never in a million years push production of a product while omitting some features to make a deadline? If honeycomb was what Android 3.0 was always meant to be, then Google would have had no problem with releasing the source for it as they have been doing for all previous versions. If you really understood androids history, then you either have insider knowledge or are demonstrating a misunderstanding of reality.

s14tam said:
So are you both saying that Google would never in a million years push production of a product while omitting some features to make a deadline? If honeycomb was what Android 3.0 was always meant to be, then Google would have had no problem with releasing the source for it as they have been doing for all previous versions. If you really understood androids history, then you either have insider knowledge or are demonstrating a misunderstanding of reality.
Click to expand...
Click to collapse
Release early, release often is a core google philosophy.
The lack of a honeycomb source release has nothing to do with being "rushed". According to Rubin, it was to prevent the proliferation of phones with a non-phone optimized OS.