yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cellzealot:
All of the low level components including the bootloader can be and are flashed from recovery by the updates. The files include complete system directories and images for other components, not patches, and can be loaded independently and reverted to prior builds as desired including the radios.

There is no specific reason this couldn't be pushed OTA other than that they are very concerned about not letting out anymore devices with this issue into the public domain for whatever reason.
[Samsung Galaxy Nexus] Proyoyo:
My order will be shipped on next Monday. Oh well, I guess waiting a few more days doesn't hurt.
[Samsung Galaxy Nexus] Dmw017:
Are you sure that's how it usually goes? I'm relieved that it will be reboxed and all but the whole..shipping back and forth, sounds like it takes forever :/
[Samsung Galaxy Nexus] SS2006:
This isn't an issue for me in Canada thankfully (no 900)

tested it

---------- Post added at 11:52 PM ---------- Previous post was at 11:52 PM ----------

Good thing its a software issue tho
[Samsung Galaxy Nexus] Dmw017:
its a hardware issue to be fixed with a software update
[Samsung Galaxy Nexus] gogol:
Ok, yes, lets think this is a hardware issue. Lets think from that point of view.

What is wrong with the hardware?

We could say the hardware does not protect much nor filter much the interference from specific freq? Or the rf shield material is crap? Cable too short? Rf shield leakage? Misaligned one of the chip inside?
[Samsung Galaxy Nexus] Nebucatnetzer:
Could you provide a picture of this? Can't hurt to help the software patch a bit.
[Samsung Galaxy Nexus] gogol:
Dont you think this will filter out also other freq?

Or degrade the general rf reception?

I wont do that.

The tape cant selectively filter or reduce rf interference from certain freq only.
[Samsung Galaxy Nexus] Alexander T.:
As the guy named Lee mentioned, it seems him to be a matter of bouncing, but I strongly disagree, and I'll tell you why:

The term bouncing refers to the situation, where the button is physically pressed (or released), and it takes some time until it develops good close (or open) contact. What we are dealing with here is NOT the case of bouncing! It has to do something with high input state, so-called hi-z or floating, which may be a result of wrong pullup/down value chosen for the port. It can also be an insufficient filtering issues, if they use an ADC as the button interface. So, if the root cause is the wrong pullup/down value, then it is a pure sw issue, and in case ADC is used, then again, it might be solved with sw patch, but this time we can't be sure, if its a hw filter issue or just a sw engineer's mistake.

So, to conclude, we can't be sure for 100% if its a HW or pure SW issue, until we analyze the schematics and figure out how the button interface is realized there.

More on hi-z and its vulnerability to RFI here: http://en.wikipedia.org/wiki/High_impedance
[Samsung Galaxy Nexus] davej777:
This.

If a previous poster is correct, the OMAP keypad controller is being used for the buttons. It's hard to find documentation on the exact device, but a similar keypad controller is described in this:

http://www.ti.com/lit/ug/swcu052g/swcu052g.pdf

Internal pullups are used, so the inputs should (hopefully) not be floating. I am not sure if it is possible to somehow disable them (by accident or otherwise) in the exact model used in the device.

Debouncing is handled partially in hardware, using a fairly crude method. The keys are scanned repeatedly, and when an event is detected, the value of a debounce setting is loaded into the timer (this is configurable in software). After counting down, it triggers an interrupt. It is then up to the driver in the kernel to see if the keypad state has changed.

This works very nicely for a button. The bounce time typically follows some kind of measurable distribution - if a hypothetical button is shown to settle within 10ms 95% of the time, you can set it to 20 and be quite sure that bouncing will not be observed in software.

The "GSM Buzz" is not like a button at all. It produces high-frequency pulses spaced milliseconds apart, and the spacing can vary. With simple "delay and check" debouncing, it is quite possible that a new interference event will be taking place after the delay. If "quite possible" means "more than 1% of the time", then it will happen often enough (especially during a call) that users will notice it. Of course, it won't be anywhere near as bad as it is with the current debouncing setting.

There may be a magic value that happens to work well with GSM, and the issue might become imperceptible. There may not be. Hoping that such a value exists does not make it more likely to exist.

