yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gogol:
Oh yeah?

Don't you know that GS II got official ICS 4.0.3 update?

http://phandroid.com/2012/03/12/sam...officially-receiving-android-4-0-updates-now/

http://xdaforums.com/showthread.php?t=1544487

So, it is understandable that Nexus owners are angry because they still on 4.0.2.

And don't say "root your phone and get 4.0.4", that won't do for most people.

Google developers should get their asses and bring back the Nexus update asap!
[Samsung Galaxy Nexus] martonikaj:
No. I don't lol.
[Samsung Galaxy Nexus] chirea.mircea:
Ahh, right 512 megs is quite low, I thought it had like 2 gigs.

This brings another point: why would Google even allow manufacturers to include their own skins anymore? Just require they include Holo and only that. Or heck, at least require them to ship their apps/skins as user apps, so that they can be removed, as currently it's a mess.

You know, the point of criticizing something is so that it can improve. The current Android fragmentation is hardly ideal and there is lots of room for improvement. If nobody would complain nothing would be done at all! People with this mentality (if you don't like it go somewhere else) are the reason why lots of popular stuff is junk and has been so for a while.

No they aren't, this is competition.
[Samsung Galaxy Nexus] OniV2:
As a former owner of a Galaxy S II, I can tell you that the fact that the Galaxy S II's 4.0.3 is ugly as all hell. Touchwiz 4.0 on top of ICS does that to a device. Heck, the new icons in the notification bar for signal strength and wireless have been kept green.

Congrats, Galaxy S II users now have a Galaxy S II that says 'Android 4.0.3' in the 'About Phone' menu. Hurrah!
[Samsung Galaxy Nexus] virtualcertainty:
No, it is really not understandable at all. I'm on 4.0.1, and I'm not a bit angry. I love it. Why such jealousy because someone got something before you? This is what we Android advocates have always wanted - manufacturers grabbing AOSP as soon as possible and getting it out to owners. You may not like hearing it but if you want a buggy, quasi-nightly, not-ready-for-release build then root and use custom rom based on 4.0.3 or 4.0.4. Otherwise be happy that your o/s is newer than 99.5% of the world.

Nobody ever guaranteed that every Nexus will get every update before every other phone. It just always worked out that way. Before now.

Do people only get a Nexus to be smug and brag about being 'first'?
[Samsung Galaxy Nexus] kecinzer:
Yes, of course :).
[Samsung Galaxy Nexus] MS.:
Then you're in the wrong forum Sir, here everyones phone is partitialy faulty or at least miss-behaving :D
[Samsung Galaxy Nexus] rdy2go:
Of course

+1
[Samsung Galaxy Nexus] iPathik:
I have a feeling that we will see an update to 4.0.5 along with the Sprint release of the Galaxy Nexus. Maybe the Sprint Galaxy Nexus will ship with 4.0.5 and we will get it OTA, that's what i am hoping at least
[Samsung Galaxy Nexus] bazzawhite:
I hope you're right but I wouldn't count on it.
[Samsung Galaxy Nexus] adrynalyne:
But...the Nexus is NOT a Nexus anymore!

I guess someone forgot to tell these fine folks that Nexus is about the pure experience, not mad updates weekly.

Silly.

I am on 4.0.3. There is nothing stopping any other GN owner either.

You don't even have to hack your device! No exploit needed at all.
[Samsung Galaxy Nexus] adrynalyne:
Yes it is, when you are in a thread complaining about Android and Android alone.
[Samsung Galaxy Nexus] Sleuth255:
Well, Dev status on LTE GNex isn't pulled. The verbiage has been changed to "archival" to maintain licensing compliance. Qualcomm never granted a distribution license to Google for their baseband drivers since there is no CDMA equivalent to a "SIM Unlocked" phone. On CDMA, distribution licensing is granted solely to the Operators. We also own usage licenses for the baseband software as end users. This is why the GNex AOSP environment includes a script which allows us to pull the drivers off our existing Toro phone and build a perfectly functioning AOSP environment for it.

Google maintains the repos for Toro and Maguro variants and provides full support for each. This is the actual definition of "maintaining dev status" in my book. It all boils down to being able to "repo sync" and obtain the code...

The only difference between Toro and Maguro development is that you actually need a Toro device in hand to initially build a fully functioning AOSP rom. If you don't have one, then bluetooth, GPS, and baseband will not be functional.
[Samsung Galaxy Nexus] adrynalyne:
It is actually more involved than that, but yeah.

