Ask / Submit

ssh over wlan / wifi connection problems [answered]

asked 2014-01-29 23:06:35 +0200

melg01 gravatar image

updated 2014-02-12 23:42:45 +0200

Connecting in local wireless network at home (wpa2 with key) from my windows pc to my Jolla with ssh putty (TCP keepalive set on). First connection doesn't work, I can't see the Jolla from my pc, until I initiate some pings from the Jolla to the pc. Then I am able to 'see' the Jolla from my pc and connect through ssh.

Once connected to the Jolla, I lose the connection quite easily again, after some inactivity, the Jolla is again invisible from the pc. Is this a common problem of Jollas wlan implementation, maybe some timeout? Any workaround? I don't have this problem with other wireless connected devices (android, raspberry and others).

Any hint greatly appreciated.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by melg01
close date 2014-01-31 22:55:19.213098

1 Answer

Sort by » oldest newest most voted

answered 2014-01-29 23:12:25 +0200

Sailor gravatar image

updated 2014-01-29 23:13:29 +0200

It's because the device goes to sleep after some time to safe battery. It even does not reply to ARP requests after that period. You need to connect it via USB to not let it go to sleep. Or using mosh is also a solution according to TMO.

edit flag offensive delete publish link more


@Sailor: Thank you for the hint, I didn't think of the sleeping, wondering why this happens when I send TCP keepalives form the pc shh, I think Jolla should honour this. When I have an endless ping running on the Jolla terminal, then it works fine. it's just not a very elegant solution.

melg01 ( 2014-01-29 23:22:02 +0200 )edit

As I understand there is an option to disable the deep sleep to keep services running, but that will be bad for the battery life (should link the relevant TMO-thread here).

foss4ever ( 2014-01-30 06:11:19 +0200 )edit

One thing I liked about my N9 was that I could always connect to it by ssh/scp wherever it was around the house. It is a bit annoying now that I have to physically find my phone to wake it up before copying files to/from it, but if the battery savings are that big maybe it is worth it.

pellen ( 2014-01-30 13:57:00 +0200 )edit

@pellen Yes, and it's also because of the hardware adaptation layer and chosen SoC, which requires to use an droidish solution in regards to CPU-states and power-consumption.. Just check out the relevant discussions in Jolla and SailfishOS threads at

foss4ever ( 2014-01-30 14:04:31 +0200 )edit

Thank you for the answers. I personally would prefer to ssh-access my jolla through wireless instead of usb. I see the point, but with other devices it was never an issue. Maybe some hardware decisions should be overthought for the next generation, likewise with the display too (which doesn't allow informational lockscreens anymore, like with the N9 amoled display). Closing this question now.

melg01 ( 2014-01-31 22:54:51 +0200 )edit

Question tools



Asked: 2014-01-29 23:06:35 +0200

Seen: 787 times

Last updated: Jan 29 '14