Others have pointed out that interference issues have existed in other devices, and software has fixed them entirely. However, "interference issues exist" does not mean "interference issues exist that are as bad as this one". This seems like incredibly bad luck - the buttons just happened to be an excellent 900mhz antenna.
[Samsung Galaxy Nexus] Alexander T.:
Thanks for your input. The keyword is "hopefully", since the chances are high that the negligible current induced with GSM Buzz on the node may produce sufficient voltage to overcome trigger's threshold just because of high input impedance (V=IR, and the R>>0 in this case), which in its turn might be the result of a wrong pullup value. Otherwise, I don't understand, why only the vol down key is affected?!
[Samsung Galaxy Nexus] davej777:
It appears that the down key is closer to the radio.

If you place another GSM phone nearby, both down and up events are observed.
[Samsung Galaxy Nexus] Alexander T.:
This makes sense.

I dindn't know that before.
[Samsung Galaxy Nexus] santacruzdz:
I was going to order mine today (date of release in Germany) 24 nov 2011. now it is delayed till minimum 8 dec. other websites say 2 weeks . You said amazon.de ?? its 3 weeks "Gewöhnlich versandfertig in 1 bis 3 Wochen.

"

in France , its middle december for sure. I contacted a seller .

---------- Post added at 10:50 AM ---------- Previous post was at 10:44 AM ----------

This is exactly what it is happening in Germany and France , where shipments have been delayed for over 2 weeks .
[Samsung Galaxy Nexus] Duddyroar:
So existing owners can reasonably expect an OTA (or downloadable) update in the next 14 days, then. Let's hope it's sooner rather than later - I'm keen to see if Google and Samsung can fix this.
[Samsung Galaxy Nexus] justabrake:
so if samsung or these retailers fix these phones then aren't they now considered refurbished and can't be sold as new phones anymore
[Samsung Galaxy Nexus] M2281088:
No, the work is officially done by Samsung, though some partners will be involved, and so the work undertaken is classed as "Improvements" rather that "Refurbishment".
[Samsung Galaxy Nexus] justabrake:
But then shouldn't it be sold as open boxes
[Samsung Galaxy Nexus] jabok:
"Samsung has asked its distributors to fix stock that hasn't shipped in relation to the above issue. This affects MobiCity's inbound stock of the Samsung Galaxy Nexus.

It's not the retailers doing the fix, it's the distributors... indeed, retailers doing it would be a silly situation. Samsung may have distributors who deal solely with Samsung product in which case they'd presumably be a bit more "trustable".

Edit: Beaten to it! :p
[Samsung Galaxy Nexus] M2281088:
No as the work is done by Samsung the units are resealed by them so are still counted as "New"
[Samsung Galaxy Nexus] justabrake:
Truthfully not to argue this but I think our country's laws are different and I don't think that would fly here in the USA just saying 2 different country's different laws I don't think we allow that here
[Samsung Galaxy Nexus] IvanDobskey:
Just done my upgrade deal with o2. Deal they offered was too good to turn down. Switched to a sim only deal at £11 per month with the phone costing £390 discounted. So fingers crossed this fix comes soon!
[Samsung Galaxy Nexus] M2281088:
Granted we have different laws here but, the legal definition of "open box merchandise" on your side of the pond is not quite as clear as it should be.

The general thought is that the product has been opened for viewing or returned. What Samsung are asking is not quite the same, they are effectively "recalling" the product from distrobution to "fix" and issue before selling. Effectively the product has left Samsung but they never left distrobution and have never been available for sale in the US.

That and the release date in the US has not been released yet so no legal US sale has been done.
[Samsung Galaxy Nexus] inoplanet:
Are you sure it's delayed totally in Germany?

Telefrog.de still says they deliver in 5-8 days...and two days ago they confirmed i will receive the phone early next week.

Maybe not all stock to Germany was delayed,just a main part of it.When looking at different sites,there are still quite a few that say that will start delivering early December,just like amazon.de.
[Samsung Galaxy Nexus] bleets:
you'd be surprised.

I'm aware of a case where entire motherboards were replaced on laptops and then sold as new.

if the work is carried out by manufacturer or partner with new parts the product can still be classed as new.
[Samsung Galaxy Nexus] si450:
I posted this before but I think it got buried before anyone really took notice, and it does sound a bit daft, but... I can't recreate the issue when the phone is in landscape, get it pretty much straight away when I turn it back upright. I've kept my fingers in the same place lightly touching both power and volume rocker but as yet not reproduced in landscape.

Not sure what the significance of that is, and it doesn't really help much, but just interested if anyone else finds this.

