Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-03-21 10:26:32 +0300

Update: After the 'fix' above 36 hours testing, my Jolla works fluently:

  • not consuming battery,
  • no booting problems,
  • no lost internet connections
  • > 62% battery
  • 6 apps open overnight (Settings, browser, tweetian, tidings, mitäkuuluu, calendar).
  • Normal day usage yesterday (few short calls, SMS:es, browsing, twitter, RSS, Mail reading)
  • Two e-mail accounts updated every 30 minutes.
  • BT on, 3gData ON, WLAN ON

I'm not saying the following list can be explained by memory/resource exhaustion by runaway process, but before this 'fix' I had at least these problems (which now all are gone):

So these were some of the issues I encountered during first 3 days also, so my point is they seriously points to direction that Sailfish runs out of resources (free memory/cpu?) for some reason. Unfortunately I cannot reproduce these any more (after 'fix' above), so if any of reader hits some of these or similar, screenshot from top command output in shell or Crest app could maybe lead to misbehaving process.

I also urge @JollaHQ to take a note and post proper instructions how user could track this issue to help them to iron it out.

Update: After the 'fix' above 36 hours testing, my Jolla works fluently:

  • not consuming battery,
  • no booting problems,
  • no lost internet connections
  • > 62% battery
  • 6 apps open overnight (Settings, browser, tweetian, tidings, mitäkuuluu, calendar).
  • Normal day usage yesterday (few short calls, SMS:es, browsing, twitter, RSS, Mail reading)
  • Two e-mail accounts updated every 30 minutes.
  • BT on, 3gData ON, WLAN ON

I'm not saying the following list can be explained by memory/resource exhaustion by runaway process, but before this 'fix' I had at least these problems (which now all are gone):

So these were some only part of the issues I encountered during first 3 days also, so my point is they seriously points to direction that Sailfish runs out of resources (free memory/cpu?) for some reason. Unfortunately I cannot reproduce these any more (after 'fix' above), so if any of reader hits some of these or similar, screenshot from top 'top' command output in shell or Crest 'Crest' app could maybe lead to misbehaving process.process (which itself maybe is not the root cause).

I also urge @JollaHQ to take a note and post proper instructions here how user could better track this issue to help them to iron it out.