yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] oscillik:
I've ignored your other comments because you're a troll.

It doesn't look good that they haven't even made an announcement.

Ok, now that the show is over and you've jointly exercised your righteousness, will you please read the entire thread?

Now to answer your question - Yes you are correct there, the issue

at the moment

only appears to be susceptible from interference due to the 900MHz GSM band. As you're in the US, you shouldn't encounter this frequency band in general usage.

However, if you end up with a handset that has the fault (if bought from the current batch that is for sale in the UK) then you will still be susceptible to interference from external devices that happen to put out 900MHz. Also, if you ever plan to travel abroad, you may end up suffering from the problem.

I hope I've been able to help clear things up a little for you there. If not, sorry.
[Samsung Galaxy Nexus] bleets:
on the other hand, you have been constantly shooting down anything anybody says that contradicts what you have chosen to believe as fact.

if somebody points something out to you or maybe says you might not be quite right, or even tells you to wait and be patient, you don't want to know.

all you have chosen to do is believe the total doom and gloom theories without considering that it might not actually be what you think.

you need to get a grip and realise what you consider to be right might not actually be the case and to just walk away for a bit and let everybody have their OWN opinion, not just yours.

wait till you get actual hard facts from the people who fault find thing properly every day.
[Samsung Galaxy Nexus] oscillik:
I have already admitted publicly that I was wrong about something. So your first sentence is based on ignorance.

As for your other points, those of us who have the phone and have been running tests to the best of our ability have been able to ascertain that at the moment the fault is extremely likely to be hardware related. Do you even have the phone?
[Samsung Galaxy Nexus] SuperUserMovado:
blame game

the best part of the nexus line is that there is always a finger to point at a partner to blame for the lack of communication.

Carriers blame Samsung,Google blames Carrier,Samsung blames Google

Its a win win for everyone

/s
[Samsung Galaxy Nexus] Dmw017:
Lol I can tell a lot of people are frustrated because of this (for good reason, just kind of humurous.. i was pissed at first too btw)

I hope the next Nexus is made by... well yeah no actually Samsung was a good choice :/ even after all this... lol . I was going to say HTC at first but the battery is garbage and Samsung is top-notch when it comes to design, screen, and overall hardware (look at the Galaxy SII). This device was rushed and yeah.. funny how this all turned out.. Verizon ends up looking like the good guy for postponing the initial release date to work out all the bugs. I can't blaim Samsung, this device was rushed just to "compete" (<-- lol) with the iPhackyou.
[Samsung Galaxy Nexus] Lootes:
I am only slightly surprised that we haven't had any official word from Samsung or Google on this matter. If tomorrow goes by without anything I would probably move to being shocked. This is my reasoning. Although this thread and these reports began to surface over the weekend, it wasn't until Monday that many users started the complaints process to Samsung, Google and the stores they purchased the devices from. These issues then need to flow through the appropriate channels that in my opinion are not always the fastest route the executive management team. Then, yesterday afternoon (Pacific time), the major android sites began to report this issue including CNet UK. At this point EMT members of both companies begin to get the news and begin to react. I imagine that Google engineers, who were still in the office, started working on their own tests emails were sent around the world to Samsung Corporate as well as Samsung UK. Today, Samsung and Google have probably spent it trying to figure out what is the exact cause of this, with our help they should have been able to narrow it down fairly quickly. Then they need to decide the appropriate way to proceed. Is it a recall? Can a software patch fix it? PR departments from both companies then need to draft the statements, legal, also from both companies, need to sign off on these statements before they go to the executive management teams. Then and only then will we hear an announcement. I agree is should have happened quicker, but sometimes this is how it goes when multiple large companies are in a joint venture. At this point, please don't even begin to assume that some CS rep from Samsung or Google or O2 or wherever has even the foggiest idea of what the company is doing and what it is going to do. All these decisions are happening now at a very high level.
[Samsung Galaxy Nexus] foxfire235:
So am i correct in my understanding that this bug only affects 900mhz 2g frequency? Has anyone TESTED 850 / 1900 mhz to see if it has the same issue? All my USA buddies are relying on the 900mhz band being the ONLY frequency affected, but I haven't seen if all frequencies have been checked.
[Samsung Galaxy Nexus] juicytuna:
Additionally IF there was a way to disable the volume rocker from within the kernel, it could be made so that volume rocker is disabled when in 2g mode or if some irregular interrupt pattern is detected.

