+43
−0
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
The current implementation failed to capture a specific scenario: device state change -> >1500ms -> setting change -> device state change. This sequence is valid and should be logged. Ensure only the first change's timestamp is reset. This allows subsequent changes to be accurately assessed for potential issues, as their timestamps are retained. Bug: 402764691 Test: atest DeviceStateAutoRotateSettingIssueLoggerTests Flag: com.android.window.flags.enable_device_state_auto_rotate_setting_logging Change-Id: I32f8a53c0ab80cc96b29a65cfa18e34b0e2d87dc