xhajt03

Yep, that's what I meant.

Note that it doesn't have to be "fishy" in the sense you might have meant, there are scenarios like that FxTec didn't manage to pay on time for batch 1 and Expansys decided to requisition devices from batch 2 and sell them to cover their costs (that would be obviously very sad for various reasons, but certainly not a proof of "unethical way of doing business" on the FxTec side).

The interesting point is - Expansys is the company which was the sender of my Pro1x in "batch 1" (and probably supposed to do the same for "batch 2"). I'm afraid that this suggests scenarios in which Fxtec isn't the one "doing this business"...

Well, let's put it this way - I'm one of those lucky enough having received Pro1x in batch 1. I'm _very_ happy that it finally happened (after long waiting). I understand the frustration of those still waiting, but people who managed to create this device don't deserve statements like those appearing above.

Having been a long time E7 user myself (in particular since 2011 until the arrival of Pro1x one month ago 😉 ), I was searching for such a solution as well. I asked the FinQwerty author about possibility of sticky keys support in FinQwerty and he mentioned that this support would need to be provided by FxTec - quoting his response: --------------------- Regarding sticky modifier keys: On Android, the modifiers become sticky if the keyboard is declared as type ALPHA in the base .kcm file. However, on Pro1 the keyboard is declared as type FULL so sticky modifiers are not enabled. Sounds

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.

Alright, my findings: First of all, I decided to use the model from https://community.fxtec.com/profile/8210-ubuntuscofield/ (and only the bottom part, because I intend to use it in a leather book case) instead of the one referenced in this thread. The person printing it for me used the FLEX filament, that was OK (in fact, he printed another using PLA and yet another using PETg as well, but only the FLEX filament ended up in something usable). However, I had to adapt (enlarge) several of the holes a bit - in particular the two speaker holes (both had to be extended a bit towards the middle), t

While there probably is no possibility to change the application invoked by the special camera button, it _is_ possible to have another camera application invoked after double-clicking of the power button. So as of now, I have the option of either starting the default camera or the alternative (in particular, I chose Open Camera). If I remember correctly, I had to deactivate the default camera application (Snapdragon Camera) temporarily (that caused the dedicated camera button not to do anything), then I could map the power button double-click to Open Camera and after reactivating Snapdragon C

OK, thanks - the hole for camera seems to be big enough to cover for a slight difference in the position. 🙂

Hello Logan, do you have any update on this? I see that the linked case design was for Pro1 rather than Pro1x. I wonder if all the controls, sensors, etc. are exactly the same size and location on both models (otherwise some updates would be necessary).