Screen record is unable to capture audio [350946972]

Assigned

Bug

[AOSP] assigned

Status Update

No update yet.

Description

bo...@gmail.com

created issue #1

Jul 3, 2024 05:52PM

Android version: 14 (AP2A.240605.24)
Device: Pixel 6a, but reproducible on other devices

Using the device screen recorder app, I'm unable to capture audio from my app drumbox (

https://play.google.com/store/apps/details?id=nl.littlerobots.drummer) This appears to have started from Android 14.

I've checked the following things:

* Audio capture policy on the app manifest
* Audio capture policy on the created output stream (using oboe)
* Setting usage to "media"
* Setting privacy mode to "none"

Changing these flags do not change the ability for the screen recorder app to capture the audio from my app, whilst previous versions of Android are capable of capturing the audio.

To reproduce:

* Open the app and play a sequence
* Capture the screen using the system screen recorder app, either in "all apps" or "specific app" mode
* Observe that the captured recording only captured the screen, not the audio.

Comments

ra...@google.com <ra...@google.com> #2Jul 4, 2024 05:11AM

Assigned to ra...@google.com.

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

ai...@gmail.com <ai...@gmail.com> #3Jul 4, 2024 07:58AM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

bo...@gmail.com <bo...@gmail.com> #4Jul 4, 2024 08:29AM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

ra...@google.com <ra...@google.com> #5Jul 6, 2024 08:14AM

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

bo...@gmail.com <bo...@gmail.com> #6Jul 6, 2024 02:43PM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

an...@bandlab.com <an...@bandlab.com> #7Jul 8, 2024 01:43AM

Comment has been deleted.

Message last modified on Jul 8, 2024 01:43AM

ai...@gmail.com <ai...@gmail.com> #8Jul 8, 2024 07:45AM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

ra...@google.com <ra...@google.com> #9Jul 12, 2024 09:13AM

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.

ph...@google.com <ph...@google.com> #10Jul 15, 2024 09:45PM

As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!

ai...@gmail.com <ai...@gmail.com> #11Jul 16, 2024 02:55AM

@comment#9 The Play Store will eventually require targeting API 33, then 34, etc, so accepting this regression in a customer release would be a time ticking bomb for Wear OS apps.

Thank you for the update @comment#10