yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Danrarbc:
It depends on what sets the rate and if it can be overridden. If it's a hardware clock then they might not be able to. But if it can be set by software the bootloader could also be updated I'm sure.

Yeah. I was thinking out loud. Clearly this is a specific range of frequencies combined with TDMA screwing with it.
[Samsung Galaxy Nexus] oscillik:
considering that the problem occurs in bootloader mode, i would say that it is via hardware clock or some other extremely low level method.
[Samsung Galaxy Nexus] gambiting:
Yes, but this is only an assumption. You have to agree, that there is a CHANCE that the pooling value can be changed. Neither one of us is a Samsung's Engineer, so we cannot rule this out.
[Samsung Galaxy Nexus] jaketurbo:
What does low level mean again?

Where do you think the bootloader resides again?
[Samsung Galaxy Nexus] oscillik:
it means you have no clue what you're talking about
[Samsung Galaxy Nexus] Danrarbc:
Can't you adjust a PS/2 polling rate anywhere in between 20Hz and 200Hz?
[Samsung Galaxy Nexus] Niksko:
I agree. Until Samsung come along and provide some official information, nobody can really comment on whether this will definitely be fixable or not, unless you've torn down your Galaxy Nexus and conducted extensive tests to determine what EXACTLY is causing the fault, and what options there are to remedy it.
[Samsung Galaxy Nexus] oscillik:
i think you're getting confused with USB
[Samsung Galaxy Nexus] Danrarbc:
USB has a much wider polling range than that.
[Samsung Galaxy Nexus] dnlsmy:
Apparently the problem has been "fixed" by Google and Samsung with an update.

P3Droid reports it has been fixed and he's supposedly running the new version, 4.0.2.

"And now I'm one of very few people who is running Android 4.0.2.....Can't wait to see how this runs"
[Samsung Galaxy Nexus] dnlsmy:
There was some error on my part, but it's still supposedly fixed.

EDIT: It seems the 4.0.2 update is for the LTE Nexus not the GSM version. He still states it HAS been fixed via software though.

So the volume bug was fixed and will be out soon..but wtf are people doing using the nexus in a 2g area? Bu… (cont) http://t.co/0qnXHqxW
[Samsung Galaxy Nexus] atomic_dude:
It has been fixed, see guys? I remeber Intel managed to fix the Pentium CPU that had a hardware bug back in the day. What's a playful volume rocker compared to that? :-)
[Samsung Galaxy Nexus] cellzealot:
Our devices were updated tonight to ICL52 4.0.2 but I don't think P3Droid stated that the issue was fixed by this update and we have no way to verify that because neither of us has experienced the problem. Our devices are different in a number of ways from those experiencing this issue and neither of us is in a place where 900MHz EMI exists nor do we have an RF generator to test for it.

We also hear conflicting info from various sources and have to sift through and piece it together ourselves to assess its substance.

Things get conflated and distorted rather quickly in this environment and change rapidly so clear, unbiased information is virtually impossible to ascertain.
[Samsung Galaxy Nexus] Chirality:
P3Droid said that the LTE version never had the volume problem in the first place, so we can assume that the 4.0.2 update for LTE GN is unrelated?

Can you reveal what the 4.0.2 update actually addressed?
[Samsung Galaxy Nexus] StuMcBill:
He did say in a previous tweet that it was fixed and would be released soon? He doesn't specify if the 4.0.2 update is the fix or not though?

https://twitter.com/#!/P3Droid/status/138758547801505792
[Samsung Galaxy Nexus] cellzealot:
We get updates pushed on a regular basis, the only thing different about this one is that it changed to 4.0.2 and I have been running it for about an hour at this point so my evaluation is minimal at best. The baseband was updated again but seems relatively equivalent in my very marginal 3G only signal area. This also makes my assessments of battery performance and general RF performance of this phone to be very negatively shaded.

I need more time before I can really make any valid judgements.
[Samsung Galaxy Nexus] Chirality:
Are you able to reveal what your relation to Verizon is? Do they supply you with changelogs, new things to test, things like that with each update?
[Samsung Galaxy Nexus] cellzealot:
No and no...I have no relationship with VZW whatsoever besides paying them a fair chunk of money each month to cover my addiction to digital toys! ;)

The updates are pushed by Google.

We get minimal official information.
[Samsung Galaxy Nexus] Chirality:
So I surmise your relationship is with Google then?

Wink once for yes.
[Samsung Galaxy Nexus] cellzealot:
TeamBlackHat is a group of very obsessed user enthusiasts with a long history of playing with phones and we have developed some very good friends in the business along the way. We are entirely unaffiliated with any official body and we never discuss our sources. Which is why we still have them all these years later...it's that simple!

It doesn't do anyone any good anyway, just to prove a point or gain credibility. I am not trying to be mysterious or elitist at all, just honest.

Hope that is an acceptable answer.
[Samsung Galaxy Nexus] appelflap:
Why not? It seems to me that you can write software to correct it. You can use a simple algorithm for that. I agree that it will not fix it at a low level, but it can correct idiosyncratic behavior at a higher level. So I'm definitely expecting a patch for this.
[Samsung Galaxy Nexus] Chirality:
Yes, perfectly acceptable. I have no doubts you have the device. Was just wondering if you are an employee or in some other position where you can tell us your association, or like you said, in an unaffiliated group. If I had known you were in an unaffiliated group I would not be pressing you for your sources.
[Samsung Galaxy Nexus] appelflap:
Why? I see software responding to it.
[Samsung Galaxy Nexus] w1nter456:
D

Well, that is also a feature call "lover beam", means whenever boys phone react with girls phone, it will immediately respond.
[Samsung Galaxy Nexus] Egan:
The cause is never the radio for transmitting RF, that's one of its main functions. The volume rocker should be shielded, which its not and is causing this weird behavior.

When you disable the radio of your Galaxy Nexus and lay my HTC Desire next to it and let my HTC Desire be called, you will have the same behavior since the volume rocker isn't shielded. Is the cause now my HTC Desire (which now has to die)? No! Its the volume rocker.

Bottom line, you can't blame the radio for transmitting radio frequencies. You can however blame other components which are too sensitive for them
[Samsung Galaxy Nexus] Egan:
I should really leave XDA, bunch of know it all kidz!
[Samsung Galaxy Nexus] :
Wouldn't it be really embarrasing if the bug turns out to be solvable through software/ baseband firmware updates? :) Have you gotten the 4.0.2 update btw? It might just fix it!

I might be wrong here though. Only time will tell :)
[Samsung Galaxy Nexus] kristovaher:
Software will not fix it. It is possible that they will release a 'hack' of sorts that will make the software ignore such a signal, but it will not really fix it, phone will still get hit by interference and might still suffer from slowdowns, even if they will be able to stop volume from being changed.
[Samsung Galaxy Nexus] samizad:
... and presumably increase battery drainage.
[Samsung Galaxy Nexus] dnlsmy:
Really sucks for UK early adopters, but there is a silver lining. Both Clove and Handtec have stated that they have talked to Samsung about the problem, and both state that they have Quality checked their batches with Samsung and that they do not suffer from the SAV ghost.

Source: http://youtu.be/nNYHHkT0tU4?t=6m55s

https://twitter.com/#!/handtec/status/138688072719155201

You can also check Handtec and Clove's blogs
[Samsung Galaxy Nexus] kristovaher:
They did not state that the quality check was to ensure they do not suffer from SAV ghost. It just received additional testing, but that happened before SAV ghost became widely spread, so the only way Samsung could have tested for that is if they knew about it already before we did and still shipped in UK last week.

I am hoping for the best though, of course.
[Samsung Galaxy Nexus] chandlerweb:
Am glad you are pointing out what they actually did say. Too many people made incorrect assumptions about the launch based on Sammy insisting multiple times it would be on 17th and not delayed. We all now know how that turned out. After that debacle I wouldn't trust Sammy's word anymore than I would a politician!
[Samsung Galaxy Nexus] jmbillings:
I'm going to have to have a go at repeating this problem later. I've not observed it yet, and I don't get a 3G signal at home. I do have Wifi on though. Should turning that off so I'm on GPRS be enough to theoretically make it happen?
[Samsung Galaxy Nexus] escrivel:
@TeamBlackHat: Do you have any news for us? Sorry for spamming for your help but there are so many insecured galaxy nexus waiting people out there :)
[Samsung Galaxy Nexus] atomic_dude:
I would put money on Samsung having fixed the sim free batch. Why do you think there was a delay from 17th to 22nd? Clove is shipping 800 units, Handec probably around that many, too. They knew the fist batch was faulty but it was too late to do something about it. Worst case scenario, Sammy needs to replace a few dozen units. The bulk of Nexus shipping is sim free and those should be ok. Can't see Clove and Handtec taking any chances sending over faulty ones. Don't know much about the phonesforyou mob but I'm sure their international (if they got any at all that is) clout is nowhere near as large as Clove's. Real Nexus toys addicts buy their poison upfront, sim free, unlocked, pure, bloatware free, etc I'm sure neither Samsung, Clove or Handtec would ever mess with them :) Why do you think Google and Sammy didn't jump all over the issue already? That's because it was all fixed fro the sim free batch maybe?

