Well, as you can see from the video below, the guy set the highest volume, then place the smartphone near the Galaxy Nexus and the Galaxy Nexus respond to it. This is CLEARLY hardware issues. This could be the real reason Verzion still haven't release the Galaxy Nexus yet.
www.youtube.com/watch?v=BIFRYY25fDo
Thanks dnlsmy.
www.youtube.com/watch?v=y_mO_K7OYR0
Update 1
Google "We are aware of the volume issue and have developed a fix. We will update devices as soon as possible."(and you holding it wrong xDD) jk
Update 2: Lee Johnston explain of "volumegate" issue
Let's talk about the Google Nexus "volumegate" issue.
Today Google said that they have fixed the problem in software, and that a fix is coming.
I see many people saying this is a bunch of BS, but in reality they just have no idea how complex electronic circuits and software interact.
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
Finally, Where is the GSM HSPA+ 32GB version of Galaxy Nexus??????!!!
www.youtube.com/watch?v=BIFRYY25fDo
Thanks dnlsmy.
www.youtube.com/watch?v=y_mO_K7OYR0
Update 1
Google "We are aware of the volume issue and have developed a fix. We will update devices as soon as possible."(and you holding it wrong xDD) jk
Update 2: Lee Johnston explain of "volumegate" issue
Let's talk about the Google Nexus "volumegate" issue.
Today Google said that they have fixed the problem in software, and that a fix is coming.
I see many people saying this is a bunch of BS, but in reality they just have no idea how complex electronic circuits and software interact.
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
Finally, Where is the GSM HSPA+ 32GB version of Galaxy Nexus??????!!!
Last edited:
