Develop Bugs

An news on 4.0.4 upgrade for gsm

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

[Q] Why is the Galaxy Nexus the red headed stepchild?

I saw one commercial around original launch time for the galaxy nexus, and honestly it pushed Google+ harder than the hardware itself. I have not seen any unlocked galaxy nexus commercials in the US. I like having the exclusive phone and all, but this seems a bit ridiculous. There is no reason the galaxy nexus couldn't have way outperformed the note in sales. I still get asked all the time when I pay with google wallet, "Is that an iPhone?". No. "Oh, is that a droid?" No! Its cute to know there are so many ignorant people out there at first. However, it tends to get irritating that google spends so much time and so many resources on ICS to make it the beautiful experience that it is and then just watches the nexus line flop hopelessly on the floor while the cumbersome touchwiz and bloated sense dominate the market.
Can someone please explain to me why Google and Samsung insist on wasting all this time and all these resources on building such a great product to only slide it into a bookshelf to collect dust as it were?

Samsung has bigger fish to fry (SGII and probably the SGIII) which due to crapware probably make more money from these phones, and Google advertises on their own sites but wouldn't make a lot of sense for them to push a phone that they probably only make little profit off of.
Enjoy the fact that you have a phone that will get JB before basically anyone else, that you have stock android, and that you have one of the greatest dev community's of all time. OF ALL TIME!
Also, go into a Verizon store, you wouldn't even think that they sold a GNexus where I live (Pittsburgh, PA), Multiple Motorola/HTC shrines while the GNexus sits right next to the Bionic in the corner of forgotten phones.

I honestly don't know and I can't tell you. There's two things Google sucks at terribly: marketing and support.
Microsoft is in a similar boat. It doesn't matter how much either company innovates, they are incapable of letting people know their products exist and they fall to the wayside.
I loved Windows Media Centre when it first came out. But version after version of it has come and gone and little features have been added. I eventually switched to XBMC. Why? Because no one knows what Windows Media Centre is. Microsoft isn't wasting time on it for the few guys with TV tuners.
Take the above example and substitute almost all Google products in there. Wave, Buzz, even Google Docs. I use it all the time and it's a great product, but people see it and have no clue it exists. For that matter I doubt they even know you can use Microsoft's web based Word with SkyDrive.
The tech companies seem to be in this funk where they compete against each other for features, but forget to inform the public that they're even offering the services they launch. It's no wonder that Apple is dominating, look at how much more they spend on campaigns. iPod ads plastered all over buildings... even seniors know the word iPod even if they don't know what it is.
All Google needs to do to take over the world is hire people from Apple's marketing team. Make something viral. The last time they had that was with the Google search engine itself and Gmail. G+ while it's nice, only boomed with the intake of new tech heads. Sign-ups died right after because no consumers know it exists and Google has failed to tell them why it's any better than Facebook.
Here in my city, the Galaxy Nexus is actually kind of popular, but that's only because Bell and Virgin put out big billboards for it's launch. I say kind of, because those billboards are gone now that the launch is over. Bet you there's still a huge iPhone 4s sign in all of those stores though.

http://forum.xda-developers.com/showthread.php?t=1382163

WiredPirate said:
http://forum.xda-developers.com/showthread.php?t=1382163
Click to expand...
Click to collapse
Wow really? This isn't a phone tech question but rather a topic of discussion.

spencer88 said:
Wow really? This isn't a phone tech question but rather a topic of discussion.
Click to expand...
Click to collapse
Not a question? lmao
[Q] Why is the Galaxy Nexus the red headed stepchild?
Click to expand...
Click to collapse

By the tone of your post I think you are comparing your phone to a soulless bastard ginger.
I on the other hand I compare mine to that sleek sexy read head with an attitude and a desire to get dirty.

geez, how many more of these kinds of posts are we going to see?

Here... now everyone can feel better and we can go about our day.

WiredPirate said:
http://forum.xda-developers.com/showthread.php?t=1382163
Click to expand...
Click to collapse
It says "!!ALL QUESTIONS GO IN THE Q&A FORUM!!", that's pretty clear.

