Archfx/duo-de

Ambient light sensor from left side screen is never used

Sidefix opened this issue · 6 comments

Acknowledgements

  • I have chosen an appropriate title.
  • 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 1
  • GSI version: v2024.07.25
  • Vendor version:

Expected Behavior

Both sensors should be used depending on posture. For example, when the first screen is exclusively used, only the sensor on its side should be used.

Current Behavior

Regardless of whether the left, right or both screens are used, only the ambient light sensor on the right is used.
Demo:

20240812_144250.mp4

Possible Solution

none identified

Steps to Reproduce

  1. Fold the device to use the left screen
  2. Block the ambient light sensor from the right screen

Logs

No response

Additional context

I know the sensor is functional since it worked fine with vanilla 12L

This is an unhandled scenario in the PostureProcesor, thanks for finding it.

Could you please manually flash the testing version (after unzipping) and put the log file here!! Steps are follows,

adb reboot fastboot
fastboot flash system aosp-arm64-ab-gapps-14.0-<<version>>.img
fastboot reboot 

Once the device is booted, use the following command to initiate the log process.

adb -d logcat | grep POSTURE > log.txt

Repeat the steps to use the left side screen mode (Tent Left and Left Phone mode), repeat it for couple of times and do a "ctrl + X" to exit the log process. Include the log file.

Thanks, Let me know

I'll need some time for this, please bear with me.

You are good, I obtained the log, fix is not complete yet

This issue is stale because it has been open for 30 days with no activity.

This issue was closed because it has been inactive for 7 days since being marked as stale.