fMSX for Android released

Página 34/51
27 | 28 | 29 | 30 | 31 | 32 | 33 | | 35 | 36 | 37 | 38 | 39

Por fms

Champion (366)

imagem de fms

13-07-2014, 02:33

roo1234 wrote:

I've tested again with 2 keyboards. Only the cursor, space, enter, shift and tab are recognized it seems. All letters are ignored, only the overlay kb works.

I went out and bought a Logitech Tablet Keyboard to test this problem. The keyboard works perfectly well. I have no idea why yours do not, but as I cannot keep buying these keyboards, you will have to do some diagnostics on your end. Start with this little app:

https://play.google.com/store/apps/details?id=aws.apps.keyev...

Run it and see what key events your keyboards generate and if there is something abnormal. As I have said before, both Apple BT keyboard and Logitech Tablet Keyboard work like a charm.

Por roo1234

Supporter (11)

imagem de roo1234

13-07-2014, 08:09

Hi, sorry for the trouble of getting a new kb.
Strange though.. I've tested with a mobile Galaxy S Duos and it's the same. Follows the program result pressing the first letter keys, and the rest are just like that, seems normal.

OS Release: 4.2.2
OS API Level: 17
Board: PXA986
Brand: samsung
CPU_ABI: armeabi-v7a
Device: goyawifi
Display: JDQ39.T110XXUANC1
Fingerprint: samsung/goyawifixx/goyawifi:4.2.2/JDQ39/T110XXUANC1:user/release-keys
Host: R0210-02
ID: JDQ39
Manufacturer: samsung
Model: SM-T110
Product: goyawifixx
Tags: release-keys
Type: user
User: se.infra
Bootloader: T110XXUANC1
CPU_ABI2: armeabi
Hardware: pxa988
Radio: unknown

Press buttons to see the keycodes:
^ KeyUp: action=1 code=61 repeat=0 meta=0 scancode=15 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=16 mFlags=8 label='Q' chars='null' number=''
^ KeyDown: action=0 code=51 repeat=0 meta=0 scancode=0 mFlags=0 label='W' chars='null' number=''
^ KeyUp: action=1 code=51 repeat=0 meta=0 scancode=0 mFlags=0 label='W' chars='null' number=''
^ KeyUp: action=1 code=51 repeat=0 meta=0 scancode=17 mFlags=8 label='W' chars='null' number=''
^ KeyDown: action=0 code=33 repeat=0 meta=0 scancode=0 mFlags=0 label='E' chars='null' number=''
^ KeyUp: action=1 code=33 repeat=0 meta=0 scancode=0 mFlags=0 label='E' chars='null' number=''
^ KeyUp: action=1 code=33 repeat=0 meta=0 scancode=18 mFlags=8 label='E' chars='null' number=''
^ KeyDown: action=0 code=46 repeat=0 meta=0 scancode=0 mFlags=0 label='R' chars='null' number=''
^ KeyUp: action=1 code=46 repeat=0 meta=0 scancode=0 mFlags=0 label='R' chars='null' number=''
^ KeyUp: action=1 code=46 repeat=0 meta=0 scancode=19 mFlags=8 label='R' chars='null' number=''
^ KeyDown: action=0 code=48 repeat=0 meta=0 scancode=0 mFlags=0 label='T' chars='null' number=''
^ KeyUp: action=1 code=48 repeat=0 meta=0 scancode=0 mFlags=0 label='T' chars='null' number=''
^ KeyUp: action=1 code=48 repeat=0 meta=0 scancode=20 mFlags=8 label='T' chars='null' number=''
^ KeyDown: action=0 code=53 repeat=0 meta=0 scancode=0 mFlags=0 label='Y' chars='null' number=''
^ KeyUp: action=1 code=53 repeat=0 meta=0 scancode=0 mFlags=0 label='Y' chars='null' number=''
^ KeyUp: action=1 code=53 repeat=0 meta=0 scancode=21 mFlags=8 label='Y' chars='null' number=''
^ KeyDown: action=0 code=49 repeat=0 meta=0 scancode=0 mFlags=0 label='U' chars='null' number=''
^ KeyUp: action=1 code=49 repeat=0 meta=0 scancode=0 mFlags=0 label='U' chars='null' number=''
^ KeyUp: action=1 code=49 repeat=0 meta=0 scancode=22 mFlags=8 label='U' chars='null' number=''

Por roo1234

Supporter (11)

imagem de roo1234

16-07-2014, 14:37

pls delete

Por roo1234

Supporter (11)

imagem de roo1234

16-07-2014, 14:36

I think I know what the problem is. Each pressed key returns more than one line as you can see above (3 lines), however the scancode for the first 2 are '0', and the label is correct. This doesn't happen with the keys that work (space, cursor), the scancode is returned in all lines. When autorepeating (long press), scancode is also 0.
This behavior is the same with my 2 keyboards.

Seems you are using 'scancode', but 'code' or even 'label' could fix it.

Rgds

Por fms

Champion (366)

imagem de fms

18-07-2014, 20:14

roo1234 wrote:

