Author Topic: 7800B undesired inputs  (Read 4759 times)

mkvsbs (OP)

  • *
  • Posts: 36
7800B undesired inputs
« on: January 19, 2014, 12:24:44 am »
First of all hi everybody.
I've just received my new S7800B. Opened. Perfect. 1.1.4 onboard. Tried touchscreen ok. Joistick (left) ok.
After connecting to Wifi an update to keymapper was automatically downloaded and, maybe a coincidence, from that moment on when I am in the Android screens I get undesired 'left key' inputs.
It's making me crazy: you type something and the cursor is moved to the left (randomly). You swipe to access the right menu and the concosle brings back the left one.
Does anybody have an opinion on the possible cause ?
I tried to Clean/Close the Keymapper but did not help.
Strange enough when I am in PSP emu game this thing does not happen.
With developer options on I verified the touchscreen and there are no dead zone, touches are well identified (and pixels properly tagged).
I made also a Restore at factory settings and it did not change the scenario (undesired inputs still there).

Thank you for your suggestions.
Bye.

Kev7112001

  • *
  • !
  • Posts: 118
Re: 7800B undesired inputs
« Reply #1 on: January 19, 2014, 01:25:28 am »
could be the hardware itself i had to fix my d-pad

mkvsbs (OP)

  • *
  • Posts: 36
Re: 7800B undesired inputs
« Reply #2 on: January 19, 2014, 04:10:00 pm »
could be the hardware itself i had to fix my d-pad

Do you have a reccomendation for an application that can verify the hardware (dpad/touchpad/joystiks) ?
Strange thing is that when the console is in EMU mode everything seems perfect.
Thx.

Joe Sixpack

  • ***
  • Posts: 1413
Re: 7800B undesired inputs
« Reply #3 on: January 20, 2014, 05:25:24 am »
1st thing, turn on show touches.
Then hit the gamepaf button and click close/clear


Report back

mkvsbs (OP)

  • *
  • Posts: 36
Re: 7800B undesired inputs
« Reply #4 on: January 23, 2014, 08:46:27 pm »
1st thing, turn on show touches.
Then hit the gamepaf button and click close/clear


Report back

Hi Joe. Thank you for the tip.
I had some issues with the charger of the 7800. Now that everything is fine from that point of view I could concentrate on this other topic.
I did what you suggested: in developer options I acitvated 'show touches' and the hit clean/close on the keymapper.
Well on the display nothing (no white circle, I mean) appeared. Yet from time to time the screen was, again, flipped to the right (without any input by me) or, always from time to time, selection icon was moving on its own on the desktop (in many directions).
Trying to understand the reason I installed the keytest apk provided with the EN1018 preinstalled package and the keytest apk available on github.
This is the result of the test with the small utilities.
All the keys are working.
The left joysticks (once moved) gives the same keycodes as the DPAD but with different source ID and flag.
The right koystick is not detected by the second utility but is perfectly dected by the JXD one.

With the keytest apk running, leaving the console on its own for a while, then, I had the chance to note some keycodes appearing on the screen (but I was touching nothing).
One of the keycode description was this one:
keycode 21, DPAD_LEFT, scan_Code=0, flags=0x400, Source=0x1000010

Also installing System Tuner I saw that some Unhandled events are created (referring to the joistick move).

Honestly it seems that all the moves done by me with the joistick are somehow recorded and playedback as soon as I exit the emulators/games.
Is it possible ?

I tried also to flash the 1.1.4 FW and fully reload the preloaded package but the behaviour is always the same.
I tried 1.6GHZ flash too (just in case). Same thing.
I had the chance to  take also a log of the events. These are the events that are casuing my desktop to move on its own (as a zombie):

D/22:17:22.620 InputEventConsistencyVerifier( 2943)
  5: sent at 2886297403000, MotionEvent { action=ACTION_UP, id[0]=0, x[0]=648.37604, y[0]=701.1236, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=2886297, downTime=2886147, deviceId=2, source=0x1002 }
D/22:17:22.620 InputEventConsistencyVerifier( 2943)
  4: sent at 2886560090000, (unhandled) MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=0.0019569471, y[0]=0.0019569471, toolType[0]=TOOL_TYPE_UNKNOWN, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=3, eventTime=2886560, downTime=0, deviceId=1, source=0x1000010 }
