Leaderboard

Looks like it's fixed. I'll test it some more but I already advised the guys at Lineage to revert it.

I'm investigating that lag issue. As explained above I further reduced the list of potential culprit. I switched back to my broken build and sure enough not long after boot I could reproduce the issue fairly easily. I'm currently attempting a build reverting that change to see if that fixes it.

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

Greetings, I have one of the fancy Pre-Christmas devices (Lineage). I had horrible problems with ticks and poor sound quality upon recording (mainly uneven recording levels, distortion to the point of being unintelligible). Fxtec asked that I return the device (at my cost) and was told the sound card was replaced. The recording issues remain. There is no answer for 45 days despite repeatedly responding to the last message from Fxtec support on 21JUL21 of: "Dear Gene, We're sorry to hear about this. Different microphones are used to record different things. When you use the voice

Today I noticed (because the device switched off GPS while my hiking app, Locus Maps, should have been recording the track) that some apps under "battery optimisation" are neither listed as "optimising battery use" nor "not optimising", but "battery optimisation not available". Is this something new, because I never saw this before, especially not with my Locus Maps app, or have I just missed out on this?

Good Morning ,Please let me know how I can get a spare screen and also what may have happened if they don't hear me on the phone when I speak.

I think they have tried to reuse all components in Pro1-X so it should work. However, only F(x)tec may know it for sure. I don't think yet.

Hello you lovely community! I have a question about the spare battery that is provided via Indogogo. I tried using the search function but I didn't stumbled upon any information about my concern (maybe I am just blind). My question: Does this battery also fit for the Pro 1 without "X"? Anyone tried this yet? As long as we can't identify the model, it seems to be the only option to get a spare battery? Thanks for your help in advance! 🙂

Still looking for a solution to my application even though others use their device differently. Also looking for a response from FxTec support. Thank you!

Thanks for the confirmation. What I'm still not sure of is whether this has been in Android 11 / LOS 18.1 right from the start, or might have been introduced later? Like in one of the last few updates? I've been on 18.1 on my Pro1 for a while now, and I've been using Locus Maps on it for a while, too, until now also without observing any GPS hiccups (I've asked about that on the Locus Maps forums, too)...

I didn't notice it before, but I just checked my Moto G8 Power on Android 11 and it's there too. I suspect it's an Android 11 thing.

Those are the changes that occurred between the 25th and the 30st of August. There is obviously one Pro1 change that could be the culprit. repo forall -c 'git log --since "AUG 25 2021" --until "AUG 30 2021" --pretty=format:"===============================%n%Cred$(git config --get remote.github.projectname)%n%Creset%H%n%an%n%ad%n%B%n"' =============================== LineageOS/android_device_fxtec_pro1 15b9323d740da90ba3c00a86002a6b995c42d211 Luca Stefani Wed Aug 18 22:07:34 2021 +0200 pro1: Adjust powerhint for QOS interface Currently all writes to the dev interface are done by WriteStrin

The first one looks like a weird variation of the phantom touch phenomenon. I can't reproduce either on my Pro1 with a screen that was replaced in January by FxTec (not a Alieexpress Elephone U Pro LCD) using that latest nightly of LOS. I tested the second video y swiping rapidly up and down on the settings menu. Different speeds, different amounts of pressure. Always rolled, never froze, no lag.

I reverted back to a custom build from the 27th of August and I don't have that issue at all. Actually I believe my code checkout was front the 25th so at some point between the 25th and the 30st someone introduced that regression. Now go figure what it is exactly.

it's definitely done in software as it depends on the app used

I switched to the AOSP keyboard, turned off the autocapitalization. the software keyboard doesn't autocapitalize, the hardware one does (tested by writing an e-mail in k9 mail)