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

Scorpius | # 2281 | 2012-11-21, 16:13 | Report

Originally Posted by lenix View Post

Please can anybody answer this question.

If I register on another device and then create Yappari.conf and fill it with the normal information... will it work?

Registering isn't working on Yappari, but I can register normally on my friends iPhone. ( I wish there is a way to input the activation code manually in yappari )

What can I do? Thanks a lot in advance

edit: I'm pretty sure IMEI spoofing will solve every single problem... my wish is IMEI spoofing.. thanks and donation is going to be made soon

It won't work. It's very weird registration doesn't work for you since people have been registering lately using Yappari with no problems.

Also IMEI spoofing won't work to use Yappari in two devices at the same time. IMEI spoofing is just to not use your real IMEI, not to spoof another device.

Now, IMEI spoofing + android=true might spoof an Android device (and it won't always work). Yappari can't spoof iPhones or any other platform.

lenix | # 2282 | 2012-11-21, 17:03 | Report

Originally Posted by Scorpius View Post

It won't work. It's very weird registration doesn't work for you since people have been registering lately using Yappari with no problems.

Also IMEI spoofing won't work to use Yappari in two devices at the same time. IMEI spoofing is just to not use your real IMEI, not to spoof another device.

Now, IMEI spoofing + android=true might spoof an Android device (and it won't always work). Yappari can't spoof iPhones or any other platform.

Thanks for the info,

I said IMEI spoofing would help because I think my IMEI is being blocked from yappari servers, so I can't register anymore. I get "Too many registration attempts. Please try later." and my .log is attached.

I tried to register my # on an iPhone ( that my company uses for development purposes ) and it worked, got the sms and the registration process completed. I think this means that it's something to do with my N900 IMEI.

Thanks for all man,

Attached Files

yappari.log.txt (2.0 KB, 87 views)

Scorpius | # 2283 | 2012-11-21, 18:05 | Report

The error you're getting is that you already registered that phone number in another device. You can't register the same number in two different devices in the same week, or month I guess.

juanroyas2 | # 2284 | 2012-11-22, 00:06 | Report

Hi scorpius!!!

I'm have been getting a bit in my yappari since 01 Nov.. I'm an older user, I have used yappari since july 2012...

The bit is: CONNECTION TIMED OUT...

Here is part of the yappari.log

Thank for the help!!

>> 0
>> 8
>> f80296f801f8017e
lun nov 19 16:07:47 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf

arams:xml:ns:xmpp-sasl

>> 0
>> 7
>> f8050f5a2abda7
There was an IO error: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
connected(): There was an IO Exception: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 10 seconds.
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: 356938037233633
Password: ac1423b8eaf3a636dc97e01f46241e62
>> 57
>> 41
>> 1
>> 1
>> 0
>> 19
>> f8050184fc116950686f6e652d322e382e332d35323232a08a
lun nov 19 16:07:59 2012
<stream:features>
<receipt_acks>

>> 0
>> 8
>> f80296f801f8017e
lun nov 19 16:07:59 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf

arams:xml:ns:xmpp-sasl

>> 0
>> 7
>> f8050f5a2abda7
There was an IO error: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
connected(): There was an IO Exception: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 10 seconds.
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: 356938037233633
Password: ac1423b8eaf3a636dc97e01f46241e62
>> 57
>> 41
>> 1
>> 1
>> 0
>> 19
>> f8050184fc116950686f6e652d322e382e332d35323232a08a
lun nov 19 16:08:10 2012
<stream:features>
<receipt_acks>

>> 0
>> 8
>> f80296f801f8017e
lun nov 19 16:08:10 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf

arams:xml:ns:xmpp-sasl

>> 0
>> 7
>> f8050f5a2abda7
There was an IO error: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
connected(): There was an IO Exception: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 10 seconds.
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: 356938037233633
Password: ac1423b8eaf3a636dc97e01f46241e62
>> 57
>> 41
>> 1
>> 1
>> 0
>> 19
>> f8050184fc116950686f6e652d322e382e332d35323232a08a
lun nov 19 16:08:21 2012
<stream:features>
<receipt_acks>

>> 0
>> 8
>> f80296f801f8017e
lun nov 19 16:08:21 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf

arams:xml:ns:xmpp-sasl

>> 0
>> 7
>> f8050f5a2abda7
There was an IO error: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
connected(): There was an IO Exception: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 10 seconds.
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: 356938037233633
Password: ac1423b8eaf3a636dc97e01f46241e62
>> 57
>> 41
>> 1
>> 1
>> 0
>> 19
>> f8050184fc116950686f6e652d322e382e332d35323232a08a
lun nov 19 16:08:33 2012
<stream:features>
<receipt_acks>

>> 0
>> 8
>> f80296f801f8017e
lun nov 19 16:08:33 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf

arams:xml:ns:xmpp-sasl

>> 0
>> 7
>> f8050f5a2abda7
There was an IO error: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
connected(): There was an IO Exception: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 10 seconds.
User has quit the application
Application destroyed
Reading roster DB...
Roster retrieved in 559 milliseconds.
Yappari 0.0.23 Build 2259
Yappari console test client start
Network connection changed: Online
Current active connection: 084036a5-0703-44f8-8384-a2077a7e3e77
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: 356938037233633
Password: ac1423b8eaf3a636dc97e01f46241e62
>> 57
>> 41
>> 1
>> 1
>> 0
>> 19
>> f8050184fc116950686f6e652d322e382e332d35323232a08a
mar nov 20 22:51:06 2012
<stream:features>
<receipt_acks>

>> 0
>> 8
>> f80296f801f8017e
mar nov 20 22:51:06 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf

arams:xml:ns:xmpp-sasl

>> 0
>> 7
>> f8050f5a2abda7
There was an IO error: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
connected(): There was an IO Exception: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 10 seconds.
User has quit the application
Application destroyed
Reading roster DB...
Roster retrieved in 234 milliseconds.
Yappari 0.0.23 Build 2259
Yappari console test client start
Network connection changed: Online
Current active connection: 084036a5-0703-44f8-8384-a2077a7e3e77
Connecting to bin-short.whatsapp.net:5222 ...
Connected successfully
IMEI: 356938037233633
Password: ac1423b8eaf3a636dc97e01f46241e62
>> 57
>> 41
>> 1
>> 1
>> 0
>> 19
>> f8050184fc116950686f6e652d322e382e332d35323232a08a
mié nov 21 18:47:19 2012
<stream:features>
<receipt_acks>

>> 0
>> 8
>> f80296f801f8017e
mié nov 21 18:47:19 2012
<auth>
mechanism=DIGEST-MD5-1
xmlns=urn:ietf

arams:xml:ns:xmpp-sasl

>> 0
>> 7
>> f8050f5a2abda7
There was an IO error: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
connected(): There was an IO Exception: Connection timed out
Connection closed.
Stopping timers.
Freeing up the connection.
Yappari will retry the connection in 10 seconds.
User has quit the application
Application destroyed

Scorpius | # 2285 | 2012-11-22, 00:27 | Report

Originally Posted by juanroyas2 View Post

Hi scorpius!!!

I'm have been getting a bit in my yappari since 01 Nov.. I'm an older user, I have used yappari since july 2012...

The bit is: CONNECTION TIMED OUT...

It looks you don't use it too much since you are using a very outdated version. Just upgrade Yappari to the latest version. Links as usual are in the first post.

jellyroll | # 2286 | 2012-11-22, 02:06 | Report

- Support of other multimedia messages.

rayson | # 2287 | 2012-11-22, 07:15 | Report

Originally Posted by em28 View Post

where is the tappari.conf located ?
can't find it on my device.

check the first page will see

save you the time :- \home\user\.config\scorpius

ename | # 2288 | 2012-11-22, 11:09 | Report

Great work, thanks

Fallingwater | # 2289 | 2012-11-22, 13:16 | Report

I'm having issues with connecting via mobile. If the phone is connected with wifi Yappari works, if it's connected with 2G/3G it gets stuck at "connecting". I can access the internet while it's stuck, so I don't think it's a connection problem. Here's the log:

Originally Posted by

Reading roster DB...
Roster retrieved in 88 milliseconds.
Yappari 0.0.25 Build 2455
Yappari console test client start
Network connection changed: Online
Current active connection: <removed for privacy>
Connecting to bin-short.whatsapp.net:5222 ...

It stays that way until I kill it.

Scorpius | # 2290 | 2012-11-22, 13:31 | Report

Originally Posted by Fallingwater View Post

I'm having issues with connecting via mobile. If the phone is connected with wifi Yappari works, if it's connected with 2G/3G it gets stuck at "connecting". I can access the internet while it's stuck, so I don't think it's a connection problem. Here's the log:

It stays that way until I kill it.

Your cell phone provider blocked outgoing connections to port 5222. In the next release the default port is 443 and you can change it back to 5222. That will solve your problem.

The thing is that I've been extremely busy at work and I haven't been able to finish it.

The Following 3 Users Say Thank You to Scorpius For This Useful Post:
davdav, ersanpermana, Tschaka