1. Handle the set member avaiabler intent, check the group is existing and create bond automatically.
2. Accept the paring request for the ongoing set member
Bug: 150670922
Bug: 178981521
Test: pair with one of the CSIP supported device,and get bonded with the
whole coordinated set
Change-Id: Ia95e1ba6dccde0a4e61a9eafdef746b1415704a4
Bug: 178981521
Bug: 150670922
Test: pair with two device which are a coordinated set, and make sure
the UI only show one device
Merged-In: I1a8d570da1af7fa4c8b3a99f8ce69d23b574e96c
Change-Id: I1a8d570da1af7fa4c8b3a99f8ce69d23b574e96c
When intentional API breakages are made, the incompatibilities tracking
file must be updated. This makes the failing build rule output the
baseline/incompatibilities file that would have made the build rule
succeed. This file can then be used to update prebuilts/sdk.
Whilst here, also make metalava quiet so we don't need to capture
stdout.
Test: make breaking change, build compat rule, inspect output dir
Change-Id: Ia95b65548371329cd467fd3093db92b471e6986d
The mainDexClasses script is obsolete, pass the rule to d8 with
--main-dex-rules instead.
Test: mma
Change-Id: Ia88660550c3e57749b8ccb154e97c31aaf2fcf3a
SignalStrengthUpdateRequest
Support different SignalMeasurementType with same type of RAN
is valid user case. For example, client may be interested to
measure both RSRP and RSRQ for EUTRAN.
Throw IAE if the SignalThresholdInfo collection is empty. This
is behavior specified in the public interface.
Bug: 198318496
Test: atest SignalStrengthUpdateRequestTest
Change-Id: I87ea5e356189f61fc58dff80456aff35ea2a8e55
Bug: 178981521
Bug: 150670922
Test: Discover and pair with the CSIP supported device, and check the
pairing string in the dialog
Merged-In: I3e99c59e0cb974409291e1b4c28393106784e133
Change-Id: I3e99c59e0cb974409291e1b4c28393106784e133
The framework-doc-stubs target currently takes the module source code
as input. Work is being done to change that over to use module sdk
artifacts, primarily the jar stub source code. Check in a
work-in-progress target that does so, to avoid it breaking and to
simplify iterating on improvements.
Bug: 186197911
Test: m framework-doc-stubs{,-module-stubs}
Merged-In: I1a275b3f44632e6655dc84d711a58fc0c5b3a46a
Change-Id: I1a275b3f44632e6655dc84d711a58fc0c5b3a46a
These two are the only annotations in the android.annotations package
that are not @hide -- they are actually in the public API.
As such, they are not suitable in the annotations library. Move them
back to frameworks/base where the other core java APIs live.
Bug: 186197911
Test: m
Merged-In: Ide01e4e7840bddf1e024e9024771e528d17a1d80
Change-Id: Ide01e4e7840bddf1e024e9024771e528d17a1d80
Add missing includes that are not transitively provided when compiling
against musl.
Bug: 190084016
Test: m USE_HOST_MUSL=true
Change-Id: If8829cebb0c62b539d7a336b75cf106755588cdd
Merged-In: If8829cebb0c62b539d7a336b75cf106755588cdd
Add missing includes that are not transitively provided when compiling
against musl.
Bug: 190084016
Test: m USE_HOST_MUSL=true
Change-Id: Ia22c3df2e904e7a479bb636b7db22e5a0c341b98
Since the EffectCallback in android::AudioEffect can
keep an instance of the latter alive for a longer time
than Java AudioEffect is alive, the callback need to
ensure that it's not trying to use deallocated objects
and deleted JVM references.
Bug: 178363662
Test: manual using EffectsTest app
Test: atest CtsMediaTestCases:AudioEffectTest
Test: atest CtsMediaTestCases:BassBoostTest
Test: atest CtsMediaTestCases:DynamicsProcessingTest
Test: atest CtsMediaTestCases:EnvReverbTest
Test: atest CtsMediaTestCases:EqualizerTest
Test: atest CtsMediaTestCases:LoudnessEnhancerTest
Test: atest CtsMediaTestCases:PresetReverbTest
Test: atest CtsMediaTestCases:VisualizerTest
Change-Id: I8c36f5af4a1a2b14e81b1344570d2f8746ffa91e
security_context_t has been marked as deprecated in libselinux from
version 3.2. Update to the `char*` type.
Bug: 190808996
Test: m
Change-Id: Ia632230e28c313d08119286973a5cf6401ef6910
A test should test the actual behavior as much as possible.
However, if the flag is true, matchesMobile/matchesMobileWildcard
will always return true regardless of the network type and metered.
Thus, remove this flag would be closer to the actual behavior.
Bug: 183776809
Test: atest FrameworksNetTests
Change-Id: I0907a08ca1dd8a14a738db4057ea5ff6a0cd925a
Add repro code to the EffectsTest app. Steps:
1. Start playback on the "Environmental Reverb Test",
memorize the session id.
2. Enter the session id on the "Bass Boost Test" or
the "Visualizer" tab.
3. Press "Hammer on release()" multiple times and check
if the app crashes. Currently this happens for
the Bass Boost effect.
Bug: 178363662
Test: see above
Change-Id: I800bc352fc8bc7073d1523c837008dc6fcfb957a
