View Single Post
Scorpius's Avatar
Posts: 1,396 | Thanked: 2,796 times | Joined on Sep 2010 @ Caracas, Venezuela
#2130
Originally Posted by reinob View Post
@Scorpius,

I'd like to ask you about the changes (besides the new encryption protocol) that you had to make in version 0.25.

The reason is that I've noticed a (slightly) higher power consumption with this new version. I've done a few experiments with powertop, and noticed that if I'm not connected (Yappari "waiting for connection") there is no significant increase w.r.t. when Yappari is fully closed.

However when I'm connected (with GPRS, but I think this is irrelevant), Yappari does some activity once per second. This prevents the CPU from going to the C4 state as often as when Yappari is not connected (not connected: C4 ~ 92% when idle, connected: C4 ~ 70% when idle, the rest in C3).

The hardware wakeups go from 1.5 wakeups/s to 4.2 wakeups/s.

It may be that something requires Yappari to do this (for obvious reasons, I cannot look at the source code), but it could also be that you've mistakenly introduced some unnecessary polling.

This is no big deal (I now tend to actively start and close Yappari according to my needs, instead of leaving it always-on), but I'd appreciate it if you could give it a look.

Cheers.
Sadly with the new encryption protocol WhatsApp servers ping the clients every 5 seconds, and Yappari has to answer that or it gets disconnected. That didn't happen in previous protocols. 0.4 (the first one) was the best with pings every 5 minutes.

I don't think I can do anything about it, but if there's something I can do I'd do it, believe me.

You can read the log (try: tail -f ~/.config/scorpius/yappari.log while you're connected) and see it for yourself.
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate

Last edited by Scorpius; 2012-11-02 at 16:18.
 

The Following 3 Users Say Thank You to Scorpius For This Useful Post: