yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gagaohlala:
Wow, want order it by a ebay seller in UK but I'm very disapointed by this issue ... I'm French and I use Orange simcard. This issue wiil hapene even i use orange in france ? I want it rapidely but if it's a HW issue, I can't order it ... Any ideas ?
[Samsung Galaxy Nexus] paul_one:
you son of a motherless goat!

haha, love the 3 amigos, that's what it reminded me of.

could be either right now.. We are waiting for word from Samsung and testing of some new devices from clove.
[Samsung Galaxy Nexus] escrivel:
Hm...is there a change that other batches from Samsung won't be affected by this bug? Could it be only the uk batch? (I know that is very unlikely!)
[Samsung Galaxy Nexus] wicksta1:
For those changing providers to avoid using 900Mhz, don't forget that if you're ever using the phone abroad and you roam onto a 900Mhz provider you'll have the same issue. Also if you do move it might be hard to prove to your new 1800Mhz provider that your phone has an issue when it's working fine on their network. Just a thought.
[Samsung Galaxy Nexus] Shodney:
I've stuck a few layers under my battery and been running it for about 10 minutes so far without an issue, but I guess it's too early to know if its had an effect for definite.

I'll keep it going and report back
[Samsung Galaxy Nexus] Tom Servo:
Can't wait for updates. Would be ****ing hilarious if a few layers of tin foil get the issue under control.
[Samsung Galaxy Nexus] matt2053:
I'm on T-Mobile in the states (850 band) so should not be affected, right?
[Samsung Galaxy Nexus] human_error:
Grr I had put my response in the poll that I had no problems, but I just told the phone to only use 2G and the button's spazzed out. Allowing it to use 3G again fixed it.

I'm on O2 and am in a perfect reception area for 2G, 3G and HSDPA.
[Samsung Galaxy Nexus] TonyHoyle:
It means the 'fix' might be picking up a free RF shield (aka. bit of tinfoil) from your local P4U. That's actually good news, compared to masking it with software or a full recall.
[Samsung Galaxy Nexus] Chirality:
Hard to say for now, there aren't any 850MHz GSM networks in Europe. We need somebody to test it in the US or test it with an RF generator that can produce 850MHz.
[Samsung Galaxy Nexus] oscillik:
a phone that cost you over £500 shouldn't need to have ghetto cheap fixes done to it at cost and effort of the buyer. The phone should just work as it was advertised, intended, and designed for.
[Samsung Galaxy Nexus] Tom Servo:
I agree. But it'd be a worthwhile fix, assuming it's effective, while you're waiting for a replacement device.

You guys should however clarify with your seller how things will be dealt with. Whether you'll be given a replacement unconditionally, or whether you have to return it within the time allotted in their policy (7 days, 14 days or whatever). Samsung might cheapen out and not do a recall.
[Samsung Galaxy Nexus] blunden:
True. However they could give you the option to fix it that way if you want as that would waiting, possibly for months, for them to manufacture new devices for everyone.
[Samsung Galaxy Nexus] burnduck:
do you think Samsung would spend a penny ship out new phones if the cheap "workaround" does work?

It's a flagship phone and it's supposed to work without any extra addon / fixes from users.
[Samsung Galaxy Nexus] oscillik:
I asked the O2 store where I bought mine from, and they have told me that even though this is my second handset, I only have 14 days

from the purchase date of the original handset

to claim a full refund, even if Samsung admit to a hardware design defect after this period. If the 14 day period lapses, all I would be entitled to would be a handset replacement (even though the Sale of Goods Act precludes any in-store policy regarding refunds).

I'm not willing to argue with them over my rights though, as it will only cause me to get insanely angry and abuse will spill from my mouth. I shall be claiming my refund before the 14 day period is over, and I shall just have to make do without a phone for however long it takes Samsung to manufacture a batch that isn't affected by this problem.
[Samsung Galaxy Nexus] Tom Servo:
Well, if you're lucky, the newer batches that arrived at SIM-free dealers might already be fixed. While Samsung didn't reply straight away when this started to happen, they came out saying that they were already aware of it, which gives at least a minimum of hope. I expected rhetoric along the lines of "We'll investigate this issue and report back".
[Samsung Galaxy Nexus] Shodney:
Well it hasn't solved the problem as, predictably, it happened just after I posted.

I can't say it has made much of a difference - perhaps happening with slightly less frequency, but the problem is still there.

