yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Gundea:
It doesn't really contradict itself. In the case of Google explicitly informing Clove that it's a software issue they know that it is a software issue, but may still not be informed as to the technical details of said software issue. Until we get some official announcements from Google/Samsung I'd refrain from commenting strongly on this matter.
[Samsung Galaxy Nexus] osgov:
Fair point. The problem is though, that as far as I can see, clove is the only retailer that issued such statement. As I said above, if google and samsung had this issue under control, there would be no need for calling off and delaying shipments.
[Samsung Galaxy Nexus] kristovaher:
Hey, everybody, you do know that the source of this statement:

..is a single website, androidpolice.com, right? It hasn't been posted by Google or anyone of Google anywhere.

We have no idea who or what actually is a source of that quote.
[Samsung Galaxy Nexus] oscillik:
the only verifiable word we've had from Google is the conversation I had with Romain Guy, last night

edit: verifiable in the sense that romanguy is a mod on the #android channel on freenode.net and is a well known Google engineer
[Samsung Galaxy Nexus] paul_one:
can someone with the volume problem get some cpu usage stats?

there's an app called "usage time lines free" which might help here.

I'd like to see how much the cpu is affected when the bug is in effect.

That way we can also compare it after the update.

some screenshots may help too.

(edit)

system stats wallpaper looks better, but it is still a wallpaper.. would rather have a dededicated tool..
[Samsung Galaxy Nexus] bleets:
been posted by various cnet sites and androidpolice is a pretty reputable source imho.

also endgadget says the same thing...
[Samsung Galaxy Nexus] jms.flynn:
Well he doesn't confirm its a hardware fault or software fault so that proves nothing, the conversation cuts off after you start rambling on about RF shielding.
[Samsung Galaxy Nexus] oscillik:
exactly my point -

neither Google nor Samsung have made any mention of what is causing the problem

if you had been following the rest of this thread, you would have seen the explanation for why the conversation just cuts off. I am not going to go back and find it for you, if you want to know the explanation, go back and read the information you should have been reading before you even commented.

Getting really sick of people making comments in here regarding information that was attained via this thread without having read the entire thread in the first place.
[Samsung Galaxy Nexus] M2281088:
Why do you feel that you must troll all the time.

FFS just let it lie.
[Samsung Galaxy Nexus] Duddyroar:
Engadget is linking to Android Police - in fact, all sites reporting on this so far have linked back to Android Police.

Until we get an official statement from Google, I'm calling BS on this.
[Samsung Galaxy Nexus] Tom Servo:
I still find it hilarious that people really pretend that a phenomenon triggered by RF interference is not a hardware issue. That'd be like claiming me punching you in the face isn't violence.
[Samsung Galaxy Nexus] kristovaher:
They all use androidpolice.com as a source

We don't really have a source, androidpolice.com is not exactly TechCrunch, Ars Technica or Engadget to be the main source of something.
[Samsung Galaxy Nexus] Duddyroar:
Amen to that!
[Samsung Galaxy Nexus] jms.flynn:
Are you kidding, I have been commenting all the way through this thread, and unfortunately have had to read your ranting over and over and over.

When Google and Samsung do release a statement saying it is a software issue you my friend will become nothing more than a troll with 90% of your posts going onto deaf ears. What's next after that oscillik? Are you going to fly to Mountain view and South Korea until somebody over there listens to you.
[Samsung Galaxy Nexus] Duddyroar:
If you honestly think this is a software issue then you really are as dumb as you sound.
[Samsung Galaxy Nexus] Rubu:
There was no explanation, just another assumption, thank you very much.

It's not unusual for companies to keep something like this quiet, doesn't mean that it's a hardware fault. At least it seems like something is happening. Hardware or software, whatever it is, they're working on it.
[Samsung Galaxy Nexus] Ladrero:
Official Source?

https://plus.google.com/113238550815846424978/posts
[Samsung Galaxy Nexus] ErGo_404:
I must admit I mostly agree with you, but imagine this :

What if the problem is caused only by the radio part (which is, due to a software bug, never really stopped). Using the 900Mhz frequency could trigger the problem, as well as approaching another cellphone using that frequency, but the problem could still come from the radio software.

