yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dg1qkt:
Nobody doubts that this is possible but this won't fix the problem. The interrupt will still be sent, cpu will still stop and calling the handler.

Which will result in non resposive ui if several hunderts of these interrupts are sent to cpu.

And it will wake up your phone from deep sleep resulting in low battery life.
[Samsung Galaxy Nexus] Evostance:
Thats an Android bug. Put it on their bug tracker
[Samsung Galaxy Nexus] ref1ux:
It's a shame this issue has appeared, because otherwise the phone is excellent.

Samsung have asked me to provide them with my IMEI, serial number, phone number etc. but tbh they seem pretty darn clueless :mad:
[Samsung Galaxy Nexus] oscillik:
if you cannot see any reason to believe that the fault cannot be fixed with a software fix then you are mistaken

this hardware defect cannot be FIXED by software, it may only be PATCHED which is completely different

even IF a patch can mask the effects of the hardware defect, the phone will suffer from performance issues and decreased battery life.

this is a hardware defect and the only way to fix it is to manufacture handsets with revised hardware that have the requisite RF shielding
[Samsung Galaxy Nexus] basketor:
I think it only proves that you have no sens of humor
[Samsung Galaxy Nexus] oscillik:
nice way of dodging that you were wrong.
[Samsung Galaxy Nexus] Mehrsau:
@oscillik:

We read your statements now about 1027310 times. It's getting boring.

Unless you are an engineer, working close on the Galaxy Nexus under the head of Samsung, I don't believe you that this needs essentially to be a hardware problem. Ever heard of baseband or firmware? There are uncountable possibilities in the software which could result in such a behavior.

So I would advise you to get a life. Who is paying you to convert us, the dumb users? You have your opinion, we have ours.. every one for their own.
[Samsung Galaxy Nexus] go2mo2:
Jesus we can all see he was joking
[Samsung Galaxy Nexus] M2281088:
I got that stupid responce from Samsung too. I think they were hinting you may need to ring them ;)

I have done that myself and have logged it with them...heres hoping that something happens soon.

The general feedback was, we will ring you back once we have any thing to say. You can return the phone within 28 days of sale if you wish.
[Samsung Galaxy Nexus] oscillik:
There are not uncountable possibilities in the software which could result in such behaviour. You are wrong. This is a hardware issue. If you are too blind to see that, then that is your prerogative.
[Samsung Galaxy Nexus] jimilikesjuice:
Ah, ty Evostance
[Samsung Galaxy Nexus] Mehrsau:
God damnit! The sky is purple! LOOK! The sky is purple! If you don't believe you are just blind! You argue like a 12 year old girl, not believing her parents that vegetables are healthy.
[Samsung Galaxy Nexus] go2mo2:
You know what im sick of seeing? That statement right there.... you are wrong. Sir your arrogance is astounding. I won't deny you have done great work in helping to identify the fault, but to suggest that you know it all is very silly. Just my opinion.
[Samsung Galaxy Nexus] kristovaher:
Please stop arguing! This serves no purpose. This thread is meant to give a way for people to report and describe their problem, if they have it, or if they do not have it.

I've written objective summary of these posts here a long while ago already and it is as the first post of this thread. Nothing, at all, has developed in the last ten or twenty pages of this thread.

YES, this is a hardware issue. It is proven countless times that the flaw is in handset hardware.

YES, it might be possible to be patched with software, firmware, driver update by a hack, making the phone 'ignore' these signals. It does NOT fix the problem, but it makes it less evident in the device. NO it is not an ideal solution by a long shot as it might still cause other issues, such as an unresponsive system for a short time.

YES, this is Samsungs fault. We will either face a mass-recall, or that very hack by Samsung.

Unless someone has something new to report, can we move on from this? I know we are all tense about the whole situation by having paid a lot of money for a device that has a major flaw, but first let's see what this current week will give us. If SIM-free devices also have the issue, then I believe that mass-recall will happen instead of Samsung releasing a 'hack' that fixes the problem.

We can speculate, but we do not know.

Just, please, I don't want to keep reading the same arguement over and over and over again.
[Samsung Galaxy Nexus] M2281088:
I am an engineer working in a similar field. I do not represent either party in this problem BUT I do support Oscillik's case.

This IS a hardware issue and the problem in my opinion, as that is all I am allowed to give, correctly identified as induced electrical stimulus from a radio signal or around 900MHz range.

