1
0
Fork 0

Remove stale values-tvdpi overlay (redundant after xhdpi switch)

The display sizing fix now uses PRODUCT_AAPT_PREF_CONFIG=xhdpi, so the
device no longer resolves the tvdpi resource bucket. The values-tvdpi
override with config_maxUiWidth=0 is dead code. The values-xhdpi override
provides the same defense-in-depth in the currently-resolved bucket.

Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
This commit is contained in:
Brendan Szymanski 2026-07-14 12:31:39 -04:00
parent 6057c30431
commit 9e8d38a0c8

View file

@ -1,26 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<resources>
<!-- Override TvFrameworkOverlay's config_maxUiWidth=1280 in the values-tvdpi
bucket (which this device resolves via PRODUCT_AAPT_PREF_CONFIG=tvdpi).
At the same config-qualifier level, our RRO priority 10 beats their
priority 0, so 0 (disabled cap) wins over 1280. This lets the native
1920x1080 panel render at full resolution instead of being capped to
1280x720@320dpi and upscaled. -->
<integer name="config_maxUiWidth">0</integer>
</resources>