As I said, Clove is about to ship 800 units. That's like what, a pallet's worth? I'm sure Samsung can manufacture that many within hours and arrange for then to be flown from their factory to UK within 12 hours. I've seen 5 tonne gas turbines being dispatched that way, let alone a pallet worth $100k!

Sure, all of the above is speculation, as is most of this thread. We're just about to find out
[Samsung Galaxy Nexus] chandlerweb:
I got mine from Phones4U "upfront, sim free, unlocked, pure, bloatware free, etc" - Piad £529 - no contract etc.

In fact all phones from Phones4U were SIM Free, its just they preferred selling them with contracts but it was still an "pure" handset.
[Samsung Galaxy Nexus] denk:
How do we actually know that the radio is disabled in HBOOT mode?

Another way to see if you will get the same effect is to try turning radio off in:

*#*#4636#*#* ---> Phone Information

then having another phone in 2G mode making a phone call and getting it close to GN just like in the video.

Just a thought.
[Samsung Galaxy Nexus] kristovaher:
Delay from 17th was because Phones4U secured exclusive launch, not because Samsung discovered a flaw. Many showed later deliveries to begin with, like Amazon.

Sent from my HTC Desire
[Samsung Galaxy Nexus] atomic_dude:
What is so special about phones4u anyway that got them exclusivity?
[Samsung Galaxy Nexus] floatlite:
They will have either paid for the exclusive, or fronted a high number of orders for Samsung product to 'buy' the exclusive. A common sales technique to try and soak up all the early demand for the product.

....as for them being so special...........
[Samsung Galaxy Nexus] Emama:
Soooooo disappointed about all Nexus phones have some kind of issues.....

I really want to get this phone...

But based on the N1 screen experience, I am not expecting Google would take all the phone back and fix it if it is hardware related.
[Samsung Galaxy Nexus] bydox:
Seems like Handtec have finally found faulty devices :/

https://twitter.com/#!/handtec/status/138997218769248257
[Samsung Galaxy Nexus] w1nter456:
I think Google only allow a firmware update to 4.0.2 to fix this problem or give us free case if it is hardware related.
[Samsung Galaxy Nexus] oscillik:
stop spreading incorrect information

this 4.0.2 update that is being mentioned is only for the Verizon version of the Galaxy Nexus, and is nothing to do with the HSPA version which is being affected by this hardware fault.

no software patch can fix this.
[Samsung Galaxy Nexus] noobdeagle:
I can see it now the moment that samsung announce a recall there will be a big thread made by you that will read "I TOLD YOU SO!" untill then i doubt you will be happy :\

let us dream about a possible software fix damnit i want more than a $700 paper weight :D

in all seriousness tho samsung is continuing orders despite it being well documented im sure they know and they must have a plan ...........or they just deny and say we are all holding it wrong
[Samsung Galaxy Nexus] oscillik:
you can hope for a software fix all you like, i don't begrudge you that luxury.

but it is disingenuous to proclaim that a

software update for a completely different phone

will fix this issue. it's completely wrong.
[Samsung Galaxy Nexus] saster2:
Nah .. they just change the documentation and call it a quad-band :)

/S
[Samsung Galaxy Nexus] s.m.knipe:
So the physical buttons must work on some sort of wireless (900 MHz) relay then right? That seems overly complicated for a hardware input. I don't know much about the hardware used in devices like this. Is it possible for EMR to interrupt/interfere with a direct signal (pulse i guess)?

I am not doubting that the issue is real, it is very real and serious, and Google and Samsung need to respond to it (PS good luck getting Samsung to admit anything hardware related is the problem). I just think we need to be sure we are looking at a symptom and a cause, not a symptom and a catalyst. Common occurrence does not necessarily indicate causality...

Do we have any hardware engineers around to comment?
[Samsung Galaxy Nexus] oscillik:
no

yes
[Samsung Galaxy Nexus] w1nter456:
Well, what I actually means was they can use some kind of hack to minimize the 2G network/volume bug problem, not completely eliminate the problem, this situation just like iPhone 4 first announcement, the software(iOS 4.0.1) will fix some of the iPhone 4 antennagate problem but not exactly all.
[Samsung Galaxy Nexus] oscillik:
well first of all, I refer you to my original point - it is for a completely different variant of the handset.

