292a6a4e9934a94eea97b018befde3baed895f7d
AudioService keeps track of status of implementations of PlayerBase. AudioService's PlaybackActivityMonitor maintains a list of playback configurations for each PlayerBase, and a list of clients that want to receive updates about the playback. Playback activity clients can query the playback configuration of the system through AudioManager, or register a callback for updates. For clients with MODIFY_AUDIO_ROUTING permission (system), the playback configurations contain more information about each player (player type, uid, pid, state), and can see all players, not just the "active" ones. The act of stripping off data about the players that is not supposed to be seen by non-system clients, is referred to as "anonymization". It is implemented in system server, so no system data is ever sent to playback activity clients without system permission. More information about the AudioPlaybackConfiguration is available in the SystemApi (uid, pid, player type, player state). Test: run cts -m CtsMediaTestCases -t android.media.cts.AudioPlaybackConfigurationTest Bug: 30955183 Change-Id: I85997594c0378216419f5f0fdaa0714996fd3573
docs: Add deprecation message for the developer.android.com docs am:
b9bd6cca9e am: 045ae0458a am: e161f75d38 am: 536dc4ecc4 am: bd7fab30dc
…
…
Merge "Create and implement a CacheListener inside WifiNetworkScoreCache." am:
31a8f712ab am: 6d749fb489 am: c5443c1d5c
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%