yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] oscillik:
wrong. Google have not confirmed the problem, only confirmed that they are

working on a software patch

. This does not preclude this being a hardware defect, only merely says that Google are working on a software workaround.
[Samsung Galaxy Nexus] bleets:
they wont issue any definite information until the update is ready to be rolled out, what happens if they say what it is and something changes?

Patience is a virtue! :)
[Samsung Galaxy Nexus] appelflap:
Lol, Italian has a lot of vowels. That's all I "see" when trying to read it
[Samsung Galaxy Nexus] neovisage.HD2:
i have my GN from phone4u as well in worthing been playine with the phone now for almost 3 days swiching to 2g mode no issue,im with 3 network.
[Samsung Galaxy Nexus] HUNZwiebel:
OFF:

In my opinion, it is a forum. It is because, we want to comment things. I comment the things.

/OFF
[Samsung Galaxy Nexus] davej777:
No problem - your log is still useful.

Let's hope Google's fix is good enough.
[Samsung Galaxy Nexus] Duddyroar:
Please read the first post in this topic. You won't get the issue as 3 isn't affected.

In other news, I've posted a video up on CNET UK showing the fault -- based on the findings in this thread, of course. :)
[Samsung Galaxy Nexus] paul_one:
there have been videos on Youtube where the users 'fight with their mobile', and loose.

what you say is dangerously innacurate.

even if there were some way to hide the hardware, the cpu would be under constant load from having to interpret these key events. it doesn't bypass the cpu just because you put an 'if' statement in the code.

the key press then needs to be evaluated, recalling previous events to see the frequency, store the new event.. you're talking about a constant pull on the cpu (if you're on o2 in the uk).

if you want to try and alter the kernel go ahead, I doubt you'll get very far, since you can't event clarify the conditionals in your posts.
[Samsung Galaxy Nexus] pienut:
Is anyone aware of an app to check what frequency your cell provider/tower is using? This being Proximus, the provider I use, has 2G on 900mhz and 3G partially on 900Mhz and partially on 2100mhz...

Just asking, don't kill me now please :-P
[Samsung Galaxy Nexus] oscillik:
That is a very good question - I myself had been wondering if there was a way to determine what frequency band the phone is transmitting/receiving in via an app.

It would be very useful in this situation.

Anyone know of such an app?
[Samsung Galaxy Nexus] burnduck:
i noticed that but it appeared to be a fault with the *#*# app, setting does seem to stay on WCDMA only for me after reboots although it says 3G and 2G

correct me if i'm wrong
[Samsung Galaxy Nexus] kristovaher:
I have updated the original post with new details about the SIM-free batch of phones and Google working on software patch.
[Samsung Galaxy Nexus] paul_one:
i use network signal info.

