f4ffaa4f57a8af4452f27e47ca65ee85fa0a60dc
Now that the delay between connectivity changes and CONNECTIVITY_ACTION has been removed (ag/599650) races between CONNECTIVITY_ACTION and the setting of the default network become more evident. In http://crbug.com/441818 Chrome is calling getaddrinfo() immediately after a device goes from no connectivity to cellular connectivity, and Chrome is erroneously getting back EAI_NODATA because netd hasn't yet set the default network for DNS resolutions. bug:18757162 Change-Id: Ib607dcb3697403272a8c838713a9cb602e9c6820
am
5fed49f7: am 4d9fcae2: Merge "Allow for a NoOp implementation of DrmManagerClientImpl" into klp-modular-dev
cherrypick from ics-mr1 docs: source for nw app Change-Id: If50f407a0e56fa802fe9beedaa650e3a131872b2
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%