Pro1X, Physical keyboard layout issues [Fixed, other software interfering]

[Tell-Son 6]

17 minutes ago, EskeRahn said:

That they worked initially is a good sign, so most likely you can avoid the full reset.

I agree with @Hook's suggestion, but start with any app that is mentioned as active under Accessibility - or just switch its rights off under accessibility. And if that does not do it, focus on anything keyboard-related, or 'fancy', the more complex the larger the risk of it trying to be clever and mess of stuff.

You could try to just STOP rather than uninstall stuff first, with the risk of them being brought back to live, making tests harder. A reboot often restarts a lot of junk you may have stopped - thanks Android.... 🤢

You MIGHT need to do a reboot after uninstalling some stuff, to see the effect.

Note on the first thing, if you did a Google restore of apps this MIGHT take quite a while, so you could have seen the keys working before some settings messed things up.

Good hunting - and please report back when you narrow down the culprit.

Sometimes in life you are a lucky guy, and the problem-app begins with an "A". Anydesk was the influencer in my case. I did not even had to uninstall it.  Just removed all the rights in the special-rights chapter.  And my physical keyboard is giving me the proper values again.

Thanks to all !

[EskeRahn 4,894]

1 hour ago, Tell-Son said:

Sometimes in life you are a lucky guy, and the problem-app begins with an "A". Anydesk was the influencer in my case. I did not even had to uninstall it.  Just removed all the rights in the special-rights chapter.  And my physical keyboard is giving me the proper values again.

Thanks to all !

Great, lucky you that it was not zx browser.... 🤣

[xhajt03 20]

Slightly related - I had issues with FxService effectively disabling FinQwerty layouts on my Pro1x (only the default layouts worked correctly, FinQwerty layouts behaved as if I had the default stock QWERTY selected). I reported the issue to @Slion (the author of FxService), but he probably couldn't have analyzed it in detail due to only having Pro1 and not Pro1x.

[VaZso 1,920]

4 hours ago, xhajt03 said:

Slightly related - I had issues with FxService effectively disabling FinQwerty layouts on my Pro1x (only the default layouts worked correctly, FinQwerty layouts behaved as if I had the default stock QWERTY selected). I reported the issue to @Slion (the author of FxService), but he probably couldn't have analyzed it in detail due to only having Pro1 and not Pro1x.

I have recently ran into a similar issue on my Pro1.
I have installed AnyDesk which has installed a service and I had no FinQwerty-like layouts working until I have found that application was the cause of my issue and disabled its service.

(Pro1, LineageOS 18.1 here.)

[Rob. S. 1,407]

On 8/18/2022 at 2:39 PM, Rob. S. said:

QWERTZ with 'Physical Keyboard' set to 'German' indeed generally works. Although there are two bugs in the layout which make both the accent grave or backtick < ` > and the apostrophe < ' > unavailable [...]

The FinQuerty app which now also has layouts for the Pro1 X (thanks to @EskeRahn for mentioning this), fixes this issue with the "FinQuerty F(x)tec Pro1 X, German for physical DE QWERTZ" layout. Excellent.

Edited October 3, 2022 by Rob. S.

[Craig 1,433]

Semicolon to the right of L sounds like standard qwerty layout to me.  If using US layout, I would expect shift + slash to give me a question mark.  

[Craig 1,433]

I just tried Pro¹-x for the first time today.  I have tried lots of things and cannot get pipe or backslash to come out of this keyboard, with layout set to both US and unset to default.   

Google Assistant has no accessbility permission.  The only thing that has accessibility permission is kde connect.

In any case, even tho the keys aren't printed right, semi colon and question mark are exactly where they should be for US layout.   

I think I'm gunna keymapper to turn Del to KEYCODE_BACKSLASH (and thus shift+del = pipe), and shift backspace to del and just avoid figuring out what weird thing fxtec did this time.   I will only use pipe when doing shell stuff and backslash only if i use dosbox, but slash, semnicolon, and question mark are part of normal English and I'm glad they work where they are already anyway.

Edited October 12, 2022 by Craig

[EskeRahn 4,894]

3 hours ago, Craig said:

I just tried Pro¹-x for the first time today.  I have tried lots of things and cannot get pipe or backslash to come out of this keyboard, with layout set to both US and unset to default

Did you try FinQwerty? It now also has layouts for Pro1X.

[Craig 1,433]

2 minutes ago, EskeRahn said:

Did you try FinQwerty? It now also has layouts for Pro1X.

I did not.  I used Keymapper to assign keycode_backslash to delete key (which makes shift+"del" work automatically for pipe) and set shift+backspace to keycode_forward_delete.  So this particular issue is worked-around for me, even tho I could never make it work FxTec's way.

Edited October 12, 2022 by Craig

[EskeRahn 4,894]

6 minutes ago, Craig said:

I did not.  I used Keymapper to assign keycode_backslash to delete key (which makes shift+"del" work automatically for pipe) and set shift+backspace to keycode_forward_delete.  So this particular issue is worked-around for me, even tho I could never make it work FxTec's way.

Have a look here: https://android.onse.fi/finqwerty/#pro1x

"English US" (no finqwerty) also includes them