This will require a hardware fix as, once again, Oscillik has pointed out. Any firmware will overcome the issue but will have an advese affect on performance and battery life.
[Samsung Galaxy Nexus] Evostance:
On the phone to them now. The woman is clueless

They've just taken the same details I emailed them and said they'd call me should they figure it out :cool:
[Samsung Galaxy Nexus] oscillik:
your silly analogy is incorrect for the following reason - there has been various examples of proof to show that this is a hardware fault

1. The problem only occurs from RF interference encountered from the 900MHz GSM band.

2. The problem exhibits itself when in airplane mode (while all radios are turned off) and when in bootloader mode (which only accepts input from the volume rocker and power switch at the hardware interrupt level)

You know what I'm sick of seeing? People who have no understanding of the fault at hand and who are making assumptions based on nothing that this is a problem that can be fixed by software, when there is evidence to the contrary.
[Samsung Galaxy Nexus] stiffn:
I purchased my phone SIM free from Phones4U on Saturday and I get the fault all the time - my home address is in a 2G area only.
[Samsung Galaxy Nexus] oscillik:
thank you for backing me up.
[Samsung Galaxy Nexus] paul_one:
I believe he's talking about the clove/handtec ones, sold by themselves in a 'sim-free' state.. whereas you'll usually get a sim with phones for you.
[Samsung Galaxy Nexus] phillipm:
I ordered my Nexus from phones4u and I just tried to cancel it with them but it has been posted.

I let them know about my concerns but the friendly customer services woman told me they have not been informed about this problem from manufacturer.

Wonder how many people got this phone that isn't on Orange/3g that are having this problem and not kicking off?! you think they'd not have time to answer the phone with the complaints they are getting.

Anyone from phones4u on this forum?
[Samsung Galaxy Nexus] Evostance:
You know when you put your phone near a radio and you get the interference noises? That's exactly what we're seeing here, apart from its with mobile signal not radio signal.

How do you fix the radio interference from a phone? Shield it. Updating the software doesn't fix this
[Samsung Galaxy Nexus] go2mo2:
Im not saying you or they are right or wrong, what im saying is why go over the point again and again? We've seen your views and theres, no need to keep hammering the same point
[Samsung Galaxy Nexus] stiffn:
No SIM given to me from P4U just the sealed boxed phone which I popped my O2 SIM into.
[Samsung Galaxy Nexus] erbain:
I'm not mistaken I just disagree with you, they are not the same thing.

I don't disagree that a software fix might have side effects, however there is at this stage no reason to believe that the side effects of the fix will have any meaningful impact on performance or battery life.

I think you'll find a software patch that makes the problem go away with no other noticeable side effects would be a fix in most people book.
[Samsung Galaxy Nexus] oscillik:
because as soon as someone starts talking about software fixes, driver fixes, baseband fixes, patches.....people start believing that this will resolve the problem.

completely baseless speculation is counter-productive to this issue.

the predication that this is a hardware fault is founded in a reliably reproducible capacity among those handsets that exhibit the fault. the theory that this is a hardware defect is rooted in reproducible evidence. the theory that this is a fault that can be fixed by software is completely baseless.

---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------

from your perspective, you have no reason to believe that the side effects of the fix will have any meaningful impact on performance or battery life because you either haven't read the whole thread and understood the implications, or you are just ignorant of the technicalities involved in trying to filter thousands of CPU hardware interrupts by using software logic.
[Samsung Galaxy Nexus] MatthewPL:
I only register here because I have enough people saying that oscillik is arogant. How would you feel when some people cannot understand that this is hardware, not software issue? I am software engineer (working on embedded systems) and I have few friends hardware engineers. And yes, we think that this is hardware problem. Why? Kristovaher told you. I can only add that it could be software you probably should recreate this on any other phone with ICS. You won't be able. Firmware? No, because everyone knows that there is something like GSM 900 and they should set firmware to avoid it. Why they didn't that? Because they cannot. It is like you have two cable with electricity (or better: network rj-45 cable). If they close enough they will interfere with each other (electromagnetic). And this is it, GSM 900 waves interfere with Galaxy Nexus hardware because lack of shielding.

It is not like iphone antenna problem, it is much worse.
[Samsung Galaxy Nexus] Evostance:
You mean like the Antennagate fix where Apple just changed how the signal bars were calculated? Yeah great fix

