Revision history [back]

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport both Android and Sailfish by only 1 GB.

New QT framework vetsion 5.2 plus another more nodern version of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes Jolla feels like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram to make part of system memory conpressed, so device can hold more active content on RAM before swapping pages to slow internal flash.

At least current Android versions use zram ss basic feature, so ut should be well behaving kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport both Android and Sailfish by only 1 GB.

New QT framework vetsion 5.2 plus another more nodern version of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes Jolla feels like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram to make part of system memory conpressed, so device can hold more active content on RAM before swapping pages to slow internal flash.

At least current Android versions use zram ss basic feature, so ut should be well behaving kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport both Android and Sailfish by only 1 GB.

New QT framework vetsion version 5.2 plus another more nodern version modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes Jolla feels like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram to make part of system memory conpressed, so device can hold more active content on RAM before swapping pages to slow internal flash.

At least current Android versions use zram ss as basic feature, so ut it should be well behaving kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes Jolla feels like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory conpressed, so compressed. By utilizing zram device can hold more active content on RAM before swapping pages to slow internal flash.

At least current recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes Jolla feels like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram device can hold more active content on RAM before swapping pages to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram device can hold more active content on RAM before swapping pages to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to dupport support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT. There are zram module available in Openrepos, it may unfortunately not be compactible with Uitukka (see comments below).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT. EDIT1. There are zram module available in Openrepos, it may unfortunately not be compactible with Uitukka (see comments below).

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos, it may unfortunately not be compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think relevant to bring up in context of Uitukka issues with OOM.

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos, it may unfortunately not be compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered n in wrong place) making this thread unintentionally wiki.wiki ... There are no way to convert this back to question, I suppose - any mods on line?

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos, it may unfortunately not be compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no way to convert this back to question, I suppose - any mods on line?

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos, Openrepos (thanks @g7), it may unfortunately not be compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no way to convert this back to question, I suppose - any mods on line?

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), @g7), it may unfortunately not be compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no way to convert this back to question, I suppose - any mods on line?

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), it may is unfortunately not be compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no way to convert this back to question, I suppose - any mods on line?

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), it is unfortunately not compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no way function for user to convert this back to question, I suppose - any mods on line?

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), it is unfortunately not compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no function for user to convert this back to question, I suppose suppose.

EDIT4. So, I got what I deserved in this case - any mods on line?Now, as Wiki entry I add reference to another suggestion to improve and balance memory managenent to do whayever it can to keep Jolla sailing. This thread vm.swappiness discuss pros and cons of setting swap management parameters.

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), it is unfortunately not compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no function for user to convert this back to question, I suppose.

EDIT4. So, I got what I deserved in this case - Now, as Wiki entry I add reference to another suggestion to improve and balance memory managenent to do whayever whatever it can to keep Jolla sailing. sailing smoothly. This thread vm.swappiness discuss deeply of pros and cons of setting the set up swap management parameters.

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), it is unfortunately not compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no function for user to convert this back to question, I suppose.

EDIT4. So, I got what I deserved in this case - Now, as Wiki entry I add reference to another suggestion to improve and balance memory managenent to do whatever it can to keep Jolla sailing smoothly. This thread vm.swappiness discuss deeply of pros and cons of the set up swap management parameters.

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), it is unfortunately not compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no function for user to convert this back to question, I suppose.

EDIT4. So, I got what I deserved in this case - Now, as Wiki entry I add reference to another suggestion to improve and balance memory managenent to do whatever it can to keep Jolla sailing smoothly. This thread vm.swappiness discuss deeply of pros and cons of the set up swap management parameters.

EDIT5. Now, we have got in our hands update 10, which, indeed, has enabled zram as a base system feartue. What I have missed so far is the information if zram is enabled automatically for those that has not set it up already before upd10. I upgraded name of this thread accordingly.

EDIT. Yes, zram is active for all u10 users. Here are information how to change the zram size from default 13%: https://together.jolla.com/question/77183/how-to-change-zram-size/

I had on Uitukka zram set as 2x48MB. Now with upd10 I have upgraded that to be 25% e.g. 2x101 MB. I still wonder what is the best size for zram to prevent too aggressive low memory killer to kick in and start killiing (randomly, not so, but it still feels like it) of tasks?

I really do not like to loose my tasks regulary, I have even started to envy iOS approarch at least save the state of task before killing it to be able to restore it at least seemingly same state...

Update 9 Uitukka seems to bring along memory pressures for ~tiny~ 1 GB RAM available. Tiny in that sense that Jolla has dual systems in place, modern Android devices have 2..3 GB of memory just for Android, but Jolla try to support both Android and Sailfish by only 1 GB.

New QT framework version 5.2 plus another more modern components of system SW like browser engine updated to Gecko 31 seems to give Jolla's RAM memory hard times. Sometimes (after update9) with many apps open Jolla feels little bit laggy like N900 which is notorious with constant swapping no matter what you try to do putting phone to lagging.

That might help partly if Jolla enables zram (linux kernel module offering compressed RAM cache) to make part of system memory compressed. By utilizing zram, device can hold more active content on RAM before swapping pages out to slow internal flash.

At least recent Android versions use zram as basic feature, so it should be well behaving linux kernel component to help Jolla out of OOM (pun intented).

EDIT1. There are zram module available in Openrepos (thanks @g7), it is unfortunately not compactible with Uitukka (see comments below).

EDIT2: I just noticed that this thread is actually at least half duplicate of zram swappiness tweaks..., but still I think that this is relevant to bring up in context of Uitukka issues with OOM.

EDIT3: I get hit by classic browser bug (clicks get registered in wrong place) making this thread unintentionally wiki ... There are no function for user to convert this back to question, I suppose.

EDIT4. So, I got what I deserved in this case - Now, as Wiki entry I add reference to another suggestion to improve and balance memory managenent to do whatever it can to keep Jolla sailing smoothly. This thread vm.swappiness discuss deeply of pros and cons of the set up swap management parameters.

EDIT5. Now, we have got in our hands update 10, which, indeed, has enabled zram as a base system feartue. What I have missed so far is the information if zram is enabled automatically for those that has not set it up already before upd10. I upgraded name of this thread accordingly.

EDIT. Yes, zram is active for all u10 users. Here are information how to change the zram size from default 13%: https://together.jolla.com/question/77183/how-to-change-zram-size/

I had on Uitukka zram set as 2x48MB. Now with upd10 I have upgraded that to be 25% e.g. 2x101 MB. I still wonder what is the best size for zram to prevent too aggressive low memory killer to kick in and start killiing (randomly, not so, but it still feels like it) of tasks?

I really do not like to loose my tasks regulary, I have even started to envy iOS approarch at least save the state of task before killing it to be able to restore it at least seemingly same state...