Notices

Originally Posted by Scorpius

The people that are getting crashes while registering please install CSSU and try again when you can (you have to wait for several minutes). All the logs uploaded here show that Yappari closed while waiting for the SMS. I want to discard an old Qt bug.

Originally Posted by Xananax

Yo,

It's not always crashing.
Now what I get is "confirmation SMS was never received" after 300 seconds of waiting.
I don't know if that helps.

Originally Posted by Scorpius

And did you get the SMS? Because the WhatsApp server confirmed it sent it to you (or at least tried).

Are you sure WhatsApp works fine in your country? It doesn't work in every country on the planet (I know it doesn't work in Syria or something)

Originally Posted by ixahmd

I am using this in US and this is what my log shows.

Code:

Reading roster DB...
Roster retrieved in 6 milliseconds.
Yappari 0.0.25 Build 2455
Yappari console test client start
Network connection changed: Online
Current active connection: a19c3549-87f0-4ce0-9c4d-5ee926adaee3
Registration started
Country code: US
reg/req/exists/start
IMEI: xxxxx
Request: https://r.whatsapp.net/v1/exist.php?cc=1&in=4847166080&udid=18a0775a7d6f056ae551af398e645cd&
Network activated: a19c3549-87f0-4ce0-9c4d-5ee926adaee3
Network activated: a19c3549-87f0-4ce0-9c4d-5ee926adaee3
Reply: <?xml version="1.0" encoding="UTF-8"?>
<exist>
<response status="fail" result="incorrect"/>
</exist>
X-Powered-By: PHP/5.3.5
Content-Type: text/xml
Connection: close
Transfer-Encoding: chunked
Date: Thu, 01 Nov 2012 09:29:29 GMT
Server: lighttpd/1.4.28
reg/req/exists/fail: incorrect
User 1xxxxxxxxxx is not registered.
reg/req/self/start
IMEI: xxxx
Request: https://r.whatsapp.net/v1/code.php?cc=1&in=0000000000&to=10000000000&lg=en&lc=US&mcc=310&mnc=260&method=self&imsi=310260911209291&token=7ea8adc22f1f1afca09999b8046bb770&udid=18a0775a7d6f056ae551af398e645cd&
Network activated: a19c3549-87f0-4ce0-9c4d-5ee926adaee3
Network activated: a19c3549-87f0-4ce0-9c4d-5ee926adaee3
Reply: <?xml version="1.0" encoding="UTF-8"?>
<code>
<response status="fail-temporarily-unavailable"/>
</code>

Hope this helps.

Originally Posted by reinob

@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.