Bug: 177641730
Test: n/a
Change-Id: Iaea2b7d55094a0e71278bbd2a09b5d6ce9de2830

* changes:
  BatteryManager: stateOfHealth is a property
  BatteryManager: Add new battery intent and property

Read batteryStateOfHealth from HealthData with access control

Bug: 251427118
Test: m update-api ; m
Change-Id: Ida87ef9f59c32cf52b036f37c7c261d03d3b4c37
Signed-off-by: AleX Pelosi <apelosi@google.com>

These are going to be public:
- Battery state of health
- Battery cycle count
- Charging status

These are going to be system API
- BATTERY_PROPERTY_MANUFACTURING_DATE
- BATTERY_PROPERTY_FIRST_USAGE_DATE
- BATTERY_PROPERTY_CHARGING_POLICY

Bug: 251427118
Test: m
Change-Id: If74b96d7657611934d293df8376296e373ec9b35
Signed-off-by: AleX Pelosi <apelosi@google.com>
Signed-off-by: Jack Wu <wjack@google.com>

Instead of checking this in the API class, throw a remote exception from
service when we detect that a non-fg app is trying to enable/disable fg
dispatch. The service is already tracking the app moving to background,
so there is no need for this redundant tracking in the API class.

Bug: 263565738
Test: atest CtsNfcTestCases
Test: CtsVerifier tag tests
Change-Id: Ia04848f6ed2595b33a861427d1d346d0dc9da8a5

Bug: 265887948
Test: build pass and verified the UI in the dark theme.
Change-Id: I6935bce627e7b28c3a9386c1f52b3953e4d1f5c3
Merged-In: I6935bce627e7b28c3a9386c1f52b3953e4d1f5c3

A line creating an output array was removed by mistake
during refactoring, add it back.

Bug: 206738075
Test: atest CtsMediaAudioTestCases:AudioRecordTest#testGetActiveMicrophones
Change-Id: I8562a403b27094954d90e97d1298fd5e8cdec843

Update ActivityEmbeddingUsage

Bug: 259592300
Test: build
Change-Id: Ic0e0ffcd576eed31a10d682bb0efdff5d1773b7d
Merged-In: Ic0e0ffcd576eed31a10d682bb0efdff5d1773b7d
(cherry picked from commit 0986205d)

Test
`com.android.server.pm.BackgroundDexOptServiceIntegrationTests#testBackgroundDexOptDowngradeSuccessful`
has been failing for a long time; temporarily disable it while we
investigate this issue

Test: atest BackgroundDexOptServiceIntegrationTests
Bug: 251438180
Change-Id: I3584ed2fd49e673a2d9bb37aabb11577c52a6267

This reverts commit 9f5ec0c7.

Reason for revert: this CL removed getPhysicalAddress from the main service thread, which caused errors.

Bug: 269451560
Change-Id: I42c478831c4daa5d17e55f7f8edd253449b863b8

Bug: 269714344
Test: atest FrameworksNetTests
Change-Id: Ifdaccb91277a579908ce28ec08318b0aea43b5de

Test: VpnTest
Bug: 269714344
Change-Id: I6615a1e3f8e9cdf7da17d66034d269b16c795d5b

the default mode is "w",if the cache file is not deleted successfully before openOutputStream and the size of new ringtone is smaller than old rongtone,the cache file will be a mixture of old and new ringtone.

Bug: 263074833

Change-Id: Ib7a0bf5e2a9f695aa4701c91c0b79c6bce2d76f1

Bug: 270014877

Change-Id: I247b271fd71658fb80323842e8e0d7542464c4c9
Test: m build

Test: refactoring CL. Existing unit tests still pass
Merged-In: I5bc9d5a9942a958491a319a800a9668c6793cf6c
Change-Id: I5bc9d5a9942a958491a319a800a9668c6793cf6c

When mode changes to NORMAL but the USAGE_VOICE_COMMUNICATION is still
present in the playback streams the mode change would trigger volume
update but would still use STREAM_VOICE_CALL volume level and the music
content will be resumed with voice call volume, possibly with higher
and potentially harmful volume level.

This change relies on mode change to get stream type from the mode
and therefor restores the right volume right away, without relying on
the onPlaybackConfigChange() which seems to be happening to late while
the loud music with the conversation volume level already reached the
listener.

Bug: 247659576
Tag: #feature
Test: manually testing with VoIP call while streaming media
Change-Id: Ie2225b7e92e0d3f7146e9266caf8bda81eddad03

Bug: b/255495104
Test: N/A
Change-Id: I11b0cb8fa3a143b4d9af74f0464ff3737393c9fd

Merge "add setDefaultExecutor to ImsCallSessionListener to set the executor when a conference call is established"

add setDefaultExecutor to ImsCallSessionListener to set the executor when a conference call is established

add a way to set the executor variable in ImsCallSessionListener, because ImsCallSessionListener has the information of ImsCallSessionImpl, which passed from vendor

Bug: 262800764
Test: aTest android.telephony.ims.*
Test: Call / Conference call E2E regression test
Merged-In: I63ba6a9d4ea4b8d963bc7bc2ee8e1d019c75ee10
Change-Id: I63ba6a9d4ea4b8d963bc7bc2ee8e1d019c75ee10

Test: adb shell dumpsys audio
Bug: 263209656
Merged-In: Ie4e6b6a59d95a47e9723bd9433aaa35aef7a2866
Change-Id: Ie4e6b6a59d95a47e9723bd9433aaa35aef7a2866

Currently, when LE Audio device becomes unavaliable due to BT adapter
disable, user can hear audio from device speaker for a split second.
This is because we make device unavaliable immediately for LE Audio.
Instead, it should become unavaliable after AUDIO_BECOMING_NOISY intent
is sent.

Since this is working correctly for A2DP, fix is to copy solution from
there for LE Audio code path, and split makeLeAudioDeviceUnavailable
into *Now and *Later versions.

With this fix, the device becomes unavaliable after the noisy intent,
and audio glitch is not heard from speaker.

Example dumpsys audio logs after fix is applied:

02-16 11:25:43:022 broadcast ACTION_AUDIO_BECOMING_NOISY
02-16 11:25:44:050 LE Audio device addr=14:3F:A6:60:0A:A5 made unavailable

Bug: 263209656
Test: play music in Spotfiy, listen on LE Audio device, then disable
Bluetooth. Verify that audio is not heard from the phoen speaker

Merged-In: I0ff85798c3672b2d6862460c2f2d914f705aac2c
Change-Id: I0ff85798c3672b2d6862460c2f2d914f705aac2c

Change-Id: Ie9dd2bc0884ec2d5d6162234717f58aaaf3ddae5