|
2016-03-03
, 12:05
|
Posts: 83 |
Thanked: 91 times |
Joined on Nov 2015
@ NIgeria
|
#912
|
Strange behaviour in the last days with Whatsup:
Do you also have the effect that the app gets constantly killed by the memory management?
For me the app gets restarted constantly when I click it and the phone was lying around for several minutes. Even if I have no other app opened it seems that the app has a memory hole which triggers the memory management to kill the process and leave me with the "zombie cover". Is this maybe a side effect of the Whatsapp server issues reported the last days or is it sth else?
I have restarted the phone already many times but it doesn't go away, unfortunately I can't identify what is eating the ram or whatever triggers the killing of the process. Anybody else with this experience?
The Following User Says Thank You to dameceno For This Useful Post: | ||
|
2016-03-07
, 00:44
|
Posts: 77 |
Thanked: 19 times |
Joined on Jun 2010
@ Spain
|
#913
|
|
2016-03-09
, 10:50
|
Posts: 3 |
Thanked: 0 times |
Joined on Apr 2015
|
#914
|
|
2016-03-10
, 07:42
|
Posts: 20 |
Thanked: 69 times |
Joined on Sep 2015
@ Finland
|
#915
|
|
2016-03-12
, 20:39
|
Posts: 23 |
Thanked: 13 times |
Joined on Jun 2015
@ Europe
|
#916
|
Used to have a lot of that happening before I reset my device. My bet is because your chat history is somewhat voluminous as a result of long activity. I clean start would certainly do the trick. Not the reset part but removing your backups db and even whatsup folder. Actually it includes uninstalling whatsup, deleting the .whatsup folder under home as well as the whatsup folder and the cepiperez folder located under /nemo/home/.conf
|
2016-03-16
, 08:11
|
Posts: 49 |
Thanked: 32 times |
Joined on Sep 2012
|
#917
|
|
2016-03-24
, 09:42
|
Posts: 12 |
Thanked: 35 times |
Joined on Feb 2015
|
#918
|
|
2016-03-24
, 09:47
|
Posts: 23 |
Thanked: 8 times |
Joined on Jan 2012
|
#919
|
Hello,
As of yesterday, I can no longer send/receive one to one messages (could not process group chats for a few months already). Is there any hope of updating Whatsup, i.e., implementing the client to client encryption, which seems the limiting factor here?
Or has it all become too tedious/complicated and I should look for another alternative?
Checking processes... not working MESSAGES: 0 - READ: 0 Socket error: Connection closed by server. Connection closed. Stopping timers. Freeing up the connection. Freeing up the socket. Retry the connection in 10 seconds. Connection status: disconnected Disconnection done Starting new connection Checking if already connecting Checking active network Connection status: connecting Connecting to c2.whatsapp.net:443... Connection status: connecting Connected successfully Unencoded Password: ElmTm0QlulriMNHtv6QuyBkGKBU= Base64 Password: Y��D%�Z�0��.�( Challenge: 9a16ab331bce9344ad480f6a12dcb196dc92a925 OUTGOING: <stream:features> <groups_v2> </groups_v2> <identity> </identity> <presence> </presence> <privacy> </privacy> <readreceipts> </readreceipts> </stream:features> OUTGOING: <auth mechanism="WAUTH-2" passive="false" user="77017340235"> <<<ENCODED DATA>>> </auth> Reading data... INCOMING: <stream:start from="s.whatsapp.net"> </stream:start> Checking processes... not working MESSAGES: 0 - READ: 0 Reading data... INCOMING: <stream:features> </stream:features> Checking processes... not working MESSAGES: 0 - READ: 0 Reading data... INCOMING: <success creation="1338382870" expiration="4444444444" kind="free" props="4" status="active" t="1458798621"> <<<ENCODED DATA>>> </success> OUTGOING: <iq id="config_1" to="s.whatsapp.net" type="set" xmlns="urn:xmpp:whatsapp:push"> <config platform="S40" version="2.12.96"> </config> </iq> Connection status: connected Checking processes... not working MESSAGES: 0 - READ: 0
|
2016-03-25
, 11:52
|
Posts: 79 |
Thanked: 41 times |
Joined on May 2012
@ kenya
|
#920
|
Thanks again for the tip
Sony C6 > Sony Ericsson K310 > Sony Ericsson K750 > N70 > N73 > N81 > N82 > N79 > E7 > N9 > Jolla