EskeRahn

Well yes and no. There ARE tempered glass protectors BUT I have only found flat ones, thus not fully covering.... What we would like would be similar to the ones for e.g. the BB Priv, or Samsung S8(+/-) & S9(+/-) that are flat in the long direction and curved in the short. (Technically MUCH simpler to make than doubled-curved ones)

That was my point. The more commonly used the tweaks you use are, the less likely they are to be affected by (minor) upgrades. But there still is a risk. And you certainly got a point on WinX being in "rolling release".

(lineage-18.1-20210412-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210328_143848 ) (Ctrl+Space still does not rotate between selected layouts, and expicitly selecting one only works for some layouts)

That the tweaks you are using have nor been affected, does not prove anything, sorry. What the developers might consider a small bugfix, might be just enough to affect a tweak. Obviously the risk is higher on a major update than a minor, and the more broadly used the tweak is, the more likely it is that their tests would have cought that a change had negative side effects I have seen more than once on Windows 10 that some tweak just stopped working with no warning after a minor update. So not limited to Android/LOS

As I saw it the point was that was that results are really hard to predict on any system, if you go to the 'edges', Most likely it is much easier to simply try it out, and fiddle until it works. So that would certainly need backups, as you might need to reset everything in the process. And even when things DO work, an upgrade may break it, as you walk on untested ice. I'm not saying that people should not tweak, But on the other hand, a robust result can hardly be expected, so the tweaks are likely to need adjustments from version to version. So a heavily tweaked system is not suitable as a st

No, it is the same BOE display unit so the protector will fit exactly as good/bad on one or the other.

Or perhaps "lack of interest" is too kind. "dis-interest" i guess would be more appropriate!

You could say that it is due to the fundamental lack of interest in users privacy at Google that it isn't....

I would prefer if it was settings the user could select/deselect (without the need of rooting and messing with system files)

On the OTA. AFAIK they still only do Total downloads, not deltas. The flip side of that is large packages has to be fetched, the positive side is that they do not need to push the same strict restrictions of a known position, as handling a delta parcel does.

Important point, thanks! We have had no information on wether all the Pro1X will be in one initial large batch, or spread out over some us unknown period. My personal guess would be that it will be spread out, and given the previous experiences over a not insubstantial period. (I'm guessing months rather than days)

Tried to extend the opengapps table with MindTheGapps: The last two I THINK could be included as obligatory in say "Google System Base" for OpenGapps. (I got them on AICP Q + OpenGapps 10 Pico also)

Note that one is a preorder, the other a indiegogo perk. That is the first is a conventional buy with the buyer rights that offer. The second is an investment without the same rights. Or said otherwise on the first FxTec have the risk, on the second you have. That is the reason for the pricedifference. But you should be able to cancel the preorder anytime, and take the IGG perk instead if you wish to - but you can not cancel a perk (except some days after picking it) I would suggest sending a mail to info@fxtec.com

We have the camera discussions in several other threads, not much point in repeating it here, just because I made a joke from a picture.... e.g. this is active:

The size (200M) seems pretty close to the opengapps nano, the pico is about half the size. I have not checked what is actually included. ADD When we find a list we can compare it with this ADD II, this is the APKs in the ZIP: product\app\GoogleCalendarSyncAdapter\GoogleCalendarSyncAdapter.apk product\app\GoogleContactsSyncAdapter\GoogleContactsSyncAdapter.apk product\app\GoogleTTS\GoogleTTS.apk product\app\MarkupGoogle\MarkupGoogle.apk product\app\PrebuiltExchange3Google\PrebuiltExchange3Google.apk product\app\talkback\talkback.apk product\priv-app\AndroidAutoStubPrebuilt\Android

Being a bit evil, following the link the second image seems to tell us that we would better ALSO have a real camera... 👼😈

I certainly hope he will 🙂 The issue as @claude0001 pointed out is that LOS is great when it stabilised, but pretty crazy that they immediately remove the older version as supported. A few months overlap - with security updates would be nice. Even what in the broad perspective can be seen as minor bugs, can be crucial for others, so some overlap where people can jump back waiting for a fix (even if it requires a wipe) would be nice. Or simply be hesitant in upgrading until those of us not dependant on it has stumbled on the bugs, and can report if&when they are fixed. I can fully u

I upgraded from @tdm's 16 to the official one without any real issues, and it also worked nicely 16->17, but the 18 seems to be a bit too rushed out - so we that upgraded are the April fools... And I even missed the first one, since I was away over eastern. If we look at the surprisingly short change list going from 17 to 18 https://download.lineageos.org/pro1/changes/ there is only a single one that is marked as specifically related to the Pro1. So not that surprising that things are not all working smoothly, 🤐 I have it on the preproduction unit only, that is not suitable as a da

(edited my post above, Some language-layouts are OK others not)

Just to be sure, did you rememeber to flash BOTH lineage AND (reflash) any gapps package you are using on the upgrade?

...As long as we avoid HDR mode, yes. Currently HDR works with the stock app, but not trough the api with other apps. Be aware that the HDR mode does not work as intended. It do take a high and low light image as it is supposed to, but some metadata handling in the Camera2 API interface must be wrong, so when the software tries to stitch the two together, we get odd shadow-results. e.g. OpenCamera HDR works just fine on a Samsung S8, so not the app that is wrong. it must be the returned images that does not match the requested shuttertime/ISO settings. And this obviously confuses the

My point was that the keyboard is no longer really usable with 18.1 it worked (with a few quirks) with 17.1. BUT exactly as they no longer support 17.1 I guess we could expect some of the fixes from 17.1 transferred over to 18.1

How odd, I will try to remove some of the things that might influence such as swiftkey, I do not personally use qwertZ, nor do the unit I use for Lineage have an unshifted keyboard. so it was just for test I tried to see if I could Germanise it.

Went from, lineage-17.1-20210329-nightly-pro1-signed.zip on March 5 security patch installed using adb sideload and opengapps pico 20210327 to lineage-18.1-20210405-nightly-pro1-signed.zip on March 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210328_143848 Note that it went (almost) smooth DESPITE the change from opengapps to mindthegapps 👍 (note there is a new 0405 18.1 build already) (Edited below) I have issues selecting anything but US hardware some build in layout for the keyboard though. So currently the keyboard on 18.1

The most protective -yet still usable- solution is a screen protector and a flip case.