EskeRahn

Yup. The keys are just as real as on e.g. the Pro1. They are transparent, and right under them is an e-ink display, I bought one just to have it. I have considered to buy one of the defective ones you can get on ebay for $20 just to take it apart... But shipping and customs would add some $40, so have been too stingy.... Add: Just ordered one anyway.... (See e.g. this for images and a video)

(I took took the liberty to change the thread title to reflect that you solved it 😇 )

Personally I hope for e-ink keys like they had on the "Alias 2" a.k.a. "SCH-U750" Samsung made for Verizon. An ingenious solution, fitting 'any' language or gaming...

For links to various ROMs, see also this

My guess would be that the app checks for physical or virtual keyboard, but are unaware of the new 'mixed' state where half of the display is dedicated for a virtual keyboard, (and thus logically should be treated as a physical). As they assumes a virtual keyboard takes up a substantial portion of the screen layout, they change the input-mode...

Are you on stock android, or some other rom? Du you see the same if you (for test) use the standard keyboard driver, and not Swiftkey? Is it a particular program, or 'any' input field? I use Swiftkey on stock, and do not see this, so I'm almost certain it is a setting somewhere that need to be changed. (the suggestion to de-select swiftkey, to see if it is a setting inside or outside swiftkey we are hunting for...)

Update to December 22, with December 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

(lineage-18.1-20211220-nightly-pro1-signed.zip on December 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)

(I admit I adjusted my Danish text, to something that ended sensible, in Google Translate)

Forgot to post it in this thread, but have also seen it, though on AICP. See these two post from the same thread. this and this.

Det duer ikke hvis vi allesammen skriver på vores eget sprog.... I mangel af bedre brug google translate. Jeg har erstattet ovenstående med indhold fra Google translate, så må du tilrette hvis nødvendigt....

Update to December 15, with December 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

Ah sorry, I was unclear. I meant that the way they implemented the repairability might have given us a vulnerability, due to less glue than the Elephone-U. Of course it is not the repairability as such.

Does anyone know if the Elephone U is plagued by the same issues? If not, it could be interesting to get a display with an Elephone-frame, to see if we can spot what they have done differently in the mounting, If could well be, like @VaZso suggests, that it is the repairability that has this negative side effect.

(lineage-18.1-20211213-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)

It is really odd that this is seen by a number of people, but not everyone. Would be nice to understand the root cause. Is it a quality issue on displays or connectors? Is the connectors sensible to e.g. humidity? Is it an assembly issue, that goes wrong on some? Is it a grounding issue? Is it a special mechanical stress that triggers it, that we could all accidentally trigger? Air humidity? Or??? I see something somewhat similar to the described while using a non-grounded cheap charger (tried several). But no issues while charging it through a grounded pc. So this make me think of s

Indeed. Splitting sticks: On indiegogo (like any other crowdfunding) we do not "purchase" an item, we make an "investment" and hope to get the perk we selected in return. But like buying shares (where we hope to be able to sell it later with a profit), there are no guarantees. The risk we take is why the price of a perk is usually substantially lower than doing a (pre)order on the same item.

Update to December 8, with November 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

See how 'easy' things are, even for this minor fruit company, according to nikkei here. Surprised that some seems to expect that it is super easy for a huge player like FxTec to get parts as they need them, just they try a little harder....

Indeed some apps with mixed functionality could need the permission to offer functions the individual user might not need. And if so indeed removing the permission solves the keyboard interference. Also note that not all apps using the accessibility API will interfere. E.g. Greenify stops apps in another way than the fake keyboard entries Android Assistant generates.

(lineage-18.1-20211206-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)

There is a lengthy talk on the keyboard-accesibility issue in the Lineage thread. In short they made some fundamental changes to fix another issue for many users. And that fix is incompatible with the way apps with the accessibility privilege (using it to fake keyboard inputs) works. Android Assistant is a simple example of that.

If the usb-board is functioning, I would expect the LED or display to react when applying power. If the display is not working, but everything else is, the LED should turn on. If the display is working, I would expect something to happen in the display. So going for the simplest options first, I would certainly start looking at the USB side (charger/cable/board)

If it is the usb-board that is damaged, it might work as a temporary measure to hold the plug at a certain angle. Try and see if you can get the LED to light up. This way you might be able to charge it enough, so you can get any needed data out. (Oh. And if you have not already tried, try a different cable and/or charger, you could be lucky that it is merely a broken cable)

In short, no I'm not telling you that.... Reread