Was this same bull**** present for the Nexus S and Nexus One?
Because I didn't see much for advertisement with them either.
Not that I care-- I don't purchase or put value on my purchases by how much they are marketed or known.
That said, I don't flaunt my phone around to a bunch of looky-lous for attention either.

adrynalyne said:
Was this same bull**** present for the Nexus S and Nexus One?
Because I didn't see much for advertisement with them either.
Not that I care-- I don't purchase or put value on my purchases by how much they are marketed or known.
That said, I don't flaunt my phone around to a bunch of looky-lous for attention either.
Click to expand...
Click to collapse
The Nexus One was considered a flop by the industry. I personally was fully behind Google selling fully unlocked phones. I think if they could have gotten the price a bit less inflated and marketed it properly, the Nexus line could be more than it is now. I just don't think Google is that interested in selling phones. It's about the money and that comes from the licencing they get from other manufacturers.

thequinox said:
The Nexus One was considered a flop by the industry. I personally was fully behind Google selling fully unlocked phones. I think if they could have gotten the price a bit less inflated and marketed it properly, the Nexus line could be more than it is now. I just don't think Google is that interested in selling phones. It's about the money and that comes from the licencing they get from other manufacturers.
Click to expand...
Click to collapse
I wasn't aware that Google licensed Android to OEM's. Pretty sure it's free because it's under the GPL.

No it is not under the GPL. Most of it is Apache licensed, with a few things under GPL. There are also closed source portions. Some things do have to be licensed to OEMs. Otherwise, they would never legally be able to offer google apps on their devices ootb, be able to sync with Google Calendar, and several other things.

adrynalyne said:
No it is not under the GPL. Most of it is Apache licensed, with a few things under GPL. There are also closed source portions. Some things do have to be licensed to OEMs. Otherwise, they would never legally be able to offer google apps on their devices ootb, be able to sync with Google Calendar, and several other things.
Click to expand...
Click to collapse
Ahh I forgot about the proprietary Google Apps. Makes sense.

thequinox said:
The Nexus One was considered a flop by the industry. I personally was fully behind Google selling fully unlocked phones. I think if they could have gotten the price a bit less inflated and marketed it properly, the Nexus line could be more than it is now. I just don't think Google is that interested in selling phones. It's about the money and that comes from the licencing they get from other manufacturers.
Click to expand...
Click to collapse
It's a reference phone. That's all that is. This reference phone has two purposes:
1) Flagship device: "beta" test the next Android update with newer hardware.
2) Reference... its a prototype to suggest what the minimum hardware should be.
Nexus One set the standard for all future phones to have a 1GHz CPU.
I agree with adrynalyne. The Galaxy Nexus has a great developer community and support with great ROMs/kernels. I can really care less if the Galaxy Nexus isn't as popular as a iPhone or Galaxy S series. Just know that the Galaxy Nexus is a flagship device and will get Android 5.0 before any other phones get it (with the exception of the next "Nexus" flagship)

regarding delayed updates

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.

Canadian GNex owners: How to Complain

Hello to Canadian Galaxy Nexus owners. If, like me, you are angry at the lack of response from Google or Samsung as to when our yakjuux firmware phones are going to be updated, here's where to complain:
Competition Bureau of Canada (I'm too new to post a link, apparently, but you can google it.)
They have a toll free number in "Contact Us". You'll talk to a real person.
This agency is responsible for investigating claims of false advertising in Canada. I have lodged a complaint against both Google and Samsung over the false claims that the phone I bought was a "Pure Google Experience" phone which would receive operating system updates in a timely fashion due to lack of carrier or manufacturer customization. I suggest you do the same, as the more complaints on an issue they receive, the higher profile the problem becomes for them. I don't know if it will help, but if you would like to reference my file number (R608849), feel free.
Individually, Google has been ignoring us for months. Perhaps the Canadian Government will have better luck.
Enjoy,
Fox

considering google doesnt publish the update directly to yakjuux, you cant really be angry at google.
point the finger at samsung.

Just change your phone to yakju and you won't have to complain. I did that months ago and have always been happy. The process was easy and very well documented on this site.
My co-worker stayed on yakjuux until this week. I was always getting updates that he wasn't.

It is okay to complain if you know you will get positive results. But in this case, it will just be a waste of time because there is no legal definition of "timely".
Just flash the phone to yakju.
Sent from my Galaxy Nexus using xda app-developers app

I don't really recall any concrete specific promises that would hold up as "false advertising", but it's been a while since I saw the ads so I don't really remember. The definitions of "timely updates" and "pure Google experience" are probably not set in stone and could be argued by either side for whatever strengthens their argument.
It sucks that yakjuux isn't getting updated, but I have a feeling most people on a developer-oriented site such as XDA would probably just spend a few minutes converting their phone to yakju/takju and be done with it rather than go on a crusade trying to get the government involved. Just saying...

I am fully aware that I can flash my phone to yakju, but I've had several friends buy this phone on my recommendation who won't do such a thing. They'll be stuck with the random reboots, low volume, etc, and I want to help them out too. Again, in this thread, people have repeated the line that Google doesn't publish the update for yakjuux phone, but I have yet to see a source from Google for that claim. The only official statement I've seen is Samsung claiming that it DOES come straight from Google. (Yes, I know that Samsung could be wrong/lying about this, but until I see an official word from Google that contradicts it, it's the only thing close to an official story I have.)
Anyway, it's the principle of the thing, now. I want them to give us what we were all led to believe we would get from this phone.

