yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] BiGMERF:
the place where i preordered is expecting a batch next tuesday as the first shipment.. this issue actually has me thinking of telling them to skip me and give me a phone from the second batch that arrives on nov 30th

opinion?
[Samsung Galaxy Nexus] martonikaj:
They're probably all going to have the same firmware version.
[Samsung Galaxy Nexus] BiGMERF:
i see conflicting reports on whether it is hardware or software related.. has it been confirmed as software?
[Samsung Galaxy Nexus] drsoum:
seems it's hardware

ok been using my GN for a couple of days now. the problem happens enough to be annoying, though not to push me to buyer's remorse. i think it's hardware because the issue also affects Twicca, which scrolls down with the volume button. i would be going through my tweets and then it decides to very quickly scroll down. one time it got so severe i had to restart the phone.

didn't notice any correlation with network coverage or wifi, but i'll keep an eye out either way.

so it seems the OS thinks the volume-down button is being pressed. this is either a very weird bug that makes it think that the button is being pressed while it's not, or more likely a hardware bug. the only thing that nags me is that if it's hardware it should be more consistent.

i got the phone from phones4u on Oxford street, running the 4.0.1 FW. i might be extra screwed cuz i live in Dubai, so a hardware return will be a logistical nightmare to say the least.
[Samsung Galaxy Nexus] :
that suggests it MAY be more HW related

Make sure you add the info HERE

http://code.google.com/p/android/issues/detail?id=22021
[Samsung Galaxy Nexus] Evostance:
I've had the issue only once but didn't notice if I was on wifi

Its off because I didn't have any issues for 2 days. Rooted the phone and I got the issue but now its gone

I cant replicate it either
[Samsung Galaxy Nexus] qreffie:
I'm not too concerned about it considering the Nexus S had a random reboot bug that affected pretty much every user for several months until the second or third patch fixed it. All phones have some issue. We unfortunately live in a world of Beta now where the product released may still have a few glitches. I have complete confidence that Google will have that straightened out soon.
[Samsung Galaxy Nexus] kristovaher:
Well, this must be the worst case scenario: a hardware issue.

Not every handset suffers from this and it happens even with a phone with no custom applications installed and even after wipe and reset. This means that the problem is not with the applications user installs and must be an issue with the state phone already is in before being used.

Also, some users who have this problem are not having this problem after replacing the phone (while possibly using the phone the same way as before). It is unlikely that the replacement phone has a different Android version or different firmware on it.

It also happens to some users when they are 'brushing against' the volume button. This is definitely a hardware related issue when that happens, as it has nothing to do with software at the time because brushing against volume button should not send phone any signals.

It also happens during 2G/3G and WiFi switches, which likely have something to do with when hardware is being accessed.

There's still a chance that it is some software bug that only happens under certain conditions, like certain network, WiFi and so on, but it is very unlikely because some people don't have the problem after getting the phone replaced while they likely use the phone in the same environment.

This seems really bad and I'm thinking about canceling my pre-order in fear of a broken batch.
[Samsung Galaxy Nexus] kristovaher:
Important notice:

Samsung is hiding peoples posts on Samsung UK Facebook page about the problem.

My friend posted on Samsung UK page the Eurodroid article and asked if he should cancel his pre-order and while I saw it at first, it was hidden later on. However it is still visible for him. It is possible that if you have posted on Samsung UK page about the problem then it is simply not visible to everyone else anymore.
[Samsung Galaxy Nexus] gogol:
This is getting ridiculous.

What is the address of this Samsung UK Facebook page?

Anyone know phone numbers of their official customer support.

Start calling them next Monday.
[Samsung Galaxy Nexus] kkh786:
I have been trying to replicate this not having any success (thankfully).

Got my handset from O2 (delivered 18th Nov).

I am hoping it is software related though. Fixable! :)
[Samsung Galaxy Nexus] kristovaher:
https://www.facebook.com/SamsungUK?sk=wall
[Samsung Galaxy Nexus] 318vert:
Everyone needs to post on their facebook page. I have
[Samsung Galaxy Nexus] jaketurbo:
Weird behaviour here...

Orange sim card, fine whatever the 3g/2g connectivity.

Vodafone sim card, volume decrease behaviour.

Weird.
[Samsung Galaxy Nexus] saquib:
When the HTC Sensation was first released, quite a few users experienced issues with touch screen becoming unresponsive, including me. In the end this issue was found to be a grounding issue between the removeable battery cover and the internal housing. Bending or adding a little foil to a grounding point fixed the issue.

