yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] IvanDobskey:
But can't you see that all complex electronic devices are likely to already have software fixes? Do you think everyone designs the perfect device? Or when they find a hardware issue during development just start again from scratch?

Nope, they do a software patch :) Samsung / google just got sloppy and let this one slip out the door unpatched. If they had patched it first then we would all be none the wiser.
[Samsung Galaxy Nexus] owen243:
Does anyone think also that the highest volume setting is REALLY low compared to other phones?

Ive missed a few phone calls and not known a notification has popped up today (Coming from a Iphone 4/BB 9780). Partner has a Sensation XE, and other family GS2 and mine is the lowest by FAR.

Is anyone thinking the same or is it just mines that faulty.

Any response is much appreciated,

Michel
[Samsung Galaxy Nexus] dawgpound6985:
P3Droid just claimed he received the update just a few minutes ago:

https://twitter.com/#!/P3Droid/status/139431642660999168

This is the same guy a lot of you discredited earlier about Google releasing a software update to fix the volume problem. In other words, he's legit.
[Samsung Galaxy Nexus] ShiroEd:
It's not just you dude.

LOTS of people are saying the volume is too low including myself. :o
[Samsung Galaxy Nexus] Gho57:
inside 4.0.2 OTA there is a fix for keyboard auto spell check:

Everytime you write accidentally the word "hardware", is correct in "software".
[Samsung Galaxy Nexus] Lcrkz0023:
Negri ...will ship to intl affiliates like Expansys also...just letting you know. Its in their policy. I also asked them about that and they reassured their policy....Other than that, you are absolutely correct on everything you said. and I agree.
[Samsung Galaxy Nexus] darkoroje:
No device is perfect, but obvious problems like this are usually detected during testing and fixed with extra shielding. It appears that neither Google nor Samsung tested the phone with 900 MHz band, which doesn't exactly inspire confidence.

I had a Galaxy S and the GPS never worked properly; Samsung never fixed it, instead they went on and released several US variants which had the same poor GPS despite Samsung promising they would fix it. So a "wait and see" attitude is justified in this case.
[Samsung Galaxy Nexus] :
according to p3droid, look out for icl53
[Samsung Galaxy Nexus] owen243:
No ones making THAT much of a big fuss over it. To be honest being in London i ALWAYS get a 3G signal so im not much affected by the Ghost problem but i have tested it and yes it did rapidly bring my phone to 0 volume.

But however i really hope they fix the low volume, its so annoying the fact i miss important calls for business and this morning the alarm went off and i didn't hear it.
[Samsung Galaxy Nexus] ballonic:
Incorrect. The problem would be fixed with the most economical fix that does not impact the end-user experience in an unacceptable way.

What you're proposing would most probably result in a phone that weighs a ton because of all the additional shielding (user experience), and would most probably ship late too (economics of the fix).

Greetz.
[Samsung Galaxy Nexus] blunden:
All I was saying was that Clove, Handtec etc. should handle it for you. They are authorized sellers as far as I know. The "they" I was referring to were those stores. I agree eBay purchases etc. are probably problematic.

I also thought I said that Samsung US would refuse to handle it, just as you said.

On a related note, there can be some instances where the store can send a warranty document granting you warranty in your own country. An example is when handyattacke.de (a German store, as the domain shows) delivered Samsung Galaxy S phones to Sweden with a document that granted warranty in Sweden. Samsung confirmed it was valid. I have no idea how they managed to do that though.

All in all, I think Samsungs anti-import warranty terms for phones are stupid and should be reworked. I understand them in the cases where different countries have different terms for what constitues a "fault" but for phones that's rarely the case. An example would be how Samsung TVs sold in Sweden guarantee no dead pixels while the same TV i Germany is allowed to have a few dead pixels, in return for a slightly lower price. I use Germany as an example because it's a common country for people to import electronics from for Swedish consumers.
[Samsung Galaxy Nexus] jabok:
You mean the ringer volume from what you write here... wrong thread, this is a whole other issue! :p

BUT, Check out Volume+ here (you can get the paid version legally for free at the author's site) -> http://androidaudiohacks.com/home/ - totally "fixes" the low volume issue.
[Samsung Galaxy Nexus] oscillik:
confirmation from Google employee Dan Morrill that this is a hardware issue
[Samsung Galaxy Nexus] owen243:
Hey,

Yeah i got the Ghost volume as every other user but im also just saying the ringer volume is way to low for people who work in busy environments.

I will try that out now and comment :)

