EskeRahn

Python=Phewton

YIKES So you are saying that I can not limit Phewton to a (virtual) machine to compile edl? Phewton actually have to infect the physical machine that is connected to the phone? ... Not a chance... But thanks anyway.

No typo. The Guide we got for using edl for flashing the Pro1X is for Linux, if I remember right. The windows guide is using QFIL. Compile edl

...Also remember that to compile it requires the PC to be infected with phewton 🤢

Just tried a factory reset (not a reflash), Entered google account, but skipped restore, and as soon as the wizard ended launched youtube and played some random junk, and it worked (no matter the volume) So this was NOT enough to trigger the bug. (despite having had it earlier)

He he, I mean Boot. When I had the bug, the first thing I did was to try headphones, and it was fine. When I had it, the only thing that helped was increasing the volume. As described earlier. I do not recall how early I tested it. But I do now it was only quite a while and multiple boots and other stuff later I tried again, only to my amazement to find that it seems to have been gone. But as this is a test-unit, I will try to do a factory reset, and see if the bug reoccur.

Sure it can be done, but someone has to make a variant of step by step guide for people not on Linux. So (almost) any Pro1X user can step back to the build they got it with. We have to remember that some might also be using a pc from the fruit company. So optimally a guide that step by step list what has to be done initially to get edl up on either Linux/Windows/Mac, and then a (almost?) common step by step guide on how to retrieve the persist the first time, and flash all the needed (including the saved persist) I'm sure that if anyone would do the work to create such a guide, it coul

(took the liberty to clarify in the title that it is not an issue with the camera function but the camera housing)

Well the problem here is that it is sticking out, so very hard to not press it inadvertently. Every time you put it on a table (without a shell or case) it will get a slight bump, also using the keyboard placed at a table every key press, will press slightly on the camera... So I would strongly suggest all Pro1X users to consider using a case OR at the very least add some suitable strip of self-adhesive rubber, at the least 1-1½mm thick along the long or short edge towards the camera, (can be found for next to nothing on ebay, thou bot likely in blue), so that the rubber hits the table first

The Pro1X camera do protrude about 0.8mm, which is more than on the Pro1, where it is less than what I can measure.

Danish passports with chips has an antenna like the travellers card above, and has the same issues. Can be read by the Pro1X, but not easily. I would guess it is the same system for all (or at the least many) countries with passports with chips.

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...