The root cause of the oversized/clipped UI is TvFrameworkOverlay's
config_maxUiWidth=1280 in the values-tvdpi resource bucket. With
PRODUCT_AAPT_PREF_CONFIG=tvdpi, the device resolves this bucket and
the 1280px cap is enforced, limiting the logical display to 1280x720
(which SurfaceFlinger then upscales to 1920x1080).
The Raspberry Pi 5 ATV build (KonstaKANG) uses PRODUCT_AAPT_PREF_CONFIG=xhdpi
and has no display sizing issues, because values-xhdpi has
config_maxUiWidth=1920 (no effective cap on 1080p displays).
Also adds a values-xhdpi/config.xml overlay with config_maxUiWidth=0 as
defense-in-depth, matching the existing values-tvdpi override.
Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
Create aosp_tart.mk as the AOSP base product config (like
aosp_oriole.mk), inherited by lineage_tart.mk (like
lineage_oriole.mk). This matches the standard LineageOS
device tree convention.
Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
- Rename product makefile: lineage_tart.mk (PRODUCT_NAME=lineage_tart)
- Update AndroidProducts.mk for lineage_tart lunch target
- Change androidboot.hardware and TARGET_BOOTLOADER_BOARD_NAME to tart
- Rename ramdisk files: fstab.tart, init.tart.rc, ueventd.tart.rc
- Update device.mk ramdisk copy targets for tart names
- Update vendor makefile reference to tart-vendor.mk
- Update extlinux.conf kernel cmdline with tart hardware ID
- Fix bluetooth device name in vendor.prop
Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