Lets say the issue occurs at 900mhz, if the put out a software fix to 'ignore' 900mhz, your phone will just not have any signal. This means it will also be using extra battery power.

You can't fix a hardware error with software.

If your car was misfiring and kept giving out errors everytime it happened, you would expect the manufacturer to just upgrade the software in the on-board computer to not log the error would you..

The issue is still there, its just not getting reported. That is not a fix
[Samsung Galaxy Nexus] go2mo2:
I understand, but that is their opinion, and i don't see why you refuse to let other people voice their opinions without you repeating your posts straight after them
[Samsung Galaxy Nexus] Evostance:
Because those people that post their opinions haven't even read the very first post of the thread!

If they read that post then they wouldn't have their opinion because they would understand!
[Samsung Galaxy Nexus] paul_one:
do you not understand that a hardware button sends an interrupt to the cpu, waking it up, forcing it to evaluate the button press?

This would have impact in performance and battery life as the cpu would never relax.

you can keep your head is the sand all you want, but i would rather everyone gets a better phone - even you.
[Samsung Galaxy Nexus] go2mo2:
Forget it.... im out
[Samsung Galaxy Nexus] oscillik:
it is not opinion. it is fact, as has been proven multiple times by others in this thread.
[Samsung Galaxy Nexus] bleets:
after watching this thread to see if there's any kind of real news and seeing oscillik constantly spamming/repeating the same thing/trying to be a foreman with a wikipedia based level of technical knowledge i just thought i'd weigh in with something nobody has actually decided to realise...

How much RF shielding do you think goes into your every day smartphone?

I cna pretty much guarantee that it's a lot less than you'd let yourself realise (practically none on a vast majority of components.)

Something is a bit different about the nexus though in that it has a pentaband WCDMA radio (aswell as the quad band GSM)

Dont know if that's affected things somehow
[Samsung Galaxy Nexus] oscillik:
Okay, lets put this in simple terms

When the handset is in

airplane mode

, all radios are turned off. This means the WiFi radio, the cellular radio, the Bluetooth radio, and the NFC radio. All turned off.

Since, for all intents and purposes, when in airplane mode the phone essentially is no longer a phone and cannot identify any external signals due to there being no radios switched on....

how can the software see a 900MHz frequency?

Simply put - it cannot. This proves that the fault is electromagnetic interference at the hardware level, with the volume rocker switches.
[Samsung Galaxy Nexus] her0n:
I've just booked tomorrow afternoon off work so I can go and get mine exchanged for a Sensation XE.

Gotta love flexitime, accruing extra hours and a nice line manager :D
[Samsung Galaxy Nexus] erbain:
Well technically that's already happening so a driver level fix to ignore strange interrupt patterns wouldn't make the battery life any worse, it just wouldn't make it any better :)

My head's not in the sand I just don't like seeing people being ripped apart by people that KNOW what the problem is and what the fix is. The only thing I'm reasonably sure about is nobody knows what the acceptable fix will be.
[Samsung Galaxy Nexus] gogol:
Easy ... if you believe this is hardware issue, just send back your phone for refund.

Then wait couple of weeks or months till new batches come out which don't have this issue, re-purchase ... and you are done!

You see? That's simple!

All right? So, stop fighting for something you don't know ;)
[Samsung Galaxy Nexus] paul_one:
this is starting to go off topic so I'll just say I'm the customer, and I say what's 'acceptable'.. :-)

and quite true about the battery/performance, it doesn't make battery or performance worse, that's the underlying hardware fault that does that.

my reference to head in the sand is trying to 'believe' or argue opinions in a fact based argument.
[Samsung Galaxy Nexus] escrivel:
Well better watch out for a SGS2 or a Razr. I think they are both better.