I'm not saying it is the case, it's just that even if what we observe may seem to prove that it's a hardware bug, we could all be wrong.
[Samsung Galaxy Nexus] osgov:
Unfortunately, until they DO release the statement, you have no real proof of it being a software OR a hardware issue. Ergo, your argument is invalid
[Samsung Galaxy Nexus] Tom Servo:
Pretty telling all this in regards to retailers, tho.

Handtec's being like "Holy ****, problem! We won't ship until we know what's going on!" while Clove's basically going "It's a non-issue, go away! Here's some misinformation!" Yeah, I'm saying misinformation. If there was some semi-official statement given to retailers, there'd be more saying the same.
[Samsung Galaxy Nexus] jms.flynn:
I didn't say I think its a software issue, I said when Google and Samsung release a statement saying that it is software issue (which they will because it will be the quickest fix), nobody will be commenting on it any more because the issue will be solved for 99% of the people using the phone. Unless of course you use your phone on bootloader all day next to a GSM 900 signal. Which obviously everybody does. :rolleyes:
[Samsung Galaxy Nexus] Tom Servo:
The GPIO chip which is responsible for the buttons is making the issue here, which is not related at all to the radio. That chip is making a fuzz under interference, which causes the driver to kick in. But apparently because the driver is ****ting the log up with messages, it MUST BE a software issue, disregarding that said driver only gets involved when the GODDAMN HARDWARE ASKS FOR IT.
[Samsung Galaxy Nexus] kristovaher:
It does not seem like this is an official source. I highly doubt this is Google's own Galaxy Nexus fan page there or managed by anyone who has any hand in this current situation. Why would Google quote The Verge, if it were their own statement? If you read other posts, then they are just as suspicious.
[Samsung Galaxy Nexus] bleets:
if trying to convince people to have a little perspective rather than trying to constantly force their beliefs on people is trolling, then i'm guilty as charged!
[Samsung Galaxy Nexus] Sejanus:
I'm fairly certain that's not an official source.

If you look at their official Android page https://plus.google.com/104629412415657030658/about you'll notice a checkmark beside the name meaning "Verified Account". Although if you search for Samsung none of their pages have "Verified Account" beside their names it's tough to say, but considering the language used on the Nexus Galaxy page it's doubtful.
[Samsung Galaxy Nexus] ejkeebler:
hypothetically they come out with a firmware update that makes this problem go away and doesn't even exist in the bootloader, does that change anyone's opinion of whether it was a software or hardware problem? or does that just mean it was a software solution?
[Samsung Galaxy Nexus] Tom Servo:
On one side, we have corroborating evidence in actual tests, video proof, log files looked at by people with knowledge in electronics and programming (and kinda physics), and on the other side people that go like "I'm not a programmer, but have some perspective..." Get the **** out!

And no, soldering a LED to a battery or writing ****ty enterprise software in Visual Basic doesn't mean you have a clue about electronics or driver development.
[Samsung Galaxy Nexus] MatthewPL:
Could somebody make some performance/battery life tests before software fix release? It would be useful to know is any change before and after software fix.

Thanks!
[Samsung Galaxy Nexus] bleets:
lol...you have video proof showing how to replicate the fault but nothing. (also nice attitude, swearing at people, very mature.)

i've only been working in a device repair environment/job for over 8 years so i know that sometimes what you think to be the cause is not at all.
[Samsung Galaxy Nexus] Tom Servo:
If interrupt storms are choked down on driver level, it should improve battery live, because letting these events bubble up to the relevant code in the Android audio subsystem is going to make the CPU work more (driver calls vs. driver+OS+Dalvik calls).
[Samsung Galaxy Nexus] JcMalta:
Lets just try and settle on this:

a) I think the quote at Google+ is genuinely from Google

b) Google/Samsung would know if a fix was possible ...

