71678ddcc45d9cd4557f3bed8bba5382bf36b68b
The way StrictMode is used during development, just dropboxing violations, could be a little more optimal, taking the ActivityManagerService call off the main thread. But we can only do this safely in the case where that's the only penalty. Data suggests this call, despite being async, still takes around 30 milliseconds. This isn't a major win, and arguably it might be a _better_ idea to slow down people's event loops more and further jank up their animations on violations, but I thought any less overhead from StrictMode, the better. Change-Id: Iad9cce1cb4a084fa64abc4b5e1b4f3bff6a08c94
am
d4d3f36f
: am 1257d330
: Merge "Clean up pending sessions on incoming call in SipService" into gingerbread
am
38476ef2
: am 8f1e7b62
: Merge "Cleanspec to fix incremental build failures of the form:" into gingerbread
Description
No description provided
Languages
Java
77.3%
Kotlin
9.2%
PowerBuilder
6.6%
C++
5.5%
AIDL
1%