I think I know what the problem is. Each pressed key returns more than one line as you can see above (3 lines), however the scancode for the first 2 are '0', and the label is correct. This doesn't happen with the keys that work (space, cursor), the scancode is returned in all lines. When autorepeating (long press), scancode is also 0.
This behavior is the same with my 2 keyboards.

How interesting... Well, I am going to compare this with the working keyboard I have, let us see what it generates...

Quote:

Seems you are using 'scancode', but 'code' or even 'label' could fix it.

No, I am ignoring the scancode. Using the code field.

Por fms

Champion (366)

imagem de fms

19-07-2014, 03:04

roo1234 wrote:

I think I know what the problem is. Each pressed key returns more than one line as you can see above (3 lines), however the scancode for the first 2 are '0', and the label is correct.

I have one more request:

Please, press and hold one of the non-working keys. While holding the key, see what event(s) it has generated. Paste them here. Then release the key, and paste event(s) generated by the release separately. I am having a huge suspicion about something =)

Por roo1234

Supporter (11)

imagem de roo1234

20-07-2014, 18:31

hi,
see here the long press and release of 'B'. Just after, the long press and release of 'space', that works in the emulator.
The events are different, when long pressing 'B', the 'keyup' event is triggered, but the real 'keyup' is when the scancode is returned '48'.

Press buttons to see the keycodes:
longpress 'B'
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyDown: action=0 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=0 mFlags=0 label='B' chars='null' number=''
release 'B'
^ KeyUp: action=1 code=30 repeat=0 meta=0 scancode=48 mFlags=8 label='B' chars='null' number=''
longpress 'space'
^ KeyDown: action=0 code=62 repeat=0 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=1 meta=0 scancode=57 mFlags=136 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=2 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=3 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=4 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=5 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=6 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=7 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=8 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=9 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=10 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=11 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
release 'space'
^ KeyUp: action=1 code=62 repeat=0 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''

Por fms

Champion (366)

imagem de fms

20-07-2014, 21:29

roo1234 wrote:

hi,
see here the long press and release of 'B'. Just after, the long press and release of 'space', that works in the emulator.
The events are different, when long pressing 'B', the 'keyup' event is triggered, but the real 'keyup' is when the scancode is returned '48'.

Well, I guess you can now see the problem by yourself. Your keyboard is not sending KeyUp events properly. The unfortunate part here is that I have no idea how to distinguish "bad" KeyUp from the "good" KeyUp. Ignoring any KeyUp lacking a scancode is not an answer, as it is likely to break support for other keyboards.

Do you by any chance have any other keyboard-related software installed on your device? Any unusual input methods, other than the standard Android one? I can see by mFlags=0 that these events are not coming from the system, so they must get generated by some software.

Also, can you try connecting this keyboard to some other fresh Android device, that has no third-party software installed? This is to verify that the behaviour you are observing is being caused by the keyboard or by the system, and not by some third-party software piece.

Por roo1234

Supporter (11)

imagem de roo1234

21-07-2014, 00:07

This is not a keyboard problem, seems to be a system/SO 'feature'. I've generated the log again below with totally different hardware (Chinese mini keyboard + Galaxy S Duos 4.0.4) and the pattern is the same. All devices are with stock android.
Tried to test in a 2.3 phone but the keyboards don't connect.

Both keyboards work with all system apps (message, S Planner, Gmail). Tested with your other emu Speccy Deluxe (same, only space and cursors) and with Zed Ex (ZX81) emulator, this one works fine with all keys!

OS Release: 4.0.4
OS API Level: 15
Board: 7x27
Brand: samsung
CPU_ABI: armeabi-v7a
Device: kyleopen
Display: IMM76I.S7562LVJAMB2
Fingerprint: samsung/kylevj/kyleopen:4.0.4/IMM76I/S7562LVJAMB2:user/release-keys
Host: SEP-122
ID: IMM76I
Manufacturer: samsung
Model: GT-S7562L
Product: kylevj
Tags: release-keys
Type: user
User: se.infra
Bootloader: unknown
CPU_ABI2: armeabi
Hardware: unknown
Radio: unknown

-----------------

Press buttons to see the keycodes:
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyDown: action=0 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=0 mFlags=0 label='Q' chars='null' number=''
^ KeyUp: action=1 code=45 repeat=0 meta=0 scancode=16 mFlags=8 label='Q' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=0 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=1 meta=0 scancode=57 mFlags=136 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=2 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=3 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=4 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=5 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=6 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=7 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=8 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=9 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyDown: action=0 code=62 repeat=10 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''
^ KeyUp: action=1 code=62 repeat=0 meta=0 scancode=57 mFlags=8 label=' ' chars='null' number=''

Por fms

Champion (366)

imagem de fms

21-07-2014, 18:46

roo1234 wrote:

This is not a keyboard problem, seems to be a system/SO 'feature'. I've generated the log again below with totally different hardware (Chinese mini keyboard + Galaxy S Duos 4.0.4) and the pattern is the same. All devices are with stock android.

Weird that I do not see this problem with Logitech and Apple keboards.

Página 34/51
27 | 28 | 29 | 30 | 31 | 32 | 33 | | 35 | 36 | 37 | 38 | 39