Ta.
[Samsung Galaxy Nexus] Roni1979:
At Amazon the status is still until last week "Gewöhnlich versandfertig in 1 bis 3 Wochen." In my preorder nothing changed at the date for shipping is 01st of december. Probably they will change, but notebook.de changed the date today to shipping on 26th of November as a third party shipping of Amazone! So I don´t believe that there is more delay on it.
[Samsung Galaxy Nexus] santacruzdz:
send me the link whre it says 26 th nov...thanks ;)
[Samsung Galaxy Nexus] inoplanet:
Like i said...telefrog.de, also with amazon.de partner confirmed shipping early next week.

And "Gewöhnlich versandfertig in 1 bis 3 Wochen." does not mean it's delayed,it means first stock should come next week...
[Samsung Galaxy Nexus] jms.flynn:
I don't think the volume issue even needs user input in terms of touching the volume rocker, if you have a spare handset which works on the 900 GSM network you can literally just put the phone close to the volume rocker and it triggers the problem. You don't even need to touch the phone, on mine anyway.

I have been able to replicate in in landscape, but its good to hears everybody's experiences and how they can/can't replicate the issue.
[Samsung Galaxy Nexus] dg1qkt:
So, if this really is a software issue, why keeping the phones back?

Why are Samsung partners opening the boxes?

Software update can be done with OTA update by the users.

So I suspect that the not sold phones will get some kind of other fix (additional shielding?), so the hardware problem is fixed with hardware change.

Additional there will be a software update to hide the problem on the devices which were already sold.
[Samsung Galaxy Nexus] jms.flynn:
Some people may have no dataplan and don't have wifi. I know it slim, but still a possibility.
[Samsung Galaxy Nexus] Gundea:
The far, far simpler explanation is that Samsung wants to avoid as much bad PR and customer experiences as possible. They do this neatly by performing the software update themselves.

Remember that many ordinary customers have no idea about these kinds of things, so Samsung is doing everything they can to keep their reputation somewhat intact.
[Samsung Galaxy Nexus] justabrake:
you really have to wonder what samsung is doing here, someone should compared fixed phones by them and ones that aren't.
[Samsung Galaxy Nexus] andrew.k:
What software update you guys are talking about? Has anyone got updated yet? Look, yesterday Samsung ang Google declared that an update had already been developed, so where the hell is it? I believe they have no update at all, and are developing plan B instead.
[Samsung Galaxy Nexus] Gundea:
Getting quite conspiratorial, are we?

They're probably doing some thorough QA on this update, to be absolutely certain that it fixes the problem and doesn't negatively affect the user experience of the device. After all, it would be pretty damn bad PR for both Google and Samsung if they state that they've solved the problem when they haven't.
[Samsung Galaxy Nexus] justabrake:
This whole thing has been a coy by samsung and google they need to publicly speak up
[Samsung Galaxy Nexus] oscillik:
I think we've gotten about as much as we're going to get out of them for the time being.
[Samsung Galaxy Nexus] Gundea:
They've publicly stated that a software update is incoming which will fix this problem, what more do they need to say?

I think that a lot of posts here are overthinking this whole situation.
[Samsung Galaxy Nexus] andrew.k:
Exactly, and the PR would be even worse if (just a suggestion!) it appear that in some aspects, i.e. in bootloader behaviour, the issue can not be solved by software update at all. In other circumstances it would never be discovered, but in this particular case worms have crawled too far from can.
[Samsung Galaxy Nexus] Roni1979:
http://www.amazon.de/Samsung-Smartp...SE6I/ref=sr_1_1?ie=UTF8&qid=1322140878&sr=8-1

Here the Link with available from 26th of November (notebook.de)
[Samsung Galaxy Nexus] gstadt:
I wonder if Samsung and Google engineers have been reading this thread to better understand the issues? They might even be reading it right now :eek:
[Samsung Galaxy Nexus] silent_killa:
I can recreate the issue sitting the device on top of a Dell PowerEdge 1950 server.
[Samsung Galaxy Nexus] paul_one:
Hmmm, this doesn't bode well for those of us going into server rooms...
[Samsung Galaxy Nexus] Evostance:
Shouldn't be taking your phones into datacentres/server rooms though ;)
[Samsung Galaxy Nexus] silent_killa:
Yeah, cant reproduce it everytime but it does happen 4/10 times. The phone however is directly on top of the server sinces its on my desk atm.