Can see this being a hardware issue truthly, but not sure if we'll as lucky to find a fix that we can implement ourselves.
[Samsung Galaxy Nexus] groove200:
yup im having this volume problem as well.....randomly muting itself. Earlier it was resting in my palm and the thing was going crazy, volume slider on screen popped up and was flickering and the phone was buzzing as it went mental for a few seconds. other times i'm holding it and i feel it buzz, check he volume and sure enough its muted itself.
[Samsung Galaxy Nexus] marky9074:
This is turning into a typical XDA thread. Surprised a mod hasnt vaped a load of these pointless posts.. maybe they spend all their time in developer threads..

...back on topic. All of this stock will have been shipped by container. That means they would have left 3~4 weeks ago. So unless Samsung can travel back in time and fix faults, then the latest batch is highly unlikely to be fixed..

Kudos to oscillik, OP and others for sticking with this thread..

Has anybody spoken to Handtec yet, as this is who my order is with...
[Samsung Galaxy Nexus] neovisage.HD2:
I have mine from phone4u worthing i been playing with the phone for nearly all day no issue yet,touch wood lol
[Samsung Galaxy Nexus] Tom Servo:
This might have been a manufacturing fault that Samsung detected and corrected, but deemed not critical and shipped the impaired devices anyway. This happens all the time in any industrial sector. You wouldn't wanna know how much flame retardant cables my company let go, that wouldn't come close to its promises.

Also, let me tell you about this concept of cargo planes...
[Samsung Galaxy Nexus] romerjon:
Which carrier are u using? Did u try to reconstruct the error?
[Samsung Galaxy Nexus] marky9074:
Would you like me to explain the difference in cost between shipping by plane or container ship? Granted, it is possible they are shipped by plane.. but highly unlikely..
[Samsung Galaxy Nexus] Tom Servo:
Ships gobble up oil like hell, and there's a crew that wants to be paid for all these weeks. None of that exists for a plane. If we can send people for chump change all over the place in a plane, you'd think they can do so with a bunch of pallets with phones. At least for initial seeding anyway.
[Samsung Galaxy Nexus] marky9074:
Again, would you like me to explain the difference in costs between shipping by container or air....
[Samsung Galaxy Nexus] kristovaher:
Seriously, could we stop arguing about pointless details? None of us know what Samsung are doing.

Reality is that in a day or two time we'll know if the SIM-free handsets shipped by Handtec and Clove and others are affected by the same problem or not. If not, then the UK release last week was with a faulty batch. If SIM-free handsets are affected, then there was no difference in batch or all currently manufactured handsets suffer from this problem.

Who cares how Samsung shipped the devices.
[Samsung Galaxy Nexus] chandlerweb:
Lets not get distracted by petty arguments. There is sufficient reason to doubt whether Clove and Handtec stock have been tested specifically for the sound issue on the basis Samsung never explicitly said it was tested for that, just that it had undergone extra testing. They didn't even say they and fixed any known issues so testing on its own is not a solution, just some added assurance. We will only know the true outcome once People get their handsets and can check it themselves. We should leave it at that for now.
[Samsung Galaxy Nexus] electric0ant:
I'm guessing you are on 3 since given the logo on your profile?

3 users are much less likely to see it happening unless you manually introduce the GSM900 interference using another phone on 2g as 3 does not use that freq.
[Samsung Galaxy Nexus] WhiteHartMart:
I've tried manually introducing interference using my wife's Vodafone phone using 2g and still can't get the problem to occur - wonder if this is just batch related?
[Samsung Galaxy Nexus] jmbillings:
I'll try it when I get home. I've certainly not observed it yet, but tbh most of the time in on Wifi as I only get 2G where I live!

Mine was a P4U handset, ordered online (so came from a warehouse somewhere, not a shop)
[Samsung Galaxy Nexus] nafem:
Bought from Phones4U last Friday. Using Vodafone SIM - Affected

Bought from Phones4U last Friday. Using Vodafone SIM - Affected
[Samsung Galaxy Nexus] HUNZwiebel:
Anybody tried with the unlocked Galaxy Nexus? Has the problem?
[Samsung Galaxy Nexus] qwerp_:
i made one of the video and my GNexus is a unlocked one.
[Samsung Galaxy Nexus] 318vert:
Doesn't matter if its locked or unlocked the problem will still occur.