Not even 'could be' lying. ARE lying.

I think the problem here is with samsung, Google was not even aware of the regional variants when the phones started to roll out. Secondly, I don't think going to the BBB or any other method of escalation is going to do anything. The phones in Canada are not marketed as being updated by Google, nor is there any statement regarding the guaranteed updating of the phone.
Regardless of the marketing, the Nexus line of phones is not for novice phone users who want a seamless experience, for those people, i tend to recommend the Galaxy 2/3 line of phones and/or the iPhone as it suites their needs better.
End recommendation: if you can't be bothered to flash a rom, you should not have gotten a Nexus in the first place. If they still insist on getting the Nexus, it takes 1 minute to flash stock yakju to a phone, do it for them - or have them order it through the play store.
Edit: Just for you FoxHoleAtheist - I posted this a while back.
http://forum.xda-developers.com/showpost.php?p=25535165&postcount=461

Matridom said:
I think the problem here is with samsung, Google was not even aware of the regional variants when the phones started to roll out. Secondly, I don't think going to the BBB or any other method of escalation is going to do anything. The phones in Canada are not marketed as being updated by Google, nor is there any statement regarding the guaranteed updating of the phone.
Regardless of the marketing, the Nexus line of phones is not for novice phone users who want a seamless experience, for those people, i tend to recommend the Galaxy 2/3 line of phones and/or the iPhone as it suites their needs better.
End recommendation: if you can't be bothered to flash a rom, you should not have gotten a Nexus in the first place. If they still insist on getting the Nexus, it takes 1 minute to flash stock yakju to a phone, do it for them - or have them order it through the play store.
Edit: Just for you FoxHoleAtheist - I posted this a while back.
http://forum.xda-developers.com/showpost.php?p=25535165&postcount=461
Click to expand...
Click to collapse
I completely disagree. The Nexus isn't intended as a developer's-only phone.. it's marketed to anyone and everyone who wants a pure google phone. Those regular users who buy them shouldn't be forced to A) search out relatively obscure tutorials on message boards and B) void their warranty to get the updates their phones need to work properly.

FoxholeAtheist said:
Again, in this thread, people have repeated the line that Google doesn't publish the update for yakjuux phone, but I have yet to see a source from Google for that claim.
Click to expand...
Click to collapse
From JBQ himself:
https://groups.google.com/forum/?fromgroups#!topic/android-building/kMhE-Orl5Kk
Can you quote the Samsung source saying the other variants do get updates from Google? (I'm not questioning you here at all, I just haven't seen that and would like to be fully informed on the topic). The Samsung updates are served from Google servers, but as far as I know Samsung prepares the update for Google to host.
FoxholeAtheist said:
A) search out relatively obscure tutorials on message boards
Click to expand...
Click to collapse
Though I can certainly understand less technical people not wanting to do it, or even knowing where to look for instructions, efrant has a great guide: http://forum.xda-developers.com/showthread.php?t=1626895 ... just in case you ever want to point someone to a proper howto.
and B) void their warranty to get the updates their phones need to work properly.
Click to expand...
Click to collapse
I don't know if it actually voids the warranty. Even if it does, you can 100% restore the phone to the stock state so they can never tell. And to my knowledge back to the Nexus One days, no Nexus phone has ever been refused warranty if it was an actual hardware problem that wasn't caused by software.
Sorry, this is getting off the original topic... just wanted to provide some info.

