For those of you wondering what phones will and will not get Gingerbread, or the tards (or just diehard wishful thinkers) that think Verizon will just skip right over FroYo and go to Gingerbread, this is an official quote from Verizon:
"Google's just-announced Gingerbread software is generating buzz in the media.
Initially, it is not available on the Verizon Wireless lineup of Android phones.
BUT ... we're working with Google as they release source code for device manufacturers to begin integration. We are also assessing which devices will get Gingerbread within the coming months.
Stay tuned - more information will be available soon."
So that means, they won't even begin ASSESSING what phones receive the updates for MONTHS. Not days, not weeks, MONTHS. So those hoping to see Gingerbread anytime soon, well, sorry to burst your bubble, but its not happening. Those thinking FroYo was delayed to bake its bug fixes into Ginger, well, they'd have to delay it for months. Lets hope this is not the case....
Don't ask where I got the quote from....'tis not your concern
No
Sent from my SCH-I500 using XDA App
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
Click to expand...
Click to collapse
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Who really cares about gingerbread anyway. I'm very satisfied with DJ05 update, roms/kernals/themes. I can now wait patiently for froyo and... not even concern myself with when/where gingerbread will be released.
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
imnuts said:
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
Click to expand...
Click to collapse
Samsung has code obviously, without it, they couldn't have built the Nexus S. And I doubt Google builds the "Nexus" software because of all the little nuances of the code interacting with drivers and so forth (RIL ring a bell????), but I could be wrong, I don't work for either Google or Samsung.
I doubt the other OEM's have any builds running yet, as evidenced by the very first reference to builds, where they say that they are working with OEM's AS GOOGLE releases source code for them to integrate into their phones, but people can take it for what they wish.
I just put the quote out there verbatim. Do with it what you will.
mexiken said:
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Click to expand...
Click to collapse
Actually I don't know how many times this has been said. Google releases their OS source not so long after their press release. It is the OEMs who have to release their kernel for us to develop anything. We've had 2.3 code for awhile now but we don't have kernel. They just released Nexus One kernel like yesterday so they'll get it pretty soon. People, Google's OS code and OEM kernel are two different things. We always had code source pretty fast at hand.
The fact that I'm super-skeptical of these unsourced-but-supposedly-from-Verizon quotes aside, I think imnuts has a point here.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months.
Click to expand...
Click to collapse
According to the rules of grammar, he's right. The order matters: since the clause "will get gingerbread within the coming months" comes after "which devices," not "we are assessing," it refers to the former. Had the quote been "We are also assessing within the coming months which devices will get Gingerbread," then it would be the other way around.
But that aside, even more importantly, saying a process will happen "within the coming months" doesn't mean that the process won't start for months. It means something is likely to be ongoing and could be done within one month, six months, or anything in between (or longer). Ultimately, that's the kind of wording people use when they want to remain intentionally vague, and we really can't read a timeline one way or the other from it. Especially when it comes to mobile carriers and software updates.
mexiken said:
There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ????
Click to expand...
Click to collapse
Well, for starters, Samsung obviously has had the 2.3 source code for quite some time considering they have a Gingerbread phone coming out tomorrow. We also know Motorola has the 3.0 code seeing as how they're working on at least one already-functional Honeycomb device. The only one we can say definitely doesn't have 2.3 is LG, because they said so (though they also said 2.3 required a 1ghz processor in the same breath, which turned out to be a complete lie, so it's hard to trust them). But clearly, AOSP gets the code just a tad later than at least some OEMs do.
Related
From : http://www.google.com/support/forum...488da0ef21660d1300048994d2e4bf4c&hl=en&hltp=1
Ry Guy
Google Employee
07:03 PM
Hey guys,
Just dropping in to let you know that the FRF72 build that is floating around is not the official update. The Android team is feverishly working to get a final version out the door, but like passion-ate has mentioned this will only happen once a release candidate meets our quality criteria.
Since today is the Summer Solstice, we know things will be heating up a bit so hopefully Froyo will be on its way shortly. Thanks for your continued patience!
-Ry Guy
So… that tells us… not very much but we now know 2 things:
* FRF72, which was the latest official leaked Froyo build, was not the final version (we kind of already suspected that)
* and Froyo is still not ready
cool, thnx for the info
And so the wait continues...
Then again if the google guys think that FRF72 still doesn't meet their standards... could be a good thing.
I'm expecting the OTA'd Froyo to have the option to take over Apple's servers and Ddos them to pieces.
watch, we will have waited all this time for froyo and instead we get gingerbread. (crosses fingers and hopes)
Good to know...seems like Google is taking QA to a new level!
http://encyclopedia2.thefreedictionary.com/When+It's+Done
(jargon) When It's Done - A manufacturer's non-answer to questions about product availability. This answer allows the manufacturer to pretend to communicate with their customers without setting themselves any deadlines or revealing how behind schedule the product really is. It also sounds slightly better than "We don't know".
sandtiger said:
http://encyclopedia2.thefreedictionary.com/When+It's+Done
(jargon) When It's Done - A manufacturer's non-answer to questions about product availability. This answer allows the manufacturer to pretend to communicate with their customers without setting themselves any deadlines or revealing how behind schedule the product really is. It also sounds slightly better than "We don't know".
Click to expand...
Click to collapse
just hopefully it wont be as bad as BlackMesaSource's "When its done" this mod has taken like 3 years
lalalalala
Blueman101 said:
just hopefully it wont be as bad as BlackMesaSource's "When its done" this mod has taken like 3 years
Click to expand...
Click to collapse
Pretty sure its actually five years in the making because I've been watching for 3 years and I'm sure they started in 04-05 right after half life source came out. nothing compared to duke nukem forever
JCopernicus said:
lalalalala
Click to expand...
Click to collapse
This newb is curious, how are you tracking these things?
flybyme said:
.....nothing compared to duke nukem froyo
Click to expand...
Click to collapse
Needed a small edit, all fixed now.
funny how long its taking google when they seemed so confident at I/O that it would be out shortly. what did they discover i wonder that suddenly needed so much attention?
anyway it doesnt bother me. but i know the complainers in the main google forum arent as forgiving. i have to wonder, what do those people think, that google is holding back 2.2 on purpose? what would be the hidden motive!
RogerPodacter said:
funny how long its taking google when they seemed so confident at I/O that it would be out shortly. what did they discover i wonder that suddenly needed so much attention?
anyway it doesnt bother me. but i know the complainers in the main google forum arent as forgiving. i have to wonder, what do those people think, that google is holding back 2.2 on purpose? what would be the hidden motive!
Click to expand...
Click to collapse
I agree, its tough to be mad since we already have it anyway. But I'm with you I'm intrigued by the delay, not put off by it. Hopefully google will not be too embarrassed to announce what caused the delay.
Re: Google Officially Updates Us On Froyo Status FRF72 Was Not Final,
I'm still excited, they work hard at Goggle, I'm sure the official update its going to be great when its ready.
I think we should have stick to 2.1 till the official froyo comes up,it's good to see that Desire to N1 Roms are active again
Rodriguezstyle ROM with FRF72 us amazing already
Fastest, smoothest Android I've ever used.
Cant wait for 75
So FRF72 is not the final build. What will be in the new build. Is there a list available what items is not met yet in the FRF72 build?
All this time I always have a feeling that froyo is being delayed due to flash! My thought is that they are waiting for the final flash build to optimize froyo for it.
Adobe has released Full flash 10.1 to android androidcentral.com/adobe-releases-flash-101-partners
so dont think they are waiting on flash anymore
and whilst waiting for flash to be ready they thought. "Hey, let's watch some korean drama and worry about gingerbread later"
As you probably know last Month that Samsung pulled-out the froyo Update files of the Samsung Galaxy S from its servers due to Many System Bugs that Made the Android froyo unstable and laggy. And Samsung UK confirmed on its twitter Status that the Froyo Update is Coming on November on its Final Version and to All Network operators and No More Delays...No More pulling-out!!
We Got Some Information that the Release Date of the Galaxy S Froyo update for USA Carriers and UK Carriers is somewhere around 11th November,2010 as a FINAL Release Date. Worldwide release will follow in few days after the Official Release of the Froyo ROM for Samsung Galaxy S, which Means that All Galaxy S users Worldwide (Include Middle-East and Arab gulf users) will get the update on November along with UK,USA Carriers too.
Froyo rolling out in UK Nov 4
So The Update is Coming Finally and NO More Delays AT ALL... More Stable... More Smoother, its a matter of time right Now. As I always say "Waiting for the froyo to come-out, better than waiting for it to load!".
http://www.youmobile.org/blogs/entry/Galaxy-S-Getting-Froyo-on-11-November-Final-Date-
To unsubscribe from these announcements, login to the forum and uncheck "Receive forum announcements and important notifications by email." in your profile.
You can view the full announcement by following this link:
http://www.samsunggalaxysforum.com/...es/final-date-for-galaxy-s-update-(nov-11th)/
Regards,
The Samsung Galaxy S Team.
Hmm. My read of the actual text that Samsung sent out is not actually any different than it was a week or so ago: the i9000 will probably have 2.2 sometime before the end of the month, along with the rest of the UK/Europe. I really don't see anything in the "official" Samsung notice that indicates Verizon, or any other US carrier.
However, since the blog posts cite "Some information" for "somewhere around 11th, November as a FINAL release date" (How's that for ambiguous, "somewhere around", but it's also "FINAL"...), I'll be guardedly optimistic.
Make that HEAVILY GUARDEDLY optimistic...
Verizon will decide when its released, not Samsung.
it says late in November for the carrier branded versions
adrynalyne said:
Verizon will decide when its released, not Samsung.
Click to expand...
Click to collapse
....Bingo!
/sigh
Sent from my SCH-I500 using XDA App
I don't care. Wait before you flame, please...
I spent the last year with an Omnia, and I tried every possible rom on it until I found the one I liked/could put up with the missing features. It wasn't perfect, but I knew that a sweet android phone was in my upgrade future so I dealt. WinMo has it's flaws, but you can't fault the dev community for everything they did to make an ok device better.
Now here I sit swyping on arguably the best hardware on the market (other Galaxy S offerings aside...) and I have to say I really like it.
Voodoo-ed, de-binged, de-odexed, and de-TouchWizzed is way easier than trying a dozen roms on a weekend and adding .cabs from 100 websites to come up with a phone that still half the time didn't know where my finger was trying to press!
What does FroYo have to offer? Apps that run off the SD card? Flash? Minor, although it is a bit frustrating that by the time we get it, it will just about be time for gingerbread.
Guess I'm trying to say, the best stuff about froyo is going to get too us sooner or later whether VZW or Samsung give it to us or the very talented dev community here makes it happen. News that comes from them isn't why I log in here.
Sent from my SCH-I500 using XDA App
Downers
adrynalyne; said:
Verizon will decide when its released, not Samsung.
Click to expand...
Click to collapse
Just trying to give some legit info for a change... A lot of wet noodles.
Ok so I was told 2.2 would be released the other day.... and YES I used the word NINJA. ... I was wrong. But do we gotta keep mentioning NINJAS? ? Hahahahahahaha : )
Sent from my SCH-I500 using XDA App
No ninja source? I have my doubts about this info...
As for Froyo, I am excited to have flash, but beyond that, voodoo seems to meet my needs. Sure, you can't get rid of voodoo without performing a animal sacrifice, but it does make my phone smooth and sexy.
Sent from my SCH-I500 using XDA App
jatilq said:
Just trying to give some legit info for a change... A lot of wet noodles.
Click to expand...
Click to collapse
Sorry man, I wasn't trying to pee in your cornflakes, it's just that I have more faith in devs than VZW & Samsung to get us what we want.
Sent from my SCH-I500 using XDA App
I don't know about you but I am waiting for my navigation to be fixed. Not to worried about the little extras but the major fixes that are, major.
Sent from my SCH-I500 using XDA App
Quoted from original post 'No More pulling-out!!' That's what she said! Ha Ha...
I'm sorry I couldn't help it. I wont do it again I swear.
Honestly I can't wait to see what magic the dev community creates with Froyo and the Fascinate. My thanks to all of you!!!
Hopefully what happened with all the Droid 1 releases is what will happen here:
Motorola (in this case Samsung) readies a build, gives it to VZW for testing.
VZW takes forever testing it, and either rejects or preps it for release.
The "hopefully" part is that, hopefully, in the meantime, the file gets leaked from the Samsung end and into our hands.
Not trying to be pessimistic, but if that first file didn't leak, Im doubtful that this one will leak early either
If Verizon decides to sit on the release at least we have US Cellular as a backup. In fact it seems like US Cellular does not waste their time with carrier customizations so they might just push it out the same day they get it from Samsung.
I used to be a US Cellular customer, my wife still is, they will not get in any hurry, I would not count on them for anything.
nitroxeno said:
If Verizon decides to sit on the release at least we have US Cellular as a backup. In fact it seems like US Cellular does not waste their time with carrier customizations so they might just push it out the same day they get it from Samsung.
Click to expand...
Click to collapse
You missed the point of the post bud.
Verizon, or any carrier, does NO customizations, they have NO development (read: coding) teams. They don't alter the file they receive from the OEM (in this case Samsung) in ANY WAY. The bloatware you see comes with the build straight out of Samsung's repository, with the specs that Verizon requested. They take their sweet time for a multitude of reasons, and somewhere in that timeframe its held up for internal testing. Each carrier is different, but Verizon is notorious for being an extensive tester, and rejecting builds pretty often.
Bloatware that Samsung did not code....VZW did or outsourced. Hence people are arguing with you. You aren't wrong, but neither are you entirely correct.
Sent from my SCH-I500 using XDA App
I made this post to give some indication of the progress of Froyo, sadly most people want more or are intent on offering some type of dark cloud.
I know Froyo might not be released on the 11th, but at least we have a legit source of its progress. Hopefully around that time or before we will have a leaked build for testing and or roms (like some other devices). I'm sure thats when the dev section will take off.
well if samsung releases it Nov 11, dont they post the source up too, so we could have a modded version running before vzw does anything?
Today, I kept getting random messages from random numbers, so I called in to block, the rep also had a vibrant. So she was like "So... how do you like the vibrant?"
I'm all like "It's sexy"
But it took her so long to solve my problems, so I asked about random stuff like "Do you know when Froyo is coming out?"
She was a pretty "SMART TECH" you don't see those much on help lines now do you?
She replies: Let me check on that for you
and then she came back on and said "it won't be anytime soon, because if it is anytime soon, the tech supports usually knows weeks or months beforehand, but right now, it says 'to be determined'"
SO, do you guys it'll take as long as the rep said?
Unfortunately, this still fell into the same "He Said She Said" category, until we get an official statement, it's all moot. She may be smart but she is still a rep and I doubt she will have access to OTA information. She most likely turned around and asked her best friend/co-worker who is a tech, and he replied that he didn't know anything, and she passes that onto you.
I think she's right. We already know that froyo would come by the end of the year according to the galaxy s twitter. I expect it to come around December 29. Am I so pessimistic?
ori2 said:
I think she's right. We already know that froyo would come by the end of the year according to the galaxy s twitter. I expect it to come around December 29. Am I so pessimistic?
Click to expand...
Click to collapse
No, I believe you are pretty optimistic. End of December...well..
same here. I read the same thing in a tech online magazine.. they actually said 2011 but no precise date..
Im running the unofficial TMO froyo posted in this forum though and I like it
Cheers
Personally, I think Samsung should just give up and hand over the kernel source, maybe keep some respect.
The Unoffical Official T-MO Froyo ROM is in the Development section. If that is actually the real thing (and I completely believe it is) I don't see what the delay is for them to just release it.
Even when it does come out, I know for myself that I will keep a custom ROM. Why have stock when you can rock!
I think the point for all of us that are running one of the leaked 2.2 roms is that an official release will have more of the bugs ironed out and it will help with some of the compatibility issues. I for one have tried all flavors and each has a quirk or two. The good thing is that when 2.2 finally drops officially the devs will have almost perfected their roms and it will be easier to implement any changes made by Tmobile.
Sent from my SGH-T959 using XDA App
I agree with the previous post. I think Samsung leaked the ROM so that the devs here could get their hands on it and make fixes that they then can implement into the official ROM.
So it wouldn't be so embarrasing on Samsung's part? x) Something big like a software update isn't too "easily" leaked. So I do sort of have to agree too.
According to this website, there have been multiple rumors from independent sources at MWC stating that Gingerbread is supposed to drop OTA by the end of this week or early next.
Any truth to this or do you guys call shenanigans?
http://www.mobilecrunch.com/2011/02...e-to-hit-nexus-ones-within-the-next-few-days/
I'll believe when I see it.
I'm afraid this rumour is even less reliable than @googlenexus' tweet in the early December days...
Same.
10sames.
I really want to believe this one as there are multiple devices set to launch with Gingerbread, and it's been long enough. Yeah, I am running CM7 but I want it fully optimized with the OTA drivers.
Here it goes again...
I will believe it when I see it.
popophobia said:
Here it goes again...
Click to expand...
Click to collapse
Eventually, one of these "here we go again" threads has to be the real one.
so wait, you said it might come this week, or next week.
so it might come in the coming weeks....and yeah this is what google has been saying all along.
let's see what happens next month.
They said "next few weeks" and that was 3 months ago, so following that logic, "next few days" will be 3 weeks
keep waiting...
Sent from my Nexus One using XDA App
Gingerbread ota will drop the day I purchase a babana shaped galaxy s.
Been running gingy on my N1 for some time now...In CM7 form.
BREAKING NEWS #mwc11: "#Nexus One #Gingerbread OTA": "In the next few DAYS".That STILL is:From this very instant up to the rest of eternity.
I understand all of the scepticism, but, with the slew of devices announced at MWC that are set to launch with Gingerbread, doesn't it make sense that the Nexus One should receive the update soon?
With the passion branch alive and well in AOSP, it's highly likely that the Nexus One is still a viable handset for Google.
I did wonder if we'd see an OTA during MWC. It seems to be a good opportunity for Google to promote Android with all these new devices that are lined up to launch with Gingerbread.
Can only hope at this point i guess
offenberg said:
Gingerbread ota will drop the day I purchase a babana shaped galaxy s.
Click to expand...
Click to collapse
Good. I would propose, you just go and buy it right now, so we can have our Gingerbreadz
Well i've played around with some roms here, some mostly work and some are still a work in progress. I'd prefer to get a polished Gingerbread whenever they decide to push it out, not really rushing this one.
I'd wait for 2.4
After using some of the AOSP built roms out there, and seeing how they are a bit wonky, I am perfectly happy waiting for a polished release. If that means 2.4 with all the bugs and fixes, then so be it.
At the end of the day, even though people who own the n1 are desperate to continue to feel like they are up to date, the fact is that 2.2.2 is functional as hell, and there isn't much that is going to be augmented by the release of 2.4. Honestly, it will look different, im sure it will have a few improvements but the functionality will still be the same. It is not the type of jump we saw going from 2.1 to 2.2
The easter bunny will be delivering it to your doorstep....
FFS, rumors or not, I'll believe it when someone ACTUALLY gets an OTA for 2.3.
It's been bothering me that a lot of people don't think the atrix is going to get an official ice cream sandwich update.
I decided to make this thread to consolidate any discussion or questions about the future update.
The android carrier alliance promises that any device will be updated to the newest version of android for 18 months after its release (if its hardware allows it).
Three points to make:
1) Since ICS is being released in oct/nov, the 18 months portion of the agreement becomes null and void. The atrix is within the timeframe.
2) The nexus S is getting ICS, and since the hardware in the atrix is superior (dual core processor, battery, etc), the atrix can receive the ICS update.
3) With google's acquisition of MM the likeliness of the atrix receiving ICS has gone up substantially, whether or not it remains as a seperate branch under google's ownership. It also increases the chances of us getting a stock (or very close to stock) ICS build.
All these signs point me to believe that the atrix is for sure getting ICS. What're your thoughts?
Cheers
Also I think the Atrix Dev Team will be handing their CM7 build over to Cyanogenmod for nightlis and it will be an official CM device. And if that happens, when Cyanogenmod makes CM8 with ICS we'll get it the I'd guess.
4 Words...
Who gives a crap.
Didn't they announce that after the release of the Atrix ? Or does that not matter?
Sent from my MB860 using XDA Premium App
I think my thread was cooler.
I voided my warranty.
Magnetox said:
3) With google's acquisition of MM the likeliness of the atrix receiving ICS has gone up substantially, whether or not it remains as a seperate branch under google's ownership. It also increases the chances of us getting a stock (or very close to stock) ICS build.
Click to expand...
Click to collapse
I think that while Google's purchase/buyout seems like it may benefit Android users. I also feel that it will not give any benefits until long after the Atrix has passed it's sell by date. Mergers and acquisitions take time to complete. Systems have to be integrated on a large scale, and corporate policies realized in the acquired business. I think Google's initial focus will be on patents, and secondary long term focus will then be Android, and how they can take the lions share of the marketplace with smart devices (not just phones). Give it 2 years at least in my opinion before we see a big swing.
This is almost the exact same thing I said over in the Motorola Forums (or maybe I said it here, I can't remember). It seems people expect things to change immediately but probably don't realize it's not even a done deal yet as of this posting. There still needs to be an investigation and approvals and all that. Like you said, it could be a couple years before any changes (within Motorola's camp anyways) becomes noticeable.
CaelanT said:
I think that while Google's purchase/buyout seems like it may benefit Android users. I also feel that it will not give any benefits until long after the Atrix has passed it's sell by date. Mergers and acquisitions take time to complete. Systems have to be integrated on a large scale, and corporate policies realized in the acquired business. I think Google's initial focus will be on patents, and secondary long term focus will then be Android, and how they can take the lions share of the marketplace with smart devices (not just phones). Give it 2 years at least in my opinion before we see a big swing.
Click to expand...
Click to collapse
Also, it seems people forget that Motoblur exists on Motorola devices. Unless they actually convert the Blur service into a full on application platform I don't see an "Official" ICS build coming to the Atrix until at least 6 months after Google releases the code for it. Our best bet lies within the great devs we have here in the community. Which reminds me, everyone, stop complaining about updates!
live4nyy said:
This is almost the exact same thing I said over in the Motorola Forums (or maybe I said it here, I can't remember). It seems people expect things to change immediately but probably don't realize it's not even a done deal yet as of this posting. There still needs to be an investigation and approvals and all that. Like you said, it could be a couple years before any changes (within Motorola's camp anyways) becomes noticeable.
Click to expand...
Click to collapse
Here's the thing, yes Google will have a flava of it sitting around that XDA can port over.
The real question is what's the ETA with the carriers?
For instance my Motorola Milestone didn't have "Froyo" ready until the end of March this year, and it was a half-assed effort put together by Telus. Then shortly after, they discontinued the phone.
I agree that XDA users will have a port of ICS through CM7, but for OTA who knows when that will be?...
Sent from my MB860 using xda premium
Magnetox said:
It's been bothering me that a lot of people don't think the atrix is going to get an official ice cream sandwich update.
I decided to make this thread to consolidate any discussion or questions about the future update.
The android carrier alliance promises that any device will be updated to the newest version of android for 18 months after its release (if its hardware allows it).
Three points to make:
1) Since ICS is being released in oct/nov, the 18 months portion of the agreement becomes null and void. The atrix is within the timeframe.
2) The nexus S is getting ICS, and since the hardware in the atrix is superior (dual core processor, battery, etc), the atrix can receive the ICS update.
3) With google's acquisition of MM the likeliness of the atrix receiving ICS has gone up substantially, whether or not it remains as a seperate branch under google's ownership. It also increases the chances of us getting a stock (or very close to stock) ICS build.
All these signs point me to believe that the atrix is for sure getting ICS. What're your thoughts?
Cheers
Click to expand...
Click to collapse
Your first point is completely wrong. They guaranteed updates to the phone, but never specifically to the "latest version" of android released. IE you will get security/bug fix updates, but not necessarily updates to the base OS. Secondly, this only applies to phones released AFTER the agreement. Also, google is merely urging NOT requiring them. So basically, all this agreement leads to is that future devices will have a minimum of an 18 month support cycle, nothing more.
Right after we get GB, people start asking for ICS...
This even shows more proof that we, as human, will never be satisfied with what we got.
which can be both good and bad..
tian105 said:
Right after we get GB, people start asking for ICS...
This even shows more proof that we, as human, will never be satisfied with what we got.
which can be both good and bad..
Click to expand...
Click to collapse
There are no humans here, only Androids and Androids are selfish.
Sent thru a series of tubes using XDA Premium app
I read this...sounds like we are going to be seeing it next month...
http://www.pocket-lint.com/news/41975/android-ice-cream-sandwich-release-date
Mac
Mac11700 said:
I read this...sounds like we are going to be seeing it next month...
http://www.pocket-lint.com/news/41975/android-ice-cream-sandwich-release-date
Mac
Click to expand...
Click to collapse
my bday is next month lol and this would make a great gift comming from googrola
tian105 said:
my bday is next month lol and this would make a great gift comming from googrola
Click to expand...
Click to collapse
I saw this on my b-day yesterday...
Mac