D/22:17:22.620 InputEventConsistencyVerifier( 2943)
  3: sent at 2886590117000, (unhandled) MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=0.0019569471, y[0]=0.0019569471, toolType[0]=TOOL_TYPE_UNKNOWN, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=3, eventTime=2886590, downTime=0, deviceId=1, source=0x1000010 }
D/22:17:22.620 InputEventConsistencyVerifier( 2943)
  2: sent at 2886940074000, (unhandled) MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=1.0, y[0]=-0.46771038, toolType[0]=TOOL_TYPE_UNKNOWN, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=5, eventTime=2886940, downTime=0, deviceId=1, source=0x1000010 }
D/22:17:22.620 InputEventConsistencyVerifier( 2943)
  1: sent at 2886950074000, (unhandled) MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=0.0019569471, y[0]=0.0019569471, toolType[0]=TOOL_TYPE_UNKNOWN, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=1, eventTime=2886950, downTime=0, deviceId=1, source=0x1000010 }
D/22:17:22.620 InputEventConsistencyVerifier( 2943)
  -- recent events --
D/22:17:22.620 InputEventConsistencyVerifier( 2943)
  0: sent at 2886950000000, KeyEvent { action=ACTION_UP, keyCode=KEYCODE_DPAD_RIGHT, scanCode=0, metaState=0, flags=0x400, repeatCount=0, eventTime=2886950, downTime=2886950, deviceId=1, source=0x1000010 }



Really, a feedback and a hint would be really appreciated !
bye

[updated 26-jan 15.48 GMT+1]
« Last Edit: January 25, 2014, 02:27:17 pm by mkvsbs »

mkvsbs (OP)

  • *
  • Posts: 36
Re: 7800B undesired inputs
« Reply #5 on: January 25, 2014, 02:29:29 pm »
-
« Last Edit: January 25, 2014, 08:18:28 pm by mkvsbs »

batteraziiz

  • *
  • Posts: 10
Re: 7800B undesired inputs
« Reply #6 on: January 26, 2014, 06:07:11 am »
Undesired inputs sounds like a dirty movie...

mkvsbs (OP)

  • *
  • Posts: 36
Re: 7800B undesired inputs
« Reply #7 on: January 26, 2014, 09:13:04 am »
Undesired inputs sounds like a dirty movie...


Horror movie better describes the scenario as the console seems driven by ghosts  ;D

tincore

  • *
  • Posts: 284
Re: 7800B undesired inputs
« Reply #8 on: January 28, 2014, 12:04:42 am »
Looks to me like a bad contact.

mkvsbs (OP)

  • *
  • Posts: 36
Re: 7800B undesired inputs
« Reply #9 on: January 31, 2014, 03:00:38 pm »
Looks to me like a bad contact.

I opened the console, looked at the PCB of the joysticks, flat cables and so on but everything seemed ok. indeed solderings are all but nice but there is nothing
that clearly sounds bad.
After putting everything back together... power on.. and the same result as before (the left and right joystick that, thanks to 'Show touches' blink with two circles on the screens.
Maybe this evening I'll try to unplug the flat cable coming from the right joystick/power button in order to see (at least) if the ghost movements/blinks from two will become one (that would mean that indeed the root cause is the stick and not something else).


flyerz

  • Posts: 1
Re: 7800B undesired inputs
« Reply #10 on: January 31, 2014, 08:16:52 pm »
I'm having the SAME problem here, dude. =/

mkvsbs (OP)

  • *
  • Posts: 36
Re: 7800B undesired inputs
« Reply #11 on: February 04, 2014, 12:52:34 pm »
I'm having the SAME problem here, dude. =/

I opened and closed this console so many times that now it takes really 2 minutes to do it..
I think I understood the real issue.
Unfortunately it is not a nice result: try to google with this keywords: 'Android Ghost Input'. You'll get tons of entries describing exactly the same issue on many many devices (tablets, phones and, yes, also consoles).

Despite the fact it seems a joystick fault.. the real rootcause seems to be the touchscreen or the flatcable connecting the touchscreen to the motherboard.
In 99% of the cases there is no solution other than having the unit replaced.

This is also explaining why the kernel was higlighting an Inconsistency in the InputDriver highlighting that an event was generated but no real key press had been detected (so smart the Android core.. so bad the physical unit by JXD.. in our cases).

P.S. Indeed for the Asus tablet, when it was NOT the flat cable fault, a solution was found in the definition of the sensitivity of the screen -calibration- at kernel level.


« Last Edit: February 04, 2014, 01:17:27 pm by mkvsbs »

 

Post a new topic
Post a new topic