Database Users

android 2.2 on the way according to some intell

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

"Android fragmentation at a minimum" they say...

I remember a while back when Google said that they were going to keep Android OS fragmentation at a minimum or I think it was not at all...
Yet along comes honeycomb a version of Android built specifically for tablets.
-Sigh-
What are your thoughts?

It's going to be very tricky to have tablets and phone with the same processing power, let alone have people wanting the same things from both.

I don't think it fragmentation at all, just a version built for tablets. I wouldn't want that on a phone <5".
I would like to see a source for that too because the whole point of the OS is for the carrier/manufacture to customize it. They are the ones that need to update faster.

fragmentation is heavy on android platform, let it be because of freedom of customization, lack of support from phone builder for updates, etc. No need to quote source, just read on it, there's plenty of info on that.

Well he said Google says but didn't give a source for it.
I know there are multiple versions out that are lower than AOSP, it's a fact. There are also features left out of recent iOS versions that are not available on older versions but because they have the same v# people don't seem to complain about it.
But there is ZERO reason to blame Google for not updating blur/touchwiz/sense when it is the Manufactures obligation to update the software with their skin.

Honeycomb has nothing to do with phones though. The OS is made specifically for tablets. Its like windows ce. Yea, its called windows, but because it only runs on smaller devices doesn't make windows fragmented. Same thing applies here. Honeycomb is specifically made for tablets.

The windows ce example is a bad one. Have u used a wall windows ce device (not windows mobile - ce/embedded edition windows)?
In any case as long as APIs are kept consistent there should not be any big problems.
The fragmentation is only problematic because of the way devices are supported, tbh...
Sent from my SGH-T959 using XDA App

Honeycomb?

http://android-developers.blogspot.com/2011/01/android-30-platform-preview-and-updated.html

v0kal said:
http://android-developers.blogspot.com/2011/01/android-30-platform-preview-and-updated.html
Click to expand...
Click to collapse
As of now this is all I would be interested in from 3.0 . Hope cyanogen can pull this into CM7
New types of connectivity: New APIs for Bluetooth A2DP and HSP let applications offer audio streaming and headset control. Support for Bluetooth insecure socket connection lets applications connect to simple devices that may not have a user interface.

Yep seems to be a preview SDK for 3.0 with a final SDK in coming weeks. Simply prep for Honeycomb tablets.

"A built-in GL renderer lets developers request hardware-acceleration of common 2D rendering operations in their apps, across the entire app or only in specific activities or views."
So it seems that 2.3 isn't hardware accelerated...now I want 3.0 on my desire . But here's another quote:
"Android 3.0 (Honeycomb) is a new version of the Android platform that is designed from the ground up for devices with larger screen sizes, particularly tablets."
So Honycomb isn't for phones? I really hope Google can clear things up a bit because I remember Andy rubben saying the Honycomb can adapt to phones & tablets.
Any thoughts or theories?

Weren't there enough thoughts and theories about it?

Jack_R1 said:
Weren't there enough thoughts and theories about it?
Click to expand...
Click to collapse
Yes there was a lot of theories, but now we have something official to discuss rather than hearsay. Anyway, don't discuss if you don't feel like it.

How about the 2.4? really don't know what Goolge is thinking about. Just want a stable version and improve it by other works. Not so much version and make people confuse. It seems that N1 may not flash it~~

mr.r9 said:
Yes there was a lot of theories, but now we have something official to discuss rather than hearsay. Anyway, don't discuss if you don't feel like it.
Click to expand...
Click to collapse
Looking at the new preview SDK, it only big screens by default. And reading through the platform highlights really only mentions tablets. However, a couple Android devs have already stated its for all platforms. Seems to me that they don't want to reveal that its for phones yet, so that they can advertise that it is made for tablets.
The main criticism the iPad got was being a giant iPhone. I think they want to avoid that by having people believe that it isn't the same Android that is on phones.
I guess when they release the full SDK we'll know for sure.

Interesting...the beat goes on!

Honeycomb is also for phones, but we all knew that right?
From the documentation:
Publishing your app for tablet-type devices only
Additionally, you should decide whether your application is for only tablet devices (specifically, xlarge devices) or for devices of all sizes that may run Android 3.0.
If your application is only for tablets (xlarge screens; not for mobile devices/phones), then you should include the <supports-screens> element in your manifest with all sizes except for xlarge declared false.
With this declaration, you indicate that your application does not support any screen size except extra large. External services such as Android Market may use this to filter your application from devices that do not have an extra large screen.
Otherwise, if you want your application to be available to both small devices (phones) and large devices (tablets), do not include the <supports-screens> element.
Click to expand...
Click to collapse
Well, all clear then! The future of Android looks neat!