This could all be handled quite elegantly in software using a combination of software volume controls, notifications warning you when the volume rocker has been disabled and so on.

For most people, most of the time, the phone would work just as it does now. In the case of when the interference problem occurs, there could be an elegant if not ideal fall back.

I'm making a lot of assumptions here but there you go. One possible way they can polish this SAV turd?
[Samsung Galaxy Nexus] Love_Velvet:
as has been said before, 850 isnt used in the uk, so it can't have been tested yet unless someone imported one to the US
[Samsung Galaxy Nexus] mingoid:
Just taken my phone back to three. I'd rather stick with my trusty Nexus One while I wait for this to play out and have the money in my pocket - it's just too stressful otherwise.

Hoping it get's fixed soon as I love the phone otherwise and I will buy again if I'm sure it's sorted. I know some people here are having a go at Samsung after a couple of other well known issues but I still think they make the best Android phones. I loathe Sense and the HTCs are generally too heavy due to the metal construction. Say what you like about the build quality of the GN, it's a 4.65" screened phone that weighs the same as my 3.7" nexus one...:o
[Samsung Galaxy Nexus] SuperUserMovado:
I have to agree with you on this one. I do believe Samsung is better than choosing htc but Google really skimped out on some of the specs for this phone. It would be nice if they picked SE as the next OEM even though SE brushed them off originally. Now that Sony has taken over I don't know if they will still have nicely designed phones. My next phone is probably the Nozomi,hopefully it will have the SE brand by the time it makes it to market.
[Samsung Galaxy Nexus] oscillik:
so far the issue has only shown up whilst encountering 900MHz GSM frequencies. We have no conclusive reports whatsoever regarding 850MHz / 1900MHz or any other frequencies used in the US.

Some tech review sites have been shown to be using an AT&T SIM in their handset, and these reviews haven't made mention of any occurrence of the problem, however these reviews may not have tested the phone in 2G mode. While this is an assumption on my part, I believe it is a safe one, since review sites are likely to have all the fastest features enabled - it makes no sense to review a product by using it in a 2G coverage area or even to force 2G coverage by setting the "Only use 2G networks" option. Again, I admit this is speculation.

Ideally, we need someone in the US to test with some US SIM cards on T-Mobile and AT&T and verify what the situation is.
[Samsung Galaxy Nexus] adamleerusse:
Not sure if this is still required but the first post says so :-)

Just email technical support at Samsung as some people have been asked to do on Samsung UK Facebook page.

Got this on launch day, o2 network, build number: ITL41D

Issue only happens when phone switches from poor 3G coverage to 2G.
[Samsung Galaxy Nexus] deyanp:
I can't help but laugh when I hear that Google and Samsung would issue an official statement. This is not going to happen, for sure. What they will do is to issue a software patch which will simply be a workaround (what was mentioned already). Newer batches (speaking Jan+) might contain a hardware fix already, but I am afraid all batches in Nov and Dec will will have it (unfortunately for me as I wait for mine to come from amazon, but do not have high hopes) ...
[Samsung Galaxy Nexus] foxfire235:
Right on. Thanks!
[Samsung Galaxy Nexus] Taggard:
My GN is en route (via express mail) to the states right now. If I get it tomorrow or Friday (Thursday is Thanksgiving here), and this is still an unknown issue, I will be happy to test it out. I have T-Mobile.
[Samsung Galaxy Nexus] oscillik:
that is very good news! I think we can all agree that we would all be very grateful for you to test this out.

As an aside, is there any way that you could possible get hold of an AT&T SIM card and test it out? Or at the very least, grab hold of a friend's AT&T phone, force it into 2G mode and carry out the 'secondary phone' test to see if it causes interference?
[Samsung Galaxy Nexus] appelflap:
C'mon ever wondered how many background services are running. This is XDA Developers if Google doesn't fix it we do. That's how it used to be and that's how it is. You don't wanna know how many things are fixed here. So please get to work lol
[Samsung Galaxy Nexus] mike freegan:
I can't see this being fixed. I think what'll happen is Samsung will ask us to put up with it until they can offer a free exchange

I predict they will have an exchange operation much like Xbox360, whereby you send yours in and they instantly send you a pre-repaired one back.

