Volume Group with associated stream type does not have their volume
restore after restart / crash due even if correctly stored in
Settings DB.
A guard prevent to restore it. However, when using volume per attributes,
Settings DB is used, so it is safe to restore volumes for all group.
This CL fixes this issue by removing this guard.
Test: set Music volume & reboot & dumpsys audio
Ensure indexes matches
Signed-off-by: Francois Gaffie <francois.gaffie@renault.com>
Change-Id: I00aa8c17bffca21a128086fbbbeafffc26521a3b
Merged-In: I239145d8bc50237ff902026594423c6d1fa04ad4
When the focus is owned by an external audio policy, and when
a client's request fails, the FocusRequester dedicated Map is not
cleared.
As the client app may not call AudioManager#abandonAudioFocus (since
the requestAudioFocus failed), it leads to not only dumpsys side effects but
also it triggers upon client's focus binder died event, the call
of notifyExtFocusPolicyFocusAbandon_syncAf.
This CL fixes this issue by removing the FocusRequester when the request
fails, the same way it is already done on permanent loss of focus.
Test: build & boot
Signed-off-by: Francois Gaffie <francois.gaffie@renault.com>
Change-Id: I4d1b216b606c8f73c9b68353723284d9e178297d
The CL that moved the initialization of the tethering offload
config HAL from C++ to Java caused the code not to retry
fetching the service if it is not ready when tethering is
started. This is because the C++ version of getService() retries,
but the Java version only retries if getService(true) is called.
Make the new code retry as well.
b/152430668#comment4 asserts that the fetch will be retried only
if the service is installed on the device, so the retries should
be attempted (and thus should not have any startup time impact)
on devices that do not support tethering offload.
Bug: 152430668
Test: builds, boots, tethering offload works
Change-Id: I093f127d90b2aa1b13eb0748378a24726d419472
These would cause these actions (and any that depended upon them) to
re-run during every incremental build. These now produce warnings:
ninja: output file missing after successful execution: out/soong/.intermediates/frameworks/base/ds-ref-navtree-docs/android_common/ds-ref-navtree-docs-proofrerad.txt
It turns out that the -proofread argument to doclava is ignored with the
following argument combinations:
* -static -devsite
* -navtreeonly
Test: m docs; m docs (nothing to do)
Change-Id: I21b939951f5a2f33914e9fc9414df8206091d262
R_EXTENSION_INT is 0 now, but if bumped we don't want to bump
the other return values of this method.
Bug: 154486201
Test: SdkExtensionsTest
Change-Id: I36855ba1881da4056276f4a5626ca64d2129353b
Merged-In: I36855ba1881da4056276f4a5626ca64d2129353b
(cherry picked from commit 11111482211f0ff59f54f71cf0145ab572af3fae)
Currently, if a prefix is learned from an RA while prefix
discovery is running, clatd will be correctly started, but
prefix discovery will be stopped.
In order to fix this, make it possible to call
stopPrefixDiscovery without transitioning to IDLE state (which
is obviously necessary in this case), by moving the assignment of
the next state from that method to its callers. For consistency,
do the same for startPrefixDiscovery.
Bug: 150648313
Test: new test coverage
Change-Id: I3803fa3d9806848b331c35ee8bac256934bd1f21
464xlat will never be started on a network that is not connected,
or on a network that has no IPv6 address.
This is a no-op test-only change but it is necessary for an
upcoming change that violates some of the invalid assumptions
currently made by this test and causes it to fail.
Bug: 150648313
Test: test-only change
Change-Id: I41766e9adaa7c24454648b371e6e3cc647693be5
All carriers discarded the requirement to put up a standing
notification when tethering is on. Thus, remove the "tethering
is on" notification.
Bug: 154438388
Test: atest TetheringTests
Change-Id: Ife3915837b6b7b83d3eaaa84b71b6409ff37b71c
The NAT64 prefix from the RA always takes precedence over the
NAT64 prefix from DNS discovery, because it is detected faster,
and detecting it does not require sending any packets.
Bug: 150648313
Test: new unit test
Change-Id: Ic7452431d2d9aea1ae59b67a9d8383c6cc5b3902
With b/152655547, all aidl_interface modules are considered as stable
unless it is explicitly with "unstable: true". This change marks the
aidl_interface that are not used across updatable module bounraries
as unstable, so that the build system does not run the API
dumping/checking on them.
Exempt-From-Owner-Approval: cherry-pick from internal
Bug: 152655547
Test: m
Merged-In: I1257c66de6dd42b2d32d47ed74cb2878f79d14fb
(cherry picked from commit db589dded4)
Change-Id: I1257c66de6dd42b2d32d47ed74cb2878f79d14fb
DcTracker uses several SIM related signals for different purposes.
Those signals include SIM record loaded/not-loaded, subscription
changed event, and carrier config changed event. Those signals
are slightly different but not that really important to DcTracker.
What DcTracker cares is
1. Whether SIM is inserted or not.
2. Whether configuration changes or not.
By listening to a single carrier config change event can handle
the cases above.
Removed all SIM record related places in DcTracker. SIM record should
not be accessed by anyone outside of UICC controller.
Test: Manual test + unit tests
Bug: 146168348
Merged-In: Iad45933ea77eb460625a891071535cbeaf8ac3b0
Change-Id: Iad45933ea77eb460625a891071535cbeaf8ac3b0
(cherry picked from commit df3001b935)
Make CellIdentity.MNC_MIN_LENGTH and CellIdentity.MNC_MAX_LENGTH
hidden public to support IccRecords changes.
Bug: 152518548
Test: make
Change-Id: Ic253a6bbbf07e4ce62a7ea25ca67dff54e2c67c8
Merged-In: Ic253a6bbbf07e4ce62a7ea25ca67dff54e2c67c8
(cherry picked from commit 3f9e9edb8e)
Otherwise bionic might still have a pointer into the old content.
Bug: https://issuetracker.google.com/152893281
Test: treehugger
Change-Id: I25e31c5da33e529c750ef6f2e3f36ca62cf4d231
Ensure that userspace reboot is supported before performing any actions.
Any call into UserspaceRebootLogger in the case that userspace reboot
is not supported should be a no-op. It is unexpected to call into
this class on an unsupported device, so log with ASSERT priority
in this case.
Test: atest UserspaceRebootHostTest
Bug: 153648276
Change-Id: Ic3041ff3abe0d2641d3d99fc8e816f1f5c491a34
Warn user of potential data charges if the backhaul is
cellular and user is roaming.
Bug: 145629001
Test: atest TetheringTests
Change-Id: I74b4f87c2f6aad09e05d3f2a779f880396885953
