Leaderboard

Not new at all... Also there on stock Android 9.

All the Pro1 labeled fixes seem to be the keyboard stuff. https://download.lineageos.org/pro1/changes/

Updated to the Sep/06 build today. Can confirm that the screen lag is fixed.

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

These two changes have been merged, and are in the 20210906 build for Pro1. If you have any trouble using a custom keymap, please open a new bug report following the instructions here: https://wiki.lineageos.org/how-to/bugreport

I can confirm that the category "optimisation not available" exists on Lineage 16, too. Though I have only a handful of system Apps, mostly related to telephony, that fall into it. Specifically, my GPS App (OsmAnd) is listed as "optimised".

Just out of curious I tried some time ago screens both for Elephone U and U Pro and both are working fine after reflashing to stock.

I'm using Delta's best charger - 5.2V 3A without fast charging and I have the same problem. I don't know what causing that, its just too inconsistent.

I have changed the behavior of DeviceSettings here: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/315310 The built-in keymap mods are still toggled off and disabled when a custom keymap is active to avoid interference, but you can now use the built-in keymap mods when a custom keymap is present but not installed.

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

My son is on ATT in Michigan also, and no amount of cojoling or sim swapping hijinx were able to allow him to to keep his pixels on ATT. He jumped ship. I'm on Tmo and the Pro1X is on order. I'll let you know how it works if it ever ships.... 😞

Sad to hear you broke the screen. On the call quality, a headset might help you. I use a wired one, and that works fine. (though obviously just a workaround not a fix)

It looks like it's still in there though somehow it was remerged? No sure what's going on TBH. Maybe they fixed it some other way too...

Good idea. Something to try next time I need a screen replacement, if noone else does it first... By the way, I guess someone should really change that script and remove those REMs before the system/vendor related lines...

PPS looking inside the fastboot_all.bat inside the .7z file, Someone with more understanding of these things might be able to pinpoint the specific file that does the trick: fastboot flash boot_a boot.img fastboot flash boot_b boot.img fastboot flash dtbo_a dtbo.img fastboot flash dtbo_b dtbo.img rem fastboot flash system_a system.img rem fastboot flash system_b system.img rem fastboot flash vendor_a vendor.img rem fastboot flash vendor_b vendor.img fastboot flash vbmeta_a vbmeta.img fastboot flash vbmeta_b vbmeta.img fastboot flash userdata.img fastboot flash abl_a abl.elf fastboot flash

The clipping seems like a firmware/software issue, so most likely not much point in sending it in. Is it related to the two sources? Someone are talking in the background and the music is playing. Could it be some attempted noise reduction that are teasing? It sounds a bit like when e.g. Skyping with someone in a meeting room, and the equipment struggles with recording what is noise and what is signal.

I'm guessing from your question that the answer to my previous question is that you are on the stock Android 9 the pro1 came with and not Lineage OS. In which case, you don't need to care what flashing is (in this context, sideloading an alternative version of the OS). It may be that all you have to do is hook up the new screen and it will be fine. If not, try a factory reset after you have installed the screen, Assuming you have the latest update to the Pro1 (dated Aug 2020, I believe), i would expect it to apply what is needed for the screen edges. The factory reset will, of course, era

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.

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.

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! 🙂

You want to buy a screen for the Elephone U Pro. Phone call quality is known to be bad sadely.

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

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.

If you are using the same MindTheGapps and you have previously flashed it to both slots, it doesn't matter if you flash it or not as long as data hasn't been wiped. At least, that's what I think is going on (I'm not an expert).

Yes, this is a side-effect of the A/B system used by the Pro1 and other modern Android devices. When you install a full OS image, it is written to the *other* slot, but add-on packages are written to the current one. You need to reboot to recovery after installing a new OS image to swap slots.

That is not what I see with getevent. Android does repeat keys when they are held down, so it seems your monitor is looking at the event stream at a much higher level than the event stream from the kernel. To fix this behavior, we probably need to be looking in the Android framework rather than the keyboard driver. I agree a GUI for creating custom keymaps would be a helpful feature. After applying CR#315276 and CR#315298, you will be able to install a custom keymap with adb: adb root; adb push my_keymap /data/system/keyboard/keymap As a sample custom keymap file, this is the KE

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

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

Ok, so way back when I said "I'll keep you guys posted" about my adventures trying to get my screen replaced. 7 months later, here's an update: Tl;dr: I still have not been able to get an official replacement screen from F(x)tec. 7 months of having effectively abandoned my Pro1 for practical reasons, and not being involved with the community at all. Trying to talk myself out of demanding a refund for the replacement screen I ordered, but I can't say that's going well. So the first thing I did was check eBay in case anyone was selling Pro1 parts, or just a dead Pro1 for parts. I was i

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 I have a similar issue. Looks like I'm getting lags or freeze from time to time. Definitely a regression in the latest release. Even though I'm not actually using the release but my own build from around the same time. It happened like 5 times while I was typing this message. That's 6 now.