well as i see the conversation problem must not be caused by batterypatch
because the last change i did was only fixing a process stop script
and none of the processes are related to conversation

i personally had this problem before
but after i cleaned the whole database i didn't have that problem again

and don_falcone said he's having the problem from time to time
and he is not using batterypatch

my best guess is that the problem caused by CSSU update

try this