Fixed
Status Update
Comments
al...@google.com <al...@google.com> #3
Please support API for 3rd party apps. I have an app Screen Recorder on Play store but every day I received too much questions about internal sound for game. If you support then users will have experience better when they share content to friends or YouTube.
Thanks!
Thanks!
ap...@google.com <ap...@google.com> #4
Hope the internal sound API for better screen recorder APP
al...@google.com <al...@google.com> #5
Please support API record internal sound for 3rd party apps.
ia...@gmail.com <ia...@gmail.com> #6
Please support All Android API To Record Internal sounds with all screen Recorder. I need to record my GD Gameplays please ;-;
al...@google.com <al...@google.com> #7
My internal sound not properly record
My android version 9 pie my phone is Nokia 6.1 plus
Iam using the screen recorder pls allow permission
Pls allow permission
Help me !
My android version 9 pie my phone is Nokia 6.1 plus
Iam using the screen recorder pls allow permission
Pls allow permission
Help me !
al...@google.com <al...@google.com>
al...@google.com <al...@google.com> #8
i hope API internal audio screen recorder is support 🙏
ia...@gmail.com <ia...@gmail.com> #9
Yes,pls bring internal audio screen recorder .
Description
Component used: Wear-Watchface
Version used: 1.2.0-alpha08 or higher
After upgrading to Wear Watchface 1.2.0-alpha08 or higher, I noticed an error in Android Studio on both the
WatchFaceType
andCanvasType
integers that they should only be used within the androidx.wear.watchface library:It appears this is an unintended side effect of this CL that marked those annotation classes as
@RestrictTo(RestrictTo.Scope.LIBRARY)
.Would it be possible to separate the constants (which really could just be on a regular Kotlin
object
, rather than as part of acompanion object
of a restricted class) from the restricted annotation class (which it doesn't matter what the class name of that annotation actually is)?It is really annoying to have the red underlines in Android Studio and associated lint failures.
FWIW, I noticed that this does not apply to constants such as
WatchFaceStyle.PROTECT_STATUS_BAR
, but only to constants within apublic annotation class
that is restricted.From this search , it appears this issue affects:
WatchFaceType
constantsCanvasType
constantsTapType
constantsComplicationsSlotBoundsType
constants