Ice cream sandwich to release next week?
http://news.cnet.com/8301-1023_3-20...xt-week/?part=rss&subj=news&tag=2547-1_3-0-20
CNET said:
Google is expected to serve up Ice Cream Sandwich--the newest version of Android--on Tuesday at the Samsung Unpacked event in San Diego.
That revelation comes courtesy of the official Android Developers YouTube channel, which earlier today posted a placeholder video titled "Android ICS launch." The site now says, "This live event is no longer available. Sorry about that." Google Executive Chairman Eric Schmidt said last month that the next flavor of the company's mobile operating system would debut sometime in October or November.
Samsung is also expected to use the event to unveil a new Android phone, perhaps the Nexus Prime, which would likely be the first Ice Cream Sandwich phone. Samsung has posted a teaser video that includes the words "Something big is coming"--perhaps an indication of the phone's screen size.
Ice Cream Sandwich is Google's first attempt to create one single unified mobile OS, taking Honeycomb features and interfaces and adapting them to run across both smartphones and tablets. ICS developers will get new open-source APIs and a framework that will help them optimize their apps to run on a variety of different Android phones and tablets.
Click to expand...
Click to collapse
Hoping to see this on my nook soon
Sent from my NookColor using xda premium
Hopefully we get a full source release soon after.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Doesn't Google usually release to one manufacturer first and then to everyone else some 6 months later? I recall that has been a concern of phone manufacturers since Google announced they wanted to buy Motorola, ie; Motorola might then exclusively get the 6 month jump. Usually Google would rotate manufacturers.
The question now is, which will come first: CM7.1 stable, or CM8?
CM8 FTW!!!!!!!!
CANCELLED!
Just saw the announcement from Samsung
I don't think we will see any ICS code anytime soon.
Personally, I think, first, they introduced the ICS (which just got delayed) then waiting for certain period of time (who know how many months) before release the source codes.
I think it's good to call CM8.
votinh said:
I don't think we will see any ICS code anytime soon.
Personally, I think, first, they introduced the ICS (which just got delayed) then waiting for certain period of time (who know how many months) before release the source codes.
I think it's good to call CM8.
Click to expand...
Click to collapse
No, I'm strongly disagreeing with this statement, with the exception of Honeycomb, Google pushes its source code to the repo's within hours or at the most a couple of days after it launches. With all the leaks lately, I wouldn't be surprised to see ICS leaked pretty soon. If it doesnt though, I'm sure we'll have source within 2-3 weeks tops.
RileyGrant said:
No, I'm strongly disagreeing with this statement, with the exception of Honeycomb, Google pushes its source code to the repo's within hours or at the most a couple of days after it launches. With all the leaks lately, I wouldn't be surprised to see ICS leaked pretty soon. If it doesnt though, I'm sure we'll have source within 2-3 weeks tops.
Click to expand...
Click to collapse
See my post above. Google usually gives one manufacturer a jump on the rest and rotates. "hours" is not really much of a jump unless they are going to change their release habits.
patruns said:
See my post above. Google usually gives one manufacturer a jump on the rest and rotates. "hours" is not really much of a jump unless they are going to change their release habits.
Click to expand...
Click to collapse
Yeah, I read that post, but that's not the case. They don't do that with the software, just the phones. For instance, the Nexus S came out on T-Mobile, then eventually Sprint, etc. When the new software is released/launched however, they push it directly to their "AOSP" (Android Open Source Project) repositories, and from there, developers have open access to the source code. Technically, since Android is licensed under the Apache Open Source license, if they are to call it "Open Source" they must post the source code within a certain time limit (which is only a couple of weeks) or else it violates the license.
Well I'm pretty excited to see some ICS efforts. New OSs are fun. I'm particularly interested in trying out the newest stock web browser.
RileyGrant said:
Yeah, I read that post, but that's not the case. They don't do that with the software, just the phones. For instance, the Nexus S came out on T-Mobile, then eventually Sprint, etc. When the new software is released/launched however, they push it directly to their "AOSP" (Android Open Source Project) repositories, and from there, developers have open access to the source code. Technically, since Android is licensed under the Apache Open Source license, if they are to call it "Open Source" they must post the source code within a certain time limit (which is only a couple of weeks) or else it violates the license.
Click to expand...
Click to collapse
You know they promised then delayed then ignored then decided not to release the Honeycomb source code, right?
There is no such a "must" from them.
But anyway, if you're correct, which I and the rest of us also wish, then it's great. I want to see them release ICS code ASAP, 3 weeks like you said is reasonable and if 3 days or even 3 hours then it's more than expect.
We all hope for the CM8, should we?
votinh said:
You know they promised then delayed then ignored then decided not to release the Honeycomb source code, right?
There is no such a "must" from them.
But anyway, if you're correct, which I and the rest of us also wish, then it's great. I want to see them release ICS code ASAP, 3 weeks like you said is reasonable and if 3 days or even 3 hours then it's more than expect.
We all hope for the CM8, should we?
Click to expand...
Click to collapse
They released what was required by the license for honeycomb but Google has confirmed that ICS will be an open source release.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
votinh said:
You know they promised then delayed then ignored then decided not to release the Honeycomb source code, right?
There is no such a "must" from them.
But anyway, if you're correct, which I and the rest of us also wish, then it's great. I want to see them release ICS code ASAP, 3 weeks like you said is reasonable and if 3 days or even 3 hours then it's more than expect.
We all hope for the CM8, should we?
Click to expand...
Click to collapse
Reason I heard is that Honeycomb was a quick throw together for a tablet OS.
Not really an excuse, but considering they've been working on ICS for quite a while now, I think it'll be in the repos pretty quickly.
RileyGrant said:
Yeah, I read that post, but that's not the case. They don't do that with the software, just the phones. For instance, the Nexus S came out on T-Mobile, then eventually Sprint, etc. When the new software is released/launched however, they push it directly to their "AOSP" (Android Open Source Project) repositories, and from there, developers have open access to the source code. Technically, since Android is licensed under the Apache Open Source license, if they are to call it "Open Source" they must post the source code within a certain time limit (which is only a couple of weeks) or else it violates the license.
Click to expand...
Click to collapse
I will agree to disagree But I do hope I am wrong!
Alright, let's hope that they do what they should have been doing.
Dalingrin said the HP Touchpad will get ICS and maybe the Nook Color.
patruns said:
I will agree to disagree But I do hope I am wrong!
Click to expand...
Click to collapse
Ya thats fine, a previous comment mentioned that they didnt have to release code such as what they did for honeycomb, however, they did release the required source for honeycomb but did not push the framework and what not because it was being saved for what we now know is ICS.
RileyGrant said:
Ya thats fine, a previous comment mentioned that they didnt have to release code such as what they did for honeycomb, however, they did release the required source for honeycomb but did not push the framework and what not because it was being saved for what we now know is ICS.
Click to expand...
Click to collapse
I think one of the main reasons for Google not releasing the source code was because they didn't want people to run it on phones, being a tablet OS.
Dalingrin said the HP Touchpad will get ICS and maybe the Nook Color.
Click to expand...
Click to collapse
When did he say that? That makes it sound that the touchpad will definitely get ICS and the nook color may get it.
Related
I just read something about Android 2.0 and i was wondering if some one knows about it, and how this is gonna work with the roms and how we can use it
in before moved to Q&A. good luck lol
...are you serious?
Oh dear.... If you mean 2.0 on the G1 in specific, it is an unknown if it will happen at this stage. I believe there are some carriers that have promised it but as of this moment we have no date (or gaurantee) of a port to the G1.
As far as features of 2.0 I would make friends with Goggle:
http://www.google.com/search?hl=en&source=hp&q=What's+new+in+Android+2.0&btnG=Google+Search
http://blogs.zdnet.com/Burnette/?p=1436
and
http://developer.android.com/sdk/android-2.0-highlights.html
should get you started.
2.0 being released to the public Nov 6th
Okay, so i know cynogen got the c&d for releasing 1.6 a bit to early...so i'm thinking the official release for 2.0 is tomorrow so will devs be able to get 2.0 out on the g1 tomorrow? leave it to verizon to kill the open source project. fukin assholes, i hate verizon. anywho, i am hoping devs will be able to start realeasing 2.0 g1 remixes tomorrow as well...seems like 2.0 kicks ass...turn by turn directions, social network integration, different apps, look at everyone hoping on Google's ****...lol...cmon AT&T you can do it...lol
JanetPanic said:
Oh dear.... If you mean 2.0 on the G1 in specific, it is an unknown if it will happen at this stage. I believe there are some carriers that have promised it but as of this moment we have no date (or gaurantee) of a port to the G1.
As far as features of 2.0 I would make friends with Goggle:
http://www.google.com/search?hl=en&source=hp&q=What's+new+in+Android+2.0&btnG=Google+Search
http://blogs.zdnet.com/Burnette/?p=1436
and
http://developer.android.com/sdk/android-2.0-highlights.html
should get you started.
Click to expand...
Click to collapse
This **************
Have... Have you been under a rock??
just because the droid is shipping today doesn't mean they are releasing the new source yet. cyanogen has already said he will be all over it when the open source comes out. he doesn't work on ports so to speak. twisted and barak are working on a droid port though i think
dgrave said:
Okay, so i know cynogen got the c&d for releasing 1.6 a bit to early...so i'm thinking the official release for 2.0 is tomorrow so will devs be able to get 2.0 out on the g1 tomorrow? leave it to verizon to kill the open source project. fukin assholes, i hate verizon. anywho, i am hoping devs will be able to start realeasing 2.0 g1 remixes tomorrow as well...seems like 2.0 kicks ass...turn by turn directions, social network integration, different apps, look at everyone hoping on Google's ****...lol...cmon AT&T you can do it...lol
Click to expand...
Click to collapse
Cyanogen probably will not even begin work on 2.0 until it has been released to the AOSP repositories. JBQ has dodged the question as to when this would occur so I would hazard a guess that it will not be for a week or two at least. Once 2.0 has been released there is the additional problem that even with the AOSP code we do not have enough to build a complete ROM. The google components that we get from the base ROM in 1.6 will be missing till we get a base ROM for 2.0. In theory this could be obtained from a different phone (such as Sholes) but then you are setting up whoever ports the ROM to the G1 for a C&D.
I think in the end we are going to need to wait for an official release of 2.0 for the G1. Failing that I think it will take a while to port another ROM and tweak it to the point of being usable for day to day operations.
dgrave said:
Okay, so i know cynogen got the c&d for releasing 1.6 a bit to early...so i'm thinking the official release for 2.0 is tomorrow so will devs be able to get 2.0 out on the g1 tomorrow? leave it to verizon to kill the open source project. fukin assholes, i hate verizon. anywho, i am hoping devs will be able to start realeasing 2.0 g1 remixes tomorrow as well...seems like 2.0 kicks ass...turn by turn directions, social network integration, different apps, look at everyone hoping on Google's ****...lol...cmon AT&T you can do it...lol
Click to expand...
Click to collapse
lol, he didn't get the C&D for releasing 1.6 early, the code was in AOSP. The reason he got the C&D was because he was distrobuting the google apps which aren't in AOSP, which none of the developers here are licenced to distribute. The reason they pissed was because he included the new market before it was included in the ROMs on phones shipping with the new market present in 1.6.
AdrianK said:
lol, he didn't get the C&D for releasing 1.6 early, the code was in AOSP. The reason he got the C&D was because he was distrobuting the google apps which aren't in AOSP, which none of the developers here are licenced to distribute. The reason they pissed was because he included the new market before it was included in the ROMs on phones shipping with the new market present in 1.6.
Click to expand...
Click to collapse
+1
While alot of people think that its just corporate america trying to keep the white man down, Im thinking that it would have been really easy for google to ruin cyan's life when in reality, they just told him what it was he was doing wrong.. He properly adjusted his technique, and now all is good and everyone is happy.
I just read this over on phandroid here's a link just take out the space after the .
phandroid. com/2010/06/22/htc-delivering-froyo-to-the-htc-desire-and-legend-within-the-next-two-weeks/
Already got froyo on my n1 and it's sweet. I wonder how much of a speed boost the legend will gain?
let's just hope you are right about this i'm dying to see froyo on my legend and starting to regret for picking legend over desire
evank418 said:
let's just hope you are right about this i'm dying to see froyo on my legend and starting to regret for picking legend over desire
Click to expand...
Click to collapse
same here.. but still looks cooler than Desire
except the "antenna" at the bottom, it's quite loose, the only thing that I don't like hardware-wise
hope that Froyo will improve it software-wise
by the way, just checked the original source (a german site) and they have update from today - we are not getting Froyo in two weeks.. everything is indefinite....
Here is the original source.
Translated by google:
HTC has denied through his PR agency, that there will be two weeks in an operating system update for the Desire and the Legend. The statement was based on a misunderstanding. It is certain that the HTC Hero will receive in the next two weeks, his update to Android 2.1. In the update for the HTC Desire remains vague and will deliver an update to the third quarter. Whether and when to upgrade to the Legend Android 2.2 get, you do not know yet.
Click to expand...
Click to collapse
c1nu5 said:
Here is the original source.
Translated by google:
Click to expand...
Click to collapse
To me this more and more sounds like the Legend is definitely not getting FroYo. They would confirm it by now otherwise (like they did for the Desire).
schpinn said:
To me this more and more sounds like the Legend is definitely not getting FroYo. They would confirm it by now otherwise (like they did for the Desire).
Click to expand...
Click to collapse
what? you're totally wrong, htc and desire will have froyo in the same time as they had the other updates together in the past.
mercuryzzz said:
what? you're totally wrong, htc and desire will have froyo in the same time as they had the other updates together in the past.
Click to expand...
Click to collapse
Uh, the article actually directly says this won't happen. Google translate failed.
Well I've heard multiple times before this that customer service reps from htc have also confirmed the update to froyo for the legend. The most recent being an email from a customer service rep stating that the user fear not about his flash playing troubles because android 2.2 and incidentally flash 10.1 would be released for the htc legend within the next 2 weeks.
Follow this up by the recent release of flash 10.1 for android 2.2 and the release of the android 2.2 source code being released today the statement of "within the next 2 weeks" seem to be exactly what is happening. Not only is android 2.2 pretty much here but will be available sooner rather then later. To add further flame to the fire htc repeatedly said android 2.2 will be supported by almost all 2010 devices and with the desire being more widely available and more powerful it is more likely to be put in with definite android 2.2 compatible even though the desire and legend get almost always get updates at the same time.
The most likely reason the statement was pulled? Well it must simply be due to google not publishing the source code yet, thus letting people essentially know froyo is ready.
Htc most certainly can't pull the plug on 2.2 before google itself does. But! Now that it has published final froyo source code it is 99.9% done and is most likely waiting to be uploaded to the server.
My uneducated guess is that we'll see froyo on the legend by mid july at the latest.
Also not sure if anyone thought of this, but bell (and indirectly virgin mobile canada) are not stupid companies. They are introducing a new android phone and thus throwing massive amounts of ad $ and marketing into it, from both bell/virgin AND htc itself. Remember this is virgins FIRST android set and bells 4th or 5th, they would most likely have talked to htc to make sure the device is upgradeable to the newest android. They just started selling it, they aren't going to allow it to be out dated within the month its released! If the did it would be a waste on advertising and a waste of introducing a new phone.
That's just my 2 cents, but it seems very logical to me, how about you?
kylecore said:
Well I've heard multiple times before this that customer service reps from htc have also confirmed the update to froyo for the legend. The most recent being an email from a customer service rep stating that the user fear not about his flash playing troubles because android 2.2 and incidentally flash 10.1 would be released for the htc legend within the next 2 weeks.
Follow this up by the recent release of flash 10.1 for android 2.2 and the release of the android 2.2 source code being released today the statement of "within the next 2 weeks" seem to be exactly what is happening. Not only is android 2.2 pretty much here but will be available sooner rather then later. To add further flame to the fire htc repeatedly said android 2.2 will be supported by almost all 2010 devices and with the desire being more widely available and more powerful it is more likely to be put in with definite android 2.2 compatible even though the desire and legend get almost always get updates at the same time.
The most likely reason the statement was pulled? Well it must simply be due to google not publishing the source code yet, thus letting people essentially know froyo is ready.
Htc most certainly can't pull the plug on 2.2 before google itself does. But! Now that it has published final froyo source code it is 99.9% done and is most likely waiting to be uploaded to the server.
My uneducated guess is that we'll see froyo on the legend by mid july at the latest.
Also not sure if anyone thought of this, but bell (and indirectly virgin mobile canada) are not stupid companies. They are introducing a new android phone and thus throwing massive amounts of ad $ and marketing into it, from both bell/virgin AND htc itself. Remember this is virgins FIRST android set and bells 4th or 5th, they would most likely have talked to htc to make sure the device is upgradeable to the newest android. They just started selling it, they aren't going to allow it to be out dated within the month its released! If the did it would be a waste on advertising and a waste of introducing a new phone.
That's just my 2 cents, but it seems very logical to me, how about you?
Click to expand...
Click to collapse
Go read about the HTC Hero. HTC's all about wasting time.
Good news, i am waiting it. BTW, does anyone have link to stock ROM froyo for any device? Pls give me the link, i'll try to port it for legend.
Thanks.
Sent from my HTC Legend using Tapatalk
owenw said:
Go read about the HTC Hero. HTC's all about wasting time.
Click to expand...
Click to collapse
Well, HTC may be about "wasting time" but I assure you a phone carrier isn't about wasting money on a device that will essentially be obsolete within the month they release it. Case in point no north american phone carrier's are introducing any android devices that aren't running android 2.2 or able to upgrade to it, why should bell/virgin mobile be any different?
BesFen said:
Good news, i am waiting it. BTW, does anyone have link to stock ROM froyo for any device? Pls give me the link, i'll try to port it for legend.
Thanks.
Sent from my HTC Legend using Tapatalk
Click to expand...
Click to collapse
The legitimate release hasn't been release, although litterally 5 minutes ago I saw reports on endgadget that small ota's of frf83 we're infact being pushed out via ota right now.
Also in this forum section someone is currently developing froyo and hopes to release it by the weekend, maybe send that person a pm?
kylecore said:
Well I've heard multiple times before this that customer service reps from htc have also confirmed the update to froyo for the legend. The most recent being an email from a customer service rep stating that the user fear not about his flash playing troubles because android 2.2 and incidentally flash 10.1 would be released for the htc legend within the next 2 weeks.
Follow this up by the recent release of flash 10.1 for android 2.2 and the release of the android 2.2 source code being released today the statement of "within the next 2 weeks" seem to be exactly what is happening. Not only is android 2.2 pretty much here but will be available sooner rather then later. To add further flame to the fire htc repeatedly said android 2.2 will be supported by almost all 2010 devices and with the desire being more widely available and more powerful it is more likely to be put in with definite android 2.2 compatible even though the desire and legend get almost always get updates at the same time.
The most likely reason the statement was pulled? Well it must simply be due to google not publishing the source code yet, thus letting people essentially know froyo is ready.
Htc most certainly can't pull the plug on 2.2 before google itself does. But! Now that it has published final froyo source code it is 99.9% done and is most likely waiting to be uploaded to the server.
My uneducated guess is that we'll see froyo on the legend by mid july at the latest.
Also not sure if anyone thought of this, but bell (and indirectly virgin mobile canada) are not stupid companies. They are introducing a new android phone and thus throwing massive amounts of ad $ and marketing into it, from both bell/virgin AND htc itself. Remember this is virgins FIRST android set and bells 4th or 5th, they would most likely have talked to htc to make sure the device is upgradeable to the newest android. They just started selling it, they aren't going to allow it to be out dated within the month its released! If the did it would be a waste on advertising and a waste of introducing a new phone.
That's just my 2 cents, but it seems very logical to me, how about you?
Click to expand...
Click to collapse
I totally agree witjh you. Froyo for legend is sure as it is sure for desire. These two phones will receive the update in the same time I think . Anyway your point is the only point with a sense. I think the same.
mercuryzzz said:
I totally agree witjh you. Froyo for legend is sure as it is sure for desire. These two phones will receive the update in the same time I think . Anyway your point is the only point with a sense. I think the same.
Click to expand...
Click to collapse
well i'm glad someone does. but you are right, this is currently all speculation and my point.. although it does all seem to add up correctly.
i guess only time will tell, but i'm not worried
it's confirmed too by HTC European customer service
I've got confirmed as well by the European customer service by an E-mail that a 2.2 upgrade will be available for the Legend in a month. I'm counting back too everyday.
mihalyf said:
I've got confirmed as well by the European customer service by an E-mail that a 2.2 upgrade will be available for the Legend in a month. I'm counting back too everyday.
Click to expand...
Click to collapse
This sounds promising
Well i am keeping my fingers crossed for froyo & gingerbread as well .....
mihalyf said:
I've got confirmed as well by the European customer service by an E-mail that a 2.2 upgrade will be available for the Legend in a month. I'm counting back too everyday.
Click to expand...
Click to collapse
@mihalyf, Could you please post a screenshot of the email or a proof of the confirmation from customer service?
.. Well, blurring out whatever you think is necessary of course..
prasannavl89 said:
@mihalyf, Could you please post a screenshot of the email or a proof of the confirmation from customer service?
.. Well, blurring out whatever you think is necessary of course..
Click to expand...
Click to collapse
here you are
.... I am sure you can appreciate that it is out of bounce for me to promise an exact date on the launch of the new upgrade.
I can however say that this upgrade will come during this month.
Sorry I cannot be more specific about this. ....
Just read the news about these two getting the update that fixes the SMS bug but no mention of any other 2.2.x O/S'd phones getting it. Can't be far off surely?
http://phandroid.com/
I just want that SMS fix, I've seen two I9000Ms do it. I pinged Samsung Canada on Twitter, we'll see what their response is.
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
Click to expand...
Click to collapse
maybe ayes maybe naws
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
(American variant releases not guaranteed)
Click to expand...
Click to collapse
Fixed that for you.
i somewhere read that we can expect 2.3 for SGS for the end for the first quarter of the year...but are you people using stock ROMS ? i think Darky's ROM is working on a multi-device able to detect and flash devices accordingly, shouldn't that fix your sms problems ?
ps: i have the i9000, but what is "the sms problem", i don't think i have it..
Everybody bug samsung to skip 2.3 and prep for 3.0.
With carriers charging 15-20¢/SMS and having a free replacement (google voice, google talk, emails)
I really couldn't care less about SMS. I should even remove the SMS app from my phone.
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
It's for both.
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
So wrong, it hurts.
rumor
the rumor is here :
i like the way they say
"site called SamFirmwares – one we’ve never heard of before."
Click to expand...
Click to collapse
they better all listen to these site ! i wonder how these big companies would react to
all the amazing roms out there !
JCopernicus said:
So wrong, it hurts.
Click to expand...
Click to collapse
Is it? Then prove me wrong...
From google:
Honeycomb is the next version of the Android platform, designed from the ground up for devices with larger screen sizes, particularly tablets.
Click to expand...
Click to collapse
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
t1mman said:
Is it? Then prove me wrong...
From google:
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
Click to expand...
Click to collapse
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
JCopernicus said:
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
Click to expand...
Click to collapse
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
t1mman said:
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
Click to expand...
Click to collapse
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
JCopernicus said:
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
Click to expand...
Click to collapse
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
t1mman said:
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
Click to expand...
Click to collapse
The large screen views (which never existed) are built from the "ground up" because, guess what? They never existed in the first place.
The reason it's taking 3.0 is because it's a huge jump in feature set, and qualifies as a version realease and not just a point release.
If a device has a certain feature it can access certain API from the android OS. If a device doesn't, then it can't. It's that simple.
"tablets" have the big screen feature and they can access the nested view API's. You don't know how android works. there is ONE line, which sits at 2.3.2, and it's device independent.
Just like the Nexus S can access the NFC api's because it has an NFC chip.
AOSP is the code that google/samsung/moto/acer/etc pull from, and build more on top.
Cyanogen roms are on par and equivalent(better actually) as google's roms, you can't get more "official" than AOSP. MFG roms are actually less true to AOSP as they are modified. You probably won't see 3.0 on the current galaxy line at all, but that has nothing to do whether it works on there or not.
Chill out dude! Take a deep breath....
This is getting nowhere, running in circle...
I'm pretty sure we won't see Honeycomb as a release by the makers (Samsungs, Motorola, LG, HTC, name em) on any smartphone. Don't know why this is such a big deal for you and what you don't get on the whole deal but if you want,
You can bookmark this thread and if you see an official honecomb as an official release by samsung or LG or HTC or google on a Smartphone, revive it from the archives and rub it on my face, I'll gladly take the fall...
Chill out? I think I'm just typing normally on a keyboard? Maybe I'm smashing keys, and don't recognize it?
You don't understand how android works if you think it won't appear on phones, we're not going around in circles. You're just wrong.
Has everybody noticed how this has slipped thru the cracks with all the distraction of Google I/O 2011 news?
Google I/O Google has said that the next version of Android, dubbed "Ice Cream Sandwich", will be open sourced "by the end of the year," and that it will not open source the current Android incarnation, the tablet-centric Honeycomb, before that time.
Source:
UU UU UU dot theregister.co.uk/2011/05/10/android_ice_cream_sandwich/
Andy Rubin has backtracked on making the Honeycomb source available until after it is no longer relevant (if even then). There is no promise any more of EVER getting the Honeycomb source, so it looks like the best we'll be able to do is SDK11 unless B&N updates stock to Honeycomb (don't hold your breath).
I wouldn't say Honeycomb will no longer be relevant after ICS. After all, ICS is a smart phone OS, whereas HC is designed for tablets. What I'm getting from this is that ICS is basically going to be the smartphone version of HC. Google has stated that they don't want people porting HC to smartphones. By delaying the release of source for HC until after ICS hits the shelves, Google is trying to forestall the translation of HC to phones by waiting to release HC code until it no longer makes sense to do so (beacuse there'll be no point in doing so).
dsf3g said:
I wouldn't say Honeycomb will no longer be relevant after ICS. After all, ICS is a smart phone OS, whereas HC is designed for tablets. What I'm getting from this is that ICS is basically going to be the smartphone version of HC. Google has stated that they don't want people porting HC to smartphones. By delaying the release of source for HC until after ICS hits the shelves, Google is trying to forestall the translation of HC to phones by waiting to release HC code until it no longer makes sense to do so (beacuse there'll be no point in doing so).
Click to expand...
Click to collapse
Actually, from the presentation, ICS is just as much for tablets, since the UI is supposed to scale based on the device.
However, they keep saying ICS for quarter 4, which is half a year away. Frankly, i am pissed that they yanked devs around for so long HOPING we might see the code, when in reality, i have no doubt they held it back solely on the request of Moto and others, to help maintain a monopoly on HC market..
Other media reports are characterizing the discussion as Rubin saying that they will never release the Honeycomb AOSP. Yet another reason to ignore the Xoom, et al. tablets if they're going to pull this bull****.
Brilliant plan -- release a closed buggy version, refuse the community to do de-bugging work for free and then hope that it will be magically fixed by merging with the OS that originally was thought to not be up to snuff.
Google thinks that they can "merge" Honeycomb back into Ice Cream Sandwich (after they "get it right").
What I want to know is, how is Andy Rubin justifying withholding the source of an "open source" OS? And what is to keep him from doing the same thing again next year with ICS?
There are more comments over in the developer thread on this subject. I started this one first, but I don't have enough posts to start one over there (grumble, grumble). I'm slowly getting closer to being able to post there though (grin).
One school of thought over there is that the Honeycomb AOSP is a hacked up kludge "not ready for primetime" and that's why Google doesn't want it out.
While that is very likely true and (and will probably continue to be true now that 3.1 is released), that is no justification for opposing "opening" the source.
Since I expect the kludges will be "grandfathered" throughout future releases, I don't expect to ever see HC AOSP. I could be wrong, but it really doesn't matter because ICS will be out by then and everybody will be wanting to port to it.
What I'm concerned with is the "promise" of ICS being released in a timely fashion. Mr. Rubin has made earlier "promises" that have later been rescinded. I don't think he EVER wanted HC released and was just trying to "buy time" until Google I/O 2011 so that he could take the heat off with the announcement of ICS.
I hope I'm wrong, but ... fool me once, shame on you. Fool me twice....
Divine_Madcat said:
However, they keep saying ICS for quarter 4, which is half a year away.
Click to expand...
Click to collapse
Fiscal, or calendar? Because fiscal Q4 is July-September.
zombieflanders said:
Fiscal, or calendar? Because fiscal Q4 is July-September.
Click to expand...
Click to collapse
Technically, i don't think they have said, but i have never seen any other Google release announcement refer to a fiscal quarter instead of the calendar. I would love for it to be fiscal, but that is a real pipe dream.
DM -
Tell them over in the other thread that Andy Rubin's quote was in a Q&A w/press after his keynote.
DiDGR8 said:
DM -
Tell them over in the other thread that Andy Rubin's quote was in a Q&A w/press after his keynote.
Click to expand...
Click to collapse
Consider it done.
Divine_Madcat said:
Consider it done.
Click to expand...
Click to collapse
Thanks (just one more post and I can get into Dev!!)
So Google has released the SDK for ICS here: http://developer.android.com/sdk/android-4.0.html
I've been doing some dev work on my Toshiba Thrive and wanted to know if anyone wanted to start working to port over ICS to our phones. I'm unsure about whether or not we'll get an actual ICS update so I figured I'd post up and gauge interest!
Let me know guys
Correct me if I'm wrong but don't we need the ICS source to be released to even start on a official port?
Sent from my MB860 using XDA App
parsa5 said:
Correct me if I'm wrong but don't we need the ICS source to be released to even start on a official port?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Its possible to port the SDK, but it will be harder, messier and things generally wont work 100%. This was the case with Honeycomb
The Cyanogen Mod team issued a statement saying that they will not release CM9 until the source is released. Don't you guys think that it's way too risky to use the SDK? Afterall, the source will be made available just a few weeks after the Galaxy Nexus will be made available to the general public (Source: Android Police).
Jibraldor said:
The Cyanogen Mod team issued a statement saying that they will not release CM9 until the source is released. Don't you guys think that it's way too risky to use the SDK? Afterall, the source will be made available just a few weeks after the Galaxy Nexus will be made available to the general public (Source: Android Police).
Click to expand...
Click to collapse
The problem with an SDK port is that you have no control over it. Its entirely up to luck if things work, and even then things wont work as well as they could were they to be compiled for the device in question. Also because of this, any work that goes into an SDK port would be 100% useless once the source is released, so there's no point in even starting it. For that reason I highly doubt CM9 will see any work done until the source hits.
Its not going to be too long now. The Galaxy Nexus will be out in a few weeks to a month, and the source shouldn't be too far behind. I dont expect us to have stable ICS this year, but hopefully we'll have something by early 2012.
Over in the desier hd forum they have a dump from a working device that we might be able to do something with.
I figured working on porting the sdk would prepare us for the source code release. We should be able to quickly port it over once the source is released.......hopefully. I don't see the GNex coming to at&t until early next year so I'm hoping to get a working port of ICS as quickly as possible on my atrix and I figure the only way to ensure that is to take initiative.
I really want the GNex though. That phone looks pretty cool. I hope it doesn't get a Verizon only release in November
spitefulcheerio said:
So Google has released the SDK for ICS here: http://developer.android.com/sdk/android-4.0.html
I've been doing some dev work on my Toshiba Thrive and wanted to know if anyone wanted to start working to port over ICS to our phones. I'm unsure about whether or not we'll get an actual ICS update so I figured I'd post up and gauge interest!
Let me know guys
Click to expand...
Click to collapse
hobbit19 is starting too, lets all work together on this
When you have something to post, then we can re-open this thread. Threads about the intention to develop are not necessary in the development lounge. PM me when you have made progress on a port and we'll re-open this thread. Good luck, mate!