Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 1 hr ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 20 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 5 hrs ago - more...
| The Following User Says Thank You to ceene For This Useful Post: | ||
|
2015-09-19
, 10:23
|
|
Posts: 395 |
Thanked: 255 times |
Joined on Nov 2010
|
#1172
|
Originally Posted by n900_man
When says: "Trying to reconnect in 10 sec", does that and if you're connection is good (that happens usually on 2.5g, maybe on 3g, really wierd on wifi), reconnects as log in.
Oh, common, why nobody hears me?
How to enable auto-reconnect feature? In log I can see following messages: "Trying to reconnect in 10 sec", but it doesn't trying to reconnect.
Apps stays freezes, and I must relaunch it.
Its annoying to watch how it disconnects 30 times per day without visible reason, and stays disconnected until I manually reconnect it.
When says: "Disconnected", does not reconnects, basically crash the app for "unknow" reasons, and you have to manually reconnects.
So there are two differents stuff that you mention, one it does what you want, the second doesn't cause the app crash.
You're problem have to be with poor signal.
Greetings.
|
|
2015-09-19
, 11:49
|
|
Posts: 30 |
Thanked: 3 times |
Joined on May 2015
|
#1173
|
Originally Posted by ceene
http://talk.maemo.org/showpost.php?p...postcount=1160
Can you send me your log reflecting this? That is not normal, as Yappari always tries to reconnect. It may happen, however, that it crashes completely. That is known to happen but it is thought to be a bug in the underlying code, i.e. QT, not in Yappari tself.
Yes, It crashes completely. You mean problem is in Qt library? Mabye its bug somewhere in Yappari... Maybe I must add more diagnostic log messages in codebase and test yappari with them to find more info...
Originally Posted by s4br0s0
Yes, I often have bad poor signal... What caused app to crash when signal is poor? Maybe some timers are out of time when waiting for packets..
You're problem have to be with poor signal.
Greetings.
Thanks for help
|
|
2015-09-19
, 12:32
|
|
Posts: 207 |
Thanked: 967 times |
Joined on Apr 2014
@ Madrid, Spain
|
#1174
|
Originally Posted by n900_man
Sorry, I must have missed your previous message. That log is unfortunately too short, although from latest message from Cepiperez I can solve at least the stream:error message, but a more complete log would be useful.
http://talk.maemo.org/showpost.php?p...postcount=1160
Yes, It crashes completely. You mean problem is in Qt library? Mabye its bug somewhere in Yappari... Maybe I must add more diagnostic log messages in codebase and test yappari with them to find more info...
The crashes are undoubtedly a problem outside Yappari, even the coredumps are corrupted. I've tested it with a debug enabled version of Yappari and it seems clear. There can be, however, some way to avoid this crashes, but I've yet to found them.
Please, try to send me a log in which those disconnect occur and in which an INCOMING <notification> is received.
I'll be releasing 2.0.21 soon and will explain with it everything that has happened during the last two weeks, it's been pretty intensive.
__________________
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-09-19
, 12:44
|
|
Posts: 395 |
Thanked: 255 times |
Joined on Nov 2010
|
#1175
|
Originally Posted by ceene
Not 100% sure but the disconnect have to be with groups incoming message, almost every tiime i got the disconnect crash, when connects again, recieve a (or several) gruop message(s).
Please, try to send me a log in which those disconnect occur and in which an INCOMING <notification> is received.
Sometimes i suspect that is just something with WA server.
Anyway, waiting for the next realese.
Greetings.
|
|
2015-09-19
, 16:42
|
|
Posts: 2 |
Thanked: 3 times |
Joined on Sep 2015
|
#1176
|
Finally am part and parcel of the maemo community, it was difficulty getting registered. First and foremost i would like to give special thanx to ceene ooh u are truely our hero in the survival of nokia n900. Yappari is just awesome. Many thanx again to th rest of developers who are making contributions to the success of these fantastic apps. I howervr facing a problem maybe a bug i dont knw, i have YAPPARI 2..0.20 upgraded via repos in app manager, but since version 2.0.14 my yappari has been crashing 3-5 minutes of each successful login via either gsm, dual mode or 3G network but works perfectly fine via wifi network and doesn't crush at all. I have seen threads about yappari saying connection closed by server, but thats not an issue to be worried about coz immediately after that notification yappari always get connected.
Plz if anyone cn tell what am missing, the help is greatly appreciated
| The Following User Says Thank You to Carlotic For This Useful Post: | ||
|
|
2015-09-19
, 21:25
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#1177
|
@Carlotic - that sounds like what was being discussed in the previous 4 or so posts: crashes due to poor connection quality, typically GPRS
|
|
2015-09-20
, 09:05
|
|
Posts: 242 |
Thanked: 169 times |
Joined on Nov 2011
|
#1178
|
Originally Posted by ceene
hi ceene, I'm getting bunch of "stream:error", too.
Sorry, I must have missed your previous message. That log is unfortunately too short, although from latest message from Cepiperez I can solve at least the stream:error message, but a more complete log would be useful.
The crashes are undoubtedly a problem outside Yappari, even the coredumps are corrupted. I've tested it with a debug enabled version of Yappari and it seems clear. There can be, however, some way to avoid this crashes, but I've yet to found them.
Please, try to send me a log in which those disconnect occur and in which an INCOMING <notification> is received.
I'll be releasing 2.0.21 soon and will explain with it everything that has happened during the last two weeks, it's been pretty intensive.
This evenience usually leads yappari to crash in a couple of minutes.
I'll try to be more specific:
- during a session first I got 2 stream errors after "receipt delivering" stuff -> stream_error_00.txt, stream_error_01.txt
- then I got 3 stream errors after get_groups_3 -> stream_error_02.txt
- finally I see a fatal get_groups_3 -> no stream error, but IO error and "Invalid length 0x8"
please note:
- 39330****** is me
- 39338******* is another yappari client (dunno if having other yappari contacts could be related to stream error problems)
EDIT : updated since this morning to 2.0.21 and so far no more "stream:error" in log nor crashes! Thank you ceene!!
Last edited by enne30; 2015-09-22 at 07:23.
|
|
2015-09-21
, 07:13
|
|
Posts: 3 |
Thanked: 2 times |
Joined on Sep 2015
@ Moscow, Russia
|
#1179
|
Originally Posted by sicelo
Thanks
Definitely banned, friend
Try to get whatsapp to unblock you by using an Android phone, or do what I did ... new number
But I'll try the first option.
 |
| Tags |
| whatsapp, yappari |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 02:03.
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.