c) MAYBE it IS a hardware problem ... in my 30+ years as a chip-level programmer I have seen PLENTY of these issues - from Commodore PET "key bounce" to Bluetooth echo .. but if a soft-fix works .. so much the better ... (and believe me we DO consider overall system performance ... but for the loss of a very few REAL cpu cycles for a quick, patchable fix its no problem ... probably 1,000,000 less overall effect than a bad app or "live wall-paper"

d) IF its fixed, its fixed ... maybe not in 100% "hardware purity" but good enough that no-one would ever notice .....

e) PROBABLY the "fix" software will remain in place if/ever the hardware problem gets fixed ....

Really, I think right now this is a time for celebration ... hopefully the problem will disappear (albeit with a totally NEGLIGIBLE software overhead)

But like all things .. we will wait and see.
[Samsung Galaxy Nexus] rabhw:
Just a few interesting tidbits I had from a live support chat with Handtec:
[Samsung Galaxy Nexus] basketor:
If it was just a shielding problem, I don't see why only 900mhz frequency would create a problem, on some cables in the device.

Even if it's possible, the odds are low.
[Samsung Galaxy Nexus] jms.flynn:
+1 Agree, enough repetitive posts. Can we just post updates on the issue regarding official statements, website links etc.
[Samsung Galaxy Nexus] Tom Servo:
Wait, do we have videos or do we not? That sentence doesn't make sense.

There's videos showing HOW to cause the issue. There's logs that show how the phone REACTS to the issue. Applying some logic and related knowledge about the topics at hand nets you a pretty decent and plausible conclusion.

I'm sure it doesn't involve fixing SMD or high density electronics.

---------- Post added at 03:42 PM ---------- Previous post was at 03:37 PM ----------

Ah, the joys of radio signals, harmonics, shielding and antenna designs. It'll blow your mind. And I mean that sincerely. If it were so easy, we wouldn't have this issue to begin with.

The working theory is the trace routing between the GPIO chip and the volume buttons causes the signal to be picked up stronger than anticipated. Inductive effects are probably strong enough for the GPIO chip to react on it. Doesn't mean something won't pick up any RF, just because it isn't some big heavy copper coil.
[Samsung Galaxy Nexus] kristovaher:
I updated in the original post that Google having a fix or that they are working on a software fix is a rumour and is not confirmed. Just having a short, so-called statement from a single not well known blog is not enough to validate it for now, even if someone from chat seemingly validates it. It does not look like Clove was in contact with Google either and are basing their information on the countless other blog posts that all have androidpolice.com as a source.

If people believe that 'statement' and do not believe the piles of proof provided in this thread and elsewhere that this is a hardware issue, then I don't know what's up :)
[Samsung Galaxy Nexus] saquib:
The Verge is reliable:

http://www.theverge.com/2011/11/23/2582349/google-galaxy-nexus-volume-bug-fix
[Samsung Galaxy Nexus] Tom Servo:
I looked up whether there were issues with the Nexus S, which is also Samsung, and guess what, certain 3G frequencies caused the capacitive search button to trigger. Why am I not surprised? :D

---------- Post added at 03:55 PM ---------- Previous post was at 03:53 PM ----------

So Handtec's delaying the deliveries until the fix went out and was tested by them? We don't even have a word on when the fix is going to be released.
[Samsung Galaxy Nexus] gagaohlala:
It's finally official !

Samsung UK said on Facebook official acount :

Regarding the Galaxy Nexus, we are aware of the volume issue and have developed a fix. We will update devices as soon as possible.

!
[Samsung Galaxy Nexus] jms.flynn:
Just as I thought, now we can see this thread slowly trail off and we can all start enjoying the phone. Using custom roms etc. Great news.
[Samsung Galaxy Nexus] kristovaher:
I am still having doubts, but apparently Samsung UK posted the same thing on their wall, so it must be valid.
[Samsung Galaxy Nexus] Roni1979:
I´m very suprised that a lot of you guys are happy that either Google nor Samsung will find a solution which fit for all of us. I think also that it´s no matter what Google/samsung will say, because you believe it´s a hardware issue. If they say it´s a software issue, you will keep on track and remain on they are liyng.

I believe that there is a problem, but either Software nor Hardware issue is out of question.

