Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 3 days, 9 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 5 days, 6 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 6 days, 3 hrs ago - more...
legendracer |
2015-09-04
, 03:42
|
|
Posts: 176 |
Thanked: 21 times |
Joined on Feb 2013
|
#1081
|
ok...registered using friend's mobile.then he registered his number...then i logged in yappari. no registration asked...came for 30 seconds...went to background. status showed disconnected. what next?i think im not banned.
|
|
2015-09-04
, 03:44
|
|
Posts: 176 |
Thanked: 21 times |
Joined on Feb 2013
|
#1082
|
i received messages as usual in his mobile. but in yappari nothing.
|
|
2015-09-04
, 04:05
|
|
Posts: 176 |
Thanked: 21 times |
Joined on Feb 2013
|
#1083
|
Yappari 2.0.16 Build 5217
Yappari console debug start
Reading roster DB...
Roster retrieved in 435 milliseconds.
Resetting timestamps at 1441339260104
Next run in 52139896
Reading open chats DB...
Open Chats retrieved in 3 milliseconds.
Entry retrieved: 91-1379508434@g.us
Entry retrieved: 918@s.whatsapp.net
Entry retrieved: 96@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Entry retrieved: 9@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Network connection changed: Online
Current active connection: b8c53e46-2b7f-4296-a082-7f336ca84a8c
Connecting to c.whatsapp.net:443...
Connected successfully
OUTGOING:
<stream:features>
<groups_v2>
<presence>
<privacy>
<readreceipts>
OUTGOING:
<auth>
mechanism=WAUTH-2
passive=false
user=919496092168
INCOMING:
<stream:start>
from=s.whatsapp.net
INCOMING:
<stream:features>
INCOMING:
<challenge>
Content of type challenge length: 20
OUTGOING:
<response>
Content of type response length: 46
There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
Yappari 2.0.16 Build 5217
Yappari console debug start
Reading roster DB...
Roster retrieved in 531 milliseconds.
Resetting timestamps at 1441339286315
Next run in 52113685
Reading open chats DB...
Open Chats retrieved in 4 milliseconds.
Entry retrieved: 91-1379508434@g.us
Entry retrieved: 918@s.whatsapp.net
Entry retrieved: 96.@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 9197@s.whatsapp.net
Entry retrieved: 91828@s.whatsapp.net
Network connection changed: Online
Current active connection: b8c53e46-2b7f-4296-a082-7f336ca84a8c
Connecting to c.whatsapp.net:443...
Connected successfully
OUTGOING:
<stream:features>
<groups_v2>
<presence>
<privacy>
<readreceipts>
OUTGOING:
<auth>
mechanism=WAUTH-2
passive=false
user=919496092168
INCOMING:
<stream:start>
from=s.whatsapp.net
INCOMING:
<stream:features>
INCOMING:
<challenge>
Content of type challenge length: 20
OUTGOING:
<response>
Content of type response length: 46
There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
Yappari 2.0.16 Build 5217
Yappari console debug start
Reading roster DB...
Roster retrieved in 435 milliseconds.
Resetting timestamps at 1441339307881
Next run in 52092119
Reading open chats DB...
Open Chats retrieved in 4 milliseconds.
Entry retrieved: 91-1379508434@g.us
Entry retrieved: 9182@s.whatsapp.net
Entry retrieved: 9659@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919473@s.whatsapp.net
Entry retrieved: 919573@s.whatsapp.net
Entry retrieved: 919992@s.whatsapp.net
Entry retrieved: 9197443@s.whatsapp.net
Entry retrieved: 9182@s.whatsapp.net
Network connection changed: Offline
User has quit the application
Application destroyed
Yappari console debug start
Reading roster DB...
Roster retrieved in 435 milliseconds.
Resetting timestamps at 1441339260104
Next run in 52139896
Reading open chats DB...
Open Chats retrieved in 3 milliseconds.
Entry retrieved: 91-1379508434@g.us
Entry retrieved: 918@s.whatsapp.net
Entry retrieved: 96@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Entry retrieved: 9@s.whatsapp.net
Entry retrieved: 91@s.whatsapp.net
Network connection changed: Online
Current active connection: b8c53e46-2b7f-4296-a082-7f336ca84a8c
Connecting to c.whatsapp.net:443...
Connected successfully
OUTGOING:
<stream:features>
<groups_v2>
<presence>
<privacy>
<readreceipts>
OUTGOING:
<auth>
mechanism=WAUTH-2
passive=false
user=919496092168
INCOMING:
<stream:start>
from=s.whatsapp.net
INCOMING:
<stream:features>
INCOMING:
<challenge>
Content of type challenge length: 20
OUTGOING:
<response>
Content of type response length: 46
There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
Yappari 2.0.16 Build 5217
Yappari console debug start
Reading roster DB...
Roster retrieved in 531 milliseconds.
Resetting timestamps at 1441339286315
Next run in 52113685
Reading open chats DB...
Open Chats retrieved in 4 milliseconds.
Entry retrieved: 91-1379508434@g.us
Entry retrieved: 918@s.whatsapp.net
Entry retrieved: 96.@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 9197@s.whatsapp.net
Entry retrieved: 91828@s.whatsapp.net
Network connection changed: Online
Current active connection: b8c53e46-2b7f-4296-a082-7f336ca84a8c
Connecting to c.whatsapp.net:443...
Connected successfully
OUTGOING:
<stream:features>
<groups_v2>
<presence>
<privacy>
<readreceipts>
OUTGOING:
<auth>
mechanism=WAUTH-2
passive=false
user=919496092168
INCOMING:
<stream:start>
from=s.whatsapp.net
INCOMING:
<stream:features>
INCOMING:
<challenge>
Content of type challenge length: 20
OUTGOING:
<response>
Content of type response length: 46
There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
Yappari 2.0.16 Build 5217
Yappari console debug start
Reading roster DB...
Roster retrieved in 435 milliseconds.
Resetting timestamps at 1441339307881
Next run in 52092119
Reading open chats DB...
Open Chats retrieved in 4 milliseconds.
Entry retrieved: 91-1379508434@g.us
Entry retrieved: 9182@s.whatsapp.net
Entry retrieved: 9659@s.whatsapp.net
Entry retrieved: 919@s.whatsapp.net
Entry retrieved: 919473@s.whatsapp.net
Entry retrieved: 919573@s.whatsapp.net
Entry retrieved: 919992@s.whatsapp.net
Entry retrieved: 9197443@s.whatsapp.net
Entry retrieved: 9182@s.whatsapp.net
Network connection changed: Offline
User has quit the application
Application destroyed
|
|
2015-09-04
, 08:11
|
|
Community Council |
Posts: 680 |
Thanked: 1,227 times |
Joined on Sep 2010
@ Mbabane
|
#1084
|
You are playing a "dangerous" game using one number on two devices back and forth.
It does look like you're not banned yet.
I would say delete the whole /home/user/.yappari directory, and also /home/user/.config/scorpius.
Re-register and see what happens. Do not keep moving the number/SIM across the two devices.
One more thing: your friends/contacts will appreciate it if you obscure their numbers
before submitting your post, maybe replace them with XXXXX like others have done? We're not bad people, but this is a public forum that even gets crawled by Google, etc.
It does look like you're not banned yet.
I would say delete the whole /home/user/.yappari directory, and also /home/user/.config/scorpius.
Re-register and see what happens. Do not keep moving the number/SIM across the two devices.
One more thing: your friends/contacts will appreciate it if you obscure their numbers
before submitting your post, maybe replace them with XXXXX like others have done? We're not bad people, but this is a public forum that even gets crawled by Google, etc.
| The Following 4 Users Say Thank You to sicelo For This Useful Post: | ||
|
|
2015-09-04
, 09:16
|
|
Posts: 176 |
Thanked: 21 times |
Joined on Feb 2013
|
#1085
|
Originally Posted by sicelo
You are playing a "dangerous" game using one number on two devices back and forth.
.
no fear since you guys are there... BTW it worked when i deleted everything and reinstalled... thanks.... works wierdly.... so different from android and windows... but it works... gotta learn...thanks brothers. keep up the spirit...i kept this phone for 1 year only because you guys are there.....
|
|
2015-09-04
, 10:18
|
|
Posts: 176 |
Thanked: 21 times |
Joined on Feb 2013
|
#1087
|
1. cant see group profile icons. shows blue icons for all. but for individual contacts it shows images.
2. if i click new message notifications, it closes. gotta open yappari to view.
3.in background i think yappari doesnt work. when i open it, shows, connecting then logged in.
2. if i click new message notifications, it closes. gotta open yappari to view.
3.in background i think yappari doesnt work. when i open it, shows, connecting then logged in.
|
|
2015-09-04
, 10:48
|
|
Posts: 176 |
Thanked: 21 times |
Joined on Feb 2013
|
#1088
|
can we not send images and files through yappari? i can receive files though...
|
|
2015-09-04
, 20:57
|
|
Posts: 13 |
Thanked: 26 times |
Joined on Sep 2015
@ Prague
|
#1089
|
Hi there,
I'm unable to receive private messages as already discussed in this thread earlier.
According to the log file below yappari receive the incoming message but it do not show it on screen for some reason.
My friend received my messages, I can see that he is typing but his reply isn't shown in yappari.
It is same with yappari 2.0.15 and 2.0.16.
I deleted .yappari and .config/scorpius but it didn't help.
Did anyone who went through the same managed to solve this problem?
Thanks
I'm unable to receive private messages as already discussed in this thread earlier.
According to the log file below yappari receive the incoming message but it do not show it on screen for some reason.
My friend received my messages, I can see that he is typing but his reply isn't shown in yappari.
It is same with yappari 2.0.15 and 2.0.16.
I deleted .yappari and .config/scorpius but it didn't help.
Did anyone who went through the same managed to solve this problem?
Thanks
Code:
Message ID 1441392409-4
OUTGOING:
<message>
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=text
<body>
Nainstaloval jsem novou verzi WA klienta, tak to snad pomuze..
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
INCOMING:
<ack>
class=message
from=420XXXXXXXXX@s.whatsapp.net
id=1441392409-4
t=1441392412
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
INCOMING:
<receipt>
from=420XXXXXXXXX@s.whatsapp.net
id=y9s3yZlThnhY3
t=1441392437
type=read
Message id=y9s3yZlThnhY3, Recovered id=
No chat for found.
Initializing logger for
Logger for initialized successfully. LastId: -1
logMessage():
logMessage():
OUTGOING:
<ack>
class=receipt
id=y9s3yZlThnhY3
to=420XXXXXXXXX@s.whatsapp.net
type=read
INCOMING:
<presence>
from=420XXXXXXXXX@s.whatsapp.net
Updating contact 420XXXXXXXXX@s.whatsapp.net
INCOMING:
<receipt>
from=420XXXXXXXXX@s.whatsapp.net
id=1441392409-4
t=1441392438
Message id=1441392409-4, Recovered id=1441392409-4
Marking message as received by target
Message not finished, moving back to store
OUTGOING:
<ack>
class=receipt
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=delivered
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
OUTGOING:
<ack>
class=receipt
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=delivery
INCOMING:
<receipt>
from=420XXXXXXXXX@s.whatsapp.net
id=1441392409-4
t=1441392438
type=read
Message id=1441392409-4, Recovered id=1441392409-4
Marking message as read by target
Message not finished, moving back to store
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
OUTGOING:
<ack>
class=receipt
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=read
INCOMING:
<chatstate>
from=420XXXXXXXXX@s.whatsapp.net
<composing>
INCOMING:
<message>
from=420XXXXXXXXX@s.whatsapp.net
id=1441390922-119
notify=Vladimir
t=1441392445
type=text
<enc>
type=msg
v=1
3
!•J…ž7ĂƒÂ˝.nĂƒÂ®GĂ‚Âś. Ă‚Â˛ĂƒÂ©yMjĂ‚Â¶Ă‚Â¤Ă‚Â”Ă‚ÂĽĂ‚ÂŞĂƒÂś(g
parseMessageInitialTagAlreadyChecked
INCOMING:
<chatstate>
from=420XXXXXXXXX@s.whatsapp.net
<composing>
INCOMING:
<message>
from=420XXXXXXXXX@s.whatsapp.net
id=1441390922-121
notify=Vladimir
t=1441392451
type=text
<enc>
type=msg
v=1
3
!•J…ž7ĂƒÂ˝.nĂƒÂ®GĂ‚Âś. Ă‚Â˛ĂƒÂ©yMjĂ‚Â¶Ă‚Â¤Ă‚Â”Ă‚ÂĽĂ‚ÂŞĂƒÂś(g*"DĂ‚ÂšĂƒÂ•ĂƒÂ—Ă‚Â*Ă‚Â‰ĂƒÂŞĂ‚ÂżĂƒÂ±ĂƒÂ—ĂƒÂ˛Ă‚Â˛{v8[8Kwy®m
parseMessageInitialTagAlreadyChecked
INCOMING:
<chatstate>
from=420XXXXXXXXX@s.whatsapp.net
<composing>
INCOMING:
<message>
from=420XXXXXXXXX@s.whatsapp.net
id=1441390922-123
notify=Vladimir
t=1441392457
type=text
<enc>
type=msg
v=1
3
!•J…ž7ĂƒÂ˝.nĂƒÂ®GĂ‚Âś. Ă‚Â˛ĂƒÂ©yMjĂ‚Â¶Ă‚Â¤Ă‚Â”Ă‚ÂĽĂ‚ÂŞĂƒÂś(g" .Ă‚ÂŁĂƒÂ©ĂƒÂ›;ĂƒÂ¬lĂƒÂ‘Ă‚Â¨ĂƒÂ˘ĂƒÂŽĂ‚ÂšĂ‚ÂŞĂƒÂ™ ^ĂƒÂ¤Ă‚Âş
parseMessageInitialTagAlreadyChecked
INCOMING:
<presence>
from=420XXXXXXXXX@s.whatsapp.net
last=1441392503
type=unavailable
Updating contact 420XXXXXXXXX@s.whatsapp.net
Updating contact 420XXXXXXXXX@s.whatsapp.net
INCOMING:
<stream:error>
<ack>
INCOMING:
<stream:close>
There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
|
|
2015-09-04
, 22:11
|
|
Posts: 13 |
Thanked: 26 times |
Joined on Sep 2015
@ Prague
|
#1090
|
Hi there,
I'm unable to receive private messages as already discussed in this thread earlier.
According to the log file below yappari receive the incoming message but it do not show it on screen for some reason.
My friend received my messages, I can see that he is typing but his reply isn't shown in yappari.
It is same with yappari 2.0.15 and 2.0.16.
I deleted .yappari and .config/scorpius but it didn't help.
Did anyone who went through the same managed to solve this problem?
Thanks
I'm unable to receive private messages as already discussed in this thread earlier.
According to the log file below yappari receive the incoming message but it do not show it on screen for some reason.
My friend received my messages, I can see that he is typing but his reply isn't shown in yappari.
It is same with yappari 2.0.15 and 2.0.16.
I deleted .yappari and .config/scorpius but it didn't help.
Did anyone who went through the same managed to solve this problem?
Thanks
Code:
Message ID 1441392409-4
OUTGOING:
<message>
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=text
<body>
Nainstaloval jsem novou verzi WA klienta, tak to snad pomuze..
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
INCOMING:
<ack>
class=message
from=420XXXXXXXXX@s.whatsapp.net
id=1441392409-4
t=1441392412
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
INCOMING:
<receipt>
from=420XXXXXXXXX@s.whatsapp.net
id=y9s3yZlThnhY3
t=1441392437
type=read
Message id=y9s3yZlThnhY3, Recovered id=
No chat for found.
Initializing logger for
Logger for initialized successfully. LastId: -1
logMessage():
logMessage():
OUTGOING:
<ack>
class=receipt
id=y9s3yZlThnhY3
to=420XXXXXXXXX@s.whatsapp.net
type=read
INCOMING:
<presence>
from=420XXXXXXXXX@s.whatsapp.net
Updating contact 420XXXXXXXXX@s.whatsapp.net
INCOMING:
<receipt>
from=420XXXXXXXXX@s.whatsapp.net
id=1441392409-4
t=1441392438
Message id=1441392409-4, Recovered id=1441392409-4
Marking message as received by target
Message not finished, moving back to store
OUTGOING:
<ack>
class=receipt
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=delivered
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
OUTGOING:
<ack>
class=receipt
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=delivery
INCOMING:
<receipt>
from=420XXXXXXXXX@s.whatsapp.net
id=1441392409-4
t=1441392438
type=read
Message id=1441392409-4, Recovered id=1441392409-4
Marking message as read by target
Message not finished, moving back to store
Chat for 420XXXXXXXXX@s.whatsapp.net found.
logMessage():
UPDATING receipts
logMessage():
OUTGOING:
<ack>
class=receipt
id=1441392409-4
to=420XXXXXXXXX@s.whatsapp.net
type=read
INCOMING:
<chatstate>
from=420XXXXXXXXX@s.whatsapp.net
<composing>
INCOMING:
<message>
from=420XXXXXXXXX@s.whatsapp.net
id=1441390922-119
notify=Vladimir
t=1441392445
type=text
<enc>
type=msg
v=1
3
!•J…ž7ĂƒÂ˝.nĂƒÂ®GĂ‚Âś. Ă‚Â˛ĂƒÂ©yMjĂ‚Â¶Ă‚Â¤Ă‚Â”Ă‚ÂĽĂ‚ÂŞĂƒÂś(g
parseMessageInitialTagAlreadyChecked
INCOMING:
<chatstate>
from=420XXXXXXXXX@s.whatsapp.net
<composing>
INCOMING:
<message>
from=420XXXXXXXXX@s.whatsapp.net
id=1441390922-121
notify=Vladimir
t=1441392451
type=text
<enc>
type=msg
v=1
3
!•J…ž7ĂƒÂ˝.nĂƒÂ®GĂ‚Âś. Ă‚Â˛ĂƒÂ©yMjĂ‚Â¶Ă‚Â¤Ă‚Â”Ă‚ÂĽĂ‚ÂŞĂƒÂś(g*"DĂ‚ÂšĂƒÂ•ĂƒÂ—Ă‚Â*Ă‚Â‰ĂƒÂŞĂ‚ÂżĂƒÂ±ĂƒÂ—ĂƒÂ˛Ă‚Â˛{v8[8Kwy®m
parseMessageInitialTagAlreadyChecked
INCOMING:
<chatstate>
from=420XXXXXXXXX@s.whatsapp.net
<composing>
INCOMING:
<message>
from=420XXXXXXXXX@s.whatsapp.net
id=1441390922-123
notify=Vladimir
t=1441392457
type=text
<enc>
type=msg
v=1
3
!•J…ž7ĂƒÂ˝.nĂƒÂ®GĂ‚Âś. Ă‚Â˛ĂƒÂ©yMjĂ‚Â¶Ă‚Â¤Ă‚Â”Ă‚ÂĽĂ‚ÂŞĂƒÂś(g" .Ă‚ÂŁĂƒÂ©ĂƒÂ›;ĂƒÂ¬lĂƒÂ‘Ă‚Â¨ĂƒÂ˘ĂƒÂŽĂ‚ÂšĂ‚ÂŞĂƒÂ™ ^ĂƒÂ¤Ă‚Âş
parseMessageInitialTagAlreadyChecked
INCOMING:
<presence>
from=420XXXXXXXXX@s.whatsapp.net
last=1441392503
type=unavailable
Updating contact 420XXXXXXXXX@s.whatsapp.net
Updating contact 420XXXXXXXXX@s.whatsapp.net
INCOMING:
<stream:error>
<ack>
INCOMING:
<stream:close>
There was an IO error: Connection closed by server.
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.