I'll leave it in place and give it a run out tomorrow, to see if theres an improvement over this morning.
[Samsung Galaxy Nexus] TonyHoyle:
A phone call to trading standard wouldn't go amiss.. They can put O2 right on the law.
[Samsung Galaxy Nexus] Evostance:
Just tried tinfoiling it up.

Doesn't work
[Samsung Galaxy Nexus] HUNZwiebel:
So phones at Clove don't have this problem?
[Samsung Galaxy Nexus] Evostance:
I highly doubt Samsung put the phone next to a 900mhz frequency
[Samsung Galaxy Nexus] hydrasworld:
Just confirmed it on my Galaxy Nexus

My steps to repeat:

put a GiffGass (o2) SIM into SGS2

put a Vodaphone SIM into GN

disable Wifi on both devices

disable 3G on both devices

place both devices close to each other

load a web-page on the SGS2 (www.google.com)

watch in amazement at the volume turn itself down on the GN!
[Samsung Galaxy Nexus] Tom Servo:
If I understand that right, Samsung claims that devices went through an additional QA step to weed out "faulty" devices.

Well, you know how it was with the GPS in the Galaxy S devices...
[Samsung Galaxy Nexus] jms.flynn:
Hopefully this should be treated differently as this is also a flagship Google phone so there is just as much bad PR for Google as there is for Samsung.
[Samsung Galaxy Nexus] kristovaher:
This is very unlikely for these two reasons:

This problem was not reported anywhere before UK launch late last week

There have been only two workdays between the UK launch and the devices shipped to Clove and others

If Samsung knew about it, it is very likely they would have intentionally shipped faulty phones for launch.

It just makes no sense. The only way Clove and others do not have faulty devices if the entire problem is the fault of a faulty batch that was unknown before 17th and that Clove and others receive another batch that does not have this issue.

But this is very unlikely, this looks like a design oversight that Samsung did not test for.
[Samsung Galaxy Nexus] nikosrs4:
when did they say that?
[Samsung Galaxy Nexus] Love_Velvet:
Whilst i dont doubt you're correct, i think its also very likely samsung may well have known about the issue, but were not able to delay the launch of the phone, so they faulty phones were sold. Obviously knowing that orange and t-mobile customers would not be as susceptible to the issue.
[Samsung Galaxy Nexus] birdster:
Just had a confirmation email for three.co.uk that my phone is on the way for delivery tomorrow (22nd), hope this is there batch, and will report back tomorrow if it has the same defect!!! Fingers crossed here!
[Samsung Galaxy Nexus] mingoid:
So I have a Nexus I bought from 3 on PAYG (waiting for it to be unlocked so I can use on Vodafone). So I tried putting my Nexus One on on Vodafone 2G and loaded a web page with the phones right next to each other.

I didn't see any effect (volume changes etc) on the Galaxy Nexus. Does this mean my phone isn't affected?

Waiting to see if I should just take it back, was already unhappy because they told me I could get the GN unlocked then 3 Customer services couldn't because they didn't have the IMEI in their database.
[Samsung Galaxy Nexus] oscillik:
then they could be sued for fraud.
[Samsung Galaxy Nexus] Evostance:
Didn't actually realise how bad this was.

If Im on GPRS and I try to call anyone, the volume keeps dropping on my phone...

Its not constant though, completely intermittent

Wonderful
[Samsung Galaxy Nexus] electric0ant:
volume drops only occur one in every five or six times i make a call with an o2 iphone in 2g mode, so it's not that consistent but more then likely the issue is there.
[Samsung Galaxy Nexus] Love_Velvet:
Definately, but would anyone be able to prove if they knew about the issue? Im not saying that is the case, it could just be they realised when the phones had been shipped and couldn't do anything about it.
[Samsung Galaxy Nexus] oscillik:
as has already been mentioned many times, the problem is likely made worse if your phone is having to transmit more power via the cellular radio to latch onto the 900MHz 2G network. this explains why the problem is intermittent when testing using the handset's internal radio.
[Samsung Galaxy Nexus] mingoid:
I've tried more than 10 times, making calls on the Nexus One (2g vodafone) next to the 3 Galaxy Nexus with no effect. The OP says that the problem occurs even when the GN is using no radios.