Will try it in our main datacentre in the basement in a mo.
[Samsung Galaxy Nexus] paul_one:
Haha, cheers.

Very true....... *looks shifty*

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

http://www.youtube.com/watch?v=I6o0H5phdyc

Somebody's reported an auto-upgrade of his phone.

Anyone seen any more reports/recently tried to update?
[Samsung Galaxy Nexus] oscillik:
this isn't an Android update. I've had this screen many times when rebooting the phone.

An OS update would ask you before downloading and installing.
[Samsung Galaxy Nexus] gix_0:
hi

Been following this tread very closely and alltough i don't have a GN yet, the site where I am going to buy it from (expansys.pt) have just sent me an email stating that Samsung has halted all GN shippements to "resolve an issue". :confused:

I am in Portugal btw and I am also convinced its a hardware problem, but i also think it can be solved in software... hopefully on a bootloader level.

Also a question: is it possible to flash the firmware OTA? (My money is on no...) :rolleyes:
[Samsung Galaxy Nexus] oscillik:
The only logical business reason why Samsung are halting shipping, considering the information we now know about the hardware fault and it's software fix, is that Samsung do not want to cause more customer outrage and disappointment with handsets that currently do suffer from the problem, so they are waiting until the software fix is pushed out before continuing shipping.

Considering the explanation of the hardware fault, and it's software fix, there is no reason to believe that this software fix cannot be sent OTA.
[Samsung Galaxy Nexus] bleets:
I thought we'd established that since you'll get the same inteference on any handset you can't class it as a fault and the fault lies with the software handling it? ;)

I would very much like you to modify your wording on this issue!
[Samsung Galaxy Nexus] oscillik:
you have established yourself to be a troll.
[Samsung Galaxy Nexus] gogol:
The more logical reason would be:

* Samsung will apply this fix because not all customers have "data" subscription to receive OTA

* Sure, customer can use WIFI, but not all customers are smart enough to know how to update their phone.

Thus, it is logical for issue as important as this is (phone cannot be used on 2G because muted), Samsung must apply the fix before the phone is sold to the customer.
[Samsung Galaxy Nexus] bleets:
nope not a troll.

i'm pedantic.

you're still really pushing that it's a hardware issue, the way you word your posts always says the hardware needs fixing. not the case. you spend your time on here spreading misinformation and it's a tad irritating. modify the way you word it. simple as that.
[Samsung Galaxy Nexus] Ladrero:
I agree with you.

In addition today Samsung Italy announced on its website that the phone will be available on December 1.

I don' think Samsung will sell defective terminals, so the December 1 or before everything has to be solved.

Source: http://www.samsungmobilestore.it/samsunggalaxynexus.aspx
[Samsung Galaxy Nexus] Duddyroar:
That happens every time you reboot the phone. Misleading wording, TBH.
[Samsung Galaxy Nexus] Erazor786:
Its laughable how many people are still saying that it isn't a hardware issue and seem to carry on having a dig at Oscillik for stating it is indeed a hardware fault.

All Oscillik is doing is keeping the information in the thread accurate. Check back in the thread and you will see the proof that a Google worker confirming that it is indeed a hardware fault yet individuals still persist to state it is not.

EDIT: Please read the first post in the thread which outlines everything their is to know about this hardware fault and the link to the confirmation that it is a hardware fault. Poster should be reading that post before replying to this thread anyway....
[Samsung Galaxy Nexus] oscillik:
actually that does make sense way more than what I said, you're right - I didn't think to realise that not everyone who buys this phone will have a data connection (although personally I think if you're going to buy a phone like this and not have at least access to a WiFi connection, there's something silly there...) but you are right - halting shipping and applying the fix at Samsung makes better sense.
[Samsung Galaxy Nexus] Duddyroar:
Let's also not forget that some owners may power up the phone for the first time and get a 2G signal as soon as their SIM card connects to the network (as it did in my case) and the fault will appear instantly (again, as it did in my case). Not the best first impression, so if Samsung can fix beforehand, that's what they'll want to do.

Sending out a phone in a 'faulty' state only for a day-one patch to be applied doesn't exactly generate consumer confidence (not that there's much left after the events of this week anyway).
[Samsung Galaxy Nexus] FISKER_Q:
I personally don't get why they just don't do it in the store, the phone usually gets setup there anyway (simcard, transferring contacts, etc.)