Google will no longer test any CDMA code that hits aosp as well. So there may be more surprises down the road.
[Samsung Galaxy Nexus] adrynalyne:
Bah! Where should I go for the happy owners?

(Other than to hell) :D
[Samsung Galaxy Nexus] Sleuth255:
@adrynalyne: I don't want to drive this too far off topic, but do GPS and Bluetooth work on Maguro if you build using the binaries on code.google.com?
[Samsung Galaxy Nexus] adrynalyne:
Yeah I think the only thing that is wonky is nfc. Otherwise the props Google provides are sufficient.
[Samsung Galaxy Nexus] akira02rex:
Can anyone confirm.
[Samsung Galaxy Nexus] sonikot:
The things that I find completely hilarious about this thread are the mention of Apple (srsly who the eff cares what they do). The iphone sucks compared to the Nexus on every level. Especially for the type of people that are on these forums.

None of these issues are gamebreakers (Oh noes my smart phone crashed and I had to pull the battery!!!) and the devs on these forums push out insanely great support, roms and extra features. If it wasn't for them our devices would be mediocre at best and we would sit around and talk about how much we hate google....Oh wait.

I personally don't wait out for google, I wait around for Kang.
[Samsung Galaxy Nexus] biffsmash:
There are loads of bugs on the Nexus, and they all exist, whether users want to kid themselves or not. I very much doubt the custom roms work properly either.

That said, just because the phone has bugs, does not mean it's a crap phone, as every phone has, or has had, bugs. It just does my head in when people try to say there are none!

Multi-touch bug exists, not enough people play games on Nexus it seems to worry about it, but it stops me playing games, and that annoys me. Random Reboots and freezes happen, and pulling my battery is a no go, as I had to stick the back cover on with double sided tape to stop the damn phone creaking!

All that said, an update is needed, and badly, and no custom rom is going to be able to appease people who feel duped by google and all the hype about speedy updates, which don't exist. We can install custom roms on any phone, thats no excuse for buggy software.
[Samsung Galaxy Nexus] rdy2go:
Exactly - how can users trust the whole Android thing when even flagship Google device is not supported sufficiently?
[Samsung Galaxy Nexus] spencer88:
And the Verizon Galaxy Nexus exclusive...the loss of outgoing audio bug, that hit me three times this morning, back to back to back phone calls. It's the worst bug I've ever experienced on a phone. It's unacceptable.
[Samsung Galaxy Nexus] virtualcertainty:
That is where your logic is fundamentally flawed. Google has never ever said, "Buy a Nexus you will get lightning fast speedy updates, and you will always get updates first forever until the end of time!"

This is a community/Internet created urban legend. At least until recently it always worked out that way. That's nice. But the people using this myth to run around angry and yell, "the nexus is not a nexus any more!" didn't know what a Nexus was in the first place. People need to adjust their expectations back to reality.
[Samsung Galaxy Nexus] miketoasty:
Personally, I am just happy that I have stock and ICS. After coming from a Droid 2 and an HTC Thunderbolt, I know how bad OEM overlays can be, and how much they bog the phone down even after week after use. My Galaxy Nexus is the first phone I have owned that I can say I will keep for 2 years. Especially with the community it has, it seems like the devs / most GNexus users don't mind the "Slow" updates, and that it's only a select group that is whining about it.
[Samsung Galaxy Nexus] b4cksl4sh:
Right now the GN is an unreliable pos! No matter if the updates come fast or slow.

Google fooled me once with the N1 and plenty unfixed bugs till today. And they fooled me a second time with the GN.

There won't be a third time for me. The perpetual beta approach might be ok for their web products but is unacceptable for a phone that i must be able to rely on.

Just take a look at at the Android bug tracker or the so called support forum. It's simply ridiculous unless you are a total blindfold Android fanboy.

The smartphones are way too expensive to accept this kind of behaviour.
[Samsung Galaxy Nexus] Simer03:
Seriously....just be happy with your phone! You're on ICS where most of the world is still stuck with Gingerbread, and by the time they get on ics, talks of the J version will be happening and the nexus will get it wayyyy earlier...I can't believe people are freaking out over a minor update when most high end phones don't even have the major one we have had for months

Sent from my Nexus Prime
[Samsung Galaxy Nexus] adrynalyne:
FTFY.

Have you noticed that the multitouch bug people only give certain games as examples? I play Minisquadron, MC2, and a couple others fairly regularly. I have never experienced a problem with any multi-touch issue.

I don't ever get reboots, but then I am careful about what software I run. Can you honestly know for certain its not software you installed? Because stock, no apps installed, does not have reboot and lockup issues.

