Leaderboard

I have bought it and it has a perfect fit (original is silver and this is black in the following photos). ...and in place: So if someone would like to buy replacement screws, I recommend buying from the link above and the correct details are "M1.4 + 2mm" and 100PCS are to be sold currently at $3.38

I've put together a guide from knowledge I gathered over the last couple of weeks as I eventually got around trying Lineage OS on my F(x)tec Pro¹: https://slions.net/threads/lineage-os-for-f-x-tec-pro1.90/ It takes you through the installation process from Windows setup to Magisk root and SafetyNet validation to working around prominent issues. It will also take you through the build process from Windows environment setup to development and code contribution. Also taking this opportunity to mention how awesome it is to be able to update, use and customize almost every aspect o

Here is a guide I made for myself, edited from @tdm's original instructions. It is a little simpler because it assumes you have USB working and all the fastboot/adb stuff installed, and that you know where to get everything. It focuses more on just the actual flashing, showing both first time and updates. Since I made these instructions for me, they don't include what to do with Magisk other than flashing the zip, since that is all that is needed for SU. It may be useful for some in combination with @Slion's wonderfully detailed instructions of all the steps with all those many helpful lin

I don't play Mario Kart, but I'm not seeing any sort of delay on my touchscreen. Responsive and snappy as always.

Elephone U pro is correct.

I've had problems loading my custom build but what currently seems to work for me without factory reset is: - Sideloading ROM - Sideloading GApps - Reboot to recovery - Sideloading Magisk - Start system I have not replaced recovery but it clearly does not start when I load ROM, GApps and Magisk in one turn and even if I try ROM, reboot, then loading the rest but in that case, I have tried loading Magisk then GApps which may be a wrong order.

The Aug/30 build introduced a weird sticky touchscreen issue for me. It's very apparent in Mario Kart Tour. When I go for a power slide and then let go of the screen to go straight again, the driver keeps sliding as if I kept my finger on the screen. In other situations tapping the screen seems delayed (maybe the release is registered too late). I've switched to the other system slot to revert to build Aug/23 and the issue is gone. Can anyone confirm?

Are you sure? I believe that it is the flashing of the stock that ALSO flashes something to the display. So even if on stock I think we might have to re-flash it to get the screen working correctly - but as it is the same image, there should be no need of a factory reset, so not that bad. I have not tried to do it though, so be sure to make suitable backup in case a wipe is needed to get things working after the flash.

Elephone U pro is correct. Yes, Elephone U Pro is definitely correct; all the successful third-party display replacements I've read about here (plus my own) were with Elephone U Pro screens. That said, I have yet to learn of any difference whatsoever between the Elephone U and the Elephone U Pro screens. Some Aliexpress sellers do offer a choice between the two, but some don't (and only offer one screen as fitting for both phones), and none of even those that do actually would show two different screens for U vs. U Pro, it's always the same image. (Have there perhaps been

I was always searching parts for "Elephone U Pro" (including screen protectors) and based on photos, I would also say that is the display what Pro1 uses. However, as far as I know well, there may be a frimware update needed which stock OS will automatically do but it would need a software under LineageOS. Without that, there are some problems with touch margin.

I'm pretty sure that a reboot to recovery is needed between the first two. At the least that was the case for Lineage 16 - have not tried without since.

Not sideloading magisk after sideloading a new ROM does not break it's functionality it seems but the app won't be fully loaded. It will look like Magisk is not installed as far as the app is concerned. Therefore when loading a new ROM the process goes: Sideload ROM Sideload GApps Sideload Magisk Reboot

As posted on GitLab there is a Magisk extension call "Fullscreen/Immersive Gestures (Q-S)" to workaround this issue. It's designed to hide the "hide keyboard" tool bar displayed below your onscreen keyboard. Use the volume +/- buttons to set it up. I used the following options: Vol+ Fullscreen (not sure though what's the difference with immersive) Vol+ Low sensitivity gesture (apparently also fixing the Task Switcher gesture being overly sensitive in landscape) Vol- Don't disable back gesture It's also worth noting that this is so annoying that manufacturers like Samsung

I think @EskeRahn told we have an "fn layer" associated to a key (in fn array) which has a modifier but not for another key. So "another key" would send the generally specified modifier together with a key instead of remaining silent while "a key" would only send the key/combination specified in fn array.

This is the way the in-kernel 'Fn-shift' feature that tdm wrote works. The in-kernel keymap can specify a modifier state for any key, and the driver will generate a 'chord' of key events when the key is pressed.

Beware of stuck keys with this approach 😞 I worry a bit about the side-effects of having a key both send a keycode and also enable virtual 'chording' via flags.

It seems it does not re-enable them but I have remembered they were disabled completely when the file exists. The modification what I did may send a keycode on pressing a modifier while it will also generate the keycode assembled in fn-level of the keymap (if enabled). So it behaves similarly except it will also generate the keycode on pressing/releasing the "fn"/Yellow Arrow key. Eliminating this behaviour is possible but it needs deeper modification so it is more complicated.

Yes, my proposal is based on your work 🙂 I am trying to simplify the implementation a bit, and extend it to more remapping cases.

This is the change that fixed the problem on our device, but caused problems on others: https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/312770