EskeRahn

If you want to keep it visible and on, you better cover it with some protection, as others have reported the print the wear off rather easily.

We do NOT want a "Huawei P20" but a "Huawei P20 PRO". And both sides have that on the list.... (the P20 is way too small) And the two cases ARE different, see the guides from the lnks:

I just noticed that not all the soft front and back cases have the edges front over back, some have back over front... So this might work for the display part. Though the edge part could be an issue.

see above

Personally I would never use free returns and refunds to return things I do not like, only to return things where the description did not match what I got.

...But the idea is not bad at all, we just need to buy TWO cases of this sort One for the lower part (e.g. for a P20 Pro) throwing away the top. PLUS one for top part throwing away the bottom. And here we need to go for a slightly SMALLER model, so the the Pro1 display size matches the intended bottoms outer dimensions. I have not found a super good candidate, but ordered some for a Note 10, that I hope fits, though they might be to short. (Note 10 is 151 x 71.8 so if we guess the bottom is 1mm thick we have 153x73.8, and thus perhaps too short....

I noticed it long ago, but never reported it, as I saw it as just an oddity as I could not imagine a scenario where this setting would ever be selected Off by anyone, As I combined it with using the keyboard open in portrait, and thought that meaningless, but off course it is not. One could argue that used in portrait the arrow-functions should be rotated counter clockwise - but that might not be easy to make orientation dependent.

It is clearly based on the AOSP launcher.

Confirmed. 😥

Sorry, read too hasty, had a foot out the door... (saw it as yet another wanting to get the symbols above the numbers with shift rather than fn) What you suggests is build into android and can be activated if they allow a way to change the type from "Full" to "Alpha" , see this

I think a LOT depends on the reception when it is out. I do not know the 'magic number' of needed additional orders they would need to cover the expenses of different hardware. If it gets a smashing success and sells in millions (unfortunately I highly doubt that) then almost any layout would be possible. But if keyboards stay a niche thing it will be hard to finance. I would have expected them to consider Spanish and French before the Scandinavian layouts. But much higher populations is not the same as a much larger market. F(x)tec could have some numbers from somewhere indicating

If there will not be a dedicated print, then US International might be an alternative. You can get the functionality already with the existing two prints, installing FinQWERTY, see the different layouts here

I believe so

The update is newer than September but the security level is not (yet). If you look at the long name you can see a date "...._20200106..."

There is a bug in the driver also, as Sym is (currently) handled as a letter-key, not a modifier-key. That is holding it sends repeated 'make' codes.

...And unfortunately the standard Danish ÆØ is swapped from the Norwegian, so for either however it is printed will be wrong for the other... 😥

Nope. It would need one with a higher hat, and possibly access to an underlying database

How odd! But nice to know, and easy to remember too. J for when the keyboard is Jinxed. 😇 If anyone gets it on a qwertZ it will be interesting if it is the letter J or the same physical key (that is letter K on qwertZ)

Too bad. My GUESS would be some pocket lint sneaked in somehow. But if I were you I would contact support. https://www.fxtec.com/support/

There are more than one possibility in this, but that is the primary functionality, yes. In the for the user simplest version the stock launcher when active (that is after e.g. pressing the Logo-key) listens for KEYCODE_ALL_APPS key event, and if fired launches the app drawer. The second is that it also listens if not in the foreground, that is pressing what ever sends the keycode launches the AppDrawer even with another app active. (This most likely would mean that it would work with another launcher too, as long as we do not directly disable the stock launcher app, but jus

We do not know where the people making the software are located, but I would not at all be surprised if they resides in China too.

I wonder if it would not be super easy to add the existing AppDrawer activity to the already exposed activity list of the launcher (see image)? Or to have it react to "KEYCODE_ALL_APPS" What does @Waxberry think? If as an activity it could be mapped with a third party tool as you suggests. I tried to emulate what happens today if a keyboard sends "KEYCODE_ALL_APPS" =284, using ADB from a PC, but it does not seem to do anything currently ... adb shell input keyevent 284 (sending other keys this way works fine, inluding 135&136 to emulate slider close and open) I tried

I really doubt it, as they will be fighting for the corners from both sides, not allowing the two parts to meet properly when closed. But some clever cutting of the grip parts might make them share the space. Why not give it a try and let us know. two plus shipping is about $6, so not a great loss if it fails...😜

They really got an odd excluding list BTW... 🥴

Can find many J7 variants, not this one. But all on this J7 list seems too wide to get a good grip (and some too short). My list of candidates is this one.