As for the battery cover, well...mine doesn't creak and its a moot point anyway. No AMOUNT of ICS updates is going to alleviate that.
[Samsung Galaxy Nexus] adrynalyne:
Your goal of a perfect bug free smart phone is unattainable. There is no such thing. Check any support forum for any device.
[Samsung Galaxy Nexus] adrynalyne:
Not only that, but we are the ONLY pure ICS experience.

But they cry....ITS NOT A NEXUS ANYMORE!!!!!!
[Samsung Galaxy Nexus] adrynalyne:
I have not had this bug in well over two months. I take and send out at least 4-5 calls a day. I can tell you did it exist at one point for me, but has not happened since I got my phone replaced. I am not denying its existence, but it may have been a hardware issue with some batches? I am on a rev 10 device now, and while nobody seems to know the difference, this is one bug I can say I have not had since my rev 9 device.
[Samsung Galaxy Nexus] Simer03:
My gf has a Verizon nexus (I've the GSM on T-Mobile) and she has not complained to me at all about her phone! She constantly tells me she loves it...no issues with service, no bugs, no nothing and we live in frickin Minnesota

Sent from my Nexus Prime
[Samsung Galaxy Nexus] adrynalyne:
My wife complains.

Here is her list of complaints about her Gnex:

It makes her hearing aids squeal, and if she moves her phone away from her ear some, she cheek hangs up.

That is her ONLY complaint. Trust me, my wife loves to complain.
[Samsung Galaxy Nexus] Simer03:
My gf had a Droid Charge and a Droid X2 before I told her to get the nexus because she just constantly complained about them! Every damn day was something else! Now, I hear nothing from her! Not even about battery life! Now she wants AOKP cuz she wants some features I have! She'll love it even more!

Sent from my Nexus Prime
[Samsung Galaxy Nexus] adrynalyne:
My wife won't do custom roms. She is the enemy of change ;)
[Samsung Galaxy Nexus] kalinf:
Sorry, but seriously - what?! People aren't happy with their phones because they are encountering bugs that are spoiling that enjoyment. The stupid version number isn't important or what people are having a problem with. What they are taking issue with is that they have spent a lot of money on their phone and it isn't working to their desired level. As the phone is priced as a high end phone and is being marketed as a consumer phone (TV and newspaper ads) then they are entitled to expect those bugs to be addressed.

When updated versions of ICS are being pushed to other devices this quite obviously makes people feel aggrieved because there is no communication or indication of when or even if any of the bugs that have been uncovered and raised will be addressed for the Nexus.

The perception is that the teams are simply working at developing new stuff rather than on repairing the broken things.

Nowadays there are too many people who are willing to accept a poor level of service.
[Samsung Galaxy Nexus] adrynalyne:
Nowadays too many people are buying for the wrong reason. They go for the shiny things and their mindset is if it doesn't satisfy them now, that is ok because it will in the future.

Future (and current new) buyers note: If a device is not acceptable out of the box, return it. DO NOT BUY IT. The smart thing to do is purchase something on what it can do now, not later. NEVER purchase a device in hopes that inadequacies may be taken care of in the future, or in a timely manner. Well, that may happen, but an intelligent buyer waits until such a day arrives, and THEN purchases it (at a lower price too).

I bought this phone with its shortcomings, accepting them, never unsatisfied with how it worked out of the box. I also bought it with the knowledge that I may have to take matters into my own hands to update the software faster. My purchase decision was informed. I do not regret it. If you are not happy with this device and still own it, it is your own fault.

The early bird gets the worm. Every time.
[Samsung Galaxy Nexus] Sleuth255:
I would counter that some, maybe most people are experiencing an extremely good level of service with the GNex. This might be a factor in the slowness of the update.
[Samsung Galaxy Nexus] thephoneguyusa:
My money is on Google working on solving problems specific to our galaxy nexus.. The s2 getting 4.0.3 is not a big deal. I can understand the frustration but good god.. Like previously stated s2 ICS is ugly as hell.

Edit: Also to add early adapters to any phone are likely to have some problems... iPhone 4 antenna issue, etc.. Yes it sucks but it happens only thing we can do is sit back grab a beer and wait.

sent from my GSM Galaxy Nexus
[Samsung Galaxy Nexus] kalinf:
True - but that argument is negated by the hasty pull of 4.0.3 and 4.0.4 and even 4.0.2 initially.
[Samsung Galaxy Nexus] adrynalyne:
4.0.3 was never released ota to be pulled. Do not speak of the Nexus S, because this is not a Nexus S forum.

Same with 4.0.4.

4.0.2 was never pulled either.

There have been two OTAs and an additional update on AOSP which supports Maguro in a four month span. That is more updates than some phones see in a year, if they even see that many.
[Samsung Galaxy Nexus] kalinf:
But nexus s is in the thread title! :p
[Samsung Galaxy Nexus] adrynalyne:
:p

Companies pull updates all the time. Samsung is the king of yanking updates (look at their SGS series). Thunderbolt had one yanked as well.

Google is updating this phone faster than other devices from other companies. Unfortunately, its just not fast enough for some people.
[Samsung Galaxy Nexus] kalinf:
:) They are gold build hunting - just release some of the fixes that they have already developed without new things because the new things will bring new bugs.
[Samsung Galaxy Nexus] adrynalyne:
Well, maybe those fixes aren't ready yet. 4.0.3 doesn't fix most of the concerns Gnex users have, and 4.0.4 introduces issues as well (according to some). JBQ says 4.0.4 isn't done, but that could mean its not done for AOSP.

