Notices


Reply
Thread Tools
Posts: 2,076 | Thanked: 3,262 times | Joined on Feb 2011
#1
I would describe N900 behaviour as sane: you have sshd running, you are on a network with IP assigned, whether your screen is on or off people on the network can come and say hello through SSH.

Jolla behaviour is a bit insane, same setup: if your ssh connection hit before screen went dark all is fine and good (until you try to ./configure/make/sudo something), but after screen goes dark (might need an extra minute or two to reproduce) no way to connect.

Does anybody know how to make Jolla more sane in such situations?

edit: This supposedly could help (from irc when asking if screen on could be faked):
echo asdf > /sys/power/wake_lock
Workaround by keeping screen on, but will be horrible on battery. Any other way?

Last edited by szopin; 2013-12-28 at 01:34.
 

The Following 3 Users Say Thank You to szopin For This Useful Post:
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#2
Device will not suspended when your device is connected to usb. In home that usually means charger or your laptop.

Only way to wake from suspend (not connected to usb and display off) is to use https://github.com/nemomobile/libiphb which allows periodic heartbeat (ie wake system up at some interval).

Having said that you really should not do it unless you want to screw up your battery life.
__________________
IRC: jonni@freenode
Sailfish: Qt5 SailfishTouchExample Qt5 MultiPointTouchArea Example ipaddress stoken Sailbox (Dropbox client)
Harmattan: Presence VNC for Harmattan Live-F1 BTinput-terminal BabyLock BabyLock Trial QML TextTV
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.

Last edited by rainisto; 2013-12-28 at 01:06.
 

The Following 2 Users Say Thank You to rainisto For This Useful Post:
Posts: 2,076 | Thanked: 3,262 times | Joined on Feb 2011
#3
Originally Posted by rainisto View Post
Device will not suspended when your connected device with usb. In home that usually means charger or your laptop.

Only way to wake from suspend (not connected to usb and display off) is to use https://github.com/nemomobile/libiphb which allows periodic heartbeat (ie wake system app at some interval).
Going to compile it in a second, do I run it from fingerterm on device and then lock or does it have to be run for each process that needs to be kept alive?

EDIT:
Having said that you really should not do it unless you want to screw up your battery life
I want to be able to use my J as my N900 pocket computer that works in pocket and does what it was told to. If I can trigger libphb off after usage and keep the rest of awesome battery life than even better, for now I need to know how to keep this thing working when I want it to

Last edited by szopin; 2013-12-28 at 01:08.
 
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#4
Originally Posted by szopin View Post
Going to compile it in a second, do I run it from fingerterm on device and then lock or does it have to be run for each process that needs to be kept alive?
Not that easy, you cant say what process needs to be kept alive, you need to integrate that into each application itself. So most likely in your use case its just easier to keep your phone in charger, or have external battery charger connected. (Or keep display on).

libiphb is mostly used by alarm application which needs to wake up from suspend, and some internal apps that needs to wake up peridically.
__________________
IRC: jonni@freenode
Sailfish: Qt5 SailfishTouchExample Qt5 MultiPointTouchArea Example ipaddress stoken Sailbox (Dropbox client)
Harmattan: Presence VNC for Harmattan Live-F1 BTinput-terminal BabyLock BabyLock Trial QML TextTV
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
 

The Following 2 Users Say Thank You to rainisto For This Useful Post:
Posts: 2,076 | Thanked: 3,262 times | Joined on Feb 2011
#5
Originally Posted by rainisto View Post
Not that easy, you cant say what process needs to be kept alive, you need to integrate that into each application itself. So most likely in your use case its just easier to keep your phone in charger, or have external battery charger connected. (Or keep display on).
My use case is N900 connected to J through ssh running makes etc on J. No way to connect USB/power on on the bus/car (train with laptop will work, sure)
 
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#6
Well, yes in developer mode, you can use "mcetool" to disable suspend all together, which will suit your case, but it will make your battery go empty pretty fast.

pkcon install mce-tools
mcetool --set-suspend-policy=disabled
__________________
IRC: jonni@freenode
Sailfish: Qt5 SailfishTouchExample Qt5 MultiPointTouchArea Example ipaddress stoken Sailbox (Dropbox client)
Harmattan: Presence VNC for Harmattan Live-F1 BTinput-terminal BabyLock BabyLock Trial QML TextTV
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.

Last edited by rainisto; 2013-12-28 at 01:17.
 

The Following 14 Users Say Thank You to rainisto For This Useful Post:
Posts: 2,076 | Thanked: 3,262 times | Joined on Feb 2011
#7
Thanks! Device goes into crazy state though, tap to unlock gone, ssh even more wild unresponsive... might need to try on fresh reboot

edit: but htop from ssh now behaves normally instead of screenshot behaviour previously, now just as lively as in fingerterm

Last edited by szopin; 2013-12-28 at 01:24.
 
Posts: 2,076 | Thanked: 3,262 times | Joined on Feb 2011
#8
Works like a charm. New ssh connections start yay! Autogen/configure on libphb went nicely up to lacking 'mce'.
Thanks a lot, with disable.sh while getting on a tram and enable.sh when disembarking this suits all my needs. TY!

Last edited by szopin; 2013-12-28 at 01:40.
 
javispedro's Avatar
Posts: 2,330 | Thanked: 5,200 times | Joined on Jan 2009 @ Barcelona
#9
Back when I realized that this device had this terribly idiotic behavior*, I tried figuring out how to take a permanent wakelock from the Android side. I did not know about the mce "feature" and thus decided to create a new daemon (actually, a kernel module).

The thing is, the battery doesn't actually seem to take a very hard hit (in fact, I got slightly more battery life after enabling the "permanent wakelock" -- but obviously because of measurement error). Then I discovered the craze about the "other half power vampire" and I suspect I will have to redo tests, but at least that got my hopes somewhat high again. I also must mention that I have not inserted a SIM card yet.

* Which is the same as every other Android device out there. That's one benefit less of Jolla vs other Android devices, and one big con when comparing to Maemo devices See blog post on why opportunistic suspend is wrong right from the mouth of a member of the original N900 team.

Code:
This supposedly could help (from irc when asking if screen on could be faked):
    echo asdf > /sys/power/wake_lock
The problem with that is that wake locks are deleted when the process that created them dies. In the above command line, a subshell (or /bin/echo) is the one creating the wakelock and thus the lock dies as soon as echo dies, which is immediate. EDIT: Possibly wrong, see next page.

Last edited by javispedro; 2013-12-29 at 20:10.
 

The Following 8 Users Say Thank You to javispedro For This Useful Post:
Community Council | Posts: 4,438 | Thanked: 11,076 times | Joined on May 2012 @ Southerrn Finland
#10
Now can anyone tell me what is different with my Jola, since I have never been hit with this problem.
I can always SSH to my Jolla, just as I can SSH to my N9, whether the screen is on or off. (and on my Jolla I do have the device lock ON, so if I want to access it via the UI then I need to unlock it first...)
 

The Following User Says Thank You to juiceme For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 18:46.