Rimaner perplessi su bug riscontrati sui device è ormai routine, ma google ha promesso risoluzione per il suo google

fonino.

Il problema riguarda l’audio del device che non risponde all’utente, e più precisamente, si regola come vuole…

O in mute o sbalzi di volume inaspettati, soprattutto quando il device è connesso in fascia 2g a 900 Mhz, questo poteva preludere un problema hardware, ed invece arriva una smentita anche da XDA. e dagli ingenieri..

.

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 it 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!”

Il problema verrà quindi risolto nel minor tempo necessario ad individuare il bug che lo causa.

a seguito un video che mostra il problema.

Contazrazor.