asked 2014-06-20 09:51:18 +0300
If I leave my phone on the table for a while (feels like 30minutes or more but I haven't objectively tested this yet), Android apps (Whatsapp) doesn't get internet connectivity anymore.
But when I go back to Sailfish and launch the browser and start browsing, Whatsapp's queued messages suddenly all get received.
If I close the Dalvik layer and relaunch it, connectivity comes back again of course.
answered 2016-02-03 15:23:12 +0300
I am experiencing the same issue with Threema in Sailfish 2.0.0.1.0. After a few minutes not using the phone, threema seems to lose connection and I don't receive messages, when they should arrive. Instead the messages pop up, sometimes when i wake up the phone, sometimes after wake up AND starting threema. sometimes without waking the phone but with hours delay. I don't see a difference between threema minimized and closed, while the phone is in sleep mode.
Any news about this in 2016?
I was able to narrow the problems down a bit more: It seems that the connectivity problems occur especially when switching networks. At home I am usually in a Wifi. When I leave the wifi and am connected via mobile network, threema loses it totally. Connection seems gone, although threema shows "green". I don't receive messages either. The next message I try to send takes about 20 seconds to be sent. It seems threema needs to re-establish the connection for that, although it was pretending to have connection. The second it is sent, I receive all the messages which were not delivered to me. :(
Has anyone and idea how I could approach the issue? Maybe I install a a native jolla messaging app which also regularly pings something to keep the "network channel" open and avoid that jolla cuts it when going to deep sleep or switching networks?
Spark ( 2016-02-09 18:31:06 +0300 )editanswered 2015-11-23 11:35:56 +0300
From personal experience of using Android there seems to be a connectivity issue with cellular data. I've experienced loss of data and I have manually had to flick the airplane mode off/on to get it working.
It's one of the reasons I have moved away from Android.
It's a "feature" of android. At first I thought it was mabye bad coding by LG/ Samsung but a little googling revels it happens on the nexus phones as well, which indicates a problem in the source code. It's been around for at least 2 years (android 4 onwards).
Maybe the Dalvik engine does the same ?
answered 2015-11-21 21:00:26 +0300
Hi there, I am also facing this issue on Sailfish OS 2.0.0.10 and whatsapp is the only android app i use - or try to use.
This bug is making me mad since i got the phone a year ago. After some weeks i came across whatsup, which was pretty buggy that days, but hey - at least i could use it somehow. After some iterations whatsup got quite nice and stable and i have been happy for a while.
Now after some update Whatsup is not working any more. Maybe it will work again someday, but if you keep in mind that the developer already got a letter from whatsapp´s lawyers, the project is doomed anyway.
And now I am back again with the stupid whatsapp-connectivity-gambling-game.
I love the phone and the sailfish os, but I must admit I am loosing faith. The only reason i have a phone is to be contactable. Thats it. All my friends and my family are using whatsapp, so there is no way to use another messaging system. I do not want to waste my spare-time debugging this issue, nor do I want to use some strange some-times-working workarounds like constant-pinging myself.
The only solution I see now is to finally dump my jolla and go back to android, even if I hate to say it.
answered 2015-11-18 00:56:03 +0300
I had the same problem. I made a factory reset and all Android Apps worke fine. Than I installed some apps. I've install Facebook Messenger and worke with it, I lost the Connection for Telegram and other Android Apps. I uninstalled the Messenger and the connection wos back again...
answered 2015-09-12 08:03:04 +0300
btw, this issue is fixed as of the latest OS update 1.1.9.28
This is still an issue in 2.0.0.10. WhatsApp as well an Conversations disconnect after a few minutes on my phone.
luna-is-here ( 2015-11-16 09:13:01 +0300 )editanswered 2015-01-17 14:25:34 +0300
Hi all:
The ping workaround is not working for me (Sailfish 1.1.1.27). I have tried in fingerterm and in android term, with data connection and wlan connection. Nothing, after some time android apps lost connectivity.
The interesting thing is it's look like ping processes also stop even in fingerterm. For example, I run
ping -i 60 8.8.8.8
in fingerterm and let the phone alone for about 20 mins. When I return to it, there are only four or five pings done. If I wait a bit, it begins to ping again.
I think these connectivity problems have been here from the beginning a way or another. For example, some time ago even the native Mitakuuluu can keep connection through wlan when phone inactive after some time. And the problem with android emulator has been here since day one too.
¿Another workaround somebody? ¿Somebody at Jolla can update us about future fixes? My company uses Slack for internal communication so this situation is a bit of a problem.
Thank your for your time.
possibly your ping is being suspended when the device goes into deep sleep. Mitakuluu solved this using systemd.
see https://together.jolla.com/question/55324/running-syncthing-permanently-in-background/
droll ( 2015-01-17 16:54:51 +0300 )editanswered 2014-09-30 18:35:14 +0300
I tried with "ping-i 60 8.8.8.8" and actually works well. But I want to point out that the string must be written in the Android Terminal, not in Sailfish Terminal. Android terminal can be found on the play store or on the web.
answered 2014-08-05 03:54:59 +0300
Coolness. doing a ping against 127.0.0.1 also works. guess fingerterm will be a permanent cover on my phone for now. :)
so to all those folks who have problems with android apps losing network connectivity, just run
ping -i 60 127.0.0.1
in fingerterm and leave it there permanently. you do incur some additional power consumption but it is very low. I used to average 1% battery usage per hour with the phone idle while I sleep at night. it's looking like 1.5% to 2% now - yes it's a 100% increase but statistics can be made to lie. :) i'm ok with 2% per hour. small price to pay to get my notifications working fine.
---------EDIT------------- seems like this still doesn't work. there are times when I don't get messages even though when I open a contact in whatsapp it will show the contact name at the top and after a few seconds it will show the last online time (which indicates whatsapp still has connectivity to whatsapp servers). rare but it happens.
I've reverted back to pinging 8.8.8.8
answered 2014-08-04 05:47:30 +0300
I may have found a workaround for this.
open fingerterm and keep a ping session alive. set the interval to 60seconds. I tried setting it 180 seconds and it still times out. but 60seconds it's ok.
Asked: 2014-06-20 09:51:18 +0300
Seen: 9,272 times
Last updated: Feb 03 '16
I've noticed this with Telegram, but it only takes a few minutes.
clau ( 2014-06-20 21:19:07 +0300 )editAlso happens to me. Even with the latest update. The notifications now with the update 8 work very well, but since the Android app loses connection, then do not work anymore
salkos73 ( 2014-07-20 12:41:36 +0300 )editI understand that when the android environment loses the connection you must dial off and then back on and it works. Or you can switch from mobile to wifi connection or wifi to mobile. Or if you are in an area where mobile network has a low signal (so you will lose your connection), when you fall into an area where the signal is better (the connection is re-established), internet access in android works. After a while you lose again. The bug is just that.
salkos73 ( 2014-08-03 16:33:52 +0300 )editi have also tried running net-ping inside dalvik to do pings every 30 seconds to google's public dns. still no luck. connection still dies. :( maybe have to write a script that disconnects data every 10 minutes and reconnects?? horrible workaround :(
droll ( 2014-08-03 21:20:40 +0300 )edit@droll Just to make sure, this problem occurs on latest Sailfish OS (1.0.8.19), right?
jiit ( 2014-08-06 10:55:43 +0300 )edit