Related
not my artical just found it orig web page
androidandmeDOTcom/2010/04/news/android-2-2-is-coming-what-features-do-you-want/
replace dot = .
Android 2.2 is coming. What features do you want?
By Taylor Wimberly on Apr 20267
The majority of Android phones are still running an outdated firmware, but that hasn’t slowed Google from advancing their mobile operating system. Everyone knows the next version of Android (codenamed Froyo) is on the way and the rumors (1, 2) are beginning to pick up that the Nexus One will receive it soon.
Based on the data from our analytics reports it appears Google has already begun testing on their next firmware – Android 2.2. Google engineers have routinely given codenames to future builds of Android (Eclair, Froyo, Gingerbread, etc.), but they don’t receive a point release till they are finalized and nearing distribution.
We have shared this reporting data before and people are always quick to point out that it can be easily faked, but I have spoke with additional sources familiar with the matter who confirmed Android 2.2 is currently being tested.
The feature set for Android 2.2 was frozen long ago, but it remains mostly unknown. Google decided last year that they would no longer publish public roadmaps for future versions of Android. Based on the information we can gather, it appears Android 2.2 will mainly focus on performance enhancements.
Some of the rumored features for Android 2.2 include:
•JIT compiler
•Free additional RAM
•OpenGL ES 2.0 enhancements
•Flash 10.1 support
•Fixed problem with “crazy screen” / Resolution of cross multitouch
•Activation of Color Trackball
•Enable FM radio
Some of these features are plausible and others we have no clue.
The JIT compiler has already been confirmed by Google and we expect to find out new details during Google I/O. Android engineers will be leading a discussion that informs devs how to test and tune their apps to work with the new compiler.
Additional free RAM should come thanks to the new Linux kernel being used in Froyo. Google is moving from 2.6.29 to the newer 2.6.32 which makes it possible to address the extra RAM. This has already been done in custom ROMs like CyanogenMod so expect this feature for sure.
I’m no expert on OpenGL, but it has long been rumored that Froyo (or a future build) will add new APIs to the Android NDK which will let Java devs have full access to the OpenGL ES 2.0 library.
Flash 10.1 is coming in the first half of the year. It is entirely possible it could be tied to a future Android firmware and be included with an OTA update.
We have already addressed the HTC touch sensor issues. It sounds like a future software update could be used to clean this up a little.
Multicolor trackball notifications are definitely coming. Android hackers like ChainsDD have already unlocked this feature for users of custom ROMs. Google advertised the multicolor trackball during its launch of the Nexus One, but the feature was cut from the final Android 2.1 build.
When it comes to the FM radio, I have no idea. Other HTC phones on a similar Snapdragon platform (Desire and Incredible) include the FM radio so it’s not out of the question that the N1 has it too.
I spoke with Google’s Eric Tseng during CES and he told me there were many secrets left in the Nexus One that we would discover later.
When is it Android 2.2 coming out?
Circle May 19th on your calendar. This is the opening day of Google I/O and I’m anticipating the release of Android 2.2 (and maybe the Flash 10.1 beta) will be tied to this event. Google has provided every developer attending the event a free Droid or Nexus One, so it is possible to see a simultaneous release on both devices.
I’m really curious how first generation devices are going to play with this release. We are expecting most phones to receive Android 2.1 this month, so it will be interesting to see how Froyo fits in. Some of the Android engineers have been talking about Froyo on the Google boards and it is unclear if the HTC Dream and Magic will be able to support it since they only have 192 MB of RAM.
p.s. if in wrong spot please move it im a tootal newb
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
Hello i want to talk about a (in my mind the last) Idea to getting more help for the Xoom Family from Moto / Google.
The Xoom Tablet is introduced January 5, 2011.
It was the first tablet to be sold with Android 3.0 aka Honeycomb.
Build up with 2 MP front-facing camera and a rear-facing 5 MP camera that records 720p video.
The Screen has a 1280×800 px widescreen, 10.1-inch display and 3D graphics acceleration.
Inside it runs a Nvidia Tegra 2 T20, 1 GHz dual-core processor combined with 1 GB DDR2 SDRAM and 32 GB Internal Memory and also could be upgraded with External SDHC microSD card slot.
At the Google I/O conference (June 27, 2012) it was announced that the Xoom would be one of the first devices to receive an upgrade to Android 4.1 aka Jelly Bean.
We have these great Product but for Developers we need so much more Informations:
If we followed the Post in the Developer Section we could readout Problem about the Size of the System Partition.
The short story is that Motorola only allocated 236MB to the system partition on the Xoom.
But with new Android Versions like Jelly Bean it fits around nearly 231MB.
Sad when you realize that there is a giant 32GB flash memory chip built in.
We could say hardware will work, but the system partition is just too small.
We should start Petition to get from Moto / Google more Informations and hopefully updated Bootloader with new Partition Layout but better would be NvFlash or ADB / Fastboot Command Support integrated.
NvFlash need the secure boot key so lets talk =)
########## Petition Text #######
To: Motorola / Google
----------------
Release the Secure Boot Key for Xoom Family Devices and bring up new Bootloader
We as consumers have loved the product that Motorola created, but feel that we should also have unlimited access to the devices we purchased.
Its great to bring up newest Android Version to Xoom but also updated Partition Layout please.
Not only does the SBK unlock huge potential for the Xoom, it also protects its users from possible bricked devices.
----------------
Sincerely,
[Your name]
Click to expand...
Click to collapse
Should we start it ???
Sounds like a good idea, but would Motorola take the risk? Since changing partition tables could screw over your tablet.
Motorola stopped updates on several other devices after they announced updates, why would they continue support for this one?
I really wish the OEMs would release their own non-carrier updates with the cavat that they will destroy all your data, and leave it up to the end user to decide if they are okay with that, instead of forcing us all into OTA releases and stopping update support.
[Motorola Atrix and Xoom owner]
I think if we could get enough activity about the Xoom they could bring up the needing points.
I actually also write to Motorola at Twitter:
@Motorola Motorola Xoom System Partition to small, please upgrade them to 1GB we have 32GB NAND inside! Update Bootloader for it please!
Click to expand...
Click to collapse
and also another point of special
@Motorola Bring Motorola Xoom telephony support. Hardware is okay only Modem and Libs doesn´t allow it. Support these great Product !!
Click to expand...
Click to collapse
Lets write to Motorola ... maybe we could win =)
In the GED Xoom don't Motorola only support hardware - Google to support software - so I half wonder if this will fall in deaf ears if directed at Moto
Lothaen said:
In the GED Xoom don't Motorola only support hardware - Google to support software - so I half wonder if this will fall in deaf ears if directed at Moto
Click to expand...
Click to collapse
Moto's ****ty partitioning is the reason we have this problem. I don't know which genius only set aside 236mb out of 32GB + an SD card slot but their lack of foresight is causing problems for devs.
063_XOBX said:
Moto's ****ty partitioning is the reason we have this problem. I don't know which genius only set aside 236mb out of 32GB + an SD card slot but their lack of foresight is causing problems for devs.
Click to expand...
Click to collapse
I think if we could flash Alternative Bootloader like U-Boot it would help too,but Motorola / Google should release Bootloader with Partition modification Support like other Companys does.
Partition layout at config file inside own Partition would be great or simply fastboot commands!
Hope more people would help these Command!
Sent from my GT-I9300 using xda app-developers app
Hello,
today i write to the Google Group who Jean-Baptiste Queru telling about the new Sources (4.2) and the Statement of Xoom doesn´t support any more.
-There is no support for 4.2 on Nexus S and Xoom. Those devices should
continue using 4.1.2.
Click to expand...
Click to collapse
I can't comment about the future of Nexus S and Xoom, sorry.
Click to expand...
Click to collapse
So i released answer about these Statement: Hope it would be agreed and is readable soon so maybe we got new Answer direct from Google!
xlanhackerx said:
Hello,
today i write to the Google Group who Jean-Baptiste Queru telling about the new Sources (4.2) and the Statement of Xoom doesn´t support any more.
So i released answer about these Statement: Hope it would be agreed and is readable soon so maybe we got new Answer direct from Google!
Click to expand...
Click to collapse
You won't.
063_XOBX said:
You won't.
Click to expand...
Click to collapse
Seems to be , the author doesnt publish my answer !
I receive only notification that the post would be readable and i become now access to the aosp group!
Sent from my GT-I9300 using xda app-developers app
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.