Assigned
Status Update
No update yet.
Comments
ra...@google.com
Information redacted by Android Beta Feedback.
ra...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
st...@telechips.com
HI,
Attached is a screenshot of the error message.
I get this message everytime I try to tap and pay.
I am guessing that it's because you have released the stable Android 15
QPR2 and I am stuck on the beta verson.
On Thu, 6 Mar 2025 at 09:22, <buganizer-system@google.com> wrote:
Attached is a screenshot of the error message.
I get this message everytime I try to tap and pay.
I am guessing that it's because you have released the stable Android 15
QPR2 and I am stuck on the beta verson.
On Thu, 6 Mar 2025 at 09:22, <buganizer-system@google.com> wrote:
Description
In this test case, the function presentAndGetFence is used to request Validate & Present operations for the test layer to HWC. During this process, the test layer is passed to HWC with a Composition Type of Device, and a Present request is issued immediately after the Validate operation.
I have some questions and concerns about this behavior:
In the actual operation of SurfaceFlinger, the process involves requesting Validate for the layers to be composed. If the Composition Type is changed during validation, acceptDisplayChange is performed before executing Present.
In our current implementation and operation of HWC, layers passed from SurfaceFlinger are processed as Client Type if they fail to meet certain conditions. As a result, the test case fails during presentDisplay due to the absence of an accept operation caused by the change in Composition Type, and the ClientTarget Buffer is not provided.
Here are my specific questions:
1. Why does this VTS test case prohibit changes to the Composition Type of the test layer provided?
1-1. Can the VTS test case be modified to allow Client Composition resulting from changes in Composition Type?
2.In scenarios where a Vendor Composer processes layers as Device Type only under specific conditions and treats others as Client Type, is it mandatory for HWC to strictly adhere to the Composition Type provided by SurfaceFlinger?
I would greatly appreciate any clarification or guidance you can provide regarding these questions. Your insights will help ensure that our HWC implementation aligns with the expected behaviors and standards.
Thank you for your time and assistance.
Best regards,
Steve.kim