907e01eb7083c54aa1e840ea4e76a6518a028a72
We've seen case of it taking longer than 1500ms for the wifi system to actually shut down after the triggering settings element is written, so extend the wait time a bit. We've seen it take more than 1500ms but not more than 2500ms, so that's the new heuristic. This will of course all become happily obsolete once we start applying restored AP definitions programmatically rather than by filesystem-level operations. Bug 22979342 Change-Id: I6acf1baac23d4100124093128b82abf242b11a0e
Merge "Fix issue #22843150: fragment transaction crash from onRequestPermisssionResult" into mnc-dev
Revert "am
1c964bec: Revert "am 6397ae6a: Merge "Update data binding for RC1." into mnc-preview-docs""
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%