We have moved to a new Sailfish OS Forum. Please start new discussions there.
![]() | 1 | initial version | posted 2014-08-31 07:27:08 +0200 |
after 4-5 days of uptime, my device starts becoming slow. apps are slower to launch, and apps take longer to respond. by the time it hits 7 days uptime, the slowdown is really irritating.
i believe it is due to memory fragmentation over time, something i also experienced on the n900. a fresh boot would always make the device snappy again.
what I've done is very very simple. i run the dalvik layer so this also contributes to fragmentation. 1. i have a script that stops the dalvik layer at night. restarting is optional. it restarts when i fireup whatsapp the next day anyway (just takes a bit longer to have whatsapp startup the first time but that's fine). 2. i don't use the built-in browser. i use firefox. i surf the web on the phone quite frequently and quite heavily. by keeping all the memory fragmentation inside the dalvik layer, i minimize slowdowns. i also find the built-in browser to be one of the worst contributors to slowdown over time.
by doing the two steps above, i have minimized the slowdown (make no mistake, it still slows down but it is so infinitesimally small that it's negligible). i am now at 7 days 18 hours 56m uptime and the phone feels like it's at 95% snappiness since a fresh boot - even the jerkiness in the phone dialer is minimal (like from a fresh boot).
i might be wrong with my analysis but this is my humble observation and workaround. i don't think the phone suffers if you use native sailfish apps (with the exception of the native browser).
![]() | 2 | No.2 Revision |
after 4-5 days of uptime, my device starts becoming slow. apps are slower to launch, and apps take longer to respond. by the time it hits 7 days uptime, the slowdown is really irritating.
i believe it is due to memory fragmentation over time, something i also experienced on the n900. a fresh boot would always make the device snappy again.
what I've done is very very simple. again. i run the dalvik layer so this also contributes to fragmentation.
1. fragmentation.
what I've done is very very simple.
i have a script that stops the dalvik layer at night. restarting is optional. it restarts when i fireup whatsapp the next day anyway (just takes a bit longer to have whatsapp startup the first time but that's fine).
2. fine).
i don't use the built-in browser. i use firefox. i surf the web on the phone quite frequently and quite heavily. by keeping all the memory fragmentation inside the dalvik layer, i minimize slowdowns. i also find the built-in browser to be one of the worst contributors to slowdown over time.
by doing the two steps above, i have minimized the slowdown (make no mistake, it still slows down but it is so infinitesimally small that it's negligible). i am now at 7 days 18 hours 56m uptime and the phone feels like it's at 95% snappiness since a fresh boot - even the jerkiness in the phone dialer is minimal (like from a fresh boot).
i might be wrong with my analysis but this is my humble observation and workaround. i don't think the phone suffers if you use native sailfish apps (with the exception of the native browser).
![]() | 3 | No.3 Revision |
after 4-5 days of uptime, my device starts becoming slow. apps are slower to launch, and apps take longer to respond. by the time it hits 7 days uptime, the slowdown is really irritating.
i believe it is due to memory fragmentation over time, something i also experienced on the n900. a fresh boot would always make the device snappy again. i run the dalvik layer so this also contributes to fragmentation.
what I've done is very very simple.
i have a script that stops the dalvik layer at night. restarting is optional. it restarts when i fireup fire up whatsapp the next day anyway (just takes a bit longer to have whatsapp startup the first time but that's fine).
i don't use the built-in browser. i use firefox. i surf the web on the phone quite frequently and quite heavily. by keeping all the memory fragmentation inside the dalvik layer, i minimize slowdowns. i also find the built-in browser to be one of the worst contributors to slowdown over time.
by doing the two steps above, i have minimized the slowdown (make no mistake, it still slows down but it is so infinitesimally small that it's negligible). i am now at 7 days 18 hours 56m uptime and the phone feels like it's at 95% snappiness since a fresh boot - even the jerkiness in the phone dialer is minimal (like from a fresh boot).
i might be wrong with my analysis but this is my humble observation and workaround. i don't think the phone suffers if you use native sailfish apps (with the exception of the native browser).
![]() | 4 | No.4 Revision |
after 4-5 days of uptime, my device starts becoming slow. apps are slower to launch, and apps take longer to respond. by the time it hits 7 days uptime, the slowdown is really irritating.
i believe it is due to memory fragmentation over time, something i also experienced on the n900. a fresh boot would always make the device snappy again. i run the dalvik layer so this also contributes to fragmentation.
what I've done is very very simple.
i have a script that stops the dalvik layer at night. restarting is optional. it restarts when i fire up whatsapp the next day anyway (just takes a bit longer to have whatsapp startup the first time but that's fine).
i don't use the built-in browser. i use firefox. i surf the web on the phone quite frequently and quite heavily. by keeping all the memory fragmentation inside the dalvik layer, i minimize slowdowns. i also find the built-in browser to be one of the worst contributors to slowdown over time.
by doing the two steps above, i have minimized the slowdown (make no mistake, it still slows down but it is so infinitesimally small that it's negligible). i am now at 7 days 18 hours 56m uptime and the phone feels like it's at 95% snappiness since a fresh boot - even the jerkiness in the phone dialer is minimal (like from a fresh boot).
i might be wrong with my analysis but this is my humble observation and workaround. i don't think the phone suffers if you use native sailfish apps (with the exception of the native browser).
after 4-5 days of uptime, my device starts becoming slow. apps are slower to launch, and apps take longer to respond. by the time it hits 7 days uptime, the slowdown is really irritating.
i believe it is due to memory fragmentation over time, something i also experienced on the n900. a fresh boot would always make the device snappy again. i run the dalvik layer so this also contributes to fragmentation.
what I've done is very very simple.
i have a script that stops the dalvik layer at night. restarting is optional. it restarts when i fire up whatsapp the next day anyway (just takes a bit longer to have whatsapp startup the first time but that's fine).
i don't use the built-in browser. i use firefox. i surf the web on the phone quite frequently and quite heavily. i also find the built-in browser to be one of the worst contributors to slowdown over time.
by doing the two steps above, i have minimized the slowdown (make no mistake, it still slows down but it is so infinitesimally small that it's negligible). i am now at 7 days 18 hours 56m uptime and the phone feels like it's at 95% snappiness since a fresh boot - even the jerkiness in the phone dialer is minimal (like from a fresh boot).
i might be wrong with my analysis but this is my humble observation and workaround. i don't think the phone suffers if you use native sailfish apps (with the exception of the native browser).