it tells you a lot - but not the frequency... possible starting point though!
[Samsung Galaxy Nexus] pienut:
Yes, I was plowing through the market. Most of these tools just show basic cell info but no frequencies :-(
[Samsung Galaxy Nexus] Hosh0:
Just in the interest of stopping opinion being spread as fact, can you please edit the post and remove the line around it will not fix the hardware defect or whatever it says. We don't know it's a hardware issue that is just what some people are thinking, it might be true in the end but it might not be, we just don't know yet.
[Samsung Galaxy Nexus] jaketurbo:
Seriously, this is still unproven.

It's very likely but no root cause has been determined... yet.

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

This whole post is assumption and barely conjecture.
[Samsung Galaxy Nexus] jms.flynn:
If Samsung had came across the problem during testing and Google wrote a software patch for it before the phones were shipped would you all be asking to return your phones. No you wouldn't because you wouldn't have known it existed. Although I am not saying that this is not a hardware issue, mainly because oscillik the nazi with strike down upon me furious anger, I am saying hardware issues are more common place than we would like in our gadgets and software, firmware and drivers normally do a great job of fixing them.

Thats why this morning I went and re purchased a Galaxy Nexus, after 1 day of gingerbread I could not be without ICS or that beautiful screen anymore.
[Samsung Galaxy Nexus] kristovaher:
Of course it is. It describes the situation as we can best describe it without any official statements from either Google or Samsung. It relies on the poll and the information gathered from countless tests done by people who already have the device in multiple networks and handsets bought from different stores and sellers.

Unless Google or Samsung specifically state that this is not a hardware issue, then all the gathered information so far states that it is. It just might be fixed by a software patch that will provide a workaround.
[Samsung Galaxy Nexus] jaketurbo:
Not meaning to sound like I'm having a go... but you've got quite a bit in there that's stated as fact.

Also comments on how Samsung shouldn't make the next google phone.

Really, let's ensure this is an informative post about a serious phone issue. Not something that is used for expressing opinion and dislike for a company.

Get some sections or bullets on there with:

- What the issue is and what impact it has

- What is confirmed by google/samsung

- What is suspected by users here

- What tests have been undertaken and how to replicate the issue

Then leave it at that for the moment.

That's what I'd do anyhow.
[Samsung Galaxy Nexus] HUNZwiebel:
Edit: Ok nothing man...
[Samsung Galaxy Nexus] osgov:
An update on handtec's galaxy nexus blog just came through:

"23/11 – UPDATE: Our expected delivery today from Samsung Distribution has been stopped\delayed for 48hrs. We now expect stock to arrive 25th November – with shipping taking place on the 25th through to 28th November. We hope the delay is related to the volume issue/bug and and the delay should reassure customers that Samsung is taking action. We apologise for the delay."

Looks like something is happening. Even though I couldn't find any official statements by either google or samsung.
[Samsung Galaxy Nexus] burnduck:
I would say this is patchable (note i didn't say fixable), but only if they implement it on a low level

My assumption is the volume rocker circuit picked up the GSM Buzz and it was registered as interrupts, if it is the case, we can simply analyse the "buzz" and filter out this kind of quick succession inputs like someone mentioned earlier.

This is the "buzz" captured by my computer's built in mic. On the phone it takes about 1.5 seconds to turn the volume down by holding the volume key, but this bug caused it to go mute in less than half a second, so I would say it's safe to assume it's actually the spikes that is being registered by the phone.

If it is the case, samsung could implement something on a low level to ignore anything that presses the key for, say, less than 0.01 of a second. I am not sure how this is going to affect the performance of the phone, since I don't know how a button talks to the phone and whether there are any intermediates handling this hardware interrupt, it might or might not sacrifice battery power.

Although it solves the problem, still I have to admit, I don't like this solution.
[Samsung Galaxy Nexus] kristovaher:
Handtec has stated that they are holding shipments for 48 hours as a result of distribution holding shipments from Samsung. Clove too seems to provide conflicting information now, where their customer support told us that they will post a notice about shipments being held. Yet Clove seems to keep shipping the device to at least some users according to the thread.

This may either mean a good thing, or a bad one:

GOOD

This 48 hour delay may mean that he software patch will be installed on newer devices and the software patch provides good enough workaround for the problem. It is unlikely that Samsung will fix hardware issues in batches in Europe in just 48 hours.

BAD

This may mean that handsets are actually faulty and cannot be fixed with a software patch alone and that Samsung put brakes on for 48 hours in order to see if mass-recall is necessary, without rushing things and notifying of mass-recall immediately should new information become available within 48 hours.
[Samsung Galaxy Nexus] kristovaher:
IMPORTANT!

Clove just posted on their blog.
[Samsung Galaxy Nexus] paul_one:
i'd put that the other way round. if they release a software fix for this the name of samsung goes down the toilet, and the nexus name with it.
[Samsung Galaxy Nexus] oscillik:
Clove are stating that this is not hardware related, without any evidence to back this claim up.
[Samsung Galaxy Nexus] Evostance:
Guys,

Just relax and enjoy your phone. Like said before, if there was a hardware issue and it was patched via software before the phone was dispatched, you wouldn't know about it.

I suggest you just enjoy your phone and wait for the update. If you're not happy then go get a refund
[Samsung Galaxy Nexus] mirilo:
Samsung Facebook UK

I have visited Samsung UK's Facebook page. All negative comments about the Nexus (including my own) have been removed. Seems like Samsung are (unsurpisingly) doing their best to keep this quiet - definitely not good for business!

Do we know how Samsung will inform us of any potential fixes, software or otherwise. In regards to software would it be an automatic update, or do we need to keep checking the update server on our phones?
[Samsung Galaxy Nexus] paul_one:
no you're right, I would be complaining about a phone that continually suffered slow downs in certain areas, got hot for no reason a d sucked with battery life.

bai bai samsung nexus... hope the next phone gets a better brand.
[Samsung Galaxy Nexus] Evostance:
:confused:

My phone doesnt get hot and the battery lasts from 8am till at least 11pm without any charges in between.

Slow downs in certain areas is to do with your carrier, not the phone
[Samsung Galaxy Nexus] Gundea:
I think that everyone complaining about poor battery life etc from the software update should shut it. You have no idea about the nature of the update nor how it will affect battery life / performance, until devices with the new software can be tested under the same conditions as the old versions no-one here has any clue.

It may turn out to be a pretty ****ty patch, and if that's the case, then feel free to rip Google/Samsung a new one, but until that time, let's refrain from posting such speculation.
[Samsung Galaxy Nexus] paul_one:
what carrier are you using? are you constantly on a poor 2g signal?

As I've previously stated, I work in converted warehouses and server rooms. This interferes and requires higher 2g signals (and far better normally than anyone else in the office).

Any software patch to 'filter' these will cause those issues.. Really annoyed at the attitude Samsung have taken here. It's worse than the windows server team I have to work near passing all their problem onto us.
[Samsung Galaxy Nexus] njiwani:
Do you think that Clove would tell all of its customers an outright lie?
[Samsung Galaxy Nexus] kerberos7:
Yes, its all about money!
[Samsung Galaxy Nexus] oscillik:
They are telling an outright lie.

Neither Google, nor Samsung have made any public statement to say that this is not a hardware issue.

The only statement that has been made has come from Google, and it is the following:

All this statement says is that Google are working on a software fix, and that they are aware of the problem. Says absolutely nothing about the cause of the problem.
[Samsung Galaxy Nexus] Gundea:
It's far more probable that Clove got its information straight from Google, and if Google says it's a hardware issue I'm at least prepared to give them the benefit of the doubt since they have far greater insight into the hardware and software involved.

That said, Google does have something to gain short term from lying, but the long term cost is simply too great for me to believe that they'd be that stupid.
[Samsung Galaxy Nexus] njiwani:
It will be more costly for them in the future as they would lose a lot of customers if this ended up being a sham.
[Samsung Galaxy Nexus] BiGMERF:
http://phandroid.com/2011/11/23/gal...le/?utm_source=twitterfeed&utm_medium=twitter

OTA to fix , on the way soon?
[Samsung Galaxy Nexus] kristovaher:
I updated the main thread once more, included the latest information and made it more reader-friendly.
[Samsung Galaxy Nexus] Evostance:
That just links to phandroid, who link to the verge, who link to etc etc etc...
[Samsung Galaxy Nexus] kerberos7:
Companys think quarterly ;)
[Samsung Galaxy Nexus] mjdyson:
Another one with the volume bug, from the first batch from Clove.

I live in an Edge area, using GiffGaff (O2). Not plagued me that much, but for turning the volume down.

Problems aside, this screen is BEAUTIFUL.
[Samsung Galaxy Nexus] mirilo:
Fix

Just had an email from Samsung UK:

"Thank you for contacting Samsung. I am sorry you are having this issue with the handset.

Please be advised you will need to upgrade the firmware of the handset in order to hopefully solve the issue.

Please connect the handset to our Samsung KIES software, and select ''Upgrade Firmware''.

I am at work, without my USB cable, so I can't try it. But will try it later. Fingers crossed!!
[Samsung Galaxy Nexus] CJSnet:
Your post says there's no official comment. Why not add:

“We are aware of the volume issue and have developed a fix. We will update devices as soon as possible.” - Google
[Samsung Galaxy Nexus] njiwani:
So you still believe that it is hardware related after Google has said it will update devices and Clove has said that software updates will be pushed out soon?
[Samsung Galaxy Nexus] Alexander T.:
If its a HW issue that can't be simply fixed by Samsung at the low-level driver level, then it means we will still have the issue in bootloader mode, since whatever workaround is delivered by Google, it will work in OS mode only, IMHO.

What do you guys think?
[Samsung Galaxy Nexus] escrivel:
Is this a bla bla answer or do they roll-out a fix?
[Samsung Galaxy Nexus] Chrono_Tata:
Since I'm pretty sure you can't connect a Nexus phone to KIES, sound like blah blah to me.
[Samsung Galaxy Nexus] oscillik:
This proves that Samsung have no clue - the Nexus handsets cannot be updated via Kies at all. This includes the Galaxy Nexus.

Google has simply said that they are working on a software fix. Again, I reiterate for you that

Google has not made any statement whatsoever on the cause of the problem

, so anyone claiming that this is not a hardware issue based on this official statement is categorically wrong.
[Samsung Galaxy Nexus] YDardeer:
Just got this email from clove.co.uk

Looks like all is good
[Samsung Galaxy Nexus] paul_one:
i got a little scared there...

does anyone know where the git source code for android is? I'm searching github in a vain attempt to look at any commits that might be added.

I should at least be able to narrow the submitted code down to a commentand work out what the code does (as long as it doesn't use a complex algorythm, that'll take me longer).
[Samsung Galaxy Nexus] gnufabio:
Hardware problem or not, the important thing is they can fix it. I think even if it's an hardware problem they won't solve it in the future revision, since they already have a software fix.
[Samsung Galaxy Nexus] jaketurbo:
Much more informative and less subjective way of doing it.

Great post.
[Samsung Galaxy Nexus] mirilo:
I wasn't aware of that! Doesn't sound good. All I can say is that I posted a message on Samsung UKs Facebook page. They messaged me and asked for details. I sent the requested details to Samsung's email address. They emailed me from dear_customer@contactus.samsung.com and told me to connect to KIES for an update. But you are correct Samsungs website does not mention Nexus compatability.
[Samsung Galaxy Nexus] osgov:
Another update from handtec:

"UPDATE A: After extensive testing of the devices on 22/11 we found many devices with the volume faults. A decisions was taken not to ship further devices until Samsung provided an update to the issue. We understand that they will be making an official announcement soon. Our daily deliveries from Samsung Distribution have also been delayed/stopped until the 25/11. Some customers have received there goods and tracking however if you have not received tracking then this delay of approx 48hrs will unfortunately effect you."

- It doesn't make any sense. If google is officially working on a software fix via air update, then there is no reason to hold the shipments, is there?
[Samsung Galaxy Nexus] gnufabio:
This update is old
[Samsung Galaxy Nexus] bleets:
so anybody saying it is not a hardware issue is categorically wrong yet you who 100% insist on it being a hardware issue yet cannot provide any FACTS as to why are 100% right? ego problems...
[Samsung Galaxy Nexus] oscillik:
no it is not all good - that email asserts that the problem is not hardware related, which is an

outright lie

at this point in time, for the following reason:

Until Google or Samsung come out with an official public statement that defines one way or the other, nobody can use Google's statement as proof that it is not a hardware issue.

Unfortunately, if this is the case, I agree with you that Samsung will not make a hardware revision.
[Samsung Galaxy Nexus] kristovaher:
Exactly, this is why I doubt Google actually has developed a fix. There is no statement, no official source that can be considered very reliable. This is also why Handtec and Clove both ask users to confirm before the shipment.

I still fear the rugs will be pulled from under us and it is a problem that cannot be really 'patched' with a software patch, like some engineers in this thread have stated.
[Samsung Galaxy Nexus] Alexander T.:
Its worth comparing the source codes of 4.0.1 and the planned 4.0.2 fix to find out what was exactly changed/added.
[Samsung Galaxy Nexus] oscillik:
re-read my post - I said that anyone who is saying it is not a hardware issue

based on Google's statement

is categorically wrong.
[Samsung Galaxy Nexus] jaketurbo:
People need to accept that the evidence so far points to a potential hardware issue but there is not outright proof.

There is a possibility it's a low level driver/configuration issue but it is believed the chances of this are limited.

It doesn't seem like an android issue.

Apparently, google are going to implement a fix, whether a work around or actually addressing the root cause...

I'm still to be convinced they have said this though. I'd prefer to see a real statement issued by google, not a few websites making a claim. Remember, media groups/organisations always want to be credited with breaking a story...
[Samsung Galaxy Nexus] JcMalta:
Just received from Clove

Clove are saying this is a SOFTWARE issue:

TL'DR: We can now confirm that Google were alerted early to this issue and have been working on a fix. It is software related and as you may have seen from various forum and blog posts this morning, they are now able to confirm that they will have a fix. It is NOT hardware related...

Full Text:
[Samsung Galaxy Nexus] oscillik:
Clove are making a disingenuous statement by asserting that "it is NOT hardware related", because neither Google nor Samsung have made any statement to explicitly state that the issue is caused by software. Google are the only ones who have made any statement at all, and they only state that there is a software fix in the works. This does not say that the issue is a software issue, only that it may be fixable via software.
[Samsung Galaxy Nexus] Jebus99:
I agree. It probably is hardware related but I wish people were not stating "facts" that are not proven. Yes I understand that people *think* they have proof in terms of it being affected in the bootloader, and with their testing. But unless someone here is an engineer involved in designing phones or has a PhD looking at RF intereference in IC's, they really shouldn't be putting their opinions as facts. We really have to wait for Samsung and Google to put out official statements on the issue. It's fine to state your opinions, just please try and refrain from making it into fact.

Edit: I agree with the fact that the websites similarly shouldn't be saying it is not a hardware fault either. The current "fact" should be that there are strong indications that it is hardware related and maybe be patched via an update but the underlying cause is yet to be determined.

Clove are particularly bad with this statement: Sorry we do not know the ‘technicalities’ of what actually causes it and how it is hardware or software related. What we do know is that it is software related and the fix is on its way. We trust that the information we have is correct and this is further backed by content from other sites who suggest this.

If you read it, it contradicts itself. We don't know if its hardware or software related but we do know it is software related. Terrible reporting. Should stick to "We don't know" because that is the only true statement out there right now.
[Samsung Galaxy Nexus] paul_one:
that's what I've seen.. basically a close copy of what oscillik posted here earlier copy and pasted across all websites... with no real full email or true source (some say samsung, some say google).
[Samsung Galaxy Nexus] mjdyson:
Probably not. From how I understand it, the 4.0 tree is for Android. The more critical firmware / onboard drivers / baseband etc are not open source. Hence the whole build will be with Google / Samsung.

When they decide to release the source for the phone itself, we may have a better idea of what the fix is.
[Samsung Galaxy Nexus] Roni1979:
I can´t imagine that Clove will send out an official Statement with information that Google said it is NOT an Hardware issue if they have not a real statement from Samsung or Google. They would not lie because otherwise they would problems a) with customer and b) with Google and Samsung for move information forward on market which are not correct. In this case I think they would be right and the patch will follow and everybody of us will be fine. Probably I´m a little bit naive.
[Samsung Galaxy Nexus] JcMalta:
@oscillik

