A little daemon listening to dbus shouldn't cause any major slowdowns/increased battery drain - many programs are doing it without issues (proximityd, for example). The real CPU/Memory hog starts - obviously - when audio is recorded, i.e. during a call Although, AIUI, it would automatically stop (and main application get terminated, leaving only daemon alive, again) after conversation ends.

Considering, that talking via GSM/VoIP is already a huge battery draining operation, it shouldn't cause *dramatic* decrease of battery life (although, some visible one for sure). It is acceptable tradeoff IMO, especially, that people activating automatic recording should be aware of it (and can be made aware via wiki page/application description in repos). Only possible caveat lies in bugs, that could interfere with recording/main program termination - that would be standby time killer. But, it's what we (beta testers) are for

BTW, when we are at it - pretty please, *if* it moves along, don't forget about SIP (VoIP) calls. Recaller ignored them hapilly, lazy bastard.

/Estel