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
http://www.hp.com/hpinfo/newsroom/press/2011/111209xa.html?mtxs=rss-corp-news
HP today announced it will contribute the webOS software to the open source community.
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/.
OK, so who's up for getting involved in this?
I'll test on my OV!
Comment 26 inShare352 HP Is Reviving The $99 TouchPad Firesale!
From a Tech Crunch article.
http://techcrunch.com/2011/12/07/hp-touchpad-ebay/
Refurb Models To Hit HP’s Ebay Store On 12/11
Starting Sunday, December 11th at 6:00 p.m. Central time, 16GB and 32GB Touchpads will be available on HP’s ebay store. A $79 accessory bundle will also be available, which includes a case, charging dock and wireless keyboard. Look for them in the laptop section. As you would expect, there are some caveats with this deal with the main disappointment being these are refurbished TouchPads rather than the brand new models sold during the first firesale.
The refurbished 16GB and 32GB models will be available in an unannounced quantity. Sales will be limited to just two SKUs per ebay member and PayPal must be used to complete the transaction. All sales are final and the product only comes with a 90-day warranty. HP wants these things gone.
------------------------------------------------------------------------------------------------------------
Sure it's not a phone, but it is a valid test platform and the tablets are highly integrated with the phones. Maybe with HP laptops and printers too, don't recall the specifics of integration with all the other platforms.
Of course they won't last long.
Disclaimer: I don not own any HP stock. I have a used PhotoSmart printer. If it has webOS on it I don't know where it is or how to interface with it.
glarepate said:
From a Tech Crunch article.
http://techcrunch.com/2011/12/07/hp-touchpad-ebay/
Refurb Models To Hit HP’s Ebay Store On 12/11
Starting Sunday, December 11th at 6:00 p.m. Central time, 16GB and 32GB Touchpads will be available on HP’s ebay store. A $79 accessory bundle will also be available, which includes a case, charging dock and wireless keyboard. Look for them in the laptop section. As you would expect, there are some caveats with this deal with the main disappointment being these are refurbished TouchPads rather than the brand new models sold during the first firesale.
The refurbished 16GB and 32GB models will be available in an unannounced quantity. Sales will be limited to just two SKUs per ebay member and PayPal must be used to complete the transaction. All sales are final and the product only comes with a 90-day warranty. HP wants these things gone.
------------------------------------------------------------------------------------------------------------
Sure it's not a phone, but it is a valid test platform and the tablets are highly integrated with the phones. Maybe with HP laptops and printers too, don't recall the specifics of integration with all the other platforms.
Of course they won't last long.
Disclaimer: I don not own any HP stock. I have a used PhotoSmart printer. If it has webOS on it I don't know where it is or how to interface with it.
Click to expand...
Click to collapse
surely they wud hav found more buyers in INDIA!!!!
THAT TOO AT A HIGHER PRICE....
Hey xda im writing a shortish informative essay for my language arts class. I was womdering if you guys would proofread it over and tell me im a dumbass if i got some of the facts wrong. I hope you guys will enjoy! Its a pleasure to be a part of this awesome community.
Thanks a bunch
-Silente
Nook Tablet Devs and Kindle Fire Devs working together!
In the fall of 2011, two average-priced E-reader/Tablet crossover devices were launched. The Kindle Fire was made by Amazon in order to enter the tablet realm with the name of their successful e-reader line stamped on its back. The other, the Nook Tablet was Barnes and Nobles second venture into the tablet realm, with their Nook Color that was released in 2010 being the first. These two device's releasing marked a new price range for tablets, with most tablets costing anywhere from $300-$500. The Kindle Fire sold for a low $200 which was a great entry level price for people who had been wanting a tablet but had not been wanting to shell out the bug bucks for it. Whereas the Nook Tablet was $50 more at $250 but boasted a better screen, twice the storage space and an expansion slot where you could put in up to 32GB more. The two were locked in mortal combat and as time went on it became apparent that the Kindle Fire was the consumer favorite, mainly because of its farther developed app store and built-in Amazon media services. The Nook's problem was that Barnes and Noble hand-picked all of the apps for its app store and thus didn't have as wide of a selection. The Kindle Fire went on to actually become a direct competitor to Apple's famed iPad while the Nook continued to simply be an e-reader tablet, and didnt make as big a splash in the world of technology.
Now as tablets go, both were quite a good deal for what you paid for them and thus were prime targets for developers. A good value at some of the lowest prices in the tablet market, whats not tol ike? And so in the first few months after their release, both the tablets started to have strong and vibrant development communities, people who were committed to breaking through the restrictions set up on both of the tablet's by their manufacturers. As time went on the Kindle Fire proved to be the easier development platform because of Barnes and Noble's restrictive bootloader. A piece of software built into the Nook Tablet that wouldn't allow it to run any software except Barnes and Nobles. Eventually though the Nook Tablet's boot loader was cracked and the devs surged through the cracks they had made, working through rooting the Nook and eventually even running a custom made version of a popular android mod CyanogenMod7. Meanwhile though, the Kindle Fire devs had not been idle, they had rooted and modded the Kindle Fire even so far as to get the latest versionofAndroid (Ice Cream Sandwich) somewhat running on the Fire. At this point though, both development communities had hit a brick wall so to speak. To go any further in running Ice Cream Sandwich on either device, they would need to re-build a 3.x kernel from scratch. Both devices came running a 2.x kernel and up until then both of the dev communities had used that to base their mods off of. It was a huge task but both dev communities tackled it valiantly and began to make progress. But then an event came around that would change the course of the 3.x kernel development infinitely for the better!
On March 1st 2012, Hashcode; one of the leading developers from the Kindle Fire development group contacted Team A from the Nook Tablet development, pointing out the similarities in the two devices they coded for and proposed that they begin to help each other by letting the other's team use bits of code in order to better both of their 3.x kernel development projects. Merely 18 minutes later, Fattire; the leading developer for Ice Cream Sandwich on the Nook Tablet side of things, replied back that it would be great if the co-operation started up because they could simply cherry-pick the parts of code that they needed from each other's projects. it would be "Good Times" as Fattire put it. Now as both the teams work doggedly to get the 3.x kernel built, both the groups know that the work load has been lightened a bit and that the two dev communities may become more of friends instead of enemies each defending their turf, or in this case respective tablets. Its all uphill from here,but hopefully the two communities can help each other climb that hill a little faster on both sides.
Sent from my Nook Tablet using xda premium
And to make it even more amazing is a number of the devs making breakthru's didn't even have the product in hand.
~ G
SilentStormer said:
Hey xda im writing a shortish informative essay for my language arts class. I was womdering if you guys would proofread it over and tell me im a dumbass if i got some of the facts wrong. I hope you guys will enjoy! Its a pleasure to be a part of this awesome community.
Thanks a bunch
-Silente
Nook Tablet Devs and Kindle Fire Devs working together!
In the fall of 2011, two average-priced E-reader/Tablet crossover devices were launched. The Kindle Fire was made by Amazon in order to enter the tablet realm with the name of their successful e-reader line stamped on its back. The other, the Nook Tablet was Barnes and Nobles second venture into the tablet realm, with their Nook Color that was released in 2010 being the first. These two device's releasing marked a new price range for tablets, with most tablets costing anywhere from $300-$500. The Kindle Fire sold for a low $200 which was a great entry level price for people who had been wanting a tablet but had not been wanting to shell out the bug bucks for it. Whereas the Nook Tablet was $50 more at $250 but boasted a better screen, twice the storage space and an expansion slot where you could put in up to 32GB more. The two were locked in mortal combat and as time went on it became apparent that the Kindle Fire was the consumer favorite, mainly because of its farther developed app store and built-in Amazon media services. The Nook's problem was that Barnes and Noble hand-picked all of the apps for its app store and thus didn't have as wide of a selection. The Kindle Fire went on to actually become a direct competitor to Apple's famed iPad while the Nook continued to simply be an e-reader tablet, and didnt make as big a splash in the world of technology.
Now as tablets go, both were quite a good deal for what you paid for them and thus were prime targets for developers. A good value at some of the lowest prices in the tablet market, whats not to like? And so in the first few months after their release, both the tablets started to have strong and vibrant development communities, people who were committed to breaking through the restrictions set up on both of the tablet's by their manufacturers. As time went on the Kindle Fire proved to be the easier development platform because of Barnes and Noble's restrictive bootloader. A piece of software built into the Nook Tablet that wouldn't allow it to run any software except Barnes and Noble's. Eventually though the Nook Tablet's boot loader was cracked and the devs surged through the cracks they had made, working through rooting the Nook and eventually even running a custom made version of a popular android mod CyanogenMod7. Meanwhile though, the Kindle Fire devs had not been idle, they had rooted and modded the Kindle Fire even so far as to get the latest versionofAndroid (Ice Cream Sandwich) somewhat running on the Fire. At this point though, both development communities had hit a brick wall so to speak. To go any further in running Ice Cream Sandwich on either device, they would need to re-build a 3.x kernel from scratch. Both devices came running a 2.x kernel and up until then both of the dev communities had used that to base their mods off of. It was a huge task but both dev communities tackled it valiantly and began to make progress. But then an event came around that would change the course of the 3.x kernel development infinitely for the better!
On March 1st 2012, Hashcode; one of the leading developers from the Kindle Fire development group contacted Team A from the Nook Tablet development, pointing out the similarities in the two devices they coded for and proposed that they begin to help each other by letting the other's team use bits of code in order to better both of their 3.x kernel development projects. Merely 18 minutes later, Fattire; the leading developer for Ice Cream Sandwich on the Nook Tablet side of things, replied back that it would be great if the co-operation started up because they could simply cherry-pick the parts of code that they needed from each other's projects. it would be "Good Times" as Fattire put it. Now as both the teams work doggedly to get the 3.x kernel built, both the groups know that the work load has been lightened a bit and that the two dev communities may become more of friends instead of enemies each defending their turf, or in this case respective tablets. Its all uphill from here,but hopefully the two communities can help each other climb that hill a little faster on both sides.
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
Two proof issues (Red text in quote)
It's nitpicking, but, I wouldn't use abbreviated words (such as "devs" and "mods") without explaining what they are abbreviations for. It might confuse an audience unfamiliar with the parlance of the community. Especially not in the title.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Birdsbeaks said:
It's nitpicking, but, I wouldn't use abbreviated words (such as "devs" and "mods") without explaining what they are abbreviations for. It might confuse an audience unfamiliar with the parlance of the community. Especially not in the title.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Click to expand...
Click to collapse
Thanks youre probably right
Thanks for all the suggestions guys!
Sent from my Nook Tablet using xda premium
change bug bucks to big bucks
Nook Tablet Devs and Kindle Fire Devs working together!
In the fall of 2011, two average-priced E-reader/Tablet crossover devices were launched. The Kindle Fire was made by Amazon in order to enter the tablet realm with the name of their successful e-reader line stamped on its back. The other, the Nook Tablet was Barnes and Nobles second venture into the tablet realm, with their Nook Color that was released in 2010 being the first. These two device's (devices') releasing (release) marked a new price range for tablets, with most tablets costing anywhere from $300-$500. The Kindle Fire sold for a low $200 which was a great entry level price for people who had been wanting a tablet but had not been wanting (had wanted a tablet but were unwilling) to shell out the bug bucks (big bucks) for it. Whereas the Nook Tablet was $50 more at $250 but boasted a better screen, twice the storage space and an expansion slot where you could put in up to 32GB more (get an additional 32GB's worth via microSD cards) . The two were locked in mortal combat and as time went on it became apparent that the Kindle Fire was the consumer favorite, mainly because of its farther developed app store and built-in Amazon media services. The Nook's problem was that Barnes and Noble hand-picked all of the apps for its app store and thus didn't have as wide of [delete] a selection. The Kindle Fire went on to actually become a direct competitor to Apple's famed iPad while the Nook continued to simply be an e-reader tablet, and didnt make as big a splash in the world of technology.
My suggestions for the first paragraph. I leave the rest to others.
That was a good read.Hope you do well with it.
The complicated, detailed history...
SilentStormer said:
On March 1st 2012, Hashcode; one of the leading developers from the Kindle Fire development group contacted Team A from the Nook Tablet development, pointing out the similarities in the two devices they coded for and proposed that they begin to help each other by letting the other's team use bits of code in order to better both of their 3.x kernel development projects. Merely 18 minutes later, Fattire; the leading developer for Ice Cream Sandwich on the Nook Tablet side of things, replied back that it would be great if the co-operation started up because they could simply cherry-pick the parts of code that they needed from each other's projects. it would be "Good Times" as Fattire put it. Now as both the teams work doggedly to get the 3.x kernel built, both the groups know that the work load has been lightened a bit and that the two dev communities may become more of friends instead of enemies each defending their turf, or in this case respective tablets. Its all uphill from here,but hopefully the two communities can help each other climb that hill a little faster on both sides.
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
Hey Silente!
Here's even more of the "inside story" if you want it-- the cooperation between KFire and NT goes back even further than what you report. In fact, I was contacted in PM a few months back by KFire developer "JackpotClavin" who had some questions regarding, if I remember right, some issues that came up w/the Nook Color that he thought might apply themselves to CM7 (and later ICS) for the Fire. So he and I had been exchanging messages back and forth for some time on various topics, since the devices are so similar. Then weeks after that, right after I had upgraded the "pvr"driver for NT to 2.6.35, I wanted to update some of the other advanced stuff (ion, tiler,etc.) and noticed that Hashcode (who I think I had spoken to once before) had already committed a lot of this work, or at least an attempt was made, for fire. So I adopted his work as a basis for porting it for NT, and after a few more days of struggling, I contacted him with questions, and we started talking in more detail. He was a HUGE help for me to understand what tiler and ion and all that even were plus issues he had encountered, etc. Ultimately that tiler/ion stuff didn't work out for 2.6.35 though.
Then a few weeks LATER, Kuzma30 (with chrmhoffmann and others) were making some serious progress with 3.0x, but we didn't have any history and the wrong pvr and I wasn't sure if it was using the right kernel to start with. So I switched to the Google version of the 3.0 kernel and used the Nexus Galaxy branch as a base for kuzma30's 3.0 work so that we would have a "known" place to start (and compatibility with video files used by the Nexus Galaxy) as well as all the history from TI and google. So I took kuzma30's stuff and add it THAT to the "end" of the source code. Doing this seemed to run well, and we had graphics, and soon touchscreen, and this became the basis for further work. And that's when what is in your essay began-- Hashcode decided to use the successes we had had with 3.0 as a basis for doing the same on the KFire, since they are so similar. that's when he branched the source for KFire and introduced himself to everyone on the forums...
Anyway, this is probably way too much info and probably too technical and even boring, but I just wanted to point out that the spirit of cooperation has been going on for a while-- there is no "turf" between devices, at least as far as I'm aware. The more the merrier! Your essay looks great btw- it's an honor to be mentioned, so thanks, and good luck with it!
ft
fattire said:
Hey Silente!
Here's even more of the "inside story" if you want it-- the cooperation between KFire and NT goes back even further than what you report. In fact, I was contacted in PM a few months back by KFire developer "JackpotClavin" who had some questions regarding, if I remember right, some issues that came up w/the Nook Color that he thought might apply themselves to CM7 (and later ICS) for the Fire. So he and I had been exchanging messages back and forth for some time on various topics, since the devices are so similar. Then weeks after that, right after I had upgraded the "pvr"driver for NT to 2.6.35, I wanted to update some of the other advanced stuff (ion, tiler,etc.) and noticed that Hashcode (who I think I had spoken to once before) had already committed a lot of this work, or at least an attempt was made, for fire. So I adopted his work as a basis for porting it for NT, and after a few more days of struggling, I contacted him with questions, and we started talking in more detail. He was a HUGE help for me to understand what tiler and ion and all that even were plus issues he had encountered, etc. Ultimately that tiler/ion stuff didn't work out for 2.6.35 though.
Then a few weeks LATER, Kuzma30 (with chrmhoffmann and others) were making some serious progress with 3.0x, but we didn't have any history and the wrong pvr and I wasn't sure if it was using the right kernel to start with. So I switched to the Google version of the 3.0 kernel and used the Nexus Galaxy branch as a base for kuzma30's 3.0 work so that we would have a "known" place to start (and compatibility with video files used by the Nexus Galaxy) as well as all the history from TI and google. So I took kuzma30's stuff and add it THAT to the "end" of the source code. Doing this seemed to run well, and we had graphics, and soon touchscreen, and this became the basis for further work. And that's when what is in your essay began-- Hashcode decided to use the successes we had had with 3.0 as a basis for doing the same on the KFire, since they are so similar. that's when he branched the source for KFire and introduced himself to everyone on the forums...
Anyway, this is probably way too much info and probably too technical and even boring, but I just wanted to point out that the spirit of cooperation has been going on for a while-- there is no "turf" between devices, at least as far as I'm aware. The more the merrier! Your essay looks great btw- it's an honor to be mentioned, so thanks, and good luck with it!
ft
Click to expand...
Click to collapse
Thanks for reading it, ive just turned it in today but i didnt see your post until now
Its cool to see that theres so much collaboration going on between these two similar dev communities. And as for the "turf" thing i guess at my school and around the general surface of the internet ocean theres a lot of competition between things. Phones, clothes, computers, tablets etc etc and i guess since im somewht new to fhe dev community i still have that "competition" mindset. Thats just something i guess i realized just now
Thanks again
Noone at my school will understand half of this essay
-Silente
Sent from my Nook Tablet using xda premium
Thought I would bring this up here, given how many of us like to game with emulators on our Shield Tablets.
It is currently on Kickstarter, but the thing about this one is that the actual product already exists and works - the guy has been making similar adapters for years with very good feedback. The funding is needed to rationalise the production costs by being able to order a large enough run on parts.
Anyone interested in a product like this please back this one and share it widely to social media, this missed funding on one round already given it's relatively niche appeal.
NZtechfreak said:
Thought I would bring this up here, given how many of us like to game with emulators on our Shield Tablets.
It is currently on Kickstarter, but the thing about this one is that the actual product already exists and works - the guy has been making similar adapters for years with very good feedback. The funding is needed to rationalise the production costs by being able to order a large enough run on parts.
Anyone interested in a product like this please back this one and share it widely to social media, this missed funding on one round already given it's relatively niche appeal.
Click to expand...
Click to collapse
Maybe it wasn't noticed by advertising it in an Android tablet section of a modding site... :/