[Gen9, Gen10 General] Deen0X:
Hi again.

I worked hard around this issue last night, testing all things i think.

my impressions.

- The problem is not about hardware testing. You said that is hard to get two controls to be connected at the same time, because there is a hardware issue that may be solved with a continuous usage of the device (talking in short words)

When i touch the Down button, i don´t need to press heavely to get a good command. in fact, the touch is soft and works well.

The same for Right command. The command respond quickly and there is no problems

if these two buttons are part of the same piece (a proper DPAD), i understand that may be a reasonable/potential issue that the triggers may be displaced from the original position, and get hard to press both commands at the same time.

but the D-PAD of the Gamepad is not a proper D-PAD. This is a 4 separated buttons, then when i press one of these buttons, this is no reason to thing that is hard to press another button, because there is nothing connected/related between these buttons to think there is a displacement of the triggers/connectors.

anyway, i pressed heavely these buttons (down + right) and i have the same issue/behavior than pressing softly. For the reason avobe, i discard that is a proper hardware problem.

- Commands sometime works

This is the most weird question, and the reason because i think the problem is software related. as i show on my first video, when i press some button (i.e. Right Trigger), the D-PAD works always the first time i pressed, but next time is not working unitl i release the previous button (Right Trigger)

when pressing Right + Down, sometimes i get a correct input and i can get them working for a little moment (half second, one second, etc), after this the down button doesn´t work again, until i release the Right button.

note: i tested all this with a proper usb joystick, and i confirm that all the programs i'm using to test this works well, reacting correctly to inputs of the joystick. (in this case, i use a generic PS2 joystic with a USB adaptor). with this, i discard that is a emulator/game problem.

with the info avobe, i conclude that if this is a hardware problem, the commands never worked. I tested many other android gaming devices (the major part of the important devices i have, and i working testing these gadgets every day) and the hardware issues works always in the same way. If you cannot press up+left (i.e.) on some device, this command will never get to work, because is a hardware problem and cannot be solved.

In the case of Archos Gamepad, sometimes the commands works. only for this reason i suppose this is a software related problem (may be the driver of the controller included on the device)

- Archos mapping tool have the same issue. Archos first answer was that the emulators/programs i'm using have bad coded the input control.

i installed a multitouch tester and mapped dpad on screen.

then i pressed the diagonals on dpad. down-right and up-right works sometimes(sometimes get both pressed, sometime get both and then down is released, etc. the same as i said before on other testings) or simply don´t works (only pressing right)

I'm using the archos mapping tool because i suppose this software is correctly coded (based on the answer of archos), but the software show the same issue.

With this test i conclude definely is not a problem with emulators/games, and comfirm (in my own point of view) that the problem is software based (probably the driver?)

are you talking with Archos guys? please tell these testing i'm doing. Surelly they realize on what is happening, and if i right (is software related), i suggest to Archos to post on his facebook about this, confirming is software related and may be solved with a patch or firmware update. (i really want to get this device working properly)

I don´t want to post more vids where show the issue, but if you need to see something on my testing, let me know and i make a video for you (or Archos)

feel free to contact to me if you need any info/help with testing.

greetings!