Hi everyone, I recently ordered my jolla C2 and I was so excited.
i just had the time to set it up but something’s been bothering me, the phone is so slow on android apps ! Scrolling makes my head ache and it’s quite exhausting having to wait constantly for the phone to react when pressing a button.
I am running the latest update (5.0.0.67) and I downloaded MicroG’s latest versions too. Any idea on how to fix this? I’m seriously thinking on returning it if I still can and getting a google pixel with CalyxOS…
Thanks in advance and goodnight !
3 Likes
You cannot do anything about it. It’s a problem with the C2’s very slow CPU and GPU, as well as the (yet) extremely poor code optimization by Jolla. The C2 has an overal sluggish feeling to me.
4 Likes
What apps are you using? On my C2 apps such as Firefox, Spotify, banking are working just fine, nothing like what you described. Yes it is not a top tier device but It is a similar experience to different sailfish phones I had - scrolling is fluid, no waiting for touch input.
What is your CPU/Memory utilization on idle, isn’t there anything eating up resources?
If all looks ok resource wise, I suggest you to try removing Appsupport completly like described in “Brutal way” paragraph
Reinstall AAS couple of apps on vanilla version. If they work fine then proceed with microG etc.
As a last resort you can always try reflashing.
I have basic apps such as mail, messaging, banking, calendar… How do I look up cpu usage?
You can do it in the terminal:
- ‘top’ shows a list of processes sorted by CPU utilization
- ‘free -m’ shows you a memory consumption, including the swap file
There are also two graphical tools I am aware of: Lighthouse and Crest but I haven’t used them personally.
Just to clarify, on which apps are you experiencing the slowdowns, are those native or android ones? How many android apps have you installed?
2 Likes
Thanks ! I have 13 android apps though it has been slow since the first one (Fdroid). It seems like it’s only slow on android apps.
I’ll try to access terminal and come back to you
The same meaning about here from my side. What helps here was to reduce the laggy performance with masking the zram swap file. So the C2 isn’t working with the slow hard drive anymore and keep all things inside the faster RAM.
But compared to the Xperia 10 III which I also use, the C2 is a lame duck.
Just for the sake of correctness, zram is not a ‘hard drive’ and neither really a file. It is a virtual block device located inside of a ram, that compresses the data put into it, on the fly with zstd. It is being used in sailfish as a swap device and I agree that swapping into zram and out introduces unwanted delays. C2 seems to be a swapping a little bit too agressively - you can even notice that swap is being used right after the boot. Disabling the zram might help and it probably won’t hurt as 8 GB seems to be enough for most use cases.
2 Likes
how is this done and what would be side effects?
Just try to log into root account
devel-su
and disable the swap, which works until next reboot
swapoff -a
To me, there are no side effects. You have to work with the systemd to get it permanently working.
At first locate the correct name of the swapfile
systemctl status "*.swap"
Then mask the swap file with devel-su or your user on the phone has sudo rights (like mine)
sudo systemctl mask swapfile.swap
If there are troubles just unmask the swap with
sudo systemctl unmask swapfile.swap
This will survive a reboot and also a SFOS update.
2 Likes
Yeah, my bad. I was just stuck with the regular swap file. Did you know why SFOS pumps more than 500 MB on startup into the swap? It’s very uncommon for a Linux system.
My Xperia 10 III do the same btw.
I dont see or feel any difference now. Scrolling and loading has the very same speed / sluggishness