second of all, that information has been gleaned from a tweet by someone who is not linked with either Samsung or Google at all, and shows very poor knowledge on the situation at hand - basically laughs at people using 2G because apparently "no-one uses 2G anymore", even though a large portion of the UK only has 2G coverage...something he should've known had he actually been knowledgeable about the situation.
[Samsung Galaxy Nexus] w1nter456:
I don't know, but what I heard from internet, this guy quite reputable and he said that the 4.0.2 will fix the 2g problem if I'm correct, i forgotten about the link, but I will try to find it if possible, thanks for commenting.

However, I dislike this guy attitude what he said was "Using nexus in 2g area is like only driving your Indy car in school zones. Let your phone be free." "So the volume bug was fixed and will be out soon..but wtf are people doing using the nexus in a 2g area?"
[Samsung Galaxy Nexus] s.m.knipe:
Interesting, so why only the volume rocker? proximity to the/an antennae? The issue seems oddly specific when the volume up and power buttons should also produce interrupts. (I'm reading through the other, more speculative thread now, to see if this vein has been chased already)

EDIT: I see that it has indeed affected volume up as well... is the power button something other than an interrupt (since it is the I/O switch when device is off), and hence its apparent exemption?
[Samsung Galaxy Nexus] MysteriousDiary:
on the google issue tracker someone posted:

O2 have just rang me back to say that they recieved an email from google saying they are aware of the problem and will be issuing a software update withing the next 48hrs. I know from the above and other stuff ive read that its sounds like a hardware issue but i'm just relaying what ive been told.

But well, it's nothing official so we've to wait if it's true.
[Samsung Galaxy Nexus] Baldyman1966:
OK, this may seem like a stupid question but here goes. I am on T-Mobile in the UK which is GSM 1800, which should not affect the phone. Also in the video the guy is holding the GSM 900 phone right next to the Nexus, in a way that wouldn't happen in real life (unless you were using Android Beam).

So I ask, should I be safe from this fault? Is it ok to go ahead with my order or should I wait a while and see what Google/Samsung say?
[Samsung Galaxy Nexus] oscillik:
there have been a few reports by people in the bigger thread that they have encountered problems while a friend or relative has been walking past them, using their own phone in a call.

But you're right - T-Mobile doesn't operate on the 900MHz frequency that seems to be most likely to cause this issue.
[Samsung Galaxy Nexus] ErGo_404:
Is it possible to de-activate the 900Mhz frequency on the phone (and force 1800 ?). Both frequencies are available for each carrier where I live.

I'm not saying that I will buy the phone, I prefer waiting for a proper fix (and confirmation that the issue is REALLY gone, I don't trust Samsung :D ), but it might help other people to know that you can disable the 900Mhz frequency.
[Samsung Galaxy Nexus] Egan:
However, when someone near you calls over 900mhz it can still mess things up on your device.
[Samsung Galaxy Nexus] oscillik:
You can disable the internal cellular radio from receiving 900MHz bands, yes. But that is pointless, since the problem isn't affecting the internal radio, the problem is affecting the volume rocker switches. There is no way to tell the volume rocker switches to stop receiving 900MHz interference.
[Samsung Galaxy Nexus] ErGo_404:
Yes but this could be fixed by adding some kind of protective case on your phone. I know it is a lot of "if" and bad fixes but Samsung will have to admit the problem at some point and replace the units. Until then people will need a solution to their problem.
[Samsung Galaxy Nexus] oscillik:
nope, this is not the same as the iPhone deathgrip, it cannot be fixed by a case. it needs a hardware revision.
[Samsung Galaxy Nexus] ErGo_404:
If you prevent the 900Mhz waves to be sent from the inside of the device, and if you prevent them to come from the outside (using a proper shielding case ?), then the volume rocker will not receive any 900Mhz waves and will not act wierdly, or at least it could reduce the issue.

EDIT : and please don't assume that I don't understand the problem. You may not agree with a lot of people here and think they are all retards, but that doesn't mean that nobody is reading what you already wrote.
[Samsung Galaxy Nexus] oscillik:
but how can you prevent the 900MHz waves coming from the inside of the device by using an external case? you can't

the only thing that can stop that is internal RF shielding, which is what Samsung should have done. But they didn't. And this is why we're having this problem.
[Samsung Galaxy Nexus] ErGo_404:
Well if you say you can de-activate the internal radio on the 900Mhz frequencies, it SEEMS ok for me to say that no 900Mhz waves will come from the inside.
[Samsung Galaxy Nexus] oscillik:
ahhh yes, fair point.

