yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] JcMalta:
@ oscillik

I am sorry you feel this way ... your efforts to make this issue raised to a high level have been great and worthwhile.

However, please review your stubbornness and arrogance in your replies ... for myself I do not worry ... I just count them as the rants of someone who will not move or listen - and who is also DEEPLY upset that the new "toy" is not working perfectly ......

And before another rant from you ... YES I HAVE READ THE ENTIRE THREAD .. the most tiresome? I have had to continually read to your self-centred opinions and "expert" knowledge backed up with nothing more than a few anecdotal yet "scientifically proven" theories, while you continue to berate, insult, belittle and troll against ANYONE that does not agree with your really quite narrow personal view.

Your contribution toward highlighting this Nexus problem HAS been extremely valuable .. but if you find another "cause" in the future, please consider the good you could do against the way you could go about achieving it ....

To quote yourself: "Well done trolls. You win."

I hope so ... your insults and obvious disrespect and contempt shown to some people (perhaps less "knowledgeable" than you - but never the less were eager to find out the _truth_ about this problem) has sometimes been quite remarkable.
[Samsung Galaxy Nexus] rob6raham:
Anyone else finding their power button stops responding after a fit of volume changing?

Been very bad today. Could be minimal 3G signal.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Duddyroar:
Yup, I've had that happen a few times - worryingly, the power button is briefly unresponsive even AFTER the volume buttons become responsive again.
[Samsung Galaxy Nexus] qwerp_:
have they got something to hide?

why post it in grey letters? where its hardly readable unless highlighted.
[Samsung Galaxy Nexus] jms.flynn:
It's highlighted buddy.
[Samsung Galaxy Nexus] paul_one:
Thanks jms.flynn for the youtube vid... I was hoping for a graph - *BUT* this is still valuable (geez - 35%!).

Sorry to see you vanish oscillik - I for one mirror your hatred for those who can not see the method in the madness.

Anyone following the thread would have seen previous posts and not posted the exact same quotes as 5 posts earlier.

Also to those who are looking at a 'fix' which might take into account frequency patterns to try and logically block out the button presses, That requires more memory, more CPU calculations, and also it needs some variance (ie, 330 +- 10)... Now seeing as how a users press on the button would be only 1 in this variance, please tell me how you can mathematically spot a single pin in the middle of a 10ft pin pile.

Just read about the power button - interesting! Could either be the buffer emptying, or it might be the hardware chip having to clear some registers... Another thing to test for I think (when this 'patch' comes along).
[Samsung Galaxy Nexus] oscillik:
are you even reading the thread? it is becoming increasingly apparent that the only people who are being affected by this are people who are on a network that runs on 900MHz (that means O2, Vodafone, giffgaff, Tesco Mobile). Since you're on Orange, you wouldn't be affected by this.

---------- Post added at 01:40 AM ---------- Previous post was at 01:39 AM ----------

this problem is only occurring when on 2G.
[Samsung Galaxy Nexus] BiGMERF:
so im screwed on tmo
[Samsung Galaxy Nexus] LadFromWales85:
Interesting. Has it been confirmed that 900MHz 3G doesn't effect the buttons?
[Samsung Galaxy Nexus] oscillik:
it hasn't been confirmed yet, but the majority of cases here are highlighting these trigger factors
[Samsung Galaxy Nexus] bisquick24:
It lacks USB OTG? Is that confirmed??
[Samsung Galaxy Nexus] oscillik:
no it isn't confirmed. please could we keep the thread on topic? there is already a thread regarding USB OTG in this very forum.
[Samsung Galaxy Nexus] LadFromWales85:
Hopefully someone from Samsung or Google will chime in soon, the phone has only been out one working day so far!

I'll get mine today hopefully. Conveniently I use both Vodafone and o2 so will see how it goes.
[Samsung Galaxy Nexus] oscillik:
If you could report back with your experience, that'd be great.
[Samsung Galaxy Nexus] paul_one:
Just quick question, have we mapped out roughly where the problems are being experienced, and also where the phones came from? ... IE, is it 1 person down south while 10 people are affected up and around Liverpool...

Also, I have ordered my GN, it will arrive on Wednesday.

I have an o2 sim card currently, and am getting a 3 sim card with the phone. Hopefully I should be able to switch between them and test it out.

Is it possible to force 2G? If not, I might be able to try and force it to use it, there's a large dead zone nearby and I should be able to get it going through 2G at least.

... I'm guessing data is on whilst this is happening... What about bluetooth/wifi/etc ?

I want to try and match the conditions as closely as possible.
[Samsung Galaxy Nexus] atomic_dude:
So 900MHz on 3G won't trigger the volume issue due to lower signal power than 2G, right? Lucky I'm always hooked to a UMTS network then...
[Samsung Galaxy Nexus] oscillik:
these are the known trigger factors so far

yes you can force it into 2G mode only, just go to Settings > More > Mobile networks > Use only 2G networks

I personally have always kept bluetooth switched off, and the problem occurs regardless of whether I have WiFi enabled or not.
[Samsung Galaxy Nexus] Chirality:
No, there are no USA GSM networks that use 900MHz.
[Samsung Galaxy Nexus] StuMcBill:
Looks like I will be waiting for this to be acknowledged / fixed before buying my Nexus since I only get O2 2g at home!

Has anyone tweeted @googlenexus about this?

Sent from my Amiga 500 using Workbench!
[Samsung Galaxy Nexus] pukemon:
Im not 100% sure but i am 99.9% sure usa uses only 850/1900 for 2g/3g. I think 900/1800 are mostly europe. 2100 im not so sure about. Tmobile might use some 2100 in the usa.

I invented cyberspace. You're trespassing.
[Samsung Galaxy Nexus] oscillik:
i'll give it a go, but there doesn't seem to be much point - as I've already said, I've messaged Google employees on Google+ about this issue and have heard absolutely nothing back yet.

I am saddened to say that I don't think this will be looked into by either Google or Samsung until there is some major tech news coverage on the issue. I've already informed GSMArena and The Verge about this. I'll be getting in touch with more tech news sites tomorrow.
[Samsung Galaxy Nexus] Clancy_s:
In case of any other passing aussies: Telstra, Optus and Vodafone 2g all use 900 MHz as well as 1800 MHz. :(
[Samsung Galaxy Nexus] Chrono_Tata:
I know everyone wants this thing fixed ASAP but c'mon guys it's the weekend. I don't think even Google engineers come to work on Sundays.
[Samsung Galaxy Nexus] atomic_dude:
I'm in 3G only mode on NextG and everything works perfectly on my current phone. Who needs 900MHz 2G when you've got 850MHz UMTS anyway? :D
[Samsung Galaxy Nexus] oscillik:
kinda missing the point though - the phone should operate properly on all it's supported frequency bands. some of us happen to have regular drops down to a 2G network due to coverage issues. basically means that whenever I leave my house, my phone will become unreliable as a communication tool since I won't hear alerts.
[Samsung Galaxy Nexus] StuMcBill:
Android Police have reported it, that's a start!

Sent from my Amiga 500 using Workbench!
[Samsung Galaxy Nexus] FISKER_Q:
*facepalm*

You can't post in colors on twitter, it's twitters design choice
[Samsung Galaxy Nexus] romerjon:
New update from The Verge:

Does this mean it's sw related?
[Samsung Galaxy Nexus] jms.flynn:
Google have also just replied to the post I started on the support forum. http://www.google.com/support/forum...ad?fid=38a9e304e3a4d03f0004b23c09b35e60&hl=en
[Samsung Galaxy Nexus] paul_one:
No, it means that they are trying to pull the same old line on everyone, to buy the phone, live with the problem, and then bring out a newer phone later... At least that's my opinion on the matter.

The fact that neither one have made a proper public announcement, or recognition of the problem at hand plus Samsung's words of "these batches have gone through additional QA testing whilst being shipped to you" to the retailers, leads me into thinking that.
[Samsung Galaxy Nexus] jms.flynn:
Whilst I agree in part with what you saying because of Google and Samsung's history (Galaxy S - GPS, Nexus S - Touchscreen etc) I think we should all wait for the fix and see how we get on before jumping to any conclusions.
[Samsung Galaxy Nexus] le_pere_noel:
just to inform no problem with my phone coming from gummobile, BUT I am in France :)
[Samsung Galaxy Nexus] paul_one:
LOL, yeah, I'm a little annoyed the phone's hardware has such a fault and instead of fixing it they're hiding it... I may get little digs in about sub-standard hardware, and the phone being such an afterbirth of a phone... But in the end, depending on what the sacrifice is and what their fix is, then I might end up owning one of them.
[Samsung Galaxy Nexus] ericshmerick:
I really wish there was a definitive answer as to if an OTA can really fix this 100%.

