EskeRahn

I have had the same thought. Could be nice to have a donor or two at hand if something breaks down in my daily driver. (That was working on the donor)

Would be awesome if FxTec could offer a setting selecting Full and Alpha, would be totally acceptable if a reboot was required after changing. With a switch people can choose what they prefer. IMHO both have their Pros and Cons, so would be great if each user could choose what matches our needs best.

It would be great if we could have an equally simple process to flash it to its stock Android-state (with GMS).

Much can change in peoples live in a couple of years. I see nothing wrong here - there could be a large number of different reasons. Though as being one of the many still waiting, I can envy those that got it, and feel frustrated that it was not those that wants it that got it in the first wave, despite being in the first third of the super early birds.......

Flashed aicp_pro1_s-17.1-WEEKLY-20220921.zip on security update 2022-03-05 Now I'm completely confused. Still initial boot-loop after flash, But despite the outer file signals aicp-S and 17.1, the inner version is aicp 16.1 and tells it is Android 11??? (I downloaded again, did a binary compare, and a re-flash - just to be sure, but....)

Be aware that AICP-R is gone within about a week, so hurry up and download!! See above

Be aware that AICP-R is gone within about a week, so hurry up and download!! See this

I must admit that I'm very close to giving up on AICP-S, since no one seems to be working on fixing the basic issues that has been there for over two months of initial release, and security updates over half a year old. So maybe I should look at sailfish instead....

It is really hard to guess what it could be, and you already know the standard suggestion: Factory reset and no apps installed, to see if that is stable, but not a very useful suggestion IRL, so as @Hook suggests, have a look at what have happened at the time the behaviour started, and peel off any new apps. There is absolutely no guarantee that an app is the culprit and even if it is, that this will find it. If an app it also could be an Android-market triggered update that have caused the problems. At the least you found a consistent way of making it crash, so I would suggest starting to

(lineage-19.1-20220919-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.

Well though I'm personally happy with my Pro1 (still waiting for the Pro1X), but that does not mean that everybody has to feel the same. So I don't see anything wrong in someone trying to find a new owner for it, that hopefully like it better. Though I had considered moving them into one thread.

Flashed aicp_pro1_s-17.1-WEEKLY-20220914.zip on security update 2022-03-05 Seems much the same. Still initial boot-loop after flash, But that aside things seem to work.

If people want to avoid the camerabutton launching the stock camera app AND they want to use a different app (e.g. open camera), a way to avoid accidental launches would be to simply disable the default camera app

Well one unit, but composed of an elastic mat (rubber, silicone, ...?), with hard keytops on top, and a plate with holes around the keys. And most likely some sort of glue hold these tops to the mat, and some adhesive (tape or glue?) fix the plate to the elastic mat

If I understand the question correctly, it is just the small hard part on top of the rubber mat that has been peeled off the Z, and I'm sure it can be glued back on with full functionality. Personally I would go for someting a little more plain than superglue, so it can be remove as first attempts. But it is likely that a tiny drop of super glue placed where you can see it has been glued earlier will work.

same here. Had it been offered as a plain pre-order only and not an igg, perk, I would have pre-ordered it.

I'm a backer too, and as backers we have invevested, hoping in getting the device cheap. A lot of things has happened since, and I'm amazed that they fight on, and have not just folded. So there is a good chance that our investment are not completely lost. If people want consumer rights they must do a order/preorder, and not invest in a crowdfunded project, where we take the risks.

There IS a sensor in the screen for it, though we do not (yet) have something that can make it turn the display off, as we do for the Pro1 - thanks to @Slion - let us hope he finds a way to do it for the Pro1X too. On the thickness, I usually cut out the credit-card part, this gives a little extra space. (and the case usually is stiffened by some cardboard, so you can bend it to get a better fit)

The method looks sound in principle, but forget about AICP-S for now... And anyway I use a MUCH older boot/image lineage_18.1-20210913-recovery-pro1.img You should fetch AICP-R not S, S is not stable (yet?), and still on march security patch.... I had a LOT of trouble with S.... With S, I needed to do a factory reset from within the recovery, and even so, it still asked me at the seventh boot, to factory reset again. And still after that does a bootloop after each flash of new version.... AICP-R is stable, so fetch a copy of R ASAP, as it is likely to roll out the bottom of the

There is also a rather similar list under*#*#4636#*#*, BUT it is not identical - I do not know how these two list are intertwined .

You could consider to choose to entirely omit the 3G bands, to avoid it attempting to switch to them. E.g. LTE only. There is a long list of combinations under preferred network type I do not know the exact meaning of all the used terms, so will likely require some googling to find the optimal setting.

Indeed, we have several reports that fastboot is more picky than adb. I have a feeling that older pc's generally works better than new pc's. That is also why a simple hub inserted between the pc and phone sometimes can do the trick.

Noticed THIS difference: And POWER_SUPPLY_INPUT_CURRENT_LIMITED sounds very much like what has been my theory all along..... The big question is how to avoid this state being triggered too soon though....

...If you are on a device with AICP or LOS you can (by an option in developer options) allow ADB to do rooted stuff, e.g. ADB root adb shell setprop persist.dbg.ims_volte_enable 1 adb shell setprop persist.dbg.volte_avail_ovr 1 adb shell setprop persist.dbg.vt_avail_ovr 1 adb shell setprop persist.dbg.wfc_avail_ovr 1 ADB unroot (not available on stock android though - neither Pro1X nor Pro1 )

(lineage-19.1-20220912-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.