Nice find
Sent from my Nexus One using XDA App

spamlucal said:
Honeycomb is also for phones, but we all knew that right?
From the documentation:
Well, all clear then! The future of Android looks neat!
Click to expand...
Click to collapse
Hmmmm...good find! Android is getting really interesting visually, which is IMO a milestone it needed to reach a while ago
Anyway, can't wait for an alpha sdk image on my phone to play with if that's possible currently

Forget Ginga and Honeycomb. Havent you all hear of whats ahead of honeycomb? Its called " Chicken Soup". Yup, ik... Weird name. But its only for dual core over 2ghz. So phones arent ready. Its suppose to be completely holographic 3d without glasses. Pretty neat. And requires horsepower of xbox 360 or more. Anything less and its a no go. Its suppose to be the next gen OS and quantum leap from even honeycomb. Remember the name "chicken soup". Its comming next year by christman. Cant wait!
Sent from my SPH-D700 using Tapatalk

SINNN said:
Forget Ginga and Honeycomb. Havent you all hear of whats ahead of honeycomb? Its called " Chicken Soup". Yup, ik... Weird name. But its only for dual core over 2ghz. So phones arent ready. Its suppose to be completely holographic 3d without glasses. Pretty neat. And requires horsepower of xbox 360 or more. Anything less and its a no go. Its suppose to be the next gen OS and quantum leap from even honeycomb. Remember the name "chicken soup". Its comming next year by christman. Cant wait!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
This was a horrible and incredibly illogical troll/joke attempt

spamlucal said:
Honeycomb is also for phones, but we all knew that right?
From the documentation:
Well, all clear then! The future of Android looks neat!
Click to expand...
Click to collapse
It actually does not mean much.
Android application could always define different layouts for different resolutions, orientations, themes or screen sizes. So, it is just one additional form factor, one of many. And the way to say to the market which layouts are supported and which are not.
It also does not mean, that "honeycomb for phones" would be the same as honeycomb for tablets "just smaller".
They only said, that phone version will move in similar direction. Which can mean pretty much anything.
In fact I expect, that honeycomb for phones will be seriously different, since a lot of new honeycomb for tablets features on smaller screens do not make any sense.

My theory:
Honeycomb is currently, Tablets only.
We are going to see a division in Android for Phones and Android for Tablets.
Tablets will be at 3.0 starting off.
Phones are currently at 2.3, and will continue 2.4 being Gingerbread as well with updates that should have happened with 2.3. (Like 2.0 and 2.1 being Eclair)
Once phones have the ability to run such a resource hungry operating system(3.0) the Phone and Tablet versions of Android will merge into one.

Wisefire said:
My theory:
Honeycomb is currently, Tablets only.
We are going to see a division in Android for Phones and Android for Tablets.
Tablets will be at 3.0 starting off.
Phones are currently at 2.3, and will continue 2.4 being Gingerbread as well with updates that should have happened with 2.3. (Like 2.0 and 2.1 being Eclair)
Once phones have the ability to run such a resource hungry operating system(3.0) the Phone and Tablet versions of Android will merge into one.
Click to expand...
Click to collapse
But the hardware of the new tablets is the same Tegra 2 of the new phones, so I think the problem is the adaptability of the OS to smaller screens in a way it is usable for our fingers.
Anyone here used the leaked "honeycomb music player"? It has all the new characteristics we saw on the xoom tablet but worked very nice on my Nexus One with 2.2.1.
I think when honeycomb's source code come out we will get working builds.
Sent from my Nexus One using XDA App

I heard Ice cream is going to be only for refrigerators. You know cause of the thermostat API that very few phones support.

marlonbr said:
But the hardware of the new tablets is the same Tegra 2 of the new phones, so I think the problem is the adaptability of the OS to smaller screens in a way it is usable for our fingers.
Anyone here used the leaked "honeycomb music player"? It has all the new characteristics we saw on the xoom tablet but worked very nice on my Nexus One with 2.2.1.
I think when honeycomb's source code come out we will get working builds.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I believe you are absolutely right. I tried making an AVD for Honeycomb with the screen resolution of my Nexus One. The launcher force closed continuously but you could see that the standard pull down notification bar was there. So I take that to mean that Honeycomb is for all devices and just changes its layout based on screen size.

