Hi all,
Is LineageOS planning on continuing support for Shield through the new releases in 2019? I understand that there's some rumors circulating about the chipset specifications as well as the question of the new Pro retaining all hardware and only having an overclocked CPU, so I assume this all needs to be looked into before discussions begin. Would be great to get out of the "walled Garden" sooner than later.
Related
Wrong: CYANOGENMOD 7 RELEASED, HARMONY SUPPORT, DIDN'T NOTICE ANY POSTS REFERING TO IT
Right: CM7 was released, with Harmony support.
Wrong: SHAME THAT NVIDIA ARE NOT SUPPORTING DEVELOPMENT FOR HARMONY CHIP FROM 2.2 ONWARDS IF REPORTS ARE TRUE
Right: It's a shame that nVidia isn't supporting Harmony developers from 2.2 onwards, if reports are true.
Mod Edit: All caps is annoying. Please don't use it. Thanks.
Yes if you actually look at the other CM7 threads you will see that the Vega changes have been added to the official tree now.....
and how can you go and say that we have cm7 (2.3) and then complain about the lack of nvidia support beyond 2.2 in the same post, completely contradicts itself....
but doesnt the tegra 2 already power a bunch of honeycomb tablets already?
mintvilla said:
but doesnt the tegra 2 already power a bunch of honeycomb tablets already?
Click to expand...
Click to collapse
there are two types of tegra 2 boards, Harmony which the vega has supported to android 2.2 and Ventana which the xoom has, supported beyond 2.2
Useless posts removed, OP reformatted. All caps is just annoying.
Also, thank you Lennyuk for your expertise. I actually wasn't aware of the two Tegra 2 revisions. What are the differences between Harmony and Ventana?
willverduzco said:
Useless posts removed, OP reformatted. All caps is just annoying.
Also, thank you Lennyuk for your expertise. I actually wasn't aware of the two Tegra 2 revisions. What are the differences between Harmony and Ventana?
Click to expand...
Click to collapse
as far as I know there is not actually a great deal of differences between the two, I think the ventana board has an extra GPU slot, that might be it.
Lennyuk said:
as far as I know there is not actually a great deal of differences between the two, I think the ventana board has an extra GPU slot, that might be it.
Click to expand...
Click to collapse
Interesting. I wonder why that would be since these SOCs don't have modular components, with the GPU being directly integrated into the SOC itself... Weird.
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 CorporationTop
Sent from my HTC Desire using XDA App
Interesting update something for developers to get teeth into sometime
Sent from my HTC Desire using XDA App
Mod Edit: All caps is annoying. Please don't use it. Thanks.[/QUOTE]
haha to right
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.
*
Sent from my HTC Desire using XDA App
Caps from original nvidia forum post.
Stop being so anal anyway
Sent from my HTC Desire using XDA App
Can anyone translate this for me? Are we (Advent Vega users) getting the Tegra 2 update? And is this the one for Honeycomb?
From what I can tell, Yes. Or am I reading this wrong?
GaiusSensei said:
Can anyone translate this for me? Are we (Advent Vega users) getting the Tegra 2 update? And is this the one for Honeycomb?
From what I can tell, Yes. Or am I reading this wrong?
Click to expand...
Click to collapse
There is no "Tegra 2" Update
You are getting confused.
Basically when the Tegra2 boards were given to manufacturers they had one of two designs
Harmony which the vega has
or Ventana which newer tablets have
These are not set in stone, they were just designs that then get built to specific needs by each manufacturer.
Nvidia are not releasing their own stock images beyond android 2.2 for Harmony however they have made it very clear that it is down to each manufacturer to do this, Nvidia will support the manufacturers for as long as they want to continue service on each device.
Advent do not yet know if the manufacturer (Shuttle) will give us a HC rom, however at least 2 other clones of the Vega have confirmed it, so it looks promising.
Point of View is supposed to deliver us a fresh HC ROM, I would be really thankful!
All I need is a rom w/o cellphone stuff, just tablet things to work always with optimizations and no slow downs.. That's why I bought a tablet with tegra... but after news like this, customers like me get pretty sad and will regret buying another device from them. Gz;
As it appears they have had either a change of heart or the community is large enough to have a voice..
Mar 16 2011 at 12:07 AM #1
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 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.
ORIGINAL 16 MARCH 2011:
NVIDIA is only supporting the Ventana platform for android releases going forward. At the moment we have released Froyo and Gingerbread OS images for Ventana and will release Honeycomb after Google has done so.
Andrew Edelsten
Tegra Developer Relations
NVIDIA Corporation
SOURCE(s):
http://developer.nvidia.com/tegra/forum/honeycomb-harmony
http://notioninkhacks.com/index.php/2011/04/12/huge-problem-on-the-honeycomb-front/
http://conclave.notionink.com/showt...mb-on-Harmony-NVIDIA-s-Official-Stance&p=1281
I was messing around the internet in http://pdadb.net/index.php?m=pdamaster&posted=1&cpu=a20aph looking at other AP20H devices, when I suddenly found this little nugget of info:
Sony tablet S, Sony Tablet P, and KDDI Asus Tough ETBW11AA are all supposedly AP20H devices running honeycomb.
Assuming that the internet isn't wrong, Is it possible that these devices are running a newer kernel version that could dissected for our benefit?
Sorry if this is a wild goose chase, but I thought it was worth letting more knowledgeable people than me figure out if this had any merit.
This might be of help, sorry if it is not.
http://forum.xda-developers.com/showthread.php?p=22101686
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
If Vulkan API is implemented at our phone it would be fantastic. Hope Asus will work on the API and make the best for our phone, let's see in a couple of months of so
Too good to be true man, too good to be true.
hi, I'm very interested in everything about vulkan since i could see some videos about it. But my knowledge about api, android and rom's is not that good, so i would thank you if i could get some answers.
1 - Is this implementation of API a work for ASUS or Intel?
2 - Since i saw that PowerVR Rogue has now SDK(i dont know what it is) for Vulkan, Is ANYONE able to make a custom rom that could use Vulkan?
3 - I've heard that Android N will have native support for Vulkan. Does it mean that if i download a custom rom, like a cyanogenmod, for Android N to my Zenfone 2 i will have the benefits of using Vulkan?
4 - Does anyone know if that Galasy S7 that had 135k+ on antutu was using Vulkan? Because my Zenfone 2 is a great phone and only scores 65k, it's scary to thing that a S7 should have more than the double of hardware capacity that my Zenfone has. I thing that should be because of vulkan, but i need to hear it from someone who knows what's talking.
I hope to get answers for this questions. Thank you all.
SSJMatt said:
)Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
Click to expand...
Click to collapse
Sorry, that's not how ASUS usually manages fixes and updates. That would take time and money and we've already spent our money so they have nothing to gain, therefore nothing will happen. Only future customers are a priority for ASUS.
A happy ASUS customer is one with low expectations.
Well, at least It'd give Asus a good excuse for being so late...
Vulkan is something that would need to be implemented at the OS level on Android (mainly the kernel, no idea what other bits Google is including in the rest of the OS). And support for each hardware would need to be provided by the OEM or manufacturers. It MAY be possible for a custom ROM to implement Vulkan support in some fashion in a current version of Android (harder and more "impossible" things have been accomplished) but it's not likely due to too many technical challenges. Besides, it wouldn't happen until after Android N is released and the AOSP code is posted. Only then would someone attempt to backport Vulkan.
I'm not 100% sure, but I do believe that Vulkan support will be a requirement by Google for devices to run Android N. So if Asus does plan on upgrading the phones then they will need to include a kernel for the hardware that supports Vulkan and those drivers would come from Intel. So the chance of the Zenfone supporting Vulkan is 100%, provided Asus upgrades it to N.
SSJMatt said:
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
Click to expand...
Click to collapse
So is the VULCAN API present in the M update?
Is Vulkan something like the Mantle for Desktops?
EDIT:
Vulkan Drivers for Nexus Player
Google’s Android Image
As part of the Android N Developer Preview 2 release, Google released an Android N image for the Nexus Player that includes Vulkan drivers. You can find out more about the Android N Developer Preview here and can download the image here. As this image is officially supported by Google, we recommend using it for Vulkan Android development.
Click to expand...
Click to collapse
https://community.imgtec.com/developers/powervr/vulkan/
There is two possibilities:
1- Vulkan added in Android N's mainline code, and CM14 (maybe) will do this too.
2- Vulkan driver will be only in manufacters Android N's source. In this case, will be needed to be backported.
In both possibilites, isnt impossible to do it, even without Asus help. But would be awesome if some official MM give it to us (not in the first version, obviously).
Its GPU manufacturer job to implement vulkan, they provide the drivers to OEM manufacturer implement it on their otas. Nvidia already did that on latest MM update to shield TV and shield tablet.
Dear all,
I guess we all agree that the SATV is one hell of a machine in terms of value per money, especially hardware-wise. However, being sold with only Android TV doesn't unlock its full potential, so people went on and flashed Ubuntu or L4T on their Shields.
As far as it seems GPU support was always missing due to Nvidia not releasing their sources.
However, that changed in February (hxxp://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=8d1fd61a3723ab8cb6b7bfeb8be38e16282cc1ed) and was even patched in March (hxxps://lists.freedesktop.org/archives/nouveau/2016-March/024305.html) for re-clocking.
I wonder now why it has not been incorporated or am I missing something?
I have to say though that I'm not a coder myself. Otherwise I'd love to do it on my own.
Best,io