Split out connectivity APIs to connectivity module directories. This prepares future move of the connectivity code into a mainline module, but still keeps it implemented by framework-minus-apex for now: the API stubs are moved to framework-connectivity.stubs, but the implementation on device remains in the same place. This allows moving the connectivity code in/out of APEX with minimal changes. BYPASS_INCLUSIVE_LANGUAGE_REASON=Moving files, can't modify released API Bug: 171540887 Test: device boots, connectivity working Merged-In: I21c42f032efa6c10e36c749df3183ce9679303a7 (cherry-pick from internal branch with API files conflicts) Change-Id: I21c42f032efa6c10e36c749df3183ce9679303a7
5 lines
231 B
Plaintext
5 lines
231 B
Plaintext
// Baseline format: 1.0
|
|
VisiblySynchronized: android.net.NetworkInfo#toString():
|
|
Internal locks must not be exposed (synchronizing on this or class is still
|
|
externally observable): method android.net.NetworkInfo.toString()
|