I have very much appreciated the work and time you have put into this issue - but PERHAPS Clove have received some information from either Google (perhaps via Samsung) that this is indeed a software issue.

I remain open to this problem being potentially due to either software or hardware ... BUT AT THE END OF THE DAY ... it is only the TRUE engineers of this device that can say for certain.....

If those engineers LIE and try a "quick software hack" to HIDE any hardware issue, then the ultimate backwash will do great damage to both Google and Samsung. For a similar reason I can see no reason for "Clove" to send out a statement as they have to all Nexus customers if they do not believe it to be true and "from the horses mouth" ... that would destroy them too .....

Lets just keep waiting ... we will see .... personally I have always suspected software, but not having any knowledge of this particular platform have never wanted to "put myself on the line"

Again .. thank you for your efforts in raising the profile of this problem - but please always be open to those that _really_ know what the problem could be.
[Samsung Galaxy Nexus] oscillik:
Unfortunately for you, it seems that you are being naive - I reiterate again that until Google or Samsung explicitly confirm one way or the other whether this is a hardware or software issue, then no publication or company can go on record to state something that neither company has said.

---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------

Why would Google only give this information to Clove, and not make a public statement regarding the cause of the problem?
[Samsung Galaxy Nexus] jms.flynn:
Nexus Nazi - No Nexus for you!