draugaz said:
It actually does not mean much.
Click to expand...
Click to collapse
A little bit of context: The text I copy-pasted is in a section called "Upgrade or Develop a New App for Tablets and Similar Devices"
In it, is says:
If you want to develop something truly for tablet-type devices running Android 3.0, then you need to use new APIs available in Android 3.0. This section introduces some of the new features that you should use.
The first thing to do when you create a project with the Android 3.0 preview is set the <uses-sdk> element to use "Honeycomb" for the android:minSdkVersion.
Click to expand...
Click to collapse
What does this mean? it means this app won't work on anything other lower than honeycomb. So, the "choose your screen size" text I pasted yesterday applies to honeycomb-only apps.
The documentation in the SDK is a nice read actually

leaked confimation that there will be a phone version of honeycomb

If you have played with the honeycomb emulator in the Android SDK, you might of been disapointed that it looked like honeycomb was only for tablets, but an insider at HTC has leaked some info about the new HTC Revolver, allegedly shipping with honeycomb. this is great news hopefully meaning google are working on a smartphone version of homneycomb aswell
http://www.engadget.com/2011/02/14/htc-revolver-a-flagship-honeycomb-phone-for-atandt/

The next version of Android after Honeycomb is reportedly merging Honeycomb and regular android together according to Eric Shmidt at MWC
http://www.wired.co.uk/news/archive/2011-02/16/android-honeycomb-and-gingerbread-to-merge

MeeGo + LiMo = Tizen OS

Intel announced MeeGo's death, now they will develop Tizen OS from MeeGo an LiMo (two good project but never finished...)
I'm sure someone here will try to port Tizen OS let's wait...
MeeGo was a great project but it was not well supported by Intel....

We will se, maybe our devs will do some miracle, and then "Tizen OS" will be usable in hd2

bartass127 said:
We will se, maybe our devs will do some miracle, and then "Tizen OS" will be usable in hd2
Click to expand...
Click to collapse
I hope so, I might even try to do it myself ( since I was unable to do meego's, it always gave me an error somehow. )
And hopefully, it will be full of life

soo hey! you should try ! and give feedback quickly as soon as it possible !

I do not know why they keep doing this to Maemo. First it was to Meego, then it is to Tizen. Seriously, you will find the same problem with Tizen... not enough support from the foundation and no device that will push its development up. Unless Bada ends up with Tizen, don't expect much from the SDK which will only be released in Q1 of 2012, the earliest. I suspect it is going to be Meego all over again, lack of drivers developed because there is no device committed to the OS, etc.
Sigh... Don't get your hopes up for 2011 for this to be on HD2, or even on 2012. Let's hope the N9's Meego version would be useful for dev work on the HD2.

erlern said:
I do not know why they keep doing this to Maemo. First it was to Meego, then it is to Tizen. Seriously, you will find the same problem with Tizen... not enough support from the foundation and no device that will push its development up. Unless Bada ends up with Tizen, don't expect much from the SDK which will only be released in Q1 of 2012, the earliest. I suspect it is going to be Meego all over again, lack of drivers developed because there is no device committed to the OS, etc.
Sigh... Don't get your hopes up for 2011 for this to be on HD2, or even on 2012. Let's hope the N9's Meego version would be useful for dev work on the HD2.
Click to expand...
Click to collapse
of course for Tizen OS (if ever will be finished) we have to wait summer 2012
n9 meego is not the intel one (meego 1.1/1.2), it's like an other system, and it's available only for 1 phone, with different hw from hd2, so i think it's impossible to port meego from N9 nokia done a great work with N9, and MeeGo is now dead, what a shame...
i think we have to wait a new Linux OS based that runs on snapdragon phones...

pirlano said:
of course for Tizen OS (if ever will be finished) we have to wait summer 2012
n9 meego is not the intel one (meego 1.1/1.2), it's like an other system, and it's available only for 1 phone, with different hw from hd2, so i think it's impossible to port meego from N9 nokia done a great work with N9, and MeeGo is now dead, what a shame...
i think we have to wait a new Linux OS based that runs on snapdragon phones...
Click to expand...
Click to collapse
Somehow this seems interesting to read concerning Nokia and Linux: http://mynokiablog.com/2011/09/29/l...power-future-nokia-feature-phones-meego-lite/

Only Time can tell what will happen!

Tizen Alpha source is released along with SDK.

I'm looking forward to this one!

To my eyes now, Tizen SO it seems another hilariously short aventure that will be dead in a year.
Alphas, betas, ideas....We want some think real and continuous.

http://www.netbooknews.com/47197/nokia-working-on-two-new-low-end-meego-smartphones/