Support and General Use > Hardware

Problems pressing "Up" button

<< < (2/3) > >>

benosoft:
I have the exact same problem, always have had it under Rockbox.
I've just tried enabling the upside down option, and indeed a right
press gets registered instead of a down press (so, pointing in the direction of hardware).

I'll try to recreate this problem under the iRiver firmware, and I'll try to
figure out if it accepts double key presses...I'll keep you posted!

___
Edit:

Actually, it happens under the iRiver firmware as well... :(
I thought it was an H3xx issue, but this is the first time I hear of
someone having the same problem...
Would it be just a batch of players that have this problem?

Btw Rockbox doesn't seem to accept double key presses on the navigational
button either, so that would mean there's not much else that can be done in software
to fix this problem... :(

Mr. Brownstone:
I've just tried the original firmware again. I've tried hammering the "Up" button in the file-tree and WPS and "Left" never gets registered incorrectly.

PaulJam:
Hi,

i have the same problem, but i believe it is a hardware problem.
If you enter the "View I/O ports" screen in the debug menu you gan see the button readings. For the UP button the value ADC_BUTTONS should change from FF to ~20.
If i press the UP button very carefully it passes the "click" (i'm not sure how to express this) of the button but the reading for ADC_BUTONS still stays at FF until i press a little bit harder, and then it changes to 20. The same (in reversed order) happens on release of the button: the reading first changes to FF and after that the (physical) button passes the "click".

For the other buttons (NAVI, LEFT, RIGHT and DOWN) the "click" and the change of the ADC_BUTTONS value happens simultaneously.

The problem is, that the 5 buttons on the center of the pad are not recognized independently, they are connected together, and the decision which button is pressed happens by measuring the resistance.
Because the "click" and the electrical contact of the UP button doesn't happen simultaneously it can happen that there is only a half electrical contact for a very short time and during this half contact the resistance is just that of the LEFT button and it gets recognized wrong.

Maybe this can be worked around in software by only accepting a buttonpress if there are several ADC_BUTTON readings in succesion with the same value (or in the same range).

I hope this was somehow understandable.

benosoft:
Yes, that actually makes perfect sense!

I'll check if I too have that 'click' behavior, but
I'd guess so.

But indeed, this would mean that the reading
would only very briefly be that of the Left button,
so maybe software could quite easily fix it after all...

I'll look into that, if I have something I'll certainly let you know!

___
Edit:

Yes, I do have the clicking problem, after the click,
I can get readings in the range of 21 to about 50 by
controlling pressure ;D (we should do something with that ;))

But it quite figures; the Left button is 44, and most of the
time when you press the Up buttton the click will 'throw'
you passed that value. When you scroll however, you might take
some pressure back, eventually causing you to hit 44...

I'll certainly have a look at the button driver code!

___
Edit 2:

The button driver actually tries to prevent false readings by requiring two
succesive readings.
But, the whole range between 0x30 and 0x54 is read as 'Left'.
So, that increases the chance of getting two 'Left' readings...
I'll try to find a more helpful range for the units with this particular issue...

Llorean:
I'm sure ranges could be narrowed if experimentation showed that valid readings happened only in say, the 40-49 range.

Navigation

[0] Message Index

[#] Next page

[*] Previous page