Skip to content
Snippets Groups Projects
  1. Jun 24, 2020
  2. Jun 22, 2020
    • Mark Chien's avatar
      Merge "Tethering: Add WiGig support" am: 65fadfc134 am: 6c5b5b0803 · fdf89ee7
      Mark Chien authored
      Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1177323
      
      Change-Id: Ib48182d51cc6e4586cb43f8ca51ea673ee14d1d7
      fdf89ee7
    • Dedy Lansky's avatar
      Tethering: Add WiGig support · 4dd87aaf
      Dedy Lansky authored
      This change is a combination of following changes:
      
      1) Tethering: add TETHERING_WIGIG type
         Currently both WIFI and WIGIG use the same tethering type,
         TETHERING_WIFI. This causes conflicts between the frameworks,
         when both WIFI and WIGIG SoftAPs are started, one or both will
         not work.
         Fix this by using a seperate tethering type for WIGIG.
      
      2) Tethering: remove TETHERING_WIGIG state machine on interface down
         The wigig state machine relies on a TETHERING_STATE_CHANGED broadcast
         that is sent when the tethering state machine is first created, during
         interface up. Currently the tethering state machine is not removed
         on interface down except for TETHERING_BLUETOOTH, and as a result
         wigig tethering only works the first time SoftAP is started.
         In order to fix this, remove the tethering state machine on interface
         down for TETHERING_WIGIG as well.
      
      Bug: 143356416
      Test: TetheringCoverageTests
      
      Change-Id: Ic4d3aca0ed69234093af7f0206dab3335938c52a
      Merged-In: Ic4d3aca0ed69234093af7f0206dab3335938c52a
      4dd87aaf
    • Dedy Lansky's avatar
      Tethering: Add WiGig support · 6896f619
      Dedy Lansky authored
      This change is a combination of following changes:
      
      1) Tethering: add TETHERING_WIGIG type
         Currently both WIFI and WIGIG use the same tethering type,
         TETHERING_WIFI. This causes conflicts between the frameworks,
         when both WIFI and WIGIG SoftAPs are started, one or both will
         not work.
         Fix this by using a seperate tethering type for WIGIG.
      
      2) Tethering: remove TETHERING_WIGIG state machine on interface down
         The wigig state machine relies on a TETHERING_STATE_CHANGED broadcast
         that is sent when the tethering state machine is first created, during
         interface up. Currently the tethering state machine is not removed
         on interface down except for TETHERING_BLUETOOTH, and as a result
         wigig tethering only works the first time SoftAP is started.
         In order to fix this, remove the tethering state machine on interface
         down for TETHERING_WIGIG as well.
      
      Bug: 143356416
      Test: TetheringCoverageTests
      
      Change-Id: Ic4d3aca0ed69234093af7f0206dab3335938c52a
      6896f619
    • Wayne Ma's avatar
      Merge "Add framework-statsd dependency and make framework-statsd visible to... · 31b64614
      Wayne Ma authored
      Merge "Add framework-statsd dependency and make framework-statsd visible to Tethering package." into rvc-dev am: 7ce578a359
      
      Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/11926261
      
      Change-Id: I81e0304f0560cbd070c5bb49967a8b6bf3e5d58a
      31b64614
    • waynema's avatar
      Add framework-statsd dependency and make framework-statsd visible to · b7048af0
      waynema authored
      Tethering package.
      
      Tethering needs StatsEvent and StatsLog which are in
      framework-statsd.stubs.module_lib to write metrics.
      
      Bug: 153942334
      
      Test: make
      Change-Id: I8ba142a9b3678de36e6c4880a64e992e00680f38
      b7048af0
    • Remi NGUYEN VAN's avatar
  3. Jun 20, 2020
    • Mark Chien's avatar
      [automerger skipped] Merge changes from topics "pass-res",... · df63d22c
      Mark Chien authored
      [automerger skipped] Merge changes from topics "pass-res", "remove-isProvisioningNeeded" am: 788abd7c99 am: 932375528d -s ours
      
      am skip reason: Change-Id I9a5ff5dbc1db3f3be7fcd7146862a16b373507e6 with SHA-1 017bfba0 is in history
      
      Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1345357
      
      Change-Id: Ie251a5e4cbfc78f8b26ae32a12679dd08bd348d9
      df63d22c
    • markchien's avatar
      [automerger skipped] Pass entitlement configuration to Settings for... · 1f5c1055
      markchien authored
      [automerger skipped] Pass entitlement configuration to Settings for entitlement check am: 902043f5 am: f7d9dd76ab -s ours
      
      am skip reason: Change-Id I6f23553bb1da5f0b767f920b32a86fafb9e00b9e with SHA-1 217d7b01 is in history
      
      Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1253710
      
      Change-Id: I259c3a257511436baac8894c7677dbd3090941ab
      1f5c1055
    • markchien's avatar
      Protect invalid entitlement app configuration · 4c9428a1
      markchien authored
      There is a protection in Settings that Settings would gray out if
      tethering requires entitlement check but the entitlement app is
      invalid. Tethering resource is moved from framework to tethering
      module, so Settings can not fetch entitlement app name anymore.
      
      In this change, tethering module would check whether entitltement app
      package name is exsited if entitlement check is needed. Tethering would
      be not supported (Settings tethering option would be hidded) if
      entitlement app is not installed.
      
      After moving the protection into tethering module,
      TetherUtil#isProvisioningNeeded is no longer needed. Because The
      only use case is Settings wants to gray out tethering setting
      when entitltement check is needed but entitlement app is invalid.
      
      Bug: 146918263
      Test: atest TetheringCoverageTests
      Change-Id: I9a5ff5dbc1db3f3be7fcd7146862a16b373507e6
      Merged-In: I9a5ff5dbc1db3f3be7fcd7146862a16b373507e6
      4c9428a1
    • markchien's avatar
      Pass entitlement configuration to Settings for entitlement check · 902043f5
      markchien authored
      Tethering resource configuration is move from framwork to tethering
      module. Since tethering resource would not be accessible from outside
      of tethering module, EntitlementManager would tell Settings the
      entitlement configuration via intent extra when run entitlement check.
      
      Bug: 146918263
      Test: atest TetheringTests
      Change-Id: I6f23553bb1da5f0b767f920b32a86fafb9e00b9e
      Merged-In: I6f23553bb1da5f0b767f920b32a86fafb9e00b9e
      902043f5
  4. Jun 19, 2020
  5. Jun 18, 2020
Loading