Thank you :)
[Samsung Galaxy Nexus] Rubu:
ALL CHIPS have to deal with debouncing, this is often done in software. As the post Dan is replying to states, this is apperently not sufficiently tested, so this really isnt a definite hardware problem. If the chip has a programmable debounce counter, this problem would be completely solvable by making that value a little higher.

Btw; thought you gave up on this thread?
[Samsung Galaxy Nexus] oscillik:
it is a definite hardware problem - two engineers have confirmed it.

and I had given up on dealing with people who couldn't accept facts. I just came back to provide proof. :)
[Samsung Galaxy Nexus] owen243:
Jabok you life saver!!

Volume + is AC! Sound is now loud :)
[Samsung Galaxy Nexus] rokfor2000:
As far as I know they didn't manage to do anything. The warranty would be valid anyway, it doesn't matter if they sent any additional documents with the phone or not. Warrany must be europe-wide whenever Samsung likes it or not. It also must be at least 2 years for new goods. Directive 1999/44/EC, May 1999 from the European Parliament.
[Samsung Galaxy Nexus] oscillik:
So why did Samsung refuse to honour the warranty of the SLCD version of the Nexus S that was intended for Europe (and not the UK) but was grey-imported into the UK?
[Samsung Galaxy Nexus] Rubu:
So even if the problem is completely solvable in software, as in, change register value and the phone acts excactly the same as a HW revision would, you'd still call it a HW problem? Because that just sounds like a software to me.

PS:I have a background in electrical engineering myself.
[Samsung Galaxy Nexus] oscillik:
Yes, it is still a hardware problem. a hardware problem with a software workaround.
[Samsung Galaxy Nexus] Rubu:
It's not a workaround, probably every phone you ever owned dealt with noise on the button pins like this. Phones could never be this small if they needed sufficient RF shielding to not pick up on any RF interference. Anyway, believe what you want to believe.
[Samsung Galaxy Nexus] jabok:
Isn't what the engineers said a case of it being a VERY COMMON hardware problem that is ROUTINELY worked out with software? i.e. they don't necessarily design, or expect perfect hardware but rather expect to "tame" the hardware with software.

Seems like everyone was right to a degree - let's all hug and let it go FFS! :rolleyes: ;)
[Samsung Galaxy Nexus] Mehrsau:
I can't believe how one single human being can repeat himself that often. Respect. You must have a lonely life.
[Samsung Galaxy Nexus] IvanDobskey:
So when is this fix going to be available? I want to get my Nexus on Friday so hopefully by then?
[Samsung Galaxy Nexus] santacruzdz:
Friday?! Haha ....this is a serious issue ..it will takes longer to fix the problem.shipments in Europe have been delayed till middle December because of this issue .
[Samsung Galaxy Nexus] saquib:
Well, if p3droid is already running the fix, should be out soon - either official or leaked.
[Samsung Galaxy Nexus] IvanDobskey:
Well from what i've read I don't think it will be more than a few days to wait. Here's hoping anyway. Ah well, I can always use my iPhone 4 until the fix is released.
[Samsung Galaxy Nexus] kristovaher:
I have updated the original post with the latest information from Samsung, Clove, Handtec, Dan Morrill and Lee Johnston.

I guess there is only one step remaining. If the patch fixes the problem then I will forever remember this thread. (Hah! Bloody likely that I will forget about it the moment my own handset actually arrives and I get to play with it)

If the patch does not fix the problem, there is a whole new can of worms to be argued about! But let's hope for the best. This thread has been quite epic so far :)
[Samsung Galaxy Nexus] blunden:
Samsung themselves specifically states that a phone outside Sweden (or rather the Nordic region) won't have warranty from Samsung Sweden. They did say in that instance that only if you also had that specific warranty card would it be honored in Sweden too. You were still entitled to the full warranty coverage provided by Samsung in the country of purchase though.
[Samsung Galaxy Nexus] bleets:
where did you get that from...

last thing i read about UK shipments was a 48 hour delay
[Samsung Galaxy Nexus] appelflap:
Epic as far as it contains a lot of offenses lol
[Samsung Galaxy Nexus] blunden:
I was just about to ask that. I see no source stating that long of a delay but rather something in line with what you suggested.
[Samsung Galaxy Nexus] rokfor2000:
Well, I must be wrong then. I never dealt with Samsung customer services before. However some time ago I did manage to convince HP to sort out for me some equipment bought on the mainland, they didn't want to do initially. Guess I was lucky :)
[Samsung Galaxy Nexus] Roni1979:
Where did you get the information that the shipments are delayed to middle of December? Amazon Germany has already confirmed shipment on 01st of December. In my preorder nothing changed on the date.
[Samsung Galaxy Nexus] s1977:
I am finally glad to hear that this can be fixed by a software patch and that this is a common occurrence in these type of devices...i.e. you can't eliminate RF interference completely..well, after reading over a 100 pages and with a lot of arguing back and forth for absolutely no damn benefit to anyone.... ;)

OP, just being pedantic but can you correct the "this type of hardware flaw to be patched with hardware" from your original post to "this type of hardware flaw to be patched with

software

" instead? I am really too tired to read anymore about hardware issues.... ;) ;)
[Samsung Galaxy Nexus] :
Those of you with the issue. Any issue with the proximity sensor and light sensor?
[Samsung Galaxy Nexus] regorsnas:
oscillik you are the boss !!

And now seroisly, it really is a hardware problem after all. But a problem than can be solved with software fix. And as I understand a software fix that won't be problematic with the battery use, or ram, etc

I decided to order the Samsung Galaxy Nexus anyway, jeje
[Samsung Galaxy Nexus] drkstl:
I'll try and borrow a friends phone to upload a video, but i found a temporary fix by putting electrical tape over both the antenna(?) above the battery and over the volume button. Hasn't replicated fault since. Tried with duct tape first but still had fault
[Samsung Galaxy Nexus] Chirality:
Man, I know Dan Morrill confirmed it and all, but it's still hard for me to take anything Lee Johnston says seriously.

Remember, he was the guy behind this: https://plus.google.com/106493827472880328627/posts/eXXc6W3s91f
[Samsung Galaxy Nexus] oscillik:
People can get things wrong. I have been wrong in the past, and indeed on this forum.

Doesn't change the fact that a Google engineer has confirmed that what he says is the case with the Galaxy Nexus.
[Samsung Galaxy Nexus] Jebus99:
Just to toss things up, but does anyone have proof that this kind of software debouncing isn't enabled by default on other phones like the SGS2 and we never noticed it because they never shipped with debouncing off. How does anyone know this isn't a standard practice done by most handset manufacturers. That would mean that this "hardware flaw" is just a part of phone design that can't be avoided and software debouncing is done on all phones to prevent it being an issue.
[Samsung Galaxy Nexus] Chirality:
Yeah, Dan Morrill's confirmation is the only thing that makes it legit. If this were just Lee Johnston, though, I wouldn't take it seriously for a second.

It's not that he got things wrong, he was just making crap up. Maybe you weren't paying attention to all this stuff when he made that post about the Nexus Prime specs. But basically what happened was BGR posted what turned out to be completely accurate leaked specs of the Galaxy Nexus. Then this Lee Johnston guy came out with pretty much made up specs for it and called the BGR leak "bogus". And for some reason a few blogs picked up on the specs that Lee Johnston made up, and people got false hope that the specs of the Galaxy Nexus would be higher than what BGR was reporting. Of course it later turned out that BGR was completely right and Lee Johnston was completely wrong, and people's hopes were dashed.

Not only that, it seemed Lee Johnston had no basis whatsoever to claim what he did. He has no industry connections. He was either just plain making stuff up, or it was just wishful thinking. He wasn't even qualified to make these judgments. To call him a "developer" is a bit of a stretch. He has this one man company where he tries to make this twitter app that isn't released, and his day job is a truck driver or something that I can't really remember.
[Samsung Galaxy Nexus] oscillik:
It has already been mentioned in the Google+ post that I linked to that this kind of hardware related issue is normally accounted for with software.

Regardless of the (now established) fact that software can filter this out, the fact remains that the problem is manifested because of interference with hardware, as outlined in said Google+ post.
[Samsung Galaxy Nexus] Chirality:
It's pretty much common knowledge that whereever you have a lot of electronics packed closely together you have to use a lot of algorithms to filter the signal to get what you want.
[Samsung Galaxy Nexus] oscillik:
Wow, that is a bit of a hole he's dug himself into.

Probably much like the one I've dug myself into with the community here :rolleyes:

I can understand why you are disbelieving of this guy, if he had caused that much aggro. But this is why I have been so 'nazi like' with regard to sticking with established information gleaned from this thread - Blogs and Tech sites like this usually don't get the full details and things like this happen :-/
[Samsung Galaxy Nexus] bleets:
I think that since you can pretty much guarantee every handset is susceptible to interference yet all have measures in place to stop that being an issue, it can be said that the GN does not have a hardware fault/issue at all and the fault is a software problem all along! :rolleyes:

isn't interpretation great? ;)
[Samsung Galaxy Nexus] s1977:
Steady now....:D Don't bring this one up again! :rolleyes:
[Samsung Galaxy Nexus] TonyHoyle:
I'd go somewhere in the middle and say it's a firmware problem :p
[Samsung Galaxy Nexus] Luxferro:
That's pretty much it.

Software controls the hardware and determines what is a button press, and what isn't. For the skeptics, google debounce, and learn what it is, and how it works. One of the first hits is this page which gives you a pretty simple explanation of what it is, and how it can be controlled. http://www.arduino.cc/en/Tutorial/Debounce
[Samsung Galaxy Nexus] Chirality:
Makes me kind of wonder what the software fix is going to do, exactly.

If it's a fix at the Android OS level, then it's not going to stop the hardware interrupts from causing context switches in the CPU which is bad for performance and battery life. It also wouldn't stop it from happening in fastboot mode.

But maybe the fix isn't at the Android level at all. Instead the fix might come with a firmware updater program that makes Android flash the button microcontroller firmware on next reboot or something like that, and the updater then changes which input events the microcontroller passes onto the IO bus. If the fix is at this low level, then the problem would disappear completely.
[Samsung Galaxy Nexus] Rubu:
it would be very silly to debounce after the interrupt generator, so I'm guessing it will be closer to the 2nd scenario than the 1st. (I also hope so, because that would be the 'best' solution, far better than handling each and every button interrupt and then filtering false positives)
[Samsung Galaxy Nexus] Chirality:
I hope it's the second one too. My only concern is, we don't know if it'll be possible to flash that particular microcontroller firmware from the phone OS. What if that particular firmware can only be programmed via JTAG? Then this software fix can only be another layer of debounce on top of the underlying firmware, but not change the behavior at the correct layer.
[Samsung Galaxy Nexus] dnlsmy:
Google Dev Dan Morrill sheds some light on the problem. It's hardware related but can be easily bypassed through software.

https://plus.google.com/u/0/112413860260589530492/posts/1a4hY7VeqiG
[Samsung Galaxy Nexus] jeffreyng:
Guys, maybe we should step back and just wait for awhile. after all google is a top tier company, their engineers are definitely one of the top players in their field. the solution they propose should be better than what you and I could have done.
[Samsung Galaxy Nexus] paul_one:
+1 on that one (hoping we update something sufficiently low enough).

