***** The Official Galaxy Nexus Thread *****

How can a software fix be done? Unless the volume rocker is more complicated than just two buttons, I don't see how it can be done.

It most likely is a hardware issue but there may be a way of getting around it through software. Hopefully without compromising anything else!
 
Hmm.. computer runs on Linux so I need to connect the phone via the "camera" mode. Only shows around 1gb available - so I can't transfer all my music! Is that expected when connecting in camera mode? No windows PCs nearby to compare...
you dont want to use camera mode do you?

Nope, but it's the only option that appears under Ubuntu. The Media Device (MTP) option doesn't appear under Ubuntu... will search around
 
It most likely is a hardware issue but there may be a way of getting around it through software. Hopefully without compromising anything else!

How? You can't just be super clever and solve RF interference on something which has 2 states (volume + / -).
 
I'd also be interested to know how you could fix an RF shielding problem using a software patch. I just don't think it's possible.
 
If we knew we'd like come up with the fix ourselves. :p

That's another thing. The fact that with so many smart people already looking at this (some of the xda people) and not coming up with even a potential solution, doesn't bode well for Samsung/Google engineers.

Maybe they will lock the volume whilst the phone is in 2G mode :p

That's the only logical thing possible? But that's still faulty.
 
Last edited:
i would imagine a software fix would some how disable the volume being controlled buy frequency, so you can in theory lock the ability to change it in the software, fixing the hardware problem if that makes sense.
 
i would imagine a software fix would some how disable the volume being controlled buy frequency, so you can in theory lock the ability to change it in the software, fixing the hardware problem if that makes sense.

Volume isn't being controlled by RF though. The normal signal is being interfered with. How do you then recover the true signal (when there are only 3 options, volume + - nothing)? The software only gets the incorrect signal.

The only other thing I can think of is putting some kind of delay in? So if the interference is causing the states to change at a high rate then, tell the software to ignore it? But from what is reported fault seems to cause it to act in the same way as holding volume down anyway.

edit:

maybe you meant what I said in second paragraph
 
Last edited:
That's another thing. The fact that with so many smart people already looking at this (some of the xda people) and not coming up with even a potential solution, doesn't bode well for Samsung/Google engineers.

Really? I'd wager we know bugger all compared to the people at Google/Samsung in this department.

The best we can do is make educated guesses as to what causes the problem and possible solutions.
 
Back
Top Bottom