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
I've been having a weird issue with Phone by Google that I think might be related to Holey Light.
Phone: Samsung Galaxy S22, Android 12, One UI 4.1
Holey Light v1.00, AOD Helper w/ Automatic AOD Control
Hide AOD: Partial
Phone By Google: 76.0.431816759
If I put the phone up to my ear, the proximity sensor turns the screen off. If I then pull the phone away from my ear, the screen turns back on, but only the very bottom section with the nav bar and a small chunk of screen where the AOD charging indicator normally is. If I click the power button to turn the screen off and then on again, the full screen comes back. I believe the proximity sensor on/off during a call is somehow interfering with either the AOD Helper or just the Hide AOD: Partial setting and causing it to try and hide the AOD when the proximity sensor re-enables the screen during a call.
The text was updated successfully, but these errors were encountered:
I've been having a weird issue with Phone by Google that I think might be related to Holey Light.
Phone: Samsung Galaxy S22, Android 12, One UI 4.1
Holey Light v1.00, AOD Helper w/ Automatic AOD Control
Hide AOD: Partial
Phone By Google: 76.0.431816759
If I put the phone up to my ear, the proximity sensor turns the screen off. If I then pull the phone away from my ear, the screen turns back on, but only the very bottom section with the nav bar and a small chunk of screen where the AOD charging indicator normally is. If I click the power button to turn the screen off and then on again, the full screen comes back. I believe the proximity sensor on/off during a call is somehow interfering with either the AOD Helper or just the Hide AOD: Partial setting and causing it to try and hide the AOD when the proximity sensor re-enables the screen during a call.
The text was updated successfully, but these errors were encountered: