Skip to content
Snippets Groups Projects
  1. Dec 14, 2020
  2. Dec 13, 2020
    • Chalard Jean's avatar
      Fix a crash in eng builds · fb0ff9bb
      Chalard Jean authored
      CAPTIVE_PORTAL is a CS-managed capability, and causes CS to log a wtf.
      When this test is run on an eng build, this sends SIGSEGV to the test,
      which is pretty difficult to debug.
      
      Test: FrameworksNetTests NetworkStackTests
      Change-Id: I72fc46a6daa4e886425b4dc967318cca9f1a5302
      fb0ff9bb
  3. Dec 12, 2020
    • Lorenzo Colitti's avatar
      Generalize support for underlying networks. · 6c01b8eb
      Lorenzo Colitti authored
      Currently, ConnectivityService assumes that only VPNs can have
      underlying networks. Make the code decide this based only on the
      return value of NetworkAgentInfo#supportsUnderlyingNetworks.
      This allows non-VPN network types to support underlying networks
      in the future.
      
      This requires storing the original agent's capabilities in
      NetworkAgentInfo so that applyUnderlyingCapabilities can mix in
      the underlying network capabilities without overwriting the
      capabilities of the network itself. Currently, the only
      information that applyUnderlyingCapabilities takes from the
      original agent's capabilities are the metered bit (stored in
      NetworkAgentInfo#declaredMetered) and the transports (assumed to
      be exactly {TRANSPORT_VPN}. Store the full capabilities instead.
      This is more state than needed but it ensures that we do not need
      to make any changes if in the future we want to propagate new
      types of information from the underlying networks.
      
      This should have no impact on current use cases (i.e., VPNs).
      
      There is a change in ordering: in disconnectAndDestroyNetwork,
      the new code propagates underlying network capabilities before
      removing the network from LegacyTypeTracker, instead of after.
      
      This is done to simplify the new code. When the new code
      propagates underlying network capabilities in response to a
      change for a particular network (e.g., connect, disconnect,
      capabilities change), it only considers networks that have the
      changed network as underlying. Because determining the
      underlying networks requires knowing the default network,
      the new code runs before the default network is changed and
      LegacyTypeTracker is updated.
      
      This shouldn't have app implications because the connectivity
      broadcasts sent by LegacyTypeTracker and the callbacks cannot be
      ordered, since they run on separate threads with unpredictable
      delays. The capability change callbacks resulting from
      propagation of underlying network capabilities were already
      sent before the rematch, so the callbacks themselves are not
      reordered in any way.
      
      Bug: 173331190
      Test: atest FrameworksNetTests \
                  CtsNetTestCases:NetworkAgentTest \
      	    CtsNetTestCases:Ikev2VpnTest \
      	    CtsNetTestCases:VpnServiceTest \
      	    CtsNetTestCases:android.net.cts.ConnectivityDiagnosticsManagerTest \
      	    HostsideVpnTests com.android.server.connectivity.VpnTest
      Change-Id: Ic5353a928a3a3541dcf953c35f47277c5e295db8
      6c01b8eb
    • Treehugger Robot's avatar
      Merge "Add missing IMF OWNERS" am: 4e3959e5 · 30497d09
      Treehugger Robot authored
      Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1525813
      
      MUST ONLY BE SUBMITTED BY AUTOMERGER
      
      Change-Id: I4b85f391e4634fa2596f7469cfb58d7917c9a8a7
      30497d09
    • Treehugger Robot's avatar
      Merge "Add missing IMF OWNERS" · 4e3959e5
      Treehugger Robot authored
      4e3959e5
    • Treehugger Robot's avatar
      Merge "Revert "Revert "Keystore 2.0 SPI: Move keymint spec to security ..."" am: dd8891ac · 4ac4916c
      Treehugger Robot authored
      Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1525189
      
      MUST ONLY BE SUBMITTED BY AUTOMERGER
      
      Change-Id: I48cb973018ef4f81b088232894c9ae087bd2d431
      4ac4916c
    • Wonsik Kim's avatar
      MediaCodecInfo: limit resolution to 4K for 32-bit processes · ef60b5fa
      Wonsik Kim authored
      Due to the limited virtual memory address space it is not practical
      to advertise support for more than 4K for 32-bit processes.
      
      Bug: 173488434
      Test: atest CtsMediaTestCases -- --module-arg CtsMediaTestCases:size:small
      Change-Id: Ibcd7f70f4efd8d696d831769bafe932207640830
      ef60b5fa
    • Chinmay Dhodapkar's avatar
      Merge "Supported IWLAN Fail Cause" am: 32e1818f · bd1ec880
      Chinmay Dhodapkar authored
      Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1513195
      
      MUST ONLY BE SUBMITTED BY AUTOMERGER
      
      Change-Id: I8e2d1e1b669e2e27dc3449cfb7ee4b2fcb9715d7
      bd1ec880
    • Treehugger Robot's avatar
  4. Dec 11, 2020
Loading