I'm on Three, so this doesn't affect me unless someone sits next to me on O2, or puts their phone on the table next to mine. However it has harmed my potential to sell the phone and means I'm stuck with 3 for as long as I have it.

I think my plan is going to be: Call 3 and tell them they can reduce me to £15 per month (so £360 for the contract) or they can lose a customer and have a used phone returned to them (£0 for Three).
[Samsung Galaxy Nexus] Taggard:
That won't be difficult at all. I work for a software engineering agency, and everyone here is dying to see my new phone. I will have no problem getting someone to volunteer their AT&T SIM for a few tests. :)

I also have my Nexus One, which I can switch to 2G to test the close proximity issues. We'll have a lab day at the office!
[Samsung Galaxy Nexus] oscillik:
this is really good news. Also, regardless of the results of your test, would you be able to post your Odin details in my Odin details thread?
[Samsung Galaxy Nexus] illumii:
heh, let me know how that goes.
[Samsung Galaxy Nexus] mike freegan:
I am master of the blag dude. If you threaten to leave, they'll offer almost anything.

It would be good for us to pull together all the people from XDA, Reddit, MoDaCo etc to co-ordinate a mass bargain, considering they also didn't test the phones that they signed us up for 24 months on.
[Samsung Galaxy Nexus] njiwani:
Your posts are freakin annoying to read...you need to get a hobby or something man
[Samsung Galaxy Nexus] oscillik:
it's freakin annoying to read the countless people spreading misinformation, disingenuous claims, and completely baseless assumptions.

My posts may annoy you, but they are rooted and based in evidence gathered by those of us who have been testing our phones.
[Samsung Galaxy Nexus] 4569294:
Will this volume bug affect me as a T-Mobile user in the U.S. who had the phone ordered from Handtec?
[Samsung Galaxy Nexus] oscillik:
I'm going to quote you what I said in the Handtec thread:

to further clarify - under normal operating conditions, and by all indications at the moment, you shouldn't encounter issues with this, except in the cases I have outlined above.

We are waiting to hear back from American users who have bought and are waiting for their Galaxy Nexus imports to arrive, so we will find out some more conclusive tests regarding frequency bands and any possibly interference very soon.
[Samsung Galaxy Nexus] Luxferro:
Just cause it happens in the bootloader doesn't mean that whatever piece of hardware or circuit isn't being controlled by some kind of firmware.

example. what portions of a phones hardware are powered up when in the bootloader state? Maybe a circuit is on when it shouldn't be. Maybe a pin is floating and can be set with a register to an internal pullup, ect.

Speculating is just that; speculation. Unless you have the design specs of the phone, and/or were involved with the design of it, you're just guessing.
[Samsung Galaxy Nexus] Tom Servo:
I've been looking at pictures on GIS with the GN and GS2 next to each other with the battery cover off. I'd wager that the general PCB layout is similar, seeing how things are laid out.

I'm going to check out the Galaxy S2 teardown on iFixit.

---------- Post added at 09:50 PM ---------- Previous post was at 09:37 PM ----------

Judging how the EMI shield is laid out on the Galaxy S2, it might be worthwhile to redo the tin foil thing, but this time on top of the battery (ideally only partially, the upper part, to prevent heat insulation) and the area where the volume rocker is.

See step 4 in the guide, where the shielding is. Given similar construction, it might help things.

http://www.ifixit.com/Teardown/Samsung-Galaxy-S-II-Teardown/5861/1

In the GS2, the antenna is on the bottom, and its connector runs up to the top part of the board using a wire on the opposite side of the volume buttons.

--edit: Theory of this is that the tin foil on top of the electronics combined with metallic traces on the PCB below the electronics create some slight Faraday effect.

--edit2: Maybe also follow the shape of the battery compartment. Instead of all tin foil directly below the battery cover, part below the battery, the rest coming up in the gap and covering the volume rocker area, creating an S fold. If I interpret the antenna design and volume button wiring correctly on the GS2 teardown, the earlier idea with foil below the battery wouldn't have helped.

