Revision history [back]

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
• Enabled zram in kernel, suggested by community in this post

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team

Updated on 3.11.2014

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
• Enabled zram in kernel, suggested by community in this post

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team

Updated on 3.11.2014
3.12.2014

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
• Enabled zram in kernel, suggested by community in this post

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team

Updated on 3.12.2014

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
• Enabled zram in kernel, suggested by community in this post

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team

Updated on 3.12.2014

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
• Enabled zram in kernel, suggested by community in this post

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team

Updated on 3.12.2014

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
• Enabled zram in kernel, suggested by community in this post

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team

Updated on 3.12.2014

Dear Jolla users,

We've been working hard on improving the out of memory (OOM) handling by the OS since the update9 opt-in was released. A portion of our time went into demo preparations for Slush and of course the tablet launch. This has left us lagging a bit behind the internal release schedule for update10.

We'd like to share the highlights of the improvements we've done so far:

• Ensured that phone UI never gets killed when OOM (Out of Memory) handling kicks in
• Improved handling of tabs in browser by releasing GPU memory on closing tabs
• Automatically unloading browser tabs in low memory situation
• Dropping memory-heavy HTML email viewer from memory when not used in a while
• Messages app is no longer kept in memory when the window is closed by the user
• Only load Phone dialers, Device lock, Facebook and Twitter feed pages in memory on demand
• Enabled memory compaction configuration option in kernel
• Removed unneeded/unnecessary kernel options to save memory
• Added memnotify patch to kernel to get notifications on memory thresholds being crossed
• Made MCE able to receive and set up memory thresholds with /dev/memnotify
• Connection manager VPN daemon (connman-vpnd) is no longer started on boot to lower memory footprint
• Enabled zram in kernel, suggested by community in this post

Furthermore, we are looking into:

• optimising handling notifications in events view when there are lots of them
• optimising call log models, and limiting the number of call log pages being loaded to reduce the time taken to startup phone app and drop memory usage
• making OOM killer more verbose to further aid debugging
• debugging frequent crashes observed during internal testing
• improving OOM handling for Android applications
• tuning operating system memory policies to guarantee there is enough memory available for user's next task

Finalisation of update10 depends on the above mentioned points and bringing SailfishOS version compatibility support for Jolla Store and Harbour. We really hope to release before Christmas, though in the event we are unable to accomplish the improvements stated above by the end of next week (=1 week before Christmas holidays begin), we will not release update10 during December. We prefer to not release at the start of a vacation period when we are not around to support you in the first few days of a new release.

Thanking you for your patience and continued support,

Jolla team