[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Commits from other roms?

(Honestly, this is nothing important to me and I won't spend hours on that. If you can link to a patchset I'll have a look, and if the patchset proofs to run stable I'll ship it. Otherwise I put it on my "boared to death"-todo-list directly behind clock customization. Meaning: if there is a day, when I got enough sleep, have nothing else to do and being really board, I start searching... propably: never.)

I'm not using Trebuchet but nova, but I think that's the intended Trebuchet behavior on large screens. (BTW: I like it - my personl preference, YMMV)

I always thought (regarding to https://developer.android.com/guide/practices/screens_support.html) neither our screen size is normal (~3" to ~4.5"), nor our density is xxhdpi (~480 dpi).

This works (mostly), because if we make our screen smaller the elements become (physically) larger. Setting the density to a higher value (here: xxhdpi instead of xhdpi) makes the elements (physically) smaller.

Since we have no accurate density configs (one for 400 ppi, one for 401 ppi, one for 402 ppi and so on), but groups (in this context: ranges), there is this wonderfull concept of dp (virtual, screen independent pixels) to adjust to the given real screen.

Based on this, I reworked the AAPT config. Your observation with Trebuchet seems to proof, I'm not completely on the wrong lane. Perhaps we need to tune lcd_density (that's the dp value; imagine this as scaling factor for displayed elements: the greater the value, the greater the elements): it's currently 420, but perhaps we need 440 - feel free to test.

If you want to test and compare, always set font size and display size to default, no matter what you want to set later as daily setting: if you change the AAPT conf, the value for "larger" or "smaller" changes, too: if we have a default of xhdpi, smaller is xxhdpi and larger is hdpi. If we use xxhdpi as default (pref config), smaller is xxxhdpi, larger is xhdpi... So you can't compare "larger" on los config with "larger" on the new AAPT config.

I you think this is complecated: perhaps it is. I've read the linked docu 20 times or so. What really helps to leave the state of confusion, is always keep in mind what unit you deal with (always clearly seperate ppi, dpi and dp), and get an imagination of the relationship of the values regarding physically displayed elements (is it directly proportional or indirect proportional).

I'll push a build today with these AAPT commit in place. Sadly I can't add an other poll, so I hope there will be enough feedback to make an educated decission, if most users prefer the los config or the new one.

[MENTION=4379461]UnbracedTundra[/MENTION]:

Just a word of warning: if you boot the next build for the first time, do NOT be shocked! logo.bin (LOGO) partition has changed with ob15 to a grayish background - and much worse: the position of the oneplus logo has changed... I have to check this (was busy getting ob15 blobs up and ****ing with AAPT). Either we can use the old logo.bin, or - I would prefer that - I can get the structure of logo.bin and we make our own (because the new logo's bg looks like **** compared to a black bg.

As stated: don't be shocked or annoyed, I'm thinking on this. We should also look at the new (ob15) bootanimation, because perhaps we can get a glimpse on how the animation is moved from the center of the screen to the top.

EDIT: [MENTION=7030109]mcdachpappe[/MENTION]: Thank you very much for building!