FYI - NVIDIA won't suport harmony based tegra2 tablets... - G Tablet Q&A, Help & Troubleshooting

Just thought this was sad....
http://developer.nvidia.com/tegra/forum/honeycomb-harmony

Probably the wrong forum for this, but I think the G-Tab will be my 1st and only android device.
From day 1 till now I have had a bad taste in my mouth between Viewsonic's dropping the ball, Google's Honeycomb decisions, and finally Nvidia's dropping the platform not even 1 year in. This is a mess.
Thanks to XDA as they have been the only group in this mess who actually cared about the end users, and they were unpaid enthusiasts. That's a huge strike against android as a viable platform.

Virtual Pariah said:
Probably the wrong forum for this, but I think the G-Tab will be my 1st and only android device.
From day 1 till now I have had a bad taste in my mouth between Viewsonic's dropping the ball, Google's Honeycomb decisions, and finally Nvidia's dropping the platform not even 1 year in. This is a mess.
Thanks to XDA as they have been the only group in this mess who actually cared about the end users, and they were unpaid enthusiasts. That's a huge strike against android as a viable platform.
Click to expand...
Click to collapse
What's the difference as long as the need is being taken care of?
For many this platform and tab have been taken from a mere consumption device to a learning tool. Who else, is offering such opportunity to better learn a mobile platform in and out?
Sometime we look right past the obvious. I would much more so want to learn than sit and play games or consume. To each his own.

Wow! Out of all the companies, nvidia was the last company I thought would do this. Reputation of driver support is just about the most important thing a chip company can have.

edirector said:
What's the difference as long as the need is being taken care of?
For many this platform and tab have been taken from a mere consumption device to a learning tool. Who else, is offering such opportunity to better learn a mobile platform in and out?
Sometime we look right past the obvious. I would much more so want to learn than sit and play games or consume. To each his own.
Click to expand...
Click to collapse
I see where you are going, but, without official support most of the enthusiast devs will migrate to another platform.
To me, the loss of the manufacturer's input would be the death knell for the device.
Most people who have paid for this tablet did so for the media consumption capabilities. At least in the general population.
I'm a tad confused that anyone would be considering withdrawal of official support a good thing...

Moved to Q&A.

Just saw an update from a nvidia rep...
UPDATE 12 APRIL 2011:
Sorry folks looks like I caused a bit of confusion. Since this is a developer forum my comments were targeted at Tegra Honeycomb developers and for this we’d like to focus on Ventana. For shipping or production products, customers should contact the device makers directly for OS support plans. They are responsible for the OS shipping on their device.
In relation to our linux kernel git repository, NVIDIA will continue to provide full open-source support for all of our kernel components and will push more of that upstream over time.
Andrew Edelsten
Tegra Developer Relations
NVIDIA Corporation
Can someone give me the plain english version?

Between this and the recent google 3.0 annoincement they must be dancing in the streets in Cupertino

thevaristy said:
Just saw an update from a nvidia rep...
UPDATE 12 APRIL 2011:
Sorry folks looks like I caused a bit of confusion. Since this is a developer forum my comments were targeted at Tegra Honeycomb developers and for this we’d like to focus on Ventana. For shipping or production products, customers should contact the device makers directly for OS support plans. They are responsible for the OS shipping on their device.
In relation to our linux kernel git repository, NVIDIA will continue to provide full open-source support for all of our kernel components and will push more of that upstream over time.
Andrew Edelsten
Tegra Developer Relations
NVIDIA Corporation
Can someone give me the plain english version?
Click to expand...
Click to collapse
Does this mean that they are supporting Gtablet Nvidia drivers. ???

Let us all hope Nvida will change there minds after a bunch of emails to support harmony on gingerbread and honeycomb

A good news from Nvidia ???
The newest update from Nvidia looks good (see below).
They will support the gtablet as long as viewsonic supports it. Nvidia is listening.
Now we have to keep the pressure on viewsonic for the support.
UPDATE 13 APRIL 2011
A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today.
Andrew Edelsten
Tegra Developer Relations
NVIDIA Corporation

Related

[Q] Honeycomb Tegra 2 platform question

