EskeRahn

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),

....On the length of the name: I use a batch I call FlashAICP-S.bat, that only takes the DATE as the argument (in the yyyymmdd format), to avoid messing with the long filenames e.g. FlashAicpS 20220810 @%~DP0\FlashBase_MindTheGapps12.bat %~dp0Pro1_ROM\AICP_taken_from_lineage_18.1-20210913-recovery-pro1.img %~dp0Pro1_ROM\aicp_pro1_s-17.1-WEEKLY-%1.zip calling @if NOT %2.==. %~dp0FlashBase.bat %1 %2 %~dp0Pro1_ROM\MindTheGapps-12.1.0-arm64-20220605_112439.zip %3 (And obviously a number of similar one-line batches for the other combos)

@Hook Are you sure you are flashing to the A/B you are booting into? I use the below bat, to do stuff. Notice the a in these two lines: fastboot flash boot_a %1 fastboot --set-active=a (I assume they could just as well both have been b, and that the important thing is that they are equal) @ECHO off if %2.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause echo * sending %~n1 fastboot flash boot_a %1 shift fastboot --set-active=a REM fastboot reboot recovery does not work, so do manually

....And if it does not work, and you have more time to spare,please try the gapps-free AICP-R -> AICP-S , thanks 🙂

Yes, please do the full optimistic dirty flash, that is AICP-R + MTG 11 -> AICP-S + MTG 12, if that works we are 99% sure a gapps-free AICP-R -> AICP-S would also work.

As well as LineageOS 19.1 and AICP-S (And the box can even be navigated in with arrow-keys and selected with Space or Ente plus Esc for cancel, if you want to avoid touch)

If you are Gapps-free, please start on AICP-R so we will know if it can upgrade to S without a reset. I suspect that it is OpenGapps, that blocked my attempt,

See ANOTHER THREAD for WORKING AICP-S :

AICP-S 17.1 for Pro1 ADD: They have broken AICP-S so it does not work at all in the versions available, even after extracting the boot.img from the zip it self. See my post later in this thread 2023-04-05. They had a few versions that worked (almost) though, the last being aicp_pro1_s-17.1-WEEKLY-20220914.zip . --------------------------------------------------------------------------------------------------------- New version of AICP-S 17.1 based on Android 12 is available for download here: https://dwnld.aicp-rom.com/ aicp_pro1_s-17.1-WEEKLY-20220810.zip It is VERY

Correct @Casey just confirmed it a quarter ago 😉

(OpenCamera supports it too, but obciously this is Pro1 and not Pro1X)

Tried with the old boot-image from lineage 18.1 20210913 (That is the one I used for AICP-R!), with a reset, got he bootloop and request for another reset BUT the splash screen is gone!! So DO NOT use one for 19.1 though it matches Android 12, Use the same as for AICP-R (matching Andoid 11) !! I will update this thread accordingly... (Or parhaps make a new one, closing this done...)

Just tried to reflash starting with the 20220426 boot-image from Lineage 19.1 - required a factory reset, but the same splash screen non the less...

The Pro1X in blue, would make it easier to keep track on which is Pro1 and Which is Pro1X... 😁 I currently have one retail Pro1 I bought, one final sample Pro1 and an early preproduction Pro1. And today got a 'verification sample' of the Pro1X (black), and will (hopefully soon) get the retail Pro1X I perked for...