summaryrefslogtreecommitdiff
path: root/java/com/android/voicemail/impl/sync/VvmNetworkRequest.java
Commit message (Collapse)AuthorAgeFilesLines
* Wait for IPv4 before sending VVM requests.Wei He2021-06-011-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | Precondition to reproduce: - Attached to a network where IPv6 arrives before IPv4 - WiFi is On - Mobile always-on is Disabled (that's default setting) - VVM server is IPV4 only What happened: - VVM sync failed with DATA_CANNOT_RESOLVE_HOST_ON_NETWORK Root Cause: - With above precondition, there will be >50% possibility that when App requests Cellular Data Network, IPV6 address will be reported a few millis before IPV4. This is causing the App to try using IPV6 address (when IPV6 comes first) to query the VVM Server DNS and as the VVM Server is an IPv4 one, it's possible to stabilish a route. Solution: - When App requests Cellular Data Network, if IPV6 network address arrives first, just wait up to 0.5 sec to do DNS query, so we're sure there's enough time to IPv4 address to be available. Bug: 183967989 Change-Id: I8af48b71ec9d6699f604a9db87bb0a77fa4379ca
* Remove redundant @TargetApi, @RequiresApi and @SuppressWarningslinyuh2018-06-281-1/+0
| | | | | | Test: Existing tests PiperOrigin-RevId: 202589482 Change-Id: I6982e4069d30032bf46caf3c9984dfc0e7196f6f
* Remove field prefixes.linyuh2017-12-271-10/+10
| | | | | | Test: Existing tests PiperOrigin-RevId: 180230450 Change-Id: I0b2589cfeeaef81e42a04efa48af24b4e4d0e95f
* Update Dialer source from latest green build.Eric Erfanian2017-03-151-0/+120
* Refactor voicemail component * Add new enriched calling components Test: treehugger, manual aosp testing Change-Id: I521a0f86327d4b42e14d93927c7d613044ed5942