Brendan Szymanski
04e94e9938
The config_maxUiWidth=0 override never took effect from /vendor/overlay: static RRO precedence is decided by partition order before priority, so the product-partition TvFrameworkOverlay (1920) always won and silently re-capped the UI to 1920x1080 on 4K displays. Moving our overlay to the product partition lets its priority 10 beat TvFrameworkOverlay's 0, so the cap is disabled and the UI renders at the display's native resolution. Users can select a lower mode in Settings if needed.
17 lines
754 B
Text
17 lines
754 B
Text
// Copyright (C) 2021-2022 KonstaKANG
|
|
// Copyright (C) 2025 Venkata Atchuta Bheemeswara Sarma Darbha
|
|
//
|
|
// SPDX-License-Identifier: Apache-2.0
|
|
|
|
// This overlay MUST live on the product partition: it overrides resources that
|
|
// TvFrameworkOverlay (a product-partition RRO from device/google/atv) also
|
|
// overrides, and static RRO precedence is decided by partition order first
|
|
// (system < vendor < odm < oem < product < system_ext) and android:priority
|
|
// second. From /vendor/overlay our entries always lose to TvFrameworkOverlay
|
|
// regardless of priority; on /product our priority 10 beats its priority 0.
|
|
runtime_resource_overlay {
|
|
name: "AndroidTvOpiOverlay",
|
|
resource_dirs: ["res"],
|
|
sdk_version: "current",
|
|
product_specific: true,
|
|
}
|