I'm considering purchasing from Expansys-USA but am afraid to spend $749 if there is a rev.B hardware version in the works...

Especially since there is no warranty on grey market phones...
[Samsung Galaxy Nexus] IvanDobskey:
New member here with a dilema :)

I have long since decided that the Galaxy Nexus was the phone to replace my iPhone 4 with my 18 month contract coming to an end next month. Only problem is that I am on O2 who use the 900Mhz frequency that causes all these volume issues :(

I can have my upgrade a month early, tomorrow and probably get a decent deal through retentions as this will be my third big contract in a row with them. However, I am tempted to buy the phone outright and put a cheap sim only deal in it on a network that hasn't been affected by the volume bug. This would be a bit more expensive though.

I'm a bit worried that any 'fix' would be masking hardware issues rather than properly fixing them.

Should I pay a bit more and switch networks to be safe?
[Samsung Galaxy Nexus] jms.flynn:
Hey I agree with you, I was so angry I returned my original Galaxy Nexus, and within 24 hours re purchased one. This phone is brilliant, such a step up from gingerbread I am happy to live with a software fix even though deep down I know that the substandard hardware has really let it down on what could have been a great launch and even greater phone.
[Samsung Galaxy Nexus] Bilbo Fraggins:
Whatever the problem is, a fix is a fix in my book. If it were up to me I would sure pick a software fix over a hardware fix.

I would implement before shipping though :p
[Samsung Galaxy Nexus] mstyle88:
I thought if you buy a phone from Expansys, Handtec, etc that it would still come with a 1yr warranty?
[Samsung Galaxy Nexus] gambiting:
Actually, no matter who you buy it from, it is still covered by Samsung's 2yr warranty.
[Samsung Galaxy Nexus] ericshmerick:
Link?

I currently have a Samsung International SGSII in the states and I have zero warranty.

How is the GNEX different?
[Samsung Galaxy Nexus] onyxogen:
Ok, but this problem is only "fixed" if the problem stops occuring in bootloader mode, inducing the signals with a second phone.

Before that, it's just a stupid cover-up.

But I know that after getting the "fix" this will be the first thing people will check.
[Samsung Galaxy Nexus] player911:
Exactly. Google will figure it out. They just need to write some traps for the low level code. Or change the codes the Volume keys respond to.

If it is a hardware problem, it won't solve the "problem" but it cures the symptoms. As long as it doesn't interfere with other things we'll be fine.
[Samsung Galaxy Nexus] jms.flynn:
I agree, its not a fix until its fixed everywhere but unless you are in the bootloader with an external 900 gsm signal next to it (because your phone won't be transmitting in bootloader), you are never going to notice it. But I agree it will probably be just a cover than a hardware fix (if it is the hardware than needs fixing), lets just see what the fix fixes. I for one will be doing the bootloader test as soon as the update is applied.

.... as you can see i am being cautious with my answers because I don't know what the issue actually is.
[Samsung Galaxy Nexus] nyyankees3511:
This guy makes sense, and the debouncing also makes sense as I have played with it in my circuits lab.

https://plus.google.com/u/0/106493827472880328627/posts/MBAEWb9125i
[Samsung Galaxy Nexus] Evostance:
Imagine if the phone wasn't released yet and this issue was discovered at the manufacture end. They'd patch it and release it and you'd be none the wiser.

Its not going to have a massive impact on your phone, Google aren't stupid and they wouldn't release something that will drain your battery or give you crap signal etc.

Everyone acting like a small software update is going to make the phone rubbish.

https://plus.google.com/u/0/106493827472880328627/posts/MBAEWb9125i

I'm on O2 currently and they have a 14 day window in which you can return the phone and cancel so do what i've done.

Upgrade to the Nexus, and then if your having serious issues and Samsung haven't patched it or w/e. Send it back and cancel

Otherwise, if its all fixed and the phones fine. Send it back anyway and cancel, then just buy one sim free from O2 on Simplicity which will cost you £460ish. As long as you use the simplicity sim in the phone for a day, O2 will unlock the phone free.

Then you can go elsewhere. My O2 contract works out at like £700 TCO, if I bought it outright from then and switched to giffgaff (who run off o2), It'd cost me like £620 TCO over 18 months.

You also get Unlimited Data, Texts and 250 mins for that £10 a month
[Samsung Galaxy Nexus] matt2053:
Also Dan Morrill from Google basically said this guy hit the nail on the head:

https://plus.google.com/112413860260589530492/posts/1a4hY7VeqiG
[Samsung Galaxy Nexus] onyxogen:
The guy is right. But: Debouncing should occur on keypad driver level and not OS level. We'll see how it is working in bootloader mode.
[Samsung Galaxy Nexus] blunden:
There is certainly nothing stopping them from honoring the warranty via Samsung UK. Samsung US will most likely not honor it though since it's not purchased in their region.
[Samsung Galaxy Nexus] gambiting:
Samsung is required by EU law to give you 2yr warranty. However, if you are in the States then it does not apply to you.
[Samsung Galaxy Nexus] ali.almahdi:
The bootloader is a piece of software, could be flashed as well! and Google engineers are not stupid, I am sure they will find the most appropriate way to do it.
[Samsung Galaxy Nexus] mdh007:
I ordered two Gnex from unlocked-mobiles.com and am very glad to hear they come with a 2year UK warranty.

I live in Canada. Anyone have any experience with Samsung UK mailing the repaired phone back overseas if I mail it straight to the repair centre in the UK?

I know retailers like Clove offer to act as a proxy but I don't think unlocked-mobiles offers this..
[Samsung Galaxy Nexus] bleets:
and people still 100% insisting it's hardware fault without any real proof it is. yes yes you can replicate the fault near 100% times and yes yes it happens in bootloader. what does that prove? only there is a fault, it doesnt say if it's hardware or softwhere.

and people go on about shielding...with buttons like on the volume rocker it'd be very difficult to shield from internal RF never mind external RF right next to the buttons
[Samsung Galaxy Nexus] Evostance:
The point is there is an issue with the hardware. Thats clear, but Google can simply modify the bounce rate for the system not to react on anything up to say 100ms as thats around the rate of a human tap.

Its sorts the problem out, end of
[Samsung Galaxy Nexus] IvanDobskey:
Thanks for your thoughts :) They do indeed make sense.

I think I will see what retentions offer me tomorrow morning and if it isn't good enough I will jump ship to Three.
[Samsung Galaxy Nexus] burnduck:
Just received a reply from Google itself, but the whole thing started to sound a bit canned.

At least it's a *direct* response from Google and I'm going to wait for a few more days and see.
[Samsung Galaxy Nexus] paul_one:
They're sure taking their time for such a simple variable change + recompile of the kernel.

There's no need to recompile the whole thing - just the kernel part... If indeed it is the bounce thing.

.... just saying.

Not really, usually it's part of the casing.

True, it could be anything between the rocker to the CPU generating the keypresses. Hiding it in software doesn't negate the fact the fault is in the hardware.

If you want to know the difference between hardware and software faults I can tell you. But what you're talking about is a "patch", not where the fault is, and not 'fixing' the fault.
[Samsung Galaxy Nexus] gnufabio:
Damn, now people will start complaining because Samsung won't fix the hardware problem.

First of all consider that the problem happens only when you are using your smartphone in 2g on a 900mhz frequence or when you put another (old) phone using the 2g next to the GN. I'm sure that if nobody told you about this issue, you wouldn't even notice it.

Recalling all device would be useless and pointless. Samsung should have to change the hardware - should they create a new phone in few days?

The software fix is a good compromise, since it will stop this problem forever and anyone won't have it ever. We get the GN working well and Samsung/Google don't pay for things that can be easily fixed by software.

I really can't understand the problem with it.
[Samsung Galaxy Nexus] IvanDobskey:
I work with software / hardware every day and I can tell you that tweaking software to overcome hardware issues is a regular occurrance. I bet 99% of electronic devices on the market have software workarounds for hardware issues. Samsung/Google just didn't fix this one before the phone was launched!
[Samsung Galaxy Nexus] paul_one:
Sorry - but have you read the thread?

in the UK, the top 2 mobile companies (o2 and vodafone) use 900Mhz, and also in the UK, our coverage can be quite patchy. If you'd read the thread you'd know that as it has been repeated.

It would actually fix the problem and give us all a better phone... So IMO not "pointless".

I shall wait to see the test results after the patch has been applied and make that "compromise" decision for myself... I see you've already made your own.
[Samsung Galaxy Nexus] bleets:
I just had a thought...

if this is a hardware fault, feel free to go to every handset manufacturer and tell them every handset they sell has a hardware fault because you can pretty much guarantee every handset will have to deal with interference. :) you just never notice.
[Samsung Galaxy Nexus] gnufabio:
Like lot of engineerers said here, patching hardware issue with software is very common, and it's plenty of device with it. Should I mention them? Acer Iconia, iPhone 4s (for the battery bug, it's not a 100% software bug), all Acer smartphone, Transformer (for auto-rotation and other things). These are the hardware-bugged devices I dealt with.