All phones4u new contracts phones are unlocked

All carphone warehouse phones are unlocked

Mine is a phones4u contract unlocked and i have this issue.
[Samsung Galaxy Nexus] swine...:
I'm on Orange so do not have the problem - but understand I will if I use Vodafone etc, which I will do at some point. I've decided to email Samsung to ask them what they intend on doing - if I've not heard back from Samsung by tomorrow PM, Phones4U will be getting a call and the phone will go back to them....

Gutted as this phone is perfect for me in every other way....
[Samsung Galaxy Nexus] Phrive:
Just spoke to Samsung over the phone, they said they are aware of the issue and it is being investigated.

Not very helpful if I'm honest, they have taken my postcode/address and contact details not sure what they are going to use them for, but was told they will call me back when they not what is going on.
[Samsung Galaxy Nexus] kojaraty:
Does it have the same problem ,can you provide the link of the video?
[Samsung Galaxy Nexus] eXtremeXJ:
Ok this only happens to me when i hold it is a very specific position and im wondering if it has anything to do with the three contacts on the right side of the phone. It usually happens when im texting with two hands on the phone. Just for the hell of it im going to put a bit of tape over the contacts to see if it occurs again.

---------- Post added at 09:43 AM ---------- Previous post was at 09:38 AM ----------

Nope nothing to do with this
[Samsung Galaxy Nexus] qwerp_:
here you go

