Leaderboard

Yes, this is a 2-in-1 problem. The first one is the different keymap of shifted (QWERTY) and normal (QWERTZ) variants of keyboards we have. It is a bit strange that F(x)tec itself has generated this issue as otherwise these layouts would work exactly the same way deep inside. So the problem is the shifting itself which made default layout of Pro1 to be unusual while QWERTZ variant is a perfectly usual layout. So @tdm's keyboard driver solved this issue by allowing to map appropriate keycodes to shifted keys respective to its written functions while also maps appropriate keycod

Android uses 'meta' for the built-in keyboard shortcuts, such as meta+B for the web browser, meta+E for the email app, meta+enter to switch back to the launcher (i.e. 'HOME'), and meta+backspace for 'BACK'. This list of shortcuts is extensible, but I don't think the interface is currently exposed in any system app. By default, the 'F logo' key generates KEY_META in LineageOS, enabling these shortcuts. You can display a list of the currently defined shortcuts with meta+/, although this is unfortunately a three-key chord on the Pro1 which makes it rather difficult to type. 😕 However, pressing b

Yes, there is still a problem to be solved, it just can't be solved by changing qwertz_fn_keys[] in the keyboard driver. @VaZso's summary is quite correct, that we will most likely need additional language-specific custom keymaps to make this work properly. We probably also need the ability to remap the six 'modifier' keys with dedicated GPIO lines (shift, ctrl, fn_l, F logo, alt, and fn_r), and this is not possible with the current custom keymap feature. However, we are making good progress towards adding support for that.

Hey guys, at least I found a kind of flip case fitting for my needs. I don't carry my Pro1 with me a lot, so the bulky design doesn't matter and it's well protected at home 😄 I've bought it at this Etsy Store, not sure about international shipping but she's located in Munich. I like the idea of wrapping this elastic plastic stripes round the edge of the keyboard, so the display can close properly. If you order you can tell an individual phones size, choose from the Pro1's data sheet h: 154mm; w: 73,6mm; d: 8mm (depth only keyboard). I also asked her to make the whole bag 5mm wider

Anyway, I had a problem with Button Mapper on stock Android of Pro1 as it caused lag on my hardware keyboard and a feeling it is not fluent which was solved by removing it...

Also, https://play.google.com/store/apps/details?id=flar2.homebutton says: That may trigger the keymap bug that Google introduced in Android 11

Yes, that is why I would put "\" to the lower-left position and I am also currently using it there. I never thought they would move ~ key to that position. 😞

Oops, I haven't looked this deeply but you are right. I am agree with that, "\" is at a very wrong position. It may be an option, but another right position for that key is the "`/~" button which should be on the left of '1'. So, I would put "\" key on the "`~" key. That key is absolutely a nonsense being there. I am absolutely and definitively against it - apart that key is handled a bit differently, it is very important for custom layouts, so should not be eliminated.

Right - anyway, for the keyboard itself, the most convenient way of working would be for me: Two slant arrows could be used freely for my custom layout (defined in .kcm file) Original AltGr function of the selected international layout could be reachable for example by "Alt" button Additional yellow characters would be accessible by another modifier like the "Sym" button. Maybe another modifier would be usable to quick-launch applications like the "F(x)" button For the functions above, an additional modifier like FN or Meta would be needed. Quick launch may be pos

Same with me. I just sent my phone to their new address on Friday. Will let you all know how that goes.

Exactly. Out of interest, I had applied the proposed patch to my LOS 16 on my QWERTZ Pro1: The respective key immediately stopped working correctly. With @tdm's default keymap, things have always worked - given the correct configuration you describe. That one has to configure things in two places is of course a little cumbersome, and many of us QWERTZies stumbled on that in the beginning. Streamlining the UI here would be nice, but also not strictly necessary, as for most users configuring this is a one-time action.

@EskeRahn Thanks for the tip Still no response to my email

From my experience with LOS (16.1 and 18.1, never used stock) I can say that the excessive call volume is related to VoLTE being enabled and active on both sides. While someone else (on another network) reported he had to completely disable 4G, for me, disabling VoLTE ("4G Calling" in the "Mobile network" settings) was enough to get rid of the issue.

I do not know if @EskeRahn made some push or @Erik read this thread, when @Rob. S. tagged him, but with some magic help after several weeks of silence Support team amazingly replied me that evening. Unfortunately just announcement, that they apology and I have to wait. So in conclusion: first contact: 22.2.2021 pictures of corners and whole phone wanted, sent 23.2.2021 then I needed the phone very much, so i somehow made it even with the ghost touchy display.. On 9.4.2021 the phone was sent on my own costs. several e-mails about when it will be, in total 6 outgoing mes