Peter Cai
437002d189
onDisconnect() will only be called when the user manually requests a disconnect. When the call is disconnected by the rtp connection itself, the call won't be cleaned up and the system will be stuck in an in-call state. Handle this correctly by moving the clean-up code to a close() function, and calling that function instead when we disconnect. Note that we cannot call the cleanup routine destroy() from the onStateChanged() function, because it seems that this triggers a deadlock somewhere down the line, probably in the calling account-related telephony code. Doing a close() function mirrors what is done in the default TelephonyConnection implementation for RIL-based calls. |
||
---|---|---|
.builds | ||
.github | ||
.tx | ||
art | ||
fastlane/metadata/android/en-US | ||
gradle/wrapper | ||
src | ||
.gitignore | ||
build.gradle | ||
CHANGELOG.md | ||
conversations.doap | ||
gradle.properties | ||
gradlew | ||
gradlew.bat | ||
LICENSE | ||
proguard-rules.pro | ||
README.md | ||
screenshots.png | ||
screenshots.xcf | ||
settings.gradle |
Cheogram Android
This is a fork of Conversations to implement features of use to the Sopranica project.