summaryrefslogtreecommitdiff
path: root/wifi/java
diff options
context:
space:
mode:
authorRemi NGUYEN VAN <reminv@google.com>2020-12-03 17:58:49 +0900
committerRemi NGUYEN VAN <reminv@google.com>2020-12-15 17:57:32 +0900
commit32a5b51fe2d7287a07e4fffd28cf99a975240b2c (patch)
treebb99ec7571d32511ef3ff820940b6fc02c2c9e7c /wifi/java
parent6557000a116008de7abfa2c49cef5192a2894856 (diff)
Register ethernet listeners on specific Executors
Have users of EthernetManager#addListener specify an Executor instead of running callbacks on ConnectivityThread. For existing clients, run callbacks on the common BackgroundThread. This change in behavior is fine because addListener is not an API, the threading model in Q was to run callbacks on the looper of the thread that first created EthernetManager (so there is already no guarantee on which thread is used), and the only users are in Settings. ConnectivityThread is moving to a connectivity-specific JAR, so it should not be used by external classes. Bug: 174436414 Test: Ethernet client / tethering working atest TetheringIntegrationTests Change-Id: Ic9a959f89915329f79eeeaa0a210ad50811d1291
Diffstat (limited to 'wifi/java')
0 files changed, 0 insertions, 0 deletions