Obsolete
Status Update
Comments
am...@google.com <am...@google.com>
am...@google.com <am...@google.com> #2
Thank you for the suggestion. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
ar...@google.com <ar...@google.com> #3
We've deferred this issue for consideration in a future release. Thank you for your time to make Android better. In case you want to provide more information with respect to this bug, please file a bug in AOSP via "https://goo.gl/TbMiIO
sa...@google.com <sa...@google.com> #4
Thank you for your feedback. We will be closing the issue as “won't fix - obsolete”. If this issue is still reproducible, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.
Description
Not applicable.
* Is this a regression from P to Q?
Not applicable.
* What device are you using? (for example, Pixel XL)
Not applicable.
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Visit
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Documentation
* What was the expected result?
For that section to cover all seven roles.
* Can you provide the API document where this expected behavior is explained?
* What was the actual result?
Visit