As already mention if after the fix everything works fine, who cares? except you guys which think that you will also have a defect mobilephone. For my opinion I think you should reject it and buy a different phone.
[Samsung Galaxy Nexus] momagic:
Samsung on Facebook just said this:

Samsung UK

Regarding the Galaxy Nexus, we are aware of the volume issue and have developed a fix. We will update devices as soon as possible.
[Samsung Galaxy Nexus] jms.flynn:
And who is to say that a HTC does not have the same issue but masked with a piece of software before it was released? You wouldn't know. If the problem can be resolved with a software or drivers with no impact on battery life or performance as far as I am concerned it is a fix. If Samsung order a product recall, I will happily let them take my phone back, but if they release a fix I will be happy.
[Samsung Galaxy Nexus] gnufabio:
Yeah, that's true. Let's see how it will work.
[Samsung Galaxy Nexus] paul_one:
unfortunately I don't see anyone actually doing the tests required to show this impact on the phone, for fear of knowing the truth.
[Samsung Galaxy Nexus] s.m.knipe:
Didn't they say elsewhere they expect shipments to resume between the 25th and 28th?

They are holding shipments to prevent liability from shipping known (and acknowledged by them) faulty units. Once a "fix" is available and acknowledged by them as such it lessens their liability for providing a fully functioning product, and they will feel safe releasing the products. Clove apparently feels that acknowledgment of the issue and the promise of an acceptable "fix" is enough to alleviate most of the liability. Samsung is not distributing more units for the same reason Handtec is withholding theirs. Other than what we can glean from the time-frame estimates they provide, this is nothing more that legal CYA for them.

Also, I do not believe that Samsung themselves have ever publicly admitted to an issue and owned up to its resolution. Even last year with the Galaxy S GPS craziness (also a hardware issue, as this is most likely), they "realized some customers were not experiencing expected performance" and released a software patch to "optimize GPS performance" (which of course did not work)- but never admitted that there was a "problem." Do not expect anything other than an "optimizing volume experience" or something similar comment from them. Google on the other hand has owned their issues the past, and the comments from their engineers individually (while not up to our usual expectations for a massive company) are better than whatever legalese statement their lawyers will eventually issue. Once the "fix" is available, the Android team will publish a statement (probably on twitter, or now on G+ actually) saying so as the official comment. I'd wager they will do so on Friday since tomorrow is a holiday here Stateside- unless they pump it out today/tonight...

Wow... maybe they are learning how to appease customers after all! Not as definitive as it could be (they could take ownership by adding " our " in front of "Galaxy Nexus" to actually tie themselves to the issue), but hey, it's a start
[Samsung Galaxy Nexus] cellzealot:
The diagnostic monitoring and logging serviceware required to prove whether any effects on the radio are created by this fix are not available to the public, so the kind of analysis you are suggesting is probably not possible for end users.

Edit: This was directed to paul_one's comments.
[Samsung Galaxy Nexus] burnduck:
on a side note, i was trying to replicate the problem while charging the phone, but it seems to me that the volume bug is less likely to appear when plugged in.. hmm
[Samsung Galaxy Nexus] paul_one:
electromagnetic field produced by the battery whilst charging (including flow of electrons through the medium) could aid to protect the piece of circuit affected by the 900mhz emi/rf wave.
[Samsung Galaxy Nexus] Tom Servo:
I don't know. I gave them explicit permission to deliver mine. Still haven't gotten a tracking number. Seeing how they ostensibly got enough stock to deal with most preorders, and given that mine was a month early, I'm surprised I'm suddenly not getting anything due to Samsung of all people withholding stock.

Nah, doesn't work that way. If having it plugged in prevents it, it sounds more like power management issue. Various other chips being undervolted by the PM chips, the affected GPIO being one of them. Possibly the threshold voltage for triggering drops with lower voltage on the chip.

If that'd turn out to be an issue contributing to the cause, a software fix would involve changing some power management parameters.
[Samsung Galaxy Nexus] Gundea:
That doesn't make any sense, I'm certain someone here will do some testing. In fact, I'm quite curious myself about how they solved this bug.