That would work and not cause you any side effects if you happen to live in an area that either

1) doesn't use 900MHz at all

or

2) you live in an area where the 3G signal is sufficient that you'd never need to drop down to 2G

unfortunately for a large population of the UK, that is not the case :(
[Samsung Galaxy Nexus] ErGo_404:
Isn't 1800Mhz also a frequency used by GSM (and therefore 2G) ?

In France the 3 main carriers can use small portions of the 900Mhz AND the 1800Mhz frequencies, so even if you don't have 3G it may be possible to only use 1800Mhz and therefore avoid the problem, whatever the carrier.
[Samsung Galaxy Nexus] oscillik:
Maybe in France, I don't know?

All I do know is that there are currently 4 known networks here in the UK that have been confirmed to use 900MHz for their 2G coverage, those are: O2, Vodafone, giffgaff, and Tesco Mobile.

O2 and Vodafone are the top two networks with the highest customer base (the last time I saw, anyway...I could be wrong here).

You may have a different experience in France, but I wouldn't be able to comment on that - the last time I was in France, I was 11!
[Samsung Galaxy Nexus] chrisjaffe:
you can add Lebara to that list. But they use the vodafone network so it is a bit redundant.
[Samsung Galaxy Nexus] Clancy_s:
Things may be interesting when the first units arrive in Aus: 2 of the major carriers (Optus and Vodafone) use 900 MHz for their 3G.
[Samsung Galaxy Nexus] _Dejan_:
So is there way to disable 900MHz radio band on Galaxy Nexus and if is how?

My Carrier offer:

GSM 900 (902,50 MHz - 914,90 MHz, 947,50 MHz - 959,90 MHz)

GSM 1800 (1740,10 MHz - 1755,10 MHz, 1835,10 MHz - 1850,10 MHz)

UMTS 2100 (1900,00 MHz - 1905,00 MHz, 1965,00 MHz - 1970,00 MHz ..... 2155,00 MHz - 2160,00 MHz ..... 2165,00 MHz - 2170,00 MHz)

Also I would like try disable 900MHz radio on my Desire runing android 2.3.5 to see if I will get coverage at home where I don't have 3G coverage...
[Samsung Galaxy Nexus] oscillik:
I must apologise to everyone of you that I have smacked down regarding the 4.0.2 update that had looked to be specific to Verizon.

I just had a conversation with Romain Guy, Android engineer and he has confirmed that they are working on a software fix.

True to my word, I am admitting when I was wrong. I sincerely apologise for being so brusque with many users in this thread and others on this particular matter.

I still firmly believe that this is a hardware fault, however. But my apology here is regarding the 4.0.2 update that was mistakenly thought to be only for the Verizon version of the Galaxy Nexus.
[Samsung Galaxy Nexus] noobdeagle:
did he not reply after that ?, seems like its missing his explanation there at the bottom as to why its not hardware.

has me woundering now if i should just pull the trigger and get handtec to send mine :\

maybe they are going to try and change it with software, but just updating the android rom means there has to be a work around cause its still in the boot-loader before it actually boots into android.
[Samsung Galaxy Nexus] oscillik:
no, he seemed not to want to carry on discussing it as he had started talking about a different topic entirely.

i'm sure he probably said more than he should have anyway...
[Samsung Galaxy Nexus] PaulCayard:
IMHO this is a +1 for a sw workaround and not a sw fix.
[Samsung Galaxy Nexus] noobdeagle:
at least its a reply from a reputable person, i guess they will be pushing that out ASAP, so will be an interesting few days to come.
[Samsung Galaxy Nexus] oscillik:
indeed, this is certainly not a fix and seems more like a patch.

yes this is exactly my main reason for posting this info - This is the first word we've had from anyone working at either Google or Samsung on the matter, to suggest that someone is actually actively working on this.

It is just a shame that the first word had to be relayed from an IRC chat log pasted on the internet by myself!
[Samsung Galaxy Nexus] MattSkeet:
To be honest I can't imagine how this could be hardware related bug?

You don't hold the phone in any specific way like for example iphone antenna problem, and you don't need to do anything with the phone at all.

First of all it's the radio that changes settings that it shouldn't, so the software gets wrong readings triggering volume.

I believe that only update we are going to see will be either kernel or radio firmware not the ics Itself
[Samsung Galaxy Nexus] deyanp:
what about this then, is that also software related??:

http://www.youtube.com/watch?v=LjwMzooNVCE