Ok, so notion ink releases a statement about how their hardware was changed to support Ventana instead of Harmony.
h ttp://notionink.wordpress. com /2011/02/08/in-the-mean-time/
Harmony and Ventana are two Tegra platforms and in September we made few hardware changes to make Adam Ventana compatible. That was done cos we sensed only Ventana devices will be able to run Honeycomb and we were right.
Next I checked nvidias developer website and saw this:
h ttp://developer.nvidia. com /tegra/devkit-ventana
The Tegra 2 "Ventana" development kit is targeted at developers creating software for Android 2.3 "Gingerbread" and above. The development kit is a quasi-tablet design and includes many devices and sensors found in Android based tablets.
So my questions are the following:
Is there any truth to the Honeycomb only running well on Ventana and not Harmony?
Is ventana a specific piece of hardware?
If not, is it just a set of "recommended" hardware features?
Will the current G tablet meet the requirements for ventana development if it is just software/recommended hardware?
I hope I'm not overstepping my bounds with to many questions at once.
Karl
Note: Please forgive the url formatting. I haven't posted enough to be allowed to post URLs yet.
kraulerson said:
Ok, so notion ink releases a statement about how their hardware was changed to support Ventana instead of Harmony.
h ttp://notionink.wordpress. com /2011/02/08/in-the-mean-time/
Harmony and Ventana are two Tegra platforms and in September we made few hardware changes to make Adam Ventana compatible. That was done cos we sensed only Ventana devices will be able to run Honeycomb and we were right.
Next I checked nvidias developer website and saw this:
h ttp://developer.nvidia. com /tegra/devkit-ventana
The Tegra 2 "Ventana" development kit is targeted at developers creating software for Android 2.3 "Gingerbread" and above. The development kit is a quasi-tablet design and includes many devices and sensors found in Android based tablets.
So my questions are the following:
Is there any truth to the Honeycomb only running well on Ventana and not Harmony?
Is ventana a specific piece of hardware?
If not, is it just a set of "recommended" hardware features?
Will the current G tablet meet the requirements for ventana development if it is just software/recommended hardware?
I hope I'm not overstepping my bounds with to many questions at once.
Karl
Note: Please forgive the url formatting. I haven't posted enough to be allowed to post URLs yet.
Click to expand...
Click to collapse
Well, Notion Ink is not a reliable source, IMHO. However, if he was able to make a few simple HW mods to his existing Harmony device, and the rest is true, I do not see an problem making similar HW mods to the gtab, should they be necessary.
However, more likely, Honeycomb will run on harmony, and/or Notion Ink is lying.
Jim
I do agree that Notion Ink cannot be quoted as a truly reliable source, but I hadn't even heard about there being 2 different platforms for the Tegra 2. Also, with the fact of the Xoom coming out this month, means it had to be in production for a while so how did they manage to do it? Also, how did NI make hardware changes in september of '10 for Ventana if the nvidia blogs says the chips won't be out till the end of Feb '11? It's very odd from the bit of digging that I've done.
kraulerson said:
I do agree that Notion Ink cannot be quoted as a truly reliable source, but I hadn't even heard about there being 2 different platforms for the Tegra 2. Also, with the fact of the Xoom coming out this month, means it had to be in production for a while so how did they manage to do it? Also, how did NI make hardware changes in september of '10 for Ventana if the nvidia blogs says the chips won't be out till the end of Feb '11? It's very odd from the bit of digging that I've done.
Click to expand...
Click to collapse
The man makes a very compelling argument.
Sent from my PC36100 using Tapatalk
If you haven't figured out yet that for the most part Rohan is talking out his .... then I don't know what to tell you. It's amazing how an upstart overseas company seems to be able to know the future before anyone else....eden is close to honeycomb....adam is venetta
kraulerson said:
I do agree that Notion Ink cannot be quoted as a truly reliable source, but I hadn't even heard about there being 2 different platforms for the Tegra 2. Also, with the fact of the Xoom coming out this month, means it had to be in production for a while so how did they manage to do it? Also, how did NI make hardware changes in september of '10 for Ventana if the nvidia blogs says the chips won't be out till the end of Feb '11? It's very odd from the bit of digging that I've done.
Click to expand...
Click to collapse
This.
thebadfrog said:
If you haven't figured out yet that for the most part Rohan is talking out his .... then I don't know what to tell you. It's amazing how an upstart overseas company seems to be able to know the future before anyone else....eden is close to honeycomb....adam is venetta
Click to expand...
Click to collapse
And most assuredly this.
Do you mean "official" Honeycomb support? (i.e. from Viewsonic)
Or unofficial Honeycomb? (i.e. via xda-developers ROMs)
The Nook Color is running Honeycomb (though just a hacked preview based on the pre-SDK) pretty well...It's screen resolution is the same as the gTablet, and it's specs are worse...
I wouldn't bet on a release from Viewsonic...I'd be willing to wager that there will be a Honeycomb port for gTablet within a few weeks (or less) of the Xoom being released...
So mid-March...LOL...
TeutonicWolf said:
I'd be willing to wager that there will be a Honeycomb port for gTablet within a few weeks (or less) of the Xoom being released...
Click to expand...
Click to collapse
I totally agree with that one... BTW, I wouldn't be too worried regarding hardware spec requirements for Honeycomb - if somebody can port it to the Dell Streak (http://www.mytabletlife.com/2011/02/08/dell-streak-honeycomb-port/), then I'm sure that even if there were different Tegra2 versions, it wouldn't be much of a show-stopper.
I am afraid to revive this post that is almost a month and half old but i found a post at nvidia and i realized that the main question was not yet answered or clarified.
Any ideas on this??
http://developer.nvidia.com/tegra/forum/honeycomb-harmony
I still can't find definitive answers as to the difference between harmony and ventana.
The latest update from Nvidia
The latest update from Nvidia:
UPDATE 13 APRIL 2011
A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today.
Andrew Edelsten
Tegra Developer Relations
NVIDIA Corporation