Could easily do an OTA as well.
[Samsung Galaxy Nexus] Sweerts:
You forget all the phones bought on the internet. And when I buy one in a store, then I would not accept a phone in a box with a broken seal, for instance. No matter what the explanation of the seller would be.
[Samsung Galaxy Nexus] oscillik:
definitely not a good first impression :(
[Samsung Galaxy Nexus] mark.m.moran:
Just got mine today here in Ireland on Vodafone and noticed the issue pretty much immediately :-( I am also having issues with PowerAmp and music crackling as soon as the screen powers off. While the screen is on it plays perfectly. Anyone else had this issue?

Cheers,

M
[Samsung Galaxy Nexus] neovisage.HD2:
right i have my gn from phone4u sim free without any contracts what should i do?going there and give it back?or just wait for OTA? Im with uk three network have this phone for four days now without any faults!even when i change in setings only for 2G!how many owners have the vol issue?
[Samsung Galaxy Nexus] oscillik:
Here is the existing thread regarding your audio buffer issue

As for the volume issue, I'm sure you've already read the first post so you should hopefully understand that there is a software fix in the works for the fault. :)

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

If you had read the first post, you would know that the fault doesn't occur with 3 because 3 uses a completely different frequency band. Not only that, but there is a poll right at the top of the page that clearly states that (at the time of my writing this) 161 people that use this forum have reported having the fault, which equates to 67.36% of the users who have voted.
[Samsung Galaxy Nexus] Skysurfer69:
Mark the post that provides the solution is here
[Samsung Galaxy Nexus] FISKER_Q:
Yes, of course, for internet shops it makes sense.

And obviously the seal would be broken when they setup your phone, that doesn't mean the seal has to be broken before that.
[Samsung Galaxy Nexus] neovisage.HD2:


Then what is your recomendation?give it back to phone4u or just wait for OTA?

Thank You
[Samsung Galaxy Nexus] BiGMERF:
engadget just posted there review of the galaxy nexus. they report that they are unable to reproduce the volume bug here state side
[Samsung Galaxy Nexus] justabrake:
who knows if someone is returning a phone with a screen problem
[Samsung Galaxy Nexus] CJSnet:
Sooo anyway, moving on... Can anyone confirm whether the over the air up date will make us lose root or not?
[Samsung Galaxy Nexus] ericshmerick:
Mine gets here tomorrow and I'm absolutely not concerned about this issue since I'm in the states.
[Samsung Galaxy Nexus] oscillik:
Since you're not experiencing the problem due to being on 3, then you would probably be best just keeping hold of the phone.
[Samsung Galaxy Nexus] phillipm:
I'm a bit concerned here, I was promised a fix for my galaxy s which obviously never happened.

Hope the fix comes before my right to return it!.
[Samsung Galaxy Nexus] justabrake:
what happens if he wants to sell it later
[Samsung Galaxy Nexus] Sorry what?:
--- EDITED!! ----
[Samsung Galaxy Nexus] blunden:
Perhaps that's what usually happens in Denmark but it's certainly not the "usual" case. A lot of people buy phones either online or in normal eletronics stores. Many times, even when people buy them with a contract there is no setup in the store. I rarely see someone setting stuff up in the store personally but sure, it probably does happen from time to time. It's very easy over here and probably in Denmark too as we don't need any form of activation that seems to be required on all carriers in the US. Just plug in the SIM and boot it up.

Yes, you did. ;) Unfortunately it's not in the first post so it's easy to miss.
[Samsung Galaxy Nexus] jaketurbo:
It's very unlikely they will EVER change the production line.

If the software fix is simple and effective, it removes the need for an expensive manufacturing change.

Really, people are being so OTT it's quite ridiculous.
[Samsung Galaxy Nexus] matt2053:
Yes you do arrive late, this was thoroughly discussed several pages back. Please search and don't clutter the thread.
[Samsung Galaxy Nexus] Sturmtief:
I'm happy to have bought the Galaxy Note instead.... Phew! :-)
[Samsung Galaxy Nexus] atomic_dude:
I couldn't agree with you more. However, I was replying the the Aussie member and my response was in the Aussie context, with a reliable 3G network coverage. Of course I wish Samsung/Google will fix this ASAP. Fingers crossed I'll not find bugs related to 850MHz 3G either :D
[Samsung Galaxy Nexus] oscillik:
I'm hoping there won't be any issues with 850MHz either...my significant other is hoping to get one, and she's in the US...