@topic: Clove is shipping their devices. So the have tested them and no Fault?
[Samsung Galaxy Nexus] gambiting:
I got a reply from Samsung, I "guess" they wanted me to call them as the message was quite unclear, but I called them, had to report the fault again, gave them my phone number and address, they said that they will call me within the next 5 days. And I have to say, the lady I was speaking with had absolutely no clue what is going on. She just wrote down the report and said she will forward it to their technical support team. I will go to Phones4U today, acknowledge them that I have this problem and that I contacted Samsung, and depending on the Samsung's reply I might want to request a refund.
[Samsung Galaxy Nexus] Tung_meister:
I wish Samsung would hurry up making an official announcement regarding the issue and how they intend to resolve it. I'm sick of how ridiculous this thread has become, I go away for a few hours and return to another 5+ pages of pointless arguing. At this point all we can do is wait to see what is said the arguing is not needed!
[Samsung Galaxy Nexus] jms.flynn:
Just took my nexus back to P4U and got a full refund, feel a bit sad because it was such an awesome handset. But at the same time, that sort of error is unacceptable.
[Samsung Galaxy Nexus] samizad:
Please do not get annoyed at people who don't read the previous posts in the thread.
[Samsung Galaxy Nexus] oscillik:
People should at the very least be reading the first post in the thread which details the issues. People are clearly not doing that.
[Samsung Galaxy Nexus] samizad:
True. Here's an off topic idea:

Don't allow posts on a thread unless the poster has first clicked on the first page.
[Samsung Galaxy Nexus] duqueso:
It looks like the issue is solved with the OTA update to ICS 4.0.2.

I'm not an owner of the Galaxy Nexus, but at least the sources seems to be realiable.

In Spanish

http://www.xatakandroid.com/moviles...-del-volumen-del-galaxy-nexus-con-android-402

In Italian

http://android.hdblog.it/2011/11/22...-bug-audio-del-galaxy-nexus-tramite-software/
[Samsung Galaxy Nexus] oscillik:
as has already been mentioned in this thread, the 4.0.2 update is for the Verizon version of the Galaxy Nexus and is in no-way related to the HSPA version of the handset which is being affected by this hardware fault.
[Samsung Galaxy Nexus] tingyue:
Hi can i ask you how you managed to get a full refund through Phones4u? were you on contract?

Thanks
[Samsung Galaxy Nexus] Duddyroar:
Can anyone translate the page? It's stuff like this which is really harmful to our cause. These sites are clearly jumping to conclusions. I highly doubt that 4.0.2 will fix the issue, but people might read those posts and assume Samsung has solved the problem.
[Samsung Galaxy Nexus] oscillik:
this is exactly why I have been trying to be vigilant on this thread and quick to squash baseless guessing by people that have no clue, except for what they've read by some poorly translated foreign webpage that itself only references a tweet, from someone who clearly has no understanding of the mobile phone network in the UK (in reference to his statment: "but wtf are people doing using the nexus in a 2g area?)
[Samsung Galaxy Nexus] duqueso:
Sorry, my bad. I think those sources aren't so reliable...
[Samsung Galaxy Nexus] mingoid:
The Spanish site quotes the Italian site and the Italian site quotes some random tweet from someone unconnected to Google or Samsung :rolleyes:
[Samsung Galaxy Nexus] matt2053:
The problem is oscillik is both a) correct, and b) an asshole. A dangerous combination to be sure! :)
[Samsung Galaxy Nexus] gambiting:
You don't have to be on contract. According to the 1979 Sales of Goods act, you can "reject" a faulty item if it was faulty at the moment you bought it. It is your statutory right, and if Phones4U store says otherwise they are braking the law, a little suggestion of taking their ass to court always helps them remember that the customers has some rights.
[Samsung Galaxy Nexus] oscillik:
you sir have hit the nail on the head :cool:
[Samsung Galaxy Nexus] nyyankees3511:
If its the rocker, no big deal ill change it myself. Ill agree with B LOL.
[Samsung Galaxy Nexus] oscillik:
gambiting is absolutely correct here - The Sale of Goods Act 1979 upholds your statutory rights,

which preclude any policy that the store you bought your item from may have in place regarding refunds/exchanges

.
[Samsung Galaxy Nexus] Duddyroar:
While I understand that your comment is in jest, I think it's rather sad that people who are level-headed and crave cold, hard facts rather than leaping on conjecture and hearsay are branded as 'ass holes'. oscillik has provided this thread with plenty of invaluable information, whereas there are many posters who have pushed the page count up with their needless and pointless waffle.

This topic is being linked to from all over the net, and that's down to people like oscillik, who are driving it forward and trying to sort the fact from the fiction.
[Samsung Galaxy Nexus] rabhw:
Handtec updated their blog:

