[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No problem, dude. Now we are watching the same movie. I think you are right, somethings wrong with our dimens, but i still belive it's an issue with AAPT. And talking of confusion, I'm not the only one being confused on AAPT config:

ingo@adler /usr/local/src/cm14 $ grep AAPT $(find device -name \*\\.mk)
device/generic/armv7-a-neon/mini_common.mk:PRODUCT_AAPT_CONFIG := normal ldpi mdpi hdpi xhdpi xxhdpi
device/generic/armv7-a-neon/mini_common.mk:PRODUCT_AAPT_PREF_CONFIG := hdpi
device/xiaomi/msm8996-common/doze/Android.mk:LOCAL_AAPT_FLAGS := --auto-add-overlay \
device/xiaomi/msm8996-common/configpanel/Android.mk:LOCAL_AAPT_FLAGS := \
device/xiaomi/msm8996-common/msm8996.mk:PRODUCT_AAPT_CONFIG := normal
device/xiaomi/msm8996-common/msm8996.mk:PRODUCT_AAPT_PREF_CONFIG := xxhdpi
device/samsung/chagallwifi/device.mk:PRODUCT_AAPT_CONFIG := xlarge
device/samsung/chagallwifi/device.mk:PRODUCT_AAPT_PREF_CONFIG := xhdpi
device/samsung/chagallwifi/device.mk:PRODUCT_AAPT_PREBUILT_DPI := hdpi mdpi xxhdpi xxxhdpi ldpi
device/samsung/chagallwifi/validityservice/Android.mk:LOCAL_AAPT_FLAGS := --auto-add-overlay
device/samsung/exynos5420-common/SamsungDoze/Android.mk:LOCAL_AAPT_FLAGS := --auto-add-overlay \
device/samsung/manta/device.mk:PRODUCT_AAPT_CONFIG := xlarge
device/samsung/manta/device.mk:PRODUCT_AAPT_PREF_CONFIG := xhdpi
device/samsung/manta/device.mk:PRODUCT_AAPT_PREBUILT_DPI := hdpi mdpi
device/oneplus/oneplus3t/doze/Android.mk:LOCAL_AAPT_FLAGS := --auto-add-overlay \
device/oneplus/oneplus3t/device.mk:PRODUCT_AAPT_CONFIG := normal
device/oneplus/oneplus3t/device.mk:PRODUCT_AAPT_PREF_CONFIG := xxhdpi
device/oneplus/bacon/bacon.mk:PRODUCT_AAPT_CONFIG := normal
device/oneplus/bacon/bacon.mk:PRODUCT_AAPT_PREF_CONFIG := xxhdpi
device/oppo/common/configpanel/Android.mk:LOCAL_AAPT_FLAGS := --auto-add-overlay
device/google/marlin/device-sailfish.mk:PRODUCT_AAPT_CONFIG := normal
device/google/marlin/device-sailfish.mk:PRODUCT_AAPT_PREF_CONFIG := xxhdpi
device/google/marlin/device-sailfish.mk:PRODUCT_AAPT_PREBUILT_DPI := xxhdpi xhdpi hdpi
device/google/marlin/device-marlin.mk:PRODUCT_AAPT_CONFIG := normal
device/google/marlin/device-marlin.mk:PRODUCT_AAPT_PREF_CONFIG := 560dpi
device/google/marlin/device-marlin.mk:PRODUCT_AAPT_PREBUILT_DPI := xxxhdpi xxhdpi xhdpi hdpi
device/google/marlin/device-common.mk:PRODUCT_AAPT_CONFIG += xlarge large
device/google/atv/products/atv_generic.mk:PRODUCT_AAPT_CONFIG := normal large xlarge tvdpi hdpi xhdpi xxhdpi
device/google/atv/products/atv_generic.mk:PRODUCT_AAPT_PREF_CONFIG := xhdpi
device/google/atv/products/sdk_atv_armv7.mk:PRODUCT_AAPT_CONFIG := normal large xlarge tvdpi hdpi xhdpi xxhdpi
ingo@adler /usr/local/src/cm14 $

In oneplus open source sofware it is like this:

PRODUCT_AAPT_CONFIG += normal large xlarge
PRODUCT_AAPT_CONFIG += hdpi mdpi

As I understand the google documentation only chgallwifi's and manta's AAPT config makes sense to me. From my understanding, op3/t (and bacon for this matter) have a "large" screen.

If you look at sailfish (Pixel with 4k) "large" and "xlarge" are added via the common make file. Even this is more plausible then "normal" (which is the only value we have in our config).

I have to rethink the complete AAPT config before putting out a testbuild. ATM I think this could be the config:

PRODUCT_AAPT_CONFIG := large normal xlarge
PRODUCT_AAPT_PREF_CONFIG := xhdpi #or xxhdpi or hdpi; testing needed
PRODUCT_AAPT_PREBUILT_DPI := xhdpi xxhdpi hdpi mdpi

Since I want to do a "long term test" (3 days, at least 2 charging cycles), because it makes me feel noob not knowing what sot I have, or if the rom is running stable for more then 24h (I think the longest time I've used the same build was 30 h, when testing my first - and never publishef - aes build), it would be great if you (and anybody else for that matter) are willing to test. I put out a build later this night or tomorrow.