The only real notable features we see in 4.0.3 is a redesigned artwork for the power menu, and a new API level, which makes no real difference in the OS itself yet. 4.0.4 introduces a way to disable the lock function of the power button.

Neither of those are introducing bugs, but neither are they fixing any. IMO, this is why Google is waiting. They simply do not have a notable bugfix release ready yet.
[Samsung Galaxy Nexus] beekay201:
[heavy sarcasm]****. I thought I had a nexus. I've been fooled.[/heavy sarcasm]

These kind of topics... hate and love them at the same time.

And one more thing... Why people think that to flash a rom you have to root?

Lolol
[Samsung Galaxy Nexus] virtualcertainty:
Yes it has. Not for the GN but for that other one... you know its name.

Yes it has. Two, maybe three times.

Yakju was stopped mid-rollout for about a month. That was around the time that the *other* Nexus update was pulled. If I was to speculate I'd say that the bugs revealed in 4.0.3 made Google stop everything to make sure where on the branch the problems were occurring. After investigating they appeared to go forward with yakju.

After yakju finished rolling out the regional builds started up at a rate of one new region about every week. Until the Google wallet vulnerabilities went public. Perhaps coincidently, the regional build updates when silent for another 3-4 weeks at the same time.

Yakjuux 4.0.2 was also pulled almost two weeks ago due to breaking NFC/market access.

And through it all 4.0.1 is still workin' fine.
[Samsung Galaxy Nexus] adrynalyne:
*This is a Galaxy Nexus forum. *Please re-read what you quoted from me when talking about 4.0.3 being pulled. What I said is still true.

We are discussing Yakju and Toro device updates. Those come from Google. There is no point in discussing Samsung supplied updates.

Lastly, funny that 4.0.2 was pulled, but yet the images were never updated. That tells me it had less to do with software. Stopped, and pulled, are two different things. A pulled update never returns without changes. A stopped one, is well, stopped for the time being.
[Samsung Galaxy Nexus] virtualcertainty:
Actually, they ALL come directly from Google. Whether Samsung is involved in non-yakju devices and their degree of involvement is the subject of speculation and conspiracy theory.

What I said is equally true.

Semantics. That may be what it means to you, but not what it *means*. What do the images even have to do with whether the update is pulled or not? They can leave the url up until the sun burns out. If they don't push that image out ever again then it is pulled.

An update breaking NFC is clearly due to software.
[Samsung Galaxy Nexus] adrynalyne:
Really? What does it mean then?

Google clearly never changed the 4.0.2 update.

How is that pulled?

And images make all the differences. They are not going to update an OTA, and not an image. If they never updated the ota, and hence, not the image, the update was stopped. If it was pulled, it would NEVER return in its current form.
[Samsung Galaxy Nexus] adrynalyne:
What evidence do you have that the updates come directly from Google?

Why would they be kept in a Samsung_Proxima folder on the ota server, instead of google_maguro?
[Samsung Galaxy Nexus] adrynalyne:
It wasn't broken for Yakju. All the more reason to realize that Google isn't the only one sending out updates.
[Samsung Galaxy Nexus] Simer03:
Not everyone experiences these problems that u guys are having, so its not like they can go to each phone and fix their separate issues....that's what warranty repair is for...the OTA updates effect everyone! Like I said, I have a GSM version and my gf has the Verizon version with no issues at all so do a battery pull or something

