This is an effort to modularize RollbackManager.
As we move RollbackManagerService to apex/, SystemServer can't reference
RollbackManagerService directly. Let's use the class name to start the
service.
(Cherry-picked from 41a5d353ccf96c3e115355c6333bca7657dff29b)
Bug: 150347230
Test: m
Merged-In: Ied68ad031f84ea4a416ad779e9ddf4cc912bd7b9
Change-Id: Ied68ad031f84ea4a416ad779e9ddf4cc912bd7b9
Use AudioAttributes.getSystemUsage() instead of getUsage()
when comparing attributes as getUsage() defaults to UNKNOWN for
system usages and causes a false match.
Bug: 136121584
Test: build & run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioProductStrategyTest
Change-Id: I377e840b18443c33fb0b562b27fbc706aaeb8055
Volume Group with associated stream type does not have their volume
restored after restart / crash even if correctly stored in
Settings DB.
A guard prevents from restoring it. However, when using volume per attributes,
Settings DB is used, so it is safe to restore volumes for all groups.
This CL fixes this issue by removing this guard.
Bug: 136121584
Test: set Music volume & reboot & dumpsys audio
Ensure indexes matches
Signed-off-by: Francois Gaffie <francois.gaffie@renault.com>
Change-Id: I00aa8c17bffca21a128086fbbbeafffc26521a3b
When a strategy holds 2 stream types, following the same volume group
(aka same volume curves), when audioservice initializes, it may
overwritte the Min/max for the volume group.
This is due to the fact that the second stream type is not recognized
and falls back on default volume group (aka Music). So, Min/max are
overwritten with music Min/max.
This CL fixes the bug by formatting correctly the AudioAttributesGroups
of a product strategy by checking not only the volume group id but
also the stream type.
Bug: 136121584
Test: build & run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioProductStrategyTest
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioVolumeGroupTest
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioVolumeGroupChangeHandlerTest
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioManagerTest#testPermissionsForVolumePerAttributes
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioManagerTest#testGetAndValidateProductStrategies
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioManagerTest#testGetAndValidateVolumeGroups
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioManagerTest#testSetGetVolumePerAttributesWithInvalidAttributes
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioManagerTest#testSetGetVolumePerAttributes
run cts-dev -m CtsMediaTestCase --test android.media.cts.AudioManagerTest#testVolumeGroupCallback
Change-Id: I3aab572ef4daeecce13bbcef6278edcc42b7d594
Signed-off-by: François Gaffie <francois.gaffie@renault.com>
This reverts commit e96b5668b35b14b98e18a4d64d7aadb7fa071f7f.
Reason for revert: Feature has been postponed
Bug: 151761909
Change-Id: I7db5fb79d52b3da33b84bb07d1f612be760299c2
Add support passphrase and ack dialogs. Passphrase should use the
exact same text and dialog as the PIN dialog, only defaulting to text
input.
Bug: 152517004
Test: Controls Mock App supports launching all dialog types
Change-Id: I3ebd51d656818f8edad9b70ccc8f0b89d6d8acc6
Removed controls should have as much cached information as possible.
This adds structure name and subtitle.
Also, if the structure is not set it would cause issues (as empty
structure is a valid structure).
Fixes: 151089232
Test: atest ControlsControllerImplTest
Test: manual
Change-Id: I6cf5f285fe85ddc78ae59133dcf406793293a3f7
Any vertical diff while dragging would stop the drag, and scroll the
parent. Request the parent to let the child maintain focus.
Bug: 152493182
Test: manual, dim a light with enough controls to scroll
Change-Id: I4b00db3501c16521dc3156dc4631aa533fdf17ae
Get activity from top to bottom order starting from boundary
would get activity that is below the one we are comparing.
Looking for occluding activity above this one instead.
Bug: 151304143
Test: start the app and sign in
Change-Id: I05a4b6d65b0de6a362f8ed9c75a12b37146a1653
App icons may not respond well to tinting, as currently defined, and
the spec calls for them to remain untouched. Make sure to limit the
icon size.
Bug: 152397193
Test: visual
Change-Id: I36afecfc440fb82814c5bd00ca20e4d71ce40789