I also want to say thanks to drkstl who has used electrical tape to effectively block some signals (unlear if it's internal, external or both).

I will be adding my own custom "shielding" to reduce the effect of the EMI radiation (obviously testing the network signals whilst doing so).

I also want to say thanks to everyone in here, this has indeed been an epic thread.

Hope all you guys are pleased with the phone and the resolution of this problem.
[Samsung Galaxy Nexus] dnlsmy:
...it's been fixed already...

They simply increased the ms interval...
[Samsung Galaxy Nexus] ericshmerick:
Seriously. The knee-jerk OMG DEFECTIV HARDWEAR posts are getting old.

Everything is fine. It's fixed. Had it been fixed before it was identified, nobody would have ever known there was an issue...
[Samsung Galaxy Nexus] matt2053:
Well, some software somewhere is already monitoring time of inputs, so we are not talking about introducing new monitoring and filtering, we are just talking about modifying a setting.
[Samsung Galaxy Nexus] CJSnet:
Zzzzzzz...
[Samsung Galaxy Nexus] Chirality:
Well, yes, but we don't know if the software that's doing the low level detection and debouncing of the volume rocker reside in easily-modified flash or EEPROM, or if it's in some kind of difficult-to-modify memory.
[Samsung Galaxy Nexus] juicytuna:
They say they have a fix that will completely cure this problem without any noticeable side effects. Let's leave aside the cynicism for now, something this thread could have done without from the start actually.
[Samsung Galaxy Nexus] paul_one:
Please can you link to where this "no side effects" quote is from Google?
[Samsung Galaxy Nexus] juicytuna:
//comment withdrawn
[Samsung Galaxy Nexus] paul_one:
I've been searching and waiting for any updates to see if anyone other than that p3droid guy has had the update.

Was wondering if you had some sort of link, as you stated it pretty plainly.

If you don't have a source, fine.. I'll continue waiting for any test results to be put up here.
[Samsung Galaxy Nexus] juicytuna:
Then I apologise for my comments. I'll see you all when the fix is issued.
[Samsung Galaxy Nexus] cellzealot:
Our phones are both engineering models as well as CDMA/LTE radios, so the builds we get pushed are not compatible with the GSM UK devices. They have a different kernel too as far as we know.

I suggest waiting for the official release that is designated for your phones.

We were not given changelogs or release notes, just told that the ICL53b update did in fact contain the fix for the global models. This was then independently verified by another source from Samsung who told us to spread the word that the fix was ready.
[Samsung Galaxy Nexus] Mr.Kakarot:
So if it's simple software, why the delay in shipping?
[Samsung Galaxy Nexus] paul_one:
Cheers team blackhat.

Do you know if the code will be available / pushed to the upstream android git so that custom ROMs don't suffer the bug?
[Samsung Galaxy Nexus] StuMcBill:
I wonder if SamOogle are waiting till the middle of the night (UK Time) to push it so that users will have a nice "Update Waiting" when they wake up.

Either that or it maybe affects some seriously low level hardware so they want to make 100% sure it will not fry any phones when its pushed?
[Samsung Galaxy Nexus] projectshadow:
I don't no if some one publish this video http://www.youtube.com/...qXjARxvErjk but in this case i think is hardware, can some one try to disable one aplicacion like beam or compass to test it??? and try to understand what's doing that crazy problem. to know if the problem is realy hardware or software
[Samsung Galaxy Nexus] matt2053:
If the fix is in Android, you will see it in AOSP. More likely though, it will be a new driver, which are nit open source but the binaries are also available from Google and the new ones will be made available. So custom ROMs will be fine either way.
[Samsung Galaxy Nexus] deadlast28:
Recent Update from Mobicity:

Guys,

Very fresh news of distributors holding some of the stock at Samsung's request to do the update before supplying. This will affect about half of our pre-order stock (the one's going out tomorrow) and new orders will be affected too. Shipment for the affected orders might be able to resume Monday.

Sorry, this is brand new news, I wanted to get it on here first.

I'll post again shortly with an update on MobiCity's response to this.

Cheers,

Darren
[Samsung Galaxy Nexus] Dmw017:
So they are going to get their nasty a$$ hands all over my Nexus to update the stupid thing when I could just as easily do it at home?

edit: oh nvm Mobicity .. Im with Handtec XD ... still, hope neither of them officially unboxes and updates anyones nexus >.> bleh
[Samsung Galaxy Nexus] Proyoyo:
Update from their website:

Hi everyone,

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. The current shipping situation is as follows:

Shipping today: All orders up to MobiCity Australia order ending in 41009 and MobiCity New Zealand order ending in 04408.

Shipping on Saturday 26th Nov: All orders up to MobiCity Australia order ending in 41768 and MobiCity New Zealand order ending in 04533.

Further shipments should resume on Monday the 28th of Nov but this may slip to Tuesday if there's logistical issues in moving so much stock around.

We will keep this post updated with as much information as possible as the situation develops.
[Samsung Galaxy Nexus] noobdeagle:
you know if it was an OTA update they could just ship but because they are not im kinda wondering if the updater operates in like download mode to update something at a lower level than the android os itself. speculation of course :P
[Samsung Galaxy Nexus] Dmw017:
Does anyone know what they mean by "fix stock" ... The retailers aren't seriously going to take the innocence of the boxes right?

Maybe I'm just nutty, but I don't like having my unicorn unboxed for me in some dark and lonely warehouse for no real reason.
[Samsung Galaxy Nexus] noobdeagle:
i think you will find faulty stock would be sent back to samsung, samsung will update then rebox and send back to retailers, retailers wouldn't do the update