EskeRahn

Yes it protects both camera and fingerprint reader in the 'Japanese book' version. I choose NOT to cut out for the camera, as I seldom use it, so no problem open the flap all the way to access it (they are already prepared, to fold in the middle) The whole idea of turning it around so it open to the right, seen as portrait, is that it 1) protects the fingerprint reader and buttons. and 2) it is more natural to have the flap away when the keyboard is opened. Here a few quick images.

Sad that you do not like it. Well if the box has been opened anyway, I see no potential drop in value by you having tried it out also. From the experiences with the Pro1 we know that FxTec has the policy that the warranty follows the device, so should it be somehow faulty, the new owner will have the same rights as you have.. But obviously if you have tried it and it works flawlessly, it reduces the risk of a DOA device for the new owner.

Have you considered a flip-case? Her a slowmo video of using a DIY case, that can be made in minutes from a cheap Pro2 Pro case, with no special skills. YouCut_20200123_155044091.mp4 It offers quite good protection IMHO.

See also https://community.fxtec.com/topic/3600-open-discussion-related-to-the-progress-in-getting-your-pro1x/?do=findComment&comment=62891

That is how I read the current situation, unfortunately. We know we need a backup of Persist, but we do not know why that did not help @ducksoup, at best it is a matter of how the restore is done, as it seems to work for @mosenwith edl.

Thanks, Could it be a problem to request it to display anything, if it is fully depleted? I mean as the logic is so dumb that it does not have a lower limit for attempting a boot, most likely there isn't one for displaying either, so could also be problematic. ...I would not dare to try it...

( @Spielverderber Found the thread, merged )

It sound like a depleted battery, and the (silly) default of booting on charging. We have another thread in here with one that had exactly the same, I'm not sure he found a fix. For anyone else i STRONGLy suggest to do the following from a pc connected (boots the phone, but does not clear things) adb reboot bootloader Wait for boot to bootloader to finish (or do manually holding VolDown+Power) fastboot oem off-mode-charge 1 There is this silly default that powering the phone turns it on, and if the battery is depleted, it does not have enough power to do the boot...

Be careful with that, unless the keys are saved first. At the least the persist partition should be saved. I would suggest to start with a factory reset (wiping any user data), and skip everything in the wizard, no restore from anywhere. If it still does not work, try the reflash,

A little more digging: It is when "Android Assistant" is given the accessibility privilege that the layouts act strangely on Pro1X

Just did a factory reset of the Pro1X, and the keyboard works as it is supposed to.

Great, Really happy that it is not a general issue, but just this one that is messed up 🙂 Can you select other languages too? Does Ctrl+Space cycle through them as it is supposed to?

If no one else find a solution before that, I plan to try to backup everything from the retail unit that I hope to get soon, as well as the early unit in the state it is, and then see If I can wipe the early unit completely with Casey's guide, and attempt to transfer the keys. It might not work as the 'serial numbers' (imei, mac etc) could be saved somewhere completely different, and they just might have to match the attestation keys... I do not know. https://forum.xda-developers.com/t/info-android-device-partitions-and-filesystems.3586565/

Indeed and maybe also what he did not *LOL* That is more precisely narrow down the difference between what @ducksoup and @mosen did. Since restoring the Persist helped Mosen, we can conclude that it is needed But since it did not for Docksoup, we can also conclude that restoring it is not enough. Maybe it is HOW they did the backup and/or the restore that was different? e.g. file rights, Maybe what Ducksoup did 'damaged' more than what Mosen did? Maybe Mosen restored something else, that also matters? It will require more thorough tests to say for sure what

Beyond A-Z? I do not get neither Ü, Ä nor Ö nor SS et cetera. I ONLY see the Y-Z swap, the rest is US. I should be on latest firmware 2.1.2, Though the hardware is not a retail unit.

Sad to hear, I was unaware of that it could be bound to a specific device, I thought it was info that could be moved even easier than a physical SIM. (Though contacts would obviously have to be handled also - but I believe it is rare to have the contacts on the sim today)

There seems to be some issues with the provided layouts, selecting a number of different languages, none of them gives me letters right of L and P. Selecting German does swap Y and Z though, all the rest is like the US. So currently not matching the print. (ADD: Well French AZERTY do move the M up right of the L - the rest still US) Ignore this, see @Benni's replies below, local issue on mine.

We have just yesterday learned that this is not enough....

Thanks so we now know that it is important but NOT sufficient to backup the persist partition, so now the big question is what ALSO should be backed up? (And without the ability to add key-attestation, it is hard for us to test, unless we initially backup EVERYTHING from a device that still got the keys....)

Personally I had hoped that when they redesigned the main board, they had added an eSim. But might have been too expensive, or might not be supported by the SoC?

Ah I see, so not only suspending battery charging, but suspending power input completely. So the discriptive wording ought to be adjusted slightly. Maybe something like suspending power input (and thus battery charging)

I wonder if that suspended battery charging could be related to the issue behind this:

Ah sorry! that option is for Lineage and AICP not stock android DAMNED!!, so the whole idea crashes, and I believe there is no recovery image to boot into by stock either... So it will require a weird approach of flashing the bootloader for LineageOS or AICP first, to fetch the Persist that way.... Then it is getting (almost) as complex as the edl

On Droidian, note that @Benni has discovered this

My fault, I replied to the post by @VaZso , i can see, sorry. Sad to hear that it seems to be hardware related. I guess you will have to send it in. 😭