I can't work out from this forum whether anyone else can't replicate the issue (i.e. whether some phones may be unaffected). Unfortunately, as I stated already my GN is locked to 3 so I can't try it on 2G itself.
[Samsung Galaxy Nexus] mhunt407:
Mine is doing the exact same! its a nightmare! Hopefully it gets sorted quickly.
[Samsung Galaxy Nexus] Evostance:
Regardless of if they know about it. They should still take it away for testing at least
[Samsung Galaxy Nexus] oscillik:
"The initial post says that the problem occurs even when the GN is using no radios." this is correct - the problem can be successfully replicated by having the phone either in airplane mode, or in bootloader mode.

you may be a lucky person in that you have a phone from a batch that isn't affected.
[Samsung Galaxy Nexus] Chirality:
It's possible that Samsung knew of the problem and fixed later batches. But rather than recalling the entire initial batch, they figured they'd let it get sold, and then they would only have to recall all those that were sold and used on networks that use 900MHz bands in the worst case, and can save money by not having to recall those that were sold to users who use it with non-900MHz networks.
[Samsung Galaxy Nexus] oscillik:
The Verge are reporting that O2 claim to have not received any complaints or exchanged handsets

That's funny...because I got mine exchanged today
[Samsung Galaxy Nexus] Love_Velvet:
I guess thats o2's way of saying nothing untill they've got more information from samsung/google. Frustrating, but common it seems.
[Samsung Galaxy Nexus] Tom Servo:
Companies always play down facts and numbers, if they put them in a negative light.
[Samsung Galaxy Nexus] sblantipodi:
and did you solved the problem?
[Samsung Galaxy Nexus] Evostance:
Bit you order online originally or in store?
[Samsung Galaxy Nexus] oscillik:
as I've already mentioned multiple times in this thread, no the problem still persists.

---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------

I bought it in the store.
[Samsung Galaxy Nexus] lightbulb115:
Bought from Phones4U Tottenham Court Road on 17/11/11, using Vodafone. Can also replicate the issue by holding my old HTC Legend nearby.

Have logged with Samsung as requested by them on their Facebook page. Fingers crossed for a speedy solution/working replacement.
[Samsung Galaxy Nexus] sblantipodi:
we have two phone here in italy (900MHz 2G) and we haven't been able to reproduce the problem.

what do you think?
[Samsung Galaxy Nexus] jms.flynn:
You seem well angry, wouldn't want to be the rep giving you your refund. :D
[Samsung Galaxy Nexus] qwerp_:
this is my latest test.

boot the phone into boot loader, without sim and battery (apparently it will run with power cable only).

and it still affected. prone area are the side where the volume button is and the place where the sim slots are.

so, i don't think any Faraday cage will solve the issue unless you wrap the whole phone up,

but if you can stop interference, doesn't it also stop the phone from getting signal? then what is the point?
[Samsung Galaxy Nexus] oscillik:
I think you have handsets from a batch that obviously weren't affected by this, which means that Samsung have knowingly sent out faulty handsets to the UK for sale.

I'm angry mainly because for the past two days I've had to deal with people on here ignoring the obvious signs of a hardware fault and continuing to claim that a software fix will sort it out. Not to mention people continually asking questions that, if they had read the thread (or even just the first post) they would have had their query resolved. Repeating oneself isn't something I like doing.

That said, if the person at the O2 shop even tries to claim that I am not entitled to a full refund, I shall bombard them with a rather vitriolic rendition of my rights as a consumer in the UK
[Samsung Galaxy Nexus] mingoid:
Aaargh. I just read the last post about the side with the volume control being more affected and tried again, and it IMMEDIATELY caused the problem. Nothing happened with my N1 on the right hand side of the phone sigh... OK, taking it back tomorrow.:mad:
[Samsung Galaxy Nexus] gambiting:
Guys, I honestly don't know what to do. I sent a message to Samsung just as instructed on their Facebook page, and I really hope to get my phone fixed/replaced. I would rather not get it refunded, I love it and I would like to just have it fixed. Is there any good argument for getting a refund,or should I just sit tight and wait for a reply from Samsung? I am asking because quite a few people in this thread have already requested a refund or are going to do so, and I am wondering what are their motives?
[Samsung Galaxy Nexus] oscillik:
I would personally advise you to get a refund, that way you can wait for confirmed reports of fully functional batches being sent out to retailers, and you can be sure that you will be getting a handset that works.

I have already had my handset replaced, and the replacement still suffers from the problem. I have had terrible experiences in the past with having expensive items sent out for repair, so I avoid it at all costs.
[Samsung Galaxy Nexus] kindiboy:
People should post their phones build numbers!

