314f51e80df91d6dbd5315d3bccdf502cb85e388
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
Description
android_packages_modules_Connectivity
Languages
Java
81.4%
Kotlin
7.7%
AIDL
4.5%
C++
4.5%
C
1.7%
Other
0.1%