EskeRahn

Indeed, as I do both, that could be the explanation why I have not seen it on any of the devices.

This might also explain why some sees it and some does not. If there is a slight variation in the length or mount of the black cable between various batches this could mean that the shorter ones go under the plastic just fine, but the longer ones have a slight curve that are pushed on unevenly. A fraction of a millimetre could be enough...

I guess we all share that frustration, as they sadly do not publish anything. So we are left at guessing on what the H.. is going on.

(lineage-20.0-20230828-nightly-pro1-signed.zip on Aug 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316) (*) on the question after the main flash on whether to reboot to recovery for additional flashing, You can either answer with No, and have it working normally. If you answer Yes it flashes correctly but we get an (incorrect) message on the PC that it failed:

I bet it is even more complex, as the conversion of the old Pro1 orders to Pro1X most likely are not forseen. Not that this excuses the lacking refunds.

They certainly are obliged to pay cancelled pre-orders back, but I do not know in what order they are required to serve their obligations.

The problem here is with the lacking info we are left to guessing. Even if your theory is correct, I highly doubt they are financing any new device themselves, so they can not just take the money someone invested in another product/project and use for us. At the most they can use of their part of the revenue for us, or from any money someone might invest in (or donate to) FxTec as a company.

I doubt that "forgot" is the right word here, but certainly very annoying that they do not post an update on IGG on what has been going on since their June-update 2½ months ago....

Will try to remember to answer Yes on Monday for the Pro1, and see if they implemented a fix. If you run each command individually on the pc it might work, ignoring any message on the pc that the flashing did not end correctly.

(lineage-20.0-20230821-nightly-pro1-signed.zip on Aug 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316) (*) still question after the main flash on whether to reboot to recovery for additional flashing, must be answered with No, (Redid with new four months newer Gapps)

(lineage-20.0-20230821-nightly-pro1-signed.zip on Aug 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-202230408_162909) (*) still question after the main flash on whether to reboot to recovery for additional flashing, must be answered with No,

...Already merged 😆

That is unfortunately a known issue with the Pro1X, that it allows itself to get discharged beyond the point of recharge by plugging in, We have several threads mentioning this. I will try to find and merge. merged

Space might do the trick, it does on plain android

(lineage-20.0-20230807-nightly-pro1-signed.zip on July 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-202230408_162909) (*) still question after the main flash on whether to reboot to recovery for additional flashing, must be answered with No,

I assume you are referring to when on the home screen, so I guess it is the launcher that would handle it, which one are you currently using. There are a truckload of launchers out there, See also https://community.fxtec.com/topic/2803-want-keyboard-shortcuts-with-nova-or-perhaps-any-non-stock-launcher

(lineage-20.0-20230731-nightly-pro1-signed.zip on July 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-202230408_162909) (*) A new question after the main flash on whether to reboot to recovery for additional flashing, must be answered with No, otherwise the PC sees the flash as failed. Instead you (like previous versions) from the main menu need to manually select Advanced and Reboot to recovery,

4.1V does not sound like a dead battery. I would expect some reaction on the LED when plugged in, but as you see neither this nor anything on the display, my suspicion would go to the ribbon cable between the two halves... As we are talking Pro1 and not Pro1X, you might try a hdmi-adapter, and see if you get an image on a monitor. If you plug it into a PC, does it react in any way, can you from the device manager see that there is something? Even if it is Off, the pc should react somehow... At the least in principle you should be able to operate the device, even without the scre

And if you do not want to use the keyboard, you can get a lot more value for the same money from other models... But that apart, it could still be an interesting protecting case for e.g. transportation, or while using it say on a bike for GPS navigation. They are available outside Canada. Just change the .ca top domain in the link to one suitable for you, e.g. .de: https://www.amazon.de/dp/B0B8S1BC74 And the price does not seem that bad: €16.50 with shipping.

(lineage-20.0-20230724-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-202230408_162909)

Just out of curiosity, do you see a different code for an 'enrolled finger' and any other rejected finger?

Interesting. It would be great if FxTec could reproduce the bug. IMHO that would make it much more likely that they can find a fix. Let me tag @Casey here, and hope you can get in direct contact. I hope they will be willing to take a trip to your location.

(merged threads)

Oh I'm not trying to say that it is not bad! What I'm saying is that we have not got a clue if it is 10% or 90% that are affected by the severe bug. we do not even have a clear pattern, so we can not say that it is likely or unlikely to work for anyone - and that only adds to the frustration... We do not even know if it is specific locations&carrier combinations that are not supported correctly, or if it is specific devices that would fail all over. I lean towards it being some particular environment it fails to handle correctly. My personal GUESS is that it is some band-swit

(lineage-20.0-20230717-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-202230408_162909)