I don't have the phone so I have no clue how to get it, but you guys should figure it out (check where the serial number is, or the serial number there should be an indication), so when you go to get your exchange unit you would be able to tell from the build number if it's from the same batch or not.
[Samsung Galaxy Nexus] mingoid:
The problem is that Samsung may not act quickly to fix this and in the meantime you have a phone that may act up while doing almost anything.

I think we all suffer from mental stress when we invest so much anticipation into a device, pay a fortune for it and then find fundamental problems. If it was software I'd probably wait but that doesn't seem likely. In the meantime I'd rather hand it back over to them, get my money back and not suffer from the stress of wondering when it's going to be fixed, or receiving "fixes" that turn out not to work. If they fix the problem for certain I'll purchase it again, it otherwise seems great. Unfortunately it's likely to be a huge PR own goal for both Samsung and Google.
[Samsung Galaxy Nexus] mhunt407:
Following the advice from Samsung on their Facebook I have sent them an email to uk.technical@samsung.com

Also, I've put up an email template at

http://www.tekcore.co.uk/2011/11/samsung-galaxy-nexus-2g-erratic-volume.html for anyone interested in getting this issue rectified. We need to get noticed! Love the handset, just wish it wasn't plagued by this issue!
[Samsung Galaxy Nexus] Chirality:
It just occurred to me that since you can trigger the problem with arbitrary RF sources at the right frequencies, it shouldn't be limited to 2G signals. According to this: http://www.gsacom.com/news/gsa_267.php4 some areas of Europe are also using the 900MHz bands for UMTS (3G). Are there anyone here with the Galaxy Nexus using it on a 900MHz 3G network? If so the problem should be triggered even while using 3G, right?
[Samsung Galaxy Nexus] oscillik:
unlikely that the build number is tied to a particular hardware revision, although it couldn't hurt to note this down.

---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------

theoretically yes, although we need someone to test this to be sure. Since most of the people who have this phone at the moment are in the UK, and there's a large likelihood that only the UK has been sent affected handsets, we'll probably never know.
[Samsung Galaxy Nexus] Chirality:
Are there any UK networks that use 900MHz UMTS?
[Samsung Galaxy Nexus] oscillik:
O2 are apparently trialling HSDPA+ 900MHz in certain parts of the UK (i believe in London, although I'm not sure exactly where).

As far as I'm aware, they're the only network that are doing such things.
[Samsung Galaxy Nexus] juicytuna:
I have mine running on O2 and it doesn't have this problem (yet?).

Build number ITL41D
[Samsung Galaxy Nexus] whyamihere:
Probably not used 2G yet.

Switch off 3G for a while and see if it occurs.

Can also point another phone at it which uses the O2/vodafone network when using 2G.
[Samsung Galaxy Nexus] oscillik:
to clarify, you need to have your phone in 2G mode and be either actively in a call, or actively in a data connection transmitting/receiving data. If you're trying to perform the check on your own handset and you only have the Galaxy Nexus, the problem seems to be exacerbated by being in a low signal area - this forces the phone to increase the power to the cellular radio.

if you want to try the trick of using another 900MHz 2G phone to see if that causes the problem, make sure that you're in a call on that second phone and then hold the phone close to the volume rocker on the Galaxy Nexus. you should find that it causes the problem, even if your Galaxy Nexus is in airplane mode.
[Samsung Galaxy Nexus] MrTechie:
I have a theory:

Can anyone with this problem please try to reproduce it but with NFC Switched OFF!!

I havent had this issue at all but then again my NFC is always off
[Samsung Galaxy Nexus] gambiting:
I have the ITL41D build but I have this problem as well.
[Samsung Galaxy Nexus] juicytuna:
I tested by disabling wifi and enabling 2g in the mobile networks menu. I see E symbol by the reception bars while browsing. No SAV bug when doing this.

I'll try and test using a second 900mhz phone as soon as I can get hold of one and I'll report back with my findings.
[Samsung Galaxy Nexus] rob6raham:
NFC is not the issue. Mine has been off since I got it but experience the bug regularly. (Poor signal area).

Build ITL41D
[Samsung Galaxy Nexus] MrTechie:
Ok, If i enable 2G i get the same problem...

Scrap my NFC Theory... Luckily i love in london so havent experienced any of the issues!
[Samsung Galaxy Nexus] paul_one:
isnt there normally a hardware build or batch code on the box? would be good so that we can know which 'batch' is or isn't faulty. would also save oscillik from having to go through a further 20 replacements.
[Samsung Galaxy Nexus] oscillik:
nope, only information on the box is the barcode for the IMEI number, and the barcode for the SKU.

nothing on there to determine what batch or revision it is.
[Samsung Galaxy Nexus] Crazy CS:
So the general consensus is that this is a hardware fault?
[Samsung Galaxy Nexus] gambiting:
It must be, if another phone's signal is causing the issue even while the phone is in the bootloader mode.
[Samsung Galaxy Nexus] Crazy CS:
Then i guess i should cancel my order...
[Samsung Galaxy Nexus] her0n:
I have a feeling i'll be spending my Friday morning in the o2 shop I bought mine from, exchanging it for an HTC Sensation XE (my original choice of phone before the Nexus was announced in Hong Kong).

My 14 days is up on the 1st Dec. Not going to leave it until then, just in case my store doesn't have the XE in stock.

Big shame as the phone is great. I'd just like to be able to actually hear people during a phonecall! I actually took my unlocked 6300i (holiday phone! :D) with me to work today.. "just in case" I needed to swap the sim over.
[Samsung Galaxy Nexus] Crazy CS:
Outright stock from Clove and Handtec have apparently been tested more by Samsung and again by the retailers who can't replicate the fault.....
[Samsung Galaxy Nexus] juicytuna:
I've just tested the second method. I put my gnex in to download mode (volume down and power) and tested by putting my gs2 in 900mhz mode next to the volume rocker. I still see no SAV bug.

Btw, I saw some additional information about the phone in download mode:

board name : tuna REV 9

board rev : hspa - 9

boot type : usb mmc1

device type: hs

build date : oct 30 2011 12:32:21
[Samsung Galaxy Nexus] oscillik:
Yeah, don't leave it until the last minute. Nokia 6310i was probably one of the most reliable phones I've ever owned :)