It's pointless because if they really fixed the problem by software there is no need to recall all the devices. As I said, Samsung would have make up a new phone. Probably the future revisions will have this hardware bug too.
[Samsung Galaxy Nexus] ballonic:
Funny to see this thread in a "developers" forum... as it looks to me many people don't have a friggin' clue about development (be that software or hardware).

As IvanDobskey points out, fixing hardware issues with software is the most normal thing in the world. And as long as the user experience doesn't become a lesser one, it doesn't matter how a fix is applied.

The idea that a smartphone today would have a hardware fault when certain RF frequencies interfere with other parts of the hardware is plainly ridiculous.

Today's smartphones have a multitude of radios, and all of these potentially interfere with other parts of the phone. It is impossible to design a smartphone that's so thin and lightweight (which is what the consumer demands), with so many parts packed together, without any interference from the phone itself, or other sources. However, low-level drivers and other software routines are full of algorithms to detect spurious RF and deal with it in a way that the end-user isn't aware of it.

In the end, every single mobile phone probably has these 'hardware faults', it's just something that you can't avoid within the hardware design. It's just that this time, the software lacked the routine to catch the issue (if that's by design or a bug, we probably won't be told), and a thread of 122 pages in a few days is the result :D

Greetz.
[Samsung Galaxy Nexus] darkoroje:
Software can be used to mask a hardware problem but not fix it. In this case the concern is at what rate are the spurious interrupts generated, and what load does handling of them put on CPU and battery usage, even if they are filtered out in the driver. If there is significant CPU load that will have a detrimental effect on battery life and also on any other task the phone is performing at the time. So we have to wait and see how well this fix performs once it is available.
[Samsung Galaxy Nexus] IvanDobskey:
Spot on :cool:

