With some more testing I found that if you completely close Wazapp and then open it, the cpu usage of the wazapp process stays at zero and the current consumption is fine. However, after sending a single message to myself the cpu usage jumps to around 2% and stays there no matter what you do, and is also accompanied by higher idle current consumption. Sounds like some kind of a bug to me.
@brkn
i'm trying your wazzap autostart script, it works as expected, but there's any way to actually not run the program on top, just start it in the background? Now, i turn on my phone and wazapp just splashes "right in your face" xD