Sent from my Nexus Prime
[Samsung Galaxy Nexus] adrynalyne:
You are wrong. They are right. Face it.
[Samsung Galaxy Nexus] spencer88:
So a battery pull is going to prevent my outgoing audio from being lost. Cool thanks for the tip.
[Samsung Galaxy Nexus] adrynalyne:
If you never had audio to begin with, how can you lose it?

A turned off phone cannot disappoint.
[Samsung Galaxy Nexus] spencer88:
I guess it would at least look good then.
[Samsung Galaxy Nexus] virtualcertainty:
Yakju wasn't released 4 days before the market was updated to Google Play. New market version, perhaps new code for NFC, perhaps a lot of things that could have been weeded out with more testing. None of which points to any evidence any specific party did the coding, testing, QA, or certification. It still came from Google's servers, however.
[Samsung Galaxy Nexus] adrynalyne:
What evidence do you have? Virtually every android device out there uses the android.clients.google mirrors. Even HTC devices with Sense updates.
[Samsung Galaxy Nexus] Evangelion01:
Those of you claiming that your Nexus 'works fine' are missing the point. Your anecdotal evidence is not worth any more than the anecdotal evidence of the people who are experiencing bugs like multitouch etc.

Those of you who scream "install a custom ROM!" - some people don't want to jeopardise their warranty. As far as I know, it's necessary to unlock the bootloader to flash a custom ROM - but perhaps I'm wrong. Even if I am wrong, this phone is advertised as being 'pure Google' and not a 'dev' phone like so many of you seem to believe. It's advertised and aimed at the layman.

The fact is that there are definitely significant bugs in 4.0.2. No matter how hard you try to argue against that, you will never be able to write to a NFC tag that has not been preformatted with your 4.0.2 Nexus. That is a bug in the OS which Google are aware of and have fixed in 4.0.3.

I don't know about you, but when there's a clear bug that has limited the function of a main selling point of a device for four months, it's only logical to expect at least some angry customers and complaints, and rightly so.
[Samsung Galaxy Nexus] adrynalyne:
The Nexus was never advertised with the ability to write NFC tags ;)
[Samsung Galaxy Nexus] Simer03:
I don't get it....people say they don't want to void their warranty by rooting and yet, they don't actually use the warranty to fix their "problem"...wow...

Sent from my Nexus Prime
[Samsung Galaxy Nexus] adrynalyne:
I think a lot of it has to do with imports. Warranty is now a suggestion that may or may not exist, rather than a cold-hard fact.
[Samsung Galaxy Nexus] :
I don't buy

anything

that doesn't have a voided warranty in short order, why should my phone be different? :cool:
[Samsung Galaxy Nexus] Evangelion01:
Yes, I know that the advertising material doesn't specifically mention tag writing. That doesn't change the fact that it's a bug within 4.0.2.

Also, for those of you who say that Google never claimed that Nexus owners are the first to get updates, here's a quote from Google's Nexus PR:

---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------

I don't quite understand this. How would a person use their warranty to fix the 'problem' of bugs?
[Samsung Galaxy Nexus] adrynalyne:
Link, please.
[Samsung Galaxy Nexus] :
That quote is rather open ended however; much could be read into it either way.
[Samsung Galaxy Nexus] Simer03:
Easy solution..sell your phone to someone that wants it and buy a galaxy s2 or something! You'll wish u didn't

Sent from my Nexus Prime
[Samsung Galaxy Nexus] Evangelion01:
That's true, I'm just pointing out that if someone read this part of the press release, it's certainly understandable why they would be up in arms when seeing other Android devices receiving 4.0.3 before them.
[Samsung Galaxy Nexus] :
Agreed. 10char.
[Samsung Galaxy Nexus] andQlimax:
BREAKING!

http://www.echosdunet.net/dossiers/dossier_9046_sfr+actualise+son+calendrier+mise+jour+android.html

end of the post:

"SFR est en train de tester et d'adapter Android 4.0.5 pour Samsung Galaxy Nexus et Google Nexus S par Samsung."

english: SFR is currently testing and adapting Android 4.0.5 for Samsung Galaxy Nexus and Google Nexus S by Samsung.

SO: is seems google distribuited the 4.0.5 update to the carriers already (this is the normal test procedure) and so is ready to release it for the users soon i guess

so sfr delayed it because they need to put their branding **** things for their customer maybe

but what we should care is that the 4.0.5 is ready and we will get it from google soon..probably
[Samsung Galaxy Nexus] The Gingerbread Man:
Thank you for something finally on topic....