We have moved to a new Sailfish OS Forum. Please start new discussions there.
8

[1.1.9.28] slow ssh/scp/rsync when screen is off

asked 2015-09-12 00:44:42 +0200

Shoppinguin gravatar image

updated 2015-09-13 03:11:04 +0200

heubergen gravatar image

Don't know if anyone experienced this before but when using ssh/scp or rsync while the screen is turned off, it is very unresponsive and slow. Transfer rates of rsync/scp are like ~.5 to 1 MByte/s versus 7-8 MByte/s while awake. pkcon even refused to do anything at all until i manually turned on the screen. I would expect the device to go into some sort of deep sleep while the screen is turned of but shouldn't it wake/speed up when there is some work to be done?

edit retag flag offensive close delete

Comments

1

I would recommend to use USB networking - Jolla should not enter deep sleep when connected to a power source (USB cable) and the connection should be faster and more stable than over WiFi. :)

MartinK ( 2015-09-12 01:43:23 +0200 )edit

I noticed this on 1.1.7 when trying to lazily do my backups (mmc cloning) over wifi - the "su" command didnt seem to finish at all before i tapped the screen active. Then i ended up doing the backup over wifi while the phone was plugged into usb for charge only because i was too lazy to change the networking ...

urjaman ( 2015-09-12 11:58:39 +0200 )edit
1

USB is not an option. The idea is to have it automatically backup as soon as it is in my home wifi. You can d this using systemd. It will run a script as soon as the device makes connection to a distinct wifi network. Please let me know if there is a command to wake the device, so i can do the backup safe and fast and put the device to sleep again after successful backup. "Race to idle" has proven to be a lot more efficient than a slow transfer that consumes less power.

Shoppinguin ( 2015-09-12 14:26:35 +0200 )edit
2

Yes, this is the case with 1.1.9, but I don't see a difference to the way it was before. Every now and then, when the screen was blank, SSH would go to sleep and I needed to double-tap to continue working. It was most annoying when this behaviour prevented the SSH session to even start.

ossi1967 ( 2015-09-12 14:32:13 +0200 )edit

1 Answer

Sort by » oldest newest most voted
2

answered 2015-09-12 17:05:50 +0200

axaq gravatar image

updated 2015-09-12 17:09:27 +0200

This power management behaviour is there from the beginnng of SFOS. You will find more questions in TJC regarding screen off, background processes or scripts and deep sleep.

I recommend reading 20743 with answer 21434 and than the linked TMO thread and especially the answer by javispedro.

You should read in any case the linked blog post from Felipe Contreras to Android vs. Maemo power management: static vs. dynamic. and watch the video. Very interesting with a lot of insides into mobile power management.

edit flag offensive delete publish link more

Comments

2

Sorry but i can't watch any video any time soon due to not having a fast enough connection. But i still got the whole point. i tried all the suggestions. Connecting a USB charger did nothing in that respect. And so did changing the MCBCFilter and wakelock. Or maybe the did, but i could not see any change. mcetool had to be installed via pkcon first as it wasn't available before, but it did the trick. I added mcetool --set-suspend-policy=disabled to the beginning of the script and mcetool --set-suspend-policy=enabled to the end. So the powersaving will only be disabled while doing the backup. it appears to be working perfectly so far. Thanks :)

Shoppinguin ( 2015-09-12 21:26:38 +0200 )edit
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2015-09-12 00:44:42 +0200

Seen: 501 times

Last updated: Sep 12 '15