Using MediaProjection with the MediaCodec API and setting KEY_REPEAT_PREVIOUS_FRAME_AFTER does not work as expected [171023079]

WAI

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ni...@legacy.loom.com

created issue #1

Oct 16, 2020 09:42PM

Sample app to reproduce: https://drive.google.com/file/d/1mZEav6OOhH3bRriyPtyVd9ucIqB43-at/view?usp=sharing shared with android-bugreport@google.com

Steps to reproduce:

Build and run application
Toggle button to start recording and grant screen capture permission
Observe logs (specifically ISSUETRACKIGNSAMPLE: H264 frame received, pts (seconds) = $pts.

Expected output:

When nothing has changed on the screen, we expect to see 30 log lines per second (given a frame rate of 30) demonstrating that 30 new frames were generated per second.

Current output:

When nothing has changed on the screen, no new frames are generated until something changes on screen.

We have set KEY_REPEAT_PREVIOUS_FRAME_AFTER when configuring the MediaCodec with the expectation that when there is no change, "the frame previously submitted to the encoder will be repeated if no new frame became available since."

Comments

ja...@google.com <ja...@google.com> #2Oct 16, 2020 09:57PM

Assigned to ja...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

ni...@legacy.loom.com <ni...@legacy.loom.com> #3Oct 16, 2020 10:36PM

Please find here the demonstration video:

https://drive.google.com/open?id=15PEkr6H-LZehyGfNaq2iiLC317wpOSIJ
Bugreport:

https://drive.google.com/open?id=1dwg-VMhIsLxTFnkCd4A-OLQPEaknj9ld

I am working on creating test account that you can use to reproduce the problem.

Thanks.

ja...@google.com <ja...@google.com> #4Oct 19, 2020 03:30PM

I created a test account that you can use. These are the steps.

1. Please install Mobile@Work from Google Play.
2. To register please launch it and tap on "Or register with server URL"
3. Enter

eapp069.auto.mobileiron.com as server URL.
4. On next screen enter user name test and password Qwerty12
5. Go though provisioning, acquiring Device Admin, grant or deny location permission.
6. Certificate provisioning will start and you will see the issue.

ja...@google.com <ja...@google.com> #5Oct 20, 2020 10:06PM

Status: Won't Fix (Intended Behavior)

Sorry for late reply. If you are still facing this issue with latest Android 11 beta then please share video & bug report.
Links in

comment #3

& credentials in

comment #4

are not working.

ja...@google.com <ja...@google.com> #6Oct 20, 2020 10:27PM

FYI, MDM apps should use DevicePolicyManager.installCaCertificate rather than prompt the user for installation.

ni...@legacy.loom.com <ni...@legacy.loom.com> #7Oct 21, 2020 04:51AM

Please provide the information requested in

comment #5

ja...@google.com <ja...@google.com> Oct 21, 2020 04:26PM

Status: Assigned (reopened)

ja...@google.com <ja...@google.com> #8Nov 23, 2020 09:57PM