EskeRahn

It looks like the one @tdm made, but it seems to be without the qwertZ support...

I do not know if you NEED it, but it looks substantially different, so I would suggest so, unless someone can say explicitely that they know you do not need it.

Done, went super smooth and fast 🙂 IF we got mindthegapps while on 16.0 It seems to be important instead to install opengapps during in the 17.1 process. (That is as Mindthegapps in this version is not supported on 17.1, we can not leave it there, but have to have opengapps replacing it - as @Wheeljack did above too )

I waited about half an hour or so... After a wipe it booted quickly. Will try the Pre-production unit too without the wipe, as this got qwertY. Do we need to remove the mindthegapps while still on 16.0 before the upgrade? Or should installing opengapps in the 17.1 process fix it?

Accepting a factory reset, things seems to work, except the keyboard.... Currently useless EDIT: FinQWERTY can make it working on qwertZ too, for the supported layouts. At the least to some degree. Some symbols like @ is inaccessible, unless you use the fake keyboard OR make a language swap with Ctrl+Space to a language supporting @, and then back.

I am loosing mine, but this is a test device. Others will have to answer if there is a way to keep stuff.... Non-destructive, see below

I was super optimistic and downloaded the two 17.1 files, flashed the loader as usual and sideloaded the zip, over the 16.0 with mindthegapps. WITHOUT wiping anything. And well the flashing went smoothly, but it did not work.... It seems 'stuck' at the loader screen. I do see the circle move over the blue sad mouth, but it does not seem to move forward from that.... So will repeat the same with a wipe.... (and opengaps - thanks @_DW_ )

A question for @tdm Is this the right one to download?

Thanks for the warning @acrux for now I'm trying to download, but I guess I'm not alone, as it takes 'forever'.,,

As suggested... And with a qquote from the original post of that thread: You can find the builds and installation instructions on the official LineageOS Downloads page

Though I like the boundaries, I bet they will be hard to get legible on such small keys, so I bet some exaggeration will be needed compared to the suggestions. Wider lines and wider space, that is a more 'fat' symbol. But the principle is great IMHO. Look at how they did the Tab & BackTab on the qwertZ variant. 🙂

....and ⤒, ⤓ too. The second would be natural for the seldom used VT (Vertical Tab). I have never seen Back-VT though, but for consistency, I would remove that one as well. (also close to the symbol often seen for caps)

I like your ideas, though one symbol is already used for backward jump to tab-stop (Shift+Tab) ⇤ I really like the principal idea of e.g. ⇱indicating a jump to a boundary, and not just an indication of something in a direction

I took the liberty to split this away from the LineageOS thread, as it is hardware-related.

Well it is more like a setting we do not want/like than something strictly wrong. But indeed would be nice with an easy way to change the setting to what we prefer, and the 7-8mm you describe sounds a bit much for my taste too.

I know they changed 'something' at a deep level to add a small margin at a very early stage, so I guess what you describe is that newer displays comes with a much wider default tap-insensitive edge (that still allows sliding so not touch insensitive). I have no idea if this can be changed without wiping everything. But as it seems to follow the hardware I guess it ought to be possible - though I got no idea on the how we can flash individual hardware components.

Is this not a deliberate fix for people to avoid unwanted edge interaction? If I do not remember wrong the lineage implementation have a setting for the size of this.... Settings►System►Advanced►Touchscreen►Margin

Sad that you do not want to use it. But feel free to add an ebay link. Others have done so previously,

Yes, it seems to be used for noise handling only, not stereo.

Same situation in Denmark. At the least with "Oister".

I guess you mean the 17.1 LOS, and well the source should be, but the automatic builds seems to fail, so not available directly

Yes, it does indeed seem to have been in a limbo for the last few weeks. I guess they were a little hasty stopping the 16.0 builds

Thanks for the idea, No I have not tried those, as default works on others. But especially the one saving the intermediates might be useful in debugging, as I then can see exactly what the ISO of each is reported, and see what happens if Brightening/Darkening the images to the same level and then see if they have similar brightness.

As the dog exists nu more, I just recreated a similar scene with a box and a sheep skin of similar whitish colour, and made a small collage. Note that the halo is most pronounced if you do not photo in the same direction as the light. The last of the four looks almost decent, where you can misinterpret the halo as a shade.

I'm not a big fan of HDR either, but as the dynamic range of digital image sensors are poor compared to real film (and most image formats and monitors are too), some motives leaves no alternatives. This dog grew up with a black German sheppherd. And getting a decent digital photo of the two was REALLY hard, and here HDR came to our help, compressing the dynamics. But though HDR certainly is not objectively accurate, it could be argued that it is subjectively more accurate, as it is closer to how we as humans experience a whole mixed scene.