Support the new IWLAN handover rules to
allow/disallow handover based on different
scenarios.
Bug: 196597630
Test: atest DataNetworkControllerTest
Merged-In: Ic5584908131d4c8e0940f3d60def2dc74a7405d9
Change-Id: Ic5584908131d4c8e0940f3d60def2dc74a7405d9
It used to be in system server, but this is for a class in boot
classpath so we can move it to AndroidRuntime.cpp and avoid system
server dirtying memory for these methods.
Test: m
Bug: 162110941
Change-Id: Ifda5957aab757fe47c97b1aee0a6a8b7a059ac3d
Change NTP polling interval from 24 hours to 18 hours. The max allowed
age of a time suggestion for it to be considered by the time_detector
is set to 24 hours, so if we only refresh NTP after 24 hours, it means
devices may commonly switch to newer NITZ signals when the NTP signal
"expires". Then it will flip back to NTP when the NTP alarm triggers.
Whether it switches to an NITZ signal or not also depends on things
like whether NITZ signals are received, or other things happen that
force the time_detector to reassess suggestions, after the NTP
suggestion has expired.
If we can keep devices consistently using NTP, that's going to lead to
better results, especially given NITZ can be quite inaccurate.
18 hours has been chosen as an arbitrary compromise: it gives the
device 25% of the expiry interval to get a fresh signal. It should
mean that NITZ isn't used in the common case.
Bug: 217357882
Test: None
Change-Id: I86281888ce009a19e50240d7f07aac1f5ce72222
While dumpProtoLocked is called, InvalidProtocolBufferException
occurred because types are mismatched between platform side and
module side.
netstats.proto was moved into connectivity module, both the
platform(incident.proto) and the module uses protoc-gen-javastream
to generate the Java classes from it. It should be fine since
platform includes the source of the proto, and jarjar the generated
classess in the module to avoid conflict with platform.
Bug: 218566849
Test: adb shell incident 3001
adb shell dumpsys netstats --proto
atest CtsIncidentHostTestCases:IncidentdTest#testIncidentReportDumpAuto
Change-Id: I4654350a59dc1ca1a925785ad37f34aa7b481235
Merged-In: I4654350a59dc1ca1a925785ad37f34aa7b481235
1. Adding the bucketDuration with unit as bucketDurationmillis
2. make the Key class be final
3. The Key set parameter be marked with an IntDef
Bug: 220153505
Test: atest NetworkStatsCollectionTest
Change-Id: Iab32b8fc129b77d6786c2f1f2339e515f2eb55f7
swapActiveStatsMap is temporary added for the NetworkStatsFactory to
call BpfNetMaps#swapActiveStatsMap in tethering mainline module. Now
NetworkStatsFactory already be mainlined, calling BpfNetMaps#swapActiveStatsMap
directly.
Bug: 218494448
Test: atest ConnectivityCoverageTests
atest FrameworksNetTests
Change-Id: I25618020c078c7de3f0036c48d06d7816a431f62
Add a field in the VpnConfig to store local route exclusion
bit from VpnProfile, and set the value into the networkAgent
of VPN network.
Bug: 184750836
Test: atest FrameworksNetTests HostsideVpnTests
Change-Id: I22b9a5990a3dab0418b44ec19d2996ead6529231
ApplicationInfo is getting too big :(
Bug: 219763513
Test: boot, TreeHugger
Merged-In: I6dba57af9aa99ec0730903dd89589d08c513beb2
Change-Id: I6dba57af9aa99ec0730903dd89589d08c513beb2
(cherry picked from commit 3d60f035c164ebc1416b5a3f7474e6088b731869)
JDK 17 no longer allows access to com.sun.tools.javac.code by default,
use the public APIs instead.
Bug: 219098645
Test: m checkbuild
Change-Id: If379935cc4ab9e5c809cc9fbfccbacfd8d87e8c8
It is not recommended to do IO in the UI thread.
Bug: 219611030
Test: boot AOSP, check if clipboard works
Signed-off-by: Roman Kiryanov <rkir@google.com>
Change-Id: Iaf445ae3e6e009b86ccf4d1783dffeebc165bb62
Mounting encrypted OBB files has never worked reliably across devices,
partly due to its reliance on Twofish encryption support in the kernel.
This is because Twofish support (CONFIG_CRYPTO_TWOFISH) has never been
required or even recommended for Android. It has never been enabled in
GKI, but even before GKI it wasn't required or recommended. Moreover,
this is now the only Android feature that still uses dm-crypt
(CONFIG_DM_CRYPT), and some devices don't have that enabled either.
Therefore, it appears that this feature is unused. That's perhaps not
surprising, considering that the documentation for OBBs
(https://developer.android.com/google/play/expansion-files) says that
they are deprecated, and also it explains OBBs as being app files that
are opaque to the platform; the ability of the platform to mount OBBs
that happen to be in a particular format is never mentioned. That means
that OBB mounting is probably rarely used even with unencrypted OBBs.
Finally, the usefulness of OBBs having their own encryption layer (in
addition to what the platform already provides via FBE) is not clear
either, especially with such an unusual choice of cipher.
To avoid the confusion that is being caused by having the broken code
for mounting encrypted OBBs still sitting around, let's remove it.
Test: atest StorageManagerTest # on Cuttlefish
Test: atest StorageManagerIntegrationTest # on Cuttlefish
Bug: 216475849
Change-Id: I6e6a6462ab8343299dc5e0145b87dc28b16b0bc1
If the signal bar visible state is STATE_DOT, it should be shown
a dot instead of signal bar icons. But the signal bar icon will
be shown again if the mobile state changed, and then, the dot and
signal bar icon are both shown. So don't update signal bar
visibility if the state is not STATE_ICON
Bugs: 200915946
Test: Manual
Change-Id: I7fb04049790f112441511462d3f2963aed42c790
