As the title says, sometimes the end of call is not detected, and recording continues on for hours, while seriously draining the battery, and ACR shows up in the Battery usage settings as higher then Screen.
I recently made a 21-hour and 11-hour accidental recording.
My phone is galaxy note 3 with bad kitkat upgrade using the MIC input source. ACR version is 8.6.
How are you detecting the end of a call? are you using PhoneStateListener? If this is not an ACR bug, but a phone bug not delivering a phone state change callback sometimes, then you may be able to work around this bug by periodically checking the phone state at least every minute, while recording is on.
Just in case the start of the call callback is also not delivered, you could also poll for that, but without requesting a wakelock. That shouldn't consume too much power.