EskeRahn

Added 'something' at the top of this on backup of the persist partition. https://community.fxtec.com/topic/3207-various-roms-available-to-the-pro1pro1x-available-for-download-links/ Please correct me if what I wrote was wrong. @mosen, @ducksoup, @steeb and I will have it changed ASAP.

Yes, but note that this is a user-to-user forum where FxTec only occasionally are active. But sure would be preferable if they provided the info. I will add 'something' for now....

Maybe you should make a separate thread on what to do switching FROM stock Android, that I can link to in the ROM thread? As this seems generally crucial/useful.

Not ALL parts are the same, but many are, would be nice with a list of what is identical, and what is not..

I'm pretty sure that the popping sounds are related to the clipping, so no clipping means no popping I tried it with some talk radio, and gone at max vol, and on the other hand when the level is below about 50% all sounds (including pops) seems completely gone from the right side/bottom speaker

Sad. Then something is stuck between the case and the button. So the only thing to do is to have it opened and have whatever it is removed. So await what support suggest you to do. IF they suggests you to open it your self, and you feel comfortable doing so, then please take (and share) some photos doing so, as we have only the FCC images of the interior of the Pro1X, there should be some visible differences compared to the Pro1.

With newest platform tools gives fastboot: error: Unable to get max-fetch-size. Device does not support fetch command. On both Pro1 and Pro1X

Not that it is an actual fix, but is a functional workaround: If you use a shell (or flip) case, the chance of accidentally triggering the fingerprint reader is practically eliminated. (There is a loooong thread on (primarily) DIY cases here, a short summary is that any soft case fitting the Huawei P20 Pro, is likely to be a good base for a Pro1(X) case. I also made my own thread here.

Looks fine to me. One minor detail. Flashing AICP, the 47% blah blah click yes is on the main zip, and does not appear again on the Gapps zip. So Lineage and AICP acts slightly different here.

The Pro1X stock Android comes with a preinstalled FactoryKit app. (Similar for the Pro1, See this) It is not launched the same way as on the Pro1. Actually I have not found the correct way to start it! Though by using an app like "Activity Launcher" and selecting a shortcut for "FactoryKit" sub-item "FactoryKit", I can launch and get the following list, and some can be started, and some crashes direcrly. Launching it the above way make the app crash or halt after the test that works are finished, so you are likely to need to swipe it away from the app-list after ea

Sounds like a software issue. Will try if I can reproduce... ADD; Yes I got the same (on a before retail sample) (Add II: Headset not affected by this bug)

It works on the Pro1X too 😀

I will highly recommend NOT omitting this tiny step. Remember that an OTA update swaps what is active between A/B so could easily become a mess Alternatively flash the boot image to booth boot_a and boot_b, so it is in whatever is active.

Me too: https://eskerahn.dk/?p=4539 Most important: Settings ► Intelligent assistance ► Other Settings ► Home key function ► Double press to launcher.

HA, I replied you in the other thread too.... EDIT: Cleaned up my mess, now point back here! I'm pretty sure that is what is going on. I both tried to do multiple "Advanced", "reboot to recovery", and that did not change a/b. Then did a new flash of AICP, and instead did "Advanced", "reboot to bootloader", and there "Recovery", and it also showed it switched, I do not know if there is any other way to get the Recovery to refresh it self than to reboot to recovery. But would be nice if it at the least gave a warning if you attempt to make a new "Apply Update", that it will NOT go to the

EDIT: Sorry for double posting, should have referred to the other thread in the first place. Replied there: https://community.fxtec.com/topic/3425-setup-lineage-os-on-your-fxtec-pro¹/?do=findComment&comment=62467

Guessing here, it might have meant more delays, E.g. if they were not available within a reasonable time frame.

I currently only got a unit that is not retail, so MIGHT be different. My button is quite loose, but if I do not touch it, it tilts one way similar to your picture. If I press at the opposite end, it tilts the other way. The active contact is near the middle of the button. If yours stay down pressing at the other end, it could indicate that 'something' is between the frame and the button. And I assume it is unlikely to get rid of this without opening the device.

Thanks for testing. Maybe what recovery boot image I have in slot boot_b for some reasons make it behave less bad than yours - I have no idea what version.... nor do I know how to find out what version is flashed in slot boot_b? Obviously I could flash to both boot_a and boot_b, that is dong the flashing double before first boot, To make sure I am in a well known state.... With the risk of making it unable to boot AICP-S. I will consider this, the next time I'm in need of a wiping it anyhow. ADD; I tried sending the boot image to both, and it worked fine, (with no reset, and nothing missin

In your guide it says that the step rebooting into recovery from within recovery "will switch the active boot slot", I believe that is strictly incorrect, When I do that it says "active slot: a" (or b) NOT changing, I believe that the "apply update" from within the bootloader of the main flash that does the switch of active slot (without the header of the recovery reflecting this), and then the reboot to recover boots into that slot... Note that flashing e.g. Gapps, does NOT change the active slot, so it is part of the flashing the main 'only'. So that a more correct wording would be e.g.

Bad news! This ALSO seems to hit stock Android 11 on the Pro1X 😭 ADD: Though it seems that unplugging and re-plugging here several times can suddenly bring it back to normal, so not as bad as what we see on Lineage. and AICP.

(For what it is worth, we might have similar issues with newer boot images for AICP-S for the Pro1, see this thread)

For a limited time I put up the old recovery image here. lineage_18.1-20210913-recovery-pro1.img

It might. See this post, though not on AICP

Thanks for the tests. Yes your guide is very close to what I do, also based on what TDM taught us. And indeed something sounds fishy. What is the recovery boot image you are using? And I also noticed tht the seventh boot is different. Already before the yellow AICP comes up, the 'flickering' of the FxTec logo is different. And it goes to a blue logo before it boots AICP (under some circumstances requesting a reset during the process),