Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 9 hrs, 54 mins ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 9 hrs, 58 mins ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 15 hrs, 17 mins ago -
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 1 day, 15 hrs ago -
Maemo repository (5)
to Community by dredlok706 - 3 days, 10 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 3 days, 13 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 4 days, 6 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 5 days, 18 hrs ago - more...
| The Following User Says Thank You to Fatalist For This Useful Post: | ||
|
2015-07-08
, 19:54
|
|
Community Council |
Posts: 691 |
Thanked: 1,240 times |
Joined on Sep 2010
@ Mbabane
|
#982
|
mine worked again after about 6 hours, and 30 minutes later disconnects again (first time was 30 minutes too, conincidentally).
i'm waiting the next 30 minutes.
one thing i never reported in the past, which seems to be related to this:
am i the only person whose Yappari segfaults immediately you finish Synchronizing? It syncs the names just fine, but immediately after that it dies.
This has been happening for a few of the previous versions too. I didn't take it seriously at the time because the sync does seem to run ok.
i'm waiting the next 30 minutes.
one thing i never reported in the past, which seems to be related to this:
am i the only person whose Yappari segfaults immediately you finish Synchronizing? It syncs the names just fine, but immediately after that it dies.
This has been happening for a few of the previous versions too. I didn't take it seriously at the time because the sync does seem to run ok.
|
|
2015-07-08
, 22:30
|
|
Posts: 242 |
Thanked: 169 times |
Joined on Nov 2011
|
#983
|
That's strange, I'm using version 2.0.14 and get no disconnections anymore; I managed to register a new sim, too (previously used on S40 device).
Anyway I cannot create groups, nor manage groups I previously created..
To clarify the problem, log referring to following actions is attached:
1) I create a group adding a single contact
2) my yappary reports that group is created successfully (other contact does not get notification)
3) I try to leave group, window closes itself, anyway group is still there in chats list
Anyway I cannot create groups, nor manage groups I previously created..
To clarify the problem, log referring to following actions is attached:
1) I create a group adding a single contact
2) my yappary reports that group is created successfully (other contact does not get notification)
3) I try to leave group, window closes itself, anyway group is still there in chats list
| The Following User Says Thank You to enne30 For This Useful Post: | ||
|
|
2015-07-09
, 00:36
|
|
Posts: 197 |
Thanked: 145 times |
Joined on Dec 2011
@ Dubai, U.A.E.
|
#984
|
Thanks alot Ceene. this will solve the issue for many users. however mine is working perfectly without any errors since .13 update.. good to see this s40 version though.. :-)
|
|
2015-07-09
, 07:02
|
|
Community Council |
Posts: 691 |
Thanked: 1,240 times |
Joined on Sep 2010
@ Mbabane
|
#985
|
Now my Yappari has worked for more than 30 minutes (almost 2 hours actually).
But I have not 'spoken' to anyone except those I have communicated with since getting updated Yappari.
This leads me to conclude that the disconnections I was getting were 'soft-bans' for communicating with numbers I haven't synchronized ...
I'll put in a bug report on Github for synchronization issues. Just strange that I might be the only one whose Yappari crashes towards the end of Sync.
But I have not 'spoken' to anyone except those I have communicated with since getting updated Yappari.
This leads me to conclude that the disconnections I was getting were 'soft-bans' for communicating with numbers I haven't synchronized ...
I'll put in a bug report on Github for synchronization issues. Just strange that I might be the only one whose Yappari crashes towards the end of Sync.
|
|
2015-07-09
, 08:02
|
|
Posts: 207 |
Thanked: 967 times |
Joined on Apr 2014
@ Madrid, Spain
|
#986
|
Originally Posted by enne30
It's more than likely that new protocol version is getting pushed out to some people, so this kind of fixes will take time until we are able to upgrade Yapparis WA protocol version.
That's strange, I'm using version 2.0.14 and get no disconnections anymore; I managed to register a new sim, too (previously used on S40 device).
Anyway I cannot create groups, nor manage groups I previously created..
To clarify the problem, log referring to following actions is attached:
1) I create a group adding a single contact
2) my yappary reports that group is created successfully (other contact does not get notification)
3) I try to leave group, window closes itself, anyway group is still there in chats list
Sorry
__________________
OVI and downloads.maemo.nokia.com mirror
Yappari for Maemo
pyLedger for Maemo
If you want to donate, please read this. If you still want to donate, contact me via private message or email. Thank you.
OVI and downloads.maemo.nokia.com mirror
Yappari for Maemo
pyLedger for Maemo
If you want to donate, please read this. If you still want to donate, contact me via private message or email. Thank you.
 |
|
2015-07-11
, 14:32
|
|
Posts: 94 |
Thanked: 33 times |
Joined on Sep 2010
|
#987
|
...? Terms of service suspends number phone and you will not open session during months.
__________________
N900, 64gigas, xlv 250 - 805mhz, CSSU testing Kernel Power.
N900, 64gigas, xlv 250 - 805mhz, CSSU testing Kernel Power.
|
|
2015-07-11
, 14:45
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#988
|
Originally Posted by sicelo
I'm all for it!
@ceene:
Suggestion: how about add code to Yappari to detect when we're starting to fail challenge requests .. and then give some sort of notification to the user to use Yappari at their own risk.
This will help stop people from retrying Yappari with old protocols, which leads to a ban. I'm on my 3rd phone number now, which I don't mind too much
| The Following 2 Users Say Thank You to marmistrz For This Useful Post: | ||
|
|
2015-07-12
, 12:18
|
|
Posts: 207 |
Thanked: 967 times |
Joined on Apr 2014
@ Madrid, Spain
|
#989
|
Originally Posted by ceene
Sorry, that answer was wrong.
The protocol has not changed, so it's basically WA1.4 with a couple fixes (the group thing that got solved for 2.0.14).
Yappari currently uses WA15 protocol since version 2.0.10 and commit e446ef651ee7781ee70b4256b373d0e8a4a426be, when coderus changes were merged.
So we're quite safe on this side.
__________________
OVI and downloads.maemo.nokia.com mirror
Yappari for Maemo
pyLedger for Maemo
If you want to donate, please read this. If you still want to donate, contact me via private message or email. Thank you.
OVI and downloads.maemo.nokia.com mirror
Yappari for Maemo
pyLedger for Maemo
If you want to donate, please read this. If you still want to donate, contact me via private message or email. Thank you.
| The Following User Says Thank You to ceene For This Useful Post: | ||
|
|
2015-07-12
, 13:05
|
|
Community Council |
Posts: 691 |
Thanked: 1,240 times |
Joined on Sep 2010
@ Mbabane
|
#990
|
Nice knowing that ceene. 
Currently all 3 of my numbers are blocked. Hope to enjoy Yappari again whenever they lift the suspension. CBF to email them.
Currently all 3 of my numbers are blocked. Hope to enjoy Yappari again whenever they lift the suspension. CBF to email them.
INCOMING:
<iq>
from=g.us
id=get_groups_3
type=error
<error>
code=501
text=feature-not-implemented
INCOMING:
<stream:error>
<ack>
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.
Invalid length 0x3