Ask / Submit

[Solved] Suddenly no connectivity in Whatsapp or DeltaChat [answered]

asked 2018-04-02 23:43:06 +0200

broncheolus gravatar image

updated 2018-04-04 16:21:58 +0200

Dear community!

From the first Day on my Jolla1 had never connection problems with android apps. (apart from conversations, but that problem was a different one, although I nerver figured out why) I started to use DeltaChat a while ago and I have to say: A really great messanger. Same with Whatsapp, never had problems with background or foreground connectivity. Since a few days I have been experiencing an issue with the connectivity of those apps. The issue did not appeare with the last update of SF (, it came out of thin air. (as far as I can tell) Messages from DC don't get delivered. When I get a message 1h too late and I want to answer immediately, the answer does not get delivered.

  • restarting AS sends the stuck messages but brings no change at the end
  • No difference when wifi on.
  • I tried to switch to 3G but only the switching brought back the connection for DC and so the message was sent. But the connection got lost and the situation was the same like with 4G
  • I deinstalled and reinstalled android support. No change.
  • When DC runs and a message is waiting for delivery and I start Aptoide side by side with DC there is a connection in Aptoide. The stuck message is delivered only when I restart DC then. So Aptoide gets connected when it's started, DC and WA not.
  • all other Android apps (News, weather,...) seem to be ok, just messengers seem to have this problem (WA and DC)
  • connection from within SF (browser) seems to be ok.

Is it possible that some configurations of android support got mixed up somehow, and a reinstall does not delete these confs. If so, can I delete all confs of AS manually? Are they recreated after starting AS again? Are there other possibilities that can cause this problem? Again, I have never experienced this problem before.

Thanks in advance, broncheolus.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2018-04-24 21:06:07.827814



I realized the same with latest Whatsapp. Until yesterday I had background processes of Whatsapp disabled (I wanted disabled 'pushing' of messages.) Enabling bg processes improved a lot, but it doesn't fix the issue.

wosrediinanatour ( 2018-04-03 10:01:34 +0200 )edit

Can you confirm you can make WhatsApp work (2.18.105, downloaded through Yalp Store) on Sailfish My headaches: as happened to you, suddenly WA stopped delivering messages. Then I made a big mistake: erasing all WhatsApp data. Now I can't even register my phone number: it says...

Unable to connect. Please check that you are connected to the Internet and try again. Please reboot your phone if your connection problem persist.

Tried to download and install last version from WhatsApp official site. When I try to sign up, it says that I must install the last versión (!?). All other Android apps (Google Maps, Waze, Opera browser...) work flawlessly. Of course, Sailfish apps work too.

Only thing I didn't try yet is reinstalling the whole Android Support.

UPDATE: Reinstalling AS did the trick. Now everything is OK.

Mced ( 2018-04-18 19:59:47 +0200 )edit

Allthought I thought at first, I cannot confirm, that WA and DC work flawlessly again. Still sometimes messages are not delivered or received at once. Sometimes it works, when I activate flight mode and disable it again. Then restarting WA or DC does the trick. The reinstalling of the Android support dit not mare a change for me, as mensioned in my original post. Still Instant messaging is still unreliable but it seems better though. Greetings, broncheolus.

broncheolus ( 2018-04-23 00:23:01 +0200 )edit

1 Answer

Sort by » oldest newest most voted

answered 2018-04-04 16:20:29 +0200

broncheolus gravatar image

Thank you Wosrediinanatour!

Disabeling and enabeling in all combinations of the backgrund processes of DC and WA made no difference. Problem was that even when you dont allow WA to run in background it starts a background process. What you dont get are notifications. Then an update of WA came in (2.18.100) and for now evering seems to work again, DC and WA. So I mark this thread as solved.

Funny isn't it? WA has a bug and another messenger stops working correctly. And (but I realised that before) WA starts a background process even when you don't allow it (but no notifications) Funny,funny! :-o)

edit flag offensive delete publish link more


For me, it's the same!

wosrediinanatour ( 2018-04-05 10:49:14 +0200 )edit

Question tools

1 follower


Asked: 2018-04-02 23:43:06 +0200

Seen: 346 times

Last updated: Apr 04 '18