http://www.youtube.com/watch?v=y_mO_K7OYR0
[Samsung Galaxy Nexus] phillipm:
They said they would get back to me 16 months ago when I phoned them with regards to my GPS problems, still waiting for them to return my call, still GPS is rubbish.
[Samsung Galaxy Nexus] HUNZwiebel:
Ok thanks. Anybody who bought it from Clove today? :(
[Samsung Galaxy Nexus] escrivel:
Don't know if you are aware of this:

Version 4.0.2 was rolled out this night. Some users are reporting that the bug is now gone.
[Samsung Galaxy Nexus] qwerp_:
where did you get this news from?

do you have the link to this upgrade?
[Samsung Galaxy Nexus] Matcarroll:
I have been at work in a different location this morning and it hasn't happened yet. My data has been switching between 3g and h. Yesterday is was 3g and e. I know e is 2g and 3g is 3g. What's h?
[Samsung Galaxy Nexus] noobdeagle:
H is like 3.5G or some places call it 4G, but its not as fast as 4G LTE

i think its HSDPA+

yes EDIT: H = 3g, H+ = 3.5g
[Samsung Galaxy Nexus] :
H=HSDPA, 3g
[Samsung Galaxy Nexus] dg1qkt:
If this really was the case it should still appear in bootloadermode.
[Samsung Galaxy Nexus] oscillik:
it is hilarious how quick some people are to believe that this fault is fixed by a software update when we have shown various proof that this fault is hardware related.

let me reiterate this for those of you who are gullible - this

hardware

fault cannot be FIXED via software, at best it can only be patched to alleviate symptoms in Android, but even if that is possible: the phone will still be susceptible to RF interference from 900MHz due to improper RF shielding
[Samsung Galaxy Nexus] escrivel:
this post:

http://xdaforums.com/showpost.php?p=19582328&postcount=71

Additional there are a few users which reporting that the bug is gone now.
[Samsung Galaxy Nexus] oscillik:
this information is completely irrelevant because this 4.0.2 update is for the Verizon version of the Galaxy Nexus, whereas this problem is affecting the HSPA+ version of the Galaxy Nexus.

get your facts straight.
[Samsung Galaxy Nexus] escrivel:
Your right, no doubt. But maybe not everybody is accepting that this bug cannot be solved. I wish that there can be a solution. Otherwise for me there will be no Galaxy Nexus!
[Samsung Galaxy Nexus] oscillik:
You are perpetuating false information. Stop spreading false information.
[Samsung Galaxy Nexus] dg1qkt:
Would you really like to have a patchwork phone, where the problem is hidden?

Like the additional bars fix for apples atennagate?

Only possible fix is hardware and the last smal chance we have is that the batches clove and so on get are ok.

Hope dies last ...
[Samsung Galaxy Nexus] oscillik:
a hidden problem is not a fixed problem.
[Samsung Galaxy Nexus] dg1qkt:
exactly, so lets hope for a faulty first batch, thats our last chance
[Samsung Galaxy Nexus] atomic_dude:
I'll keep an eye on this

http://www.samsung.com/uk/consumer/mobile-devices/smartphones/android/GT-I9250TSAXEU-support
[Samsung Galaxy Nexus] oscillik:
unfortunately that page, as can be expected from Samsung, is as much use as a chocolate teapot.

If you click through the sections (Downloads, FAQs, How-to guides, Troubleshooting) you will find that most of the information is not even relevant to the Galaxy Nexus but is referencing the Galaxy S line.
[Samsung Galaxy Nexus] qwerp_:
by the way,

i just made another test.

for those that uses 3G network, you are not entirely save as well. you are just by passing the 2G interference from you own handset.

i have replace my SIM with a UK 3 card. (on WCDMA only).

introduce interference from a 2G o2 phone call, the vol goes funny again..

so for whoever wants to try out. find a o2 phone, switch it to 2G mode only, make a phone call and place it close to the volume rocker...
[Samsung Galaxy Nexus] jhericurls:
If its hidden, then its no longer a problem :confused:
[Samsung Galaxy Nexus] go2mo2:
God don't say that, there's going to be loads of arguments now lol
[Samsung Galaxy Nexus] WhiteHartMart:
If its hidden, the problem hasn't gone away and we don't surely know what affect it might have on other aspects of the phone?

If Samsung try to hide this away then my phone's going back under the Sale of Goods Act.

**lol - see what's started now!!
[Samsung Galaxy Nexus] oscillik:
this was already proven to be the case when the test was conducted while in bootloader mode.

you are gullible, and I question your ethics as an adult. "Out of sight, out of mind" is not an acceptable way to deal with problems.

If the problem is 'hidden' with a software patch, that means that the CPU on the handset will be working overtime to compensate for the hardware fault. This will result in a significantly slower handset and significantly lower battery life.
[Samsung Galaxy Nexus] qwerp_:
oscillik, yes i know, but for those that is on the so call by pass "fix" forcing on 3G network or other carrier on 3G band only, the problem is still there and can be triggered by someone on a 2G network making a phone call near to you.

thats is the message what i am trying to pass on.
[Samsung Galaxy Nexus] oscillik:
granted, there are some people participating in this thread that have a few more chromosomes than the rest of us, and obviously need things reiterating to them again and again.
[Samsung Galaxy Nexus] justabrake:
it's funny google wanted no problems with apple on this phone but they might be in for a class action lawsuit :)
[Samsung Galaxy Nexus] Hosh0:
You know, if you are going to bang on about how much smarter you are than other people then you might want to get basic grammar right. You have provided a lot of useful information in this thread as have others and I know it can be frustrating repeating yourself, but if you don't have anything to add other than a personal insult, there is no real need to say anything...
[Samsung Galaxy Nexus] Udaw:
Does Every Nexus have that problem ?
[Samsung Galaxy Nexus] oscillik:
You're not the one who has spent hours trawling through the comments in this thread and others, trying to put right the misleading information that people keep perpetuating in here.

So forgive me if I am more than frustrated when all those hours put into this thread and others have been whittled down to absolutely nothing during the time that I have slept.
[Samsung Galaxy Nexus] qwerp_:
we cannot be sure. but we are pretty sure that the first batch that was launch in UK since 17th seems to be affected.

not sure about others and there has not been much confirmation from others.
[Samsung Galaxy Nexus] gregounech:
I am going to get my Galaxy Nexus on Three today, should I still buy it as I will use it on three or wait for new batches of Galaxy Nexus without this problem ?
[Samsung Galaxy Nexus] Shodney:
How about we all sit back and wait for the Samsung engineers to sort the problem out?

I mean, they built the thing. They should know how to avoid the problem, right?

Oh, wait... ;)
[Samsung Galaxy Nexus] oscillik:
i would advise to wait until there is confirmation that stock exists in shops that is not affected by this.

all indications point to the current stock in the UK being affected by this hardware defect.
[Samsung Galaxy Nexus] escrivel:
We here in Germany putting all our hopes on a fault-free batch. Maybe the UK batch was really bad? Just think about the dev Galaxy Nexus which was sold!
[Samsung Galaxy Nexus] 4nt:
I thought I was lucky and didn't have this problem, today it went totally wild shifting itself back and forth quickly, glad I didn't have headphones in!
[Samsung Galaxy Nexus] Evostance:
Ive got until next Wednesday to call O2 and tell them I want to cancel my contract if Samsung haven't announced a fix.

