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.
Related
Disturbing news from the official Android developer website: it appears that nearly all reference to CDMA phones and tablets has disappeared from the official documentation. This includes Android source code and factory ROMs for Verizon’s CDMA version of the Galaxy Nexus and Motorola XOOM, as well as the Nexus S 4G. What this implies (and only implies) is that Google is no longer providing official updates for the removed devices, as is generally expected of “developer” hardware. The GSM Nexus S and WiFi-only Motorola XOOM are still present, as are the two initial images for the Galaxy Nexus CDMA/LTE, though these are marked as “archived, for reference only”.
Click to expand...
Click to collapse
It looks like this will put a huge dent in development for CDMA phones, including my shiny new Galaxy Nexus. What's the deal? Is this as big a blow as it looks like?
What it means is that Google will no longer provide AOSP code and documentation for the Verizon Galaxy Nexus in the way they do for the GSM Galaxy Nexus.
From Google's point of view, it makes sense since nothing they have provided allows one to build a working firmware for the Verizon Galaxy Nexus phone (due to the missing radio interface libraries that Google couldn't get permission from Verizon to redistribute) so instead of pretending that the Verizon Galaxy Nexus is an AOSP reference device they have decided to drop the developer support for it.
What people should be doing is lobbying Verizon (and others) to change their policy/rules and to allow Google to redistribute the CDMA radio libraries under the same "you get to use these but you cant modify or redistribute them" license that they use for the GSM radio libraries.
My understanding is that it won't have any impact on Google's development for the phone - that all updates will be pushed out for this Nexus device just as quickly as any others. Of course, we'll have to wait and see. Google's clarification that was posted shortly after the news broke - was that since the radio IS different and contains non-open source elements, that per their definitions it was no longer being listed a "developer device". A handful of other devices were also re-classified.
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.
Multi touch bug ftl and slow multitasking.
Was really hoping Google would solve these problems earler
Sent from my Galaxy Nexus using XDA App
hurricurry said:
Multi touch bug ftl and slow multitasking.
Was really hoping Google would solve these problems earler
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Multi touch bug is a complete killer. Really can't wait for 4.0.4 AOSP hopefully soon
The news is that not everyone is on 4.0.2 yet. If you can't wait then grab a custom rom, otherwise a whole lot of patience may be necessary.
virtualcertainty said:
The news is that not everyone is on 4.0.2 yet. If you can't wait then grab a custom rom, otherwise a whole lot of patience may be necessary.
Click to expand...
Click to collapse
Totally true.
Google is not really considering Galaxy Nexus a Nexus device it seems. Some other systems have gotten newer version of Android already.
At least my Galaxy Nexus runs bloatware-free official Android, even if the build is totally outdated by now. The only real benefit of having a Galaxy Nexus it seems.
Well, I actually don't think it is all that bad. The oldest ISC version out there is still only around 3 months old and better than 99% of Android's entire installation base.
The fact that a few manufacturers jumped on AOSP so soon is great and I'm happy for those users. I don't see the need to be 'first' and it doesn't sour my experience any. Google obviously thought the GN would re-fork with 4.0.3 by now but sometimes bugs get in the way of developer's best intentions.
virtualcertainty said:
Well, I actually don't think it is all that bad. The oldest ISC version out there is still only around 3 months old and better than 99% of Android's entire installation base.
The fact that a few manufacturers jumped on AOSP so soon is great and I'm happy for those users. I don't see the need to be 'first' and it doesn't sour my experience any. Google obviously thought the GN would re-fork with 4.0.3 by now but sometimes bugs get in the way of developer's best intentions.
Click to expand...
Click to collapse
Well yeah, but the things that annoy me are the bugs that are present in 4.0.2 and have been fixed in 4.0.4. And not only that, but also the API features of 4.0.3+ that was supposed to be the 'base' version of Android 4.0.
I don't mind how long major releases would take, but this is a small incremental update. I am just surprised that it takes so long to serve it to 'Google phone'.
kristovaher said:
Totally true.
Google is not really considering Galaxy Nexus a Nexus device it seems. Some other systems have gotten newer version of Android already.
At least my Galaxy Nexus runs bloatware-free official Android, even if the build is totally outdated by now. The only real benefit of having a Galaxy Nexus it seems.
Click to expand...
Click to collapse
Newer versions such as what? The latest aosp is 4.0.3 and not 4.0.4. It's quite obvious that 4.0.4 is not ready.
The Galaxy nexus is a Google supported device and is a nexus.
Sent from my Galaxy Nexus using xda premium
Well, if you look from it from the other side. Google might actually spare us from the still-bugged 4.0.3 version wich is AOSP. Also, JBQ already confirmed that the 4.0.4 version contained a "nasty bug" and wasn't ready for release.
If you look at it that way, new devices with 4.0.3 is still bugged in a way. And Google wants to keep those versions away from their current Nexus.
Just my way of being patient
Oddly enough, some of the tablets shown at MWC (on 4.0.3) had multi touch issues. This brings in a whole new strand of questions...
Sent from my Galaxy Nexus using xda premium
In regards to the latest os .... can anyone tell me what phone has ics update already???? And I've said phone ohh and it has to be released now announced
Sent from my Galaxy Nexus using xda premium
hurricurry said:
Multi touch bug ftl and slow multitasking.
Was really hoping Google would solve these problems earler
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I was really hoping people would stop *****ing about OTAs.
Sorry, but you all sound like a bunch of whiney kids. You'll never be satisfied because the OTAs will never be quick enough to satisfy people. Google is not going to give you nightly builds of ICS. So just calm down and wait for it to be finished and pushed out.
martonikaj said:
I was really hoping people would stop *****ing about OTAs.
Sorry, but you all sound like a bunch of whiney kids. You'll never be satisfied because the OTAs will never be quick enough to satisfy people. Google is not going to give you nightly builds of ICS. So just calm down and wait for it to be finished and pushed out.
Click to expand...
Click to collapse
You just love calling everyone whiney kids don't you?
People are pissed because we have a Nexus that for the first time, is NOT leading the way in terms of OS version. We are pissed because of the overwhelming silence from Google.
It would take them 15 minutes to post a blog on where things are at.
Scottatron said:
You just love calling everyone whiney kids don't you?
People are pissed because we have a Nexus that for the first time, is NOT leading the way in terms of OS version.
Click to expand...
Click to collapse
Yes I do. And people deserve to be given some perspective.
What do you mean? ~1% of Android devices have ICS. How is that not leading the way in terms of OS version when we're the only phone with it? Nothing has a higher OS (and don't say "omg the NS has 4.0.3!"). The Galaxy Nexus launched Android 4.
Why are you crying about not having 4.0.3/4.0.4 over 4.0.2. If its not ready, its not ready. That's why we don't have it officially yet. For all you know Google is holding off till 4.0.5, 4.0.6, or 4.1... no one knows.
Like your phone for what it is. You're like a dog chasing his tail when you get something great and always look for the next best thing. You'll spend your entire time with the device wanting more, and you'll never enjoy what you have.
Like I said in the other thread: OTA's will never come fast enough for people. If Google started pushing one every month (regardless of how what it did or didn't include/fix), it still wouldn't be fast enough because people would prefer it was 3 weeks instead, then 2 weeks, then 1 week, then nightlies. And guess what? Google isn't going to do nightly OTAs of ICS (not even close!). If you want nightlies, go build a ROM from CM source and change things for yourself. Or better yet, build straight from AOSP source and fix the bugs yourself. Make a thread for it and let people ***** at you for not fixing them faster.
maybe this is why apple is having better success in the mobile world then google and all the others.
while all i have is an old ipod touch from apple, and have GN and ACER tablet, the fact is that google ANNOUNCED 4.0.3 as THE LASTEST STABLE release, however, even on the official supported hardware i still have 4.0.2
this is why i personally compare android to the old windows mobile system.
on the old windows mobile system, if you wanted to upgrade to the latest, you had to hack the device and upgrade yourself, and even then not all devices could be upgraded to all OSs. when i talk to people about android, i still find mayself telling them that even on the official hardware you need to hack the device to get the official upgrade.
if google and all the open source will learn a little from old mistake they will build a better test environments and stop calling any buggy version an official release, or make sure that all devices be able to get the latest version when it is announced (ipod/iphone 3rd gen can still be updated to ios5 even if it can barely work with it) .
the simple fact is, the android is repeating all of the mistakes that even microsoft with WP7 have learned, and am not showing even the slightest inclinations to make a change to this inadequate system of multiversioning....
PCHelper said:
maybe this is why apple is having better success in the mobile world then google and all the others.
while all i have is an old ipod touch from apple, and have GN and ACER tablet, the fact is that google ANNOUNCED 4.0.3 as THE LASTEST STABLE release, however, even on the official supported hardware i still have 4.0.2
this is why i personally compare android to the old windows mobile system.
on the old windows mobile system, if you wanted to upgrade to the latest, you had to hack the device and upgrade yourself, and even then not all devices could be upgraded to all OSs. when i talk to people about android, i still find mayself telling them that even on the official hardware you need to hack the device to get the official upgrade.
if google and all the open source will learn a little from old mistake they will build a better test environments and stop calling any buggy version an official release, or make sure that all devices be able to get the latest version when it is announced (ipod/iphone 3rd gen can still be updated to ios5 even if it can barely work with it) .
the simple fact is, the android is repeating all of the mistakes that even microsoft with WP7 have learned, and am not showing even the slightest inclinations to make a change to this inadequate system of multiversioning....
Click to expand...
Click to collapse
I'll tend to agree with most of what you said.... Apple has this down to a T with releasing OS versions. Everyone with the previous 2 versions of the hardware is completely guaranteed to get the update the day that it comes out. Models 3 years ago may or may not get a full update, but they'll at least get a partial update (with some features pulled). You know what you're getting and you know when you're getting it. You'll never be in limbo. When Apple announces a new iOS version, they explicitly say which models will get it. The consistency is good.
WP7 is a bit better analogy of what Android has to strive for IMO. Android covers tons of carriers, devices, etc. but still needs to be able to handle pushing OTAs to everyone in a timely matter. This is a huge logistical hurdle for MS (or Google) to try jump. MS is handling it by putting very strict guidelines on what hardware can be used and what you can/can't do to the software (which is pretty much nothing). This makes the OTA process a 1000 times easier for MS to implement. What it leads to is basically knowing that the OTA update will work on all of these different devices because they're about 90% identical in hardware, and 99% identical in software. The only hurdle for them is pretty much getting carriers to accept the terms of pushing the OTA.
While Google could implement a system like this, it'd be at least a year out. Because in order for this MS-style system to work, Android would have to have specific hardware and software guidelines. The problem being that Android is open source and free, and manufacturers can really do whatever they want. They only have to follow some very relaxed "guidelines" to get GAPPS. Even if Google wanted to push OTAs to all of these phones in their current state they couldn't. Google doesn't hold the code from Samsung, HTC, LG, Huawei, and others because they're each doing it in house. There is no unifying OTA that can be pushed. Ultimately Google has no say in what happens after they certify it for GAPPS support. At that point, its between the manufacturers and carriers what is going to happen.
Google needs to start hitting manufacturers where they can, with GAPPS. Its the only closed-source part of Android and its a really really important one. They need to start forcing UI guidelines and skinning policies that let OTAs flow smoother. On the carrier side, they need to start pushing carriers to allow manufacturers to push them when its ready. Google can only do so much to carriers though. At that point they can threaten, but again its not up to Google what happens with those devices once the licenses go out. Its not a Google sale to the carrier, its a manufacturer sale. Until every phone Google sells is a Nexus, they won't be able to tell carriers what to do. Although the market share is huge for Android, it doesn't have the same unified push to bully carriers like Apple has.
....but I've got a couple other points as well on your post. You're making it sound like the Galaxy Nexus is running 4.0.2, and the rest of devices are running/being sold with 4.0.3 (the "stable" build). This is not the case. Whether its running the most "stable" build or not, the GNex is the most up to date of all Android phones out there right now. And we'll be getting stock 4.0.3 before anyone, and all of those phones being sold from this point w/ 4.0.3 will have skins attached as well.
martonikaj said:
the GNex is the most up to date of all Android phones out there right now. And we'll be getting stock 4.0.3 before anyone
Click to expand...
Click to collapse
Why doesn't the Nexus S factor into your argument?
Evangelion01 said:
Why doesn't the Nexus S factor into your argument?
Click to expand...
Click to collapse
First off, the Nexus S update has yet to be pushed to everyone. Its still halted because of bugs (and the NS4G doesn't have it officially, either). Second, simply because it's 4.0.3 doesn't mean that it's "better" than 4.0.2 on the Galaxy Nexus. For all intents and purposes, it's the same update... look at the NS4G and NS on Gingerbread. One was on 2.3.5, the other on 2.3.7... doesn't mean one was better than the other, but simply the NS4G needed specific build # because its a different device.
If you're splitting hairs of 4.0.3 vs. 4.0.2 to try and win this argument, it's not going to work.
now here is where we can start the argument... 4.0.3 is better then 4.0.2 if only due to the codex hardware fix.
But that is not the question. The issue is it was officially released as latest stable, however only after official release somehow all of a sudden the official Google phones are full of bugs and it is not good for them. If it is not developed and tested on the official hardware, then why put the official stamp on everything? Where is Google QA? Why buy Google official devices if we cannot even get the minimum we expect from the name? Pay attention, I am not talking about vendor devices, only on official stamped device/software....
Sent from my Galaxy Nexus using xda premium
Scottatron said:
You just love calling everyone whiney kids don't you?
People are pissed because we have a Nexus that for the first time, is NOT leading the way in terms of OS version. We are pissed because of the overwhelming silence from Google.
It would take them 15 minutes to post a blog on where things are at.
Click to expand...
Click to collapse
+1
Couldn't have put it better myself. Google really needs to pull its **** together and give us some of that 4.0.4 goodness!
Thank god for unlockable bootloaders and XDA devs, huh. Oh, wait......
From my point of view (and mine only) I knew the nexus would have an unlockable boot loader, I knew there would be a root exploit before I even brought the device and I knew the devs here would provide better then Google themselves, that's why I personally, brought the phone. Fortunately you didn't choose HTC. The delays are longer and the devices more secure. What I'm trying to say is, make the most the the nexus and this community and get a custom ROM or makesure you choose devices in the future for the right reasons. Let's face it, very few of us brought it for the specs....
Sent from my Galaxy Nexus using XDA App
sorry if this has been posted, though it was interesting.
pretty sure this has what everyone has been saying, though id share
Despite the Nexus name or "Google experience" branding, carriers are inevitably involved on some level when a device is officially sold or supported by them. And, according to Queru's remarks, it's the carriers creating the delays in getting upgrades pushed out to certain models of Google's flagship devices.
Click to expand...
Click to collapse
Source: http://blogs.computerworld.com/20088/google_nexus_xoom_ice_cream_sandwich_delays
Yes. We know this.
Nothing new here...just keep moving.
Also, the Xoom.
Sent from my Galaxy Nexus using XDA
Uh... we've known this for several months now.
I am tired and weary of combating all of these claims, when they simply are not true.
What makes a Nexus device? Overall, the Google marketing? team responsible for it names the device. They decide what falls under the Nexus moniker. It is a name, and nothing more. I know a lot of people think it means it is a developer phone. No, it does not mean that. The Nexus Q has the Nexus name, but I really doubt you will be seeing AOSP support for it. Time will tell.
Is the Nexus a developer phone? Sure. Is it marketed or expected to be a phone specifically for developers? No.
In the past, Google has released an ADP, short for Android Developer Phone. There was the ADP1, ADP2, ADP3 (which turned out to be the Nexus One). These phones were not sold at carrier locations, not subsidized, and specifically meant for developers. It was before my time with Android, but I believe the ADP1 (basically an unlocked G1) required you to register with Google as a developer. The ADP2 came out later, and once again Google made it clear it was not meant for non-developers.
The Nexus devices were when Google decided to meld developer and end user devices. The Nexus One was provided unsubsidized from Google for a time, and subsidized through Tmobile. Verizon took a shot at it, but canceled the phone early on in testing. These phones did not require registration as a developer, and were sold in carrier stores.
The Nexus S expanded upon this. It was available to multiple carriers subsidized. Sprint received a model called the Nexus S 4G. It had full AOSP support with the exception of WIMAX (I think). Google had resdistribution licenses for Gingerbread and all was right in the world. Yes, the 4G received updates slower than the plain Nexus S, but it still received them. It was a Nexus device.
Fast forward to today. The Galaxy Nexus has been released as GSM, and CDMA/LTE. Verizon gets updated directly from Google, but does not authorize them for OTA until they meet their 'quality standard'. Then Google throws the switch. Google builds them, through and through. The Verizon model has been the center of controversy for some time because Google was unable to obtain redistrubtion licenses for the proprietary blobs. It still had all of the code needed to build from AOSP though, but without CDMA or LTE. This was because Google could not give us the proprietary files needed to make such things work. Their hands were tied, because it is closed source. So, Google threw their hands up in the air and told the world after they tried to obtain the rights for a while when 4.0.3 came out. Did it change anything? A little. It was made clear that because the licenses could not be obtained, that AOSP would include what it always has for CDMA/LTE, but not the proprietaries for download. In addition, it meant that Google would no longer pay someone to test the CDMA/LTE code in AOSP because they cannot even support a full build due to the licensing issues. This ruling extended to all CDMA devices, even the Nexus S 4G. This has never been an issue with GSM, because Google has a license to redistribute the blobs.
What does this change? Well for one, it is up to us to find our own CDMA/LTE blobs from a rom or phone. By the way, we aren't allowed to do this if you follow the license. We do anyway
It also means if/when we find a bug in the CDMA/LTE AOSP code, we cannot expect Google to fix it. I don't really foresee this becoming an issue, but it could.
Now, back to the original subject. Does it mean the Verizon phone isn't a Nexus? I mean, it has BLOAT (apks and libs for Verizon apps to work as well as Backup Assistant for those coming from feature phones).
No! It is a Nexus. Every device has proprietary blobs. The Verizon model has a couple more. The Sprint model has a few more than that. However, who cares? Do you guys think the yakjuxx variants are not Nexus devices? They get updates even slower than Verizon or Sprint. Nexus devices can exist, even if Google cancels AOSP tomorrow. AOSP does not make a Nexus device. A design and vision that Google oversees makes a Nexus. Thats it.
All devices have open and closed sourced items.
All devices have proprietary blobs.
It doesn't matter that Verizon includes a couple extra items, or decides to test updates longer than Google. As I mentioned before, not everything on ANY Nexus device is open source.
GSM requires proprietary blobs.
CDMA requires proprietary blobs.
A licensing issue does not undo a device from being a Nexus. Neither do delayed carrier updates. If you live in the US and have a subsidized or network locked device, you should expect that the carrier has control over your hardware. There is no other way to put it, but it does not change the overall nature of the device. Not all Nexus updates are coming from Google anymore as well. Yakjuxx variants as well as Sprint's Toroplus model get updates built from Samsung.
Ok, I want to say a lot more, but I will stop here.
A nexus is a nexus, but I didn't like that fact Verizon wanted to **** around with the software causing a standoff between them and Google.
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Gromet said:
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I had 4.1 on my CDMA Toroplus within 24hrs of the announcement. That's why I got a Nexus. Who cares when the carriers are gonna push the OTA?
Gromet said:
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
This. I have the sprint nexus and I'm def getting one off the play store and slapping an att sim in there next time.
Sent from my Galaxy Nexus using xda premium
Gromet said:
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Verizon makes no modifications to anything Google does. Verizon doesn't even develop their own software. They send Google what they want on the device. What you like or dislike does not change the device from being a Nexus.
Moving on...
phatmanxxl said:
A nexus is a nexus, but I didn't like that fact Verizon wanted to **** around with the software causing a standoff between them and Google.
Click to expand...
Click to collapse
What standoff? The one the blogosphere invented? I've seen nothing official from Google confirming any standoff.
I sure see a lot of proprietary apks on the Sprint version. Did you here of any dicking around and standoff between Sprint an Google?
Backup Assistant and an Account Management application are hardly a standoff-ish issue. The software was added in, and does not modify any of the actual base code.
jesusice said:
I had 4.1 on my CDMA Toroplus within 24hrs of the announcement. That's why I got a Nexus. Who cares when the carriers are gonna push the OTA?
Click to expand...
Click to collapse
I beat you by 12 hours or so, but yeah, same deal. Try that with any other non-Nexus device (and have it fully working).
Folks, likes or dislikes have nothing to do with this thread. I have my own issues about how Verizon handles things.
The thread is about the device being a Nexus, not personal feelings.
Why do people treat this kind of crap like it's Religion?
I believe the reason why people think this is because of the sensational headlines "blogs" create to draw clicks. There are a handful of Android specific blogs (which I won't name) that post the most far-fetched of rumors and the "doomsday" headlines with the sole purpose of creating traffic.
People need to draw their own conclusions on things instead of taking what "Joe Bag 'O Donuts" on [insert] tech blog as fact.
live4nyy said:
Why do people treat this kind of crap like it's Religion?
Click to expand...
Click to collapse
More importantly, why do people continue to spread FUD regardless of facts?
Funny how people said we wouldn't see 4.0.4 factory images, wrong. This CDMA nexus bashing is lame and tiresome.
Sent from my Galaxy Nexus using Tapatalk 2
El Daddy said:
I believe the reason why people think this is because of the sensational headlines "blogs" create to draw clicks. There are a handful of Android specific blogs (which I won't name) that post the most far-fetched of rumors and the "doomsday" headlines with the sole purpose of creating traffic.
People need to draw their own conclusions on things instead of taking what "Joe Bag 'O Donuts" on [insert] tech blog as fact.
Click to expand...
Click to collapse
This.
What I wouldn't give to see every blog out there nuked from existence. Do you guys remember the Internet, before blogs existed?
Better days...
---------------
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
delete
jesusice said:
I had 4.1 on my CDMA Toroplus within 24hrs of the announcement. That's why I got a Nexus. Who cares when the carriers are gonna push the OTA?
Click to expand...
Click to collapse
^THIS^
adrynalyne said:
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
Click to expand...
Click to collapse
I hate exclusivity. It's like High School all over again.
adrynalyne said:
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
Click to expand...
Click to collapse
This. Especially when I hear comments like, "Enjoy waiting [x] months for an update." Just because I have a CDMA Nexus doesn't mean I don't have a "true" Nexus. Even various GSM Nexus models are still officially stuck on 4.0.2.
Sent from my Galaxy Nexus using xda premium
Not sure why people are blaming blogs for the fact that the VZW Nexus gets updates months after its unlocked GSM brethren. That's not a made-up problem, it's simply a fact being reported.
adrynalyne said:
-snip-
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
Click to expand...
Click to collapse
Unfortunately, I think you will find this mentality with anything. (gadgets, cars, sports teams, race, etc.) "Mine is the best and everything else sucks!"
---------- Post added at 03:05 PM ---------- Previous post was at 03:04 PM ----------
Cabal_ said:
Not sure why people are blaming blogs for the fact that the VZW Nexus gets updates months after its unlocked GSM brethren. That's not a made-up problem, it's simply a fact being reported.
Click to expand...
Click to collapse
That doesn't mean it's not a Nexus device...
Cabal_ said:
Not sure why people are blaming blogs for the fact that the VZW Nexus gets updates months after its unlocked GSM brethren. That's not a made-up problem, it's simply a fact being reported.
Click to expand...
Click to collapse
How about the sensationalist standoffs? Plenty of wild claims out there.
Are those fact?
Once again, that still does not make it a non-Nexus device.
Here is a fact for ya:
There are still some maguro devices out there on 4.0.1 and 4.0.2. I still call them Nexus devices.