If this is true, that means that Samsung have knowingly shipped out broken handsets to Phones4u, O2, and 3 stores. The first report of this problem happened late on Friday night. There is no way that Samsung could've gone from being clueless about this last week, to having new stock manufactured and sent out to retailers even before the first public report of the problem

that is unless they already knew....which it seems like that may be the case.
[Samsung Galaxy Nexus] nyyankees3511:
P3droid claims bug is fixed and soon will be pushed..

http://www.tweetdeck.com/twitter/P3Droid/~c0x5g
[Samsung Galaxy Nexus] juicytuna:
Appologies if this has been discussed but what is everyones build date? It can be found in the bottom left corner along with some other information when in download mode.

Mine doesnt have this problem and is showing a build date of Oct 30 2011 12:32:21
[Samsung Galaxy Nexus] sblantipodi:
who is p3droid and how it fixed it?
[Samsung Galaxy Nexus] Chrono_Tata:
Well take into account that review units seem to not have this problem either. It is possible that our batch was just the one faulty batch.
[Samsung Galaxy Nexus] kindiboy:
This is exactly what I said on the Verge....Clove contacted samsung about the problem, samsung said that the new batch went trough yet another QA process, yet clove didn't trust Samsung saying that they will do their own test on some devices to try and replicate the issue. On the other hand, handtec is saying that they are getting their phones from the same "new" batch that Clove is getting and yet they will do their own tests to try and reproduce the issue. So... I bet Samsung sold the first batch of faulty devices to people knowingly.
[Samsung Galaxy Nexus] oscillik:
there is no fix, it is a hardware issue and the only way to fix it is to replace the handset with a brand new one from a different hardware revision that doesn't suffer from the RF interference

review units wouldn't have been tested running in 2G mode on 900MHz networks, so your point is completely and entirely moot.
[Samsung Galaxy Nexus] jaketurbo:
Seriously whats the need for your attitude?
[Samsung Galaxy Nexus] gambiting:
Oscillik, to be perfectly honest, they can't fix the issue completely with a software update. BUT if they know what frequency specifically causes this problem,they can set the radio drivers to avoid that frequency and use other channels of the GSM 900 standard instead. This would stop the phone from generating the issue by itself, but it would still be prone to external interference from other handsets. Still, it might be more cost effective than recalling all affected handsets.
[Samsung Galaxy Nexus] Clancy_s:
That's an interesting thought: in Aus Optus and Vodafone use 900 MHz for 3G. If the new batch isn't fixed (I put limited trust in Samsung's 'extra QA') someone might get a chance to test that in a few days - our first GNs should be arriving here early next week.

I'm behind a firewall atm and can't access tweetdeck - if it's not against forum policy could you please quote him in full?