The real problem lies in the fact that we don't have a baseline for the expected battery life of the Galaxy Nexus using 2G on the 900 MHz frequency band in a poor singal area. Anyway, any fix will most certainly improve the battery life over what it has now, since the faulty signals won't rise as high up in the system and cause more and more code to be run. Actually, I'm pretty certain that it'll be a complete non issue, but if someone notices that the battery drains abnormally heavily in 2G areas then we have a problem.
[Samsung Galaxy Nexus] pienut:
Same here.

Also gave them explicit permission but did not receive a tracking number so far.

Just a support ticket which remains unanswered.
[Samsung Galaxy Nexus] paul_one:
to be honest, I'm more curious over cpu usage. if it goes up when the problem occurs, you can get bad things like dropped calls, slow ui feedback, etc, and of course that impacts battery.. I can always try and get a bigger battery and case later on, but if the ui freezes all the time while I enter phone numbers etc, then that's a bigger everyday impact on me using the phone... guess we'll see!

I need to slowly stop obsessing over this...
[Samsung Galaxy Nexus] jms.flynn:
http://www.youtube.com/watch?v=n6DzEBoQ5VU&feature=youtu.be

Ignore the shaking hands, but the volume actually blocks the CPU usage. But you can see the usage go up in the list of processes I've done about 5 tests and they all average out to around 34-35% cpu usage for me.
[Samsung Galaxy Nexus] Tom Servo:
If a software fix just masks the issue, it'll still eat less CPU power.

During the interrupt storm, all interrupts are handled on driver level regardless. A lot of them bubble up to some input layer, which causes that error message in the log. All that managed to fill the input buffer before the overrun will be handed higher up the layers dealing with volume stuff.

A fix would cut out the bubbling. There'll probably be some minor accounting code, to discern between interference and actual presses (5 presses per second versus >25 "presses" per second), but that wouldn't remotely eat as much CPU time as processing the events.

Meanwhile I'm however hopeful that this is a power management issue. Anyone else tried to cause the issue while charging?
[Samsung Galaxy Nexus] oscillik:
I give up with this thread. Quite a few people commenting here are ignorant of the facts established through testing carried out by those of us who actually have the phone. I am willing to wager that the majority of people who are ignoring the facts are people who do not own the handset, and furthermore have little understanding of the technicalities concerned with this particular fault.

These people are quick to misunderstand an

uncorroborated

statement by Google that they are working on a software fix, and are choosing to read this as confirmation that the issue is caused by software, when Google have said nothing of the sort. I have no qualms about calling each of you people 'thick', since you fail to understand plain English.

As such, I can no longer stand to battle facts with people that are incapable of understanding or even reading.

Well done trolls. You win.
[Samsung Galaxy Nexus] jms.flynn:
Don't let the door hit your ass on the way out.
[Samsung Galaxy Nexus] regorsnas:
Samsung said in Facebook:

"Regarding the Galaxy Nexus, we are aware of the volume issue and have developed a fix. We will update devices as soon as possible."

This was an hour ago.

But like oscillik said, for me it isn't a proff that is only a software problem. I need more information from Samsung or Google.

facebook.com/SamsungUK/posts/324057714277932
[Samsung Galaxy Nexus] Nail_s:
I've collected my parcel with GN today from Handtec, because they sent it to me before they realised there is volume bug in their batch.

I'm waiting 10 days for software fix. After that time if it will not be fixed I'm sending device back for refund...
[Samsung Galaxy Nexus] s.m.knipe:
Here is the post containing Handtec's post on their blog:

Again though, this only gives a "best guess" based on their "best guess" of when the update will hit.
[Samsung Galaxy Nexus] Tom Servo:
My preorder was done in October and should have been covered by the batch received on Nov 21st. That's what they said when they announced the reception of the stock. Suddenly I'm being delayed because a batch, that was supposed to arrive at their place today , was delayed. Doesn't quite make sense. Especially since they stopped all shipments pretty soon after starting, unless specifically requested otherwise, so there should even be excess stock.

--edit: Meanwhile I got a wishy-washy response about this on my ticket. :confused:
[Samsung Galaxy Nexus] jms.flynn:
Yes I have been able to recreate the issue whilst charging, do you need a video?