As long as the end user doesn't have any unwanted side effects to deal with, who cares how they get around the problem.
[Samsung Galaxy Nexus] gnufabio:
Not to much cycles..this bug doesn't happen continuously, but only in certain conditions. Just think to all the sensors and chips always working in background (prox. sensor, light sensor, accelerometer, touchscreen, speakers, ecc). You will find out that these few interrupts sent by the volume rocker is pratically irrelevant.
[Samsung Galaxy Nexus] Lcrkz0023:
All this is starting to become redundant.......superfluity!

everybody keep saying the same ol thing recycled...just saying :(
[Samsung Galaxy Nexus] ballonic:
That's correct but only partially. For the hardware designer, software would indeed not fix the problem. For the end-user, software can fix the problem.

In regards to CPU: We're talking about an integer (if even that size) value that needs to be sampled every few miliseconds. I think you can safely say that with a dual core 1.2Ghz CPU there will be an effect on battery life, but you and I probably won't notice it. I think that's the most realistic perspective of what would probably be the software fix.

Greetz.
[Samsung Galaxy Nexus] BarryH_GEG:
Samsung's warranty policy is geared toward preventing products from being sold outside their intended country of sale and/or unauthorized resellers. Any phone sold in the U.S. whether through Negri, Amazon, NewEgg, etc., is considered grey market and has no warranty. The exception being Expansys-USA which will ship phones to their international affiliates for service on behalf of their U.S. customers for the life of the two-year warranty. Phones bought in the UK from an authorized reseller retain their warranty. Samsung requires an invoice and/or a credit card receipt in local currency which they'll ask for prior to repair. They also have a database of serial numbers so they know which phones were sent to which distributors and resellers. The phone has to be repaired in the country of its intended sale. If you purchased from Negri and have the volume +/- issues it's up to Negri to exchange your phone. Samsung UK will not repair it. We all went through this with the i9100 and there are lots of examples where Samsung's refused warranty service because the above conditions weren't met. This isn't speculation, it's fact. Something to consider when you're looking to save $10 bucks rather than buying from Expansys-USA, Clove, or Handtec.

http://www.agmaglobal.org/about/members.shtml