SF: fixing estimatedDpi checking x twice
This was caught after the change was merged. In practice it is unlikely
that y would be -1 with x not also being -1, but code shouls still be
correct.
Flag: com.android.graphics.surfaceflinger.flags.correct_dpi_with_display_size
Bug: 361413340
Test: HWComposerTest
Change-Id: I8ed47e73239c3d1cbeca8f093644d852cfb04011
diff --git a/services/surfaceflinger/DisplayHardware/HWComposer.cpp b/services/surfaceflinger/DisplayHardware/HWComposer.cpp
index bd093f5..d08e261 100644
--- a/services/surfaceflinger/DisplayHardware/HWComposer.cpp
+++ b/services/surfaceflinger/DisplayHardware/HWComposer.cpp
@@ -305,7 +305,7 @@
// The logic here checks if hwc was able to provide some dpi, and if so if the dpi
// disparity between the axes is more reasonable than a rough estimate, otherwise use
// the estimated dpi as a corrected value.
- if (estimatedDpi.x == -1 || estimatedDpi.x == -1) {
+ if (estimatedDpi.x == -1 || estimatedDpi.y == -1) {
return dpi;
}
if (dpi.x == -1 || dpi.y == -1) {