Android Central

There's been quite the hoopla over the past few days around the Galaxy Nexus volume bug -- that's the nasty little issue which results in the phone's volume levels going crazy when it's on a 900MHz 2G/EDGE network, or when it's exposed to RF interference from another phone that is.

We reached out to Samsung for comment on the glitch, and they've responded today with the confirmation that a fix is indeed in the works.

We are aware of the volume issue and have developed a fix. We will update devices as soon as possible.

So hopefully that'll be the end of that. It's worth remembering that this shouldn't be an issue in the U.S., because neither of the GSM carriers in the States operate on 900 MHz. That and the fact that the U.S. has neither the phone nor a firm release date yet. D'oh.

And don't fret if it looks like the update's coming from Samsung even though this is a Nexus phone. Google has issued the exact same statement this morning, and we'd expect updates to roll out the same way as with other Nexus phones -- from Google directly.

For more Galaxy Nexus goodness, be sure to check out our full review of the GSM version.

 
There are 22 comments

tronthedon says:

Hmm I thought it was a hardware issue?

Rukia#AC says:

You should take yourself over to The Verge and see the amount of arguing they've been doing in the comments over there.

shhon75 says:

I wished I had that issue... that would mean I have the phone :P

philly says:

software issue? I thought this was pure-google.. why is the update coming from samsung?

looks like another fascinate.. Samsung was the biggest problem with its 8 month delayed froyo update.. Verizon was the 2nd biggest problem.

Both Google and Samsung are sending out the same press release. Added a graf to clarify.

Rukia#AC says:

If it's a hardware driver update e.g. a radio antenna. Samsung will update it. If it's a software problem. Google will update it.

icebike says:

If it's hardware samsung will ignore it. If it's software google will fix it.

There. Fixed it for you.

hhtran says:

Wouldn't RF interference still be a problem with a CDMA phone?

Not when this happens on 900MHZ only and there is no 900MHZ GSM int he USA.

Conan Kudo says:

Actually, it will be a problem. In the United States, the GSM 850 and the CDMA 850 (sometimes called CDMA 800) bands both overlap the European GSM 900 band. Verizon also uses CDMA 850 as its dominant frequency band, with some CDMA 1900 sprinkled throughout its areas thanks to various acquisitions over the years. So it could actually be a problem for the Verizon version.

Only on T-Mobile USA will this issue never crop up.

Hand_O_Death says:

"That and the fact that the U.S. has neither the phone nor a firm release date yet. D'oh."

Low blow Alex, low blow.

And that's why people want a Nexus. A fix is out in a week. I'm just hoping that after this phone starts to sell on Verizon it will stay out of the way. Theurvtesters are no robs that let the Charge and TBolt out.

icebike says:

There is no fix!

And if it is hardware there won't be a fix.

This announcement simply acknowledges the problem. HTC did the same with the nexus one screen bug but it was never fixed.

squiggie says:

Why doesn't Samsung concentrate on fixing LOS on the Epic 4G Touch??? WTF?!?!

ReiMei says:

Google is fixing it not Samsung.

hmmm says:

I don't mind letting the foreigners test the phone for us :) Just as long as we get it here eventually. Actually, as long as we get it here in the next two months or so. Any longer than that and it will be old news and old technology.

sproketz says:

Wish they had a fix for the lack of a US release date.

I'm a Systems Engineer and also a Developer. I deal with things like this every day.

What we have here is indeed a hardware issue, in that the radio interference is coming in through the radio hardware.
However things like this can be fix fairly easily in software. It's called debounce.
When you monitor an electronic input like the buttons on a phone there is always noise and flutter even when you just press the button. If testing by Google has shown that they just need to turn up the debounce time (the time which an input must exceed for it to be determined to be a genuine press) then it will more than likely just work and no one will ever see ti again.

Like I said I deal with this kind of thing every day, it's not a big deal as long as your debounce time is not excessive. But noise happens down on the order of 1 to 40 ms, real inputs when you press a button last from 100 or 200ms if you tap the button, up to seconds if you hold it down.

This is nothing like Apple and the iPhone 4 antennae problems that could not be fixed in software. I'm sure everyone will see in due time, the problem will be fixed, and the dust will blow over.

And people will be saying "wow, I was wrong, Google rocks!"

Cheers,

Lee.

tronthedon says:

Thanks for the explanation

kinster02 says:

Good job UK, I new there was a reason that they chose you guys to be the guinea pigs and work out the bugs before they release it here...keep flushing out the bugs.

Meanwhile in America, we still don't have a release date from Verizon for this phone