[Announce] Yappari - A WhatsApp Client for the N900 ONLY - Page 213 - maemo.org

lenix | # 2121 | 2012-11-01, 23:06 | Report

Originally Posted by Scorpius View Post

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.

I'm having this problem on a clean flash with CSSU installed.

solbrit | # 2122 | 2012-11-02, 00:38 | Report

Annoying connection problems in v0.0.25... Whenever I go from wifi to gprs or vice versa no more messages can be sent or received although Yappari happily claims it's logged in. Re-syncing the contacts makes it notice the connection change and get it to log in again and all is back to normal. For two minutes until the phone switches connection once and then back again without me noticing and I write a fairly long message which then won't send and can't be copied and thus has to be re-written... Sigh...
I know I'm not the only one here with this problem, but has anyone found a solution? Otherwise I hope Scorpius is on it

Xananax | # 2123 | 2012-11-02, 04:21 | Report

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.

Also, my country is blacklisted on paypal, so if I can contribute some other way, let me know. I can do design work, or send a little something your way (indie game, music album, or any digital gift)

Attached Files

yappari-log.txt (18.2 KB, 433 views)

Last edited by Xananax; 2012-11-02 at 04:25.

Scorpius | # 2124 | 2012-11-02, 04:40 | Report

Originally Posted by Xananax View Post

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.

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)

The Following User Says Thank You to Scorpius For This Useful Post:
Ammar Hamdan

WeASeL... | # 2125 | 2012-11-02, 05:52 | Report

Few Suggestions for upgrades (AWESOME WORK BY THE WAY):

Sending/Receiving Audio files and Video files
Use of Emoticons in the Status
Sharing your location
Ability to save unregistered numbers to Contacts
For Yappari to be recognized as an IM client by the N900 to be included in the "SHARE" feature.
Option to view your current contact list AND Favourites SEPERATELY
Option to INVITE contacts that are not Favourites.

Everybody stated Group Chat so I figured I'd leave it out and be different.

These are just suggestions... I know how tedious programming/coding can be with the resources you have to work with.

GREAT WORK Scorpius.

Xananax | # 2126 | 2012-11-02, 07:24 | Report

I am in Lebanon but it works prefectly well. All my friends are using it; it is what brought me to try to find a solution for my Nokia as they're beggining to plan stuff on it and I am just left out. Furthermore, a friend is (was until recently) using the java port on his N9.

Can I do anything more to help?

If
a) WhatsApp works
and
b) Yappari works

I can only surmize my case is an edge case that uncovers some part of WhatsApp that you didn't need to deal with. Maybe they can confirm with something beside an sms, in certain countries? Maybe for Lebanon, phone numbers are sent differently?
(my number comes in the form [+961][70][123456], knowing that most cellphone numbers here are in the form [+961][3][123456]. I tried [+961][7][xx..] to no avail)

Can I do anything to help speed up my case? I am willing to test stuff, compile custom code, etc.

ixahmd | # 2127 | 2012-11-02, 08:48 | Report

Originally Posted by Scorpius View Post

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)

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.

reinob | # 2128 | 2012-11-02, 09:41 | Report

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

The Following 3 Users Say Thank You to reinob For This Useful Post:
af7567, Duke, mr_pingu

gilesn | # 2129 | 2012-11-02, 11:46 | Report

same problem here, for an NL code

Originally Posted by ixahmd View Post

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.

Scorpius | # 2130 | 2012-11-02, 16:15 | Report

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.

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

The Following 3 Users Say Thank You to Scorpius For This Useful Post:
af7567, nkirk, reinob