Still finding it hard to believe their batch doesn't have this issue...
[Samsung Galaxy Nexus] Duddyroar:
We really need them to confirm what their 'test' is. They could be using a SIM from an unaffected network, like 3 or Orange. Until they disclose what their testing procedure is, I wouldn't put any weight behind that statement.
[Samsung Galaxy Nexus] qwerp_:
i just phone up Phones2U oxford street, asking them if they have received any new batch, they say they have.

i have going to try my luck to go get a exchange to see if that helps. (hopefully the same batch as the handtec or clove ones).
[Samsung Galaxy Nexus] Duddyroar:
Let us know how you get on. This will be a good test to see if this is indeed a batch-related problem, as you're someone who has already experienced the fault.

I've actually exchanged my phone at 3, but the replacement has the same issue. I think it's from the same batch though, as the 3 store in my town said they haven't sold many since launch.
[Samsung Galaxy Nexus] oscillik:
if you are able to get a replacement from a supposed new batch, please could you post your Odin details so we can ascertain if it is infact from a new batch? And of course, if you could conduct the tests to see if it suffers from 900MHz interference ;)
[Samsung Galaxy Nexus] foner78:
I preordered from Handtec and should receive my GN in the next couple days, so will be able to test for this issue using my O2 HTC Sensation. I fully expect the fault will be present. Not a good thing to feel about your shiny new smartphone before it has even arrived :(
[Samsung Galaxy Nexus] oscillik:
if you could also carry out the following, it would help
[Samsung Galaxy Nexus] electric0ant:
I doubt it, they will say anything to keep the sale and stop you from returning the phone. I just got an exchange with them last night and it's still having issues.

for those who are having issues getting phones4u to give a refund tell them to call their head office who have been much more helpful in authorising a refund.
[Samsung Galaxy Nexus] appelflap:
Let's create an app for this .. a background service adhering to the following specs

Save the current volume level when it is changed by the user.

Changed by the user would be when the on screen volume slider is used or when the volume rocker is used.

Now if there's a sudden volume change AND the network is on 2G and neither the volume slider is used OR the rocker set the volume to the saved volume.

:D
[Samsung Galaxy Nexus] qwerp_:
i don't really want a refund. i still want a galaxy nexus (with the issue fixed). so, if that is the case, i will keep asking for a replacement unit from time to time untill they actually fix the issue.
[Samsung Galaxy Nexus] basketor:
Wrong about what ?

What I suggested is that you are not 100% sure that the gsm is totally disabled in plane mode or bootloader mode, beeing by design or by bug.
[Samsung Galaxy Nexus] oscillik:
it is totally disabled. it is also completely non-functional while in bootloader mode.
[Samsung Galaxy Nexus] basketor:
How do you know it is totally disabled ?
[Samsung Galaxy Nexus] birdster:
I just recieved my GN from three.co.uk, did some tests and have no problems at all with it, my other phone set to 2g right next to it phoned and txt from it the GN was solid it didnt flinch, I did notice that the box the nexus had come in had been opened the factory seal was broken and a three.co.uk security sticker was replaced over it, maybe good news with this batch from three :D
[Samsung Galaxy Nexus] rabhw:
http://twitter.com/#!/handtec :
[Samsung Galaxy Nexus] oscillik:
Tweet from Handtec regarding the stock they just received from Samsung that supposedly had been tested
[Samsung Galaxy Nexus] Duddyroar:
Please, seriously? It's bootloader mode. Let's not get into silly arguments.
[Samsung Galaxy Nexus] oscillik:
troll.

did you make sure to place the phone next to the volume slider as demonstrated in this video?
[Samsung Galaxy Nexus] kristovaher:
This is the reason they should have actually tested the handsets before shipping.

So that means SIM free batch of this week is affected too. No wonder Clove did not say anything, Samsung has likely told everybody to ship despite the problem and promised some fix, since it is cheaper than mass recall.

Sent from my HTC Desire
[Samsung Galaxy Nexus] basketor:
you want silly arguments I can provide you some

"you can't call and send sms on plane mode and bootloader, so this proves the gsm device is 100% disabled"

the first thing I would investigate as an ingeneer is if the device state is really the one expected, and unless you can receive microwaves with your brain, or have the source code in front of you, or debug in real time, you have really no way to know that.

That is I don't say there might not be a hardware issue, it's still a possibility, however I still see nothing that really proves it