If Samsung don't fix it by then, I will cancel my contract and buy it outright and keep swapping until I get a fixed one :)
[Samsung Galaxy Nexus] andrew.k:
We here in Russia also put our hopes on you German fault-free batch :) since Russian launch has not even been announced. But frankly, the hope is quite subtle. The problem really looks like an engineering fault rather than a batch production flaw.
[Samsung Galaxy Nexus] gogol:
We here in The Netherlands also put our hopes on you Russian fault-free batch who also hopes on German fault-free batch ... so, finger crossed! :)

I am pretty sure, this is fixable by the way.

Probably there is wrong logic in their software for handling this kind of signals, that's all.
[Samsung Galaxy Nexus] oscillik:
please read the thread. your assumption is wrong. this cannot be fixed unless a new hardware revision is manufactured by Samsung.

the hardware defect may be able to be patched in software to hide the issue from the software, but this would be at detriment to battery life and performance.

This is by no means a fix.
[Samsung Galaxy Nexus] basketor:
What proves the fact that it does it even in plane mode or in bootloader mode ?

Does it really proves that any wireless capability is off ?

Isn't Jack Bauer removing the battery of it's phone even when it's off to be sure to not be tracked ?

Aren't the CIA supposed to be able to trigger our phone on and listen it at any time ? :D
[Samsung Galaxy Nexus] gogol:
I did read the thread, but there is still no solid conclusion about the root cause.

All those conclusion are just "assumptions" or "opinions" from you and others.

You can call me stupid or anything for not believing you, but that's up to you :)

From my understanding, there is still possibility for wrong logic on software / firmware which handles that "event".

I won't rule that out :)
[Samsung Galaxy Nexus] rob6raham:
Just spoke to O2. They're not briefed on any fault and the techies think a recovery would fix it. They offered me a new handset and I tried to explain what at already been discovered about it. Useless.

Worth calling though as I read an article saying O2 had received no complaints...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] oscillik:
this video proves that the hardware fault occurs in bootloader mode

this one proves that it happens in airplane mode

the very fact that you are referencing a fictional television series proves that you are not qualified to take part in technical aspects of this discussion.

there is solid conclusion on the root cause - 900MHz RF interference causing electromagnetic interference with the volume rocker switches because the phone has not been RF shielded properly. there is no firmware or logic software in play here, since the volume rocker switches are sending hardware interrupts directly to the CPU.

this is a hardware defect.
[Samsung Galaxy Nexus] Evostance:
Just had a reply from Samsung

:confused::confused::confused:
[Samsung Galaxy Nexus] oscillik:
Samsung are clueless.
[Samsung Galaxy Nexus] veper:
The problem is that the phone itself (the hardware) shouldn't have been prone to RF interference, ie. the "event" you're referring to shouldn't happen at all.

Anything you do to bypass the problem will result in penalty somewhere (more CPU utilization, less battery time, etc.).
[Samsung Galaxy Nexus] gogol:
The interrupt handler is a piece of software ... In PC era, it is in the BIOS, which can be overwritten. Probably they will be able to "patch" that.
[Samsung Galaxy Nexus] oscillik:
you are wrong. as I have already mentioned in a previous post, the volume rocker and the power switch are akin to a PS/2 keyboard for PCs - the interrupts are handled at the CPU level. If you had bothered to read the pertinent post confirming this you would understand.
[Samsung Galaxy Nexus] erbain:
Some people in this thread are very sure of themselves, I don't claim to know what the fix for this bug will be, but I don't see any reason at this point to believe it can't be fixed at the driver level with little to no impact on battery life.

I'm not saying that is possible because I don't know, If I were to state that as a fact I would be making as big an assumption as the people stating only a hardware fix is possible / acceptable.
[Samsung Galaxy Nexus] jimilikesjuice:
I haven't come across this issue myself. The only problem I've noticed is a lag when typing. It only happens when there's more than one line of text and it does it in SMS, Email and the XDA app...I have informed Samsung and am awaiting a response
[Samsung Galaxy Nexus] go2mo2:
+1
[Samsung Galaxy Nexus] paul_one:
hahaha, that samsung email is just useless.. why even offer an email address in that case?

I see no real updates have come about. Samsung/google have given no word and handtec/clove have given the ol' "we can't replicate the save ghost" (with no proof of their testing procedure).

Friday inclusive, it's been just about 48 hours since things started circulating about this.

If this carries on, I hope all of us will talk with our money and buy something else more worth our money.