Ask / Submit
55

[Bug] After 4-5 days uptime Jolla UI/UX becomes sluggish

asked 2014-01-15 10:36:33 +0300

zlatko gravatar image

updated 2014-09-11 23:42:57 +0300

chemist gravatar image

I have noticed in my nearly a month using Jolla, that after several(2-3) days of uptime the UI start to experience lags and sluggishness. What I notice:

  • after double tap to wake I can not swipe from lock screen to main applications. It takes several attempts to make it.
  • applications start opening with big delay
  • applications start closing with big delay, e.g. I close an application and the place for its cover in main screen stays empty for seconds until the covers rearrange to fill up the gap left.
  • answering/rejecting a call becomes hard - it needs several tries to be able to swipe the screen up/down. Screens feels unresponsive.
  • swiping up/down the app launcher feel a bit "jerky", not fluent as it should be.

After reboot all these symptoms are gone, device feels quick. When I experience that behaviour top does not show any excessive CPU load or something suspicious. I do NOT have alien dalvik installed, there aren't any "big" modifications done, except from stopping tohd.service to get rid of NFC bug. I normally have 6-7 applications open: phone, mail, messages, Twetian, terminal. Developer mode is enabled of course. My question is if everyone else had noticed similar behaviour? If this a common problem, or just my device configuration has the issue?

edit retag flag offensive close delete

Comments

2

I have the same issues here, just as you describe.

I have alien-dalvik installed, but never used. Have developer mode and have made some modifications to notification LED.

Besides what you state above I also get "application not responding" quite often when this happens. I usually have 7-14 apps running, where browser, mail and cutespotify would be the most memory hungry (others are such as people, dialer and calculator). I also note that the display does not blank something like every other time when this behavior is present.

Mohjive ( 2014-01-15 11:06:21 +0300 )edit
4

No such problems here.

elakim ( 2014-01-15 12:22:02 +0300 )edit

I have come across the same issue. At first i thought it was because of some tweaks I had done but undoing them and rebooting the device did not clear the issue (well, obviously it did, for a day or two until the symptoms returned).

typo ( 2014-01-15 13:38:07 +0300 )edit

I have also most of these issues. I will check next time if the reboot does help for a few days. I also noticed when these issues appear that the Jolla store app crashes sometimes when opening the app (don't know if it has something to do with these issues but it came to my mind).

Neo ( 2014-01-15 13:54:52 +0300 )edit

I have the same problems, especially unlocking the phone becomes quite hard after a few days. Animations when swiping between panels often get stuck somewhere in the middle for a second or two. At this point usually six-eight applications are running. I have recently restored to factory settings and have not made any system changes since then.

ih ( 2014-01-15 14:49:28 +0300 )edit

3 Answers

Sort by » oldest newest most voted
0

answered 2014-08-31 11:33:56 +0300

droll gravatar image

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.

1.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).

2.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).

edit flag offensive delete publish link more
1

answered 2014-08-20 09:29:34 +0300

Bysmyyr gravatar image

Maybe you should check this, I had quite similar problems and that was the problem: https://together.jolla.com/question/30822/root-and-home-disks-full-and-causing-various-problems/

edit flag offensive delete publish link more

Comments

My / is 52% used, sdcard 81% so should not matter. And reboot fixes the issues so this should not be the problem. Though brtfs drivers might be contributing, who knowns.

mcfrisk ( 2014-08-20 10:00:42 +0300 )edit

you should check that, I had that problem with 60% use of / and reboot helped also then...

Bysmyyr ( 2014-08-20 10:02:13 +0300 )edit

Then I have to check it and politely say wtf :)

mcfrisk ( 2014-08-20 10:11:43 +0300 )edit
1

I have plenty of space on root filesystem (checked using by btrfs functions). I still occasonally feel that device is sluggish after longer uptime. One possible explanation might be fragmented swap space after filling it up few times of heavy use with multitasking many apps simultanously. You can check the swap usage by fingerterm/developer mode running command:

swapon -s

if the command shows that swap space is fully used then it is possible that swap is fragmented which may cause sluggish response to new tasks like receiving call. At least one of my former device N900 was famous to become sluggish after heavy swap usage (which was common phenomenon because "tiny" main memory space of 256 MB).

pata ( 2014-08-21 17:39:08 +0300 )edit
1

answered 2014-01-15 12:17:02 +0300

foss4ever gravatar image

updated 2014-01-15 12:18:54 +0300

Haven't experienced this. I usually have the device on 2-3 days between reboots, and I tend to recharge once in two days even if I have the tohd.service masked.and battery would probably last twice as long.

Note that I.don't have a SIM card in the phone but just using email, Tweetian, browser, Friends, Tidings, camera etc being connected most always to some public Wifi-network. t

So with this config, no UX sluggishness here :)

edit flag offensive delete publish link more

Comments

Same here, currently 4½ days uptime and no problems. I do have a SIM (that I hardly use) tohd.service stopped and recharging a lot, due to using usb for deploy from qtcreator.

(corrected and reposted)

evk ( 2014-01-15 13:52:07 +0300 )edit

This is a bit off topic, but how long uptime have people got after disabling the tohd.service or using the foil solution vs the earlier situation when NFC is always on?

TimTTK ( 2014-01-15 16:52:07 +0300 )edit

@TimTTK What I've read abt NFC-fix and its effect on battery consumption in diffetent forums, here, Twitter it seems that the battery lasts anything from 2 to 6 times longer with tohd.service stopped (or NFC-tag removed/covered). I even measured this powertop in my device and the power consumption dropped ftom 800 - 1000 mW to 50 - 100 mW in idle. Read the forums for more (reviewjolla by @simo, JollaTides or JollaUsers) there are some pretty convincing results of this workaround (which will be incorporated in the future upgrades very soon to our devices).

foss4ever ( 2014-01-15 18:01:07 +0300 )edit

ok, thanks a lot, I'll look in to it.

TimTTK ( 2014-01-15 18:17:33 +0300 )edit

btw, why this is here, this is not an answer to problem?

Bysmyyr ( 2014-08-20 09:29:01 +0300 )edit
Login/Signup to Answer

Question tools

Follow
7 followers

Stats

Asked: 2014-01-15 10:36:33 +0300

Seen: 1,174 times

Last updated: Sep 02 '14