Obviously, these are assuming the PCB design is similar.
[Samsung Galaxy Nexus] Jebus99:
This thread is getting extremely crowded and gossipy. Please make it clear that everything up to this point is speculation based on user experience. No one has taken their phone apart and found the root cause. We have to wait till Samsung/Google or a knowledgable party
[Samsung Galaxy Nexus] Nebucatnetzer:
Shouldn't a shield or a faraday cage be grounded? How would you do that? In addition shouldn't it cover the whole thing which you want to protect on all sides?
[Samsung Galaxy Nexus] Tom Servo:
I'm not sure about the grounding part. If you need that, I figure you can make the foil touch the SIM holder metal. It appears grounded on the GS2.

As far as covering all sides goes, it's mainly about preventing the internal about interfering. I doubt that other phones will cause the Nexus to freak out, unless they're really close. Signal strength diminishes in square relative to the distance.
[Samsung Galaxy Nexus] burnduck:
people people why all the argue

i don't care what causes the problem, whether it's hardware or software, as long as they do something and it's proper and permanently fix I'll be a happy chappy, but afaik there're no official statements from either Google or Samsung regarding this issue and all we've got are words from the o2 reps, which is more or less credible as the internet.

So for those who are experiencing this problem, please send an email to

Samsung UK at

uk.technical@samsung.com

to make them aware of the seriousness of the situation.
[Samsung Galaxy Nexus] chrisn0123:
My SIM FREE Galaxy Nexus will arrive tomorrow from Clove. I am on giffgaff (O2) and use 2G a lot, so will do thorough testing on 900MHz. Will test TX'ing from another handset near to it and will TX using other frequencies using my handheld radio on low power (amateur radio). I'll certainly send it back for a refund if the hardware fault is on mine and buy the Note instead.
[Samsung Galaxy Nexus] paul_one:
<warning - joke ahead!> Can you please say that's your opinion and it's not stated fact, unless you can prove the fault is with the oscillik hardware and not in the forum software this is just an opinion and there's no scientific fact to show that evolution is real.... wait, what were we talking about again? :-)

</joke>

seriously, I go away to deal with my migraine and people still arguing opinion in a fact thread?

I thought "earthing" was always touching - well - Earth. In phones I guess it's touching the outer case to add to the Faraday cage effect, possibly going back to the third battery pin?

*edit*

Oh, some further thoughts: I guess no-one can reproduce on say, the SGS2, holding an old phone next to it on 2G?
[Samsung Galaxy Nexus] Tom Servo:
Shrug, no idea. When designing DC electronics, you have to have a ground (as in earthing). That includes mobile electronics. Never bothered to figure out why it's called a ground.
[Samsung Galaxy Nexus] DoddyUK:
Given this nonsense reply I got from Samsung UK's email address, you're best off just emailing Google:

Needless to say, the CSR on the Samsung hotline was equally useless.
[Samsung Galaxy Nexus] oscillik:
conversation with Romain Guy, Android engineer on #android freenode.net

<oscillik> romainguy: any news on this 900MHz issue with the Galaxy Nexus? please?
<oscillik> by all accounts, this seems like hardware defect
<Khaytsus> oscillik: that's a Samsung problem, not Google ;)
<CPng|N> yeah how do they manage to come out with these features and then not implement them on new lines?
<romainguy> oscillik: the volume that changes by itself?
<CPng|N> as if a tiny 3 color LED is that expensive
<oscillik> romainguy: yes
<Cancel_> romainguy: that's a "feature"
<Khaytsus> CPng|N: What's funny is as I recall NOBODY really utilized the RGB notification light except third party apps
<oscillik> due to interference from the 900MHz GSM band
<romainguy> it's a known issue and I believe we have a software fix
<FernandoMiguel> Khaytsus: N1 was the only device with RGB track ball
<romainguy> but it's not my area so...
<lonelyDonut> Khaytsus: i used the **** out of them on the N1. I miss it so.
<romainguy> no guarantee etc.
<Khaytsus> FernandoMiguel: So you're saying small footprint of users to have such a feature eh?
<oscillik> romainguy: really? even though by all accounts it seems largely to be a hardware defect due to insufficient RF shielding?

Looks like Google are in fact working on a software patch for this, and I am going to publicly admit that I was wrong about the 4.0.2 patch being specific to the Verizon version.

edit: Pastebin link of the conversation for easier reading
[Samsung Galaxy Nexus] Tom Servo:
I wonder if 4.0.2 is in AOSP already. Because then you could verify.

