am skip reason: Change-Id I0399917e7cefa1547d617e688225544c4fc1a231 with SHA-1 f053e4b6f5 is in history
Change-Id: Ia881348345ad2ede4181453a206250123c7ff247
am skip reason: Change-Id I0399917e7cefa1547d617e688225544c4fc1a231 with SHA-1 f053e4b6f5 is in history
Change-Id: I178d7b119ce2f11ce03acc5491b87224625d60a6
am skip reason: Change-Id I0399917e7cefa1547d617e688225544c4fc1a231 with SHA-1 f053e4b6f5 is in history
Change-Id: I8a441c075d7a67f9bb5528c66cbf67df7fbacc60
This adds metalava api tracking generation to the module
stub rules, to make sure we know exactly what API a
particular module stub exports.
Bug: 147768409
Test: m update-api check-api
Exempt-From-Owner-Approval: approved internally
Change-Id: Iaf2ef5b5751eb208d119ddbc74481239366fe581
Merged-In: Iaf2ef5b5751eb208d119ddbc74481239366fe581
(cherry picked from commit e7c52c7e3f)
Per API review:
- @IntDef defined on the type integer parameter
- have getters on each parameter that is set in the
TetheringRequest.Builder
- new added API should not be deprecated
Below APIs is moved from system-current to module-lib-current that only
plafrom code(e.g. ConnectivityManager and Settings) can use them.
TetheringRequest.
onTetherableInterfaceRegexpsChanged, TetheringInterfaceRegexps:
Only platform code can use them because interfaces by regular
expressions are a mechanism which is planning to be deprecated.
Also rename some constants for easier to understand.
Bug: 149858697
Bug: 151243337
Test: m doc-comment-check-docs
atest TetheringTests
Change-Id: Idd041f0fbeca411ea23e49786a50dd7feb77ef45
am skip reason: Change-Id I30f68d83344f66fb3ef77abf3f8748c3eb1276f0 with SHA-1 57e22c5ab9 is in history
Change-Id: I75906f95862b679ddec38f353adca8f84d98ee92
am skip reason: Change-Id I30f68d83344f66fb3ef77abf3f8748c3eb1276f0 with SHA-1 3355cc4f06 is in history
Change-Id: Id85f3640395b4a8ad4daf016015172b237a49e33
am skip reason: Change-Id I30f68d83344f66fb3ef77abf3f8748c3eb1276f0 with SHA-1 3355cc4f06 is in history
Change-Id: I381af2103d8a3d66c92e73ede2615352fbab8160
am skip reason: Change-Id I30f68d83344f66fb3ef77abf3f8748c3eb1276f0 with SHA-1 57e22c5ab9 is in history
Change-Id: I512bf5f89f1ae69bfbd1c90ebcd9708824743fea
am skip reason: Change-Id I30f68d83344f66fb3ef77abf3f8748c3eb1276f0 with SHA-1 3355cc4f06 is in history
Change-Id: If7c9139689d3e76653f00017a567d39d3612b47c
am skip reason: Change-Id I30f68d83344f66fb3ef77abf3f8748c3eb1276f0 with SHA-1 3355cc4f06 is in history
Change-Id: I705409f05587f01fa3e2ebfd1e3f5e7e58002d97
Application can specify static ipv4 server and client address to setup
tethering and this is one shot configuration. Tethering service would
not save the configuration and the configuration would be reset when
tethering stop or start failure.
When startTethering callback fired, it just mean tethering is requested
successful. Therefore, callers may call startTethering again if
startTethering successful but do not receive following tethering active
notification for a while. Tethering service never actually does anything
synchronously when startTethering is called:
-startProvisioningIfNeeded just posts a message to the handler thread.
-enableTetheringInternal doesn't do anything synchronously, it just
asks the downstreams to get their interfaces ready and waits for
callbacks.
If tethering is already enabled with a different request,
tethering would be disabled and re-enabled.
Bug: 141256482
Test: -build, flash, boot
-atest TetheringTests
-atest CtsTetheringTest
Change-Id: I2b2dd965a673e6f1626738d41b5d443f0f9fbd0e
Merged-In: I0399917e7cefa1547d617e688225544c4fc1a231
(cherry picked from commit 5d6723e24e21154bef3967585a8adc069e007f49)
am skip reason: Change-Id Iaf2ef5b5751eb208d119ddbc74481239366fe581 with SHA-1 a5428687e4 is in history
Change-Id: I8e128a279e8ca746bfff52d0d0a7223f79e3bae8
am skip reason: Change-Id Iaf2ef5b5751eb208d119ddbc74481239366fe581 with SHA-1 a5428687e4 is in history
Change-Id: Ibc7f6be60ed3d9460cc01de3aa33027609acd442
am skip reason: Change-Id Iaf2ef5b5751eb208d119ddbc74481239366fe581 with SHA-1 a5428687e4 is in history
Change-Id: I7d747bc98bb8e6114956ea503d894f8b30fda46b
This adds metalava api tracking generation to the module
stub rules, to make sure we know exactly what API a
particular module stub exports.
Bug: 147768409
Test: m update-api
Exempt-From-Owner-Approval: Approved in master
Change-Id: Iaf2ef5b5751eb208d119ddbc74481239366fe581
Merged-In: Iaf2ef5b5751eb208d119ddbc74481239366fe581
(cherry picked from commit b602b0b2f18d96866a5d7e5d27958af774d1f802)
This adds metalava api tracking generation to the module
stub rules, to make sure we know exactly what API a
particular module stub exports.
Bug: 147768409
Test: m update-api
Exempt-From-Owner-Approval: Approved in master
Change-Id: Iaf2ef5b5751eb208d119ddbc74481239366fe581
Merged-In: Iaf2ef5b5751eb208d119ddbc74481239366fe581
The NetworkStack.getService() API should be used instead.
Bug: 151243982
Test: atest FrameworksNetTests TetheringTests
Manual tethering test
Change-Id: I7855090bffbe895c8349ad4903b8f2eb55515f0b
am skip reason: Change-Id I9495a198cf247e6c79100f7ac1edcea370b071de with SHA-1 abb0596a0a is in history
Change-Id: I67dd1a6963aa14cf3443af12ba28cd9af74cff44
am skip reason: Change-Id I9495a198cf247e6c79100f7ac1edcea370b071de with SHA-1 abb0596a0a is in history
Change-Id: I214ca8cb07535dbe33be18aa9a49d31811451ff5
am skip reason: Change-Id I9495a198cf247e6c79100f7ac1edcea370b071de with SHA-1 abb0596a0a is in history
Change-Id: I19399123661123386472ff3f39d268d85917cbe1
Currently, in NetworkStats, there are many methods to manipulate
the records. However, some methods are similar and ambiguous,
such as addEntry, addValues, setValues, addIfaceValues,
combineValues and combineAllValues.
Thus, properly grouping and renaming methods are necessary.
In this change, for methods that add one record conditionally,
name them addEntry.
addValues -> addEntry
Test: atest FrameworksNetTests ImsPhoneCallTrackerTest TetheringTests
Fix: 148895143
Change-Id: I9495a198cf247e6c79100f7ac1edcea370b071de
Merged-In: I9495a198cf247e6c79100f7ac1edcea370b071de
(cherry picked from ag/10700816)
am skip reason: Change-Id I141393f229e772d2eb9f7c156849e379bd71b845 with SHA-1 5752baa6b6 is in history
Change-Id: I1ba4a8a293f97fc6739a8cd4e5ba3ac443749180
