I thought it was my fault that the problem was happening -- maybe I was pressing "Up/Left" on the keypad by accident, thereby registering two buttons.

But I'm sitting here right now pressing "Up/Left" in the original firmware file-tree and only the "Up" is registered, moving the cursor up the list and never taking me back to the previous folder. It doesn't matter what position I hit the "Up" button in ROCKbox, even if I press "Up/Right" it still registers "Left" sometimes.

The problem is always intermittent, but happens frequently. Maybe the iRiver firmware has some kind of double-press detection.

I have the exact same problem, always have had it under Rockbox.I've just tried enabling the upside down option, and indeed a rightpress 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 tofigure 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 ofsomeone 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 navigationalbutton either, so that would mean there's not much else that can be done in softwareto fix this problem...

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).

But indeed, this would mean that the readingwould 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 bycontrolling pressure (we should do something with that )

But it quite figures; the Left button is 44, and most of thetime when you press the Up buttton the click will 'throw'you passed that value. When you scroll however, you might takesome 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 twosuccesive 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...

Well, even with trying very hard I couldn't get any reading more than 1 or 2steps from their 'natural' (click) value.I think the 'Left' range could be changed to 0x42-0x46 without getting any artifacts.I'll try to test extensively under these conditions...

I have had problems with the double-button-press and the up key, and it is only in the rockbox FW. I am getting similar readings to those of Mr. Brownstone, so it doesnt make sense that I would have a problem, especially considering that the up buttonpress is often accompanied by a RIGHT buttonpress, the opposite of what you guys are getting. I may be having a problem all my own, but i thought I'd throw it out there.

this problem first arose for me with early rockbox FW, and then it dissapeared, and now it has come back again, if that makes any difference