I use CSipSimple on several devices, and always with the exact same configuration.
Some configuration details: Version 1.02.03, Integrate with Android, Only for outgoing, UDP only, Only "Wifi for outgoing calls" is checked under Network.
I have the following observation:
On all devices, after a fresh boot, and CSipSimple installed but no call having been placed, power consumption is, say, 0.5% per hour (screen turned off, phone left alone untouched).
On e.g. an htc Desire X (Stock Android 4.1.1), this does not change after I place a call with CSipSimple and hang up again
But on a Samsung S4 Mini (Stock Android 4.4.2) the following happens 100% reproducibly: After placing a call with CSipSimple and hanging up again, the battery consumption of the phone rises ten-fold to about 5% per hour (phone again left alone in sleep mode and not touched). The issue seems to affect several Samsung models in particular.
When checking what causes the excessive battery drain under Android's Settings/Battery, it is not attributed to "CSipSimple", but actually to "Android OS", where you can see that the CPU constantly remains in "Awake" state after the first call with CSIPSimple. ("CPU Awake" time indicator constantly going up if checked periodically).
Interestingly: I have found out that briefly starting Android's built-in Music player, then stopping and closing it again, again allows the CPU to go back to deep sleep when the screen is turned off, and the excessive battery drain initiated by CSIPsimple is stopped again (until another cal is placed using CSIpSimple).
So it looks like we may be looking at an issue with some sort of audio wakelock remaining active after a CSipSimple call, particularly on Samsung devices. I am wondering if there could be a fix or workaround implemented in CSipSimple?
I use CSipSimple on several devices, and always with the exact same configuration.
Some configuration details: Version 1.02.03, Integrate with Android, Only for outgoing, UDP only, Only "Wifi for outgoing calls" is checked under Network.
I have the following observation:
When checking what causes the excessive battery drain under Android's Settings/Battery, it is not attributed to "CSipSimple", but actually to "Android OS", where you can see that the CPU constantly remains in "Awake" state after the first call with CSIPSimple. ("CPU Awake" time indicator constantly going up if checked periodically).
Interestingly: I have found out that briefly starting Android's built-in Music player, then stopping and closing it again, again allows the CPU to go back to deep sleep when the screen is turned off, and the excessive battery drain initiated by CSIPsimple is stopped again (until another cal is placed using CSIpSimple).
So it looks like we may be looking at an issue with some sort of audio wakelock remaining active after a CSipSimple call, particularly on Samsung devices. I am wondering if there could be a fix or workaround implemented in CSipSimple?