You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All requested information has been provided properly.
This is not a feature request.
This issue is not a duplicate of an existing issue.
The issue is solely related to this GSI.
This issue occurs with the latest available build.
I am not running a custom vendor on my device.
This issue is not kernel related.
This issue is not related to Magisk/KernelSU/APatch.
Info
Device: Surface Duo 2
GSI version: 2024.12.23
Vendor version:
Expected Behavior
When the device posture is within the peak mode trigger, it should display the overlay over either screen.
Current Behavior
Putting the device in peak mode disables one of the screens, and does nothing for the other active screen. Happens on both rotations. ( Aka if right side is on left is off, vice versa)
The overlay never shows.
Possible Solution
The overlay was working before. I think this is related to the optimisations previously in the posture processor that tries to reduce the references to left and right to a singular screen view.
Steps to Reproduce
Put phone in peak mode
Issue occurs (one screen on, no overlay)
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Acknowledgements
Info
Expected Behavior
When the device posture is within the peak mode trigger, it should display the overlay over either screen.
Current Behavior
Putting the device in peak mode disables one of the screens, and does nothing for the other active screen. Happens on both rotations. ( Aka if right side is on left is off, vice versa)
The overlay never shows.
Possible Solution
The overlay was working before. I think this is related to the optimisations previously in the posture processor that tries to reduce the references to left and right to a singular screen view.
Steps to Reproduce
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: