EskeRahn

Yes, there is a small Hall sensor in one half and a magnet in the other. Seen in landscape, it is slightly above the USB, and if I remember correctly about 1cm in. Add from here The sensor is near the camera button about 12mm closer to the keyboard, and roughly 5mm in from the USB edge You could also display the image from here full size on the Pro1 display...

well I guess that would require an additional variant of the guide, aimed at edl.

I saw it initially but have not seen it since. But would be REALLY surprised if some magic secret update should have been issued that does not even change the build/number. More likely it is something that disappears after 'something', the big question then is what that 'something' is. Could be as simple as a boot, but sound unlikely that those having the issue have not booted.

I got all three working, after studying the antennas, and it is really picky on how it is placed for the credit cards with the 'large' antennas.

I tried to look a little closer at the antennas The simple foil tag (outer circle about 25mm): Put light through the travellers card and the credit cards to see antenna structure of the two cards. (and recreated in paint, not exact measurements at all) This is the one that is seen but is really hard to get working And this one with a fairly complex antenna loop is usually completely ignored, but I CAN get it working, holding it exactly right! (all three works flawlessly on the Pro1)

(....Personally I would not use any phone for lo light images of anything but still motives. My personal pocketable favourite here is the Rx100III by Sony...)

I also read a NFC-tag on the late sample Pro1X. I have two other tags that can be read by the Pro1, but NOT the Pro1X. I edited the title slightly. This tag works on Pro1X, Pro1 (and Titan Slim also on stock Android 11) This tag I only managed to get to work once(!) a few times with the Pro1X after maybe once every 100 retry. Else i get "NFC read error. Try again." (Pro1 & Slim OK) Have not been able a really hard time to get this one to work at all on the Pro1X. (Pro1 & Slim OK) But I CAN get it working, holding it exactly right!

No, OTA=Over-The-Air, so only did official update from within adroid (adup´s app on the retail Pro1). If a used the word "sideload" for that, it was a slip of the tongue. On that unit the only thing fastboot I have done was fastboot oem off-mode-charge 1 Unless my memory completely fails me. ( alsoI got a preproduction Pro1, and a "Final sample" Pro1, that has been flashed with boht sailfish, lineage and aicp in various versions, and can boot into recovery. Holding VolUp+Pwr at the dead icen after attemptied recovery, Works the same if I press shortly or hold to various states o

The bootloader menu works fine (whether launched by buttons or adb reboot bootloader) , but when I select the Recovery option, I see the F logo, and then a dead android.

You are welcome, for details see this.

no no the bootloader is there, but selecting recovery within it fails. I see exactly the same on my retail Pro1 (no X), that has only had OTA updates.

Unfortunately the default bootloader does not seem to have a recovery image in it - at the least the 'early unit' I have does not, nor does the retail Pro1 (no X)

I'm almost convinced we have not had an update, but that the bug is not always there. (I do not know neither what triggers the bug, nor what triggers it disappears)

And a yet unused one that have long been awaiting the arrival of a blue retail Pro1X 😁 ...Yes the camera struggle with the white-balance of blue against red background...

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.