EskeRahn

Yes it could be mounted upside-down

Allow me to tag @Erik so he sees this.

Odd! Could it be caught as a spam-mail by the mail server for the account registered with the order?

There have been other threads mentioning this subject I will try and find those rather than repeat the story. ADD: I have been whining on the search in here before, but as you can not search for anything less than four characters, it is really hard to guess how to find a thread on the LED... Anyway "LED Colour Tester" works on Lineage, but has not worked on Stock since very early on. Long story on the whys, but the short story is the lack of a diffuser....

Much good can be said about LineageOS version, but those users that find a need for the few apps that require the device to pass the SafetyNet test, will have to stay on Stock, or fiddle with Magisk and MagiskHide on LineageOS to try to trick SafetyNet to believe it is safe. I guess this could be a place to start.

I'm pretty sure "system actualisation" = "system update", translation issue we have had earlier.

(lineage-16.0-20201005-nightly-pro1-signed.zip installed smoothly using sideload, with and without addonsu)

Well a rod with cogwheels in each end might be a way to synchronize the two sides.

I have a fear that if you are on qwerZ, and they want to send you a replacement device, then it might be related to them aparrently having had qwertZ templates in backorder for a long time. c.f. that some regular orders for qwertZ devices are about a year old now. Fxtec have for now even stopped taking new orders for the qwertZ variant (presumably for the same reason). I do hope that what ever is holding this up gets sorted soon, so you and other can get their devices.

Note that if they still got a stack of unanswered email, a new mail will put you in the bottom of the stack. But let us tag @Erik again, and hope they can clear things up.

I guess this is their main selling-point for the non-free version. But would be nice if this could be bought even without the device support. I'm not sure how they actually implemented the Alien Dalvik, but would guess hardware dependent, and here (unfortunately for us) the supported Xperia 10 and XA2 uses SDM630 so might require some modifications to work for other CPUs&GPUs, and thus also devices like the Pro1....

I'm certainly with you there. As many in here already know. And your guess on the reason is (at the least) as good as mine. But the device can be fully assembled and tested less the key-tops, so they could add it as (one of) the very last step before packing.

It is indeed quite similar to what we see in step 8 in your link. All that is needed to swap it is a little heat to loosen the adhesive, and the key mat can be removed. But why the qwertZ plates are harder to get than the qwertY I do not know. A GUESS could be that they are too small to get priority, if the company making them are very busy catching up for a larger client after the corona lockdown - but pure guesswork...

(The 20200825 image is now available in the original post) https://community.fxtec.com/topic/2466-guide-restore-to-stock-firmware-using-fastboot-method

The account numbers are not the original ones, they changed at the forum upgrade, as you can see mine is number 5183, and I have been active in here long before Erik was hired.... The first (or at the least among the first handful) would be Waxberry - and he got 5215...

I hope they go for std NanoSIM + sd + eSIM. An eSIM chip can hold multiple profiles so a standard SIM only for compatibility with carriers not (yet) supporting eSIM.

Well I imagine, that it MIGHT be possible to fix with some rod and cogwheels in the keyboard part synchronising the two sides. Obviously the technically super simple mechanism of the Pro1 has this coupling by design by the support being a plate and not two individual arms. (Actually the mechanism of the Pro1 though very simple in principle once you got the idea, is a bit harder to do with the correct ratios if you try to do the math, it was a bit of a puzzle when II tried to make a program to create the principal gif here)

Well we have seen the mechanism. As I described here the inventor himself struggles with it in their own presentation video (from 01:00 to 01:20 here). But obviously they might have improved that since, but we are to see that first....

There is a big IF in this. You are assuming that they are going to produce to stock. You could be right. But I wouldn't if it was me. I personally would not at all be surprised if once all pre-orders are handled, they will pile enough orders, before they produce a new batch for those - plus a few extras. I don't think they will want to produce more than they feel quite certain they can sell (plus what they need for guarantee repairs & swaps) If my guess here is right, I would expect that the more the order flow slows down, the less beyond the already ordered they will produce.

I have blown away some dirt (pocket lint?) and given the two sides of the top end of the support plate on my retail unit a tiny drop of silicone (the type you can use for the rubber sealing on car doors). Opened and closed it a dozen of times, and removed the excess with a paper tissue. And it moves smoothly again.

(lineage-16.0-20200928-nightly-pro1-signed.zip installed smoothly, with and without addonsu)

Interesting, Unfortunately It seems to only record in the left hand channel from the right hand microphone when selected... 😖

I have had similar experiences. I normally either use it with a headset or hands-free on a desk though, so rarely I use it as a classic phone next to the ear. I have installed an app to automatically detect to switch to hands-free, and actually thought it was the app that was buggy, but could be something with the sensor-driver...

Ah, yes, unfortunately this is stock only. I have tried to copy and sideload the apk to Lineage, it does not work. 😥 On Stock you can also see an action installing "KeyEvent display", as stock sends a key sequence (Ctrl+F4/F5 if I remember right) on close/open, but it is captured deeper in Lineage, so not as easy to check, Maybe @tdm got at test-tool? You do get a keyevent sequence activating the other hall-sensor on Lineage also though. (Detect case lid close/open, slightly different sequence than stock).

There is both the sensor, and what is supposed to read the sensor. Try the factorykit build in test (but look out for triggering the emergency call) Here my translated list. See top of thread on how to open.