If you are not willing to fix it yourself then file a complaint against Samsung.
Most people complain through the wrong channels or just don't complain because they don't know who will listen and can actually do anything about it.
Thanks for posting the info.

FoxholeAtheist said:
I completely disagree. The Nexus isn't intended as a developer's-only phone.. it's marketed to anyone and everyone who wants a pure google phone. Those regular users who buy them shouldn't be forced to A) search out relatively obscure tutorials on message boards and B) void their warranty to get the updates their phones need to work properly.
Click to expand...
Click to collapse
I never said it was a developers phone. I stated it was not for novices. this phone is on the bleeding edge of android, it's expected to have issues.

Ya I didn't wait or bother, I just unlocked and rooted and be done with being a slave to anyone when my phone gets updated. Never looked back.

FoxholeAtheist said:
Hello to Canadian Galaxy Nexus owners. If, like me, you are angry at the lack of response from Google or Samsung as to when our yakjuux firmware phones are going to be updated, here's where to complain:
Competition Bureau of Canada (I'm too new to post a link, apparently, but you can google it.)
They have a toll free number in "Contact Us". You'll talk to a real person.
This agency is responsible for investigating claims of false advertising in Canada. I have lodged a complaint against both Google and Samsung over the false claims that the phone I bought was a "Pure Google Experience" phone which would receive operating system updates in a timely fashion due to lack of carrier or manufacturer customization. I suggest you do the same, as the more complaints on an issue they receive, the higher profile the problem becomes for them. I don't know if it will help, but if you would like to reference my file number (R608849), feel free.
Individually, Google has been ignoring us for months. Perhaps the Canadian Government will have better luck.
Enjoy,
Fox
Click to expand...
Click to collapse
I know how you feel I have the Nexus S was suppose to get the 4.0 first after Gnex and that didn't happend. Just asking like that in a friendly way. But could Google or Samsung be mad at you cause you modified their device and their rom ?
I'm not pretty sure but I'm pretty sure somewhere there's a word or 2 about not modifying anything of Samsung or Google. Just saying don't want any problem or start a fight
Goes both ways I guess. No offense

Canadian here, but dont care. I'd rather flash my own firmwares.

Although I agree with you FoxholeAtheist, I don't think a forum like xda-developers is the right place to champion your cause, as most of the folks here will have the same response that speedyink just posted above. Maybe go to the Rogers/Bell/Telus forums and post it there. Just sayin'.

I could have swore that Google marketed the nexus line as a developer phone since its conception. I don't see you getting much support for your cause on a forum for developers. Most here have flashed their ROM and moved on.

They marketed the Nexus One as such, and never again. People just ASSumed. It is a consumer device with development abilities.

FoxholeAtheist;28719966If said:
You have no grounds to complain. Nobody is obligated to give time lines for updates. Doing so, and missing the date, means a huge backlash for the company... it's not the risk for them to do that.
As others have suggested. Just flash updates yourself. I'm Canadian and have been running Jellybean since it was first available.
Click to expand...
Click to collapse

You have no right to complain, nor will the Competition Bureau do anything about it.
The Nexus is marketed as a Pure Google phone. This much you are correct about... However 4.0.2 ICS is still a "pure google experience". They never made any guarantees as to when you'd be receiving updates, if you receive them at all. This is all based on what you believe they should do, not what they told you they would do.
Beyond this, flashing to Yakju/Takju is as easy as pie if you follow efrants thread... you don't even have to flash the regional radio... you can keep it completely 100% stock "Pure Google/Updated by Google" experience like I did and be happy.
Your efforts in complaining will be fruitless. The competition bureau will not investigate this claim based on what you believe, they will look at what you were told, which was basically nothing.

Is Google to Blame for VZW Galaxy Nexus Updates Falling Behind?

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.