HP released Version 1.0 of OpenWebOS the end of September. Their WebOS-Ports team has produced a running version of OWOS for the GNexus device. Some stuff is still missing or WIP, but the OS itself boots and runs.
They have even released the source and toolchain for the port.
I would love seeing this run on the Tab.
Me too.
Although there would be no third-party apps as HP isn't licensing the App Catalogue (yet).
Related
Just noticed this over on Notion Ink's website...
Android 2.3 comes with Kernel version 2.6.35. The latest which NVidia Tegra works with is 2.6.36! http://android.git.kernel.org/?p=kernel/tegra.git;a=summary
Click to expand...
Click to collapse
Perhaps some one far smarter than me can make use of this info...
I don't think the stock tegra kernel has all the drivers necessary for the G Tablet. Because I think people have known about that repository, and as far as I know, nobody's built their own kernel that's worked with the G Tablet, but rather have been using kernels pre-built for the G Tablet or the ZPad.
This is why people keep talking about wanting the source from Viewsonic.
But if somebody wants to try doing a kernel build and seeing what does or doesn't work, more power to you!
This is actually only sort of related, but I noticed screenshots a few days ago of what was supposedly 2.3, but the about phone item show a 2.6.29 kernel version like 2.0 & 2.1 use, while 2.2 uses 2.6.32, and I knew that 2.3 was also getting a kernel update..
Oddly enough noone commented on that in the comment section on that site, and I just couldn't be bothered to create an acct to comment...
I've searched nvidia's git repo for our touchscreen drivers and they are not there. Therefore, trying to build from nvidia's git for the gtab won't do us any good until Viewsonic (malata, etc.) posts the kernel source.
this may sound silly. but can we somehow maybe get drivers from the touchscreen for the tegra? instead of looking for drivers from nvidia for the screen can we look for drivers from the screen maker for the tegra?
Bukem75 said:
Just noticed this over on Notion Ink's website...
Android 2.3 comes with Kernel version 2.6.35. The latest which NVidia Tegra works with is 2.6.36! http://android.git.kernel.org/?p=ker....git;a=summary
Perhaps some one far smarter than me can make use of this info...
Click to expand...
Click to collapse
Their NI Adam is not coming with Android 2.3, it comes with the scandal or it's hardly coming in at all: http://fineoils.blogspot.com
This is a preemptive note about posting any new threads asking "when will honeycomb come to the gTablet?" or "why can't we do this because the Nook has it?" or "why isn't the sky blue today?"
Honeycomb is not available for the gTablet yet for the following reasons:
1. source hasn't even been released by Google yet
2. any port based on the SDK doth not a Honeycomb ROM make
3. we do not even have libraries (or source) from nVidia for Gingerbread yet
Until we have source from Google and nVidia, we won't have workable Honeycomb. There will be some ports, but until one of the above happens, we are not going to be getting Honeycomb. Best case is 30 days from now (roughly the end of March).
Any post asking about Honeycomb will be promptly closed and/or deleted.
This isn't about discouraging discussion about Honeycomb on the gTablet - it's about stopping the endless flaming and abuse and posting and complaining about something that has been answered multiple times - thus taking away from other progress and endeavors.
UPDATE 3/18/11 - We now have access to the Gingerbread libs needed for hardware acceleration, but in order to use them a complete rework of the github repo is required and a year's worth of merges and cleanups would need to be done. Slow going and no ETA.
UPDATE 4/12/11 - http://www.androidcentral.com/nvidia-stop-supporting-harmony-platform-past-froyo
UPDATE 4/13/11 - http://developer.nvidia.com/tegra/forum/honeycomb-harmony#comment-6191
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.
UPDATE 5/10/11 - There is now a pretty hacked together port of HC that has been ported to the gTablet - it is a mashup of other, authorized by Google tablets which have stock HC on them, and thrown together for Vega, Adam and gTablet. A lot doesn't work; it is not feature perfect..... it is only recommended for testing type users who are familiar with nvflash etc. and it is not built from source specifically for our devices. It is by no means official, nor is it what would probably be called "stable" - but it is as close as we've come to HC on the gTablet. Here is the post that has more information: http://forum.xda-developers.com/showthread.php?t=1065220
UPDATE 5/10/11 - Per Google I/O's Fireside chat today there will be no Honeycomb source released. Ever. You'll have to wait for Ice Cream Sandwich which will be out in Q4 2011.
UPDATE 5/14/11 - The ADAM/VEGA/ZPAD/GTAB port of the mashup Transformer/Iconia/Xoom Honeycomb systems is coming along nicely. See the above thread for more information. Good work to the devs involved in that project.
Hi there, just been reading about this after I found it on a gadget website this morning . hopefully it'll ship to tablets soon..... or if the devs in here, mdj and dexter are feeling generous they may buy one of the new tablets and port it over perhaps??
http://2dayblog.com/2011/06/23/android-3-2-coming-this-summer/
quick quote if you aren't allowed external site access and youre reading from your xda app.
"Yesterday we saw the launch of the world’s first Android 3.2 tablet, Huawei’s MediaPad. However, it seems it won’t be long until we see more tablets running 3.2, as the build is set for release this summer.
Android 3.2 doesn’t offer much in the way of features. This is my next reports that it does contain some bug fixes and improved hardware acceleration, but the biggest thing is that it will bring support for Qualcomm processors as well as Nvidia’s popular Tegra 2 chipset.
The Motorola Xoom will reportedly get Android 3.2 in the next few weeks, but Qualcomm support could mean that current 7-inchers (like the HTC Flyer) may also get the update. Fingers crossed!"
So seeing as the Xoom is getting it in the next few weeks, lets give support to our devs and maybe the A500 may get it also.
HC 3.2 is just 3.1 optimised for 7" tablets. Of no real relevance to Acer Iconia A500 users. It really should have been called 3.11 but then that might have recalled some scary memories for seasoned Windows users.
tonyblack said:
HC 3.2 is just 3.1 optimised for 7" tablets. Of no real relevance to Acer Iconia A500 users. It really should have been called 3.11 but then that might have recalled some scary memories for seasoned Windows users.
Click to expand...
Click to collapse
I remember those days, LOL
daswahnsinn said:
I remember those days, LOL
Click to expand...
Click to collapse
Yeah, trying to get a Windows 3.11 PC connected to a novell netware network using thinnet cable, made even Linux administration seem easy.
tonyblack said:
HC 3.2 is just 3.1 optimised for 7" tablets. Of no real relevance to Acer Iconia A500 users. It really should have been called 3.11 but then that might have recalled some scary memories for seasoned Windows users.
Click to expand...
Click to collapse
I got nostalgic for my first Windows PC, so I'm running my old "friend" Windows 3.11 on my Iconia using DOSbox.
In relevance to the thread though:
"Tech site This Is My Next, however, reports that Android 3.2 Honeycomb will be the last in the Android 3.x series and that it has several new features:
- optimized for 7-inch devices,
- expands support for more mobile processors such as NVIDIA Tegra 2 and Qualcomm’s processors,
- fixes some bugs and improves hardware acceleration, and
- provides updates to widgets and apps (e.g., Movies, Movie Studio, Music, etc.)."
http://www.androidauthority.com/google-brings-out-quickie-android-3-2-honeycomb-update-17253/
NOTE: These drivers CAN NOT BE INSTALLED! These drivers were also NOT used by the Cyanogen Team for porting purposes as by using these drivers, you would not be able to use webOS. I am only posting these drivers as evidence, and for research/educational purposes, and it is in the DEVELOPMENT category as such.
Greetings,
This morning's news article here on XDA revealed some newly released information regarding the fact that HP actually installs Android on every Touchpad device during the manufacturing for testing purposes, and that the recent devices brought to light that were bought preinstalled with Android 2.2 were devices that for some reason were not flashed with webOS after the testing process. Now that the Cyanogen Team has officially released the alpha for CM7.1 for the Touchpad, and the news of HP's doings with the Touchpad has come to light, I feel that I should release this.
In late August, multiple people who were working on porting Android to the HP Touchpad were sent an anonymous email containing a zip (attached) which contained a copy of an email, along with Android touchscreen drivers. Based on the contents of the email, and other information we had collected, we determined that the email was from a Cypress Semiconductors employee, and we presumed that it was leaked to us by a Cypress or possibly HP insider. Our presumptions were even more reinforced once we examined the source code of the drivers that was included, which was VERY advanced as it was much more accurate than the webOS Touchscreen drivers that was shipped with the device. From this, we have determined that most likely these drivers were used for testing the hardware during the manufacturing process, as stated in the email.
You may ask why does this matter... the fact is that HP has continued to deny that they do not have any Android build for the Touchpad and they are not responsible for the devices shipped with Android 2.2. While I am almost positive that HP did not have the intent to distribute these devices, the fact is that they did get out... and they were not just found in a dumpster, or it somehow "got legs and walked out of the factory"... HP sold these devices. They first sold them to retailers (Best Buy and Walmart), and at least three of these were confirmed to have been sold to consumers (with a possible fourth device being investigated by us today). So although HP did not intentionally release these devices, these devices have been sold at retail stores in different parts of the US... and HP still has not released the kernel source code.
The GNU General Public License is the license that the Linux Kernel is under, and thus all derivatives must be licensed under... including webOS and Android. Basically, the GPL requires that any changes made to a the Linux kernel source code must be re released to anyone requesting it if whatever it is that uses that kernel is released to the public... regardless of intention. We know that HP released these devices, and we know that HP uses Android for testing of the devices, and that they are violating the GPL by not releasing the kernel source code.
Anyways, what you have all been waiting for... Here is a copy of the attachment sent to us anonymously by the presumed Cypress/HP insider. http://trsohmers.com/files/touchpad/CY8CTMA395_Android_Drivers.zip
From the official CM blog:
It’s been awhile since the last update and I just wanted to let everyone know about our progress with CM9. As I mentioned in the previous update, Android 4.0 contains many internal changes that require updated graphics drivers. Unfortunately, these drivers are almost always closed-source and don’t appear until a device or devkit is released with them. For many devices, our hands are tied. Some very clever workarounds have gone into CM9, but we’re still blocked on some subsystems like the camera.
Since Android 4.0 is such a major change from 2.3, we started with a fresh codebase from Google and have been forward-porting features from CM7 with an eye on design and better integration. This is a somewhat time-consuming process, but it allows us to rethink everything. We’ve eliminated the CMParts app, instead choosing to add our custom features directly into the main settings. We are also taking a “just works” approach when it comes to configuration- CM7 had too many options that just weren’t widely used. We hope to achieve a good balance between tweakability and a great out-of-the-box experience. I want your phone or tablet to feel like it should have come with CM9.
Currently, you can compile CM9 for a small number of devices- notably the Samsung Galaxy Nexus and Nexus S, the Samsung Galaxy Tab 10.1 (Wi-Fi and T-Mobile versions), the HP Touchpad and Motorola Xoom. The next devices to show up will likely be a whole array of Samsung phones (Exynos chipset), with devices based on the Qualcomm MSM8660 and 7×30 chipsets to follow. It’s still unclear if we can provide support for the QSD8x50 family of devices (Nexus One, HTC Evo, etc), but the answer almost always turns out to be “yes” for these kinds of things.
As our hardware support improves, I’ll keep this blog updated. As much as we’d like to stay ahead of the manufacturers, it may be a tie this time Thanks for the continued support, and please consider dropping us a buck or two using the link at the bottom of the page if you enjoy CyanogenMod.
Click to expand...
Click to collapse
While it doesn't say specifically, it looks like we'll be getting official CM9 support!
The day that is released (stable) will mark the day of my first non-stock flash of the Note.