In January we will have Ice Cream Sandwich
http://gizmovil.com/2011/10/dispositivos-de-acer-actualizaran-a-ice-cream-sandwich-en-enero
if it is true 10 points for Acer
regards
There is a link to a slashgear thread in that article. I am really happy if that is true! Maybe that is why we haven't gotten a firmware update to fix a couple of these bugs.
http://www.slashgear.com/acer-andro...eam-sandwich-update-in-january-2012-25190709/
I am looking forward to this.
i love it
It would be nice if they rolled this update out before Christmas it would draw a bunch of new buyers to the tablet. and increase the attention to it for devolpers.
I don't think Google has released ICS yet to developers, so it won't be before Christmas.
ics
They released ics at the same time they announced it. I have the sdk and can run it in the emulator. I am sure they have released it to devolpers since there is a phone out running it.
Okay, so I saw a bunch of the tech news sites running with the story about 5.0 coming out in Q2 (Google I/O?). Anybody have any GOOD info on this? I can't imagine it will be anywhere near as big an update as 4.0 was, but I am curious as to what it will have, who will get it first (GNex makes the most sense), and how far behind that release 6.0 and the next Nexus device are.
The next version will be 4.1
Sent from my Galaxy Nexus using XDA App
Hemlocke said:
Okay, so I saw a bunch of the tech news sites running with the story about 5.0 coming out in Q2 (Google I/O?). Anybody have any GOOD info on this? I can't imagine it will be anywhere near as big an update as 4.0 was, but I am curious as to what it will have, who will get it first (GNex makes the most sense), and how far behind that release 6.0 and the next Nexus device are.
Click to expand...
Click to collapse
We won't be seeing 5.0 for at least until Q4.
We may not get it until Q4 but it is extreamley probable that is will be announced in Q2 due to that's when google i|o is
cordell507 said:
We may not get it until Q4 but it is extreamley probable that is will be announced in Q2 due to that's when google i|o is
Click to expand...
Click to collapse
Doubt it. THey haven't even polished ICS. They would just stir up **** talking about 5.
if anything, Android 5 would probably be more of a minor update like it was from froyo to gingerbread than gingerbread to ICS. more behind the scene changes
This just further proves to the tech blog community that 'android fragmentation' will always exist.
kfirms said:
This just further proves to the tech blog community that 'android fragmentation' will always exist.
Click to expand...
Click to collapse
If thats the price of having a 'latest and greatest' style community I'm fine with that. I think went you have fast paced development and your always looking at the next big thing theres always gonna be a lack of consistency.
Troll... troll and more troll...
Enviado desde mi Galaxy Nexus usando Tapatalk
If it duel boot chromium then it will be a PC build
Sent from my Galaxy Nexus using xda premium
Why has the word RUMOR been left out of this entire thread!?
Okay continue the speculation..
Have to love Rumors, I think 4.1 is more logical than 5.0 and I would think we would see it on the gnex fairly quick. But again this is all speculation and rumors at this point.
Sent from my Galaxy Nexus using Tapatalk
I don't really see versioning == fragmentation. Having developed with and seen the android SDK grow, it looks like natural evolution to me.
Most people don't really get it. From 2.3 to 4.0 isn't like they rewrote "android", the changes are not that drastic. Its still essentially the same basic API and framework, with additions and deprecations as needed. In fact the increase of a "major" version number (2->4) was completely a farce, and entirely marketing spin.
So, 5.0 will be much of the same, and 4.0 is so good now, I can't say I'm all that worried about when its coming out. My main concerns are with manufactures optimization of the drivers that interface with the ICS HAL. Get that ironed out first, and let ICS be ICS.
Only real direction for growth is for Android to start having the ability to become a desktop computer + tablet in one, basically like W8 is trying to do.
ICS basically bridged phone + tablet, so only remaining path is to add desktop to it, to be able to replace most office computers (that aren't needing high powered gear)
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Deofol said:
I don't really see versioning == fragmentation. Having developed with and seen the android SDK grow, it looks like natural evolution to me.
Most people don't really get it. From 2.3 to 4.0 isn't like they rewrote "android", the changes are not that drastic. Its still essentially the same basic API and framework, with additions and deprecations as needed. In fact the increase of a "major" version number (2->4) was completely a farce, and entirely marketing spin.
So, 5.0 will be much of the same, and 4.0 is so good now, I can't say I'm all that worried about when its coming out. My main concerns are with manufactures optimization of the drivers that interface with the ICS HAL. Get that ironed out first, and let ICS be ICS.
Click to expand...
Click to collapse
Anti-android people just like to throw out the word fragmentation, don't feed trolls.
kfirms said:
This just further proves to the tech blog community that 'android fragmentation' will always exist.
Click to expand...
Click to collapse
Hey you, get back under your bridge until we say you can come out.
Damnit I accidentally hit thanks.
I don't know why people keep shooting this down as a rumor?
It's almost certain that we will see a major announcement in Q2, since google has been updating android 2 times a year almost since its release. The only uncertainty is whether they'll upgrade the name and how much they'll upgrade the version number.
So yes we will see an announcement at Google I/O and it'll be likely to hit our gn's first, just as we will see another one in Q3/4 along with another device release.
mortenmhp said:
I don't know why people keep shooting this down as a rumor?
It's almost certain that we will see a major announcement in Q2, since google has been updating android 2 times a year almost since its release. The only uncertainty is whether they'll upgrade the name and how much they'll upgrade the version number.
So yes we will see an announcement at Google I/O and it'll be likely to hit our gn's first, just as we will see another one in Q3/4 along with another device release.
Click to expand...
Click to collapse
You must have missed the announcement where Google said they will only give one update a year from here on out. With all the clamoring on how ICS is a "huge" update you will NOT see 5.0 in Q2 AND something in Q4.
Sent from my Galaxy Nexus using xda premium
I think we'll see a 4.1 update fairly soon, but JellyBean probably not until next year during the annual release and it will probably be just back end code like stated. We'll probably start seeing information on it around the end of Q2 but I don't see anything dramatic coming to light.
ICS was the BIG change over everyone was waiting for that brings tons of features to the table. I can't see them doing anything dramatic for a while. I think the CORE Android is where they want it to be now where Tablets and Phones are merged into one single version.
someone swing by google and see if the statue is up or not
mortenmhp said:
I don't know why people keep shooting this down as a rumor?
Click to expand...
Click to collapse
Because everywhere this is found on the internet it is tagged with a big ass RUMOR in the title!! And the original source is known for pulling **** out of their ass.
quoted from
http://www.androidauthority.com/android-jelly-bean-multiple-nexus-devices-86027/
WSJ: Multiple Nexus devices coming this fall, from five manufacturers, Jelly Bean onboard
Traditionally in the Android development cycle, major versions have launched at the end of the year (exception being Gingerbread/Honeycomb). According to the Wall Street Journal, Android Jelly Bean should launch this year, “by Thanksgiving”.
Will this be Android 5.0 or another version? That depends on Google’s plans for their I/O developer event happening in June. Andy Rubin’s team has two options: one, launch an Android 4.1 version with some improvements at I/O (and call it Jelly Bean), and then give a new name to Android 5.0. Two, use the event to showcase upcoming features of Android 5.0 Jelly Bean, and release it this fall.
Now, the rumor in WSJ says that Google is getting five manufacturers (probably Samsung, HTC, Motorola, Sony and LG – no love for Huawei, Google?) to release “Nexus devices”, all at the same time, this fall. How is this possible? Well, Google plans to give all of them early access to the next major version of Android, much like Microsoft does with Windows and WP7 manufacturers.
Google plans to launch the next version of Android with all of them at once , with some less important manufacturers launching a little later.
So what does this mean for us, the users? It means that we get to choose from at least 5 phones and maybe some tablets, too (some manufacturers will choose to release both a phone and a tablet), so our choices for stock Android devices will greatly improve. Even better, they will all be available from day one. That means that, if you don’t like a particular Nexus device, you have several others to choose from, and you won’t have to wait many more months until other devices appear.
This deal means that stock devices will flood the market. Also, manufacturers will have early access to the Android code, meaning that they will also be able to upgrade their skins faster and launch new devices faster. However, the first devices will still be only stock Android. And Google should make sure of that through a formal agreement.
According to WSJ, the Nexus devices will most likely be sold through Google’s Play Store in US, Europe and Asia, which again is a great move for Google, because they’ll be able to wrestle control over Android from carriers. It won’t hurt carriers too much, because at least in US, most people still buy phones through carrier subsidies, but it should work very well in markets in Europe and Asia.
Overall, this is a very smart move from Google, that will benefit themselves, the consumers, and even the manufacturers.
Please post ALL new phone news here:
http://forum.xda-developers.com/showthread.php?t=1642801
Thanks
FNM
Before you all scream heresy, hear me out.
Today marked Verizon officially announcing 4.2.2 for the Galaxy Nexus, thus marking the end of the VZW model being 4 updates behind the GSM models. Here's the thing...every time there's been an update in testing, El Madhatter has informed us because of his testing phone. He never got a 4.1.2, 4.2, or 4.2.1 build. His device went straight from 4.1.1/JRO03O to 4.2.2/JDQ39. Because of that, one can logically deduce that Google never actually released a 4.1.2, 4.2, or 4.2.1 build to Verizon for testing on the device.
There is historical precedent for this. Let's go back to December, 2011 when Android 4.0.3/Ice Cream Sandwich was released to the Nexus S and Motorola Xoom. Only two variants ever got Android 4.0.3:
1. The 900 MHz carrier-unlocked Nexus S (I9020T/I9023 - Got build IML74K)
2. The Wi-Fi Motorola Xoom (MZ604 - Got build IML77)
Here's a list of devices that never saw an update until Android 4.0.4/IMM76(X) was released in late March, 2012:
1. The 850 MHz carrier-unlocked Nexus S (I9020A - Updated directly by Google with no carrier approvals just like I9020T)
2. The Sprint Nexus S 4G (D720)
3. The Korean Nexus S (M200)
4. The Verizon Motorola Xoom (MZ600/MZ602)
5. The carrier-unlocked Galaxy Nexus running yakju firmware (I9250)
6. The Verizon Galaxy Nexus (I515)
The I9250 Play Store (running takju) model was not available yet.
So as you can see, clearly Google picks and chooses which devices get which updates in the event of brand new Android versions sometimes. Some builds (like 4.0.3) were clearly designed to be limited rollouts to test on a more limited scale. Then once they fix bugs, they do a more massive rollout (like they did with 4.0.4). Something tells me that 4.2 was the same thing.
4.2 and 4.2.1 had exactly one difference...the fixing of the December event bug. So, I think it's clear that Google probably intended the 4.2/4.2.1 JOP40(X) builds to be the test builds that they used to gauge the major problems. Now that the major issues with those builds are fixed, 4.2.2 is their "mass rollout" build that they're releasing to absolutely everything.
I think this is actually smart on Google's part, given that Verizon requires testing and approval of all updates to phones they sell.
Also, within that parameter, 4.2.2/JDQ39 hit GSM Galaxy Nexus models on February 12. We on Verizon got the official OTA rollout beginning March 19. That's a little over a month. That's the fastest update the VZW Galaxy Nexus has ever received.
Discuss.
i think its a little of both.
verizon does slow down the update process, but google is the one that releases the update itself.
Good thoughts. I also think it is likely that Verizon started testing and rejected those builds. 4.2 and 4.2.1 had some serious issues and I'm sure big red didn't want to support them.
A buddy of mine from high school works for Verizon corporate. I've asked him why VzW always seems to lag on updates. A lot of it comes down to VzW: It's not that Google never sent the updates to VzW, it's that VzW tests everything and what they don't like doesn't get pushed out to VzW customers.
Makes since to me, but I think Vzw miss handled the public relations aspects of it. I'm mean with all those jelly bean builds being released. They could've let their customers know that they're not interested in those builds but will update our phones with a build that meets their standards
I for one was ready you shout heresy at the top of my lungs, but then I saw it was written by Oldblue and had to give it a chance. I'm halfway convinced. Another peculiarity is the build numbers of late - in the past, each AOSP device typically had a slightly different build number (IMM76K, D, Q, JRO03C, R, O) due to small changes made to the final build for each unique piece of hardware. With 4.1.2 the build was JZO54K across all AOSP platforms, which continued with JOP40C,D and JDQ39. Something has changed in the build process to make Android more universal, and in the case of JDQ39 made it through Verizon testing in record time.
Now, do I believe that Google didn't send 4.2 or 4.2.1 to Verizon? Not sure, but it's worth pondering in absence of knowing what internal conversations occurred.
Sent from my Xoom using xda premium
It just wasn't a good idea for Verizon to take on the nexus. Nexus devices shouldn't be controlled by a carrier at all. Carrier's don't want to deal with the problems that the nexus devices bring.
Google doesn't release perfect builds to the nexus because that isn't the purpose of nexus phones. In order to be on the cutting edge of android development you have to deal with some things not working perfectly. I think everyone can agree that 4.2 and 4.2.1 had some pretty significant issues and Verizon customer support may not know what to do if a customer calls in needing help with something not working.
Winesnob said:
I for one was ready you shout heresy at the top of my lungs, but then I saw it was written by Oldblue and had to give it a chance. I'm halfway convinced. Another peculiarity is the build numbers of late - in the past, each AOSP device typically had a slightly different build number (IMM76K, D, Q, JRO03C, R, O) due to small changes made to the final build for each unique piece of hardware. With 4.1.2 the build was JZO54K across all AOSP platforms, which continued with JOP40C,D and JDQ39. Something has changed in the build process to make Android more universal, and in the case of JDQ39 made it through Verizon testing in record time.
Now, do I believe that Google didn't send 4.2 or 4.2.1 to Verizon? Not sure, but it's worth pondering in absence of knowing what internal conversations occurred.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Well there were past examples of all platforms having the same build number. All Galaxy Nexus devices launched with 4.0.1/ITL41D and 4.0.2 was ICL53F across the board.
On the Xoom, the Wi-Fi and Verizon models shared build numbers sometimes.
For the Nexus S, all variants ran 2.3.4/GRJ22. All except Sprint ran 2.3.6/GRK39F. Also, the Nexus One's Gingerbread builds always matched the GSM Nexus S variants...GRI40, GRJ22 and GRK39F.
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
Well there were past examples of all platforms having the same build number. All Galaxy Nexus devices launched with 4.0.1/ITL41D and 4.0.2 was ICL53F across the board.
On the Xoom, the Wi-Fi and Verizon models shared build numbers sometimes.
For the Nexus S, all variants ran 2.3.4/GRJ22. All except Sprint ran 2.3.6/GRK39F. Also, the Nexus One's Gingerbread builds always matched the GSM Nexus S variants...GRI40, GRJ22 and GRK39F.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
True, but the most striking thing to me is that JDQ39 is on the N4,N7,N10, and GNex. Crossing that many platforms with the same AOSP core seems a bit unusual.
Sent from my Xoom using xda premium
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
iLeopard said:
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
Click to expand...
Click to collapse
In the case of the Verizon Galaxy Nexus variant, Verizon's only role is testing of any update. Beyond that, updates for that device come direct from Google. So Google submits the updates to Verizon, Verizon signs off, Google rolls it out. My point was, I don't think step one (Google submitting the update for testing) ever happened for 4.1.2, 4.2, or 4.2.1.
Sent from my Nexus 7 using Tapatalk HD
iLeopard said:
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
Click to expand...
Click to collapse
You are confusing carriers with manufacturers. TouchWiz is Samsung, Motoblur is Motorola, Sense is HTC. Carriers don't request these features, they come from the makers as a branding mark on top of the Android API. Carriers do on frqeuent occasion have the manufacturers presinstall bloatware from which the carrier receives advertising revenue or promotes its own services. The Nexus (despite being on Verizon) is a Google device, does not come with bloatware, and has no manufacturer skin stuck on top of Android. The vast majority of proprietary drivers for Nexus devices are posted on Googles open source pages as they have licensed them for distribution as intact binary files, aiding third party developers in building AOSP for Nexus devices. The Galaxy Nexus software update battle is between Google and Verizon - Verizon doesn't continue developing the platform, they simply test and decide if they are going to push it out. If not, they notify Google with specific issues and move forward from there.
Sent from my Xoom using xda premium
Winesnob said:
You are confusing carriers with manufacturers. TouchWiz is Samsung, Motoblur is Motorola, Sense is HTC. Carriers don't request these features, they come from the makers as a branding mark on top of the Android API. Carriers do on frqeuent occasion have the manufacturers presinstall bloatware from which the carrier receives advertising revenue or promotes its own services. The Nexus (despite being on Verizon) is a Google device, does not come with bloatware, and has no manufacturer skin stuck on top of Android. The vast majority of proprietary drivers for Nexus devices are posted on Googles open source pages as they have licensed them for distribution as intact binary files, aiding third party developers in building AOSP for Nexus devices. The Galaxy Nexus software update battle is between Google and Verizon - Verizon doesn't continue developing the platform, they simply test and decide if they are going to push it out. If not, they notify Google with specific issues and move forward from there.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Right, I did in fact confuse those two. Thank you.
The VZ variant complies with LTE standards though which does imply driver differences between the GSM and CDMA version?
iLeopard said:
Right, I did in fact confuse those two. Thank you.
The VZ variant complies with LTE standards though which does imply driver differences between the GSM and CDMA version?
Click to expand...
Click to collapse
Yes but Google and Samsung control that. The CDMA and LTE drivers for the VZW Galaxy Nexus are available on the AOSP driver page on Google's developer site.
Sent from my Nexus 7 using Tapatalk HD
Didn't the Sprint Galaxy Nexus get more updates though?
Sent from my Galaxy Nexus using xda premium
Yuhfhrh said:
Didn't the Sprint Galaxy Nexus get more updates though?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Toroplus (mysidspr) is maintained by Samsung, and that device bumped from 4.1.1 to 4.2.1. So no, it didn't get more updates and is actually an update behind the Google maintained Galaxy Nexi (takju, takju, mysid)
Sent from my Xoom using xda premium
My curse is that every thing reminds me of South Park, so I immediately thought "What's important right now, is figuring out whose fault this is."
Maybe you're right, but that answer only welcomes more questions. Could be Google thinks of VZW users as helpless children that can't handle the potential bugs present in the newest firmware. Maybe the opposite: Google thinks of VZW users as elitists who only deserve stable updates?. Or maybe they think, "We are VZW/Google, you know those AT&T jokers don't have service in the more rural areas of the country, you'll pay for it and then wait longer for updates. F you." Or maybe, VZW and/or Google were actually genuinely testing the firmware on the VZW LTE device before releasing it. I imagine it takes a while for the can-you-hear-me-now guy to make his rounds.
If anyone is to blame for lagging updates it's people like you who create threads like these. There has been a whacked sense of entitlement going on these past years and it's easier to find someone to blame rather than demonstrate patience. I would wager people are already asking when the next update is coming out. People call and harass Verizon or whoever and then tell the whole internet about how no one at Verizon knows anything or they are giving you conflicting dates. You're not forced to sign a contract with a particular cell phone carrier...are you? Oh and then the update finally comes and people rush to find and post the latest bugs and then call and harass Verizon or google again and ask them when the next update is coming. Has anyone ever called Verizon after an update and thanked them? Hmmm probably not, too busy asking for more and more. Android updates have become like crack for people and it's time to step away from the white mountains and just relax. They are just phones people!! Call your grandmothers instead of checking for updates everyday!
The op shows no sense of entitlement nor is requesting another update. Simply pondering on why various versions of nexus have updated differently. Fact is, to an extent your right, a lot of people are constantly crying for updates, but this thread is not one of those situations.
I, for one, bought a nexus for the purpose of being at the forefront of updates, but I'm not crying for any. As long as googles follows through with the promise of keeping my bought from Google devices up to date with the latest release I'm happy. That's not a sense of entitlement, its called buying a nexus for a specific reason.
Sent from my Nexus 7 using xda premium
hlaalu said:
If anyone is to blame for lagging updates it's people like you who create threads like these. There has been a whacked sense of entitlement going on these past years and it's easier to find someone to blame rather than demonstrate patience. I would wager people are already asking when the next update is coming out. People call and harass Verizon or whoever and then tell the whole internet about how no one at Verizon knows anything or they are giving you conflicting dates. You're not forced to sign a contract with a particular cell phone carrier...are you? Oh and then the update finally comes and people rush to find and post the latest bugs and then call and harass Verizon or google again and ask them when the next update is coming. Has anyone ever called Verizon after an update and thanked them? Hmmm probably not, too busy asking for more and more. Android updates have become like crack for people and it's time to step away from the white mountains and just relax. They are just phones people!! Call your grandmothers instead of checking for updates everyday!
Click to expand...
Click to collapse
Seriously? Wow. I never EVER hinted at a sense of entitlement. I agree with you that there is definitely a lot of that in this community, but that was not the point of this thread. If you look at any of the work I do around here, my entire purpose on XDA is to catalog stock OTA updates for Nexus devices and help the community with reverting to stock if necessary. Thus, a thread like this would be logical for me to start as this topic is basically at the crux of what I do here.
I should tell you, sir, to go back under your rock and stay there.