--edit: They don't have Gitweb anymore :|
[Samsung Galaxy Nexus] sblantipodi:
I appreciate that you admit that you are possibly wrong, your campaign about hardware issues was very "strange", you were sure about an hardware problem without any data that can confirm it.
[Samsung Galaxy Nexus] oscillik:
oh please don't misunderstand me - I still firmly believe that this is a hardware defect.

However, I was quick to smack down reports of a 4.0.2 update because at the time we had information that said this update was specific to the Verizon version of the Galaxy Nexus.

It looks like I was very wrong to smack people down about that, and for that I apologise to each and every one of you that I smacked down. I was wrong.
[Samsung Galaxy Nexus] bleets:
im interested to see if he got any more response after his last comment in that paste...
[Samsung Galaxy Nexus] phillipm:
Did more information come from the conversation.. :)
[Samsung Galaxy Nexus] sblantipodi:
you are always too fast to reach conclusions, calm down, that conversation with romain guy says: "it's a known issue and I believe we have a software fix"

I believe means that he is not sure.
[Samsung Galaxy Nexus] oscillik:
unfortunately no :( He obviously didn't want to comment on it anymore, since he moved onto a different topic.

unfortunately nope.

Agreed - this isn't definitive, but it's the best information we've had so far regarding any work that is being done about this by either Google or Samsung.
[Samsung Galaxy Nexus] burnduck:
only if that "software fix" is indeed a fix not a "patch"
[Samsung Galaxy Nexus] oscillik:
posting this here too as a way of trying to humble myself regarding this 4.0.2 update
[Samsung Galaxy Nexus] PaulCayard:
IMHO, a 4.0.2 (or any SW update) that "mask" the problem is not a good news.

If a new SW fix the problem, I think that we never know if it was an HW problem (masked by new SW) or a SW problem properly fixed.
[Samsung Galaxy Nexus] paul_one:
What's the betting that they just adjust the radio transmit power (or adjust the frequency a tad)?
[Samsung Galaxy Nexus] oscillik:
I agree - if the fault is indeed a hardware defect (as I still believe it to be), then any software 'patch' to paper over the cracks is a bad thing. If indeed this is a hardware defect, then the phone should never have shipped in this state and certainly should be recalled and customers given opportunity to get a new batch.
[Samsung Galaxy Nexus] samizad:
Don't worry about it man. You have been on this thread and the other one for, it seems like, every second this fiasco has been going on. You need a rest but I appreciate your taking ownership of this problem. Someone has to.

Maybe update the first post with latest theories.
[Samsung Galaxy Nexus] Duddyroar:
Agreed, this isn't the news I was hoping for. Although none of us here is an expert in this field, the evidence that has been put forward suggests that a software patch isn't going to remove the issue. If one is issued, then it will give Samsung the chance to get out of a recall, and we could potentially be stuck with defective phones.

I'm tempted to return my phone for a refund, TBH.
[Samsung Galaxy Nexus] oscillik:
I must admit - I am knackered, and had been contemplating getting into bed 2 hours ago. But I didn't, and I'm glad I didn't because now we have a bit more information than we did 2 hours ago.

As for updating the first post, I cannot do that as I didn't start this thread. I'm sure kristovaher will update it though once he sees the information.

Lets be clear here though - this still appears to be a hardware defect. It's just that we have had our first word that someone is actually paying attention to it and looking into it.
[Samsung Galaxy Nexus] Hosh0:
Wait if they mask the problem so it has no impact on the user, then who cares? Do you really think there is no where else in the phone where the hardware isn't performing exactly how it's supposed to/expected to and software is being used to enhance or mask it's faults?
[Samsung Galaxy Nexus] oscillik:
If you're thinking of getting a refund, now would be the best time to do it - before the update is pushed out.

Unless of course, the update does diddly squat...
[Samsung Galaxy Nexus] Robboftw:
Because in all likelihood it WILL have an impact on the user.
[Samsung Galaxy Nexus] oscillik:
My guess here:

The only thing that they could conceivably do to mask this would be to stop the internal cellular radio from interfering so much with the volume rocker switches.

This would not stop external interference though, so technically the phone is still defective.

Again, that is just my guess on this particular development though.
[Samsung Galaxy Nexus] Hosh0:
Jumping to conclusions here. I mean this thread has gone around and around like this. Lets just see what they come up with then worry about that.