Topics

So because of the other issues this is "appropriate"? No. This defect is inappropriate on an $800+ device. I would still want a replacement even it this was the only issue. Maybe you understand that the screen is the thing you focus on while using the device. So yeah... I am focused on it, in addition to the countless other issues... That would be even worse as the rounds are already cutting off text in the terminal, and also cuts part of the AM/PM in the status bar time. Rounded corners are bad design in the first place, the solution is not to cut off even more pixels and further reduce real-estate. They should have chosen with a regular flat rectangle screen with no curves or rounds...

Academically speaking yes it is... But just imagine that fxtec had pre-installed an app giving more rounded corners (maybe hard-coded). Then you would have never noticed that the display-defect existed - but sure it would still be there in principle. If the Pro1/Pro1X were otherwise close to flawless perfection, I could understand the focus on this. But as there are so many different more serious issues I think the wording of @Rob. S. "it's a minor cosmetic blemish," is quite appropriate for this one. ADD: Being polemic one could say that it is a question of poor QC. IF they had noticed this as a frequent issue, they could have hid the issue from us with deliberately disabled black corners.

Well, we COULD hope that the camera module in this - or a later version - is not fixed, so we can have a keyboard back-module, at the cost of an inferior camera

Lineage-21-20240909-NIGHTLY-pro1x with September 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained. 

I'm on linux. I can make a full reset factory with QDL, but I would instead fix the boot issue I have.   I've been able to reach the internal data with the droidian recovery installed on the slot B (I hope this doesn't mess more with the SFOS boot process), but there isn't really any log about the SFOS boot process, I can't get why my phone is stuck during at the initial security code input screen. What could prevent the OS to boot ?