Skip to content
Snippets Groups Projects
  1. May 03, 2018
    • Erik Kline's avatar
      Add static IpClient logging · c172c7d8
      Erik Kline authored
      Support keeping IpClient logs around and dumping them
      during dumpsys.  Previously we got this benefit for
      wifi by virtue of WifiStateMachine's long-lived nature.
      Now that this is changing we need to be sure we have
      logs, and this method gets us Ethernet logs as well.
      
      Bug: 62476366
      Bug: 77999594
      Test: as follows
          - built
          - flashed
          - booted
          - runtest frameworks-net passes
          - dumpsys connmetrics [ipclient] works
      Merged-In: Ib4daf0902cae91acadbe9965de1fb73c96a47bec
      Merged-In: Ie947394fabcaca7fc1d067f095c2442ee2704593
      Change-Id: I1136a83de8097fdb4130debe1eaf689be7132fe5
      (cherry picked from commit 3f8306b8)
      c172c7d8
  2. May 02, 2018
  3. May 01, 2018
    • Chenbo Feng's avatar
      Remove the unused file parsing function · b815c978
      Chenbo Feng authored
      With the new xt_bpf support for iface stats. We no longer need to parse
      the per interface stats from /proc/net/dev. And since the old xt_qtaguid
      code path also not depend on it, we can completly remove that helper
      function since no caller is depending on it now.
      
      Bug: 72111305
      Test: runtest frameworks-net -c com.android.internal.net.NetworkStatsFactoryTest
      Change-Id: Icb7eaeef0eeb9fdffd32a90316c76ee05bafffbe
      b815c978
    • Chenbo Feng's avatar
      Use eBPF map data for per iface stats · dcc56783
      Chenbo Feng authored
      After adding the xt_bpf module and ifaceStatsMap, eBPF tool can now
      support reading per interface data. So networkStatsFactory should move
      away from parsing proc/net/dev and use the eBPF map stats instead.
      
      Bug: 72111305
      Test: atest com.android.server.net.NetworkStatsServiceTest
      Change-Id: Ibcc6150d00835b3bd33af22a72e4a86e172581cf
      dcc56783
    • Anton Hansson's avatar
      frameworks/base: Update a few more references to android.jar. · 0c703900
      Anton Hansson authored
      These files are moving. Update the paths so that the old files can be
      deleted.
      
      Bug: 77525052
      Test: ./build for one of these scripts
      Change-Id: Iacca1f1930d6a2614866f6503a2b4c1eba4d4018
      0c703900
    • Chalard Jean's avatar
    • android-build-prod (mdb)'s avatar
      Merge changes Ie4709b6e,I57980ccb · 9b1c3e00
      android-build-prod (mdb) authored
      * changes:
        com.android.nfc_extras is built with java_sdk_library
        Fix link-type check warning on com.android.nfc_extras
      9b1c3e00
  4. Apr 30, 2018
  5. Apr 28, 2018
    • Pulkit Bhuwalka's avatar
      Get/Set IO capability of Bluetooth device · 979698bc
      Pulkit Bhuwalka authored
      Creates the hidden BluetoothAdapter APIs which can be used to
      control IO capability settings on the local Bluetooth device.
      
      Bug: 36015413
      Test: Used a test activity to control getting/setting the value and
      attempting pairing.
      
      Change-Id: Ibbfdc5ae5a1d56c6e3d003ab3bf5d095dcb583e4
      (cherry picked from commit 6043b7b90a27a836241bfc05e71eb46ce04c66cf)
      979698bc
  6. Apr 27, 2018
    • Shuo Qian's avatar
      093ade31
    • Ajay Panicker's avatar
      Don't set Bluetooth volume when the Bluetooth stream changes · 085ecc32
      Ajay Panicker authored
      Don't restore the remembered volume whenever an Bluetooth A2DP stream
      comes up or whenever Bluetooth AVRCP reports absolute volume support.
      All Bluetooth volume memory will now be handled by Bluetooth.
      
      Bug: 30602783
      Test: See that AudioService doesn't try to change the volume when a
      Bluetooth device connects.
      
      Change-Id: I683062c1a0565591ae33cbbb0381730b86ad17c2
      085ecc32
    • Jiyong Park's avatar
      com.android.nfc_extras is built with java_sdk_library · 611b7f4e
      Jiyong Park authored
      Remove the biolerplate code using java_sdk_library module type.
      
      Bug: 77575606
      Test: m -j
      
      Change-Id: Ie4709b6ebc18bc2e4e26137d4a097d734f4435fe
      611b7f4e
    • android-build-prod (mdb)'s avatar
    • Chalard Jean's avatar
      Let DnsManager fill in LinkProperties for private DNSes · f97656b8
      Chalard Jean authored
      (clean cherry-pick from ag/3880157)
      
      Test: new tests pass
      Bug: 73641539
      Change-Id: I971ef4d27b22a435d7459e1c4b31a8715ef6e610
      Merged-In: I837df61e3c277ae08ebf4fdcd4c4e9ac8c550811
      Merged-In: I72ecaa4f7d7320ffa2e0ba82fadafc947c8a6981
      f97656b8
    • Chalard Jean's avatar
      Add the list of private DNS addresses to LinkProperties · 03dbf6bd
      Chalard Jean authored
      (clean cherry-pick from ag/3874803)
      
      Test: atest android.net.LinkPropertiesTest, also new tests pass
      Bug: 73641539
      Change-Id: If33a35b1354a67db09411ff098f20064797296ad
      Merged-In: I4b739c56e658690532ae9deb0b9a3bc9b2adf8b0
      Merged-In: I6bdbef78d078d68534c8e07e9af031ce374560ef
      03dbf6bd
    • Jiyong Park's avatar
      Fix link-type check warning on com.android.nfc_extras · 863f3538
      Jiyong Park authored
      The library has been built without SDK, and is used by an app
      NfcExtrasTests that is built with SDK. Such this SDK -> non-SDK
      dependency has been causing link-type check warnings, which will turn
      into errors soon.
      
      This change fixes the warning by making a stub library
      com.android.nfc_extras.stubs from the runtime library and let the app to
      link against the stub library. Since the stubs library does not use any
      private APIs, it is built with SDK.
      
      Bug: 69899800
      Test: m -j NfcExtrasTests is successful and does not show any link-type
      check warning.
      
      Merged-In: I57980ccbc9036d7cc6df114a975a384d10a2962b
      Change-Id: I57980ccbc9036d7cc6df114a975a384d10a2962b
      (cherry picked from commit ded4fd72)
      863f3538
    • Shuo Qian's avatar
      Restore the OEM hook implementation and usage · 1c11e207
      Shuo Qian authored
      The current plan is to keep the OEM hook implementation in the framework
      , this is for legacy device and old device upgrading (per b/78098059).
      
      For P launching device, the OEM hook service is removed in hal, so the 
      OEM hook api in framework should return something dummy, and prevent 
      infinite loop to get service, but these parts should be done in seperate
      CLs after this restore CL is merged.
      
      This reverts commit f09bde28.
      
      Bug: 34344851
      Change-Id: I2aea9be9aa7cecd4f7a1f1783391f0af173bfc59
      Test: pass Treehugger tests; pass cuttlefish test RilE2eTests
      
      Merged-In: I1f2117331a7f846b192c5f956f3841d58cb8154b
      1c11e207
    • android-build-prod (mdb)'s avatar
  7. Apr 26, 2018
  8. Apr 25, 2018
  9. Apr 24, 2018
Loading