[Q] Are future Gtab Honeycomb roms dependent on google?

Hey all, Just bought the g-tab as my first android device. I liked playing with the Xoom and iPads in the store, but wanted the same experience for cheap and knew that I would have to root this g-tab thing to unleash that awesome hardware value. So far I've easily put TNT Lite 4.2 and it really is much faster and more usable then the Tap N Crap that viewsonic shipped. Thanks a bunch devs for fixing what should have never been modded in such a crappy way.
My question is will there every be Android 3.0 available for the gtab? I just read an article about how google is trying to ensure oems don't mess up the UI like viewsonic did to protect their reputation. Since the gtab wasn't even an official android device, I'm wondering if Honeycomb will even be available to viewsonic or devs here to put on the gtab.
I totally agree with this article. Google shouldn't be as totalitarian as Apple, but this lack of quality control is making Android look bad in the public sphere (not to hackers of course) So did I just buy a dead end device?
As a new user - I still can't post links, so here's the pasted article from pc world:
Why Google's Tighter Control Over Android Is a Good Thing
Limiting availability of Android 3.0 code and apparent tightening of Android smartphone standards means that Google finally gets it about the platform.
By Galen Gruman, Infoworld Apr 6, 2011 11:30 am
Last week, Google said it would not release the source for its Android 3.0 "Honeycomb" tablet to developers and would limit the OS to select hardware makers, at least initially. Now there are rumors reported by Bloomberg Businessweek that Google is requiring Android device makers to get UI changes approved by Google .
As my colleague Savio Rodrigues has written, limiting the Honeycomb code is not going to hurt the Android market . I believe reining in the custom UIs imposed on Android is a good thing. Let's be honest: They exist only so companies like Motorola, HTC, and Samsung can pretend to have any technology involvement in the Android products they sell and claim they have some differentiating feature that should make customers want their model of an Android smartphone versus the umpteenth otherwise-identical Android smartphones out there.
[ Compare mobile devices using your own criteria with InfoWorld's smartphone calculator and tablet calculator. | Keep up on key mobile developments and insights via Twitter and with theMobile Edge blog and Mobilize newsletter. ]
The reality of Android is that it is the new Windows : an operating system used by multiple hardware vendors to create essentially identical products, save for the company name printed on it. That of course is what the device makers fear -- both those like Acer that already live in the race-to-the-bottom PC market and those like Motorola and HTC that don't want to.
But these cosmetic UI differences cause confusion among users, sending the message that Android is a collection of devices, not a platform like Apple's iOS. As Android's image becomes fragmented, so does the excitement that powers adoption. Anyone who's followed the cell phone industry has seen how that plays out: There are 1 billion Java-based cell phones out there, but no one knows it, and no one cares, as each works so differently that the Java underpinnings offer no value to anyone but Oracle, which licenses the technology.
Google initially seemed to want to play the same game as Oracle (and before it Sun), providing an under-the-hood platform for manufacturers to use as they saw fit. But a couple curious things happened:
Vendors such as Best Buy started selling the Android brand, to help create a sense of a unified alternative to BlackBerry and iOS, as well as to help prevent customers from feeling overwhelmed by all the "different" phones available. Too much choice confuses people, and salespeople know that.
Several mobile device makers shipped terrible tablets based on the Android 2.2 smartphone OS -- despite Google's warnings not to -- because they were impatient with Google's slow progress in releasing Honeycomb. These tablets, such as the Galaxy Tab , were terrible products and clear hack jobs that only demonstrated the iPad's superiority . I believe they also finally got the kids at Google to understand that most device makers have no respect for the Android OS and will create the same banal products for it as they do for Windows. The kids at Google have a mission, and enabling white-box smartphones isn't it.
I've argued before that Android's fragmentation, encouraged by its open source model, was a mistake . Google should drive the platform forward and ride herd on those who use it in their devices. If it wants to make the OS available free to stmulate adoption, fine. But don't let that approach devolve into the kind of crappy results that many device makers are so clueless (or eager -- take your pick) to deliver.
So far, Google's been lucky in that the fragmentation has been largely in cosmetic UI areas, which doesn't affect most Android apps and only annoys customers when they switch to a new device. The fragmentation of Android OS versions across devices is driving many Android developers away , as are fears over a fractured set of app stores. Along these lines, Google has to break the carriers' update monopoly, as Apple did, so all Android devices can be on the same OS page.
It is true that HTC's Eris brought some useful additions to the stock Android UI, serving as a model for future improvements. But the HTC example is the exception, and Google's apparent new policy would allow such enhancements if Google judges them to be so.
More to the point is what the tablet makers such as ViewSonic, Dell, and Samsung did with their first Android tablets. Their half-baked products showed how comfortable they are soiling the Android platform. For them, Android is just another OS to throw on hardware designed for something else in a cynical attempt to capture a market wave. The consistently low sales should provide a clue that users aren't buying the junk. But do they blame the hardware makers or Google? When so many Android devices are junk, it'll be Google whose reputation suffers.
Let's not forget Google's competition, and why Google can't patiently teach these companies about user experience: Apple, a company that knows how to nurture, defend, and evangelize a platform. Let's also not forget the fate of Microsoft and Nokia , who let their Windows Mobile and Symbian OSes fragment into oblivion. And let's remember that the one company that knows how the vanilla-PC game is played, Hewlett-Packard, has decided to move away from the plain-vanilla Windows OS and stake its future on its own platform, WebOS , for both PCs and mobile devices. In that world, a fragmented, confused, soiled Android platform would have no market at all.
If Google finally understands that Android is a platform to be nurtured and defended, it has a chance of remaining a strong presence in the mobile market for more than a few faddish years. If not, it's just throwing its baby into the woods, where it will find cruel exploitation, not nurturing or defense.
I didn't read your 1000 word post, but I read your topic. HC on GTAB has NOTHING to do with Google. It has everything to do with Nvidia abandoning GTAB.
The media has an idea in their head but they are shooting the messenger. Google has no choice when Nvidia stops producing source for the proprietary elements of the system.
Nvidia simply does not care about Harmony which is the hardware reference legacy devices are built on.
So this device is going to be left behind when it comes to the new android stuff?
It is interesting that you ask. With 318 posts here you have to have followed some of the threads discussing this before. At this point in time I don't think anyone knows. Lots of speculation, lots of pent up desire and the best Devs ever so I am sure there will be improvements, Will it ever make full HC who knows?? If you read your article carefully, even the stuff out there ( Zoom and Transformer) does not have complete Honeycomb.
I wonder what Honeycomb will bring to the picture that we don't have already. I have my gtablet rooted and running TnT 4.4 and it's sufficient for almost all my tablet needs. Yesterday I was reading Kindle books to the kids, streaming movies/music from my media center PC, watching youtube and browsing the net, all with nary a hiccup. I even got a cheapo keyboard leathercase to use for editing documents. If it's the UI, the current Launcher Pro Premium and GO Launcher EX are pretty nice alternatives.
I have played with the XOOM tablet at Best Buy and thought other than some pretty UI and a nicer screen, functionally I wasn't getting much for double the price.
samaruf said:
I wonder what Honeycomb will bring to the picture that we don't have already. I have my gtablet rooted and running TnT 4.4 and it's sufficient for almost all my tablet needs. Yesterday I was reading Kindle books to the kids, streaming movies/music from my media center PC, watching youtube and browsing the net, all with nary a hiccup. I even got a cheapo keyboard leathercase to use for editing documents. If it's the UI, the current Launcher Pro Premium and GO Launcher EX are pretty nice alternatives.
I have played with the XOOM tablet at Best Buy and thought other than some pretty UI and a nicer screen, functionally I wasn't getting much for double the price.
Click to expand...
Click to collapse
Thats interesting. What ROM are you running? Most of my video is choppy, and I read in the dev forum this has to do with no video acceleration yet for the Gingerbread versions.
Good point - if it does what you want it to do then so what if it's not the newest... I'm a little embarrassed, but still rockin out to my first gen iPod nano a the gym
Guess I still wanted whatever tablet specific ui improvements that honeycomb was expected to bring.
nitefallz said:
Thats interesting. What ROM are you running? Most of my video is choppy, and I read in the dev forum this has to do with no video acceleration yet for the Gingerbread versions.
Click to expand...
Click to collapse
As I mentioned in my post, my ROM is TnT Lite 4.4 with Clemsyn's kernel (v9). I can stream 700 MB avi files with no stuttering or choppiness. I use GMote app on the tablet and the GMote server in the media PC. My video player is Rockplayer, which is free from the market.
I too was just at Best Buy bout a week ago and messed around with the Xoom for a little bit. Quickly I realized why its been a couple years since I've been to this store (prices?!?!), not to mention the help asking me if I had any questions and if I was looking to buy the Xoom (they left me alone after proclaiming I was completely satisfied with my gtab).
The only real difference I could notice (which in my eyes was a big one) was the interface. Its definitely more "flashy" in looks and prettier for eye-candy, but no real difference outside of that, actually seemed to lag a bit; almost comparable to the gtab out of box.
Me personally, I'm in no hurry to see any kind of honeycreams equivalent make its way to the gtab. I'm more anxious to see gojimi release their vegan ginger Beta more than anything right now. Been counting the days (sometimes hours) since reading their update about him coming back from vacation, lets do this!
Closing thread - see this
http://forum.xda-developers.com/showthread.php?t=1026411

No HC for tablets with harmony boards.

Its official:
http://phandroid.com/2011/04/12/nvidia-sadly-wont-provide-honeycomb-drivers-and-support-for-harmony-tegra-2-devices/
was just reading the same forum on Nvidia..... http://developer.nvidia.com/tegra/forum/honeycomb-harmony
Unbelievable !
If this is true - will not buy a single nvidia product anymore. Lousy bastards they are !
ibila said:
Its official:
http://phandroid.com/2011/04/12/nvidia-sadly-wont-provide-honeycomb-drivers-and-support-for-harmony-tegra-2-devices/
Click to expand...
Click to collapse
They are getting whipped for that
I dont get it though ? Are not all drivers for the platform opensource ?
How hard is it to move a driver btwn minor Linux versions ?
Our Folio will not get Honeycomb from Toshiba anyway, and the harmony machines out does not fit Googles requirments for Honeycomb.
As long as the drivers can be recompiled for the Honeycomb kernel there are many groups out there that can do a community port.
(Still waiting for Honeycomb Android source though...)
I agree, Nvidia will feel the consequences of this decision.
I was all for Tegra and was determined that my next tablet would also be a Tegra, but now there will not be a next time for me.
Whoever decided this at Nvidia should have their head examined, talk about bad reputation and bad business...
Nvidia has responded to the massive critic they got.
Here's the response from Nvidia:
"A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today."
I like the last sentence "We will be reaching out to them today"...

Welcome Back webOS (well, kinda)

http://www.engadget.com/2011/12/09/hp-webos-to-live-on-through-open-source-hardware-lineup-still/
When HP abruptly announced it was discontinuing the TouchPad and ceasing work on any future devices running webOS, we took that to mean the underdog operating system had died a premature death. But when the company ousted bumbling CEO Leo Apotheker and replaced him with Meg Whitman, we had to wonder if webOS might have some life in it yet. Well, the company just came back with a final verdict: the company will continue to develop webOS, as promised, but with the help of the open source community. In other words, webOS as a platform will live on, and developers both inside HP and out will spruce up the OS for interested OEMs (whoever they may be), along with people who already own webOS devices. Says Sam Greenblatt, CTO of the outfit's advanced technologies division: "We looked at all the various options we have on the table. We think this option is the best for the tech industry and HP."
Still, if you were hoping Whitman would resurrect the TouchPad and Pre 3 beyond just another fire sale, we hate to be the bearer of disappointing news. The bottom line: HP's webOS hardware lineup is still dead -- for now, at least. Greenblatt emphasized that HP might later choose to build devices running webOS, the same way any other OEM would evaluate any other operating system. In an interview, company representatives were also quick to say that with the help of developers outside HP, webOS could become a more attractive choice for devices other than phones and tablets (printers, anyone?). Still, though Greenblatt says there has been a "great deal" of interest from companies eyeing the software, it remains unclear which manufactures, if any, will decide to give the OS a more immediate home.​
So how long would we have to wait until we see AWESOME webOS hit the forums?
Oh and here's there Press Release...
HP to Contribute webOS to Open Source
HP to enable creativity of the community to accelerate the next-generation web-centric platform
PALO ALTO, Calif., Dec. 9, 2011 – HP today announced it will contribute the webOS software to the open source community.
HP plans to continue to be active in the development and support of webOS. By combining the innovative webOS platform with the development power of the open source community, there is the opportunity to significantly improve applications and web services for the next generation of devices.
webOS offers a number of benefits to the entire ecosystem of web applications. For developers, applications can be easily built using standard web technologies. In addition, its single integrated stack offers multiplatform portability. For device manufacturers, it provides a single web-centric platform to run across multiple devices. As a result, the end user benefits from a fast, immersive user experience.
"webOS is the only platform designed from the ground up to be mobile, cloud-connected and scalable," said Meg Whitman, HP president and chief executive officer. "By contributing this innovation, HP unleashes the creativity of the open source community to advance a new generation of applications and devices."
HP will make the underlying code of webOS available under an open source license. Developers, partners, HP engineers and other hardware manufacturers can deliver ongoing enhancements and new versions into the marketplace.
HP will engage the open source community to help define the charter of the open source project under a set of operating principles:
- The goal of the project is to accelerate the open development of the
webOS platform
- HP will be an active participant and investor in the project
- Good, transparent and inclusive governance to avoid fragmentation
- Software will be provided as a pure open source project
HP also will contribute ENYO, the application framework for webOS, to the community in the near future along with a plan for the remaining components of the user space.
Beginning today, developers and customers are invited to provide input and suggestions at http://developer.palm.com/blog/.
LOL, have you seen the HP web OS guys business card... Here it is
From Google currents:
Here Is the Absolute Saddest Business Card in the World
John Kneeland does not have an easy job at the moment. John Kneeland is probably nervous about his career every morning. John Kneeland is probably w...
Source: http://goo.gl/mag/ZS3fL
Sent from my HTC smartphone on the Now Network from Sprint!
Shot from my sharp shooter in 3d
cleanrom2.9.5
Looks like the EVO3D is already running webOS
http://mobile.theverge.com/2011/12/...r-htcs-evo-3d-a-proof-of-concept-for-the-time
Sent from my PG86100 using XDA App
wow no one cares for webOS? I was so ****in stocked i thought this thread would get stickied ahah wow.
LOL, I think its good stuff anything out of the ordinary is cool
Shot from my sharp shooter in 3d
cleanrom2.9.5
This is a whole new operating system for us and the dev at webOS has a 3d and already got it booted I believe. I'm ****ing stoked
Sent from my PG86100 using XDA App
The EVO 3d boot is 3 months old. But um looking forward to this.
Sent from my PG86100 using xda premium
I also am looking forward to this. I think it would be quite fun to run on BootManager. If they could figure out how to make the android market and apps compatible with webOS that would make even more tempting for many people. I for one am very much so in love with webOS.
It's the only viable option to Android. Seeing it Open Source is such good news.
Sent from my PG86100 using xda premium

An interesting article on the possible future of Android

Hey Guys, just came across this article and thought it was a good read. Do you think Android will partner with Asus to make their own brand of tablets...will it be better for us as Android buyers in the future if Android had more control by being the hardware as well as software maker. or do you feel like this is turning them into Apple-lite
http://www.androidauthority.com/will-google-abandon-android-71483/
Seems like Android Authority is a bit desperate for clicks. That is all I got from it.
detta123 said:
Seems like Android Authority is a bit desperate for clicks. That is all I got from it.
Click to expand...
Click to collapse
yeah basically..lol.
they taking the whole Asus Manufacturing Google Nexus tablet and spinning it into some crazy apocalyptic Android dying story. Android will be fine. Android growth has really actually just begun. we haven't seen nothing yet. Google needs a nexus tablet to instill confidence and optimism in Androids future. It can almost be guareenteed to attract more developers to android ecosystem. If android was dying, I'd seriously doubt they'd be making a tablet with Asus, restructured Google Play Store, and Making Google store purchases possible to be made online by anyone. All these recent moves Google has made is pointing to something big coming up.
Android for LIFE!
All of my current and future devices will continue to be android.
It is just way too much fun, IOS sucks.
If android goes away, I will go back to laptops.
Sent from my Transformer Prime TF201 using Tapatalk
I dont even want to read that article Android brings profit and is a huge thing worldwide. Why would you abandon something like this? Of course its not Google's biggest income generator but it has so much potential and it serves as competition to Apple.
Google deciding to do some hardware manufacturing? I really like that. They probably learn from it and be able to improve the software/hardware.
There is one thing though they could do to android imho. I like some of the 3rd party GUI's that come with android devices. For example HTC Sense. They add alot of nice widgets and great looking uniform base apps.
BUT. At the price of getting important updates like ICS half a year later? No... No.
For me there are 2 ways those companies could handle the situation. Make custom UI's optional. Let people use vanilla Android if they want fast upgrades and let them switch to custom UI's once their done. Or just open all the bootloaders and release all kernel source and stuff to XDA so people can make their own roms and updates (which usually are better anyway...).
Apart from that Android is just totally great.
clouds5 said:
For me there are 2 ways those companies could handle the situation. Make custom UI's optional. Let people use vanilla Android if they want fast upgrades and let them switch to custom UI's once their done. Or just open all the bootloaders and release all kernel source and stuff to XDA so people can make their own roms and updates (which usually are better anyway...).
Apart from that Android is just totally great.
Click to expand...
Click to collapse
Actually Google is already consdidering this. read several articles on it. it's a great idea bit one catch, Phone carriers would hate it. those companies add those GUI to devices to differentiate themselves from other similar devices. I'd rather have vanilla android experience and not have bloat ui on top of it. A GUI on top of vanilla android will never be faster out the box than a plain vanilla experience. one suggestion was to make the various companies GUI removable if the user chooses. they could use that companies GUI or go vanilla route or use one of the many launchers available on android. Usually a company GUI will be more integrated and stable than one from marketplace.
Yeah i've read about that too. i dont think custom UIs need to go away. Sometimes they're great. And with tegra3 phones coming out i guess the performance wont be such an issue anymore.
But i'd love to see some change in that situation. I think updates shouldnt be delayed more than 1 month. Not like half a year.
The article is the usual blog filler; title is admittedly clickbait. Then again, most news & blog sites have SEO'ed titles to varying degree. Yellow journalism used to be on the fringe. Now, it's the way to get clicks. That's the cost of "free" content.
Idle gossip aside, Google's strategy for tablet adoption has not worked. It will need to do something, and soon. We should know by Google I/O in June, if not earlier.
IMO, the rumors presently circulating--direct-sale of cheapo tablet & online store--aren't enough. The problems are more fundamental, and are myriad. To me, what's discouraging aren't the obstacles, but that I haven't seen any signal from Google leadership that they recognize the scope of the obstacles.
At any rate, Android won't suffer the fate of WebOS. It's entrenched on phones, and its open-source distribution will allow it to live on as a "hobbyist" OS, if nothing else.
Things move pretty fast in this mobile market, so we won't have long to wait, one way or the other.
Trolling done wrong.
A terrible excuse for either op-ed or journalism. sigh.
Seems this kid who wrote the article didn't get the point of android....
It amplifies all the Google services. It gives Google a extremely huge platform to present their products... it generates Google accounts which can be used for the almost infinite range of Google products. It helps to spread G+ and not to mention Google ad-words..
There is no essential need for a strong Google Phone brand... When you use it the normal way you pretty soon notice that Android is a Google product... you are asked to create a Google account, you have a ton of Google services pre-installed etc. .
Android could be a losing deal and it would still be worth the effort. Just because it spreads Google stuff. The power you have when 50% of the smart-phones world wide run with your is is enormous... Google does not have to worry too much about branding as long as the providers don't remove the Google-Products from it...
I see it like a commenter in the article, Google Tablet to fight the Kindle Fire... because it breaks the Google-branding... not so funny for Google...
>[Android] amplifies all the Google services. It gives Google a extremely huge platform to present their products...There is no essential need for a strong Google Phone brand...Android could be a losing deal and it would still be worth the effort.
These are all true. But IMO it misses the forest for the trees, the forest in this case being the next computing form factor, ie the tablet being a successor rather than adjunct of laptops. That should be the goal, not just an extension to sell more wares.
To be the next "computer," the OS has to do more, akin to the range of functions on desktop OS'es. Android, like iOS, lacks basic underpinnings--things like built-in networking, printing, support for peripheral devices, apps interoperability, etc etc.
The shortcoming doesn't affect Apple, because iOS has achieved critical mass on phones and tablets. Its success engenders 3rd-party support to address any deficit faced.
The other aspect not oft mentioned is that a bona fide OS needs support. One takeaway from a quick scan through these and other (official) Android forums is that OS support is grossly inadequate. As much complaints as there are in this forum, Asus is actually one of the better vendors for support. Users of Acer, Toshiba, and others, have given up on support. And these are enthusiasts. Think of how worse it would be for normal users.
The writing is on the wall: HW vendors don't have the expertise to support the OS. Google needs to do it. But with its current distribution philosophy, ie making AOSP code public and let HW vendors do what they will, Google can't do that. For it to support its OS, Google will need to follow the Microsoft path.
Getting its hands dirty with its own hardware may be a start, assuming Google better supports its product. But customer support has never been in Google's DNA, so I have my doubt that things would improve soon.
Google bought Motorolla, why would they need to partner with ASUS?
Sent from my DROID2 GLOBAL using Tapatalk
>Google bought Motorolla, why would they need to partner with ASUS?
Because Asus can make cheap tablets, eg the rumored $199 tab, and Moto can't. Secondly, because Google still needs to maintain some degree of impartiality. With declining vendor support (on tablets), it can ill afford to piss off the few remaining.
e.mote said:
>Google bought Motorolla, why would they need to partner with ASUS?
Because Asus can make cheap tablets, eg the rumored $199 tab, and Moto can't. Secondly, because Google still needs to maintain some degree of impartiality. With declining vendor support (on tablets), it can ill afford to piss off the few remaining.
Click to expand...
Click to collapse
Agreed, the Motorola Xoom, great as it was(I owned one), was simply overpriced.
I do believe that in order to be widely accepted as being better than Apple, Google needs to seriously focus on getting better developer support. You can release the best tablet in the world, but if you do not have developer support, people will continue to flock to IOS. Lower the price of tablets while maintaining good quality standards, and gain developer support=win for Android
e.mote said:
>[Android] amplifies all the Google services. It gives Google a extremely huge platform to present their products...There is no essential need for a strong Google Phone brand...Android could be a losing deal and it would still be worth the effort.
These are all true. But IMO it misses the forest for the trees, the forest in this case being the next computing form factor, ie the tablet being a successor rather than adjunct of laptops. That should be the goal, not just an extension to sell more wares.
To be the next "computer," the OS has to do more, akin to the range of functions on desktop OS'es. Android, like iOS, lacks basic underpinnings--things like built-in networking, printing, support for peripheral devices, apps interoperability, etc etc.
The shortcoming doesn't affect Apple, because iOS has achieved critical mass on phones and tablets. Its success engenders 3rd-party support to address any deficit faced.
The other aspect not oft mentioned is that a bona fide OS needs support. One takeaway from a quick scan through these and other (official) Android forums is that OS support is grossly inadequate. As much complaints as there are in this forum, Asus is actually one of the better vendors for support. Users of Acer, Toshiba, and others, have given up on support. And these are enthusiasts. Think of how worse it would be for normal users.
The writing is on the wall: HW vendors don't have the expertise to support the OS. Google needs to do it. But with its current distribution philosophy, ie making AOSP code public and let HW vendors do what they will, Google can't do that. For it to support its OS, Google will need to follow the Microsoft path.
Getting its hands dirty with its own hardware may be a start, assuming Google better supports its product. But customer support has never been in Google's DNA, so I have my doubt that things would improve soon.
Click to expand...
Click to collapse
You make some interesting points, but I disagree that iOS is anywhere near being accepted as a PC replacement. In many important ways, Android is much farther along in this respect--access to the file system alone is one area. And, I think the idea that tablets will replace PCs is way overblown--having tried to use mine (even with the keyboard dock) as a replacement for my Windows notebook, I can testify that although some things are more convenient with tablets (like ebook reading, casual surfing, etc.), NOTHING is as efficient as with a "real" PC.
I could never do my job on any existing tablet, whether it's iOS or Android. I work with complex documents, use Photoshop for more than changing color tones, do some light video editing, etc. None of those are efficient (or even possible) on a tablet. Even the simple things like browsing, Twitter, etc., etc., are more efficient on a notebook or desktop. Again, a tablet is convenient--lightweight, long battery life, etc.--so it has its place alongside a real PC. But thinking it can replace a PC for most people is, I think, entirely unrealistic at this point.
Maybe that'll change in a few years, although I doubt even that. Seriously, who can imagine working EXCLUSIVELY on a 10" screen? And if a tablet becomes something that you plug into external monitors and keyboards and such, well then, ASUS is already mostly there with the Transformer series. And at that point what we'll have is just a more portable PC with external accessories. Once a tablet becomes complex enough in terms of network support, printing, peripheral devices like scanners, etc., then is it really a "tablet" any longer?
..........
demandarin said:
Actually Google is already consdidering this. read several articles on it. it's a great idea bit one catch, Phone carriers would hate it. those companies add those GUI to devices to differentiate themselves from other similar devices. I'd rather have vanilla android experience and not have bloat ui on top of it. A GUI on top of vanilla android will never be faster out the box than a plain vanilla experience. one suggestion was to make the various companies GUI removable if the user chooses. they could use that companies GUI or go vanilla route or use one of the many launchers available on android. Usually a company GUI will be more integrated and stable than one from marketplace.
Click to expand...
Click to collapse
I was hearing at one point that Google was looking to simplify the custom GUI creation (just a custom GUI xml that the manufacturer can push that the vanilla OS will honor) so that even if there are large changes underneath by Google, there is no change needed by the manufacturer prior to release (assuming the manufacturer is only making GUI changes and not anything deeper).
sparkym3 said:
I was hearing at one point that Google was looking to simplify the custom GUI creation (just a custom GUI xml that the manufacturer can push that the vanilla OS will honor) so that even if there are large changes underneath by Google, there is no change needed by the manufacturer prior to release (assuming the manufacturer is only making GUI changes and not anything deeper).
Click to expand...
Click to collapse
that was what it was involving. thanks for pointing out those details.
Link doesn't work anymore!

Categories

Resources