Rob. S.

Surely looks like a defective camera to me. There's no way a phone camera with its huge depth of field could render one corner halfway sharp (bottom right) while blurring the rest of the image if there wasn't something bent out of shape in it.

I did. Nothing seemed to change. None of the built-in layouts seem to do anything. With LineageOS 17.1 and physical keyboard set to US Intl., I can use Sym + ' and then e to get é. Or Sym + " and then a to get ä. No root here.

Did you try LineageOS with its US Intl. setting for the physical keyboard?

Oh, I see! Interesting! It could be then, of course, that Fxtec would already sell their replacements "pre-flashed"... But still I don't think they'd intentionally try to make things difficult for those of us who want to replace only the panel itself. It would go against their self-repairability promises with which they started out. Also, it seems they're out of display replacements themselves, as on IndieGogo these are not expected to become available before August...

If I understood all the past information correctly, Fxtec is in fact supportive of repairs with those cheap parts. Also, I believe their own screen replacements (the added value of which is the easier replacement as they include the screen casing with all that's inside) needed the changed driver, too, from some point in time onwards, and someone who's using LineageOS, which Fxtec also officially supports, would need the driver package, too, even if they got the screen replacement from Fxtec...

From what I've heard in the meantime, there must have been some confidentiality restriction on those files, whatever the reason for that may be. Perhaps EvilDragon has become aware of that, too, and maybe that's why he doesn't react on further requests here, either. If communicating with Fxtec would work as we would like it to work, we could get into a discussion with them about it, but as it doesn't, I wouldn't get my hopes up. Still it wouldn't hurt to try...

I'm in not quite the same but remotely similar kind of a situation, with a device I got second-hand that had already been flashed with LineageOS, but without root, and sooner or later I'm going to want Magisk and hide-root and Xposed to pass SafetyNet and enable Google Pay and the security token app for my employer's VPN. From what I've read, I'd say we need forget about TWRP for the time being, though, because there's no official version yet that would handle decryption, so it's no use for backups. Also, I don't know whether someone is working on getting such a fully-functional TWRP for

Thanks @all for the tips regarding protection. I've already ordered screen protectors. I already do have two flip cases which basically fit, but I'm hesitant to use one because of the need to customize the holes and also they significantly add bulk, much more than the flipcase I used to have for the Moto Z3 Play which fit like a (surgeon's) glove... But I guess I'll give one of them a try, after all. (I've also been playing with the thought of buying a 3D printer just to print my own Pro1 protectors 😉 )

I did so, but @EvilDragon currently doesn't seem to be reachable through forum messaging (or maybe I'm too impatient)... Is there perhaps someone else with the file(s) (and the description)? I dropped the phone again today and now the display has a slightly splintered corner... I'll definitely need to get some protection for the phone, going forward... And I wouldn't want to replace the screen before making sure I can still use all of my apps...

Would it perhaps make sense for @tdm to include that in LineageOS and AICP, too? If it doesn't break something with older displays, that is...

For anyone who might be interested in a Pro1 but finding @Devion's offer too cheap, there's one of three Pro1s left someone from Japan is selling on ebay for $1,450 / EUR 1,232 ... 😉

Same here by OTA...

Just on a side note, it may or may not have anything to do with this – I have experienced anomalous behaviour with my Moto Z3 Play a few times which seemed to relate to either SIM card or SD card not being properly (physically) connected. Removing and reinserting the card tray and rebooting usually returned things to normal. This came to my mind now as I remembered the Pro1's card tray to be quite flimsy (not that other phones' card trays would always be more sturdy).

I'm usually not one to abuse my gear, but the last twelve months or so were particularly unlucky ones with regard to screens! Last year I bought a new TV (thankfully a cheap one, less than half of the regular Pro1 price...) and I destroyed the panel on the day it had been delivered, in the act of mounting the set on the wall... At least I learned tow things that day! One, modern TV panels are extremely delicate, and two, contrary to phones, modern TVs can only be disposed of once the panel is damaged. In relation to the panel there's nothing else of value in them...

A black spot of 3mm diameter, after dropping the phone, hitting a wooden floor hard with the display facing downwards. Doesn't make the phone unusable, but at some point I'll want to replace the screen. Already bought two replacement screens, one for spares... Good question.

I'm about to replace my screen as well and I have asked for the APK, too. I just need to make sure before I start that rooting the phone (running on unrooted LineageOS 17.1) doesn't break anything for me...

Hmmm... But you do get that extremely loud in-call audio anyway?

I'm on LineageOS 17.1. Changed title and first post accordingly... Sorry for not mentioning it. My partner's Fairphone 3 (stock Android 10), same carrier as me, doesn't seem to have the setting, either.

Excellent!

Looks like the suspicion I wrote about earlier was correct. Since I disabled "4G calling" (HD voice aka wideband audio) in "Network and Internet" -> "Mobile Network", I didn't get any calls anymore with too loud in-call audio. I'm quite confident about this now as one specific caller which always used to be too loud when calling from his home line wasn't too loud anymore after I made that change. So far I don't see any disadvantages of that change, either. [Edit:] This is LineageOS 17.1. Sorry I didn't mention this earlier...

Same here with OTA. (On a side note, I sometimes see your sideload success report before my phone would report availability of an OTA update; in that case the update will always appear immediately after a manual re-check, though.)

@fxtec-preorder-47xx After I got my Pro1 just a few weeks ago, I thought I'd be guarding it as the apple of my eye. Unfortunately I couldn't find any of those nice, thin cases yet which really would fit (like this one that I had been using with the Moto Z3 Play). Recently, now, the phone slipped through my fingers and landed on the wooden floor, screen facing down – no marks on the outside, it is really durable. But a black spot in the display. (I've asked support about the availability of spare screens and have yet to receive a reply, but I suppose I'll need to go with one of those Elephone U

Once, and I think really only once, there used to be a phone, that could be inserted into a bigger (dumb) screen that made it a tablet, which again could be mounted to a (dumb) keyboard, which made it a laptop – everything powered by the phone. I can't remember the manufacturer, though – Acer? Asus? For everything with less integration I'd actually prefer using separate components, too.

Haha, no, I hadn't 😄 Ok, for me, on LineageOS 17.1 the camera button works for both starting the camera and for shooting, including AF on half-press!

On my phone with LineageOS 17.1, the camera button doesn't open any camera app, but does work for shooting (including autofocus on half-press). [Edit: see here!] That said, I can open the camera app (my preferred one) by double-tapping the on/off button, so I'm not missing much there.