EskeRahn

Just to be sure, have you tried other nfc-items? That is do we know if it is general or specific to yubikey ? I tried my Titan slim on Android 11, and nfc works out of the box. I will try to install installed AICP-R and AICP S, on my test unit Pro1 to see it it is related to Android 11 / 12 ADD I, just tried AICP-R on a Pro1, and it worked out of the box installing "NFC tools" for test. ADD II, just tried the broken AICP-S on a Pro1, and it worked out of the box (well after the boot-loop) installing "NFC tools" for test. So the issues seems to be related to Pro1X, (or your spe

The reader is working on my Pro1 with Stock Android. And yes,at the top (seen in portrait) I believe it is between the logo and the camera

Flashed today's release aicp_pro1_s-17.1-WEEKLY-20220803.zip, with factory reset and no Gapps And it is the same error as above. Boot-loop some ten 10 times, asks for Reset, Boots with error screen, and all seems to work, except this splash screen on each boot. (But to make things clear, it is 'only' on the first try after flash that it requires a reset)

Is this Pro1 or Pro1X?

Maybe they changed something for the worse? That could be why it was so relatively easy to trigger it here too? (reposting this as i had to steal an old post....)

Thanks for the workaround, I have marked your post as recommended, hopping that other will see it. And pinned this thread.

Minor bug: It can forget to respect the screen time-out, so drained from 30% to 5 % in 2½ hour. (And then was in the no-charging mode, until boot...)

So I guess we can conclude that batch 1 is US qwertY, and other layouts are in batch 2.

(lineage-19.1-20220801-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313)

(and does so even within the pinned ones it seems)

Sad you can not get things to work with your US carrier. On sale you might try this thread, usually many eager buyers, though with the Pro1X beginning to be delivered, I guess many will hestiate to see users reactions, to decide if the pro1 or pro1x is best for them.

Thanks for the link and guide, added this to thread here: https://community.fxtec.com/topic/3207-various-roms-available-to-the-pro1pro1x-available-for-download-links/

...Done, but no matter what I do, the system insists on the strange order. Despite I both created and pinned them in order 1,2,3.....

Well we know that at the least @esialb got it, see this https://community.fxtec.com/topic/3596-stock-firmware-for-pro1-x/

(deleted, see updated version below.)

Glad to hear you got it. You might consider 'vote' in the three polls if you did not already https://community.fxtec.com/topic/3590-pro1x-delivery-progress-part-13/ I have not heard the source for any new ROMs yet, but will updated the ROM thread as soon as I do

Now that is a tempting offer.... Had it been qwertZ it would be been hard to resist it... My keyboard is beginning to act up giving double strokes on several. But after almost three years daily usage that is acceptable, and a Pro1X hopefully should be delivered soon here too...

It exits the bootloop after about 10 iterations, with a request for a new wipe though.

99.99% sure it will not work for you either, but thanks for trying.

I have tried to report it here, hope this is the correct place? Though I doubt it as this got #1 @Sean McCreary ? @tdm ?

Flashed todays release aicp_pro1_s-17.1-WEEKLY-20220727.zip, with factory reset And it is the same as above. with and without MindTheGapps-12.1.0-arm64-20220605_112439.zip Goes directly into bootloop, and after about 10 failed attempts asks for a new factory reset, and after that continues with the above splash on top of the setup wizard. (Did not bother to flash back to AICP-R, just turned it off, awaiting a usable version, hopefully next week...)

In my person experience Lineage was better than stock BUT neither worked for me as the carriers I tried do not accept the device.

I do not know, but for SOME vendors it is also a matter of the carrier white-listing the device. I wrote this quite a while ago.

There are no easy to access list currently/yet. Some bugs are general for the OS, and some are specific for the Pro1. It would great if some took the job of maintaining such lists. Especially for the issues that are specific for the Pro1. The info IS generally available in each of the linked thread. But quite a bit of work to extract the issues, and remove those that have been fixed since the issue was posted. So If you (or someone else) took the time to do this, it would surely help others in deciding which one is best for them. It is unlikely that it is the same ROM for all

Indeed. When the first report they got a mail, we can expect all in the first batch to get a similar mail within few days. Those of us that do not, well we (or they) are in batch 2....