Leaderboard

@DieBruineI have sent the E=mail to fxtec asking to transfer the perk.

@hengyedev You transfer the Pro1x 8GB/256GB Indiego perk to me and pay for shipping costs and I will send you the Pro1. I require an email confirmation from FxTec and or Indiego, you have my email address. After that I will send you the Pro1 like brand new complete in the box insured up to €500,- with tracking, next business day at the latest CET+2 🤗 I have already sold two in this topic. One was delivered in Australia, the other in the US. And I sent five of my own Photon Q's to Cornholio, on good faith, for SIM-modifications. You already have all my personal details. That's

No, not now. I will report it in a few minutes. I just deactivate all apps that manipulate my android, mainly Tasker ☺️. At the end of last night, the issues comes from KeyMapper and Auto Input. Edit 1: Yes, the keyboard layout is changed, when I activate the Accessibility Services of Assistant for Android

Is this the app that triggers the problem? https://play.google.com/store/apps/details?id=com.google.android.apps.googleassistant There is also another app with a similar name from AA Mobile. I would like to be able to duplicate the problem, but I think I need more details.

Thanks!! Not quite though. It is allowed to have Greenify set to ON in accessibility, so not a general issue, BUT if I turn it ON for "Android Assistant", the keyboard is messed up, and turning it off things works again. So now at the least we have a way to trigger the phenomena!

The app is not the cause itself, it is the active "accessibility service".

@hengyedev, that is a very minor problem for everyday use (own experience)...

Well, my keyboard works! I deactivate many apps. Now I will check which app was the problem. Special thanks to @Sean McCrearyand of course @EskeRahn for your time and support!!! Edit 1: The app which change my keyboard layout was KeyMapper Edit 2: The app which changed the layout too was AutoInput (for Tasker)

EITHER First I uninstalled KeyMapper and said: that was not the problem, yes... because AutoInput was installed too 😑 Well, one app with activated accessibility service crashed the layout.

Just to be sure for those that are testing. Does it require BOTH of these two to be installed to trigger the issue, or does EITHER of them do it individually?

Picture 1 = upper left Picture 2 = lower right Picture 3 = lower left Vazso is the winner, I also use a black background on my own Pro1 😅

The bottom left curve of the display is not perfect, but that problem is marginal. Edit: look at the blue part

I can't notice it in the pictures...is it that tiny difference on the border at bottom left?

I use a black wallpaper, so not an issue. 😅

My Pro1 had this as well. I didn't even consider this being some issue and I never noticed it in action. If it were a QWERTZ edition I'd buy it immediately.

I think that is a minor issue of the display, it is not glue residue. However, it practically doesn't matter. My original display did not have such an issue, but all the displays I bought at Aliexpress had a similar issue in at least one corners, sometimes two... and one of them has a black spot in a very wrong place. My current display has a bit bigger black spot in the upper right corner anyway. So although it is not perfect, practically it does not make problem living together with it - at least I had to look at my phone to find out which corner is the location of this issue f

Could you provide a bit more information to help us develop a test case? I see you have a QWERTZ Pro1, but which languages do you want to use CTRL-space to switch among? Also, which specific keys do not produce the characters you want? If none of them are correct except 'Z' and 'Y', then I suspect you have the wrong physical layout. To check this in the settings app on LineageOS 18.1, look at System -> Languages & input -> Physical keyboard -> Advanced settings -> Physical layout. You should be able to switch between the QWERTY and QWERTZ variants there. Edit: To be v

The 2021-06-05 patches have been fully merged into Lineage branches 16.0, 17.1 and 18.1 only today. That was too late for the build bot. It should come next week, I guess.

Just did a clean factory reset, restoring nothing, opened the Android Market app and installed Android Assistant (only). And from Accessibility set it to ON, and it is enough to trigger the phenomena.